Bluetooth on Udoo Neo ?
by Ken Harris
Is it possible to enable Bluetooth on Udoo Neo ? FYI, it uses the TI
WL1831 module.
I tried :
hciattach -n ttymxc2 texas
... but got "Initialization timed out."
I also tried various combinations of bit rates and flow control.
Any tips are welcome.
-K
4 years, 9 months
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
Any notes on how to setup Fedora on the Vamrs Rock960?
by William Cohen
Hi,
Given RHBZ1639765, "Rock960 hangs after boot" and uboot-images-armv8-2018.09-1.fc29.noarch having rock960-rk3399 files it looks like there are some people that have Fedora running on the Vamrs Rock960, but arm-image-installer doesn't list the board on the supported list. Does anyone have some notes on how they got Fedora running on the board?
-Will
5 years, 2 months
f29 uboot & odroid hc2 (patch)
by Torbjorn Jansson
Hello
I asked on linux-arm-kernel mail list regarding the "missing" dtb file problem
for odroid hc2.
The info i got was that the hc1 dtb file is the correct one to use for hc2 too
and there is a patch to make uboot detect and use the right dtb file.
The patch in question:
http://git.denx.de/?p=u-boot.git;a=patch;h=9cd97c5b049a9a282dda0b1782cbb3...
I rebuilt uboot-tools-2018.09-1.fc29.x86_64 with this patch applied and it
boots and uses the hc1 dtb file correctly.
No need for a manual symlink like:
ln -s exynos5422-odroidhc1.dtb exynos5422-odroidunknown.dtb
So would be nice if this could be considered for inclusion in the fedora uboot
package sometime in the future to make it easier to get the hc2 up and running.
5 years, 2 months
Mate Spin
by Stewart Samuels
Hello All,
Does anyone know if the Mate (not Mate-Compiz) release of Fedora has
been terminated? I don't seem to be able to find it for Fedora 29 in
the normal places such as:
/pub/fedora/linux/releases/29/Spins/armhfp/images
Alternatively, if Mate is no longer supported, is there a similar
standard URL such as that provided above for Fedora 29 spins that I can
use to download images, including Mate-Compiz (if that is the now
supported Mate based desktop)?
Thanks for any help.
Stewart
5 years, 2 months
Fedora ARM & AArch64 Status Meeting Minutes 2019-01-22
by Paul Whalen
========================================================
#fedora-meeting-2: Fedora ARM and AArch64 Status Meeting
========================================================
Meeting started by pwhalen at 15:00:33 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-2/2019-01-22/fedora_arm_...
.
Meeting summary
---------------
* roll call (pwhalen, 15:00:33)
* 1) ==== Userspace Status ==== (pwhalen, 15:09:06)
* Firefox fails to build on arm - /usr/bin/ld: final link failed:
memory exhausted (pwhalen, 15:11:59)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1658940
(pwhalen, 15:12:12)
* Rawhide now includes GCC9, some breakage may occur (pwhalen,
15:18:49)
* 2) ==== Kernel Status ==== (pwhalen, 15:19:01)
* F29: kernel-4.20.3-200.fc29 (pwhalen, 15:19:13)
* LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=1180452
(pwhalen, 15:19:13)
* F30: kernel-5.0.0-0.rc3.git0.1.fc30 (pwhalen, 15:20:18)
* LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=1181002
(pwhalen, 15:20:19)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1666868
(pwhalen, 15:22:27)
* Please test and report any issues to the list or #fedora-arm.
(pwhalen, 15:23:23)
* 3) ==== Bootloader Status ==== (pwhalen, 15:24:32)
* uboot-tools-2019.01-1.fc30 available now (pwhalen, 15:24:46)
* LINK: https://koji.fedoraproject.org/koji/buildinfo?buildID=1179800
(pwhalen, 15:24:46)
* 4) == F30 == (pwhalen, 15:26:39)
* Latest nominated nightly -
https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
(pwhalen, 15:26:40)
* F30 Beta Blockers (pwhalen, 15:27:36)
* LINK:
https://qa.fedoraproject.org/blockerbugs/milestone/30/beta/buglist
(pwhalen, 15:27:43)
* initial-setup fails to run with recent anaconda (cannot import name
'initThreading' from 'pyanaconda.threading') (pwhalen, 15:28:08)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1666849
(pwhalen, 15:28:08)
* 5) == Open Floor == (pwhalen, 15:35:27)
Meeting ended at 15:38:55 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* pwhalen (51)
* pbrobinson (16)
* jlinton (10)
* zodbot (6)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
5 years, 2 months
rock64 and odroid c2 boards
by mark co-dyre
Hello all,
I've been looking for a group like this for a while now to hopefully help with learning how to get get a recent version of u-boot working properly so I can get fedora 29 to boot on my rock64 and odroid c2 boards. I'd also like to contribute this back once I get this working properly.
So far I've gotten the odroid c2 to boot fine using the stock hardkernel 3.16 lts kernel and their older version of u-boot. For this I had used a chrooted instance of a Fedora 29 minimum sitting on the Ubuntu distro they provide. From this I built a new initramfs with dracut against a copy of the hosted ubunutu lib/modules.
This all worked fine although I'd like to get it working with a recent u-boot, UEFI and load the grub.efi binary to boot the standard fedora kernel. I had got to the point where I had loaded the grub binary and was able to select my kernel (stock fedora 4.18.x kernel); Although things would hang after. I suspect the main reason for the hang was I borrowed the opensuse grub.efi UEFI app because I could not get the fedora one to run. Other than the binary blob stuff from hardkernel u-boot was stock and it was booting into u-boot just fine.
I've set that board aside for now to use it as a build host and have moved on to my rock64 board. After putting the stock fedora 29 minimal image on a card and attempting to boot it Im seeing:
... regular u-boot stuff blah blah blah (full u-boot log is below)
Hit any key to stop autoboot: 0
Card did not respond to voltage select!
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
** Unable to read file / **
Found EFI removable media binary efi/boot/bootaa64.efi
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
Scanning disk rksdmmc@ff500000.blk...
Card did not respond to voltage select!
Scanning disk rksdmmc@ff520000.blk...
Disk rksdmmc(a)ff520000.blk not ready
Found 4 disks
858216 bytes read in 43 ms (19 MiB/s)
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
## Starting EFI application at 02000000 ...
System BootOrder not found. Initializing defaults.
Creating boot entry "Boot0000" with label "Fedora" for file "\EFI\fedora\shimaa64.efi"
... hangs here
I'm using the u-boot binary from another distro (arch linux) configured for a rock64 device; Not the Fedora one. I'm pretty ignorant on how the shim stuff works although I would like to learn all those details to form a better understanding. My current understanding is that this shim is a signed (by UEFI signing service) initial bootloader that handles chaining to a trusted full bootloader (grub in this case). Does grub need to be signed in some way to work with this shim that loads it?
Are there any good resources out there that would help me better understand what is happening? My next step is going to be to use the fedora u-boot of course and see where that leads me. Although my gut is telling that may not produce the outcome I desire.
I'm very familiar with patching and building so I'm not afraid to dig in and create some patches to bounce back once I have these up and running I'm just hoping to have someone provide some insight as to what I should be focusing on so I can gain some traction.
I've noticed there's a #fedora-meeting-2 IRC channel that meets on Tues at 3pm UTC; I'm planning on dropping by next week.
Well that's all for now I'm exhausted and need some sleep :)
Thanks for reading,
DDR version 1.06 20170424
In
SRX
LPDDR3
786MHz
Bus Width=32 Col=11 Bank=8 Row=15/15 CS=2 Die Bus-Width=32 Size=4096MB
ddrconfig:7
OUT
Boot1 Release Time: 2017-05-18, version: 2.43
ChipType = 0x11, 187
emmc reinit
emmc reinit
SdmmcInit=2 20
SdmmcInit=0 0
BootCapSize=0
UserCapSize=30436MB
FwPartOffset=2000 , 0
StorageInit ok = 60041
Raw SecureMode = 0
SecureInit read PBA: 0x4
SecureInit read PBA: 0x404
SecureInit read PBA: 0x804
SecureInit read PBA: 0xc04
SecureInit read PBA: 0x1004
SecureInit ret = 0, SecureMode = 0
LoadTrustBL
No find bl30.bin
No find bl32.bin
Load uboot, ReadLba = 2000
Load OK, addr=0x200000, size=0x8b0ec
RunBL31 0x10000
NOTICE: BL31: v1.3(debug):f947c7e
NOTICE: BL31: Built : 09:28:45, May 31 2017
NOTICE: BL31:Rockchip release version: v1.3
INFO: ARM GICv2 driver initialized
INFO: Using opteed sec cpu_context!
INFO: boot cpu mask: 1
INFO: plat_rockchip_pmu_init: pd status 0xe
INFO: BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destiK
ERROR: Error initializing runtime service opteed_fast
INFO: BL31: Preparing for EL3 exit to normal world
INFO: Entry point address = 0x200000
INFO: SPSR = 0x3c9
U-Boot 2018.03-1 (Apr 02 2018 - 19:14:47 -0600) Arch Linux ARM
Model: Rockchip RK3328 EVB
DRAM: 4 GiB
MMC: rksdmmc@ff500000: 1, rksdmmc@ff520000: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment
Failed (-5)
In: serial@ff130000
Out: serial@ff130000
Err: serial@ff130000
Model: Rockchip RK3328 EVB
Net:
Warning: ethernet@ff540000 (eth0) using random MAC address - e6:d0:8e:31:57:c3
eth0: ethernet@ff540000
Hit any key to stop autoboot: 0
Card did not respond to voltage select!
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
** Unable to read file / **
Found EFI removable media binary efi/boot/bootaa64.efi
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
Scanning disk rksdmmc@ff500000.blk...
Card did not respond to voltage select!
Scanning disk rksdmmc@ff520000.blk...
Disk rksdmmc(a)ff520000.blk not ready
Found 4 disks
858216 bytes read in 43 ms (19 MiB/s)
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
## Starting EFI application at 02000000 ...
System BootOrder not found. Initializing defaults.
Creating boot entry "Boot0000" with label "Fedora" for file "\EFI\fedora\shimaa64.efi"
5 years, 3 months
