=======================
OH - ABSOLUTELY!! What the single IP connect does is slow up the grab and run. Not much, granted, but can be enough. Especially if the login has been modified to help its rightful owner.

Hey!- Rob.Rice - you have been giving good advice and I will look into wicd.
Thanks for directing me to Eric. Thanks for putting up with my long winded ways. Be you Christan, Jewish, Muslim or whatever - Seasons Greetings and have a good month.

Norseman01

So just to help a little on this. I run a wireless Slackware -current desktop and have an ath9K adapter. I'm running -current without any problem. I also ran into problems when switching from 13.3 to 14.1. One of the things that has changed in 14.2 is that the kernel now has the ath9K supported and doesn't require the ath9k firmware. Were you trying to add the firmware for ath9k?

I've just had this battle. Going from 14.1 to 14.2, if you keep these files
/etc/rc.d/rc.inet1.conf
/etc/wpa_supplicant.conf
/etc/dhcpcd.conf

you ought to be able to get going manually or with the rc.inet1 script if you get NetworkManager out of the way. A simpler approach might be to get NetworkManager doing the business, but I'm still working my way through documentation, but it appears you can just run nm-connection-editor under X and set yourself up.

per #17 bamunds: trying to add...? Nope. 13.0->14.1 is as simple as doing the standard install, cd /etc/rc.d and fill in the rc.inet1.conf properly. Then fix the wireless.conf to use your domain rather than "any" and run rc.inet1 wlan0 start
--------------------
per #18 business_kid: =========================================
Since legacy setup is so simple with 14.1, installing and get working and keeping the three files, doing a legacy install of 14.2 and overlaying the three files you mention, plus the small change in wireless.conf, just might work. The 14.1 has no need for a manual setting of the wireless chip so how it gets into play is not relevant. If the machine runs correctly on 13.? and 14.1 then 14.2 having it in the kernel, otherwise not messed with, should present no problems. If the problem still exists - then migrating the WiFi chip to kernel is where the problem exists. yes?

Nubies just entering Slackware with 14.2 as their first and only copy are still screwed.

I was about to sign off and had a thought. In the NetworkManager and/or wicd - present a fully flushed out script. Not "with everything" but with "straight out of the box" useability. You cannot go on the net to seek answers if you can not get on the net in the first place. Get us on and we can each decide the complexity level we wish.

Norseman01

No the problem is not with the kernel or the kernel code. Slackware has a version for users who simply want it to "work" out of the box it is called LIVESLAK from Eric H (aka AlienBob). It can be burned to a DVD/CD or USB and you simply boot it and it comes up to run. It can then be installed to the hard drive if desired. However it is still for a wired connection.

Setting up the wireless is well explained on this page http://docs.slackware.com/slackbook:wifi?s[]=wireless. I suggest you review it and reconsider wicd, which is also covered. This isn't too complicated and anyone expecting to Slackware to work as if it is a simple appliance is quite naive. Even a oven requires someone to read what temperature to set on the oven in a receipt book, but howto set the temperature for a specific time requires you to read the manual!

If you just want to get your wireless working and I'm assuming your router is set up for wpa or wpa2 you can just modifiy two files and forget all the inet crap.

in "/etc/wpa_supplicant.conf" cut and paste the following with the correct router name and password.

network={
ssid="YourRouterName"
proto=WPA RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
psk=wpa/2passphrase
}

Then in "/etc/r.d/rc.local" add the following assuming wlan0


wpa_supplicant -Dwext -iwlan0 -c /etc/wpa_supplicant.conf > /dev/null 2>&1

reboot and your wireless should come up.

I use wicd which isn't installed automatically for some reason? It is in your /extra/wicd directory of your distribution media and needs to be installed. Once installed you need to run wicd-client or wicd-curses, follow the instructions and add this line to your rc.local

/etc/rc.d/rc.wicd start

You also need to put all your rc.inet1.conf and anything else you changed stuff back to the original and turn off dhcp on anything in rc.inet1.conf

There is nothing wrong with wicd you'll like it if you try it.

I would also endorse the idea of using wicd. The only possible difficulty with wicd in any form is that there are not many, if any, distributions that pre-configure wicd settings, so you may have to configure either your Ethernet or wireless connections (or both). These things are fairly well documented, so if you have questions or issues, seek out the documentation before beginning an installation and be prepared to set up whatever characteristics you may require. It appears that there have been several suggestions provided already on the specifics to do this, so take note now so that you won't be "offline" and unprepared if issues do arise as you configure your system.