mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Fritz Emboli <fritz.emboli@gmail.com>
To: PTXdist Mailing List <ptxdist@pengutronix.de>
Subject: [ptxdist] DistroKit Raspberry 2
Date: Sat, 24 Jun 2017 18:14:28 +0200	[thread overview]
Message-ID: <CAC+LiDScEoHbNYEcGUZfE=dKx1s2ugMYMQZvFsrgfZ+H=brVOg@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2985 bytes --]

Hi,

i tried DistroKit.

ptxdist go; ptxdist images went through.

But when i try to boot, i get this:

barebox 2016.05.0-20160610-1 #1 Sat Jun 24 14:46:36 CEST 2017


Board: Raspberry Pi 2 Model B
bcm2835-cs 3f003000.timer: probe failed: Device or resource busy
bcm2835-gpio 3f200000.gpio: probed gpiochip-1 with base 0
bcm2835-gpio bcm2835-gpio0: probe failed: Device or resource busy
malloc space: 0x07be4000 -> 0x07fe3fff (size 4 MiB)
bcm2835_mci bcm2835_mci0: registered as bcm2835_mci0
mci0: detected SD card version 2.0
mci0: registered disk0
environment load /boot/barebox.env: No such file or directory
Maybe you have to create the partition.
running /env/bin/init...

Hit m for menu or any other key to stop autoboot:  1
ext4 ext40: EXT2 rev 1, inode_size 128
blspec: blspec_scan_directory: /mnt/disk0.1 loader/entries
blspec: ignoring entry with incompatible devicetree "ti,am335x-bone"
blspec: ignoring entry with incompatible devicetree "ti,am335x-bone-black"
blspec: blspec_scan_directory: disk0.1 loader/entries
blspec: booting Raspberry Pi 2 - Pengutronix-DistroKit from mci0

Loading ARM Linux zImage '/mnt/disk0.1//boot/zImage'
Loading devicetree from '/mnt/disk0.1//boot/bcm2836-rpi-2-b.dtb'
commandline: console=ttyAMA0,115200 loglevel=5 systemd.log_level=warning
systemd.show_status=auto loglevel=5 systemd.log_level=warning
systemd.show_status=auto root=/dev/mmcblk0p2 rootfstype=ext4 rootwait rw
[    0.000836] arm_arch_timer: WARNING: Invalid trigger for IRQ16, assuming
level low
[    0.000856] arm_arch_timer: WARNING: Please fix your firmware
[    0.000875] arm_arch_timer: WARNING: Invalid trigger for IRQ17, assuming
level low
[    0.000886] arm_arch_timer: WARNING: Please fix your firmware
[    0.067195] arm_arch_timer: WARNING: Invalid trigger for IRQ16, assuming
level low
[    0.067199] arm_arch_timer: WARNING: Please fix your firmware
[    0.067211] arm_arch_timer: WARNING: Invalid trigger for IRQ17, assuming
level low
[    0.067214] arm_arch_timer: WARNING: Please fix your firmware
[    0.068191] arm_arch_timer: WARNING: Invalid trigger for IRQ16, assuming
level low
[    0.068195] arm_arch_timer: WARNING: Please fix your firmware
[    0.068202] arm_arch_timer: WARNING: Invalid trigger for IRQ17, assuming
level low
[    0.068205] arm_arch_timer: WARNING: Please fix your firmware
[    0.069086] arm_arch_timer: WARNING: Invalid trigger for IRQ16, assuming
level low
[    0.069090] arm_arch_timer: WARNING: Please fix your firmware
[    0.069097] arm_arch_timer: WARNING: Invalid trigger for IRQ17, assuming
level low
[    0.069100] arm_arch_timer: WARNING: Please fix your firmware
[    1.170790] i2c-bcm2835 3f805000.i2c: Could not read clock-frequency
property
[    1.325575] dwc2 3f980000.usb: 3f980000.usb supply vusb_d not found,
using dummy regulator
[    1.334002] dwc2 3f980000.usb: 3f980000.usb supply vusb_a not found,
using dummy regulator

Then the green LED just double flashes.

Any idea how i could proceed?

Thanks

  Fritz

[-- Attachment #1.2: Type: text/html, Size: 3439 bytes --]

[-- Attachment #2: Type: text/plain, Size: 91 bytes --]

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

                 reply	other threads:[~2017-06-24 16:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAC+LiDScEoHbNYEcGUZfE=dKx1s2ugMYMQZvFsrgfZ+H=brVOg@mail.gmail.com' \
    --to=fritz.emboli@gmail.com \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox