Skip to contentSkip to conversation

dhcp problem with realtek 8139 clone with rh 7.1

DISCUSSION Michael K. Johnson 6 participants 6 messages May 4, 2001 – May 5, 2001

lore
Share & tools
lore
#0 lore raw
Quoted 8 lines · you

I have som problem with my realtek 8139 clone. It won't work with dhcp against my isp. I've just installed redhat 7.1 on a i386 with to (exactly the same) network cards, one that should be connected to my isp, and one to
the local network. My local network works fine, but when I try to start eth0
(which is the card connecting to my isp) I get

Quoted 4 lines

Determining IP configuration... Operation failed.
failed.

If I manually try to run 'pump -i eth0' I also get Operation failed.

This sounds more like pump failing to negotiate dhcp properly than like a failure in the driver. Let's check that possibility first before assuming a driver bug.

Install dhcpcd, chmod a-x /sbin/pump, and see if it works better (if pump is not there or not executable, the scripts fall back to dhcpcd). If so, please file a bug report against pump in buzilla
http://bugzilla.redhat.com/bugzilla/

michaelkjohnson

"He that composes himself is wiser than he that composes a book."
Linux Application Development -- Ben Franklin
http://people.redhat.com/johnsonm/lad/

#1 lore raw
Quoted 26 lines · Michael K. Johnson
Quoted 8 lines · you

I have som problem with my realtek 8139 clone. It won't work with dhcp against my isp. I've just installed redhat 7.1 on a i386 with to (exactly the same) network cards, one that should be connected to my isp, and one to
the local network. My local network works fine, but when I try to start eth0
(which is the card connecting to my isp) I get

Quoted 4 lines

Determining IP configuration... Operation failed.
failed.

If I manually try to run 'pump -i eth0' I also get Operation failed.

This sounds more like pump failing to negotiate dhcp properly than like a failure in the driver. Let's check that possibility first before assuming a driver bug.

Install dhcpcd, chmod a-x /sbin/pump, and see if it works better (if pump is not there or not executable, the scripts fall back to dhcpcd). If so, please file a bug report against pump in buzilla
http://bugzilla.redhat.com/bugzilla/

michaelkjohnson

Quoted 8 lines

"He that composes himself is wiser than he that composes a book."
Linux Application Development -- Ben Franklin
http://people.redhat.com/johnsonm/lad/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

I've had the same problem with the 8139too drivers and DHCP. The reason I figure it must be the drivers is because in the 2.4.3 kernel, I'm able to use the 8139too drivers with DHCP without any problems. In 2.4.4 it locks my system.

Signature · 3 lines
Adam
[email protected]
Linux user #190288
#2 lore raw
Quoted 4 lines

I've had the same problem with the 8139too drivers and DHCP. The reason I figure it must be the drivers is because in the 2.4.3 kernel, I'm able to use the 8139too drivers with DHCP without any problems. In 2.4.4 it locks my system.

Multiple such reports - seems the 8139too update broke stuf - any ideas Jeff, should I revert to the 2.4.3 one ?

#3 lore raw
Quoted 8 lines · Alan Cox
Quoted 5 lines

I've had the same problem with the 8139too drivers and DHCP. The reason I figure it must be the drivers is because in the 2.4.3 kernel, I'm able to use the 8139too drivers with DHCP without any problems. In 2.4.4 it locks my system.

Multiple such reports - seems the 8139too update broke stuf - any ideas Jeff, should I revert to the 2.4.3 one ?

I would say if Monday comes by without hearing from me, yes. It fixes some people, breaks others :/

I've already got a fix on the dhcp breakage -- need to lock and unlock EEprom before setting certain registers, and I am working on the other problem (symptom: 'partner ability 0000' even when a link is present).

Signature · 3 lines
Jeff Garzik      | Game called on account of naked chick
Building 1024    |
MandrakeSoft     |
#4 lore raw
In reply to Alan Cox
Quoted 7 lines · Alan Cox
Quoted 4 lines

I've had the same problem with the 8139too drivers and DHCP. The reason I figure it must be the drivers is because in the 2.4.3 kernel, I'm able to use the 8139too drivers with DHCP without any problems. In 2.4.4 it locks my system.

Multiple such reports - seems the 8139too update broke stuf - any ideas Jeff, should I revert to the 2.4.3 one ?

Ack!

I have two diskless systems that with 2.4.4 end up with VERY slow network interfaces. I then do a

	cp ../linux-2.4.2.clean/drivers/net/8139too.c drivers/net

and rebuild. Fixes my problems....

Jeff, my offer of acess to a box that has this problem still stands.

Roger.

Signature · 4 lines
** [email protected] ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots. 
* There are also old, bald pilots. 
#5 lore raw
In reply to Michael K. Johnson
Quoted 8 lines · Michael K. Johnson
Quoted 4 lines

I have som problem with my realtek 8139 clone. It won't work with dhcp against my isp. [...]

Determining IP configuration... Operation failed.

This sounds more like pump failing to negotiate dhcp properly than like a failure in the driver. Let's check that possibility first before assuming a driver bug.

It happens here also, but it does not seem to be a pump issue:

- I am using dhcpcd ;)

- DHCP with 2.4.3 works fine

- The packages sent by the DHCP-server are having the correct destination MAC, but 'tcpdump' on the RTL8139 machine does not see them unless the promiscous mode ist enabled. When putting the NIC into promiscous mode, DHCP works fine[1].

- After the DHCP info are fetched and the IP is set, the promiscous mode can be turned off.

- When setting the IP statically things are working without turning on promiscous mode

Enrico