Running the slitaz-4.0.iso live from USB Stick using Gub4dos or Grub2

SliTaz Forum » English Support » Live and installation

Running the slitaz-4.0.iso live from USB Stick using Gub4dos or Grub2

(12 posts) (4 voices)

Started 10 years ago by lindylex
Latest reply from lindylex
This topic is not a support question

Tags:

No tags yet.

lindylex

offline
Member

I can not seem to get slitaz-4.0.iso live to run from the usb stick.

Below are all the combinations I have tried. None of these work.

Using Grub 2 failed with a variety of errors I detailed using Grub4dos. I am not committed to Grub 2 or or Grub4dos. I would like a solution.

[ GRUB 2 ]

menuentry "SliTaz, ISO 4.0" {
set isofile="/boot/iso/slitaz-4.0.iso"
loopback iso $isofile
linux (iso)/boot/bzImage from=$isofile ramdisk_size=6666 home=usb root=/dev/ram0 rw autoexec=startx changes=s512.dat
initrd (iso)/boot/rootfs1.gz
}

menuentry "slitaz test" {
loopback loop (hd0,1)/boot/iso/slitaz-4.0.iso
linux (loop)/boot/bzImage isofrom=/dev/disk/by-uuid/1662-5E2F/boot/iso/slitaz-4.0.iso boot=live quiet noeject noprompt
initrd (loop)/boot/rootfs1.gz
}

menuentry "slitaz 4.0 PLEASE WORK" {
set isofile="/boot/iso/slitaz-4.0.iso"
loopback loop $isofile
linux (loop)/boot/bzImage rw root=/dev/null lang=C kmap=us screen=1024x768x16 autologin
initrd (loop)/boot/rootfs4.gz
}

menuentry "slitaz test 2" {
loopback loop /boot/iso/slitaz-4.0.iso
gfxpayload=800x600
linux (loop)/boot/bzImage isofrom=/dev/disk/by-uuid/1662-5E2F/boot/iso/slitaz-4.0.iso boot=live quiet noeject noprompt
initrd (loop)/boot/rootfs4.gz,/boot/rootfs3.gz,/boot/rootfs2.gz,/boot/rootfs1.gz
}

menuentry "SliTaz, frugal, 1" {
linux /boot/slitaz/boot/bzImage rw root=/dev/null vga=normal autologin
initrd /boot/slitaz/rootfs4.gz,/boot/slitaz/rootfs3.gz,/boot/slitaz/rootfs2.gz,/boot/slitaz/rootfs1.gz
}

menuentry "SliTaz, frugal, 2" {
gfxpayload=800x600
linux /boot/slitaz/boot/bzImage rw root=$root autologin
initrd /boot/slitaz/boot/rootfs4.gz,/boot/slitaz/boot/rootfs3.gz,/boot/slitaz/boot/rootfs2.gz,/boot/slitaz/boot/rootfs1.gz
}

menuentry "SliTaz, frugal, 3" {
gfxpayload=800x600
linux /boot/slitaz/boot/bzImage rw root="/boot/slitaz/" autologin
initrd /boot/slitaz/boot/rootfs4.gz,/boot/slitaz/boot/rootfs3.gz,/boot/slitaz/boot/rootfs2.gz,/boot/slitaz/boot/rootfs1.gz
}

menuentry "SliTaz, frugal, 3" {
gfxpayload=800x600
linux /boot/slitaz/boot/bzImage rw root="/dev/sda1" autologin
initrd /boot/slitaz/boot/rootfs4.gz,/boot/slitaz/boot/rootfs3.gz,/boot/slitaz/boot/rootfs2.gz,/boot/slitaz/boot/rootfs1.gz
}

menuentry 'slitaz-3.0-3in1.iso slitaz3 (u/p:tux,u/p:root)' {
insmod ext2
set root='(hd0,1)'
echo 'Loading /boot/iso/slitaz-4.0.iso ...'
loopback loop (hd0,1)/boot/iso/slitaz-4.0.iso
linux (loop)/boot/slitaz/bzImage iso_filename=/boot/iso/slitaz-4.0.iso ramdisk_size=100000 rw root=/dev/null vga=normal autologin
echo 'Loading initial ramdisk ...'
initrd (loop)/boot/slitaz/rootfs3.gz
}

[ GRUB4DOS ]

title SliTaz GNU/Linux
root (hd0,1)
kernel /boot/slitaz/boot/vmlinuz-2.6.37-slitaz root=/dev/sda1
initrd /boot/slitaz/boot/rootfs4.gz

"SliTaz GNU/Linux" Error: No such partition

title Slitaz rootfs1
kernel /boot/slitaz/boot/vmlinuz-2.6.37-slitaz root=/dev/ram0 vga=791
initrd /boot/slitaz/boot/rootfs1.gz

"Slitaz rootfs1" Error: NO filesystem could mount root tries...
Kernel panic - not syncing: VFS:.....

title Boot SliTaz 2.0 LiveCD
find --set-root --ignore-floppies --ignore-cd /boot/iso/slitaz-4.0.iso
map --mem /boot/iso/slitaz-4.0.iso (0xff)
map --hook
chainloader (0xff)

