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.
Hello.
I am a newbie in Slackware and linux in general. After a few days trying t get ACPI work on 2.4 kernel i'd try the test26.s kernel. Ok the install was fine , and after install i have installed kernel_modules and kernel_source.
After reboot my laptop fan was turning on and off when needed. Now there was another problem
I don have network. I have internet connection with dhcp. after a little trying i have installed ipv6 module and finaly i get the IP and my internet was up, but HORYBLY SLOW. this went fine till the first reboot and after that no network nothing.
Can any one help me on this issue ? right now i am forced to use Windowze but i WHANT slackware back !!!
Modify the /etc/rc.d/rc.inet1.conf for DHCP and recompile your kernel so it has support for your network card build in.
Can i just boot another live distro , for ex. Ubuntu , and see what module does it use for my network ?
and after that i try to insert that module in my Slak kernel ?
Or is better to use HUGE kernel ?
What is the main difference beetween test26.s and huge26.s ?
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,644
Rep:
The main difference AFAIK is that huge26.s has much more hardware support build in the kernel while test26.s offers support rather in form of kernel modules. So chances are good that your network card will be supported by huge26.s. And yes, using a live distro might help you with identifying the network card's module, but only if it is not build in the kernel but loaded as module, else it will not be listed by "lsmod" I think.
What network card do you have? If that's the only problem you have right now in my opinion it will be easier to find the modules' name so that you can load it manually or modify your rc.modprobe.
The main difference AFAIK is that huge26.s has much more hardware support build in the kernel while test26.s offers support rather in form of kernel modules. So chances are good that your network card will be supported by huge26.s. And yes, using a live distro might help you with identifying the network card's module, but only if it is not build in the kernel but loaded as module, else it will not be listed by "lsmod" I think.
What network card do you have? If that's the only problem you have right now in my opinion it will be easier to find the modules' name so that you can load it manually or modify your rc.modprobe.
My network card as Windoze say is : Via Compatable Faste Ethernet Controller.
But with kernel 2.4 it worked perfectly
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,644
Rep:
What happens if you do as root "modprobe via-rhine" and then "/etc/rc.d/rc.inet1 restart" and "/etc/rc.d/rc.inet2 restart" (one of them is probably not necessary, but won't hurt anyway)? Does your network card work?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.