Prev: Akonadi and Slackware 13.1
Next: Kernel Panic: Slackware 13.1 64-bit
From: Paweł Wlaź on 1 Jun 2010 08:25


On Tue, 1 Jun 2010, Martin wrote:

[ . . . ]

> http://www.frogge.de/pepper/p50ij/p50ij.html#wlan
>
> It is still not totally end-user-proof as you still have to edit config
> files whenever you move to a new access point with authentication. Wicd
> alone is not the answer.
>

And exactly what is missing in wicd? I am using two totally different
laptops and I can connect to any wireless network (secured or not)
*without* manually editing any config files. Maybe, maybe for some
laptops you have to configure your wireless card, but after that, you
do not have to "edit config files whenever you move to a new acess
poin with authentication", as you write. So, even if wicd alone is not
the anser, its answer is much simpler than yours.

Pawel

From: Loki Harfagr on 1 Jun 2010 08:28
Tue, 01 Jun 2010 14:17:00 +0200, Helmut Hullen did cat :

> Hallo, john,
>
> Du meintest am 31.05.10:
>
>> So I am of the opinion still. Slackware needs a reliable and out-of-
>> the-box wireless setup. Knoppix which is maintained by Klaus Knopper
>> has such a setup. With the increasing number of home wireless networks
>> it is pretty much a necessity.
>
> What about "RIP"?
>
> http://www.tux.org/pub/people/kent-robotti/looplinux/rip/
>
> It's now my favourite PXE LiveCD system.
>
> And it offers "wireless configuration" per mouse click.

Wot? The wireless card is in your mouse?
From: Douglas Mayne on 1 Jun 2010 09:14
On Tue, 01 Jun 2010 14:25:43 +0200, Paweł Wlaź wrote:

> On Tue, 1 Jun 2010, Martin wrote:
>
> [ . . . ]
>
>> http://www.frogge.de/pepper/p50ij/p50ij.html#wlan
>>
>> It is still not totally end-user-proof as you still have to edit config
>> files whenever you move to a new access point with authentication. Wicd
>> alone is not the answer.
>>
>>
> And exactly what is missing in wicd? I am using two totally different
> laptops and I can connect to any wireless network (secured or not)
> *without* manually editing any config files. Maybe, maybe for some
> laptops you have to configure your wireless card, but after that, you do
> not have to "edit config files whenever you move to a new acess poin
> with authentication", as you write. So, even if wicd alone is not the
> anser, its answer is much simpler than yours.
>
> Pawel
>
Ack! IME, wicd is sufficient and doesn't require editing config files. It
transparently handles all of the parameters that had previously required
manual loading of wpa_supplicant, etc. And the wicd-curses program gives
a similar interface to CLI-only interfaces.

To the OP: Because wicd is in the "extra" package group, that makes it
part of the default "slackware" in my book. For whatever reason, because
it has not been elevated to "slackware/n" or another package group as you
would like is a very minimal problem. Just remember to check your list of
extra packages that you need to finish up an install. My list of extra
package includes at least grub, wicd, and tightVNC; from there, I
remember to get a bunch of packages from slackbuilds (apcupsd,
openoffice, various xfce gadgets, etc). What I install depends on the
box's intended function (server, workstation, etc.) YMMV.

--
Douglas Mayne
From: Helmut Hullen on 1 Jun 2010 12:03
Hallo, Loki,

Du meintest am 01.06.10:

>> http://www.tux.org/pub/people/kent-robotti/looplinux/rip/
>>
>> It's now my favourite PXE LiveCD system.
>>
>> And it offers "wireless configuration" per mouse click.

> Wot? The wireless card is in your mouse?

Yes - of course! It's a rumpy mouse!

Viele Gruesse
Helmut

"Ubuntu" - an African word, meaning "Slackware is too hard for me".

From: Chris Vine on 1 Jun 2010 14:56
On Mon, 31 May 2010 18:54:24 -0700 (PDT)
"john(a)wexfordpress.com" <john(a)wexfordpress.com> wrote:
[snip]
> Yes Yes, I downloaded wicd and the Broadcom drivers, and after much
> fiddling got wireless to work for a week or two. Then it stopped
> working. Just for a test I booted a Knoppix disk. It found wireless
> right away. So I installed Knoppix to the hard drive. My wife likes it
> much better than Slackware plus xfce (I wouldn't subject her to KDE4).
>
> So I am of the opinion still. Slackware needs a reliable and out-of-
> the-box wireless setup. Knoppix which is maintained by Klaus Knopper
> has such a setup. With the increasing number of home wireless networks
> it is pretty much a necessity.

I don't agree. I see no reason why Slackware should package up
proprietary drivers for cheap hardware for suppliers who won't release
their source code or even adequate specifications.

But even if that is wrong, your opinion is not well thought out
even on that level, because the problem is not just what you think it
is. The fact of the matter is that the proprietary broadcom driver (the
latest of which is at
http://www.broadcom.com/support/802.11/linux_sta.php) does not compile
against kernel versions 2.6.33 or later.

You would be better advised to complain to broadcom about their not
releasing their source code rather than complaining that Slackware does
not provide an out of date kernel and proprietary drivers, or being more
careful about the hardware you purchase.

However, I will send you a patch which will enable you to compile the
broadcom driver with 2.6.33 (and so Slackware-13.1) if you wish. But I
expect you would be better off sticking with Knoppix, as you say.

Alternatively you could use Slackware 13.0 until broadcom catch up. If
you ran into this problem with Slackware 13.0 then probably you did not
blacklist the ssb and b43 drivers in a file in modprobe.d, as the
broadcom documentation tells you to do.

Chris

First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: Akonadi and Slackware 13.1
Next: Kernel Panic: Slackware 13.1 64-bit