[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: NVidia driver on FC1 (tech prob not idiological)



Am Mi, den 09.06.2004 schrieb Gary Stainburn um 18:33:

> > Try what the readme offers:
> >
> > Option "IgnoreEDID" "boolean"
> 
> Which section am I supposed to put this in? Also, which readme were you 
> looking at. I downloaded the one from the same web page as the driver and 
> couldn't find any mention of it.

Of course in the section Device where you did set the driver to nvidia
instead of nv. The readme is on the nvidia.com site:

ftp://download.nvidia.com/XFree86/Linux-x86/1.0-5336/README

> > and adjust the frequency settings as the refresh rates seem to not fit.
> > You may to check whether a different default resolution works.
> 
> I dont know how to change the frequency used.  I did try to change the colour 
> depth but the server refused to start complaining about not knowning how to 
> handle it (I can't remember the exact error but I tried values of both 24 and 
> 32).

In your XF86.Config you have:

Section "Monitor"
	Identifier   "Monitor0"
	VendorName   "Monitor Vendor"
	ModelName    "LCD Panel 1400x1050"
	HorizSync    31.5 - 90.0
	VertRefresh  59.0 - 75.0

And from the log it is to be seen that the refresh rates given are too high. Adjust them to proper values, like maximum 60 for the vertical refresh.
See you own posted log!

(WW) NVIDIA(0): The user specified HorizSync "31.500-90.000" has been adjusted
(WW) NVIDIA(0):      to "31.500-65.000" (the intersection with EDID-specified
(WW) NVIDIA(0):      HorizSync "29.000-65.000")
(WW) NVIDIA(0): The user specified VertRefresh "59.000-75.000" has been
(WW) NVIDIA(0):      adjusted to "59.000-60.000" (the intersection with
(WW) NVIDIA(0):      EDID-specified VertRefresh "0.000-60.000"
(II) NVIDIA(0): Monitor0: Using hsync range of 31.50-65.00 kHz
(II) NVIDIA(0): Monitor0: Using vrefresh range of 59.00-60.00 Hz
(II) NVIDIA(0): Clock range:  12.00 to 400.00 MHz

The color depth of 16 (thousands of colors) is ok. Be aware that if you change the DefaultDepth you too have to add or change the Depth too, so that it exists.
To test a different resolution comment the resolution line with a leading # and create a new one where the biggest resolution is less, like 1024x768. 

> I tried putting acpi=on in grub.conf. I had to also put pci=noacpi to get rid 
> of a number of error messages.  However, I did still get errors complaining  
> about toshiba_acpi.o module but it goes off the screen too quick and dmesg 
> doesn't show it.

That is normal with the toshiba_acpi.o modules as that is hard coded in
the /etc/rc.sysinit script and probes for all ACPI modules. Just ignore
it.

> ACPI is now working though, because the battery icon in the systray now works 
> right. (I tried sound again but it still isn't working).

Which soundcard/soundchip? Is it supported by OSS or do you need ALSA?
If not sure, then google is your friend ;)

Alexander


-- 
Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13
Fedora GNU/Linux Core 2 (Tettnang) on Athlon CPU kernel 2.6.5-1.358 
Serendipity 19:06:05 up 7 days, 19:24, load average: 0.16, 0.33, 0.27 

Attachment: signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]