Tiny Core Base > Alpha Releases
Tiny Core v4.0 Alpha 2 Testing
yoshi314:
--- Quote from: roberts on September 04, 2011, 03:11:04 PM ---If you can, boot with boot option, 'showapps'. Each extension will then be displayed. This might be useful to see which extension is hanging.
--- End quote ---
i'm having a hunch it's actually alsa startup script atm.
will test with the parameter.
edit: well, this is beyond embarrassing, but it seems i left the getfllash10 script in onboot.lst
and it asks for confirmation to reinstall, but it only shows with showapps boot parameter.
Jason W:
I noticed and fixed that getFlash10 issue as i saw the same thing almost a week ago. It happened when flash10.tcz is lower down the list in onbootl.st, which it naturally would be.
Have you updated your extensions recently, or is it doing this on a new install?
I will take another look at the startup script.
EDIT: I see that my correction got lost in the shuffle, corrected extension is uploaded now.
yoshi314:
--- Quote from: Jason W on September 04, 2011, 04:18:10 PM ---I noticed and fixed that getFlash10 issue as i saw the same thing almost a week ago. It happened when flash10.tcz is lower down the list in onbootl.st, which it naturally would be.
Have you updated your extensions recently, or is it doing this on a new install?
I will take another look at the startup script.
EDIT: I see that my correction got lost in the shuffle, corrected extension is uploaded now.
--- End quote ---
new install.
also, there is no cryptsetup in 4.x repositories. version from 3.x works just fine.
roberts:
--- Quote from: u54749 on September 04, 2011, 03:49:55 PM ---The busybox binary isn't setuid root anymore. Is this intentional?
I have serious instabilities with this alpha version (Xorg, ALSA, ...). After four hours of searching I have come to the conclusion that the new "ldconfig" binary is malfunctioning.
Here is an example with the libva extension
~ $ tce-load -i libva.tcz
libva.tcz: OK
~ $ ldconfig -p | grep libva
result with the alpha2 ldconfig
libva.so.1 (libc6) => /usr/local/lib/libva.so.1
libva.so (libc6) => /usr/local/lib/libva.so
libva-x11.so.1 (libc6) => /usr/local/lib/libva-x11.so.1
libva-x11.so (libc6) => /usr/local/lib/libva-x11.so
libva-tpi.so.1 (libc6) => /usr/local/lib/libva-tpi.so.1
libva-tpi.so (libc6) => /usr/local/lib/libva-tpi.so
libva-glx.so.1 (libc6) => /usr/local/lib/libva-glx.so.1
libva-glx.so (libc6) => /usr/local/lib/libva-glx.so
result with the alpha1 ldconfig
libva.so.1.0.4 (libc6) => /usr/local/lib/libva.so.1.0.4
libva.so.1 (libc6) => /usr/local/lib/libva.so.1
libva.so (libc6) => /usr/local/lib/libva.so
libva-x11.so.1.0.4 (libc6) => /usr/local/lib/libva-x11.so.1.0.4
libva-x11.so.1 (libc6) => /usr/local/lib/libva-x11.so.1
libva-x11.so (libc6) => /usr/local/lib/libva-x11.so
libva-tpi.so.1.0.4 (libc6) => /usr/local/lib/libva-tpi.so.1.0.4
libva-tpi.so.1 (libc6) => /usr/local/lib/libva-tpi.so.1
libva-tpi.so (libc6) => /usr/local/lib/libva-tpi.so
libva-glx.so.1.0.4 (libc6) => /usr/local/lib/libva-glx.so.1.0.4
libva-glx.so.1 (libc6) => /usr/local/lib/libva-glx.so.1
libva-glx.so (libc6) => /usr/local/lib/libva-glx.so
The new ldconfig misses part of the entries.
When I copy over the old "ldconfig" in alpha2 everything works normally.
--- End quote ---
Both will be corrected in next cut. Thanks for reporting.
Jason W:
yoshi314-
Try getFlash10 from a new download again, my correction had a typo that is fixed now.
Also, cryptsetup or anything that depends on kernel modules was not copied over to the 4.x repo. When new modules are made and the 3.x extension tested, they can be submitted to 4.x. Every extension was manually reviewed and copied or not copied over to 4.x on a case by case basis, so as to not start out with a broken repo.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version