On 25/07/2020 00:00, rah+debian...@settrans.net wrote:
> On 24/07/2020 20:50, Vagrant Cascadian wrote:
>> If so, you may have to wipe the environment from the media
> Regardless, where is the environment being read from? How can one wipe it?
I've written all zeroes to /dev/mmcblk1 (eMMC) and al
On 24/07/2020 20:50, Vagrant Cascadian wrote:
> On 2020-07-24, rah wrote:
>> For some reason, the u-boot environment has `board_name=BBG1` so it
>> thinks the board is a BeagelBone Green. If I reset the environment,
>> the board_name variable is set to:
>
> Have you used saveenv in the past on e
Package: u-boot-omap
Version: 2020.07+dfsg-1
Severity: normal
I've successfully installed u-boot to an SD card and set my BeagleBone
Black to not boot from MMC. However, when u-boot runs, it cannot
boot the kernel:
==
U-Boot SPL
reassign 889142 consolekit 0.4.6-6
severity 889142 important
merge 597937 889142
thanks
On 05/02/18 14:00, Christopher Schramm wrote:
> see e.g.
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601003
Aye, that's what I'm looking at, thanks.
Bob
On 03/02/18 00:20, Christopher Schramm wrote:
> sounds like your user is not allowed to use bluetooth. Make sure he's a
> member of the bluetooth group. Relevant rules are in
> /etc/dbus-1/system.d/bluetooth.conf from bluez.
Hi Christopher,
I notice there is
in addition to
I was expect
5 matches
Mail list logo
