Is it possible to enable Bluetooth on Udoo Neo ? FYI, it uses the TI
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.
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
--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
mount -t auto /dev/sdf2 /tmp/sd
ln -s exynos5422-odroidxu4.dtb exynos5422-odroidunknown.dtb
4: make it boot by running sd_fusing
mkdir sd_fusing; cd sd_fusing
chmod a+x sd_fusing.sh
cp /usr/share/uboot/odroid-xu3/u-boot.bin .
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:
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.
Has anyone had any luck getting Fedora 28 to work on the Odroid C2?
I've tried downloading the Fedora 28 Server aarch.raw.xz image which i
put onto my sd card. I then moved the Archlinux aarch64 boot parition
into boot along with the lib/modules and lib/firmware folders from
Archlinux. This has been to no avail. I'm working on building the
hardkernel kernel myself now but have never actually compiled a kernel
myself so I'm not sure what I fully need to get the Fedora rootfs to
boot with the kernel.
If anyone has some guidance or a nice writeup on getting a bootable
kernel recognized by Fedora on the Odroid C2 that would be greatly
I have f29 (kernel-4.18.12-300.fc29.aarch64 ) on machine, which is changing its place from time to
time - between two TVs. Old, and older:)
Both are connected by HDMI. Video output is fine, even acceleration is working, but sound work only
on newer of those two.
I don't know if this is regression, because this machine replaced 32b rapbery2 with kodi, which was
working without issues on both TVs (but was eaten by (not mine) dog)
I was following https://fedoraproject.org/wiki/How_to_debug_sound_problems but had not found much:
- with removed pulseaudio, the aplay -vv segfaults
- I really on pulseaudio anyway, as I need to transfer sound to this machine over network
- the diff of alsa-info.sh's is really minimal , only
for non working and
- when alsamixer is opened, then the default looks like working, and the job on old tv; but not do
nothing older tv.
- when alsamixer -c0 is opened, then the vc4-hdmi reports no control for selected device for
*both* tvs (which is same as f6 and selecting vc4-hdmi)
Does anybody have a clue what to try?
Thanx in advance form java world,
@@ -1,5 +1,5 @@
-cat: /tmp/alsa-info.TzPwpaQcKW/acpidevicestatus.tmp: No such file or directory
+cat: /tmp/alsa-info.GXybsmPDbN/acpidevicestatus.tmp: No such file or directory
cat: '/sys/module/(null)/parameters/*': No such file or directory
@@ -8,7 +8,7 @@
!!ALSA Information Script v 0.4.64
-!!Script ran on: Mon Oct 29 14:09:06 UTC 2018
+!!Script ran on: Mon Oct 29 14:15:02 UTC 2018
@@ -152,7 +152,7 @@
access 'read volatile'
Senior QE engineer, OpenJDK QE lead, Mgr.
Red Hat Czech
jvanek(a)redhat.com M: +420775390109
I mentioned this issue on IRC but also posting here:
I've been using Fedora on Cubox-i for a long time, I noticed that 4.18.x kernels broke networking. Booting to 4.17.19-200.fc28 fixes the issue for me.
The eth0 interface is still visible on 4.18.x kernels but it does not work:
- The interface was connected to an Amplifi HD, the link kept going up/down every few seconds (no such issue on older kernels)
- Connecting the interface to a Cisco switch fixes the unstable link issue, the rest of the tests were done with this switch
- DHCP hangs (tested manually with dhclient, no output)
- Setting an static IP on the interface works but no traffic passes through (tested ICMP, etc.)
I can provide more technical details and kernel log messages if required.
I'm interested to install Fedora ARM on an F2FS file system.
Are there tips or scripts to do this ?
It looks like "arm-image-installer" basically uses "dd" to copy an
image to storage.
I had a script once that created partitions and file systems and
copied (and then had to twiddle with the UUIDs in file systems or
/etc/fstab) ... but I think I lost that script.
I suppose I could make a kickstart file and use livemedia-creator or
appliance-tools to create an image ... but I've never got that to