SliTaz Forum
You are not logged in.
If simply load standart initrd made by well known cat4321>rootfs - it works!
Loading it, running tazusb writefs gzip, overwriting initrd to new, reboot - error.
I tried both gzip and lzma, rc1 and last rolling, (really, every time before load I checked for right kernel bzimage file) add or remove root=/dev/null kernel option - all kernel panic.
root=/dev/ram, I found while searching also not helpful.
but in april version (before RC1) it just works.
/init not changed. I was even tried to overwrite /usr/bin/tazusb to before-rc1-version - no changes.
There was dbus loading problem since rc1- due to rewritten rcS. Maybe this is some connections.
[attachment=30733,1543]
i never use any NTFS on this drive. Two images for different kernel options (/dev/null...)
[attachment=30733,1544]
Offline
Why did you 'cat4321>rootfs'?
SliTaz is designed to load as many of the squashfs files as there is for the amount of memory available.
Who cares on design while main code not working. I'm talking about [c]cat rootfs4.gz rootf3.gz rootfs2.gz rootfs1.gz > rootfs.gz[/c]
just made it shorter - who used it - knows what I mean.
Anyway bug is not here.
Offline
I confirm this problem which also plagues [c]tazlito writefs[/c] which uses the same code.
Offline
Loading from iso:
base, justx -> tazusb writefs = bug free!
gtkonly, core --> tazusb writefs = kernel panic
so, problem located somewhere in rootfs2.gz
Offline
Heh, I've unpacked all the rootfs, one-by-one to the ext4 partition and I got the same result. It was about a week ago. Then I formatted partition as ext3, ext2 but no luck. And then I gave up, left without install the distro to my hard drive. But... Stop. It loaded using ntldr + grldr + rootfs1..4 as usually. Or?..
Offline
It seems I found it. Bug caused by util-linux-mount from gtkonly+core.
If loading multiple initrd (even cat'ed) - looks like /bin/mount from base flavor is used anyway before repacking.
util-linux-mount overwrites base busybox-builtin /bin/mount
I think, it have to be moved from /bin to /usr/bin.
for all 4 files in /util-linux-mount-2.24/fs/bin
also dbus service failed to start after repacking justx (rootfs4+3).
/var/run must be excluded here:
/usr/bin/tazusb line 479 must be
[c]for dir in /proc /run /sys /tmp /mnt /media /var/run[/c]
same must be for tazlito. not tested it yet
Offline
little mistake, not all /var/run ,just /var/run/dbus/pid like in bootlog message error
Note about main topic bug - uninstalling util-linux-mount NOT solving error. /bin/mount /bin/mountpoint /bin/umount overwritten by it. So I move it to /usr/bin and unpack 3 base files from [c]lzma d rootfs4.gz rootfs4.cpio[/c]
Then made tazusb writefs gzip and now it works for me. I hope it will be in repository, no way to release with such critical bugs.
Offline
Thanks for all the research, az_ua. I have the same problem with tazlito writeiso lzma, which I reported a couple of days ago here. So, I just booted the 5.0-rc2 CD as "Just-X", set-up the keyboard, added a few applications and then gave it another go with tazlito. And this time I got a bootable ISO that worked. Great! The only fly in the soup was that the original CD wouldn't automatically eject, something I never encountered when I tried to make a new CD out of "SliTaz Live" ...
Exit or burn ISO to cdrom (Exit|burn) burn
eject: /dev/cdrom: Input/output error
Please insert a blank cdrom and press ENTER
Offline
Fix one problem and break something else in the process.
Busybox eject has been broken since the post 4.0 release of cooking/5.0 because the live cd in the drive is auto mounted when spacefm/pcmanfm starts.
Busybox eject doesn't umount the drive so eject fails unless you umount in terminal prior to eject.
This was a problem with spacefm as well.
Util-linux-eject works because it umounts the disk before it ejects with it's depend util-linux-mount.
Offline
it effects also the slitaz-rolling-core.iso - stops with the same kernel panic
Offline
Nobody want to fix it?
Solution was ready almost 2 days ago in my post above, even few hour before full-of-errors slitaz-rolling-core.iso was auto?-generated.
So, just move /bin files from util-linux-mount to /usr/bin, it is not right place for it. /bin/mount depends on /usr/lib/libmount, but it is not accessible exactly while booting 1-part(NOT-4in1)rootfs.
by the way I also preparing fixes for dbus+tazusb now. But for starting only. troubles began because /var/run/ now not equals /run/
offtopic! Still struggling hard with multiple instances os dbus-daemon after re-login. Can't got why /etc/xdg/autostart/pcmanfm link executing via dbus, also it should be running after lxpanel(which runs menu-cache) to get application in sidepanel working.
Offline
@bellard
/bin/mnt? Interesting way to solve it. I hope /bin/mountpoint is not in use. Thanks for feedback.
Also after boot writefs-gen'ed rootfs dbus failed to start and tazpanel running only manually due to /var/run is old+saved.
My edits:
/var/run to /run in [c]/usr/bin/tazpanel[/c] PIDFILE=/run/$NAME.pid
[c]/etc/init.d/dbus[/c]
line 26 and 46 now looks like
[c]mkdir -p /var/run/dbus && ln -s /var/run/dbus /run/dbus[/c]
(old one was mkdir -p /run/dbus) and it seems to be improperly with current PIDFILE=/var/run/dbus/pid
Including above-described, my error-free rootfs was made by modified tazusb with exclude folder in line 479: [c]for dir in /var/run/dbus[/c]
UPDATE
I think this is better for dbus
[c]mkdir -p /run/dbus && ln -s /run/dbus /var/run/dbus[/c]
some little troubles with icons: pcmanfm was no icon in menu - I change it to "computer" like in mc.desktop file. No icon anywhere for gpicview.
Offline
@az_ua
Where you see /bin/mnt?
Really [c]mnt[/c] is function with goal to substitute [c]mount[/c] (which can be /bin/mount or in your variant also /usr/bin/mount) to [c]busybox mount[/c] (where busybox binary is /bin/busybox, and "mount" is option for busybox). So this construction always uses busybox's mount function regardless of existence or absence or substitution of the /bin/mount.
http://hg.slitaz.org/slitaz-boot-scripts/rev/79aea3c677ca#l1.7
Offline
Core iso built with slitaz-boot-scripts-5.6.2 kernel panics.
Offline
There still seems to be no solution to the problem az_ua describes in the previous posts:
- ISOs generated with tazlito out of Live, Core or GTKonly panic on boot-up
- ISOs generated with tazlito out of JustX boot without a problem
In the latest version of tazlito there's now an "umount" ahead of the eject command, which solves the problem with the failing auto-eject after generating the ISO image. But there are still other problems which are related to this. Burning or blanking CDs fails for the same reason. It seems, every CD that's loaded gets instantly mounted which prevents wodim from doing its job. In Live, Core or GTKonly the PCManFM configuration could be responsible for the auto-mounting of loadad CDs. But as the problem also occurs in JustX there has to be some other process which mounts the CDs. The solution would be to either prevent CDs from being auto-mounted or to put an "umount" ahead of any process that stumbles over a mounted CD.
In SliTaz 3.0 CDs were not auto-mounted. Even the system CD wasn't mounted after boot-up and tazlito would only temporarily mount the system CD to pull in some stuff needed for the new ISO. But SliTaz 3.0 was using hal and things are different now. Still, if this is possible, I think it would be generally better not to auto-mount CDs.
Offline
Booting CD by System Tools-Create a LiveCD.
Now it is totally new Error.
In first post old panic was just after Freeing unused kernel memory.
Now next step (Switching to clocksource tsc) passed, then HANGS for a minute, with showing input: ImPS/2... (before udevd[ starting in saved to file bootlog)
If no reset and wait - I can see
init SEGFAULT in libc2.14
This is not mount failed.
boot&HDDinstall of rolling iso works (rolling-core even not starts). This iso built with old init bootscripts.
After loading from HDD, I did tazusb writefs, load, and it works. Without dbus+xorg starting, but loaded, with util-linux-mount is present in tazpkg -l output!!!, mount -? shows that busybox-ver used = and no panic with old /init!
I will try it over, but now I begins to think, that topic-starting error caused only if current / is in RAM, like running tazusb from livecd, but nobody who using HDD-installed / can confirm it.
Anyway, 5.6.2 boot-script looks like fixes nothing. Even more, what works before not works now, but this may be my hardware specific problem.
For tazusb it is possible to use files from old rootfs4.gz as I described few days ago. But really no solution for downloaded by tazlito-wiz.
Offline
@az_ua
Virtualbox:
Boot into 5.0-rc2 in virtual cdrom drive, use tazinst(full install script) cdrom as install source,syslinux as bootloader,virtualbox hard drive image(ext4) as install target.
tazinst syslinux install bug:
Boot of install fails with "Could not find kernel image: vesamenu32"
Boot into live cd,mount hard drive image, copy /boot/isolinux/vesamenu32 to /boot/syslinux on image.
5.0-rc2 full install boots to desktop with no errors.
Recharge/update all packages
5.0-rc2 full install boots to desktop with no errors.
Slitaz-base.iso built with slitaz-boot-scripts-2.6.2 halts on boot before "Switching / to tmpfs..."
[c]tazlito clean-distro[/c]
Edit distro-packages.list to use slitaz-boot-scripts-2.6.1
[c]tazlito gen-distro[/c]
slitaz-base.iso boots to login
Offline
my previous message was about iso 2014-Jun-08
rolling works rolling-core not
Now about following, just found it
slitaz-rolling-core.iso 2014-Jun-10 20:23:05
slitaz-rolling.iso 2014-Jun-11 00:34:03
no loading, in any flavor, even base.
no init segfault like in tazlito-wiz generated
no kernel panic, just hangs
if try in virtualbox-high CPU usage.
by the way coommand for virtualbox start
insmod /lib/modules/3.2-slitaz/misc/vboxdrv.ko
At first I think cancelling to 5.6.1 bootscripts needed
But maybe this will help
looks like excess enter
1.44 do echo "Loading module: $i"
1.45 - modprobe $i 2>/dev/null || insmod $(find /lib/modules|sed "/$i.ko/!dq")
1.46 + modprobe $i 2>/dev/null ||
1.47 + busybox insmod $(find /lib/modules|sed "/$i.ko/!dq")
1.48 done
http://hg.slitaz.org/slitaz-boot-scripts/rev/79aea3c677ca
Offline
[ Generated in 0.018 seconds, 7 queries executed - Memory usage: 1.58 MiB (Peak: 1.77 MiB) ]