[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#c26 Scott Couston <alpha096@virginbroadband.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Info Provider|alpha096@virginbroadband.co |jsmeix@novell.com |m.au | --- Comment #26 from Scott Couston <alpha096@virginbroadband.com.au> 2009-04-02 12:47:53 MDT --- Johannes, your #2 hits right home in your reference to a possible lower level issue. Note the only major variable here between your test and mine is X_64 AND/OR the actual Scanner Device. So traditional debug makes sense in 'what is fundamentally different about your test and mine for me to get such a different delay and USB issue. So I now started with the 'differences' or the usual 'What has changed' type question to myself and come up with 2 variables. 1. The scanner is USB dependant on its power source and the other is my X_64 Arch. Can you help in directing questions of mine in #23 to some one in Kernel Support for the answer as I can change the ACPI/USB/CPU BUS/ in above and come up with two entirely different build and recognition times. BIOS defaults only help with M.S O/S so I cannot rely on those. I think we need answers to #23 because I can either halt startup - Period! or start-up runs as normal and scanner database builds in a reasonable time frame. So for us to move forward I need a level playing field and advise on what we, as Linux O/S expect the defaults in X_64 to be particularly in our USB Legacy?Support and/or version support + ACPI questions. This bug may very well be a software non-issue, and I am inclined to agree with this thought, however we all need to learn about AMD X_64 Arch and CPU to move forward in a predictable manner in many issues, including this one. So Why am I bugging you - I dont know who to place Needinfo for answers to #23 in Kernel Support - Can you help redirect appropriately...TA To all in above - As always I may appear to be standing on my head, living in the Southern Hemisphere but sometimes I would like to think I am still rational ;-) -- 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