Suspend and unload reload modules error

capthookb · 09-09-2006, 12:52 PM

I have kernel 2.6.15 and i have patched with suspend2 patch.
I use acpitool to suspend to ram my pc but when i get back some devices are not working (my DVB Skystar2 card) and the mouse.
For the DVB card i get around the problem by removing and reloading the apropriate module. But for mouse i cannot.

Code:

root@domatio:~# rmmod evdev
ERROR: Module evdev is in use

root@domatio:~# lsmod | grep evdev
evdev                   6976  1

Is there any way to unload and reload the evdev module?

Old_Fogie · 09-12-2006, 07:00 AM

did you try synaptics driver which one are you using?

to manually unload a module requires "rmmod evdev -f" assuming your kernel is compiled to allow you to unload modules.

Sometimes, 1/40 times maybe this happens to me, and I just kill X by ctrl+alt+bckspace and then I'm fine, i use fluxbox so it's back in there in seconds anyway.

capthookb · 09-12-2006, 08:18 AM

No, i'm using evdev driver because it's the only driver that works with my tilt wheel (microsoft mouse)
The thing is that the driver is used by X and it doesn't allow me to unload and reload it.
When i kill or exit X windows to console login, the evdev module is no longer used, and i can unload and reload it. But then when i start again X the mouse is no longer working.
So i guess it's a bug of either evdev or something else.

Old_Fogie · 09-12-2006, 04:30 PM

what happens if you unplug the mouse and put it back in, does hotplug 'modprobe evdev' for you?

capthookb · 09-13-2006, 09:15 AM

The mouse is not working if i unplug and replug it.
The driver is used by X and not by the mouse.
Unplugging it doesn't remove evdev module.
I also tried removing usb modules first but i still couldn't remove evdev during X.
That's why only when i quit X i am able to unload the evdev module.

Old_Fogie · 09-13-2006, 06:40 PM

what i meant was if you exit X...unplug the mouse...issue the standby command. no your pc is sleeping. then wake it up, give a few seconds or so...then plug the mouse in and go into X do you get a working mouse?

FWIW on one pc I had a similar issue and I checked my kernel compile and I put evdev as a "check" for yes and not a 'dot' for module and that resolved me. Mileage may vary obviously.

FWIW-2: I went thru the mailing list there at suspend2 site, and there is mention of people having this like you and I and no responses.

capthookb · 09-14-2006, 07:00 AM

I tried compiling evdev in the kernel as well. But i had the same problem.
I haven't tried what you said about shutting down X, unpluging the mouse, suspend and then do it in the reverse order...
Basically i have set up mythtv and i want with the remote control to just suspend the pc (withouth doing anything else). And then when i turn the pc on again, i would be glad to have every hardware working again...
But unfortunately that's not the case. Who knows maybe in next kernels....

P.S: I've upgraded to 2.6.17.11 but the problem remains.

Thank you for your concern!

Old_Fogie · 09-14-2006, 08:25 AM

Yeah I suggested it as it just might help you pinpoint what's going on.

have you tried to 'blacklist' the evedev modules in the config files for suspend2.

you should be able to tell it not to rmmod your evdev or mouse in those files.

give that a shot.

capthookb · 09-14-2006, 04:11 PM

I discovered why my mouse is not working after the suspend

But i still cannot solve the problem.
After doing a

Code:

#cat /proc/bus/input/devices

before and after the suspend i discovered that the event device of the mouse has changed from 1 to 2.

Before the suspend:

Code:

I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/class/input/input0
H: Handlers=kbd event0
B: EV=120013
B: KEY=4 2000000 3802078 f840d001 f2ffffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=045e Product=008c Version=0057
N: Name="Microsoft Microsoft Wireless Optical Mouse? 1.0A"
P: Phys=usb-0000:00:10.0-1/input0
S: Sysfs=/class/input/input1
H: Handlers=mouse0 event1
B: EV=7
B: KEY=1f0000 0 0 0 0 0 0 0 0
B: REL=1c3

and after the suspend:

Code:

I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/class/input/input0
H: Handlers=kbd event0
B: EV=120013
B: KEY=4 2000000 3802078 f840d001 f2ffffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=045e Product=008c Version=0057
N: Name="Microsoft Microsoft Wireless Optical Mouse? 1.0A"
P: Phys=usb-0000:00:10.0-1/input0
S: Sysfs=/class/input/input4
H: Handlers=mouse0 event2
B: EV=7
B: KEY=1f0000 0 0 0 0 0 0 0 0
B: REL=1c3

and in xorg.conf i have "Option" "Device" "/dev/input/event1"
If i shutdown X, change the event device in xorg.conf and then fire up X again the mouse is working!!!

Any ideas?

capthookb · 09-14-2006, 05:16 PM

While searching google i came up with this page: http://gentoo-wiki.com/HOWTO_Advanced_Mouse

where it explains the configuration of mice working with evdev in xorg.conf. For xorg version > 0.6.9 (i have 0.6.9) instead of the Option "Device" "dev/input/eventX" you can set the mouse with the Option "Name" so evdev won't have to look for a specific /dev/input/eventX option because they can change.

Code:

    Identifier     "Mouse1"
    Driver         "evdev"
    Option         "Device" "/dev/input/event1"

Code:

    Identifier     "Mouse1"
    Driver         "evdev"
    Option         "Name"   "Microsoft Microsoft Wireless Optical Mouse� 1.0A"

The string in the name has to be the exact same string that cat /proc/bus/input/devices prints. But in my case that doesn't work. In the string there is the ® character and i don't know if X accepts these characters while parsing xorg.conf or even how to type such a character in xorg.conf
.....

Old_Fogie · 09-15-2006, 08:56 AM

I'm at a loss to be honest.

Maybe make a post, or send an email off to xorg developers? Maybe there is a way to make an 'alias' for the device or something like that? Possibly taking out the trademark logo and all.