nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   Signal 11 with legacy-173/amd64/kernel-2.6.2[68] (http://www.nvnews.net/vbulletin/showthread.php?t=132890)

uOpt 05-13-09 04:36 PM

Signal 11 with legacy-173/amd64/kernel-2.6.2[68]
 
Are the 173 legacy drivers known to work with kernels 2.6.26-2.6.28 using 64 bit code?

I have to use the legacy drivers on this dual-single-core Opteron (AMD 81xx AGP chipset) with AGP FX 5200.

I get the following error in both 2.6.26 and 2.2.68:

Code:

[...]
(II) Initializing extension GLX

Backtrace:
0: X(xf86SigHandler+0x6a) [0x48dd0a]
1: /lib/libc.so.6 [0x7f12d6a04f60]
2: X(SecurityExtensionInit+0x68d) [0x510f1d]
3: X(InitExtensions+0x8a) [0x4b1c5a]
4: X(main+0x2f0) [0x436a20]
5: /lib/libc.so.6(__libc_start_main+0xe6) [0x7f12d69f11a6]
6: X(FontFileCompleteXLFD+0x281) [0x435e99]

Fatal server error:
Caught signal 11.  Server aborting

(II) Screen 0 shares mem & io resources
(II) Screen 1 shares mem & io resources

Does this sound familiar?

I use 173.14.12 successfully under i386 (32 bit) with 2.6.24.3 on the same machine (same card etc, dual-boot i386/amd64).

Before I go on a binary search to look for the newest working drivers, is there anything known about the status of the drivers.

After the above error the console is not restored, I'm left with a blank screen.

uOpt 05-13-09 04:59 PM

Re: Signal 11 with legacy-173/amd64/kernel-2.6.2[68]
 
Here is one curious thing: I configure my dual-head AGP to be on PCI devices

Code:

        BusID          "PCI:5:0:0"
        Screen          0
[...]
        BusID          "PCI:5:0:0"
        Screen          1

However, the kernel on the broken amd64 kernel reports:
Code:

May 13 16:48:11 pls kernel: agpgart: Found an AGP 3.0 compliant device at 0000:04:00.0.
May 13 16:48:11 pls kernel: agpgart: Putting AGP V3 device at 0000:04:00.0 into 8x mode
May 13 16:48:11 pls kernel: agpgart: Putting AGP V3 device at 0000:05:00.0 into 8x mode
May 13 16:48:13 pls kernel: Xorg[4445]: segfault at 31 ip 7f12d3d3251c sp 7fffe049b3a0 error 4 in nvidia_drv.so[7f12d3b47000+3c9000]

On the i386 kernel no such lines are reported.

The two kernels has been configure with identical AGP options:
Code:

CONFIG_AGP=y
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
CONFIG_AGP_AMD64=y
CONFIG_AGP_INTEL=m
# CONFIG_AGP_NVIDIA is not set
CONFIG_AGP_SIS=m
# CONFIG_AGP_SWORKS is not set
CONFIG_AGP_VIA=m
# CONFIG_AGP_EFFICEON is not set

I wonder whether AGP gets in my way here.

Snooping through dmesg I see the broken setup uses the GART IOMMU:

Working:
Code:

Linux agpgart interface v0.102
agpgart: Detected AMD 8151 AGP Bridge rev B3
agpgart: AGP aperture is 128M @ 0xf0000000

Not working:
Code:

PCI: Using ACPI for IRQ routing
PCI: Cannot allocate resource region 0 of device 0000:04:00.0
agpgart: Detected AMD 8151 AGP Bridge rev B3
agpgart: AGP aperture is 128M @ 0xf0000000
PCI-DMA: using GART IOMMU.
PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture


uOpt 05-13-09 07:11 PM

Re: Signal 11 with legacy-173/amd64/kernel-2.6.2[68]
 
1 Attachment(s)
I now tried the same 2.6.24 kernel source that worked when it is compiled as i386 (that doesn't mean it is the same config). Same segfault as with the other kernel versions.

Any ideas?

uOpt 05-13-09 08:59 PM

Re: Signal 11 with legacy-173/amd64/kernel-2.6.2[68]
 
Fixed.

The problem was a broken Xorg in Dbian-stable.

xserver 1.4.2-10.lenny1 works (with legacy and 2.6.28 as stated).

Unfortunately there doesn't seem to be a way to tell me which package exactly I had before apt-get but it seems to be /xserver-xorg-core_2%3a1.4.2-10_amd64.deb (no "lenny" in the same).


All times are GMT -5. The time now is 06:46 PM.

Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.