public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: meino.cramer@gmx.de
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Cohorent pool size too small...
Date: Sun, 5 Oct 2014 16:54:15 +0200	[thread overview]
Message-ID: <20141005145415.GE3856@solfire> (raw)
In-Reply-To: <m0rjk4$1d9$1@ger.gmane.org>

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...?

By the way: I hacked the kernel to provide more coherent pool size
with the effect that NO module was loaded anymore...without any trace
in the dmesg out (beside the greater pool size itsself...)...

best regards,
mcc



> 
> > [    9.931976] usb 2-1: New USB device found, idVendor=148f, idProduct=7601
> > [    9.931994] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> > [   10.077532] rtusb init rt2870 --->
> > [   10.079338] 
> > 
> > === pAd = e0c58000, size = 860808 ===
> > 
> > [   10.079939] ERROR: 256 KiB atomic DMA coherent pool is too small!
> > Please increase it with coherent_pool= kernel parameter!
> > [   10.079968] <-- ERROR in Alloc Bulk buffer for HTTxContext!
> > [   10.079983] ---> RTMPFreeTxRxRingMemory
> > [   10.080026] <--- RTMPFreeTxRxRingMemory
> > [   10.080040] ERROR!!! Failed to allocate memory - TxRxRing
> > 
> > 
> > But 
> > 
> > cat /proc/cmdline 
> > 
> > shows:
> > 
> > console=tty1 root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait fixrtc capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G,coherent_pool=2M
> > 
> > (this is an embedded device, thats why there are the other parameters
> > around...)
> > 
> > I do not find any way to set this parameter while compiling the
> > kernel. And setting the kernel parameter seems not to work either...
> > 
> > Lost?
> > 
> > ...or am I only blind... ? ;)
> > 
> > How can I increase the cohorent pool size successfully?
> > 
> > Best regards,
> > mcc
> > 
> > PS: The driver sources are not included in the kernel and have to be
> > compiled externally/extra...
> > 
> > 
> > 
> 
> 
> 


  reply	other threads:[~2014-10-05 14:54 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 [this message]
2014-10-05 17:31     ` walt
2014-10-05 17:44       ` meino.cramer
2014-10-06  8:43         ` Hinnerk van Bruinehsen
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=20141005145415.GE3856@solfire \
    --to=meino.cramer@gmx.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