Ed Tomlinson <[email protected]> wrote:
>
>> ---------- Forwarded Message ----------
>>
>> Subject: Re: Xorg and RADEON (dri disabled)
>> Date: Wednesday 20 July 2005 21:25
>> From: Ed Tomlinson <[email protected]>
>> To: [email protected]
>> Cc: Michal Schmidt <[email protected]>
>>
>> On Wednesday 20 July 2005 21:13, Michal Schmidt wrote:
>> > Ed Tomlinson wrote:
>> > > Hi,
>> > >
>> > > With Xorg I get:
>> > >
>> > > (==) RADEON(0): Write-combining range (0xd0000000,0x8000000)
>> > > drmOpenDevice: node name is /dev/dri/card0
>> > > drmOpenDevice: open result is -1, (No such device)
>> > > drmOpenDevice: open result is -1, (No such device)
>> > > drmOpenDevice: Open failed
>> > > drmOpenDevice: node name is /dev/dri/card0
>> > > drmOpenDevice: open result is -1, (No such device)
>> > > drmOpenDevice: open result is -1, (No such device)
>> > > drmOpenDevice: Open failed
>> > > drmOpenByBusid: Searching for BusID pci:0000:01:00.0
>> > > drmOpenDevice: node name is /dev/dri/card0
>> > > drmOpenDevice: open result is 7, (OK)
>> > > drmOpenByBusid: drmOpenMinor returns 7
>> > > drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
>> > > (II) RADEON(0): [drm] loaded kernel module for "radeon" driver
>> > > (II) RADEON(0): [drm] DRM interface version 1.2
>> > > (II) RADEON(0): [drm] created "radeon" driver at busid "pci:0000:01:00.0"
>> > > (II) RADEON(0): [drm] added 8192 byte SAREA at 0xffffc20000411000
>> > > (II) RADEON(0): [drm] drmMap failed
>> > > (EE) RADEON(0): [dri] DRIScreenInit failed. Disabling DRI.
>> > >
>> > > And glxgears reports 300 frames per second. How do I get dri back? It
>> > > was working fine with XFree. The XF86Config-4 was changed by the upgrade
>> > > dropping some parms in the Device section. Restoring them has no effect
>> > > on the problem.
>>
>> > What kernel do you use? I get the same behaviour with 2.6.13-rc3-mm1,
>> > but it works with 2.6.13-rc3.
>>
>> I also use 2.6.13-rc3-mm1. Will try with a previous version an report to lkml if
>> it works.
>>
>
> I just tried 13-rc2-mm1 and dri is working again. Its reported to also work
> with 13-rc3.
Useful info, thanks.
> What in mm1 is apt to be breaking dri?
Faulty kernel programming ;)
I assume that the failure to open /dev/dri/card0 only happens in rc3-mm1?
Could you compare the dmesg output for 2.6.13-rc3 versus 2.6.13-rc3-mm1?
And double-check the .config settings: occasionally config options will be
renamed and `make oldconfig' causes things to get acidentally disabled.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |