Tiny Core 3.0 Alpha 4 Testing

[bigpcman]

@bigpcman: Nothing in messages.txt either. If you haven't already, please check the md5sums of all extensions, the base image, and do a fsck. Also, is your kernel current? There was an update after the first alphas.

On eeepc, try loading the hwmon and pci-hotplug extensions.

OK, I installed hwmon and pci-hotplug extensions to load on boot and now the "eeepc_laptop" driver installs correctly on boot. That's good news.

Now then, the bad news is I still get error messages as follows:

5-10 of these "/etc/init.d/rcS: line 459: usleep: Text file busy" 
and 20-30 "Bus error"

See attached syslog

edit: Note, just as before if I use the "showapps" boot code all the errors go away (even when no extensions are installed). Seems to me there is a race condition on boot.

BTW all of today's testing has been done on a completely new install.

[curaga]

Just thought I'd point out again that there seems to be a problem with the graphics extension, on radeon cards, at least.

Games that need graphics-2.6.29.1-tinycore.tcz (Games from the Humble Indie Bundle) to run at full speed in 2.11 are acting as if graphics-2.6.33.33-tinycore.tcz hasn't been installed when run under TC3.

Please post Xorg.0.log and dmesg.

[bigpcman]

Moving on to more applications. Tried running Xampp today. Installed bash and ipv6 extensions. I get the following errors:

Code: [Select]

tc@box:/mnt/sdb1/mysys$ sudo /opt/lampp/lampp start
Starting XAMPP for Linux 1.7.3a...
netstat: /proc/net/tcp6: No such file or directory
netstat: /proc/net/udp6: No such file or directory
netstat: /proc/net/raw6: No such file or directory
netstat: /proc/net/tcp6: No such file or directory
netstat: /proc/net/udp6: No such file or directory
netstat: /proc/net/raw6: No such file or directory
XAMPP: Starting Apache with SSL (and PHP5)...
netstat: /proc/net/tcp6: No such file or directory
netstat: /proc/net/udp6: No such file or directory
netstat: /proc/net/raw6: No such file or directory
XAMPP: Starting MySQL...
netstat: /proc/net/tcp6: No such file or directory
netstat: /proc/net/udp6: No such file or directory
netstat: /proc/net/raw6: No such file or directory
XAMPP: Starting ProFTPD...
XAMPP for Linux started.


In tc2.11.1 the firewall extension is required to resolve all ip6 errors. No firewall extension exists in 3.0 repository.

[curaga]

A modprobe of ipv6 should handle that. Was the module loaded automatically in 2.x?

[bigpcman]

A modprobe of ipv6 should handle that. Was the module loaded automatically in 2.x?

Looks like a reboot fixed the problem. The extension installation by itself did not load the ipv6 module.

[bigpcman]

This may not have anything to do with tc3.0 but  I used to be able to:

Code: [Select]

sudo /usr/local/etc/init.d/dropbear start -w -g -m -p 57231 -b /etc/dropbear/banner
where the -p option set the port number. Now the -p seems to be ignored:

from "top"

Code: [Select]

1266  1264 root     S     2236  0.1   0  0.0 /usr/bin/dropbear -w -g -b /etc/dropbear/banner

and indeed port 22 is used not 57231.


edit: Ok, I see what's going on, I'm calling the dropbear script which needs to be modified to include the command options. When using the command:

Code: [Select]

sudo dropbear -w -g -m -p 57231 -b /etc/dropbear/banner

it works as before.

[bigpcman]

odd error on manual backup using panel tool:
Should be sdb1/tce?

Code: [Select]

tc@box:/tmp$ cat backup_status
tar: can't open '/mnt/sdb1/tcebackup/mydata.tgz': No such file or directory
tc@box:/tmp$

removed mydata.tgz and selected none on panel backuptool then entered sdb1/tce and tried again. Then I received the following error:

Code: [Select]

