LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Desktop
User Name
Password
Linux - Desktop This forum is for the discussion of all Linux Software used in a desktop context.

Notices

Reply
 
Search this Thread
Old 03-16-2007, 03:38 AM   #16
Simon Bridge
Guru
 
Registered: Oct 2003
Location: Waiheke NZ
Distribution: Ubuntu
Posts: 9,211

Rep: Reputation: 197Reputation: 197

Assuming you have a LCD monitor - try adding a monitor section.
That is your only error - and X says that it is using some sort of default. It is possible that the default monitor config is incompatible with the nvidia driver.

Try this bit from Zetabill's post:
Code:
Section "Monitor"
    Identifier     "LCD_default"
    HorizSync       31.5 - 90.0
    VertRefresh     60.0 - 60.0
    Option         "DPMS"
EndSection
... at least this can be eliminated.
 
Old 03-16-2007, 04:41 AM   #17
GrapefruiTgirl
Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550
The difference between Slackware and Fedora are vast, I'm sure, as between many different Linuxes. But when it comes to the X server, and by extension, the xorg.conf file, all systems share the same stuff in this file, regardless of Linux distribution. The only exceptions *may* be from vastly differing "versions" of the X server.
And, I definitely agree with Simon on that last item: A monitor section should be added, using safe values such as those above to start with. In fact, at least having the usual minimum of required sections put into the file, eliminates the lack of them as suspect, if it still is not working properly for you.
 
Old 03-16-2007, 06:45 PM   #18
zetabill
Member
 
Registered: Oct 2005
Location: Rhode Island, USA
Distribution: Slackware, Xubuntu
Posts: 348

Rep: Reputation: 31
Caution to you when putting Horizsync and Vertrefresh values in. I included mine as an example and I had to google my laptop's LCD to get those values. If you have a CRT then you can possibly damage your unit by using wrong values.

But yes you still need a monitor section and you need those Modes in the display subsections as I described before. X just doesn't know how to output anything.

I'm also still curious as to why Fedora is having such a cow over this with your machine...

Check /etc/inittab for something like this:
Code:
c1:12345:respawn:/sbin/agetty 38400 tty1 linux
c2:12345:respawn:/sbin/agetty 38400 tty2 linux
c3:12345:respawn:/sbin/agetty 38400 tty3 linux
c4:12345:respawn:/sbin/agetty 38400 tty4 linux
c5:12345:respawn:/sbin/agetty 38400 tty5 linux
c6:12345:respawn:/sbin/agetty 38400 tty6 linux
If you have it and it's drastically different then post your inittab. These are the lines which spawn the Ctrl+Alt+F? gettys. If you have them already then it's definitely a kernel issue... probably with that nvidia kmod. Even if your X server crashes you should be able to get to one of those gettys but if your keyboard just dies then your kernel is probably having trouble. I don't think it would be "panicking" because you should be able to see those errors.

Ultimately Simon Bridge is correct... You may need help from a Fedora 6 user who has encountered this problem already. I last used Fedora at Core 4 and I'm baffled at how different it's becoming. It really is generating its own way of doing things lately...
 
Old 03-19-2007, 09:30 PM   #19
violettheconqueror
Member
 
Registered: Sep 2005
Location: California
Distribution: Fedora 7
Posts: 44

Original Poster
Rep: Reputation: 15
my inittab is different it has mingetty not agetty and no "c" just the number:

Code:
#
# inittab       This file describes how the INIT process should set up
#               the system in a certain run-level.
#
# Author:       Miquel van Smoorenburg, <miquels@drinkel.nl.mugnet.org>
#               Modified for RHS Linux by Marc Ewing and Donnie Barnes
#

# Default runlevel. The runlevels used by RHS are:
#   0 - halt (Do NOT set initdefault to this)
#   1 - Single user mode
#   2 - Multiuser, without NFS (The same as 3, if you do not have networking)
#   3 - Full multiuser mode
#   4 - unused
#   5 - X11
#   6 - reboot (Do NOT set initdefault to this)
# 
id:3:initdefault:

