Comment 4 for bug 227198

Found it. It seems that modinfo needs some love.

My home directory is NFS mounted. "sudo modinfo xyz" works when I'm in some non-NFS mounted directory:

johan@transwarp:~$ sudo modinfo usbcore
modinfo: could not open usbcore: Permission denied

johan@transwarp:~$ cd /tmp/

johan@transwarp:/tmp$ sudo modinfo usbcore
filename: /lib/modules/2.6.24-16-generic/kernel/drivers/usb/core/usbcore.ko
license: GPL
srcversion: E8DACA0029626C336D1A513
alias: usb:v*p*d*dc*dsc*dp*ic09isc*ip*
alias: usb:v*p*d*dc09dsc*dp*ic*isc*ip*
depends:
vermagic: 2.6.24-16-generic SMP mod_unload 586
parm: usbfs_snoop:true to log all usbfs traffic (bool)
parm: blinkenlights:true to cycle leds on hubs (bool)
parm: old_scheme_first:start with the old device initialization scheme (bool)
parm: use_both_schemes:try the other device initialization scheme if the first one fails (bool)
parm: autosuspend:default autosuspend delay (int)
johan@transwarp:/tmp$

When "modinfo fglrx" tries to open("fglrx", O_RDONLY), it fails with ENOENT.

When "sudo modinfo fglrx" tries to open("fglrx", O_RDONLY), it fails with EACCESS.

So modinfo needs to do something differently when it gets EACCESS trying to open the requested module in the current directory.