Arch Linux

dlz

Member

Registered: 2011-04-04

Posts: 18

[SOLVED] Pegasus USB Ethernet Adapter - can not bring up interface

Hello!

I can't get my Pegasus USB Ethernet Adapter get to work.
It's a "Teledat Fast Ethernet USB".
Here is a picture of the internal hardware:
Pegasus AN986

the pegasus driver loaded automatically when plugging in, but netctl can not bring the interface up

# journalctl -xn
[...]
[...] network[660]: Starting network profile 'foo.enp0s29f3u1'...
[...] network[660]: Failed to bring interface 'enp0s29f3u1' up
[...] network[660]: Failed to bring the network up for profile 'foo.enp0s29f3u1'
[...] systemd[1]: netctl@foo.enp0s29f3u1.service: main process exited, code=exited, status=1/FAILURE
[...] systemd[1]: Failed to start Networking for netctl profile foo.enp0s29f3u1.
[...]

some additional information:

$ ip link
[...]
3: enp0s29f3u1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
    link/ether 00:50:ba:77:a9:d5 brd ff:ff:ff:ff:ff:ff

# ip link set enp0s29f3u1 up
RTNETLINK answers: No such file or directory

$ dmesg
[...]
[...] usb 2-7: USB disconnect, device number 3
[...] usb 5-1: new full-speed USB device number 2 using uhci_hcd
[...] usb 5-1: config 1 interface 0 altsetting 0 has 2 endpoint descriptors, different from the interface descriptor's value: 3
[...] pegasus: v0.6.14 (2006/09/27), Pegasus/Pegasus II USB Ethernet driver
[...] pegasus 5-1:1.0: eth0, D-Link DSB-650TX, 00:50:ba:77:a9:d5
[...] usbcore: registered new interface driver pegasus
[...] systemd-udevd[2016]: renamed network interface eth0 to enp0s29f3u1

I also compiled the latest pegasus driver, but still no luck to bring the interface up.

$ dmesg
[...]
[...] usb 4-1: new full-speed USB device number 2 using uhci_hcd
[...] usb 4-1: config 1 interface 0 altsetting 0 has 2 endpoint descriptors, different from the interface descriptor's value: 3
[...] pegasus: v0.9.3 (2013/04/09), Pegasus/Pegasus II USB Ethernet driver
[...] pegasus 4-1:1.0: eth1, D-Link DSB-650TX: 00:50:ba:77:a9:d5
[...] usbcore: registered new interface driver pegasus
[...] systemd-udevd[715]: renamed network interface eth1 to enp0s29f2u1

So, RTNETLINK is looking for a file. Do I need a firmware?
Is there a way to find out what file RTNETLINK is looking for?
Also, is the different amount of endpoint descriptors a problem?

Testing was done on a 32bit laptop and 64bit machine.

$ uname -a
Linux amsterdam 3.9.7-1-ARCH #1 SMP PREEMPT Thu Jun 20 22:45:32 CEST 2013 x86_64 GNU/Linux

EDIT:
As it turned out the device is broken. I managed to install Windows XP and the original driver for the device. No way to get this thing working.

Last edited by dlz (2013-07-22 09:28:38)