# System initialization.
si::sysinit:/etc/rc.d/rc.sysinit

l0:0:wait:/etc/rc.d/rc 0
l1:1:wait:/etc/rc.d/rc 1
l2:2:wait:/etc/rc.d/rc 2
l3:3:wait:/etc/rc.d/rc 3
l4:4:wait:/etc/rc.d/rc 4
l5:5:wait:/etc/rc.d/rc 5
l6:6:wait:/etc/rc.d/rc 6

# Trap CTRL-ALT-DELETE
ca::ctrlaltdel:/sbin/shutdown -t3 -r now

# When our UPS tells us power has failed, assume we have a few minutes
# of power left.  Schedule a shutdown for 2 minutes from now.
# This does, of course, assume you have powerd installed and your
# UPS connected and working correctly.  
pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down"

# If power was restored before the shutdown kicked in, cancel it.
pr:12345:powerokwait:/sbin/shutdown -c "Power Restored; Shutdown Cancelled"


# Run gettys in standard runlevels
1:2345:respawn:/sbin/mingetty tty1
2:2345:respawn:/sbin/mingetty tty2
3:2345:respawn:/sbin/mingetty tty3
4:2345:respawn:/sbin/mingetty tty4
5:2345:respawn:/sbin/mingetty tty5
6:2345:respawn:/sbin/mingetty tty6

# Run xdm in runlevel 5
x:5:once:/etc/X11/prefdm -nodaemon
 
Old 03-19-2007, 09:55 PM   #20
inspiron_Droid
Member
 
Registered: Dec 2006
Distribution: Debian (Wheeze)
Posts: 391

Rep: Reputation: Disabled
I know for a fact that If you went to mepis which is based on Ubuntu you could have that pesky nvedia rendering problem solve from square one.
 
Old 03-19-2007, 10:28 PM   #21
GrapefruiTgirl
Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550
Hi violettheconqueror..

I commend your determination. Good to see you're still at it, but how unfortunate that this crazy thing is giving you such a hard time. That sux. ..and after just having gone through all the pages in the Fedora forum, I'm some glad I found Slackware. Some of the issues in Fedora seem pretty overwhelming.
Now, you've probably browsed the Fedora forum too already, and if so, then sorry for providing you with stuff you have probably already seen, but I figured I would put some links here from the Fedora forum, regarding FC and nVidia..
http://www.linuxquestions.org/questi...d.php?t=535610
http://www.linuxquestions.org/questi...d.php?t=420876
http://www.linuxquestions.org/questi...d.php?t=534504
http://www.linuxquestions.org/questi...d.php?t=529071

This last one looks worth a good slow read, as the problem is nearly identical to yours, and there's an Xorg.conf file in there for FC6 with an nVidia card, and I believe at the end of the thread the problem got fixed. Not for sure, I didn't read every word, but check it out.

Seems FC6 and nVidia are an unhappy marriage.

Best of luck! Don't give up..
PS: Here's a google result too, with lots of FC6/nVidia/xorg.conf links:
http://www.google.com/search?q=xorg....fficial&hs=nA9

Last edited by GrapefruiTgirl; 03-19-2007 at 10:30 PM.
 
Old 03-20-2007, 09:20 PM   #22
violettheconqueror
Member
 
Registered: Sep 2005
Location: California
Distribution: Fedora 7
Posts: 44

Original Poster
Rep: Reputation: 15
I added the moniter section today, and tested it, still no change. I am using an LCD moniter, its an HYvision mv178 and google is failing at finding detailed technical information on it, I could find nothing about max refresh rates, just color depths and things like that, the hyvision website is terrible and has no usefull information on it.

here is my xorg.conf now:

Code:
# Xorg configuration created by pyxf86config

Section "ServerLayout"
	Identifier     "Default Layout"
	Screen      0  "Screen0" 0 0
	InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
	ModulePath   "/usr/lib/xorg/modules/extensions/nvidia"
	ModulePath   "/usr/lib/xorg/modules"
