Arch Linux

Gelax!

Member

From: Cagliari

Registered: 2011-10-03

Posts: 11

[Solved] problems after "udev -> systemd-tools" update

Hello,
After the last pacman -Syu the keyboard, the mouse and the sound card of my notebook have stopped working..
The last update was:

Pacchetti (10): dnsmasq-2.62-1  fakeroot-1.18.4-1  filesystem-2012.6-2
                geoip-database-20120606-1  icu-49.1.2-1  krb5-1.10.2-1
                libsystemd-185-1  mx-1.4.6-1  rsync-3.0.9-3
                systemd-tools-185-1

the keyboard works in a tty shell, doesn't work only in X... but if i plug an USB mouse or keyboard the plugged device works also fine in X.

this is my modules and daemons in rc.conf:

MODULES=(acpi-cpufreq cpufreq_ondemand cpufreq_powersave vboxdrv bridge tun)
DAEMONS=(hwclock syslog-ng dbus !network @networkmanager @netfs @crond @sensors @bluetooth gdm)

thanks to everyone

Last edited by Gelax! (2012-06-08 10:04:51)

Gelax!

Member

From: Cagliari

Registered: 2011-10-03

Posts: 11

Re: [Solved] problems after "udev -> systemd-tools" update

I tried downgrading udev and its dependencies, but nothing has changed

pacman -U udev-182-2-x86_64.pkg.tar.xz initscripts-2012.04.1-1-any.pkg.tar.xz mkinitcpio-0.8.8-1-any.pkg.tar.xz xf86-video-ati-6.14.4-4-x86_64.pkg.tar.xz xf86-video-intel-2.18.0-3-x86_64.pkg.tar.xz xorg-server-1.12.1-2-x86_64.pkg.tar.xz 

Gelax!

Member

From: Cagliari

Registered: 2011-10-03

Posts: 11

Re: [Solved] problems after "udev -> systemd-tools" update

Solved .. the problem was caused by a wrong mount in fstab. (I have an SSD).

none /run tmpfs mode=0755,size=10m,noatime,nosuid 0 0

was changed to:

none /run/lock tmpfs mode=1777,size=10m,noatime,nosuid,nodev,noexec 0 0

falconindy

Developer

From: New York, USA

Registered: 2009-10-22

Posts: 4,111

Website

Re: [Solved] problems after "udev -> systemd-tools" update

You shouldn't have a mount entry for either of those things in /etc/fstab ...

---

blog | ±github

Gelax!

Member

From: Cagliari

Registered: 2011-10-03

Posts: 11

Re: [Solved] problems after "udev -> systemd-tools" update

I have a SSD, I read on the forum that a possible optimization was to mount in ram /var/run and /var/lock...
before having these problems I mounted it in this way and everything worked perfectly.

none /var/run tmpfs mode=0755,size=10m,noatime,nosuid 0 0
none /var/lock tmpfs mode=1777,size=10m,noatime,nosuid,nodev,noexec 0 0

after the system upgrade i have tryed to mount /run in ram but that created these problems...
so I just mounted /run/lock in ram and everything works fine

Last edited by Gelax! (2012-06-08 12:16:35)

65kid

Member

From: Germany

Registered: 2011-01-26

Posts: 663

Re: [Solved] problems after "udev -> systemd-tools" update

/run is mounted as tmpfs automatically and /var/run and /var/lock are supposed to be symlinks to /run and /run/lock (see latest news item). So these fstab entries are pointless.

Gelax!

Member

From: Cagliari

Registered: 2011-10-03

Posts: 11

Re: [Solved] problems after "udev -> systemd-tools" update

yes i know that now they are symlinks, but previously of the upgrade they was directories, and i mounted it in tmpfs by fstab...
But i did not know that /run was mounted automatically as tmpfs!
Thank you very much, i remove if from my fstab

Gelax!

Member

From: Cagliari

Registered: 2011-10-03

Posts: 11

Re: [Solved] problems after "udev -> systemd-tools" update

One last question, my fstab contains these other two lines for the SSD, they are correct?
thanks

tmpfs /tmp tmpfs nosuid,noatime,mode=1777 0 0
tmpfs /var/log tmpfs defaults,noatime,mode=0755 0 0

Last edited by Gelax! (2012-06-08 12:42:10)

65kid

Member

From: Germany

Registered: 2011-01-26

Posts: 663

Re: [Solved] problems after "udev -> systemd-tools" update

depends. If you use initscripts and you don't want to keep your logs, these are fine as far as I can see. If you use systemd you could remove /tmp since systemd mounts this by itself, but it doesn't hurt to still have it in fstab either.

Gelax!

Member

From: Cagliari

Registered: 2011-10-03

Posts: 11

Re: [Solved] problems after "udev -> systemd-tools" update

yes i use initscripts, thanks for the reply