Bug#537625: linux-image-2.6.26-2-amd64: RealTek r8111c NIC chipset not supported
dann frazier wrote: (Readding the bug to the CC list) On Sun, Jul 19, 2009 at 08:54:28PM -0400, Gary Dale wrote: dann frazier wrote: On Sun, Jul 19, 2009 at 06:05:39PM -0400, Gary Dale wrote: Package: linux-image-2.6.26-2-amd64 Version: 2.6.26-17 Severity: normal The RealTek 8111c chipset, frequently used in mainboards from many manufacturers, is not supported in the 2.6.26 kernel. I've tried the Ubuntu 9.04 distro and it does work with their 2.6.28 kernel. RealTek offer the source for a Linux driver on their web site that, according to some reports I've seen re. getting it to work with earlier Ubuntu versions, works back to at least kernel 2.6.24. I'd compile the module but aptitude reports problems getting everything I need. SO for now I'm using an old Linksys 10/100 USB Ethernet adapter. It looks like the r8169 module got loaded for your device: r8169 31492 0 What problem are you seeing with it? The 8111c doesn't use the r8169 driver. It uses the r8168. However, neither one seems to detect the onboard 8111c NIC on bootup. and the /etc/network directory doesn't seem to contain anything The r8169 source looks like it is intended to work with that the pci ids in your report, and the driver did appear to have claimed your device: Kernel driver in use: r8169 It might be interesting to see the output of 'dmesg' that shows the r8169 driver loading. The messages in your original report are missing the output from the first 11s after boot. Did you try 2.6.30? I know r8168 isn't there, but it would be interesting to know if r8169 from that kernel works. As for r8168 - it isn't upstream, so isn't a candidate for inclusion in the linux-2.6 package. It would be possible for someone to package it as a separate out of tree module package, see the RFP process here: http://www.debian.org/devel/wnpp/ I've now compiled the r8168 from the Realtek site and I can manually configure the network to work (as is evidenced by this e-mail). I'm just trying to work my way through the various documents to make it permanent. Apparently putting it into modules isn't sufficient. The Realtek documentation unfortunately only gives instructions for RedHat and Suse, neither of which are applicable to Debian. It's been a while since I had to manually configure the network settings and things seem to have changed a lot. The KDE 4.2 GUI tools don't help at all - they just generate an error message about not being able to parse an XML file. Try interfaces(5) I'll put the r8169 driver back tonight and let you know what I find. Meanwhile, as I mentioned earlier, the 2.6.30 kernel gave me the same results as the 2.6.26 did - a failure to bring up the interface. re. interfaces: as near as I can tell, the interfaces file is correct (not a network expert). It's the one that brought up the NIC on my previous mainboard and successfully brings up the USB ethernet adapter when I plug it in. When I manually do an ifconfig -a however, the onboard NIC gets added as eth1, even though there is no eth0. # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback address 127.0.0.1 netmask 255.0.0.0 # This is a list of hotpluggable network interfaces. # They will be activated automatically by the hotplug subsystem. mapping eth0 script grep map eth0 # The primary network interface allow-hotplug eth0 iface eth0 inet dhcp auto eth0 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#537625: linux-image-2.6.26-2-amd64: RealTek r8111c NIC chipset not supported
On Mon, Jul 20, 2009 at 06:58:01AM -0400, Gary Dale wrote: dann frazier wrote: (Readding the bug to the CC list) On Sun, Jul 19, 2009 at 08:54:28PM -0400, Gary Dale wrote: dann frazier wrote: On Sun, Jul 19, 2009 at 06:05:39PM -0400, Gary Dale wrote: Package: linux-image-2.6.26-2-amd64 Version: 2.6.26-17 Severity: normal The RealTek 8111c chipset, frequently used in mainboards from many manufacturers, is not supported in the 2.6.26 kernel. I've tried the Ubuntu 9.04 distro and it does work with their 2.6.28 kernel. RealTek offer the source for a Linux driver on their web site that, according to some reports I've seen re. getting it to work with earlier Ubuntu versions, works back to at least kernel 2.6.24. I'd compile the module but aptitude reports problems getting everything I need. SO for now I'm using an old Linksys 10/100 USB Ethernet adapter. It looks like the r8169 module got loaded for your device: r8169 31492 0 What problem are you seeing with it? The 8111c doesn't use the r8169 driver. It uses the r8168. However, neither one seems to detect the onboard 8111c NIC on bootup. and the /etc/network directory doesn't seem to contain anything The r8169 source looks like it is intended to work with that the pci ids in your report, and the driver did appear to have claimed your device: Kernel driver in use: r8169 It might be interesting to see the output of 'dmesg' that shows the r8169 driver loading. The messages in your original report are missing the output from the first 11s after boot. Did you try 2.6.30? I know r8168 isn't there, but it would be interesting to know if r8169 from that kernel works. As for r8168 - it isn't upstream, so isn't a candidate for inclusion in the linux-2.6 package. It would be possible for someone to package it as a separate out of tree module package, see the RFP process here: http://www.debian.org/devel/wnpp/ I've now compiled the r8168 from the Realtek site and I can manually configure the network to work (as is evidenced by this e-mail). I'm just trying to work my way through the various documents to make it permanent. Apparently putting it into modules isn't sufficient. The Realtek documentation unfortunately only gives instructions for RedHat and Suse, neither of which are applicable to Debian. It's been a while since I had to manually configure the network settings and things seem to have changed a lot. The KDE 4.2 GUI tools don't help at all - they just generate an error message about not being able to parse an XML file. Try interfaces(5) I'll put the r8169 driver back tonight and let you know what I find. Meanwhile, as I mentioned earlier, the 2.6.30 kernel gave me the same results as the 2.6.26 did - a failure to bring up the interface. Cool - try booting and providing the output of 'dmesg' and 'lsmod'. re. interfaces: as near as I can tell, the interfaces file is correct (not a network expert). It's the one that brought up the NIC on my previous mainboard and successfully brings up the USB ethernet adapter when I plug it in. When I manually do an ifconfig -a however, the onboard NIC gets added as eth1, even though there is no eth0. Debian does persistant naming, to avoid nics getting reordered. Once the OS assigns a name to a physical NIC, that name becomes reserved for that NIC. If the NIC that was originally assigned eth0 gets removed, you will no longer have an eth0. # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback address 127.0.0.1 netmask 255.0.0.0 # This is a list of hotpluggable network interfaces. # They will be activated automatically by the hotplug subsystem. mapping eth0 script grep map eth0 # The primary network interface allow-hotplug eth0 iface eth0 inet dhcp auto eth0 -- dann frazier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#537625: linux-image-2.6.26-2-amd64: RealTek r8111c NIC chipset not supported
Package: linux-image-2.6.26-2-amd64 Version: 2.6.26-17 Severity: normal The RealTek 8111c chipset, frequently used in mainboards from many manufacturers, is not supported in the 2.6.26 kernel. I've tried the Ubuntu 9.04 distro and it does work with their 2.6.28 kernel. RealTek offer the source for a Linux driver on their web site that, according to some reports I've seen re. getting it to work with earlier Ubuntu versions, works back to at least kernel 2.6.24. I'd compile the module but aptitude reports problems getting everything I need. SO for now I'm using an old Linksys 10/100 USB Ethernet adapter. -- Package-specific info: ** Version: Linux version 2.6.26-2-amd64 (Debian 2.6.26-17) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Sun Jun 21 04:47:08 UTC 2009 ** Command line: root=/dev/md2 ro ** Not tainted ** Kernel log: [ 11.831094] usbcore: registered new interface driver pegasus [ 12.171598] input: PC Speaker as /class/input/input4 [ 12.209500] ACPI: PCI Interrupt :00:14.2[A] - GSI 16 (level, low) - IRQ 16 [ 12.247999] hda_codec: Unknown model for ALC882, trying auto-probe from BIOS... [ 12.253966] input: ImExPS/2 Generic Explorer Mouse as /class/input/input5 [ 12.265119] cx23885 driver version 0.0.1 loaded [ 12.285120] ACPI: PCI Interrupt :01:05.1[B] - GSI 19 (level, low) - IRQ 19 [ 12.285202] PCI: Setting latency timer of device :01:05.1 to 64 [ 12.331141] Error: Driver 'pcspkr' is already registered, aborting... [ 12.334057] ACPI: PCI Interrupt :02:00.0[A] - GSI 18 (level, low) - IRQ 18 [ 12.334203] CORE cx23885[0]: subsystem: 0070:7911, board: Hauppauge WinTV-HVR1250 [card=3,autodetected] [ 12.438975] cx23885[0]: i2c bus 0 registered [ 12.438975] cx23885[0]: i2c bus 1 registered [ 12.438975] cx23885[0]: i2c bus 2 registered [ 12.466976] tveeprom 1-0050: Encountered bad packet header [ff]. Corrupt or not a Hauppauge eeprom. [ 12.466976] cx23885[0]: warning: unknown hauppauge model #0 [ 12.466976] cx23885[0]: hauppauge eeprom: model=0 [ 12.466976] cx23885[0]: cx23885 based dvb card [ 12.581972] MT2131: successfully identified at address 0x61 [ 12.581972] DVB: registering new adapter (cx23885[0]) [ 12.581972] DVB: registering frontend 0 (Samsung S5H1409 QAM/8VSB Frontend)... [ 12.581972] cx23885_dev_checkrevision() Hardware revision = 0xc0 [ 12.581972] cx23885[0]/0: found at :02:00.0, rev: 3, irq: 18, latency: 0, mmio: 0xfd60 [ 12.581972] PCI: Setting latency timer of device :02:00.0 to 64 [ 13.552758] ov511: Failed to read sensor ID. You might not have an [ 13.552758] ov511: OV7610/20, or it may be not responding. Report [ 13.552758] ov511: this to m...@alpha.dyndns.org [ 13.552758] ov511: This is only a warning. You can attempt to use [ 13.552758] ov511: your camera anyway [ 13.708727] ov511: Sensor is an OV7610 [ 14.471631] ov511: Device at usb-:00:12.1-2 registered to minor 0 [ 14.471683] usbcore: registered new interface driver ov511 [ 14.471715] ov511: v1.64 for Linux 2.5 : ov511 USB Camera Driver [ 15.350755] Adding 2008116k swap on /dev/sda3. Priority:-1 extents:1 across:2008116k [ 15.363547] Adding 2008116k swap on /dev/sdb3. Priority:-2 extents:1 across:2008116k [ 15.866342] EXT3 FS on md2, internal journal [ 16.364299] ide_generic: please use probe_mask=0x3f module parameter for probing all legacy ISA IDE ports [ 16.364299] ide_generic: I/O resource 0x1F0-0x1F7 not free. [ 16.364299] ide_generic: I/O resource 0x170-0x177 not free. [ 16.410868] it87: Found IT8718F chip at 0x228, revision 5 [ 16.410868] it87: in3 is VCC (+5V) [ 16.410868] hwmon-vid: Unknown VRM version of your x86 CPU [ 16.484813] device-mapper: uevent: version 1.0.3 [ 16.484813] device-mapper: ioctl: 4.13.0-ioctl (2007-10-18) initialised: dm-de...@redhat.com [ 17.598202] fuse init (API version 7.9) [ 17.661005] kjournald starting. Commit interval 5 seconds [ 17.667061] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended [ 17.690839] EXT3 FS on md0, internal journal [ 17.690839] EXT3-fs: mounted filesystem with ordered data mode. [ 17.902649] kjournald starting. Commit interval 5 seconds [ 18.035045] EXT3 FS on md1, internal journal [ 18.035045] EXT3-fs: mounted filesystem with ordered data mode. [ 18.950122] eth0: set allmulti [ 18.950576] eth0: set allmulti [ 20.154585] eth0: set allmulti [ 20.154628] eth0: set allmulti [ 21.142076] NET: Registered protocol family 10 [ 21.142076] lo: Disabled Privacy Extensions [ 21.142076] eth0: set allmulti [ 21.142076] eth0: set allmulti [ 23.876858] eth0: set allmulti [ 23.876858] eth0: set allmulti [ 42.073045] kvm: Nested Paging enabled [ 50.406387] pnp: the driver 'parport_pc' has been registered [ 50.406387] lp: driver loaded but no devices found [ 50.444684] ppdev: user-space parallel port driver [ 53.082248] mtrr: no
Bug#537625: linux-image-2.6.26-2-amd64: RealTek r8111c NIC chipset not supported
On Sun, Jul 19, 2009 at 06:05:39PM -0400, Gary Dale wrote: Package: linux-image-2.6.26-2-amd64 Version: 2.6.26-17 Severity: normal The RealTek 8111c chipset, frequently used in mainboards from many manufacturers, is not supported in the 2.6.26 kernel. I've tried the Ubuntu 9.04 distro and it does work with their 2.6.28 kernel. RealTek offer the source for a Linux driver on their web site that, according to some reports I've seen re. getting it to work with earlier Ubuntu versions, works back to at least kernel 2.6.24. I'd compile the module but aptitude reports problems getting everything I need. SO for now I'm using an old Linksys 10/100 USB Ethernet adapter. It looks like the r8169 module got loaded for your device: r8169 31492 0 What problem are you seeing with it? -- dann frazier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#537625: linux-image-2.6.26-2-amd64: RealTek r8111c NIC chipset not supported
(Readding the bug to the CC list) On Sun, Jul 19, 2009 at 08:54:28PM -0400, Gary Dale wrote: dann frazier wrote: On Sun, Jul 19, 2009 at 06:05:39PM -0400, Gary Dale wrote: Package: linux-image-2.6.26-2-amd64 Version: 2.6.26-17 Severity: normal The RealTek 8111c chipset, frequently used in mainboards from many manufacturers, is not supported in the 2.6.26 kernel. I've tried the Ubuntu 9.04 distro and it does work with their 2.6.28 kernel. RealTek offer the source for a Linux driver on their web site that, according to some reports I've seen re. getting it to work with earlier Ubuntu versions, works back to at least kernel 2.6.24. I'd compile the module but aptitude reports problems getting everything I need. SO for now I'm using an old Linksys 10/100 USB Ethernet adapter. It looks like the r8169 module got loaded for your device: r8169 31492 0 What problem are you seeing with it? The 8111c doesn't use the r8169 driver. It uses the r8168. However, neither one seems to detect the onboard 8111c NIC on bootup. and the /etc/network directory doesn't seem to contain anything The r8169 source looks like it is intended to work with that the pci ids in your report, and the driver did appear to have claimed your device: Kernel driver in use: r8169 It might be interesting to see the output of 'dmesg' that shows the r8169 driver loading. The messages in your original report are missing the output from the first 11s after boot. Did you try 2.6.30? I know r8168 isn't there, but it would be interesting to know if r8169 from that kernel works. As for r8168 - it isn't upstream, so isn't a candidate for inclusion in the linux-2.6 package. It would be possible for someone to package it as a separate out of tree module package, see the RFP process here: http://www.debian.org/devel/wnpp/ I've now compiled the r8168 from the Realtek site and I can manually configure the network to work (as is evidenced by this e-mail). I'm just trying to work my way through the various documents to make it permanent. Apparently putting it into modules isn't sufficient. The Realtek documentation unfortunately only gives instructions for RedHat and Suse, neither of which are applicable to Debian. It's been a while since I had to manually configure the network settings and things seem to have changed a lot. The KDE 4.2 GUI tools don't help at all - they just generate an error message about not being able to parse an XML file. Try interfaces(5) -- dann frazier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
