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.
Yes startx starts the gui. To make it always boot to gui edit /etc/inittab and change
id:3:initdefault:
to
id:4:initdefault:
Don't know about your nic but you may need to load a module for it if you can find which one. You will probably be better off making a new thread about that so people can see what you need help about.
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,644
Rep:
I think the modules should be called e100 or eepro100. Maybe add them to /etc/rc.d/rc.modules or compile your own kernel with both or just one of them (if you test them before which is the right one) compiled in.
To add them to rc.modules add these lines to that file:
modprobe e100
modprobe eepro100
You use "installpkg filename" to install the packages. Edit: or, as Hern_28 says, run pkgtool and select to install packages from the current directory, or another directory as is relevant.
Just cd in the /extra/linux(version) and type pkgtool, select install from current directory, and answer yes to everything except the headers. Only warning is the headers will bork your system so don't install them.
Edit: its possible that this might also fix the networking problem too but there is no guarantee. Reason why I suggest everything else is you will need the rest to compile software if you ever desire to try it. The other files are also necessary to install proprietary video drivers.
2nd edit: Nylex is correct, been a while since i installed slackware or used the pkgtool. Thank you Nylex. I Changed this to keep others from making a mistake .
When you run installpkg, you aren't asked whether to install the package or not, so I suggest not running "installpkg *.tgz" as that will install the headers as well as the others.
When you run installpkg, you aren't asked whether to install the package or not, so I suggest not running "installpkg *.tgz" as that will install the headers as well as the others.
I just ran installpkg *.tgz, and now when I boot up, it runs KDE. At install, I chose XFCE. Is there a way to install xfce and delete KDE?
P.S- Internet is running smoothly. Posting from my slackware box now.
Run xwmconfig to set your default window manager. If you want to remove KDE, then just remove all the KDE packages, which you can do with "removepkg kde*".
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.