NETDEV-BCM43XX BUG - Failure to associate AP with latest devscape git pull..

NETDEV-BCM43XX BUG - Failure to associate AP with latest devscape git pull..

[Robert Martin]

Kernel = 2.6.19 SMP
bcmwl5 firmware = 4.10.40.0
Devscape bcm43xx_d80211 driver = Latest git pull
Wireless card =  Broadcom Corporation Dell Wireless 1390 WLAN Mini-PCI 
Card (rev 01) (PCI-E)

I seem to be having a problem associating with my AP--everything appears 
fine and I can bring my wireless adapter up (the LED lights up 
correctly), and I don't see complaints about firmware/IRQs in the dmesg 
output.  I am able to see operating APs with an "iwlist wlan0 scan", but 
I am unable to connect to the AP, with or without WEP encryption enabled 
(tried none, hex and ascii; nothing worked).  This is with the latest 
wireless-dev pull and a vanilla 2.6.19 kernel with "irqpoll" option 
enabled, otherwise it misbehaves.  I would be happy to give more 
information if requested, or try different kernel/firmware options.

Here I have provided my dhclient connect attempt output with the 
relevant tcpdump.  Thank you greatly for your time.

========DHCLIENT ATTEMPT OUTPUT 
BEGIN======================================================
Internet Systems Consortium DHCP Client V3.0.4-RedHat
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit

wmaster0: unknown hardware address type 801
/sbin/dhclient-script: configuration for wlan0 not found. Continuing 
with defaults.
/etc/sysconfig/network-scripts/network-functions: line 78: wlan0: No 
such file or directory
wmaster0: unknown hardware address type 801
Listening on LPF/wlan0/00:14:a5:da:ba:87
Sending on   LPF/wlan0/00:14:a5:da:ba:87
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
/sbin/dhclient-script: configuration for wlan0 not found. Continuing 
with defaults.
/etc/sysconfig/network-scripts/network-functions: line 78: wlan0: No 
such file or directory

========DHCLIENT CONNECT OUTPUT 
END=======================================================

========TCPDUMP (tcpdump -vvv -i wlan0 -XX) OUTPUT 
BEGIN========================================================

19:04:08.726651 IP (tos 0x10, ttl  16, id 0, offset 0, flags [none], 
proto: UDP (17), length: 328) 0.0.0.0.bootpc > 255.255.255.255.bootps: 
BOOTP/DHCP, Request from 00:14:a5:da:ba:87 (oui Unknown), length: 300, 
xid:0x789b990d, flags: [none] (0x0000)
         Client Ethernet Address: 00:14:a5:da:ba:87 (oui Unknown) [|bootp]
       0x0000:  ffff ffff ffff 0014 a5da ba87 0800 4510  ..............E.
       0x0010:  0148 0000 0000 1011 a996 0000 0000 ffff  .H..............
       0x0020:  ffff 0044 0043 0134 6187 0101 0600 789b  ...D.C.4a.....x.
       0x0030:  990d 0000 0000 0000 0000 0000 0000 0000  ................
       0x0040:  0000 0000 0000 0014 a5da ba87 0000 0000  ................
       0x0050:  0000 0000 0000 0000 0000 0000 0000 0000  ................
19:04:12.001529 IP (tos 0x10, ttl  16, id 0, offset 0, flags [none], 
proto: UDP (17), length: 328) 0.0.0.0.bootpc > 255.255.255.255.bootps: 
BOOTP/DHCP, Request from 00:14:a5:da:ba:87 (oui Unknown), length: 300, 
xid:0x789b990d, secs:4, flags: [none] (0x0000)
         Client Ethernet Address: 00:14:a5:da:ba:87 (oui Unknown) [|bootp]
       0x0000:  ffff ffff ffff 0014 a5da ba87 0800 4510  ..............E.
       0x0010:  0148 0000 0000 1011 a996 0000 0000 ffff  .H..............
       0x0020:  ffff 0044 0043 0134 6183 0101 0600 789b  ...D.C.4a.....x.
       0x0030:  990d 0004 0000 0000 0000 0000 0000 0000  ................
       0x0040:  0000 0000 0000 0014 a5da ba87 0000 0000  ................
       0x0050:  0000 0000 0000 0000 0000 0000 0000 0000  ................
