Very Computer

by **vsyn** » Sat, 29 Apr 2000 04:00:00

I just got FreeBSD up and running on my i-opener. I haven't used
FreeBSD in several years, so this is somewhat of an adventure. =)

I am trying to set up network access with Inland's USB Ethernet
adapter. I recompiled the kernel, adding in UHCI hub support and kue
USB Ethernet support. The message "ugen0: USB-Ethernet <blah blah>"
now appears in the dmesg log.

I can't get the interface to activate, however... Typing "ifconfig
kue0" and "ifconfig ugen0" both gave me "no such interface" or
similar. I did notice that ugen? is the /dev entry for generic USB
devices, so it probably wouldn't be the interface name, right?

Is there another step? A different interface name? Help...

--
vsync
http://quadium.net/
Orjner.

by **Dan McGrego** » Sat, 29 Apr 2000 04:00:00

Quote:> Is there another step? A different interface name? Help...

Try a "/sbin/ifconfig -a" and see what appears. You should see something
like this:
-- Note I am on a NetBSD system right now, so this may not be accurate
for FreeBSD --

ep0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500
address: 00:10:5a:04:b5:8f
media: Ethernet 10baseT
inet 24.66.252.226 netmask 0xffffff00 broadcast 255.255.255.255

This is a 3Com Etherlink III (3c509).

ne0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500
address: 00:00:21:b8:86:60
media: Ethernet manual
inet 10.13.100.1 netmask 0xff000000 broadcast 10.255.255.255

This is a generic NE2000 compatible card.

lo0: flags=8009<UP,LOOPBACK,MULTICAST> mtu 32976
inet 127.0.0.1 netmask 0xff000000

This is my loopback interface

ppp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
ppp1: flags=8010<POINTOPOINT,MULTICAST> mtu 1500

These are kernel ppp interfaces

sl0: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 296
sl1: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 296

These are slip interfaces

strip0: flags=0<> mtu 1100
strip1: flags=0<> mtu 1100

These are an interface for a packet radio system which I don't own.

tun0: flags=10<POINTOPOINT> mtu 1500
tun1: flags=10<POINTOPOINT> mtu 1500

These are tunnel devices, used for User-PPP.

gre0: flags=8010<POINTOPOINT,MULTICAST> mtu 1450
gre1: flags=8010<POINTOPOINT,MULTICAST> mtu 1450

Some form of IP tunneling.

ipip0: flags=8010<POINTOPOINT,MULTICAST>
ipip1: flags=8010<POINTOPOINT,MULTICAST>

IP in IP tunnel devices

eon0: flags=3<UP,BROADCAST> mtu 1500

I have no idea, and there is no manual page for "eon"

But anyway, look for what could be a USB Nic in there. It should stick
out like a sore thumb, because there is only one of them.

---
My brother-in-law has found a way to make ends meet. He goes around
with his head stuck up his ass.

by **vsyn** » Sat, 29 Apr 2000 04:00:00

> > Is there another step? A different interface name? Help...

> Try a "/sbin/ifconfig -a" and see what appears. You should see something
> like this:

Tried this. As I recall (since that box is off now), I had the
loopback, ppp, several tunnels, and IP over parallel. Nothing
different between when the adapter is plugged in or not.

--
vsync
http://quadium.net/
Orjner.

by **Mikko Tyolajar** » Sat, 29 Apr 2000 04:00:00

>> > Is there another step? A different interface name? Help...

>> Try a "/sbin/ifconfig -a" and see what appears. You should see something
>> like this:
>Tried this. As I recall (since that box is off now), I had the
>loopback, ppp, several tunnels, and IP over parallel. Nothing
>different between when the adapter is plugged in or not.

Is "usbd" running? (usbd_enable="YES" in /etc/rc.conf).

/Mikko
--

RSA Security

by **vsyn** » Sat, 29 Apr 2000 04:00:00

> >> > Is there another step? A different interface name? Help...

> >> Try a "/sbin/ifconfig -a" and see what appears. You should see something
> >> like this:

> >Tried this. As I recall (since that box is off now), I had the
> >loopback, ppp, several tunnels, and IP over parallel. Nothing
> >different between when the adapter is plugged in or not.

> Is "usbd" running? (usbd_enable="YES" in /etc/rc.conf).

Yes, and messages appear when I connect and disconnect devices. My
USB Zip250 drive is also working flawlessly.

--
vsync
http://quadium.net/
Orjner.

by **vsyn** » Sun, 30 Apr 2000 04:00:00

> You have to have, in your kernel, the -correct- driver for the
> USB-Ethernet converter. If the device is a Kawasaki converter, then
> you need to apply a patch to usbdevs.h and usbdevs_data.h. See
> http://www.freebsd.org/cgi/query-pr.cgi?pr=17815. I had trouble with
> this diff patch, so instead I did minor surgery to the files if_kue.c,
> usbdevs, usbdevs.h, and usbdevs_data.h. I'll send them in case of
> need.

Thanks... It's all working now!

I have managed to discover the basic ins and outs of this OS the hard
way, as is usual for me... =)

Quote:> Question for smart people: how do you run the awk script that
> generates usbdevs.h and usbdevs_data.h? I fiddled with it and all I
> got is one beep and an error per attempt.

make -f Makefile.usbdevs

--
vsync
http://quadium.net/ - last updated Fri Apr 28 18:03:25 MDT 2000
Orjner.

by **vsyn** » Sun, 30 Apr 2000 04:00:00

> > You have to have, in your kernel, the -correct- driver for the
> > USB-Ethernet converter. If the device is a Kawasaki converter, then
> > you need to apply a patch to usbdevs.h and usbdevs_data.h. See
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=17815. I had trouble with
> > this diff patch, so instead I did minor surgery to the files if_kue.c,
> > usbdevs, usbdevs.h, and usbdevs_data.h. I'll send them in case of
> > need.

> Thanks... It's all working now!

Well, it's mostly working... Every so often I get a message about
'Watchdog failure on kue0', the interface dies, and I have to
disconnect and reconnect the adapter.

Is this a bug? A really cheap adapter that I should exchange?

--
vsync
http://quadium.net/ - last updated Sat Apr 29 01:17:46 MDT 2000
Orjner.

by **vsyn** » Mon, 01 May 2000 04:00:00

> [Context, for those of you who were out drinking while the cartoon was
> running, is enabling USB kue0 on an I-Opener.]

> [snip]

> > Well, it's mostly working... Every so often I get a message about
> > 'Watchdog failure on kue0', the interface dies, and I have to
> > disconnect and reconnect the adapter.

> > Is this a bug? A really cheap adapter that I should exchange?

> Apparently it is a bug, and not just a USB or kue0 bug. Now that you
> have mentioned it I have removed the chicken's foot I suspended over
> the converter.

Okay. I may still exchange the adapter, though, as it seems to have
difficulties connecting to certain 10/100 hubs.

--
vsync
http://quadium.net/ - last updated Sat Apr 29 23:36:54 MDT 2000
Orjner.