usbip 0.1.7 incompatible with kernel 3.2.x upstream moved
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
usbip (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Hi,
The usbip userspace programs have been moved into the linux kernel source. The repository at usbip.sourcefor
Quoting the usbip/obsolete/
> root@blinky:~# more usbip/obsolete/
> The linux drivers and command line tools are now being maintained in the linux kernel tree.
>
> The versions found here are not being maintained and thus obsolete.
>
> For the most recent versions, please visit:
> http://
>
> The git tree (git is the version control system used there instead of SVN):
> git://git.
>
> The drivers were already in the kernel tree since version 2.6.28. The userspace tools have been moved on 20110520.
>
The usbip package should instead be being built from the usbip userspace source found in the linux kernel. This is especially important as the usbip modules the userspace tools rely on have been changed:
linux/drivers/
26/* kernel module names */
27#define USBIP_CORE_MOD_NAME "usbip-core"
28#define USBIP_HOST_DRV_NAME "usbip-host"
29#define USBIP_VHCI_DRV_NAME "vhci_hcd"
The 1.0.7 usbip userspace code instead checks on the old module names (usbip and usbip_common_mod):
root@spug:
./lib/stub_driver.c
./lib/vhci_driver.c
Since the ubuntu 12.04 LTS kernel had the following bug fix applied:
https:/
The usbip 0.1.7 package is no longer compatible with the newer kernel module names.
The usbip package should be rebuilt from the new kernel usbip userspace source to regain compatibility.
Cheers,
Doug
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: usbip 0.1.7-3
ProcVersionSign
Uname: Linux 3.2.0-24-generic x86_64
NonfreeKernelMo
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Sat May 5 11:12:12 2012
InstallationMedia: Mythbuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcEnviron:
LANGUAGE=en_AU:en
TERM=xterm
PATH=(custom, no user)
LANG=en_AU.UTF-8
SHELL=/bin/bash
SourcePackage: usbip
UpgradeStatus: Upgraded to precise on 2012-05-03 (1 days ago)
Status changed to 'Confirmed' because the bug affects multiple users.