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

Re: building kernel drm modules [was Re: DRI on mach64 (ATI Technologies Inc 3D Rage Pro 215GP (rev 5c))]



On Tue, Sep 23, 2008 at 09:39:43AM +0200, Michel Dänzer wrote:
> On Tue, 2008-09-23 at 08:48 +0200, Hans Ekbrand wrote:
> > 
> > 1. added experimental to sources.list
> > 
> > $ grep experimental /etc/apt/sources.list
> > deb-src http://ftp.se.debian.org/debian/ experimental main
> > 
> > 2. Backported drm-modules-source from experimental to lenny
> > 
> > # apt-get build-dep drm-modules-source
> > # apt-get --build source drm-modules-source
> > 
> > 3. Installed the backported drm-modules-source package
> > 
> > # dpkg -i drm-modules-source_2.3.1+git+20080706+401f77a-1_all.deb
> > 
> > I just ignored the other packages that where built in this run:
> > 
> > libdrm-dev_2.3.1+git+20080706+401f77a-1_powerpc.deb
> > libdrm2_2.3.1+git+20080706+401f77a-1_powerpc.deb
> > libdrm2-dbg_2.3.1+git+20080706+401f77a-1_powerpc.deb
> > 
> > Was that correct?
> 
> Yes, but couldn't you just install drm-modules-source from experimental?

Well, I just don't want to install binary packages from experimental,
but that might have worked alright in this case.

> >   CC [M]  /usr/src/modules/drm-modules/linux-core/mach64_drv.o
> >   CC [M]  /usr/src/modules/drm-modules/linux-core/mach64_dma.o
> >   CC [M]  /usr/src/modules/drm-modules/linux-core/mach64_irq.o
> >   CC [M]  /usr/src/modules/drm-modules/linux-core/mach64_state.o
> 
> As you can see, the mach64 driver builds fine; try setting the
> environment variable DRM_MODULES=mach64 for running module-assistant.

Good advice! The building of installation of the module worked well. I
rebooted and start X. X works, but strangely wdm will not work with it.

- running X alone works.

but the following is logged early in the X startup process.

(WW) ****INVALID IO ALLOCATION**** b: 0xfe000c00 e: 0xfe000cff correcting
(EE) end of block range 0xfdffffff < begin 0xfe000000

- running clients on a server that was started alone works
  (xlogo, xdpyinfo, ion3, emacs)

- Starting glxgears on a bare X server succeeds!

pc237:~# DISPLAY=:0.0 glxgears -info
GL_RENDERER   = Mesa DRI Mach64 [Rage Pro] 20051019
GL_VERSION    = 1.2 Mesa 7.0.4
GL_VENDOR     = Gareth Hughes, Leif Delgass, Jos%G�%@ Fonseca
GL_EXTENSIONS = GL_ARB_imaging GL_ARB_multisample GL_ARB_multitexture GL_ARB_transpose_matrix GL_ARB_vertex_buffer_object GL_ARB_window_pos GL_EXT_abgr GL_EXT_bgra GL_EXT_blend_color GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_clip_volume_hint GL_EXT_compiled_vertex_array GL_EXT_convolution GL_EXT_copy_texture GL_EXT_draw_range_elements GL_EXT_histogram GL_EXT_packed_pixels GL_EXT_polygon_offset GL_EXT_rescale_normal GL_EXT_separate_specular_color GL_EXT_subtexture GL_EXT_texture GL_EXT_texture3D GL_EXT_texture_edge_clamp GL_EXT_texture_object GL_EXT_vertex_array GL_APPLE_packed_pixels GL_IBM_rasterpos_clip GL_MESA_ycbcr_texture GL_MESA_window_pos GL_NV_light_max_exponent GL_NV_texgen_reflection GL_OES_read_format GL_SGI_color_matrix GL_SGI_color_table GL_SGIS_generate_mipmap GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod
571 frames in 5.0 seconds = 114.087 FPS
568 frames in 5.0 seconds = 113.469 FPS

- glxgears also work fine in managed window (ion3)

- The only client that I have tried that does not work is wdm (the X
server dies when wdm opens its login-window). The following four lines
are printed to Xorg.log.0 when wdm opens its' login window on the X
server:

(II) MACH64(0): [drm] Uninstalled interrupt handler for IRQ 22
(II) MACH64(0): [drm] removed 1 reserved context for kernel
(II) MACH64(0): [drm] unmapping 8192 bytes of SAREA 0xcba54000 at 0x48022000
(II) MACH64(0): [drm] Closed DRM master.

I can live without wdm, but does anyone what is going on here?

Here is my xorg.conf

# xorg.conf (X.Org X Window System server configuration file)
#

Section "InputDevice"
	Identifier	"Generic Keyboard"
	Driver		"kbd"
	Option		"XkbRules"	"xorg"
	Option		"XkbModel"	"pc105"
	Option		"XkbLayout"	"se"
	Option		"XkbOptions"	"lv3:lwin_switch"
EndSection

Section "InputDevice"
	Identifier	"Configured Mouse"
	Driver		"mouse"
EndSection

Section "Device"
	Driver          "ati"
	Identifier	"Configured Video Device"
	BusID		"PCI:0:18:0"
	Option		"UseFBDev"		"true"
#	Option		"UseFBDev"		"false"
EndSection

Section "Monitor"
	Identifier	"Configured Monitor"
	Option		"DPMS"	"true"
	HorizSync 60-60
	VertRefresh 75-117
EndSection

Section "Screen"
	Identifier	"Default Screen"
	Monitor		"Configured Monitor"
	Device		"Configured Video Device"
	DefaultDepth	16
EndSection

Section "DRI"
        Mode    0666
EndSection

## End of xorg.conf

> FWIW, the xgi driver build should be fixed in upstream commit
> eac0933be75b226e0b623d8dcbf343c391eb88a2 .

OK.

-- 
Hans Ekbrand (http://sociologi.cjb.net) <hans@sociologi.cjb.net>
Q. What is that strange attachment in this mail?
A. My digital signature, see www.gnupg.org for info on how you could
   use it to ensure that this mail is from me and has not been
   altered on the way to you.

Attachment: signature.asc
Description: Digital signature


Reply to: