From: sergey.kish@gmail.com
To: 9fans@9fans.net
Subject: [9fans] how to make hardware work?
Date: Mon, 17 Jan 2011 10:20:07 -0500 [thread overview]
Message-ID: <8834e48c8d961779e1c2083f7f2f73cf@gmail.com> (raw)
In-Reply-To: <61dc89372119bc4ce74704ba0436c3bc@hera.eonet.ne.jp>
I've installed Plan 9 on my netbook. There are several things I can't
leave without - internet and music.
My system information collected in Linux and Plan 9, usb/ether output
https://gist.github.com/782904
Ethernet works ok, how to make PPP over USB? I've found ppp(8),
usb/ether and cinap_lenrek/usbether, zwansch/usbuart in contrib.
term% usb/ether -D
usb/ether: fsioproc pid 471
<- Tversion tag 65535 msize 8216 version '9P2000'
-> Rversion tag 65535 msize 8192 version '9P2000'
<- Tauth tag 4 afid 219 uname sergeykish aname
-> Rerror tag 4 ename permission denied
<- Tattach tag 4 fid 219 afid -1 uname sergeykish aname
-> Rattach tag 4 qid (0000000000000000 0 d)
usb/ether: startdevs: opening #0 [2]
usb/ether: [2]: can't open endpoint [2]: '[2]' file does not exist
usb/ether: no device found
I have no idea what to do.
There is no /dev/audio, cat '#A' says hardware isn't soundblaster.
Not so important issues:
* There is no plugged usb disk (which I use to boot)
* I'd like to have wifi
* and accelerated graphics (it is hard to get poulsbo working even on
Linux)
How to make it work? Is there tutorials, books? Ruby, Python,
JavaScript and Sh are my primary languages today. Used to program
windows applications on C++ (shame on me).
next prev parent reply other threads:[~2011-01-17 15:20 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 7:54 [9fans] plan9 go output faults on 9vx but ok on cpu Skip Tavakkolian
2011-01-11 14:11 ` erik quanstrom
2011-01-11 15:06 ` Devon H. O'Dell
2011-01-11 17:03 ` Charles Forsyth
2011-01-11 17:51 ` ron minnich
2011-01-11 19:35 ` Pavel Zholkover
2011-01-11 23:58 ` Charles Forsyth
2011-01-11 16:25 ` ron minnich
2011-01-12 8:32 ` Skip Tavakkolian
2011-01-12 16:12 ` andrey mirtchovski
2011-01-12 22:03 ` ron minnich
2011-01-13 5:54 ` ron minnich
2011-01-14 17:32 ` Pavel Zholkover
2011-01-15 2:00 ` Anthony Martin
2011-01-15 9:47 ` Pavel Zholkover
2011-01-15 9:01 ` kokamoto
2011-01-15 9:19 ` Pavel Zholkover
2011-01-15 9:30 ` lucio
2011-01-15 9:58 ` Pavel Zholkover
2011-01-15 10:29 ` lucio
2011-01-15 10:40 ` lucio
2011-01-15 11:25 ` Pavel Zholkover
2011-01-16 1:51 ` kokamoto
2011-01-16 2:04 ` kokamoto
2011-01-16 6:21 ` kokamoto
2011-01-17 12:03 ` kokamoto
2011-01-17 15:20 ` sergey.kish [this message]
2011-01-16 2:06 ` Skip Tavakkolian
2011-01-11 17:03 ` Pavel Zholkover
2011-01-11 18:55 ` Anthony Martin
2011-01-11 19:06 ` Anthony Martin
2011-01-11 22:58 ` ron minnich
2011-01-12 22:31 ` Anthony Martin
2011-01-12 22:36 ` erik quanstrom
2011-01-12 23:28 ` Pavel Zholkover
2011-01-12 23:29 ` Charles Forsyth
2011-01-17 15:23 [9fans] how to make hardware work? sergey.kish
2011-01-17 17:17 ` John Floren
2011-01-17 18:11 ` Nick LaForge
2011-01-17 18:37 ` lsub
2011-01-17 18:52 ` lsub
2011-01-17 19:09 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2011-01-17 19:35 ` Nick LaForge
2011-01-17 23:27 ` John Floren
2011-01-18 0:01 ` Francisco J Ballesteros
2011-01-18 3:29 ` Nick LaForge
2011-01-18 13:27 ` sergey.kish
2011-01-18 13:53 ` erik quanstrom
2011-01-18 19:23 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
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=8834e48c8d961779e1c2083f7f2f73cf@gmail.com \
--to=sergey.kish@gmail.com \
--cc=9fans@9fans.net \
/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).