This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Intel Pro 1000MT QuadPort

From the Hardware Compatibility List I see my brand new nic sitting there:

Code:

                                                  | t | e | u | h | v |
-Intel Corp.--------------------------------------|---|---|---|---|---|
  82546GB PRO/1000MT Quad Port Server Adapter     | X |   |   |   |   |

t   = 'tested' with Astaro Security Linux 5.000: we support these
      controllers

To be sure: it is an Intel PRO 1000 MT QuadPort Server Adapter (intel product code: PWLA8494MT)  with 2x 82546GB dual gigabit ethernet controllers (makes 4 ports right!). As seen in the table, it (should be) is fully tested and approved "OK" by Astaro.

I put this inside a PowerEdge 1550 server in a 64bits PCI slot. It replaced a temporarely RTL8139 NIC that was living there.

But... It my 400+ euro card is not detected by the kernel and moreover the RTL8139 kernel module is giving some errors at bootup (which is "logical", because this card is removed).

Do I have to reinstall Astaro (5.023)?
Or can I just su in the machine and do some modconf magic? I assume the kernel modules for the i82546GB controllers are in place. So I don't understand why these do not fire up.

Also I don't understand why the RTL8139 kernel modules is giving errors as it is removed now. Does the kernel do a one-time only hardware detection (at install)?

This thread was automatically locked due to age.

Parents

0 BarryG over 21 years ago

Yes, ASL only detects hw at install.

Edit
/etc/modules.conf

and change to the name of the correct kernel module (run lsmod if you don't know the name)

I don't know if a multi-port nic needs multiple entries or not. probably.

Barry
Cancel
Vote Up 0 Vote Down

Cancel
0 Tester100 over 21 years ago in reply to BarryG

You will need to edit your modules.conf file and replace the 8139too.o entry with the following

alias eth0 e100.o
alias eth1 e100.o
alias eth2 e100.o
alias eth3 e100.o

save your modules.conf file

run the command rmmod 8139too and then insmod e100

this should load the driver.

Go to webmin and configure the card or use ifconfig ethx up

This should take care of the four ports on the card.
Cancel
Vote Up 0 Vote Down

Cancel
0 cyclops over 21 years ago in reply to Tester100

I am not sure if it causes any trouble but normally you don't use file extensions inside modules.conf ->

alias eth0 e100
alias eth1 e100
alias eth2 e100
alias eth3 e100

Greetings
cyclops
Cancel
Vote Up 0 Vote Down

Cancel
0 Rob_F over 21 years ago in reply to cyclops

shouldnt it be the ee100pro driver?
Cancel
Vote Up 0 Vote Down

Cancel
0 BarryG over 21 years ago in reply to Rob_F

you mean eepro100

either would probably work, but the e100 is the one written by intel and is probably slightly more reliable. It's also the one Astaro 3.x and 5.x chose to use on our firewalls.

Barry
Cancel
Vote Up 0 Vote Down

Cancel
0 cyclops over 21 years ago in reply to Rob_F

e1000 for gigabit cards
Cancel
Vote Up 0 Vote Down

Cancel
0 Rob_F over 21 years ago in reply to cyclops

eepro100.o exists as does e100.o

so Astaro says use e100 not eepro100?
Cancel
Vote Up 0 Vote Down

Cancel
0 BarryG over 21 years ago in reply to Rob_F

When I installed ASL 3.x and 5.x, it chose the e100 driver for my Intel 100mbit NICs.

Also, some googling reveals that e100 is written by Intel, whereas eepro100 was written by Donald Becker, IIRC.

e100 is probably slightly more reliable, but both are very good.
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 BarryG over 21 years ago in reply to Rob_F

When I installed ASL 3.x and 5.x, it chose the e100 driver for my Intel 100mbit NICs.

Also, some googling reveals that e100 is written by Intel, whereas eepro100 was written by Donald Becker, IIRC.

e100 is probably slightly more reliable, but both are very good.
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data