Author Topic: [SOLVED] The KDE 4.5 Ethernet problem that was not  (Read 1217 times)

Offline jlf001

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 519
[SOLVED] The KDE 4.5 Ethernet problem that was not
« on: August 15, 2010, 02:24:29 PM »
I'm unable to connect any of my laptops hardwired since the KDE 4.5 update.  Wireless works fine.  Any ideas?

Jeff
« Last Edit: August 18, 2010, 03:08:48 PM by jlf001 »

Offline jlf001

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 519
Re: KDE 4.5 Ethernet problem
« Reply #1 on: August 17, 2010, 03:17:41 PM »
Am I the only one with this problem?  I have four laptops that won't connect hardwired.  My only desktop, with KDE 4.5, works fine works fine hardwired.

Jeff

P.S.  I hate the say this, but two of these laptops still have Windose and they work hardwired or wireless.
« Last Edit: August 17, 2010, 03:23:45 PM by jlf001 »

Offline ElCuervo

  • Hero Member
  • *****
  • Posts: 4148
  • I'm walking on sunshine!
Re: KDE 4.5 Ethernet problem
« Reply #2 on: August 17, 2010, 03:35:34 PM »
Quote
Am I the only one with this problem?
It could be that your lack of responses is due to your lack of details regarding the steps you have taken to rectify the problem.

Have you gone through PCC>Network & Internet>Set up connection? If that doesn't work, open a terminal and give us the result of ifconfig.
"If there were no change, there would be no butterflies" - Walt Disney

http://linuxcounter.net/cert/433721.png

Offline muungwana

  • Hero Member
  • *****
  • Posts: 6232
Re: KDE 4.5 Ethernet problem
« Reply #3 on: August 17, 2010, 04:09:39 PM »

network management in pclinuxos is completely independent of any desktop environment. The problem is most likely not caused by kde.

do you have a connection tray icon on your tray area? how do you change connection from wireless to wired?
.. 3 things are certain in life : death, taxes and software bloat ..
.. tell me something i don't know, something i can use as i struggle to reason with the world around me ..

Offline jlf001

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 519
Re: KDE 4.5 Ethernet problem
« Reply #4 on: August 17, 2010, 04:19:45 PM »
On this particular laptop, a Dell E1705, I've already tried using the setup connection and get the following error.  "Unable to find network interface using b44 driver"

Here are the results of ifconfig and lspci:

[jlf@localhost ~]$ ifconfig
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:10 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:500 (500.0 b)  TX bytes:500 (500.0 b)

wlan0  Link encap:Ethernet  HWaddr 00:18:DE:9B:6B:96  
          inet addr:xxx.xxx.x.xx  Bcast:xxx.xxx.x.xxx  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:973 errors:0 dropped:0 overruns:0 frame:0
          TX packets:550 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:246846 (241.0 KiB)  TX bytes:86146 (84.1 KiB)

[jlf@localhost ~]$ lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03)
00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express PCI Express Root Port (rev 03)
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:1c.1 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 2 (rev 01)
00:1c.3 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 4 (rev 01)
00:1d.0 USB Controller: Intel Corporation N10/ICH7 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 Mobile PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 01)
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 01)
00:1f.3 SMBus: Intel Corporation N10/ICH 7 Family SMBus Controller (rev 01)
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility X1400
03:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)
03:01.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller
03:01.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19)
03:01.2 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 0a)
03:01.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 05)
03:01.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev ff)
0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)

I never had a problem until I upgraded from KDE 4.46 to KDE 4.50

Jeff
« Last Edit: August 17, 2010, 04:24:44 PM by jlf001 »

Offline jlf001

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 519
Re: KDE 4.5 Ethernet problem
« Reply #5 on: August 17, 2010, 04:30:44 PM »

network management in pclinuxos is completely independent of any desktop environment. The problem is most likely not caused by kde.

do you have a connection tray icon on your tray area? how do you change connection from wireless to wired?

Yes I've got a tray icon.  I usually, turn off the wireless connection first and the plug in the Ethernet cable.  I've even tried disabling the wifi card and booting with the cable plugged in.  Still no luck.

Jeff 

Offline muungwana

  • Hero Member
  • *****
  • Posts: 6232
