Page: 1, 2, 3, 4  Next

Wired networking not working with Liquorix 3.5 variants
lithium17
Status: Curious
Joined: 08 Sep 2012
Posts: 5
Reply Quote
Hello.
I have been using liquorix kernel for a long time, but today is my first problem.
After installing 3.5.0-3.dmz.3-liquorix-686 version (future repo), I have lost my wired internet.

My old desktop has no wifi, so I have no means of going online and have reverted to the older 3.4.0-9.dmz.4-liquorix-686 kernel.

Please advise.

lspci:
:: Code ::
00:00.0 Host bridge: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller (rev 10)
00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 10)
00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 01)
00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1 (rev 01)
00:1d.0 USB controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 (rev 01)
00:1d.1 USB controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 (rev 01)
00:1d.2 USB controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 (rev 01)
00:1d.3 USB controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 (rev 01)
00:1d.7 USB controller: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge (rev 01)
00:1f.2 IDE interface: Intel Corporation N10/ICH7 Family SATA Controller [IDE mode] (rev 01)
00:1f.3 SMBus: Intel Corporation N10/ICH 7 Family SMBus Controller (rev 01)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 01)
05:00.0 Communication controller: Conexant Systems, Inc. HSF 56k Data/Fax Modem


lshw:
:: Code ::
*-network
                description: Ethernet interface
                product: RTL8101E/RTL8102E PCI Express Fast Ethernet controller
                vendor: Realtek Semiconductor Co., Ltd.
                physical id: 0
                bus info: pci@0000:01:00.0
                logical name: eth0
                version: 01
                serial: 00:21:85:65:fe:ac
                size: 100Mbit/s
                capacity: 100Mbit/s
                width: 64 bits
                clock: 33MHz
                capabilities: bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
                configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full ip=192.168.0.103 latency=0 multicast=yes port=MII speed=100Mbit/s
                resources: irq:41 ioport:de00(size=256) memory:fdbff000-fdbfffff memory:fdc00000-fdc1ffff


Thank you for your time.
Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 1122
Reply Quote
Can you provide the output of inxi -bxx? Instructions to get inxi are available here: smxi.org/site/install.htm#inxi.
Back to top
inxi
lithium17
Status: Curious
Joined: 08 Sep 2012
Posts: 5
Reply Quote
Hello dmz,

Here is the output of "inxi -bxx". Note that I issued this while running 3.4.0-9.dmz.4. Do you need me to run it with kernel 3.5.0-x as well?l

:: Code ::
System:    Host: sid Kernel: 3.4.0-9.dmz.4-liquorix-686 i686 (32 bit, gcc: 4.6.3)
           Desktop: N/A dm: gdm Distro: aptosid 2010-02 Κῆρες - xfce - (201009132215)
Machine:   System: HP-Pavilion product: FK880AA-AB4 g3560d Chassis: Hewlett-Packard type: 3
           Mobo: MSI model: Boston version: 1.0 Bios: Phoenix version: 5.13 date: 08/19/2008
CPU:       Dual core Intel Pentium Dual CPU E2180 (-MCP-) clocked at 1200.00 MHz
Graphics:  Card: Intel 82G33/G31 Express Integrated Graphics Controller bus-ID: 00:02.0
           X.Org: 1.12.3.902 drivers: intel (unloaded: fbdev,vesa) Resolution: 1440x900@59.9hz
           GLX Renderer: Mesa DRI Intel G33 x86/MMX/SSE2 GLX Version: 1.4 Mesa 8.0.4
           Direct Rendering: Yes
Network:   Card: Realtek RTL8101E/RTL8102E PCI Express Fast Ethernet controller
           driver: r8169 ver: 2.3LK-NAPI port: de00 bus-ID: 01:00.0
Drives:    HDD Total Size: 160.0GB (59.8% used)
Info:      Processes: 105 Uptime: 4 days Memory: 419.4/2014.0MB Runlevel: 5 Gcc sys: 4.7.1 alt:
           4.4/4.5/4.6
           Client: Shell inxi: 1.8.14

Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 1122
Reply Quote
Maybe the version of r8169 in Debian is incompatible with Linux 3.5. What happens when you try modprobe r8168 while logged booted to 3.5? That might get you your ethernet access back - and if so, you may want to purge r8168-dkms.
Back to top
lithium17
Status: Curious
Joined: 08 Sep 2012
Posts: 5
Reply Quote
Well, it works fine with aptosid's 3.5-slh kernels, so I figured it was an issue with liquorix/zen kernels. I will check later when I reboot to 3.5
Back to top
lithium17
Status: Curious
Joined: 08 Sep 2012
Posts: 5
Reply Quote
Just tried modprobe r8168 & modprobe r8169 while running 3.5.0-3-dmz.3-liquorix-686. Does not work, sadly.

