SliTaz Forum

m00dyson

Member

Registered: 2012-04-21

Posts: 14

How to boot Slitaz4 with Radeon HD4000 series

I had successfully boot Slitaz3 on my PC with HD4650, but someone mentioned me that if i want support i should use the latest version of Slitaz. (I already tried it in VBox, but mouse didnt work) So i give it a try and boot LiveCD and it paas fine local & kbd setup but after it initializes GPU drivers all i can see is blinking dash in uper corner or if i use muse and click i see thin tiled line on back background (Ctrl+Alt+Del successfully reboots PC)

Is there a vga=SWITCH i should use and how to boot Slitaz4 thru syslinux on mbcd/usb (so i can boot extracted iso instead SlitazONLY iso) because it contains rootfs1..4.gz instead of previously only one rootfs.gz (how to append all four rootfs parts?)

Ceel

Administrator

Registered: 2011-04-02

Posts: 1,424

Re: How to boot Slitaz4 with Radeon HD4000 series

Hi m00dyson,

Use slitaz-4.0-core.iso (http://mirror.slitaz.org/iso/4.0/flavors/)

On this iso there is only one rootfs.gz

mojo

Administrator

Registered: 2011-03-29

Posts: 2,174

Re: How to boot Slitaz4 with Radeon HD4000 series

Try adding [c]lang=en_US kmap=us nomodeset[/c] to kernel options

You don't have to download another iso.

How to append all four rootfs parts to a single rootfs.gz?

Copy all rootfs*.gz to $PWD

Run the command:

[c]cat $(ls -r rootfs*.gz) > rootfs.gz[/c]

m00dyson

Member

Registered: 2012-04-21

Posts: 14

Re: How to boot Slitaz4 with Radeon HD4000 series

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 [c]code[/c]isolinux.cfg[c]/code[/c] 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

[c]append initrd=/boot/rootfs4.gz,/boot/rootfs3.gz,/boot/rootfs2.gz,/boot/rootfs1.gz[/c]

SliTaz gtkOnly Live

[c]append initrd=/boot/rootfs4.gz,/boot/rootfs3.gz,/boot/rootfs2.gz[/c]

SliTaz justX Live

[c]append initrd=/boot/rootfs4.gz,/boot/rootfs3.gz[/c]

SliTaz base Live

[c]append initrd=/boot/rootfs4.gz[/c]

and every flavor above base use one more [c]rootfsX.gz[/c] so that's why they're separately packed.

Thanks mojo for that [c]cat $(ls -r rootfs*.gz) > rootfs.gz[/c] "trick", which come quite handy. I now know (until i forget again ) that variable values in .cfg files coud be separated by comma [c]initrd=$val1,$val2,...,$valn[/c]. And i guess that they must be in proper order to boot?

I used to boot up slitaz base with [c]rootfs4.gz[/c] but obviously i didnt boot anything with other rootfs.gz in my blank boot attempts.

I still didnt try [c]nomodeset[/c] 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 [c]syslinux -sd /boot/dir /dev/sdcX[/c]. But now i'm guessing this syslinux that's boot up with ST3.0-core is weirdo cause it doesnt support [c]syslinux --version[/c] and i dont know how to use syslinux.bin (non-installed) that comes on LiveCD as isolinux.bin. I tried to run it as [c]./syslinux.bin[/c] 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 [c]syslinux[/c] in Slitaz3.0-core boot. Because after running [c]syslinux.exe --mbr --active --directory "X:\boot\syslinux" --install X:[/c] with all files unchanged, same usb stick boots up flawlessly.

Trying to boot with [c]nomodeset[/c] returns an [c]error setting MTRR (base=0x00000000,size=0x01000000,type=1) Invalid Argument (22)[/c] 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