Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 39971 - gdm can't start
Summary: gdm can't start
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-31 05:57 UTC by Martin Valensky
Modified: 2004-08-06 01:04 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
xfree log file (XFree86.0.log,38.12 KB, text/plain)
2004-01-31 05:58 UTC, Martin Valensky
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Valensky 2004-01-31 05:57:13 UTC
I can't start gdm no ways.

Reproducible: Always
Steps to Reproduce:
1.I'm trying start gdm via '/etc/init.d/xdm start'.
2.Screen is switched to grafical mode and back to console.
3.Xfree can be started via 'startx' (works).



Expected Results:  
Gdm should be started and then I could login.

Portage 2.0.49-r20 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r9, 2.4.
20-gentoo-r9)
=================================================================
System uname: 2.4.20-gentoo-r9 i686 AMD Duron(tm) Processor
Gentoo Base System version 1.4.3.10
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O2 -mcpu=i686 -pipe"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.
1/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-O2 -mcpu=i686 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="http://mirrors.sec.informatik.tu-darmstadt.de/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 apm arts avi berkdb bonobo cdr crypt cups enable-gnome enable-gui 
encode esd foomaticdb gdbm gif gnome gpm gtk gtk2 gtkhtml imlib java jpeg kde 
libg++ libwww mad mikmod motif mozilla mpeg ncurses nls oggvorbis opengl oss pam 
pdflib perl png python qt quicktime readline sdl slang spell ssl svga tcpd 
truetype x86 xml2 xmms xv zlib video_cards_radeon"
 
