SliTaz Forum
You are not logged in.
Pages: 1
Every time I check slitaz I'm really amazed how much they put in a 30MB distro.
Still, I am unable to install it and have it working, I'm sure it must be something stupid, but I can't seem to fix it no matter what I try, so better asking for help.
I did this: I boot the pc with the livecd/liveusb, I run tazinst as root, make the new profile, edit it to install on a free partition, check it, all ok, I install, boot the other OS (linux too), grub-update, reboot, select slitaz entry, and get a kernel panic. Grub2 doesn't like slitaz? I am missing some boot parameters?
Then I tried installing on a usb key, same procedure (just re customized the .conf), but when I boot from it it tries to boot from the hdd... and it hangs.
I scrapped using a liveusb with home=usb or home=UUID cause it doesn't remember installed modules, just some settings of them, really strange, seems like a permission issue, stuff is just incomplete.
So, what I'm asking is a kind soul to please help me with the HDD install, and the USB install.
tazinst is really nice, I think it's working, but there must be something else I'm missing.
Offline
If you boot your other OS and look into the installed slitaz - everything ok there?
You have a directory /boot, a kernel? Can you show here what is inside that directory?
- With Grub2 I cannot help you, did not learn it yet. A harddrive-install here look from another OS' grub2-grub.cfg-file like this:
}
menuentry "slitaz 3.0 hdd sda8 UUIID vmlinuz-2.6.30.6-slitaz (on /dev/sda8)" {
insmod part_msdos
insmod ext2
set root='(hd2,msdos8)'
search --no-floppy --fs-uuid --set b6a998e7-7105-4865-82c0-fad6ee514df2
linux /boot/vmlinuz-2.6.30.6-slitaz root=UUID=b6a998e7-7105-4865-82c0-fad6ee514df2 ro resume=UUID=b6a998e7-7105-4865-82c0-fad6ee514df2
}
and most likely yours should be similar. - USB-installs I did not do yet.
Offline
Well, you kind of solved the HDD install issue: I booted the other OS, and examined the grub menu entryes, which turned out to have slitaz mapped on sdb3, while it should be sda3, since the HDD is sda, it's the only one, and all other OS are mapped in sda partitions. I'm puzzled on why it happened.
Modding by hand grub2 files isn't the way, and if I update kernel on the other linux I'll probably have to redo this fix, but so far it's fixed. Thanks a lot.
Now, I need to fix the USB install to. I already tried the same fix, so far no luck.
Offline
edit: I poked around the usb install some more, I had it working using home=sdx. but this doesn't really solve it, cause if I use the usb key on another PC it won't work. I tried passing the UUID, but it goes kernel panic, can't find the /home, even giving rootdelay.
Please, can someone help me with another little push? Thanks.
Offline
Easy Live USB Install:
Boot into SliTaz Livecd
[1]Applications/System Tools/GParted Partition Editor
Format the USB flash drive with ext3 filesystem.
Don't use fat32 or NTFS filesystems which break login.
Write down the USB flash drive Partition device name.
[2]Applications/System Tools/Create a LiveUSB
Your booted into livecd,leave ISO Image: (None)
Select the USB Media: device name from previous step.
Click OK button
Offline
I did that, but it doesn't retain changes.
If I edit it manually to root=sdx it works, but with portability in mind it should be better to use UUID, which doesn't seem to work.
Offline
tazusb script adds blkid of install partition to /boot/extlinux/extlinux.conf home=
root@slitaz:/home/tux# blkid
/dev/sdc1: UUID="2c55c420-760a-4fa3-871b-64191dcc338a" TYPE="ext2"
/boot/extlinux/extlinux.conf :
append initrd=/boot/rootfs.gz rw root=/dev/null vga=normal autologin home=2c55c420-760a-4fa3-871b-64191dcc338a
Offline
May be one addition more:
,,how" your machine ,,sees" the harddrive depends on its kernel. It can happen, e.g.,
that your slitaz kernels says /dev/hda while another distri booted on the same machine says /dev/sdc.
Using blkid:
I recommend
#blkid -g
#blkid
, return. Then use the output. The first commend kind of cleans the program.
Offline
@michaelbischof
The UUID system is used to avoid the problem of different hardware and distros UDEV assigning different /dev names to the same partition. Generally speaking hdX is assigned to IDE drives and sdX to sata/serial drives. More critical is as you add/remove drives the drive letter changes,with USB as drives/devices are removed/inserted the numbers increase. The Universal Unique IDentification given to the partition is identified on all modern hardware by all modern distros. UUID never changes until you repartition the drive.
Offline
@mojo: mmm, it installs grub as a boot manager, but your suggestions should be pertinent.
I'll try some more times passing the home=UUID and see what happens. Thanks for now.
Offline
Slitaz Install Tools
Frugal install:
tazusb on both Slitaz 3 and 4 installs extlinux bootloader, not grub.
Full install:
slitaz-installer on slitaz-3.0 use's grub
tazinst on Slitaz-4.0-RC use's grub
Offline
well, I'm doing full install now, and I see grub, since (sadly) frugal didn't work 
Offline
well, I can't seem to get this working.
if I do a frugal install on usb, ext3 formatted, then boot that, I can install packages, and they are remembered on reboot, but others setting are not, like network configuration. maybe it's because it's in the compressed fs, or it's a permission thing, but it won't have complete persistence (a shame, it boots so fast)
if I do a full usb install, using tazinst, then I have to change drive sdx based on the system I boot from. It does retain all settings, but it's a bit slower than live (not an issue). As soon as I try to pass the UUID, it complains about home= and goes kernel panic. I tried and tried again, rebooting and rebooting, but if it's not in the sdx format it doesn't boot.
at least I have it working on the hdd, so I know it's possible.
but what is preventing it to work on a usb key?
Offline
Frugal only,not for full install: home=
Follow the directions in my first reply on this thread,a frugal install to the USB key will work.
Offline
"Grub2 doesn't like slitaz?"
lol
That sucks. A kernel panic means the kernel loaded, but the kernel then freaked out, usually means the kernel can't access rootfs.
With a manual install, the most likely cause is forgetting to specify the path to the initrd.
Offline
yes, the kernel loads and recognizes my HW. and initrd should be taken care by tazinst, right?
still, grub2 loads it fine from my hdd, so it can be the grub2 version slitaz uses, but I think it's not really probable.
Offline
Pages: 1
[ Generated in 0.015 seconds, 8 queries executed - Memory usage: 1.56 MiB (Peak: 1.77 MiB) ]