Re: upgrade of kernel breaks drm/dri?
Hi,
Sorry, please ignore this. I shoudl have double checked that the CONFIG_DRM
was even abled at all. I thought it would be default but was not even set.
My bad...
Kevin
On Sunday 30 November 2003 10:28, Kevin B. Hendricks wrote:
> Hi,
>
> Forgive me if this has been dicsussed before. Tux racer used to work just
> fine with my old YDL 3 kernel and XFree86 4.3.0.
>
> I have now upgrade to to Ben's latest 2.4.23 kernel and it seems sadly Tux
> racer has sloowed way down again.
>
> Looking in /var/log/XFree86*.log the only bad thing I can see is:
>
> drmOpenDevice: minor is 0
> 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: minor is 0
> 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
> [drm] failed to load kernel module "radeon"
> (II) RADEON(0): [drm] drmOpen failed
> (EE) RADEON(0): [dri] DRIScreenInit failed. Disabling DRI.
>
>
> So it appears I seem to be missing a device node. I manually used mknod as
> root to create /dev/dri/card0 (card1, card2 and card3 already existed but
> no card0) using char 226,0
>
> But it seems that everytime I startup X something deletes my newly created
> device node "card0".
>
> Does anyone have a clue as to why that special device keeps getting deleted
> and or what I should do to get poor Tux back up to speed.
>
> Any hints appreciated.
>
> Thanks,
>
> Kevin
Reply to: