RE: Initrd problems

2003-12-09 Thread Lewis Shobbrook
Thanks Herbert that did the trick, should have guessed that from the example... > > # Examples: > > # > > # ext2 > > # wd io=0x300 > > FastTrak.o > > Try just "FastTrak". Cheers, Lewis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL P

Re: Initrd problems

2003-12-09 Thread Herbert Xu
On Wed, Dec 10, 2003 at 10:23:14AM +1100, Lewis Shobbrook wrote: > > # Examples: > # > # ext2 > # wd io=0x300 > FastTrak.o Try just "FastTrak". -- Debian GNU/Linux 3.0 is out! ( http://www.debian.org/ ) Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]> Home Page: http://gondor.apana.org.au/~herb

RE: Initrd problems

2003-12-09 Thread Lewis Shobbrook
ignored. # # You must run mkinitrd(8) to effect this change. # # Examples: # # ext2 # wd io=0x300 FastTrak.o > -Original Message- > From: Herbert Xu [mailto:[EMAIL PROTECTED] > Sent: Tuesday, 9 December 2003 06:08 > To: Lewis Shobbrook > Cc: [EMAIL PROTECTED]; [EMAIL PROTE

Re: Initrd problems

2003-12-09 Thread Herbert Xu
On Tue, Dec 09, 2003 at 11:04:22AM +1100, Lewis Shobbrook wrote: > > Basically the driver module is not loading and we can't mount the root > filesystem. The module FastTrak.o can't be found, but I've mounted the > rd image and can verify the inclusion. I've adjusted the modules file > within the

Re: initrd problems

2002-09-20 Thread Tim Olsen
I think I figured it out. mkinitrd only works with Debian kernel sources. (bug 149236) -Tim On Fri, Sep 20, 2002 at 11:44:07AM -0400, Tim Olsen wrote: > > I am having problems setting up an initial ramdisk for my kernel. I > get the following message during boot: > > RAMDISK: Couldn't fin