Re: Debian Bullseye on Raspberry Pi 4 4GB?

On Fri, 2021-02-19 at 18:42 -0800, Rick Thomas wrote: > If I can get the Pi4 working with either of the Debian alternatives, > I will probably buy a Pi zero W as the actual replacement for the > Sheeva, and keep the Pi4 for experimentation. I'm sure someone who follows rpi closer than I will

Re: Bug#933294: Kernel quirks on QNAP TS-109 (Marvell orion)

On Sun, 2019-08-04 at 15:51 +0200, Martin Michlmayr wrote: > Copying the relevant Debian bug (#933294). > > * Matthieu CERDA [2019-08-04 15:42]: > > In dmesg during boot, which I suspect means that something is wrong in > > GPIO / PIC communication. > > > > I tried to replicate the way Linux

Re: need recommendation for a realtime kernel to build for an armhf

On Sun, 2019-06-16 at 12:11 +0800, Paul Wise wrote: > On Sun, Jun 16, 2019 at 10:52 AM Gene Heskett wrote: > > > Get familiar with it Alan, despite our objections, both ifconfig and > > route have been expunged from the stretch and newer repo's. I haven't > > figured it out either. And the man

Re: (Marvell) migrating RAID1 from MBR (1TB) to GPT (6TB): U-Boot and GPT?

On Tue, 2019-04-16 at 19:04 +0200, Emanuele Olivetti wrote: > ...in my /etc/fstab I have: > > # /etc/fstab: static file system information. > # > # Use 'vol_id --uuid' to print the universally unique identifier for > a > # device; this may be used with UUID= as a more robust way to name >

Re: guruplug doesn't boot after upgrade kernel

On Thu, 2019-04-11 at 17:06 +0200, Lieven Baes wrote: > [0.00] Kernel command line: $(bootargs_console) > earlyprintk=serial,ttyS0,115200 Looks like `$(bootargs_console)` isn't actually being substituted. Are you sure the `$(...)` syntax is correct? Vendor u-boots sometime deviate a bit

Re: Does ARMEL toolchain include NEON support?

On Wed, 2019-02-27 at 23:45 +, Steve McIntyre wrote: > On Wed, Feb 27, 2019 at 06:30:36PM -0500, Jeffrey Walton wrote: > > On Wed, Feb 27, 2019 at 5:46 PM Steve McIntyre wrote: > > > So, I've got to ask - what hardware are you likely targeting here > > > where it matters to build stuff for

Re: Multiple console support in d-i

On Wed, 2019-01-23 at 03:41 +, Wookey wrote: > You are right. I wasn't taking note of those: > > E=enabled > C=preferred console > p=used for printk buffer > a=safe to use when CPU is offline > > console=tty0 > tty0 -WU (EC p )4:7 > ttyAMA0 -W- (E p a)

Re: Multiple console support in d-i

On Tue, 2019-01-22 at 04:31 +, Wookey wrote: > On 2019-01-20 03:02 +, Ben Hutchings wrote: > > Reading /proc/consoles is exactly what you should do. > > Checking this on a booted thunderx machine (with no explicit kernel cmdline > options) it lists > ttyAMA0 > > If I boot with explicit

Re: Multiple console support in d-i

On Sat, 2019-01-19 at 11:08 +, Steve McIntyre wrote: > >So far I have done a proof-of-concept hack and demonstrated that > >running two instances does in fact work nicely without anything > >obvious breaking. The console selection still needs some work/checking > >(I've run out of time for

Re: Upcoming Qt switch to OpenGL ES on arm64

On Mon, 2018-11-26 at 12:07 +0100, bret curtis wrote: > The hardware that supports GLES also supports OpenGL because GLES is > a subset of OpenGL. I'm confused by this inference. If GLES is a subset of OpenGL then surely hardware which claims to implement GLES is at liberty to only implement that

Re: Is there a way to make the pi use swap?

On Mon, 2018-09-17 at 09:18 +0200, Philip Hands wrote: > Gene Heskett writes: > > And pray tell, where does one set that swappiness? > > Sounds like something that could be handy. > > When wondering that sort of thing, I generally try this sort of command > to find out: Or one could try, for

Re: "external abort on linefetch (0x814)" on Kirkwood 6282 SoC

On Sat, 2018-06-09 at 16:23 +0200, Andrew Lunn wrote: > > Debian uses a Marvell specific kernel, so we don't need to worry > about > > the impact on other platforms. > > That i was not sure about. Are there any plans to merge all ARM v5 > kernels together? Not AFAIK, marvell is the only armv5

Re: "external abort on linefetch (0x814)" on Kirkwood 6282 SoC

(adding debian-kernel, context: external aborts on qnap/marvell systems with 1G of RAM, avoided with VMSPLIT_3G_OPT=y). On Sat, 2018-06-02 at 21:31 +0200, Andrew Lunn wrote: > On Sat, Jun 02, 2018 at 09:48:47PM +0300, Timo Jyrinki wrote: > > 2018-06-02 18:55 GMT+03:00 Ian Campbell :

Re: "external abort on linefetch (0x814)" on Kirkwood 6282 SoC

On Sat, 2018-06-02 at 16:55 +0100, Ian Campbell wrote: > On Sat, 2018-06-02 at 15:36 +0300, Timo Jyrinki wrote: > > 2018-05-28 19:00 GMT+03:00 Andrew Lunn : > > > Could you try changing "Memory split" to "3G/1G user/kernel split > > (for > >

Re: "external abort on linefetch (0x814)" on Kirkwood 6282 SoC

On Sat, 2018-06-02 at 15:36 +0300, Timo Jyrinki wrote: > 2018-05-28 19:00 GMT+03:00 Andrew Lunn : > > Could you try changing "Memory split" to "3G/1G user/kernel split > (for > > full 1G low memory)". You should then see that the lowmem in the > > Virtual kernel memory layout table goes from

Re: D-Link DNS-323 support

On Mon, 2018-04-09 at 08:06 +0200, basti wrote: > I have try to restore a Kernel /Ramdisk backuped via > > cat /dev/mtdblock2 > uKernel > cat /dev/mtdblock3 > uRamdisk > > The System wont start with error "Bad CRC checksum". Did you try to restore with cat ... > /dev/mtdblock? Some devices

Re: D-Link DNS-323 support dropped in Debian stretch

On Tue, 2018-03-27 at 21:25 +0300, Aaro Koskinen wrote: > Hi, > > On Mon, Mar 26, 2018 at 07:36:26PM +0900, Roger Shimizu wrote: > > There's one possibility that can bring back qnap, or even D-Link > > DNS device: > > - create a new flavour for armel, such as armel-none-mini > > - the new flavour

Re: Help needed for small assembler script for the iraf package

On Mon, 2018-01-01 at 15:20 +0100, Ole Streicher wrote: > However, I have no idea how to write the same for the 64-bit platform > arm64 (the code in the repo does not work). Maybe someone could help > me here? Preferably under the IRAF license [3], so that it can be > included upstream later. My

Re: found net prob, temp fixed. installed xfce4, how to autostart it?

On Thu, 2017-09-28 at 16:48 +0200, Stefan Peter wrote: > Hi Gene > > On 28.09.2017 16:31, Gene Heskett wrote: > > Is there a one stop locale configurator for an X-less machine? I > > did a > > dpkg-reconfigure locale once before, but I'll try again. > > Try dpkg-reconfigure locales > (with an s

Re: Summary of the Arm ports BoF at DC17

On Mon, 2017-09-18 at 10:15 +0100, Edmund Grimley Evans wrote: > > But it did remind me that on some platforms writing "2" to > > /proc/sys/abi/cp15_barrier will enable hw support for these > > instructions, since some platforms do support them even thought > > they > > are deprecated. It's

Re: Summary of the Arm ports BoF at DC17

On Sun, 2017-09-17 at 12:59 -0700, Vagrant Cascadian wrote: > On 2017-09-15, Ben Hutchings wrote: > > On Thu, 2017-09-14 at 03:40 +0100, Steve McIntyre wrote: > > [...] > >> There is optional kernel support to trap the exceptions here > >> and emulate the instructions, but it's really not

Re: ARM Ports BoF: armel in buster

On Fri, 2017-09-01 at 19:27 +0300, Adrian Bunk wrote: > [...] > > What matters for buster is gcc 8, and there is no current deprecation > in gcc that would affect the armel port. Thanks for all the info! > armel is a port on borrowed time since it supports old hardware > no longer supported

Re: ARM Ports BoF: armel in buster

On Mon, 2017-08-28 at 06:53 +0800, Paul Wise wrote: > On Sun, Aug 27, 2017 at 9:49 PM, Roger Shimizu wrote: > > > However, I think armel is time to transit to v5. > > As someone who can no longer run Debian stable on his MIPS device due > to the CPU requirements bump in stretch, I'm not sure

Re: Qnap TS-109 II Status light flashing, no LAN LED

On Sun, 2017-07-30 at 19:46 +0100, Martin Michlmayr wrote: > * ges...@ftp83plus.net [2017-07-29 12:29]: > > I just installed Debian on a Qnap Ts-109 II. I followed these > > isntructions , but now the Status LED is flashing red and green, > > and > > the LAN LED is off. The

Re: "external abort on linefetch (0x814)" on Kirkwood 6282 SoC

On Wed, 2017-07-26 at 19:55 +0200, Andrew Lunn wrote: > On Wed, Jul 26, 2017 at 05:18:05PM +0100, Ian Campbell wrote: > > On Wed, 2017-07-26 at 17:22 +0200, Andrew Lunn wrote: > > > I have a 6282 system i can try to reproduce this on. It will > probably > > > be

Re: "external abort on linefetch (0x814)" on Kirkwood 6282 SoC

On Wed, 2017-07-26 at 17:22 +0200, Andrew Lunn wrote: > I have a 6282 system i can try to reproduce this on. It will probably > be a few days before i get around to it. Thanks! For some reason my original mail never made it to debian-arm or linux- arm-kernel, suspiciously the mail which I

Re: CP15 Barrier emulation performance?

On Tue, 2017-07-11 at 08:56 +0100, Edmund Grimley Evans wrote: > > Does this emulation take a considerable performance hit, as opposed > > to > > running on armhf hardware/kernel, where the instruction doesn't > > appear > > to be listed as deprecated? > > I'd expect the kernel-emulated

Re: Errors and crash while (re-)installing Debian on TS-421

On Sat, 2017-07-08 at 14:49 +0100, Ian Campbell wrote: > I'll recover that and have a play, see if I can figure this bit out > at least. earlyprintk + debug gives the full log below which includes: [0.321125] Unpacking initramfs... [0.324623] Initramfs unpacking failed

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

On Wed, 2017-03-01 at 20:32 -0800, Forest wrote: Can't really answer the rest of your questions, but: > Thanks so much for your help, Uwe.  Looks like I don't have to resort to > emergency hardware replacement after all. You should arrange for the contents of the mtd devices to be included in

Re: debian-installer failure with arm64 (was RE: laxton (softiron) boot failure with Debian linux-image-4.7.0-0.bpo.1-arm64)

On Thu, 2017-01-05 at 13:46 +, Ian Jackson wrote: > Ian Campbell writes ("Re: debian-installer failure with arm64... > > > In that scenario the "Continue the install without loading kernel > > modules?" message is expected and (working from memory

Re: debian-installer failure with arm64 (was RE: laxton (softiron) boot failure with Debian linux-image-4.7.0-0.bpo.1-arm64)

On Tue, 2017-01-03 at 18:48 +, Ian Jackson wrote: > (CCing debian-arm, because I think this is now something related to > d-i > on ARML.) > > Hi.  I'm writing with my Xen Project hat on.  We have two Softiron > ARM64 servers which I am trying to get up and running in our CI > system. > [...]

Re: how to build a kernel package of flavor 'armmp'

On Mon, 2016-12-19 at 16:52 +, Simon H wrote: > Although it did not do a total rebuild, I think it rebuilt every > loadable module (kind of expected if they will check kernel > version). Ah, yes, it was probably relinking the .ko out of the .o rather than fully compiling, but still quite

Re: how to build a kernel package of flavor 'armmp'

On Mon, 2016-12-19 at 09:09 +, Simon H wrote: > However, when using > 'dpkg -i linux-image-4.8.7_4.8.7-1_armhf.deb' > to install the kernel, the device complains: > > "Kernel /boot/vmlinuz-4.8.7 does not match any of the expected > flavors > (armmp), therefore not writing it to flash"

Re: Debian and QEMU virtio-net-device

On Mon, 2016-11-14 at 23:13 -0500, Jerry Stuckle wrote: > > Everything I've found on the internet indicates the -sd parameter should > be all I need, but it doesn't work.  Any ideas here? The armmp kernel flavour works on many different platforms and is therefore more modular than the old

Re: Debian and QEMU virtio-net-device

On Mon, 2016-11-14 at 12:46 -0500, Jerry Stuckle wrote: > Hi, Ian, > > I tried several variations with different DTBs, and nothing worked.  I > also tried your example, with no difference.  All I get is an empty console. Please tell us the actual commands which you have tried to run. Ian.

Re: Debian and QEMU virtio-net-device

On Sun, 2016-11-13 at 21:39 -0500, Jerry Stuckle wrote: > Boot only gave me an empty window.  No messages, nothing.  I had to > force close the machine. You need the DTB too. /usr/lib/linux-image-3.16.0-4-armmp should contain vexpress-v2p-ca9.dtb which seems like the one you want (but there are

Re: Debian and QEMU virtio-net-device

On Sat, 2016-11-12 at 16:16 -0500, Jerry Stuckle wrote: > Ian, > > That's interesting, because when I do lsb_release-a returns > > No LSB modules are available. > Distribution ID: Debian > Description: Debian GNU/Linux 8.6 (jessie) > Release: 8.6 > Codename:Jessie > >

Re: Debian and QEMU virtio-net-device

On Sat, 2016-11-12 at 10:22 -0500, Jerry Stuckle wrote: > Ian, > > Thanks for clarifying this - I misunderstood your previous statement > and > thought it was the Wheezy kernel which supported virtio and not > Jessie. > > However, I am already running Jessie. The logs you posted earlier

Re: Debian and QEMU virtio-net-device

On Fri, 2016-11-11 at 20:05 -0500, Jerry Stuckle wrote: > Ian, > > Thanks much for the info. > > I find it interesting that the virtio options for vexpress would require > PCI, since the vexpress architecture doesn't support PCI. IIRC there was _no_ option to support virtio on any platform

Re: Debian and QEMU virtio-net-device

On Fri, 2016-11-11 at 11:55 -0500, Jerry Stuckle wrote: > Hi, Ian, and thanks again for your time. > > No, this is an armhf kernel, installed from > debian-7.1.0-armhf-netinst.iso (and updated).  It does not include PCI > support (neither does hardware) and trying to use virtio-net-pci returns >

Re: Debian and QEMU virtio-net-device

On Fri, 2016-11-11 at 14:38 +, Mark Morgan Lloyd wrote: > On 11/11/16 08:00, Ian Campbell wrote: > > > > On Wed, 2016-11-09 at 08:18 -0500, Jerry Stuckle wrote: > > > > > > Again, I appreciate any insight you can provide. > > > > Looks like y

Re: Debian and QEMU virtio-net-device

On Wed, 2016-11-09 at 08:18 -0500, Jerry Stuckle wrote: > Again, I appreciate any insight you can provide. Looks like you are using the armel vexpress kernel, which AFAICT includes PCI based virtio support, unlike most other ARM configurations which include the MMIO (discovered via DTB or ACPI)

Re: Debian and QEMU virtio-net-device

On Tue, 2016-11-08 at 08:51 -0500, Jerry Stuckle wrote: > Any other ideas? I'm at a bit of a loss, maybe someone else has some bright ideas. A few bits of info whic might jolt someones memory: What is your full qemu command line for the working case (with the default nic) and non-working cases?

Re: Debian and QEMU virtio-net-device

On Tue, 2016-11-08 at 08:42 +, Mark Morgan Lloyd wrote: > > Does "ifconfig -a" (as root) show the virtio device with some name > > other than eth0? If so then you might need to edit > > /etc/udev/rules.d/70-persistent-net.rules to cause it to forget the > > old > > device. > > Is that file

Re: Debian and QEMU virtio-net-device

On Mon, 2016-11-07 at 22:57 -0500, Jerry Stuckle wrote: > The only odd thing I see in the syslog at startup are lines indicating > eth0 is not found. Wild stab in the dark: Perhaps things have remembered the mac address of the original (automatically added) device as eth0 and so the virtio device

Re: Gigabyte MP30-AR1

On Mon, 2016-09-12 at 14:45 +0100, Wookey wrote: > Centos may be choosing to explicitly prefer the ACPI in their kernel? Given the downstream relationship with RHEL (who certainly do so in the preview releases) I'd offer good odds that this was the case. Ian.

Re: Native kernel build produces armhf on armel system

On Mon, 2016-03-21 at 11:52 +, Ben Hutchings wrote: > On Mon, 2016-03-21 at 11:06 +0000, Ian Campbell wrote: > > > > On Mon, 2016-03-21 at 11:31 +0100, JM wrote: > > > > > > > > > Hi, > > > > > > The system is a qnap, kirkwood fl

Re: Native kernel build produces armhf on armel system

On Mon, 2016-03-21 at 11:31 +0100, JM wrote: > Hi, > > The system is a qnap, kirkwood flavour. > > I would previously build vanilla kernels with Debian's .config as > described in the Kernel Handbook (copy old config, make oldconfig, > make deb-pkg) and that worked well as of 4.4.1-1-exp1. > >

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

On Tue, 2016-02-16 at 08:11 +, Tixy wrote: > On Tue, 2016-02-16 at 00:28 +0100, Martin Granehäll wrote: > [...] > > When I ran flash-kernel tool manually I saw that new uImage and > > uInitrd files were generated, but not in /boot. It says > > "using /dev/sda1 as boot device", but that is and

Re: Qnap / mv643xx_eth link dropping

On Sun, 2016-01-24 at 10:09 +, Ian Campbell wrote: > On Thu, 2016-01-21 at 15:01 +0100, JM wrote: > > On Thu, Jan 21, 2016 at 2:36 PM, Thomas Pircher < > > tehpeh-deb...@tty1.net> wrote: > > > On 2016-01-21 13:18, JM wrote: > > [...] > > >

Re: Qnap / mv643xx_eth link dropping

On Thu, 2016-01-21 at 15:01 +0100, JM wrote: > On Thu, Jan 21, 2016 at 2:36 PM, Thomas Pircher < > tehpeh-deb...@tty1.net> wrote: > > On 2016-01-21 13:18, JM wrote: > [...] > > Still it might be worth to try disabling TCP offloading in > > /etc/network/interfaces: > >[...] > This seems to have

Re: orion5x housekeeping

On Wed, 2015-12-30 at 18:51 -0800, Martin Michlmayr wrote: > I was looking at debian-installer and thought it would be good to see > if there are maintainers (and if not, at least users) for the orion5x > devices we supposedly support. I wonder if, for armel generally (or even arm* generally), we

Re: XZ compression for the initramfs

On Thu, 2015-12-31 at 10:50 -0800, Martin Michlmayr wrote: > > [...] > CONFIG_RD_XZ is enabled at least in jessie and stretch. > > Any objections/feedback? Given the above I wonder if we should consider making XZ the default in initramfs-tools, if CONFIG_RD_XZ was enabled in Wheezy I'd say this

Re: orion5x housekeeping

On Thu, 2015-12-31 at 08:43 -0800, Martin Michlmayr wrote: >  > > * Buffalo LinkStation Pro Duo (LS-WTGL) > > Mine still has the stock firmware. > > I didn't even know that it was supported by the mainline kernel. > > But I just checked and support was added recently in 4.3 :) > > Roger Shimizu

Re: XZ compression for the initramfs

On Fri, 2016-01-01 at 13:03 +, Ben Hutchings wrote: > On Fri, 2016-01-01 at 12:22 +0000, Ian Campbell wrote: > > On Thu, 2015-12-31 at 10:50 -0800, Martin Michlmayr wrote: > > > > > > [...] > > > CONFIG_RD_XZ is enabled at least in jessie and stretch.

Re: Cubieboard4, u-boot, flash-kernel

On Tue, 2015-12-29 at 12:15 +0100, Karsten Merker wrote: > On Mon, Dec 28, 2015 at 02:45:33PM -0800, Vagrant Cascadian wrote: > > I'm trying to get a Cubieboard4 board booting. > > > > It looks like the Cubieboard4 has support in mainline linux since > at > > least 4.2 (so should work with

Re: Banana Pi M1 netinstall does not find wired ethernet

On Mon, 2015-12-07 at 20:14 +0800, Adam Ward wrote: > The installer hangs when detecting hardware and therefore cannot > continue to get network connectivity. IIRC this is/was a bug in the installer. The daily builds[0] have it fixed. These will become the Stretch installer with the next alpha or

Re: Mainstream Debian on Raspberry Pi 2

On Tue, 2015-12-01 at 09:20 +, Mark Morgan Lloyd wrote: > Ian Campbell wrote: > > On Mon, 2015-11-30 at 14:03 +0100, Marcin Juszkiewicz wrote: > >> W dniu 30.11.2015 o 13:52, Mark Morgan Lloyd pisze: > >>> I've been playing with Debian for the RPi2 (not the o

Re: Mainstream Debian on Raspberry Pi 2

On Tue, 2015-12-01 at 16:10 +, Mark Morgan Lloyd wrote: > > With respect to mainline kernel support, this page shows a pretty good > > picture: > > http://elinux.org/RPi_Upstreaming > > > > Many of the drivers are already upstreamed or queued for 4.4. > > So is there a chance it will be

Re: Mainstream Debian on Raspberry Pi 2

On Mon, 2015-11-30 at 14:03 +0100, Marcin Juszkiewicz wrote: > W dniu 30.11.2015 o 13:52, Mark Morgan Lloyd pisze: > > I've been playing with Debian for the RPi2 (not the original RPi) from > > http://sjoerd.luon.net/posts/2015/02/debian-jessie-on-rpi2/ and find > > that it fairly readily accepts

Re: Running Debian from a USB-drive on a Cubox-i 4

On Sat, 2015-11-28 at 21:37 -0500, Pierre wrote: > Before updating the initramfs, one must define the type of platform as > flash-kernel can't access /proc/cpuinfo from the chroot: > > echo "SolidRun Cubox-i Dual/Quad" > /etc/flash-kernel/machine FWIW you can also set FK_MACHINE="SolidRun

Re: Bug#804351: installation-reports: Stretch installer-armel (2015-10-23) does not see storage devices on Dreamplug

On Thu, 2015-11-12 at 06:50 -0500, James Valleroy wrote: Hi James, I think this should be fixed in the latest dailies from http://d-i.debian.org/daily-images/armel/daily/kirkwood/netboot/marvell/ or at least my dreamplug is OK in recovery mode with the one from 2 days ago. This will then

Re: Bug#804351: installation-reports: Stretch installer-armel (2015-10-23) does not see storage devices on Dreamplug

On Sat, 2015-11-28 at 14:40 -0500, James Valleroy wrote: > On 11/28/2015 07:04 AM, Ian Campbell wrote: > > On Thu, 2015-11-12 at 06:50 -0500, James Valleroy wrote: > > > > Hi James, > > > > I think this should be fixed in the latest dailies from > > http://

Re: Stretch installer fails to detect network device for Sheevaplug

On Fri, 2015-11-27 at 13:57 +, Steve Ginter wrote: > Hi all, > The newest stretch installer does not detect the network card, and > manually selecting the driver for "mv643xx_eth: Ethernet driver for > Marvell MV643XX" does not work. I keep getting kicked back to the > "Detect Network

Re: Bug#762634: initramfs-tools: [armhf] mounting rootfs on USB disk fails / some USB host controller drivers missing in initramfs

On Wed, 2015-11-11 at 18:46 -0600, Vagrant Cascadian wrote: > On 2014-09-30, Ben Hutchings wrote: > > On Tue, 2014-09-30 at 08:19 +0100, Ian Campbell wrote: > > > On Fri, 2014-09-26 at 00:08 +0100, Ben Hutchings wrote: > > > > However, at the moment initramfs-t

Re: Bug#804351: installation-reports: Stretch installer-armel (2015-10-23) does not see storage devices on Dreamplug

On Wed, 2015-11-11 at 19:13 -0500, James Valleroy wrote: > On 11/11/2015 03:43 PM, Ian Campbell wrote: > > Perhaps you could drop to a shell and try manually loading those > > modules and see what, if anything, it says? > > Modules seem to load ok: Did lsusb (or mayb

Re: Bug#804351: Kirkwood / Qnap HS-210, kernel 3.16->4.2/ udev 215->227 upgrade issue

On Wed, 2015-11-11 at 09:22 +1300, m...@wiimail.com wrote: > Thanks to all those that replied. > Due to lack of time to debug this properly I just reverted to a jessie > image via recovery mode: > http://www.cyrius.com/debian/kirkwood/qnap/ts-219/recovery/ > All is fine again... > Cheers

Re: Bug#804351: installation-reports: Stretch installer-armel (2015-10-23) does not see storage devices on Dreamplug

On Sat, 2015-11-07 at 12:12 -0500, James Valleroy wrote: > Package: installation-reports > Severity: important > > When I run Jessie installer, I can see the USB stick (which the > installer was loaded from), and the internal microSD. > > With current Stretch installer, neither storage device is

Re: Bug#804351: Kirkwood / Qnap HS-210, kernel 3.16->4.2/ udev 215->227 upgrade issue

On Tue, 2015-11-10 at 01:08 +, Ben Hutchings wrote: > On Mon, 2015-11-09 at 14:18 -0800, Martin Michlmayr wrote: > > * Ian Campbell <i...@debian.org> [2015-11-09 08:37]: > > > It might be the same issue as this recent installation report: > > > https://bugs.deb

Re: Kirkwood / Qnap HS-210, kernel 3.16->4.2/ udev 215->227 upgrade issue

On Mon, 2015-11-09 at 15:38 +1300, m...@wiimail.com wrote: > Hi all. > > I have been happily running debian on a Qnap HS-210 for about a year > now. > > It was a sid install onto a USB drive, last updated just before the > jessie release. > So it was running on kernel 3.16+63 and udev 215-9

Re: I/O issues with writing to mtdblock devices on kirkwood

On Wed, 2015-10-21 at 22:22 +0100, Iain McFarlane wrote: > >> 3.16 - No SATA errors when updating initrd - the kernel is flashed using > >> dtb but how do I tell if it is used? > [...] > In which case it is using the board file > > How do I force it to use the dtb? If the DTB has been appended

Re: I/O issues with writing to mtdblock devices on kirkwood

On Wed, 2015-10-21 at 22:22 +0100, Iain McFarlane wrote: > >> 3.16 - No SATA errors when updating initrd - the kernel is flashed using > >> dtb but how do I tell if it is used? > [...] > In which case it is using the board file > > How do I force it to use the dtb? If the DTB has been appended

Re: I/O issues with writing to mtdblock devices on kirkwood

On Mon, 2015-10-12 at 18:21 +0200, Andrew Lunn wrote: > > I've been on backports for some time. AFAIR the problems started > > with the change to dtb/dts. > > Which kernel version? Can you give me a kernel version when it was > good and a version when it was bad? > > For a few kernel versions it

Re: Summary of the ARM ports BoF at DC15

On Mon, 2015-09-14 at 15:31 +0200, Paul Wise wrote: > On Mon, Sep 14, 2015 at 2:29 PM, Lucy Wayland wrote: > > On Sat, Sep 12, 2015 at 03:55:38PM +0100, Ian Campbell wrote: > > > On Fri, 2015-09-11 at 16:58 +0100, Steve McIntyre wrote: > > > Does this issue go away ent

Re: Summary of the ARM ports BoF at DC15

On Sat, 2015-09-12 at 23:26 +0100, Wookey wrote: > +++ Ian Campbell [2015-09-12 15:55 +0100]: > > > The other two subarches in the kernel are orion5x and versatile. I > have > > no personal interest in either. My gut suggests that orion5x (the > > Marvell variant pr

Re: Summary of the ARM ports BoF at DC15

On Fri, 2015-09-11 at 16:58 +0100, Steve McIntyre wrote: > armel > = > > [...] > Known worries/issues: > > * Kernel size due to very restrictive flash space; has been a >problem, but not believed to be affecting current users so much >now. Several problematic sub-arches have been

Re: flash-kernel puts QNAP on its knees

On Sun, 2015-09-06 at 13:02 +0200, Rob J. Epping wrote: > Hi, > > On 08/21/2015 02:11 PM, Ian Campbell wrote: > > On Sun, 2015-08-09 at 09:39 +0200, JM wrote: > >> > >> This is just a hunch, but perhaps a part of the problem is because > >> flash-kerne

Re: I/O issues with writing to mtdblock devices on kirkwood

On Sat, 2015-09-05 at 23:08 +0200, Andrew Lunn wrote: > On Fri, Aug 21, 2015 at 01:24:17PM +0100, Ian Campbell wrote: > > Hi kirkwood-upstream, > > > > We (Debian) have had a couple of reports of I/O errors running > Debian > > on kirkwood, specifically it seems t

Re: Modifying kernel bootargs

On Fri, 2015-09-04 at 09:19 +0100, Tim Fletcher wrote: > On 03/09/15 17:56, Ian Campbell wrote: > > On Thu, 2015-09-03 at 18:00 +0200, JM wrote: > > > Hi, > > > > > > I can't seem to figure out how to pass kernel parameters using flash > > > -kernel. T

Re: Modifying kernel bootargs

On Thu, 2015-09-03 at 18:00 +0200, JM wrote: > Hi, > > I can't seem to figure out how to pass kernel parameters using flash > -kernel. This is with flash-kernel 3.45 and linux-image-kirkwood 4.1.0-2 > from testing on QNAP TS-212P. > > I edit the LINUX_KERNEL_CMDLINE in

Re: flash-kernel puts QNAP on its knees

On Sun, 2015-08-09 at 09:39 +0200, JM wrote: This is just a hunch, but perhaps a part of the problem is because flash-kernel simply cats the image to mtdblock, which is not the recommended way to deal with flash storage [1]. I'm afraid I disagree with this, cat-ing to mtdblock is IMHO

I/O issues with writing to mtdblock devices on kirkwood

Hi kirkwood-upstream, We (Debian) have had a couple of reports of I/O errors running Debian on kirkwood, specifically it seems to relate to later kernels (e.g. 4.0+) and I _suspect_ (without proof) that it may be due to the switch from board files to the DTS based kernel, or some change implied

Re: I/O issues with writing to mtdblock devices on kirkwood

On Fri, 2015-08-21 at 15:07 +0200, Andrew Lunn wrote: On Fri, Aug 21, 2015 at 01:24:17PM +0100, Ian Campbell wrote: Hi kirkwood-upstream, Hi Ian Thanks for forwarding the reports to us. I will try to reproduce it on my TS-119P. No problem. BTW maybe Debian bug #794265[0] is related

Re: RAID installation (Kirkwood) QNAP TS-420U

On Fri, 2015-07-10 at 22:09 +0200, Peter Nagel wrote: Am 09.07.2015 14:38, schrieb Peter Nagel: I'm thinking about to first install wheezy and than dist-upgrade to jessie ... Are there any other (better) solutions? ... a dist-upgrade from wheezy to jessie does not solve the problem.

Re: RAID installation (Kirkwood) QNAP TS-420U

On Sat, 2015-07-11 at 15:05 +0200, Nagel, Peter (IFP) wrote: Am 11.07.2015 um 11:12 schrieb Ian Campbell: According to my reading of the release notes that you linked to either nofail or noauto on the appropriate line in the fstab is supposed to do just that. Reading further at http

Re: Brief report: QNAP TS-212P with linux-image-kirkwood 4.0.0-2

On Tue, 2015-07-07 at 23:17 +0200, JM wrote: On Fri, May 29, 2015 at 2:14 PM, JM fi...@archlinux.us wrote: * qcontrol service does not start. This appears to be due to the fact that qcontrol expects a symlink platform-gpio-keys-event in /dev/input/by-path, while with

Re: Kirkwood installation on QNAP TS-420U

On Sat, 2015-06-27 at 12:02 +0200, Nagel, Peter (IFP) wrote: My problem was that I have done the installation without any user account (using the expert mode) which is a bad idea if ssh is the only connection and root is (by default) not allowed to login via ssh. My understanding was that

Re: U-Boot, d-i and selecting the console device

On Sun, 2015-06-21 at 19:01 +0200, Karsten Merker wrote: What about adding support in debian-installer to dsisplay on both the serial console and framebuffer? My memory on that topic is unfortunately a bit shady, but IIRC this was proposed some time ago already and was dismissed due to

Re: How to start Xen hypervisor on armhf based system(s)?

On Fri, 2015-06-26 at 09:27 -0400, Nigel Sollars wrote: Hi Guido, I think this is the sauce your looking for: http://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions#Booting_Xen That plus the Allwinner specific stuff at

Re: Kirkwood installation on QNAP TS-420U

On Fri, 2015-06-26 at 16:27 +0200, Nagel, Peter (IFP) wrote: [...] Just a hunch, but can you still log-in as install/installer? Perhaps the kernel/initrd didn't get flashed and you somehow ended up in debian-installer again? [...] I've also tried to login as installer (for DHCP and known

Re: Brief report: QNAP TS-212P with linux-image-kirkwood 4.0.0-2

On Thu, 2015-06-04 at 14:30 +0200, JM wrote: I tested the patch you suggested, and somewhat surprisingly it fixed the xhci/USB3.0 initialization problem, Great! but the stalling and sata resets during kernel/initramfs flashing persist. Not Great :-( Please can you report this one to

Re: jessie installation problem on arm sheevaplug

On Sun, 2015-06-07 at 14:09 +0200, John Hughes wrote: Marvell setenv teststring abcdef Marvell setenv testcmd 'setenv testvar $(teststring)' Marvell run testcmd Marvell printenv testvar testvar=$(teststring) It looks like the interpolation is not

Re: Brief report: QNAP TS-212P with linux-image-kirkwood 4.0.0-2

On Sun, 2015-05-31 at 15:55 +0200, JM wrote: Yes, I managed to catch it in the act: http://pastebin.com/PYqqrcLX Basically, the device stalls during the flashing process (which takes maybe three minutes), and that seems to cause sata to time out, and eventually everything gets remounted

Re: Brief report: QNAP TS-212P with linux-image-kirkwood 4.0.0-2

On Tue, 2015-06-02 at 08:40 +0100, Ian Campbell wrote: On Sun, 2015-05-31 at 15:55 +0200, JM wrote: Yes, I managed to catch it in the act: http://pastebin.com/PYqqrcLX Basically, the device stalls during the flashing process (which takes maybe three minutes), and that seems

Re: Brief report: QNAP TS-212P with linux-image-kirkwood 4.0.0-2

On Fri, 2015-05-29 at 14:14 +0200, JM wrote: * I am experiencing system instability following flash-kernel on kernel update: rm: cannot remove ‘/tmp/flash-kernel.VuR9vASl’: Read-only file system run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 1 dpkg:

Re: 3.16 kernel features on QNAP TS-212p

On Sun, 2015-05-17 at 20:25 -0700, Martin Michlmayr wrote: Ian, are you familiar with these features? Not really. For #2 a bug report against the kernel would be appreciated so we can consider enabling it for Stretch if not Jessie. Only problem would be if it were something which has to be

Re: Upgrading QNAP HS-210 to Jessie

On Thu, 2015-05-07 at 16:00 -0400, Philippe Clérié wrote: Hello, I have just completed a dist-upgrade of the HS-210 to Jessie. Things went pretty I'd. It boots, I can SSH in with the same key, my stuff is still there, but the front LED flashes red and it emits a long beep every minute.

Re: Upgrading QNAP HS-210 to Jessie

On Fri, 2015-05-08 at 13:13 -0400, Philippe Clérié wrote: On 08/05/15 05:50, Ian Campbell wrote: On Thu, 2015-05-07 at 16:00 -0400, Philippe Clérié wrote: Hello, I have just completed a dist-upgrade of the HS-210 to Jessie. Things went pretty I'd. It boots, I can SSH in with the same

Re: Cubietruck install - no wlan?

On Sun, 2015-05-03 at 13:49 +, Andrew M.A. Cater wrote: Clean install of Jessie - no wlan appears to be detected even after installing firmware-brcm80211 and adding the text file. Install of Debian using Debian SD card image and a USB stick with hd-media and debian-arm CD1. Wireless

Re: Cubox i4pro real time clock(s)

On Wed, 2015-04-29 at 15:33 -0700, Rick Thomas wrote: On Apr 29, 2015, at 12:35 PM, Karsten Merker wrote: On Tue, Apr 28, 2015 at 04:55:40AM -0700, Rick Thomas wrote: On Apr 10, 2015, at 4:20 AM, Karsten Merker mer...@debian.org wrote: On Fri, Apr 10, 2015 at 03:07:31AM -0700, Rick Thomas

  1   2   3   4   >