F14 boot hangs on atd ...
Beartooth
beartooth at comcast.net
Mon Dec 20 17:34:35 UTC 2010
On Sat, 18 Dec 2010 17:40:50 -0500, Tom Horsley wrote:
> On Sat, 18 Dec 2010 22:19:09 +0000 (UTC) I Beartooth wrote:
>
>> Anyway, I suspect the real trouble is misrecognition of the
>> monitor. That's an HP w2207h, at 1680x1050; but xrandr reports 800x480.
That much seems now confirmed. Under ssh -Y, I ran yum update,
then xrandr again, and something seems to have helped a little bit :
among the technojabber below, note that 1024x768 is now present, though
still neither right, nor close, nor used.
[root at BBB ~]# xrandr
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 4096 x 4096
VGA-0 disconnected (normal left inverted right x axis y axis)
DVI-0 disconnected (normal left inverted right x axis y axis)
LVDS connected 1024x768+0+0 (normal left inverted right x axis y axis)
0mm x 0mm
1024x768 60.0*+ 60.0
800x600 60.3 59.9 56.2
848x480 59.7
720x480 59.7
640x480 59.9 59.4
S-video disconnected (normal left inverted right x axis y axis)
[root at BBB ~]#
-- but booting still hangs at whatever follows atd.
This is with the KVM switch out of the loop, and the PC connected
directly and alone to all three peripherals.
> Try booting run level 3 - that won't try to start the X server. (edit
> /etc/inittab and change the :5: on the last line to :3:).
OK, did that, rebooted; grub found a non-PAE kernel (same
numbers), which wasn't there before; I chose it, and got to a login
prompt, which did at least work.
But what good is running without X going to do me?? I'm
electronically dependent on it, and would be even if *seeing* stuff
weren't a main use of my computers.
I logged in as my userid, ran startx, and got a fatal error.
Using /etc/X11/xorg.conf, and also things called xorg.conf.d both
in /etc and in /usr/share, it says "no drivers available" and also "no
screens found."
> You could also look at the /var/log/Xorg.0.log file and see if there are
> any errors that make any sense, but if you are just using it as a
> server, maybe you don't need it starting up X anyway.
I must have said it badly. The machine was designed and built as
a server -- and the first thing I had done to it was change that. It's
now just a PC, with two hard drives and very serious fans.
But that's just a misunderstanding, with no blame to you nor
anyone else.
As root via ssh -Y, I did "cat /var/log/Xorg.0.log|most"; what I
got first included this :
[ 36.234] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Dec 18 $
[ 36.265] (==) Using config file: "/etc/X11/xorg.conf"
[ 36.265] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 36.265] (==) Using system config directory "/usr/share/X11/xorg$
[ 36.325] (==) No Layout section. Using the first Screen section.
[ 36.325] (==) No screen section available. Using defaults.
[ 36.325] (**) |-->Screen "Default Screen Section" (0)
[ 36.325] (**) | |-->Monitor "<default monitor>"
[ 36.325] (==) No device specified for screen "Default Screen Sec$
Using the first device section listed.
[ 36.325] (**) | |-->Device "Videocard0"
[ 36.325] (==) No monitor specified for screen "Default Screen Se$
Using a default monitor configuration.
[ 36.325] (**) Option "AIGLX" "on"
[ 36.325] (==) Automatically adding devices
[ 36.325] (==) Automatically enabling devices
The next log page (after scrolling) referred me to
https://fedoraproject.org/wiki/Input_device_configuration
-- which appears to be an answer of sorts (bad, very bad; and the only
one, afaik) to protests by several of us here on the list about the
incomprehensible boot messages concerning configuration in recent
releases. It is *not* edifying -- but that's another thread ...
I'll get this much off now, suppressing a rant, and go on looking
through that log for what may look like clues.
More information about the users
mailing list