Hi,
I did some new tests to see what's my transmission problems with
rtl8187b. I can associate and can send pings (and even to connect
through ssh with other hosts) but i can't transmit "big" files. But
at first mail I didn't know how big must be a "big" file.
I tested with 64, 128, 256, 512, 1024 and 2048 bytes files. From 64 to
512 I always can transmit the file. 1024 sometimes hangs and 2048
always hangs. All files can be transmitted using rt73usb wireless.
I put the tcpdump output of those tests in:
http://www.slackware.com/~piterpunk/transmittests/
The 512-byte file dump is almost equal for both wireless cards.
2048-byte is very different. All logs are scp from my machine to
slackware.com. But the same happens sending mail (but not receiving),
uploading ftp files, doing scp to other machines, etc...
I'll be very happy to provide any extra information or do additional
tests with the cards to help the problem diagnostics. Changing the
rate didn't have any influence in test results. I have an iwl3945 that
works fine, too.
Thanks in advance!
Piter PUNK
--
| E-Mail: [email protected]
.|.
/V\
// \\ UIN:116043354 Homepage:http://piterpunk.info02.com.br
/( )\
^`~'^ ----> Slackware Linux <----
#105432
Larry Finger wrote:
> Piter PUNK wrote:
>> This is the built-in rtl8187b adapter:
>>
>> usb 1-1: new high speed USB device using ehci_hcd and address 7
>> usb 1-1: configuration #1 chosen from 1 choice
>> usb 1-1: New USB device found, idVendor=0bda, idProduct=8189
>> usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
>> usb 1-1: Product: RTL8187B_WLAN_Adapter
>> usb 1-1: Manufacturer: Manufacturer_Realtek
>> usb 1-1: SerialNumber: 00e04c000001
>> rtl8187: 8187B chip detected. Support is EXPERIMENTAL, and could damage
>> your
>> hardware, use at your own risk
>> phy3: Selected rate control algorithm 'pid'
>> phy3: hwaddr 00:16:44:aa:df:bf, RTL8187BvE V0 + rtl8225z2
>
>
> My device is a little different that yours:
>
> rtl8187: 8187B chip detected. Support is EXPERIMENTAL, and could damage your
> hardware, use at your own risk
> rtl8187: inconsistency between id with OEM info!
> phy1: Selected rate control algorithm 'pid'
> phy1: hwaddr 00:11:6b:3e:c4:0a, RTL8187BvB(early) V0 + rtl8225z2
>
> I'll review the code to look at the differences in paths for your device and
> mine. Just in case there is a data dependency, please send me (privately) your
> 2048 byte file.
Is an all zeroed file: dd if=/dev/zero of=file2048 count=2048 bs=1
Data is independent and, maybe, I can transmit something between 1024
and 2048 bytes; not tested yet. I only begin those tests with files with
different sizes to "see" why I can connect with SSH, browse in web,
download my mails... and can't send mail, upload files or fill web
forms.
Feel free to suggest other tests. I have many wireless devices and
access points available to test.
Thanks!
Piter PUNK
--
| E-Mail: [email protected]
.|.
/V\
// \\ UIN:116043354 Homepage:http://piterpunk.info02.com.br
/( )\
^`~'^ ----> Slackware Linux <----
#105432
Larry Finger wrote:
> What are the details of your device? Please post the output of 'dmesg | grep -i
> rtl'.
This is the built-in rtl8187b adapter:
usb 1-1: new high speed USB device using ehci_hcd and address 7
usb 1-1: configuration #1 chosen from 1 choice
usb 1-1: New USB device found, idVendor=0bda, idProduct=8189
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1: Product: RTL8187B_WLAN_Adapter
usb 1-1: Manufacturer: Manufacturer_Realtek
usb 1-1: SerialNumber: 00e04c000001
rtl8187: 8187B chip detected. Support is EXPERIMENTAL, and could damage your
hardware, use at your own risk
phy3: Selected rate control algorithm 'pid'
phy3: hwaddr 00:16:44:aa:df:bf, RTL8187BvE V0 + rtl8225z2
This is my external rtl8187b USB dongle:
usb 1-3: new high speed USB device using ehci_hcd and address 8
usb 1-3: configuration #1 chosen from 1 choice
rtl8187: 8187B chip detected. Support is EXPERIMENTAL, and could damage your
hardware, use at your own risk
phy4: Selected rate control algorithm 'pid'
phy4: hwaddr 00:18:e7:42:2c:23, RTL8187BvE V0 + rtl8225z2
usb 1-3: New USB device found, idVendor=0bda, idProduct=8189
usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-3: Product: RTL8187B_WLAN_Adapter
usb 1-3: Manufacturer: Manufacturer_Realtek
usb 1-3: SerialNumber: 00e04c000001
Both have the same "not-working" results. Using any of my other
adapters the transmission works fine. (ok, it didn't work with
USB Marvell dongle... but it isn't even detected)
Thanks!
Piter PUNK
--
| E-Mail: [email protected]
.|.
/V\
// \\ UIN:116043354 Homepage:http://piterpunk.info02.com.br
/( )\
^`~'^ ----> Slackware Linux <----
#105432
Piter PUNK wrote:
> Larry Finger wrote:
>> What are the details of your device? Please post the output of 'dmesg
>> | grep -i
>> rtl'.
>
> This is the built-in rtl8187b adapter:
>
> usb 1-1: new high speed USB device using ehci_hcd and address 7
> usb 1-1: configuration #1 chosen from 1 choice
> usb 1-1: New USB device found, idVendor=0bda, idProduct=8189
> usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> usb 1-1: Product: RTL8187B_WLAN_Adapter
> usb 1-1: Manufacturer: Manufacturer_Realtek
> usb 1-1: SerialNumber: 00e04c000001
> rtl8187: 8187B chip detected. Support is EXPERIMENTAL, and could damage
> your
> hardware, use at your own risk
> phy3: Selected rate control algorithm 'pid'
> phy3: hwaddr 00:16:44:aa:df:bf, RTL8187BvE V0 + rtl8225z2
>
> This is my external rtl8187b USB dongle:
>
> usb 1-3: new high speed USB device using ehci_hcd and address 8
> usb 1-3: configuration #1 chosen from 1 choice
> rtl8187: 8187B chip detected. Support is EXPERIMENTAL, and could damage
> your
> hardware, use at your own risk
> phy4: Selected rate control algorithm 'pid'
> phy4: hwaddr 00:18:e7:42:2c:23, RTL8187BvE V0 + rtl8225z2
> usb 1-3: New USB device found, idVendor=0bda, idProduct=8189
> usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> usb 1-3: Product: RTL8187B_WLAN_Adapter
> usb 1-3: Manufacturer: Manufacturer_Realtek
> usb 1-3: SerialNumber: 00e04c000001
>
> Both have the same "not-working" results. Using any of my other
> adapters the transmission works fine. (ok, it didn't work with
> USB Marvell dongle... but it isn't even detected)
My device is a little different that yours:
rtl8187: 8187B chip detected. Support is EXPERIMENTAL, and could damage your
hardware, use at your own risk
rtl8187: inconsistency between id with OEM info!
phy1: Selected rate control algorithm 'pid'
phy1: hwaddr 00:11:6b:3e:c4:0a, RTL8187BvB(early) V0 + rtl8225z2
I'll review the code to look at the differences in paths for your device and
mine. Just in case there is a data dependency, please send me (privately) your
2048 byte file.
Thanks,
Larry
Piter PUNK wrote:
>
> Hi,
>
> I did some new tests to see what's my transmission problems with
> rtl8187b. I can associate and can send pings (and even to connect
> through ssh with other hosts) but i can't transmit "big" files. But
> at first mail I didn't know how big must be a "big" file.
>
> I tested with 64, 128, 256, 512, 1024 and 2048 bytes files. From 64 to
> 512 I always can transmit the file. 1024 sometimes hangs and 2048
> always hangs. All files can be transmitted using rt73usb wireless.
I have not downloaded your tcpdump file yet to see your details. On my system, I
am unable to duplicate your results. I used dd with /dev/urandom as the source
to create files of 1024, 2048, 4096, 8192, 16384, and 32768 bytes. All of these
could be transmitted to a second host on my local network using scp.
What are the details of your device? Please post the output of 'dmesg | grep -i
rtl'.
Larry