FS#49688 - [linux] 4.6.2-1 Typo in output of "uname -r" breaks modprobe
Attached to Project:
Arch Linux
Opened by Felix Hirn (Boonami) - Sunday, 12 June 2016, 16:42 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 12 June 2016, 17:35 GMT
Opened by Felix Hirn (Boonami) - Sunday, 12 June 2016, 16:42 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 12 June 2016, 17:35 GMT
|
Details
Description:
Trying to add any module via e.g. *modprobe fat* yields > modprobe: FATAL: Module fat not found in directory /lib/modules/4.6.1-2-ARCH , which is obviously the wrong version number (the last two digits are flipped). According to [man modprobe](http://man7.org/linux/man-pages/man8/modprobe.8.html), modprobe looks up modules in */lib/modules/`uname -r`*. Invoking *uname -r* returns > 4.6.1-2-ARCH , which is wrong again. According to [this stackexchange post](http://unix.stackexchange.com/questions/136959/where-does-uname-get-its-information-from), uname reads a hardcoded C structure from the running kernel, populated in *sys/utsname.h* (see also [man 2 uname](http://man7.org/linux/man-pages/man2/uname.2.html)). Since *uname*'s output includes the keyword *ARCH*, I don't think this is an upstream issue, but rather a packaging mistake. Steps to reproduce: 1. Install *linux 4.6.2-1* 2. Run *modprobe* with an arbitrary module name, e.g. *modprobe fat*. 3. Run *uname -r*. 4. Observe how the output of the last command is subtly, but fatally wrong. |
This task depends upon
Closed by Doug Newgard (Scimmia)
Sunday, 12 June 2016, 17:35 GMT
Reason for closing: Not a bug
Additional comments about closing: Reboot
Sunday, 12 June 2016, 17:35 GMT
Reason for closing: Not a bug
Additional comments about closing: Reboot