19:04:21.000548 IP (tos 0x10, ttl  16, id 0, offset 0, flags [none], 
proto: UDP (17), length: 328) 0.0.0.0.bootpc > 255.255.255.255.bootps: 
BOOTP/DHCP, Request from 00:14:a5:da:ba:87 (oui Unknown), length: 300, 
xid:0x789b990d, secs:13, flags: [none] (0x0000)
         Client Ethernet Address: 00:14:a5:da:ba:87 (oui Unknown) [|bootp]
       0x0000:  ffff ffff ffff 0014 a5da ba87 0800 4510  ..............E.
       0x0010:  0148 0000 0000 1011 a996 0000 0000 ffff  .H..............
       0x0020:  ffff 0044 0043 0134 617a 0101 0600 789b  ...D.C.4az....x.
       0x0030:  990d 000d 0000 0000 0000 0000 0000 0000  ................
       0x0040:  0000 0000 0000 0014 a5da ba87 0000 0000  ................
       0x0050:  0000 0000 0000 0000 0000 0000 0000 0000  ................
19:04:32.001816 IP (tos 0x10, ttl  16, id 0, offset 0, flags [none], 
proto: UDP (17), length: 328) 0.0.0.0.bootpc > 255.255.255.255.bootps: 
BOOTP/DHCP, Request from 00:14:a5:da:ba:87 (oui Unknown), length: 300, 
xid:0x789b990d, secs:24, flags: [none] (0x0000)
         Client Ethernet Address: 00:14:a5:da:ba:87 (oui Unknown) [|bootp]
       0x0000:  ffff ffff ffff 0014 a5da ba87 0800 4510  ..............E.
       0x0010:  0148 0000 0000 1011 a996 0000 0000 ffff  .H..............
       0x0020:  ffff 0044 0043 0134 616f 0101 0600 789b  ...D.C.4ao....x.
       0x0030:  990d 0018 0000 0000 0000 0000 0000 0000  ................
       0x0040:  0000 0000 0000 0014 a5da ba87 0000 0000  ................
       0x0050:  0000 0000 0000 0000 0000 0000 0000 0000  ................
19:04:40.001672 IP (tos 0x10, ttl  16, id 0, offset 0, flags [none], 
proto: UDP (17), length: 328) 0.0.0.0.bootpc > 255.255.255.255.bootps: 
BOOTP/DHCP, Request from 00:14:a5:da:ba:87 (oui Unknown), length: 300, 
xid:0x789b990d, secs:32, flags: [none] (0x0000)
         Client Ethernet Address: 00:14:a5:da:ba:87 (oui Unknown) [|bootp]
       0x0000:  ffff ffff ffff 0014 a5da ba87 0800 4510  ..............E.
       0x0010:  0148 0000 0000 1011 a996 0000 0000 ffff  .H..............
       0x0020:  ffff 0044 0043 0134 6167 0101 0600 789b  ...D.C.4ag....x.
       0x0030:  990d 0020 0000 0000 0000 0000 0000 0000  ................
       0x0040:  0000 0000 0000 0014 a5da ba87 0000 0000  ................
       0x0050:  0000 0000 0000 0000 0000 0000 0000 0000  ................
19:04:49.000321 IP (tos 0x10, ttl  16, id 0, offset 0, flags [none], 
proto: UDP (17), length: 328) 0.0.0.0.bootpc > 255.255.255.255.bootps: 
BOOTP/DHCP, Request from 00:14:a5:da:ba:87 (oui Unknown), length: 300, 
xid:0x789b990d, secs:41, flags: [none] (0x0000)
         Client Ethernet Address: 00:14:a5:da:ba:87 (oui Unknown) [|bootp]
       0x0000:  ffff ffff ffff 0014 a5da ba87 0800 4510  ..............E.
       0x0010:  0148 0000 0000 1011 a996 0000 0000 ffff  .H..............
       0x0020:  ffff 0044 0043 0134 615e 0101 0600 789b  ...D.C.4a^....x.
       0x0030:  990d 0029 0000 0000 0000 0000 0000 0000  ...)............
       0x0040:  0000 0000 0000 0014 a5da ba87 0000 0000  ................
       0x0050:  0000 0000 0000 0000 0000 0000 0000 0000  ................
