LinuxQuestions.org - [SOLVED] 14.1 problems after upgrade (keyboard & kde)

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - 14.1 problems after upgrade (keyboard & kde) (https://www.linuxquestions.org/questions/slackware-14/14-1-problems-after-upgrade-keyboard-and-kde-4175484176/)

14.1 problems after upgrade (keyboard & kde)

I've two pretty critical issues following upgrade of my work desktop to slackware64-14.1-multilib from slackware64-14.0-multilib.

No Keyboard prior to opening /
I have a LUKS system with all disks encrypted. Prior to opening the / FS my USB keyboard doesn't function. It was working fine previously. The module used is ehci-hcd and it is loaded along with {u,o,x}hci-hcd, usbhid and others.

The intriguing thing it it is listed as detected. In the buffer, around the same time as the LUKS passphrase prompt it does state that the logitech keyboard is detected, albeit with OHCI :-/ PS2 keyboard works, but then once / is loaded it is ehci not ohci in use.

Really confusing me.
No KWin
Worse still, once I'm in I had trouble compiling the kernel module for the nvidia blob. First complaining about a library not being a symlink (which was easily enough solved) and then complaining that a 32-bit mesa library has the wrong architecture (even though I've checked and it's right). I still managed to get it to compile a module, but the errors disturb me.

Problem is, once I log into KDE a lot isn't working. My profile was completely chuffed and I have no KWin! So I have a taskbar and can launch apps, but there's no window management.

I tried moving (IIRC) .kde, .config, .qt out of the way, but still not enough to make KWin load properly.

Would appreciate any information anyone has on either of these as I'm shortly going to run out of time to work on it and will be forced to revert to my 14.0 backup.

*UPDATE*
Seems having looked into the details, the keyboard IS actually in the OCHI port :-/ so makes sense to be detected as such on boot.

Going to try removing ehci and seeing what happens, and then perhaps trying to add a delay in the init.

Quote:

Originally Posted by zordrak (Post 5062371)

[*]No KWin
Worse still, once I'm in I had trouble compiling the kernel module for the nvidia blob. First complaining about a library not being a symlink (which was easily enough solved) and then complaining that a 32-bit mesa library has the wrong architecture (even though I've checked and it's right). I still managed to get it to compile a module, but the errors disturb me.

Problem is, once I log into KDE a lot isn't working. My profile was completely chuffed and I have no KWin! So I have a taskbar and can launch apps, but there's no window management.

I tried moving (IIRC) .kde, .config, .qt out of the way, but still not enough to make KWin load properly.[/LIST]
Would appreciate any information anyone has on either of these as I'm shortly going to run out of time to work on it and will be forced to revert to my 14.0 backup.

About that, see these posts:
http://www.linuxquestions.org/questi...ml#post5061573

http://www.linuxquestions.org/questi...ml#post5062158

http://www.linuxquestions.org/questi...ml#post5062342

Quote:

Originally Posted by brianL (Post 5062377)

About that, see these posts:
http://www.linuxquestions.org/questi...ml#post5061573

http://www.linuxquestions.org/questi...ml#post5062158

http://www.linuxquestions.org/questi...ml#post5062342

Thanks for that. does explain nvidia; though not sure it'll help me with KWin. Will put a known-working blob in and go from there.

Have now also tried a 10-second wait-for-root. No joy.

Have tried swapping between ehci and ohci controllers, no joy - except that replugging does show in the console; detecting the device and showing its details, just still it doesn't work.

Is there maybe some new driver I'm missing? I'm using hid and usbhid.. is there some new way of doing this?

No real idea how to help, but I can post what might be relevant from running lsmod:

Code:

usbhid                37080  0 

hid                    87523  2 hid_generic,usbhid

ohci_hcd              23924  0 

ehci_pci                3688  0 

ehci_hcd              39275  1 ehci_pci

I think I've realised what's going on with the e/ohci issue. I think the way it's picked up is that all the ports report into OHCI, but up to EHCI if they're detected as USB2 which this keyboard won't be. So it is OHCI I need here. But I more beginning to believe that it's not the specific hcd driver that's causing trouble because the device is being correctly detected, just not used.

As per your lsmod brianL and matching against mine, I may have found exactly the problem I was assuming existed: "hid_generic"

I have added this module and now it seems to be working!

So, on top of usb, usbhid and {x,o,u,e}hci-hcd - where the hell did hid_generic come from since the last slack kernel?

Quote:

Originally Posted by zordrak (Post 5062425)

where the hell did hid_generic come from since the last slack kernel?

Probably something to do with quantum physics - it just popped into existence from nothing. :)

Now to work out how to fix KDE. I imagine I've missed a dot-directory in making it start afresh. If only KDE was more tolerant of upgrades from old profile versions.

I did a fresh install, not an upgrade from 14.0. That could be why I'm not having any (fingers crossed) problems. :)

I would have, but I'm short on time to do this as I'm dealing with my main work desktop and I have SOO much that is extra or custom in terms of packages and such it seemed like a very long way around. I did a full backup I can revert to - obviously I would like to not! :)

Ok, not KDE's fault. Was nvidia's fault. 325.15 saved the day!

Had to watch out for two things though:
1. hplip system tray autostart O_o I have no HP printer, no idea why this would default.
2. KDE reset my activities from Desktop to Desktop Icons. No thanks KDE.