Bug 115177 - sax2 doesn't start on Fujitsu Siemens Lifebook E8010
Summary: sax2 doesn't start on Fujitsu Siemens Lifebook E8010
Status: VERIFIED INVALID
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: SaX2 (show other bugs)
Version: Beta 4
Hardware: Other All
: P5 - None : Major
Target Milestone: ---
Assignee: Marcus Schaefer
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-03 20:21 UTC by Gernot Hillier
Modified: 2005-09-05 13:15 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
SaX.log (72.91 KB, text/x-log)
2005-09-03 20:22 UTC, Gernot Hillier
Details
hwinfo output on this laptop (297.58 KB, text/plain)
2005-09-03 20:23 UTC, Gernot Hillier
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gernot Hillier 2005-09-03 20:21:30 UTC
On my Fujitsu Siemens Lifebook E8010, sax2 doesn't start in the text console 
after "init 3". 
 
This is a system updated from 9.3->10.0b3->10.0b4. 
 
Same problem already occured for b3 (sorry for the late report). 
 
This system is one of those were you need 855resolution to patch VBIOS to use 
the native resolution. 
 
However, at the moment I tried to start SaX2, the VBIOS was already patched - 
and I'm quite sure SaX2 worked in 9.3 under the same conditions w/o problems.
Comment 1 Gernot Hillier 2005-09-03 20:22:10 UTC
Created attachment 48713 [details]
SaX.log
Comment 2 Gernot Hillier 2005-09-03 20:23:37 UTC
Created attachment 48714 [details]
hwinfo output on this laptop
Comment 3 Gernot Hillier 2005-09-03 20:25:45 UTC
What I forgot to mention, this machine has a touchpad and one of those awful 
trackpoints in the keyboard. 
Comment 4 Gernot Hillier 2005-09-03 20:27:00 UTC
If you need a working xorg.conf (from 9.3), please just tell me... :) 
Comment 5 Marcus Schaefer 2005-09-05 09:34:44 UTC
The problem is there is no core pointer because of a wrong entry in  
xorg.conf  
  
    Option       "Protocol" "synaptics" 
 
I do not have any clue how this was included. The hwinfo output seems 
to show the correct protocol. Please provide more specific information: 
 
  (1) call "hwinfo --mouse" and provide the result 
  (2) now call "sysp -s mouse" and provide the result 
 
Also usefull would be to see a complete SaX.log. Please call 
 
   "sax2 -r" 
 
from runlevel 3 and provide the log 
 
  /var/log/SaX.log 
 
Thanks 
Comment 6 Gernot Hillier 2005-09-05 13:05:29 UTC
What the... I just tried to follow your requirements, and... I somehow fixed 
it :-((( 
 
I can't understand this, but I'm sorry to tell you the problem does not occur 
any more. I tried to reboot the machine twice and sax2 now always starts. :(( 
 
So I suppose we should close this bug, right? 
Comment 7 Gernot Hillier 2005-09-05 13:08:42 UTC
One question still (forgot this before, sorry!): does SaX2 read the old 
xorg.conf if it exists?  
 
If yes, it could got confused because with SUSE 9.3 I played around with the 
pointer settings some time because I wanted both touchpad and trackpoint to 
work reliably. So maybe the old xorg.conf contained quite wrong entries - but 
at least it worked for X... 
Comment 8 Marcus Schaefer 2005-09-05 13:12:07 UTC
yes sax will import your configuration if you start sax on a running 
X-server which you have access to. So I now can understand the strange 
protocol entry :) 
Comment 9 Gernot Hillier 2005-09-05 13:15:17 UTC
Thanks.