EndSection

Section "InputDevice"
	Identifier  "Keyboard0"
	Driver      "kbd"
	Option	    "XkbModel" "pc105"
	Option	    "XkbLayout" "us"
EndSection

Section "Monitor"
    Identifier     "LCD_default"
    HorizSync       31.5 - 90.0
    VertRefresh     60.0 - 60.0
    Option         "DPMS"
EndSection

Section "Device"
	Identifier  "Videocard0"
	Driver      "nvidia"
	Option	    "AddARGBGLXVisuals" "True"
EndSection

Section "Screen"
	Identifier "Screen0"
	Device     "Videocard0"
	Monitor    "LCD_default"
	DefaultDepth     24
	SubSection "Display"
		Viewport   0 0
		Depth     24
		Modes     "1280x1024" "1024x768" "800x600" "640x480"
	EndSubSection
EndSection
perhaps I could add lower "depth"s (im assuming this refers to color depth).
does anyone see something obviously wrong with this setup?

grapefruitgirl: I read that last thread on the fedora forums, and it wasnt applicable although the situation was very similar, because I only have a single-head setup.

I still entertain the possibility of x picking the wrong port on my video card, however wouldnt my current moniter say "no signal" or something of that sort instead of just go black? (its the glowing black, not that "im turned off" black) Also those values in my "moniter" section probably arn't out of range of my moniter, because my moniter tells me if the signal is out of range.

Thank you all for your input so-far.
 
Old 03-20-2007, 09:51 PM   #23
GrapefruiTgirl
Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550
You are RIGHT, it is rotten trying to find specs on that thing. However, I did come across ONE THING that may be very key to the problem. The monitor is apparently Analog-in ONLY, meaning that if the card is not detecting the display properties correctly, and is sending a digital signal, it won't work. Try adding the 3 lines below to either the screen section. Of all of them, the middle one would be the one to eliminate first. But the 1st and 3rd may work
Otherwise, I can't see a single thing wrong with your file.

Option "ConnectedMonitor" "TV"
Option "TVStandard" "NTSC-M"
Option "TVOutFormat" "COMPOSITE"

And here is the link to the spec sheet, which I presume you found already.
http://www.megavisionsys.com/product...sp?model=MV178
It doesn't specify the refresh rates, of all things not to specify . As it is analog, you are probably safe using 60.0. In fact, why not remove the second 60 you have there? You only need one of them.

Last edited by GrapefruiTgirl; 03-20-2007 at 10:07 PM.
 
Old 03-20-2007, 09:53 PM   #24
violettheconqueror
Member
 
Registered: Sep 2005
Location: California
Distribution: Fedora 7
Posts: 44

Original Poster
Rep: Reputation: 15
I found something interesting on the nv forums, however i dont fully understand it:

"setting NvAGP[in xorg.conf] to 0 fixed the problem."

I dont know what this is, or where to add it in xorg.conf...anyone familiar with this? The thread goes on to say that setting the AGP rate lower in either the driver or the system BIOS, any ideas on what that means or how one would do that?

heres a link to the thread if you'd like to read it: http://www.nvnews.net/vbulletin/show...ht=fedora+core

still reading on...
 
Old 03-20-2007, 09:55 PM   #25
GrapefruiTgirl
Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550
OH, and finally, the monitor is DDC enabled, meaning it should be able to be probed for possible settings and specs, and then the server can determine what to use. But save this option for now.
We'll come back to it as required.

And that line you posted means "Turn off nVidia AGP (Accelerated Graphics Processing)". My bios does not have a setting for it, however, it DOES have an option which I can select whether the AGP slot is treated as AGP or standard PCI by default.
My AGP slot is 4x. Acelerated cards can work at a MAXimum of 8x. Standard PCI card is likely 1x or 2x

Last edited by GrapefruiTgirl; 03-20-2007 at 09:58 PM.
 
