RaspBerry PI 3B+
by RENARD Pierre-Francois
Hello
I have just received 2 wonderfull Raspberry PI3B+ but I am not able to
boot them and I have a wonderfull rainbow screen.
I check the power, and it is OK.
I tried the NOOBS image from raspberry and it is working.
I guess we are just lacking for the firmware/drivers of this new PI3B+.
How can I generate theses files ?
Do you have any documentations ?
I m ready to experiment and share to help others.
Thanks a lot
Fox
6 years
My experience with Fedora Rawhide on Odroid XU4 and Odroid H1
by arm_ml＠rirasoft.de
Hello,
based on research from Stewart Samuels with
Fedora-Mate-armhfp-Rawhide-20180301.n.0-sda.raw.xz I installed this on
my both Odroid.
First:
Odroid XU4Q (without fan) + SSD
/boot on SD-Card
/ on SSD
Today I've update the system to the latest updates. Kernel
4.16.0-0.rc6.git1.1.fc29.armv7hl works for me with X
[root@odroidxu4 ~]# ps ax | grep X
953 tty1 Ssl+ 0:02 /usr/libexec/Xorg -core -noreset :0 -seat
seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch
-background none
2046 ? R 0:00 /usr/bin/perl -XU
/usr/lib/x2go/libx2go-server-db-sqlite3-wrapper.pl listsessionsroot
odroidxu4.reschke.lan
2048 pts/0 S+ 0:00 grep --color=auto X
[root@odroidxu4 ~]#
Second:
Odroid H1
/boot on SD-Card
/ on SSD
/var, /mail, /nextcloud with LVM
I removed all graphical applications
Only Kernel 4.16.0-0.rc4.git3.1.fc29.armv7hl is working fine with LVM.
With all newer Kernel system stopps at rescue modus after initialize
LVM. Volumegroup and Logical Volume are present, after typing "systemctl
default" system boots into multiuser.target correct. System is running
"normal" but with a continoius load from 4 (without any running
services). This didn't happens with 4.16.0-0.rc4.git3.1.fc29.armv7hl.
This system should work in the near future as a Nextcloud-Server, so I
need LVM.
Greetings
Andreas
6 years
Orange Pi PC/Zero/Mini
by Fabian Affolter
Hi all,
As Peter requested :-)
During the last three weeks I attended two conferences. In India we
wanted to have actual hardware to allow the participants of the training
to do their exercises and the attendees of the crypto currencies village
see how it works.
I'm going to split it. Covering the Orange Pi devices here and the
Raspberry Pi and the UDOO Neo in another message.
I decided to go with three Orange Pi Zero. They are easy to carry
around, have a physical NIC, are cheap and with a big powerbank we were
able to survive the power outages with are happening from time to time
there.
Of course, we wanted to run Fedora but I ended up using Armbian. I was
using fedora-arm-image-installer to create the cards.
# fedora-arm-image-installer \
--image=Fedora-Server-armhfp-27-1.6-sda.raw.xz
--target=orangepi_zero --media=/dev/mmcblk0 --resizefs
To get some feedback I connected a serial converter to the Orange Pi
Zero. The output is visible but minicom doesn't allow me to log in aka
doesn't accept any input no matter of minicom's settings. Same result
with a different adapter. My guess is that it would work if you know how
to do it as in a lot of cases it's the only way to get the details or
perform the initial setup.
According to the serial output the Orange Pi Zero should be available
over the network. It doesn't show me its IP address but that's fine. OK,
if are not using network which you have some sort of control over it
then it would be handy if you get the IP address from the serial output.
In the meantime were three SD card ready with Armbian and I stopped. The
reason is simple: Armbian is more plug-and-play than Fedora. The initial
configuration can be done over SSH and I don't wanted to waste more time
on getting Fedora running without any indication of success.
The next one was an Orange Pi PC. Reason to use was the HDMI output
which would make it possible to attach the unit to a projector.
Workstation image instead of Server this time.
# fedora-arm-image-installer \
--image=Fedora-Workstation-armhfp-27-1.6-sda.raw.xz \
--target=orangepi_pc --media=/dev/mmcblk0 --resizefs
Device starts running, no graphical output. Perhaps broken...no, works
fine with Armbian. Perhaps is the screen not playing nice with Fedora.
Other screen, same result.
Let's test the Orange Mini (that one is approx. the same age as the
Orange Pi PC). Same image, different target. After a couple of seconds
the LED went on but not HDMI output.
Kind regards,
Fabian
6 years
Re: The 4.15 kernel rebase on stable releases
by Stewart Samuels
I just got a chance to test the 4.16.0-0.rc2 kernel using the 20180220
Xfce Rawhide Spin. It fails to boot due to a kernel paging request.
Here are the snippets:
U-Boot 2018.03-rc2 (Feb 16 2018 - 14:14:52 +0000) for ODROID-XU3/XU4/HC1
CPU: Exynos5422 @ 800 MHz
Model: Odroid XU3 based on EXYNOS5422
Board: Odroid XU3 based on EXYNOS5422
Type: xu4
DRAM: 2 GiB
MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 1
Loading Environment from MMC... *** Warning - bad CRC, using default
environment
Failed (-5)
In: serial
Out: serial
Err: serial
Net: No ethernet found.
Hit any key to stop autoboot: 0
mmc_init: -5, time 6
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:2...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
591 bytes read in 14 ms (41 KiB/s)
Ignoring unknown command: ui
Ignoring malformed menu command: autoboot
Ignoring malformed menu command: hidden
Ignoring unknown command: totaltimeout
Fedora-Xfce-armhfp-Rawhide-20180220.n.0 Boot Options.
1: Fedora-Xfce-armhfp-Rawhide-20180220.n.0
(4.16.0-0.rc2.git0.1.fc28.armv7hl)
Enter choice: 1: Fedora-Xfce-armhfp-Rawhide-20180220.n.0
(4.16.0-0.rc2.git0.1.fc28.armv7hl)
Retrieving file: /initramfs-4.16.0-0.rc2.git0.1.fc28.armv7hl.img
54271696 bytes read in 4082 ms (12.7 MiB/s)
Retrieving file: /vmlinuz-4.16.0-0.rc2.git0.1.fc28.armv7hl
6660608 bytes read in 519 ms (12.2 MiB/s)
append: ro root=UUID=7d9c6236-7437-49c9-9e30-cf5ba8d147d5 cma=192MB
Retrieving file:
/dtb-4.16.0-0.rc2.git0.1.fc28.armv7hl/exynos5422-odroidxu4.dtb
56970 bytes read in 508 ms (109.4 KiB/s)
Kernel image @ 0x42000000 [ 0x000000 - 0x65a200 ]
## Flattened Device Tree blob at 43000000
Booting using the fdt blob at 0x43000000
Loading Ramdisk to 4cc3e000, end 4ffffed0 ... OK
Loading Device Tree to 4cc2d000, end 4cc3de89 ... OK
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x100
[ 0.000000] Linux version 4.16.0-0.rc2.git0.1.fc28.armv7hl
(mockbuild(a)buildvm-armv7-07.arm.fedoraproject.org) (gcc version
8.0.1 20180218 8
[ 0.000000] CPU: ARMv7 Processor [410fc073] revision 3 (ARMv7),
cr=10c5387d
.
.
.
[ 6.366866] 12c30000.serial: ttySAC3 at MMIO 0x12c30000 (irq =
61, base_baud = 0) is a S3C6400/10
[ 6.377630] msm_serial: driver initialized
[ 6.380655] STMicroelectronics ASC driver initialized
[ 6.390013] libphy: Fixed MDIO Bus: probed
[ 6.393299] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI)
Driver
[ 6.399194] ehci-pci: EHCI PCI platform driver
[ 6.403631] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 6.409762] ohci-pci: OHCI PCI platform driver
[ 6.414203] uhci_hcd: USB Universal Host Controller Interface driver
[ 6.420729] usbcore: registered new interface driver
usbserial_generic
[ 6.427020] usbserial: USB Serial support registered for generic
[ 6.433186] mousedev: PS/2 mouse device common for all mice
[ 6.445564] device-mapper: uevent: version 1.0.3
[ 6.449213] device-mapper: ioctl: 4.37.0-ioctl (2017-09-20)
initialised: dm-devel(a)redhat.com
[ 6.461297] ledtrig-cpu: registered to indicate activity on CPUs
[ 6.466198] hidraw: raw HID events driver (C) Jiri Kosina
[ 6.471445] usbcore: registered new interface driver usbhid
[ 6.476783] usbhid: USB HID core driver
[ 6.483709] drop_monitor: Initializing network drop monitor service
[ 6.489025] Initializing XFRM netlink socket
[ 6.493716] NET: Registered protocol family 10
[ 8.028149] Unable to handle kernel paging request at virtual
address fffffffc
Stewart
On 02/22/2018 12:01 PM, Peter Robinson wrote:
> On Thu, Feb 22, 2018 at 7:52 PM, Stewart Samuels <searider74(a)gmail.com> wrote:
>>
>> On 02/22/2018 11:39 AM, Peter Robinson wrote:
>>> On Thu, Feb 22, 2018 at 7:24 PM, Stewart Samuels <searider74(a)gmail.com>
>>> wrote:
>>>> Hi Peter,
>>>>
>>>> I just got a chance to update my Odroid Xu4 with the latest updates for
>>>> F27.
>>>> All was working fine with the exceptions for the Exynos 5 USB-3 issues
>>>> prior
>>>> to this upgrade. After the upgrade and a reboot, my system no longer
>>>> boots
>>>> into graphics mode. It seems to be failing somewhere along the line with
>>>> udev, but I am not certain of this. The system will eventually boot into
>>>> non-graphics mode, which can be seen when connecting the serial port and
>>>> watching the boot messages.
>>>>
>>>> As I mentioned in previous posts, the Rawhide Spins all seem to have this
>>>> issue too. In fact, they have had the problem for a long time now. On
>>>> the
>>>> positive side, both this release of F27 updates and the Rawhide spins do
>>>> seem to have the USB-3 issues fixed.
>>> Can you try the 4.16rc2 kernel [1] and see if that has the same
>>> issues. The 4.16 kernel might help as there was a bunch of stuff that
>>> changed in the exynos drm driver.
>>>
>>> https://koji.fedoraproject.org/koji/buildinfo?buildID=1046448
>> Looking at the builds in this URL I see "rawhide" listed as one of the
>> "Tasks". Doe this mean the current rawhide build are already including the
>> kernel-4.16.0-0.rc2 kernel?
> Yes, and the just branched F-28 will as well. So you can do an upgrade
> to F-28 and get it there too
>
>>>> Attached, is a MS Word formatted file of my boot log. Hope this helps.
>>> Please don't do that, word processing docs are really not the way to
>>> handle this in open source just fpaste it or something. If it's booted
>>> just do "dmesg | fpaste" and provide the URL.
>>>
>>>> Regards,
>>>> Stewart
>>>>
>>>>
>>>> On 02/12/2018 09:56 AM, Peter Robinson wrote:
>>>>> Hi All,
>>>>>
>>>>> Just a heads up that the 4.15 kernel is headed to stable releases.
>>>>>
>>>>> I did a bunch of testing over the weekend and fixed up a bunch of
>>>>> issues, added some minor enhancements across a number of platforms.
>>>>> There is a kernel-4.15.2-301.fc27 build [1] which had all those fixes
>>>>> for people to test, I expect a 4.15.3 kernel going to updates-testing
>>>>> later today or tomorrow.
>>>>>
>>>>> A few notes for the fixes I added:
>>>>> * fixed cpufreq/thermal on i.MX6 (thanks kwizart for upstream fix)
>>>>> * Crypto/rng engine on some AllWinner devices now loads/works
>>>>> (A10/A143/A20 at least, I suspect more will come with later kernels)
>>>>> * Exynos 5 USB-3 issue should now be fixed once and for all (I hope)
>>>>> * A bunch of improvements for monitor detection on the Raspberry Pi
>>>>> * Ethernet driver more stable on AllWInner A64/H5 platforms (like
>>>>> Pine64)
>>>>> * Numerous other upstream fixes improvements that headed upstream
>>>>> * 4.15.3 (not in the build above) will include aarch64 fixes for
>>>>> Spectre/Meltdown.
>>>>>
>>>>> So please test and feel free to reply to this thread with any new
>>>>> issues you see with the 4.15 series, or any positive results.
>>>>>
>>>>> [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=24966088
>>>>> _______________________________________________
>>>>> arm mailing list -- arm(a)lists.fedoraproject.org
>>>>> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
>>>>
6 years
Fedora-Workstation-armhfp-28-20180319.n.0
by Richard Ryniker
Problem or just noise? "dnf upgrade" succeeded today (260+ packages
updated, seems like a lot for a one-day-old build, but this may simply be
a busy time.) System was booted to multi-user target after upgrade, this
message was generated at login time (but login succeeded, and journalctl
captured the log with this message.)
Mar 20 18:33:03 localhost kernel: vc4_hdmi 3f902000.hdmi: ASoC: can't open interface 3f902000.hdmi: -19
Mar 20 18:33:03 localhost kernel: vc4_hdmi 3f902000.hdmi: ASoC: can't open interface 3f902000.hdmi: -19
Mar 20 18:33:03 localhost kernel: vc4_hdmi 3f902000.hdmi: ASoC: can't open interface 3f902000.hdmi: -19
Mar 20 18:33:03 localhost kernel: vc4_hdmi 3f902000.hdmi: ASoC: can't open interface 3f902000.hdmi: -19
Mar 20 18:33:03 localhost kernel: vc4_hdmi 3f902000.hdmi: ASoC: can't open interface 3f902000.hdmi: -19
6 years
How boot process works
by Alessio Ciregia
Hello.
I know, there is google. :-)
But someone could suggest a document that explains in simple words how the
Raspberry Pi boot process works? In Fedora I know there is a vfat
partition. What are the involved files? Who tell to look for the uboot
file? Etc.
Please be patient, I'm not a developer nor an engineer, just asking to
understand a little bit more how things works.
Thanks,
A.
6 years, 1 month
UDOO Neo/Raspberry Pi 3
by Fabian Affolter
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
OK, I didn't have much luck with the Orange Pi devices. But there was
an UDOO Neo and a Raspberry Pi 3 in the toy box. Demo stations for the
booth at CLT.
Again the Workstation image but with brand new SD card.
UDOO Neo: no output over HDMI and the NIC doesn't start blinking. So,
I assume that the device was not booting at all. Test with other HDMI
cable, different adapters and screens, still no output.
Raspberry Pi 3: Good news, that one is starting and working. At least
sort of. The one I have tends to freeze randomly with Fedora 27. No
idea, why. New SD card, dedicated PSU and enough cooling.
My experience with my ancient Cubieboard and Fedora let me believe
that using Fedora on newer (not talking about brand new device here)
single board computer would be pretty much the same. Create an SD
card, plug it in, power up, go through the initial setup and start
using it. Unfortunately this is not the case at the moment.
Kind regards,
Fabian
-----BEGIN PGP SIGNATURE-----
iF0EARECAB0WIQQvbJMP08R+OGr6TrTiPNLdNqQ5fwUCWrFUJwAKCRDiPNLdNqQ5
f/0oAJ4+zEqrtuN7FsTswDVKCVkwXglAsACfdD/dG0bM9+Ah5Q0k/PWgwyFlfgo=
=ZyQf
-----END PGP SIGNATURE-----
6 years, 1 month
Fedora 27 not boot on BBB
by sakurai
2018-03-13 8:18 GMT+09:00 Peter Robinson <pbrobinson(a)gmail.com>:
> On Mon, Mar 12, 2018 at 10:47 PM, sakurai <sakurai(a)pugpug.org> wrote:
>> Hi Peter,
>>
>> Thank you for your prompt comment.
>> I removed uEnv.txt but following message was displayed.
(snip)
>
> I don't know what you've done to now, you're likely possibly better
> off starting again with arm-image-installer to setup the image again
> with am335x_evm and then try booting with the boot button held down.
I tried again using arm-image-installer by following command.
> fedora-arm-image-installer --image=Fedora-Server-armhfp-27-1.6-sda.raw.xz --target=am335x_evm --media=/dev/sdd --norootpass --resizefs --addconsole --selinux=off
Not am335x_boneblack? Anyway I installed using arm335x_evm this time.
My boot loader may be new because Angstrom will not boot without
holding the boot button.
> You might also want to give the full output.
Here is the full output.
U-Boot SPL 2013.04-dirty (Jun 19 2013 - 09:57:14)
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
OMAP SD/MMC: 0
mmc_send_cmd : timeout: No status update
reading u-boot.img
reading u-boot.img
U-Boot 2013.04-dirty (Jun 19 2013 - 09:57:14)
I2C: ready
DRAM: 512 MiB
WARNING: Caches not enabled
NAND: No NAND device found!!!
0 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Warning - readenv() failed, using default environment
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
Net: <ethaddr> not set. Validating first E-fuse MAC
cpsw, usb_ether
Hit any key to stop autoboot: 0
gpio: pin 53 (gpio 53) value is 1
mmc0 is current device
micro SD card found
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
SD/MMC found on device 0
reading uEnv.txt
** Unable to read file uEnv.txt **
gpio: pin 55 (gpio 55) value is 1
** File not found /boot/uImage **
U-Boot#
--
SAKURAI, Atsushi <sakurai(a)pugpug.org>
6 years, 1 month
