WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Recent Posts

Pages: [1] 2 3 ... 10
1
dCore X86 / Re: sce-update: RAM-usage
« Last post by sm8ps on August 24, 2016, 10:59:07 PM »
This is normal behavior for all processes in Linux that use RAM.  Unused RAM is used, and then kept in cache until another process needs it or the cache is cleared, "cache-clear" in Tinycore will do it.  The warning given by sce-import or sce-update in regards to RAM is on the safe side and is not considering cached RAM or swap space, and can usually be ignored.   Hard drive or other storage space is another situation and the warning should be heeded there.

I don't see sce-update occupying more RAM on my desktop system after already browsing the web and other RAM consuming activities, as cached RAM that is no longer needed is used instead of empty or free RAM.  Below is before and after the cache-clear command:

EDIT: I don't see the checking part of sce-update use much RAM, of course if the -r option is used then .deb unpacking happens in RAM, the total of which is the size of the uncompressed contents of what will be in the resulting SCE.

Thanks for the briefing about the kernel's handling of RAM usage! I must confess that I did not have that kind oversight before. It makes sense now.

Still the warning about insufficient RAM is troubling, and if it can usually be disregarded then it should not really appear, should it? I see that considering swap space is not desirable but the way I understand your explanations, cached RAM should be considered. Is there a reasonably simple way to make ''sce-update'' take that into account? I think that would be helpful here.

I have another system in about the same state that I could use for testing purposes. My approach was watching ''free -h'' while launch ''sce-update -arns'' was running. Is there any more concise way of testing RAM usage?

I always use the Unix sync command to write out, don't know if this could be some tips on this.
Thanks for the tip! Though, I do not think that disk cache is the real issue here but maybe I am wrong. Does anybody know better?
2
piCore Test Releases / Re: piCore-8.0beta5
« Last post by Paul_123 on August 24, 2016, 08:05:51 PM »
Try beta5 and the current VC set.

I pulled the vc tonight to pack, so it should line up with the kernel you pulled.   So I'll give it a test tomorrow. 

The other vc binaries I tested worked fine.
3
piCore Test Releases / Re: piCore-8.0beta5
« Last post by bmarkus on August 24, 2016, 08:02:47 PM »
Try beta5 and the current VC set.
4
piCore Test Releases / Re: piCore-8.0beta5
« Last post by Paul_123 on August 24, 2016, 07:56:22 PM »
Bela,

I did not try this yet with this beta that you just posted,  I was typing this as you locked the other thread......

I was testing the userspace binaries after I packed them.   I wanted to play with loading and removing overlays after boot.

Code: [Select]
tc@piCorePlayer:/mnt/mmcblk0p1/overlays$ sudo dtoverlay -a -v -d /mnt/mmcblk0p1/overlays
run_cmd: mount -t configfs none '/config/device-tree'
mount: mount point /config/device-tree does not exist
* Failed to mount configfs - 2
tc@piCorePlayer:/mnt/mmcblk0p1/overlays$ sudo mkdir /config/device-tree
tc@piCorePlayer:/mnt/mmcblk0p1/overlays$ sudo dtoverlay -a -v -d /mnt/mmcblk0p1/overlays
* configfs overlays folder not found - incompatible kernel

found very little with a quick google search....but found references to mounting the configfs manually

Code: [Select]
sudo mount -t configfs none /sys/kernel/config
sudo dtoverlay -a -d /mnt/mmcblk0p1/overlays
<list of all overlays is printed>

dtoverlay now runs, but does not show any overlays loaded. 
5
piCore Test Releases / piCore-8.0beta5
« Last post by bmarkus on August 24, 2016, 07:46:32 PM »
Team Tiny Core is proud to announce immediate availability of the fifth beta release of the piCore-8.0 edition.

With this release kernel is frozen, it will be used in final version (except really serious issue found).

8.0beta5

- kernel updated to 4.4.19, now supports CM3 Compute module, not yet available to buy
- firmware updated to 20160823
- GCC updated to 6.2.0
- GLIBC updated to 2.24
- util-linux updated to 2.28.1


8.0beta4

- kernel updated to 4.4.15
- firmware updated to 20160715
- MicroPython updated to 1.8.2-19


8.0beta3

- kernel updated to 4.4.14
- firmware updated to 20160626
- MicroPython updated to 1.8.1-90
- added ZBUD=y to kernel config
- on-board audio enabled by default
- VC I2C disabled by default
- serial console works on RPi3, using /dev/ttyS0, all other boards /dev/ttyAMA0
- serial console terminal emulation change from VT100 to linux


8.0beta2

- kernel updated to 4.4.13
- e2fsprogs updated to 1.43.1
- MicroPython updated
- RPi firmware updated to 20160613


8.0beta1

- kernel 4.4.11
- glibc 2.23
- BusyBox 1.24.2
- util-linux 2.28
- e2fsprogs 1.43
- MicroPython 1.8
- Perl 5.24
- GCC 6.1

TC scripts also updated to latest common base. Except ncurses which doesn't build properly all packages in the repo updated and rebuilt using the new toolchain, not just copied over from 6.x/7.x repos. Dependencies revised, may be different to previous versions. It means limited number of packages in the repo, e.g. Xorg and graphical stuff are missing.

Only one SD card image available, it works on all RPi boards. Download location:

http://tinycorelinux.net/8.x/armv6/test_releases/

Please try it and share your experience, bugs found, etc.
6
TCE Talk / Re: pcre symlinks
« Last post by bmarkus on August 24, 2016, 04:38:35 PM »
Dave

be more specific. Which architecture and which version are you talking about? Please attach warnings you are referring.
7
TCE Talk / pcre symlinks
« Last post by wysiwyg on August 24, 2016, 09:55:38 AM »
Good afternoon all!  I have been playing around with some of the packages for TC and noticed several warnings from the pcre package - the libs are not symlinked (which ldconfig complains about).  I know this is true for the 32bit, but not sure about other arch's.

Dave
8
Release Candidates / Re: Announcements
« Last post by Jason W on August 24, 2016, 08:49:00 AM »
Fixing exit status of 1 upon a successful sce-import session.

modified:   usr/bin/deb2sce
modified:   usr/bin/sce-import

http://tinycorelinux.net/dCore/x86/release_candidates/
9
dCore X86 / Re: Wifi connection impossible after sce-update.
« Last post by sbaguz on August 24, 2016, 07:38:06 AM »
@Misalf:
Yes, I know: I was also thinking about adding echo wext | sudo tee /etc/sysconfig/wifi-wpadrv to bootlocal.sh, but this would haven't been a real solution, not having worked on the cause of the issue...  ;)

@Jason:
Thanks: updating the wireless packages did the trick!
10
piCore Test Releases / Re: piCore-8.0beta4
« Last post by bmarkus on August 24, 2016, 07:03:34 AM »
Hi Paul

thanks please do, pack current GitHub version I mean binaries. I changed locations moved from /opt to /usr/local for convenience.

Béla
Pages: [1] 2 3 ... 10