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!
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!
FS#19554 - [kernel26] 2.6.33.4-1 doesn't load modules (lance.ko, ext2.ko) on VMware VM
Attached to Project:
Arch Linux
Opened by Renato Schmidt (rescbr) - Friday, 21 May 2010, 05:15 GMT
Last edited by Jan de Groot (JGC) - Sunday, 27 June 2010, 17:34 GMT
Opened by Renato Schmidt (rescbr) - Friday, 21 May 2010, 05:15 GMT
Last edited by Jan de Groot (JGC) - Sunday, 27 June 2010, 17:34 GMT
|
DetailsFresh install on VMware, Kernel 2.6.33.4-1 doesn't load some modules (in this case, I missed ext2 and lance), but lsmod reported others being loaded.
modprobe outputs "FATAL: Module lance not found"; insmod returns "insmod: error inserting '/lib/modules/2.6.33-ARCH/kernel/drivers/net/lance.ko': -1 Operation not permitted". Error message on dmesg is: "lance.c: Module autoprobing not allowed. Append "io=0xNNN" value(s)." On a later test, ext2 seems to load with insmod but not modprobe, but did not test device mounting. Installed kernel26-lts (which is 2.6.27.46-1) and it worked flawlessly. Another virtual machine using 2.6.32.9-1 works with no problem. There are some posts on the forum regarding this kernel version and problems with networking, but they might be unrelated as they do not contain full dmesg output or any at all. |
This task depends upon
Closed by Jan de Groot (JGC)
Sunday, 27 June 2010, 17:34 GMT
Reason for closing: Fixed
Additional comments about closing: works in 2.6.34-2
Sunday, 27 June 2010, 17:34 GMT
Reason for closing: Fixed
Additional comments about closing: works in 2.6.34-2
dmesg-2.6.33.4-1.txt
kernel26-lts upgrade should have fixed this.
can you confirm?