19:05:03.000152 IP (tos 0x10, ttl  16, id 0, offset 0, flags [none], 
proto: UDP (17), length: 328) 0.0.0.0.bootpc > 255.255.255.255.bootps: 
BOOTP/DHCP, Request from 00:14:a5:da:ba:87 (oui Unknown), length: 300, 
xid:0x789b990d, secs:55, flags: [none] (0x0000)
         Client Ethernet Address: 00:14:a5:da:ba:87 (oui Unknown) [|bootp]
       0x0000:  ffff ffff ffff 0014 a5da ba87 0800 4510  ..............E.
       0x0010:  0148 0000 0000 1011 a996 0000 0000 ffff  .H..............
       0x0020:  ffff 0044 0043 0134 6150 0101 0600 789b  ...D.C.4aP....x.
       0x0030:  990d 0037 0000 0000 0000 0000 0000 0000  ...7............
       0x0040:  0000 0000 0000 0014 a5da ba87 0000 0000  ................
       0x0050:  0000 0000 0000 0000 0000 0000 0000 0000  ................

===========TCPDUMP OUTPUT 
END==============================================================

Re: NETDEV-BCM43XX BUG - Failure to associate AP with latest devscape git pull..

[Paul Collins]

Robert Martin <robertm83@gmail.com> writes:

> I seem to be having a problem associating with my AP--everything
> appears fine and I can bring my wireless adapter up (the LED lights up
> correctly), and I don't see complaints about firmware/IRQs in the
> dmesg output.  I am able to see operating APs with an "iwlist wlan0
> scan", but I am unable to connect to the AP, with or without WEP
> encryption enabled (tried none, hex and ascii; nothing worked).  This
> is with the latest wireless-dev pull and a vanilla 2.6.19 kernel with
> "irqpoll" option enabled, otherwise it misbehaves.  I would be happy
> to give more information if requested, or try different
> kernel/firmware options.

I started playing with wireless-dev's bcm43xx-d80211 recently and
noticed that I had to set the frequency manually.  When I did that,
setting the ap manually caused the card to associate immediately.

Here's the sequence of commands I run.  (The driver seems stable on my
hardware, so I've only had to do this twice in the last week, and then
only for reasons unrelated to the driver.)

 ip link set up wlan0
 iwlist wlan0 scan
 iwconfig wlan0 essid $essid key $wep_key
 iwconfig wlan0
(note frequencies differ)
 iwconfig wlan0 freq $freq_from_iwlist_scan
 iwconfig wlan0 ap $ap_mac_address
 dhclient wlan0


-- 
Paul Collins
Wellington, New Zealand

Dag vijandelijk luchtschip de huismeester is dood

Re: NETDEV-BCM43XX BUG - Failure to associate AP with latest devscape git pull..

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 327 bytes --]

On Sun, 2006-12-03 at 16:21 -0500, Robert Martin wrote:

> I would be happy to give more 
> information if requested, or try different kernel/firmware options.

Has it ever worked? I'm curious because the PCI-E chips are 4318s which
are known to not work properly due to missing/wrong TX power
calibration.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

Re: NETDEV-BCM43XX BUG - Failure to associate AP with latest devscape git pull..

[Dan Williams]

On Mon, 2006-12-04 at 21:30 +1300, Paul Collins wrote:
> Robert Martin <robertm83@gmail.com> writes:
> 
> > I seem to be having a problem associating with my AP--everything
> > appears fine and I can bring my wireless adapter up (the LED lights up
> > correctly), and I don't see complaints about firmware/IRQs in the
> > dmesg output.  I am able to see operating APs with an "iwlist wlan0
> > scan", but I am unable to connect to the AP, with or without WEP
> > encryption enabled (tried none, hex and ascii; nothing worked).  This
> > is with the latest wireless-dev pull and a vanilla 2.6.19 kernel with
> > "irqpoll" option enabled, otherwise it misbehaves.  I would be happy
> > to give more information if requested, or try different
> > kernel/firmware options.
> 
> I started playing with wireless-dev's bcm43xx-d80211 recently and
> noticed that I had to set the frequency manually.  When I did that,
> setting the ap manually caused the card to associate immediately.

