[opensuse] 'Missing' monitor during OpenSuSE 11.0 Install
I had an interesting occurance during the install of OpenSuSE 11 on a machine which previously had 10.3 installed. During the HW configuration no monitor (a ViewSonic E790F) was found, both the graphic (ATI Radeon 8500 series) and sound cards were found and configured no problem. The result of this was that on completing setup I had no window system, just a straight login. I rebooted the system in failsafe mode which gave me a window system. I looked at the options on the failsafe boot and noticed an option X11failsafe, which I then added to the normal boot option, rebooted the system, which again resulted in a windows system, and the system seems to be working as normal. Has anyone else seen this? Can anyone explain to me what has happened, or what occurred. Thanks Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2008-07-21 at 09:27 -0400, Peter Bloomfield wrote: ...
Has anyone else seen this? Can anyone explain to me what has happened, or what occurred.
Look at the logs when the problem occurs for hints. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIhJiRtTMYHG2NR9URAhExAJ4hpKr6Et5m9R7e8euN3rUvjnoQ1wCfTbAH 7uXmeE0VpnHzdO46LXPULKI= =Bu2+ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 21 July 2008 08:27:48 am Peter Bloomfield wrote:
I rebooted the system in failsafe mode which gave me a window system. I looked at the options on the failsafe boot and noticed an option X11failsafe, which I then added to the normal boot option, rebooted the system, which again resulted in a windows system, and the system seems to be working as normal.
Has anyone else seen this? Can anyone explain to me what has happened, or what occurred.
The X11failsafe will probably load VESA driver, like installation system. Check /etc/xorg.conf to see is you monitor configured and with what parameters. Check /var/log/Xorg.0.log to see why monitor wasn't recognized/used. -- Regards, Rajko http://en.opensuse.org/Portal needs helpful hands. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 21 July 2008 09:27, Peter Bloomfield wrote:
I had an interesting occurance during the install of OpenSuSE 11 on a machine which previously had 10.3 installed.
During the HW configuration no monitor (a ViewSonic E790F) was found, both the graphic (ATI Radeon 8500 series) and sound cards were found and configured no problem. The result of this was that on completing setup I had no window system, just a straight login.
I rebooted the system in failsafe mode which gave me a window system. I looked at the options on the failsafe boot and noticed an option X11failsafe, which I then added to the normal boot option, rebooted the system, which again resulted in a windows system, and the system seems to be working as normal.
I followed up both suggestions and having dug a little deeper I arrived with this. It appears that sax2 was failing to execute correctly, ie it failed during execution, somewhere around line 693 of the program init.pl I have two graphics chips, on the motherboard and ATI radeon 8500 series, so issuing the command 'sax2 -c 1' forcing it to point at the ATI card allowed me to configure the monitor and now I can boot without the X11failsafe. I am still 'non the wiser' as to why sax2 failed. If someone can let me know how to pipe the output of the command 'sax2 -a' to a log file I will post it here. I can log most of the ouput, but not the lines during the failure, where it prints which lines of which object the program failed at. Thanks for the suggestions, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, Jul 22, 2008 at 08:13:37AM -0400, Peter Bloomfield wrote:
If someone can let me know how to pipe the output of the command 'sax2 -a' to a log file I will post it here. I can log most of the ouput, but not the lines during the failure, where it prints which lines of which object the program failed at.
You are probably looking for a way to redirect the error output, try: $ [whatever command you used] 2>&1 If you want to learn more about the whole concept of output redirection: http://tldp.org/HOWTO/Bash-Prog-Intro-HOWTO-3.html does that help? cheers, Sonja -- Sonja Krause-Harder (skh@suse.de) SUSE Research & Development ----------------------------------------------------------------- SUSE Linux Products GmbH GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 22 July 2008 10:56, Sonja Krause-Harder wrote:
On Tue, Jul 22, 2008 at 08:13:37AM -0400, Peter Bloomfield wrote:
If someone can let me know how to pipe the output of the command 'sax2 -a' to a log file I will post it here. I can log most of the ouput, but not the lines during the failure, where it prints which lines of which object the program failed at.
You are probably looking for a way to redirect the error output, try:
$ [whatever command you used] 2>&1
If you want to learn more about the whole concept of output redirection: http://tldp.org/HOWTO/Bash-Prog-Intro-HOWTO-3.html
does that help?
I tried a number of combinations to redirect the output, but non saved the failed program listing to a file. Anybody else have any suggestions? Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 22 July 2008 07:13:37 am Peter Bloomfield wrote: ...
I am still 'non the wiser' as to why sax2 failed. If someone can let me know how to pipe the output of the command 'sax2 -a' to a log file I will post it here. I can log most of the ouput, but not the lines during the failure, where it prints which lines of which object the program failed at.
/var/log/SaX.log should be good enough for debugging. In any case it would be interesting to file bug report. -- Regards, Rajko http://en.opensuse.org/Portal needs helpful hands. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 22 July 2008 21:14, Rajko M. wrote:
On Tuesday 22 July 2008 07:13:37 am Peter Bloomfield wrote: ...
I am still 'non the wiser' as to why sax2 failed. If someone can let me know how to pipe the output of the command 'sax2 -a' to a log file I will post it here. I can log most of the ouput, but not the lines during the failure, where it prints which lines of which object the program failed at.
/var/log/SaX.log should be good enough for debugging. I looked in here but there does not appear to much helpful debugging information.
In any case it would be interesting to file bug report.
I have never filed a bug report, since I always assume that I have screwed something up, which is invariably the case. Here there was not much I could mess up during install, so will look into this. I would like to be able to save the listing from the program to put in the bug report, but have failed so far to do so. Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 23 July 2008 07:13:48 am Peter Bloomfield wrote:
On Tuesday 22 July 2008 21:14, Rajko M. wrote:
On Tuesday 22 July 2008 07:13:37 am Peter Bloomfield wrote: ...
I am still 'non the wiser' as to why sax2 failed. If someone can let me know how to pipe the output of the command 'sax2 -a' to a log file I will post it here. I can log most of the ouput, but not the lines during the failure, where it prints which lines of which object the program failed at.
/var/log/SaX.log should be good enough for debugging.
I looked in here but there does not appear to much helpful debugging information.
Actually helpful is XOrg.0.log, SaX.log and output of 'hwinfo -gfxcard'. Each
separately is not complete information. There is also third utility that I
can't recall the name.
There is difference in output of 'hwinfo -gfxcard' when you boot in runlevel 3
with onboard adapter enabled or disabled in BIOS. So far I recall it is fine
if primary adapter is the same as required with 'sax2 -c
In any case it would be interesting to file bug report.
I have never filed a bug report, since I always assume that I have screwed something up, which is invariably the case. Here there was not much I could mess up during install, so will look into this. I would like to be able to save the listing from the program to put in the bug report, but have failed so far to do so.
I wouldn't worry about that output as part of that is in SaX.log or Xorg.0.log. If guys that will debug problem need more they will tell what and how to obtain it. -- Regards, Rajko http://en.opensuse.org/Portal needs helpful hands. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
Carlos E. R. -
Peter Bloomfield -
Rajko M. -
Sonja Krause-Harder