First, you don't disturb me. I went back to the a-2 thread and you never elaborated on which extension(s) you loaded, what kind of hardware, etc., to explain what might be needed to reproduce the same problem. Was this related to 64-bit kernel? Did you get the same or similar errors booting "base norestore" etc.? What chipset was supported in a-1 but not previously?
You are absolutely right. But I didn't elaborate about all these things because I didn't know I had to, my knowledge of linux is very, very limited and nobody asked me to clarify.... so I'll try to make things better now. Excuse me if I post irrelevant information.
* My computer is a Acer Aspire One, AO751H with an Intel Atom processor Z520 with an ide 160 Gb harddisk. TC 2.10 was able to boot from a CD or a pendrive, but it didn't recognize (find?) the harddisk. In a thread I started on that issue curaga
pointed that "it's a poulsbo chip. Unsupported currently in TC 2.x. Unless someone makes an extension, wait for 3.x."
So I have been using TC 2.10 and 2.11 booting from a ext2 formatted SD card.
* The tests I have done with alpha-1, alpha-2 and alpha-3 all have been done booting from the same SD card (formatted as ext2, with persistent home and opt). All three alpha's do find the harddisk now.
* With alpha-1 I haven't found any problem so far and thus I use it now as if it were stable. With alpha-2 I found different boot errors (different in different boots as I mentioned in the alpha-2 thread) while loading the TC Extensions. With alpha-3, also boot errors at the same stage.
* As I think that the system is 32 bits, I have only used 32-bit kernel.
* The extensions I load on boot are: alsa, pcmanfm and vlc. Only these three.
* The bootcodes I use are: quiet vga=788 noswap home=sdb1 opt=sdb1 laptop restore=sdb1/tce max_loop=255 waitusb=5
* I changed waitusb to 10 but it didn't make any difference
* Both in alpha-2 or in alpha-3, after the boot errors, the system finally boots and all three extensions do work, but other things, like mounting a pendrive through cpanel's mount do not work (I guess
is that it is related to the errors on booting)
I attach the message after booting with syslog enabled.