with the Broadcom BCM4313 driver now integrated with SUSE 11.4
during the installation process the system always hangs just after the following line
starting network manger
connecting …xx
till i removed the wlan module and then i could launch yast installer normally
but after installing the system and booting up normally i tried to insert the wlan module but then had the same problem
the system always hangs just after the following line
starting network manger
connecting …xx
i’m using i686-32bit version gnome-live
my laptop is G62-a11SE Notebook PC
On 03/28/2011 12:06 AM, caf4926 wrote:
>
> Did you try this
> ‘Install Broadcom Drivers from Packman’ (http://tinyurl.com/2c72nor)
Rather than using the closed-source driver, install the compat-wireless package
for your kernel. There has been a lot of work recently on the brcm80211 driver
and c-w has all the new stuff. One of the faults now corrected is that it would
hang on booting when the rfkill switch was off.
I just got a couple of the new devices (BCM4313 and BCM943224) that use the AI
interconnect. Both work well with the version of brcm80211 in the
wireless-testing tree, which is the source of compat-wireless.
One of the faults now corrected is that it would
hang on booting
that exactly what is happinig the **** machine hangs on booting and on installation
i spend the whole fking week removing and inserting the wlan device from the laptop **
when the rfkill switch was off.
so that’s it just turn the **** switch on
or install rfkill tool and then set the switch to unlock
Preface: I am not in charge in this forum - all I write is written from a normal user (one that rated himself not very experienced with software or hardware but due to his profession has leaned to interpret text).
Hello desperate/angry mostafaxxx!
Probably with c-w is the package compat-wireless is meant.
Both the context
the (half-)sentence right in front “…]install the compat-wireless package
for your kernel.”] -
and the meaning of the sentence with “c-w”
to get the newest things from the hard working kernel developers (like lwfinger is one) who are struggling/fighting to deliver free and open stuff -
told me that).
And if you want to go the open and free way (after getting a bit calmer again?) - I guess that you first need to determine you kernel flavor.
uname -a
entered in a terminal (emulator)
will give you something like
(color added by me)
so in my case the flavor would be default.
@lwfinger / @all
Dear patient human being, retired Experimental Mineralogist/X-Ray Crystallographer and high valued but unpaid, hard working kernel developer!
Dear other experienced openSUSE users!
Doing that was my suggestion if you you would want to follow lwfinger’s suggestion (which I do not fully understand because I did not find any packages build explicitly for openSUSE 11.4 as I have pointed out/have tried to point out)
Yes.
0.
Please make sure that you have 0.1 - not added a package build for the openSUSE Tumbleweed distribution
and especially that you have 0.2 - not added a repository for the openSUSE Tumbleweed distribution
If not now most probably later something like 0.2 will end in a all messed up system.
Please wait for lwfinger to explain his suggestion.
A few questions are persisting my amateurish mind just now:
2.1
Have you installed packages build for openSUSE 11.4 (compare 0.)?
2.2
If I
go to software.opensuse.org ,
choose openSUSE 11.4
add “compat-wireless” to the seach line and
press ENTER
2.3
So I guess (literally)
ether a package builder should give the openSUSE Build Service a slight kick to build the script against the kernel(s) 2.6.38-1.2
or (if the new kernel version makes no difference to the script) a package builder should rename the script in order to avoid puzzlement and not working dependencies.
