[Bug 79626] Re: realtek gigabit ethernet not recognised on feisty
This is a bit of a problem for me. I have a laptop Acer Aspire 5024wmli, and my Gigabit nic works under windows, but stopped working under ubuntu Karmic about a week ago. how can i help get this one fixed? -- realtek gigabit ethernet not recognised on feisty https://bugs.launchpad.net/bugs/79626 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79626] Re: realtek gigabit ethernet not recognised on feisty
This bug report is being closed because we received no response to the previous inquiry for information. Please reopen if this is still an issue in the current Ubuntu release, Jaunty Jackalope 9.04. To reopen the bug, click on the current status, under the Status column, and change the status back to New. Thanks. ** Changed in: linux (Ubuntu) Status: Incomplete = Won't Fix -- realtek gigabit ethernet not recognised on feisty https://bugs.launchpad.net/bugs/79626 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79626] Re: realtek gigabit ethernet not recognised on feisty
** Changed in: linux (Ubuntu) Importance: Undecided = Low ** Changed in: linux (Ubuntu) Assignee: (unassigned) = Colin King (colin-king) -- realtek gigabit ethernet not recognised on feisty https://bugs.launchpad.net/bugs/79626 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79626] Re: realtek gigabit ethernet not recognised on feisty
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test: 1) If you are comfortable installing packages on your own, the linux- image-2.6.27-* package is currently available for you to install and test. --or-- 2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD. Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback. ** Tags added: cft-2.6.27 -- realtek gigabit ethernet not recognised on feisty https://bugs.launchpad.net/bugs/79626 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79626] Re: realtek gigabit ethernet not recognised on feisty
[quote]jared1999 said on 2007-06-02: (permalink) There is an issue with wake-on-lan setting if you dual boot with Windows. The Gentoo wiki has some information, read the troubleshooting section almost at the top. http://gentoo-wiki.com/HARDWARE_RTL8168 This worked for me.[/quote] This is on the money. Given that we probably won't get far trying to have Realtek change the Windows driver I guess its up to the R8169/8111 kernel driver person to find out how to turn on the card again. From reading that Gentoo link it appears Realtek themselves have done some work relating to this and Kernel 2.6. I believe this is actually a Windows driver bug - the Realtek DOS driver (used for ghosting among other things) also doesn't successfully turn the card back on after Windows has shutdown, so the issue is really at the Realtek end of things. Regards, Craig -- realtek gigabit ethernet not recognised on feisty https://bugs.launchpad.net/bugs/79626 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79626] Re: realtek gigabit ethernet not recognised on feisty
I have the same problem. If i start my system with ethernet cable disconnect, the kernel dont recognize my connection, but qhen i start system with cable connected it works well until i desconnect the cable, when i do it the ubuntu doesnt recognize the link anymore. So i reload NIC's module. But my speed lan is correctly detected (100Mb/s) and i prefer reload the module and the networking services. Is it a kernel problem? I was using Edgy without problems, this problems appears when i upgrade my system. -- realtek gigabit ethernet not recognised on feisty https://bugs.launchpad.net/bugs/79626 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79626] Re: realtek gigabit ethernet not recognised on feisty
** Changed in: linux-source-2.6.20 (Ubuntu) Assignee: (unassigned) = Ubuntu Kernel Team -- realtek gigabit ethernet not recognised on feisty https://bugs.launchpad.net/bugs/79626 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79626] Re: realtek gigabit ethernet not recognised on feisty
@Leterp: To apply the ethtool settings permanently: Create a file /etc/network/if-pre-up.d/any_name_you_like with following content: #!/bin/sh ethtool -s eth0 autoneg off speed 10 duplex half The script is called every time before the network device is activated. -- realtek gigabit ethernet not recognised on feisty https://bugs.launchpad.net/bugs/79626 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79626] Re: realtek gigabit ethernet not recognised on feisty
Did you try the ethtool workaround I posted here? -- realtek gigabit ethernet not recognised on feisty https://bugs.launchpad.net/bugs/79626 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79626] Re: realtek gigabit ethernet not recognised on feisty
Janosch, i dont read the comment. Work for me, thank you very much for your atention. Exist one method for permanent config? Or all time that to want to use will have that to use the command? Thanks again. -- realtek gigabit ethernet not recognised on feisty https://bugs.launchpad.net/bugs/79626 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79626] Re: realtek gigabit ethernet not recognised on feisty
well ... thats not exactly a fix ... so I dont want to use it. Kalyan -- realtek gigabit ethernet not recognised on feisty https://bugs.launchpad.net/bugs/79626 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79626] Re: realtek gigabit ethernet not recognised on feisty
There is an issue with wake-on-lan setting if you dual boot with Windows. The Gentoo wiki has some information, read the troubleshooting section almost at the top. http://gentoo-wiki.com/HARDWARE_RTL8168 This worked for me. -- realtek gigabit ethernet not recognised on feisty https://bugs.launchpad.net/bugs/79626 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79626] Re: realtek gigabit ethernet not recognised on feisty
I have the same problem, in notebook Toshiba A135-S4487. The diver 8169 for RTL8168/8111 doens't work, the DHCP not begin. ** Changed in: linux-source-2.6.20 (Ubuntu) Assignee: Ubuntu Kernel Team = Leterp ** Tags added: 8169 rtl8168 -- realtek gigabit ethernet not recognised on feisty https://bugs.launchpad.net/bugs/79626 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79626] Re: realtek gigabit ethernet not recognised on feisty
** Changed in: linux-source-2.6.20 (Ubuntu) Assignee: Leterp = (unassigned) -- realtek gigabit ethernet not recognised on feisty https://bugs.launchpad.net/bugs/79626 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79626] Re: realtek gigabit ethernet not recognised on feisty
still happens in feisty final with all updates. Come on, any replies from the DEVs about this? This worked great in all previous releases why doesn't it work in Feisty -- realtek gigabit ethernet not recognised on feisty https://bugs.launchpad.net/bugs/79626 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79626] Re: realtek gigabit ethernet not recognised on feisty
I found sth that works for me. I set my realtek 8168b to half-duplex and 10Mbit/s and now I get a DHCP offer. I used ethtool to do that: ethtool -s eth0 duplex half speed 10 autoneg off. I hope this is useful for somone else. Even if this is a workaround I would love to get at least 100MBit/s working. -- realtek gigabit ethernet not recognised on feisty https://bugs.launchpad.net/bugs/79626 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79626] Re: realtek gigabit ethernet not recognised on feisty
I got the same issue. My onboard RTL8168B is recognized but doesen't get an IP assigned. All other devices within my network are getting an IP assigned. Ethtool tells me that link is up. I have the same issue in Vista Business 32bit, so it might be a BIOS or hardware issue. I have two more network device for testing purposes on the ubuntu pc: A 3Com 3c950-TX, which seems to have exact the same issues. A DWL-122 USB WLAN device, which works flawlessly -- realtek gigabit ethernet not recognised on feisty https://bugs.launchpad.net/bugs/79626 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
RE: [Bug 79626] Re: realtek gigabit ethernet not recognised on feisty
I wish they fix this ASAP. I even tried with the r1000 driver with no success. Kalyan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Janosch Peters Sent: Tuesday, May 15, 2007 3:59 PM To: [EMAIL PROTECTED] Subject: [Bug 79626] Re: realtek gigabit ethernet not recognised on feisty I got the same issue. My onboard RTL8168B is recognized but doesen't get an IP assigned. All other devices within my network are getting an IP assigned. Ethtool tells me that link is up. I have the same issue in Vista Business 32bit, so it might be a BIOS or hardware issue. I have two more network device for testing purposes on the ubuntu pc: A 3Com 3c950-TX, which seems to have exact the same issues. A DWL-122 USB WLAN device, which works flawlessly -- realtek gigabit ethernet not recognised on feisty https://bugs.launchpad.net/bugs/79626 You received this bug notification because you are a direct subscriber of the bug. -- realtek gigabit ethernet not recognised on feisty https://bugs.launchpad.net/bugs/79626 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79626] Re: realtek gigabit ethernet not recognised on feisty
I have installed final release of 7.04 on a laptop and forced r1000 driver. I get link up but I cant get a DHCP IP assigned. The DHCP server is handing out the IP but the NIC doesnt get one assigned. Any help is greatly appreciated. Thanks, Kalyan -- realtek gigabit ethernet not recognised on feisty https://bugs.launchpad.net/bugs/79626 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79626] Re: realtek gigabit ethernet not recognised on feisty
Just installed the BETA FEISTY version on my lappy. To my big surprise the ETH0 is not being recognised. Which worked flawlesly in Edgy and Dapper. This lappy uses the R8169 chispet for its NIC and when doing lsmod the 'r8169' module is loaded but nothing is using it. 'ifup eth0' reports that ETH0 is unknown. But 'ifconfig up eth0' brings the ethernet online. But the problem is that I must do this everytime I restart Feisty in order to have internet conectivity. I already tried inserting this into '/etc/network/interface' 'auto eth0 iface eth0 inet dhcp' and then restarting the network but I get an error that ETH0 does not exist. -- realtek gigabit ethernet not recognised on feisty https://bugs.launchpad.net/bugs/79626 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79626] Re: realtek gigabit ethernet not recognised on feisty
Confirmed bugs need to be assigned to ubuntu-kernel-team. ** Changed in: linux-source-2.6.20 (Ubuntu) Assignee: Kyle McMartin = Ubuntu Kernel Team -- realtek gigabit ethernet not recognised on feisty https://launchpad.net/bugs/79626 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79626] Re: realtek gigabit ethernet not recognised on feisty
There've been some patches to add support to r8169 for more chipsets, I'll try to get these included for you to test. Alternately, I can try to bring back the r1000.ko module. -- realtek gigabit ethernet not recognised on feisty https://launchpad.net/bugs/79626 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79626] Re: realtek gigabit ethernet not recognised on feisty
Please attach the output of lsmod from the working edgy instalation, so we can see which module is loaded. Plain text is fine. You can run the following command: lsmod ~/lsmod.edgy and attach the lsmod.edgy file in your home directory to this bug directly. Cheers, Kyle -- realtek gigabit ethernet not recognised on feisty https://launchpad.net/bugs/79626 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79626] Re: realtek gigabit ethernet not recognised on feisty
Please attach the output of lsmod from the working edgy instalation, so we can see which module is loaded. Actually I already did this... and the output is (starting on page 7) in the document I already uploaded in my previous comment. Anyway...in case something has changed in the last couple of days, I pasted the output of lsmod again, but this time not in document but as plain text in this comment. Module Size Used by nls_cp437 6912 1 isofs 38076 1 udf89348 0 rfcomm 42260 0 l2cap 27136 5 rfcomm bluetooth 53476 4 rfcomm,l2cap speedstep_centrino 9760 1 cpufreq_userspace 5408 0 cpufreq_stats 7744 0 freq_table 6048 2 speedstep_centrino,cpufreq_stats cpufreq_powersave 2944 0 cpufreq_ondemand8876 2 cpufreq_conservative 8712 0 video 17540 0 tc1100_wmi 8324 0 sony_acpi 6412 0 sbs16804 0 pcc_acpi 14080 0 i2c_ec 6272 1 sbs hotkey 11556 0 dev_acpi 12292 0 container 5632 0 button 7952 0 battery11652 0 asus_acpi 17688 0 ac 6788 0 ipv6 272288 10 lp 12964 0 af_packet 24584 2 tsdev 9152 0 nvidia 4554836 12 snd_hda_intel 20116 3 snd_hda_codec 164608 1 snd_hda_intel usbhid 45152 0 i2c_core 23424 2 i2c_ec,nvidia sg 37404 0 r1000 17792 0 psmouse41352 0 snd_pcm_oss47360 0 snd_mixer_oss 19584 1 snd_pcm_oss snd_pcm84612 4 snd_hda_intel,snd_hda_codec,snd_pcm_oss snd_timer 25348 2 snd_pcm snd58372 10 snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_mix er_oss,snd_pcm,snd_timer parport_pc 37796 1 soundcore 11232 1 snd snd_page_alloc 11400 2 snd_hda_intel,snd_pcm parport39496 2 lp,parport_pc serio_raw 8452 0 hw_random 7320 0 shpchp 42144 0 pci_hotplug32828 1 shpchp floppy 63044 0 evdev 11392 1 intel_agp 26012 1 agpgart34888 2 nvidia,intel_agp pcspkr 4352 0 ext3 142728 2 jbd62228 1 ext3 uhci_hcd 24968 0 ehci_hcd 34696 0 usbcore 134912 4 usbhid,uhci_hcd,ehci_hcd ide_generic 2432 0 ide_cd 33696 1 cdrom 38944 1 ide_cd jmicron 5504 0 [permanent] ahci 20356 0 sd_mod 22656 4 generic 6276 0 ata_piix 11780 3 libata 74892 2 ahci,ata_piix scsi_mod 144648 4 sg,ahci,sd_mod,libata thermal15624 0 processor 31560 2 speedstep_centrino,thermal fan 6020 0 fbcon 41504 0 tileblit3840 1 fbcon font9344 1 fbcon bitblit 7168 1 fbcon softcursor 3328 1 bitblit vesafb 9244 0 capability 5896 0 commoncap 8704 1 capability -- realtek gigabit ethernet not recognised on feisty https://launchpad.net/bugs/79626 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79626] Re: realtek gigabit ethernet not recognised on feisty
Please attach the output of lsmod from the working edgy instalation, so we can see which module is loaded. Actually I already did this... and the output is (starting on page 7) in the document I already uploaded in my previous comment. Anyway...in case something has changed in the last couple of days, I pasted the output of lsmod again, but this time not in document but as plain text in this comment. Module Size Used by nls_cp437 6912 1 isofs 38076 1 udf89348 0 rfcomm 42260 0 l2cap 27136 5 rfcomm bluetooth 53476 4 rfcomm,l2cap speedstep_centrino 9760 1 cpufreq_userspace 5408 0 cpufreq_stats 7744 0 freq_table 6048 2 speedstep_centrino,cpufreq_stats cpufreq_powersave 2944 0 cpufreq_ondemand8876 2 cpufreq_conservative 8712 0 video 17540 0 tc1100_wmi 8324 0 sony_acpi 6412 0 sbs16804 0 pcc_acpi 14080 0 i2c_ec 6272 1 sbs hotkey 11556 0 dev_acpi 12292 0 container 5632 0 button 7952 0 battery11652 0 asus_acpi 17688 0 ac 6788 0 ipv6 272288 10 lp 12964 0 af_packet 24584 2 tsdev 9152 0 nvidia 4554836 12 snd_hda_intel 20116 3 snd_hda_codec 164608 1 snd_hda_intel usbhid 45152 0 i2c_core 23424 2 i2c_ec,nvidia sg 37404 0 r1000 17792 0 psmouse41352 0 snd_pcm_oss47360 0 snd_mixer_oss 19584 1 snd_pcm_oss snd_pcm84612 4 snd_hda_intel,snd_hda_codec,snd_pcm_oss snd_timer 25348 2 snd_pcm snd58372 10 snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_mix er_oss,snd_pcm,snd_timer parport_pc 37796 1 soundcore 11232 1 snd snd_page_alloc 11400 2 snd_hda_intel,snd_pcm parport39496 2 lp,parport_pc serio_raw 8452 0 hw_random 7320 0 shpchp 42144 0 pci_hotplug32828 1 shpchp floppy 63044 0 evdev 11392 1 intel_agp 26012 1 agpgart34888 2 nvidia,intel_agp pcspkr 4352 0 ext3 142728 2 jbd62228 1 ext3 uhci_hcd 24968 0 ehci_hcd 34696 0 usbcore 134912 4 usbhid,uhci_hcd,ehci_hcd ide_generic 2432 0 ide_cd 33696 1 cdrom 38944 1 ide_cd jmicron 5504 0 [permanent] ahci 20356 0 sd_mod 22656 4 generic 6276 0 ata_piix 11780 3 libata 74892 2 ahci,ata_piix scsi_mod 144648 4 sg,ahci,sd_mod,libata thermal15624 0 processor 31560 2 speedstep_centrino,thermal fan 6020 0 fbcon 41504 0 tileblit3840 1 fbcon font9344 1 fbcon bitblit 7168 1 fbcon softcursor 3328 1 bitblit vesafb 9244 0 capability 5896 0 commoncap 8704 1 capability -- realtek gigabit ethernet not recognised on feisty https://launchpad.net/bugs/79626 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79626] Re: realtek gigabit ethernet not recognised on feisty
Ok, so it is r1000. Thanks. -- realtek gigabit ethernet not recognised on feisty https://launchpad.net/bugs/79626 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79626] Re: realtek gigabit ethernet not recognised on feisty
Sigh, apparently they've reused PCI device Ids for incompatible products. Nasty. Please attach the output of sudo lspci -vvv and sudo lspci -vvxxx to the bug report as plain text attachments, hopefully we can figure out what needs to change in the r8169 driver. -- realtek gigabit ethernet not recognised on feisty https://launchpad.net/bugs/79626 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79626] Re: realtek gigabit ethernet not recognised on feisty
Wow that is really good, if you can conclude anything from this piece of data. Anyway... here is the other data you requested. sudo lspci -vvv gives me the following output: 00:00.0 Host bridge: Intel Corporation Memory Controller Hub (rev 02) Subsystem: ASUSTeK Computer Inc. Unknown device 81ea Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- Latency: 0 Capabilities: [e0] Vendor Specific Information 00:01.0 PCI bridge: Intel Corporation PCI Express Root Port (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 0, Cache Line Size: 32 bytes Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 9000-9fff Memory behind bridge: fa80-fe8f Prefetchable memory behind bridge: bfe0-dfd0 Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR+ NoISA- VGA+ MAbort- Reset- FastB2B- Capabilities: [88] #0d [] Capabilities: [80] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot +,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [90] Message Signalled Interrupts: 64bit- Queue=0/0 Enable + Address: fee0 Data: 40c1 Capabilities: [a0] Express Root Port (Slot+) IRQ 0 Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag- Device: Latency L0s 64ns, L1 1us Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported- Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- Device: MaxPayload 128 bytes, MaxReadReq 128 bytes Link: Supported Speed 2.5Gb/s, Width x16, ASPM L0s, Port 2 Link: Latency L0s 256ns, L1 4us Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch- Link: Speed 2.5Gb/s, Width x16 Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd- HotPlug- Surpise- Slot: Number 0, PowerLimit 0.00 Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- Slot: AttnInd Off, PwrInd On, Power- Root: Correctable- Non-Fatal- Fatal- PME- 00:1a.0 USB Controller: Intel Corporation USB UHCI Controller #4 (rev 02) (prog- if 00 [UHCI]) Subsystem: ASUSTeK Computer Inc. Unknown device 81ec Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- SERR- FastB2B- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort - MAbort- SERR- PERR- Latency: 0 Interrupt: pin A routed to IRQ 169 Region 4: I/O ports at dc00 [size=32] 00:1a.1 USB Controller: Intel Corporation USB UHCI Controller #5 (rev 02) (prog- if 00 [UHCI]) Subsystem: ASUSTeK Computer Inc. Unknown device 81ec Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- SERR- FastB2B- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort - MAbort- SERR- PERR- Latency: 0 Interrupt: pin B routed to IRQ 225 Region 4: I/O ports at e000 [size=32] 00:1a.7 USB Controller: Intel Corporation USB2 EHCI Controller #2 (rev 02) (prog -if 20 [EHCI]) Subsystem: ASUSTeK Computer Inc. Unknown device 81ec Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort - MAbort- SERR- PERR- Latency: 0 Interrupt: pin C routed to IRQ 50 Region 0: Memory at febffc00 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3h ot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Debug port 00:1b.0 Audio device: Intel Corporation HD Audio Controller (rev 02) Subsystem: ASUSTeK Computer Inc. Unknown device 81ec Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 0, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 58 Region 0: Memory at febf8000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3ho t+,D3cold+)
[Bug 79626] Re: realtek gigabit ethernet not recognised on feisty
sudo lspci -vvxxx turns the following output on my screen: (however all the results I just posted of sudo lspci -vvxxx, lsmod and lspci -vvv were performed on a functioning Edgy computer, while the problem was in Feisty but I already mentioned that before so I think the data is still valuable then. Just making sure you guys know... 00:1c.3 PCI bridge: Intel Corporation PCI Express Port 4 (rev 02) (prog-if 00 [N ormal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 0, Cache Line Size: 32 bytes Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 I/O behind bridge: b000-bfff Memory behind bridge: fea0-feaf Prefetchable memory behind bridge: fff0- Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- Reset- FastB2B- Capabilities: [40] Express Root Port (Slot+) IRQ 0 Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag- Device: Latency L0s unlimited, L1 unlimited Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported- Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- Device: MaxPayload 128 bytes, MaxReadReq 128 bytes Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 4 Link: Latency L0s 256ns, L1 4us Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch- Link: Speed 2.5Gb/s, Width x1 Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd- HotPlug+ Surpise+ Slot: Number 0, PowerLimit 0.00 Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- Slot: AttnInd Unknown, PwrInd Unknown, Power- Root: Correctable- Non-Fatal- Fatal- PME- Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0 Enable + Address: fee0 Data: 40d1 Capabilities: [90] #0d [] Capabilities: [a0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot +,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:1c.4 PCI bridge: Intel Corporation PCI Express Port 5 (rev 02) (prog-if 00 [N ormal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 0, Cache Line Size: 32 bytes Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: a000-afff Memory behind bridge: fe90-fe9f Prefetchable memory behind bridge: fff0- Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- Reset- FastB2B- Capabilities: [40] Express Root Port (Slot+) IRQ 0 Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag- Device: Latency L0s unlimited, L1 unlimited Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported- Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- Device: MaxPayload 128 bytes, MaxReadReq 128 bytes Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 5 Link: Latency L0s 256ns, L1 4us Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch- Link: Speed 2.5Gb/s, Width x1 Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd- HotPlug+ Surpise+ Slot: Number 0, PowerLimit 0.00 Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- Slot: AttnInd Unknown, PwrInd Unknown, Power- Root: Correctable- Non-Fatal- Fatal- PME- Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0 Enable + Address: fee0 Data: 40d9 Capabilities: [90] #0d [] Capabilities: [a0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot +,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00:1d.0 USB Controller: Intel Corporation USB UHCI Controller #1 (rev 02) (prog- if 00 [UHCI]) Subsystem: ASUSTeK Computer Inc. Unknown device 81ec Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- SERR- FastB2B- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort - MAbort- SERR- PERR- Latency: 0 Interrupt: pin A routed to IRQ 233 Region 4: I/O ports at d480
[Bug 79626] Re: realtek gigabit ethernet not recognised on feisty
Ok I typed in lspci -vvn, lsmod, and dmesg, and there is a lot of output, so I decided to put all the content in a text file. As I'm not that technical I really don't know what i'm talking about, so maybe I have put too much output in it (it's 18 pages long), but I really didn't know if I could skip some pieces. I think it's valuable to state that the eth0 port is recognized in Edgy but not in Feisty, all these commands are typed into a working Edgy terminal, as I formatted my Feisty partitions. How can I check whether the r1000 module is loaded? As I already said, I'm not that technical, but if I can help, I'm glad to do so. ** Attachment added: all the output of these three commands under Edgy http://librarian.launchpad.net/6139212/results%20%22lspci%20-vvn%22%2C%20%22lsmod%22%2C%20and%20%22dmesg%22.odt -- realtek gigabit ethernet not recognised on feisty https://launchpad.net/bugs/79626 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79626] Re: realtek gigabit ethernet not recognised on feisty
Also, can you recall which module is loaded in edgy for this card? Was it the r1000 module? -- realtek gigabit ethernet not recognised on feisty https://launchpad.net/bugs/79626 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