Old 03-20-2007, 10:02 PM   #26
GrapefruiTgirl
Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550
Here is the data from the section in my nVidia README pertaining to the NvAGP option.
X Config Options

Option "NvAGP" "integer"

Configure AGP support. Integer argument can be one of:
Value Behavior
0 disable AGP
1 use NVIDIA's internal AGP support, if possible
2 use AGPGART, if possible
3 use any AGP support (try AGPGART, then NVIDIA's AGP)

Please note that NVIDIA's internal AGP support cannot work if AGPGART is either statically compiled into your kernel or is built as a module and loaded into your kernel. Please see Appendix F, Configuring AGP for details. Default: 3.
 
Old 03-20-2007, 10:06 PM   #27
GrapefruiTgirl
Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550
I am flipping thru the Apendix F about adjusting the AGP settings inside the driver.
It involves actually changing some code in the extracted binary driver archive. Not fun, but doable.

Also Violet, what is the motherboard in your machine, and the CPU type? The README details some known bugs and issues with some types of processors and motherboards.
 
Old 03-20-2007, 10:22 PM   #28
violettheconqueror
Member
 
Registered: Sep 2005
Location: California
Distribution: Fedora 7
Posts: 44

Original Poster
Rep: Reputation: 15
my motherboard is a ASUS K8V-X SE, my processor is an AMD64 2800. Here is my lspci output just in case you feel like punnishing yourself by reading it...I dont understand most of it but it may be useful:

Code:
[root@localhost violet]# lspci
bash: lspci: command not found
[root@localhost violet]# /sbin/lspci
00:00.0 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
00:00.1 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
00:00.2 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
00:00.3 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
00:00.4 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
00:00.7 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South]
00:0c.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 61)
00:0c.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 61)
00:0c.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 63)
00:0e.0 PCI bridge: Pericom Semiconductor Unknown device 8148
00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80)
00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South]
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
00:11.6 Communication controller: VIA Technologies, Inc. AC'97 Modem Controller (rev 80)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:00.0 VGA compatible controller: nVidia Corporation NV40 [GeForce 6800 XT] (rev a1)
02:08.0 USB Controller: NEC Corporation USB (rev 41)
02:08.1 USB Controller: NEC Corporation USB (rev 41)
02:08.2 USB Controller: NEC Corporation USB 2.0 (rev 02)
02:09.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46)
02:0a.0 RAID bus controller: Silicon Image, Inc. PCI0680 Ultra ATA-133 Host Controller (rev 02)
im gonna try your analog moniter suggestion in a minute here grapefruitgirl thanks

PS: where is the xorg README and the apendix F you speak of? I may bennifit from reading them, if not for this problem just for knowing more about xorg

Last edited by violettheconqueror; 03-20-2007 at 10:23 PM.
 
Old 03-20-2007, 10:29 PM   #29
GrapefruiTgirl
Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550Reputation: 550
Actually, I am reading the nVidia driver README, which I downloaded from nVidia. They make it available online in a page by page format, so I just loaded up all the pages in my browser in tabs, copied and pasted them all into one big file (except the Contents Table and introduction stuff) and then I formatted the file a little bit for clarity.
You are welcome to it, if you would like me to email it to you.
EDIT - I did email it, but if the format of it is all screwy, reply to my email and I will send it as an attachment if you like.

Also, in it, Appendix M is about the /Proc directory on your machine, where a lot of nVidia-driver and card and AGP info and errors gets logged, apparently..

Last edited by GrapefruiTgirl; 03-20-2007 at 10:49 PM.
 
Old 03-20-2007, 11:15 PM   #30
violettheconqueror
Member
 
Registered: Sep 2005
Location: California
Distribution: Fedora 7
Posts: 44

Original Poster
Rep: Reputation: 15
first off thanks for sending me the README i'll read through it.

I did try your suggestion of adding those lines to my xorg.conf, and no luck same exact problem, here are the two configurations i tried:

