[lkml]   [2000]   [Dec]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subject2.2.18 and joy-gravis.o
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 5.50.4611.1300" name=GENERATOR>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Is the joy-gravis module non-working in 2.2.18
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>setup:</FONT></DIV>
<DIV><FONT face=Arial size=2>es1370 on a K6-2 400&nbsp;/ ALi 15xx board, Gravis
XTerminator gamepad</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>I'm loading the module with joystick=1 to enable
the gameport, and it shows in dmesg, loading joystick module, then when I
modprobe joy-gravis, I get this output:</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>lib/modules/.../misc/joy-gravis.o: init_module:
Device or resource busy<BR>/lib/modules/.../misc/joy-gravis.o: insmod
/lib/modules/.../misc/joy-gravis.o failed</FONT></DIV>
<DIV><FONT size=2></FONT>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>This also happens with the emu10k1 sound
<DIV><FONT face=Arial size=2>Before when the boot-time gameport hack was used,
the gamepad module loaded up fine.</FONT></DIV></BODY></HTML>
 \ /
  Last update: 2005-03-22 12:52    [W:0.038 / U:0.272 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site