Re: PWM and SPI peripherals

On 8/7/24 21:44, isidro wrote: Hello Uwe! On 8/2/24 16:07, Uwe Kleine-König wrote: which pins do you want to control? I need 2 pins (for 2 led strips). I don't care which ones. Looking again, spi is probably the more sensible option compared to PWM. You need to modify the device tr

Re: rpi4: linux-image-6.1.0-18-arm64 kernel does not detect ds1307 rtc

Hello, we met via irc, here comes just the summary to maybe benefit others with similar problems. On 6/27/24 19:27, Uwe Kleine-König wrote: On 6/27/24 10:15, Tuxo wrote: My ds1307 rtc module plugged into my Raspberry Pi 4B (4GB) model is not getting recognized by the the Bookworm arm64

Re: rpi4: linux-image-6.1.0-18-arm64 kernel does not detect ds1307 rtc

Hello Tuxo, On 6/27/24 10:15, Tuxo wrote: My ds1307 rtc module plugged into my Raspberry Pi 4B (4GB) model is not getting recognized by the the Bookworm arm64 kernel. Which pins do you use to connect to the RTC? In Raspian and Ubuntu the driver is built as a module with CONFIG_RTC_DRV_DS1307

Re: Raspberry Pi: gpiomem device support

Hello Thomas, On 03.04.24 21:49, Thomas Lehmann wrote: I forgot to include the references: [1]: https://raspi.debian.net/tested-images/ [2]: https://github.com/raspberrypi/linux/issues/2514 Ah, and I found Kernel code in drivers/char/raspberrypi-gpiomem.c and the accompanying Kconfig defining

Re: AR9271 Raspberry Pi 2B

Hello John, On 07.01.24 09:08, John Wick wrote: An AR9271 Wi-Fi USB dongle doesn't work neither with firmware-ath9k-htc nor firmware-atheros on Raspberry Pi 2B: > [...] > I have tried the both images: https://raspi.debian.net/tested/20230102_raspi_2_bullseye.img.xz https://raspi.debian.net/t

Re: Using Raspberry POE hat with bullseye

Hello Fernando, On 8/20/23 18:00, Fernando Fernández wrote: First of all, sorry for replying to this old e-mail. It's my first time writing in Debian lists and I don't know if this behaviour is unwanted, I apologise in this case. No problem, that's fine (for me at least). I've switched from

Re: Activate a Real Time Clock chip on I2C in Raspberry Pi 4B with Debian (not Raspbian)

On 4/16/23 10:01, Diederik de Haas wrote: On Sunday, 16 April 2023 04:47:37 CEST Rick Thomas wrote: I've got a Raspberry Pi 4B (4GB) with a DS3231 RTC module. I can make the combo work with Ubuntu and RaspberryPI-OS. I'd like to try it with the plain-vanilla Debian from

Re: cubox-i does not boot after upgrade to bullseye

Hi Rainer, On 12/28/21 13:46, Rainer Dorsch wrote: Am Dienstag, 28. Dezember 2021, 11:47:37 CET schrieb Uwe Kleine-König: I can recommend barebox here instead of U-Boot. i.MX is the probably best supported platform for it and I would expect the cubox-i to be directly supported. Barebox can

Re: cubox-i does not boot after upgrade to bullseye

On 12/27/21 18:22, Vagrant Cascadian wrote: On 2021-12-27, Rainer Dorsch wrote: I upgraded a cubox-i from buster to bullseye. The upgrade went through without any issues. But after the upgrade the system does not boot anymore. The output of the serial console is below. The boot process hangs at

Re: Serial Consoles

Hi Rainer, On 12/28/21 01:17, Rainer Dorsch wrote: I am using a serial console to connect to a cubox-i. As terminal program I either use "screen -fn /dev/ttyUSB0 115200" or minicom. If I paste some text in the terminal, after about 30 characters the content gets lost. The problem is likely tha

Re: Using Raspberry POE+ hat with bullseye