/var/log/messages
Jan 31 14:27:17 wally gdm[20226]: gdm_main: Here we go...
Jan 31 14:27:17 wally gdm[20226]: XDMCP: Start up on host wally, port 177
Jan 31 14:27:17 wally gdm[20226]: gdm_start_first_unborn_local: Starting :0
Jan 31 14:27:17 wally gdm[20226]: gdm_display_manage: Managing :0
Jan 31 14:27:17 wally gdm[20226]: Resetting counts for loop of death detection
Jan 31 14:27:17 wally gdm[20226]: gdm_display_manage: Forked slave: 20229
Jan 31 14:27:17 wally gdm[20226]: Accepting XDMCP connections...
Jan 31 14:27:17 wally gdm[20229]: gdm_slave_start: Starting slave process for :0
Jan 31 14:27:17 wally gdm[20229]: gdm_slave_start: Loop Thingie
Jan 31 14:27:17 wally gdm[20229]: Sending VT_NUM == -1 for slave 20229
Jan 31 14:27:17 wally gdm[20229]: Sending VT_NUM 20229 -1
Jan 31 14:27:17 wally gdm[20226]: Handling message: 'VT_NUM 20229 -1'
Jan 31 14:27:17 wally gdm[20226]: Got VT_NUM == -1
Jan 31 14:27:17 wally gdm[20229]: gdm_server_start: :0
Jan 31 14:27:17 wally gdm[20229]: gdm_auth_secure_display: Setting up access for 
:0
Jan 31 14:27:17 wally gdm[20229]: gdm_auth_secure_display: Setting up socket 
access
Jan 31 14:27:17 wally gdm[20226]: (child 20229) gdm_slave_usr2_handler: :0 got 
USR2 signal
Jan 31 14:27:17 wally gdm[20229]: gdm_auth_secure_display: Setting up network 
access
Jan 31 14:27:17 wally gdm[20229]: gdm_auth_secure_display: Setting up access for 
:0 - 6 entries
Jan 31 14:27:17 wally gdm[20229]: Sending COOKIE == <secret> for slave 20229
Jan 31 14:27:17 wally gdm[20229]: Sending COOKIE 20229 
76f0f417838dd7114bf752b798fd55d3
Jan 31 14:27:17 wally gdm[20226]: Handling message: 'COOKIE 20229 7...'
Jan 31 14:27:17 wally gdm[20226]: Got COOKIE == <secret>
Jan 31 14:27:17 wally gdm[20229]: gdm_server_spawn: Forked server on pid 20230
Jan 31 14:27:17 wally gdm[20229]: gdm_server_start: Before mainloop waiting for 
server
Jan 31 14:27:17 wally gdm[20226]: (child 20229) gdm_slave_usr2_handler: :0 got 
USR2 signal
Jan 31 14:27:17 wally gdm[20230]: gdm_server_spawn: '/usr/X11R6/bin/X :0 
-nolisten tcp -audit 0 -auth /var/lib/gdm/:0.Xauth vt7'
Jan 31 14:27:17 wally gdm[20229]: gdm_server_start: After mainloop waiting for 
server
Jan 31 14:27:17 wally gdm[20229]: gdm_server_start: Completed :0!
Jan 31 14:27:17 wally gdm[20229]: Sending VT_NUM == 7 for slave 20229
Jan 31 14:27:17 wally gdm[20229]: Sending VT_NUM 20229 7
Jan 31 14:27:17 wally gdm[20226]: (child 20229) gdm_server_usr1_handler: Got 
SIGUSR1, server running
Jan 31 14:27:17 wally gdm[20226]: Handling message: 'VT_NUM 20229 7'
Jan 31 14:27:17 wally gdm[20226]: Got VT_NUM == 7
Jan 31 14:27:17 wally gdm[20229]: Sending XPID == 20230 for slave 20229
Jan 31 14:27:17 wally gdm[20229]: Sending XPID 20229 20230
Jan 31 14:27:17 wally gdm[20226]: (child 20229) gdm_slave_usr2_handler: :0 got 
USR2 signal
Jan 31 14:27:17 wally gdm[20226]: Handling message: 'XPID 20229 20230'
Jan 31 14:27:17 wally gdm[20226]: Got XPID == 20230
Jan 31 14:27:17 wally gdm[20229]: gdm_slave_run: Opening display :0
Jan 31 14:27:17 wally gdm[20226]: (child 20229) gdm_slave_usr2_handler: :0 got 
USR2 signal
Jan 31 14:27:19 wally devfsd[161]: error calling: "unlink" in "GLOBAL"
Jan 31 14:27:19 wally devfsd[161]: error calling: "unlink" in "GLOBAL"
Jan 31 14:27:19 wally devfsd[161]: error calling: "unlink" in "GLOBAL"
Jan 31 14:27:19 wally devfsd[161]: error calling: "unlink" in "GLOBAL"
Jan 31 14:27:19 wally devfsd[161]: error calling: "unlink" in "GLOBAL"
Jan 31 14:27:19 wally devfsd[161]: error calling: "unlink" in "GLOBAL"
Jan 31 14:27:19 wally devfsd[161]: error calling: "unlink" in "GLOBAL"
Jan 31 14:27:19 wally devfsd[161]: error calling: "unlink" in "GLOBAL"
Jan 31 14:27:19 wally devfsd[161]: error calling: "unlink" in "GLOBAL"
Jan 31 14:27:19 wally devfsd[161]: error calling: "unlink" in "GLOBAL"
Jan 31 14:27:19 wally devfsd[161]: error calling: "unlink" in "GLOBAL"
Jan 31 14:27:19 wally devfsd[161]: error calling: "unlink" in "GLOBAL"
Jan 31 14:27:19 wally devfsd[161]: error calling: "unlink" in "GLOBAL"
Jan 31 14:27:19 wally devfsd[161]: error calling: "unlink" in "GLOBAL"
Jan 31 14:27:19 wally devfsd[161]: error calling: "unlink" in "GLOBAL"
Jan 31 14:27:19 wally devfsd[161]: error calling: "unlink" in "GLOBAL"
Jan 31 14:27:19 wally devfsd[161]: error calling: "unlink" in "GLOBAL"
Jan 31 14:27:19 wally devfsd[161]: error calling: "unlink" in "GLOBAL"
Jan 31 14:27:19 wally devfsd[161]: error calling: "unlink" in "GLOBAL"
Jan 31 14:27:19 wally devfsd[161]: error calling: "unlink" in "GLOBAL"
Jan 31 14:27:19 wally devfsd[161]: error calling: "unlink" in "GLOBAL"
Jan 31 14:27:19 wally devfsd[161]: error calling: "unlink" in "GLOBAL"
Jan 31 14:27:19 wally devfsd[161]: error calling: "unlink" in "GLOBAL"
Jan 31 14:27:19 wally devfsd[161]: error calling: "unlink" in "GLOBAL"
Jan 31 14:27:19 wally devfsd[161]: error calling: "unlink" in "GLOBAL"
Jan 31 14:27:19 wally devfsd[161]: error calling: "unlink" in "GLOBAL"
Jan 31 14:27:19 wally devfsd[161]: error calling: "unlink" in "GLOBAL"
Jan 31 14:27:19 wally [fglrx:firegl_umm_init] *ERROR* UMM area already 
initialized!
Jan 31 14:27:19 wally [fglrx:firegl_unlock] *ERROR* Process 20230 using kernel 
context 0
Jan 31 14:27:19 wally devfsd[161]: error calling: "unlink" in "GLOBAL"
Jan 31 14:27:22 wally gdm[20229]: Sending START_NEXT_LOCAL
Jan 31 14:27:22 wally gdm[20226]: Handling message: 'START_NEXT_LOCAL'
Jan 31 14:27:22 wally gdm[20229]: gdm_slave_greeter: Running greeter on :0
Jan 31 14:27:22 wally gdm[20229]: gdm_slave_greeter: Greeter on pid 20294
Jan 31 14:27:22 wally gdm[20229]: Sending GREETPID == 20294 for slave 20229
Jan 31 14:27:22 wally gdm[20229]: Sending GREETPID 20229 20294
Jan 31 14:27:22 wally gdm[20226]: (child 20229) gdm_slave_child_handler
Jan 31 14:27:22 wally gdm[20226]: Handling message: 'GREETPID 20229 20294'
Jan 31 14:27:22 wally gdm[20226]: Got GREETPID == 20294
Jan 31 14:27:22 wally gdm[20226]: (child 20229) gdm_slave_usr2_handler: :0 got 
USR2 signal
Jan 31 14:27:22 wally gdm[20294]: gdm_slave_greeter: Cannot start greeter trying 
default: /usr/bin/gdmlogin
Jan 31 14:27:22 wally gdm[20294]: gdm_slave_greeter: Error starting greeter on 
display :0
Jan 31 14:27:22 wally gdm[20226]: (child 20229) gdm_slave_child_handler
Jan 31 14:27:22 wally gdm[20226]: (child 20229) gdm_slave_child_handler: 20294 
died
Jan 31 14:27:22 wally gdm[20226]: (child 20229) gdm_slave_child_handler: 20294 
returned 4
Jan 31 14:27:22 wally gdm[20226]: (child 20229) gdm_server_stop: Server for :0 
going down!
Jan 31 14:27:22 wally gdm[20226]: (child 20229) gdm_server_stop: Killing server 
pid 20230
Jan 31 14:27:22 wally gdm[20226]: mainloop_sig_callback: Got signal 17
Jan 31 14:27:22 wally gdm[20226]: gdm_cleanup_children: child 20229 returned 4
Jan 31 14:27:22 wally gdm[20226]: gdm_child_action: Aborting display :0
Jan 31 14:27:22 wally gdm[20226]: gdm_display_unmanage: Stopping :0 (slave pid: 
0)
Jan 31 14:27:22 wally gdm[20226]: (child 20229) gdm_server_stop: Server pid 
20230 dead
Jan 31 14:27:22 wally gdm[20226]: main: Exited main loop
Jan 31 14:27:43 wally (wally-6106): GConf server is not in use, shutting down.
Jan 31 14:27:43 wally (wally-6106): Exiting
Comment 1 Martin Valensky 2004-01-31 05:58:09 UTC
Created attachment 24685 [details]
xfree log file
Comment 2 foser (RETIRED) gentoo-dev 2004-02-17 15:51:06 UTC
sorry there has been no move on this, is this stil a problem ?

