From: Christian Lamparter <chunkeey@googlemail.com>
To: James Grossmann <cctsurf@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Prism54/p54pci
Date: Fri, 6 Nov 2009 21:33:38 +0100 [thread overview]
Message-ID: <200911062133.38842.chunkeey@googlemail.com> (raw)
In-Reply-To: <167ae39b0911061137m72a1e7e9le0e2b59b64be2821@mail.gmail.com>
On Friday 06 November 2009 20:37:00 James Grossmann wrote:
> Doing it from the console doesn't seem to give a kernel oops... it
> just locks up the computer such that I can't even change the caps lock
> status. It starts the connection, and then the activity light on the
> card goes on and the computer is locked up.
well, there are other ways to capture the oops, but I don't think
your laptop has a serial console or a real reset button?!
does your caps lock & scroll lock LED blink? (they should)
does the kernel reboot itself (after ~10 seconds), if you add
panic=10
to the kernel-parameters in grub configuration?
do you have some sort of bootsplash or frame buffer console?
(e.g. KMS/vesa/etc...) because these advanced features can make it
really hard to get the message to the screen before it goes black.
is there nothing in /var/log/syslog after a crash?
> With regard to the losing connection/timing out, I'm seeing that a
> fair amount, when I have data transferring (watching an active ssh
> connection, or streaming audio), and especially when I'm not doing
> anything...
well, there could be several different things, I hope you're using
services like Network-manager, wpa_supplicant to manage your connection.
Because they will automatically reconnect as soon as the link dies.
what could be interesting: iw dev wlanX scan / iwlist wlanX scan
dump from your AP... especially the TSF/tsf value,
(it's a hexadecimal value which acts like a uptime for the AP)
Regards,
Chr
next prev parent reply other threads:[~2009-11-06 20:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 21:00 Prism54/p54pci James Grossmann
2009-10-08 16:28 ` Prism54/p54pci Larry Finger
2009-10-27 18:37 ` Prism54/p54pci Luis R. Rodriguez
[not found] ` <167ae39b0910310615k5475e5cp55d1c0d60e7a443b@mail.gmail.com>
2009-10-31 13:26 ` Prism54/p54pci Luis R. Rodriguez
2009-10-31 14:11 ` Prism54/p54pci James Grossmann
2009-10-31 21:24 ` Prism54/p54pci Christian Lamparter
2009-11-02 5:07 ` Prism54/p54pci James Grossmann
[not found] ` <200911021611.37354.chunkeey@googlemail.com>
[not found] ` <167ae39b0911060900i2c8f4a78w4edecdcec36f1a38@mail.gmail.com>
2009-11-06 17:48 ` Prism54/p54pci Christian Lamparter
2009-11-06 18:45 ` Prism54/p54pci James Grossmann
2009-11-06 19:14 ` Prism54/p54pci Christian Lamparter
2009-11-06 19:37 ` Prism54/p54pci James Grossmann
2009-11-06 20:33 ` Christian Lamparter [this message]
2009-11-06 20:52 ` Prism54/p54pci James Grossmann
2009-11-06 21:45 ` Prism54/p54pci Christian Lamparter
2009-11-06 22:17 ` Prism54/p54pci James Grossmann
2009-11-12 16:17 ` Prism54/p54pci Christian Lamparter
2009-11-12 18:56 ` Prism54/p54pci Tim Gardner
2009-11-12 19:37 ` Prism54/p54pci Christian Lamparter
2009-11-12 19:45 ` Prism54/p54pci Luis R. Rodriguez
2009-11-12 19:54 ` Prism54/p54pci Tim Gardner
2009-11-13 1:49 ` Prism54/p54pci Luis R. Rodriguez
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=200911062133.38842.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=cctsurf@gmail.com \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).