Ceph (last release) on aarch64
by Pierre-Francois RENARD
Hello all,
I am trying to build a ceph cluster based on 4 raspberry3B+.
Following the official CEPH documentation is a dead end as packages are only available for readhat/centos and not fedora ! I tried to used the el7 repository but the are conflicts and lacks with fedora repos.
Did I miss something ?
I am now trying to compile from sources.
it is still ongoing ( 16% after 24h !)
I am considering cross compilation from a X86_64 hosts but I cannot find any recent ( and probably uptodate ) documentation, any clue on that ?
Thanks
Fox
5 years, 1 month
Re: [Test-Announce] Fedora 30 Candidate Beta-1.4 Available Now!
by Adam Williamson
On Thu, 2019-03-21 at 01:36 +0000, rawhide(a)fedoraproject.org wrote:
> According to the schedule [1], Fedora 30 Candidate Beta-1.4 is now
> available for testing. Please help us complete all the validation
> testing! For more information on release validation testing, see:
> https://fedoraproject.org/wiki/QA:Release_validation_test_plan
>
> Test coverage information for the current release can be seen at:
> https://www.happyassassin.net/testcase_stats/30
>
> You can see all results, find testing instructions and image download
> locations, and enter results on the Summary page:
>
> https://fedoraproject.org/wiki/Test_Results:Fedora_30_Beta_1.4_Summary
>
> The individual test result pages are:
>
> https://fedoraproject.org/wiki/Test_Results:Fedora_30_Beta_1.4_Installation
> https://fedoraproject.org/wiki/Test_Results:Fedora_30_Beta_1.4_Base
> https://fedoraproject.org/wiki/Test_Results:Fedora_30_Beta_1.4_Server
> https://fedoraproject.org/wiki/Test_Results:Fedora_30_Beta_1.4_Cloud
> https://fedoraproject.org/wiki/Test_Results:Fedora_30_Beta_1.4_Desktop
> https://fedoraproject.org/wiki/Test_Results:Fedora_30_Beta_1.4_Security_Lab
>
> All Beta priority test cases for each of these test pages [2] must
> pass in order to meet the Beta Release Criteria [3].
>
> Help is available on #fedora-qa on irc.freenode.net [4], or on the
> test list [5].
Hey folks!
So, unfortunately we had some trouble getting a candidate build done,
but now we have one. The go/no-go meeting is on Thursday at 17:00 UTC -
that's in about 11 hours. Obviously time is tight to do the testing,
but if folks could help test as much stuff as possible, that'd be
great.
We do have one outstanding blocker bug, but there's a chance it'll get
downgraded at the meeting, so it'd be great if we could complete the
testing for all Beta tests on this compose. If there isn't enough time,
though, no-one will blame us :)
Thanks everyone!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
5 years, 1 month
how to make a working f28 sd card for odroid-hc2 ?
by Torbjorn Jansson
Hello
for a while now i have been struggling to create a set of steps to make a
successfully bootable fedora 28 image for my odroid hc2 computers.
the reason for this is several, but main one is to have all gluster related
packaged available like the samba vfs modules and iscsi related packages for
gluster that is missing from the ubuntu images.
plus i prefer fedora.
all i get is a sd card that boots but then hangs on initial setup and if i try
to work around that by disabling it then boot takes maybe 5-10 minutes at least
with failing services (probably those that depend on network) and when i
finally get to a login prompt root doesn't work
here is my step by step instructions so far that's not quite working:
(this is done from a fedora 28 host)
1: first install needed packages
dnf install arm-image-installer-2.5-1.fc28.noarch
dnf install uboot-images-armv7-2018.03-6.fc28.noarch
2: get image and install it to sd card
fedora-arm-image-installer --target=none
--image=Fedora-Minimal-armhfp-28-1.1-sda.raw.xz --resizefs --norootpass
--media=/dev/sdf --args "rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd
cpuidle.off=1 no_bL_switcher console=tty1 console=ttySAC2,115200n8"
(sdf in this case is my sd card)
3: fix the missing dtb file
mkdir /tmp/sd
mount -t auto /dev/sdf2 /tmp/sd
cd /tmp/sd/dtb
ln -s exynos5422-odroidxu4.dtb exynos5422-odroidunknown.dtb
umount /tmp/sd
4: make it boot by running sd_fusing
mkdir sd_fusing; cd sd_fusing
wget
https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd...
\
https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd...
\
https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd...
\
https://raw.githubusercontent.com/hardkernel/u-boot/odroidxu4-v2017.05/sd...
chmod a+x sd_fusing.sh
cp /usr/share/uboot/odroid-xu3/u-boot.bin .
./sd_fusing.sh /dev/sdf
ok so now comes the problems
at this stage i have a bootable image but it gets stuck, most likely on initial
setup that never shows up.
the thing is, it is not locked up because if i plug in an usb device i get a
few lines on the serial console so kernel is still working but boot is stuck.
last few lines on serial console is something like:
Starting firewalld - dynamic firewall daemon...
Starting Initial Setup configuration program...
then some stuff related to usb & my disk
then on first boot a few lines related to OpenSSH key generation
rebooting hangs at same place with exception of SSH keys.
to get a bit further i can mount the root filesystem manually on my other
computer and remove the following two files:
rm /etc/systemd/system/graphical.target.wants/initial-setup.service
rm /etc/systemd/system/multi-user.target.wants/initial-setup.service
this gets rid of the initial setup but then i get a whole bunch of services
failing and boot being really really slow, it takes probably 10-15 minutes for
everything to time out and get to the logon prompt.
when i get it root doesn't work.
this is where i kind of gave up.
i know i somehow managed to get a bootable image several months ago, but i'm
not sure if i then had to manually set root password by editing passwd or
shadow before trying to boot.
things on my wish list for this board:
easier installation and updated packages that work.
for example arm-image-installer with a board definition for odroid.
may be usefull even if we have to run sd_fusing manualy after anyway, possibly
with a text saying so.
this also would help to make --addconsole work
uboot that recognized hc2 so it loads the right file
dtb file for hc2, one that works and is appropriate.
5 years, 1 month
Raspberry Pi 3B+ fails to boot aarch64 image
by Jan Kratochvil
Hello,
sorry it may not be really Fedora specific but all images fail to boot for me
except for the plain 32-bit Raspbian.
Fedora 29 aarch64 Workstation fails on:
https://www.jankratochvil.net/t/rpi3fail.jpg
[FAILED] Failed to start Avahi mDNS/DNS-SD Stack.
...
[FAILED] Failed to start Modem Manager
etc.
No graphical screen ever appears.
Fedora 29 arm also failed, I do not remember now how.
Various 64-bit Debian-derivatives also fail to boot.
Tried both MicroSD 16GB 23MB/s card and USB flashdisk 16GB 16MB/s.
Using official Raspberry power supply with their logo 5.1V 2.5A.
Any idea?
Thanks,
Jan
5 years, 1 month
Fedora-Xfce-armhfp-30-20190312.n.0-sda crashed last night
by Robert Moskowitz
The last messages last night were:
Mar 12 21:21:54 localhost systemd[1]: Started dnf makecache.
Mar 12 21:21:54 localhost audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=dnf-makecache comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=success'
Mar 12 21:21:54 localhost audit[1]: SERVICE_STOP pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=dnf-makecache comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=success'
Mar 12 21:21:50 localhost systemd[1]: Starting dnf makecache...
Mar 12 21:21:54 localhost dnf[32080]: Metadata cache refreshed recently.
Mar 12 21:21:54 localhost systemd[1]: dnf-makecache.service: Succeeded.
Mar 12 21:21:54 localhost systemd[1]: Started dnf makecache.
Mar 12 21:21:54 localhost audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=dnf-makecache comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=success'
Mar 12 21:21:54 localhost audit[1]: SERVICE_STOP pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0
msg='unit=dnf-makecache comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=success'
Then, some point later, a drive problem and crash. note the drive is a
Kingston SSD:
scanning bus for devices...
Device 0: (0:0) Vendor: ATA Prod.: KINGSTON SV300S3 Rev: 541A
Type: Hard Disk
Capacity: 228936.5 MB = 223.5 GB (468862128 x 512)
Here is what appeared on the console (note I have booted the system back
up this morning):
# [49033.321960] EXT4-fs error (device sda3): ext4_find_entry:1438:
inode #6412: comm kworker/u4:3: reading directory lblock 0
[49033.333133] EXT4-fs error (device sda3) in
ext4_reserve_inode_write:5903: Journal has aborted
[49033.354708] EXT4-fs error (device sda3): ext4_journal_check_start:61:
Detected aborted journal
[49033.363535] EXT4-fs (sda3): Remounting filesystem read-only
[49033.375324] EXT4-fs (sda3): ext4_writepages: jbd2_start: 4054 pages,
ino 262658; err -30
[49033.391407] EXT4-fs error (device sda3): ext4_find_entry:1438: inode
#6412: comm kworker/u4:0: reading directory lblock 0
[49033.410833] EXT4-fs error (device sda3): ext4_find_entry:1438: inode
#6412: comm kworker/u4:0: reading directory lblock 0
[49033.429168] EXT4-fs error (device sda3): ext4_find_entry:1438: inode
#6412: comm kworker/u4:0: reading directory lblock 0
[49033.447931] EXT4-fs error (device sda3): ext4_find_entry:1438: inode
#6412: comm kworker/u4:0: reading directory lblock 0
[49033.467215] EXT4-fs error (device sda3): ext4_find_entry:1438: inode
#6412: comm kworker/u4:0: reading directory lblock 0
[49033.485748] EXT4-fs error (device sda3): ext4_find_entry:1438: inode
#6412: comm kworker/u4:0: reading directory lblock 0
[49033.504649] EXT4-fs error (device sda3): ext4_find_entry:1438: inode
#6412: comm kworker/u4:0: reading directory lblock 0
[49033.522691] EXT4-fs error (device sda3): ext4_find_entry:1438: inode
#6412: comm kworker/u4:0: reading directory lblock 0
[49038.328845] EXT4-fs error (device sda3): ext4_find_entry:1438: inode
#6412: comm kworker/u4:0: reading directory lblock 0
[49038.348733] EXT4-fs error (device sda3): ext4_find_entry:1438: inode
#6412: comm kworker/u4:0: reading directory lblock 0
[49038.370459] EXT4-fs error (device sda3): ext4_find_entry:1438: inode
#6412: comm kworker/u4:0: reading directory lblock 0
[49038.386797] EXT4-fs error (device sda3): ext4_find_entry:1438: inode
#6412: comm kworker/u4:0: reading directory lblock 0
[49038.404675] EXT4-fs error (device sda3): ext4_find_entry:1438: inode
#6412: comm kworker/u4:0: reading directory lblock 0
[49038.419659] EXT4-fs error (device sda3): ext4_find_entry:1438: inode
#6412: comm kworker/u4:3: reading directory lblock 0
[49038.431818] EXT4-fs error (device sda3): ext4_find_entry:1438: inode
#6412: comm kworker/u4:0: reading directory lblock 0
[49038.452657] EXT4-fs error (device sda3): ext4_find_entry:1438: inode
#6412: comm kworker/u4:0: reading directory lblock 0
[49038.465314] EXT4-fs error (device sda3): ext4_find_entry:1438: inode
#6412: comm kworker/u4:2: reading directory lblock 0
[49038.477341] EXT4-fs error (device sda3): ext4_find_entry:1438: inode
#6412: comm kworker/u4:1: reading directory lblock 0
[49043.336333] EXT4-fs error (device sda3): ext4_find_entry:1438: inode
#6412: comm kworker/u4:1: reading directory lblock 0
[49043.355629] EXT4-fs error (device sda3): ext4_find_entry:1438: inode
#6412: comm kworker/u4:1: reading directory lblock 0
[49043.372138] EXT4-fs error (device sda3): ext4_find_entry:1438: inode
#6412: comm kworker/u4:1: reading directory lblock 0
[49043.390238] EXT4-fs error (device sda3): ext4_find_entry:1438: inode
#6412: comm kworker/u4:1: reading directory lblock 0
[49043.403614] EXT4-fs error (device sda3): ext4_find_entry:1438: inode
#6412: comm kworker/u4:1: reading directory lblock 0
[49043.420805] EXT4-fs error (device sda3): ext4_find_entry:1438: inode
#6412: comm kworker/u4:1: reading directory lblock 0
[49043.436772] EXT4-fs error (device sda3): ext4_find_entry:1438: inode
#6412: comm kworker/u4:1: reading directory lblock 0
[49043.449376] EXT4-fs error (device sda3): ext4_find_entry:1438: inode
#6412: comm kworker/u4:1: reading directory lblock 0
[49043.461505] EXT4-fs error (device sda3): ext4_find_entry:1438: inode
#6412: comm kworker/u4:1: reading directory lblock 0
[49043.476116] EXT4-fs error (device sda3): ext4_find_entry:1438: inode
#6412: comm kworker/u4:1: reading directory lblock 0
[49078.110404] EXT4-fs error (device sda3): ext4_find_entry:1438: inode
#6412: comm kworker/u4:3: reading directory lblock 0
[49078.144537] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x0000000b
[49078.152223] CPU: 1 PID: 1 Comm: systemd Tainted: G C
5.0.0-300.fc30.armv7hl #1
[49078.160743] Hardware name: Allwinner sun7i (A20) Family
[49078.165994] [<c0312560>] (unwind_backtrace) from [<c030c9a0>]
(show_stack+0x18/0x1c)
[49078.173740] [<c030c9a0>] (show_stack) from [<c0b29a00>]
(dump_stack+0x80/0x9c)
[49078.180966] [<c0b29a00>] (dump_stack) from [<c0350750>]
(panic+0xe8/0x2d0)
[49078.187844] [<c0350750>] (panic) from [<c0355444>] (do_exit+0x5d0/0xaec)
[49078.194543] [<c0355444>] (do_exit) from [<c0355a00>]
(do_group_exit+0x64/0xe0)
[49078.201764] [<c0355a00>] (do_group_exit) from [<c0360238>]
(get_signal+0x230/0x718)
[49078.209418] [<c0360238>] (get_signal) from [<c030c108>]
(do_work_pending+0xcc/0x4c0)
[49078.217158] [<c030c108>] (do_work_pending) from [<c030106c>]
(slow_work_pending+0xc/0x20)
[49078.225324] Exception stack(0xef115fb0 to 0xef115ff8)
[49078.230372] 5fa0: be2c6fc0
be2c719c 00000080 b6cc5d04
[49078.238543] 5fc0: be2c7198 00000000 b6f62000 00000011 ffffffff
00000000 005df204 be989b9c
[49078.246713] 5fe0: 00000010 be2c6fb0 005abdb4 b6e432bc a00e0010 ffffffff
[49078.253334] CPU0: stopping
[49078.256053] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G C
5.0.0-300.fc30.armv7hl #1
[49078.264737] Hardware name: Allwinner sun7i (A20) Family
[49078.269969] [<c0312560>] (unwind_backtrace) from [<c030c9a0>]
(show_stack+0x18/0x1c)
[49078.277710] [<c030c9a0>] (show_stack) from [<c0b29a00>]
(dump_stack+0x80/0x9c)
[49078.284931] [<c0b29a00>] (dump_stack) from [<c030fff0>]
(handle_IPI+0x1ac/0x348)
[49078.292324] [<c030fff0>] (handle_IPI) from [<c03025bc>]
(gic_handle_irq+0x80/0x88)
[49078.299889] [<c03025bc>] (gic_handle_irq) from [<c0301a0c>]
(__irq_svc+0x6c/0x90)
[49078.307361] Exception stack(0xc1201f38 to 0xc1201f80)
[49078.312408]
1f20: 00000000
00989c68
[49078.320578] 1f40: 00000000 c031d820 00000000 00000000 c1200000
00000000 c1208df4 410fc074
[49078.328748] 1f60: c1201f90 c1208e3c c1203d00 c1201f88 c03093b8
c0309394 600f0013 ffffffff
[49078.336922] [<c0301a0c>] (__irq_svc) from [<c0309394>]
(arch_cpu_idle+0x24/0x54)
[49078.344317] [<c0309394>] (arch_cpu_idle) from [<c037ec68>]
(do_idle+0x10c/0x230)
[49078.351711] [<c037ec68>] (do_idle) from [<c037efe0>]
(cpu_startup_entry+0x20/0x28)
[49078.359280] [<c037efe0>] (cpu_startup_entry) from [<c1000e8c>]
(start_kernel+0x3fc/0x490)
[49078.367460] ---[ end Kernel panic - not syncing: Attempted to kill
init! exitcode=0x0000000b ]---
[49078.376359] ------------[ cut here ]------------
[49078.380978] WARNING: CPU: 1 PID: 1 at kernel/sched/core.c:1181
set_task_cpu+0xfc/0x248
[49078.388882] Modules linked in: ip6t_rpfilter ip6t_REJECT
nf_reject_ipv6 xt_conntrack ebtable_nat ip6table_nat nf_nat_ipv6
ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat_ipv4
nf_nat iptable_mangle iptable_raw iptable_security nf_conntrack
nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip_set nfnetlink ebtable_filter
ebtables ip6table_filter ip6_tables vfat fat sun4i_codec rc_cec
snd_soc_core sun4i_backend ac97_bus snd_pcm_dmaengine axp20x_pek snd_seq
snd_seq_device axp20x_adc snd_pcm joydev snd_timer sun4i_gpadc_iio
sunxi_cedrus(C) snd v4l2_mem2mem sun4i_ts nvmem_sunxi_sid soundcore
videobuf2_dma_contig videobuf2_memops sunxi_wdt sunxi_cir videobuf2_v4l2
videobuf2_common videodev sun4i_drm_hdmi media sun4i_drm sun4i_frontend
leds_gpio cpufreq_dt lz4 lz4_compress zram dm_multipath axp20x_battery
axp20x_ac_power axp20x_usb_power industrialio axp20x_regulator
pinctrl_axp209 mmc_block sun4i_tcon sun8i_tcon_top drm_kms_helper
dwmac_sunxi syscopyarea sysfillrect stmmac_platform
[49078.389026] sysimgblt stmmac fb_sys_fops drm sunxi phy_generic
sun4i_gpadc musb_hdrc i2c_mv64xxx rtc_sunxi ahci_sunxi libahci_platform
sun4i_ss des_generic ehci_platform udc_core ohci_platform sunxi_mmc
phy_sun4i_usb sun4i_dma sunrpc
[49078.496659] CPU: 1 PID: 1 Comm: systemd Tainted: G C
5.0.0-300.fc30.armv7hl #1
[49078.505168] Hardware name: Allwinner sun7i (A20) Family
[49078.510395] [<c0312560>] (unwind_backtrace) from [<c030c9a0>]
(show_stack+0x18/0x1c)
[49078.518134] [<c030c9a0>] (show_stack) from [<c0b29a00>]
(dump_stack+0x80/0x9c)
[49078.525356] [<c0b29a00>] (dump_stack) from [<c03505b4>]
(__warn+0xdc/0xf8)
[49078.532229] [<c03505b4>] (__warn) from [<c0350978>]
(warn_slowpath_null+0x40/0x4c)
[49078.539794] [<c0350978>] (warn_slowpath_null) from [<c0378a14>]
(set_task_cpu+0xfc/0x248)
[49078.547966] [<c0378a14>] (set_task_cpu) from [<c03797a4>]
(try_to_wake_up+0x308/0x49c)
[49078.555878] [<c03797a4>] (try_to_wake_up) from [<c03c9264>]
(hrtimer_wakeup+0x28/0x30)
[49078.563790] [<c03c9264>] (hrtimer_wakeup) from [<c03c97c4>]
(__hrtimer_run_queues+0x190/0x2dc)
[49078.572394] [<c03c97c4>] (__hrtimer_run_queues) from [<c03ca0cc>]
(hrtimer_interrupt+0x118/0x2b8)
[49078.581262] [<c03ca0cc>] (hrtimer_interrupt) from [<c0991898>]
(arch_timer_handler_phys+0x30/0x38)
[49078.590220] [<c0991898>] (arch_timer_handler_phys) from [<c03b4788>]
(handle_percpu_devid_irq+0xbc/0x22c)
[49078.599783] [<c03b4788>] (handle_percpu_devid_irq) from [<c03af66c>]
(generic_handle_irq+0x24/0x34)
[49078.608822] [<c03af66c>] (generic_handle_irq) from [<c03afd38>]
(__handle_domain_irq+0xa0/0xb8)
[49078.617514] [<c03afd38>] (__handle_domain_irq) from [<c0302598>]
(gic_handle_irq+0x5c/0x88)
[49078.625858] [<c0302598>] (gic_handle_irq) from [<c0301a0c>]
(__irq_svc+0x6c/0x90)
[49078.633330] Exception stack(0xef115e60 to 0xef115ea8)
[49078.638379] 5e60: 00000055 2e56b000 c123ce90 c123ce90 c134c198
00000000 00000000 00000000
[49078.646549] 5e80: ef115ed8 00000000 ef115f64 00000504 00000000
ef115eb0 c0350864 c0350868
[49078.654714] 5ea0: 60070013 ffffffff
[49078.658205] [<c0301a0c>] (__irq_svc) from [<c0350868>]
(panic+0x200/0x2d0)
[49078.665078] [<c0350868>] (panic) from [<c0355444>] (do_exit+0x5d0/0xaec)
[49078.671775] [<c0355444>] (do_exit) from [<c0355a00>]
(do_group_exit+0x64/0xe0)
[49078.678993] [<c0355a00>] (do_group_exit) from [<c0360238>]
(get_signal+0x230/0x718)
[49078.686643] [<c0360238>] (get_signal) from [<c030c108>]
(do_work_pending+0xcc/0x4c0)
[49078.694380] [<c030c108>] (do_work_pending) from [<c030106c>]
(slow_work_pending+0xc/0x20)
[49078.702545] Exception stack(0xef115fb0 to 0xef115ff8)
[49078.707591] 5fa0: be2c6fc0
be2c719c 00000080 b6cc5d04
[49078.715761] 5fc0: be2c7198 00000000 b6f62000 00000011 ffffffff
00000000 005df204 be989b9c
[49078.723929] 5fe0: 00000010 be2c6fb0 005abdb4 b6e432bc a00e0010 ffffffff
[49078.730534] ---[ end trace 1e9429e735db4f06 ]---
5 years, 1 month
dnf error - Fedora-Xfce-armhfp-30-20190312.n.0-sda
by Robert Moskowitz
I did a dnf update successfully. Then a 'dnf list > dnf.lst' to get the
packages available. Then tried to install tigervnc-server:
# dnf install tigervnc-server
Fedora Modular 30 - armhfp 0.0 B/s | 0 B 00:00
Failed to synchronize cache for repo 'fedora-modular'
Error: Failed to synchronize cache for repo 'fedora-modular'
5 years, 1 month
Initial testing of Fedora-Xfce-armhfp-30-20190312.n.0-sda
by Robert Moskowitz
This is my first bootup of F30-arm-Xfce.
I am running on a Cubieboard2, using the F29 uboot. /boot and / are on
the sata drive, per my regular Cubie setup.
Setting up monitor and keyboard for the test is a bit of a pain, my KVM
does not support HDMI, so I use a real keyboard and mouse and disconnect
my monitor from my work notebook for first boot and initial testing. I
hope to at least use the KVM keyboard/mouse for next testing.
I am please to observe that the video handling is snappier than it was
with F29-Xfce. The 1st config GUI was actually bearable, and when I
selected items like setting the root password, feeling that a shade was
being pulled up was less. It actually went up much faster than back in
my F29 testing.
The Xfce desktop itself is reasonable speed-wise. So what ever was done
with the video handling (I remember comments about the Cubie GPU and
GTK3), thanks!
Still no Xfce GUI date/time applet. This is an Xfce issue, and I will
take it to their list. Again.
Next to try the KVM, then see if I can get VNC working...
More comments as time allows.
5 years, 1 month
Re: Banana Pi-R1 stabil
by Gerhard Wiesinger
On 07.03.2019 16:31, Maxime Ripard wrote:
> On Wed, Mar 06, 2019 at 09:03:00PM +0100, Gerhard Wiesinger wrote:
>> while true; do echo "========================================"; echo -n
>> "CPU_FREQ0: "; cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq;
>> echo -n "CPU_FREQ1: "; cat
>> /sys/devices/system/cpu/cpu1/cpufreq/cpuinfo_cur_freq; sleep 1; done&
>> ./stress/cpuburn-a7
> Run cpufreq-ljt-stress-test
>
On ALL Banana Pi R1 I have and Banana Pro OK, see below
Ciao,
Gerhard
./cpufreq-ljt-stress-test
The cjpeg and djpeg tools from libjpeg-turbo are not found.
Trying to download and compile them.
Downloading libjpeg-turbo-1.3.1.tar.gz ... done
Extracting libjpeg-turbo-1.3.1.tar.gz ... done
Compiling libjpeg-turbo, please be patient ... done
Creating './whitenoise-1920x1080.jpg' ... done
CPU stress test, which is doing JPEG decoding by libjpeg-turbo
at different cpufreq operating points.
Testing CPU 0
960 MHz ............................................................ OK
912 MHz ............................................................ OK
864 MHz ............................................................ OK
720 MHz ............................................................ OK
528 MHz ............................................................ OK
312 MHz ............................................................ OK
144 MHz ............................................................ OK
Testing CPU 1
960 MHz ............................................................ OK
912 MHz ............................................................ OK
864 MHz ............................................................ OK
720 MHz ............................................................ OK
528 MHz ............................................................ OK
312 MHz ............................................................ OK
144 MHz ............................................................ OK
Overall result : PASSED
5 years, 1 month