Hello, On 11/29/21 00:36, Ryutaroh Matsumoto wrote: I am using Debian Bullseye on a Raspberry PI 4 with a POE+ hat. So far I am unable to get the fan on the POE+ hat working. (deleted) #uname -a Linux host 5.10.0-9-arm64 #1 SMP Debian 5.10.70-1 (2021-09-30) aarch64 GNU/ Linux (deleted) #unam

Re: Raspberry pi 3b+ i2c

Hello, On 10/22/21 7:50 PM, Christian Happ wrote: I have installed debian 11 (Bullseye) 64 on my RPI 3b + and want to use the i2c bus on the GPIO pins. Is there a tutorial that covers installing the necessary files? Which peripheral do you have connected to which i2c bus? Assuming there is

Re: Linux mainline / pure Debian on Acer Chromebook R13 [was: Re: Feedback from the community -> ARM]

On 6/18/21 9:16 PM, Milan P. Stanić wrote: Are those patches published somewhere (and what are they for)? Yes, here: https://git.alpinelinux.org/aports/tree/testing/linux-elm one is to fix mmc devices order to not be random. That should better be done in the machine.dts. See for example htt

Re: Feedback from the community -> ARM

Hello, On 6/11/21 6:07 PM, Diederik de Haas wrote: On vrijdag 11 juni 2021 15:20:34 CEST Uwe Kleine-König wrote: In my bubble most vendor kernel already do this. They align however not to an ELTS kernel, but to the Android universe. That's at least the case for NXP which is quite domina

Re: Feedback from the community -> ARM

Hello Diederik On 6/11/21 2:50 PM, Diederik de Haas wrote: On donderdag 10 juni 2021 16:43:44 CEST Uwe Kleine-König wrote: - Fragmentation - Vendor kernels vs. mainline This got better in the past is my subjective impression, but it still hurts. Device tree made this a

Re: Feedback from the community -> ARM

Hello Peter, On 6/10/21 7:07 PM, Peter Ehlert wrote: On 6/10/21 7:43 AM, Uwe Kleine-König wrote: next week there is a (virtual) meeting at ARM who invited some people involved in Linux on ARM CPUs. One of the topics there is to tell them Debian's needs and pain points. where and ho

Feedback from the community -> ARM

Hello, next week there is a (virtual) meeting at ARM who invited some people involved in Linux on ARM CPUs. One of the topics there is to tell them Debian's needs and pain points. My current list (based on own experience and asking for feedback in #debian-arm) currently has: - Fragmentati

Re: iMX8 support in debian

Hi, On 3/25/21 5:29 PM, Wookey wrote: On 2021-03-25 15:12 +0100, Uwe Kleine-König wrote: Update: Wookey reported a bug and mentioned via irc that imx8 is missing. I enabled a few settings (see https://deb.li/3fUTV) and I'm convinced that only ARCH_MXC is not enough. That does look

Re: iMX8 support in debian

Hello William, On 3/24/21 10:05 PM, Wookey wrote: On 2021-03-24 20:29 +0100, William Bonnet wrote: I own since a couple weeks a nitrogen iMX8 board I am currently using a kernel and image provided by the manufacturer. I would be really happy to help on this task and join the effort. Please ho

Re: CONFIG_VIDEO_CODA is not set

Hallo Rainer, On 12/25/20 10:43 PM, Rainer Dorsch wrote: I just installed bullseye with the daily installer on a cubox-i. I noticed that # CONFIG_VIDEO_CODA is not set which means that the H264 HW decoder at least on imx6 is not enabled. See e.g. https://imxdev.gitlab.io/tutorial/ Decoding_v

Re: Qnap TS-219P+ Kernel 5.9.0-1-marvell

Hello basti, On 11/3/20 1:20 PM, basti wrote: > Not enough space for kernel in MTD 'Kernel' (need 2316696 but is > actually 2097152). > > It seems that Debian ("Bullseye") no longer will run with that. For now it is not even certain that bullseye will include support for armhf at all. See

Re: Armbian

Hello, On 2/3/20 9:46 PM, Andreas Jellinghaus wrote: > The debian installer sounds great in theory, but in practice you install > from one medium to a second medium. But with the device I have there is > just a single medium: the sdcard I enter. I don't know the capabilities of the vendor U-Boot,

Re: SheevaPlug, hctosys: unable to open rtc device, after Buster upgrade

Hello, On 9/30/19 10:37 AM, Rick Thomas wrote: > Another case where this argument falls down is the Cubox-iPro which has two > hardware clocks. The first, labeled /dev/rtc0 by the Debian kernel, is > accurate as long as the power is up, but it has no battery backup, so when > the power fails t

Re: SheevaPlug, hctosys: unable to open rtc device, after Buster upgrade

Hello Rick, On Sun, Sep 29, 2019 at 07:47:40PM -0700, Rick Thomas wrote: > > On Sep 29, 2019, at 1:05 PM, Uwe Kleine-König > > wrote: > > > > The step from 4.19.67-2 to 4.19.67-2+deb10u1 is harmless for this > > problem. The issue that John is describin

Re: SheevaPlug, hctosys: unable to open rtc device, after Buster upgrade

Hello, [I repaired the quoting style and expanded To: a bit] On Sun, Sep 29, 2019 at 07:36:27PM +, John Blake wrote: > On Saturday, September 28, 2019, 3:52:11 PM MDT, Rick Thomas > wrote: > > On Sep 28, 2019, at 1:14 PM, John Blake wrote: > > > > > > After upgrading my Sheevaplug from S

Re: devregs for imx

On 7/28/19 12:15 PM, Rainer Dorsch wrote: > Hi, > > does anybody know if there is something equivalent to devregs in > > https://github.com/boundarydevices/imx-utils > > to probe and manipulate the hardware registers in an imx6 for Debian. There is memtool in Debian that allows to inspect and m

Re: Buster on nap TS-219p II

Hello, On 7/23/19 9:45 PM, basti wrote: > Hello, > today I have try to upgrade my NAS to buster. > I get the following error: > > flash-kernel: installing version 4.19.0-5-marvell > > The initial ramdisk is too large. This is often due to the unnecessary > inclusion > of all kernel modules in th

Re: Bug#920607: Debian Buster installer on qnap ts-21x / Fujitsu Q700 : /dev/mtdblock* missing

Control: tag -1 + pending On Wed, Jan 30, 2019 at 09:42:32PM +0100, Uwe Kleine-König wrote: > Maybe adding spi-orion to > debian/installer/modules/armel-marvell/mtd-modules is the right fix > here, but I don't understand enough about the generation of udebs to > judge if this

Re: Bug#920607: Debian Buster installer on qnap ts-21x / Fujitsu Q700 : /dev/mtdblock* missing

ot included in any udeb. Maybe adding spi-orion to debian/installer/modules/armel-marvell/mtd-modules is the right fix here, but I don't understand enough about the generation of udebs to judge if this is right. Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König| Industrial Linux Solutions | http://www.pengutronix.de/ |

Re: Debian Buster installer on qnap ts-21x / Fujitsu Q700 : /dev/mtdblock* missing

On 1/27/19 12:13 PM, Lukas Straub wrote: > Package: linux > Version: 4.19.12-1 > > Hello Everyone, > I tried the latest Buster Installer on my Fujitsu Q700 (rebranded > qnap ts-21x) and Everything works except that /dev/mtdblock* devices > are missing so flashing the kernel and initrd fails. I se

Re: Unknown QNAP Model

Hello Eric, On 12/9/18 12:31 AM, Eric wrote: > Can Debian be installed on the TS-451+ model? According to https://www.qnap.com/de-de/product/ts-451+/specs/hardware this NAS is powered by an intel CPU. So you're at least on the wrong mailing list. Best regards Uwe signature.asc Description: Op

Re: Problems using stock kernel armmp with Marvell 38x hardware.

Hello, On 10/19/2018 11:25 PM, LinAdmin wrote: > On 19.10.2018 20:12, Uwe Kleine-König wrote: >> Hello, >> >> On 10/19/2018 04:39 PM, LinAdmin wrote: >>> When the system is idle, one CPU is always busy at least 50% >>> with a kworker thread which IMHO doe

Re: Problems using stock kernel armmp with Marvell 38x hardware.

Hello, On 10/19/2018 04:39 PM, LinAdmin wrote: > When the system is idle, one CPU is always busy at least 50% > with a kworker thread which IMHO does not perform any useful > work. When idle, the kernel 4.9.y built exclusively for > Marvell has both CPU’s at below 1% load. How do you diagnose tha

Re: Problems using stock kernel armmp with Marvell 38x hardware.

Hello, [I already replied to this mail in private by accident, so there is some old stuff in it for LinAdmin] On Tue, Sep 25, 2018 at 10:45:06AM +0200, LinAdmin wrote: > a) In the kernel config I used, the buffer management > CONFIG_MVNETA_BM_ENABLE was set, while in > config-4.9.0-8-armmp it is

