Tiny Core Base > TCB Q&A Forum

TCL V10 Boot Problem

(1/1)

gmc:
I have a system that has been running TCL 4.7.7 without any problems for some years now.

I have a custom Xorg configuration that gives me a virtual desktop with multiple resolutions that I can easily switch between with Ctrl-Alt+ or Ctrl-Alt-.

I just tried to run (CD boot) the new TCL V10 on this machine and ran into a problem.  When I boot Tiny Core (not Plus), it boots almost to the desktop (GUI) and then black screens and stops.  It looks like there is an extremely short flash of the desktop just before the black screen.  I can drop to the CLI after the black screen/stop.  Boot code 'base' allows a full boot to GUI desktop, but without grabbing the Xorg settings from sda1.

I can boot TCL V9.0 and it imports the Xorg settings from version 4.7.7 on sda1 and I have my customized Xorg resolutions.

I have tried boot codes such as VGA=, xvesa=xxx,yyy,nn, and xsetup.  None of those affect the outcome in any noticeable manner (xsetup does not appear to do anything at all).  'Norestore' has no effect.

I have tried a number of other desktop Window Mangers from the menu (using TCL+), they all have the same outcome, that is to say, they boot to a black screen just before the GUI would normally load and then stop.

If I delete the version 4.7.7 files from sda1 and then boot version 10 I get the normal boot with GUI, but of course there is no customized Xorg.

I would like to keep the Xorg setup I already have in place.  If Xorg is the problem, how do I proceed?

Rich:
Hi gmc
It sounds like it's finding your  tce  directory for version 4.7.7. I'm guessing some of those extensions are not compatible
with TC10. I would do an install to a separate partition including the TC10 versions of your current extensions and then
copy your  Xorg.conf  file over.

gmc:
Thanks, that makes sense to me.  I was hoping to be able to narrow the problem down to a specific "thing" but this may be the way to go.  I'll give it a try.

mocore:
ftr using something like


--- Code: ---# eg create new/blank disk or partition , with the label NCORE

mkdir test ;
cd test ;

echo "http://tinycorelinux.net/9.x/x86_64/release/distribution_files/vmlinuz64

http://tinycorelinux.net/9.x/x86_64/release/distribution_files/corepure64.gz

http://tinycorelinux.net/9.x/x86_64/tcz/info.lst.gz

" | while read line ; do
    [ -z "$line" ] || wget -nc -nH -x "$line" ;
 done

# create link to make  tce= boot option use linked tcz dir
ln ./9.x/x86_64/tcz ./9.x/x86_64/optional


--- End code ---

the above to store different tc versions, tcz ect

it is possible to have a local directory structure like tinycorelinux.net
and isolate different tc versions+tcz on the same folder/disk/partition  !
by setting the appropriate paths in boot loader config file !!

++grub2 eg menu

--- Code: --- menuentry "tc-test " {
 search --no-floppy --fs-uuid --set=root  --label NCORE

         linux  /test/9.x/x86_64/release/distribution_files/vmlinuz64 norestore base tce=LABEL=NCORE/test/9.x/x86_64/
         initrd /test/9.x/x86_64/release/distribution_files/corepure64.gz
  }

--- End code ---

DanTC:
I get the same thing when booting the dCorePlusBijoni64.iso ... 
 
In the boot process using these opts kind of work:

--- Code: ---init=/init   waitusb=25    noutc   vga=791
--- End code ---

it will continue to boot, but then 'flash out'... and display a black text screen. There I issue:

--- Code: ---xinit  xterm
--- End code ---

... and the GUI desktop is started and displays.

hope this helps

Navigation

[0] Message Index