Author Topic: (SOLVED) Xorg crash and burn in VirtualBox  (Read 10288 times)

VastOne

  •      v-ger
  • Posts: 4166
    • View Profile
    • VSIDO Community
(SOLVED) Xorg crash and burn in VirtualBox
« on: May 11, 2015, 03:47:49 AM »
@vastone- you trying to log into fluxbox or cwm.

On my recent updates, something is broken.in lightdm. I don't get the host name or clock in the lightdm bar. Everything else is there and I can log in.

Your fatal.errors look to be related to Xorg- which just went through a major upgrade.

Do you have xinit installed? You can try disabling lightdm service and see if you can log in with startx.

Not so trivial for me and the V-Box build environment I use for VSIDO

I did a normal update for the x32 build environment and I can no longer boot to the machine.

Here is the complete xsession-errors

systemctl status shows lightdm as the only failure... I get right to the point of lightdm environment to begin and I am stalled at a blinking cursor... /var/logs is not showing me anything and swapping out all of the lightdm conf files have led to nothing as well..

I loaded xdm and never saw X start either so it is confusing (read FRUSTRATING) that it is not obvious as to whter or not it is even a lightdm issue (as opposed to Xorg) ...

I have been at it all day and am tired so any and all feedback and guidance will be rewarded
VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO

VastOne

  •      v-ger
  • Posts: 4166
    • View Profile
    • VSIDO Community
Re: Xorg crash and burn in VirtualBox
« Reply #1 on: May 11, 2015, 02:45:20 PM »
@RatMan...

