http://bugzilla.novell.com/show_bug.cgi?id=555351 http://bugzilla.novell.com/show_bug.cgi?id=555351#c19 Scott Couston <alpha096@virginbroadband.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |alpha096@virginbroadband.co | |m.au --- Comment #19 from Scott Couston <alpha096@virginbroadband.com.au> 2010-02-26 09:36:17 UTC --- Dan I have the same CPU and I have the same situation and I am a user. I have a possible work around while others debate priorities on Kernel Problems for X_64. With the following I'm punting on you having an ASUS Motherboard if you have a Gigabyte board nothing will help you except the boot from install DVD as below....Sorry Firstly there is absolutely nothing wrong with your BIOS version - Lets get that right now! Go into BIOS Turn off the selection of an Over-clocking Profile. It will contain a default profile and there are normally 4 of them - most all Dynamic - This is the problem. You can, however freely use a permanent clock frequency - you can overclock if you wish until the CPU throws a whammy! Check the USB Version Selection in BIOS - I think it may be limited to only one version (specification) rather than both specs. That should do it, Totally ignore the rubbish in the start-up log - Its all crap but it will disappear if your turn default Cool N Quiet==Disabled. Last resort you can try is to leave the install DVD in and boot from it>Boot from Hard Disk>Desktop Theoretically the above line should be nonsense, but it does stop all these huge errors in the new Kernel. Email me personally if you still have problems - I have more tricks to grant stability. Suse.de will still be arguing about the priority of this bug well before anyone does anything to correct this. Argument over priorities are neither helpful nor constructive and have no place in bug reports - we settle personal opinions via less public high-school yard brawls. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.