WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: tinycore_v4.0rc1  (Read 3973 times)

Offline hiro

  • Hero Member
  • *****
  • Posts: 829
Re: tinycore_v4.0rc1
« Reply #15 on: September 14, 2011, 08:11:52 AM »
Impressive, but I expect multitasking to be a big factor here when measured in real time. Can you see how do their cpu times compare?

Offline floppy

  • Hero Member
  • *****
  • Posts: 577
Re: tinycore_v4.0rc1
« Reply #16 on: September 14, 2011, 11:00:42 AM »
Good speed. My first experience with MC 4.0.1 + Xorg7.4:
a) my bootcodes had to be changed from "hdx" to "sdx"; example my TCE from "hdd3" to "sdc3".. no big issue, only an information (I know.. but labels etc. takes too many characters on my boot code line)
b) the error message appear on the screen during boot "hwclock: can t open dev/misc/rtc no such file or directory. No big issue
c) all Icons of wbar are gone. In the end of the dmesg log file I have..
[   81.286884] wbar[2516]: segfault at 8 ip b73975f7 sp bfa1bc3c error 4 in libc-2.13.so[b7338000+132000]
[   81.944419] wbar[2524]: segfault at 8 ip b74b05f7 sp bffa711c error 4 in libc-2.13.so[b7451000+132000]
[  111.960914] wbar[2595]: segfault at 8 ip b74e95f7 sp bfebb8bc error 4 in libc-2.13.so[b748a000+132000]
[  113.606922] wbar[2599]: segfault at 8 ip b748e5f7 sp bffc4edc error 4 in libc-2.13.so[b742f000+132000]
[  116.151117] wbar[2603]: segfault at 8 ip b74eb5f7 sp bfa5238c error 4 in libc-2.13.so[b748c000+132000]
[  116.899406] wbar[2607]: segfault at 8 ip b74905f7 sp bf994f1c error 4 in libc-2.13.so[b7431000+132000]
[  169.002069] wbar[2712]: segfault at 8 ip b73605f7 sp bfbe28ac error 4 in libc-2.13.so[b7301000+132000]
They takes a long boot time.
AMD K6-IIIATZ 550MHz MB DFI K6xv3/+66
P4 HP DC7100 3GB 3GHz
Samsung NC10 boot from SD card port (via USB reader)
.. all TinyCore proofed

Offline Lee

  • Hero Member
  • *****
  • Posts: 570
    • My Core wiki user page
Re: tinycore_v4.0rc1
« Reply #17 on: September 14, 2011, 11:24:57 AM »
WRT wbar:

Did you get a fresh copy of wbar.tcz?  If so, it was updated around the end of August (see the .info) such that you have to fix your ~/.wbar to use "-pos" instead of "-p".  It segfaults if you don't.  That stumped me for a while, too, until I checked the .info file.  :)

Lee
32 bit core4.7.7, Xprogs, Xorg-7.6, wbar, jwm
PPR, data persistence through filetool.sh
USB Flash drive, one partition, ext2, grub4dos

Online bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 5026
    • My Community Forum
Re: tinycore_v4.0rc1
« Reply #18 on: September 14, 2011, 10:55:10 PM »
It is great to have cpufreq modules in the base. Tested on three different machines, one notebook with Intel Core Duo and two desktops with AMD dual CPUS-s where one doesn't support scaling. Proper drivers (acpi and powernow_k8) were loaded, ondemand governor were activated and scaling was working after boot without doing any extra.

I love this behavior.
Béla
Ham Radio callsign: HA5DI

"Amateur Radio: The First Technology-Based Social Network."

Online bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 5026
    • My Community Forum
Re: tinycore_v4.0rc1
« Reply #19 on: September 14, 2011, 11:02:22 PM »
mdadm.tcz is missing in TC4 repo.
Béla
Ham Radio callsign: HA5DI

"Amateur Radio: The First Technology-Based Social Network."

Online bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 5026
    • My Community Forum
Re: tinycore_v4.0rc1
« Reply #20 on: September 14, 2011, 11:36:09 PM »
raid modules are not part of base, therefore raid devices are not recognized during boot. Please considere adding them to base even if they are big (?). Using any live distro without instant raid support is a pain when used for disaster recovery.

To have raid moduls included is much more important than cpu frequency scaling. Even if size matters, move out cpufreq modules to extension as it is now but add raid.
Béla
Ham Radio callsign: HA5DI

"Amateur Radio: The First Technology-Based Social Network."

Offline maro

  • Hero Member
  • *****
  • Posts: 1228
Re: tinycore_v4.0rc1
« Reply #21 on: September 14, 2011, 11:43:06 PM »
bmarkus: I have not looked at the size of the RAID modules, but if they are big would not a more suitable place for such an add-on that probably only a few users need for disaster recovery be either in the 'multicore.iso' or in ones own re-mastered image?

Online bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 5026
    • My Community Forum
Re: tinycore_v4.0rc1
« Reply #22 on: September 14, 2011, 11:45:54 PM »
bmarkus: I have not looked at the size of the RAID modules, but if they are big would not a more suitable place for such an add-on that probably only a few users need for disaster recovery be either in the 'multicore.iso' or in ones own re-mastered image?

If something is not in base, you can make your own version always. However raid is a bit different. But lets see what others are saying. I made my vote :)
Béla
Ham Radio callsign: HA5DI

"Amateur Radio: The First Technology-Based Social Network."

Offline hiro

  • Hero Member
  • *****
  • Posts: 829
Re: tinycore_v4.0rc1
« Reply #23 on: September 15, 2011, 02:19:03 AM »
You have computers without USB? I'm curious...

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 7903
Re: tinycore_v4.0rc1
« Reply #24 on: September 15, 2011, 06:43:15 AM »
Wouldn't raid also need the mdadm userspace tools to be useful?

@hiro:
time loadcpufreq
real   0m 0.07s
user   0m 0.01s
sys   0m 0.00s

time loadcpufreq.sh
real   0m 1.02s
user   0m 0.66s
sys   0m 0.27s
The only barriers that can stop you are the ones you create yourself.

Online bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 5026
    • My Community Forum
Re: tinycore_v4.0rc1
« Reply #25 on: September 15, 2011, 07:02:15 AM »
Wouldn't raid also need the mdadm userspace tools to be useful?


normally mdadm is not needed, only to manage raid (add, remove devices, create arrays, etc., not on a daily bases.

Kernel detects raid devices at boot (if raid array supports autodetect which is the usual case) and next it can be mounted, etc on a usual way as any other block device.

Status can be displayed with 'cat /proc/mdstat'
Béla
Ham Radio callsign: HA5DI

"Amateur Radio: The First Technology-Based Social Network."

Offline gutmensch

  • Administrator
  • Hero Member
  • *****
  • Posts: 606
  • I can make it disappear, have no fear!
    • remembrance blog
Re: tinycore_v4.0rc1
« Reply #26 on: September 17, 2011, 03:01:33 AM »
RC1 is running great for me in VMWare Workstation, seems to be even a lot faster than 3.x, yeehaaw!

One problem appears (sometimes): udevadm settle from dhcp.sh doesn't quit, therefore no udhcpc starting for my network device... when I kill udevadm manually after startup, everything continues to work as expected. I can reproduce this with running udevadm settle myself, it's timeouting every second on polling some device (it seems) - attaching log, anyone else seeing this? Already loaded the scsi extension to make sure he's maybe not waiting for that (although I use an IDE hdd in VMWare).
« Last Edit: March 05, 2012, 07:26:32 AM by gutmensch »
If I seem unduly clear to you, you must have misunderstood what I said. (Alan Greenspan)