Configured my internet stuff yet it refuses to let me use the internet!
 

I set up all my internet stuff from the terminal. I set it as a DHCP and put in a domain name and everything. I then rebooted Slack, went in and the same thing happens. "Error loading page", and "Could not find page" are just some of my favorites. What's going on? I configured everything correctly, is Slack not seeing my network card or something? I'm typing this from Win right now, I wish I was able to type from Slack though..

Thanks for putting up with me, if I can just get this to work I'll leave you guys alone. Thanks for any help.

What network card are you using?

You're right. I had the same problem. You need to manually load the network driver or configure it to load at startup.

If your network driver is not already there, you may have to recompile the kernel module for them :(

eep, doesn't sound too fun..

About that card type ... my dad knows that, but I'll ask him tomorrow what it is.

why worry so much about kernel compilation? ihihih
just do it if needed...

but I have some more info for you:

disable the current interfaces such as eth0 or stuff like that (just for now)

run "adsl-setup", and follow the very well commented script

after you did that you can do these:
adsl-start (to bring up your dsl link)
adsl-status (to see how the link is)
adsl-stop (to kill the processes pppd and adsl-connect, that is, disconnect :-)

Here I assume you have an ADSL connection as mentioned in previous threads...
if everything's right, you should see the interface ppp0 up when running ifconfig...

if your link is up, try "ping www.google.com" for example and see if it responds something like this:

JOANNES=[Online]=>ping www.google.com
PING www.google.akadns.net (64.233.187.104) 56(84) bytes of data.
64 bytes from 64.233.187.104: icmp_seq=1 ttl=240 time=231 ms
64 bytes from 64.233.187.104: icmp_seq=2 ttl=240 time=231 ms
64 bytes from 64.233.187.104: icmp_seq=3 ttl=240 time=225 ms
64 bytes from 64.233.187.104: icmp_seq=4 ttl=240 time=226 ms

No... fun if you like compiling your custom kernels and kernel modules :). Not fun if you want something to "just work". I don't think Slack is one of those distros that "just work".

I totally agree with you: Slack is not one of those distros that "just work"

I know but I was getting so tired of newbie distros like RH and such. They do everything for you and that's no fun. Sounds kind of confusing but I'll try to figure this out, I'm going to just sleep on it for now ... Literally, it's kind of late.

Try Debian. It's neither newbie nor totally difficult.

It has more config tools than slack, but not so many that they get in your way. You have both options.

not that confusing
 

it's not that hard...
see the steps:

1.disable the interfaces (ethx, pppx...)

2. adsl-setup (adjust everything)

3. adsl-start (to connect)

4 adsl-status (to see the link status: on or off)

5. adsl-stop (to disconnect)

the other parts of my previous post are just tests, they are not necessary
and I assume your IP address and net config are already set up..

Slackware isn't supposed to be...

Not a distro that 'just works'?
 

Funny that that's the general feeling of this thread. I came back to Slack because it did just work, where others, like Xandros OCE2 didn't. And on a laptop of all things! [Compaq PIII-1Ghz, 320/20, Cabletron Wireless card]

Though I'll probably get burned for being one of the few that it did 'just work' for, as I intend, this weekend, to install it on at least one server for the house and it'll be my first Slackware install on a desktop system since before the Great Version Inflation incident.

haha, i agree with the last poster. one reason i love slack is because a default install "just works". i have a dell truemobile 1150, and i've been trying to get it to work in custom kernels, so i've been doing a lot of reading up on it. everyone has problems with this card, across all the distros. in slack 10.0 it worked out of the box. and the best part about slack is that now, i'm trying to figure out why and how by compiling my own kernel. and i can get into the guts of it if i like, or not, as i choose.

Might be awhile before I go with Debain, if I change anything it'll probably be to FreeBSD.

OK I'll run those commands, thanks.

Wait.. punching in commands is just fine but how to do disable the interfaces? And do I need to disable them to get the internet to work? Furhtermore, how/do I/need to put them back on?

I don't know how I did it, but I typing from Slack right now. Guess I just needed to reboot my computer for the settings to go through.

Thanks for the help on the config.