Am , schrieb Stewart Samuels:
Hello Andreas,
I've updated the bug report and also provided the process for
installing the eMMC card. Have you successfully installed F26 on your
eMMC card?
Stewart
On 08/29/2017 12:27 AM, arm...@rirasoft.de wrote:
Am , schrieb den...@ausil.us:
You can drop
Hello Andreas,
I've updated the bug report and also provided the process for installing
the eMMC card. Have you successfully installed F26 on your eMMC card?
Stewart
On 08/29/2017 12:27 AM, arm...@rirasoft.de wrote:
Am , schrieb den...@ausil.us:
You can drop a snippet into a config file
Am , schrieb den...@ausil.us:
You can drop a snippet into a config file that will make sure it's
there. Could you please file a bug against dracut and CC me on it.
Dennis
---cut---
Hello Dennis and Stewart,
I've open a bug against dracut:
https://bugzilla.redhat.com/show_bug.cgi?id=1482825
You can drop a snippet into a config file that will make sure it's there. Could
you please file a bug against dracut and CC me on it.
Dennis
On 28 August 2017 7:49:40 pm GMT-04:00, Stewart Samuels
wrote:
>Reinserting the parameters and rebuilding initramfs does indeed
Reinserting the parameters and rebuilding initramfs does indeed work
after performing the "dnf update". Dracut needs to be updated upstream
to include these modules for the Odroid systems, particularly for the
XU3 & XU4 systems. In the mean time, one can do the builds by hand if
they can
Okay. Rebooting after the "dnf update" fails at the DW_MMC again. I
will check that the modules are there.
Stewart
On 08/28/2017 04:25 PM, den...@ausil.us wrote:
Best bet for usb3 is likely to file an upstream kernel bug and work
with the author. It will likely need someone to bisect
Ok. Will do. Thanks again!
Stewart
On 08/28/2017 04:25 PM, den...@ausil.us wrote:
Best bet for usb3 is likely to file an upstream kernel bug and work
with the author. It will likely need someone to bisect where it failed
using the upstream kernels and processes.
Dennis
On 28 August
Best bet for usb3 is likely to file an upstream kernel bug and work with the
author. It will likely need someone to bisect where it failed using the
upstream kernels and processes.
Dennis
On 28 August 2017 6:22:12 pm GMT-05:00, Stewart Samuels
wrote:
>HI Dennis,
>
HI Dennis,
I've now got the system booting from the eMMC card.
Thanks again for the tip. I noticed earlier as well that the mmc_block
module was not being loaded. I tried adding the mmc_block and
pwrseq_emmc modules as kernel parameters on the append line of the
extlinux.conf file but
El jue, 24-08-2017 a las 16:47 -0700, Stewart Samuels escribió:
> All,
>
> I have been working toward getting the Odroid-Xu4 to boot from the
> eMMC card but the system continues to fail in the same place no
> matter what I try. It dumps me into the dracut shell when it cannot
> find the root
tewart Samuels <searide...@gmail.com>
Cc: arm@lists.fedoraproject.org
Subject: Re: [fedora-arm] Re: Fedora with Odroid-XU4 and Cloudshell 2
On Fri, Aug 25, 2017 at 12:47 AM, Stewart Samuels <searide...@gmail.com> wrote:
> All,
>
> I have been working toward getting the Odroi
On Fri, Aug 25, 2017 at 12:47 AM, Stewart Samuels wrote:
> All,
>
> I have been working toward getting the Odroid-Xu4 to boot from the eMMC card
> but the system continues to fail in the same place no matter what I try. It
> dumps me into the dracut shell when it cannot
Using the same process as described by Dennis below (and what works for
the microSD card boot process, seems to fail to boot using the eMMC
card. The system dumps you into the dracut shell looking for the root
partition. Even though the root partition UUID in
/boot/extlinux/extlinux.conf
> The Fedora 24 system is running with 4.6.5-300.fc24.armv7hl
>
> I've installed follow kernel:
> 4.11.8-300.fc26
> 4.12.5-300.fc26
> and from Rawhide
> 4.13.0-0.rc5.git4.1.fc28
>
> All this kernel have the same problem. If it helps, I've attached dmesg and
> lsmod with this kernel version.
It
>> What does lscpu show? I suspect being a big.little platform you'll
>> find that all the CPUs work but it might only run one cluster at a
>> time, or only power up the second cluster under load. I'm not sure
>> what the algorithms the cpu frequency drivers use for the exynos
>> platforms, I
Am , schrieb Peter Robinson:
On Thu, Aug 24, 2017 at 1:34 AM, Stewart Samuels
wrote:
Okay. I can confirm I can now boot the USB device to completion. I
was
also successfully able to upgrade the system using the "dnf -y update"
command and reboot successfully using the
On Thu, Aug 24, 2017 at 1:34 AM, Stewart Samuels wrote:
> Okay. I can confirm I can now boot the USB device to completion. I was
> also successfully able to upgrade the system using the "dnf -y update"
> command and reboot successfully using the newer kernel. The key was
Okay. I can confirm I can now boot the USB device to completion. I was
also successfully able to upgrade the system using the "dnf -y update"
command and reboot successfully using the newer kernel. The key was NOT
to create a new initramfs image after changing the UUIDs for the root
El mié, 23-08-2017 a las 14:43 -0700, Stewart Samuels escribió:
> HI Dennis
>
> Examining your process stated below, did you really append the u-
> boot.dtb to the u-boot.bin file in the u-boot-dtb.bin file? Why did
> you concatenate them? That seems out of the norm. Why not just
> flash the
HI Dennis
Examining your process stated below, did you really append the
u-boot.dtb to the u-boot.bin file in the u-boot-dtb.bin file? Why did
you concatenate them? That seems out of the norm. Why not just flash
the u-boot.bin file provided by Fedora?
Regards,
Stewart
On 08/23/2017
El mié, 23-08-2017 a las 11:46 -0700, Stewart Samuels escribió:
> Dennis,
>
> Have you tried building the system on an eMMC card and booting that?
> Just curious.
>
> Thanks,
>
> Stewart
I have not, I do not have a emmc card
Dennis
> On 08/23/2017 10:41 AM, Dennis Gilmore wrote:
> >
Dennis,
Have you tried building the system on an eMMC card and booting that?
Just curious.
Thanks,
Stewart
On 08/23/2017 10:41 AM, Dennis Gilmore wrote:
El mié, 23-08-2017 a las 09:13 -0700, Stewart Samuels escribió:
Hi Dennis,
I have been doing the same process as you with the
El mié, 23-08-2017 a las 09:13 -0700, Stewart Samuels escribió:
> Hi Dennis,
>
> I have been doing the same process as you with the exception that I
> change the UUIDs in extlinux.conf and /etc/fstab. The other thing I
> do, because I change update the UUIDs, is create a new initramfs. I
> will
El mié, 23-08-2017 a las 16:56 +0200, Andreas Reschke escribió:
> Am 23.08.2017 um 16:20 schrieb Dennis Gilmore:
> --
> >
>
> Hello Dennis,
>
> that looks beautiful. You have a running Odroid-XU4 with actual
> Kernel
> with Fedora 26 !!
>
> How did you manage it? I haven't so much luck with
Am 23.08.2017 um 16:20 schrieb Dennis Gilmore:
---cut---
>
> I setup a new SD card installing the released server image, and after
> appending cpuidle.off=1 it booted fine
>
> U-Boot 2017.05 (Jun 24 2017 - 16:40:39 +) for ODROID-XU3
>
> CPU: Exynos5422 @ 800 MHz
> Model: Odroid XU3 based
El mar, 22-08-2017 a las 18:18 -0700, Stewart Samuels escribió:
> Dennis,
>
> How do I rebuild the initrd? I can do this on my raspberryPI 2
> running Fedora 26 if I know the procedure to do it?
you would have to use an arm device mount the filesystems, bind mount
in /dev /proc /sys chroot in,
Dennis,
How do I rebuild the initrd? I can do this on my raspberryPI 2 running
Fedora 26 if I know the procedure to do it?
In the mean time, I will try to do the modprobe. Would I do this within
the dracut shell when the system aborts?
Stewart
On 08/22/2017 04:24 PM,
Here is the output from cat /proc/modules:
-
dracut:/#
dracut:/# cat /proc/modules
hid_logitech_hidpp 24576 0 - Live 0xbf461000
xhci_plat_hcd 16384 0 - Live 0xbf44f000
dwc3 110592 0 - Live 0xbf407000
ulpi 16384 1 dwc3, Live
cat /proc/partitions in dracut returns no output other than the dracut
prompt. An ls -l command shows listing output: See the following:
-
dracut:/# pwd
/
dracut:/# cat /proc/partitions
dracut:/# ls -l
total 12
lrwxrwxrwx 1
What is the output of "cat /proc/partitions" next step would be making sure the
right modules for the block storage are loaded.
Dennis
On 22 August 2017 6:03:52 pm GMT-05:00, Stewart Samuels
wrote:
>Dennis,
>
>I let the system try to boot and gave it more time with the
BTW, the device is an eMMC device connected to the system via a USB
adaptor. Would that make a difference per the UUIDs?
Stewart
On 08/22/2017 04:03 PM, Stewart Samuels wrote:
Dennis,
I let the system try to boot and gave it more time with the dracut
messages. It dumps me into the
Dennis,
I let the system try to boot and gave it more time with the dracut
messages. It dumps me into the dracut login via emergency mode looking
for the root partition it seems. It cannot find the system drive via
the UUID that I showed in my last email is the UUID for the root
partition.
Dennis,
I have confirmed the UUID is still 11cf09b5-43b2-4588-969d-550b4e2af05.
See output from my Ubuntu login that follows. Our root partition here
shows up as /dev/sda4.
Stewart
--
El mar, 22-08-2017 a las 15:14 -0700, Stewart Samuels escribió:
> Hello Dennis,
>
> The parameter you provided me below was incorrect (spelling error).
> I used cpuidle.off=1 and the system now boot much further, but
> eventually goes into a:
>
> > dracut-initqueue[493]: Warning:
Hello Dennis,
The parameter you provided me below was incorrect (spelling error). I
used cpuidle.off=1 and the system now boot much further, but eventually
goes into a:
dracut-initqueue[493]: Warning: dracut-initqueue timeout - starting
timeout scripts
loop and never completes the
Hi Dennis,
I placed this parameter value on the append line of extlinux.conf. This
did not get me past the point of failure in the boot process. Did I
insert the parameter on the correct line? If not, please provide more
information, perhaps even an example.
Thanks for your response and
El mar, 15-08-2017 a las 17:25 -0700, Stewart Samuels escribió:
> Ok. The u-boot issue was my mistake. I was trying to use the
> /usr/share/uboot/odroid u-boot files instead of the
> /usr/share/uboot/odroid-xu3 files. Now I am getting output to the
> serial console and the system begins the
On Wed, Aug 16, 2017 at 4:26 PM, Stewart Samuels wrote:
>
>
> On 08/16/2017 07:53 AM, Peter Robinson wrote:
>>
>> On Wed, Aug 16, 2017 at 3:14 PM, Stewart Samuels
>> wrote:
>>>
>>>
>>> On 08/16/2017 04:14 AM, arm...@rirasoft.de wrote:
Am ,
On 08/16/2017 07:53 AM, Peter Robinson wrote:
On Wed, Aug 16, 2017 at 3:14 PM, Stewart Samuels wrote:
On 08/16/2017 04:14 AM, arm...@rirasoft.de wrote:
Am , schrieb Stewart Samuels:
Ok. The u-boot issue was my mistake. I was trying to use the
On Wed, Aug 16, 2017 at 3:14 PM, Stewart Samuels wrote:
>
>
> On 08/16/2017 04:14 AM, arm...@rirasoft.de wrote:
>>
>> Am , schrieb Stewart Samuels:
>>>
>>> Ok. The u-boot issue was my mistake. I was trying to use the
>>> /usr/share/uboot/odroid u-boot files instead of the
Am , schrieb Stewart Samuels:
Ok. The u-boot issue was my mistake. I was trying to use the
/usr/share/uboot/odroid u-boot files instead of the
/usr/share/uboot/odroid-xu3 files. Now I am getting output to the
serial console and the system begins the boot process as expected.
However, it hangs
Ok. The u-boot issue was my mistake. I was trying to use the
/usr/share/uboot/odroid u-boot files instead of the
/usr/share/uboot/odroid-xu3 files. Now I am getting output to the
serial console and the system begins the boot process as expected.
However, it hangs in the kernel seemingly
org
Subject: [fedora-arm] Re: Fedora with Odroid-XU4 and Cloudshell 2
On 11 August 2017 at 06:29, Andreas Reschke <arm...@rirasoft.de> wrote:
Am 10.08.2017 um 12:26 schrieb Peter Robinson:
> On Wed, Aug 9, 2017 at 9:17 PM, Stewart Samuels <searide...@gmail.com> wrote:
>> He
On 11 August 2017 at 06:29, Andreas Reschke wrote:
> Am 10.08.2017 um 12:26 schrieb Peter Robinson:
> > On Wed, Aug 9, 2017 at 9:17 PM, Stewart Samuels
> wrote:
> >> Hello Paul,
> >>
> >> I'm not getting any output from the Odroid serial port, even from
Am 10.08.2017 um 12:26 schrieb Peter Robinson:
> On Wed, Aug 9, 2017 at 9:17 PM, Stewart Samuels wrote:
>> Hello Paul,
>>
>> I'm not getting any output from the Odroid serial port, even from
>> u-boot.bin. How can I tell if the issue is from u-boot.bin or after? Also,
>
>
Am 09.08.2017 um 20:57 schrieb Stewart Samuels:
> Hello Andreas,
>
> I have been away for awhile as my wife and I relocated from the East
> Coast of the U.S. to Oregon. Now that we are settling in a bit, I am
> once again finding some time to work on my Odroid XU4.
>
> I hope all is well with
On Wed, Aug 9, 2017 at 9:17 PM, Stewart Samuels wrote:
> Hello Paul,
>
> I'm not getting any output from the Odroid serial port, even from
> u-boot.bin. How can I tell if the issue is from u-boot.bin or after? Also,
If you don't get output from u-boot it's a u-boot or a
Hi Stewart,
- Original Message -
> Hello Andreas,
>
> I have been away for awhile as my wife and I relocated from the East
> Coast of the U.S. to Oregon. Now that we are settling in a bit, I am
> once again finding some time to work on my Odroid XU4.
>
> I hope all is well with you.
Hello Andreas,
I have been away for awhile as my wife and I relocated from the East
Coast of the U.S. to Oregon. Now that we are settling in a bit, I am
once again finding some time to work on my Odroid XU4.
I hope all is well with you. I see you have been working hard on trying
to get
49 matches
Mail list logo