Re: Fwd: Re: CMA on raspberry pi 4
by ng0177＠gmail.com
Thanks. Just out of curiosity, how can I use "dmesg" w/o keyboard?
Appreciate, Thomas
On Mon, Aug 3, 2020 at 7:37 PM Stefan Wahren <stefan.wahren(a)i2se.com> wrote:
> Hi,
>
> Am 03.08.20 um 12:04 schrieb Peter Robinson:
> > On Mon, Aug 3, 2020 at 10:57 AM <ng0177(a)gmail.com> wrote:
> >> I used today's rawhide image from
> https://dl.fedoraproject.org/pub/fedora/linux/releases/32/Workstation/aar...
> and get to the Welcome screen but then neither USB keyboard nor mouse work
> and I am stuck on my RPi4/8GB.
> > I don't think the support for loading the USB firmware on the 8Gb
> > model has made it upstream yet. In the 1/2/4gb models it was loaded by
> > the Raspberry Pi firmware from SPI flash, in the 8Gb model they
> > dropped the SPI flash and there has to be kernel patches to load it.
> > That problem is unrelated to the CMA/DMA issue.
>
> the USB quirk is available in Linux 5.8 [1], but there is a related
> report [2].
>
> It seems to be related to the board revision and possibly arm64.
>
> A dmesg output might be helpful.
>
> Regards
> Stefan
>
> [1] -
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit...
>
> [2] - https://github.com/raspberrypi/linux/issues/3747
>
>
>
>
3 years, 10 months
Re: Fwd: Re: CMA on raspberry pi 4
by Stefan Wahren
Am 04.08.20 um 21:46 schrieb ng0177(a)gmail.com:
> Thanks. Just out of curiosity, how can I use "dmesg" w/o keyboard?
In general there are two options
1) connect via SSH (not sure this a real option because this service
could be disabled per default)
2) connect via debug UART (requires serial to USB adapter)
An alternative solution would be try to mount the SD card on a PC and
look for the kernel messages in /var/log
Regards
>
> Appreciate, Thomas
>
> On Mon, Aug 3, 2020 at 7:37 PM Stefan Wahren <stefan.wahren(a)i2se.com
> <mailto:stefan.wahren@i2se.com>> wrote:
>
> Hi,
>
> Am 03.08.20 um 12:04 schrieb Peter Robinson:
> > On Mon, Aug 3, 2020 at 10:57 AM <ng0177(a)gmail.com
> <mailto:ng0177@gmail.com>> wrote:
> >> I used today's rawhide image from
> https://dl.fedoraproject.org/pub/fedora/linux/releases/32/Workstation/aar...
> and get to the Welcome screen but then neither USB keyboard nor
> mouse work and I am stuck on my RPi4/8GB.
> > I don't think the support for loading the USB firmware on the 8Gb
> > model has made it upstream yet. In the 1/2/4gb models it was
> loaded by
> > the Raspberry Pi firmware from SPI flash, in the 8Gb model they
> > dropped the SPI flash and there has to be kernel patches to load it.
> > That problem is unrelated to the CMA/DMA issue.
>
> the USB quirk is available in Linux 5.8 [1], but there is a related
> report [2].
>
> It seems to be related to the board revision and possibly arm64.
>
> A dmesg output might be helpful.
>
> Regards
> Stefan
>
> [1] -
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit...
>
> [2] - https://github.com/raspberrypi/linux/issues/3747
>
>
>
3 years, 10 months
Re: Fedora Server 36 VGA output on a Raspberry Pi 3b
by Brandon Nielsen
On 3/15/22 3:04 PM, Peter Robinson wrote:
>> Was hoping to add a bit of test coverage, and ran into a strange issue.
>>
>> The beta Server compose[0] boots, but there is no VGA output after the
>> initial rainbow, u-boot, GRUB, and "Booting..." text (using an HDMI->VGA
>> adapter) on a Raspberry Pi 3b. Cockpit works so boot clearly succeeded.
>>
>> Fedora Minimal for the same compose[1] works as expected with text based
>> initial setup appearing over VGA.
>>
>> Is this a known issue or intended behavior? I couldn't find anything in
>> Bugzilla.
>
> The HDMI to VGA adapters have always been as ropey as hell on the RPi,
> in fact they were never particularly great even on the OLPCs back in
> the day either.
>
> They're also very variable from device to device so it's very much a
> case of it may or may not work but we don't really get a lot of
> reports either way these days TBH.
>
> P
I figured that was probably the case. The only thing of note I see in
the logs is:
Feb 16 00:01:21 fedora kernel: of_clk_hw_onecell_get: invalid index 15
Feb 16 00:01:21 fedora kernel: [drm:vc4_vec_bind [vc4]] *ERROR* Failed
to get clock: -2
Feb 16 00:01:21 fedora kernel: vc4-drm soc:gpu: failed to bind
3f806000.vec (ops vc4_vec_ops [vc4]): -2
Interesting that I don't see the issue on minimal.
2 years, 2 months
Re: using the rpi gpio python module
by Aleksandra Fedorova
I am not an expert but this is what I've got on the topic:
0) There is a package in Fedora repositories: libgpiod-utils. It provides command line interface(gpioset and gpioget commands) to operate GPIO pins. It is simple, it is based on the C library, not Python, and it just works.
But Python is more fun, so we don't stop here.
1) cpuinfo and "RuntimeError: This module can only be run on a Raspberry Pi!"
On Raspbian cpuinfo looks as follows:
---
$ cat /proc/cpuinfo
...
Hardware : BCM2835
Revision : a22082
Serial : ***
---
but Fedora defines itself as a generic device tree based system
---
$ cat /proc/cpuinfo
...
Hardware : Generic DT based system
Revision : 0000
Serial : ***
---
Many GPIO-related libraries are written for Raspbian and they search through /proc/cpuinfo for the system information.
See for example https://sourceforge.net/p/raspberry-gpio-python/code/ci/default/tree/sour... Here RPi.GPIO doesn't recognize the platform at all and fails with the "This module can only be run on a Raspberry Pi!"
Originally I expected this to be easy to fix. So I filed a bug https://bugzilla.redhat.com/show_bug.cgi?id=1471731 and then tried to workaround it locally. I patched the code of the RPi.GPIO library simply replacing the "/proc/cpuinfo" path with the "/etc/rpi3-cpuinfo.txt" where I've put the raspbian-style system description.
Now the library can be imported. But the simple script like this:
---
import RPi.GPIO as GPIO
GPIO.setmode(GPIO.BCM)
GPIO.setup(12, GPIO.OUT, initial=GPIO.HIGH)
---
fails with the segmentation fault.
So it seems to be more differences than expected, and after looking into the sources again: https://sourceforge.net/p/raspberry-gpio-python/code/ci/default/tree/sour... I gave up on the idea of making it work, since it uses a lot of hardcoded offset parameters and operates on /dev/mem which is much lower level then I could handle.
2) SYSFS
There is another interface to work with GPIO pins, which is supported by some libraries like https://github.com/derekstavis/python-sysfs-gpio It operates by exporting pins via /sys/class/gpio/export and so on.
But is disabled by default on Fedora kernel.
You can enable it by setting CONFIG_GPIO_SYSFS=y in the kernel config and recompiling the kernel.
Note though that this interface is considered to be deprecated in the kernel, and will be removed by 2020, but for now it works.
3) GPIO character device
Now there is a new character device interface provided by the kernel. It exposes set of GPIO pins as a single file descriptor, and you can interact with it via ioctl syscalls (https://github.com/torvalds/linux/blob/master/include/uapi/linux/gpio.h). It is used by the libgpiod library mentioned in 0) above.
I was looking for the Pythonic support for it here or there but there is none. So I created my own very simple wrapper
https://github.com/bookwar/python-gpiodev/
I tested it of F26, F27(both armv7hl) on Raspberry Pi 3, and you can switch LED lights and read button events with it.
--
Aleksandra Fedorova
bookwar
6 years, 5 months
Re: Raspberry Pi and its 7" display
by Peter Robinson
On Tue, Dec 11, 2018 at 3:18 AM Kevin Cummings
<cummings(a)kjchome.homeip.net> wrote:
>
> On 12/10/18 9:20 PM, Peter Robinson wrote:
> >> Hi Folks,
> >> Longtime Fedora user here. Last winter, I got a Raspberry Pi, and
> >> installed F28 on it. Using the HDMI output, it works well. Recently, I
> >
> > Any reason for F-28 instead of F-29?
>
> Lazy? I think you're lucky I upgraded it from the F27 I originally
> installed....
>
> >> picked up the Raspberry Pi 7" display (and case). After hooking up the
> >> display to the Pi via the ribbon cable, I booted it up.
> >>
> >> The 7" display works well as the initial console, and I see all the
> >> usual messages go flying by. At some point (when it decides to switch
> >> to graphics mode) the display goes blank. Nothing on it. I cannot
> >> switch even to a virtual console. The new case blocks using the HDMI
> >> port, so I had to remove the Pi from the case (while leaving the ribbon
> >> cable attached to the display). After plugging a monitor into the HDMI
> >> port, what I discovered was that the Pi boots using the display as
> >> console, then switches to the HDMI port for the X11 driver. (not useful)
> >
> > If you block the vc4 driver it will continue to work as a pure non
> > accelerated display, at the moment when the accelerated driver
> > initialises it can't detect the DSI attached display so it goes blank.
>
> So if I blacklist the vc4 driver, will an X11 session start up on the
> display? If not, can I modify the boot up to bring Linux up in command
> line only mode? Will the virtual consoles work in that mode?
>
> I don't (yet) understand the uboot stuff. In a PC, I can interrupt grub
> and edit the command line to put kernel options on the boot line. I
> don't know how to do that with uboot.
U-Boot in basically a firmware so in the context you put it it's not
grub2 or like it, on aarch64 mode on the Raspberry Pi we have grub2,
in F-30 we should this for ARMv7 too, The extlinux boot menu is
rudimentary, it doesn't support editing.
> > The support status is documented in the Fedora Raspberry Pi FAQ [1]
>
> Yes, it talks about supporting the touchscreen display. But there are
> two parts: The graphics display, and the touch screen. Is the graphics
> screen currently supported?
No
> I can wait for touchscreen support.
>
> >> How can I get the X11 display to come up on the 7" display in graphics
> >> mode. What do I need? A new xorg-x11-drv driver? A newer kernel?
> >
> > The Raspberry Pi doesn't have, nor will ever have a xorg driver. The
> > driver is a 3D mesa accelerated driver, the 2D support is via glamor
> > (2D over 3D) to mesa.
>
> Sorry, in all the PCs I've every used, there has been a specific driver
> to get X11 to run (reasonably) on every different video card I've had to
> run X11 on. I'm not familiar with using them as only frame-buffer. So
> this is new territory for me.
X11 drivers are going away, even in the PC case, EG these days for new
intel devices it uses mesa/3D glamor for Xorg too.
> > The upstream open source driver we use doesn't yet fully support the
> > touch screen display, I don't believe it's far off but upstream is yet
> > to finish the work to have it supported.
>
> Yes, that's what [1] says.
>
> >> I'd like to turn this into a MythTV server (with a USB capture) and use
> >> the display as a system console with the ability to watch videos on it.
> >> (Yeah, I'm aware that its only a 800x400 screen.) Failing that, I'd
>
> I should have said 800x480 screen, and I also see that text mode
> actually runs at 720x480?
>
> >> like to use it in a "tablet" mode and get used to the touch screen
> >> interface.
> >
> > Well when it's supported upstream it will be enabled.
> >
> > [1] https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#Is_the_Rasp...
> > _______________________________________________
> > 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
>
> Thanks for the help so far.
>
> --
> Kevin J. Cummings
> cummings(a)kjchome.homeip.net
> cummings(a)kjc386.framingham.ma.us
> kjchome(a)icloud.com
> Registered Linux User #1232 (http://www.linuxcounter.net/)
> _______________________________________________
> 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
5 years, 5 months
Re: Raspberry PI 3 locking up
by Winfried de Heiden
Hi all,
Confirm:
"...came back, and the monitor (tv in this case) was off, as it shuts
itself off after not getting a signal for x amount of time. The
keyboard didn't respond to any input. The ssh session I had open locked
up, and I couldn't connect to it on the IP address the router said it
was using..."
Seems exactly the same for me :(
Winfried
-----Oorspronkelijke bericht-----
Datum: Wed, 1 Feb 2017 23:54:25 +0000 (UTC)
Onderwerp: [fedora-arm] Re: Raspberry PI 3 locking up
Cc: arm(a)lists.fedoraproject.org <arm(a)lists.fedoraproject.org>
Aan: Rafael Leiva-Ochoa <spawn(a)rloteck.net>, Peter Robinson <pbrobinson
@gmail.com>, Winfried de Heiden <wdh(a)dds.nl>
Reply-to: Sean Omalley <omalley_s(a)rocketmail.com>
Van: Sean Omalley <omalley_s(a)rocketmail.com>
I have a 2.5amp power supply too. It stopped responding twice since I
have updated (which took around 10 hours.)
I went to dinner and came back, and the monitor (tv in this case) was
off, as it shuts itself off after not getting a signal for x amount of
time. The keyboard didn't respond to any input. The ssh session I had
open locked up, and I couldn't connect to it on the IP address the
router said it was using. (it keeps incrementing, which is annoying and
strange in it's own right.) This is the last part of that log.
It is connected to the network via a wireless dongle. But I didn't have
issues with that adapter on x86 when I had other network issues with
the built-in adapter.
Feb 01 17:43:39 unknownc83a35b012e1.attlocal.net NetworkManager[742]:
<info> [1485989019.9453] manager: NetworkManager state is now
CONNECTED_SITE
Feb 01 17:43:39 unknownc83a35b012e1.attlocal.net dbus-daemon[686]:
[system] Activating via systemd: service
name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-
dispatcher.service' requested by ':1.9' (uid=0 pid=742
comm="/usr/sbin/NetworkManager --no-daemon "
label="system_u:system_r:NetworkManager_t:s0")
Feb 01 17:43:39 unknownc83a35b012e1.attlocal.net systemd[1]: tmp.mount:
Cannot add dependency job, ignoring: Unit tmp.mount is masked.
Feb 01 17:43:39 unknownc83a35b012e1.attlocal.net systemd[1]: Starting
Network Manager Script Dispatcher Service...
Feb 01 17:43:40 unknownc83a35b012e1.attlocal.net kernel:
alloc_contig_range: [21fdc, 21fe0) PFNs busy
Feb 01 17:43:40 unknownc83a35b012e1.attlocal.net kernel:
alloc_contig_range: [220c0, 220c4) PFNs busy
Feb 01 17:43:40 unknownc83a35b012e1.attlocal.net kernel:
alloc_contig_range: [220c4, 220c8) PFNs busy
Feb 01 17:43:40 unknownc83a35b012e1.attlocal.net dbus-daemon[686]:
[system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb 01 17:43:40 unknownc83a35b012e1.attlocal.net audit[1]:
SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295
subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success'
Feb 01 17:43:40 unknownc83a35b012e1.attlocal.net systemd[1]: Started
Network Manager Script Dispatcher Service.
Feb 01 17:43:40 unknownc83a35b012e1.attlocal.net nm-dispatcher[2019]:
req:1 'connectivity-change': new request (5 scripts)
Feb 01 17:43:40 unknownc83a35b012e1.attlocal.net nm-dispatcher[2019]:
req:1 'connectivity-change': start running ordered scripts...
Feb 01 17:43:50 unknownc83a35b012e1.attlocal.net audit[1]: SERVICE_STOP
pid=1 uid=0 auid=4294967295 ses=4294967295
subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success'
Feb 01 17:44:25 unknownc83a35b012e1.attlocal.net NetworkManager[742]:
<info> [1485989065.1881] manager: NetworkManager state is now
CONNECTED_GLOBAL
Feb 01 17:44:25 unknownc83a35b012e1.attlocal.net dbus-daemon[686]:
[system] Activating via systemd: service
name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-
dispatcher.service' requested by ':1.9' (uid=0 pid=742
comm="/usr/sbin/NetworkManager --no-daemon "
label="system_u:system_r:NetworkManager_t:s0")
Feb 01 17:44:25 unknownc83a35b012e1.attlocal.net systemd[1]: tmp.mount:
Cannot add dependency job, ignoring: Unit tmp.mount is masked.
Feb 01 17:44:25 unknownc83a35b012e1.attlocal.net systemd[1]: Starting
Network Manager Script Dispatcher Service...
Feb 01 17:44:25 unknownc83a35b012e1.attlocal.net dbus-daemon[686]:
[system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb 01 17:44:25 unknownc83a35b012e1.attlocal.net audit[1]:
SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295
subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success'
Feb 01 17:44:25 unknownc83a35b012e1.attlocal.net nm-dispatcher[2039]:
req:1 'connectivity-change': new request (5 scripts)
Feb 01 17:44:25 unknownc83a35b012e1.attlocal.net systemd[1]: Started
Network Manager Script Dispatcher Service.
Feb 01 17:44:25 unknownc83a35b012e1.attlocal.net nm-dispatcher[2039]:
req:1 'connectivity-change': start running ordered scripts...
Feb 01 17:44:35 unknownc83a35b012e1.attlocal.net audit[1]: SERVICE_STOP
pid=1 uid=0 auid=4294967295 ses=4294967295
subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success'
Feb 01 18:01:01 unknownc83a35b012e1.attlocal.net CROND[2082]: (root)
CMD (run-parts /etc/cron.hourly)
Feb 01 18:01:02 unknownc83a35b012e1.attlocal.net run-parts[2085]:
(/etc/cron.hourly) starting 0anacron
Feb 01 18:01:02 unknownc83a35b012e1.attlocal.net run-parts[2091]:
(/etc/cron.hourly) finished 0anacron
________________________________
From: Rafael Leiva-Ochoa <spawn(a)rloteck.net>
To: Peter Robinson <pbrobinson(a)gmail.com>; Winfried de Heiden <wdh@dds.
nl>
Cc: arm(a)lists.fedoraproject.org
Sent: Wednesday, February 1, 2017 5:04 PM
Subject: [fedora-arm] Re: Raspberry PI 3 locking up
I will try my 2.5 amp power supply tonight. If I still see the same
problems I will go ahead and respond back to the same email.
On Wed, Feb 1, 2017 at 11:41 AM Winfried de Heiden <wdh(a)dds.nl> wrote:
Hi all,
> Double checked: 2.5A power supply.Winfried
>
>
> Op 01-02-17 om 13:58 schreef Winfried de Heiden:
>
> Hi all,
> >
> > I don't know by head but it should be enough; it worked for weeks
> > and it is sold as "the official PI power supply".
> >
> >
> > I'll check tonight to be shure.
> >
> >
> > Winfried
> >
> >
> > -----Oorspronkelijke bericht-----
> >
> >
> > Datum: Wed, 1 Feb 2017 11:27:45 +0000
> > Onderwerp: [fedora-arm] Re: Raspberry PI 3 locking up
> > Cc: arm(a)lists.fedoraproject.org, Rafael Leiva-Ochoa <spawn@rloteck.
> > net>
> > Aan: Winfried de Heiden <wdh(a)dds.nl>
> > Van: Peter Robinson <pbrobinson(a)gmail.com>
> > On Wed, Feb 1, 2017 at 7:52 AM, Winfried de Heiden <wdh(a)dds.nl>
> > wrote:
> > Hi all, Same for me, since a couple of days the Rapsbery Pi 3
> > suddenly stops. One or
two time I was quick enough to catch a kernel panic on the screen.
Looks like a kernel thing to me. I moved the SD-card to my "
old" Raspberry
Pi 2 (two), the same installation is running fine for a couple of
days.
What is the AMP rating of your power supplies?
> > Screen shot of the kernel panic attached. I think I' ll create a
> > bugzilla on
this. Winfried Op wo, 1 feb 2017 om 1:26 , schreef Rafael Leiva-Ochoa <
spawn(a)rloteck.net>: Hi Everyone, I've been running a raspberry pi 3
with Fedora release 25 (Twenty Five)
using kernal 4.9.6-200.fc25.armv7hl, and I have been noticing for the
last 2
weeks that my Pi locks up. I tried hooking it up to an HDMI monitor,
and USB
keyboard to see if the system generates any message, but I only get a
blank
screen and no reaction from the keyboard. I have looked at the
/var/log/message, and dmesg, and I don't see anything that could be
causing
the problem. I was thinking it could be overheating, but Fedara 25 does
not
support any of the rasbian commands to run heat sensor checks. Any
ideas? Thanks, Rafael _______________________________________________
arm mailing list -- arm(a)lists.fedoraproject.org To unsubscribe send an
email to arm-leave(a)lists.fedoraproject.org
_______________________________________________
arm mailing list -- arm(a)lists.fedoraproject.org To unsubscribe send an
email to arm-leave(a)lists.fedoraproject.org
> >
> > _______________________________________________
arm mailing list -- arm(a)lists.fedoraproject.org To unsubscribe send an
email to arm-leave(a)lists.fedoraproject.org
_______________________________________________
arm mailing list -- arm(a)lists.fedoraproject.org
To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
_______________________________________________
arm mailing list -- arm(a)lists.fedoraproject.org
To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
7 years, 4 months
Re: PCIe slot on Raspberry Pi CM4
by Peter Robinson
On Mon, Sep 4, 2023 at 3:34 AM James Clark <jjc(a)jclark.com> wrote:
>
> I am trying to connect an i210-T1 to the PCIe slot on a Raspberry Pi CM4 with the official IO board. The problem is it won't boot. I tried this in Fedora 38 initially. Now I've installed a recent nightly (Fedora-Server-39-20230828.n.0.aarch64.raw.xz) and I've connected a USB TTL adapter. It appears to be a U-Boot problem. I get the following over and over again
The PCIe does work because the USB-3 is a VIA PCIe attached device on
the RPi4, I wonder what interesting things this card is doing to cause
this error. Do you have more details like make/model of the card, is
it single or multiport etc?
> U-Boot 2023.10-rc3 (Aug 21 2023 - 00:00:00 +0000)
>
> DRAM: 992 MiB (effective 7.9 GiB)
> RPI Compute Module 4 (0xd03141)
> Core: 212 devices, 16 uclasses, devicetree: board
> MMC: mmcnr@7e300000: 1, mmc@7e340000: 0
> Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1...
> In: serial,usbkbd
> Out: serial,vidconsole
> Err: serial,vidconsole
> Net: eth0: ethernet@7d580000
> PCIe BRCM: link up, 2.5 Gbps x1 (SSC)
> "Error" handler, esr 0xbf000002
> elr: 00000000000b52b0 lr : 00000000000b526c (reloc)
> elr: 000000003df812b0 lr : 000000003df8126c
> x0 : 000000000000dead x1 : 0000000000100000
> x2 : 0000000000008000 x3 : 00000000fd508000
> x4 : 000000003db399f0 x5 : 0000000000000001
> x6 : 000000003df82bb8 x7 : 000000003db39fc0
> x8 : 000000003df82c90 x9 : 000000003db3992c
> x10: 0000000000000002 x11: 0000000000000140
> x12: 000000003db39918 x13: 000000003db39fc0
> x14: 00000000ffffffff x15: 000000003db39b78
> x16: 000000003df82c90 x17: 0000000000c0c0c0
> x18: 000000003db47d60 x19: 000000003db399f0
> x20: 0000000000000001 x21: 000000003db53f00
> x22: 0000000000000000 x23: 0000000000010000
> x24: 000000003dfc58fc x25: 000000000001ff00
> x26: 000000000000ffff x27: 0000000000000000
> x28: 000000003db53b10 x29: 000000003db39950
>
> Code: 350001f4 f94017e0 39400000 92401c00 (d5033fbf)
> Resetting CPU ...
>
> resetting ...
>
> James
>
>
> _______________________________________________
> 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://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
9 months
Re: Raspberry Pi 2 reboots
by Juan Orti
El sáb, 12-01-2019 a las 16:04 +0100, Torbjorn Jansson escribió:
> how many amp do your power supply have?
> do you have any usb devices or other things connected to it that
> draws a lot of
> power?
>
> any lines in the system log or dmesg related to power?
> some Pi models can detect a poor power supply and log it and when you
> have a
> gui up you also get a small icon on screen, i think it was a flash
> icon for
> insufficient power.
> there is a forum post related to this with icons and description but
> i don't
> have the link right now.
>
> journalctl -e --system perhaps can give you some clues whats going
> on.
The power supply is fine. I've used one of 2A and other of 3A, and I
don't see the under voltage icon. I've been using this Pi for 3 years
with this same power supply.
It has only connected the ethernet and hdmi cables, no USB.
I've checked the journal, but nothing is written in the moment of the
crash.
Is it possible to use kdump in the Pi? How can I modify the kernel
command line to add the crashkernel parameter?
Thanks.
5 years, 4 months
