I dusted off my Linksprite pcDuino3 Nano Lite and did a image build with:
--target=Linksprite_pcDuino3_Nano --media=/dev/sdb --norootpass
--selinux=OFF --addconsole --resizefs
I booted up the image with a UDB keyboard and VGA monitor (via an
HDMI-to-vga adapter) attached plus the TTY console.
The boot dropped into the headless config. No video.
Is this a limitation with the F26 support? I had it working with F23 a
Maybe something with this HDMI to VGA adapter? It is a different one
than I used last year (that one is in use elsewhere).
Just did a poweroff on the pcDuino3 Nano.
Did nothing after logging in. No upgrades nothing. Got the following
messages on the TTY console after lots of shutdown messages:
[ 7544.587424] reboot: Power down
[ 7546.646239] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[ 7547.177766] systemd-shutdow: 4 output lines suppressed due to
[ 7547.191003] Kernel panic - not syncing: Attempted to kill init!
[ 7547.200158] CPU: 0 PID: 1 Comm: systemd-shutdow Tainted: G W
[ 7547.210060] Hardware name: Allwinner sun7i (A20) Family
[ 7547.215310] [<c021a378>] (unwind_backtrace) from [<c0214c9c>]
[ 7547.223058] [<c0214c9c>] (show_stack) from [<c05bdfc4>]
[ 7547.230287] [<c05bdfc4>] (dump_stack) from [<c0397230>]
[ 7547.237167] [<c0397230>] (panic) from [<c025fa60>] (do_exit+0x678/0xce4)
[ 7547.243870] [<c025fa60>] (do_exit) from [<c0283bc4>]
[ 7547.251007] [<c0283bc4>] (SyS_reboot) from [<c020fe20>]
[ 7547.259354] ---[ end Kernel panic - not syncing: Attempted to kill
Is there WiFi support for any of the allwinner boards?
I see that Rawhide has the latest uboot (2017.01) and still no
CubieTruck WiFi support. With Hans stepping down as uboot maintainer, I
no longer see his uboot planning page to see if WiFi will happen or not.
I know I can add a USB WiFi device, but would really like to use the
Hi Jeremy, all,
I was just catching up with some folks and we discussed the status of
48-bit VA support. It seems to me that it would make most sense to have
an official coordination effort between those vendors/community members
who are interested, to ensure that they help with the necessary package
updates ahead of the kernel, and work with a test kernel to identify any
additional packages or issues that need resolving. I believe it would
make most sense to have a Fedora feature page (or something less grand,
but similar in concept) tracking this for F26, with the deps.
Perhaps Jeremy can update us on the status, and then he and others can
help drive this forward (someone should nominate themselves as the ring
leader too). I spoke with Cavium earlier today, and I know they'll be
keen to help. I know Qualcomm had expressed interest during our IRC
meetings in helping out. To that end, I'm copying at least those I know
so far who are interested here.
Computer Architect | Sent from my Fedora powered laptop
I just did an image build for a Cubietruck with the
Fedora-Xfce-armhfp-25-1.3-sda with --selinux=OFF
It installed fine; still no wifi :(
Then I did a 'dnf update' and caught the following messages:
Upgrading : selinux-policy-targeted-3.13.1-225.6.fc25.noarch
[ 8981.136506] SELinux: Permission validate_trans in class security not
defined in policy.
[ 8981.144734] SELinux: Permission module_load in class system not
defined in policy.
[ 8981.152998] SELinux: the above unknown classes and permissions will
[ 8985.835670] SELinux: Context
unconfined_u:unconfined_r:sandbox_t:s0-s0:c0.c1023 became invalid
[ 8987.072186] SELinux: Context
system_u:unconfined_r:sandbox_t:s0-s0:c0.c1023 became invalid (unmapped).
What are these messages about? What should I do about them?
On RPi2 with Fedora 25 the wi-fi dongle TPLINK TL-WN722N don't work. In the dmesg I have:
[ 31.261891] ath9k_htc 1-1.4:1.0: ath9k_htc: Target is unresponsive
[ 31.288770] ath9k_htc: Failed to initialize the device
[ 31.320315] usb 1-1.4: ath9k_htc: USB layer deinitialized
When I try another distro such as Raspbian, CentOS RPi2 version or Fedberry, then the dongle works well. Then only distro in which don't work is Fedora 25 and I need to use Fedora 25 on this RPi.
Why this dongle don't work only on this distro?
With nothing on the agenda, I propose we cancel tomorrow's Fedora ARM & AArch64
If we've missed something or you do have something to discuss, please respond to
this email and we can go ahead with the meeting as planned.