[ Thread Index |
Date Index
| More lists.tuxfamily.org/slitaz Archives
]
- To: slitaz@xxxxxxxxxxxxxxxxxxx
- Subject: udev failure
- From: Indigo <pointofavailability@xxxxxxxxx>
- Date: Thu, 11 Nov 2010 20:53:07 +0000
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=TW2Q5ulPeJv77X94yWF0ZIrkTC5THaZBBwrct+e99Pw=; b=QBpQcf8OeiUofVwWfsvUuV2kOVm46nj2U1rPWm3KPWOtWM1CDf1AfByuDmfutsuQJ2 Wy3yd8NO0nl6TEnQfkrvdxuYH6sctKa6zLApxOKTcb9B0MUwrpLf90SiuvRcrvuCVv9T ayIbcM/g8Ifb1hhX/RehCAJ3iATyYYxtJQQS4=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=kcCqERHxPh87l/3xGeHRO0cVS2xah0FXMaBM21uHqYp4d3hb+ZiTeLXxgWx21rEPkm WLLSFxIA2JulA16VUJvnAx5UogXpwmSOnJzT4CbqzSo1JpsqqutnBb3L0UVwsNUyGMvH 50qYqJvzhjzmsdhmsHBTGtkBTIHTZphr4/UcQ=
I am trying to diagnose why udev fails during bootup. In
/etc/udev/udev.conf I set udev_log="debug", but since the filesystem
is mounted read-only during the boot process, output is sent to the
console, and the messages roll by way too quickly to read.
Nevertheless, I have glimpsed at least one read-only filesystem error,
and I'm almost certain udevd is failing because of this -- udevadm
also has errors, 'unable to connect to socket, connection refused',
though the status does not show it as failed.
I'm writing with three questions in mind:
1) As I understand it, the kernel would need to be recompiled to
include udevtmpfs, which is where most distros mount udev, in order to
fix this. It is beyond my knowledge, but is it possible to start udev
after the filesystem has been checked and remounted read-write?
2) Could this cause Xorg's failure to use hardware detection to get
the right refresh rates for the display? The reason only some systems
seem to have problems with attaining higher resolutions is that Xorg
is falling back to default horizontal refresh rates that are out of
range for newer screens. I know Xorg depends on udev, but I don't
really understand the process.
3) Has anyone got any better ideas? I don't know how I can get a
copy of the output during bootup, and I have no idea what more can be
done to troubleshoot Xorg.
---
SliTaz GNU/Linux Mailing list - http://www.slitaz.org/