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.
Now I think you should fix this partition issue before trying to get internet...
For the net card module, I think you need the e100 module
-> Device Drivers
-> Networking support
-> Network device support (NETDEVICES [=y])
-> Ethernet (10 or 100Mbit)
-> EISA, VLB, PCI and on board controllers (NET_PCI [=y])
Intel(R) PRO/100+ support
Nope, can't even start anything on that kernel D: Using my old (Thank GOD I left it) slackware linux, kernel 2.4.26 to type this.
This is the reply when I start:
First it tells me to go in maintenance mode or press ctrl+d to go on (the system will restart if I do, so I only can go to maintenance mode). I type my root pass, and it tells me to run e2fsck and blah.
I do as it tells me, and it spits out this:
Quote:
No such file or directory while trying to open /dev/hda2
The superblock could not be read or does not describve a correct ext2 filesystem.
If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else) then the superblock is corrupt-
And it tells me to run this with an alternate superblock, and says e2fsck -v -y <device>
Maybe an IDE driver issue ? What is your driver chipset ?
(/sbin/lspci | grep IDE [or -i ide or similar...])
Did you enable the correct IDE driver in config ?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.