That sounds suspiciously like the driver either doesn't have the correct
scan results to be able to pick the AP's frequency, or is not correctly
searching those scan results to find it...  If the AP is in the scan
list, the driver should definitely be able to find & set the frequency
for the AP, _unless_ you've previously specified a non-zero frequency
for iwconfig ethX freq [1].  Do you see your AP in the 'iwlist wlan0
scan' output?

dan

[1] with WEXT, if you've specified a fixed frequency with iwconfig wlan0
freq XXXX, the driver should stay locked to that frequency until it is
told to unlock with iwconfig wlan0 freq 0.

> Here's the sequence of commands I run.  (The driver seems stable on my
> hardware, so I've only had to do this twice in the last week, and then
> only for reasons unrelated to the driver.)
> 
>  ip link set up wlan0
>  iwlist wlan0 scan
>  iwconfig wlan0 essid $essid key $wep_key
>  iwconfig wlan0
> (note frequencies differ)
>  iwconfig wlan0 freq $freq_from_iwlist_scan
>  iwconfig wlan0 ap $ap_mac_address
>  dhclient wlan0
> 
> 

Re: NETDEV-BCM43XX BUG - Failure to associate AP with latest devscape git pull..

[Robert Martin]

I've only had the laptop (Compaq V6000Z series) for about a week, so I'd 
be unable to tell you if the driver had worked before, but I seem to 
have had the same problem that Paul Collins did pertaining to frequency 
mismatch.  Setting it manually to the value "iwlist" gave me for the AP 
makes it work, albeit at very slow speeds (driver issue?).  I might have 
been mistaken about the PCI-E, the lspci -n gives me...

03:00.0 0280: 14e4:4311 (rev 01)

...and lspci -vvv gives me...

03:00.0 Network controller: Broadcom Corporation Dell Wireless 1390 WLAN 
Mini-PCI Card (rev 01)
       Subsystem: Hewlett-Packard Company Unknown device 1363
       Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- 
ParErr- Stepping- SERR+ FastB2B-
       Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
<TAbort- <MAbort- >SERR- <PERR-
       Latency: 0, Cache Line Size: 64 bytes
       Interrupt: pin A routed to IRQ 22
       Region 0: Memory at b3200000 (32-bit, non-prefetchable) [size=16K]
       Capabilities: [40] Power Management version 2
               Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
               Status: D0 PME-Enable- DSel=0 DScale=2 PME-
       Capabilities: [58] Message Signalled Interrupts: 64bit- Queue=0/0 
Enable-
               Address: 00000000  Data: 0000
       Capabilities: [d0] Express Legacy Endpoint IRQ 0
               Device: Supported: MaxPayload 128 bytes, PhantFunc 0, 
ExtTag+
               Device: Latency L0s <4us, L1 unlimited
               Device: AtnBtn- AtnInd- PwrInd-
               Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
               Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
               Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
               Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s, Port 0
               Link: Latency L0s <4us, L1 <64us
               Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch-
               Link: Speed 2.5Gb/s, Width x1
       Capabilities: [100] Advanced Error Reporting
       Capabilities: [13c] Virtual Channel

...although I could have sworn I read somewhere that this series uses 
the PCI-E mini bus.  Thank you for your time.


Johannes Berg wrote:
> On Sun, 2006-12-03 at 16:21 -0500, Robert Martin wrote:
>
>   
>> I would be happy to give more 
>> information if requested, or try different kernel/firmware options.
>>     
>
> Has it ever worked? I'm curious because the PCI-E chips are 4318s which
> are known to not work properly due to missing/wrong TX power
> calibration.
>
> johannes
>   

Re: NETDEV-BCM43XX BUG - Failure to associate AP with latest devscape git pull..

[Paul Collins]

Dan Williams <dcbw-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> writes:

