> >
> >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 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 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 debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Ian Broadbent wrote:
>>> 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 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 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).
>

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.

> Ah well, ... as written .. thanks for responding at least.
>
> Ian

HTH

Wackojacko


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

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 80000000 (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 dffff000 (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 Management version 2
Capabilities: [b0] Message Signalled Interrupts: Mask- 64bit+
Queue=0/2
Enable-
Capabilities: [cc] HyperTransport: MSI Mapping

00:09.0 PCI bridge: nVidia Corporation MCP61 PCI Express bridge (rev a2)
(prog-i
f 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
Capabilities: [40] Subsystem: ASRock Incorporation Unknown
device 03e8
Capabilities: [48] Power Management version 2
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+
Queue=0/1
Enable+
Capabilities: [60] HyperTransport: MSI Mapping
Capabilities: [80] Express Root Port (Slot+) IRQ 0

00:0b.0 PCI bridge: nVidia Corporation MCP61 PCI Express bridge (rev a2)
(prog-i
f 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
Capabilities: [40] Subsystem: ASRock Incorporation Unknown
device 03e9
Capabilities: [48] Power Management version 2
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+
Queue=0/1
Enable+
Capabilities: [60] HyperTransport: MSI Mapping
Capabilities: [80] Express Root Port (Slot+) IRQ 0

00:0c.0 PCI bridge: nVidia Corporation MCP61 PCI Express bridge (rev a2)
(prog-i
f 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
Capabilities: [40] Subsystem: ASRock Incorporation Unknown
device 03e9
Capabilities: [48] Power Management version 2
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+
Queue=0/1
Enable+
Capabilities: [60] HyperTransport: MSI Mapping
Capabilities: [80] Express Root Port (Slot+) IRQ 0

00:0d.0 VGA compatible controller: nVidia Corporation Unknown device
03d1 (rev a
2) (prog-if 00 [VGA])
Subsystem: ASRock Incorporation Unknown device 03d1
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 10
Memory at de000000 (32-bit, non-prefetchable) [size=16M]
Memory at c0000000 (64-bit, prefetchable) [size=256M]
Memory at dd000000 (64-bit, non-prefetchable) [size=16M]
Expansion ROM at dffc0000 [disabled] [size=128K]
Capabilities: [48] Power Management version 2
Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+
Queu Enable-

00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
Hy nsport Technology Configuration
Flags: fast devsel
Capabilities: [80] HyperTransport: Host or Secondary Interface

00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
Ad Map
Flags: fast devsel

00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
DR troller
Flags: fast devsel

00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron]
Mi neous Control
Flags: fast devsel
Capabilities: [f0] #0f [0010]




--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

> 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 debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Ian Broadbent wrote:
>> 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
>

OK, rename the current xorg file and rerun dpkg-reconfigure xserver-xorg
and select nvidia, leave the PCI BUS empty and restart X.

Also post the output of lspci -v |grep VGA (should show video
controller) and /var/log/xorg if no luck.

HTH

Wackojacko

PS no need to CC me I am subscribed to the list.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On 27 Mar 2007, Ian Broadbent wrote:
> > >
> > >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 me find the settings for
> > >this to get the colours to be accurately displayed?
> >
[snip]

Have you tried the fglrx packages (fglrx-driver and fglrx-kernel-src)? I
installed these recently on a Thinkpad X61M and got 3d acceleration. I
can't remember the exact steps I used (and the machine is not here at
present to check) but it's explained in the docs and there is stuff on
Google about doing it.

Anthony
--
Anthony Campbell - ac@acampbell.org.uk
Microsoft-free zone - Using Linux Gnu-Debian
http://www.acampbell.org.uk (blog, book reviews,
on-line books and sceptical articles)


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Tue, 2007-03-27 at 13:39 +0100, Wackojacko wrote:
> Ian Broadbent wrote:
> >> 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
> >
>
> OK, rename the current xorg file and rerun dpkg-reconfigure xserver-xorg
> and select nvidia, leave the PCI BUS empty and restart X.

Done. Same warnings (only this time for PCI 00:1:3 rather than
00:13:0) Same error 11.

>
> Also post the output of lspci -v |grep VGA (should show video
> controller) and /var/log/xorg if no luck.

return from root call to lspci.....

brutus:~# lspci -v |grep VGA
00:0d.0 VGA compatible controller: nVidia Corporation Unknown device
03d1 (rev a2) (prog-if 00 [VGA])


..... which looks very similar to the entry in the longer lspci report.

The log file(s) are attached.....
Xorg.0.log.old is the one from when it fails using 'nvidia'
Xorg.0.log is the most recent after I reset the xorg.conf to use 'nv'

I presume that the fonts having warnings is just that <warnings> as it
appears to find alternatives later.

....as for the rest, I don't know what I am missing, ...perhaps i am too
hooked up on the PCI warning and missing something more obvious.



Ian

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Joe Hart wrote:
> Anthony Campbell wrote:
>> On 27 Mar 2007, Ian Broadbent wrote:
>>>>> 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 me find the settings for
>>>>> this to get the colours to be accurately displayed?
>> [snip]
>
>> Have you tried the fglrx packages (fglrx-driver and fglrx-kernel-src)? I
>> installed these recently on a Thinkpad X61M and got 3d acceleration. I
>> can't remember the exact steps I used (and the machine is not here at
>> present to check) but it's explained in the docs and there is stuff on
>> Google about doing it.
>
>> Anthony
>
> flgrx is for ati cards. OP has nvidia. Ian, don't do that.
>
> 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.
>
>

It would if I slow down on my typing. I meant fglrx is for ati.

Joe
- --
Registerd Linux user #443289 at http://counter.li.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGCQIqiXBCVWpc5J4RAh0ZAJwPLOD0rbxglcSRnUf0Vz z/99zzsACePCIw
xwB/3VOnB9UrngGFs0+2SJI=
=L2G5
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Anthony Campbell wrote:
> On 27 Mar 2007, Ian Broadbent wrote:
>>>> 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 me find the settings for
>>>> this to get the colours to be accurately displayed?
> [snip]
>
> Have you tried the fglrx packages (fglrx-driver and fglrx-kernel-src)? I
> installed these recently on a Thinkpad X61M and got 3d acceleration. I
> can't remember the exact steps I used (and the machine is not here at
> present to check) but it's explained in the docs and there is stuff on
> Google about doing it.
>
> Anthony