Re: Enable flexcan kernel module

Hello, On 10/05/2018 11:41 AM, Maciej Pijanowski wrote: > This is my first interaction with the Debian community - I hope > this would be the correct list for such a message. > > I'm working with NXP i.MX6 boards quite a lot and they do already > have good mainline support. I've been using a Debi

Re: QNAP TS-231P

Hello, On 09/04/2018 02:09 PM, Martin Michlmayr wrote: > * basti [2018-09-04 13:10]: >> I have buy an QNAP TS-231P I can use this for testing for ne next 2 or 3 >> weeks. > > This device isn't supported in Debian and there are no plans: > > TS-x31+ series (TS-231+ and TS-431+) and TS-x31P serie

Re: Arch qualification for buster: call for DSA, Security, toolchain concernsj

Hello Julien, On 06/29/2018 11:23 AM, Julien Cristau wrote: >> If the concerns are mostly about the hardware not being rackable, there >> is a rackable NAS by Netgear: >> >> >> https://www.netgear.com/business/products/storage/readynas/RN2120.aspx#tab-techspecs >> >> with an armhf cpu. Not s

Re: Arch qualification for buster: call for DSA, Security, toolchain concernsj

Hello, On Wed, Jun 27, 2018 at 08:03:00PM +, Niels Thykier wrote: > armel/armhf: > > > * Undesirable to keep the hardware running beyond 2020. armhf VM >support uncertain. (DSA) >- Source: [DSA Sprint report] > > [DSA Sprint report]: > https://lists.debian.org/debian-p

Re: Fwd: Looking for a small NAS that runs Debian well

Hello Rogério, On 12/13/2017 02:35 AM, Rogério Brito wrote: > I would like to find a substitute to my KuroBox Pro, which is an armel-based > NAS. Here is its summary: > > * An Orion processor running at 400MHz > * 128MB of RAM > * a slot for one 3.5" SATA HDD > * gigabit ethernet > * 2 USB 2.0 p

Re: Anyone using stretch/buster/sid on ARMv4t ?

On 11/11/2017 09:03 PM, Andreas Henriksson wrote: > Hello, > > On Tue, Nov 07, 2017 at 11:10:27PM +0200, Adrian Bunk wrote: > [...] >> This whole "so many packages are broken on armel" narrative >> is actually mostly FUD, and you are suggesting mitigations >> for a nonexisting problem. >> >> The o

Re: how to distinguish armel and armhf at runtime?

Hello, On 09/24/2017 12:55 AM, peter green wrote: >> No, it's for run time. The target is sparse which can parse C and to be >> able to handle system includes it needs the right cpp variables defined. > Are people expected to have gcc installed when using this tool? if so > gcc -dumpmachine may be

Re: how to distinguish armel and armhf at runtime?

