Tiny Core Linux

Tiny Core Extensions => TCE Talk => Topic started by: Vilkata on January 20, 2014, 07:01:15 PM

Title: Starting X at boot
Post by: Vilkata on January 20, 2014, 07:01:15 PM
I apologize if this is the wrong forum to post this in, but as it is a small question related to more or less the first step from microcore to full tinycore.

As the computer I am on is incredibly dated, I installed microcore(5.1) with persistent home and opt. I then installed Xorg-7.7.tcz( with -wi options,) as with Xlibs, chromium-browser, and the intel video drivers(needed for this computer). I then added an entry for chromium to .X.d, and when i use startx, it works as I intend.

But, I cannot get x to start at boot. I tried adding it to bootlocal.sh, but it didnt work, and figured I would ask. Ideas?
Title: Re: Starting X at boot
Post by: gerald_clark on January 20, 2014, 07:06:21 PM
Unless you have a 'text' boot code, you should automatically be logged in as tc withan X desktop.
Show us the output of 'showbootcodes' and 'ls -l /etc/sysconfig'
Title: Re: Starting X at boot
Post by: Vilkata on January 24, 2014, 03:51:09 PM
Code: [Select]
tc@box:~$ showbootcodes
initrd=/tce/boot/core.gz quiet home=sda1 opt=sda1 norestore waitusb=5:UUID="591190b2-75a0-438b-8145-76cd507401d7" tce=UUID="591190b2-75a0-438b-8145-76cd507401d7" BOOT_IMAGE=/tce/boot/vmlinuz

Code: [Select]
tc@box:~$ ls -l /etc/sysconfig
total 36
-rw-r--r--    1 root     root             5 Jan 24 20:37 Xserver
-rw-r--r--    1 root     root             2 Jan 24 20:37 backup
-rw-rw-r--    1 root     staff            0 Nov 26 10:16 backup_device
-rw-r--r--    1 root     root             9 Jan 24 20:37 cdroms
-rw-r--r--    1 root     root            13 Jan 24 20:37 desktop
-rw-r--r--    1 root     root             5 Jan 24 20:37 icons
-rw-r--r--    1 root     root            10 Jan 24 20:37 keymap
-rw-r--r--    1 root     root             7 Jan 24 20:37 language
-rw-r--r--    1 root     root             7 Jan 24 20:37 mydata
-rw-r--r--    1 root     root             0 Jan 24 20:37 newmodules
lrwxrwxrwx    1 root     root            13 Jan 24 20:37 tcedir -> /mnt/sda1/tce/
-rw-r--r--    1 root     root             3 Jan 24 20:37 tcuser
Title: Re: Starting X at boot
Post by: gerald_clark on January 24, 2014, 04:18:35 PM
Did you also install Xprogs and a windows manager?
What is the output of 'version' ?
Did you modify /home/tc/.profile?
Title: Re: Starting X at boot
Post by: Vilkata on January 24, 2014, 04:27:23 PM
yes, at this point I have full TC, but the same problem, all works fine when I use startx, but it is still not autostarting.

version is 5.1, and I have not modified .profle, but will post it so you can check for any errors:
Code: [Select]
# ~/.profile: Executed by Bourne-compatible login SHells.
#
# Path to personal scripts and executables (~/.local/bin).
[ -d "$HOME/.local/bin" ] || mkdir -p "$HOME/.local/bin"
export PATH=$HOME/.local/bin:$PATH

ONDEMAND=/etc/sysconfig/tcedir/ondemand
[ -d "$ONDEMAND" ] && export PATH=$PATH:"$ONDEMAND"

# Environment variables and prompt for Ash SHell
# or Bash. Default is a classic prompt.
#
PS1='\u@\h:\w\$ '
PAGER='less -EM'
MANPAGER='less -isR'

EDITOR=vi

export PS1 PAGER FILEMGR EDITOR MANPAGER

export BACKUP=1
[ "`id -un`" = "`cat /etc/sysconfig/tcuser`" ] && echo "$BACKUP" | sudo tee /etc/sysconfig/backup >/dev/null 2>&1
export FLWM_TITLEBAR_COLOR="58:7D:AA"

if [ -f "$HOME/.ashrc" ]; then
   export ENV="$HOME/.ashrc"
   . "$HOME/.ashrc"
fi

TERMTYPE=`/usr/bin/tty`
[ ${TERMTYPE:5:3} == "tty" ] && (
[ ! -f /etc/sysconfig/Xserver ] ||
[ -f /etc/sysconfig/text ] ||
[ -e /tmp/.X11-unix/X0 ] ||
startx
)
Title: Re: Starting X at boot
Post by: gerald_clark on January 24, 2014, 04:43:12 PM
Have you modified .ashrc ?
Title: Re: Starting X at boot
Post by: Vilkata on January 24, 2014, 04:49:10 PM
Once again, nope, posted for verification.
Code: [Select]
# ~/.ashrc: Executed by SHells.
#
. /etc/init.d/tc-functions
if [ -n "$DISPLAY" ]
then
`which editor >/dev/null` && EDITOR=editor || EDITOR=vi
else
EDITOR=vi
fi
export EDITOR

# Alias definitions.
#
alias df='df -h'
alias du='du -h'

alias ls='ls -p'
alias ll='ls -l'
alias la='ls -la'

# Avoid errors... use -f to skip confirmation.
alias cp='cp -i'
alias mv='mv -i'
alias rm='rm -i'

alias d='dmenu_run &'
alias ce='cd /etc/sysconfig/tcedir'
Title: Re: Starting X at boot
Post by: tinypoodle on January 24, 2014, 05:19:28 PM
Please post /mnt/sda1/tce/onboot.lst and your bootloader config.
Title: Re: Starting X at boot
Post by: Vilkata on January 24, 2014, 05:27:21 PM
onboot.lst:

Code: [Select]
Xprogs.tcz
aterm.tcz
flwm_topside.tcz
libXau.tcz
libXdmcp.tcz
libXt.tcz
libfontenc.tcz
libXft.tcz
libXinerama.tcz
libXcursor.tcz
wbar.tcz
flwm_topside.tcz
Xorg-7.7.tcz
xf86-video-intel.tcz
cups.tcz
libasound.tcz
dbus-glib.tcz
gtk2.tcz
conky.tcz

and extlinux.conf:

Code: [Select]
DEFAULT core
LABEL core
KERNEL /tce/boot/vmlinuz
APPEND initrd=/tce/boot/core.gz quiet  home=sda1 opt=sda1 norestore waitusb=5:UUID="591190b2-75a0-438b-8145-76cd507401d7" tce=UUID="591190b2-75a0-438b-8145-76cd507401d7"
Title: Re: Starting X at boot
Post by: tinypoodle on January 24, 2014, 06:09:23 PM
Try with removing "quiet  home=sda1 opt=sda1" from boot config and changing "waitusb=" value to 20, and see what happens then.
Title: Re: Starting X at boot
Post by: Vilkata on January 24, 2014, 07:10:22 PM
Except for the obvious(my wallpaper didnt restore, for example,) there was no difference; still booted to prompt, startx worked fine.
Title: Re: Starting X at boot
Post by: gerald_clark on January 24, 2014, 07:43:05 PM
show us 'ls -l /home/tc/.profile'
Title: Re: Starting X at boot
Post by: Vilkata on January 24, 2014, 08:01:21 PM
Code: [Select]
tc@box:~$ ll /home/tc/.profile
-rw-r--r--    1 tc       staff          920 Nov 26 10:16 /home/tc/.profile
Title: Re: Starting X at boot
Post by: gerald_clark on January 24, 2014, 08:06:06 PM
startx is run from .profile.
I guess it is up to you to find out why .profile is not being sourced, or the startx is not being reached.
Title: Re: Starting X at boot
Post by: Juanito on January 25, 2014, 12:51:25 AM
It won't help with your problem, but:
onboot.lst:

Code: [Select]
Xprogs.tcz
aterm.tcz
flwm_topside.tcz
libXau.tcz
libXdmcp.tcz
libXt.tcz
libfontenc.tcz
libXft.tcz
libXinerama.tcz
libXcursor.tcz
wbar.tcz
flwm_topside.tcz
Xorg-7.7.tcz
xf86-video-intel.tcz
cups.tcz
libasound.tcz
dbus-glib.tcz
gtk2.tcz
conky.tcz

..can be reduced to:
Code: [Select]
Xprogs.tcz
aterm.tcz
flwm_topside.tcz
wbar.tcz
Xorg-7.7.tcz
xf86-video-intel.tcz
cups.tcz
libasound.tcz
dbus-glib.tcz
gtk2.tcz
conky.tcz

I'm also wondering what purpose libasound serves loaded "onboot"?
Title: Re: Starting X at boot
Post by: tinypoodle on January 25, 2014, 02:56:52 AM
I'm also wondering what purpose libasound serves loaded "onboot"?

Ditto with gtk2
Title: Re: Starting X at boot
Post by: curaga on January 25, 2014, 04:28:23 AM
How dated are we talking about? Is this a really low-ram comp?
Title: Re: Starting X at boot
Post by: Rich on January 25, 2014, 10:31:35 AM
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.
Title: Re: Starting X at boot
Post by: Vilkata on January 25, 2014, 11:08:57 AM
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
Title: Re: Starting X at boot
Post by: Rich on January 25, 2014, 12:34:18 PM
Hi Vilkata
I clicked on the link you provided but it says that the paste has been removed.
Title: Re: Starting X at boot
Post by: Vilkata on January 25, 2014, 12:38:55 PM
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
Title: Re: Starting X at boot
Post by: tinypoodle on January 25, 2014, 09:58:16 PM
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  :o
Why would you add chromium to .X.d?
Title: Re: Starting X at boot
Post by: Vilkata on January 26, 2014, 11:47:02 AM
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  ;D
Title: Re: Starting X at boot
Post by: curaga on January 26, 2014, 12:06:21 PM
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.
Title: Re: Starting X at boot
Post by: Vilkata on January 26, 2014, 03:15:40 PM
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. :P Thanks for your help everybody, and thanks for making such an awesome distro.
Title: Re: Starting X at boot
Post by: tinypoodle on January 26, 2014, 06:08:15 PM
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?
Title: Re: Starting X at boot
Post by: Juanito on January 26, 2014, 10:17:39 PM
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.