[fedora-arm] Re: aarch64 - fedora28 - Fedora-Server-28-20180327.n.0.aarch64.raw.xz

[Pierre-Francois RENARD]

same for me here:)
new kernel 4.16.0-300-fc28.aarch64 is wroking fine and onboard ethernet is 
working :)

Thanks a lot
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] Re: aarch64 - fedora28 - Fedora-Server-28-20180327.n.0.aarch64.raw.xz

[Peter Robinson]

On Wed, Apr 4, 2018 at 2:22 PM, Richard Ryniker  wrote:
>>  I can manually configure my Raspberry Pi model 3B-plus on-board wired
>>  Ethernet port to operate. It is indeed only DHCP configuration that
>>  fails, but only with the on-board device; DHCP configuration of a USB
>>  wired Ethernet port works fine.
>>
>> Have you tried the 4.16.0-300 kernel that's in (or on it's way) to 
>> updates-testing?
>
> Works fine, Peter Robinson.  Thank you.

Thought it might ;-)
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] Re: aarch64 - fedora28 - Fedora-Server-28-20180327.n.0.aarch64.raw.xz

[Richard Ryniker]

>  I can manually configure my Raspberry Pi model 3B-plus on-board wired
>  Ethernet port to operate. It is indeed only DHCP configuration that
>  fails, but only with the on-board device; DHCP configuration of a USB
>  wired Ethernet port works fine.
> 
> Have you tried the 4.16.0-300 kernel that's in (or on it's way) to 
> updates-testing?

Works fine, Peter Robinson.  Thank you.
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] Re: aarch64 - fedora28 - Fedora-Server-28-20180327.n.0.aarch64.raw.xz

[Peter Robinson]

On Tue, 3 Apr 2018, 20:11 Richard Ryniker,  wrote:

> I can manually configure my Raspberry Pi model 3B-plus on-board wired
> Ethernet port to operate.  It is indeed only DHCP configuration that
> fails, but only with the on-board device; DHCP configuration of a USB
> wired Ethernet port works fine.
>

Have you tried the 4.16.0-300 kernel that's in (or on it's way) to
updates-testing?
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] Re: [aarch64 - fedora28 - Fedora-Server-28-20180327.n.0.aarch64.raw.xz ]

[Richard Ryniker]

>Why disable SELinux?

It does not provide any significant value for my Raspberry Pi computer
intended for use as an embedded system or in a DACS role, where network
security is important but a simple (root or user) local privilege scheme
is fine.  The goals of SELinux are important, but its rocky history
suggests there will continue to be problems.  I am reluctant to spend
resources on SELinux for these Raspberry Pi systems, but will do so for
open or multi-user systems.

Actually, the fedora-arm-image-installer "--selinux=off" option
configures SELinux to permissive mode, therefore it will still report
troubles but not interrupt programs because of them.  This seems a good
middle ground.

>When in the boot process? Was it the grub2 menu

Possibly.  I do not know.  If you think it useful, I will repeat the
experiment and make a video recording of the console.  I do not see
evidence of the pause in the log files:

http://ryniker.org/Fedora/dmesg03
http://ryniker.org/Fedora/log03

>So why not just use the minimal image?

I probobly ought to, but in this case I wanted to try an aarch64 image
similar to one that Tomáš Frolík reported caused him difficulty.

>I've had reports of this [on board wired Ethernet port] working fine

From the log file, it appears to fail (repeatedly) during appempts to
perform a DHCP operation for its default configuration.  However, default
configuration of the USB Ethernet dongle uses DHCP without any problem.
This suggests a hardware setup or driver issue is the culprit.
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] Re: [aarch64 - fedora28 - Fedora-Server-28-20180327.n.0.aarch64.raw.xz ]

[Peter Robinson]

On Tue, Apr 3, 2018 at 10:17 AM, Pierre-Francois RENARD
 wrote:
> Ok guys,
>
> I tried the last image this morning :)
> I am using the Server one
>
> With fedora-arm-image-installer, there are a few things that are not working 
> ( especially the LVM management, so root is not resized, passwd cannot be 
> erased ...)

As per the documentation you cal also just dd it out and expand the
LVM to your liking once it's booted.