On Sat, Sep 23, 2017 at 02:08:28AM +0100, Steve McIntyre wrote: > On Fri, Sep 22, 2017 at 09:57:02PM +0200, Uwe Kleine-König wrote: > >Hello, > > > >for the package sparse I have to distinguish armel and armhf. The reason > >is that sparse parses system headers a

Re: how to distinguish armel and armhf at runtime?

On 09/22/2017 10:51 PM, John Paul Adrian Glaubitz wrote: > Override the signal for SIGILL, then try to execute an instruction that is > only available on either architecture, maybe? That won't work. On an armv7 which runs armel (but which could run armhf) the instruction will not fault but still

how to distinguish armel and armhf at runtime?

Hello, for the package sparse I have to distinguish armel and armhf. The reason is that sparse parses system headers and so has to know which cpp symbols to define. Usually it uses uname -m to distinguish platforms but that isn't suitable to tell armel and armhf apart. For armhf I need to define

Re: enabling CONFIG_FB_SIMPLE for arm64 kernels for Raspberry Pi3 support

Hello Jonathan, On 06/22/2017 05:02 PM, Jonathan Dowland wrote: > Would it be possible to get CONFIG_FB_SIMPLE enabled for arm64 kernels? Are > there any downsides? I don't see a reason to not enable it. -> http://deb.li/FUoc Best regards Uwe signature.asc Description: OpenPGP digital signat

Re: Bug#856487: libsbc1: compiling with gcc > 4.9 causes stack corruption

Hello, after some discussion in #debian-arm, I have to revise this. On 04/26/2017 10:30 AM, Uwe Kleine-König wrote: > On Mon, Apr 17, 2017 at 05:02:32PM +0100, Paul Brook wrote: >> Package: libsbc1 >> Version: 1.3-1+b2 >> Followup-For: Bug #856487 >> >> Not

Re: libsbc1: compiling with gcc > 4.9 causes stack corruption

Hello, On 04/26/2017 09:34 AM, Niels Thykier wrote: > On Mon, 17 Apr 2017 17:02:32 +0100 Paul Brook wrote: >> Package: libsbc1 >> Version: 1.3-1+b2 >> Followup-For: Bug #856487 >> >> Not a stack corruption. >> >> This is miscompilation of sbc_analyze_4b_8s_armv6. gcc appears to look >> into the

Re: flash-kernel failure during apt-get upgrade. Now what?

On 03/02/2017 05:32 AM, Forest wrote: >> Right, this is still the same data as in your first reply. You can try >> >> flash_unlock -i /dev/mtd1 0 1 >> >> . Looking at the device tree no other reason for the flash being RO >> sticks out. The chip has a write-protect input, maybe its status can be >>

Re: flash-kernel failure during apt-get upgrade. Now what?

Hello, On 03/02/2017 01:08 AM, Forest wrote: > I just noticed something, though: In both tests above, the hex dumps aren't > full of 0x00 or 0xFF, but they aren't full of garbage, either. For example: > > : 56190527 9aac8fc2 4e5a9258 28a41f00 '..VX.ZN...( > 0010: 0080 00800

Re: flash-kernel failure during apt-get upgrade. Now what?

On 02/25/2017 10:36 PM, Forest wrote: > On Sat, 25 Feb 2017 22:21:22 +0100, Uwe Kleine-König wrote: > >> Without having checked every byte, this looks okish. Is this NAND or NOR >> memory? > > Looks to me like it's NOR: > > $ cat /sys/class/mtd/mtd?/type |uni

Re: flash-kernel failure during apt-get upgrade. Now what?

Hello, On Fri, Feb 24, 2017 at 03:12:17PM -0800, Forest wrote: > On Fri, 24 Feb 2017 22:21:58 +0100, Uwe Kleine-König wrote: > > >That message is generated in the verify step. So the data that should be > >written to your device cannot be read back. > > Yes, that'

Re: flash-kernel failure during apt-get upgrade. Now what?

