openSUSE Forums > Archives > Novell Archives » Starting Suse = Losing Signal to Monitor

Go Back   openSUSE Forums > Archives > Novell Archives
Forums FAQ Members List Search Today's Posts Mark Forums Read


Novell Archives Archived content from Novell openSUSE support forums

 
Page 1 of 2 1 2
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 08-May-2006, 11:36
nick800@gmail.com
Guest
 
Posts: n/a
Default Starting Suse = Losing Signal to Monitor

Ok, I just installed Suse 10 enterprise on a new system, everything worked
fine, it starts up, gives me the options of starting suse 10 or suse 10 in
bash mode. If I start it in suse 10, it loads up everything then right when
it's about to start up I lose monitor signal.

Anyone got any ideas as to how to find out whats going on?

How do I adjust monitor settings through bash mode?

Any help would be greatly appreciated.
  #2 (permalink)  
Old 08-May-2006, 12:02
Andres Rodriguez Guapacha
Guest
 
Posts: n/a
Default Re: Starting Suse = Losing Signal to Monitor

You can check your monitor's vertical and horizontal refresh rates in the
proper manual, then init in runlevel 3 (bash) and call YaST to configure
the refresh rates in the Hardware -> Graphics Card and Monitor section.

Or directly calling SaX2, but I prefer the other way (I do not know why)=P



--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
  #3 (permalink)  
Old 08-May-2006, 12:33
nick800@gmail.com
Guest
 
Posts: n/a
Default Starting Suse = Losing Signal to Monitor

> Ok, I just installed Suse 10 enterprise on a new system, everything worked
> fine, it starts up, gives me the options of starting suse 10 or suse 10 in
> bash mode. If I start it in suse 10, it loads up everything then right when
> it's about to start up I lose monitor signal.
>
> Anyone got any ideas as to how to find out whats going on?
>
> How do I adjust monitor settings through bash mode?
>
> Any help would be greatly appreciated.


side note, when I run yast, and choose graphics and monitor, it loses
signal directly after I hit enter.

all of the other hardware checks work properly.

the display is done through VIA km400
  #4 (permalink)  
Old 08-May-2006, 12:35
nick800@gmail.com
Guest
 
Posts: n/a
Default Re: Starting Suse = Losing Signal to Monitor

> You can check your monitor's vertical and horizontal refresh rates in th=
> e =
>
> proper manual, then init in runlevel 3 (bash) and call YaST to configure=
> =
>
> the refresh rates in the Hardware -> Graphics Card and Monitor section.
>
> Or directly calling SaX2, but I prefer the other way (I do not know why)=
> =3DP
>
>
>
> -- =
>
> Using Opera's revolutionary e-mail client: http://www.opera.com/mail/


system loses signal when I try to enter the graphics card and monitor
section and when I try ot run sax2..
  #5 (permalink)  
Old 08-May-2006, 13:40
Uwe Buckesfeld
Guest
 
Posts: n/a
Default Re: Starting Suse = Losing Signal to Monitor

On 05/08/2006 nick800@gmail.com wrote:
> system loses signal when I try to enter the graphics card and monitor
> section and when I try ot run sax2..


Double check, you are at runlevel 3 at this time?
Try
sax2 -r
from the command line.

Uwe

--
Novell Support Connection Volunteer SysOp
Please don't send me support related e-mail unless I ask you to do so.
  #6 (permalink)  
Old 08-May-2006, 14:10
nick800@gmail.com
Guest
 
Posts: n/a
Default Re: Starting Suse = Losing Signal to Monitor

> On 05/08/2006 nick800@gmail.com wrote:
> > system loses signal when I try to enter the graphics card and monitor
> > section and when I try ot run sax2..

>
> Double check, you are at runlevel 3 at this time?
> Try
> sax2 -r
> from the command line.
>
> Uwe
>


yes I was always at runlevel 3
sax2 -r results in the same effect as sax2, when it tries to startup the
signal to the monitor stops

I tried using a different monitor, and tried setting the display at 800x600
60 using gtf, and 600x400 30, neither worked.