What xfree are you using exactly ? Try starting gdm from an xterm, see if there is any ouput, since it's most likely not xfree itself.
Comment 3 atom 2004-05-05 09:02:26 UTC
i am having this same issue. it first surfaced when i upgraded gtk to 2.4.0-r1. at the time i was using gdm-2.4.1.7-r1. this first problem was gdm would start and then just hang there displaying the pointer and nothing else. i wondered if it was an issue with the gtk upgrade, so i reinstalled gdm. this left me with the symptoms in the bug. X starts then crashes repeatedly. i do want to point out that my messages log shows:

Apr 20 00:37:20 default kernel: mtrr: your processor doesn't support write-combining
Apr 20 00:37:20 default kernel: atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
Apr 20 00:37:20 default kernel: atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
Apr 20 00:37:20 default kernel: atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
Apr 20 00:37:20 default kernel: atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.


i noticed another user in the forums with this issue as well.

*  x11-base/xfree
      Latest version installed: 4.3.99.902-r2


Portage 2.0.50-r6 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.6.2-rc1-gentoo)
=================================================================
System uname: 2.6.2-rc1-gentoo i686 AMD-K7(tm) Processor
Gentoo Base System version 1.4.10
distcc 2.13 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled]
ccache version 2.3 [enabled]
Autoconf: sys-devel/autoconf-2.58-r1
Automake: sys-devel/automake-1.8.3
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O3 -march=i686 -funroll-loops -pipe"
CHOST="i686-pc-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/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -march=i686 -funroll-loops -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache distcc sandbox"
GENTOO_MIRRORS="ftp://ftp.ussg.iu.edu/pub/linux/gentoo"
MAKEOPTS="-j5"
PKGDIR="/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.us.gentoo.org/gentoo-portage"
USE="3dnow X aalib acpi alsa apache2 apm avi berkdb cdr cjk crypt cups curl dga dvd dvdr encode esd evms2 faad flac flash foomaticdb gd gdbm gif gnome gnutls gphoto2 gpm gstreamer gtk gtk2 gtkhtml imap imlib ipv6 java jpeg kde kerberos libg++ libwww lirc mad matroska mikmod mmx motif mozilla mpeg mysql ncurses nls nvidia oggvorbis opengl oss pam pdflib perl png python qt quicktime readline samba scanner sdl slang spell sse ssl svga tcltk tcpd tiff truetype v4l vim-with-x wxwindows x86 xml2 xmms xosd xv xvid zlib"
Comment 4 atom 2004-05-05 09:03:43 UTC
this happens with gdm-2.4.4.7-r1 as well.
Comment 5 foser (RETIRED) gentoo-dev 2004-05-05 09:06:18 UTC
if it's a problem with xfree-4.3.99 only i don't think we're going to do much about it ...
Comment 6 Donnie Berkholz (RETIRED) gentoo-dev 2004-05-05 09:44:00 UTC
Please try to reproduce this with xorg-x11.
Comment 7 atom 2004-05-05 14:17:40 UTC
ok, switched to xorg-x11. gdm still crashing repeatedly. using gdm-2.4.4.7-r1

