Opened 13 years ago

Last modified 5 years ago

#8238 assigned bug

USB ASIX 88772B Low-Power 10/100 Fast Ethernet driver

Reported by: starsseed Owned by: kallisti5
Priority: normal Milestone: R1
Component: Drivers/Network/usb_asix Version: R1/Development
Keywords: ASIX Cc:
Blocked By: Blocking:
Platform: All

Description

I added the 0x0b95:0x7e2b device id to the ASIX driver. It's the Low-Power version of the already supporter 0x0b95:0x7720 "ASIX 88772 10/100" device. (see the patch)

The device is detected, it detects if the link is plugged or not, but it doesn' t seems to send/receive any data ( DHCP or static configuration)

  • Did I do something incorrect ?
  • Is the ASIX driver in a good working state ?

NB : in the screenshot, you can see the driver loaded in the kernel team, but "listusb" does not report the device/manufacturer name.

Attachments (5)

Asix_Driver.diff​ (657 bytes ) - added by starsseed 13 years ago.
ASIX driver patch
Asix88772B.png​ (105.4 KB ) - added by starsseed 13 years ago.
usb_asix.bz2​ (19.0 KB ) - added by siarzhuk 13 years ago.
Yet another fix for device lookup routines.
syslog​ (258.3 KB ) - added by starsseed 13 years ago.
my last syslog
usb_asix.log​ (507.2 KB ) - added by starsseed 13 years ago.
...and the relative driver log

Download all attachments as: .zip

Change History (30)

by starsseed, 13 years ago

Attachment: Asix_Driver.diff​ added

ASIX driver patch

comment:1 by starsseed, 13 years ago

patch: 0 → 1

by starsseed, 13 years ago

Attachment: Asix88772B.png​ added

comment:2 by diver, 13 years ago

See #7915.

in reply to:  description comment:3 by siarzhuk, 13 years ago

Replying to starsseed:

I added the 0x0b95:0x7e2b device id to the ASIX driver. It's the Low-Power version of the already supporter 0x0b95:0x7720 "ASIX 88772 10/100" device. (see the patch)

That is AX88772B but AX88772. Looks like a bit more changes are required to support it. I'll look into it.

The device is detected, it detects if the link is plugged or not, but it doesn' t seems to send/receive any data ( DHCP or static configuration)

  • Did I do something incorrect ?
  • Is the ASIX driver in a good working state ?

It is as perfect as possible. :-D

NB : in the screenshot, you can see the driver loaded in the kernel team, but "listusb" does not report the device/manufacturer name.

Those strings are descriptive and has no affect on driver functions. It is typical situation that they contains emptyness or even some trash.

in reply to:  description ; comment:4 by siarzhuk, 13 years ago

Owner: changed from nobody to siarzhuk
Status: new → assigned

Replying to starsseed:

I added the 0x0b95:0x7e2b device id to the ASIX driver. It's the Low-Power version of the already supporter 0x0b95:0x7720 "ASIX 88772 10/100" device. (see the patch)

I have checked the FreeBSD driver for changes required to support AX88772A/B and looks like some time is required to import them into Haiku driver. Do you have this hardware for a long time? Can you wait for some weeks?

comment:5 by siarzhuk, 13 years ago

Component: Drivers/Network → Drivers/Network/usb_asix

in reply to:  4 comment:6 by starsseed, 13 years ago

Replying to siarzhuk:

I have checked the FreeBSD driver for changes required to support AX88772A/B and looks like some time is required to import them into Haiku driver.

But much less work than writing a FreeBSD driver for the Atheros AR9485 adapter... ( my only alternative - apart VirtualBox)

Do you have this hardware for a long time? Can you wait for some weeks?

I own this hardware for 2 weeks. Since the Linux driver is not natively supported yet (I had to compile the driver), I would say that Haiku is not lagging that much !

To make it short : Yes I can wait a bit.

comment:7 by siarzhuk, 13 years ago

Please try the version I have just attached. It is a good idea to activate private logging by using usb_asix.settings template and show me the log of this test session.

Thank you.

PS: By the way, your still have the version with just added ids? Can you show me the putput of ifconfig command. Was the MAC address obtained correctly???

in reply to:  7 ; comment:8 by starsseed, 13 years ago

Replying to siarzhuk:

Please try the version I have just attached.

not sure that your driver work with my "ASIX 88772B" it is loaded by the kernel but it seems it doesn't support the device (see the syslog attachment). Did you add the 88772B's device ID?

It is a good idea to activate private logging by using usb_asix.settings template and show me the log of this test session.

I cant find this file. where should-it be and what should-it contain?

