I am still using kernel 2.4 with my iMac as the rivafb driver is said to be broken in 2.6. During the last week we had two new kernels 2.4, 2.4.26 and 2.4.26-r1. And between the 2 we had a new version of gcc namely gcc3.3.3_pre20040408-r1. I compiled the first kernel with gcc3.2.3 which was my previous version of gcc. I then compiled 2.4.26-r1 with the new gcc3.3.3 upon reboot it refuse to mount my hfsplus partition where OSX reside with the following message: insmod: /lib/modules/2.4.26-ppc-r1/kernel/fs/hfsplus/hfsplus.o: couldn't find the kernel version the module was compiled for insmod: /lib/modules/2.4.26-ppc-r1/kernel/fs/hfsplus/hfsplus.o: insmod hfsplus failed some other modules like alsa got in the same kind of trouble. lsmod revealed that i had absolutly no module loaded. At first i thought it was a kernel problem. However recompiling 2.4.26 which was working pefectly well with gcc3.3.3 resulted in that kernel suffering of the same problem. I therefore conclude it is a gcc problem, possibly related to this bug: http://bugs.gentoo.org/show_bug.cgi?id=42689 Reproducible: Always Steps to Reproduce: 1.emerge gcc3.3.3_pre 2.compile a kernel 2.4.26 or 26-r1 with some module 3.boot the kernel 4.try to load module bash-2.05b$ emerge info Portage 2.0.50-r8 (default-ppc-2004.1, gcc-3.3.3, glibc-2.3.3.20040420-r0, 2.4.26-ppc) ================================================================= System uname: 2.4.26-ppc ppc 7450, altivec supported Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.58-r1 Automake: sys-devel/automake-1.8.3 ACCEPT_KEYWORDS="ppc" AUTOCLEAN="yes" CFLAGS="-O2 -mcpu=7450 -pipe -maltivec -mabi=altivec -fno-strict-aliasing" CHOST="powerpc-unknown-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O2 -mcpu=7450 -pipe -maltivec -mabi=altivec -fno-strict-aliasing" DISTDIR="/usr/portage/distfiles" FEATURES="ccache" GENTOO_MIRRORS="ftp://ftp.vic.keypoint.com.au http://mirrors.tds.net/gentoo ftp://mirrors.tds.net/gentoo http://mirror.tucdemonic.org/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X aalib alsa arts berkdb cdr cups dvd dvdr esd fbcon foomaticdb gdbm gif gpm gtk2 imlib jpeg kde libwww mitshm motif mozilla ncurses nls oggvorbis opengl oss pam perl png ppc ppds python qt readline sdl sheep slang ssl tcpd tetex truetype xml xml2 xv"
I have the same problem here. *EVERY* module compiled using the new gcc will not able to be loaded, and fails with a "couldn't find the kernel version the module was compiled for". By the way, I'm not able to compile the new glibc... but seems to be another bug. Emerge info: Gentoo Base System version 1.4.16 Portage 2.0.50-r7 (default-ppc-2004.1, gcc-3.3.3, glibc-2.3.2-r9, 2.4.24-ppc-r4) ================================================================= System uname: 2.4.24-ppc-r4 ppc 7455, altivec supported Autoconf: sys-devel/autoconf-2.58-r1 Automake: sys-devel/automake-1.8.3 ACCEPT_KEYWORDS="ppc" AUTOCLEAN="yes" CFLAGS="-O2 -pipe -mcpu=7450 -mpowerpc-gfxopt -fsigned-char" CHOST="powerpc-unknown-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O2 -pipe -mcpu=7450 -mpowerpc-gfxopt -fsigned-char" DISTDIR="/usr/portage/distfiles" FEATURES="ccache" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://www.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://pplux.com/gentoo-portage" USE="X aalib alsa altivec apm berkdb bonobo cdr clanVoice crypt cups curl dga divx4linux doc dumb-allegro dv dvd dvdr encode esd ethereal fbcon foomaticdb gb gdbm gif glade glut gnome gnome-libs gstreamer gtk gtk2 gtkhtml guile i8x0 imagemagick imap imlib imlib2 jpeg ldap libwww lua mad matroska mbox md5sum mitshm motif mozctl mozilla moznocompose moznoirc moznomail mozsvg mpeg music ncurses nls oggvorbis opengl oss pam pcmcia pdflib perl pic plotutils png pnp ppc python quicktime radeon readline samba sdl slang spell ssl tcpd tetex theora threads tiff transcode truetype unicode usb v4l video_cards_radeon wavelan wxwindows xinerama xml xml2 xmms xv xvid zlib"
dmesg please
Created attachment 32996 [details] dmesg as requested dmesg as requested but it doesn't contain any mention to the failure of loading modules. By the way is there a "tool for modules" package that should be recompiled with the new gcc?
I just re-emerged modutils to compile it with gcc3.3.3_pre20040408-r1 in case it would help. It didn't.
I'm having problems with gcc 3.3.3 at my own code (those wich gcc complains with a internal error), I've downgraded gcc to 3.3.2 and kernel 2.4.26[-r1] can now load modules again. If helps, kernel 2.6.5 with gcc 3.3.3 compiles and seems to work fine.
Some other people are seeing this problem too (including myself). Would it be appropriate to get gcc3.3.3_pre20040408-r1 masked with ~ppc and roll back to 3.3.2-r7? http://forums.gentoo.org/viewtopic.php?t=197648 Until I get my ISA bus hardware working on 2.6, I can't upgrade ;)
That would be fine with me. I just reported an other bug: http://bugs.gentoo.org/show_bug.cgi?id=57531 Would the roll back to gcc 3.3.2 solve this problem as well? However I also notice that gcc 3.3.2-r7 is marked ~ppc64 but not ppc or ~ppc, so that may create new problems for some people.
I thought 3.3.4 had some successful testing on ppc ?
upstream problems with gcc and kernel you can't use 2.4 on anything later than gcc 3.3.3 including. The next ppc internal meeting we'll try to have a coordinated solution.
2.4 kernels on ppc should have been made dependent on <gcc-3.3.3 . We have switched to a gcc-3.4 toolchain and recommend using a 2.6 kernel as default. 2.4 kernels have been put in maintenance mode upstream.
