New install 3.5 + equo world/ broke X "r128"?

[joe3]

I'm at a loss to understand. I recently got around to downloading Sabayon 3.5 release 1. Which I installed to /dev/sda7 on my desktop PC.

I figured that it was a fairly recent release so I might actually get it to update world. Especially since I've not yet installed the assorted software I insist on or done much else to configure it my way.

Since I'd never played with emerge on it I figured I'd try using equo to update "world" (I don't really remember clearly but I think I used --deep) I did a clean boot, did an <alt>+<ctrl>+<F2> logged in as root and did an "equo world" command...

About 20 hours later it wanted to remove one package that wasn't in the repositories anymore... Since I hadn't installed anything yet And had no Idea what the package was, I went with it's recommendation and let it delete said package... And I let it have it's way with the config files it said needed to be updated.

Then I noticed that <alt>+<F7> didn't pull up the gui logon screen. But I edited my grub to use the new kernel, & rebooted. But I still didn't get a gui-boot A little poking around and I found an Xorg.0.log that seamed to be complaining about a missing module "r128"...

Since my video card is an old rage 128, I think that's the problem.

How can I fix this??? Please don't say I'd need to do a clean install after spending 20 hours waiting for all the package updates...

In case it helps, I'm including the text of that Xorg.0.log below,,,

Please help:

--
joe3


- - - - - - - - -< Begin Xorg.0.log >- - - - - - - - - -


X.Org X Server 1.4.2
Release Date: 11 June 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.25-sabayon i686
Current Operating System: Linux localhost 2.6.26-sabayon #1 SMP Sat Aug 9 12:00:55 UTC 2008 i686
Build Date: 05 July 2008 12:20:12PM

Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
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: Sat Sep 27 14:11:15 2008
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Main Layout"
(**) |-->Screen "Screen 1" (0)
(**) | |-->Monitor "Generic Monitor"
(**) | |-->Device "VESA"
(**) |-->Input Device "Mouse1"
(**) |-->Input Device "Mouse2"
(**) |-->Input Device "Mouse3"
(**) |-->Input Device "stylus"
(**) |-->Input Device "cursor"
(**) |-->Input Device "eraser"
(**) |-->Input Device "Keyboard1"
(**) Option "AllowMouseOpenFail" "true"
(==) Automatically adding devices
(==) Automatically enabling devices
(==) Including the default font path /usr/share/fonts/misc/,/usr/share/fonts/TTF/,/usr/share/fonts/OTF,/usr/share/fonts/Type1/,/usr/share/fonts/100dpi/,/usr/share/fonts/75dpi/.
(**) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/Type1/,
/usr/share/fonts/TTF/,
/usr/share/fonts/75dpi/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/corefonts,
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF,
/usr/share/fonts/Type1/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
(==) RgbPath set to "/usr/share/X11/rgb"
(==) ModulePath set to "/usr/lib/xorg/modules"
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) Loader magic: 0x8193a40
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.3
X.Org Video Driver: 2.0
X.Org XInput driver : 2.0
X.Org Server Extension : 0.3
X.Org Font Renderer : 0.5
(II) Loader running on linux
(II) LoadModule: "pcidata"
(II) Loading /usr/lib/xorg/modules//libpcidata.so
(II) Module pcidata: vendor="X.Org Foundation"
compiled for 1.4.2, module version = 1.0.0
ABI class: X.Org Video Driver, version 2.0
(++) using VT number 7

(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 1022,7006 card 0000,0000 rev 25 class 06,00,00 hdr 80
(II) PCI: 00:01:0: chip 1022,7007 card 0000,0000 rev 01 class 06,04,00 hdr 81
(II) PCI: 00:07:0: chip 1022,7408 card 0000,0000 rev 01 class 06,01,00 hdr 80
(II) PCI: 00:07:1: chip 1022,7409 card 0000,0000 rev 07 class 01,01,8a hdr 00
(II) PCI: 00:07:3: chip 1022,740b card 0000,0000 rev 03 class 06,80,00 hdr 00
(II) PCI: 00:07:4: chip 1022,740c card 0000,0000 rev 06 class 0c,03,10 hdr 00
(II) PCI: 00:0f:0: chip 105a,4d68 card 105a,4d68 rev 01 class 01,80,85 hdr 00
(II) PCI: 00:13:0: chip 1102,0002 card 1102,8032 rev 07 class 04,01,00 hdr 80
(II) PCI: 00:13:1: chip 1102,7002 card 1102,0020 rev 07 class 09,80,00 hdr 80
(II) PCI: 00:14:0: chip 8086,1229 card 8086,0040 rev 0c class 02,00,00 hdr 00
(II) PCI: 01:05:0: chip 1002,5046 card 1002,5446 rev 00 class 03,00,00 hdr 00
(II) PCI: End of PCI scan
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 0 I/O range:
[0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) Bus 0 non-prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B]
(II) Bus 0 prefetchable memory range:
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B]
(II) PCI-to-PCI bridge:
(II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x000a (VGA_EN is set)
(II) Bus 1 I/O range:
[0] -1 0 0x0000e000 - 0x0000efff (0x1000) IX[B]
(II) Bus 1 non-prefetchable memory range:
[0] -1 0 0xff900000 - 0xff9fffff (0x100000) MX[B]
(II) Bus 1 prefetchable memory range:
[0] -1 0 0xeea00000 - 0xf6afffff (0x8100000) MX[B]
(II) PCI-to-ISA bridge:
(II) Bus -1: bridge is at (0:7:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
(--) PCI:*(1:5:0) ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS rev 0, Mem @ 0xf0000000/26, 0xff9fc000/14, I/O @ 0xe800/8, BIOS @ 0xff9c0000/17
(II) Addressable bus resource ranges are
[0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B]
[1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) OS-reported resource ranges:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
(II) PCI Memory resource overlap reduced 0xf8000000 from 0xfbffffff to 0xf7ffffff
(II) PCI Memory resource overlap reduced 0xfebff000 from 0xfebfffff to 0xfebfefff
(II) PCI I/O resource overlap reduced 0x0000ff8c from 0x0000ff8f to 0x0000ff8b
(II) Active PCI resource ranges:
[0] -1 0 0xffac0000 - 0xffadffff (0x20000) MX[B]
[1] -1 0 0xffaf6000 - 0xffaf6fff (0x1000) MX[B]
[2] -1 0 0xffafc000 - 0xffafffff (0x4000) MX[B]
[3] -1 0 0xffaf7000 - 0xffaf7fff (0x1000) MX[B]
[4] -1 0 0xfebff000 - 0xfebfefff (0x0) MX[B]O
[5] -1 0 0xf8000000 - 0xf7ffffff (0x0) MX[B]O
[6] -1 0 0xff9c0000 - 0xff9dffff (0x20000) MX[B](B)
[7] -1 0 0xff9fc000 - 0xff9fffff (0x4000) MX[B](B)
[8] -1 0 0xf0000000 - 0xf3ffffff (0x4000000) MX[B](B)
[9] -1 0 0x0000ff00 - 0x0000ff3f (0x40) IX[B]
[10] -1 0 0x0000fff0 - 0x0000fff7 (0x8) IX[B]
[11] -1 0 0x0000ff40 - 0x0000ff5f (0x20) IX[B]
[12] -1 0 0x0000ff90 - 0x0000ff9f (0x10) IX[B]
[13] -1 0 0x0000ffa8 - 0x0000ffab (0x4) IX[B]
[14] -1 0 0x0000ffa0 - 0x0000ffa7 (0x8) IX[B]
[15] -1 0 0x0000ffac - 0x0000ffaf (0x4) IX[B]
[16] -1 0 0x0000ffe0 - 0x0000ffe7 (0x8) IX[B]
[17] -1 0 0x0000cb00 - 0x0000cb0f (0x10) IX[B]
[18] -1 0 0x0000e800 - 0x0000e8ff (0x100) IX[B](B)
(II) Inactive PCI resource ranges:
[0] -1 0 0x0000ff8c - 0x0000ff8b (0x0) IX[B]O
(II) Active PCI resource ranges after removing overlaps:
[0] -1 0 0xffac0000 - 0xffadffff (0x20000) MX[B]
[1] -1 0 0xffaf6000 - 0xffaf6fff (0x1000) MX[B]
[2] -1 0 0xffafc000 - 0xffafffff (0x4000) MX[B]
[3] -1 0 0xffaf7000 - 0xffaf7fff (0x1000) MX[B]
[4] -1 0 0xfebff000 - 0xfebfefff (0x0) MX[B]O
[5] -1 0 0xf8000000 - 0xf7ffffff (0x0) MX[B]O
[6] -1 0 0xff9c0000 - 0xff9dffff (0x20000) MX[B](B)
[7] -1 0 0xff9fc000 - 0xff9fffff (0x4000) MX[B](B)
[8] -1 0 0xf0000000 - 0xf3ffffff (0x4000000) MX[B](B)
[9] -1 0 0x0000ff00 - 0x0000ff3f (0x40) IX[B]
[10] -1 0 0x0000fff0 - 0x0000fff7 (0x8) IX[B]
[11] -1 0 0x0000ff40 - 0x0000ff5f (0x20) IX[B]
[12] -1 0 0x0000ff90 - 0x0000ff9f (0x10) IX[B]
[13] -1 0 0x0000ffa8 - 0x0000ffab (0x4) IX[B]
[14] -1 0 0x0000ffa0 - 0x0000ffa7 (0x8) IX[B]
[15] -1 0 0x0000ffac - 0x0000ffaf (0x4) IX[B]
[16] -1 0 0x0000ffe0 - 0x0000ffe7 (0x8) IX[B]
[17] -1 0 0x0000cb00 - 0x0000cb0f (0x10) IX[B]
[18] -1 0 0x0000e800 - 0x0000e8ff (0x100) IX[B](B)
(II) Inactive PCI resource ranges after removing overlaps:
[0] -1 0 0x0000ff8c - 0x0000ff8b (0x0) IX[B]O
(II) OS-reported resource ranges after removing overlaps with PCI:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
(II) All system resource ranges:
[0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0xffac0000 - 0xffadffff (0x20000) MX[B]
[5] -1 0 0xffaf6000 - 0xffaf6fff (0x1000) MX[B]
[6] -1 0 0xffafc000 - 0xffafffff (0x4000) MX[B]
[7] -1 0 0xffaf7000 - 0xffaf7fff (0x1000) MX[B]
[8] -1 0 0xfebff000 - 0xfebfefff (0x0) MX[B]O
[9] -1 0 0xf8000000 - 0xf7ffffff (0x0) MX[B]O
[10] -1 0 0xff9c0000 - 0xff9dffff (0x20000) MX[B](B)
[11] -1 0 0xff9fc000 - 0xff9fffff (0x4000) MX[B](B)
[12] -1 0 0xf0000000 - 0xf3ffffff (0x4000000) MX[B](B)
[13] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[14] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[15] -1 0 0x0000ff00 - 0x0000ff3f (0x40) IX[B]
[16] -1 0 0x0000fff0 - 0x0000fff7 (0x8) IX[B]
[17] -1 0 0x0000ff40 - 0x0000ff5f (0x20) IX[B]
[18] -1 0 0x0000ff90 - 0x0000ff9f (0x10) IX[B]
[19] -1 0 0x0000ffa8 - 0x0000ffab (0x4) IX[B]
[20] -1 0 0x0000ffa0 - 0x0000ffa7 (0x8) IX[B]
[21] -1 0 0x0000ffac - 0x0000ffaf (0x4) IX[B]
[22] -1 0 0x0000ffe0 - 0x0000ffe7 (0x8) IX[B]
[23] -1 0 0x0000cb00 - 0x0000cb0f (0x10) IX[B]
[24] -1 0 0x0000e800 - 0x0000e8ff (0x100) IX[B](B)
[25] -1 0 0x0000ff8c - 0x0000ff8b (0x0) IX[B]O
(II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
(II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
(II) "glx" will be loaded. This was enabled by default and also specified in the config file.
(II) "freetype" will be loaded. This was enabled by default and also specified in the config file.
(II) "type1" will be loaded. This was enabled by default and also specified in the config file.
(II) "record" will be loaded by default.
(II) "dri" will be loaded. This was enabled by default and also specified in the config file.
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.4.2, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "i2c"(II) Module "i2c" already built-in
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="X.Org Foundation"
compiled for 1.4.2, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "ddc"(II) Module "ddc" already built-in
(II) LoadModule: "type1"
(II) Loading /usr/lib/xorg/modules/fonts//libtype1.so
(II) Module type1: vendor="X.Org Foundation"
compiled for 1.4.2, module version = 1.0.2
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.5
(II) Loading font Type1
(II) LoadModule: "freetype"
(II) Loading /usr/lib/xorg/modules/fonts//libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
compiled for 1.4.2, module version = 2.1.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.5
(II) Loading font FreeType
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.4.2, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "synaptics"
(II) Loading /usr/lib/xorg/modules/input//synaptics_drv.so
(II) Module synaptics: vendor="X.Org Foundation"
compiled for 4.3.99.902, module version = 1.0.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 2.0
(II) LoadModule: "vbe"
(II) Loading /usr/lib/xorg/modules//libvbe.so
(II) Module vbe: vendor="X.Org Foundation"
compiled for 1.4.2, module version = 1.1.0
ABI class: X.Org Video Driver, version 2.0
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.4.2, module version = 1.0.0
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension XFree86-DRI
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
compiled for 1.4.2, module version = 1.13.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 0.3
(II) Loading extension RECORD
(II) LoadModule: "r128"
(WW) Warning, couldn't open module r128
(II) UnloadModule: "r128"
(EE) Failed to load module "r128" (module does not exist, 0)
(II) LoadModule: "mouse"
(II) Loading /usr/lib/xorg/modules/input//mouse_drv.so
(II) Module mouse: vendor="X.Org Foundation"
compiled for 1.4.2, module version = 1.3.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 2.0
(II) LoadModule: "synaptics"
(II) Reloading /usr/lib/xorg/modules/input//synaptics_drv.so
(II) LoadModule: "wacom"
(II) Loading /usr/lib/xorg/modules/input//wacom_drv.so
(II) Module wacom: vendor="X.Org Foundation"
compiled for 4.3.99.902, module version = 1.0.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 2.0
(II) Wacom driver level: 47-0.7.8 $
(II) LoadModule: "kbd"
(II) Loading /usr/lib/xorg/modules/input//kbd_drv.so
(II) Module kbd: vendor="X.Org Foundation"
compiled for 1.4.0.90, module version = 1.2.2
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 2.0
(EE) No drivers available.

Fatal server error:
no screens found

[wolfden]

what did you download?? there is no 3.5 r1

what is the iso name?

[joe3]

OK sorry, something I read on my way to finding out about this available version of sabayon refered to it as stable release 1 and since the kernal the dvd installed had r1 at the end of it's filename I, did that stupid thing and did "assume" that r1 and/or release 1 was an recognizeable referance... wherever I have used either referance, please substitute

Sabayon Linux 3.5 Stable

or

Sabayon-Linux-x86-3.5.iso

Whichever makes the most sense...

Thanks & my appologies for the confusion

--
joe3

[mhtt]

you can try checking which Ati drivers you have. do "equo search ati-drivers" and see whether the one you have is for the new kernel (2.6.26?) If not than reequo the right driver. After that try "Xinit" to see whether X loads or new errors come up. G-luck!

[joe3]

Well I thank you for the hint. But it didn't work.

I don't know why there is such a difference. But when I installed from the Sabayon-Linux-x86-3.5.iso x worked with the initial kernal "kernel-genkernel-x86-2.6.25-sabayon-r1". I didn't do any tweeking before doing the equo world. I rebooted into the new sabayon install, escaped the kdm gui login with <alt>+<ctrl>+<F2> Logged in as root, and ran the equo world command... I can't say just what the name of the package that equo said wasn't available anymore and should be removed was... I hadn't installed anything and the name of whatever it was didn't mean anything to me. I only have the memory that I let it uninstall ONE package...

The PC was still running on the old kernal when I logged out of the console root session. Then I attempted to use <alt>+<F7> to get back to the kdm login screen so I could login with the initial user account and poke arround to make sure everything was OK. BUT the lKDM login screen was already gone. I wasn't sure why not but thought that probably something that had been upgraded was no longer compatable with the old kernal and so I rebooted using the new kernal... And x was still broke.

I tried your suggestion about the ati-drivers and NONE of them appeard to be installed. So I used equo to install the one for the x86-2.6.26-sabayon kernel. rebooted again but still no x ... I should perhaps mention that the xor.conf says the driver is supposed to be "r128" ... Perhaps if I knew what it should say to use the new ati-driver???.

[joe3]

I have more data on this problem.

The desktop with the rage 128 recently lost the old windows drive.I replaced it with a larger drive which gave me room to install sabayon 3.5 stable WITHOUT losing the existing loop2 installation. Actually I was also going to install another distro as well, But I decided to use the space to install a redundant copy of sabayon 3.5 stable so I could rerun the equo world to see what the heck that package it wanted to delete was... That turned out to be "cogito" so I doubt that could be the problem.

On the other hand, _THIS_ time I spent more time babysitting the 20+ hour process of "equo world" and I happened to be there when the pc beeped a few times and then informed me that the r128 driver had been moved to it's own package... "xf86-video-r128"... Something I never saw last time (probably because it scrolled off the screen...)

equo search xf86-video-r128 didn't find anything. So I did an:

emerge --sync and

tried with emerge...

emerge found:

[ebuild N ] x11-drivers/xf86-video-r128-6.8.0 USE="dri -debug"

But it was NOT merged, due to something called collision(s) with

x11-drivers/xf86-video-ati-6.9.0
/usr/share/hwdata/videoaliases/r128.xinf


Arghghghgh!

Can I perhaps safely unmerge x11-drivers/xf86-video-ati-6.9.0
Then merge x11-drivers/xf86-video-r128-6.8.0 ?????????????

--
joe3

[joost]

yes you can.

[joe3]

It Worked....

[lxnay]

We are adding the package back to the repo, I didn't know what happened

[joe3]

The problem is only partly fixed. I had spent too much time trying to set up a truly current "stable" Sabayon to migrate to. And I needed to spend most of my computer time trying to get a new home based business off the ground, before it bankrupts me. (I had wanted to work from an up to date Sabayon that I hadn't messed up trying to figure out emerge. This one was going to mostly use equo and whatever default settings it liked to use.)... And when I removed the ati driver that was blocking the r128 driver and then installed the r128 driver & rebooted I got for the first time since the [equo world] the gui kdm login screen. But I was too tired to do anything with it and shut down. When I got up I booted my old loop2 installation (which has all my user stuff set up, to spend some time on the business and to tell the nice people in the forum who had been helping me that replacing the driver worked...

It wasn't until I needed to work on my gnucash data that I discovered that it was no longer working and reinstall was blocked/masked by something that some update or other had changed since I installed it the first time.(different thread) that I decided I needed to migrate my user files to the new theoretically working [updated] Sabayon 3.5 stable installation that I actually tried to login to the initial user account to open a root shell from which to set up my normal user accounts with the same normal user id numbers and set up my personal data partitions to mount where only my user account can get at them, that I discovered that when I try to log in via the kdm gui screen, I briefly get the rotating mouse pointer and gray screen background that I'd expect when it's logging in a user to a kde session, but before the process completes, the screen is replaced once more by the kdm login screen.

I think this means the kde process crashes and then kdm respawns, but I'm not sure... I'm not used to this kind of problem. Never had it before with Sabayon, which is the ONLY distro I let boot from kdm instead of booting to runlevel 3, and using startx where if x crashed I'd be back at a console user prompt {with some potentialy useful error messages sitting on the console screen if by chance I see something I understand when I scroll up its buffer with <shift>+<page up>} instead... (I'd probably do that with Sabayon but when I tried {probably when I was first playing with 3.4F} booting with nox and then using startx (which I lack the skill to tweak) I didn't get kde, and have no knowledge or desire to use whatever that gui it did boot. (I selected kde a long time ago, and unless kde4 chases me away, I won't willingly be using any other desktop.)

Bottom line is there is still something wrong with the gui that fixing the video driver didn't fix...

It does occur to me that it was pure chance that during the 20 hour process of the [equo world] (2nd time around) I happened to be at my desk when the PC beeped and the text about the r128 support being moved to it's own driver slowly scrolled off the screen... But I have no way of knowing if there was some other similar message about some other critical driver or library update info that may also have been flagged with a beep while I wasn't sitting there for the whole 20 hours to notice it...

I'm thinking that when I can spare the time from working on my business again, (might take a month) I could try another reinstall from the dvd. Then do something like:

equo world | tee ~/equo-world_out.txt

to get a file that hopefully will contain any such priority messages that I might even find, if I slowly page through the whole file...

But I can't remember how to make sure that tee catches any stderr as well as stdout.

A clue would be appreciated...

Though in any case, I can't spend any more time on it right now. I'm going to have to do my day to day business stuff with the old Sabayon except that when I need gnucash, I'm going to have to reboot into either kubuntu or openSuSE... (that fscking bugs me but I can't spend the time to try to figure out how to get around the masked to only MAYBE get gnucask running again...)

Then when I get caught up. I'll return to this issue... Cause I really do prefer to work in the nice environment I've come to expect from Sabayon... So I'm sure that I will do my best to make the time to try this one more time... {in about a month, which hopefully won't be so long that the portage tree (or whatever equo uses) changes so much that the equo world has to many dependency issues to succeed in actually bringing a fresh 3.5 stable install up to date...}

In any case, thanks for all the kind help. I will be back!

--
joe3