Tiny Core Linux

General TC => Tiny Core on Virtual Machines => Topic started by: ElQuia on February 13, 2011, 01:56:42 PM

Title: VirtualBox Additions and TinyCore 3.4
Post by: ElQuia on February 13, 2011, 01:56:42 PM

Hi guys, sorry for a noob question. I have installed TinyCore 3.4 in VirtualBox 4.0.2 on Windows 7 x64.
When I install the VBox 4.02 additions available (yes, they say "testing") in apps, on reboot I can NOT get a GUI, it tries and fall backs to a small command line window.

I have TC 3.12 installed with the additions tat were available before and it works ok in Virtual Box 4.02
I dont know why this newer install won't.

Please help?

Title: Re: VirtualBox Additions and TinyCore 3.4
Post by: ElQuia on February 18, 2011, 12:52:42 PM

 ??? AnyBody  ??? Pleaseeeeee :(

Title: Re: VirtualBox Additions and TinyCore 3.4
Post by: Arslan S. on February 18, 2011, 02:09:03 PM

can you replace "waitforX" in ~/.xsession with something like "sleep 5" and try again

see
http://forum.tinycorelinux.net/index.php?topic=8284.msg44716#msg44716 (http://forum.tinycorelinux.net/index.php?topic=8284.msg44716#msg44716)

Title: Re: VirtualBox Additions and TinyCore 3.4
Post by: ElQuia on February 18, 2011, 02:33:06 PM

Arslan S.:
First, thanks for your reply.
Second: I am proficient with windowz, but real noob, doing my first steps in linux. Could you please tell me step by step how to replace "waitforX" in ~/.xsession with something like "sleep 5" ?
I don´t know even where to find "~/.xsession"  :(

Title: Re: VirtualBox Additions and TinyCore 3.4
Post by: Rich on February 18, 2011, 02:51:26 PM

Hi ElQuia
.xsession is in your home directory. Click on the desktop and go to SystemTools and Editor.
Now open and edit the file, you will already be in the correct directory.

Title: Re: VirtualBox Additions and TinyCore 3.4
Post by: ElQuia on February 18, 2011, 03:02:53 PM

OK Rich, will do and be back, but maybe first i will install 3.5 (just saw the update) and then try again. Ill be back with testing results tomorrow.

THANKS  :) :) to all

Title: Re: VirtualBox Additions and TinyCore 3.4
Post by: Arslan S. on February 20, 2011, 05:58:28 AM

i have packed up vbox 4.0.4 and tested vbox additions on a windows host
x starts fine with vboxvideo driver, problem mentioned here http://forum.tinycorelinux.net/index.php?topic=966.msg39666#msg39666 (http://forum.tinycorelinux.net/index.php?topic=966.msg39666#msg39666) seems to be gone

so removing testing flag and submitting the updates soon

Title: Re: VirtualBox Additions and TinyCore 3.4
Post by: maro on February 20, 2011, 05:15:12 PM

Thanks Arslan for building VBox 4.0.4. When I read the changelog (http://www.virtualbox.org/wiki/Changelog) I spotted this ticket (http://www.virtualbox.org/ticket/8231) and assumed that it might be related to the problem we've seen now for a while.

Before I had a chance to test this assumption you've announced the extension rebuild, so we just have to wait the short time until it hits the repository to benefit from this improvement.

Title: Re: VirtualBox Additions and TinyCore 3.4
Post by: Arslan S. on February 21, 2011, 06:30:48 AM

that's exactly the fix

Ubuntu 10.04 Xorg server version is 1.7.6, tiny core linux 3.x Xorg version is 1.7.7
looking at Xorg.log exactly the same crash report

wish we had submitted the bug report though

Title: Re: VirtualBox Additions and TinyCore 3.4
Post by: hiro on February 21, 2011, 10:06:52 AM

I hereby report all the voodoo in Xorg :)

Title: Re: VirtualBox Additions and TinyCore 3.4
Post by: curaga on February 21, 2011, 12:08:27 PM

Is this a different issue from the waitforX w/ virtualbox video drivers one?

Title: Re: VirtualBox Additions and TinyCore 3.4
Post by: Arslan S. on February 21, 2011, 01:30:39 PM

i don't think there is anything to do with waitforX, the problem was a null pointer in vboxvideo driver

Quote

in vboxvideo.c and VGAHWPTR(pScrn) is NULL.

Code: [Select]

VGAHWPTR(pScrn)->IOBase = pScrn->domainIOBase;

Title: Re: VirtualBox Additions and TinyCore 3.4
Post by: hiro on February 21, 2011, 04:41:00 PM

Doesn't waitforX trigger this? I thought it also happens here when you close the last X client...