Mailinglist Archive: opensuse-bugs (15061 mails)
| < Previous | Next > |
[Bug 262317] sax2 fails due logitech usb gaming mouse
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Tue, 11 Sep 2007 20:00:14 -0600 (MDT)
- Message-id: <20070912020014.7333ECC78D@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=262317#c113
--- Comment #113 from darren winter <sgt-d@xxxxxxxxxx> 2007-09-11 20:00:12 MST ---
Created an attachment (id=163398)
--> (https://bugzilla.novell.com/attachment.cgi?id=163398)
sax logs & xorg confs
> #48 - patch -p0 when residing in / as root
> attachment: bug-262317_sax2-logitech-profile.diff
meh-rd42:/ # patch -p0 < bug-262317_sax2-logitech-profile.diff
patching file /usr/share/sax/profile/logitech-Gaming
patching file /usr/share/sax/profile/logitech-MediaPlay
patching file /usr/share/sax/profile/logitech-mxlaser
> #100 Afterwards run "sax2 -r". Attach /var/log/SaX.log.
meh-rd42:/ # sax2 -r
SaX: initializing please wait...
SaX: your current configuration will not be read in
SaX: access to your display has been granted
SPP: prepare device [0] profile: NoModelines
SPP: prepare device [1] profile: logitech-Gaming
SPP: prepare device [0] profile: microsoft-natural
SPP: including prepared profile(s)...
SaX: startup
SaX: X-Server: :0.0 -> grant
SaX: using cache data...
popups...
title: message
invalid color/resolution combination.
the selected resolution and/or color settings are not supported by the graphics
cards framebuffer.
title: message
3d accelleration not supported
sax2 cannot offer activation of the 3d subsystem because your graphics
card/driver doesn't support 3d.
results...
when sax2 came up, i clicked test - no test occurred, sax2 window disappeared
-> sax1.log
i ran it again and clicked save this time, the window went away -> sax2.log
in any case, when i restarted x, my monitor started flipping diagonally at
about 10,000 mph. i had to kill it and login again to get it to stop.
i rebooted, same thing. i had to restart x and login to get it to stop.
additionally, for some stupid reason. /boot/grub/menu.lst on my main title
vga-0x31a was changed by sax2 to vga=0x0. so when i was booting up my text was
like 10 inches tall.
does the mouse work? it always has AFTER i have gotten back in to X and/OR
been able to run sax2 -r. so, this time, with the patch the mouse worked...
but it also worked when i ran sax2 -r back in beta 1 and beta 2 with the same
exact results as i had tonight - but in both of those cases i never patched
anything. and if you look at these new logs, i'm not sure the end of the logs
look like any kind of real success, maybe i'm wrong though.
xorg.sax was the config AFTER i ran sax2 -r - like i said, it doesn't appear to
be working, so maybe this file is unchanged by it... and when compared to my
real xorg.conf = identical.
anyway, these are my results with the patch on suse 10.3 beta 3 64-bit and the
logitech g5 version 1 (one side button).
hope this helps!
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
--- Comment #113 from darren winter <sgt-d@xxxxxxxxxx> 2007-09-11 20:00:12 MST ---
Created an attachment (id=163398)
--> (https://bugzilla.novell.com/attachment.cgi?id=163398)
sax logs & xorg confs
> #48 - patch -p0 when residing in / as root
> attachment: bug-262317_sax2-logitech-profile.diff
meh-rd42:/ # patch -p0 < bug-262317_sax2-logitech-profile.diff
patching file /usr/share/sax/profile/logitech-Gaming
patching file /usr/share/sax/profile/logitech-MediaPlay
patching file /usr/share/sax/profile/logitech-mxlaser
> #100 Afterwards run "sax2 -r". Attach /var/log/SaX.log.
meh-rd42:/ # sax2 -r
SaX: initializing please wait...
SaX: your current configuration will not be read in
SaX: access to your display has been granted
SPP: prepare device [0] profile: NoModelines
SPP: prepare device [1] profile: logitech-Gaming
SPP: prepare device [0] profile: microsoft-natural
SPP: including prepared profile(s)...
SaX: startup
SaX: X-Server: :0.0 -> grant
SaX: using cache data...
popups...
title: message
invalid color/resolution combination.
the selected resolution and/or color settings are not supported by the graphics
cards framebuffer.
title: message
3d accelleration not supported
sax2 cannot offer activation of the 3d subsystem because your graphics
card/driver doesn't support 3d.
results...
when sax2 came up, i clicked test - no test occurred, sax2 window disappeared
-> sax1.log
i ran it again and clicked save this time, the window went away -> sax2.log
in any case, when i restarted x, my monitor started flipping diagonally at
about 10,000 mph. i had to kill it and login again to get it to stop.
i rebooted, same thing. i had to restart x and login to get it to stop.
additionally, for some stupid reason. /boot/grub/menu.lst on my main title
vga-0x31a was changed by sax2 to vga=0x0. so when i was booting up my text was
like 10 inches tall.
does the mouse work? it always has AFTER i have gotten back in to X and/OR
been able to run sax2 -r. so, this time, with the patch the mouse worked...
but it also worked when i ran sax2 -r back in beta 1 and beta 2 with the same
exact results as i had tonight - but in both of those cases i never patched
anything. and if you look at these new logs, i'm not sure the end of the logs
look like any kind of real success, maybe i'm wrong though.
xorg.sax was the config AFTER i ran sax2 -r - like i said, it doesn't appear to
be working, so maybe this file is unchanged by it... and when compared to my
real xorg.conf = identical.
anyway, these are my results with the patch on suse 10.3 beta 3 64-bit and the
logitech g5 version 1 (one side button).
hope this helps!
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
| < Previous | Next > |