PS: By the way, your still have the version with just added ids? Can you show me the output of ifconfig command. Was the MAC address obtained correctly???

the ifconfig comand shows 

/dev/net/usb_asix/0
	Hardware type: Ethernet, Address: 9c:eb:e8:02:87:1c
	Media type: Auto-select
	inet addr: 169.254.0.6, Bcast: 169.254.255.255, Mask: 255.255.0.0
	MTU: 1500, Metric: 0, up broadcast link auto-configured
	Receive: 0 packets, 5295 errors, 0 bytes, 0 mcasts, 0 dropped
	Transmit: 13 packets, 0 errors, 3861 bytes, 0 mcasts, 0 dropped
	Collisions: 0

and the syslog reports continuously something like 

KERN: [33musb_asix:[0m01.10.802:Read::Error: no place for TRXHeader:only 0 of 4 bytes.
KERN: usb error ehci -1: qtd (0x05164f00) error: 0x06048148
KERN: [33musb_asix:[0m01.10.813:Read::Device status error:0x8000a014
KERN: [33musb_asix:[0m01.10.814:Read::Error: no place for TRXHeader:only 0 of 4 bytes.
KERN: usb error ehci -1: qtd (0x05165280) error: 0x06048148
KERN: [33musb_asix:[0m01.10.824:Read::Device status error:0x8000a014
KERN: [33musb_asix:[0m01.10.825:Read::Error: no place for TRXHeader:only 0 of 4 bytes.
KERN: usb error ehci -1: qtd (0x05165600) error: 0x06048148
KERN: [33musb_asix:[0m01.10.835:Read::Device status error:0x8000a014
KERN: [33musb_asix:[0m01.10.836:Read::Error: no place for TRXHeader:only 0 of 4 bytes.
KERN: usb error ehci -1: qtd (0x05165980) error: 0x06048148
KERN: [33musb_asix:[0m01.10.847:Read::Device status error:0x8000a014

These lines fill a 512ko syslog file in about 10 seconds!

in reply to:  8 ; comment:9 by siarzhuk, 13 years ago

Replying to starsseed:

Replying to siarzhuk:

Please try the version I have just attached.

not sure that your driver work with my "ASIX 88772B" it is loaded by the kernel but it seems it doesn't support the device (see the syslog attachment). Did you add the 88772B's device ID?

That was the easiest part of fix.

It is a good idea to activate private logging by using usb_asix.settings template and show me the log of this test session.

I cant find this file. where should-it be and what should-it contain?

​http://cgit.haiku-os.org/haiku/tree/src/add-ons/kernel/drivers/network/usb_asix/usb_asix.settings - just drop it into driver settings directory (somewhere at ~/config/settings/kernel/drivers/) rename to usb_asix and change contents appropriately.

PS: By the way, your still have the version with just added ids? Can you show me the output of ifconfig command. Was the MAC address obtained correctly???

the ifconfig comand shows 

/dev/net/usb_asix/0
	Hardware type: Ethernet, Address: 9c:eb:e8:02:87:1c
	Media type: Auto-select
	inet addr: 169.254.0.6, Bcast: 169.254.255.255, Mask: 255.255.0.0
	MTU: 1500, Metric: 0, up broadcast link auto-configured
	Receive: 0 packets, 5295 errors, 0 bytes, 0 mcasts, 0 dropped
	Transmit: 13 packets, 0 errors, 3861 bytes, 0 mcasts, 0 dropped
	Collisions: 0

and the syslog reports continuously something like 

KERN: [33musb_asix:[0m01.10.802:Read::Error: no place for TRXHeader:only 0 of 4 bytes.
KERN: usb error ehci -1: qtd (0x05164f00) error: 0x06048148
KERN: [33musb_asix:[0m01.10.813:Read::Device status error:0x8000a014
KERN: [33musb_asix:[0m01.10.814:Read::Error: no place for TRXHeader:only 0 of 4 bytes.
KERN: usb error ehci -1: qtd (0x05165280) error: 0x06048148
KERN: [33musb_asix:[0m01.10.824:Read::Device status error:0x8000a014
KERN: [33musb_asix:[0m01.10.825:Read::Error: no place for TRXHeader:only 0 of 4 bytes.
KERN: usb error ehci -1: qtd (0x05165600) error: 0x06048148
KERN: [33musb_asix:[0m01.10.835:Read::Device status error:0x8000a014
KERN: [33musb_asix:[0m01.10.836:Read::Error: no place for TRXHeader:only 0 of 4 bytes.
KERN: usb error ehci -1: qtd (0x05165980) error: 0x06048148
KERN: [33musb_asix:[0m01.10.847:Read::Device status error:0x8000a014

These lines fill a 512ko syslog file in about 10 seconds!

Was the syslog you have provided acquired with the latest version?

I'll look into it today evening.

in reply to:  9 comment:10 by starsseed, 13 years ago

Replying to siarzhuk:

Replying to starsseed: 

KERN: [33musb_asix:[0m01.10.802:Read::Error: no place for TRXHeader:only 0 of 4 bytes.
KERN: usb error ehci -1: qtd (0x05164f00) error: 0x06048148
KERN: [33musb_asix:[0m01.10.813:Read::Device status error:0x8000a014
KERN: [33musb_asix:[0m01.10.814:Read::Error: no place for TRXHeader:only 0 of 4 bytes.
KERN: usb error ehci -1: qtd (0x05165280) error: 0x06048148
KERN: [33musb_asix:[0m01.10.824:Read::Device status error:0x8000a014
KERN: [33musb_asix:[0m01.10.825:Read::Error: no place for TRXHeader:only 0 of 4 bytes.
KERN: usb error ehci -1: qtd (0x05165600) error: 0x06048148
KERN: [33musb_asix:[0m01.10.835:Read::Device status error:0x8000a014
KERN: [33musb_asix:[0m01.10.836:Read::Error: no place for TRXHeader:only 0 of 4 bytes.
KERN: usb error ehci -1: qtd (0x05165980) error: 0x06048148
KERN: [33musb_asix:[0m01.10.847:Read::Device status error:0x8000a014

These lines fill a 512ko syslog file in about 10 seconds!

Was the syslog you have provided acquired with the latest version?

the syslog was generated with my driver(the one in the trunc + my patch containing the DeviceID)

comment:11 by siarzhuk, 13 years ago

Please try with new one. The device recognition procedure was improved. Thanks.

in reply to:  11 comment:12 by starsseed, 13 years ago

Replying to siarzhuk:

Please try with new one. The device recognition procedure was improved. Thanks.

This new one doesn't change anything. Sorry.

by siarzhuk, 13 years ago

Attachment: usb_asix.bz2​ added

Yet another fix for device lookup routines.

comment:13 by siarzhuk, 13 years ago

Could you, please, try the next version? Thanks.

by starsseed, 13 years ago

Attachment: syslog​ added

my last syslog

by starsseed, 13 years ago

Attachment: usb_asix.log​ added

...and the relative driver log

comment:14 by starsseed, 13 years ago

this time I can see :

  • the driver loaded
  • the MAC adress retrieved
  • the ethernet link detected
  • a default ip address assigned (@=169.254.0.6, netmask=255.255.0.0)

comment:15 by siarzhuk, 13 years ago

Looks like receiveing doesn'T work with USB error. Unfortunately I have to go away now for two weeks for vacations and cannot help a lot. I have comitted current version - and you can try to tweak it yourself if you want. :-\

comment:16 by korli, 12 years ago

Please check with hrev44805. Tested OK on mine, it works OK.

comment:17 by starsseed, 12 years ago

hrev44805 doesn't help. I still can't receive any data.

comment:18 by kallisti5, 12 years ago

Owner: changed from siarzhuk to kallisti5

comment:19 by siarzhuk, 9 years ago

JFYI: the datasheet for AX88772B can be goodled by name AX88772B_Datasheet_v104.pdf. My copy is 1120745 bytes big and was received directly from Asix support 4 years ago. It is looking fairly detailed.

comment:20 by kallisti5, 9 years ago

Is this still an issue? The FreeBSD stack has been updated a few times since it was last tested.

comment:21 by korli, 9 years ago

This driver is native.

in reply to:  20 comment:22 by starsseed, 9 years ago

Replying to kallisti5:

Is this still an issue?

yes it is.

The FreeBSD stack has been updated a few times since it was last tested.

as Korli said, the driver is not based on the FreeBSD stack.

comment:23 by pulkomandy, 8 years ago

patch: 1 → 0
Version 0, edited 8 years ago by pulkomandy (next)

comment:24 by phoudoin, 7 years ago

Seems a duplicate of #9624

comment:25 by probono, 5 years ago

Getting 

KERN: [33musb_asix:[0m31.23.576:Read::Error of queue_bulk_v request:0x80000000
KERN: PMA: bad value for allocate (41231686064 bytes)
KERN: usb error xhci 0: failed to allocate TRBs

The AX88772B based USB to Ethernet device does not get an IP address in Haiku (nightly build as of today),

Note: See TracTickets for help on using tickets.