"Boot SliTaz 2.0 LiveCD" Error: Blank Screen

title Slitaz 4 RC Live I
find --set-root /boot/iso/slitaz-4.0.iso
map --heads=0 --sectors-per-track=0 /boot/iso/slitaz-4.0.iso (0xff)
map --hook
root (0xff)
chainloader /boot/slitaz/boot/isolinux/isolinux.bin

"Slitaz 4 RC Live I" Error: File not found "isolinux.bin"

title Slitaz 4 RC Live II
find --set-root /boot/iso/slitaz-4.0.iso
map --heads=0 --sectors-per-track=0 /slitaz-4.0.iso (0xff)
map --hook
root (0xff)
chainloader /boot/slitaz/boot/isolinux/isolinux.bin

"Slitaz 4 RC Live II" Error: File not found...

title slitaz-4.0-RC1.iso
map /boot/iso/slitaz-4.0.iso (hd32) | map --mem /boot/iso/slitaz-4.0.iso (hd32)
map --hook
chainloader (hd32)

"slitaz-4.0-RC1.iso"' Error: File not found....

title Boot slitaz-4.0.iso I
map --mem --heads=0 --sectors-per-track=0 (pd)/boot/iso/slitaz-4.0.iso (0xff)
map --hook
chainloader (0xff)
boot

title Boot slitaz-4.0.iso II
map --mem --heads=0 --sectors-per-track=0 /boot/iso/slitaz-4.0.iso (0xff)
map --hook
chainloader (0xff)
boot

"Boot slitaz-4.0.iso II" Error: Request events from the kernel...

title Slitaz 4.0 III
map /boot/iso/slitaz-4.0.iso (0xff) || map --mem /boot/iso/slitaz-4.0.iso (0xff)
map --hook root (0xff)
chainloader (0xff)

"Slitaz 4.0 III" I can not start GUI with "startx"

title SliTaz Linux 4.0 IV
find --set-root /boot/iso/slitaz-4.0.iso
map --heads=0 --sectors-per-track=0 /boot/iso/slitaz-4.0.iso (0xff)
map --hook
root (0xff)
chainloader

title slitaz-4.0.iso XXX
map --heads=0 --sectors-per-track=0 /boot/iso/slitaz-4.0.iso (0xFF)
map --hook
map --status
kernel (0xFF)/boot/bzImage rw root=/dev/null vga=normal
initrd (0xFF)/boot/rootfs1.gz
boot

"slitaz-4.0.iso XXX" Error: Kernel panic not syncing :VFS:

Posted 10 years ago #

tazpider

offline

Member

Working entry of Grub2 I use looks as follows:

menuentry 'Slitaz 4.0 Live' {
        linux (hd1,4)/slitaz/bzImage
        initrd (hd1,4)/slitaz/rootfs.gz
}

For some other isos I have:

menuentry "Mint 16 LiveCD C" {
        set isofile="/iso/linuxmint-16-cinnamon-dvd-32bit.iso"
        loopback loop (hd1,3)/$isofile
        linux (loop)/casper/vmlinuz boot=casper iso-scan/filename=$isofile toram
        initrd (loop)/casper/initrd.lz
}

Maybe that helps you creating yours in correct way.

Posted 10 years ago #

lindylex

offline
Member

Tazpider: Slitaz 4.0 does not have a rootfs.gz file. It has four and they are numbered like the following.

rootfs1.gz, rootfs2.gz, rootfs3.gz, rootfs4.gz

Posted 10 years ago #
Bellard

offline
Key Master

You can create rootfs.gz :
$ cat rootfs4.gz rootfs3.gz rootfs2.gz rootfs1.gz > rootfs.gz

Posted 10 years ago #

Ceel

offline

Administrator

@lindylex

GRUB2: initrd line should be something like

   initrd /boot/slitaz/boot/rootfs4.gz /boot/slitaz/boot/rootfs3.gz /boot/slitaz/boot/rootfs2.gz /boot/slitaz/boot/rootfs1.gz
   don't use [,] but [space]

GRUB4DOS:

   root (hd0,1)
   kernel /boot/slitaz/boot/vmlinuz-2.6.37-slitaz root=/dev/sda1

I think if root=/dev/sda1 then root should be (hd0,0).

Posted 10 years ago #

lindylex

offline
Member

Bellard, what is the advantage or purpose of doing that concatenation?

Posted 10 years ago #
lindylex

offline
Member

The following will get Slitaz 4.0 to ask me for my keyboard layout preference, and country local. Then it drops me to command-line. I type user name "tux" then I type "startx" and get the following error.

ERROR: server is already active for display 0....

menuentry 'Slitaz 4.0 Live tazpider suggestion II' {
linux /boot/slitaz/boot/bzImage
initrd /boot/slitaz/boot/rootfs.gz
}

title SliTaz GNU/Linux II
root (hd0,0)
kernel /boot/slitaz/boot/bzImage root=/dev/sda1
initrd /boot/slitaz/boot/rootfs.gz

title Slitaz rootfs
kernel /boot/slitaz/boot/vmlinuz-2.6.37-slitaz root=/dev/ram0 vga=791
initrd /boot/slitaz/boot/rootfs.gz

