From: Paul Fertser <fercerpav@gmail.com>
To: b43-dev@lists.infradead.org
Subject: Issues with 14e4:4315 on "lenovo ideapad s9" - works only after wl
Date: Sun, 10 Oct 2010 21:03:11 +0400 [thread overview]
Message-ID: <20101010170311.GW1593@home.pavel.comp> (raw)
In-Reply-To: <AANLkTinYvvk0mYTgKu2gJziLSEoZnMm491wUbZ4BO_Sf@mail.gmail.com>
On Sun, Oct 10, 2010 at 08:39:04AM -0700, Larry Finger wrote:
> 2010/10/10 Paul Fertser <[1]fercerpav@gmail.com>
> On Sat, Oct 09, 2010 at 11:37:37PM +0200, Gabor Stefanik wrote:
> > The PhoenixBIOS DMA problem is known not to appear if wl has been
> > loaded beforehand. Be patient, we are working on this. (But good to
> > know the S9 also reproduces it - it's probably less expensive than the
> > S10 for the team to buy.)
>
> And yes, i know remote debugging is usually a pain but i think i can not
> only provide ssh access but also some means to physically power-cycle the
> device (though it'd take some time to find necessary parts).
> ?
> Before devoting too much effort to debugging, please try a recent
> compat-wireless version. There were some changes in b43 that are implemented
> there that might not be in your kernel.
I hoped Compat-wireless backport release: compat-wireless-2010-10-01-10-gb9b0a4f
is recent enough.
As for the remote debugging, it seems to me that having an ssh access
coupled with a computer-controlled outlet would be almost identical to
local, right?
> On my HP Mini 110 netbook, those fixes got rid of the DMA errors. Will
> they allow your S9 to cold boot b43?
I wonder if those DMA errors are just a sign of some other problem because
the driver automatically switches to PIO but it doesn't help.
--
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercerpav at gmail.com
next prev parent reply other threads:[~2010-10-10 17:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-09 11:53 Issues with 14e4:4315 on "lenovo ideapad s9" - works only after wl Paul Fertser
2010-10-09 18:36 ` Paul Fertser
2010-10-09 20:37 ` Gábor Stefanik
2010-10-09 21:32 ` Paul Fertser
2010-10-09 21:37 ` Gábor Stefanik
2010-10-10 7:21 ` Paul Fertser
2010-10-10 15:39 ` Larry Finger
2010-10-10 17:03 ` Paul Fertser [this message]
2010-10-11 1:50 ` Larry Finger
2010-10-11 7:37 ` Rafał Miłecki
2010-10-13 6:58 ` PIO mode (was: Re: Issues with 14e4:4315 on "lenovo ideapad s9" - works only after wl) Paul Fertser
2010-10-17 22:35 ` PIO mode Larry Finger
2010-10-18 4:11 ` Paul Fertser
2010-10-18 19:57 ` Larry Finger
2010-10-19 0:43 ` Paul Fertser
2010-10-19 16:04 ` Larry Finger
2010-10-19 16:22 ` Paul Fertser
2010-10-19 17:02 ` Larry Finger
2010-10-20 17:37 ` Larry Finger
2010-10-20 17:54 ` Paul Fertser
2010-10-20 18:31 ` Larry Finger
2010-10-20 19:37 ` MMIO trace for "warm" boot of b43 on IdeaPad S9 (was: Re: PIO mode) Paul Fertser
2010-10-20 22:19 ` Larry Finger
2010-10-21 6:05 ` MMIO trace for "warm" boot of b43 on IdeaPad S9 Paul Fertser
2010-10-21 8:53 ` Transfer zeroes via ssh test (was: Re: PIO mode) Paul Fertser
2010-10-21 14:27 ` Larry Finger
2010-10-21 20:55 ` Michael Büsch
2010-10-10 16:50 ` Issues with 14e4:4315 on "lenovo ideapad s9" - works only after wl Gábor Stefanik
2010-10-12 22:12 ` Paul Fertser
2010-10-12 23:05 ` Paul Fertser
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=20101010170311.GW1593@home.pavel.comp \
--to=fercerpav@gmail.com \
--cc=b43-dev@lists.infradead.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).