From: Dave MacFarlane <driusan@gmail.com>
To: 9front mailing list <9front@9front.org>
Cc: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9front] DHCP not working on usb ethernet dongle
Date: Thu, 5 Jan 2017 09:06:22 -0500 [thread overview]
Message-ID: <CAG2UyHp42Pqr-+UDzXYR5ps0KjS3pjOq7-7XxRA_vovcwNCQzA@mail.gmail.com> (raw)
In-Reply-To: <1b89fb9b2c22e6b7351e3be528134b94@quintile.net>
I don't think it's related, since there's no primary ethernet or /net
on the laptop for it to conflict with (there's just a wifi card that
isn't supported, which is why I needed the dongle in the first place.)
I spent some time comparing nusb/ether/asix.c to the axeg(4) driver on
my lunch hour yesterday, and I'm suspecting that it might be a 88178
vs 88178a chipset thing since the rx ctl register is different between
the two drivers and the problem is that asixreceive() is never getting
called, but I haven't had a chance to dig any deeper or verify if it's
an "a" chipset with mislabeled packaging while I have physical access
to the machine/dongle.
On Wed, Jan 4, 2017 at 6:20 PM, Steve Simon <steve@quintile.net> wrote:
> Its not the same problem, but just in case it helps,
> adding a second usb ether adapter onto a raspberry pi,
> which runs the labs distro not 9front.
>
> I need to add
> ether1=type=usb
> to cmdline.txt
>
> and then add the following to /cfg/$sysname/termrc
>
> if(! ~ `{cat '#l1/ether1/addr'} 000000000000){
> echo ether1: present
> bind -b '#l1' /net.alt
> bind -b '#I1' /net.alt
> ip/ipconfig -x /net.alt ether /net.alt/ether1
> ndb/cs -x /net.alt
> ndb/dns -x /net.alt -r
> }
> if not {
> echo ether1: missing
> }
>
> this worked seamlessly once I got a supported, and reliable ethernet dongle.
> I tried a couple of chinese ones but settled on an apple one which is well
> manufactured (perhaps I was just unlucky).
>
> All kudos to Richard Miller who helped me through this.
>
> -Steve
--
- Dave
next prev parent reply other threads:[~2017-01-05 14:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 21:19 Dave MacFarlane
2016-12-29 22:23 ` [9front] " sl
2016-12-29 22:31 ` Dave MacFarlane
2016-12-29 22:37 ` cinap_lenrek
2016-12-30 1:02 ` driusan
2016-12-30 4:13 ` cinap_lenrek
2016-12-31 1:49 ` Dave MacFarlane
2017-01-02 3:21 ` cinap_lenrek
2017-01-04 23:20 ` Steve Simon
2017-01-05 14:06 ` Dave MacFarlane [this message]
2017-01-02 3:35 ` mveety
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=CAG2UyHp42Pqr-+UDzXYR5ps0KjS3pjOq7-7XxRA_vovcwNCQzA@mail.gmail.com \
--to=driusan@gmail.com \
--cc=9fans@9fans.net \
--cc=9front@9front.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).