to, 2012-04-05 kello 07:41 -0500, Joshua Poehls kirjoitti:
> I started installing Arch in VirtualBox this morning but twice now the
> screen goes black at some point during (or right after) the package
> download step and never comes back.
Well Linux in general has a "powersaving" or "screensaving" feature
don't know the exact meaning/use of it, but anyway in console, if you
don't touch the keyboard for a while the screen will blank itself.
Pressing any key will wake it up again. Don't know if this is the thing
you are experiencing...

Doh. I think that was it. Thank you...

--
Joshua Poehls



On Thu, Apr 5, 2012 at 7:45 AM, Jesse Juhani Jaara <jesse.jaara@gmail.com>wrote:

> to, 2012-04-05 kello 07:41 -0500, Joshua Poehls kirjoitti:
> > I started installing Arch in VirtualBox this morning but twice now the
> > screen goes black at some point during (or right after) the package
> > download step and never comes back.
> Well Linux in general has a "powersaving" or "screensaving" feature
> don't know the exact meaning/use of it, but anyway in console, if you
> don't touch the keyboard for a while the screen will blank itself.
> Pressing any key will wake it up again. Don't know if this is the thing
> you are experiencing...
>

On Wed, 2012-05-02 at 00:38 +0800, 郑文辉(Techlive Zheng) wrote:
> 2012/4/5 Joshua Poehls <joshua@zduck.com>:
> > Doh. I think that was it. Thank you...
> >
> > --
> > Joshua Poehls
> >
> >
> >
> > On Thu, Apr 5, 2012 at 7:45 AM, Jesse Juhani Jaara <jesse.jaara@gmail.com>wrote:
> >
> >> to, 2012-04-05 kello 07:41 -0500, Joshua Poehls kirjoitti:
> >> > I started installing Arch in VirtualBox this morning but twice now the
> >> > screen goes black at some point during (or right after) the package
> >> > download step and never comes back.
> >> Well Linux in general has a "powersaving" or "screensaving" feature
> >> don't know the exact meaning/use of it, but anyway in console, if you
> >> don't touch the keyboard for a while the screen will blank itself.
> >> Pressing any key will wake it up again. Don't know if this is the thing
> >> you are experiencing...
> >>
> I have similar problmes here. After upgrade to the newest linux
> kernel, the virtualbox became unresponsed, and output a screen of
> dignostic informations.
>
> Anyone knows what happend?

I neither read the complete thread nor do I know what to do, but I
remember that there was an issue regarding to an upgrade of X, when
using Arch in VBox. Perhaps there's a solution or at least an
explanation somewhere in the mailing list archive end 2011 or during
2012. Windoof still is fine in my VBox running on Arch ;D.

- Ralf

> I do not have an X installed on my vbox.

Pardon for my noise. I'm that accustomed to other distros, that I forgot
that a default Arch install fortunately comes without X.

On what OS VBox is running? Do you run VBox on Arch to install Arch on
VBox? Perhaps this information is relevant.

- Ralf

On Wed, 2012-05-02 at 01:19 +0800, 郑文辉(Techlive Zheng) wrote:
> 2012/5/2 Ralf Mardorf <ralf.mardorf@alice-dsl.net>:
> >> I do not have an X installed on my vbox.
> >
> > Pardon for my noise. I'm that accustomed to other distros, that I forgot
> > that a default Arch install fortunately comes without X.
> >
> > On what OS VBox is running? Do you run VBox on Arch to install Arch on
> > VBox? Perhaps this information is relevant.
> >
> > - Ralf
> >
>
> Both host and guest environments are Arch Linux.
>
> I used vbox as a development enviroment.

I'm quiet now, since I don't have knowledge, I only remembered that
there was an issue regarding to X.

Since Arch is a relaxation compared to other Linux distros, regarding to
some problems, I hope every developer will be able to run Arch on VBox
on Arch .

Good luck!
Ralf

On Wed, May 02, 2012 at 01:00:29AM +0800, 郑文辉(Techlive Zheng) wrote:
> [2012-05-01 22:08] upgraded virtualbox-archlinux-modules (4.1.10-1 -> 4.1.14-2)
> [2012-05-01 22:08] upgraded virtualbox-archlinux-additions (4.1.10-1
> -> 4.1.14-2)

This usually means vbox won't launch for me. I think I was lucky vbox didn't
crash on me (or didn't care enough), but the kernel modules vbox uses and which
I compile w/ # /usr/bin/vboxbuild need to be recompiled at that point.
The modules I use are vboxdrv and vboxnetflt, there might be one more or so.

also important when we're supposed to help you would be if you posted your
error messages by pastebin or screenshot or whatever, actual screen photo.

cheers!
mar77i