SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It needed external drivers which were not available.
Try again.
Andy
OK, I'll take a shot at it. What were the missing drivers?
If they are available to redistribute and we don't include them, I'd like to know. However, I suspect there's at least an open source driver that works with the hardware or you'd see the same issue with other Linux distributions as well.
If the driver is not free to redistribute, you can hardly blame us for that.
OK, I'll take a shot at it. What were the missing drivers?
If they are available to redistribute and we don't include them, I'd like to know. However, I suspect there's at least an open source driver that works with the hardware or you'd see the same issue with other Linux distributions as well.
If the driver is not free to redistribute, you can hardly blame us for that.
Assuming you installed 14.1, that should be supported out of the box. No extra software is needed or even available.
Are you sure the problem isn't that you didn't enable networkmanager? See ryanmcquen's post for how to enable it. Reboot afterwards, start Xfce or KDE, and you should have a working wifi applet in the system tray. Or, I guess, do that when you decide to give Slackware another try.
Quote:
I hope you have a better tomorrow.
*grins like Chow Yun Fat
Don't worry, I don't have two handguns to pull out.
You're experiencing the typical symptoms of migrating from Windows. In a first stage you may think that distributions, interfaces and software in general that try to make the migration easier emulating Windows are better, and in front of those that don't you'll complain in forums thinking it's a bug. Well that's just a wrong first impression. I was trying along the years to advice that that developers mistake in the end would hurt the evolution of Linux. And I was right, today we all suffer the consequences of the lindowisation. Curiously, a lot of linux developers, maintainers and users that today complain about that consequences stay in that mistake of advocating the "out of the box" experience ala Windows (and they call my sincere advice trolling).
The true is that to enjoy and value a unix like OS you must first get the out of the box experience out of your system. By system I mean you :-). Because freedom has sense when YOU choose and decide what to automate.
In practice, if you're not really disposed or you have not enough time to learn how to configure i.e. your network by hand, I mean reading documentation and editing text files, my advice is don't fool yourself, MS Windows is the better option for you.
$ grep -i iwlwifi config-*-3.10.17
config-generic-3.10.17:CONFIG_IWLWIFI=m
config-generic-3.10.17:CONFIG_IWLWIFI_OPMODE_MODULAR=y
config-generic-3.10.17:# CONFIG_IWLWIFI_DEBUG is not set
config-generic-3.10.17:# CONFIG_IWLWIFI_DEVICE_TRACING is not set
config-generic-3.10.17:# CONFIG_IWLWIFI_P2P is not set
config-huge-3.10.17:CONFIG_IWLWIFI=m
config-huge-3.10.17:CONFIG_IWLWIFI_OPMODE_MODULAR=y
config-huge-3.10.17:# CONFIG_IWLWIFI_DEBUG is not set
config-huge-3.10.17:# CONFIG_IWLWIFI_DEVICE_TRACING is not set
config-huge-3.10.17:# CONFIG_IWLWIFI_P2P is not set
I had to look PEBKAC up since I hadn't seen it before, and I LMAO! So true! I must note, however, that PEBKAC exists everywhere, even (dare I say especially?) among experienced users. We accumulate so much knowledge that we forget the basics on occasion. (I include myself in that equation).
Sorry, it wasn't intentional: I didn't notice that you had commented again while I was writing my post. Anyway, it seems that your device is supported, so yours is probably a mere configuration issue. Regarding the lack of automated configuration tools in Slackware, that's exactly how the distribution is intended to be: simple, transparent, and stable. It might have a steeper learning curve than other distros, and will require some documentation effort, but it's definitely worth trying, and then you'll appreciate the advantages. But I suggest again that you read some stuff, and then you'll understand why Slackware is the way it is, and you will be able to make a conscious choice. Which, of course, is entirely up to you.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.