11:06 a.m.
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)
11:16 a.m.
Additional bug? in F28 x64 installer:
# fedora-arm-image-installer
--image=/home/rgm/arm/Fedora-Minimal-armhfp-Rawhide-20181203.n.0-sda.raw.xz
--supported --media=/dev/sdb
cat: /usr/share/doc/fedora-arm-installer//SUPPORTED-BOARDS: No such file
or directory
The installer looks at what my system lists as supported boards, rather
than what the image shows and why the double // ?
Our newcomer, Adrian, has offered to look at the Installer script. Well
here is one thing that needs help it seems.
On 12/4/18 12:06 PM, Robert Moskowitz wrote:
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)
_______________________________________________
arm mailing list -- arm(a)lists.fedoraproject.org
To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
11:51 a.m.
On Tue, Dec 4, 2018 at 5:17 PM Robert Moskowitz <rgm(a)htt-consult.com> wrote:
Additional bug? in F28 x64 installer:
# fedora-arm-image-installer
--image=/home/rgm/arm/Fedora-Minimal-armhfp-Rawhide-20181203.n.0-sda.raw.xz --supported
--media=/dev/sdb
cat: /usr/share/doc/fedora-arm-installer//SUPPORTED-BOARDS: No such file or directory
The installer looks at what my system lists as supported boards, rather than what the
image shows and why the double
You need to update to the latest version.
12:12 p.m.
On 12/4/18 12:51 PM, Peter Robinson wrote:
On Tue, Dec 4, 2018 at 5:17 PM Robert Moskowitz
<rgm(a)htt-consult.com> wrote:
> Additional bug? in F28 x64 installer:
>
> # fedora-arm-image-installer
--image=/home/rgm/arm/Fedora-Minimal-armhfp-Rawhide-20181203.n.0-sda.raw.xz --supported
--media=/dev/sdb
> cat: /usr/share/doc/fedora-arm-installer//SUPPORTED-BOARDS: No such file or
directory
>
> The installer looks at what my system lists as supported boards, rather than what the
image shows and why the double
You need to update to the latest version.
Yeah,,,
I had tried a 'dnf update fedora-arm*' and got nothing to update.
Had problems with the system so did a general dnf update to get the
latest stuff before rebooting and now it works.
So my bad on trying a shortcut to update fedora-arm-image-installer....
No odroid listed, so it is do it the long way, it seems.
12:24 p.m.
El mar, 04-12-2018 a las 13:12 -0500, Robert Moskowitz escribió:
On 12/4/18 12:51 PM, Peter Robinson wrote:
> On Tue, Dec 4, 2018 at 5:17 PM Robert Moskowitz <
> rgm(a)htt-consult.com> wrote:
> > Additional bug? in F28 x64 installer:
> >
> > # fedora-arm-image-installer --image=/home/rgm/arm/Fedora-
> > Minimal-armhfp-Rawhide-20181203.n.0-sda.raw.xz --supported --
> > media=/dev/sdb
> > cat: /usr/share/doc/fedora-arm-installer//SUPPORTED-BOARDS: No
> > such file or directory
> >
> > The installer looks at what my system lists as supported boards,
> > rather than what the image shows and why the double
> You need to update to the latest version.
>
Yeah,,,
I had tried a 'dnf update fedora-arm*' and got nothing to update.
Had problems with the system so did a general dnf update to get the
latest stuff before rebooting and now it works.
So my bad on trying a shortcut to update fedora-arm-image-
installer....
No odroid listed, so it is do it the long way, it seems.
The odroid boards need binary files we can not distribute. While I have
a couple they are not really supportable.
Dennis
12:33 p.m.
On 12/4/18 1:24 PM, Dennis Gilmore wrote:
El mar, 04-12-2018 a las 13:12 -0500, Robert Moskowitz escribió:
> On 12/4/18 12:51 PM, Peter Robinson wrote:
>> On Tue, Dec 4, 2018 at 5:17 PM Robert Moskowitz <
>> rgm(a)htt-consult.com> wrote:
>>> Additional bug? in F28 x64 installer:
>>>
>>> # fedora-arm-image-installer --image=/home/rgm/arm/Fedora-
>>> Minimal-armhfp-Rawhide-20181203.n.0-sda.raw.xz --supported --
>>> media=/dev/sdb
>>> cat: /usr/share/doc/fedora-arm-installer//SUPPORTED-BOARDS: No
>>> such file or directory
>>>
>>> The installer looks at what my system lists as supported boards,
>>> rather than what the image shows and why the double
>> You need to update to the latest version.
>>
> Yeah,,,
>
> I had tried a 'dnf update fedora-arm*' and got nothing to update.
>
> Had problems with the system so did a general dnf update to get the
> latest stuff before rebooting and now it works.
>
> So my bad on trying a shortcut to update fedora-arm-image-
> installer....
>
> No odroid listed, so it is do it the long way, it seems.
The odroid boards need binary files we can not distribute. While I have
a couple they are not really supportable.
So this confirms it is the long way and no shortcuts forthcoming.
OK. I will deal with it. It does look to be one of the better boards
out there right now. But will see if I can get it to boot as I would
like...
5:45 p.m.
>>> On Tue, Dec 4, 2018 at 5:17 PM Robert Moskowitz <
>>> rgm(a)htt-consult.com> wrote:
>>>> Additional bug? in F28 x64 installer:
>>>>
>>>> # fedora-arm-image-installer --image=/home/rgm/arm/Fedora-
>>>> Minimal-armhfp-Rawhide-20181203.n.0-sda.raw.xz --supported --
>>>> media=/dev/sdb
>>>> cat: /usr/share/doc/fedora-arm-installer//SUPPORTED-BOARDS: No
>>>> such file or directory
>>>>
>>>> The installer looks at what my system lists as supported boards,
>>>> rather than what the image shows and why the double
>>> You need to update to the latest version.
>>>
>> Yeah,,,
>>
>> I had tried a 'dnf update fedora-arm*' and got nothing to update.
>>
>> Had problems with the system so did a general dnf update to get the
>> latest stuff before rebooting and now it works.
>>
>> So my bad on trying a shortcut to update fedora-arm-image-
>> installer....
>>
>> No odroid listed, so it is do it the long way, it seems.
> The odroid boards need binary files we can not distribute. While I have
> a couple they are not really supportable.
So this confirms it is the long way and no shortcuts forthcoming.
OK. I will deal with it. It does look to be one of the better boards
out there right now. But will see if I can get it to boot as I would
like...
The Odroid boards are OK, but we don't have any engagement with them
so they're a best effort and they do occasionally break. The Odroid
people don't tend to do anything upstream and they have a signed SPL
(Secondary Process Loader) which means we can't produce working U-Boot
binaries due to the bits that Dennis mentions above. They really are a
community supported best effort, I personally prefer to engage and
actively support devices where the companies work with the upstream
communities to support their devices.
Peter
1:58 a.m.
Am 05.12.18 um 00:45 schrieb Peter Robinson:
>>>> On Tue, Dec 4, 2018 at 5:17 PM Robert Moskowitz <
>>>> rgm(a)htt-consult.com> wrote:
>>>>> Additional bug? in F28 x64 installer:
>>>>>
>>>>> # fedora-arm-image-installer --image=/home/rgm/arm/Fedora-
>>>>> Minimal-armhfp-Rawhide-20181203.n.0-sda.raw.xz --supported --
>>>>> media=/dev/sdb
>>>>> cat: /usr/share/doc/fedora-arm-installer//SUPPORTED-BOARDS: No
>>>>> such file or directory
>>>>>
>>>>> The installer looks at what my system lists as supported boards,
>>>>> rather than what the image shows and why the double
>>>> You need to update to the latest version.
>>>>
>>> Yeah,,,
>>>
>>> I had tried a 'dnf update fedora-arm*' and got nothing to update.
>>>
>>> Had problems with the system so did a general dnf update to get the
>>> latest stuff before rebooting and now it works.
>>>
>>> So my bad on trying a shortcut to update fedora-arm-image-
>>> installer....
>>>
>>> No odroid listed, so it is do it the long way, it seems.
>> The odroid boards need binary files we can not distribute. While I have
>> a couple they are not really supportable.
> So this confirms it is the long way and no shortcuts forthcoming.
>
> OK. I will deal with it. It does look to be one of the better boards
> out there right now. But will see if I can get it to boot as I would
> like...
The Odroid boards are OK, but we don't have any engagement with them
so they're a best effort and they do occasionally break. The Odroid
people don't tend to do anything upstream and they have a signed SPL
(Secondary Process Loader) which means we can't produce working U-Boot
binaries due to the bits that Dennis mentions above. They really are a
community supported best effort, I personally prefer to engage and
actively support devices where the companies work with the upstream
communities to support their devices.
Peter
_______________________________________________
Peter: you're right. But on the other hand, there is no other SBC with
this power (Hexacore, USB3,SATA,...)
Andreas
12:38 p.m.
Am 04.12.18 um 19:24 schrieb Dennis Gilmore:
El mar, 04-12-2018 a las 13:12 -0500, Robert Moskowitz escribió:
> On 12/4/18 12:51 PM, Peter Robinson wrote:
>> On Tue, Dec 4, 2018 at 5:17 PM Robert Moskowitz <
>> rgm(a)htt-consult.com> wrote:
>>> Additional bug? in F28 x64 installer:
>>>
>>> # fedora-arm-image-installer --image=/home/rgm/arm/Fedora-
>>> Minimal-armhfp-Rawhide-20181203.n.0-sda.raw.xz --supported --
>>> media=/dev/sdb
>>> cat: /usr/share/doc/fedora-arm-installer//SUPPORTED-BOARDS: No
>>> such file or directory
>>>
>>> The installer looks at what my system lists as supported boards,
>>> rather than what the image shows and why the double
>> You need to update to the latest version.
>>
> Yeah,,,
>
> I had tried a 'dnf update fedora-arm*' and got nothing to update.
>
> Had problems with the system so did a general dnf update to get the
> latest stuff before rebooting and now it works.
>
> So my bad on trying a shortcut to update fedora-arm-image-
> installer....
>
> No odroid listed, so it is do it the long way, it seems.
The odroid boards need binary files we can not distribute. While I have
a couple they are not really supportable.
Dennis
Hello Dennis,
I'm very satisfied with my 3 Odroid HC1 running with Fedora as
Nextcloud, Mail, NTP, transmission, et cetera.
Greetings
Andreas
3:14 p.m.
New subject: Odroid-HC1 won't boot
On 12/4/18 1:24 PM, Dennis Gilmore wrote:
The odroid boards need binary files we can not distribute. While I have
a couple they are not really supportable.
No success today. Here is what I tried:
used
https://blog.christophersmart.com/2018/04/28/fedora-on-odroid-hc1-mini-na...
All work was done on my F28 x64 notebook on to a 16GB uSD card.
downloaded and installed F30 minimal:
fedora-arm-image-installer
--image=/home/rgm/arm/Fedora-Minimal-armhfp-Rawhide-20181203.n.0-sda.raw.xz
--target=none --media=/dev/sdb
Then installed the bootloader:
mkdir hardkernel ; cd hardkernel
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...
cp /run/media/rgm/__/usr/share/uboot/odroid-xu3/u-boot.bin .
chmod a+x sd_fusing.sh
./sd_fusing.sh /dev/sdb
Note that I took the uboot from the F30 install.
Next I fixed extlinux. The above website had extlinux.conf directly in
the mounted boot partition, I found it in the extlinux directory.
sed -i "s|append|& cpuidle.off=1 \
console=tty1 console=ttySAC2,115200n8 \
rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd no_bL_switcher|" \
/run/media/rgm/__boot/extlinux/extlinux.conf
This resulted in:
cat /run/media/rgm/__boot/extlinux/extlinux.conf
# extlinux.conf generated by appliance-creator
ui menu.c32
menu autoboot Welcome to Fedora-Minimal-armhfp-Rawhide-20181203.n.0.
Automatic boot in # second{,s}. Press a key for options.
menu title Fedora-Minimal-armhfp-Rawhide-20181203.n.0 Boot Options.
menu hidden
timeout 20
totaltimeout 600
label Fedora-Minimal-armhfp-Rawhide-20181203.n.0
(4.20.0-0.rc4.git2.1.fc30.armv7hl)
kernel /vmlinuz-4.20.0-0.rc4.git2.1.fc30.armv7hl
append cpuidle.off=1 console=tty1 console=ttySAC2,115200n8
rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd no_bL_switcher ro
root=UUID=0405755f-001a-4df5-8a6d-c9538ca89ee3 rhgb quiet LANG=en_US.UTF-8
fdtdir /dtb-4.20.0-0.rc4.git2.1.fc30.armv7hl/
initrd /initrd-4.20.0-0.rc4.git2.1.fc30.armv7hl.img
I inserted the uSD card in the Odroid, connected the serial cable,
running screen and here is the capture:
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
Scanning mmc 2:2...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
728 bytes read in 3 ms (236.3 KiB/s)
Ignoring unknown command: ui
Ignoring malformed menu command: autoboot
Ignoring malformed menu command: hidden
Ignoring unknown command: totaltimeout
Fedora-Minimal-armhfp-Rawhide-20181203.n.0 Boot Options.
1: Fedora-Minimal-armhfp-Rawhide-20181203.n.0
(4.20.0-0.rc4.git2.1.fc30.arm
v7hl)
Enter choice: 1: Fedora-Minimal-armhfp-Rawhide-20181203.n.0 (4.20.0-0.rc4
.git2.1.fc30.armv7hl)
Retrieving file: /initrd-4.20.0-0.rc4.git2.1.fc30.armv7hl.img
** File not found /initrd-4.20.0-0.rc4.git2.1.fc30.armv7hl.img **
Skipping Fedora-Minimal-armhfp-Rawhide-20181203.n.0
(4.20.0-0.rc4.git2.1.fc30.ar
mv7hl) for failure retrieving initrd
SCRIPT FAILED: continuing...
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!?
1 USB Device(s) found
scanning bus 2 for devices... 2 USB Device(s) found
scanning usb for storage devices... 0 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
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
BOOTP broadcast 6
Retry time exceeded; starting again
missing environment variable: pxeuuid
Retrieving file: /extlinux/pxelinux.cfg/00000000
*** ERROR: `serverip' not set
Retrieving file: /extlinux/pxelinux.cfg/0000000
*** ERROR: `serverip' not set
======================
So what am I missing here?
Do you have to run the Hardkernel script on an arm boot?
Please advise. Thanks
4:30 p.m.
New subject: Odroid-HC1 won't boot
El mar, 04-12-2018 a las 16:14 -0500, Robert Moskowitz escribió:
On 12/4/18 1:24 PM, Dennis Gilmore wrote:
> The odroid boards need binary files we can not distribute. While I
> have
> a couple they are not really supportable.
No success today. Here is what I tried:
used
https://blog.christophersmart.com/2018/04/28/fedora-on-odroid-hc1-mini-na...
All work was done on my F28 x64 notebook on to a 16GB uSD card.
downloaded and installed F30 minimal:
fedora-arm-image-installer
--image=/home/rgm/arm/Fedora-Minimal-armhfp-Rawhide-20181203.n.0-
sda.raw.xz
--target=none --media=/dev/sdb
Then installed the bootloader:
mkdir hardkernel ; cd hardkernel
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...
cp /run/media/rgm/__/usr/share/uboot/odroid-xu3/u-boot.bin .
chmod a+x sd_fusing.sh
./sd_fusing.sh /dev/sdb
Note that I took the uboot from the F30 install.
Next I fixed extlinux. The above website had extlinux.conf directly
in
the mounted boot partition, I found it in the extlinux directory.
sed -i "s|append|& cpuidle.off=1 \
console=tty1 console=ttySAC2,115200n8 \
rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd no_bL_switcher|" \
/run/media/rgm/__boot/extlinux/extlinux.conf
This resulted in:
cat /run/media/rgm/__boot/extlinux/extlinux.conf
# extlinux.conf generated by appliance-creator
ui menu.c32
menu autoboot Welcome to Fedora-Minimal-armhfp-Rawhide-20181203.n.0.
Automatic boot in # second{,s}. Press a key for options.
menu title Fedora-Minimal-armhfp-Rawhide-20181203.n.0 Boot Options.
menu hidden
timeout 20
totaltimeout 600
label Fedora-Minimal-armhfp-Rawhide-20181203.n.0
(4.20.0-0.rc4.git2.1.fc30.armv7hl)
kernel /vmlinuz-4.20.0-0.rc4.git2.1.fc30.armv7hl
append cpuidle.off=1 console=tty1 console=ttySAC2,115200n8
rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd no_bL_switcher ro
root=UUID=0405755f-001a-4df5-8a6d-c9538ca89ee3 rhgb quiet
LANG=en_US.UTF-8
fdtdir /dtb-4.20.0-0.rc4.git2.1.fc30.armv7hl/
initrd /initrd-4.20.0-0.rc4.git2.1.fc30.armv7hl.img
I inserted the uSD card in the Odroid, connected the serial cable,
running screen and here is the capture:
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
Scanning mmc 2:2...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
728 bytes read in 3 ms (236.3 KiB/s)
Ignoring unknown command: ui
Ignoring malformed menu command: autoboot
Ignoring malformed menu command: hidden
Ignoring unknown command: totaltimeout
Fedora-Minimal-armhfp-Rawhide-20181203.n.0 Boot Options.
1: Fedora-Minimal-armhfp-Rawhide-20181203.n.0
(4.20.0-0.rc4.git2.1.fc30.arm
v7hl)
Enter choice: 1: Fedora-Minimal-armhfp-Rawhide-20181203.n.0
(4.20.0-0.rc4
.git2.1.fc30.armv7hl)
Retrieving file: /initrd-4.20.0-0.rc4.git2.1.fc30.armv7hl.img
** File not found /initrd-4.20.0-0.rc4.git2.1.fc30.armv7hl.img **
was there an initrd in the boot partition? the problem is that it was
not found. the file should actually be named initramfs-<version>.img
not initrd-<version>.img
Dennis
Skipping Fedora-Minimal-armhfp-Rawhide-20181203.n.0
(4.20.0-0.rc4.git2.1.fc30.ar
mv7hl) for failure retrieving initrd
SCRIPT FAILED: continuing...
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!?
1 USB Device(s) found
scanning bus 2 for devices... 2 USB Device(s) found
scanning usb for storage devices... 0 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
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
BOOTP broadcast 6
Retry time exceeded; starting again
missing environment variable: pxeuuid
Retrieving file: /extlinux/pxelinux.cfg/00000000
*** ERROR: `serverip' not set
Retrieving file: /extlinux/pxelinux.cfg/0000000
*** ERROR: `serverip' not set
======================
So what am I missing here?
Do you have to run the Hardkernel script on an arm boot?
Please advise. Thanks
5:53 p.m.
New subject: Odroid-HC1 won't boot
On 12/4/18 5:30 PM, Dennis Gilmore wrote:
El mar, 04-12-2018 a las 16:14 -0500, Robert Moskowitz escribió:
> On 12/4/18 1:24 PM, Dennis Gilmore wrote:
>> The odroid boards need binary files we can not distribute. While I
>> have
>> a couple they are not really supportable.
> No success today. Here is what I tried:
>
> used
> https://blog.christophersmart.com/2018/04/28/fedora-on-odroid-hc1-mini-na...
>
> All work was done on my F28 x64 notebook on to a 16GB uSD card.
>
> downloaded and installed F30 minimal:
>
> fedora-arm-image-installer
> --image=/home/rgm/arm/Fedora-Minimal-armhfp-Rawhide-20181203.n.0-
> sda.raw.xz
> --target=none --media=/dev/sdb
>
> Then installed the bootloader:
>
> mkdir hardkernel ; cd hardkernel
>
> 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...
>
> cp /run/media/rgm/__/usr/share/uboot/odroid-xu3/u-boot.bin .
>
> chmod a+x sd_fusing.sh
>
> ./sd_fusing.sh /dev/sdb
>
> Note that I took the uboot from the F30 install.
>
> Next I fixed extlinux. The above website had extlinux.conf directly
> in
> the mounted boot partition, I found it in the extlinux directory.
>
> sed -i "s|append|& cpuidle.off=1 \
> console=tty1 console=ttySAC2,115200n8 \
> rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd no_bL_switcher|" \
> /run/media/rgm/__boot/extlinux/extlinux.conf
>
> This resulted in:
>
> cat /run/media/rgm/__boot/extlinux/extlinux.conf
> # extlinux.conf generated by appliance-creator
> ui menu.c32
> menu autoboot Welcome to Fedora-Minimal-armhfp-Rawhide-20181203.n.0.
> Automatic boot in # second{,s}. Press a key for options.
> menu title Fedora-Minimal-armhfp-Rawhide-20181203.n.0 Boot Options.
> menu hidden
> timeout 20
> totaltimeout 600
>
> label Fedora-Minimal-armhfp-Rawhide-20181203.n.0
> (4.20.0-0.rc4.git2.1.fc30.armv7hl)
> kernel /vmlinuz-4.20.0-0.rc4.git2.1.fc30.armv7hl
> append cpuidle.off=1 console=tty1 console=ttySAC2,115200n8
> rd.driver.pre=ledtrig-heartbeat,xhci-plat-hcd no_bL_switcher ro
> root=UUID=0405755f-001a-4df5-8a6d-c9538ca89ee3 rhgb quiet
> LANG=en_US.UTF-8
> fdtdir /dtb-4.20.0-0.rc4.git2.1.fc30.armv7hl/
> initrd /initrd-4.20.0-0.rc4.git2.1.fc30.armv7hl.img
>
>
> I inserted the uSD card in the Odroid, connected the serial cable,
> running screen and here is the capture:
>
>
>
> 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
> Scanning mmc 2:2...
> Found /extlinux/extlinux.conf
> Retrieving file: /extlinux/extlinux.conf
> 728 bytes read in 3 ms (236.3 KiB/s)
> Ignoring unknown command: ui
> Ignoring malformed menu command: autoboot
> Ignoring malformed menu command: hidden
> Ignoring unknown command: totaltimeout
> Fedora-Minimal-armhfp-Rawhide-20181203.n.0 Boot Options.
> 1: Fedora-Minimal-armhfp-Rawhide-20181203.n.0
> (4.20.0-0.rc4.git2.1.fc30.arm
> v7hl)
> Enter choice: 1: Fedora-Minimal-armhfp-Rawhide-20181203.n.0
> (4.20.0-0.rc4
> .git2.1.fc30.armv7hl)
> Retrieving file: /initrd-4.20.0-0.rc4.git2.1.fc30.armv7hl.img
> ** File not found /initrd-4.20.0-0.rc4.git2.1.fc30.armv7hl.img **
was there an initrd in the boot partition? the problem is that it was
not found. the file should actually be named initramfs-<version>.img
not initrd-<version>.img
ls /run/media/rgm/__boot/
config-4.20.0-0.rc4.git2.1.fc30.armv7hl
dtb
dtb-4.20.0-0.rc4.git2.1.fc30.armv7hl
efi
extlinux
grub
lost+found
System.map-4.20.0-0.rc4.git2.1.fc30.armv7hl
vmlinuz-4.20.0-0.rc4.git2.1.fc30.armv7hl
no initramfs....
And I built this via the standard installer, using target=none.
Is this file suppose to be in the image I downloaded or is it made
somehow during the install.
Dennis
> Skipping Fedora-Minimal-armhfp-Rawhide-20181203.n.0
> (4.20.0-0.rc4.git2.1.fc30.ar
> mv7hl) for failure retrieving initrd
> SCRIPT FAILED: continuing...
> 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!?
> 1 USB Device(s) found
> scanning bus 2 for devices... 2 USB Device(s) found
> scanning usb for storage devices... 0 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
> BOOTP broadcast 3
> BOOTP broadcast 4
> BOOTP broadcast 5
> BOOTP broadcast 6
>
> Retry time exceeded; starting again
> missing environment variable: pxeuuid
> Retrieving file: /extlinux/pxelinux.cfg/00000000
> *** ERROR: `serverip' not set
> Retrieving file: /extlinux/pxelinux.cfg/0000000
> *** ERROR: `serverip' not set
>
> ======================
>
>
> So what am I missing here?
>
> Do you have to run the Hardkernel script on an arm boot?
>
> Please advise. Thanks
>
>
> _______________________________________________
> arm mailing list -- arm(a)lists.fedoraproject.org
> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
6:01 p.m.
New subject: Odroid-HC1 won't boot
Can you trim irrelevant bits from your mails, makes it easier to read.
was there an initrd in the boot partition? the problem is that it
was
not found. the file should actually be named initramfs-<version>.img
not initrd-<version>.img
ls /run/media/rgm/__boot/
config-4.20.0-0.rc4.git2.1.fc30.armv7hl
dtb
dtb-4.20.0-0.rc4.git2.1.fc30.armv7hl
efi
extlinux
grub
lost+found
System.map-4.20.0-0.rc4.git2.1.fc30.armv7hl
vmlinuz-4.20.0-0.rc4.git2.1.fc30.armv7hl
no initramfs....
And I built this via the standard installer, using target=none.
Is this file suppose to be in the image I downloaded or is it made somehow during the
install.
It should be there and it's not part of the install, what is the full
image name of the image you're writing out? We've had some regressions
in ARMv7, I would try the latest image from today's compose as it
should be now fixed, I'm guessing with a rc4 kernel this image is from
last week?
6:08 p.m.
New subject: Odroid-HC1 won't boot
On 12/4/18 7:01 PM, Peter Robinson wrote:
Can you trim irrelevant bits from your mails, makes it easier to
read.
I was thinking of trimming but could not figure out the irrelevant
bits. Sigh.
> was there an initrd in the boot partition? the problem is that it was
> not found. the file should actually be named initramfs-<version>.img
> not initrd-<version>.img
>
>
> ls /run/media/rgm/__boot/
> config-4.20.0-0.rc4.git2.1.fc30.armv7hl
> dtb
> dtb-4.20.0-0.rc4.git2.1.fc30.armv7hl
> efi
> extlinux
> grub
> lost+found
> System.map-4.20.0-0.rc4.git2.1.fc30.armv7hl
> vmlinuz-4.20.0-0.rc4.git2.1.fc30.armv7hl
>
> no initramfs....
>
> And I built this via the standard installer, using target=none.
>
> Is this file suppose to be in the image I downloaded or is it made somehow during the
install.
It should be there and it's not part of the install, what is the full
image name of the image you're writing out? We've had some regressions
in ARMv7, I would try the latest image from today's compose as it
should be now fixed, I'm guessing with a rc4 kernel this image is from
last week?
I used:
Fedora-Minimal-armhfp-Rawhide-20181203.n.0-sda
I built the uSD card with
fedora-arm-image-installer
--image=/home/rgm/arm/Fedora-Minimal-armhfp-Rawhide-20181203.n.0-sda.raw.xz
--target=none --media=/dev/sdb
Tomorrow I will grab the latest and try again. Thanks.
7:49 a.m.
New subject: Odroid-HC1 won't boot
On 12/4/18 7:08 PM, Robert Moskowitz wrote:
On 12/4/18 7:01 PM, Peter Robinson wrote:
> Can you trim irrelevant bits from your mails, makes it easier to read.
I was thinking of trimming but could not figure out the irrelevant
bits. Sigh.
>
>> was there an initrd in the boot partition? the problem is that it was
>> not found. the file should actually be named initramfs-<version>.img
>> not initrd-<version>.img
>>
>>
>>
>> no initramfs....
>>
>> And I built this via the standard installer, using target=none.
>>
>> Is this file suppose to be in the image I downloaded or is it made
>> somehow during the install.
> It should be there and it's not part of the install, what is the full
> image name of the image you're writing out? We've had some regressions
> in ARMv7, I would try the latest image from today's compose as it
> should be now fixed, I'm guessing with a rc4 kernel this image is from
> last week?
I used:
Fedora-Minimal-armhfp-Rawhide-20181203.n.0-sda
Now using Fedora-Minimal-armhfp-Rawhide-20181205.n.0-sda and still no
initramfs:
ls /run/media/rgm/__boot/
config-4.20.0-0.rc5.git1.1.fc30.armv7hl
dtb
dtb-4.20.0-0.rc5.git1.1.fc30.armv7hl
efi
extlinux
grub
lost+found
System.map-4.20.0-0.rc5.git1.1.fc30.armv7hl
vmlinuz-4.20.0-0.rc5.git1.1.fc30.armv7hl
What build should I fall back to?
thanks
9:43 a.m.
New subject: Odroid-HC1 won't boot
Hi Robert,
----- Original Message -----
On 12/4/18 7:08 PM, Robert Moskowitz wrote:
>
>
> On 12/4/18 7:01 PM, Peter Robinson wrote:
>> Can you trim irrelevant bits from your mails, makes it easier to read.
>
> I was thinking of trimming but could not figure out the irrelevant
> bits. Sigh.
>
>>
>>> was there an initrd in the boot partition? the problem is that it was
>>> not found. the file should actually be named initramfs-<version>.img
>>> not initrd-<version>.img
>>>
>>>
>>>
>>> no initramfs....
>>>
>>> And I built this via the standard installer, using target=none.
>>>
>>> Is this file suppose to be in the image I downloaded or is it made
>>> somehow during the install.
>> It should be there and it's not part of the install, what is the full
>> image name of the image you're writing out? We've had some regressions
>> in ARMv7, I would try the latest image from today's compose as it
>> should be now fixed, I'm guessing with a rc4 kernel this image is from
>> last week?
>
> I used:
>
> Fedora-Minimal-armhfp-Rawhide-20181203.n.0-sda
>
Now using Fedora-Minimal-armhfp-Rawhide-20181205.n.0-sda and still no
initramfs:
ls /run/media/rgm/__boot/
config-4.20.0-0.rc5.git1.1.fc30.armv7hl
dtb
dtb-4.20.0-0.rc5.git1.1.fc30.armv7hl
efi
extlinux
grub
lost+found
System.map-4.20.0-0.rc5.git1.1.fc30.armv7hl
vmlinuz-4.20.0-0.rc5.git1.1.fc30.armv7hl
What build should I fall back to?
There is still an issue in rawhide with the minimal image, I need to look
at further. The server image[1] looks ok- both kernel and initrd are there
anyways, there may be other problems. Or you could try one of the desktops.
Paul
[1] -
https://kojipkgs.fedoraproject.org/compose//rawhide/Fedora-Rawhide-201812...
>
> thanks
> _______________________________________________
> arm mailing list -- arm(a)lists.fedoraproject.org
> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
>
9:53 a.m.
New subject: Odroid-HC1 won't boot
On 12/5/18 10:43 AM, Paul Whalen wrote:
Hi Robert,
----- Original Message -----
>
> On 12/4/18 7:08 PM, Robert Moskowitz wrote:
>>
>> On 12/4/18 7:01 PM, Peter Robinson wrote:
>>> Can you trim irrelevant bits from your mails, makes it easier to read.
>> I was thinking of trimming but could not figure out the irrelevant
>> bits. Sigh.
>>
>>>> was there an initrd in the boot partition? the problem is that it was
>>>> not found. the file should actually be named
initramfs-<version>.img
>>>> not initrd-<version>.img
>>>>
>>>>
>>>>
>>>> no initramfs....
>>>>
>>>> And I built this via the standard installer, using target=none.
>>>>
>>>> Is this file suppose to be in the image I downloaded or is it made
>>>> somehow during the install.
>>> It should be there and it's not part of the install, what is the full
>>> image name of the image you're writing out? We've had some
regressions
>>> in ARMv7, I would try the latest image from today's compose as it
>>> should be now fixed, I'm guessing with a rc4 kernel this image is from
>>> last week?
>> I used:
>>
>> Fedora-Minimal-armhfp-Rawhide-20181203.n.0-sda
>>
> Now using Fedora-Minimal-armhfp-Rawhide-20181205.n.0-sda and still no
> initramfs:
>
> ls /run/media/rgm/__boot/
> config-4.20.0-0.rc5.git1.1.fc30.armv7hl
> dtb
> dtb-4.20.0-0.rc5.git1.1.fc30.armv7hl
> efi
> extlinux
> grub
> lost+found
> System.map-4.20.0-0.rc5.git1.1.fc30.armv7hl
> vmlinuz-4.20.0-0.rc5.git1.1.fc30.armv7hl
>
> What build should I fall back to?
There is still an issue in rawhide with the minimal image, I need to look
at further. The server image[1] looks ok- both kernel and initrd are there
anyways, there may be other problems. Or you could try one of the desktops.
Paul
[1] -
https://kojipkgs.fedoraproject.org/compose//rawhide/Fedora-Rawhide-201812...
I will try the server image. The Odroid-HC1 has no video interface so
no way to get through the setup.
thanks
10:25 a.m.
New subject: Fedora-Server-armhfp-Rawhide-20181205.n.0-sda fails login on odroid-hc1
On 12/5/18 10:43 AM, Paul Whalen wrote:
There is still an issue in rawhide with the minimal image, I need to look
at further. The server image[1] looks ok- both kernel and initrd are there
anyways, there may be other problems. Or you could try one of the desktops.
Paul
[1] -
https://kojipkgs.fedoraproject.org/compose//rawhide/Fedora-Rawhide-201812...
Followed all the steps with using only uSD and booted up. Went through
the setup, and noticed it was not getting a network connection reported
in the setup, perhaps I should have gone into that option...
Anyway, first boot continued to login, but:
[ OK ] Started Update UTMP about System Runlevel Changes.
Fedora 30 (Server Edition)
Kernel 4.20.0-0.rc5.git1.1.fc30.armv7hl on an armv7l (ttySAC2)
Web console: https://localhost.localdomain:9090/
localhost login: root
Password:
-- root: no shell: Permission denied
Fedora 30 (Server Edition)
Kernel 4.20.0-0.rc5.git1.1.fc30.armv7hl on an armv7l (ttySAC2)
Web console: https://localhost.localdomain:9090/
localhost login: root
Password:
Last login: Sun Oct 28 20:34:22 on ttySAC2
-- root: no shell: Permission denied
Fedora 30 (Server Edition)
Kernel 4.20.0-0.rc5.git1.1.fc30.armv7hl on an armv7l (ttySAC2)
Web console: https://localhost.localdomain:9090/
localhost login: rgm
Password:
-- rgm: no shell: Permission denied
Fedora 30 (Server Edition)
Kernel 4.20.0-0.rc5.git1.1.fc30.armv7hl on an armv7l (ttySAC2)
Web console: https://localhost.localdomain:9090/
===============================
Why no shell? And can't get to the web console until I figure out if it
got an IP address and which (I have to look into which VLAN that port on
the switch is).
thanks
10:38 a.m.
New subject: Fedora-Server-armhfp-Rawhide-20181205.n.0-sda fails login on odroid-hc1
On 12/5/18 11:25 AM, Robert Moskowitz wrote:
On 12/5/18 10:43 AM, Paul Whalen wrote:
>
> There is still an issue in rawhide with the minimal image, I need to
> look
> at further. The server image[1] looks ok- both kernel and initrd are
> there
> anyways, there may be other problems. Or you could try one of the
> desktops.
>
> Paul
>
>
> [1] -
>
https://kojipkgs.fedoraproject.org/compose//rawhide/Fedora-Rawhide-201812...
Followed all the steps with using only uSD and booted up. Went
through the setup, and noticed it was not getting a network connection
reported in the setup, perhaps I should have gone into that option...
Anyway, first boot continued to login, but:
[ OK ] Started Update UTMP about System Runlevel Changes.
Fedora 30 (Server Edition)
Kernel 4.20.0-0.rc5.git1.1.fc30.armv7hl on an armv7l (ttySAC2)
Web console: https://localhost.localdomain:9090/
localhost login: root
Password:
-- root: no shell: Permission denied
Fedora 30 (Server Edition)
Kernel 4.20.0-0.rc5.git1.1.fc30.armv7hl on an armv7l (ttySAC2)
Web console: https://localhost.localdomain:9090/
localhost login: root
Password:
Last login: Sun Oct 28 20:34:22 on ttySAC2
-- root: no shell: Permission denied
Fedora 30 (Server Edition)
Kernel 4.20.0-0.rc5.git1.1.fc30.armv7hl on an armv7l (ttySAC2)
Web console: https://localhost.localdomain:9090/
localhost login: rgm
Password:
-- rgm: no shell: Permission denied
Fedora 30 (Server Edition)
Kernel 4.20.0-0.rc5.git1.1.fc30.armv7hl on an armv7l (ttySAC2)
Web console: https://localhost.localdomain:9090/
===============================
Why no shell? And can't get to the web console until I figure out if
it got an IP address and which (I have to look into which VLAN that
port on the switch is).
thanks
Hmm. I forgot to grow the rootfs partition. Could it have been out of
room?
Right now I am falling back to trying F29 armfhp server.
11:01 a.m.
New subject: Fedora-Server-armhfp-Rawhide-20181205.n.0-sda fails login on odroid-hc1
----- Original Message -----
On 12/5/18 11:25 AM, Robert Moskowitz wrote:
>
>
> On 12/5/18 10:43 AM, Paul Whalen wrote:
>>
>> There is still an issue in rawhide with the minimal image, I need to
>> look
>> at further. The server image[1] looks ok- both kernel and initrd are
>> there
>> anyways, there may be other problems. Or you could try one of the
>> desktops.
>>
>> Paul
>>
>>
>> [1] -
>>
https://kojipkgs.fedoraproject.org/compose//rawhide/Fedora-Rawhide-201812...
>
> Followed all the steps with using only uSD and booted up. Went
> through the setup, and noticed it was not getting a network connection
> reported in the setup, perhaps I should have gone into that option...
>
> Anyway, first boot continued to login, but:
>
> [ OK ] Started Update UTMP about System Runlevel Changes.
>
> Fedora 30 (Server Edition)
> Kernel 4.20.0-0.rc5.git1.1.fc30.armv7hl on an armv7l (ttySAC2)
>
> Web console: https://localhost.localdomain:9090/
>
> localhost login: root
> Password:
> -- root: no shell: Permission denied
>
> Fedora 30 (Server Edition)
> Kernel 4.20.0-0.rc5.git1.1.fc30.armv7hl on an armv7l (ttySAC2)
>
> Web console: https://localhost.localdomain:9090/
>
> localhost login: root
> Password:
> Last login: Sun Oct 28 20:34:22 on ttySAC2
> -- root: no shell: Permission denied
>
> Fedora 30 (Server Edition)
> Kernel 4.20.0-0.rc5.git1.1.fc30.armv7hl on an armv7l (ttySAC2)
>
> Web console: https://localhost.localdomain:9090/
>
> localhost login: rgm
> Password:
> -- rgm: no shell: Permission denied
>
> Fedora 30 (Server Edition)
> Kernel 4.20.0-0.rc5.git1.1.fc30.armv7hl on an armv7l (ttySAC2)
>
> Web console: https://localhost.localdomain:9090/
>
> ===============================
>
> Why no shell? And can't get to the web console until I figure out if
Looks like an selinux issue, adding enforcing=0 to the kernel args should
get you logged in.
> it got an IP address and which (I have to look into which VLAN
that
> port on the switch is).
>
> thanks
Hmm. I forgot to grow the rootfs partition. Could it have been out of
room?
Right now I am falling back to trying F29 armfhp server.
Thats a better bet, its been tested and should just work for you.
Paul
11:21 a.m.
New subject: Fedora-Server-armhfp-Rawhide-20181205.n.0-sda fails login on odroid-hc1
Hi Robert,
I was able to reproduce the log in issue, filed a bug on selinux:
https://bugzilla.redhat.com/show_bug.cgi?id=1656529
Thanks,
Paul
----- Original Message -----
>
>
> ----- Original Message -----
> >
> >
> > On 12/5/18 11:25 AM, Robert Moskowitz wrote:
> > >
> > >
> > > On 12/5/18 10:43 AM, Paul Whalen wrote:
> > >>
> > >> There is still an issue in rawhide with the minimal image, I need to
> > >> look
> > >> at further. The server image[1] looks ok- both kernel and initrd are
> > >> there
> > >> anyways, there may be other problems. Or you could try one of the
> > >> desktops.
> > >>
> > >> Paul
> > >>
> > >>
> > >> [1] -
> > >>
https://kojipkgs.fedoraproject.org/compose//rawhide/Fedora-Rawhide-201812...
> > >
> > > Followed all the steps with using only uSD and booted up. Went
> > > through the setup, and noticed it was not getting a network connection
> > > reported in the setup, perhaps I should have gone into that option...
> > >
> > > Anyway, first boot continued to login, but:
> > >
> > > [ OK ] Started Update UTMP about System Runlevel Changes.
> > >
> > > Fedora 30 (Server Edition)
> > > Kernel 4.20.0-0.rc5.git1.1.fc30.armv7hl on an armv7l (ttySAC2)
> > >
> > > Web console: https://localhost.localdomain:9090/
> > >
> > > localhost login: root
> > > Password:
> > > -- root: no shell: Permission denied
> > >
> > > Fedora 30 (Server Edition)
> > > Kernel 4.20.0-0.rc5.git1.1.fc30.armv7hl on an armv7l (ttySAC2)
> > >
> > > Web console: https://localhost.localdomain:9090/
> > >
> > > localhost login: root
> > > Password:
> > > Last login: Sun Oct 28 20:34:22 on ttySAC2
> > > -- root: no shell: Permission denied
> > >
> > > Fedora 30 (Server Edition)
> > > Kernel 4.20.0-0.rc5.git1.1.fc30.armv7hl on an armv7l (ttySAC2)
> > >
> > > Web console: https://localhost.localdomain:9090/
> > >
> > > localhost login: rgm
> > > Password:
> > > -- rgm: no shell: Permission denied
> > >
> > > Fedora 30 (Server Edition)
> > > Kernel 4.20.0-0.rc5.git1.1.fc30.armv7hl on an armv7l (ttySAC2)
> > >
> > > Web console: https://localhost.localdomain:9090/
> > >
> > > ===============================
> > >
> > > Why no shell? And can't get to the web console until I figure out if
>
> Looks like an selinux issue, adding enforcing=0 to the kernel args should
> get you logged in.
>
> > > it got an IP address and which (I have to look into which VLAN that
> > > port on the switch is).
> > >
> > > thanks
> >
> > Hmm. I forgot to grow the rootfs partition. Could it have been out of
> > room?
> >
> > Right now I am falling back to trying F29 armfhp server.
>
> Thats a better bet, its been tested and should just work for you.
>
> Paul
> _______________________________________________
> arm mailing list -- arm(a)lists.fedoraproject.org
> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
>
11:40 a.m.
New subject: Fedora-Server-armhfp-Rawhide-20181205.n.0-sda fails login on odroid-hc1
On 12/5/18 12:21 PM, Paul Whalen wrote:
Hi Robert,
I was able to reproduce the log in issue, filed a bug on selinux:
https://bugzilla.redhat.com/show_bug.cgi?id=1656529
Then I won't spend any more testing time with this image and just work
with F29 for now until F30 is fixed.
Thanks for doing this.
Robert
Thanks,
Paul
----- Original Message -----
>
> ----- Original Message -----
>>
>> On 12/5/18 11:25 AM, Robert Moskowitz wrote:
>>>
>>> On 12/5/18 10:43 AM, Paul Whalen wrote:
>>>> There is still an issue in rawhide with the minimal image, I need to
>>>> look
>>>> at further. The server image[1] looks ok- both kernel and initrd are
>>>> there
>>>> anyways, there may be other problems. Or you could try one of the
>>>> desktops.
>>>>
>>>> Paul
>>>>
>>>>
>>>> [1] -
>>>>
https://kojipkgs.fedoraproject.org/compose//rawhide/Fedora-Rawhide-201812...
>>> Followed all the steps with using only uSD and booted up. Went
>>> through the setup, and noticed it was not getting a network connection
>>> reported in the setup, perhaps I should have gone into that option...
>>>
>>> Anyway, first boot continued to login, but:
>>>
>>> [ OK ] Started Update UTMP about System Runlevel Changes.
>>>
>>> Fedora 30 (Server Edition)
>>> Kernel 4.20.0-0.rc5.git1.1.fc30.armv7hl on an armv7l (ttySAC2)
>>>
>>> Web console: https://localhost.localdomain:9090/
>>>
>>> localhost login: root
>>> Password:
>>> -- root: no shell: Permission denied
>>>
>>> Fedora 30 (Server Edition)
>>> Kernel 4.20.0-0.rc5.git1.1.fc30.armv7hl on an armv7l (ttySAC2)
>>>
>>> Web console: https://localhost.localdomain:9090/
>>>
>>> localhost login: root
>>> Password:
>>> Last login: Sun Oct 28 20:34:22 on ttySAC2
>>> -- root: no shell: Permission denied
>>>
>>> Fedora 30 (Server Edition)
>>> Kernel 4.20.0-0.rc5.git1.1.fc30.armv7hl on an armv7l (ttySAC2)
>>>
>>> Web console: https://localhost.localdomain:9090/
>>>
>>> localhost login: rgm
>>> Password:
>>> -- rgm: no shell: Permission denied
>>>
>>> Fedora 30 (Server Edition)
>>> Kernel 4.20.0-0.rc5.git1.1.fc30.armv7hl on an armv7l (ttySAC2)
>>>
>>> Web console: https://localhost.localdomain:9090/
>>>
>>> ===============================
>>>
>>> Why no shell? And can't get to the web console until I figure out if
> Looks like an selinux issue, adding enforcing=0 to the kernel args should
> get you logged in.
>
>>> it got an IP address and which (I have to look into which VLAN that
>>> port on the switch is).
>>>
>>> thanks
>> Hmm. I forgot to grow the rootfs partition. Could it have been out of
>> room?
>>
>> Right now I am falling back to trying F29 armfhp server.
> Thats a better bet, its been tested and should just work for you.
>
> Paul
> _______________________________________________
> arm mailing list -- arm(a)lists.fedoraproject.org
> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
>
11:38 a.m.
New subject: Fedora-Server-armhfp-Rawhide-20181205.n.0-sda fails login on odroid-hc1
On 12/5/18 12:01 PM, Paul Whalen wrote:
----- Original Message -----
>
> On 12/5/18 11:25 AM, Robert Moskowitz wrote:
>>
>> On 12/5/18 10:43 AM, Paul Whalen wrote:
>>> There is still an issue in rawhide with the minimal image, I need to
>>> look
>>> at further. The server image[1] looks ok- both kernel and initrd are
>>> there
>>> anyways, there may be other problems. Or you could try one of the
>>> desktops.
>>>
>>> Paul
>>>
>>>
>>> [1] -
>>>
https://kojipkgs.fedoraproject.org/compose//rawhide/Fedora-Rawhide-201812...
>> Followed all the steps with using only uSD and booted up. Went
>> through the setup, and noticed it was not getting a network connection
>> reported in the setup, perhaps I should have gone into that option...
>>
>> Anyway, first boot continued to login, but:
>>
>> [ OK ] Started Update UTMP about System Runlevel Changes.
>>
>> Fedora 30 (Server Edition)
>> Kernel 4.20.0-0.rc5.git1.1.fc30.armv7hl on an armv7l (ttySAC2)
>>
>> Web console: https://localhost.localdomain:9090/
>>
>> localhost login: root
>> Password:
>> -- root: no shell: Permission denied
>>
>> Fedora 30 (Server Edition)
>> Kernel 4.20.0-0.rc5.git1.1.fc30.armv7hl on an armv7l (ttySAC2)
>>
>> Web console: https://localhost.localdomain:9090/
>>
>> localhost login: root
>> Password:
>> Last login: Sun Oct 28 20:34:22 on ttySAC2
>> -- root: no shell: Permission denied
>>
>> Fedora 30 (Server Edition)
>> Kernel 4.20.0-0.rc5.git1.1.fc30.armv7hl on an armv7l (ttySAC2)
>>
>> Web console: https://localhost.localdomain:9090/
>>
>> localhost login: rgm
>> Password:
>> -- rgm: no shell: Permission denied
>>
>> Fedora 30 (Server Edition)
>> Kernel 4.20.0-0.rc5.git1.1.fc30.armv7hl on an armv7l (ttySAC2)
>>
>> Web console: https://localhost.localdomain:9090/
>>
>> ===============================
>>
>> Why no shell? And can't get to the web console until I figure out if
Looks like an selinux issue, adding enforcing=0 to the kernel args should
get you logged in.
>> it got an IP address and which (I have to look into which VLAN that
>> port on the switch is).
>>
>> thanks
> Hmm. I forgot to grow the rootfs partition. Could it have been out of
> room?
>
> Right now I am falling back to trying F29 armfhp server.
Thats a better bet, its been tested and should just work for you.
Hmmm. gparted shows that I am using 1.64GB out of the base 2.33GB, but
I am going to do a complete install anyway and try again. And the vlan
I was plugged into did not have its dhcp server up and running, so I
switched ports to a different vlan
So I DID do a setup with F29, using the uboot from F30:
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
It works. I am logged in as root on the console. I have a network
connection (have not tested the web admin yet). I wanted to see the
random entropy:
# cat /proc/sys/kernel/random/entropy_avail
3413
Nice! I did not have to add any rng tools almost double what I see on
my Cubietrucks (as I recall).
So supposedly since F28 and definitely F29, the steps for getting Fedora
working on an Odroid-HC1 are straight-forward. Just not directly
supported. You do have to get a recent copy of the uboot into your
hardkernel directory.
Next is get F30 rawhide working then start testing what I can get on the
sata drive.
11:51 a.m.
New subject: Fedora-Server-armhfp-Rawhide-20181205.n.0-sda fails login on odroid-hc1
On 2018-12-05 18:38, Robert Moskowitz wrote:
So I DID do a setup with F29, using the uboot from F30:
U-Boot 2018.09 (Sep 11 2018 - 09:51:41 +0000) for ODROID-XU3/XU4/HC1
a bit offtopic but that uboot does not contain the needed patch for hc2, but it
wont matter for you since you have a hc1
lets hope uboot gets updated at some later stage.
12:09 p.m.
New subject: Fedora-Server-armhfp-Rawhide-20181205.n.0-sda fails login on odroid-hc1
On 12/5/18 12:51 PM, Torbjorn Jansson wrote:
On 2018-12-05 18:38, Robert Moskowitz wrote:
> So I DID do a setup with F29, using the uboot from F30:
>
> U-Boot 2018.09 (Sep 11 2018 - 09:51:41 +0000) for ODROID-XU3/XU4/HC1
>
a bit offtopic but that uboot does not contain the needed patch for
hc2, but it wont matter for you since you have a hc1
lets hope uboot gets updated at some later stage.
It is the latest uboot from the latest rawhide image; but the same I see
in F29. Perhaps there will be a new set of uboot files soon with your
HC2 support.
5:42 p.m.
On 12/4/18 12:51 PM, Peter Robinson wrote:
> On Tue, Dec 4, 2018 at 5:17 PM Robert Moskowitz <rgm(a)htt-consult.com> wrote:
>> Additional bug? in F28 x64 installer:
>>
>> # fedora-arm-image-installer
--image=/home/rgm/arm/Fedora-Minimal-armhfp-Rawhide-20181203.n.0-sda.raw.xz --supported
--media=/dev/sdb
>> cat: /usr/share/doc/fedora-arm-installer//SUPPORTED-BOARDS: No such file or
directory
>>
>> The installer looks at what my system lists as supported boards, rather than
what the image shows and why the double
> You need to update to the latest version.
>
Yeah,,,
I had tried a 'dnf update fedora-arm*' and got nothing to update.
Had problems with the system so did a general dnf update to get the
latest stuff before rebooting and now it works.
So my bad on trying a shortcut to update fedora-arm-image-installer....
No odroid listed, so it is do it the long way, it seems.
The supported boards list is the list that the tool can provision, not
necessarily the boards that Fedora supports in general.
1968
days inactive
1969
days old
25 comments
6 participants
participants (6)
-
Andreas Reschke -
Dennis Gilmore -
Paul Whalen -
Peter Robinson -
Robert Moskowitz -
Torbjorn Jansson