Re: [SLE] Black screen after NVidia update - 2nd posting

• Previous message: BandiPat: "Re: [SLE] cannot access modem"
• In reply to: Curtis Rey: "Re: [SLE] Black screen after NVidia update - 2nd posting"
• Next in thread: Carlos E. R.: "Re: [SLE] Black screen after NVidia update - 2nd posting"
• Reply: Carlos E. R.: "Re: [SLE] Black screen after NVidia update - 2nd posting"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

To: suse-linux-e@suse.com
Date: Fri, 12 Sep 2003 23:20:28 +0200

On Friday 12 September 2003 07:07, Curtis Rey wrote:
<SNIP>
>
> Ok, this sounds like the ever popular monitor fun with sax2. I
> unfortunately don't have as much experience with LCDs. I might suggest
> that you could try the command
>
> SaX2 -r
>
Did this :
* boot to init 3 (using my 'good' XF86Config)
* sax2 -r
  -> sax2 starts up with a very fuzzy screen (almost unreadable)
* changed monitor from 'vesa' to 'lcd' 1024x768@60Hz
  -> same fuzzy screen
* cancel sax2
* then I replaced XF86Config with the nvidia-version
* reboot into init 3
* lsmod
  -> shows no 'agpgart' and no 'nvidia'
* sax2 -r
  -> again the fuzzy screen
* cancel sax2
* goto init 5 (so, with the nvidia-XF86Config) just to try
  -> black screen
* CTRL-ALT-DEL does not work, so : cut power
* reboot to init 3, replace XF86Config with the nv-version
* goto init 5, -> everything OK.

NOW HERE IS A STRANGE THING :
When (in init 5 mode) I start sax2 from within a terminal, then I get a normal
- good - sax screen.
Then I cancel sax2, go down to init 3, and start sax2 in command mode, and
then I get the fuzzy screen again I mentioned before.
But I am using the "good" nv-version of XF86Config !!
Looks like something is wrong with sax, regardless the XF86Config used ??

> I strongly suspect that this is all about the monitor/video card/drivers
> not being set up in the correct fashion (through no fault of yours). I
> situations like this I have had to hand modify the XF86Config file in the
> v-sync/h-sync do lower levels, and also at time tinker with the modelines.
> As far as the modelines, there are a couple of ways to try to see if
> they're reconfiged. One is to use
>
> sax2 -x
Did this too.
After sax2 -x I got the @!#-fuzzy screen again.

BTW, someone told me that with TFT screens (like mine) there is no
vsync/hsync. He said there is only a 'reaction time'. Is that not true ?
Anyway, I could not find any information about vsync/hsync in the
documentation of my notebook.
Also, modelines is a new phenomenon to me.
I'm afraid I'll have some studying to do before I know how to manipulate this.

> The other methods is from the XF86.org site and tells how to manually probe
> the modeline timings for each resolution. They also have sections that
> explains setup and troubleshooting LCDs.
This is probably where I must start my study !? ;-(
Have not done so yet.

> LCDs can be a specific pain in the ass (nvidia readme also has a section for
> LCDs).
The NVidia Readme LCD section does not help for this problem, unless I missed
something.

> You should be able to put back in the NVIDIA specific XF86Config file and
> at boot up in the command section (in lilo/grub) issue the command "init
> 3". Then you boot to a non-X mode but if the nvidia kernel driver is
> installed it should load the modules. You can issue the "lsmod" and see if
> nvidia and agpgart modules are loaded. Then you can copy the XF86config
> file back again.
OK, done so -- see log above.
What I don't understand is : how can we expect to see something about XF86 at
this level when X is not started yet ?

<SNIP>
> Also you need to look in /etc/module.conf file and see if the line "alias
> char-major-195 nvidia". If it's not then this explains why you get a black
> screen.
This is OK. That line is present.

<SNIP>
> I really think that this is all about the LCD and something specific to the
> monitor. If you have the specs for the monitor (i.e. the notebook manual)
> with the v-sync/h-sync/refresh rates then you might be able to check this
> against the XF86Config file.
Don't have this information. See my remarks above.

> Keep trying, we'll nail this yet. :)
Thanks for your encouragement (and your continued assistence).
I really need this, because I have been tempted several times to drop the
issue and keep working in the nv-mode.

Greetings,

-- 
Jan Elders
Nuenen
the Netherlands
-- 
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@suse.com

• Previous message: BandiPat: "Re: [SLE] cannot access modem"
• In reply to: Curtis Rey: "Re: [SLE] Black screen after NVidia update - 2nd posting"
• Next in thread: Carlos E. R.: "Re: [SLE] Black screen after NVidia update - 2nd posting"
• Reply: Carlos E. R.: "Re: [SLE] Black screen after NVidia update - 2nd posting"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]