Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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.
Hi all! I am considering adding Slackware to my computer so that it will be dual booting openSUSE/Slackware instead of openSUSE/Vista. I have an HP Pavillion dv2xxxx and I'm concerned about the wireless feature. With openSUSE that was not a problem (the touchpad had to be configured though). What are the possible difficulties I may encounter and how can I prepare for them?
Feel free to add any information that you think might be helpful (partitioning e.g.). Many thanks in advance!
Congratulations for that decision.
Although as usual there is lean support from wireless hardware makers for linux meantime. Since you have a driver for that hardware by way of Suse i suppose it should work with your Slackware.
One more info: if you wanted faster software choice and installation for Slackware 13.37 I will suggest you first begin with Salix OS, it is faster there and the packages are ready and can be installed by few clicks; still you will enjoy the fast and stable Slackware in Salix OS variant.
Good luck.
One more info: if you wanted faster software choice and installation for Slackware 13.37 I will suggest you first begin with Salix OS, it is faster there and the packages are ready and can be installed by few clicks; still you will enjoy the fast and stable Slackware in Salix OS variant.
Good luck.
Thanks for the info. I wasn't aware of that choice. I'll look into it, though I'm not easily intimidated by tedious procedures.
What wireless chipset is in your computer? That's the key piece of information to determine how difficult is might be to set up in Slackware.
I have Salix on my netbook and quite like it for that purpose, but I would not use it in preference to Slackware on a laptop/desktop. But that's just me.
It's the PRO/Wireless 5100 AGN [Shiloh] Network Connection.
I'm trying to define a good partitioning scheme for a 140GB disc. Do I really need more than /, /home and swap for home use?
And another question. I have the bootloader from openSUSE installed with the options 1. Boot from MBR and 2. Boot from the extended partition. I used the extended partition because I had two Vista partitions originally. Now, I have erased both Vista partitions, so that I can install the Slackware. Where should I place the bootloader and can I use the one that openSUSE uses? I'm a tad bit confused and a little help would be appreciated.
So I went on and installed it (just 2 partitions and swap) and I was able to use openSUSE's boot loader. I actually did the partitioning from opemSUSE which helped me a bit. The major problem I have now is with the network. I think I may have skipped accidentally this step so now it I have no wireless connection, hence no internet. What's the best way of dealing with this problem?
Having no internet is a huge obstacle and has to be tackled first.
Try running the lspci command from the terminal (you may have to do that with root privileges).
That should report the wireless chipset, which is much more important as far as Linux is concerned the wireless card brand. Post the results here and we can help.
I'm trying to configure the network. Problem it doesn't go by the book, or I'm doing something wrong. I tried
Code:
bash-4.1# ./rc.wireless
WARNING: The script 'rc.wireless' must be executed by 'rc.inet1'!
You should run the command "/etc/rc.d/rc.inet1 <your_interface>_start" yourself.
bash-4.1# iwconfig
lo no wireless extensions.
bash-4.1
What's <your_interface> supposed to mean and how can I find mine?
Intel generally works well with Linux, but googling "Intel Corporation PRO/Wireless 5100 AGN slackwar" seems to indicate that that chipset can be cantankerous.
Try installing wicd. It's in Extras. It's a lot easier to use than wpa-supplicant. I have had a chip on my Acer not work with wpa-supplicant fire right up with wicd. (No, I don't know why, I was just glad it started working). That one also has an intel chip:
Try installing wicd. It's in Extras. It's a lot easier to use than wpa-supplicant. I have had a chip on my Acer not work with wpa-supplicant fire right up with wicd. (No, I don't know why, I was just glad it started working).
I cannot even access the dvd, which I know it's in /dev/sr0 (as reported during installation.
I cannot even access the dvd, which I know it's in /dev/sr0 (as reported during installation.
Maybe it's not meant to be...
- pascal
A little late in jumping in. For the network you can use Configuring your network in Slackware <- Alien_Bob's excellent article on the way network cards are configured in Slackware. + Loads of internal reference links + Ethernet & Wireless
You need to be sure that the firmware is there for your device.
As for the '/dev/sr0' issue, what do you see in 'dmesg'? Both for boot & after installing a media disk after the system has booted. Post your '/etc/fstab'.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.