https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#Manual

> I am working on a small hack of the script to managed that :)

Pull requests are welcome:
https://pagure.io/arm-image-installer

> I tried then to boot on 2 different rpi3b+
> here is what I discovered
>
> 1/ it is loading the EFI firmware ("starting EFI application at 01000 
> ..." message is printed

That;s expected, it is booting via EFI for aarch64

> 2/ "8xx_eth Waiting for PHY auto negociation to complete..."
> 2.1/ no ethernet cable => printing something ending by "-5" like an infinite 
> loop
> 2.2/ ethernet cable present => it is OK and grub menu is printed and then 
> kernel linux is loaded, but screen goes black each time
> but after a lot of time I finally have the configuration menu :)
>
> I configured it, but ethernet was not a success (it is the embedded port).
> After reboot same issue
> black screen for a very long time
> no ethernet

I've had reports of the ethernet working just fine by a few people, I
suggest installing this kernel [1] as there's improvements to
ethernet, at least static MAC address, else you can wait until it
lands in a stable image.

[1] https://koji.fedoraproject.org/koji/buildinfo?buildID=1064791
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] Re: [aarch64 - fedora28 - Fedora-Server-28-20180327.n.0.aarch64.raw.xz ]

[Pierre-Francois RENARD]

Ok guys,

I tried the last image this morning :)
I am using the Server one 

With fedora-arm-image-installer, there are a few things that are not working ( 
especially the LVM management, so root is not resized, passwd cannot be erased 
...)

I am working on a small hack of the script to managed that :)


I tried then to boot on 2 different rpi3b+
here is what I discovered

1/ it is loading the EFI firmware ("starting EFI application at 01000 ..." 
message is printed
2/ "8xx_eth Waiting for PHY auto negociation to complete..."
2.1/ no ethernet cable => printing something ending by "-5" like an infinite 
loop
2.2/ ethernet cable present => it is OK and grub menu is printed and then 
kernel linux is loaded, but screen goes black each time
but after a lot of time I finally have the configuration menu :)

I configured it, but ethernet was not a success (it is the embedded port).
After reboot same issue
black screen for a very long time
no ethernet

Fox

___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] Re: [aarch64 - fedora28 - Fedora-Server-28-20180327.n.0.aarch64.raw.xz ]

[Peter Robinson]

On Tue, Apr 3, 2018 at 5:02 AM, Richard Ryniker  wrote:
> I used Fedora-Workstation-28-20180402.n.0.aarch64.raw.xz and can boot
> successfully on my Raspberry Pi model 3B-plus.  I used:
>
> fedora-arm-image-installer  --target=rpi3 --media=/dev/sdi --norootpass 
> --resizefs --selinux=off 
> --image=fedora/F28/Fedora-Workstation-28-20180402.n.0.aarch64.raw.xz

Why disable SELinux, there should be no need to do that, is there a
particular reason or "just because"?

> to prepare a new SD card, but the root file system was not resized.  I
> had to do that manually.  A dtb file for the 3-plus is already in this
> image, there is no need to do anything about that.

Correct, rc7 is now stable and it includes that file, there's been
further updates and improvements that will be going out stable soon.

> There was some hesitation early in the boot process. (Maybe fsck? Maybe
> some First Boot procedure timing out, or perhaps some parameter-setting
> activity - there was something that looked like a text menu but it
> disappeared before I could read it.)  It lasted around two minutes.

When in the boot process? Was it the grub2 menu, that should be the
only text menu you get with a Workstation install.

> After boot, I logged on as root, created a user, enabled sshd, and can
> now connect to the machine using ssh.
>
> Note that before I booted the system, I changed the default target from
> graphical to multi-user, in order to avoid gnome-shell troubles:

So why not just use the minimal image?

> https://bugzilla.redhat.com/show_bug.cgi?id=1561184
>
> I suspect the wired Ethernet port is not operational (I used a USB
> Ethernet dongle for my ssh connection.)  I have not tried any wi-fi
> activity.

I've had reports of this working fine, that said it should be much
improved with the 4.16.0-300 or later kernel when that lands including
stable MAC address.

