Should Slackware 10.1 do everything that Slax does? I downloaded the Slax
live CD and lo and behold, it recognized my built in wireless circuit and I
was on line. I would like to use Slackware 10.1 on my notebook if it will
do the same thing. Anyone know??

Thanks!!

Rick Morris wrote in <BEA528C6.18CC0%wmorris@neb.rr.com>:

> Should Slackware 10.1 do everything that Slax does? I downloaded the Slax
> live CD and lo and behold, it recognized my built in wireless circuit and
> I
> was on line. I would like to use Slackware 10.1 on my notebook if it will
> do the same thing. Anyone know??

Slax does add things for functionality, like mplayer, so it's not
guaranteed. But that's probably likely to be more related to the kernel
than anything else. Use a 2.6 kernel (since slax does) and enable hotplug,
and with luck it will work.

There is an rc.wireless script that executes by default in slack. I
would say probably, but again its not gauranteed. But it should be a
trivial manner to figure out what Slax is doing to enable it, and then
simply adding that to the Slackware boot up if it doesn't do it by
default.

Rick Morris wrote:
> Should Slackware 10.1 do everything that Slax does? I downloaded the Slax
> live CD and lo and behold, it recognized my built in wireless circuit and I
> was on line. I would like to use Slackware 10.1 on my notebook if it will
> do the same thing. Anyone know??
>
> Thanks!!
>
I have a D-Link wireless PCMCIA card in my laptop. It was recognized and
working, almost immediately upon the first bootup. Since my wireless
setup is completely nailed down (as much as I can do so) I had to edit
the wireless setup to add in the SSID and the 64 encyption key by hand.
Other than that, it works 100% from the get-go.

--
HJohnson
aka HuMJohn AT Aerosurf DOT net

On Mon, 09 May 2005 14:10:44 -0700, masked.slacker@gmail.com wrote:

> There is an rc.wireless script that executes by default in slack. I
> would say probably, but again its not gauranteed. But it should be a
> trivial manner to figure out what Slax is doing to enable it, and then
> simply adding that to the Slackware boot up if it doesn't do it by
> default.

I had to add smoe lines manually so rc.wireless script is called from rc.M
(like rc.inet1 is). I also had to install and configure ndiswrapper
software since my wlan card is not supported by kernel. Even then I was
unable to use network until I made some changes to rc.wireless.
I think many less experienced or just not interested in users may find it
diffcult to use wireless devices in Slackware.

Mateusz Marzantowicz wrote:
> On Mon, 09 May 2005 14:10:44 -0700, masked.slacker@gmail.com wrote:
>
>
>>There is an rc.wireless script that executes by default in slack. I
>>would say probably, but again its not gauranteed. But it should be a
>>trivial manner to figure out what Slax is doing to enable it, and then
>>simply adding that to the Slackware boot up if it doesn't do it by
>>default.
>
>
> I had to add smoe lines manually so rc.wireless script is called from rc.M
> (like rc.inet1 is). I also had to install and configure ndiswrapper
> software since my wlan card is not supported by kernel. Even then I was
> unable to use network until I made some changes to rc.wireless.
> I think many less experienced or just not interested in users may find it
> diffcult to use wireless devices in Slackware.
>

See http://sox.homeip.net/slackware/rc_scripts/ where I address just
that issue (wireless networking in Slack). Also, for various modern
wireless cards, there's a Slackware package (plus SlackBuild scripts
in case you want to build them yourself) at
http://sox.homeip.net/slackware/slackbuilds/

I hope my enhancements to rc.inet1 and rc.wireless will appear in
Slackware in future; otherwise, you can use them as drop-in
replacements for the Slackware originals.

BTW: do NOT call rc.wireless from rc.M, as it is already called from
rc.inet1.

Eric