Skip to main content

Thread: boot sequence stuck on unreadably distorted X dialog, but I don't want X


out of seemingly nowhere, after did apt-get update && apt-get upgrade, boot sequence no longer finishes. gets stuck on believe x-based gui dialog (not curses-based), screen unreadably distorted (as if each horizontal row of pixels has been shifted different amount).

first of all, nothing x-based should happen @ all. hate gui-based login, splash screens, starting x when don't have to, etc. (and here's reason why). therefore, unstalled gdm (don't know why turning service off didn't acomplish anything, in jaunty), , use nosplash boot option. login @ console... i'm used calling runlevel 3 in other distros.

so, might able stop reading here , answer this: possibly giving me x-based gui when normal boot sequence doesn't involve x @ all?

when hold power button reset, displays correctly split-second before system resets. looks dialog single ok. hitting enter (on separate try, while it's messed up) apparently brings dialog. no matter hit there (enter, tab, up-down, enter again, etc.) nothing happens, , i've yet catch split-second glimpse of 1 looks like. can hit ctrl-alt-f* other virtual consoles, they're blank.

furthermore, can boot single-user mode, run init 3, , login , startx usual. works fine. why single-user mode , init 3 not equivalent normal boot sequence?!

i've checked /var/log/messages , don't see out of ordinary. if fact, boot sequence looks done before runs problem; essential , running. see drops in /var/log/xorg.failsafe.log file:

here errors:
code:
root@coronet:/var/log# cat xorg.failsafe.log | grep ee         (ww) warning, (ee) error, (ni) not implemented, (??) unknown. (ii) loading extension mit-screen-saver (ee) config/hal: couldn't initialise context: unknown error (null)
i don't hal, other service running. maybe x needs hasn't started here yet?

here warnings:
code:
root@coronet:/var/log# cat xorg.failsafe.log | grep ww         (ww) warning, (ee) error, (ni) not implemented, (??) unknown. (ww) directory "/usr/share/fonts/x11/cyrillic" not exist. (ww) open acpi failed (/var/run/acpid.socket) (no such file or directory) (ww) vesa(0): unable estimate virtual size (ww) vesa(0): no valid modes left. trying less strict filter... (ww) vesa(0): unable estimate virtual size (ww) vesa(0): no valid modes left. trying aggressive sync range... (ww) vesa(0): unable estimate virtual size
well, certianly sounds problem, doesn't help. again, x works fine when start myself startx do. i'm not looking solve these x errors, fix whatever in boot sequence that's attempting start x in first place.

i'm running latest karmic. booting normal environment using single-user, init 3 route, i've done apt-get update && apt-get upgrade && apt-get dist-upgrade. nothing changed. on asus eee pc 1005ha.

appreciated.

in advance.

when it's stuck on scrambed dialog, , switch different virtual console, blank, can login. nothing ever appears on screen, can type out ps axjf > ps.out , go read later booting single-user. , here's offender:

code:
/bin/bash /etc/gdm/failsafexserver  \_ xinit /etc/gdm/failsafexinit /etc/x11/xorg.conf.failsafe -- /usr/bin/x -br -once -config /etc/x11/xorg.conf.failsafe -logfile /var/log/xorg.failsafe.log      \_ /usr/bin/x :0 -br -once -config /etc/x11/xorg.conf.failsafe -logfile /var/log/xorg.failsafe.log      \_ /bin/bash /etc/gdm/failsafexinit /etc/x11/xorg.conf.failsafe          \_ zenity --warning --text <big><b>ubuntu running in low-graphics mode</b></big>\n\nthe following error encountered.  may need\nto update configuration solve this.\n\n(ee) failed load module "i810" (module not exist, 0)
so module i810 secondary problem here (the primary problem being why failsafexserver starting in first place). see error in everyday xorg.0.log, when works fine:

code:
(ii) loadmodule: "i810" (ww) warning, couldn't open module i810 (ii) unloadmodule: "i810" (ee) failed load module "i810" (module not exist, 0)
that's because loads intel before that, , apparently fine using it:

code:
(ii) loadmodule: "intel" (ii) loading /usr/lib/xorg/modules/drivers//intel_drv.so
(the hardware is: intel corporation mobile 945gm/gms/gme, 943/940gml express integrated graphics controller (rev 03))

must admit, don't know failsafex is, apparently it's not failsafe plain old x

, why there /etc/gdm when uninstalled gdm? hmmm, see it's owned x11-common package. anyways, gdm uninstalled:

code:
root@coronet:~# dpkg -l | grep gdm root@coronet:~# service gdm status gdm: unrecognized service
i don't want sidetracked specific i810 issue, can tell nothing in x config names driver:

code:
root@coronet:/etc/x11# find . -type f | xargs grep i810 root@coronet:/etc/x11#
but there's no xorg.conf i'm used (new bulletproof x, guess, imho more of pita before). there's xorg.conf.failsafe, specified driver "vesa".

of course, maybe it's trying start x prompt me other problem never gets expressed, fixing worth shot.

but, again, if knows how behavior non-x login environment, way working until today, wouldn't have think driver issue.



Forum The Ubuntu Forum Community Ubuntu Official Flavours Support General Help [ubuntu] boot sequence stuck on unreadably distorted X dialog, but I don't want X


Ubuntu

Comments

Popular posts from this blog

Error: ‘for’ loop initial declarations are only allowed in C99 or C11 mode - Raspberry Pi Forums

class MPU6050 has no member named begin

missing filename after '-o'