Code:
# Xorg configuration created by pyxf86config

Section "ServerLayout"
	Identifier     "Default Layout"
	Screen      0  "Screen0" 0 0
	InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
	ModulePath   "/usr/lib/xorg/modules/extensions/nvidia"
	ModulePath   "/usr/lib/xorg/modules"
EndSection

Section "InputDevice"
	Identifier  "Keyboard0"
	Driver      "kbd"
	Option	    "XkbModel" "pc105"
	Option	    "XkbLayout" "us"
EndSection

Section "Monitor"
    Identifier     "LCD_default"
    HorizSync       31.5 - 90.0
    VertRefresh     60.0
    Option         "DPMS"
EndSection

Section "Device"
	Identifier  "Videocard0"
	Driver      "nvidia"
	Option	    "AddARGBGLXVisuals" "True"
	Option	    "ConnectedMonitor" "TV"
	Option	    "TVStandard" "NTSC-M"
	Option 	    "TVOutFormat" "COMPOSITE"
EndSection

Section "Screen"
	Identifier "Screen0"
	Device     "Videocard0"
	Monitor    "LCD_default"
	DefaultDepth     24
	SubSection "Display"
		Viewport   0 0
		Depth     24
		Modes     "1280x1024" "1024x768" "800x600" "640x480"
	EndSubSection
EndSection
and this one also:

Code:
# Xorg configuration created by pyxf86config

Section "ServerLayout"
	Identifier     "Default Layout"
	Screen      0  "Screen0" 0 0
	InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
	ModulePath   "/usr/lib/xorg/modules/extensions/nvidia"
	ModulePath   "/usr/lib/xorg/modules"
EndSection

Section "InputDevice"
	Identifier  "Keyboard0"
	Driver      "kbd"
	Option	    "XkbModel" "pc105"
	Option	    "XkbLayout" "us"
EndSection

Section "Monitor"
    Identifier     "LCD_default"
    HorizSync       31.5 - 90.0
    VertRefresh     60.0
    Option         "DPMS"
EndSection

Section "Device"
	Identifier  "Videocard0"
	Driver      "nvidia"
	Option	    "AddARGBGLXVisuals" "True"
EndSection

Section "Screen"
	Identifier "Screen0"
	Device     "Videocard0"
	Monitor    "LCD_default"
	DefaultDepth     24
	SubSection "Display"
		Viewport   0 0
		Depth     24
		Modes     "1280x1024" "1024x768" "800x600" "640x480"
		Option	    "ConnectedMonitor" "TV"
		Option	    "TVStandard" "NTSC-M"
		Option 	    "TVOutFormat" "COMPOSITE"
	EndSubSection
EndSection
See anything I obviously skrewed up on?

after that, I was looking through my BIOS for stuff related to AGP and I found these options, I dont know what most of them mean:

Primary Graphis Adapter [agp]
search for MPA resources [yes]
Vlink 8x support [enabled]
AGP mode [8x]
AGP fast Write [Enabled]
Graphics apature size [64 MB]
AGP 3.0 Calibration cycle[Disabled]
DBI output for AGP trans [Disabled]

Im not sure if any of these might help me or not. some other things that may or may not be important, when I boot up I get an error saying "no PSB or ACPI _Pss Objects found" relating to the kernel somehow, could that be a problem?
 
  


Reply

Tags
3d, dri, driver, nvidia


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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 Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
(nvidia) First startx = blank screen, second startx = works ?!? BuckRogers01 Linux - Hardware 2 04-07-2006 06:26 PM
Nvidia Driver "Virtual Screen" Quirk tionik06 Linux - Hardware 4 07-31-2005 07:07 AM
Blank screen after "startx" after reboot after install cg from nvidia rozky Linux - Software 2 04-04-2005 09:49 PM
Blank screen untril I "startx" after boot GML3G0 Linux - Software 8 03-26-2005 03:42 PM


All times are GMT -5. The time now is 08:45 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration