Re: New install - boot, 'startx', freeze.

On Thu, Mar 26, 2015 at 11:22 PM, Mark Filipak <[email protected]>
wrote:

> On 03/26/2015 09:50 PM, Lucas C. Villa Real wrote:
> > On Thu, Mar 26, 2015 at 3:56 AM, Mark Filipak
> -big snip-
> >     When I entered 'startx', I got the same gray screen with mouse
> cursor in
> >     the center, non-working, and no keyboard action.
> >
> >
> > Sorry, no idea here. Gobo is known to work fine on QEMU, which was the
> > platform used during the development and release cycle of 015. I'd
> > suggest you to try it with QEMU. If that is not an option, you can send
> > me the contents of /Data/Variable/log/Xorg.0.log and we can keep trying
> > to debug your problem.
> >
> > Lucas
>
> I don't mind devoting my time and attention to this. I don't mind being
> as generous as you obviously are.   *<|;~]
>
> But I really can't live with Enlightenment, not in a system I use. I've
> dated some really beautiful women, but I never married them.
> Enlightenment reminds me of a fashion show. It's fun to look at what
> comes down the catwalk, but I wouldn't want to live day-to-day with any
> of them.
>

Ha! That makes sense ;-)


> Looking at the 'xorg.conf' that you proposed, I'm struck that it's all
> graphics driver switches. Do you really think that's the problem? I have
> no experience with Gobo/Enlightenment, so I don't know how to run it
> without a mouse. The display isn't blank. It's just a gray background
> and an unmovable mouse cursor, but it's not blank. I don't see how the
> display could be the problem. Also, the keyboard doesn't appear to work.
> Can Gobo be run via a keyboard? I don't know. The live CD running
> Enlightenment wouldn't do anything without a mouse. The hard disk
> installed Gobo is the same, but without the volcanic cinder cones.
>
> Another thing I question is: Why is Gobo trying to sniff out the VM? I
> thought that guest OSes weren't aware (couldn't become aware?) that
> they're in virtualized hardware.
>
> What say you, Lucas?
>

The thing about Gobo trying to sniff out the VM is because Xorg's automatic
configuration either hangs when probing certain drivers or produces
settings that will not work when the host is under QEMU (at least that is
what my experience has shown). For that reason, we ship a default xorg.conf
that QEMU deals with just fine.

Now, I remember facing a similar problem before: the mouse would just not
work on QEMU for some weird reason. However, I noticed that by forcing Udev
to get device events from the kernel one more time ("udevadm trigger"), the
input device would then be discovered.

Two simple things that you can do are:
1) type 'udevadm trigger' in the console
2) type 'gpm -m /dev/input/mice -t imps2' and check that the cursor moves
in the console

If you have feedback from the mouse after (2), then I believe that you will
also have proper input in Xorg.

Lucas

_______________________________________________
gobolinux-users mailing list
[email protected]
http://lists.gobolinux.org/mailman/listinfo/gobolinux-users