Re: 2.6.22 kernel and WiFi

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



well as a matter of fact, it does work, sort of.

Linux vader 2.6.22.1-27.fc7 #1 SMP Tue Jul 17 17:19:58 EDT 2007 x86_64
x86_64 x86_64 GNU/Linux



I dont remember if the driver is 32 or 64 bit, still...

bcm43xx_mac80211: Radio turned on
bcm43xx_mac80211: Radio enabled by hardware
bcm43xx_mac80211: ERROR: bbatt(11) >= size of LO array

Call Trace:
[<ffffffff8877c83a>] :bcm43xx_mac80211:bcm43xx_get_lo_g_ctl+0x54/0x93
[<ffffffff8877c8af>] :bcm43xx_mac80211:bcm43xx_lo_g_ctl_current+0x36/0x3b
[<ffffffff8877c98a>] :bcm43xx_mac80211:bcm43xx_lo_g_adjust+0x9/0x15
[<ffffffff887770c3>] :bcm43xx_mac80211:bcm43xx_phy_init_pctl+0x338/0x6a2
[<ffffffff88771c29>] :bcm43xx_mac80211:bcm43xx_phy_read+0x58/0x60
[<ffffffff8877a367>] :bcm43xx_mac80211:bcm43xx_phy_initg+0xc85/0xd0a
[<ffffffff8877ab9a>] :bcm43xx_mac80211:bcm43xx_phy_init+0x582/0x5a3
[<ffffffff8876d105>] :bcm43xx_mac80211:bcm43xx_chip_init+0x675/0x984
[<ffffffff8876e7a1>] :bcm43xx_mac80211:bcm43xx_wireless_core_init+0x27d/0x70a
[<ffffffff8876ffff>] :bcm43xx_mac80211:bcm43xx_add_interface+0x5c/0xf1
[<ffffffff887275c6>] :mac80211:ieee80211_open+0x222/0x34c
[<ffffffff811e6ada>] rtnl_fill_ifinfo+0x32d/0x488
[<ffffffff811e05bb>] dev_open+0x2f/0x6e
[<ffffffff811de783>] dev_change_flags+0x5a/0x118
[<ffffffff811e7674>] rtnl_setlink+0x2bf/0x3f2
[<ffffffff811d6954>] sock_rmalloc+0x24/0x4d
[<ffffffff811d6900>] sock_no_sendpage+0x98/0xc8
[<ffffffff811e6d5c>] rtnetlink_rcv_msg+0x0/0x1e5
[<ffffffff811f4e9b>] netlink_run_queue+0x75/0x103
[<ffffffff811e6d09>] rtnetlink_rcv+0x30/0x4c
[<ffffffff811f5377>] netlink_data_ready+0x12/0x50
[<ffffffff811f416d>] netlink_sendskb+0x23/0x3c
[<ffffffff811f5352>] netlink_sendmsg+0x2b7/0x2ca
[<ffffffff811d48bd>] sock_sendmsg+0xea/0x107
[<ffffffff81045461>] autoremove_wake_function+0x0/0x2e
[<ffffffff81045461>] autoremove_wake_function+0x0/0x2e
[<ffffffff810706f8>] get_page_from_freelist+0x38a/0x51c
[<ffffffff81075eee>] zone_statistics+0x3f/0x60
[<ffffffff810706f8>] get_page_from_freelist+0x38a/0x51c
[<ffffffff81073059>] mark_page_accessed+0x1b/0x2f
[<ffffffff811d4af1>] sys_sendmsg+0x217/0x28a
[<ffffffff81116277>] __up_read+0x19/0x7f
[<ffffffff811d5a01>] sys_getsockname+0x82/0xb2
[<ffffffff81009b5e>] system_call+0x7e/0x83

bcm43xx_mac80211: Chip initialized
bcm43xx_mac80211: 32-bit DMA initialized
bcm43xx_mac80211: Wireless interface started

It works, so far..

and by the way dont buy hp laptops...



On 7/19/07, Sam Varshavchik <[email protected]> wrote:
Mark Haney writes:

> Sam Varshavchik wrote:
>> Mark Haney writes:
>>
>>> You know, replies like this really irritate me. Not only do they not
>>> answer the question, you get a nice little 'lecture' on 'linux for
>>> linux'.  Let me see if I can set things straight.  I had NO CHOICE in
>>> laptops.  I got what I was given by the company.
>>
>> Hahahahahahahahahahahahahahahaha!
>>
>> Let me get this straight:
>>
>> 1) Your company gave you a laptop, presumably preconfigured with MS
>> Windows.
>>
> Nope.  It had no OS.

<wink> <wink> <nudge> <nudge>

> Um, my company, being a bunch of geeks actually ENCOURAGE us to test new
> stuff.

Huh? How come such a bunch of geeks didn't know about Broadcom's (lack of)
support, on Linux, and foisted this laptop off on you? It's not such a big
secret, after all.


>        And the wireless isn't busted.  Since you apparently don't
> bother reading the entire thread, I'll say it slowly.
> It...works...but...will...it...work...with....2.6.22?

Now try reading, equally slow, my initial reply, with the answer: maybe, if
you pray to the right gods.

>>>                                            I CHOSE to run linux
>>> on it since I detest windows and refuse to buy tools when open source
>>> options are better.  Therefore I was unable to do any 'homework'.
>>
>> Did you also "choose" to do something this dumb all by yourself, or did
>> someone tell you to do it?
>
> This dumb?  My friend, I've been running linux since Slackware 3.  I
> know what I'm doing with it.

I don't agree.  Nobody who knows what they're doing would choose to waste
their time with the ndiswrapper drivel.

>                              For years, I've been on the RH and Fedora
> mailing lists since I prefer those OS's (because I live in NC and have a
> loyal streak in me.) and until recently been very happy with the Fedora
> community.  As I said, your first post irritated me.

Yes, I can see that. Sometimes, when reality hits one in the face, the
feeling is not very pleasant.

And the reality is, whether you like it or not, is that folks who are in the
know, and who are up to speed in this particular area, don't give a friggin
hoot about ndiswrapper, and will expend no effort into making sure that
ndiswrapper works. This is because they just don't care a fig about hacking
MS-Windows device drivers into running on Linux. They'd rather spend
whatever time they have into developing free, native Linux drivers for
hardware whose manufacturers work with the Linux community and support it.

So, basically, the current and future ndiswrapper situation is simply with:
if it works, great, if not, you're boned. And, nobody will be able to tell
you, with absolute certainty, if your hardware will work. The best you can
hope to get, until you actually try it, is an educated guess.

And if you want to prove me wrong, the way to do that is to simply trot out
someone who'll give you the definitive answer. I think I'll just sit and
wait here, until this happens. I have plenty of time.



--
fedora-list mailing list
[email protected]
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list



--
[Jorge J. Boscán Etura]
quando omni flunkus moritatus


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux