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

Bug#239617: marked as done ([radeon] DRM doesn't fly on a KT400; suspected motherboard configuration issue)



Your message dated Mon, 12 Feb 2007 23:40:01 +0100
with message-id <45D0ECC1.3050909@ens-lyon.org>
and subject line ping timeout, closing
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: xserver-xfree86
Version: 4.3.0-7

I have an interesting problem trying to get DRI working on my Radeon
9000, with kernel 2.6.4.

If I don't configure the agp bus by inserting the correct modules into
the kernel, X starts and works, however, it fails to initialize DRI,
and I get the following messages in my kernel log:

[drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held
[drm:radeon_unlock] *ERROR* Process 802 using kernel context 0

X works fine, but Direct Rendering: No in glxinfo.

If I configure the agp bus by inserting the agp driver (via-agp),
as X starts, the computer completely dies. By which I mean, the screen
goes black and shuts off, and the computer is unresponsive on the
network. There is no indications in any logs, and it seems impossible
to capture any information from the output of X (nothing gets printed
in the split second before the monitor gets shut off).

I have tried various combinations of arguments to the radeon driver in
the X configration, tried diddling options in bios, and the behavior
is always the same.

I note that It does the same thing when I don't insert the proper agp
module but do specify ForcePCIMode in the driver. 

The important section of XF86Config-4:

Section "Device"
	Identifier      "Radeon 9000"
	Driver          "radeon"
	BusId           "1:0:0"
EndSection

This is what I'm currently using (without DRI), and it behaves the same with m
any other arguments that I have tried (I should've kept track of
these, but various things turing off fastness, turning on fastness,
etc).

lspci:

00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400 AGP] Host Bridge (rev 80)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge
00:06.0 Multimedia video controller: Brooktree Corporation Bt848 Video Capture (rev 11) 
00:0a.0 PCI bridge: Hint Corp HB6 Universal PCI-PCI bridge (non-transparent mode) (rev 11)
00:10.0 USB Controller: VIA Technologies, Inc. USB (rev 80)
00:10.1 USB Controller: VIA Technologies, Inc. USB (rev 80)
00:10.2 USB Controller: VIA Technologies, Inc. USB (rev 80)
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE (rev 06)
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235 AC97 Audio Controller (rev 50)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R250 If [Radeon 9000] (rev 01)
01:00.1 Display controller: ATI Technologies Inc Radeon R250 [Radeon 9000] (Secondary) (rev 01)
02:08.0 FireWire (IEEE 1394): NEC Corporation: Unknown device 00ce (rev 01)
02:09.0 USB Controller: NEC Corporation USB (rev 41)
02:09.1 USB Controller: NEC Corporation USB (rev 41)
02:09.2 USB Controller: NEC Corporation USB 2.0 (rev 02)

uname -a:

Linux chaak 2.6.4-1-k7 #1 Sat Mar 13 22:44:25 EST 2004 i686 GNU/Linux

lsmod (note that this is the working configuration without DRI, the
crashing configuration occurs when I insert via-agp (and agpgart)):

Module                  Size  Used by
psmouse                19784  0
radeon                118956  0
hid                    32960  0
mousedev               10004  2
ipv6                  253120  10
af_packet              22280  12
ehci_hcd               26564  0
usbcore               105756  4 hid,ehci_hcd
via82cxxx_audio        29896  1
uart401                11716  1 via82cxxx_audio
sound                  83820  2 via82cxxx_audio,uart401
ac97_codec             18828  1 via82cxxx_audio
via_rhine              21448  0
mii                     5184  1 via_rhine
crc32                   4352  1 via_rhine
raw1394                33324  0
video1394              19404  0
ohci1394               35460  1 video1394
ieee1394              110456  3 raw1394,video1394,ohci1394
tuner                  18060  0
tvaudio                22220  0
bttv                  150124  0
video_buf              21380  1 bttv
i2c_algo_bit            9736  1 bttv
v4l2_common             6208  1 bttv
btcx_risc               4808  1 bttv
i2c_core               23364  4 tuner,tvaudio,bttv,i2c_algo_bit
videodev                9920  1 bttv
soundcore              10272  4 via82cxxx_audio,sound,bttv
ide_scsi               15172  0
ext3                  120552  3
jbd                    61464  1 ext3
mbcache                 9092  1 ext3
sd_mod                 16800  0
ata_piix                8388  0
libata                 41088  1 ata_piix,[permanent]
scsi_mod              118264  3 ide_scsi,sd_mod,libata
ide_disk               18432  6
ide_detect              1152  0
via82cxxx              13980  1
ide_core              155172  4 ide_scsi,ide_disk,ide_detect,via82cxxx
unix                   28464  374
font                    8448  0
cfbcopyarea             3968  0
cfbimgblt               3200  0
cfbfillrect             3840  0



-- 
-><- Nick Rusnov
-><- http://nick.industrialmeats.com
-><- nick@fargus.net/nickrusnov@debian.org 


--- End Message ---
--- Begin Message ---
I am closing this bug since the submitter did not reply to the ping I
send a couple weeks ago. If anybody ever reproduces this problem, feel
free to reopen.

Brice


--- End Message ---

Reply to: