![]() |
grep........: blank
ls -la : NetworkManager-0.9.8.8-x86_64-1 |
As a quick fix you could install wicd from extra/
Reboot and issue 'wicd-curses' from the console to connect. (Another recommendation made by Slackware is a full install. It's probably best if you do this in future even if you don't want KDE. It makes it a lot easier in situations like this). |
No way of connecting to internet from command line? With NetworkManager 0.9.8?
|
Have a look at nmcli and it's options, it'll be something like
nmcli connection add type 802-11-wireless (or whatever) ssid .... etc but wicd might be easier for now. It's up to you. |
Quote:
for the sake of clarity, can you tell us whether you have a 3G mifi router to which you connect wirelessly (802.11), or a 3G modem you plug into a USB port, which is a different type of wireless connection (wireless WAN)? I don't think wicd supports this kind of connection, but nmtui might do. |
3G mobile hotspor,
|
3G Mobile hotspots
|
3G mobile USB tethering, MTS mblaze ultra 3G
|
Quote:
IF I will have to use that shit, err... "blaze ultra-crap", I would choose the downloading of the full ISO via torrent, for the sake of the pieces checksum, check the torrent four times, then I would follow very careful that UPGRADE.TXT. From when slackpkg-ing without kernel upgrade is recommended method of upgrading on Slackware? I laugh my ass! |
San2ban, your install seems borked: NetworkManager seems to be at the old version.
IMHO, the only way to solve is to download a slackware64-14.2 iso and reinstall all the packages. |
Quote:
This is like all the people telling Android owners to do a full wipe 3x. There's no point. One wipe is enough, just as one checking of the torrent is enough. |
Quote:
IF the ISO was successfully read four times, you can bet that it will give you some fine data on the number five attempt. |
Quote:
Quote:
|
Quote:
Quote:
This fallacy has been floating around longer than using a taskmanager to kill all running applications in Android to help save your battery. |
ok what i found on all my upgrades from 14.1 to current to slackware 14.2 for the last 5 months is.
For some reason networkmanager using it used eth1 instead of eth0 I only have one device. I have no clue why but when I go to the "/etc/rc./rc.intet1.conf" and add yes to the eth1 and reboot networkmanager is happy. it is only this way on an upgrade ok. from a new install that is not an issue. I have no clue why because I stop caring I brought this up I think last year or the very begening of this year. I noticed the same thing happen again on my latest stable upgrade last night. as for the udev problem that was solved many moons ago slackpkg install-new would have fixed that. and after your done. with the upgrade clean the system and start fresh time. Why because this is the most incredible virgin Pat has put out and she needs to start clean only my point of view. |
All times are GMT -5. The time now is 02:56 PM. |