Re: NVIDIA and Etch : WAS Re: Problems with GRUB and SATA
Question please... should the driver be 'nvidia' or 'nv', (if 'nvidia' - any suggestions as to what I am missing?) ... if it's should be 'nv' in any event .. then can someone help me find the settings for this to get the colours to be accurately displayed? It depends. IIRC 'nv' is the open source driver that comes with Xorg and 'nvidia' is the proprietary driver. Which one you use depends on what you want out of your card I suppose. Thanks Magnus, with the 'nv' all I get is basic graphics. The modules and various bits'n'pieces for the 3d acceleration and advanced elements all load and report (via the log files) as being 'ok', but each time (and I have now rebuilt the kernel with the proprietory driver pack 5 times with various options selected and deselected) I fire it up with 'nvidia' in the xorg.conf file it fails with warnings about no instance for NVIDIA and the X-server failing with a 'Caught signal 11'. Also note that there are two versions of the proprietary driver available in Debian (at least in Sid); the package names for the older one end with -legacy. On top of this there's a new version of the driver out, but it doesn't seem to have hit Sid yet AFAIU it removes support for some older cards. Yep, I was aware of that thanks I haven't gone the legacy route because this is meant to be a 'new' motherboard and revised NVIDIA chipset (NF-6100-406)... so I presumed that going 'legacy' would not be much use. Sorry I can't help you out more than this... /M Thanks for at least responding Magnus I have been asking the same questions now for days of various forums ... and folks must be getting as sick of me asking as I am of trying to get this thing to work. I have read dozens of trails about this 'Signal 11' ... but so far not one of them has thrown any light on it. (The error codes listed for the xserver are about as obscure as they could be ... at least the version I downloaded was). I must have done something really dumn... but I just can't figure this one out. I suspect it has somethign to do with the warning about there being no instance for NVIDIA at 00:1:3 (or 00:0:13 ... quite why they keep alternating is also a mystery to me). Ah well, ... as written .. thanks for responding at least. Ian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NVIDIA and Etch : WAS Re: Problems with GRUB and SATA
On Tue, 2007-03-27 at 13:05 +0100, Wackojacko wrote: I have read dozens of trails about this 'Signal 11' ... but so far not one of them has thrown any light on it. (The error codes listed for the xserver are about as obscure as they could be ... at least the version I downloaded was). Try commenting the PCI bus line out of the xorg.conf and see if the driver can auto detect the card. Otherwise, look at lspci -v for details of the bus. HTH Wackojacko OK, now I am really into DEEP water I have run the lspci command ... but I'm not too sure what it is telling me on a quick scan down this lot (below) I only see the entry for VGA graphics controller. Would you not expect to see something that looked like GeForce6 or DX9.0 or similar? Sorry folks this is now at the 'bleeding-edge' of my limited knowledge Does this list below give anyone a clue? Ian brutus:~# lspci -v 00:00.0 RAM memory: nVidia Corporation MCP61 Memory Controller (rev a1) Subsystem: ASRock Incorporation Unknown device 03ea Flags: bus master, 66MHz, fast devsel, latency 0 Capabilities: [44] HyperTransport: Slave or Primary Interface Capabilities: [dc] HyperTransport: MSI Mapping 00:01.0 ISA bridge: nVidia Corporation MCP61 LPC Bridge (rev a2) Subsystem: ASRock Incorporation Unknown device 03e0 Flags: bus master, 66MHz, fast devsel, latency 0 00:01.1 SMBus: nVidia Corporation MCP61 SMBus (rev a2) Subsystem: ASRock Incorporation Unknown device 03eb Flags: 66MHz, fast devsel, IRQ 11 I/O ports at ec00 [size=64] I/O ports at 5000 [size=64] I/O ports at 6000 [size=64] Capabilities: [44] Power Management version 2 00:01.2 RAM memory: nVidia Corporation MCP61 Memory Controller (rev a2) Subsystem: ASRock Incorporation Unknown device 03eb Flags: 66MHz, fast devsel 00:01.3 Co-processor: nVidia Corporation MCP61 SMU (rev a2) Subsystem: ASRock Incorporation Unknown device 03f4 Flags: 66MHz, fast devsel Memory at 8000 (32-bit, non-prefetchable) [disabled] [size=512K] 00:02.0 USB Controller: nVidia Corporation MCP61 USB Controller (rev a2) (prog-i f 10 [OHCI]) Subsystem: ASRock Incorporation Unknown device 03f1 Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 225 Memory at d000 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] Power Management version 2 00:02.1 USB Controller: nVidia Corporation MCP61 USB Controller (rev a2) (prog-i f 20 [EHCI]) Subsystem: ASRock Incorporation Unknown device 03f2 Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 209 Memory at dfffec00 (32-bit, non-prefetchable) [size=256] Capabilities: [44] Debug port Capabilities: [80] Power Management version 2 00:04.0 PCI bridge: nVidia Corporation MCP61 PCI bridge (rev a1) (prog-if 01 [Su btractive decode]) Flags: bus master, 66MHz, fast devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=32 Capabilities: [b8] Subsystem: ASRock Incorporation Unknown device 03f3 Capabilities: [8c] HyperTransport: MSI Mapping 00:05.0 Audio device: nVidia Corporation MCP61 High Definition Audio (rev a2) Subsystem: ASRock Incorporation Unknown device 0888 Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 11 Memory at dfff8000 (32-bit, non-prefetchable) [size=16K] Capabilities: [44] Power Management version 2 Capabilities: [50] Message Signalled Interrupts: Mask+ 64bit+ Queue=0/0 Enable- Capabilities: [6c] HyperTransport: MSI Mapping 00:06.0 IDE interface: nVidia Corporation MCP61 IDE (rev a2) (prog-if 8a [Master SecP PriP]) Subsystem: ASRock Incorporation Unknown device 03ec Flags: bus master, 66MHz, fast devsel, latency 0 I/O ports at ffa0 [size=16] Capabilities: [44] Power Management version 2 00:07.0 Bridge: nVidia Corporation MCP61 Ethernet (rev a2) Subsystem: ASRock Incorporation Unknown device 03ef Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 50 Memory at dfffd000 (32-bit, non-prefetchable) [size=4K] I/O ports at e480 [size=8] Capabilities: [44] Power Management version 2 Capabilities: [50] Message Signalled Interrupts: Mask+ 64bit+ Queue=0/3 Enable+ Capabilities: [6c] HyperTransport: MSI Mapping 00:08.0 IDE interface: nVidia Corporation MCP61 SATA Controller (rev a2) (prog-i f 85 [Master SecO PriO]) Subsystem: ASRock Incorporation Unknown device 03f6 Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 233 I/O ports at e400 [size=8] I/O ports at e080 [size=4] I/O ports at e000 [size=8] I/O ports at dc00 [size=4] I/O ports at d880 [size=16] Memory at dfffc000 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] Power
Re: NVIDIA and Etch : WAS Re: Problems with GRUB and SATA
Try commenting the PCI bus line out of the xorg.conf and see if the driver can auto detect the card. Otherwise, look at lspci -v for details of the bus. Oh and BTW. I had already tried that (and have just repeated it 'just in case') ... no effect whatsoever. same error-11 , same warnings. Ian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NVIDIA and Etch : WAS Re: Problems with GRUB and SATA
Ian, It sounds to me like your xorg.conf is still messed up. Can you post that too? Just the relevant Device and Screen sections should be enough. But you can put the whole thing here too. Then we should get a pretty good idea what is going on. Will do... but just now I have to go and get some work done... I only meant to spend 15-20 minutes on this this morning... and have just noticed the time oops I have meetings soon and I haven't even prepared for them yet. more later... thanks folks. Ian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NVIDIA and Etch : WAS Re: Problems with GRUB and SATA
snip xorg nvidia log (II) Initializing extension GLX Backtrace: 0: /usr/bin/X(xf86SigHandler+0x6d) [0x4802ed] 1: /lib/libc.so.6 [0x2ac51f460110] 2: /lib/libc.so.6(__ctype_tolower_loc+0x25) [0x2ac51f45a2c5] 3: /usr/bin/X(xf86nameCompare+0xfe) [0x4a4cde] 4: /usr/bin/X(InitInput+0x103) [0x45ea23] 5: /usr/bin/X(main+0x337) [0x430e57] 6: /lib/libc.so.6(__libc_start_main+0xda) [0x2ac51f44d4ca] 7: /usr/bin/X(FontFileCompleteXLFD+0x9a) [0x43026a] Fatal server error: Caught signal 11. Server aborting Ah! Seems to be a problem with the GLX extension, are you sure the nvidia-glx package matches the source from which you compiled the module? I have googled this error (last line of backtrace) and it appears others are having problems and it does seem to be the nvidia-glx package causing the problem. Bug#415878 (1) seems similar to your problem and suggests commenting the Load glx from xorg. Might want to try this and see if it loads (albeit without glx acceleration) and add to the bug report if necessary. HTH Wackojacko My thanks to Anthony, Joe, Magnus and especially to Jacko (can't bring myself to write 'Wackojacko') You were spot on... remove the Load GLX from xorg.conf and set the driver back to 'nvidia' and it started up perfectly ...well .'almost'. As you may recall from earlier posts I had a heavy pink cast over the KDE desktop it's still there, but now at least it goes away as soon as I start the nvidia-settings programme unfortunately, it returns when I switch to Gnome but as don't usually switch between display-managers it shouldn't be a major problem. Can I ask (and learn) then about the backtrace reporting. I presume than the backtrace always then applies to the last element on the log prior to it? I didn't know that (if correct).. so although I read the backtrace I thought it was telling me that step seven in the trace was the root problem (something to do with the fonts)... rather than the actual bugbear being the last thing in the log above the point where the backtrace begins. Is my assumption correct? Is it always so? If yes... then todays been helpful on two counts. So ... final question (if you don't mind) how do I add this to the bug report as you suggested? Sorry, bug reporting is also new to me. Thanks again folks... it really is very much appreciated Ian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: NVIDIA and Etch : WAS Re: Problems with GRUB and SATA
You could of snipped the unnecessary bits. Chris. errr.. that might be good advice Chris BUT, it kinda ASSumes that I knew what the 'unnecessary bits' were ... doesn't it? If I'd known that ... then I would have been able to spot the error instantly (as others did when they saw the full detailed listing). Thanks anyway. As written previously it's now at least resolved in that we know what the problem is/was and I have NVIDIA running (crippled.. but running). Ian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to compile
On Tue ... you wrote I have an AMD64 box and I was looking to install the AMD64 Etch port. Only problem with that is that I want either Gnome or preferably KDE to go with it, and that port doesn't include those environments. ... later you wrote in answer to this I'm running etch-amd64 as I type this in kmail.. ;) Do you mean you have KDE in Etch AMD64? I'm not too sure I understand the first part, with it's implied 'problem'. I have an AMD64 machine, ... I have installed, and have running Etch (in 64 bit mode) and also have KDE and GNOME desktops (and packages) installed. (I'm in Gnome now as I type this) I did have some difficulties with the new BIOS on the machine and how it was interrogating the SATA with SMART, and also with getting the full GLX 3d acceleration to work with my NVIDIA chipset BUT they are not what I believe you are seeing as the 'problem'. I didn't have any problems getting Gnome and KDE to install and work. What 'problem' are you anticipating? From my experience they both work fine (albeit the new NVIDIA driver upsets KDE colours if you switch between them... but that again is not a fault of the kernel (AFAIK). Ian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
