From: "Nick Manley" <darkhack@gmail.com>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IRQ Issues with 2.6.17.8
Date: Sun, 13 Aug 2006 13:02:34 -0500 [thread overview]
Message-ID: <6b4360c80608131102g5fa30b21gfc9b2f83996a1f63@mail.gmail.com> (raw)
In-Reply-To: <1155489057.24077.152.camel@localhost.localdomain>
I'm not a kernel hacker so I don't know a whole lot about it but I
figured that these errors would be the cause of ndiswrapper not
working correctly since they appear even without it installed and not
to mention the odd behavior that occurs. Depending on exactly which
distro or kernel that I am using, sometimes ndiswrapper will cause a
kernel panic and other times I can load the driver but no new network
interface would appear. I suspected that the culprit would be that
the kernel isn't properly assigned my wireless card an IRQ.
>From versions 2.6.11 through 2.6.15.x my system would not boot at all
unless I passed some kind of parameter (like irqpoll or acpi=off) and
it wasn't until 2.6.16 that this was fixed. My line of thinking was
that maybe the problem still existed and that my USB wireless card
(SMC2862-W) was not being recognized.
I'm not a master of kernel messages but a few of the messages such as
the "mp-bios bug" and "cannot allocate region 3 of device" which
appeared during the boot process of several distros made me worry.
I'll report this to the ndiswrapper developers. I'm sorry if I took
up your time. I really appreciate your efforts. Thank you for all of
your help.
On 8/13/06, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>
> Looking at the trace I see only a couple of things and neither look like
> problems with the kernel
>
> - your distribution seems to be loading the wrong driver for the network
> card (8139cp not 8139too). Take that up with the distro provider I
> suspect or check your config has the right drivers included
>
> - The BIOS timer setup is a bit odd in the BIOS. From dmesg we select
> the timer via virtual wire mode and sort that out
>
> and the "Cannot allocate resource" one looks harmless too.
>
>
>
> So what actual problems are you really seeing (other than the expected
> 'NDISwrapper doesn't work')
>
>
next prev parent reply other threads:[~2006-08-13 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-13 15:36 Nick Manley
2006-08-13 17:10 ` Alan Cox
2006-08-13 18:02 ` Nick Manley [this message]
2006-08-13 19:08 ` Alan Cox
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=6b4360c80608131102g5fa30b21gfc9b2f83996a1f63@mail.gmail.com \
--to=darkhack@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®