You are not logged in.
Just figured out that I might share this solution with my fellow laptop users using broadcom-wl drivers from AUR.
With that said, I have installed my broadcom-wl driver from AUR by building it through ABS and issuing pacman -U.
I did this during the time when the arch repositories still hold kernel-2.6.32.
I found this issue after installing samba, since I need to connect to a local windows share. smbclient complains with "libkrb5.so.26 no such file yada yada." A proposed solution is to do a system upgrade, which I can't do because broadcom-wl requires kernel-2.6.33. This effectively blocks even upgrading the kernel to 2.6.33 via the Arch repository. Plus, I can't risk losing my wireless connection as there are no wired connections in the area I was on.
But then I figured out, the solution is to remove broadcom-wl temporarily, then do a system upgrade. Don't worry about wireless not working after removing the package. Wireless networking will still work, just make sure that the wl module is loaded.
Not sure if a full system upgrade would fix my problem with smbclient though. A bug was filed about the smbclient [url=http://bugs.archlinux.org/task/18905?cat[0]=10&percent[0]=&pri[0]=&reported[0]=&sev[0]=2&status[0]=&string]issue[/url].
Last edited by avendael (2010-04-14 07:18:19)
Offline
I just found out why broadcom-wl blocks kernel2.6.33.
depends=('kernel26>=2.6.29 'kernel26<2.6.33')This line is at fault. The latest PKGBUILD, however, has this line fixed.
Offline