General TC > Remasters / Remixes - Unofficial

After remastering (manual/automated) TCL does not boot...

(1/4) > >>

MJZ:
...though it does boot in VirtualBox4.0.12  ???


First, as I am new to the forum, let me say, you engineered a great piece of software!
It was already very useful to me, and I will use it further.   :)


Now I have a kind of weird problem (already put 10 working hours in solving it...):
After remastering (manually and with ezremaster resp. remaster.sh), when loaded with (different) bootloaders, the screen goes blank and the system freezes. It is hard to determine the exact point of time, but I guess, it is either during loading the gziped ramdisk to ram, or shortly afterwards. The Kernel doesn't give any (visible) output yet.
The vmlinuz is ok, booting it without a ramdisk is ok (besides missing fs).

The weirdest thing: to provide a test case, I remastered TCL (microcore and tinycore!), without applying any changes to it. So I basically just unpacked und re-packed them. Same Problem each time!

And: remasterd TCL does run on VirtualBox! Tests on other machines are pending...

As I said, I tinkered with it for 10h.... Thank you for any help you can provide.
Cheers
Michael



ps: my machine is quite standard, amd phenom x4 II 955, asus M4N68T-M LE board, 4GB DDR3 ram, nVidia GT 430.....

maro:
First up to see how far the kernel gets in it's boot process I'd suggest to avoid boot code 'quiet' (or rather use 'debug' instead). This way you should at least get some output from the kernel which should guide your next steps. If you don't get anything from the kernel then it's obviously the boot loader that needs looking into.

MJZ:
thank you.
I tried that, there is no output (or at least none I can perceive before the screen turns dark).
Weird thing about the bootloaders: they had no problem loading the original ramdisk; and they have no problem in virtualbox. Are there any such problems known, especially syslinux/isolinux?
i will try some more loaders and report back...

coreplayer2:
Not sure if this is related but, I have reported similar sounding issue with early versions of syslinux version 4.   Prior releases ie 3.86 (I think and earlier) did not have this problem.   In my experience this occurred only on older equipment, where black screen appeared early during syslinux boot process.

try an earlier syslinux version or grub4dos (both of which boots fine on older equipment not supported by syslinux v4).

Like I say not sure if this is same issue but it sure sounds similar.

MJZ:
as the same problem occurs with isolinux/syslinux, and grub-legacy and grub2, I'm not sure that it is a boot loader specific problem.
With grub2, I got now a slightly different result: after loading the two TCL files, the kernel boots but panics.
See attached output.
Any ideas? Thank you again.

Navigation

[0] Message Index

[#] Next page