Hi Ceel,
Yes i'm quite n00b with linux flavors. But it should be nice if for people like us (nyubz) there is section in slitaz tedious handbook "Messing up with flavors" or so.
Unluckily i'm messing with syslinux multiboot so i had to peek inside code
isolinux.cfg/code
and there wasan answer for my question
All flavours are on this SliTaz4.0.iso i have, just as Mojo said. they're just separately packed as
SliTaz core Live
append initrd=/boot/rootfs4.gz,/boot/rootfs3.gz,/boot/rootfs2.gz,/boot/rootfs1.gz
SliTaz gtkOnly Live
append initrd=/boot/rootfs4.gz,/boot/rootfs3.gz,/boot/rootfs2.gz
SliTaz justX Live
append initrd=/boot/rootfs4.gz,/boot/rootfs3.gz
SliTaz base Live
append initrd=/boot/rootfs4.gz
and every flavor above base use one more rootfsX.gz
so that's why they're separately packed.
Thanks mojo for that cat $(ls -r rootfs*.gz) > rootfs.gz
"trick", which come quite handy. I now know (until i forget again ) that variable values in .cfg files coud be separated by comma initrd=$val1,$val2,...,$valn
. And i guess that they must be in proper order to boot?
I used to boot up slitaz base with rootfs4.gz
but obviously i didnt boot anything with other rootfs.gz in my blank boot attempts.
I still didnt try nomodeset
because i only have Slitaz3.0 Live boot and syslinux doesnt make USB bootable in my case. I tried USB boot as sdc5(logical) and sdc1(primary) partition with syslinux -sd /boot/dir /dev/sdcX
. But now i'm guessing this syslinux that's boot up with ST3.0-core is weirdo cause it doesnt support syslinux --version
and i dont know how to use syslinux.bin (non-installed) that comes on LiveCD as isolinux.bin. I tried to run it as ./syslinux.bin
from xterm and only get a mess.
I guess i should use syslinux.exe on Win that work in a past iirc
Yup, something is definitely wrong with syslinux
in Slitaz3.0-core boot. Because after running syslinux.exe --mbr --active --directory "X:\boot\syslinux" --install X:
with all files unchanged, same usb stick boots up flawlessly.
Trying to boot with nomodeset
returns an error setting MTRR (base=0x00000000,size=0x01000000,type=1) Invalid Argument (22)
and now im kicked out to terminal (w/o need to Ctrl + Alt + F2)
My wild guess this looks like Slitaz4.0 have some issue with 16GB memory and not HD4650 card. Isnt there support for AMD64 and machines with more than 4GB memory?
Even "screensaver" works in terminal box ... leaving me with just Welcome to your box after ~10min :D