Re: dhcp problem with realtek 8139 clone with rh 7.1
Hi, joining this conversation after reading it on an archive (so am not too sure how far it has progressed.) Me too! I am having the same problem as you describe. After booting and an initial (try) use of dhcp (which will fail) everything works fine. Until I shutdown then I get something along the lines of "too much work on interrupt." Damn how annoying that was, it's been a while since I have had issues like this with a release of a kernel. Oh well, I'll keep looking into this. Seeya -- Greg Wellington New Zealand ICQ# 19058919 Rome did not create a great empire by having meetings They did it by killing all those who opposed them. - 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/
Re: dhcp problem with realtek 8139 clone with rh 7.1
Alan Cox wrote: > > 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. -- ** [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. - 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/
Re: dhcp problem with realtek 8139 clone with rh 7.1
Alan Cox wrote: > > > 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 ' even when a link is present). -- Jeff Garzik | Game called on account of naked chick Building 1024| MandrakeSoft | - 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/
Re: dhcp problem with realtek 8139 clone with rh 7.1
> 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 ? - 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/
Re: dhcp problem with realtek 8139 clone with rh 7.1
Michael K. Johnson <[EMAIL PROTECTED]> writes: > >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 - 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/
Re: dhcp problem with realtek 8139 clone with rh 7.1
"Michael K. Johnson" wrote: > > In linux-kernel, you wrote: > >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 > > > >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/ > - > 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. -- Adam [EMAIL PROTECTED] Linux user #190288 - 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/
Re: dhcp problem with realtek 8139 clone with rh 7.1
In linux-kernel, you wrote: >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 > >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/ - 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/
dhcp problem with realtek 8139 clone with rh 7.1
Hi, 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 Determining IP configuration... Operation failed. failed. If I manually try to run 'pump -i eth0' I also get Operation failed. If I run 'mii-tool -v eth0' I get eth0: autonegotiation failed, link ok product info: vendor 00:00:00, model 0 rev 0 basic mode: autonegotiation enabled basic status: autonegotiation complete, link ok capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD I've tried using the rtl8139 as well as the 8139too driver shipped with linux kernel 2.4.4 which I'm using, and I'm trying to connect via a cable modem. My dmesg looks a bit strange too, I get som messages several times. 8139too Fast Ethernet driver 0.9.16 eth0: RealTek RTL8139 Fast Ethernet at 0xc4802000, 00:10:a7:08:2c:70, IRQ 11 eth0: Identified 8139 chip type 'RTL-8139C' eth1: RealTek RTL8139 Fast Ethernet at 0xc4804000, 00:10:a7:07:fc:83, IRQ 10 eth1: Identified 8139 chip type 'RTL-8139C' ... eth0: Setting half-duplex based on auto-negotiated partner ability . eth1: Setting half-duplex based on auto-negotiated partner ability . IP-Config: Incomplete network configuration information. NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 204k freed Adding Swap: 265032k swap-space (priority -1) keyboard: Timeout - AT keyboard not present? parport0: PC-style at 0x378 [PCSPP(,...)] eth0: Setting half-duplex based on auto-negotiated partner ability . eth0: Setting half-duplex based on auto-negotiated partner ability . eth0: Setting half-duplex based on auto-negotiated partner ability . eth1: Setting 100mbps full-duplex based on auto-negotiated partner ability 41e1. keyboard: Timeout - AT keyboard not present? keyboard: Timeout - AT keyboard not present? keyboard: Timeout - AT keyboard not present? eth0: Setting half-duplex based on auto-negotiated partner ability . eth0: Setting half-duplex based on auto-negotiated partner ability . eth0: Setting half-duplex based on auto-negotiated partner ability . eth0: Setting half-duplex based on auto-negotiated partner ability . eth0: Setting half-duplex based on auto-negotiated partner ability . eth0: Setting half-duplex based on auto-negotiated partner ability . eth0: Setting half-duplex based on auto-negotiated partner ability . eth0: Setting half-duplex based on auto-negotiated partner ability . eth0: Setting half-duplex based on auto-negotiated partner ability . eth0: Setting half-duplex based on auto-negotiated partner ability . eth0: Setting half-duplex based on auto-negotiated partner ability . eth0: Setting half-duplex based on auto-negotiated partner ability . eth0: Setting half-duplex based on auto-negotiated partner ability . eth0: Setting half-duplex based on auto-negotiated partner ability . Is this normal? Can anybody please help getting the card to work properly? Rgds, /Rasmus - The life which is unexamined is not worth living. -Plato - 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/