FluxBox only, always, ever... no time anymore to mess with others   :-[

It is Xorg broken, specifically the removal of v-box mods or kernel or X packages.  I am retracing it all now and will find what is gone or missing

VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO

VastOne

  •      v-ger
  • Posts: 4166
    • View Profile
    • VSIDO Community
Re: Xorg crash and burn in VirtualBox
« Reply #2 on: May 11, 2015, 09:36:20 PM »
Also... xinit/startx shows Fatal Server Error (EE) no screens found (EE) and I am not sure it is missing packages from a xserver update

I updated the x64 that did not remove anything and have the same issue

X is just broken in virtualbox right now
VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO

VastOne

  •      v-ger
  • Posts: 4166
    • View Profile
    • VSIDO Community
Re: Xorg crash and burn in VirtualBox
« Reply #3 on: May 12, 2015, 01:56:43 AM »
The missing component is xserver-xorg-video-modesetting which depends on xorg-video-abi-19 which is a Virtual Package NOW missing from xserver-xorg-core

Once this is resolved I should be able to build again

DAFUQ you doing to us all debian?
VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO

VastOne

  •      v-ger
  • Posts: 4166
    • View Profile
    • VSIDO Community
Re: Xorg crash and burn in VirtualBox
« Reply #4 on: May 13, 2015, 01:54:25 AM »
Posting this in hopes of some kind of assist... I am tired of trying and getting massive headaches trying to figure this one out

Results of

Code: [Select]
sudo grep systemd /var/log/syslog
Code: [Select]
May 12 12:36:33 vsido systemd-modules-load[159]: Inserted module 'fuse'
May 12 12:36:33 vsido systemd-modules-load[159]: Failed to find module 'overlay'
May 12 12:36:33 vsido kernel: [    1.237509] random: systemd-udevd urandom read with 0 bits of entropy available
May 12 12:36:34 vsido systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
May 12 12:36:34 vsido systemd[1]: Unit lightdm.service entered failed state.
May 12 12:36:34 vsido systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
May 12 12:36:34 vsido systemd[1]: Unit lightdm.service entered failed state.
May 12 12:36:34 vsido systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
May 12 12:36:34 vsido systemd[1]: Unit lightdm.service entered failed state.
May 12 12:36:34 vsido systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
May 12 12:36:34 vsido systemd[1]: Unit lightdm.service entered failed state.
May 12 12:36:35 vsido systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
May 12 12:36:35 vsido systemd[1]: Unit lightdm.service entered failed state.
May 12 12:36:35 vsido systemd[1]: lightdm.service start request repeated too quickly, refusing to start.
May 12 12:36:35 vsido systemd[1]: Failed to start Light Display Manager.
May 12 12:36:35 vsido systemd[1]: Unit lightdm.service entered failed state.
May 12 12:38:17 vsido systemd[1067]: Starting Paths.
May 12 12:38:17 vsido systemd[1067]: Reached target Paths.
May 12 12:38:17 vsido systemd[1067]: Starting Timers.
May 12 12:38:17 vsido systemd[1067]: Reached target Timers.
May 12 12:38:17 vsido systemd[1067]: Starting Sockets.
May 12 12:38:17 vsido systemd[1067]: Reached target Sockets.
May 12 12:38:17 vsido systemd[1067]: Starting Basic System.
May 12 12:38:17 vsido systemd[1067]: Reached target Basic System.
May 12 12:38:17 vsido systemd[1067]: Starting Default.
May 12 12:38:17 vsido systemd[1067]: Reached target Default.
May 12 12:38:17 vsido systemd[1067]: Startup finished in 17ms.
May 12 12:38:17 vsido dbus[632]: [system] Activating via systemd: service name='org.freedesktop.ConsoleKit' unit='console-kit-daemon.service'
May 12 12:38:18 vsido dbus[632]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkitd.service'
May 12 13:19:54 vsido systemd-modules-load[160]: Inserted module 'fuse'
May 12 13:19:54 vsido systemd-modules-load[160]: Failed to find module 'overlay'
May 12 13:19:54 vsido systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE
May 12 13:19:54 vsido systemd[1]: Failed to start Load Kernel Modules.
May 12 13:19:54 vsido systemd[1]: Unit systemd-modules-load.service entered failed state.
May 12 13:19:54 vsido kernel: [    1.218020] random: systemd-udevd urandom read with 0 bits of entropy available
May 12 13:19:54 vsido dbus[597]: [system] Successfully activated service 'org.freedesktop.systemd1'
May 12 13:19:56 vsido systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
May 12 13:19:56 vsido systemd[1]: Unit lightdm.service entered failed state.
May 12 13:19:57 vsido systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
May 12 13:19:57 vsido systemd[1]: Unit lightdm.service entered failed state.
May 12 13:19:57 vsido systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
May 12 13:19:57 vsido systemd[1]: Unit lightdm.service entered failed state.
May 12 13:19:57 vsido systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
May 12 13:19:57 vsido systemd[1]: Unit lightdm.service entered failed state.
May 12 13:19:57 vsido systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
May 12 13:19:57 vsido systemd[1]: Unit lightdm.service entered failed state.
May 12 13:19:58 vsido systemd[1]: lightdm.service start request repeated too quickly, refusing to start.
May 12 13:19:58 vsido systemd[1]: Failed to start Light Display Manager.
May 12 13:19:58 vsido systemd[1]: Unit lightdm.service entered failed state.
May 12 15:57:35 vsido systemd-modules-load[159]: Inserted module 'fuse'
May 12 15:57:35 vsido systemd-modules-load[159]: Failed to find module 'overlay'
May 12 15:57:35 vsido systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE
May 12 15:57:35 vsido systemd[1]: Failed to start Load Kernel Modules.
May 12 15:57:35 vsido systemd[1]: Unit systemd-modules-load.service entered failed state.
May 12 15:57:35 vsido kernel: [    1.200320] random: systemd-udevd urandom read with 0 bits of entropy available
May 12 15:57:35 vsido systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
May 12 15:57:35 vsido systemd[1]: Unit lightdm.service entered failed state.
May 12 15:57:36 vsido systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
May 12 15:57:36 vsido systemd[1]: Unit lightdm.service entered failed state.
May 12 15:57:36 vsido systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
May 12 15:57:36 vsido systemd[1]: Unit lightdm.service entered failed state.
May 12 15:57:36 vsido systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
May 12 15:57:36 vsido systemd[1]: Unit lightdm.service entered failed state.
May 12 15:57:37 vsido systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
May 12 15:57:37 vsido systemd[1]: Unit lightdm.service entered failed state.
May 12 15:57:37 vsido systemd[1]: lightdm.service start request repeated too quickly, refusing to start.
May 12 15:57:37 vsido systemd[1]: Failed to start Light Display Manager.
May 12 15:57:37 vsido systemd[1]: Unit lightdm.service entered failed state.
May 12 15:57:52 vsido systemd[1047]: Starting Paths.
May 12 15:57:52 vsido systemd[1047]: Reached target Paths.
May 12 15:57:52 vsido systemd[1047]: Starting Timers.
May 12 15:57:52 vsido systemd[1047]: Reached target Timers.
May 12 15:57:52 vsido systemd[1047]: Starting Sockets.
May 12 15:57:52 vsido systemd[1047]: Reached target Sockets.
May 12 15:57:52 vsido systemd[1047]: Starting Basic System.
May 12 15:57:52 vsido systemd[1047]: Reached target Basic System.
May 12 15:57:52 vsido systemd[1047]: Starting Default.
May 12 15:57:52 vsido systemd[1047]: Reached target Default.
May 12 15:57:52 vsido systemd[1047]: Startup finished in 71ms.
May 12 15:57:52 vsido dbus[599]: [system] Activating via systemd: service name='org.freedesktop.ConsoleKit' unit='console-kit-daemon.service'
May 12 15:57:52 vsido dbus[599]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkitd.service'
May 12 16:29:32 vsido 40grub2: debug: parsing: menuentry 'VSIDO Jedi x32 GNU/Linux, with Linux 3.16.0-4-686-pae (systemd) (on /dev/sdc1)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-3.16.0-4-686-pae--73f9c70a-e99a-4802-9e58-7ac8fe0ef467' {
May 12 16:29:32 vsido 40grub2: Skipping entry 'VSIDO Jedi x32 GNU/Linux, with Linux 3.16.0-4-686-pae (systemd) (on /dev/sdc1)':
May 12 16:29:32 vsido 40grub2: debug: parsing: linux /boot/vmlinuz-3.16.0-4-686-pae root=UUID=73f9c70a-e99a-4802-9e58-7ac8fe0ef467 ro quiet init=/lib/systemd/systemd
May 12 16:29:32 vsido 40grub2: debug: parsing: menuentry 'VSIDO Jedi x64 GNU/Linux, with Linux 3.16.0-4-amd64 (systemd) (on /dev/sdd1)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-3.16.0-4-amd64--b80d39ca-f238-442f-8462-412b94ae2fb7' {
May 12 16:29:32 vsido 40grub2: Skipping entry 'VSIDO Jedi x64 GNU/Linux, with Linux 3.16.0-4-amd64 (systemd) (on /dev/sdd1)':
May 12 16:29:32 vsido 40grub2: debug: parsing: linux /boot/vmlinuz-3.16.0-4-amd64 root=UUID=b80d39ca-f238-442f-8462-412b94ae2fb7 ro quiet init=/lib/systemd/systemd
May 12 16:29:33 vsido 40grub2: debug: parsing: menuentry 'VSIDO Jedi x64 GNU/Linux, with Linux 3.16.0-4-amd64 (systemd)' --class vsido --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.16.0-4-amd64-init-systemd-b80d39ca-f238-442f-8462-412b94ae2fb7' {
May 12 16:29:34 vsido 40grub2: debug: parsing: linux#011/boot/vmlinuz-3.16.0-4-amd64 root=UUID=b80d39ca-f238-442f-8462-412b94ae2fb7 ro  quiet init=/lib/systemd/systemd
May 12 16:29:34 vsido 40grub2: result: /dev/sdd1:/dev/sdd1:VSIDO Jedi x64 GNU/Linux, with Linux 3.16.0-4-amd64 (systemd):/boot/vmlinuz-3.16.0-4-amd64:/boot/initrd.img-3.16.0-4-amd64:root=UUID=b80d39ca-f238-442f-8462-412b94ae2fb7 ro quiet init=/lib/systemd/systemd
May 12 16:29:34 vsido 40grub2: debug: parsing: menuentry 'VSIDO Jedi x32 GNU/Linux, with Linux 3.16.0-4-686-pae (systemd) (on /dev/sdc1)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-3.16.0-4-686-pae--73f9c70a-e99a-4802-9e58-7ac8fe0ef467' {
May 12 16:29:34 vsido 40grub2: Skipping entry 'VSIDO Jedi x32 GNU/Linux, with Linux 3.16.0-4-686-pae (systemd) (on /dev/sdc1)':
May 12 16:29:34 vsido 40grub2: debug: parsing: linux /boot/vmlinuz-3.16.0-4-686-pae root=UUID=73f9c70a-e99a-4802-9e58-7ac8fe0ef467 ro quiet init=/lib/systemd/systemd
May 12 16:31:49 vsido systemd-modules-load[162]: Inserted module 'fuse'
May 12 16:31:49 vsido kernel: [    1.247649] random: systemd-udevd urandom read with 0 bits of entropy available
May 12 16:31:49 vsido dbus[606]: [system] Successfully activated service 'org.freedesktop.systemd1'
May 12 16:31:49 vsido systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
May 12 16:31:49 vsido systemd[1]: Unit lightdm.service entered failed state.
May 12 16:31:50 vsido systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
May 12 16:31:50 vsido systemd[1]: Unit lightdm.service entered failed state.
May 12 16:31:50 vsido systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
May 12 16:31:50 vsido systemd[1]: Unit lightdm.service entered failed state.
May 12 16:31:51 vsido systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
May 12 16:31:51 vsido systemd[1]: Unit lightdm.service entered failed state.
May 12 16:31:51 vsido systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
May 12 16:31:51 vsido systemd[1]: Unit lightdm.service entered failed state.
May 12 16:31:51 vsido systemd[1]: lightdm.service start request repeated too quickly, refusing to start.
May 12 16:31:51 vsido systemd[1]: Failed to start Light Display Manager.
May 12 16:31:51 vsido systemd[1]: Unit lightdm.service entered failed state.
May 12 16:32:09 vsido systemd[1059]: Starting Paths.
May 12 16:32:09 vsido systemd[1059]: Reached target Paths.
May 12 16:32:09 vsido systemd[1059]: Starting Timers.
May 12 16:32:09 vsido systemd[1059]: Reached target Timers.
May 12 16:32:09 vsido systemd[1059]: Starting Sockets.
May 12 16:32:09 vsido systemd[1059]: Reached target Sockets.
May 12 16:32:09 vsido systemd[1059]: Starting Basic System.
May 12 16:32:09 vsido systemd[1059]: Reached target Basic System.
May 12 16:32:09 vsido systemd[1059]: Starting Default.
May 12 16:32:09 vsido systemd[1059]: Reached target Default.
May 12 16:32:09 vsido systemd[1059]: Startup finished in 10ms.
May 12 16:32:09 vsido dbus[606]: [system] Activating via systemd: service name='org.freedesktop.ConsoleKit' unit='console-kit-daemon.service'
May 12 16:32:09 vsido dbus[606]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkitd.service'
May 12 20:23:05 vsido systemd-modules-load[161]: Inserted module 'fuse'
May 12 20:23:05 vsido kernel: [    1.265023] random: systemd-udevd urandom read with 0 bits of entropy available
May 12 20:23:05 vsido dbus[605]: [system] Successfully activated service 'org.freedesktop.systemd1'
May 12 20:23:05 vsido systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
May 12 20:23:05 vsido systemd[1]: Unit lightdm.service entered failed state.
May 12 20:23:06 vsido systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
May 12 20:23:06 vsido systemd[1]: Unit lightdm.service entered failed state.
May 12 20:23:06 vsido systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
May 12 20:23:06 vsido systemd[1]: Unit lightdm.service entered failed state.
May 12 20:23:06 vsido systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
May 12 20:23:06 vsido systemd[1]: Unit lightdm.service entered failed state.
May 12 20:23:07 vsido systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
May 12 20:23:07 vsido systemd[1]: Unit lightdm.service entered failed state.
May 12 20:23:07 vsido systemd[1]: lightdm.service start request repeated too quickly, refusing to start.
May 12 20:23:07 vsido systemd[1]: Failed to start Light Display Manager.
May 12 20:23:07 vsido systemd[1]: Unit lightdm.service entered failed state.
May 12 20:23:19 vsido systemd[1054]: Starting Paths.
May 12 20:23:19 vsido systemd[1054]: Reached target Paths.
May 12 20:23:19 vsido systemd[1054]: Starting Timers.
May 12 20:23:19 vsido systemd[1054]: Reached target Timers.
May 12 20:23:19 vsido systemd[1054]: Starting Sockets.
May 12 20:23:19 vsido systemd[1054]: Reached target Sockets.
May 12 20:23:19 vsido systemd[1054]: Starting Basic System.
May 12 20:23:19 vsido systemd[1054]: Reached target Basic System.
May 12 20:23:19 vsido systemd[1054]: Starting Default.
May 12 20:23:19 vsido systemd[1054]: Reached target Default.
May 12 20:23:19 vsido systemd[1054]: Startup finished in 11ms.
May 12 20:23:19 vsido dbus[605]: [system] Activating via systemd: service name='org.freedesktop.ConsoleKit' unit='console-kit-daemon.service'
May 12 20:23:19 vsido dbus[605]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkitd.service'
VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO

ozitraveller

  • Posts: 385
    • View Profile
    • Star
Re: Xorg crash and burn in VirtualBox
« Reply #5 on: May 13, 2015, 03:32:22 AM »
@VastOne - sorry to hear about your problems. Is there are useful information in /var/log/lightdm/lightdm.log ? Ozi

jedi

  • DEFCON 1
  • Posts: 1618
  • Not all those who wander are lost.
    • View Profile
    • NixNut.com
Re: Xorg crash and burn in VirtualBox
« Reply #6 on: May 13, 2015, 05:59:24 AM »
This might have something to do with the removal of;
Code: [Select]
xserver-xorg-video-modesettingduring the latest updates over the last few days...

Can it be apt-pinned to keep it for the time being, or would that not work at all?  Total guess work here on my part...
Forum Netiquette

"No matter how smart you are you can never convince someone stupid that they are stupid."  Anonymous

PackRat

  • Posts: 2163
    • View Profile
    • PackRat configs on github
Re: Xorg crash and burn in VirtualBox
« Reply #7 on: May 13, 2015, 01:26:06 PM »
@vastone -

what is the output of:

Code: [Select]
systemctl --state=failed
and what is module overlay related to; looks like fuse is causing some issues.

Also, the recent xorg update mayhem was removing a bunch of files - mostly video drivers. This is all in vm correct? Do you need/have the drivers for your vmware  installed:

these drivers -

xserver-xorg-video-vmware
xserver-xorg-video-nouveau
xserver-xorg-video-fbdev
xserver-xorg-video-vesa

were all candidates for un-installation - amongst others. Maybe you had one slip through the cracks.
I am tired of talk that comes to nothing.
-- Chief Joseph

...the sun, the darkness, the winds are all listening to what we have to say.
-- Geronimo

VastOne

  •      v-ger
  • Posts: 4166
    • View Profile
    • VSIDO Community
Re: Xorg crash and burn in VirtualBox
« Reply #8 on: May 13, 2015, 04:15:55 PM »
@VastOne - sorry to hear about your problems. Is there are useful information in /var/log/lightdm/lightdm.log ? Ozi

Thanks Ozi

Attached are the

lightdm.log
x-0.log (from /var/log/lightdm)
Xorg.0.log
VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO

VastOne

  •      v-ger
  • Posts: 4166
    • View Profile
    • VSIDO Community
Re: Xorg crash and burn in VirtualBox
« Reply #9 on: May 13, 2015, 04:33:02 PM »
@vastone -

what is the output of:

Code: [Select]
systemctl --state=failed
and what is module overlay related to; looks like fuse is causing some issues.

Also, the recent xorg update mayhem was removing a bunch of files - mostly video drivers. This is all in vm correct? Do you need/have the drivers for your vmware  installed:

these drivers -

xserver-xorg-video-vmware
xserver-xorg-video-nouveau
xserver-xorg-video-fbdev
xserver-xorg-video-vesa

were all candidates for un-installation - amongst others. Maybe you had one slip through the cracks.

RatMan...

Output of systemctl --state=failed

Code: [Select]
  UNIT            LOAD   ACTIVE SUB    DESCRIPTION
● lightdm.service loaded failed failed Light Display Manager

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.

1 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

If I completely remove lightdm and go with another (mdm) it fails also... It is an X issue is seems even though it is not reporting that way from systemctl

These were all that were updated and/or not included in the original Xorg updates that has been checked and restored

Code: [Select]

xserver-common xserver-xorg
  xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
  xserver-xorg-input-synaptics xserver-xorg-input-vmmouse
  xserver-xorg-video-all xserver-xorg-video-ati xserver-xorg-video-cirrus
  xserver-xorg-video-fbdev xserver-xorg-video-intel xserver-xorg-video-mach64
  xserver-xorg-video-mga xserver-xorg-video-neomagic
  xserver-xorg-video-nouveau xserver-xorg-video-openchrome
  xserver-xorg-video-qxl xserver-xorg-video-r128 xserver-xorg-video-radeon
  xserver-xorg-video-savage xserver-xorg-video-siliconmotion
  xserver-xorg-video-sisusb xserver-xorg-video-tdfx xserver-xorg-video-trident
  xserver-xorg-video-vesa xserver-xorg-video-vmware
VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO

PackRat

  • Posts: 2163
    • View Profile
    • PackRat configs on github
Re: Xorg crash and burn in VirtualBox
« Reply #10 on: May 13, 2015, 05:03:05 PM »
@vastone -

search this error which is in your logs -

Code: [Select]
(EE) no screens found(EE)
There are some links for this occurring in ubuntu, centos, and arch after an xorg upgrade. Looks like a couple in VM's. Solution usually involves re-installing the video driver, or reconfiguring xorg.conf
I am tired of talk that comes to nothing.
-- Chief Joseph

...the sun, the darkness, the winds are all listening to what we have to say.
-- Geronimo

VastOne

  •      v-ger
  • Posts: 4166
    • View Profile
    • VSIDO Community
Re: Xorg crash and burn in VirtualBox
« Reply #11 on: May 13, 2015, 05:10:41 PM »
RatMan, I have seen and tried them all .. or at least all except the one that corrects this issue

It seems to have several layers... I am tempted to load the latest Beta 5 of V-Box

Another solution I have is to shitcan the V-Box build environment and install the fsa's of March backups on metal and go forward from there

Ultimately I will get new ISO's with the 4.0 kernel out
VSIDO      VSIDO Twitter     VSIDO FB     VSIDO Google+   

I dev VSIDO

jedi

  • DEFCON 1
  • Posts: 1618
  • Not all those who wander are lost.
    • View Profile
    • NixNut.com
Re: Xorg crash and burn in VirtualBox
« Reply #12 on: May 13, 2015, 07:06:58 PM »
Another solution I have is to shitcan the V-Box build environment and install the fsa's of March backups on metal and go forward from there
Ultimately I will get new ISO's with the 4.0 kernel out

fsa's = FSARCHIVER! = solution!  Bet you get it solved in less than 24 hours!!!  I trust everything to fsa's.  Your suggestion to use fsarchiver a few years back has always stuck with me!  (and never failed once!)
Forum Netiquette

"No matter how smart you are you can never convince someone stupid that they are stupid."  Anonymous

ozitraveller

  • Posts: 385
    • View Profile
    • Star
Re: Xorg crash and burn in VirtualBox
« Reply #13 on: May 13, 2015, 09:01:37 PM »
@vastone - this looks like the point of failure

Code: [Select]
[    10.443] (EE) VESA(0): Cannot read int vect
Which I think is in : xserver-xorg-video-all

Code: [Select]
[    10.443] (II) Module int10: vendor="X.Org Foundation"
[    10.443] compiled for 1.17.1, module version = 1.0.0
[    10.443] ABI class: X.Org Video Driver, version 19.0
[    10.443] (II) VESA(0): initializing int10
[    10.443] (EE) VESA(0): Cannot read int vect
[    10.443] (II) UnloadModule: "vesa"
[    10.443] (II) UnloadSubModule: "int10"
[    10.443] (II) Unloading int10
[    10.443] (II) UnloadSubModule: "vbe"
[    10.443] (II) Unloading vbe
[    10.443] (EE) Screen(s) found, but none have a usable configuration.
[    10.444] (EE)
Fatal server error:
[    10.444] (EE) no screens found(EE)
[    10.444] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
 for help.
[    10.444] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    10.444] (EE)
[    10.448] (EE) Server terminated with error (1). Closing log file.

ozitraveller

  • Posts: 385
    • View Profile
    • Star
Re: Xorg crash and burn in VirtualBox
« Reply #14 on: May 13, 2015, 09:04:53 PM »
RatMan, I have seen and tried them all .. or at least all except the one that corrects this issue

It seems to have several layers... I am tempted to load the latest Beta 5 of V-Box

Another solution I have is to shitcan the V-Box build environment and install the fsa's of March backups on metal and go forward from there

Ultimately I will get new ISO's with the 4.0 kernel out

I would agree with this as well.

I'm using VB as my build enviroment. Currently no problems. But I'm building with jessie. Build on metal if that's possible.