Just confirmed that networking works with 3.5-3.slh.3-aptosid-686.

Seems like I can only use up to 3.4 liquorix for the time being (maybe permanently).
Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 1122
Reply Quote
Do you have the r8168-dkms package installed? Try installing that to get realtek's out-of-tree ethernet driver installed.


Although I also have a computer here compatible with this module, the open source r8168 driver works on my local machine. It's strange to me that yours doesn't work. I compared the configuration between slh's and mine, and they're identical for Realtek. Maybe you can check dmesg to see if you're missing any necessary firmware?
Back to top
lithium17
Status: Curious
Joined: 08 Sep 2012
Posts: 5
Reply Quote
:: damentz wrote ::
Do you have the r8168-dkms package installed? Try installing that to get realtek's out-of-tree ethernet driver installed.


Although I also have a computer here compatible with this module, the open source r8168 driver works on my local machine. It's strange to me that yours doesn't work. I compared the configuration between slh's and mine, and they're identical for Realtek. Maybe you can check dmesg to see if you're missing any necessary firmware?

That might be because mine, according to inxi output pasted above is r8169, not 8168. Tried r8168-dkms anyway and and got messages I don't understand, but it seemed to install. But networking didn't work after reboot, modprobe wasn't affective also. Worse, installing dkms made me lose wired networking with all kernels.

Since I'm not experienced enough with linux, I removed dkms and r8168-dkms and rebooted and got back wired internet, thankfully. I'm not going to mess with the system anymore and will settle for vanilla or slh kernels since I cannot risk not having internet. Somehow, this dkms escapade now seems to prevent even new slh kernels from being suggested during dist-upgrade, so it must have tweaked some kind of apt preferences as well, which now adds an extra step of inconvenience for me.

I'm grateful for your help but think I will stop using liquorix and settle for something that just works out of the box (that is why I started using Debian), which in this scenario are vanilla and aptosid kernels. I don't want to touch dkms stuff again. Dkms is beyond my ability and I'm too scared.

Thank you, sincerely.
Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 4127
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
Just wanted to confirm this issue, realtek 8169 driver fails to operate on 3.5 liquorix on my system:

:: Code ::
Network:   Card: Realtek RTL8111/8168B PCI Express Gigabit Ethernet controller
           driver: r8169 ver: 2.3LK-NAPI port: c800 bus-ID: 01:00.0
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>


A few other oddities, I just noticed that yesterday or the day before, the driver was reporting only 100mb connection speed, today, having changed nothing, it reports the correct 1000 mb.

dmesg reports that r8169 has loaded, on boot, there is a noticeable lag when networking starts, you can see the startup output hang there. It also reports ifup for eth0 worked, so clearly as far as the system is concerned, the driver loaded fine, and networking started fine, only it does not work.

No errors in dmesg that I can see, unless I missed it, I've saved dmesg from that boot to see.

Using 3.4 liquorix for now until issue is resolved.
Back to top
arclance
Status: Interested
Joined: 26 May 2012
Posts: 41
Reply Quote
Could the problems with the r8169 kernel driver with 3.5.0-4 be due to the problem reported in this bug report?
bugs.debian.org/cgi-bin/bugreport.cgi?bug=687927
I saw the missing firmware message when I installed 3.5.0-4 though my ethernet card that uses r8169 still works.
:: Code ::
           *-network
                description: Ethernet interface
                product: RTL8111/8168B PCI Express Gigabit Ethernet controller
                vendor: Realtek Semiconductor Co., Ltd.
                physical id: 0
                bus info: pci@0000:07:00.0
                logical name: eth0
                version: 06
                serial: SERIAL_NUMBER
                size: 1Gbit/s
                capacity: 1Gbit/s
                width: 64 bits
                clock: 33MHz
                capabilities: bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
                configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl8168e-3_0.0.4 03/27/12 ip=INT_IP latency=0 multicast=yes port=MII speed=1Gbit/s
It think it still works because it does not use the missing firmware.
Back to top
Display posts from previous:   
Page: 1, 2, 3, 4  Next
All times are GMT - 8 Hours