[Qemu-devel] kqemu failure

[Qemu-devel] kqemu failure

[katakombi]

Hi pals,

  I succeeded in building the kernel module, but if I modprobe it tells me

root@1[katakombi]# modprobe kqemu
FATAL: Error inserting kqemu (/lib/modules/2.6.7/misc/kqemu.ko): Device or 
resourcebusy

or (on console, additionally):
kqemu: could not get major 254

I think any other loaded module may exclude the module, is it no good to have 
an win4lin-patched kernel running?


I also have quite some stuff loaded:

root@1[katakombi]# lsmod
Module                  Size  Used by
appletalk              29876  2
ipx                    23980  2
intel_mch_agp           7952  0
sworks_agp              6944  0
amd_k7_agp              5772  0
ali_agp                 5248  0
sis_agp                 5892  1
ati_agp                 6412  0
nvidia_agp              5788  0
via_agp                 6784  0
intel_agp              16156  0
agpgart                26408  10 
intel_mch_agp,sworks_agp,amd_k7_agp,ali_agp,sis_agp,ati_agp,nvidia_agp,via_agp,intel_agp
nvidia               3466652  12
ipt_state               1792  1
ipt_MASQUERADE          3072  1
ipt_LOG                 6016  7
iptable_mangle          2304  0
iptable_filter          2432  1
iptable_nat            21036  2 ipt_MASQUERADE
ip_conntrack           28936  3 ipt_state,ipt_MASQUERADE,iptable_nat
ip_tables              16256  6 
ipt_state,ipt_MASQUERADE,ipt_LOG,iptable_mangle,iptable_filter,iptable_nat
ipv6                  222176  8
parport_pc             27712  1
lp                      8620  0
parport                20672  2 parport_pc,lp
binfmt_misc             7944  1
apm                    15464  2
ds                     13572  0
yenta_socket           17280  0
pcmcia_core            51652  2 ds,yenta_socket
8250                   15840  0
serial_core            18688  1 8250
hfs                    39684  0
minix                  27140  0
ntfs                  110060  0
nls_iso8859_1           3968  0
nls_cp437               5632  0
tuner                  16780  0
tvaudio                19852  0
bttv                  138828  0
video_buf              16132  1 bttv
i2c_algo_bit            8840  1 bttv
v4l2_common             5120  1 bttv
btcx_risc               3976  1 bttv
i2c_core               18580  4 tuner,tvaudio,bttv,i2c_algo_bit
videodev                7424  1 bttv
8139too                21376  0
mii                     3968  1 8139too
snd_emu10k1            87080  2
snd_rawmidi            21824  1 snd_emu10k1
snd_seq_device          7564  2 snd_emu10k1,snd_rawmidi
snd_ac97_codec         68088  1 snd_emu10k1
snd_pcm_oss            48296  0
snd_mixer_oss          17152  1 snd_pcm_oss
snd_pcm                80520  3 snd_emu10k1,snd_ac97_codec,snd_pcm_oss
snd_timer              22916  2 snd_emu10k1,snd_pcm
snd_page_alloc          9352  2 snd_emu10k1,snd_pcm
snd_util_mem            3968  1 snd_emu10k1
snd_hwdep               8480  1 snd_emu10k1
snd                    50020  14 
snd_emu10k1,snd_rawmidi,snd_seq_device,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer,snd_util_mem,snd_hwdep
soundcore               7264  1 snd
sis900                 16516  0
crc32                   4096  2 8139too,sis900
joydev                  7872  0
tsdev                   5376  0
evdev                   7040  0
usbhid                 28608  0
floppy                 53200  0
uhci_hcd               28176  0
ohci_hcd               18692  0
root@1[katakombi]#                  


I'd appreciate any help,
 thanks
   Stefan K. >8^)

Re: [Qemu-devel] kqemu failure

[katakombi]

Argh,
  sometimes reading helps!
Sorry for bothering, I created the device by running the install script and 
all's well :)


SK >8^)

Re: [Qemu-devel] kqemu failure

[Magnus Damm]

Hello,

On Tue, 15 Feb 2005 19:58:38 +0100, katakombi <katakombi@web.de> wrote:
> Hi pals,
> 
>   I succeeded in building the kernel module, but if I modprobe it tells me
> 
> root@1[katakombi]# modprobe kqemu
> FATAL: Error inserting kqemu (/lib/modules/2.6.7/misc/kqemu.ko): Device or
> resourcebusy
> 
> or (on console, additionally):
> kqemu: could not get major 254

Something on your system is probably already using major 254. A wild
guess is the pcmcia stuff. Have a look at the majors in use in
/proc/devices. Try "cat /proc/devices | grep 254" and see what comes
out.

Try to patch the code with the major changing patches posted to this list.

Good luck!

/ magnus