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#c30
Scott Couston changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
Info Provider|alpha096@virginbroadband.co |
|m.au |
--- Comment #30 from Scott Couston 2009-04-06 14:20:32 MDT ---
Steffen - I do not have the authority to directly assign a bug unless the
assignee requests it.
Yes there is a taint of Hardware issues here but the scanner device, its USB
connection and the PC Architecture are inseparable. That is why my test results
in speed and time of this module are so vastly different that those in #2. Also
this bug is not found in gnome.
Once we can all start off the with same X_64 standard BIOS options in EVERY AM2
socket motherboard, ALL with the same AMD features we can move forward.
If Kernel development tells us that Yast/Kernel/KDE4 provides 2 different
environments totally depend and on 2 X AMD X_64 standard BIOS Option we can
move to correct this....The how here in yet to be known.
However IF Kernel Development can tell us that this 2 X AMD X_64 standard BIOS
Option matters nothing to do with the way we manage the USB Bus - Then I am mad
and the reason for this massive difference will require me to work out
"What is different about your #2 results environment and my own massive
differences" it may well be that I close this bug until I can work out what the
difference is - and this may prove to be allusive for some time to come.
Just to re-cap-
I just want to start off with the same level playing field now with my X_64
Arch and AMD stand BIOS options x 2 that is present in you X32 P3 in #2 and
only Kernel Development will have the answer to start this process.
--
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.