Tag Info

New answers tagged


As said in the EDIT, After the night it came back to normal. IMO it's a hardware pb because sometimes it comes back, and then disappear. Maybe is it linked to the humidity of the room...


I have solved this problem using another method, which is mounting on boot using fstab. More information about that is on this page https://bbs.archlinux.org/viewtopic.php?id=191120


You need to combine udev and systemd. Add a new rule for udev, in /etc/udev/rules.d/95-mywifi.rules, as follows: ACTION=="add", ATTRS{idVendor}=="...", ATTRS{idProduct}=="...", SYMLINK=="mywifi", TAG+="systemd", ENV{SYSTEMD_WANTS}="netctl-auto@mywifi.service" (You must substitute for the dots the Vendor and Product codes appropriate to your dongle). ...


Ok, solution found: I forgot to add "resume" to the hooks in "/etc/mkinitcpio.conf" and generate a new ramdisk with "mkinitcpio -p linux". All stated in the Arch wiki link about suspend and hibernation (see above).


Well. I don't really know what was wrong to create HFS partitions with gdisk or cgdisk. But just don't do it. I have created the hfs partition with Disk utility & used the original bless of Osx then everything worked like charm. If you are going to install Arch, just before deleting OSX, create an empty hfs+ partition to boot properly, since Apple's EFI ...


Check with xev what event is emitted when pressing power off button. In my case was a XF86PowerOff. I simply added a global hotkey to my window manager (AwesomeWM) which runs a little bash script: #!/usr/bin/bash zenity --question --text "Power off?" --default-cancel && poweroff After that my system is asking me what to do when I'm pressing ...


I figured the error out, the nginx config was pointing to the wrong files

Top 50 recent answers are included