[SOLVED] From Kernel 4.4.7 Back to 4.4.6 (USB Problems).

cwizardone · 04-15-2016, 08:54 PM

There is apparently some sort of conflict between the 4.4.7 kernel and the USB ports.

First, yes, my user name is in the proper group(s) and nothing has changed other than the installation of today's updates.

When lsusb is ran the devices are shown, but XSane cannot not find the scanner. What is worst is VirtualBox cannot see any of the USB ports. The setup in VirtualBox shows everything is in order, but it can't see the printer or the scanner.

As I've said before, XSane and the scanner don't get along and I've spent enough hours over the years trying to get a quality scan out of XSane it would probably add up to days if not weeks.
As the scanner is used almost daily, I setup winXP-sp3 in VirtualBox and run the HP scanning software from there and get excellent results. Works and has worked for years UNTIL a couple of hours ago when today's updates were installed.

To double check I booted over to winXp (dual boot) and fired up the same HP software. It found the scanner and worked perfectly.

So, the 4.4.6 kernel has been re-installed, the computer rebooted, and VirtualBox once again sees the USB ports and the scanner works there and with XSane in Slackware.

BTW, every time the kernel is changed it is necessary to un-install and then re-install VirtualBox, as was done twice this afternoon.

Any ideas would be appreciated.
Thanks.

rkelsen · 04-15-2016, 10:33 PM

Quote:

Originally Posted by cwizardone

BTW, every time the kernel is changed it is necessary to un-install and then re-install VirtualBox, as was done twice this afternoon.

You don't need to completely remove and reinstall Virtualbox... you just have to compile its modules for the new kernel:

Code:

# cd /usr/src/vboxhost-5.x.xx
# make install

Ztcoracat · 04-15-2016, 10:52 PM

Kernel regression maybe?
Maybe kernel 4.4.7 doesn't have support for usb yet? (anything's possible)

I've never had any issues with updates wrecking anything as long as I've been running Slackware.
I have had updates wreck things on other distributions but never Slackware.
Reading the change logs for kernel 4.4.7 may provide an answer.
What does kernel 4.4.7 have that kernel 4.4.6?

Run dmesg and see if it gives you any clues.

mralk3 · 04-15-2016, 11:06 PM

Quote:

Originally Posted by rkelsen

You don't need to completely remove and reinstall Virtualbox... you just have to compile its modules for the new kernel:

Code:

# cd /usr/src/vboxhost-5.x.xx
# make install

That and if you have VirtualBox Guest Additions you need to rebuild those modules too for guest support. Copy paste, file sharing in the guest OS <-> host OS. You need to do both of these things each time you upgrade your kernel.

Maybe you already know all this, but it might be helpful to another Slackware user with a similar issue.

Ztcoracat · 04-15-2016, 11:15 PM

Quote:

Originally Posted by rkelsen

You don't need to completely remove and reinstall Virtualbox... you just have to compile its modules for the new kernel:

Code:

# cd /usr/src/vboxhost-5.x.xx
# make install

I run this as root when the kernel gets upgraded:

Code:

/etc/init.d/vboxdrv setup

Works for me-

cwizardone · 04-15-2016, 11:37 PM

Quote:

Originally Posted by Ztcoracat

....I've never had any issues with updates wrecking anything as long as I've been running Slackware.
I have had updates wreck things on other distributions but never Slackware.
Reading the change logs for kernel 4.4.7 may provide an answer.....

It doesn't happen often, but it does happen. Two or three weeks ago there was a problem with the polkit upgrades and there have been other problems over the years, but that is what -current it for, is it not.

@rkelsen and mralk3,
Somewhere along the line it was recommended that the previous version of VirtualBox be uninstalled before installing/upgrading to a new version. IIRC, it was when they moved from the 4.xx series to the 5.xx series.
I use their package and it has always worked. In /opt/VirtualBox is a file named, uninstall.sh. Run that and it removes the module. Run the VirtualBox-whateverversion-Linux_amd64.run package again and it rebuilds the module using the new kernel and installs it. Simple enough and takes only a minute or so.

Ztcoracat · 04-15-2016, 11:47 PM

Quote:

Originally Posted by cwizardone

It doesn't happen often, but it does happen. Two or three weeks ago there was a problem with the polkit upgrades and there have been other problems over the years, but that is what -current it for, is it not.

If kernel 4.4.6 works for you than delight in that and enjoy the rest of your weekend.

Most folks don't read through their updates. I do.
-::-Reading through the entire update when it's done can give you an idea of what may break things.-::-
It could of been something in the update or it could of been something in the upgrade if you ran 'slackpkg upgrade-all'-

Agreed, it does happen sometimes.

cwizardone · 04-15-2016, 11:59 PM

@Ztcoracat
I read through the 4.4.7 change log the day before yesterday and again a few minutes ago, and saw references to BTUSB and ALSA USB and several others, but I really don't know enough to identify a possible problem.

Ztcoracat · 04-16-2016, 12:10 AM

Quote:

Originally Posted by cwizardone

@Ztcoracat
I read through the 4.4.7 change log the day before yesterday and again a few minutes ago, and saw references to BTUSB and ALSA USB and several others, but I really don't know enough to identify a possible problem.

Ok-
I'll read through the change log tomorrow evening and see if there is a solution to the possible issue.
There was a recent patch to the previous mainline and a incremental patch and you can view the difference in cgit. Once you know all of that information it can become clear in the changelog what stands out. <OR> not-

-::-I'm still learning myself about the changelogs.-::-

keefaz · 04-16-2016, 05:36 AM

Maybe do a diff from both kernels configs?

Ztcoracat · 04-16-2016, 09:32 AM

I think you may have a module/driver issue going on with the usb ports.
In a lot of cases the wrong driver is loaded first which will cause the device to not work.
If that's the case than you would have to blacklist the driver thus allowing the proper driver to load.
Drivers are listed in the output of 'lsmod'-
<OR> manually install a driver and possibly have to configure it. (not sure)

I had a similar usb issue and couldn't find out why a device was seen in lsusb but couldn't mnt the device. I thought it may have been a kernel bug.

There were several patches for Alsa usb but they were pcm and mute button things associated with audio output.There were 2 btusb patches but they were fixes for Bluetooth.

Code:

Bluetooth: btusb: Add a new AR3012 ID 13d3:3472
Bluetooth: btusb: Add a new AR3012 ID 04ca:3014

There were a handful of patches made for usb malformed usb descriptor issues that explained a discovery in Fedora but I don't know if it's related to your usb issue.

Code:

 A Fedora user reports that the ftdi_sio driver works properly for the
    ICP DAS I-7561U device.  Further, the user manual for these devices
    instructs users to load the driver and add the ids using the sysfs
    interface.
    
    Add support for these in the driver directly so that the devices work
    out of the box instead of needing manual configuration.

he driver can be crashed with devices that expose crafted descriptors
    with too few endpoints.

I could be wrong cwizardone but it sounds like a module/driver issue with kernel 4.4.7.
I encourage you to make a bug report so that the men that make patches to the kernel can fix it.

You could write to one of the maintainers that do the patches for the kernel.
Greg Kroan-Hartman greg@linuxfoundation.org

It could be that the Kernel was not loading the usb_storage module during startup.

Code:

su modprobe usb_storage

Plug in the drive after running that cmd and see if it starts working?
http://ubuntuforums.org/showthread.php?t=1586206

Other links that may help.
https://wiki.archlinux.org/index.php/kernel_modules
https://wiki.archlinux.org/index.php...s#Blacklisting

http://www.linuxquestions.org/questi...-a-4175431580/
http://www.linuxquestions.org/questi...tected-876180/

http://digital.ni.com/public.nsf/all...257C670068ED2B

mralk3 · 04-16-2016, 09:54 AM

You probably already know this, but i will add it just in case someone else doesnt. If you write to a kernel dev be sure to attach to the email your boot dmesg output, lspci -v output, and lsusb output.

cwizardone · 04-16-2016, 10:18 AM

Quote:

Originally Posted by Ztcoracat

I think you may have a module/driver issue going on with the usb ports.......

Thanks for all your help. It is sincerely appreciated!

Ztcoracat · 04-16-2016, 10:15 PM

Quote:

Originally Posted by cwizardone

Thanks for all your help. It is sincerely appreciated!

You're Welcome-

cwizardone · 04-24-2016, 01:42 PM

The 4.4.8 kernel fixed the problem.
All the latest updates have been installed and all is well..... so far.