Linux Arch user here, I need to wait 90 seconds everytime I'm launching laptop because of this.
How to get rid of this?
Other urls found in this thread:
wiki.archlinux.org
twitter.com
Install Gentoo
in /etc/systemd/system.conf you can change the default timeout period
#DefaultTimeoutStartSec=90s
#DefaultTimeoutStopSec=90s
You might want to fix the actual issue though, since it's hanging on your network device it's probably timing out to get DHCP or something. (Laptop?)
didn't see you said laptop in your post, this is almost certainly related to your wifi or it trying to get DHCP from your ethernet port.
Acer Aspire 5742G
I'll try edit this file, thanks
As you said, this is related to ethernet port. This is what I get after 90 seconds.
Changing file didn't helped.
I tried to change it 0s, then 1s, still same result.
turn off DHCP or disable the network interface by default: wiki.archlinux.org
Can't help too much, I use Debian.
did you uncomment the config variables?
>2017 almost 2018
>lunix still can't into wifi working correctly
what a piece of shit
Set up eth0 in /etc/network/interfaces to be hotpluggable.
Fuck this, I did and I set that 0s. And you know what? I fucked up my pc. Now it's gonna launch entire eternity. I need to reinstall arch.
I get something similar (start job is running) but for the dhcpdp service for my ethernet adapter. It corrects itself after 6-10 seconds, but it's still annoying and adds that much more time to boot up. I googled around and some said it was related to a systemd update
Maybe it's good time to try gentoo
>the ganoo linux experience
>broadcom wifi
i had the same issue for the longest time, and i fixed it by installing debian stable
dhcpcd*
Also surely it doesn't take my dhcp "server" (the router) 10 seconds to do the 4 way DHCP handshake. That's ridic
OP here.
I'm done, I'm installing gentoo.
Try using NetworkManager instead of dhcpcd.
Install Network Manager:
$ sudo pacman -S networkmanager network-manager-applet
Then disable dhcpcd.
$ sudo systemctl disable dhcpcd.service
Then
$ sudo systemctl enable networkmanager.service
Arch is an independently developed distribution aimed at competent gnu/linux users. Try ubuntu.
Reinstalling for one fucking change that can be done in the same media that's used for the reinstallation. The absolute state of Sup Forums.
Try Debian you idiot
Only good goys use Arch
>systemd
found the problem
also (((update)))
>$ sudo systemctl enable networkmanager.service
FYI it has to be NetworkManager.service because it's case sensitive and won't work otherhwise
Correct. I was just writing from memory.
I wasn't trying to one-up you btw. I actually have the same problem as OP and just discovered the case sensitive issue as I was following instructions in this thread. My problems are all solved now, dunno about OP
Disable and uninstall DHCPD. Install connman.
boot off a live CD and change the 0 (disabled) to something reasonable, like 10 or 30.
Turning off timeout completely is a bad idea.
The correct solution is to configure your network device to not try to find DHCP on boot.
If you're not competent enough to do this, or boot off a live CD to fix your config file, you shouldn't be using Arch.
>can't do basic thing
>better pick a distro where I got to write my own configs
man, Sup Forums pushes these distro memes hard. Install Ubuntu.
(((package managers)))
sounds overkill when you can just tell systemd to transit to rescue.target (or any target that's pre-network) and fix it from there
You shouldn't be on Arch if you don't know what chroot is...
>systemd is fast they said
OP here.
Managed to solve this problem.
OP here.
Baited yet another group of newshits.
fuck off to your botnet, brainlet
install windows
Install Windows.