#Slackware networking not working

1 messages · Page 1 of 1 (latest)

open meadow
#

I already tried out mint, it was a bit boring
also I already got far enough into slackware that I'm trying to update from a mirror and for some reason I can't connect to internet
I already did netconfig
and pinging doesn't do anything it just claims I can't reach anything
Using ip link show and then using ifconfig eth0 or ip link set dev eth0 just changed the name for some reason?

strange storm
#

I haven't used slackware before, so take this with a grain of salt. udev changes the names of the NICs on your machine so that they will always be the same name upon reboot. So use those names when you set up your networking

open meadow
#

Eitherent shows as working but pinging still does nothing

#

*Ethernet

#

Yeah, it ain't reaching the router

#

I can't ping the router

strange storm
#

Do you have a route set up? What does ip r show?

open meadow
#

It gives me a loopback address

#

127.0.0.0/8 lo scope link

timber kelp
#

Show us the ifconfig output?

open meadow
#

Eithernet doesn't show anything because I don't have it plugged in at the moment but there's normally some rx packets being recieved

#

*Ethernet

open meadow
#

I think I've gotta somehow change the loopback address to the address of the router I'm trying to connect to

#

Is my dhcpd.conf file supposed to be empty?

#

It keeps saying that the directory just doesn't exist

#

I did something

#

I'm not sure what

#

I think I fixed the ip address thing or something because it's pinging now

#

Idk how to make it stop

strange storm
open meadow
#

I could ping the router but I still can't ping google or anything like that

#

From anything I can find dns isn't set up but how would I set up dns?

strange storm
open meadow
#

As far as I know no, however I think I just screwed up because I changed it from using autoconfig for both ipv4 and ipv6 to just ipv4

#

and now it works

strange storm
#

Ah ok

strange storm
#

Ahh, you're cross-posting. It would be best to either only ask questions here or in general, but not both

open meadow
#

Yeah I'm thinking I've solved it but I'm not sure

open meadow
#

Does anyone know how to solve ".serverauth.993" does not exist? it shows up when trying to start a windows manager

timber kelp
open meadow
#

startx

#

No such file or directory

timber kelp
#

That last bit should be a tilde

#

Not a dash

#

(The curly key above tab on a US keyboard)

open meadow
#

(invalid option -- '~')

timber kelp
#

Show a picture? You're missing a space or something

#

Check my command very carefully and type it exactly, because it for sure works to show what I want

open meadow
#

alr gimme a sec

open meadow
#

*think

timber kelp
#

Yes, there should be a space between -ld and ~

#

~ is shorthand for the current user's home directory, I didn't want to be guessing at it's path

#

But, first thing I notice from the screenshot is that you are running as the root user. You should not run a graphical desktop as the root user. Not that it would be unfunctional, but it opens up rush that you don't need to be taking

#

Have you created a regular user account yet?

open meadow
#

Yeah

timber kelp
#

Okay, you should try startx when logged in as your regular user, it might just work, but if you get the same problems, then show me the ls output from your regular user

open meadow
timber kelp
#

Did you do a full install of Slackware, or minimal, then adding packages?

open meadow
#

Full install

timber kelp
#

Okay, so you should have all of the dependencies you need. Can you cat /var/log/Xorg.0.log?

open meadow
#

I've ran it

#

It doesn't seem to have worked

timber kelp
#

Gods it's been so long since I've used Slackware in anger. Try sudo init 4, or sudo runlevel 4, I can't remember which of those will elevate your runlevel to graphical multiuser and just give you a login screen. I would usually just change the value in /etc/inittab from 3 to 4 and reboot when I used to use Slackware regularly

#

I really hope you don't actually need to configure your xorg. That's some pain usually

open meadow
#

It's asking for a password and it's not the password for either root or my normal account

timber kelp
#

Oh, I bet your regular user isn't a sudoer. su -, enter your root password, then run those commands without sudo

#

Is Slackware your first attempt at Linux?

open meadow
timber kelp
#

No worries. Just that Slackware, like Arch, doesn't do a lot of handholding.

open meadow
#

I've noticed

timber kelp
#

Lol

open meadow
#

It says it's starting the X11 manager

timber kelp
#

It's how I cut my teeth though, it will give you a solid foundation

timber kelp
open meadow
#

Nope, still siting at starting x11

#

*sitting

timber kelp
#

Hmmmmm

open meadow
#

Still going

timber kelp
#

Hit enter again, it's probably back at the shell

open meadow
#

Yeah, I think you're right

#

Tried init 4 again and this time it did nothing

#

I'm thinking of just rebooting and trying init 4 again

#

I'm gonna do that

#

That didn't wrok

#

*work

#

I might just not use slackware and go with something else

#

This has been a dumpster fire

timber kelp
#

Sorry, I wandered off to play games for a bit. Slackware definitely takes some fiddling. The community is smaller than you will find if you run something like Debian or Fedora. To really wrangle Slackware, you'll either need to know your CLI pretty well, or be prepared to learn it trial-by-fire style. From what I saw in this thread before I joined, and what I was here for later, I have three observations/tips:
1- Your computer was not able to access the internet probably because you hadn't run dhcpcd (the dhcp client daemon), Slack feels like you'd still have to do that by yourself.
2- Launching the wm, if you truly intend to do it from a bare login shell, more power to you, but when I ran Slackware as a desktop machine, the first thing I'd do is sudo nano /etc/inittab and change the line about runlevel from 3 to 4. Save and reboot and you should get a graphical login.
3- I think you were missing sudo privileges, so you'll need to su -, then run visudo, check out which group is granted sudo privileges, then add yourself to that group, which you can do manually with nano /etc/group, just make sure you get the spelling of your username correct. Then log out/log in to be able to use sudo properly.