Introduction/ looking for mentor
by Adrian
Hey,
I'm Adrian Sorge and I would love to contribute to the fedora on arm group, because I've been interested in non x86 architectures since about 5 years.
I'm a computer engineering student living in Germany(CET). I have experiences in programming (mostly c(++) and java), automation(ansible and puppet) and monitoring(nagios).
I would like to start with some changes to the arm-image-installer (I was thinking about adding some functions, including the automatic download of the image before writing it to the medium).
Since I'm new to open source development, it would be great if someone could help me getting started and/or be my mentor/sponsor.
Best Regards
Adrian
5 years, 3 months
test results on odroid-hc1 on booting from sata
by Robert Moskowitz
Does not work. Sigh.
U-Boot 2018.09 (Sep 11 2018 - 09:51:41 +0000) for ODROID-XU3/XU4/HC1
CPU: Exynos5422 @ 800 MHz
Model: Odroid XU3 based on EXYNOS5422
Board: Odroid XU3 based on EXYNOS5422
Type: hc1
DRAM: 2 GiB
MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 2
Loading Environment from MMC... Card did not respond to voltage select!
*** Warning - No block device, using default environment
In: serial
Out: serial
Err: serial
Net: No ethernet found.
Hit any key to stop autoboot: 0
MMC Device 1 not found
no mmc device at slot 1
Card did not respond to voltage select!
switch to partitions #0, OK
mmc2 is current device
** Invalid partition 1 **
starting USB...
USB0: USB EHCI 1.00
USB1: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
USB2: Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 1 for devices... cannot reset port 1!?
2 USB Device(s) found
scanning bus 2 for devices... 2 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
scanning usb for ethernet devices... 1 Ethernet Device(s) found
Waiting for Ethernet connection... done.
BOOTP broadcast 1
BOOTP broadcast 2
DHCP client bound to address 192.168.192.15 (5004 ms)
*** ERROR: `serverip' not set
==================================
Setup was a 4GB uSD that only had the hardkernel bootloader and uboot.
No partitions.
sata drive (SSD) had the image (all partitions) installed. Including
changes to extlinux.conf
So now to get what others have working: boot on uSD and / on sata.
5 years, 3 months
test results on odroid-hc1 on booting from uSD with rootfs on sata
by Robert Moskowitz
This was 'easy'
Install image on uSD and do all the steps to make it bootable. But
instead of growing the rootfs partition, delete it.
Install image on the sata. Enlarge the rootfs and delete the boot
partition.
Insert the uSD and sata drive and boot.
That is all it takes. It helps that we dd the images so that both
devices have partitions with the same UUIDs.
There are improvements, like deleting partition 1 from the sata and
moving the start of the rootfs to that point, but I did not try this. I
will leave it for others.
Enjoy!
But I really want complete booting from sata...
5 years, 3 months
Re: Installer failure on SSd drive
by Robert Moskowitz
On 12/5/18 1:22 PM, Paul Whalen wrote:
>
> ----- Original Message -----
>>
>> On 12/5/18 1:05 PM, Robert Moskowitz wrote:
>>>
>>> On 12/5/18 1:01 PM, Robert Moskowitz wrote:
>>>> =====================================================
>>>> = Selected Image:
>>>> = /home/rgm/arm/Fedora-Server-armhfp-29-1.2-sda.raw.xz
>>>> = Selected Media : /dev/sdc
>>>> = U-Boot Target : none
>>>> =====================================================
>>>>
>>>> *****************************************************
>>>> *****************************************************
>>>> ******** WARNING! ALL DATA WILL BE DESTROYED ********
>>>> *****************************************************
>>>> *****************************************************
>>>>
>>>> Type 'YES' to proceed, anything else to exit now
>>>>
>>>> = Proceed? yes
>>>> = Writing:
>>>> = /home/rgm/arm/Fedora-Server-armhfp-29-1.2-sda.raw.xz
>>>> = To: /dev/sdc ....
>>>> 0+337225 records in
>>>> 0+337225 records out
>>>> 3242196992 bytes (3.2 GB, 3.0 GiB) copied, 148.012 s, 21.9 MB/s
>>>> = Writing image complete!
>>>> mount: /tmp/root: wrong fs type, bad option, bad superblock on
>>>> /dev/sdc3, missing codepage or helper program, or other error.
>>>> Error: mount /dev/sdc3 /tmp/root failed
>>>>
>>>> what does this mean? The SSD was in a USB/sata adapter that I have
>>>> used many times in the past. I unplugged and replugged the USB and
>>>> now all 3 partitions are showing and I am using gparted to enlarge
>>>> the / partition. But it came up on sdd where before it was on sdc.
>>>>
>>> gparted failed to grow the partition.
>>>
>>> mount: /tmp/gparted-n5hfh1: wrong fs type, bad option, bad superblock
>>> on /dev/sdd3, missing codepage or helper program, or other error
>>>
>>> So probably a problem with the SSD?
>>>
>> same failure with a HD. I am going to try a different adapter.
>>
>> mount: /tmp/root: wrong fs type, bad option, bad superblock on
>> /dev/sdd3, missing codepage or helper program, or other error.
>> Error: mount /dev/sdd3 /tmp/root failed
> What version of the arm-image-installer is this? I fixed a few things in
> the latest (arm-image-installer-2.10-1).
>
> I have seen that when writing out the server image repeatedly, a reboot
> should 'fix' it.
ARGH!!!!
I have been running fedora-arm-image-installer that has been in my
working directory since 11/14!!! version 1.99 :(
Just using what I had in my notes instead of noticing the name change to
arm-image-installer.
Time to delete this old cruft.
yes, I did LOTS of writing out images. And a reboot helped.
5 years, 3 months
Installer failure on SSd drive
by Robert Moskowitz
=====================================================
= Selected Image:
= /home/rgm/arm/Fedora-Server-armhfp-29-1.2-sda.raw.xz
= Selected Media : /dev/sdc
= U-Boot Target : none
=====================================================
*****************************************************
*****************************************************
******** WARNING! ALL DATA WILL BE DESTROYED ********
*****************************************************
*****************************************************
Type 'YES' to proceed, anything else to exit now
= Proceed? yes
= Writing:
= /home/rgm/arm/Fedora-Server-armhfp-29-1.2-sda.raw.xz
= To: /dev/sdc ....
0+337225 records in
0+337225 records out
3242196992 bytes (3.2 GB, 3.0 GiB) copied, 148.012 s, 21.9 MB/s
= Writing image complete!
mount: /tmp/root: wrong fs type, bad option, bad superblock on
/dev/sdc3, missing codepage or helper program, or other error.
Error: mount /dev/sdc3 /tmp/root failed
what does this mean? The SSD was in a USB/sata adapter that I have used
many times in the past. I unplugged and replugged the USB and now all 3
partitions are showing and I am using gparted to enlarge the /
partition. But it came up on sdd where before it was on sdc.
5 years, 3 months
Finding out which boards are supported
by Robert Moskowitz
Without doing an install to:
cat /usr/share/doc/arm-image-installer/SUPPORTED-BOARDS
Kind of a catch-22. You have to do an install to find out if your board
is supported?
I know there is a uboot for odroid-xu3, but does the F30 installer
install for it?
Well I will give it a try, but still you have created a catch-22 here.
(and who here has read the book or saw the movie? :) ).
(book is MUCH better than the movie, you really cannot follow all the
flashbacks in the movie)
5 years, 3 months
Read only sdb - just not my day...
by Robert Moskowitz
So I am pulling out my hair because even after a reboot I am still getting
dd: failed to open '/dev/sdb':
Read-only file system
= Writing image complete!
Warning: Unable to open /dev/sdb read-write (Read-only file system).
/dev/sdb has been opened read-only.
Warning: Unable to open /dev/sdb read-write (Read-only file system).
/dev/sdb has been opened read-only.
mount: /tmp/root: WARNING: device write-protected, mounted read-only.
= No U-Boot will be installed.
Tried a bunch of uSD cards. Then I just happened to look at my uSD card
holder and see that the lock switch was locked....
Just one of those days.
:)
5 years, 3 months