I'm a Slitaz noob, usually running some Ubuntu distro.
I downloaded the new 4.0 RC1 and made a bootable usb drive with it using unetbootin, but it crashes during startup with a kernel panic message on two different computers. Have I done something wrong? The method I used works with the 3.0 Slitaz distro.
Any suggestions are welcome, but I only know basic terminal commands, so go easy on me ;)
4.0-RC1 crashing on boot-up with kernel panic - HELP?
(42 posts) (10 voices)- Started 13 years ago by llexam
- Latest reply from eee2guser
- This topic is resolved
-
Posted 13 years ago #
-
Try adding rootdelay=8 to kernel boot code when unetbootin's menu appears.
Posted 13 years ago # -
I tried adding rootdelay=8 to the boot code, with no change in the error message on either computer.
It looks like possibly a dual error: filesystem could not mount root, and kernel panic.
I tried re-formatting my usb device with ext2, ext4, and FAT (ext3 not an option), with the result of 'operating system not found' when I try ext2 or 4 (but FAT works fine).
None of that is an issue if I make a Slitaz 3.0 usb boot (using FAT).
Any more suggestions? I would really like to try running this new RC.Posted 13 years ago # -
Hi,
I guess unetbootin dont magae correcly our new 4in1 ISO wich have now 4 rootfs.gz instead of 1. Maybe better to boot from a burned cdrom and them create a LiveUSB with SliTaz home made tools.
I dont have any Windows system to make test but your can try out TazUSB for Windows to create bootable SliTaz Live USB from windows – http://is.gd/TazUSBexe
- Christophe
Posted 13 years ago # -
@pankso
This I tried yesterday. I booted frugal: the directory slitaz.4 contained /slitaz/boot/bzImage and the different rootfs.gz-files, 1-4. I got this kernel panic booting manually from grub with rootfs1.gz till rootfs3.gz, only rootfs4.gz booted, but I could not get a working Xorg-server.root (hd0,1)
kernel /slitaz.4/boot/bzImage root=/dev/ram0 rw nomodeset
initrd /slitaz.4/boot/rootfs1.gz
bootIf you tell me what kind of log would be of use for you I could repeat that (later).
Posted 13 years ago # -
Take a look on cdrom at /boot/isolinux/isolinux.cfg. Your grub config will be :
root (hd0,1)
kernel /slitaz.4/boot/bzImage root=/dev/ram0 rw nomodeset
initrd /slitaz.4/boot/rootfs4.gz /slitaz.4/boot/rootfs3.gz /slitaz.4/boot/rootfs2.gz /slitaz.4/boot/rootfs1.gzor
root (hd0,1)
kernel /slitaz.4/boot/bzImage root=/dev/ram0 rw nomodeset
initrd /slitaz.4/boot/rootfs4.gz /slitaz.4/boot/rootfs3.gz /slitaz.4/boot/rootfs2.gzor
root (hd0,1)
kernel /slitaz.4/boot/bzImage root=/dev/ram0 rw nomodeset
initrd /slitaz.4/boot/rootfs4.gz /slitaz.4/boot/rootfs3.gzor
root (hd0,1)
kernel /slitaz.4/boot/bzImage root=/dev/ram0 rw nomodeset
initrd /slitaz.4/boot/rootfs4.gzPosted 13 years ago # -
I burnt a CD. It boots without problem. But no way to get a working Xscreen. Nouveau failed even when I booted with nomodeset in the command line.
It always ended up in ,,Found no screens". - I give it up now, other things to do. The ,,rest" of my different slitazes work well. But apparently this new Xorg thing has many, many issues, especially in case one uses nvidia graphic cards of mixed ages.Posted 13 years ago # -
@michaelbischof You booted last 4.0-RC1 without any modification (not a custom build) ? If yes and Xorg dont start with a standard Nvidia card then we are in trouble... I might have stripped down too much Xorg... on this version the package is called xorg-server-light and it means what it means, I remove all dri/drm dependencies to avoid mesa and friends on the ISO.
I have done a contributor flavor at the same time than 4.0-RC1 but with a lot more package include Xorg with intel, nv, ati, geode drivers and mesa. If this one boot you to the desktop then we have found the bug and we will think about having full Xorg by default.
Thanks a lot for these feedback, without the users community we could not fix and make SliTaz better :-)
- Christophe
Posted 13 years ago # -
initrd /slitaz.4/boot/rootfs4.gz
is a text only flavor.initrd /slitaz.4/boot/rootfs4.gz /slitaz.4/boot/rootfs3.gz
is X11 only flavor (no wm)The full flavor is
initrd /slitaz.4/boot/rootfs4.gz /slitaz.4/boot/rootfs3.gz /slitaz.4/boot/rootfs2.gz /slitaz.4/boot/rootfs1.gzPosted 13 years ago # -
Ok,
but I cannot promise to have done this in a minute. Anyway - stay tuned! (As usual I will first try to boot from a frugal setup, not from CD)In the last month the only version of slitaz that I could start with an Xscreen without further trouble was this Xvesa-flavor. For me it is no problem - but when I hand it over to a pupil there is no hope. The do not work in front of a black screen! ;-)
Posted 13 years ago # -
Look at your watch!
This functions nice - some more feedback: it runs with nouveau, without nvidia, but looks better than the old cooking. Heaven knows why! ;-)
Yes, handsome I would say. Better icons...With firefox plus icedtea installed it has 340 MB space - in this form I would give it to pupils. Because only then they can run, if needed, LibreOffice (but as => AppRun, not installed!).
<= But the next question I will ask is: how can it come that this Kompozer does not run within Slitaz-devel? It runs well with Slitaz 2.0, you just click on the executable file kompozer - that's it!Posted 13 years ago # -
SOLVED: I found a command line from another distro (crunchbang) that was successful in making a bootable usb with no start-up errors or crashes with 4.0-RC1 on two different computers. Here's the command line I used in case anyone else needs it:
sudo dd if=/path/to/iso/slitaz-4.0-RC1.iso of=/dev/sdb bs=4M;sync
SUMMARY: unetbootin does not make a properly bootable usb, use terminal command line instead.
Posted 13 years ago # -
@pankso
If you find some time to explain here a bit in details what exactly you did with this http://is.gd/TazDevISO that worked nice out of the box?
To enjoy that it works is one thing - to understand why it works another one.Posted 13 years ago # -
> You booted last 4.0-RC1 without any modification (not a custom build) ?
> If yes and Xorg dont start with a standard Nvidia card then we are in trouble...... we are indeed. For me it's been like that since the official cooking version from last May and with all the rolling versions I have tried since (at least half a dozen). Needless to say that it's still like that with the current RC. But as nobody ever complained about the issue I thought that my hardware was to blame ... a fairly standard mobo (Asus P5KPL-AM SE), a Pentium D 820 CPU and a slightly outdated Nvidia PCI Express card (G72, GeForce 7300 SE/7200 GS). So, I decided to let Slitaz 4 pass and stick a while longer with Slitaz 3, which has been working wonderfully well since almost 2 years now. But, wo knows, maybe there's still hope? Maybe someone will address the issue and I'll be able to update to the new version ???
Posted 13 years ago #
Reply »
You must log in to post.
