Re: Realtek RTL 8139C and Linux Kernel 2.4.22.
On Tuesday 30 September 2003 04:35, uGAH man wrote: > > /proc/pci (kernel 2.4) > > > > Bus 0, device 9, function 0: > > Ethernet controller: Realtek Semiconductor Co., Ltd. > > RTL-8139/8139C/8139C+ (rev 16). > > IRQ 10. > > Master Capable. Latency=32. Min Gnt=32.Max Lat=64. > > I/O at 0xb800 [0xb8ff]. > > Non-prefetchable 32 bit memory at 0xe380 [0xe38000ff]. Hm Just to let you know that you're not alone in this world: I think I'm seeing something similar... I have a Realtek card too, that I just dropped in there to connect my laptop to. I also have a Davicom card which is the one I'm using to connect to the Internet, that works beautifully, but the Realtek card gives me very little. It is not something I have given any priority, though... Cheers, Kjetil -- Kjetil Kjernsmo Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Homepage: http://www.kjetil.kjernsmo.net/OpenPGP KeyID: 6A6A0BBC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Realtek RTL 8139C and Linux Kernel 2.4.22.
On Mon, 2003-09-29 at 20:56, uGAH man wrote: > Micha Feigin wrote: > > > On Mon, 2003-09-29 at 05:54, devotion wrote: > > > >> Hi. [snip] > When I run dmesg|grep -n -B 3 -A 3 eth , i get: > Kernel 2.2: > 53-3c59x.c 18Feb01 Donald Becker and others > http://www.scyld.com/network/vortex.html > 54-pcnet32.c: PCI bios is present, checking for devices... > 55-rtl8139.c:v1.07 5/6/99 Donald Becker > http://cesdis.gsfc.nasa.gov/linux/drivers/rtl8139.html > 56:eth0: RealTek RTL8139 Fast Ethernet at 0xb800, IRQ 10, 00:e0:7d:c8:12:93. > 57-via-rhine.c:v1.08b-LK1.0.1 12/14/2000 Written by Donald Becker > 58- http://www.scyld.com/network/via-rhine.html > 66:eth1: 8139too Fast Ethernet driver 0.9.18-pre4 Jeff Garzik > <[EMAIL PROTECTED]> > 67:eth1: Linux-2.2 bug reports to Jens David <[EMAIL PROTECTED]> > 68:eth1: RealTek RTL8139 Fast Ethernet board found at 0xd004d000, IRQ 10 > 69:eth1: Chip is 'RTL-8139C' - MAC address '00:e0:7d:c8:12:93'. > 70-CSLIP: code copyright 1989 Regents of the University of California > 71-PPP: version 2.3.7 (demand dialling) > 72-PPP line discipline registered. > 74-PPP BSD Compression module registered > 75-PPP Deflate Compression module registered > 76:eth1: Setting half-duplex based on auto-negotiated partner ability . > 77-registered device ppp0 > 78-probable hardware bug: clock timer configuration lost - probably a > VIA686a. > 79-probable hardware bug: restoring chip configuration. > -- > 81-device ppp0 left promiscuous mode > 82-device ppp0 entered promiscuous mode > 83-device ppp0 left promiscuous mode > 84:eth1: Promiscuous mode enabled. > 85:device eth1 entered promiscuous mode > 86:device eth1 left promiscuous mode > 87:device eth0 entered promiscuous mode > 88:device eth0 left promiscuous mode > 89-device ppp0 entered promiscuous mode > 90-device ppp0 left promiscuous mode > > Kernel 2.4: > ike:/home/ugah# dmesg | grep -n -B 3 -A 3 eth > 78-Adding Swap: 514100k swap-space (priority -1) > 79-8139too Fast Ethernet driver 1.6.0 loaded > 80-PCI: Found IRQ 10 for device 00:09.0# > 81:eth0: use memory map. ioaddr=0xd086e000 > 82:eth0: Identified 8139CP chip type 'RTL-8139C' > 83:eth0: RealTek RTL8139CP Fast Ethernet at 0xd086e000, > 00:e0:7d:c8:12:93, IRQ 10 > 84-NTFS driver v1.1.22 [Flags: R/O MODULE] > 85-CSLIP: code copyright 1989 Regents of the University of California > 86-PPP generic driver version 2.4.2 > -- > 93-PPP Deflate Compression module registered > 94-usb.c: registered new driver usblp > 95-printer.c: v0.11: USB Printer Device Class driver > 96:eth0: Setting half-duplex based on auto-negotiated partner ability . Looks like the 2.4 kernel isn't seeing eth1 at boot time, and that's odd. How about "/sbin/lspci" (which is more compact than 'cat /proc/pci')? -- - Ron Johnson, Jr. [EMAIL PROTECTED] Jefferson, LA USA "Experience hath shewn, that even under the best forms [of government] those entrusted with power have, in time, and by slow operations, perverted it into tyranny." Thomas Jefferson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Realtek RTL 8139C and Linux Kernel 2.4.22.
uGAH man wrote: uGAH man wrote: Micha Feigin wrote: > On Mon, 2003-09-29 at 05:54, devotion wrote: > >> Hi. >> I asked help some time ago and got no reply... trying again (sorry if >>that unappropriate). >> I have very recently installed the Debian 3.0r1 Linux cd, using >>default kernel that comes with it, the 2.2.20idepci. >> I am using adsl, whose modem is connected to my only NIC, a Realtek >>8139C (not C+, i see 8139C on the chip), and the realtek 8139C driver >>(8139too.o) detected 2 network interfaces (eth0 and eth1), both on the >>same IRQ (10). >> When i boot, eth0 is brought up and eth1 stays down. >> When i start pppoeconf, it searches for Access Concentrators on >>"both" the nics, and finds it in the eth1 card. >> pppoeconf saves my setup, and when i boot, eth0 is brought up, and >>eth1 is also brought up. When ppp tries to use eth1, the box resets >>(IRQ conflict?). >> I therefore edited the ppp_on_boot script to bring eth0 down and >>bring eth1 up, and now everything related to internet works fine in my >>2.2 kernel. >> Problem is, I want to install the 2.4 kernel to support all my other >>hardware. I installed the same driver, but now it only detects 1 >>network interface card (which was expected at first). pppoeconf >>detects the concentrator in eth0 (which was also expected) (it does >>not detect it when i unplug the cable, so i assume its communicating >>with the modem), but i am not getting any reply from my ISP's >>authentication server (at 200.165.104.12) nor any DNS servers... >> Does anyone what this is all about? >> I have tried to: >> - download the driver from the realtek site, compile it with the new >>kernel, same result >> - recompile the 2.2 kernel (debian package), but no 8139too.c within it >> - recompile the 2.4 8139too.c with the 2.2 kernel includes, does not >>compile >> None of these attempts succeded. >> Any help is very appreciated, thanks. >> -- Fred >> > > Try running tcpdump on the iterface while you are starting ppp and see > if you can see any requests the card is sending out and not getting replies > to. Whats the output of tcpdump if you run a dhco client in the interface? >Are you sure it's a driver issue? > What does the output of this command look like? > dmesg |grep -n -B 3 -A 3 eth > > Also, what about /etc/network/interfaces , /sbin/ifconfig and > /sbin/route ? OK, i tried running these commands, i got: Kernel 2.4 (non working): ike:/home/ugah# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:E0:7D:C8:12:93 inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:10 Base address:0xe000 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:560 (560.0 b) TX bytes:560 (560.0 b) Kernel 2.2 (working): ike:~ugah# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:E0:7D:C8:12:93 inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:10 Base address:0xb800 eth1 Link encap:Ethernet HWaddr 00:E0:7D:C8:12:93 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2883 errors:0 dropped:0 overruns:0 frame:0 TX packets:1911 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:2835304 (2.7 MiB) TX bytes:191356 (186.8 KiB) Interrupt:10 Base address:0xd000 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:3924 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:560 (560.0 b) TX bytes:560 (560.0 b) ppp0 Link encap:Point-to-Point Protocol inet addr:200.165.218.232 P-t-P:200.216.95.212 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:2881 errors:0 dropped:0 overruns:0 frame:0 TX packets:1909 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:10 RX bytes:3553263 (3.3 MiB) TX bytes:204722 (199.9 KiB) When I run dmesg|grep -n -B 3 -A 3 eth , i get: Kernel 2.2:
Re: Realtek RTL 8139C and Linux Kernel 2.4.22.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 In addition to what Ron Johnson asked for, what does /proc/pci say? - -- John_ email: [EMAIL PROTECTED]Quis custodiet ipsos custodes -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iEYEARECAAYFAj94gmIACgkQkz0vhQtHHRgtLgCeMium28xkV5SWUbFuDFeAhe0S nykAn1jN7hi8R5NJ9v7iwTLHVx5rGX2k =jrSj -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Realtek RTL 8139C and Linux Kernel 2.4.22.
Micha Feigin wrote: > On Mon, 2003-09-29 at 05:54, devotion wrote: > >> Hi. >> I asked help some time ago and got no reply... trying again (sorry if >>that unappropriate). >> I have very recently installed the Debian 3.0r1 Linux cd, using >>default kernel that comes with it, the 2.2.20idepci. >> I am using adsl, whose modem is connected to my only NIC, a Realtek >>8139C (not C+, i see 8139C on the chip), and the realtek 8139C driver >>(8139too.o) detected 2 network interfaces (eth0 and eth1), both on the >>same IRQ (10). >> When i boot, eth0 is brought up and eth1 stays down. >> When i start pppoeconf, it searches for Access Concentrators on >>"both" the nics, and finds it in the eth1 card. >> pppoeconf saves my setup, and when i boot, eth0 is brought up, and >>eth1 is also brought up. When ppp tries to use eth1, the box resets >>(IRQ conflict?). >> I therefore edited the ppp_on_boot script to bring eth0 down and >>bring eth1 up, and now everything related to internet works fine in my >>2.2 kernel. >> Problem is, I want to install the 2.4 kernel to support all my other >>hardware. I installed the same driver, but now it only detects 1 >>network interface card (which was expected at first). pppoeconf >>detects the concentrator in eth0 (which was also expected) (it does >>not detect it when i unplug the cable, so i assume its communicating >>with the modem), but i am not getting any reply from my ISP's >>authentication server (at 200.165.104.12) nor any DNS servers... >> Does anyone what this is all about? >> I have tried to: >> - download the driver from the realtek site, compile it with the new >>kernel, same result >> - recompile the 2.2 kernel (debian package), but no 8139too.c within it >> - recompile the 2.4 8139too.c with the 2.2 kernel includes, does not >>compile >> None of these attempts succeded. >> Any help is very appreciated, thanks. >> -- Fred >> > > Try running tcpdump on the iterface while you are starting ppp and see > if you can see any requests the card is sending out and not getting replies > to. Whats the output of tcpdump if you run a dhco client in the interface? >Are you sure it's a driver issue? > What does the output of this command look like? > dmesg |grep -n -B 3 -A 3 eth > > Also, what about /etc/network/interfaces , /sbin/ifconfig and > /sbin/route ? OK, i tried running these commands, i got: Kernel 2.4 (non working): ike:/home/ugah# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:E0:7D:C8:12:93 inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:10 Base address:0xe000 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:560 (560.0 b) TX bytes:560 (560.0 b) Kernel 2.2 (working): ike:~ugah# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:E0:7D:C8:12:93 inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:10 Base address:0xb800 eth1 Link encap:Ethernet HWaddr 00:E0:7D:C8:12:93 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2883 errors:0 dropped:0 overruns:0 frame:0 TX packets:1911 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:2835304 (2.7 MiB) TX bytes:191356 (186.8 KiB) Interrupt:10 Base address:0xd000 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:3924 Metric:1 RX packets:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:560 (560.0 b) TX bytes:560 (560.0 b) ppp0 Link encap:Point-to-Point Protocol inet addr:200.165.218.232 P-t-P:200.216.95.212 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:2881 errors:0 dropped:0 overruns:0 frame:0 TX packets:1909 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:10 RX bytes:3553263 (3.3 MiB) TX bytes:204722 (199.9 KiB) When I run dmesg|grep -n -B 3 -A 3 eth , i get: Kernel 2.2: 53-3c59x.c 18Feb01 Donald Becker and others http://www.scyld.com/network/vortex.h
Re: Realtek RTL 8139C and Linux Kernel 2.4.22.
On Mon, 2003-09-29 at 05:54, devotion wrote: > Hi. > I asked help some time ago and got no reply... trying again (sorry if > that unappropriate). > I have very recently installed the Debian 3.0r1 Linux cd, using > default kernel that comes with it, the 2.2.20idepci. > I am using adsl, whose modem is connected to my only NIC, a Realtek > 8139C (not C+, i see 8139C on the chip), and the realtek 8139C driver > (8139too.o) detected 2 network interfaces (eth0 and eth1), both on the > same IRQ (10). > When i boot, eth0 is brought up and eth1 stays down. > When i start pppoeconf, it searches for Access Concentrators on > "both" the nics, and finds it in the eth1 card. > pppoeconf saves my setup, and when i boot, eth0 is brought up, and > eth1 is also brought up. When ppp tries to use eth1, the box resets > (IRQ conflict?). > I therefore edited the ppp_on_boot script to bring eth0 down and > bring eth1 up, and now everything related to internet works fine in my > 2.2 kernel. > Problem is, I want to install the 2.4 kernel to support all my other > hardware. I installed the same driver, but now it only detects 1 > network interface card (which was expected at first). pppoeconf > detects the concentrator in eth0 (which was also expected) (it does > not detect it when i unplug the cable, so i assume its communicating > with the modem), but i am not getting any reply from my ISP's > authentication server (at 200.165.104.12) nor any DNS servers... > Does anyone what this is all about? > I have tried to: > - download the driver from the realtek site, compile it with the new > kernel, same result > - recompile the 2.2 kernel (debian package), but no 8139too.c within it > - recompile the 2.4 8139too.c with the 2.2 kernel includes, does not > compile > None of these attempts succeded. > Any help is very appreciated, thanks. > -- Fred > Try running tcpdump on the iterface while you are starting ppp and see if you can see any requests the card is sending out and not getting replies to. Whats the output of tcpdump if you run a dhco client in the interface? -- Micha Feigin [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Realtek RTL 8139C and Linux Kernel 2.4.22.
On Sun, 2003-09-28 at 21:54, devotion wrote: > Hi. > I asked help some time ago and got no reply... trying again (sorry if > that unappropriate). > I have very recently installed the Debian 3.0r1 Linux cd, using > default kernel that comes with it, the 2.2.20idepci. > I am using adsl, whose modem is connected to my only NIC, a Realtek > 8139C (not C+, i see 8139C on the chip), and the realtek 8139C driver > (8139too.o) detected 2 network interfaces (eth0 and eth1), both on the > same IRQ (10). > When i boot, eth0 is brought up and eth1 stays down. > When i start pppoeconf, it searches for Access Concentrators on > "both" the nics, and finds it in the eth1 card. > pppoeconf saves my setup, and when i boot, eth0 is brought up, and > eth1 is also brought up. When ppp tries to use eth1, the box resets > (IRQ conflict?). > I therefore edited the ppp_on_boot script to bring eth0 down and > bring eth1 up, and now everything related to internet works fine in my > 2.2 kernel. > Problem is, I want to install the 2.4 kernel to support all my other > hardware. I installed the same driver, but now it only detects 1 > network interface card (which was expected at first). pppoeconf > detects the concentrator in eth0 (which was also expected) (it does > not detect it when i unplug the cable, so i assume its communicating > with the modem), but i am not getting any reply from my ISP's > authentication server (at 200.165.104.12) nor any DNS servers... > Does anyone what this is all about? > I have tried to: > - download the driver from the realtek site, compile it with the new > kernel, same result > - recompile the 2.2 kernel (debian package), but no 8139too.c within it > - recompile the 2.4 8139too.c with the 2.2 kernel includes, does not > compile > None of these attempts succeded. > Any help is very appreciated, thanks. > -- Fred Are you sure it's a driver issue? What does the output of this command look like? dmesg |grep -n -B 3 -A 3 eth Also, what about /etc/network/interfaces , /sbin/ifconfig and /sbin/route ? -- - Ron Johnson, Jr. [EMAIL PROTECTED] Jefferson, LA USA "Perl is worse than Python because people wanted it worse." Larry Wall, 10/14/1998 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
