Due to an obsolete function call in lirc_serial (and other modules), the kernel modules will fail to load with an Unknown symbol error. While this has reportedly been fixed in the newest prerelease version of lirc, it would be nice for us non-~arch folks to have a patch in portage to let us use 0.7.2 until 0.7.3 is finalized. I have a patch and a new ebuild to fix this problem. I will attach them. Reproducible: Always Steps to Reproduce: 1. Install latest kernel (i.e. 2.6.14-gentoo-r4) 2. Install lirc-0.7.2 3. Try modprobe lirc_serial Actual Results: modprobe fails with Unknown symbol verify_area Expected Results: lirc_serial and lirc_dev should be loaded into the kernel Gentoo Base System version 1.6.13 Portage 2.0.51.22-r3 (default-linux/x86/2005.1, gcc-3.4.4, glibc-2.3.5-r2, 2.6.14-gentoo-r4 i686) ================================================================= System uname: 2.6.14-gentoo-r4 i686 AMD Athlon(tm) dev-lang/python: 2.2.3-r6, 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.4.1-r10, 1.5.20 virtual/os-headers: 2.4.19, 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=athlon -mmmx -msse -m3dnow -O3 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon -mmmx -msse -m3dnow -O3 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 3dnow 3dnowext X a52 aac aalib acl acpi acpi4linux alsa amr apm atlas audiofile avi bash-completion berkdb bitmap-fonts bonobo bootsplash bzip2 cdda cddb cdio cdparanoia cdr crypt cscope css cups curl dga dpms dts dv dvb dvd dvdr dvdread dxr3 edl eds emboss encode esd exif expat fam fame fat fb fbcon fbdev ffmpeg fftw flac flash foomaticdb fortran fuse gb gd gdbm gdk ggi ggz gif gimpprint glibc-compat20 glut glx gphoto2 gpm gs gstreamer gtk gtk2 gtkhtml id3 ieee1394 imap imlib ipv6 jack joystick jp2 jpeg jpeg2k lame lcms libg++ libsamplerate libwww lirc live lm_sensors lzo mad matroska mikmod mjpeg mmap mmx mmxext mng mod motif mozctl mozilla mozsvg mozxmlterm mp3 mpeg mpeg2 mpeg4 mplayer musepack mysql mythtv nas ncurses network nls nsplugin ntfs nvidia ogg oggvorbis on-the-fly-crypt opengl oss pam pdflib perl plotutils png python qt qtmt quicktime radeon rar readline real reiserfs rtc samba sblive screen sdl sensord shorten silverxp slang smooth sndfile soundtouch speex spell sse ssl startup-notification stream subtitles svg svga svgz tcltk tcpd tga theora tiff transcode truetype truetype-fonts type1-fonts udev usb v4l v4l2 vcd vfat vlm vorbis win32codecs xanim xfs xine xinerama xkb xml xml2 xmms xosd xv xvid xvmc yv12 zlib zvbi userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
Created attachment 74830 [details, diff] Patch for lirc-0.7.2 to change verify_area to access_ok This patch corrects the problem on my system.
*** This bug has been marked as a duplicate of 111820 *** *** This bug has been marked as a duplicate of 111820 ***
Created attachment 74831 [details] This ebuild patches the lirc source using the attached patch. When I drop this ebuild and the previous patch into a portage overlay set with PORTDIR_OVERLAY, lirc-0.7.2 compiles and installs correctly.
My apologies for reopening this bug if it is truly inappropriate, but it appears that this is a different bug from bug 111820. This is just a patch to get us by until 0.7.3 is out. Bug 111820 talks about compile failures. This bug talks about insmod failures. If this bug should be lumped in with bug 111820, then close it again and I will comment on this issue on bug 111820.
Won't be fixed until 0.7.3, we track all issues in Bug 111820. *** This bug has been marked as a duplicate of 106683 ***