Re: [Mesa3d-users] sample_server fails to start with radeon driver - fbdev/DRI - linux-solo

[S. P. <pr...@gm...>]

I had a look at the gentoo-wiki, sounds quite complicated and Arch Linux
doesn't feel too well with it...
Anyway, I accidentally deleted my whole working directory today... and so i
had to compile fbdev/DRI once again.
Now the sample_server starts with the same output without errors, screen
goes black and font goes dark grey, but i can exit the sample_server with
Ctrl+C when using ssh.
Soon I try to start sample_server again I get this output:

[root@server miniglx]# ./sample_server & ./miniglxtest
[miniglx] probed chipset 0x4e48
got MMIOAddress 0xb7fad000 offset 134217728
shared virtual width is 1280
[drm] drmSetBusid failed (5, PCI:1:0:0), Device or resource busy
__miniglx_StartServer: __driInitFBDev failed
Error: __miniglx_StartServer failed
[2] 15643
[miniglx] probed chipset 0x4e48
CreateNotify
Authorize - magic 4
xf86-video-ati-6.6.2 or newer needed for Radeon 9500/9700/9800 cards.
libGL error: InitDriver failed
libGL error: reverting to (slow) indirect rendering
XOpenDisplay: __driCreateScreen failed
Error: XOpenDisplay failed
DestroyNotify
[2]+  Exit 1                  ./sample_server



I tried to install the new driver from here
http://xorg.freedesktop.org/releases/individual/driver/ but the error stays
the same - even after rebooting.

Running ./sample_server alone results in:
[root@server miniglx]# ./sample_server
[miniglx] probed chipset 0x4e48
got MMIOAddress 0xb7df4000 offset 134217728
shared virtual width is 1280
[drm] drmSetBusid failed (5, PCI:1:0:0), Device or resource busy
__miniglx_StartServer: __driInitFBDev failed
Error: __miniglx_StartServer failed

Running ./miniglxtest alone results in:
[root@server miniglx]# ./miniglxtest
[miniglx] probed chipset 0x4e48
CreateNotify
Authorize - magic 8
xf86-video-ati-6.6.2 or newer needed for Radeon 9500/9700/9800 cards.
libGL error: InitDriver failed
libGL error: reverting to (slow) indirect rendering
XOpenDisplay: __driCreateScreen failed
Error: XOpenDisplay failed
DestroyNotify

Whenever I load the module radeonfb the screen goes black and the font
re-appears much smaller after a few seconds, it seems the screen uses a
better screen resolution soon i modprobe radeonfb.

What exactly is not working? The Framebuffer? The Framebuffer-Driver? fbdev?
The example-tools?
The parts of the kernel I should activate when following
http://gentoo-wiki.com/HOWTO_Framebuffer_Support are activated here under my
Arch Linux - but due to using Lilo as Bootloader i didn't manage to boot
with the boot-options listed in the gentoo wiki...
I'll try it later on, maybe i'll install grub...

Thanks, Maurizio

On Mon, May 19, 2008 at 3:23 PM, Maurizio Rottin <mau...@gm...>
wrote:

> 2008/5/19, Simon Prückl <pr...@gm...>:
> > I'm on x86, yes. I compiled the kernel using the manual from the official
> > Arch Linux Wiki, I used the old config and just changed the 2 lines the
> > manual told me to do.
> > I don't know anything about the framebuffer - when starting the
> > sample_server without module radeonfb loaded he complains there's no
> > /dev/fb0, after modprobe radeonfb it "works" and results in the output
> > posted 2 mails ago (see below).
>
> so the problem is the framebuffer module, not mesa.
> in my gentoo i had to build ati-drivers, plus build uvesafb (couse
> vesafb does not work anymore since 2.6.22 i believe), then rebuild the
> kernel with the path to an initrd ad hoc and klibc to make it work
> http://gentoo-wiki.com/HOWTO_Framebuffer_Support
>
> --
> mr
>