Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 26 Jun 2016 19:51:25 -0400
From:      Thomas Laus <lausts@acm.org>
To:        =?iso-8859-1?B?T3RhY8OtbGlv?= <otacilio.neto@bsd.com.br>
Cc:        freebsd-arm@freebsd.org
Subject:   Re: 'urtwn' & 'urtwnfw' Devices Unknown in r302145
Message-ID:  <20160626235125.GA87206@mail.laus.org>
In-Reply-To: <eaca152f-230c-a323-34cf-94e8e23bad86@bsd.com.br>
References:  <20160623220014.GA73746@mail.laus.org> <E1bGNqB-0096kk-EF@smtp.hs-karlsruhe.de> <576FFBC8.21954.BF018@lausts.acm.org> <eaca152f-230c-a323-34cf-94e8e23bad86@bsd.com.br>

next in thread | previous in thread | raw e-mail | index | archive | help
Otaclio [otacilio.neto@bsd.com.br] wrote:
> I don't understand the problem that you are facing. I was running the ALPHA4
> and now ALPHA5 and I do not have problems to detect my urtwn devices. All
> need is plug it into my notebook. I have tested using amd64 and beaglebone
> black and both detects the device and it works.
> 
> ugen0.2: <vendor 0x0bda> at usbus0
> urtwn0: <vendor 0x0bda product 0x8178, class 0/0, rev 2.00/2.00, addr 1> on
> usbus0
> urtwn0: MAC/BB RTL8192CU, RF 6052 2T2R
> urtwn0: enabling 11n
> [ota@nostromo /usr/home/ota]$ uname -a
> FreeBSD nostromo 11.0-ALPHA5 FreeBSD 11.0-ALPHA5 #1 r302205: Sun Jun 26
> 05:33:10 BRT 2016 ota@squitch:/usr/obj/usr/src/sys/GENERIC-NODEBUG  amd64
> 
> _______________________________________________
>
Otaclio:

I don't know the reason either and that is why I am asking for
suggestions on how to identify and resolve my issues.  I captured some
console messages that may provide additional insight.

With Belkin USB Device

Jun 26 19:09:02 fbsd11 kernel: ugen0.2: <vendor 0x0bda> at usbus0
Jun 26 19:09:02 fbsd11 kernel: urtwn0: <vendor 0x0bda product 0x8191, class 0/0, rev 2.00/2.00, addr 1> on usbus0
Jun 26 19:09:02 fbsd11 kernel: urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R
Jun 26 19:09:02 fbsd11 kernel: urtwn0: enabling 11n

With Edimax N150N Device

Jun 26 19:10:01 fbsd11 kernel: ugen0.2: <vendor 0x7392> at usbus0
Jun 26 19:10:01 fbsd11 kernel: urtwn0: <vendor 0x7392 product 0x7811, class 0/0, rev 2.00/2.00, addr 2> on usbus0
Jun 26 19:10:01 fbsd11 kernel: urtwn0: MAC/BB RTL8188CUS, RF 6052 1T1R

Ifconfig messages after either urtwn insertion.

re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	options=8209b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE>
	ether 30:5a:3a:07:fa:54
	inet 192.168.1.105 netmask 0xffffff00 broadcast 192.168.1.255 
	media: Ethernet autoselect (100baseTX <full-duplex>)
	status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
	options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
	inet 127.0.0.1 netmask 0xff000000 
	groups: lo 

FBSD11 >ifconfig urtwn0 up
ifconfig: interface urtwn0 does not exist

FBSD11 >uname -a
FreeBSD fbsd11 11.0-ALPHA5 FreeBSD 11.0-ALPHA5 #0 r302200M: Sun Jun 26 10:54:44 EDT 2016 lausts@fbsd11:/usr/obj/usr/src/sys/GENERIC-NODEBUG amd64

It looks like the device gets identified, but the kernel module just
doesn't like something with either Realtek urtwn network hardware.  I
have a spare hard disk and will load a fresh snapshot of FreeBSD 11.0
tomorrow and I'll report to the list if anything is different.  I
receive the same results with either my 'amd64' and BeagleBone Black
computers.  Both of my urtwn network interfaces are detected and
usable on another computer that is running FreeBSD 10.3 Release-P5.

Tom


-- 
Public Keys:
PGP KeyID = 0x5F22FDC1
GnuPG KeyID = 0x620836CF



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160626235125.GA87206>