SliTaz Forum
You are not logged in.
Pages: 1
Is it just me or is there a pb with tazusb and rolling ?
I get a kernel panic when rebooting a usb key with rolling after tazusb writefs 
Offline
Have you tried "rootdelay=10" ?
Offline
Which is why I'm looking into building a version using buildroot that's compatible with the cooking packages. If I automate the process enough, I'll allow you guys the chance to use it to build your own versions (with PAE, 64bit, arm, etc) too.
Offline
Yes; I think i have seen that rolling automatically adds a rootdelay when booting.
What puzzled me is that this is a "standard" version of rolling (with roofsgz1.gz -> rootfs4.gs it boots from usb without problem)
I then just did a tazusb writefs, which creates a single rootfs.gs. Nothing else changed (except, modified the booting command accordingly, obviously). Tried both without and with gz compression
the first line of trouble i see says
[c]mount: mounting tmpfs on /run failed: No such file or directory
/init: line 119: can't creat /run/ini: nonexistent directory
tee: /run/boot.log: No suche file or directory[/c]
the system then detect psmouse, the touchpad, some usb device then complains again
[c]mount: mounting /run on /mnt/run failed: no such file or directory
/init: line 179, can't create /run/init: nonexistent directory
/init: .: line 119: can't open '/run/init'
Kernel panic - not syncing: Attempted to kill init !
Pid: 1, comm: init Not tainted 3.2-slitaz #4
Call trace
[then trace log][/c]
Is it just me ??
Offline
No, it's not just you. TazUSB is broken and it generates broken linux systems as can be shown with the mounting and the linux taint error.
Offline
ok thanks
I'll wiat until that gets fixed sometime later in the process....
Offline
I think it's up to us to fix it. I'll have a look when I try integrating the scripts in my own build. I might as well fix things as I go.
Offline
christophe,
mount: mounting tmpfs on /run failed: No such file or directory
Something strange because package slitaz-base-files-5.4.1 includes /run folder into it. I downloaded a package slitaz-base-files-5.4.1.tazpkg from mirror, and extracted it, and /run is here.
Trixar_za,
TazUSB is broken and it generates broken linux systems
I think, it not very broken while I use now my customized rootfs.gz in the SliTaz 4.0 produced with tazusb writefs.
But time passed, and maybe TazUSB now have new bugs, who knows…
Then I knew that fact of successive rootfs.gz creating is depending of:
[*]size of your RAM,
[*]number of packages that you installed over standard ones.
Now my RAM is 1 GiB, and rootfs.gz is 176 MiB (I know, its big!) and all works.
If you run SliTaz frugal, the filesystem is resided in the RAM.
When you create your rootfs.gz using tazusb writefs, your rootfs.gz created in the root (/) — in the RAM again.
So, its very easy to get corrupted rootfs.gz because of the small size of the RAM. Corrupted rootfs.gz have no several files, and you get kernel panic.
I think, its better to rewrite TazUSB to make rootfs.gz out from RAM — directly on the hard disk, or on the USB-flash disk. Then you'll get unlimited in size, not corrupted, archive.
_____
Guys! Last time (maybe, two weeks) I'm under massive rewriting (not refactoring) of slitaz-base-files, slitaz-tools, and tazusb. I rewrite old gtkdialogs using Yad, implement wide using of /lib/libtaz.sh and some more ideas. These projects seems unmaintained for long time, and I have a lot of changes, every of that I want to double-check if it works correctly, and these projects depends one from another… So, I'm in no hurry with changes committing into Hg repos. Please, if anyone want to make changes into TazUSB, not change it globally. Thanks!
Offline
Aleksej: Can you email me your changed packages in tar.gz form?
Offline
mount: mounting tmpfs on /run failed: No such file or directory
....
mount: mounting /run on /mnt/run failed: no such file or directory
boot and autologin OK.
--- tazusb-orig
+++ tazusb
@@ -457,9 +457,9 @@
status
# Create list of files
- find /bin /etc /init /sbin /var /dev /lib /root /usr >/tmp/list
+ find /bin /etc /home /init /sbin /var /dev /lib /root /usr >/tmp/list
- for dir in /home /proc /sys /tmp /mnt /media /media/cdrom /media/flash /media/usbdisk
+ for dir in /run /proc /sys /tmp /mnt /media /media/cdrom /media/flash /media/usbdisk
do
echo $dir >>/tmp/list
done
Offline
@christophe - I use "tazlito writeiso lzma" without a cdrom mounted - it creates a rootfs in /home/slitaz.....
take care, that you have an empty /home directory, when you run it..... otherwhise the iso is a monster...
Offline
@trixar_za + Aleksej
maybe it has something to do with this change of bellard
http://hg.slitaz.org/tazlito/rev/04a0a9b9df91
after this change tazlito was working - before there was also kernel panik
Offline
Pages: 1
[ Generated in 0.022 seconds, 8 queries executed - Memory usage: 1.55 MiB (Peak: 1.77 MiB) ]