Thank you for your reply. I did notice that the
drivers were on the disk, but they are in a folder
within the net directory, and all the other drivers
are not in folders. I don't know if that makes a
difference, but I am not able to select the e1000 from
the list of drivers when I boot my computer.
Thank you again for your help, please let me know if
there is anything I can do.
--- Alain Knaff <alain(a)knaff.lu> wrote:
On Wednesday 21 May 2003 15:48, Ian Oliver wrote:
I've downloaded the new alpha release, and
to add the e1000.o module using the instructions
the web page.
I get to Step 5. And when I run the mount command
recieve this error message:
[root@ioliver udpcast]# mount -o loop -t minix
mount: wrong fs type, bad option, bad superblock
or too many mounted file systems
You need to be aware that the new boot loader
release is based on a
different program (busybox, rather than the SuSE
install disk as was
the case before) and it also uses a different
rather than minixfs). Thus, the instructions for the
old version no
longer apply. But they should not be needed either,
because e1000 is
already included in the default image.
If you need support for other cards, which might not
be included in
the new image, then use the instructions at
For instance, to make a floppy with the pcnet32 and
the acenic module,
use the following command line:
/boot/vmlinuz-2.4.21-rc2-udpcast -m "pcnet32 acenic"
However, by default, the following modules are
already included anyways:
3c59x 8139too 8390 dl2k dmfe e100 e1000 eepro100
hamachi hp100 natsemi ne2k-pci ns83820 pcnet32 r8169
tc35815 tg3 tlan tulip typhoon via-rhine winbond-840
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.