The only things I can find online have to deal with getting the unichrome
driver for the via km400 chipset, but I downloaded it to a cd and have no
idea how to install it as I'm a linux noob, it's a gzip file.


  #7 (permalink)  
Old 08-May-2006, 15:20
linuxjoe
Guest
 
Posts: n/a
Default Re: Starting Suse = Losing Signal to Monitor

nick800@gmail.com wrote:

> yes I was always at runlevel 3
> sax2 -r results in the same effect as sax2, when it tries to startup the
> signal to the monitor stops


Try sax2 -r -m0=fvdev
  #8 (permalink)  
Old 08-May-2006, 23:00
Uwe Buckesfeld
Guest
 
Posts: n/a
Default Re: Starting Suse = Losing Signal to Monitor

On 05/08/2006 linuxjoe wrote:
> Try sax2 -r -m0=fvdev


fbdev?

Uwe

--
Novell Support Connection Volunteer SysOp
Please don't send me support related e-mail unless I ask you to do so.
  #9 (permalink)  
Old 09-May-2006, 07:33
linuxjoe
Guest
 
Posts: n/a
Default Re: Starting Suse = Losing Signal to Monitor

Uwe Buckesfeld wrote:

> fbdev?


yep.... typed to fast
  #10 (permalink)  
Old 14-May-2006, 08:23
Rajko M
Guest
 
Posts: n/a
Default Re: Starting Suse = Losing Signal to Monitor

nick800@gmail.com wrote:

>> On 05/08/2006 nick800@gmail.com wrote:
>> > system loses signal when I try to enter the graphics card and monitor
>> > section and when I try ot run sax2..

>>
>> Double check, you are at runlevel 3 at this time?
>> Try
>> sax2 -r
>> from the command line.
>>
>> Uwe
>>

>
> yes I was always at runlevel 3
> sax2 -r results in the same effect as sax2, when it tries to startup the
> signal to the monitor stops
>
> I tried using a different monitor, and tried setting the display at
> 800x600 60 using gtf, and 600x400 30, neither worked.
>
> The only things I can find online have to deal with getting the unichrome
> driver for the via km400 chipset, but I downloaded it to a cd and have no
> idea how to install it as I'm a linux noob, it's a gzip file.


Hi Nick,

First look at this:
http://www.viaarena.com/default.aspx...hrome&Filter=1
The onboard Unichrome is not for gaming.

From viaarena.com:
http://www.viaarena.com/default.aspx...&ArticleID=376
I get this:
http://www.openchrome.org/
where I used Binary Packages link:
http://wiki.openchrome.org/tikiwiki/...inary+packages
Link for SUSE points to nonexisting directory which means that they don't
really have any support. The
http://ftp.gwdg.de/pub/suse/i386/supplementary/X/Xorg
has only versions 6.8.1 and 6.8.2.

The source
http://www.openchrome.org/trac
is for guys that have time and skills, not for users.

So back to google, gives:
http://forums.suselinuxsupport.de/lo...hp/t14324.html
and it has link to here:
http://unichrome.sourceforge.net/
That I have seen before in google results, but I liked to see some third
party opinions.
In section Unichrome X driver you have link to "releases/files":
http://sourceforge.net/project/showf...kage_id=166541
My guess is that you downloaded xf86-video-unichrome-0.2.5.tar.gz .

As I can see in README precondition is that "sufficiently built X tree is
present (see 1.2 otherwise)" and the section 1.2 is to be written. Default
Xorg source compiled and installed doesn't work well in SUSE, checked.
What would happen after compilation against it is probably the same that you
have right now.

I would like to see hidden .X.err file that is in user home directory, and
maybe /var/log/Xorg.0.log that you can access as root user. That is just to
check that your problems are not related to missconfigured adapter by sax2
like too high resolution that monitor can't present, or similar, before
going to https://bugzilla.novell.com and file bug report.

--
Regards,
Rajko M.
 
Page 1 of 2 1 2

Bookmarks


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




 

Search Engine Friendly URLs by vBSEO 3.3.0 RC2