[Prism54-users] LOTS of packet loss

[Franco]

> Please provide the dmesg output of A while A is trying to
> talk to B.

I enclose the output;
actually, I typed "dmesg" before and after trying to talk
to B from A, but the output didn't change.

> Also you may want to check for firmware upgrades on that AP.

OK, I'm working on it...

> Have you tried connecting A and B on a different AP and seeing if these
> problems are still present?

Uhm, no, I can't do this test... so do you think 
the problem is AP related? Let's see what happens
upgrading the firmware...

Franco  (dmesg output follows for PC A, Roper card)

Loaded prism54 driver, version 1.2
ACPI: PCI interrupt 0000:02:0a.0[A] -> GSI 9 (level, low) -> IRQ 9
divert: allocating divert_blk for eth1
eth1: prism54 driver detected card model: XG-900/GW-DS54G
divert: freeing divert_blk for eth0
eth1: removing device
divert: freeing divert_blk for eth1
Unloaded prism54 driver
ip_tables: (C) 2000-2002 Netfilter core team
ip_conntrack version 2.1 (3060 buckets, 24480 max) - 296 bytes per conntrack
8139too Fast Ethernet driver 0.9.27
ACPI: PCI interrupt 0000:02:02.0[A] -> GSI 9 (level, low) -> IRQ 9
divert: allocating divert_blk for eth0
eth0: RealTek RTL8139 at 0x2000, 00:40:2b:39:67:36, IRQ 9
eth0:  Identified 8139 chip type 'RTL-8100B/8139D'
Loaded prism54 driver, version 1.2
ACPI: PCI interrupt 0000:02:0a.0[A] -> GSI 9 (level, low) -> IRQ 9
divert: allocating divert_blk for eth1
eth1: prism54 driver detected card model: XG-900/GW-DS54G
eth1: islpci_open()
eth1: resetting device...
eth1: uploading firmware...
eth1: firmware uploaded done, now triggering reset...
eth1: mgt_commit has failed. Restart the device 
eth1: no IPv6 routers present