Starting X at boot

[tinypoodle]

I'm also wondering what purpose libasound serves loaded "onboot"?

Ditto with gtk2

[curaga]

How dated are we talking about? Is this a really low-ram comp?

[Rich]

Hi Vilkata
After you boot while still at the command line:

Code: [Select]

ls -l /var/log/See if  Xorg.0.log  was created. If it's there, check if it lists any errors.

[Vilkata]

Juanito: I will change my onboot as you suggested, plus removing asound and gtk2. I had simply added the needed apps, and then using the app gui I removed everything listed as unneeded for onboot.

Curagua: 247 mb ram, 1.1 Gz Celeron.

Rich: Will do, and update when I get back.

Edit: /var/log/Xorg.0.log was created, and indeed lists several errors.

http://pastebin.com/2mMr9

[Rich]

Hi Vilkata
I clicked on the link you provided but it says that the paste has been removed.

[Vilkata]

http://pastebin.com/SwR5p9ES Redid it, this one works

Edit: and here is the Xorg.0.log after I manually startx: http://pastebin.com/zwfNckmT

[tinypoodle]

It might be preferable you'd post the log after manually starting X with 'startx' as well, for comparison.

In relation to requirements of Core and to testimonies of other users of this forum, I wouldn't call 247 mb ram, 1.1 Gz Celeron "incredibly dated" at all.

OTOH, the attempt of running chromium with such specs sounds painful 
Why would you add chromium to .X.d?

[Vilkata]

I will do so and edit it into my last post for convenience.

And I have since changed the setup described in the original post, though the issue with X not starting remains.

My idea originally was that this computer could serve as a really basic desktop for browsing, email, etc; having it start to simply a browser seemed the best way to get the most out of it, and for the most part, it is usable for the most part, as long as flash isn't involved obviously.

When that didn't work, as I hinted at but wasn't clear about earlier, I fully reinstalled, full tinycore, which booted properly the first time, and then the same issue as here. I no longer have chromium in .X.d, and have actually switched to seamonkey.

More relevantly, possibly, I also switched flwm_topside to openbox a few hours ago, as my xorg log will most likely show, but otherwise, no changes between the two logs 

[curaga]

Your log shows an Intel driver bug where it randomly fails to start. It's been reported on various OSes since 2000 and apparently never solved.

Your graphics chip, i815, is very old and basically unsupported by current Intel drivers. So you may want to use fbdev or vesa, or perhaps install a discrete graphics card.

[Vilkata]

When using Xvesa, opening a gtk app gives me buggy display, until I close it, to the point where it is unusable; Xorg, obviously, does not work without said drivers, and as such, going the route of Xorg + xf86-video-intel was my only real choice.

Now knowing that it is 'simply' an old, unresolved bug, I made a simple workaround; as invoking startx a second time seemed to work, I simply added it a second time to .profile, and thus far seems to be working. Thanks for your help everybody, and thanks for making such an awesome distro.

[tinypoodle]

When using Xvesa, opening a gtk app gives me buggy display, until I close it, to the point where it is unusable; Xorg, obviously, does not work without said drivers, and as such, going the route of Xorg + xf86-video-intel was my only real choice.

What about Xorg vesa or fbdev drivers?

[Juanito]

I used to have an old intel graphics chipset a while back - it wouldn't work with Xvesa alone, but the 915resolution extension got it working.