[NBLUG/talk] ADMTEK wireless Driver Update, sort of...
thiessen at sonic.net
Mon Jun 7 11:40:45 PDT 2004
On Mon, Jun 07, 2004 at 12:21:48PM -0700, Dave Sisley wrote:
> Thanks for the responses, guys.
> I don't think I can use Justin's suggestion (sshing from outside),
> since I don't have a wireless connection to my laptop (the source of
> my original problem!).
Sure thing. I just thought that maybe your laptop had wired ethernet built-in,
and that you could hook this up as well and use it for debugging.
In the end, even if you can't get the sysreq key to work, you should still be
able to use a null-modem cable and log in from another computer via the serial
port. AFAIK, this is the most foolproof way of getting back into your box,
so if alt-sysrq doesn't work, you may be reduced to this method.
Best of luck. I know how frustrating hardware problems can be...
> As for the tips from Lincoln and Augie, they look more promising.
> Only problem is that if I try using alt-sysrq, I get a screenshot
> dialog. I'm assuming that this is because I don't have the kernel
> configured to enable the sysreq key. I hope you will understand if,
> given my obvious lack of full-strength linux wizardry, I don't go and
> re-compile my kernel. I have enough troubles!
> I must say though, that the page Augie referenced
> (http://linux.about.com/library/bl/open/newbie/blnewbie5.1.htm) looks
> like a cool resource, especially for those wishing to up their magic
> I'm hoping that this system-locking-module problem is only temporary,
> and that the maintainer of the module (Michael Wu - let's give the guy
> a round of applause) can iron this out eventually. I'm fighting the
> urge to run to ebay or Best Buy and just spending my way out of this
> Thanks again!
> Dave Sisley
> dsisley at arczip.com
> talk mailing list
> talk at nblug.org
More information about the talk