[Bug 481299] Yast Scanner Model and Driver Devours system resources at the expense of basic O/S
http://bugzilla.novell.com/show_bug.cgi?id=481299 User alpha096@virginbroadband.com.au added comment http://bugzilla.novell.com/show_bug.cgi?id=481299#c23 Scott Couston <alpha096@virginbroadband.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|alpha096@virginbroadband.co | |m.au | --- Comment #23 from Scott Couston <alpha096@virginbroadband.com.au> 2009-04-01 19:16:49 MDT --- Before I get to logs - I assume the normal Yast logs? Also some question on how Linux responds to some Hardware variables and this may answer why when I insert a new USB device into a New BUS ID the boot process is halted - no time out after 30 mins and no further than boot detecting new USB device. Q. With X_64 AMD we have the option to run in cool and quiet mode or not. Most of us choose disable as the CPU starts at very low frequency and is pathetically slow to up to nominal CPU clock frequency - so most of us leave it disabled to enjoy the performance benefits. 1. Benefits of Disable are CPU clock remains constant, however All ACPI, _PCC, _PSS, _PCT calls are rejected from the O/S and Bios Manages the cooling Policy. 2. Benefits of Enable is that the above O/S calls are not ignored, BUT the CPU clock start at minimum and is so very very very late in placing the CPU clock to its normal frequency and the O/S has to demand CPU performance for quite a long while. Other BIOS Questions related are Plug and Play device can only be set to O/S or BIOS - which do you wish -does it matter. Is legacy support for USB required or will support for V1.1 and V2.0 all o.k? Do I need to enable ACPI SRAT Table Y/N Can you get back to me on the above and I will assume logs are normal Yast Logs. By supplying this info you may well have solved USB device issues!? -- 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.
participants (1)
-
bugzilla_noreply@novell.com