[Bug 956467] New: Booting Leap 42.1 disables USB, Camera and finger scanner when booting into Windows the next time
http://bugzilla.suse.com/show_bug.cgi?id=956467 Bug ID: 956467 Summary: Booting Leap 42.1 disables USB, Camera and finger scanner when booting into Windows the next time Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: hkuehnemund@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Issue: Dual boot setup, Windows 7 (installed first) and a new Leap 42.1 installation next to it on an t440p in a docking station. In Windows, keyboard and mouse (wireless through Logitech Unify USB dongle) work fine as well as camera and fingerprint scanner When booting into Leap (using restart and selecting Leap 42.1 in Grub), things continue to work fine. When booting into Windows again (using restart and selecting Windows 7 in Grub), keyboard and mouse don't work any longer as well as camera and fingerprint scanner. Looking at the device list in windows, all those devices are not available. Rebooting Windows enables them again. Expected result: Leap does not mess up with internal devices like USB (e.g. for wireless keyboard) when booting into Windows after being on Leap. This did not happen with openSUSE13.2 which was installed before Leap was applied (using a fresh installation, no update whatsoever). I know this sounds very strange. I'm in Nuremberg office 2.2.18, so feel free to pass by and we can take a look together. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=956467
http://bugzilla.suse.com/show_bug.cgi?id=956467#c1
--- Comment #1 from Hannes Kühnemund
http://bugzilla.suse.com/show_bug.cgi?id=956467
Hannes Kühnemund
http://bugzilla.suse.com/show_bug.cgi?id=956467
http://bugzilla.suse.com/show_bug.cgi?id=956467#c2
Oliver Neukum
http://bugzilla.suse.com/show_bug.cgi?id=956467
http://bugzilla.suse.com/show_bug.cgi?id=956467#c3
--- Comment #3 from Hannes Kühnemund
http://bugzilla.suse.com/show_bug.cgi?id=956467
http://bugzilla.suse.com/show_bug.cgi?id=956467#c4
--- Comment #4 from Hannes Kühnemund
http://bugzilla.suse.com/show_bug.cgi?id=956467
http://bugzilla.suse.com/show_bug.cgi?id=956467#c5
Oliver Neukum
So false alarm, the issue is still there. Leap disables all ACPI devices when booting into Windows the next time. Quite a bummer for LEAP tbh.
Is this a regression from 13.2? Could you test vanilla KOTD? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=956467
http://bugzilla.suse.com/show_bug.cgi?id=956467#c6
Hannes Kühnemund
Is this a regression from 13.2?
Definitely, it was working when 13.2 was running.
Could you test vanilla KOTD?
Where can I find it? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=956467
http://bugzilla.suse.com/show_bug.cgi?id=956467#c7
--- Comment #7 from Oliver Neukum
(In reply to Oliver Neukum from comment #5)
Could you test vanilla KOTD?
Where can I find it?
http://kernel.suse.com/branches/vanilla -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=956467
Oliver Neukum
http://bugzilla.suse.com/show_bug.cgi?id=956467
Chenzi Cao
http://bugzilla.suse.com/show_bug.cgi?id=956467
http://bugzilla.suse.com/show_bug.cgi?id=956467#c8
Oliver Neukum
http://bugzilla.suse.com/show_bug.cgi?id=956467
http://bugzilla.suse.com/show_bug.cgi?id=956467#c9
Thomas Renninger
Thomas, any ideas? Not really. Sounds really nasty...
Trying out different kernels sounds like a good idea. First find out whether it has to do with the kernel version at all: A 13.2 kernel on Leap should verify that. This is cumbersome, but I have no other idea as well. You could also try one of these boot paraemeters (from kernel sources, Documentation/kernel-parameters.txt): reboot= [KNL] Format (x86 or x86_64): [w[arm] | c[old] | h[ard] | s[oft] | g[pio]] \ [[,]s[mp]#### \ [[,]b[ios] | a[cpi] | k[bd] | t[riple] | e[fi] | p[ci]] [[,]f[orce] Where reboot_mode is one of warm (soft) or cold (hard) or gpio, reboot_type is one of bios, acpi, kbd, triple, efi, or pci, reboot_force is either force or not specified, reboot_cpu is s[mp]#### with #### being the processor to be used for rebooting. Hm, does the platform support UEFI? If yes, is it used? If supported, but not used, I'll try UEFI. ... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=956467
http://bugzilla.suse.com/show_bug.cgi?id=956467#c10
--- Comment #10 from Hannes Kühnemund
Could you test vanilla KOTD?
So I installed the Kernel of the day from http://kernel.suse.com/branches/vanilla. I actually had two of them running, one from last week and one from today I did not boot into Windows in between them, the laptop was suspended over the weekend. I cannot really tell if the current situation was caused by the KOTD, but Windows does start anymore when selecting it from the grub list. All it shows the some greenish horizontal lines, probably the content from the frame buffer. Pressing F8 to get into the Windows Safe Boot menu doesn't work either. So Windows is now broken and I need to reinstall it (or at least try to repair with a Windows DVD). Oliver, so the offer to give the laptop to you for further analysis is currently on hold. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=956467
Oliver Neukum
http://bugzilla.suse.com/show_bug.cgi?id=956467
http://bugzilla.suse.com/show_bug.cgi?id=956467#c12
--- Comment #12 from Hannes Kühnemund
So Windows is now broken and I need to reinstall it (or at least try to repair with a Windows DVD).
I had a backup of my entire disk and dd'ed all partitions back to disk. Windows is now operational again. I then upgraded the BIOS from version 2.18 (2013) to 2.34 (most recent one) in hope of resolving some of those ACPI things. And now it gets interesting with the latest BIOS. The bad news is, that Windows still does not recognize ACPI devices after Leap was running before. Sometimes (unfortunately not reproducible), which is new, Windows automatically reboots before the password prompt. The worse news is, that Leap now faces the same issue after Windows was running before. No USB devices found, e.g. lsusb hangs forever and prevents a shutdown. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=956467
http://bugzilla.suse.com/show_bug.cgi?id=956467#c13
Hannes Kühnemund
participants (1)
-
bugzilla_noreply@novell.com