On 5/29/07, Alan Womack <[EMAIL PROTECTED]> wrote: > The default for gmail!
I use gmail everyday, and i allways scroll down first :) > > On 5/28/07, Ken Moffat <[EMAIL PROTECTED]> wrote: > > A: Because it messes up the order in which people normally read > > text. > > Q: Why is top-posting such a bad thing? > > <> > > > > > > I have not tried having TWO ide's in there yet. > > > > > I put a second hard drive in there AND changed the device order to > controllers without ID, THAT seems to be a ticket someplace. > > > So, what is this 'intel boot manager' ? Does it run before grub or > > after ? It is something you used when you only had the IDE drive ? > > PXE or something like that, seems to used for the ability to boot a > system from over a network, but there is no direct option for it. That isn't a boot manager :) It's just for Intel network cards.. I have a Intel Gbit card too, and it has the same prog. It allows you to boot a PXE over LAN. Nothing to do with this problem.. > > > > > I've seen cable problems (although I've never seen anything that > > complained) - for IDE it doesn't always work if you have only a > > slave, and perhaps with CS and the drive connected at the slave > > position it might fail. With SCSI, termination is important. > > > > I was working on just getting the single drive as a master. I did try > it also in the save position, but the bios then complained about there > being no primary hard drive. You can set that error to ignore, but it doesn't help solve the problem, as it won't change the order they are listed in grub. That could only be changed by editing the devices.map file. (grub install required) > <> > > Alan On 5/29/07, Alan Womack <[EMAIL PROTECTED]> wrote: > > It seems I can control the drive controllers and am now making some > > progress. I can get GRUB to continue on, but I hit a kernel panic > > that halts me later. > > any way to store the dmesg on a system that isn't booting properly? I tried that too, but these are only stored when the system has access to the hard drive, and once you reboot, all the log info stored in the RAM is cleared and so it is gone. However, you can setup a serial (COM) link to another PC, and with some boot option, you could send all log info to another PC with that serial cable. > > I get to > VFS: cannot open root device "sda1" or unknown-block(0,0) > please append correct "root=" boot option > Kernel panic - not syncing: VFS: Unable to mount root DS on unknown-block(0,0) The error itself is simple, you haven't set the root= option correct, it points to a non-existing hard drive. > > Since the boot messages go by so fast, and I cannot get pause, or > scroll lock to stop the screen I cannot see what happens earlier in > the boot. > > Alan This is a common problem, I don't think it's possible to pause or such, but you could try to append vga=6 to your boot line, this will change the font size, so that when the error occurs, you can read a bigger part of the log, and probably also the piece where your hard drive drives are loaded, and the kernel finds your drives, and shows you which name it has atm. I used this way to find out how my USB drives were called in my new kernel. Tijnema -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
