[EMAIL PROTECTED] wrote:
> kernel panic at boot time
>
> > What kernel do you use?
>
> original Seawolf (2.4.2-??)
Try getting a good kernel?
I only use Red Hat kernels for installs :)
> > Do you boot IDE or SCSI?
>
> System:
> 1) On-board IDE (no connections)
> 2) MegaRAID 1200 (external array under construction; no connections at this time)
> 3) BusLogic 958
> * 4.3G U+W drives = /dev/sda, /dev/sdb, /dev/sdc
> * PD/CD = /dev/sdd, /dev/cdrom
> * CD-RW = /dev/sg0, /dev/cdrom1
> * ADR tape = /dev/nst0
> * DAT tape = /dev/nst1
> 4) Promise-100
> * 60G UDMA100 Maxtor = /dev/hde
>
> I want to boot from /dev/hde, and but IDE/SCSI mix confuses things. If I
> understood LILO's ability to explicitly reorder the BIOS disk discovery order,
> I'd probably be able to get it to work the way I want it. But I don't.
Some BIOSes can have the builtin IDE turned off, so that the Promise
card would be hda/b/c/d instead. It might help.
BIOSes also have an option to boot addin cards before the builtin
devices,
which might change the drive ordering?
Any particular reason not to boot from a SCSI disk?
I had a SCSI root, and an IDE /boot, because the SCSI controler
wasn't bootable. Perhaps you coulkd have a SCSI boot and
a IDE root (If that's what you want)
> > What's the problem with mkbootdisk?
>
> Apparently doesn't copy correct ramdisk, kernel, or whatever onto the boot disk.
> Result is boot-time kernel panic. Can't tell you details at this time (I'm at
> work). Also, the mkbootdisk text equiv doesn't support vga= settings, so I can't
> specify VESA framebuffer modes.
mkbootdisk is a script. It uses syslinux, so you can edit the script
or the bootdisk (a VFAT formatted floppy) an ad the vga option to
syslinux.cfg.
> > Do you need an initial ram disk?
>
> Yes. I make them using same command line params I've always used to build ram
> disks for SCSI. Dasy to do. Filesizes of mine are consistent with working
> version initrds.
> Haven't checked that, but also haven't seen mkbootdisk fail to copy them
> correctly in the past.
mkbootdisk calls mkinitrd. It has an option to pass parameters to
mkinitrd. That might help. Best bet is to check the initrd.
Also, have you tried booting without the bootdisk?
If you have /boot on a disk BIOS can see, you should beable to
but lilo on it and it will load the initrd using BIOS and not need
a floppy. If you have this working, then mkbootdisk is the problem, and
I'd file a bug, then write my own script to do it, or fix theirs.
It's a pretty simple bash script.
> Present "Red Hat Way" is to modularize everything. Ergo, mkinitrd even for IDE.
I thought they dropped the modular IDE stuff. The beta I tried with that
wouldn't handle IDE RAID (using md.o) because RAID was started before
IDE was loaded, so md.o saw no partitions.
Again, I don't do the "Red Hat way" :)
> I've been unable to locate a grub source not filled with dire warnings. Is it
> ready for prime time?
Never used it personally, but a friend has it on his Mandrake system.
No problems yet.
-Thomas
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
