Mailinglist Archive: opensuse-factory (904 mails)

[Jim Flanagan <linuxjim@xxxxxxxxxx>]

Basil Chupin wrote:
> So far getting my wireless on my laptop working with SuSE wasn't too 
> hard, but
> kubuntu is 1 click. With SuSE all the how-to's I read everyone is still
> suggesting using ndiswrapper which involves cleaning up all the bcmxx 
> stuff
> first then hunting down the drivers to use with ndiswrapper, installing
> ndiswrapper and finally configuring ndiswrapper, but with kubuntu it just
> downloads the firmware automatically and wireless works.
>
> I experimented with this, I found out where Kubuntu is getting that 
> firmware
> and downloaded it and extracted it in /lib/firmware on SuSE and the 
> wireless
> card instantly worked. Maybe SuSE should look into something like 
> that. So
> far the way I see other suse users getting their bcmxx wireless 
> working on
> SuSE makes me feel sorry for them. If only they knew that all they had 
> to do
> was download 1 file and stick it in their firmware folder they would 
> be set
> and ready to go. I wish I could tell *EVERY* bcmxx suse user about this.

Do you really want your OS to overwrite your firmware without 
notifying/asking you? Are these firmware upgrades sophisticated enough 
that they won't break the device if you mulit-boot to a different OS??

> Another thing is apt. Oh boy do I miss apt when working in SuSE. I know
> there's probably an equivilent for SuSE, like YUM or such, but I don't 
> know
> how to use it as good as I do apt.
Isn't the difference really the difference in the way rpm works vs deb? 
I really am not experienced in deb at all so I can't fully comment here, 
but the two package management schemes are very different. Which one is 
better? Suse stuck with rpm.

Jim F
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx