from 2.6.31-rc1 to present there was a couple of commits for
wireless. prior to that the wireless on my machine(imac)
was o.k.,
Now the wireless does work(streams music,t.v. etc..)
but when I look at iwconfig there's nothing no info.
(I use wicd as my connection manager, and in the bottom corner
of the screen the transmit power is down to almost nothing,
causing wicd to constantly reconnect)
out of a random guess what commit might have caused this, so I can at least
fix this over here(that is until the manufacturer comes out with a new
version). I can go in and individually revert all of the wireless, but
before that
I want a quick lead.
any ideas?
regards,
Justin P. Mattock
Justin P. Mattock wrote:
> from 2.6.31-rc1 to present there was a couple of commits for
> wireless. prior to that the wireless on my machine(imac)
> was o.k.,
> Now the wireless does work(streams music,t.v. etc..)
> but when I look at iwconfig there's nothing no info.
> (I use wicd as my connection manager, and in the bottom corner
> of the screen the transmit power is down to almost nothing,
> causing wicd to constantly reconnect)
>
> out of a random guess what commit might have caused this, so I can at least
> fix this over here(that is until the manufacturer comes out with a new
> version). I can go in and individually revert all of the wireless, but
> before that
> I want a quick lead.
>
> any ideas?
>
If you have a git tree, use the "git bisect" commands to find the bad
commit.
Larry Finger wrote:
> Justin P. Mattock wrote:
>
>> from 2.6.31-rc1 to present there was a couple of commits for
>> wireless. prior to that the wireless on my machine(imac)
>> was o.k.,
>> Now the wireless does work(streams music,t.v. etc..)
>> but when I look at iwconfig there's nothing no info.
>> (I use wicd as my connection manager, and in the bottom corner
>> of the screen the transmit power is down to almost nothing,
>> causing wicd to constantly reconnect)
>>
>> out of a random guess what commit might have caused this, so I can at least
>> fix this over here(that is until the manufacturer comes out with a new
>> version). I can go in and individually revert all of the wireless, but
>> before that
>> I want a quick lead.
>>
>> any ideas?
>>
>>
>
> If you have a git tree, use the "git bisect" commands to find the bad
> commit.
>
>
alright. I'll give that a try.
Justin P. Mattock
Larry Finger wrote:
> Justin P. Mattock wrote:
>
>> from 2.6.31-rc1 to present there was a couple of commits for
>> wireless. prior to that the wireless on my machine(imac)
>> was o.k.,
>> Now the wireless does work(streams music,t.v. etc..)
>> but when I look at iwconfig there's nothing no info.
>> (I use wicd as my connection manager, and in the bottom corner
>> of the screen the transmit power is down to almost nothing,
>> causing wicd to constantly reconnect)
>>
>> out of a random guess what commit might have caused this, so I can at least
>> fix this over here(that is until the manufacturer comes out with a new
>> version). I can go in and individually revert all of the wireless, but
>> before that
>> I want a quick lead.
>>
>> any ideas?
>>
>>
>
> If you have a git tree, use the "git bisect" commands to find the bad
> commit.
>
>
Well, I did the git bisect start routine,
but realized, this takes longer than expected,
so being easier for myself going the the web interface with firefox
seems better.
But after looking through all of the changes through
mac80211, and reverting most of them, and having my machine
scarcely not boot, as well as osx, I decided (f^*k this s^*t)
I'll just leave my machine(imac) with the kernel that runs nicely.
But positive side with all of the changes to mac80211, my macbook
is running all of that just fine(seems to be running a little hotter,
but that just might be the outside temp doing this).
Thanks for the reply,
(I'll just be patient until the later).
Justin P. Mattock