flgrx is for ati cards. OP has nvidia. Ian, don't do that.

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.


- --
Registerd Linux user #443289 at http://counter.li.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGCQGgiXBCVWpc5J4RAismAJ4k6celWxvDeVL7iES/6kVtdBnHjQCcDPww
Kr/U0j3yyKJbrkzQKJWnecY=
=alli
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

> >
> > 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 debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On 27 Mar 2007, Joe Hart wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Anthony Campbell wrote:
> > On 27 Mar 2007, Ian Broadbent wrote:
> >>>> 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 me find the settings for
> >>>> this to get the colours to be accurately displayed?
> > [snip]
> >
> > Have you tried the fglrx packages (fglrx-driver and fglrx-kernel-src)? I
> > installed these recently on a Thinkpad X61M and got 3d acceleration. I
> > can't remember the exact steps I used (and the machine is not here at
> > present to check) but it's explained in the docs and there is stuff on
> > Google about doing it.
> >
> > Anthony
>
> flgrx is for ati cards. OP has nvidia. Ian, don't do that.
>

Sorry - yes, of course. Brain not working properly this morning.

Anthony


--
Anthony Campbell - ac@acampbell.org.uk
Microsoft-free zone - Using Linux Gnu-Debian
http://www.acampbell.org.uk (blog, book reviews,
on-line books and sceptical articles)


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Ian Broadbent wrote:
> On Tue, 2007-03-27 at 13:39 +0100, Wackojacko wrote:
>> Ian Broadbent wrote:
>>>> 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
>>>
>> OK, rename the current xorg file and rerun dpkg-reconfigure xserver-xorg
>> and select nvidia, leave the PCI BUS empty and restart X.
>
> Done. Same warnings (only this time for PCI 00:1:3 rather than
> 00:13:0) Same error 11.
>
>> Also post the output of lspci -v |grep VGA (should show video
>> controller) and /var/log/xorg if no luck.
>
> return from root call to lspci.....
>
> brutus:~# lspci -v |grep VGA
> 00:0d.0 VGA compatible controller: nVidia Corporation Unknown device
> 03d1 (rev a2) (prog-if 00 [VGA])
>

IIRC, this suggests the bus id is 00:0d.0.

Also try installing the pciutils package and running update-pciids as
root. Then rerun the lspci command.

> .... which looks very similar to the entry in the longer lspci report.
>
> The log file(s) are attached.....
> Xorg.0.log.old is the one from when it fails using 'nvidia'
> Xorg.0.log is the most recent after I reset the xorg.conf to use 'nv'
>
> I presume that the fonts having warnings is just that <warnings> as it
> appears to find alternatives later.
>
> ...as for the rest, I don't know what I am missing, ...perhaps i am too
> hooked up on the PCI warning and missing something more obvious.
>
>
>
> Ian
>

<snip xorg nv log>

> (II) Primary Device is: PCI 00:0d:0
> (WW) NV: No matching Device section for instance (BusID PCI:0:1:3) found

Again suggests different PCI Bus ID as above.

<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

(1)
http://people.debian.org/~terpstra/t...d3b216.en.html


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

>
> <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 ful 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 debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Tue, Mar 27, 2007 at 11:23:14AM +0100, Ian Broadbent wrote:
> 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?
>
> brutus:~# lspci -v
>
> 00:0d.0 VGA compatible controller: nVidia Corporation Unknown device
> 03d1 (rev a
> 2) (prog-if 00 [VGA])
> Subsystem: ASRock Incorporation Unknown device 03d1
> Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 10
> Memory at de000000 (32-bit, non-prefetchable) [size=16M]
> Memory at c0000000 (64-bit, prefetchable) [size=256M]
> Memory at dd000000 (64-bit, non-prefetchable) [size=16M]
> Expansion ROM at dffc0000 [disabled] [size=128K]
> Capabilities: [48] Power Management version 2
> Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+

You could of snipped the unnecessary bits.

Looks like recent h/w. Try running, as root, the following:

update-pciids

from a command line while you are online.

Then try as root
lspci | grep VGA

--
Chris.
======
Don't forget to check that your /etc/apt/sources.lst entries point to
etch and not testing, otherwise you may end up with a broken system once
etch goes stable.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

> You could of snipped the unnecessary bits.
> Chris.
errrrrrr...... 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 debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Wed, Mar 28, 2007 at 05:52:23AM +0100, Ian Broadbent wrote:
> > You could of snipped the unnecessary bits.
> > Chris.
> errrrrrr...... 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).

That was the lspci -v listing I was referring to.

--
Chris.
======
Don't forget to check that your /etc/apt/sources.lst entries point to
etch and not testing, otherwise you may end up with a broken system once
etch goes stable.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org