F19 --> F18 feasible?

[Beartooth]

On Wed, 16 Oct 2013 18:00:11 +0200, Suvayu Ali wrote:

> On Tue, Oct 15, 2013 at 05:04:26PM +0000, Beartooth wrote:
>> 
>> 	My old Thinkpad T30 (on which I ran fedup from F18 to F19) is
>> beginning to seem like more effort than it's worth, ever if eventual
>> success of the effort were a sure thing. Is there a FedDown lurking out
>> there somewhere?
> 
> You can always try `yum --releasever=18 distro-sync'.  But it goes
> without saying, there are no guarantees whatsover.
> 
> That said, could you elaborate your actual problem?  Maybe then someone
> can help.

	I'll try, and also refer you to a thread I began Sunday, called 
"F19 : getting to GUI (or anywhere)," in case I omit anything.

	I had F18 running fine, till I did a fedup (by the website) to 
F19. It seemed to finish, and claimed success. I rebooted. The display 
that came up was way, way oversize. I did Ctrl-Alt-F1 (or maybe F2; I 
disremember); it helped, and the display has been more like normal size 
since. 

	The text displays in a very dim pink-orange-brown color, 
reminiscent of a flashlight whose batteries are almost dead, with the 
green OK of the boot messages barely discernible. (I have it plugged into 
a UPS.)

	It rarely finishes booting, or else abandons the display. At 
first it stopped when it hit sendmail; now it stops after saying it has 
installed an ABRT core dump hook (whatever that is).

	In any case, it fails to show a login screen. It responds to ssh 
over my LAN; so I can log in that way. Here's another attempt to work 
over ssh -Y (which didn't affect the display on the T30's own monitor).

[root at T30 ~]# xinit


X.Org X Server 1.14.3
Release Date: 2013-09-12
X Protocol Version 11, Revision 0
Build Operating System:  3.10.9-200.fc19.x86_64 
Current Operating System: Linux T30.localdomain 3.11.1-200.fc19.i686.PAE 
#1 SMP Sat Sep 14 15:20:42 UTC 2013 i686
Kernel command line: BOOT_IMAGE=/vmlinuz-0-
rescue-1d7352e603b24d77a5b516b0204a434a root=/dev/mapper/vg_t30-lv_root ro 
rd.md=0 rd.dm=0 KEYTABLE=us SYSFONT=True rd.lvm.lv=vg_t30/lv_swap 
rd.luks=0 LANG=en_US.UTF-8 rd.lvm.lv=vg_t30/lv_root rhgb quiet
Build Date: 16 September 2013  12:43:28AM
Build ID: xorg-x11-server 1.14.3-1.fc19 
Current version of pixman: 0.30.0
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Oct 16 16:35:33 2013
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension SELinux
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
(II) [KMS] Kernel modesetting enabled.
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Internal error:   Could not resolve keysym XF86AudioMicMute
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Internal error:   Could not resolve keysym XF86AudioMicMute
Errors from xkbcomp are not fatal to the X server
xinit: Unable to run program "xterm": No such file or directory
Specify a program on the command line or make sure that /usr/bin
is in your path.

xinit: connection to X server lost

waiting for X server to shut down (EE) Server terminated successfully 
(0). Closing log file

[root at T30 ~]# 

-- 
Beartooth Staffwright, Neo-Redneck Not Quite Clueless Power User
Remember I have precious (very precious!) little idea where up is.