Tiny Core Linux

Tiny Core Base => TCB Q&A Forum => Topic started by: combo3 on September 03, 2009, 10:49:32 AM

Title: [SOLVED] Netboot display cheatcode won't take
Post by: combo3 on September 03, 2009, 10:49:32 AM

I'm netbooting TC2.2 on a Dell OptiPlex GX1 with a maximum display resolution of 800x600x24.

/netboot/pxelinux.cfg/default

Code: [Select]

DEFAULT tinycore
TIMEOUT 300    
          
LABEL tinycore
KERNEL bzImage
APPEND quiet noswap vga=789 initrd=tinycore.gz
Screen size is fine during the boot phase, but reverts to high resolution once the system enters runlevel 5, forcing me to do a Ctrl-Alt-Bksp-xsetup-startx dance.

{Note: I've tried every option under the 640x480 and 800x600 columns listed in http://tinycorelinux.com/faq.html#bootcodes - to no avail. Adding "xsetup" to the APPEND line works, but sort of defeats the purpose of having a "vga=7xx" option.)


Right after booting ~/.xsession shows:

Code: [Select]

Xvesa -br -screen 1024x768x32 -shadow -mouse /dev/input/mice,5 -nolisten tcp -I 2>&1 > /dev/null & waitforX
A remaster with /etc/skel/.xsession changed to 800x600x24 works, but I was hoping for a more elegant solution.

Am I missing something obvious?

Title: Re: Netboot display cheatcode won't take
Post by: gerald_clark on September 03, 2009, 03:47:01 PM

After running xsetup.sh and startx, run the backup utility.
The settings will be reloaded next time you boot.

Title: Re: Netboot display cheatcode won't take
Post by: roberts on September 03, 2009, 10:29:08 PM

The vga options are for the console. Xvesa and console resolutions are not isomorphic.
As stated performing a backup presists your Xvesa resolution,

Title: Re: Netboot display cheatcode won't take
Post by: combo3 on September 06, 2009, 04:11:07 AM

Thanks for the replies.

To clarify:

This machine has no hard drive, so I planned on using it as a diskless internet kiosk in a public waiting area -- the kind of place where quick reboots and lack of persistency are highly desirable.


Anyways, I solved my problem by switching monitors. Seems the issue was hardware related.