Tiny Core Base > Alpha Releases

Tiny Core 3.0 Alpha 2 Testing

<< < (4/8) > >>

u54749:
>>> Check for a BIOS update for your machine.

This does not explain why Alpha1 (and 1.x and 2.x) boots correctly and Alpha2 does not.
The configuration of the machine has not changed

^thehatsrule^:
You could compare any relevant messages from `dmesg`

u54749:
I have overwritten Alpha1 by  Alpha2 on my system. I can't find Alpha1 any more in the TC download area.  So I can't do the comparison at this time.

roberts:

--- Quote from: jur on May 12, 2010, 10:09:25 AM ---All was running fine up to the point I did a 'Build dep reporting database' in AppsAudit. Then all the deps containing abc-2.6.33.3-tinycore.tcz became abc-KERNEL.tcz, and my system stopped working because it can't find those KERNEL dependencies.

KERNEL seems not getting parsed...?

--- End quote ---
Found it. Fixed it. Thanks!

roberts:

--- Quote from: u54749 on May 12, 2010, 01:14:05 PM ---I see some strange boot behavior in Alpha 2

with "quiet" boot mode enabled
In Alpha 1
-  shows GRUB4DOS messages
-  shows "Booting Tinycore_3.0alpha1" below the GRUB4DOS messages
(boot continues with more messages and finally TC desktop is shown)

In Alpha 2
-  Shows GRUB4DOS messages
-  Overwrites the GRUB4DOS messages on top of the screen with error message:
pci 0000:01:00.0: no compatible bridge window for [mem 0x80000000-0x8001ffff pref]

- after a fraction of a second clears the screen completely (you have to read really fast...)
- then shows "Booting Tinycore_3.0alpha2" on the top of the screen
(boot continues with more messages and finally TC desktop is shown)

It's the first time I see this particular error message

--- End quote ---

Did you download distribution files or the iso?
Did you check md5sum to ensure a good download?

Since there was no change in kernel or modules for alpha1 to alpha2 and
since you are seeing error before "Booting Tiny Core.." I would start by checking that the download is good.

The only change, early in the boot proces, but after "Booting Tiny Core" was a change to permission on ramzswap. You could also try to boot using the 'embed' option to eliminate that change.

Navigation

[0] Message Index

[#] Next page

[*] Previous page