Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#41673 - [usbip] /sys/bus/usb/drivers/usbip-host directory is missing

Attached to Project: Community Packages
Opened by sam (asg1448) - Sunday, 24 August 2014, 05:41 GMT
Last edited by Sébastien Luttringer (seblu) - Tuesday, 26 August 2014, 08:54 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sébastien Luttringer (seblu)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: driver missing?

/sys/bus/usb/drivers/usbip-host directory is missing

Additional info:
* package version(s):
usbip 3.16-1, x64
kernel 3.16.1-1-ARCH

Steps to reproduce:

#usbipd --daemon
# usbip --debug bind --busid=4-3
usbip: debug: usbip.c:141:[run_command] running command: `bind'
usbip: debug: sysfs_utils.c:17:[write_sysfs_attribute] error opening attribute /sys/bus/usb/drivers/usbip-host/match_busid
usbip: debug: utils.c:47:[modify_match_busid] failed to write match_busid: No such file or directory
usbip: error: unable to bind device on 4-3


This task depends upon

Closed by  Sébastien Luttringer (seblu)
Tuesday, 26 August 2014, 08:54 GMT
Reason for closing:  Not a bug
Comment by Doug Newgard (Scimmia) - Sunday, 24 August 2014, 06:11 GMT
Are the usbip-core and usbip-host modules loaded? If you haven't rebooted after installation, they're probably not.

Edit: I see by your forum thread that that was the problem and that you already figured it out. https://bbs.archlinux.org/viewtopic.php?id=186112
Comment by sam (asg1448) - Sunday, 24 August 2014, 06:31 GMT
apparently following commands would install necessary drivers:

# modprobe usbip_core
# modprobe usbip_host
Comment by Doug Newgard (Scimmia) - Sunday, 24 August 2014, 06:36 GMT
Do not just close this, the bug is still relevant. The package should either go ahead and load the modules, or tell you that you need to load them and NOT automatically load them on boot. The half-way situation right now is confusing.
Comment by Sébastien Luttringer (seblu) - Monday, 25 August 2014, 01:10 GMT
Despite I didn't like that, it's already the case, modules are loaded by systemd

$ pacman -Qo /usr/lib/modules-load.d/usbip.conf
/usr/lib/modules-load.d/usbip.conf is owned by usbip 3.16-1
Comment by Doug Newgard (Scimmia) - Monday, 25 August 2014, 01:54 GMT
They're loaded on boot, not on install. The software is non-functional until you either reboot or manually load the modules.
Comment by Sébastien Luttringer (seblu) - Monday, 25 August 2014, 03:11 GMT
yes, like all others packages we don't modprobe nor restart systemd modules-load.service in .install.

I looked into several fellow packages which does that and they don't print a message about that.

What is confusing me, is more why modules are not loaded by the kernel. After all, usbip is in the kernel tree.

IMHO, a warning message about usbip doesn't load its modules itself should go in the usbip wiki page (that's where we put configuration instructions and tips). It's also what we do with other packages.
Comment by Doug Newgard (Scimmia) - Monday, 25 August 2014, 03:55 GMT
Do those other packages install a modules-load.d file to then magically work after a reboot?

I'm not being sarcastic, I'm actually asking since I don't know what packages you're referring to.
Comment by Sébastien Luttringer (seblu) - Monday, 25 August 2014, 09:44 GMT
$ pkgfile -sg '/usr/lib/modules-load.d/*'
core/nfs-utils
extra/capi4hylafax
extra/ossp
extra/x2goserver
community/acpi_call
community/acpi_call-lts
community/cdemu-daemon
community/cdrtools
community/drbd
community/espeakup
community/tp_smapi
community/tp_smapi-lts
community/usbip
Comment by Doug Newgard (Scimmia) - Monday, 25 August 2014, 14:41 GMT
If that's the convention, then so be it. I figured it would be handled like tmpfiles, where the files are created in the install script so that the software is functional after installation.

Loading...