Re: KDE 4.5 Ethernet problem
« Reply #6 on: August 17, 2010, 04:42:14 PM »

you have a broadcomm wired interface and you are using a b44 driver and the problem is most likely due to a problem with this driver

are all 4 laptops from the same manufacturer and all started showing the same problem after you update to kde 4.5 and all show the same error msg when trying to set up a new connection in pcc?

what kernel are you using? you can find out about what kernel you are using by opening the terminal and type "uname -r"
.. 3 things are certain in life : death, taxes and software bloat ..
.. tell me something i don't know, something i can use as i struggle to reason with the world around me ..

Offline jlf001

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 519
Re: KDE 4.5 Ethernet problem
« Reply #7 on: August 17, 2010, 05:38:26 PM »

you have a broadcomm wired interface and you are using a b44 driver and the problem is most likely due to a problem with this driver

are all 4 laptops from the same manufacturer and all started showing the same problem after you update to kde 4.5 and all show the same error msg when trying to set up a new connection in pcc?

what kernel are you using? you can find out about what kernel you are using by opening the terminal and type "uname -r"

I initially thought it was a kernel problem, so I went back to 2.6.32.17 (I'm currently running 2.6.33.7), however I had the same problems. As for the laptops, the three Dell's have broadcom interfaces and the ACER has an Atheros interface.  And yes, all worked fine prior to KDE 4.5.  By the way, the desktop that's hardwired has a Realtek interface in it and no wireless card.  Could this be some type of a switching problem on the laptops?  They all show wifi as the Default connection under Network Monitoring and I haven't been able to change that.

Jeff

Offline muungwana

  • Hero Member
  • *****
  • Posts: 6232
Re: KDE 4.5 Ethernet problem
« Reply #8 on: August 17, 2010, 06:33:45 PM »

can you go to pcc->hardware->browse and configure hardware->ethernetcards and then try to (re)set your card driver?

you have a strange problem. Most people do not experience connectivity problem from the wired interface.
.. 3 things are certain in life : death, taxes and software bloat ..
.. tell me something i don't know, something i can use as i struggle to reason with the world around me ..

Offline jlf001

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 519
Re: KDE 4.5 Ethernet problem
« Reply #9 on: August 17, 2010, 07:04:54 PM »

can you go to pcc->hardware->browse and configure hardware->ethernetcards and then try to (re)set your card driver?

you have a strange problem. Most people do not experience connectivity problem from the wired interface.

Been there, done that and no luck.  Is there a .conf file that I can delete to start over again without wifi or ethernet configured?  I might have this laptop totally messed up by now.  I'm going to disconnect the wifi card and see what happens when I boot back up hardwired.

Jeff
« Last Edit: August 17, 2010, 07:24:57 PM by jlf001 »

Offline muungwana

  • Hero Member
  • *****
  • Posts: 6232
Re: KDE 4.5 Ethernet problem
« Reply #10 on: August 17, 2010, 07:26:54 PM »

try this:
unplug the wired cable and then go to pcc and delete all network connections then delete "/etc/udev/rules.d/70-persistent-net.rules" text file and then restart. Only root can delete this text file hence open a file manager with root privileges before you go there.

When the system is up,plug in the wired cable and then go to pcc and then try to create a new connection. When you are done, open the terminal and then log in as root and then type this command and paste its content here.

cat /var/log/syslog | tail -n 100

.. 3 things are certain in life : death, taxes and software bloat ..
.. tell me something i don't know, something i can use as i struggle to reason with the world around me ..

Offline jlf001

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 519
Re: KDE 4.5 Ethernet problem
« Reply #11 on: August 17, 2010, 08:23:47 PM »

try this:
unplug the wired cable and then go to pcc and delete all network connections then delete "/etc/udev/rules.d/70-persistent-net.rules" text file and then restart. Only root can delete this text file hence open a file manager with root privileges before you go there.

When the system is up,plug in the wired cable and then go to pcc and then try to create a new connection. When you are done, open the terminal and then log in as root and then type this command and paste its content here.

cat /var/log/syslog | tail -n 100



Deleting the 70-persistent-net.rules reset everything and this time, I did not get the b44 driver error.  However, still no hardwired connection.  Here's the results of the command you had me run:

[root@localhost ~]# cat /var/log/syslog | tail -n 100
Aug 17 21:59:53 localhost klogd: CPU1 attaching sched-domain:
Aug 17 21:59:53 localhost klogd:  domain 0: span 0-1 level MC
Aug 17 21:59:53 localhost klogd:   groups: 1 0
Aug 17 21:59:54 localhost klogd: xt_time: kernel timezone is -0400
Aug 17 21:59:54 localhost hald: mounted /dev/mmcblk0p1 on behalf of uid 500
Aug 17 21:59:55 localhost klogd: u32 classifier
Aug 17 21:59:55 localhost klogd:     Actions configured
Aug 17 21:59:55 localhost klogd: netfilter PSD loaded - (c) astaro AG
Aug 17 21:59:55 localhost klogd: IFWLOG: register target
Aug 17 21:59:55 localhost logger: Shorewall started
Aug 17 21:59:55 localhost ntpd_initres[3529]: host name not found EAI_NODATA: pool.ntp.org
Aug 17 21:59:55 localhost klogd: usbcore: registered new interface driver snd-usb-audio
Aug 17 22:00:17 localhost net_applet[3811]: ### Program is starting ###
Aug 17 22:00:26 localhost rtkit-daemon[3872]: Sucessfully called chroot.
Aug 17 22:00:26 localhost rtkit-daemon[3872]: Sucessfully dropped privileges.
Aug 17 22:00:26 localhost rtkit-daemon[3872]: Sucessfully limited resources.
Aug 17 22:00:26 localhost rtkit-daemon[3872]: Running.
Aug 17 22:00:26 localhost rtkit-daemon[3872]: Canary thread running.
Aug 17 22:00:26 localhost rtkit-daemon[3872]: Watchdog thread running.
Aug 17 22:00:26 localhost polkitd[3876]: started daemon version 0.96 using authority implementation `local' version `0.96'
Aug 17 22:00:26 localhost rtkit-daemon[3872]: Sucessfully made thread 3870 of process 3870 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
Aug 17 22:00:26 localhost rtkit-daemon[3872]: Supervising 1 threads of 1 processes of 1 users.
Aug 17 22:00:27 localhost rtkit-daemon[3872]: Sucessfully made thread 3882 of process 3882 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11.
Aug 17 22:00:27 localhost rtkit-daemon[3872]: Supervising 2 threads of 2 processes of 1 users.
Aug 17 22:00:27 localhost pulseaudio[3882]: pid.c: Daemon already running.
Aug 17 22:00:49 localhost drakconf.real[3936]: ### Program is starting ###
Aug 17 22:00:54 localhost drakconf.real[3953]: ### Program is starting ###
Aug 17 22:00:57 localhost ntpd_initres[3529]: host name not found EAI_NODATA: pool.ntp.org
Aug 17 22:01:10 localhost draknetcenter[3998]: ### Program is starting ###
Aug 17 22:01:11 localhost klogd: iwl3945 0000:0c:00.0: firmware: requesting iwlwifi-3945-2.ucode
Aug 17 22:01:11 localhost klogd: iwl3945 0000:0c:00.0: loaded firmware version 15.32.2.9
Aug 17 22:01:11 localhost klogd: Registered led device: iwl-phy0::radio
Aug 17 22:01:11 localhost klogd: Registered led device: iwl-phy0::assoc
Aug 17 22:01:11 localhost klogd: Registered led device: iwl-phy0::RX
Aug 17 22:01:11 localhost klogd: Registered led device: iwl-phy0::TX
Aug 17 22:01:20 localhost draknetcenter[3998]: ### Program is exiting ###
Aug 17 22:01:24 localhost draknetcenter[4050]: ### Program is starting ###
Aug 17 22:02:01 localhost draknetcenter[4050]: running: /bin/rpm -q --qf %{name}  dhcp-client                                                               
Aug 17 22:02:02 localhost draknetcenter[4050]: adding alias eth0 to b44                                                                                     
Aug 17 22:02:02 localhost draknetcenter[4050]: adding alias pci:v000014E4d0000170Csv00001028sd000001CDbc02sc00i00 to b44
Aug 17 22:02:02 localhost draknetcenter[4050]: modified file /etc/sysconfig/network-scripts/ifcfg-eth0
Aug 17 22:02:02 localhost draknetcenter[4050]: modified file /etc/sysconfig/network-scripts/ifcfg-eth0
Aug 17 22:02:02 localhost draknetcenter[4050]: changed mode of /etc/sysconfig/network-scripts/ifcfg-eth0 to 755
Aug 17 22:02:02 localhost draknetcenter[4050]: written eth0 interface configuration in /etc/sysconfig/network-scripts/ifcfg-eth0
Aug 17 22:02:02 localhost draknetcenter[4050]: writing host information to /etc/hosts
Aug 17 22:02:02 localhost draknetcenter[4050]: created file /etc/hosts
Aug 17 22:02:02 localhost draknetcenter[4050]: writing host information to /etc/hosts
Aug 17 22:02:02 localhost draknetcenter[4050]: created file /etc/hosts
Aug 17 22:02:02 localhost draknetcenter[4050]: set sethostname to localhost.localdomain
Aug 17 22:02:02 localhost draknetcenter[4050]: running: /usr/bin/run-parts --arg localhost.localdomain /etc/sysconfig/network-scripts/hostname.d
Aug 17 22:02:02 localhost draknetcenter[4050]: modified file /etc/sysconfig/network
Aug 17 22:02:02 localhost draknetcenter[4050]: running: /lib/udev/write_net_rules f6:15:00:25:00:00
Aug 17 22:02:02 localhost draknetcenter[4050]: running: /lib/udev/write_net_rules 0a:00:27:00:00:00
Aug 17 22:02:02 localhost draknetcenter[4050]: modified file /etc/modprobe.conf
Aug 17 22:02:02 localhost draknetcenter[4050]: running: dmidecode
Aug 17 22:02:02 localhost draknetcenter[4050]: to put in /etc/modprobe.preload nvram, evdev, evdev
Aug 17 22:02:02 localhost draknetcenter[4050]: modified file /etc/modprobe.preload
Aug 17 22:02:05 localhost draknetcenter[4050]: running: /sbin/ifdown eth0 daemon
Aug 17 22:02:05 localhost ifplugd(eth0)[2821]: Exiting.
Aug 17 22:02:05 localhost klogd: b44: eth0: powering down PHY
Aug 17 22:02:05 localhost klogd: b44: eth0: BUG!  Timeout waiting for bit 00000002 of register 42c to clear.
Aug 17 22:02:05 localhost draknetcenter[4050]: running: /sbin/ifup eth0 daemon
Aug 17 22:02:05 localhost ifplugd(eth0)[4308]: ifplugd 0.28 initializing.
Aug 17 22:02:05 localhost klogd: b44: eth0: BUG!  Timeout waiting for bit 00000002 of register 42c to clear.
Aug 17 22:02:05 localhost ifplugd(eth0)[4308]: Using interface eth0/F6:15:00:25:00:00 with driver <b44> (version: 2.0)
Aug 17 22:02:05 localhost ifplugd(eth0)[4308]: Using detection mode: SIOCETHTOOL
Aug 17 22:02:05 localhost ifplugd(eth0)[4308]: Initialization complete, link beat not detected.
Aug 17 22:02:26 localhost drakconnect[4349]: ### Program is starting ###
Aug 17 22:02:43 localhost drakconnect[4395]: ### Program is starting ###
Aug 17 22:02:56 localhost drakconnect[4395]: running: /bin/rpm -q --qf %{name}  dhcp-client
Aug 17 22:02:56 localhost drakconnect[4395]: modified file /etc/sysconfig/network-scripts/ifcfg-eth0
Aug 17 22:02:56 localhost drakconnect[4395]: modified file /etc/sysconfig/network-scripts/ifcfg-eth0
Aug 17 22:02:56 localhost drakconnect[4395]: changed mode of /etc/sysconfig/network-scripts/ifcfg-eth0 to 755
Aug 17 22:02:56 localhost drakconnect[4395]: written eth0 interface configuration in /etc/sysconfig/network-scripts/ifcfg-eth0
Aug 17 22:02:56 localhost drakconnect[4395]: writing host information to /etc/hosts
Aug 17 22:02:56 localhost drakconnect[4395]: created file /etc/hosts
Aug 17 22:02:56 localhost drakconnect[4395]: writing host information to /etc/hosts
Aug 17 22:02:56 localhost drakconnect[4395]: created file /etc/hosts
Aug 17 22:02:56 localhost drakconnect[4395]: set sethostname to localhost.localdomain
Aug 17 22:02:56 localhost drakconnect[4395]: running: /usr/bin/run-parts --arg localhost.localdomain /etc/sysconfig/network-scripts/hostname.d
Aug 17 22:02:56 localhost drakconnect[4395]: modified file /etc/sysconfig/network
Aug 17 22:02:56 localhost drakconnect[4395]: running: /sbin/ifdown eth0 daemon
Aug 17 22:02:56 localhost ifplugd(eth0)[4308]: Exiting.
Aug 17 22:02:56 localhost klogd: b44: eth0: powering down PHY
Aug 17 22:02:56 localhost klogd: b44: eth0: BUG!  Timeout waiting for bit 00000002 of register 42c to clear.
Aug 17 22:02:56 localhost drakconnect[4395]: running: /sbin/ifup eth0 daemon
Aug 17 22:02:56 localhost ifplugd(eth0)[4553]: ifplugd 0.28 initializing.
Aug 17 22:02:56 localhost drakconnect[4395]: running: /etc/rc.d/init.d/network-up start
Aug 17 22:02:56 localhost klogd: b44: eth0: BUG!  Timeout waiting for bit 00000002 of register 42c to clear.
Aug 17 22:02:56 localhost ifplugd(eth0)[4553]: Using interface eth0/F6:15:00:25:00:00 with driver <b44> (version: 2.0)
Aug 17 22:02:56 localhost ifplugd(eth0)[4553]: Using detection mode: SIOCETHTOOL
Aug 17 22:02:56 localhost ifplugd(eth0)[4553]: Initialization complete, link beat not detected.
Aug 17 22:02:59 localhost ntpd_initres[3529]: host name not found EAI_NODATA: pool.ntp.org
Aug 17 22:03:11 localhost ntpd[3502]: synchronized to LOCAL(0), stratum 10
Aug 17 22:03:11 localhost ntpd[3502]: kernel time sync status change 0001
Aug 17 22:03:14 localhost drakconnect[4395]: modified file /etc/modprobe.conf
Aug 17 22:03:14 localhost drakconnect[4395]: running: dmidecode
Aug 17 22:03:14 localhost drakconnect[4395]: to put in /etc/modprobe.preload nvram, evdev, evdev
Aug 17 22:03:14 localhost drakconnect[4395]: modified file /etc/modprobe.preload
Aug 17 22:03:14 localhost drakconnect[4395]: ### Program is exiting ###

Offline muungwana

  • Hero Member
  • *****
  • Posts: 6232
Re: KDE 4.5 Ethernet problem
« Reply #12 on: August 17, 2010, 08:42:30 PM »
Aug 17 22:02:56 localhost klogd: b44: eth0: BUG!  Timeout waiting for bit 00000002 of register 42c to clear.

The above line is what makes this wired connection not working .. i just google it and i got a few hits and i am looking at a few of them.
.. 3 things are certain in life : death, taxes and software bloat ..
.. tell me something i don't know, something i can use as i struggle to reason with the world around me ..

Offline jlf001

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 519
Re: KDE 4.5 Ethernet problem
« Reply #13 on: August 17, 2010, 08:46:08 PM »
Just to add another thought.  I'm typing this hardwired from the livecd 2001-1.  Oh well, I dive into this again tomorrow.  Time for bed, I need to be up at 5:00 AM.  Thanks for your help so far.

Jeff

Offline muungwana

  • Hero Member
  • *****
  • Posts: 6232
Re: KDE 4.5 Ethernet problem
« Reply #14 on: August 17, 2010, 08:58:38 PM »

A bit of googling and this seem to be the best link from a few that showed up: https://bbs.archlinux.org/viewtopic.php?pid=803969

This person has the same card you have and is having the same problem and solved it by changing a kernel. Try all available kernels and hope atleast one will work. I cant seem to find any solution that didnt involve kernel change.
.. 3 things are certain in life : death, taxes and software bloat ..
.. tell me something i don't know, something i can use as i struggle to reason with the world around me ..