From: Hinnerk van Bruinehsen <h.v.bruinehsen@fu-berlin.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Cohorent pool size too small...
Date: Mon, 6 Oct 2014 10:43:57 +0200 [thread overview]
Message-ID: <20141006084357.GC12584@TranscendTheRubicon.zedat.fu-berlin.de> (raw)
In-Reply-To: <20141005174403.GF3856@solfire>
[-- Attachment #1: Type: text/plain, Size: 1814 bytes --]
On Sun, Oct 05, 2014 at 07:44:03PM +0200, meino.cramer@gmx.de wrote:
> walt <w41ter@gmail.com> [14-10-05 19:36]:
> > On 10/05/2014 07:54 AM, meino.cramer@gmx.de wrote:
> > > walt <w41ter@gmail.com> [14-10-05 16:16]:
> > >> > On 10/05/2014 06:52 AM, meino.cramer@gmx.de wrote:
> > >>> > > Hi,
> > >>> > >
> > >>> > > while trying to get a mt7601sta (UWN200 WiFi dongle) driver running
> > >>> > > and working I came accross this in the dmesg output:
> > >>> > >
> > >>> > > [ 9.931938] usb 2-1: device v148f p7601 is not supported
> > >> >
> > >> > This looks to me like it's the real error, not the one below.
> > > What I dont understand is: If I provide the kernel driver...why does
> > > the kernel "decides" not to support the hardware the driver itsself
> > > supports...?
> >
> > Where did you get the driver? Are you sure it's really the right one?
> >
> >
> >
>
> One of the main maintainer for the Beaglebone black kernel sources
> (Robert C. Nelson) point me to his git repository of this driver.
>
> I am now back to kernel 3.8.13, where this stuff runs...
> (The kernel I tried it before was 3.14.19)
> But this kernel version get no much updates thess days and is
> somehow old...
>
So you tried to run a driver for 3.8.x on a 3.14.x kernel?
Such things often result in breakage as, while the kernels interface to
userspace is very stable, the internal interfaces aren't stable at all. Likely
there would be some other stuff necessary to get the driver to work properly.
Some googling around led me to [1] though, which seems to imply that there is
support on newer kernels (3.15.10 and newer), if you use the right patch...
So maybe you are sucessful with that...
WKR
Hinnerk
[1] http://www.spinics.net/lists/linux-wireless/msg126291.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-10-06 8:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-05 13:52 [gentoo-user] Cohorent pool size too small meino.cramer
2014-10-05 14:12 ` [gentoo-user] " walt
2014-10-05 14:54 ` meino.cramer
2014-10-05 17:31 ` walt
2014-10-05 17:44 ` meino.cramer
2014-10-06 8:43 ` Hinnerk van Bruinehsen [this message]
2014-10-06 16:34 ` meino.cramer
2014-10-06 18:47 ` thegeezer
2014-10-06 22:30 ` meino.cramer
2014-10-07 7:28 ` Hinnerk van Bruinehsen
2014-10-07 15:51 ` meino.cramer
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=20141006084357.GC12584@TranscendTheRubicon.zedat.fu-berlin.de \
--to=h.v.bruinehsen@fu-berlin.de \
--cc=gentoo-user@lists.gentoo.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