From: Henry N. <hen...@ar...> - 2008-06-25 20:01:12
|
Jonathan Deitch wrote: > I can't find either winmsd or msinfo under Vista ... neither seems to > exist ... Have you tryed the "Search ... for file"? MS says _all_ XP and Vista have it: http://support.microsoft.com/kb/q300887/#appliesto > > I did, earlier, post the IRQ results from the working Knoppix boot ... > was that not sufficient? > > CPU0 > 0: 57713 local-APIC-edge-fasteoi timer > 1: 141 IO-APIC-edge i8042 > 8: 1 IO-APIC-edge rtc > 9: 26 IO-APIC-fasteoi acpi > 12: 151 IO-APIC-edge i8042 > 14: 1215 IO-APIC-edge ide0 > 16: 0 IO-APIC-fasteoi yenta > 17: 122 IO-APIC-fasteoi ahci > 18: 2 IO-APIC-fasteoi ohci_hcd:usb1, ehci_hcd:usb6 > 19: 29 IO-APIC-fasteoi ohci_hcd:usb2, ohci_hcd:usb3, Under Linux the IRQ0 is a "fake" or it is redirected. Your Linux boot messages says, that IRQ0 is not connected to the timerchip. BIOS has sayed it is vector 0x31, I assume it is IRQ17. But this is your USB controller. Vector 0x31 is false listed by BIOS, that says the other kernel message from Gparted. The question is: Where is the timer real? Native Linux can move the IRQ by reprogramming the timer chip (set a virtual irq line or so). But coLinux should not do it. In a virtualisation we have per define no hardware access. You can see it in the list above, that your IRQ0 is not an "IO-APIC". If we would know the real Timer IRQ, we can trace it on your machine. If you not have the tools, then please open your hardware device control center (I'm german, so please sorry for wrong translation) and view your hardware devices in a list sorted by type, than lets see the IRQ list seen by Windows. - Something must be difference from the list you send from Knoppix. The question is what? You can send me a screenshot from that view. -- Henry N. |