On Monday 02 April 2001 22:04, Matthias Badaire wrote:
> Peter Ruskin <[EMAIL PROTECTED]> writes:
> > On Saturday 31 March 2001 17:30, Chmouel Boudjnah wrote:
> > > Peter Ruskin <[EMAIL PROTECTED]> writes:
> > > > On Saturday 31 March 2001 16:06, Chmouel Boudjnah wrote:
> > > > > Peter Ruskin <[EMAIL PROTECTED]> writes:
> > > > > > 1)  kernel-2.4.2-i586.config (2.4.2-18mdk) :
> > > > > > CONFIG_BLK_DEV_OFFBOARD=y 2)  kernel-2.2.18-i586-up.config : 
> > > > > > # CONFIG_BLK_DEV_OFFBOARD is not set
> > > > >
> > > > > i have forwarded to our kernel22 maintainners.
>
> it is me 8)
>
> > > > Please tell me whether CONFIG_BLK_DEV_OFFBOARD is going to be set
> > > > or unset by default, so I can decide what to do with my fstab and
> > > > lilo.conf.
> > >
> > > to be set.
>
> It is now in the kernel22-2.2.19-3mdk
>
> > > > I would prefer it to revert to unset, like it used to be - I'm
> > > > running Cooker, 7.2, OpenLinux and win98 on the same box.
>
> Normally you just have to change your fstab, isn't it ?

Did that already.

>
> > As I still can't get into cooker, I rebuilt my kernels in 7.2 with
> > CONFIG_BLK_DEV_OFFBOARD set, ran lilo and rebooted.
> >
> > Result: kernel panic - can't find root partition.  I now have to
> > append "ide0=0xd400,0xd802 ide1=0xdc00,0xe002 " to lilo [kernels used
> > are 2.4.2-18mdk ( rebuilt for 7.2 ) and 2.2.17-27mdk].
>
> Obviously but as I said before, changing your fstab should avoid this
> problem .

But it doesn't - that's my point.  I don't understand it.  fstab lists all 
partitions as /dev/hd{a,b,c,d}* and sda* but when lilo wants to boot from 
/dev/hda3 it panics because it can't find it - until I append 
"ide0=0xd400,0xd802 ide1=0xdc00,0xe002 ".

>
> > This is a nuisance.  Surely it would be better to unset this config
> > flag.

-- 
              ----------------------------------------------------
                 Linux Mandrake release 7.2 (Odyssey) for i586
                                    KDE 2.1
              Linux 2.2.17-27mdkWin4Lin, Uptime 5 hours 45 minutes
              ----------------------------------------------------

Reply via email to