Tiny Core Base > Release Candidate Testing
tinycore_v2.9rc4
jur:
Robert:
Booting my netbook at home is an even bigger mess. Something fundamental seems to be going wrong - I get an avalanche of error messages, all of which go away if I use 'base'.
The thing is, my two setups are just totally different - one is booting of a vfat usb stick on my work laptop (couple years old Toshiba Satellite 512MB mem) with only /tce persistent and no onboot extensions, while the home netbook is an Asus 1000he with 1GB mem different everything, Xorg, persistent /home, /opt, on ext3 hard drive partition.
But these 2 very different setups give very similar results - total mess while booting. Both cases boot fine with tc-2.8.1
One thing I have in both setups, is a whole swag of tinycore.gz files, named eg tinycore-2.9rc4 if I am not booting off them. Both setups, these files are in /tce, not in/boot or whatever. Could there be some mixup?
Is there a way to record a boot log so I can send you the error messages?
jur:
I think I have found the problem.
In both the aforementioned cases, once I moved the booting files to a directory called /boot, booting proceeds fine. Permissions for /dev/shm are also correct.
So the difference between tc-2.8 and tc-2.9rc4 is, the booting files cannot be in /tce in 2.9rc4, while with 2.8.1 (and prior versions) this presents no problem.
Juanito:
--- Quote from: jur on February 18, 2010, 06:51:27 AM ---once I moved the booting files to a directory called /boot, booting proceeds fine.
--- End quote ---
By "booting files", do you mean bzImage and tinycore.gz/microcore.gz and/or Xlibs.gz, XProgs.gz and Xvesa.gz?
curaga:
@bmarkus: the glibc extensions haven't yet been updated to 2.11.1.
bmarkus:
--- Quote from: curaga on February 18, 2010, 09:08:05 AM ---@bmarkus: the glibc extensions haven't yet been updated to 2.11.1.
--- End quote ---
OK, I will postpone this test. Do you have a timeframe?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version