problems after last 12.3 update

Hello everybody.

On my Opensuse 12.3 I have performed the last on-line update. Everything seemed OK. No message, No problem, but only until the first reboot. Since that I am with LAN card not installed with the terrific message in Yast2 “Unable to configure the network card because the kernel device (eth0, wlan0) is not present. This is mostly caused by missing firmware (for wlan devices). See dmesg output for details.”

Moreover any USB key is not recognized when plugged in. The result is that I’m not able to transfer files out of the PC.

Any advice? Thank you in advance
Phil

Do you see any interface in “ifconfig -a” output?

So you have NO lan card right?

So what to you have? You say something about a USB device??

Hi. Thanks for the answer

ipconfig lists Local Loopback IP 127.0.0.1 only. No eth.

Please post output of


/sbin/lspci -nnk

and


lsusb

LAN card is installed in the PC, but not recognized by Suse.
USB keys work well at the boot (I would be able to boot an O.S. from a USB key), but no longer after Suse has been loaded: if I plug in a key, it is not recognized by the Suse.

Thanks

Impossible for me to copy the results.

Anyway lspci, among the others, lists USB Controller and the right type of Ethernet Adapter
susb lists 3 devices. One of this is the correct Logitech cordless receiver

Thanks

How about booting from a Live medium?

You could first generate the output like this:


echo "LSPCI:" > ~/forums_output.txt
/sbin/lspci -nnk >> ~/forums_output.txt
echo "LSUSB:" >> ~/forums_output.txt
lsusb >> ~/forums_output.txt 

This puts the output in a textfile in your homedir, named forums_output.txt

Next boot from the Live USB stick or CD, mount the partition where your /home resides, and open the textfile to post the contents here. That is, if the Live medium does work.

Apologies if I missed this in the replies to your post, … but did you check what this error message suggests to check ? ie did you check for the firmware ? Is there an appropriate entry in the ‘dmesg’ ? Please advise if you need help in knowing how to check for that ?

wrt being unable to copy files off of the PC, this is most unusual. Still, note for small entries showing on the screen, one can always take a picture with a digital camera of one’s display, and use a site such as ImageBam - free image hosting site to post and share the image.

Here they are.

As you can see, there’s no driver loaded for the Ethernet device. Could you check the BIOS if you see anything strange? Also see if Legacy USB is enabled.

Driver should be r8169 (and it does require external firmware):

filename:       /lib/modules/3.7.10-1.16-desktop/kernel/drivers/net/ethernet/realtek/r8169.ko
firmware:       rtl_nic/rtl8168g-1.fw
firmware:       rtl_nic/rtl8106e-1.fw
firmware:       rtl_nic/rtl8411-1.fw
firmware:       rtl_nic/rtl8402-1.fw
firmware:       rtl_nic/rtl8168f-2.fw
firmware:       rtl_nic/rtl8168f-1.fw
firmware:       rtl_nic/rtl8105e-1.fw
firmware:       rtl_nic/rtl8168e-3.fw
firmware:       rtl_nic/rtl8168e-2.fw
firmware:       rtl_nic/rtl8168e-1.fw
firmware:       rtl_nic/rtl8168d-2.fw
firmware:       rtl_nic/rtl8168d-1.fw
version:        2.3LK-NAPI
license:        GPL
description:    RealTek RTL-8169 Gigabit Ethernet driver
author:         Realtek and the Linux r8169 crew <netdev@vger.kernel.org>
srcversion:     581830050EFAE8E28042881
alias:          pci:v00000001d00008168sv*sd00002410bc*sc*i*
alias:          pci:v00001737d00001032sv*sd00000024bc*sc*i*
alias:          pci:v000016ECd00000116sv*sd*bc*sc*i*
alias:          pci:v00001259d0000C107sv*sd*bc*sc*i*
alias:          pci:v00001186d00004302sv*sd*bc*sc*i*
alias:          pci:v00001186d00004300sv*sd*bc*sc*i*
alias:          pci:v00001186d00004300sv00001186sd00004B10bc*sc*i*
alias:          pci:v000010ECd00008169sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008168sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008167sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008136sv*sd*bc*sc*i*
alias:          pci:v000010ECd00008129sv*sd*bc*sc*i*
depends:        
intree:         Y
vermagic:       3.7.10-1.16-desktop SMP preempt mod_unload modversions 
parm:           use_dac:Enable PCI DAC. Unsafe on 32 bit PCI slot. (int)
parm:           debug:Debug verbosity level (0=none, ..., 16=all) (int)

Does “modprobe r1869” work? Is there anything under /lib/firmware/rtl_nic?

On 2013-09-23 16:06, arvidjaar wrote:
>
> Driver should be r8169 (and it does require external firmware):

Wild guess:

The OP did an update, that is known. Guess 1: the update included a
kernel. Guess 2: the firmware comes in a different package, and it is
missing after the update.

Maybe? :-?


Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

modprobe r8169 says:
FATAL: Could not load /lib/modules/3.7.10-1.1-desktop/modules.dep: No such file or directory
In fact folder 3.7.10-1.1-desktop is not present. There are instead two other folders: 3.7.10-1.11-desktop and 3.7.10-1.16-desktop that both contains modules.dep file and many drivers including r8169.ko

Thanks

In /lib/firmware/rtl_nic there are 16 files beginning with rtl8105 or rtl8106 or rtl8168 or rtl8402 or rtl8411

Guess 1: Could be. I do not remember. Most probably, anyway.
Guess 2: I didn’t get any specific message before or after the update

Nothing appearing out of order. In fact USB works well before to load Suse and also after but only with USB keyboard. It seems to me that Suse does not perform the automount of the USB keys.

dmesg does not have anything strange. The only “not found” is in “PM: Image not found (code -22)”. USB is registered with keyboard recognized. There is nothing about eth0 or r8169.

About to copy file out of the PC, I meant not able to port files out since network, USB and also DVD driver do not work as usual.

I have tried to copy the folder 3.7.10-1.11-desktop to 3.7.10-1.1-desktop in /lib/modules. After reboot LAN card, USB keys and DVD driver work well as usual.
Now I’m wondering whether the system is stable in this way or not. Why there were two subfolders in /lib/modules with different version number? and why the one loaded is 3.7.10-1.1?

Thanks again

Aaargh. It may work now, or seem to work, but you broke the system, i.e. the folders containing the kernel modules now contain the modules of a different (not too much, but still) kernel.