Xvesa fix and/or resolution choice on boot

[marky]

Hi,

I started to use TC Plus a week ago and I love it.
I use it on two different computers with the pretty decent hardware.
Somehow I've lost ability to open Xvesa window in the ControlPanel. It shows up for a split of second with nothing visible and disappears. On both machines.

Actually the only reason I need it is that on laptop I'd need to change the resolution to fit the screen and I'm not able to do it now since the Xvesa set up is not accessible.

Any clue, please?

[gerald_clark]

Exit to the shell and run xsetup.sh.

[curaga]

If you've installed Xorg or Xfbdev, the script will not show resolutions, as those two are configured differently.

[marky]

First of all, I'm not that good to know what exactly to do by:

Exit to the shell and run xsetup.sh

.
By Ctrl+Alt+F1 went to the console and tried to run that xsetup.sh command with no success, since I couldn't get to the /user/bin folder. I've tried to run sh ./xsetup.sh in several ways, with no success since I still consider myself as a newbie in linux.

Secondly, here it is my end list of installed apps copied from TC Sytem Stats window:

Code: [Select]

wpa_supplicant
xbitmaps
xcursor-themes
xdg-utils
xf86-input-evdev
xf86-video-vesa
xfe-common
xfi
xkeyboard-config
Xlibs
Xorg-7.7
Xorg-7.7-3d
Xorg-7.7-3d-dev
Xorg-7.7-bin
Xorg-7.7-dev
Xorg-7.7-lib
Xorg-fonts
xorg-proto
xorg-server
xorg-server-dev
Xprogs
xtrans
Xvesa
xzgv

and it seems that xorg is there.

So, what now?

[Juanito]

If you have loaded the Xorg-7.7 extension after you loaded Xvesa, tinycore will run Xorg and not Xvesa.

You will need to ensure that Xorg-7.7 is not listed "onboot", reboot and then Xvesa and xsetup.sh should run without problems.

[marky]

Actually, that list I've posted before was from System Stats.

onboot.lst differs from it:

Code: [Select]

Xlibs.tcz
Xprogs.tcz
aterm.tcz
flwm_topside.tcz
wbar.tcz
flwm_topside.tcz
wifi.tcz
wl-modules-4.8.17-tinycore.tcz
iw.tcz
pci-utils.tcz
firmware-atheros.tcz
firmware-atheros.tcz.md5.txt
firmware-broadcom_bnx2.tcz
firmware-broadcom_bnx2.tcz.md5.txt
firmware-broadcom_bcm43xx.tcz
firmware-broadcom_bcm43xx.tcz.md5.txt
firmware-ipw2100.tcz
firmware-ipw2100.tcz.md5.txt
firmware-ipw2200.tcz
firmware-ipw2200.tcz.md5.txt
firmware-iwlwifi.tcz
firmware-iwlwifi.tcz.md5.txt
firmware_iwlwifi-7260.tcz
firmware_iwlwifi-7260.tcz.md5.txt
firmware-libertas.tcz
firmware-libertas.tcz.md5.txt
firmware-myri10ge.tcz
firmware-myri10ge.tcz.md5.txt
firmware-netxen.tcz
firmware-netxen.tcz.md5.txt
firmware-openfwwf.tcz
firmware-openfwwf.tcz.md5.txt
firmware-radeon.tcz
firmware-radeon.tcz.md5.txt
firmware-ti-connectivity.tcz
firmware-ti-connectivity.tcz.md5.txt
firmware-ueagle-atm.tcz
firmware-ueagle-atm.tcz.md5.txt
firmware-vxge.tcz
firmware-vxge.tcz.md5.txt
firmware-iwimax.tcz
firmware-iwimax.tcz.md5.txt
firmware-zd1211.tcz
firmware-zd1211.tcz.dep
firmware-zd1211.tcz.md5.txt
firmware.tcz
firmware.tcz.md5.txt
tc-install.tcz
kmaps.tcz
gparted.tcz
firefox_getLatest.tcz
firefox.tcz
spacefm-doc.tcz
spacefm.tcz
ImageMagick-dev.tcz
ImageMagick-doc.tcz
conky.tcz
xzgv.tcz
xfi.tcz
Xvesa.tcz
and doesn't include either one since I didn't load them as you can see.

[Juanito]

Your onboot.lst seems messed up, it should not contain any file names ending in *md5.txt.

The command to use to see which extensions are loaded is "tce-status -i", the following command will show which X server extensions are loaded:

Code: [Select]

$ tce-status -i | grep X

[curaga]

If you are using Xorg, google xorg.conf, arch wiki tends to have good explanations.

[marky]

Your onboot.lst seems messed up, it should not contain any file names ending in *md5.txt.

The command to use to see which extensions are loaded is "tce-status -i", the following command will show which X server extensions are loaded:

Code: [Select]

$ tce-status -i | grep X

I'd love to do it but I'm not able to copy the result from the Terminal.
Sending along phone pictures then:
https://drive.google.com/open?id=0B4YHneheJg-vMzVnaVhJSjRYQkk
https://drive.google.com/open?id=0B4YHneheJg-vTTNOb01MNFBnNms

[Juanito]

That confirms that you have both Xorg-7.7 and Xvesa loaded - in this case tinycore will use the one that was loaded last, presumeably Xorg-7.7, but you can confirm with this command:

Code: [Select]

$ cat /etc/sysconfig/Xserver
As mentioned previously, you need to reboot and only load one of Xfbdev, Xorg-7.7, Xvesa

[marky]

Xvesa came out after that command, but the others are not included in onboot.lst, so how to exclude them from boot?

You will need to ensure that Xorg-7.7 is not listed "onboot",

And in what way please?
I didn't load anything deliberately, just installed TC and several basic apps.

[Juanito]

The easiest way to edit onboot.lst is to use the apps gui - apps/maintenance/onboot maintenance

It would also probably be a good idea to read this: http://tinycorelinux.net/book.html

[marky]

The easiest way to edit onboot.lst is to use the apps gui - apps/maintenance/onboot maintenance

My onboot.lst posted above is taken just from apps/maintenance/onboot maintenance thing.

[Juanito]

To fix things, you will either need to reboot or, if /etc/sysconfig/Xserver=Xvesa, exit to the prompt using the exit icon and "startx"

[polikuo]

If I were you, I'd re-configure the onboot.lst

How did you generate it in the first place ?