This give me a different error after typing "startx": Can't open /home/tux.config/slitaz/applications.conf

I think it has to do with loading this file first rootfs4.gz. I believe each rootfsX.gz loads something different from what I read.

menuentry "slitaz test 2" {
loopback loop /boot/iso/slitaz-4.0.iso
gfxpayload=800x600
linux (loop)/boot/bzImage isofrom=/dev/disk/by-uuid/1662-5E2F/boot/iso/slitaz-4.0.iso boot=live quiet noeject noprompt
initrd (loop)/boot/rootfs4.gz /boot/rootfs3.gz /boot/rootfs2.gz /boot/rootfs1.gz
}

Posted 10 years ago #
Bellard

offline
Key Master

@lindylex: not sure that every grub2 supports multiple initrd.
> I think it has to do with loading this file first rootfs4.gz
right.

Posted 10 years ago #
lindylex

offline
Member

"I think it has to do with loading this file first rootfs4.gz right. " yes.

It looks like this might be a problem with my video card. http://doc.slitaz.org/en:guides:xorg-xvesa

To bad they never made a version 4.0 of the following slitaz-3.0-xvesa.iso .

Posted 10 years ago #
Ceel

offline
Administrator
@lindylex

Then it drops me to command-line. I type user name "tux" then I type "startx" and get the following error

What about login as root and then typing slim?

This give me a different error after typing "startx": Can't open /home/tux.config/slitaz/applications.conf

try login as tux, then
```
  mkdir /home/tux/.config/slitaz/
  cp /etc/slitaz/applications.conf /home/tux/.config/slitaz/
  su
  slim
```
Posted 10 years ago #
lindylex

offline
Member

[ PARTIAL SOLUTION ]

Both of the following work.

menuentry "slitaz slitaz-3.0-xvesa" {
loopback loop /boot/iso/slitaz-3.0-xvesa.iso
gfxpayload=800x600
linux (loop)/boot/bzImage isofrom=/dev/disk/by-uuid/1662-5E2F/boot/iso/slitaz-4.0.iso boot=live quiet noeject noprompt
initrd (loop)/boot/rootfs.gz
}

menuentry "slitaz slitaz-3.0-xvesa II" {
loopback loop /boot/iso/slitaz-3.0-xvesa.iso
gfxpayload=800x600
linux (loop)/boot/vmlinuz-2.6.30.6-slitaz isofrom=/dev/disk/by-uuid/1662-5E2F/boot/iso/slitaz-4.0.iso boot=live quiet noeject noprompt
initrd (loop)/boot/rootfs.gz
}

Get the iso for the older version 3.0 of Slitaz

http://mirror.slitaz.org/iso/3.0/flavors/slitaz-3.0-xvesa.iso

I remain committed to solving this for version 4.

///////

I am almost there. I use the following to start the O.S. All the content from the iso have been extracted to the usb stick at "/boot/slitaz/"

For Grub2 Works

menuentry 'Slitaz 4.0 Live tazpider suggestion II' {
linux /boot/slitaz/boot/bzImage lang=en kmap=en
initrd /boot/slitaz/boot/rootfs.gz
}

For Grub4Dos Works

title Slitaz rootfs
kernel /boot/slitaz/boot/vmlinuz-2.6.37-slitaz root=/dev/ram0 vga=791 lang=en kmap=en
initrd /boot/slitaz/boot/rootfs.gz

I get to the commandline and login in using "tux" [enter]

su root [enter]
password: root [enter]

I have to find out what is my video card.

lspci [enter]

I have an Nvida video card so I use the nv drivers.

tazx [enter]

choose vesa it downloads vesa drivers.

I select nv. It sets that up.

This is where I am stuck. Xserver is running for the tux user and root. How do I stop it from running and start x using vesa drivers?

This does not stop the xserver "alt-ctrl-backspace". I tried it in the tux user and root user. Getting help from http://doc.slitaz.org/en:guides:xorg-xvesa and http://doc.slitaz.org/en:handbook:xwindow

Posted 10 years ago #
lindylex

offline
Member

I am a little closer. I think this might have to do with the permissions.

I use the following in Grub2 to boot Slitaz 4.0 and disable X server. This disable X server "screen=text". I had to do this because Ctrl+Alt+Backspace did not disable X server.

menuentry 'Slitaz 4.0 Live screen=text' {
linux /boot/slitaz/boot/bzImage screen=text
initrd /boot/slitaz/boot/rootfs.gz
}

I log in as root.

#root [ enter]
I am ask for the root password
# root [ enter ]

I need to have a wired internet connection for this to work.

# tazx [ enter ]

I install XVesa and install "nv" because I have an Nvidia video card.

# slim [ enter ]

I see a login manager with the tux user in the user name. I hit [ enter ] enter tux as the password and it quickly drop to terminal and opens the login manager again. I tried root user also.

This link helped me get this far. http://vanilla.slitaz.org/index.php?p=/discussion/2484/cant-run-xserver-on-slitaz-cooking-version/p1

Posted 10 years ago #

RSS feed for this topic

Reply

You must log in to post.