Tiny Core Linux
Tiny Core Base => Raspberry Pi => piCore Test Releases => Topic started by: bmarkus on July 22, 2016, 01:39:04 AM
-
Team Tiny Core is proud to announce immediate availability of the second 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.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.
-
Couple of systems upgraded PI3, B. No issues so far.
-
Couple of systems upgraded PI3, B. No issues so far.
Thanks!
-
Still no GUI available ...
I have few questions and I'm sorry I don't understand much even after reading the book for TinyCore.
My Raspberry Pi is 3B.
But I think that is armv7 yet the test versions being built are under armv6. To me its a huge deal to just know if builts for armv7 are not built because they are the same as armv6 or not? If they are not the same in source code... then whats the difference?
Other question is when I download and then of course make space for the second partition, as ext4 why is this second partition needed? would it not be better to just extend the fat partition instead? Also I know that the fat partition is loaded into ram and then no changes can be made unless you tell it not to load into ram or you mount it and then make changes. How can I make it not load into ram? is it a boot code ? or what should I do? I couldn't figure it out after reading the book.
-
Test versions work on ALL RPi boards. It is stated in release announcement. Read it!
FAT partition is not loaded to RAM.
Do not use the FAT partition (/dev/mmcblk0p1) other than boot. Keep as it is except customizing command line and config. It is not Linux-friendly and not a journaling file system.
-
Hi,
Is there a complete list of TCZs currently available for piCore 8 with brief descriptions? I'm looking for an image display utility such as fbi or qiv and I tried searching with TCE for keywords such as image/picture/viewer and only found libraries but not utilities.
Thanks,
-
You mean like:
http://tinycorelinux.net/8.x/armv6/tcz/
http://tinycorelinux.net/8.x/armv7/tcz/
-
Yes. Well, almost... I had already found those lists but unless you are already familiar with the extension names and know what they do it can be difficult finding what you need. I assume that using the keyword option in TCE searches through all the module descriptions as opposed to the search option which only looks at the titles. Correct?
So if don't find any extensions whose name I already know through the search option and don't find anything related to relevant words through the keyword option then it is safe to assume that there is no such extension available as yet?
Thanks,
-
The tags option searches through tags.db.gz, so if no viewers come up, there either are none, or they don't have that as a tag.
http://tinycorelinux.net/8.x/armv6/tcz/tags.db.gz
-
Hi Bela.
I have a problem with the Hifiberry DAC+ I2S DAC now. It simply isn't detected. Other I2S DACs are working fine (like the IQaudIO DAC).
dmesg show this
[ 3.929387] usb 1-1.4: Manufacturer: Logitech
[ 3.939819] input: Logitech USB Optical Mouse as /devices/platform/soc/20980000.usb/usb1/1-1/1-1.4/1-1.4:1.0/0003:046D:C077.0002/input/input1
[ 3.951710] hid-generic 0003:046D:C077.0002: input,hidraw1: USB HID v1.11 Mouse [Logitech USB Optical Mouse] on usb-20980000.usb-1.4/input0
[ 4.478277] zram: Added device: zram0
[ 5.061954] gpiomem-bcm2835 20200000.gpiomem: Initialised: Registers at 0x20200000
[ 5.063062] bcm2835-wdt 20100000.watchdog: Broadcom BCM2835 watchdog timer
[ 5.190068] bcm2708_i2c 20804000.i2c: BSC1 Controller at 0x20804000 (irq 77) (baudrate 100000)
[ 5.965491] zram0: detected capacity change from 0 to 105721856
[ 5.991300] random: mkswap urandom read with 106 bits of entropy available
[ 6.023712] Adding 103240k swap on /dev/zram0. Priority:-1 extents:1 across:103240k SSFS
[ 6.457730] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 8.021568] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 8.160854] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 9.178740] random: nonblocking pool is initialized
[ 14.575283] i2c /dev entries driver
[ 14.641538] uart-pl011 20201000.uart: no DMA platform data
[ 14.649628] snd-rpi-hifiberry-dacplus soc:sound: ASoC: CODEC DAI pcm512x-hifi not registered
[ 14.649670] snd-rpi-hifiberry-dacplus soc:sound: snd_soc_register_card() failed: -517
[ 15.915489] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[ 17.408363] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
tc@box:~$
lsmod shows:
tc@box:~$ lsmod
Module Size Used by Not tainted
snd_soc_pcm512x_i2c 2698 0
snd_soc_pcm512x 19804 1 snd_soc_pcm512x_i2c
snd_soc_hifiberry_dac 3027 0
snd_soc_hifiberry_dacplus 4954 0
snd_soc_bcm2835_i2s 6994 0
i2c_dev 6578 0
snd_soc_core 163972 4 snd_soc_pcm512x,snd_soc_hifiberry_dac,snd_soc_hifiberry_dacplus,snd_soc_bcm2835_i2s
regmap_i2c 4078 1 snd_soc_pcm512x_i2c
snd_pcm_dmaengine 5906 1 snd_soc_core
snd_pcm 95473 5 snd_soc_pcm512x,snd_soc_hifiberry_dac,snd_soc_hifiberry_dacplus,snd_soc_core,snd_pcm_dmaengine
snd_timer 22396 1 snd_pcm
snd 68368 3 snd_soc_core,snd_pcm,snd_timer
regmap_mmio 3728 1 snd_soc_bcm2835_i2s
squashfs 32160 17
evdev 11650 0
i2c_bcm2708 5740 0
bcm2835_wdt 4133 0
spi_bcm2835 7424 0
bcm2835_gpiomem 3823 0
zram 22461 1
zsmalloc 14329 1 zram
lz4_compress 3289 1 zram
uio_pdrv_genirq 3718 0
uio 10230 1 uio_pdrv_genirq
tc@box:~$
Do you have an idea of what is going on.
I will try to go back to previous piCore versions to spot where it was working.
Thanks
Steen
-
review of piCore8.0 beta 1
Same problem:
[ 5.979631] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 8.283470] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 8.827662] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 14.675762] snd-rpi-hifiberry-dacplus soc:sound: ASoC: CODEC DAI pcm512x-hifi not registered
[ 14.675802] snd-rpi-hifiberry-dacplus soc:sound: snd_soc_register_card() failed: -517
[ 14.722339] i2c /dev entries driver
[ 14.749060] snd-rpi-hifiberry-dacplus soc:sound: ASoC: CODEC DAI pcm512x-hifi not registered
[ 14.749098] snd-rpi-hifiberry-dacplus soc:sound: snd_soc_register_card() failed: -517
[ 14.758744] uart-pl011 20201000.uart: no DMA platform data
[ 15.896088] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[ 17.556191] random: nonblocking pool is initialized
[ 17.556443] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
tc@box:~$
-
piCore7.00 beta4 - here hifiberry DAC+ is found. But still it produce a similar error in dmesg (so this error is probably not important):
[ 15.295052] snd-rpi-hifiberry-dacplus sound: ASoC: CODEC DAI pcm512x-hifi not registered
[ 15.432086] snd-rpi-hifiberry-dacplus sound: snd_soc_register_card() failed: -517
[ 15.581995] i2c /dev entries driver
[ 15.596562] snd-rpi-hifiberry-dacplus sound: pcm512x-hifi <-> 20203000.i2s mapping ok
[ 15.637521] uart-pl011 20201000.uart: no DMA platform data
[ 17.803076] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[ 19.335928] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
[ 21.389657] random: nonblocking pool is initialized
lsmod:
tc@box:~$ lsmod
Module Size Used by Not tainted
i2c_dev 6686 0
snd_soc_hifiberry_dac 2911 0
snd_soc_pcm512x_i2c 2570 1
snd_soc_pcm512x 18073 1 snd_soc_pcm512x_i2c
snd_soc_hifiberry_dacplus 4736 0
snd_soc_bcm2708_i2s 7654 2
snd_soc_core 168317 4 snd_soc_hifiberry_dac,snd_soc_pcm512x,snd_soc_hifiberry_dacplus,snd_soc_bcm2708_i2s
snd_pcm_dmaengine 5794 1 snd_soc_core
regmap_i2c 3346 1 snd_soc_pcm512x_i2c
snd_pcm 93037 5 snd_soc_hifiberry_dac,snd_soc_pcm512x,snd_soc_hifiberry_dacplus,snd_soc_core,snd_pcm_dmaengine
regmap_mmio 3556 1 snd_soc_bcm2708_i2s
snd_timer 24444 1 snd_pcm
snd_compress 8861 1 snd_soc_core
clk_hifiberry_dacpro 2682 1
snd 68803 4 snd_soc_core,snd_pcm,snd_timer,snd_compress
i2c_bcm2708 6208 0
spi_bcm2835 7880 0
bcm2835_gpiomem 3703 0
bcm2835_rng 2207 0
uio_pdrv_genirq 3670 0
uio 10078 1 uio_pdrv_genirq
aplay -l
tc@box:~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sndrpihifiberry [snd_rpi_hifiberry_dacplus], device 0: HiFiBerry DAC+ HiFi pcm512x-hifi-0 []
Subdevices: 1/1
Subdevice #0: subdevice #0
tc@box:~$
so in piCore version7 the Hifiberry DAC is found but in version8 it is not found.
In both tests alsa.tcz is installed via tce command.
-
Hi sbp
From the version that works:
[ 15.596562] snd-rpi-hifiberry-dacplus sound: pcm512x-hifi <-> 20203000.i2s mapping ok
Is it possible i2s got disabled in the newer versions?
-
Hi Steen
I don't have such board so can't test. Kernel config related to sound in 8.0 is the same as Raspbian. If it Works there look for differences in config.txt
Next week will be beta5 with 4.4.17 kernel but expect no deifference.
Béla
-
Bela,
I don't have the boards to test either, and not sure yet if it will fix the problem. But the alsa-modules-KERNEL extensions are missing the module.
drivers/clk/clk-hifiberry-dacpro.ko
Paul
-
Hi Paul
Thanks. I can't access my RPi in next days but will check it next week.
-
Hi Bela.
I tested the idea Paul provided - and it fixed the issue. Now my HifiBerry DAC is loading fine.
So the alsa-modules-KERNEL.tcz is missing the module "/usr/local/lib/modules/4.4.15-piCore+/kernel/drivers/clk/clk-hifiberry-dacpro.ko"
-
Thanks I will fix it in next beta.
-
Hi,
I just installed it on my rpi3, the nozswap option doesn't work.
Thanks.
-
Hi,
I just installed it on my rpi3, the nozswap option doesn't work.
Thanks.
works fine here. Make sure you are editing the correct command line
cmdline.txt <-----for all rpi's except the rpi3
cmdline3.txt <-----for the rpi3
-
Thanks !
-
Hi Bela.
I tested the idea Paul provided - and it fixed the issue. Now my HifiBerry DAC is loading fine.
So the alsa-modules-KERNEL.tcz is missing the module "/usr/local/lib/modules/4.4.15-piCore+/kernel/drivers/clk/clk-hifiberry-dacpro.ko"
Missing module is added to alsa-modules-KERNEL.tcz for 4.4.15, update your system.
-
Thanks.
With this version 8.0beta4, I can install mpd + upmpdcli ( http://www.lesbonscomptes.com/upmpdcli/ ) + shairport_sync to create a UPnP player and AirPlay.
-
Hi Béla,
Any chance of loading rpi-vc.tcz into the piCore-8.0 repository.
thanks
Greg
-
Bela,
I can pack the rpi-vc stuff to help out if you would like. For the TC extensions, do you just download and pack from the prebuilt binaries, or do you compile natively on a tc build from the userland source.
Paul
-
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