Gordon ``48, 1'' is 0x3001, not 0x4801.
Of course, you are right ! I'll try that next week and let you know...
Gordon Maybe try that, but I can't say that I know what your problem
Gordon is.
My problem is that I've done too much hex lately and I have a tendancy
to interpret everything I see
- Forwarded message from Laurent Bonnaud [EMAIL PROTECTED] -
- I also tried passing the root= option as an hex value. I used:
title Debian GNU/Linux, kernel 2.4.12-686
root(hd0,0)
kernel /boot/vmlinuz-2.4.12-686 root=0x4801 ro
initrd
sorry here is a link to the original mail and followups:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=111315repeatmerged=yes
On Wed, Nov 14, 2001 at 09:01:57PM -0600, Gordon Matzigkeit wrote:
Maybe try that, but I can't say that I know what your problem is.
msg04606/pgp0.pgp
Jason == Jason Thomas [EMAIL PROTECTED] writes:
Jason sorry here is a link to the original mail and followups:
Jason http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=111315repeatmerged=yes
Well, as he said and as I've seen, it works with 2.2 but not with some
or all 2.4. Does grub do
Jason == Jason Thomas [EMAIL PROTECTED] writes:
Jason Adrian, are you able to test this, and maybe debug!
Jason Thanks.
Just back from hols.
snip
Here is what I have in /boot/grub/menu.lst:
title Debian GNU/Linux, kernel 2.4.9-686 root (hd0,0) kernel
Adrian, are you able to test this, and maybe debug!
Thanks.
- Forwarded message from Laurent Bonnaud [EMAIL PROTECTED] -
Date: Wed, 05 Sep 2001 15:13:07 +0200
From: Laurent Bonnaud [EMAIL PROTECTED]
To: Debian Bug Tracking System [EMAIL PROTECTED]
Subject: Bug#111315: grub: problem
I think I may have some helpful information regarding this.
On Thu, Sep 06, 2001 at 08:25:16AM +1000, Jason Thomas wrote:
| - Forwarded message from Laurent Bonnaud [EMAIL PROTECTED] -
...
[ kernel 2.4.x ]
...
| - partitions are detected correctly (including the root partition)
| -
On Wed, Sep 05, 2001 at 08:10:56PM -0400, dman wrote:
| kernel /boot/vmlinuz-2.4.9-686 root=/dev/rd/c0d0p1 ro
no its a DAC960 raid controller.
your problem could be because your fstab was wrong? or you didn't have
devfs mounted, which can be setup to do so automatically when you