Hello, On 02/23/2017 10:57 PM, Forest wrote: > I just did an apt-get upgrade to apply the DSA-3791-1 security update from > two days ago, and flash-kernel produced this warning for both the kernel and > initramfs: > > File does not seem to match flash data. > > I'm now afraid to reboot this bo

Re: Debian, Qemu, KVM and Raspberry Pi

On 11/08/2016 04:01 PM, Mark Morgan Lloyd wrote: > I prefer to run pukka Debian rather than Raspbian, approximately as > described at http://sjoerd.luon.net/posts/2015/02/debian-jessie-on-rpi2/ > > http://blog.flexvdi.com/2015/03/17/enabling-kvm-virtualization-on-the-raspberry-pi-2/ > and related

Issues when building armhf packages in sid chroot with merged-usr

Hello, I tried to build the experimental linux package on an armhf machine using sbuild. It failed (after 7 hours, sigh) with: dpkg-shlibdeps: error: no dependency information found for /usr/lib/ld-linux-armhf.so.3 (used by debian/linux-kbuild-4.9/usr/lib/linux-kbuild-4.9/scripts/pnmtol

Re: Cubox-i 4x4 RAM [was Re: Performance of armhf boards]

Hello, On 10/05/2016 10:54 PM, Vagrant Cascadian wrote: > I believe it actually requires u-boot to initialize ram timings and > various other parameters. You can trick the kernel into using more Right, the kernel expects the boot loader to initialize RAM. I don't know about u-boot, but barebox ed

Re: Porting Debian arm(hf) to Turris Omnia (open-hardware router)

Hello Axel, On 09/25/2016 12:33 AM, Axel Beckert wrote: > Anyone knows what's the state about Debian on Turris Omnia? > https://wiki.debian.org/InstallingDebianOn/Router is very scarce on > that topic. Compared to an ordinary router the Turris Omnia is not very typical. It has more RAM and flash

Re: Debian on Qnap TS-109

Hello, On 09/13/2016 07:57 PM, [ftp83plus] wrote: > 1. I can't log in through SSH using root user. It denies me access even > when I use the password set during setup. I can log in using the > standard user, and perform "su" to get to root. How come root can't > log in directly? chec

Re: Debian Jessie on QNAP TS-112P - Reboot instead of shutdown

Hello Helge, Cc: += linux-i2c On Sun, Aug 07, 2016 at 08:48:29PM +0200, Helge Wiemann wrote: > I located the battery and removed it for 60 seconds, then booted up my NAS > and performed your commands. My syslog and tracelog are attached. > > I think this made no difference. The date is still inc

Re: Debian Jessie on QNAP TS-112P - Reboot instead of shutdown

Hello Helge, On 08/07/2016 11:37 AM, Helge Wiemann wrote: > apt install i2c-tools > echo 0-0030 > /sys/bus/i2c/devices/0-0030/driver/unbind > i2cget -y 0 0x30 0x80 > > This is what you asked for: > > 1) -bash: echo: write error: No such device > 2) no output > 3) i2cget -y 0 0x30 0x80 > 4) -bash

Re: Debian Jessie on QNAP TS-112P - Reboot instead of shutdown

Hello Helge, On 08/06/2016 08:55 PM, Helge Wiemann wrote: > Ever since I applied your patch the system clock would not sync and > point to January 1st (1970?). Is there any way I can reverse the stuff I > did to my NAS? What is my patch? Can you show your boot log? What is the output on console a

Re: Debian Jessie on QNAP TS-112P - Reboot instead of shutdown

Hello, On Tue, Jul 19, 2016 at 09:47:04PM +0200, Helge Wiemann wrote: > I do have "/sys/bus/i2c/devices/0-0030", but did not specifically follow > your instructions you described in the bug report. If it helps you I will, > please let me know. > > I am running a cron job to switch off my NAS at 1

Re: Debian Jessie on QNAP TS-112P - Reboot instead of shutdown

