WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: does not boot tc 3.3. was working fine w/ tc3.2  (Read 2577 times)

Offline pdbtinycore

  • Newbie
  • *
  • Posts: 4
does not boot tc 3.3. was working fine w/ tc3.2
« on: December 06, 2010, 11:35:58 AM »
using a not too common PC a sony VAIO X series model VPCX115KX.
was working fine with 3.2 and options
    tinycore vga=791 laptop

now with 3.3 absolutely nothing happens, tried usbwait, other display options ...

I also used ubuntu 10.04 which worked fine but ubuntu 10.10 does not boot either and
I was specially hopeful with TC which had some difficulty with the display initially but
worked very well with 3.2.

I have tried again 3.2 to make sure that it still works on my VAIO X and it does.
Any help would be appreciated.

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: does not boot tc 3.3. was working fine w/ tc3.2
« Reply #1 on: December 06, 2010, 12:11:56 PM »
Likely the wait scsi scan mod. Try this and see if it will boot:
tinycore vga=791 laptop base norestore nofstab
« Last Edit: December 06, 2010, 12:14:32 PM by roberts »
10+ Years Contributing to Linux Open Source Projects.

Offline pdbtinycore

  • Newbie
  • *
  • Posts: 4
Re: does not boot tc 3.3. was working fine w/ tc3.2
« Reply #2 on: December 06, 2010, 02:58:28 PM »
solution proposed does work.
I had tried norestore base but nofstab on top did it.
Is this related to the fact that this is an SSD disk?
Can I expect it to work w/o these option necessary in the future?

Many thanks for this prompt answer.
PdB
PS: I would appreciate if you can point me to some place which elaborates
on this explanation: I used to work on linux kernel and would be interested
in getting involved again if I can.

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: does not boot tc 3.3. was working fine w/ tc3.2
« Reply #3 on: December 06, 2010, 11:31:13 PM »
What happens if after boot if you open a terminal and issue a

sudo /usr/sbin/rebuildfstab

Any errors or hangs there?
10+ Years Contributing to Linux Open Source Projects.

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 10965
Re: does not boot tc 3.3. was working fine w/ tc3.2
« Reply #4 on: December 07, 2010, 04:44:26 AM »
Also, could you boot with "tinycore vga=791 laptop debug" and post the last screen that you see?
The only barriers that can stop you are the ones you create yourself.

Offline pdbtinycore

  • Newbie
  • *
  • Posts: 4
Re: does not boot tc 3.3. was working fine w/ tc3.2
« Reply #5 on: December 07, 2010, 08:48:49 AM »
I tried first

tinycore vga=791 laptop debug

and IT WORKED fine.
Even more surprising after It worked fine EVEN w/o the debug option.

Flabbergasted I suspected some mistake and tried again with  formatting the USB key.
It still worked fine even w/o the debug option.

I concluded that I had probably made a mistake all along but tried another usb boot: the
first one I used was the multiboot form pen.
I tried now with LiLi usb creator, also with  key formatting: the problem reappeared

tinycore vga=791 laptop         does not boot, nothing appears on screen.

Adding base, norestore, nofstab did not fix anything, still nothing on the screen
finally adding debug option gives the same result: nothing on the screen.

Went back to the multiboot usb from pen , reformatted and tried again

tinycore vga=791 laptop

now we are back to no boot, nothing on the scree.

When I added the debug options everything works fine, tried the rebuildfstab command
in a terminal which works w/o complaining.

If I try again w/o the debug option sometimes it boots fine sometimes it hangs
after displaying
pci 0000:02:00.1: no compatible bridge window for [mem 0xfffe0000 - 0xffffffff

I did not try again the "base norestore nofstab" options, which seems now like a red herring.
There is probably a timing window which makes this problem appear and disappear
probably caused by something else (sorry for the probably's, I am not on a sure footing here).

Do not hesitate to contact me if you think I can help, to run more tests or use alternate
usb creators or whatever, I am interested in the solution.
Regards