From: Magnus Damm <magnus.damm@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] kqemu failure
Date: Tue, 15 Feb 2005 21:11:54 +0100 [thread overview]
Message-ID: <aec7e5c305021512116b5eddd3@mail.gmail.com> (raw)
In-Reply-To: <200502151958.38274.katakombi@web.de>
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
prev parent reply other threads:[~2005-02-15 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 18:58 [Qemu-devel] kqemu failure katakombi
2005-02-15 19:55 ` katakombi
2005-02-15 20:11 ` Magnus Damm [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aec7e5c305021512116b5eddd3@mail.gmail.com \
--to=magnus.damm@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).