From: Hetz Ben Hamo <hetzbh@gmail.com>
To: esrever_otua@pythonhacker.is-a-geek.net, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] KQEMU error, unable to get major 254
Date: Fri, 11 Feb 2005 03:47:11 +0200 [thread overview]
Message-ID: <41e41e7a05021017473367d235@mail.gmail.com> (raw)
In-Reply-To: <1108084799.5629.3.camel@localhost.localdomain>
Earlier in IRC someone mentioned that changing the code to work with
major 253 solved this issue...
Can someone tell where do you "officially" can request a major number
these days? (if it's possible)..
Thanks,
Hetz
On Fri, 11 Feb 2005 14:19:59 +1300, Darryl Dixon
<esrever_otua@pythonhacker.is-a-geek.net> wrote:
> Hi Fabrice,
>
> I have managed to download the latest cvs and tried it out on Fedora
> Core 3 (kernel 2.6.10). It seems that for some reason the kqemu module is
> unable to be assigned major device number 254. Below are the errors:
> [root@localhost ~]# modprobe kqemu
> FATAL: Error inserting kqemu (/lib/modules/2.6.10-1.760_FC3/misc/kqemu.ko):
> Device or resource busy
> [root@localhost ~]# tail /var/log/messages
> Feb 11 14:14:07 localhost kernel: QEMU Accelerator Module version 1.0.0,
> Copyright (c) 2005 Fabrice Bellard
> Feb 11 14:14:07 localhost kernel: This is a proprietary product. Read the
> LICENSE file for more information
> Feb 11 14:14:07 localhost kernel: Redistribution of this module is
> prohibited without authorization
> Feb 11 14:14:07 localhost kernel: kqemu: could not get major 254
>
>
> Regards,
>
> --
> Darryl Dixon <esrever_otua@pythonhacker.is-a-geek.net>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
>
>
prev parent reply other threads:[~2005-02-11 2:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-11 1:19 [Qemu-devel] KQEMU error, unable to get major 254 Darryl Dixon
2005-02-11 1:41 ` [Qemu-devel] [PATCH] " Darryl Dixon
2005-02-11 1:47 ` Hetz Ben Hamo [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=41e41e7a05021017473367d235@mail.gmail.com \
--to=hetzbh@gmail.com \
--cc=esrever_otua@pythonhacker.is-a-geek.net \
--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).