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

Bug#380534: marked as done (drm mach64 module compiled from dri cvs against linux-headers-2.6.17-1-686 fails to load)

Your message dated Wed, 9 Aug 2006 09:06:10 +0200
with message-id <20060809070610.GR10067@baikonur.stro.at>
and subject line Bug#380534: Bug resolved
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: linux-headers-2.6.17-1-686
Version: 2.6.17-4
Severity: normal


here is the error on the command-line when calling modprobe mach64:
FATAL: Error inserting mach64
(/lib/modules/2.6.17-1-686/kernel/drivers/char/drm/mach64.ko): Unknown
symbol in module, or unknown parameter (see dmesg)

Here is the output in dmesg:

[drm] Initialized drm 1.0.1 20051102
mach64: disagrees about version of symbol drm_open
mach64: Unknown symbol drm_open
mach64: disagrees about version of symbol drm_fasync
mach64: Unknown symbol drm_fasync
mach64: disagrees about version of symbol drm_poll
mach64: Unknown symbol drm_poll
mach64: disagrees about version of symbol drm_core_get_reg_ofs
mach64: Unknown symbol drm_core_get_reg_ofs
mach64: disagrees about version of symbol drm_pci_alloc
mach64: Unknown symbol drm_pci_alloc
mach64: disagrees about version of symbol drm_irq_uninstall
mach64: Unknown symbol drm_irq_uninstall
mach64: disagrees about version of symbol drm_ioctl
mach64: Unknown symbol drm_ioctl
mach64: disagrees about version of symbol drm_exit
mach64: Unknown symbol drm_exit
mach64: disagrees about version of symbol drm_core_get_map_ofs
mach64: Unknown symbol drm_core_get_map_ofs
mach64: disagrees about version of symbol drm_init
mach64: Unknown symbol drm_init
mach64: disagrees about version of symbol drm_vbl_send_signals
mach64: Unknown symbol drm_vbl_send_signals
mach64: disagrees about version of symbol drm_pci_free
mach64: Unknown symbol drm_pci_free
mach64: disagrees about version of symbol drm_mmap
mach64: Unknown symbol drm_mmap
mach64: disagrees about version of symbol drm_core_reclaim_buffers
mach64: Unknown symbol drm_core_reclaim_buffers
mach64: disagrees about version of symbol drm_release
mach64: Unknown symbol drm_release

I'm sure this is not a bug in the dri cvs, because I also built the same
module against the headers in a custom-compiled 2.6.17.3 downloaded from
kernel.org, and the module works fine with that kernel.

here is the procedure I used for fetching the cvs and compiling the module:
 git clone git://anongit.freedesktop.org/git/mesa/drm
 cd drm/linux-core
 make DRM_MODULES="mach64" LINUXDIR=/usr/src/linux
 (/usr/src/linux is a symlink to /usr/src/linux-headers-2.6.17-1-686)
 cp /lib/modules/2.6.17-1-686/kernel/drivers/char/drm/drm.ko
 /lib/modules/2.6.17-1-686/kernel/drivers/char/drm/drm.ko.orig
 cp drm.ko /lib/modules/2.6.17-1-686/kernel/drivers/char/drm/drm.ko
 cp mach64.ko /lib/modules/2.6.17-1-686/kernel/drivers/char/drm/mach64.ko
 depmod -a $(uname -r)
 modprobe -r drm
 modprobe -r mach64
 modprobe mach64


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-1-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages linux-headers-2.6.17-1-686 depends on:
ii  gcc-4.1                       4.1.1-9    The GNU C compiler
ii  linux-headers-2.6.17-1        2.6.17-4   Common header files for Linux kern
ii  linux-kbuild-2.6.17           2.6.17-2   Kbuild infrastructure for Linux 2.

linux-headers-2.6.17-1-686 recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Tue, Aug 08, 2006 at 09:49:03PM -0400, Chris O'Callaghan wrote:
> This bug seems to have been resolved in a recent update of this package.
> 
> -- 
> Chris O'Callaghan                

closing, thanks for your report.

-- 
maks

--- End Message ---
Reply to: