Hi, Larry,
I applied the 10-pcs patch to the kernel (gentoo-sources 2.6.17-r7), and it did 
recognize
the card.
I will put the output of the files here:

[EMAIL PROTECTED] ~ $ su
Password:
localhost igor # modprobe bcm43xx
localhost igor # dmesg |tail
bcm43xx: Number of cores: 4
bcm43xx: Core 0: ID 0x800, rev 0x1000, vendor 0x4243, enabled
bcm43xx: Core 1: ID 0x812, rev 0xa, vendor 0x4243, disabled
bcm43xx: Core 2: ID 0x817, rev 0x3, vendor 0x4243, disabled
bcm43xx: Core 3: ID 0x820, rev 0x1, vendor 0x4243, enabled
bcm43xx: PHY connected
bcm43xx: Detected PHY: Version: 4, Type 2, Revision 8
bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2)
bcm43xx: Radio turned off
bcm43xx: Radio turned off

localhost igor # iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

eth1      IEEE 802.11b/g  ESSID:off/any  Nickname:"Broadcom 4311"
          Mode:Managed  Access Point: Invalid   Bit Rate=1 Mb/s
          RTS thr:off   Fragment thr:off
          Encryption key:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

localhost igor #

Now, I have a wireless-tools installed on my PC, and I might configure it 
incorrectly.
Also, as one of the post on Gentoo Forum suggests I might need to downgrade 
DHCPCD to the 2.0.0 (have 2.0.5
currently).

Here is the quote from that thread about working 1390:

[quote]
My only problem at this point seems to be I occasionally get bumped from the 
wireless and have to reload the settings (I don't see freqs changing but who 
knows) and my speed is fairly slow (but at least I get net).

Other users like bigun89 have asked about DHCP related problems so I figured I 
would post my experience above... that and I figured perhaps it would help to 
get more confirmation on the patchset working for me at least. As always, the 
patchset isn't 'tested' yet... but then again the bcm43xx driver is still a 
driver in an alpha stage and it's worked for me.
[/quote]

Is that what you were talking about? And if yes, is you new patch fixes this 
issue?

Thank you.

-----Original Message-----
>From: Larry Finger <[EMAIL PROTECTED]>
>Sent: Sep 25, 2006 8:32 PM
>To: Igor Korot <[EMAIL PROTECTED]>
>Cc: [email protected]
>Subject: Re: Card for testing
>
>Igor Korot wrote:
>> Larry,
>> 
>> -----Original Message-----
>>> From: Larry Finger <[EMAIL PROTECTED]>
>>> Sent: Sep 25, 2006 9:53 PM
>>> To: Igor Korot <[EMAIL PROTECTED]>
>>> Cc: [email protected]
>>> Subject: Re: Card for testing
>>>
>>> Igor Korot wrote:
>>>> Larry,
>>>>
>>>>
>>>> Well, let me try this one first. If it will run OK, then we can stop right 
>>>> here. If not, then...
>>>> see below.
>>>> Also, is this an intermitent problem - sometimes it works, sometimes - 
>>>> doesn't?
>>> No - the standard code cannot access the registers of a PCI-E device.
>> 
>> OK.
>> 
>>>> I can try to install the gentoo-sources 2.6.18, which is marked as "not 
>>>> stable" at the moment, along
>>>> with the patch mentioned. Or maybe I can apply it to my 2.6.17 first?
>>>> But I'd rather start with the 10-pcs patchset on my current kernel.
>>>> Also, according to the JoseJX (I'm guessing the maintainer of the driver), 
>>>> the patchset will be
>>>> incorporated into the later kernels. So, we are not losing anything...
>>> By all means, try Stefano's 10-piece set. If that works, we will know more, 
>>> but I'm not sure.
>> 
>> Before doing that, just to be absoplutely sure I didn't miss anything...
>> This is what I have in my kernel:
>> 
>> CONFIG_HOTPLUG=y
>> # CONFIG_HOTPLUG_CPU is not set
>> # CONFIG_HOTPLUG_PCI is not set
>> 
>> Do I need the last one "on"?
>> Yes, there is also a report of one person that has it's working from the 
>> thread mentioned
>> with the 10-pcs. patch. But it's one person only, and I want to try it 
>> mostly because
>> we might know more from this.
>
>Yes. I have HOTPLUG_PCI set.
>
>>> My patch will not apply to 2.6.17. I'm not sure why Gentoo calls 2.6.18 
>>> "not stable". There are 
>>> problems with the bcm43xx driver in the vanilla code, but my patch fixes 
>>> all of them. Once you apply 
>>> the patch, you will essentially be running the 2.6.19 version of bcm43xx.
>> 
>> My guess is that Gentoo devs might introduce something and need to test more 
>> the behavior
>> of the kernel. And again, I am running gentoo-sources kernel, which is, 
>> ASAIU, vanilla plus
>> some gentoo fixes. At least I got this understanding from the Gentoo 
>> Installation Guide.
>> Anyway, like I said, I will apply his patch to my 2.6.17 stable gentoo 
>> kernel, and then
>> will upgrade to the next one and will pach it accordingly.
>> 
>>> Actually, I'm the maintainer of bcm43xx-softmac and the reason I'm looking 
>>> for testers is to prove 
>>> the quality of the PCI-E patches. Yes, I'm hoping to get them into 2.6.19 
>>> before it closes.
>> 
>> OK, it is good to know. Now, I'd like to be more productive with the testing.
>> What kind of files/information you are looking for in order to check if it's 
>> working?
>
>After you get a system built, I would like to see the output from the dmesg 
>command, plus the output 
>of an iwconfig command.
>
>Larry

_______________________________________________
Bcm43xx-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Reply via email to