From: "Paweł Lasek" <pawel.lasek@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] PCICIA Modem
Date: Mon, 26 Dec 2005 15:19:12 +0100 [thread overview]
Message-ID: <9f3897940512260619i6d205e38ma107a2eb68aaa6a0@mail.gmail.com> (raw)
In-Reply-To: <20051226090025.438b041a@localhost.localdomain>
On 12/26/05, Martin C. Atkins <martin_ml@parvat.com> wrote:
> I've got something with (I believe) the same number (and from the same source - a VAIO).
> (I don't have it handy to double check the model number, however)
> My modem is a softmodem, and so no, it won't "just" show up as a serial port!
> (And I had a good deal of trouble getting it to work under Linux - in fact,
> I eventually gave up - the modem worked - eventually, just - but suspend/resume broke it)
Then it's screwed, I say... If it's soft-modem, the only available
solution is to write a driver for it. However isn't it rather rare for
PCMCIA modems to be soft-modems? At least the one I have is just a
"PCMCIA Serial Port", the same goes for the one mounted on Compaq
Insight/LightsOut PCI which is in my school's Proliant 1850R.
> Martin
Good Luck with making it work on Plan9 (At least none of you seem to
have the problem of Plan9 not booting at all ;-) ( Solution for me:
Run Xen/Linux w/ Plan9 in domain 1 ))
--
Paweł Lasek
"Once a hitokiri, always a hitokiri. This will never change" - Jine-Ei
http://plasek.jogger.pl [in polish]
http://plasek.wordpress.com [in polish]
next prev parent reply other threads:[~2005-12-26 14:19 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-07 10:34 [9fans] const Steve Simon
2005-12-07 12:17 ` Russ Cox
2005-12-07 13:01 ` erik quanstrom
[not found] ` <000401c5fb32$64502e00$14aaa8c0@utelsystems.local>
2005-12-07 14:10 ` "Nils O. Selåsdal"
2005-12-07 15:05 ` Steve Simon
2005-12-07 15:30 ` Lucio De Re
2005-12-07 15:53 ` C H Forsyth
[not found] ` <1E68F99F-78D7-4321-BE56-7D0319212596@telus.net>
2005-12-07 16:11 ` "Nils O. Selåsdal"
2005-12-07 17:27 ` Paul Lalonde
2005-12-07 16:23 ` jmk
2005-12-07 17:28 ` Skip Tavakkolian
2005-12-07 18:51 ` Joel Salomon
2005-12-07 18:58 ` Charles Forsyth
2005-12-07 19:30 ` Joel Salomon
2005-12-07 19:36 ` Brantley Coile
2005-12-07 19:51 ` rog
2005-12-07 21:07 ` Charles Forsyth
2005-12-07 21:18 ` Bruce Ellis
2005-12-07 21:22 ` Paul Lalonde
2005-12-07 22:04 ` Rob Pike
2005-12-07 22:44 ` Micah Stetson
2005-12-07 22:44 ` Micah Stetson
2005-12-07 22:46 ` Brantley Coile
2005-12-07 20:33 ` Skip Tavakkolian
2005-12-08 7:39 ` geoff
2005-12-08 7:53 ` Lucio De Re
2005-12-08 7:54 ` geoff
2005-12-08 10:23 ` Bruce Ellis
2005-12-08 15:58 ` Brantley Coile
2005-12-09 1:44 ` geoff
2005-12-09 2:04 ` Russ Cox
2005-12-09 2:19 ` geoff
2005-12-09 9:54 ` Charles Forsyth
2005-12-09 16:25 ` David Leimbach
2005-12-09 16:59 ` Richard Bilson
2005-12-09 17:42 ` David Leimbach
2005-12-09 19:17 ` Richard Bilson
2005-12-09 17:01 ` Ronald G Minnich
2005-12-09 17:39 ` Russ Cox
2005-12-09 17:40 ` [9fans] PCICIA Modem TamTam
2005-12-09 18:59 ` Sascha Retzki
2005-12-12 15:07 ` Paweł Lasek
2005-12-26 9:00 ` Martin C. Atkins
2005-12-26 14:19 ` Paweł Lasek [this message]
2005-12-09 19:37 ` [9fans] Re: const Nikita Danilov
2005-12-09 20:30 ` Russ Cox
2005-12-09 20:37 ` Ronald G Minnich
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=9f3897940512260619i6d205e38ma107a2eb68aaa6a0@mail.gmail.com \
--to=pawel.lasek@gmail.com \
--cc=9fans@cse.psu.edu \
/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).