> There are problems, but a lot is working.  Certainly enough to make
> it reasonable to explore and learn what needs work.

Well the support has just landed, I've also been traveling so not had
the time to actually focus on it, we should have it to parity with the
original RPi3 in time for GA freeze in a couple of weeks.
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] Re: [aarch64 - fedora28 - Fedora-Server-28-20180327.n.0.aarch64.raw.xz ]

[Richard Ryniker]

I used Fedora-Workstation-28-20180402.n.0.aarch64.raw.xz and can boot
successfully on my Raspberry Pi model 3B-plus.  I used:

fedora-arm-image-installer  --target=rpi3 --media=/dev/sdi --norootpass 
--resizefs --selinux=off 
--image=fedora/F28/Fedora-Workstation-28-20180402.n.0.aarch64.raw.xz

to prepare a new SD card, but the root file system was not resized.  I
had to do that manually.  A dtb file for the 3-plus is already in this
image, there is no need to do anything about that.

There was some hesitation early in the boot process. (Maybe fsck? Maybe
some First Boot procedure timing out, or perhaps some parameter-setting
activity - there was something that looked like a text menu but it
disappeared before I could read it.)  It lasted around two minutes.

After boot, I logged on as root, created a user, enabled sshd, and can
now connect to the machine using ssh.

Note that before I booted the system, I changed the default target from
graphical to multi-user, in order to avoid gnome-shell troubles:

https://bugzilla.redhat.com/show_bug.cgi?id=1561184

I suspect the wired Ethernet port is not operational (I used a USB
Ethernet dongle for my ssh connection.)  I have not tried any wi-fi
activity.

"dnf upgrade" wqs successful, and updated 60 packages.

There are problems, but a lot is working.  Certainly enough to make
it reasonable to explore and learn what needs work.  

___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] Re: [aarch64 - fedora28 - Fedora-Server-28-20180327.n.0.aarch64.raw.xz ]

[Peter Robinson]

On Mon, Apr 2, 2018 at 8:46 PM, Pierre-Francois RENARD
 wrote:
> Hi again,
> I was not able to boot this way.
>
> I tried then to do all the stuffs (update to latest 28 ) with a rpi2 and it 
> worked.
> But when I try to boot this sd card on the rpi3b+ it is not working.
> I can see the EFI boot + grub menu.
> Then the screen goes black and nothing more.

HDMI based screen? Serial console? More details please.

I have rebased a bunch of stuff around the support for the 3+, there's
not an official Fedora kernel build just yet but you can get a scratch
 and test it [1]

[1] https://koji.fedoraproject.org/koji/taskinfo?taskID=26121358
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] Re: [aarch64 - fedora28 - Fedora-Server-28-20180327.n.0.aarch64.raw.xz ]

[Pierre-Francois RENARD]

I did it already.
I checked the /boot/dtb/broadcom/ directory and I have 2 files

-rw-r--r--.  1 root root 12611 Mar 26 18:10 bcm2837-rpi-3-b.dtb
-rw-r--r--.  1 root root 12933 Mar 26 18:10 bcm2837-rpi-3-b-plus.dtb


I am running kernel 4.16.0-0.rc7.git0.1.fc28.aarch64 and Peter was talking 
about rc6?
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] Re: [aarch64 - fedora28 - Fedora-Server-28-20180327.n.0.aarch64.raw.xz ]

[Richard Ryniker]

See Peter Robinson's post on March 23, 2018, at 10:42 PM that details how
to copy the Raspberry Pi device tree file for the model 3+. 
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org

[fedora-arm] Re: [aarch64 - fedora28 - Fedora-Server-28-20180327.n.0.aarch64.raw.xz ]

[Pierre-Francois RENARD]

Hi again,
I was not able to boot this way.

I tried then to do all the stuffs (update to latest 28 ) with a rpi2 and it 
worked.
But when I try to boot this sd card on the rpi3b+ it is not working.
I can see the EFI boot + grub menu.
Then the screen goes black and nothing more.

How can I try to understand what's going on ? 

Thanks
Fox
___
arm mailing list -- arm@lists.fedoraproject.org
To unsubscribe send an email to arm-le...@lists.fedoraproject.org