tc@box:/tmp$ cat backup_status
tar: etc/group : No such file or directory
tar: etc/passwd                     : No such file or directory
tar: error exit delayed from previous errors


So I guess if the files in the .filetool.lst are not found this can cause problems. Not sure what caused the first problem? The files passwd and group do exist so I don't know why they can't be saved. Perhaps they are in use?

[althalus]

Just thought I'd point out again that there seems to be a problem with the graphics extension, on radeon cards, at least.

Games that need graphics-2.6.29.1-tinycore.tcz (Games from the Humble Indie Bundle) to run at full speed in 2.11 are acting as if graphics-2.6.33.33-tinycore.tcz hasn't been installed when run under TC3.

Please post Xorg.0.log and dmesg.

This little idiot should have looked at dmesg before posting about his problems. Turns out that I now need to load firmware.tcz before trying to use graphics-2.6.33.3-tinycore.tcz with my gfx chip.

EDIT: Actually, the firmware module seems to have corrected a couple of other little annoyances that had cropped up in TC3 that i hadn't experienced in 2.x.

[jur]

The work-around for the gtk-2 bug, requiring export GDK_NATIVE_WINDOWS=true no longer works very well in tc3.0a.

As soon as I right-click on a file in rox, and select open as text, and close rox, the previously set global variable GDK_NATIVE_WINDOWS is cleared.

I checked back into tc2.11.1 and the problem is not present there, so I report it here.

[^thehatsrule^]

Split out OT discussion to:
http://forum.tinycorelinux.net/index.php?topic=6167.0
http://forum.tinycorelinux.net/index.php?topic=6166.0

2) What is the strategy when it comes to 64 bits? Will 64 bit support only come with the base system and the extensions will stay 32 bit? If not, shouldn't the 64 bit extensions and 32 bit extensions be separated?

None of this is essential in any way, but I wanted to ask these before it's too late, because the design has been declared fix again.

Greetings,
SvOlli

See earlier threads, esp. alpha1 and alpha2.

More splits:
http://forum.tinycorelinux.net/index.php?topic=6192.0
http://forum.tinycorelinux.net/index.php?topic=6208.0

[curaga]

Base & extensions will stay 32-bit for the time being. The kernel already brings most benefits (ie. large amounts of ram). If someone needs to build a 64-bit app for speed reasons or whatever, the runtime libs are available separate from toolchain64.

[bmarkus]

Base & extensions will stay 32-bit for the time being. The kernel already brings most benefits (ie. large amounts of ram). If someone needs to build a 64-bit app for speed reasons or whatever, the runtime libs are available separate from toolchain64.

I'm not an expert 32 vs. 34 bit but recall few articles explaining cases when 64 bit apps run slower than 32 bit. Just a thought.

[SvOlli]

Base & extensions will stay 32-bit for the time being. The kernel already brings most benefits (ie. large amounts of ram). If someone needs to build a 64-bit app for speed reasons or whatever, the runtime libs are available separate from toolchain64.

That's exactly what I wanted to know. Thanks!

I'm not an expert 32 vs. 34 bit but recall few articles explaining cases when 64 bit apps run slower than 32 bit. Just a thought.

I discovered a case of the exact opposite: if your code does heavy float calculations you'll get ~50%(!) speed gain on the same machine. I tried it with oggenc.

[bigpcman]

I thought I understood the apps audit tool but maybe not. See the attached pic. The OnDemand part of the tool seems to be out of sync with the ".OnDemand" directory in /home/tc.

edit: I deleted the x11vnc entry out of .OnDemand and rebooted and now I get different results. See the second pic.

[roberts]

I thought I understood the apps audit tool but maybe not. See the attached pic. The OnDemand part of the tool seems to be out of sync with the ".OnDemand" directory in /home/tc.

edit: I deleted the x11vnc entry out of .OnDemand and rebooted and now I get different results. See the second pic.

One has nothing to do with the other. Any currently uninstalled extension, at the time of script invocation, is shown as available for select for ondemand.