no mouse in Windows 8 after restarting from Linux
 

Hi

I recently installed Linux Ubuntu scure 64bits (its was hard with Windows 8 EFI). The problem is, when I'm in linux and then I restart (or power off) to enter to Windows I have not mouse in Windows 8. So I must Power off my PC and then I Have mouse.

Someone could help me.

Thanks in advance.

Maybe this question would be better asked in a Windows forum.
jdk

Sounds like Windows is relying upon a hardware reset state to recognize the mouse, and that Linux is changing that hardware state. Probably disabling an interrupt.

1. Change Linux mouse settings to something more compatible with the Windows hardware use.

2. Try hitting the physical reset button between Linux shutdown and before the Windows boot, to force a hardware reset. Careful timing needed, and you will probably, sooner or later, get the timing wrong. But it is a test.

3. Change the Linux shutdown scripts in /etc/rc.d to restore the original mouse settings, like restoring the mouse interrupt. I currently have no clue on HOW to do that.

this sounds like a windows8 FUBARED implementation of Microsoft royally messed up
"secure boot"

Microsoft support might be a better place to find an answer

I'd be with selfprogrammed on the idea of some saved state. Some power is being left on enough to hold some state in a chip or prom or what not.

I'm not sure I understand the original post, it seems to contradict itself

So you power off your machine, power it back on into Windows, and the mouse doesn't work.

So you power off your machine, power it back on into Windows, and the mouse does work.

Which is it? What are you doing different when it does work versus when it doesn't work? Is this a reboot versus power off discrepancy, or are you saying that the machine has to be powered off from Windows, in order for the mouse to work in Windows the next time it's turned on? Is this a PS2 mouse? USB? Laptop trackpad?

i read it as
1) running linux
2) reboot to windows
3) - no mouse
4) reboot FROM WINDOWS to windows
-- mouse works


to me it sounds like the mouse is not seen by the boot process in windows the first time around

the second reboot from win8 to win8 seams to reset the win8 secure boot sig and the kernel mod mouse driver in win8 for the mouse is aloud to run

a messed up implementation of MS's mess they call "secure boot"

it is a win8 issue

and Microsoft support is the best place for getting an answer

OK, then I am confused also.

Yes that is my problem.

Completely agree
 

We may not help much as Win 8 is not open source.

I see occasional similar-type problems where mouse wouldn't work between OS reboots on a couple Dell dual-boot laptops (fedora and vista/w7) . I always figured it was just a BIOS glitch, and it wasn't annoying enough to me that I felt I should look for any bios updates to download. I just got in the habit of powering off the laptops between OS boots.

The first option is if it is an external mouse. Try booting with it not attached and then attaching it after Windows has booted. Try another mouse. Well, even if it is internal, try an external mouse anyways; try both constantly attached and also removed and inserted after OS boot. If one of these work-arounds takes care of it, consider living with it.

One, painful option, not necessarily realistic. Is to restore that PC back to their day #1 installed configuration. Iteratively test the mouse to verify that it works all the time. If there are never any problems, then it points towards the Linux installation, IMHO modifications to the boot loader. I say this is too costly in terms of your time if a different or externally added mouse takes care of the problem, or the option of unplugging the mouse during boot works.

Microsoft may not help for two or three reasons either.

1.) You installed Linux on what they perceive is "their" machine. BAD YOU! Support denied!
2.) You should first prove that there's a problem with the mouse in the only Windows case. I.e. boot to Windows repeatedly and prove that the mouse doesn't work. If you can't, support denied!
3.) There's something called the Interrupt Descriptor Table which I believe BIOS sets up and further their booting process can change that table as well. Possible, sort of beyond my depth here in real experience; but it may also be that the Linux boot process modifies that as well. Even further, a lot of recover/restore apps are actually Linux so which boots PC recovery menus. I recall working with things like this and it was difficult because you had to "find" where the interrupt vectors were for system resources, but also not modify, or modify and restore. My bad descriptions aside, they even sniff that you'd installed an alternate boot loader, support denied! (They'd actually be somewhat justified here too, unfortunately.)

"So, then I said, 'Hey, maybe it’s the needle!'"
--Steve Martin"

People still dual-boot? I don't understand why you jus wouldn't use VMWare or VirtualBox to run Linux / Windows. I see no need to dual boot systems for reasons exactly listed above in this thread. Just something to think about...

have you tried running CUDA in a windows VM install on linux
or
used CUDA in a linux VM install on windows ?

By any chance do you have a Microsoft brand mouse?

Just from experience I have a microsoft comfort curve and sometimes when boot into Linux and then reboot into windows Using Win 7 No EFI and then reboot back into Windows, sometimes I find I have to reboot again so my keybaord will start working. I don't have this problem with any other product such as logitech etc.

All my hardware has always worked flawlessly with Linux System, so I think its a Microsoft Problem with there OS and Products.

Try a different Mouse brand and see if you still have that problem. I'm really not sure what that would have to do with it, but it solved my problem.