Apr 20 05:02:56 default gdm[6450]: gdm_main: Here we go...
Apr 20 05:02:56 default gdm[6450]: gdm_start_first_unborn_local: Starting :0
Apr 20 05:02:56 default gdm[6450]: gdm_display_manage: Managing :0
Apr 20 05:02:56 default gdm[6450]: loop check: last_start 0, last_loop 0, now: 1082451776, retry_count: 0
Apr 20 05:02:56 default gdm[6450]: Resetting counts for loop of death detection
Apr 20 05:02:56 default gdm[6452]: gdm_slave_start: Starting slave process for :0
Apr 20 05:02:56 default gdm[6452]: gdm_slave_start: Loop Thingie
Apr 20 05:02:56 default gdm[6452]: Sending VT_NUM == -1 for slave 6452
Apr 20 05:02:56 default gdm[6452]: Sending VT_NUM 6452 -1
Apr 20 05:02:56 default gdm[6450]: gdm_display_manage: Forked slave: 6452
Apr 20 05:02:56 default gdm[6450]: Handling message: 'VT_NUM 6452 -1'
Apr 20 05:02:56 default gdm[6450]: Got VT_NUM == -1
Apr 20 05:02:56 default gdm[6452]: gdm_server_start: :0
Apr 20 05:02:56 default gdm[6452]: gdm_auth_secure_display: Setting up access for :0
Apr 20 05:02:56 default gdm[6450]: (child 6452) gdm_slave_usr2_handler: :0 got USR2 signal
Apr 20 05:02:56 default gdm[6452]: gdm_auth_secure_display: Setting up access
Apr 20 05:02:56 default gdm[6452]: gdm_auth_secure_display: Setting up access for :0 - 1 entries
Apr 20 05:02:56 default gdm[6452]: Sending COOKIE == <secret> for slave 6452
Apr 20 05:02:56 default gdm[6452]: Sending COOKIE 6452 ce...
Apr 20 05:02:56 default gdm[6450]: Handling message: 'COOKIE 6452 ce...'
Apr 20 05:02:56 default gdm[6450]: Got COOKIE == <secret>
Apr 20 05:02:56 default gdm[6452]: gdm_server_spawn: Forked server on pid 6453
Apr 20 05:02:56 default gdm[6452]: do_server_wait: Before mainloop waiting for server
Apr 20 05:02:56 default gdm[6450]: (child 6452) gdm_slave_usr2_handler: :0 got USR2 signal
Apr 20 05:02:57 default gdm[6453]: gdm_server_spawn: '/usr/X11R6/bin/X :0 -nolisten tcp -audit 0 -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt7'
Apr 20 05:02:57 default gdm[6452]: gdm_server_start: After mainloop waiting for server
Apr 20 05:02:57 default gdm[6452]: gdm_server_start: Completed :0!
Apr 20 05:02:57 default gdm[6452]: Sending VT_NUM == 7 for slave 6452
Apr 20 05:02:57 default gdm[6452]: Sending VT_NUM 6452 7
Apr 20 05:02:57 default gdm[6450]: (child 6452) gdm_server_usr1_handler: Got SIGUSR1, server running
Apr 20 05:02:57 default gdm[6450]: Handling message: 'VT_NUM 6452 7'
Apr 20 05:02:57 default gdm[6450]: Got VT_NUM == 7
Apr 20 05:02:57 default gdm[6452]: Sending XPID == 6453 for slave 6452
Apr 20 05:02:57 default gdm[6452]: Sending XPID 6452 6453
Apr 20 05:02:57 default gdm[6450]: (child 6452) gdm_slave_usr2_handler: :0 got USR2 signal
Apr 20 05:02:57 default gdm[6450]: Handling message: 'XPID 6452 6453'
Apr 20 05:02:57 default gdm[6450]: Got XPID == 6453
Apr 20 05:02:57 default gdm[6452]: gdm_slave_run: Opening display :0
Apr 20 05:02:57 default gdm[6450]: (child 6452) gdm_slave_usr2_handler: :0 got USR2 signal
Apr 20 05:02:58 default kernel: mtrr: your processor doesn't support write-combining
Apr 20 05:03:00 default gdm[6452]: Sending START_NEXT_LOCAL
Apr 20 05:03:00 default gdm[6450]: Handling message: 'START_NEXT_LOCAL'
Apr 20 05:03:00 default gdm[6452]: gdm_slave_greeter: Running greeter on :0
Apr 20 05:03:00 default gdm[6450]: (child 6452) gdm_slave_child_handler
Apr 20 05:03:00 default gdm[6452]: gdm_slave_greeter: Greeter on pid 6458
Apr 20 05:03:00 default gdm[6452]: Sending GREETPID == 6458 for slave 6452
Apr 20 05:03:00 default gdm[6452]: Sending GREETPID 6452 6458
Apr 20 05:03:00 default gdm[6450]: Handling message: 'GREETPID 6452 6458'
Apr 20 05:03:00 default gdm[6450]: Got GREETPID == 6458
Apr 20 05:03:00 default CRON[6460]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons ) 
Apr 20 05:03:00 default gdm[6450]: (child 6452) gdm_slave_usr2_handler: :0 got USR2 signal
Apr 20 05:03:00 default gdm[6452]: gdm_slave_wait_for_login: In loop
Apr 20 05:03:00 default gdm[6450]: (child 6452) gdm_slave_child_handler
Apr 20 05:03:00 default gdm[6450]: (child 6452) gdm_slave_child_handler: 6458 died
Apr 20 05:03:00 default gdm[6450]: (child 6452) gdm_slave_child_handler: 6458 died of 6
Apr 20 05:03:00 default gdm[6452]: term_quit: Final cleanup
Apr 20 05:03:00 default gdm[6452]: gdm_slave_quick_exit: Will kill everything from the display
Apr 20 05:03:00 default gdm[6452]: Running gdm_verify_cleanup and pamh != NULL
Apr 20 05:03:00 default gdm[6452]: gdm_server_stop: Server for :0 going down!
Apr 20 05:03:00 default gdm[6452]: gdm_server_stop: Killing server pid 6453
Apr 20 05:03:01 default gdm[6452]: gdm_server_stop: Server pid 6453 dead
Apr 20 05:03:01 default gdm[6452]: gdm_slave_quick_exit: Killed everything from the display
Apr 20 05:03:01 default gdm[6450]: mainloop_sig_callback: Got signal 17
Apr 20 05:03:01 default gdm[6450]: gdm_cleanup_children: child 6452 returned 65
Apr 20 05:03:01 default gdm[6450]: gdm_child_action: In remanage
Comment 8 atom 2004-05-05 14:19:01 UTC
and messages:

Apr 20 04:37:13 default kernel: mtrr: your processor doesn't support write-combining
Apr 20 04:44:19 default last message repeated 5 times
Apr 20 05:00:45 default last message repeated 2 times
Apr 20 05:02:58 default last message repeated 6 times
Comment 9 atom 2004-05-05 15:33:27 UTC
i have solved this problem for me. i recompiled my kernel (i was actually using 2.6.3 contrary to what my emerge info shows). i am now running 2.6.5 with the same kernel config and gdm works flawlessly for me. there appears to be an issue with the mtrr, gtk-2.4, and gdm with 2.6.3? let me know if you would like me to test anything.

thanks
Comment 10 foser (RETIRED) gentoo-dev 2004-05-06 07:12:12 UTC
dunno, if it works with newer kernels I don't care to investigate much further. I'm on a kernel 2.6.3 system btw and it works just fine.

Anyone got any other insights, otherwise i'm closing this ?
Comment 11 Mike Gardiner (RETIRED) gentoo-dev 2004-08-06 01:04:27 UTC
See foser's previous comment