Andrew Benton schrieb:

>> Ricky Blankenaufulland wrote:
>>
>
>>>> Because the network card is not support by the kernel itself I
>>>> downloaded the driver at Intel's. Compiling into the Kernel ist not
>>>> possible you have to compile a module.
>
>>
>>
>> Are you sure you can't compile it into the kernel? What does lspci say?



The Readme of e1000 (version 6.0.60) says:

This file describes the Linux* Base Driver for the Intel(R) PRO/1000 Family
of Adapters, version 6.0.x. This driver supports the 2.4.x and 2.6.x
kernels.
[...]
This driver is only supported as a loadable module at this time. Intel
is not
supplying patches against the kernel source to allow for static linking of
the driver.


But if you an idea how I could compile it in I would be thankful. But I
do not think this is the problem as insmod works well.

lspci ist not present on my system (should it), but cat /proc/pci says:

PCI devices found:
  Bus  0, device   0, function  0:
    Host bridge: Advanced Micro Devices [AMD] AMD-751 [Irongate] System
Controller (rev 35).
      Master Capable.  Latency=64.
      Prefetchable 32 bit memory at 0xe8000000 [0xebffffff].
      Prefetchable 32 bit memory at 0xedbff000 [0xedbfffff].
      I/O at 0xdc00 [0xdc03].
  Bus  0, device   1, function  0:
    PCI bridge: Advanced Micro Devices [AMD] AMD-751 [Irongate] AGP
Bridge (rev 1).
      Master Capable.  Latency=64.  Min Gnt=6.
  Bus  0, device   4, function  0:
    ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South]
(rev 20).
  Bus  0, device   4, function  1:
    IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 6).
      Master Capable.  Latency=32.
      I/O at 0xffa0 [0xffaf].
  Bus  0, device   4, function  3:
    USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (#2) (rev 6).
      IRQ 10.
      Master Capable.  Latency=64.
      I/O at 0xd800 [0xd81f].
  Bus  0, device   4, function  2:
    USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 6).
      IRQ 10.
      Master Capable.  Latency=64.
      I/O at 0xd400 [0xd41f].
  Bus  0, device   4, function  4:
    SMBus: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 16).
  Bus  0, device  13, function  0:
    VGA compatible controller: nVidia Corporation NV4 [RIVA TNT] (rev 4).
      IRQ 11.
      Master Capable.  Latency=64.  Min Gnt=5.Max Lat=1.
      Non-prefetchable 32 bit memory at 0xef000000 [0xefffffff].
      Prefetchable 32 bit memory at 0xec000000 [0xecffffff].
  Bus  0, device  14, function  1:
    Ethernet controller: PCI device 0086:1079 (rev 3).
      IRQ 9.
      Master Capable.  Latency=64.  Min Gnt=255.
      Non-prefetchable 64 bit memory at 0xeefc0000 [0xeefdffff].
      Non-prefetchable 64 bit memory at 0xeef80000 [0xeefbffff].
      I/O at 0x5000 [0x503f].
  Bus  0, device  14, function  0:
    Ethernet controller: PCI device 0086:1079 (rev 3).
      IRQ 5.
      Master Capable.  Latency=64.  Min Gnt=255.
      Non-prefetchable 64 bit memory at 0xeef20000 [0xeef3ffff].
      Non-prefetchable 64 bit memory at 0xeeec0000 [0xeeefffff].
      I/O at 0x4c00 [0x4c3f].


The last two entries should be from the card.

The readme of the driver also states possible problems with hotplug. But
stopping network, disable hotplug (echo 0 > /proc/sys/kernel/hotplug)
and insmod'ing it then does not help.
I also created a modules.conf with
alias eth0 e1000
alias eth1 e1000
but without having this pseudo-device created.

To answer Declan Moriarty's question considering ethernet bridging I
have to say that I cannot find the option under menuconfig.

To add: If I insmod e1000 it outputs two lines identifying it as intel
pro/1000 driver and a copyright notice. Should it tell about found nics?

I will look if I can install lspci if that gives more usefull information.

Is there a way to create this pseudo-devices manual?

Thanks in advance!

Best regards,
- Ricky Blankenaufulland

-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to