Opened 13 years ago
Closed 13 years ago
#7908 closed bug (fixed)
[usb_davicom] doesn't work
Reported by: | diver | Owned by: | siarzhuk |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Drivers/Network/usb_davicom | Version: | R1/Development |
Keywords: | Cc: | siarzhuk | |
Blocked By: | Blocking: | ||
Platform: | All |
Description
This is hrev42620, gcc2hybrid.
I installed usb_davicom via UserBuildConfig:
AddFilesToHaikuImage home config add-ons kernel drivers bin : usb_davicom ; AddSymlinkToHaikuImage home config add-ons kernel drivers dev net : /boot/home/config/add-ons/kernel/drivers/bin/usb_davicom : usb_davicom ;
ifconfig /dev/net/usb_davicom/0
/dev/net/usb_davicom/0 Hardware type: Ethernet, Address: none Media type: Auto-select inet addr: 169.254.0.56, Bcast: 169.254.255.255, Mask: 255.255.0.0 MTU: 1500, Metric: 0, broadcast link configuring Receive: 0 packets, 0 errors, 0 bytes, 0 mcasts, 0 dropped Transmit: 0 packets, 0 errors, 0 bytes, 0 mcasts, 0 dropped Collisions: 0
grep davicom /var/log/syslog
KERN: usb_davicom:01.26.277:init_driver::ver.0.8.3 KERN: usb_davicom:01.26.278:SetupDevice::MAC address is:00:00:00:00:19:79 KERN: usb_davicom:01.26.278:usb_davicom_device_added::New device is added at 0. KERN: usb_davicom:01.26.278:publish_devices::publishing net/usb_davicom/0 KERN: usb_davicom:00.12.176:init_driver::ver.0.8.3 KERN: usb_davicom:00.12.177:SetupDevice::MAC address is:00:00:00:00:19:79 KERN: usb_davicom:00.12.177:usb_davicom_device_added::New device is added at 0. KERN: usb_davicom:00.12.177:publish_devices::publishing net/usb_davicom/0 KERN: loaded driver /boot/home/config/add-ons/kernel/drivers/dev/net/usb_davicom KERN: usb_davicom:00.14.218:StartDevice::Error writing 0X8 to NCR: 0x80000009.
after replugging:
KERN: usb hub 2: port 1: device removed KERN: usb hub 2: port 1 disabled KERN: usb_davicom:01.49.027:usb_davicom_device_removed::Device at 0 deleted. KERN: usb hub 7: port 1: new device connected KERN: usb ehci -1: fullspeed device connected, giving up port ownership KERN: usb hub 2: port 1: new device connected KERN: usb hub 7: port 1: device removed KERN: usb_davicom:01.52.345:init_driver::ver.0.8.3 KERN: usb_davicom:01.52.345:SetupDevice::MAC address is:00:00:00:00:19:79 KERN: usb_davicom:01.52.345:usb_davicom_device_added::New device is added at 0. KERN: usb_davicom:01.52.345:publish_devices::publishing net/usb_davicom/0 KERN: slab memory manager: created area 0x88001000 (7819) KERN: register_domain(9, unix)
grep dm9601 /var/log/messages
Aug 10 22:08:20 iceid kernel: [ 26.925515] dm9601 2-2:1.0: eth0: register 'dm9601' at usb-0000:00:04.0-2, Davicom DM9601 USB Ethernet, 00:00:00:00:19:79 Aug 10 22:08:20 iceid kernel: [ 26.925688] usbcore: registered new interface driver dm9601
lshw
Ethernet interface logical name: eth1 serial: 00:00:00:00:19:79 size: 100MB/s capacity: 100MB/s capabilities: ethernet, Physical interface, twisted pair, Media Independent Interface, 10MB/s, 10MB/s (full duplex), 100MB/s, 100MB/s (full duplex), Auto-negotiation configuration: autonegotiation: on broadcast: yes driver: dm9601 driverversion: 22-Aug-2005 duplex: full firmware: Davicom DM9601 USB Ethernet link: yes multicast: yes port: MII speed: 100MB/s
sudo mii-tool -v eth1
eth1: negotiated 100baseTx-FD flow-control, link ok product info: vendor 00:60:6e, model 12 rev 0 basic mode: autonegotiation enabled basic status: autonegotiation complete, link ok capabilities: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control link partner: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control
sudo mii-diag -v eth1
mii-diag.c:v2.11 3/21/2005 Donald Becker (becker@scyld.com) http://www.scyld.com/diag/index.html Using the new SIOCGMIIPHY value on PHY 0 (BMCR 0x3100). The autonegotiated capability is 01e0. The autonegotiated media type is 100baseTx-FD. Basic mode control register 0x3100: Auto-negotiation enabled. You have link beat, and everything is working OK. This transceiver is capable of 100baseTx-FD 100baseTx 10baseT-FD 10baseT. Able to perform Auto-negotiation, negotiation complete. Your link partner advertised 45e1: Flow-control 100baseTx-FD 100baseTx 10baseT-FD 10baseT, w/ 802.3X flow control. End of basic transceiver information. libmii.c:v2.11 2/28/2005 Donald Becker (becker@scyld.com) http://www.scyld.com/diag/index.html MII PHY #0 transceiver registers: 3100 782d 0181 b8c0 05e1 45e1 0001 0000 0000 0000 0000 0000 0000 0000 0000 0000 0410 8018 7802 0000 0003 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000. Basic mode control register 0x3100: Auto-negotiation enabled. Basic mode status register 0x782d ... 782d. Link status: established. Capable of 100baseTx-FD 100baseTx 10baseT-FD 10baseT. Able to perform Auto-negotiation, negotiation complete. Vendor ID is 00:60:6e:--:--:--, model 12 rev. 0. Vendor/Part: Davicom (unknown type). I'm advertising 05e1: Flow-control 100baseTx-FD 100baseTx 10baseT-FD 10baseT Advertising no additional info pages. IEEE 802.3 CSMA/CD protocol. Link partner capability is 45e1: Flow-control 100baseTx-FD 100baseTx 10baseT-FD 10baseT. Negotiation completed. Davicom vendor specific registers: 0x0410 0x8018 0x7802.
tcpdump -vvv is silent.
Change History (7)
comment:1 by , 13 years ago
Cc: | added |
---|
comment:2 by , 13 years ago
comment:3 by , 13 years ago
listusb
046d:c05b /dev/bus/usb/0/0 "Logitech" "USB Optical Mouse" ver. 5400 ---Note here are 3 second delay after previous line--- 0a46:9601 /dev/bus/usb/0/1 "" "" ver. 0101 03f0:1d17 /dev/bus/usb/0/4 "Hewlett-Packard" "hp LaserJet 1320 series" ver. 0100 03ee:8801 /dev/bus/usb/0/5 "" "" ver. 0112 0000:0000 /dev/bus/usb/0/hub "HAIKU Inc." "OHCI RootHub" ver. 0110 04b8:0142 /dev/bus/usb/1/2 "EPSON" "EPSON Perfection V33/V330" ver. 0100 0000:0000 /dev/bus/usb/1/hub "HAIKU Inc." "EHCI RootHub" ver. 0200
Version 0, edited 13 years ago by (next)
comment:4 by , 13 years ago
listusb -v
[Device /dev/bus/usb/0/1] Class .................. 0x00 (Per-interface classes) Subclass ............... 0x00 Protocol ............... 0x00 Max Endpoint 0 Packet .. 8 USB Version ............ 0x0110 Vendor ID .............. 0x0a46 Product ID ............. 0x9601 Product Version ........ 0x0101 ---Note here is 1 second delay before next line--- Manufacturer String .... "" ---Note here is 1 second delay before next line--- Product String ......... "" ---Note here is 1 second delay before next line--- Serial Number .......... "" [Configuration 0] Configuration String . "" [Interface 0] [Alternate 0 active] Class .............. 0x00 (Per-interface classes) Subclass ........... 0x00 Protocol ........... 0x00 Interface String ... "" [Endpoint 0] MaxPacketSize .... 64 Interval ......... 0 Type ............. Bulk Direction ........ Input [Endpoint 1] MaxPacketSize .... 64 Interval ......... 0 Type ............. Bulk Direction ........ Output [Endpoint 2] MaxPacketSize .... 8 Interval ......... 1 Type ............. Interrupt Direction ........ Input
comment:5 by , 13 years ago
That MAC address looks rather strange to me.
KERN: usb_davicom:01.26.278:SetupDevice::MAC address is:00:00:00:00:19:79
Does this device work under other OS ?
comment:6 by , 13 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
I heard siarzhuk is working on this. Please assign the ticket to yourself to avoid duplicating work next time. I'm waiting for your changes !
Note:
See TracTickets
for help on using tickets.
sudo lsusb -v -s 002:003