[Prism54-devel] [Bug 53] kernel BUG at oid_mgt.c:333

[bugzilla-daemon@mcgrof.com]

http://prism54.org/cgi-bin/bugzilla/show_bug.cgi?id=53





------- Additional Comments From mathiasb@email.dk  2004-04-09 15:52 -------
Hello again! Iv'e tried the latest snapshot (20040409) and now it seems to work
alrihgt! :) At first i got tricked, as i got this, when sticking in the card:

PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
eth2: prism54 driver detected card model: SMC2835W
eth2: islpci_open()
eth2: resetting device...
eth2: uploading firmware...
eth2: firmware uploaded done, now triggering reset...
eth2: expecting oid 0xff020003, received 0x2009806.
eth2: timeout waiting for mgmt response
eth2: expecting oid 0x10000002, received 0x0.
eth2: timeout waiting for mgmt response
eth2: expecting oid 0x12000002, received 0xcdce0010.
eth2: timeout waiting for mgmt response
eth2: expecting oid 0x12000007, received 0x12000002.
eth2: timeout waiting for mgmt response
eth2: expecting oid 0xff02000f, received 0xcdce0010.
eth2: timeout waiting for mgmt response
eth2: mgt_commit has failed. Restart the device

And then the lights went out in the card. But on a hunch i tried to use the
essid of my network instead of 'any', and behold! (iwevent):

19:23:13.629918    eth2     ESSID:off/any
19:25:47.449463    eth2     Mode:Managed
19:26:05.690502    eth2     Mode:Managed
19:26:36.675491    eth2     ESSID:"home"
19:26:37.959934    eth2     Custom driver event:Authenticate request to
00:04:E2:9D:6B:5C  : ACCEPTED  (00)
19:26:37.962065    eth2     Custom driver event:Associate request to
00:04:E2:9D:6B:5C  : ACCEPTED  (00)
19:26:37.963269    eth2     New Access Point/Cell address:00:04:E2:9D:6B:5C

The card is up and on! i was also able to get an ip. And then i tried to go some
of the places that had failed before (searching on forums.gentoo.org, and this
form), and look both worked! :) and if/iwconfig works as well. 

Oh, and may i say that there really seems to be a big difference in the driver
since snapshot 20040130 which i used so far

So i quess this bug is closed from my side, with the minor correction that
'iwconfig ethX essid any' does not work.

btw. you said, and i can see in the changelog, that you forced serialization.
what does that mean in this case? is that a good or a bad thing? 
(you can write it on the forum if its not appropriate here...)



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.