slackware live current won't connect to my wifi
 

slackware64 live current won't connect to my wifi.

i can see my network in network manager but when i select it and enter my key , it just tries for a minute and deactivates.

i use the nightly 2016-01-18 iso , dd'd to a usb stick.
I use an old Pentium Core i3 laptop with intel Centrino Wireless-N 1000 ( 8086:0083 ) a good performer in windoze.

i have configured my router to favor 802.11N

Hi,

I think it would have been better if you didn't use "dd". If Slackware Live is running on a read/write filesystem like ext4, you can write changes to the system and customize the configurations so that everytime you boot, the changes persist. But if you used the "dd" command, the filesystem will most probably be read-only (something like iso-9660).

So, please try to make the Slackware live using the iso2usb.sh script (http://www.slackware.com/~alien/liveslak/).

good point. i had to dd coz i didnt have a slackware machine that could run the script. will the script work if i boot the iso from a dvd ?

Ok, let us say you have the iso somewhere on your hard drive. What you can do:

- boot from a live DVD so that you have a running Linux system
- mount the partition from your hard drive/any other drive holding the iso file
- have that script somewhere on your running system with executable permission
- run the script: ./iso2usb.sh -i PATH_TO_YOUR_ISO_FILE -o /dev/sdX

Just be careful about the /dev/sdX, make sure it is pointing to your usb. List the contents of /dev/disk/ to know for sure.

refreshing, back on topic :

slackware64 live current won't connect to my wifi.

i can see my network in network manager but when i select it and enter my key , it just tries for a minute and deactivates.

i use the nightly 2016-01-18 iso , dd'd to a usb stick.
I use an old Pentium Core i3 laptop with intel Centrino Wireless-N 1000 ( 8086:0083 ) a good performer in windoze.

i have configured my router to favor 802.11N

Try switching Network Manager's default dhcp client from dhcpcd to dhclient. I'm not sure if there's a GUI setting for this, but I believe you can edit /etc/NetworkManager/NetworkManager.conf to change it as well.

I upgraded to -current yesterday and also had issues with WiFi

In my /var/log/syslog, I saw entries like:

Poking around the internet, it seemed like this was a bug in NetworkManager. Using the current /source/n/NetworkManager slackbuild, and using the latest (1.4.4) source (from https://wiki.gnome.org/Projects/NetworkManager/), the problem went away (I am once again able to connect via wireless without issue).

So, try upgrading NetworkManager from the version in -current (1.2.6, I think) to 1.4.4.

Ah, just saw you are trying from an ISO image, so perhaps recompiling NetworkManager isn't an easy option!

if he made the iso himself, he can just use a newer NetworkManager

fresh install?

not accepting key

check key to see if correct entry

don't use nightly, prone to errors.
use stable current

No, a Live DVD, read the posts.
There is no such thing as a "stable current". Stable = 14.2. Development = Current.

My Bag, but what is this nightly that is spoke of then?
(their is a 14.2 that is not (kept) current in the mirrors list then on the bottom of the mirror list has a current as well. my confusion I suppose)

semantics is a bitch sometimes. lol

Semantics yes, and typos/spelling too...

You seem to be unaware of the difference between stable releases and the development version? A stable release like 14.2 will only receive maintenance by way of critical bugfixes. New development (what you call "keeping it current") only happens to the development tree which is aptly called "slackware-current".

If you care to read the posts and follow the provided URLs you will find that the OP is talking about a Live ISO of Slackware64-current, which I provide on my server, and which gets re-generated every time there is an update to slackware-current. It is meant as a quick way to experience the latest developments without having to install slackware-current.

FYI: see http://bear.alienbase.nl/mirrors/sla...-current-live/

being still a stable updated to current status more than the other type of Slackware that does not use the current mirror. yes | no


nevertheless, for sake of argument,
Nightly - to my learning was always developers tinkering with the code and putting out what they left off with, therefore not always a stable release.

Typos and misspellings, if someone can actully make out that a word is misspelled for whatever reason, that shows that they know what they word is, therefore not a big deal. please refer to my little whatever they call it that lays under ones own post that quotes can be put there.

I've already admitted fault, and thank you for the update on that information. may you have a nice day. :D