> On Mon, 2006-12-04 at 21:30 +1300, Paul Collins wrote:
>> Robert Martin <robertm83-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>> 
>> > I seem to be having a problem associating with my AP--everything
>> > appears fine and I can bring my wireless adapter up (the LED lights up
>> > correctly), and I don't see complaints about firmware/IRQs in the
>> > dmesg output.  I am able to see operating APs with an "iwlist wlan0
>> > scan", but I am unable to connect to the AP, with or without WEP
>> > encryption enabled (tried none, hex and ascii; nothing worked).  This
>> > is with the latest wireless-dev pull and a vanilla 2.6.19 kernel with
>> > "irqpoll" option enabled, otherwise it misbehaves.  I would be happy
>> > to give more information if requested, or try different
>> > kernel/firmware options.
>> 
>> I started playing with wireless-dev's bcm43xx-d80211 recently and
>> noticed that I had to set the frequency manually.  When I did that,
>> setting the ap manually caused the card to associate immediately.
>
> That sounds suspiciously like the driver either doesn't have the correct
> scan results to be able to pick the AP's frequency, or is not correctly
> searching those scan results to find it...  If the AP is in the scan
> list, the driver should definitely be able to find & set the frequency
> for the AP, _unless_ you've previously specified a non-zero frequency
> for iwconfig ethX freq [1].  Do you see your AP in the 'iwlist wlan0
> scan' output?

Yes, this is how I noticed that iwconfig was reporting a different
frequency to that listed in iwlist scan.

>> Here's the sequence of commands I run.  (The driver seems stable on my
>> hardware, so I've only had to do this twice in the last week, and then
>> only for reasons unrelated to the driver.)
>> 
>>  ip link set up wlan0
>>  iwlist wlan0 scan
>>  iwconfig wlan0 essid $essid key $wep_key
>>  iwconfig wlan0
>> (note frequencies differ)
>>  iwconfig wlan0 freq $freq_from_iwlist_scan
>>  iwconfig wlan0 ap $ap_mac_address
>>  dhclient wlan0

-- 
Paul Collins
Wellington, New Zealand

Dag vijandelijk luchtschip de huismeester is dood

Re: NETDEV-BCM43XX BUG - Failure to associate AP with latest devscape git pull..

[Robert Martin]

Paul Collins wrote:
> (Please use reply-to-all to keep Cc:s intact, and place new material
> below quoted material.)
>
> Robert Martin <robertm83@gmail.com> writes:
>
>   
>> Paul Collins wrote:
>>     
>>> Robert Martin <robertm83@gmail.com> writes:
>>>
>>>       
>>>> Alas, that seems to have been the problem, I was getting different
>>>> frequencies.  Once I manually set the frequency, dhclient worked
>>>> perfectly.  The only problem now is that I seem to be limited to very
>>>> slow speeds (on the order of 5-20K/s, or ~120 kilobits/s).
>>>>         
>>> I guess the speed problem is due to the general state of BCM4318
>>> support, as mentioned by the developers.
>>>
>>> I'm glad the frequency thing isn't some weird glitch that only I am
>>> experiencing though.
>>>
>>>       
>> I'm pretty sure that I'm using a 4311 chip... lspci -n gives...
>>
>> 03:00.0 0280: 14e4:4311 (rev 01)
>>
>> ...I might have been mistaken about it being a PCI-E chip in that
>> case.  One additional question, it seems the link quality is very low;
>> "iwconfig wlan0" tells me it's 3/100 after associating with my AP.
>> Could that be the power issue that Johannes Berg was speaking of?  I'm
>> curious as to what speeds you're running at, and what your link
>> quality is.
>>     
>
> My card (a 4306) seems to be running at 11Mbps.  No idea how to change
> it: iwconfig doesn't report the current rate (I had to go digging in
> sysfs) and trying to change it with iwconfig fails with "Operation not
> supported".
>
> Here's the signal info:
>
>         Link Quality=228/100  Signal level=-32 dBm  Noise level=-70 dBm
>
> The machine is about 3 metres from the AP.
>
>   
A quick test just incase the information is somehow helpful... I moved 
to within two meters of my AP with nothing blocking the way--the link 
quality jumped up to 46/100 (vs 3/100 5m away and a wall blocking), 
though there was no increase in speed (still limited to ~120 kilobits/s).

Before:  Link Quality=3/100  Signal level=-73 dBm  Noise level=-66 dBm

After: Link Quality=46/100  Signal level=-49 dBm  Noise level=-69 dBm

Re: NETDEV-BCM43XX BUG - Failure to associate AP with latest devscape git pull..

[Paul Collins]

Robert Martin <robertm83@gmail.com> writes:

> Paul Collins wrote:
>> I started playing with wireless-dev's bcm43xx-d80211 recently and
>> noticed that I had to set the frequency manually.  When I did that,
>> setting the ap manually caused the card to associate immediately.
>
> Alas, that seems to have been the problem, I was getting different
> frequencies.  Once I manually set the frequency, dhclient worked
> perfectly.  The only problem now is that I seem to be limited to very
> slow speeds (on the order of 5-20K/s, or ~120 kilobits/s).

I guess the speed problem is due to the general state of BCM4318
support, as mentioned by the developers.

I'm glad the frequency thing isn't some weird glitch that only I am
experiencing though.

-- 
Paul Collins
Wellington, New Zealand

Dag vijandelijk luchtschip de huismeester is dood

Re: NETDEV-BCM43XX BUG - Failure to associate AP with latest devscape git pull..

[Paul Collins]

(Please use reply-to-all to keep Cc:s intact, and place new material
below quoted material.)

Robert Martin <robertm83-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> Paul Collins wrote:
>> Robert Martin <robertm83-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>>
>>> Alas, that seems to have been the problem, I was getting different
>>> frequencies.  Once I manually set the frequency, dhclient worked
>>> perfectly.  The only problem now is that I seem to be limited to very
>>> slow speeds (on the order of 5-20K/s, or ~120 kilobits/s).
>>
>> I guess the speed problem is due to the general state of BCM4318
>> support, as mentioned by the developers.
>>
>> I'm glad the frequency thing isn't some weird glitch that only I am
>> experiencing though.
>>
> I'm pretty sure that I'm using a 4311 chip... lspci -n gives...
>
> 03:00.0 0280: 14e4:4311 (rev 01)
>
> ...I might have been mistaken about it being a PCI-E chip in that
> case.  One additional question, it seems the link quality is very low;
> "iwconfig wlan0" tells me it's 3/100 after associating with my AP.
> Could that be the power issue that Johannes Berg was speaking of?  I'm
> curious as to what speeds you're running at, and what your link
> quality is.

My card (a 4306) seems to be running at 11Mbps.  No idea how to change
it: iwconfig doesn't report the current rate (I had to go digging in
sysfs) and trying to change it with iwconfig fails with "Operation not
supported".

Here's the signal info:

        Link Quality=228/100  Signal level=-32 dBm  Noise level=-70 dBm

The machine is about 3 metres from the AP.

-- 
Paul Collins
Wellington, New Zealand

Dag vijandelijk luchtschip de huismeester is dood

Re: NETDEV-BCM43XX BUG - Failure to associate AP with latest devscape git pull..

[Johannes Berg]

[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]

On Mon, 2006-12-04 at 13:17 -0500, Robert Martin wrote:

> 03:00.0 0280: 14e4:4311 (rev 01)

4311 is pci-e though, iirc. Linux just shows pci-e like pci devices.


>        Capabilities: [d0] Express Legacy Endpoint IRQ 0
>                Device: Supported: MaxPayload 128 bytes, PhantFunc 0, 
> ExtTag+
>                Device: Latency L0s <4us, L1 unlimited
>                Device: AtnBtn- AtnInd- PwrInd-
>                Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
>                Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
>                Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
>                Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s, Port 0
>                Link: Latency L0s <4us, L1 <64us
>                Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch-
>                Link: Speed 2.5Gb/s, Width x1
>        Capabilities: [100] Advanced Error Reporting
>        Capabilities: [13c] Virtual Channel

looks like pci-e capabilities to me..

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]