Well,
It seems that I know the reason why is disabled my wifi...
it's looks like the rfkill is active - as I have get acquainted this thing -
it means that for spare battery power you could turn off the wifi chip. This
is the rfkill. But I couldn't turn off this - or manage. Normally as far as
I know, Networkmanager could do this at in right click menu, and manage this
part. But currently the whole network managing upper part is greyed out - so
it means for me that unreachable.
Somebodí at support chat has adviced to me to install system-config-network
- this helped to me a lot to get the diagnosis.
So - I hope this will help if somebody knows the solution for this - here is
the part of the dmesg:
Error for wireless request "Set Mode" (8B06) :
SET failed on device wlan0 ; Invalid argument.
RTNETLINK answers: Operation not possible due to RF-kill
Error for wireless request "Set Frequency" (8B04) :
invalid argument "Automatic".
Thx,
Zoltan
2010/9/5 Zoltan Hoppar <hopp...@gmail.com>
> Thanks,
>
> I knew this, but doesnt work. However I have insterted successfully the b43
> driver, but somehow gets disabled my wireless network. I think this is
> causing by NetworkManager, but couldn't tell that why. Maybe I don't have
> right, but currently I'm stucked with an disabled Broadcom-PHY. Well, it
> seems in dmesg that first turns on the PHY then turns off???
>
> Here is my part of the dmesg:
>
> sky2 0000:02:00.0: eth0: enabling interface
> ADDRCONF(NETDEV_UP): eth0: link is not ready
> b43 ssb0:0: firmware: requesting b43/ucode15.fw
> b43 ssb0:0: firmware: requesting b43/lp0initvals15.fw
> b43 ssb0:0: firmware: requesting b43/lp0bsinitvals15.fw
> b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
> ADDRCONF(NETDEV_UP): wlan0: link is not ready
> sky2 0000:02:00.0: eth0: Link is up at 100 Mbps, full duplex, flow control
> both
> ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> Bluetooth: L2CAP ver 2.14
> Bluetooth: L2CAP socket layer initialized
> Bluetooth: BNEP (Ethernet Emulation) ver 1.3
> Bluetooth: BNEP filters: protocol multicast
> Bridge firewalling registered
> Bluetooth: SCO (Voice Link) ver 0.6
> Bluetooth: SCO socket layer initialized
> Bluetooth: RFCOMM TTY layer initialized
> Bluetooth: RFCOMM socket layer initialized
> Bluetooth: RFCOMM ver 1.11
> hda-intel: IRQ timing workaround is activated for card #1. Suggest a bigger
> bdl_pos_adj.
> b43-phy0: Radio hardware status changed to DISABLED
>
> Furthermore, on networkmanager gui where you could turn off/on the networks
> (right click on upper systray icon), greyed out - so couldn't explain what
> happened...
>
> PS: If I would like to always load an module for my computer, where must I
> note that for the system? (HP WMI driver module)
>
> 2010/9/4 Athmane Madjoudj <athma...@gmail.com>
>
> On 09/04/2010 09:24 PM, Zoltan Hoppar wrote:
>> > Hi Everyone,
>> >
>> > I have a little problems with my new laptop HP Probook 4515s with Fedora
>> > 13, and the latest kernel.
>> >
>> > 1. Somehow, I couldn't activate the broadcom PHY - wifi module, I have
>> > followed many advices - linuxwireless.org <http://linuxwireless.org>
>> and
>> > after many tries I have given up. In result I got only an broken network
>> > manager.
>>
>> Try the following:
>>
>> 1. Enable RPMFusion repo (both free and non-free). [1]
>> 2. as root:
>> # yum install kmod-wl broadcom-wl
>>
>> [1] http://rpmfusion.org/Configuration
>>
>> HTH
>>
>> [... SNIP ...]
>>
>>
>> --
>> Athmane Madjoudj
>> --
>> users mailing list
>> users@lists.fedoraproject.org
>> To unsubscribe or change subscription options:
>> https://admin.fedoraproject.org/mailman/listinfo/users
>> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
>>
>
>
>
> --
> PGP: 06853DF7
>
--
PGP: 06853DF7
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
