SliTaz Forum
You are not logged in.
Hello,
I'm new here & to SliTaz Linux. 
I'm trying to install SliTaz on the harddisk. I downloaded the file slitaz-4.0.iso & tried to install on harddisk following this guide: http://doc.slitaz.org/en:handbook:installation
However, there's only one "rootfs.gz" in the guide but there are 4 "rootfs.gz" type files in the CD.
So I was confused & the differences I made during installation are these:
####################################
lzma d rootfs1.gz -so | cpio -id
lzma d rootfs2.gz -so | cpio -id
lzma d rootfs3.gz -so | cpio -id
lzma d rootfs4.gz -so | cpio -id
......
rm rootfs* init
####################################
After reboot, the boot process stops at a "kernel panic" message 
(I'm trying to upload a pic of it)
These are the contents of the partition where I attempted the installation:
#####################################################################
$ls
boot lost+found
$ ls boot/
bin etc home media proc run sys usr vmlinuz-2.6.37-slitaz
dev grub lib mnt root sbin tmp var
#####################################################################
How to solve this problem?
Thanks.
[attachment=16959,688]
Offline
Make the boot directory,copy the kernel:
[c]# mkdir /mnt/target/boot[/c]
[c]# cp -a /media/cdrom/boot/vmlinuz-* /mnt/target/boot[/c]
Copy the 4 rootfs.gz
[c]# cp /media/cdrom/boot/rootfs*.gz /mnt/target[/c]
Change into the directory with the rootfs*.gz
[c]# cd /mnt/target[/c]
Combine the 4 rootfs.gz into 1 rootfs.gz
[c]# cat $(ls -r rootfs*.gz) > rootfs.gz[/c]
Extract the file tree from rootfs.gz
[c]# lzma d rootfs.gz -so | cpio -id[/c]
Remove init and the rootfs*.gz
# rm init rootfs*.gz
Offline
Hi,
Thanks for you reply & explaining installation steps. I did those after formating the drive.
Now, stuck at installing grub.
--------------------------------------------------------------------------------
root@slitaz: /mnt/target # grub-install --root-directory=/mnt/target /dev/hdd12
Could not find device for /mnt/target/boot: Not found or not a block device.
--------------------------------------------------------------------------------
I think I'm using the same command I tried first time, which worked. This time it's not working.
Note, I need to "chainload" this with other Linux.
What to do now?
Thanks.
Offline
Grub is installed to Master Boot Record of drive,not the partition.
Reference: http://doc.slitaz.org/en:handbook:installation => GRUB Boot-Loader
Otherwise, to install GRUB onto the MBR (Master Boot Record) using a root directory of /mnt/target (the target mounted partition) and the disk named hdd, use the following command and note the lack of a partition number:
[c]root@slitaz: /mnt/target # grub-install --root-directory=/mnt/target /dev/hdd[/c]
Offline
I tried this time with /dev/hdd & it's installed but after reboot it's the other Linux (fedora)'s Grub, which installed on /dev/hda.
Any way to work around this?
Thanks.
Offline
Boot into fedora and edit the grub menu so it gives you a menu entry to boot the slitaz install.
How you do this depends on if fedora installed grub legacy or grub 2.
Reference:
grub legacy=> http://members.iinet.net.au/~herman546/p15.html
grub 2.0=> http://members.iinet.net/~herman546/p20.html
Dualboot=> http://members.iinet.net/~herman546/index.html
Offline
The fedora grub detected Slitaz after I run the "grub-mkconfig" (found on Internet search).
But it gives a kernel panic. I uploaded a picture, please check.
I'm checking those reference links. Thanks for providing.
From what I've seen about Slitaz by Live CD, I'm actually liking it as a Light Linux distribution.
[attachment=16984,690]
Offline
you should put a better picture, that one is truncating the message on the screen which may have the info we need
I have hit a similar problem several time and this was tied to either
-not specifying the correct sdaX or hdaX in grub (as read by Slitaz, not necessarily as understood by fedora), in which case some (boring) trial and error is required
- not enough time allowed to mount the device where / has been installed
Add rootdelay=9 in the grub menu for the slitaz OS, this may solve that last issue (it did for me)
Offline
0. Flash-card 8 GiB sda1 formated as ext2/ext3/ext4
1. Grub-loaders installed on sda (not sda1), firstly Grub4Dos, secondary GRUB2
2. Under SYSLINUX-bootloader all is fine.
Variants of Grub4Dos loading slitaz:
------------------------------------
title SliTaz GNU/Linux (cooking sda1) (Kernel bzImage slitaz)
root (hd0,0)
kernel /boot/bzImage root=/dev/sda1 quiet
title SliTaz GNU/Linux (cooking hda1) (Kernel bzImage slitaz)
root (hd0,0)
kernel /boot/bzImage root=/dev/hda1 quiet
title SliTaz GNU/Linux (initrd rootfs.gz) (Kernel bzImage slitaz)
root (hd0,0)
kernel /boot/bzImage root=/dev/sda1 quiet
initrd=/boot/rootfs.gz rw lang=ru_RU kmap=ru config=UUID=5bd805eb-940b-4a29-a146-2fef3b893ebc,install.sh root=/dev/null vga=normal autologin home=UUID=5bd805eb-940b-4a29-a146-2fef3b893ebc
Variants of GRUB2 loading slitaz:
---------------------------------
### BEGIN /etc/grub.d/10_linux ###
menuentry "GNU/Linux, with Linux 2.6.37-slitaz" {
insmod ext2
set root=(hd0,1)
linux /boot/bzImage rootdelay=8 root=/dev/sda1 home=sdb autologin
initrd /boot/rootfs.gz
}
menuentry "GNU/Linux, with Linux 2.6.37-slitaz" {
insmod ext2
set root=(hd0,1)
linux /boot/bzImage rootdelay=8 root=/dev/sda1 home=sda autologin
initrd /boot/rootfs.gz
}
As result: "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown block(0:0)"
// variants: on unknown block(0:8) on unknown block(x:y) on unknown block(x:yy)
!!!unknown block!!!
Offline
i think you have problems with your addressing scheme
if you have another (fixed) hdd, which is likelyn then shouldn' the flashcard be adressed ad hd1,1 and the root as /dev/sdb1
(or any other numbering depending on your system)
Unless someone is fluent with grub it may take a while to debug
you can check eg http://www.linuxquestions.org/questions/ubuntu-63/grub-drive-designation-dev-sda1-hd-1-0-a-624330/
The full screen including the message just before the crash may have valuable informations (eg the name of the partition which is not found), you should provide it; not just the latest error message: we already know there is a kernel panic on the way...
Offline
Photographed the camera.
The information quickly runs on the screen.
Here last screen.
That will do?
If the previous screen of a conclusion I will practice is necessary and I will send.
[attachment=17108,693]
Offline
Loading SliTaz 4.0 over grub2
It's 2 last screens in 1 picture
Offline
Thanks for all the comments.
I retied the whole process. This time installed grub onto /dev/hdd12 , then added "chainloader" in Fedora grub & it works (I guess)!
But new questions:
1) SliTaz boots onto console/text mode, how to switch to Graphical desktop as seen on Live CD? (uploaded a picture of logged on screen)
2) What to add in SliTaz grub/menu.lst so it'll auto boot after a time period (now it shows SliTaz's grub & stops there till I press 'Enter')?
Here's what inside menu.lst:
######################################################################
title SliTaz _4.0
root (hd1,11)
kernel /boot/vmlinuz-2.6.37-slitaz root=/dev/hdd12 vga=normal
######################################################################
Thanks.
[attachment=17111,696]
Offline
Is it one problem or two problems here ? slimkin vs fail2, it is the same person ?
Slimkin, it sounds to me the loading device is sdb not sda, try correcting grub with root=/dev/sdb1 and also add the rootdelay=9 instruction as i recommended, I think it will boot.
ONLY change the lines with root=/dev/sda1
since at least it is able to boot.
I would remove the home=sdX inxtruction also, until it boots; once it boots you will be able to change that, if required.
I also had to fight for a while with grub to start my old slitaz version after i had upgraded my configuration, and had moved the disks around.
For the machine booting to console, what does it say when you start from root:
# slim
?
Offline
fail2 - is topicstarter.
slimkin is only new member.
Thanks christophe.
Offline
Should I start a new topic?
Offline
ok let me know if that works. I think it will or may need some trial/error, i am not a grub expert, but I would swear you are hitting the same pb i did hit recently...
Offline
Hi, christophe!
My report:
http://forum.slitaz.org/topic/slitaz-40-on-flash-card-persistent-frugal-grub2-loader#post-17191
Offline
sklimkin= my underderstanding is that all your pbs are solved
Fail2: no, we can continue here. I just confused the 2 problems for a while
So, when you login as root, what happens when you say
# slim
I think there is a slim log in /var somewhere, any hint there ?
Offline
@christophe
"........Fail2: no, we can continue here. I just confused the 2 problems for a while
So, when you login as root, what happens when you say......."
Hi,
I thought mine is no longer a Kernel Panic problem, so I started a new topic here:
http://forum.slitaz.org/topic/graphical-desktop-how
Please check.
Offline
[ Generated in 0.016 seconds, 7 queries executed - Memory usage: 1.57 MiB (Peak: 1.77 MiB) ]