Hello Helge, On Mon, Jul 18, 2016 at 08:24:38PM +0200, Helge Wiemann wrote: > Issuing... > > echo +150 > /sys/bus/i2c/devices/0-0030/rtc/rtc*/wakealarm > > ...would not work as I don't have the "rtc" directory. But you have /sys/bus/i2c/devices/0-0030? Even if you didn't unbind the driver with

Re: Re: Debian Jessie on QNAP TS-112P - Reboot instead of shutdown

Hello Helge, On Sun, Jul 17, 2016 at 08:25:37AM +0200, Helge Wiemann wrote: > Sorry for my late reply, but I stopped watching this thread and relied on > the mailing system to send me a notification (which never came). I learned > from Martin yesterday there has been a fix and he kindly forwarded

Re: affordable arm boards with plenty of ram.

Hello, On 05/19/2016 01:43 PM, peter green wrote: > I'm looking for an arm board/box to add to my collection of buildboxes. > > Critera (in roughly descending order of importance): > > Reasonablly affordable (upper limit ~£200) > As much ram as possible. > Plenty of CPU power would be nice. > A

Re: linux: [armv7] kernel panic on power down of Cubieboard (A20)

Hello Peter, On 05/02/2016 04:59 AM, Peter Colberg wrote: > Are any of you running an armv7 board similar to the Cubieboard or > Cubietruck by chance, who happen to see a kernel panic on poweroff > using Debian testing/unstable with Linux kernel 4.2 up to 4.5? > > https://bugs.debian.org/818951

Re: Debian Jessie on QNAP TS-112P - Reboot instead of shutdown

Hello Helge, On 04/17/2016 04:18 PM, Helge Wiemann wrote: > However, all is good now. can you try if doing: echo +2 > /sys/class/rtc/rtc0/wakealarm triggers the problem again? If so, echo 0 > /sys/class/rtc/rtc0/wakealarm might fix it again. Do you have something about rtc i

Re: Cubox-i 4x4 RAM [was Re: Performance of armhf boards]

Hello, On 04/22/2016 08:54 AM, Rick Thomas wrote: > > On Apr 21, 2016, at 9:04 AM, Vagrant Cascadian wrote: > >> On 2016-04-21, Rick Thomas wrote: >>> Are you saying that the amount of RAM seen by Debian Linux is >>> determined by something in u-boot? >> >> Yes. > > How is this information com

Re: choosing low-power/low-noise/free NAS servers to run Debian

Hello, On 04/12/2016 10:20 AM, Daniel Pocock wrote: > How many can be upgraded to Debian and operated with 100% free software, > no binary firmware blobs at all? Is there any comparison table that is > useful for people buying these things with the intention of running free > software? I have a

Re: modprobe fuse fails after upgrade to Jessie 8.3 on Dreamplug (Kirkwood)

Hello Martin, On 02/16/2016 12:28 AM, Martin Granehäll wrote: > Thanks a lot for helping me out here. > I have managed to solve it, or at least found a workaround. > > The system uses u-boot, and picks uImage and uInitrd from an external sd > card at boot time. So either change U-Boot to boot fr

Re: modprobe fuse fails after upgrade to Jessie 8.3 on Dreamplug (Kirkwood)

Hallo, On 02/15/2016 01:29 PM, Martin Granehäll wrote: > _sources.list:_ > # deb http://ftp.se.debian.org/debian/ jessie main > deb http://ftp.se.debian.org/debian/ jessie main non-free contrib > deb-src http://ftp.se.debian.org/debian/ jessie main non-free contrib > deb http://security.debian.org

Re: modprobe fuse fails after upgrade to Jessie 8.3 on Dreamplug (Kirkwood)

Hello Martin, On 02/15/2016 10:33 AM, Martin Granehäll wrote: > Thanks. Yes, I rebooted. that means that you rebooted and are still unable to load the fuse module? > But this indicates I somehow didn't get the latest kernel update after all? What is in your apt sources.list? What is the output

