SliTaz Forum
You are not logged in.
Pages: 1
Grub menu.lst for flash drive permanent install:
# For booting SliTaz from : /dev/sdc1
#
title SliTaz GNU/Linux
root (hd0,0)
kernel /boot/vmlinuz-2.6.30.6-slitaz root=/dev/sda1
Hi,
sdc1 is a flash drive with a hard drive install on it.
When I boot and hit <esc> and select it for booting it
becomes hd0,0 for grub. I'm getting a kernel panic and
it says sda1 not supported for optional features...
What optional features ?
Will not let me use LABEL= for root either. This kernel
has me stumped. Fstab has no entry for "/" either
from install and that is a little worrisome as well,
especially when my notations appear to be rejected by the kernel.
Any ideas ?
THX.
Patrick
Offline
----------------
# For booting SliTaz from : /dev/sdc1
[...]
root (hd0,0)
kernel /boot/vmlinuz-2.6.30.6-slitaz root=/dev/sda1
----------------
Have you got an internal Hard Drive? If so, you are telling Slitaz to get the kernel from it and not from the external, I think.
A question: grub is installed in the main drive, or in the outer drive?
If it is outside, you should try using another boot loader, anyway. For external devices, syslinux is a good option, even for multi-boot external systems.
------------------
Fstab has no entry for "/" either
from install and that is a little worrisome as well,
------------------
Then, you may add an entry for it in /etc/fstab. I know no distribution that can work without having a "/" directory!
Offline
When I boot I hit escape at the startscreen and I can select any internal or
external drive and directly boot from it. It has always become hd0,0 for
grub and /dev/sda1 for fstab.
Grub is installed both on the internal drive and the flash drive for direct booting
bypassing the internal drive completely, at least that's the theory that
worked previously. Never used syslinux.
I wonder if ext3 is a problem...it says cannot mount sda due to unsupported features,
then it says file system cannot mount root. This old kernel just doesn't want to
install on a flash drive today. Any other ideas ????
THX.
Patrick
Offline
-------------------------
I wonder if ext3 is a problem
-------------------------
ext3 is no problem, sure.
Are you using GRUB-legacy, or GRUB2?
If you are using the first, you can edit your internal boot loader to look like this:
### If you have made a Hard Drive install
title SliTaz GNU/Linux
root (hd1,0)
kernel /boot/vmlinuz-2.6.30.6-slitaz root=/dev/sdb1
### If you have installed Slitaz in its compressed form-- frugal install
title Slitaz GNU/LInux
root (hd1,0)
kernel /boot/bzimage root=/dev/null
initrd /boot/rootfs.gz
Don't forget to append any cheatcode you need to the "kernel" line.
Offline
Well I think this is going down in the books as a hardware problem.
When it does boot it gets a kernel panic before mounting the filesystem.
hd0,0 or hd1,0 with fstab filled in as well.
This is an EeePC 900 which I saw a post about but need to spend some time
looking for and reading it.
thanks for your response.
Offline
As a last resort, you can turn to syslinux. Install it in the external hard drive and use that drive as you would do with any live distribution.
The chumsy (and easy) way to have syslinux installed with all its stuff is to execute syslinux against the drive and then copy the /boot folder of Slitaz iso over the /boot folder of the hard drive. Finally, you go and configure the bootloader by searching for the syslinux.cfg/isolinux.cfg file and editing its entries to match something like
-------------
display isolinux.msg
label slitaz
kernel /boot/bzImage
append initrd=/boot/initrd.gz rw root=/dev/sda1 vga=normal autologin # Not sure!!!
include common.cfg
-------------
Reading syslinux documentation and some hard working might be required.
Offline
----------------------------------------------------------------------
Reading syslinux documentation and some hard working might be required
----------------------------------------------------------------------
Well when I have time for that I will. Here is a question.
A eeepc flavor was available. I wonder what flavor presently
matches that. Should be pretty compatible then. I like this
"flavors" idea. Should start another thread about that.
Offline
I am encountering the same problem and I agree with Black Rider with "Slitaz getting kernel from the hard drive instead of the flash drive"
So my question is, is there a way to mount a flash drive with out the computer booted up completely
I am going to try this and let you know:
root (hd1,0)
mount UUID=c2ba4de9-2623-405f-9ae4-c42c9d50158f / ext2 none 0 0
kernel /boot/vmlinuz-2.6.30.6-slitaz root=/dev/sdb1
Not sure it's going to work but would love to try.
Well, as you guys probably already know, the last trick didn't work. So my solution to my problem is to just use live usb and save the fs file (rootfs.gz) every time I make changes on exit. After configuring all hardware and installing all the programs I need, rootfs.gz file is about 82mb and for me it didn't really affect boot time.
In fact, I think it is a better way of doing it coz I will be able to use it on any system, anywhere I go and not specifically tailored to one pc only.
@Patrick, did you try something like that ?
# For booting SliTaz from flash drive
#
title SliTaz GNU/Linux
kernel /boot/vmlinuz-2.6.30.6-slitaz root=UUID=c2ba4de9-2623-405f-9ae4-c42c9d50158f
Offline
Yes and that gave me the same result. Here is the strange thing.
root=(hd1,0) gives me "fs is ext2fs" and "something x83". This tells me that the pc is recognizing my flash drive. (hd0= hard drive;hd1=flash drive)
But: kernel /boot/vmlinuz-2.6.30.6-slitaz root=/deb/sdb1 still gave me "file not found!"
Oops. that question was for Patrick. Sorry. But yeah I've tried that.
Pages: 1
[ Generated in 0.018 seconds, 7 queries executed - Memory usage: 1.55 MiB (Peak: 1.77 MiB) ]