Re: modprobe fuse fails after upgrade to Jessie 8.3 on Dreamplug (Kirkwood)

Hello Martin, On 02/15/2016 12:53 AM, Martin Granehäll wrote: > I have used fuse successfully on the Dreamplug with Jessie 8.2 but after > last update to 8.3, the kernel module doesn't load. > Does latest version of fuse depend on later kernel, or could something > be wrong with my installed kerne

Bug#813995: flash-kernel: writes to nand without being aware of bad blocks

Package: flash-kernel Version: 3.35+deb8u2 Severity: critical Justification: causes serious data loss Control: block 806926 with -1 Hello, when flash-kernel writes a kernel/initrd to NAND flash it uses plain write(2) to /dev/mtdX (flash-kernel < 3.52) or flashcp (flash-kernel >= 3.52). If the dev

Re: Odd messages booting Cubox-i4 Pro "imx-gpc 20dc000.gpc: failed to get pu regulator: -517" and "ERROR: could not get clock /usdhc1_pwrseq:ext_clock(0)"

Hello, On 02/04/2016 02:44 PM, John Holland wrote: > > On 04.02.2016, at 14:04, Nigel Sollars > wrote: > >> There seems to be a good explanation here, >> >> https://lists.debian.org/debian-arm/2013/12/msg00038.html >> >> On Wed, Feb 3, 2016 at 12:56 PM, Rick Thomas >

Re: Porting Debian arm(hf) to Turris Omnia (open-hardware router)

Hello Martin, On 11/20/2015 07:56 PM, Uwe Kleine-König wrote: > On 11/20/2015 03:49 PM, Martin Strbačka wrote: >> Hello, the switch-chip is Marvell 88E6176. Unfortunately you are right >> we are not allowed to share the documentation. > > Is this device similar to a pre

Re: Porting Debian arm(hf) to Turris Omnia (open-hardware router)

Hello Martin, On 11/20/2015 03:49 PM, Martin Strbačka wrote: > On 15.11.2015 10:05, Ondřej Surý wrote: >> On Sat, Nov 14, 2015, at 22:07, Uwe Kleine-König wrote: >>> On 11/13/2015 02:55 PM, Ondřej Surý wrote: >>>> we (@CZ.NIC) built open-hardware[1] and open-sourc

Re: Porting Debian arm(hf) to Turris Omnia (open-hardware router)

Hello Ondřej, On 11/13/2015 02:55 PM, Ondřej Surý wrote: > we (@CZ.NIC) built open-hardware[1] and open-source[2] router called > Turris Omnia (https://omnia.turris.cz/en/); I spoke about it shortly > @DebConf15 lightning talks, and now we have IGG campaign > (http://igg.me/at/turris-omnia) - and

Re: rawtherapee FTBFS on arm (C++11 issue)

Hello, On 11/04/2015 10:46 AM, Philip Rinn wrote: > Hi, > > I need some help understanding what happens. > I uploaded a new version of rawtherapee to cope with new sigc++ and glibmm2.4 > versions. This involved bulding rawtherapee with -std=c++11. Now rawtherapee > FTBFS on arm64, armel, armhf,

Re: Debian ARM architectures and subarchitectures

Uwe -- Pengutronix e.K. | Uwe Kleine-König| Industrial Linux Solutions | http://www.pengutronix.de/ | -- To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.or

Re: Debian ARM architectures and subarchitectures

d the three i.MX53 platforms by Freescale. I think it's OK to skip these for now. Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König| Industrial Linux Solutions | http://www.pengutronix.de/ | -- To UNSUBSCRIBE, email to d

Re: kexec on kirkwood kernels?

I'm hoping someone can help me avoid having to use gdb over JTAG to > resolve this. Thanks. Try enabling DEBUG_LL and EARLY_PRINTK in the kernel to boot and pass earlyprintk as kernel parameter. Best regards Uwe -- Pengutronix e.K. | Uwe Klein