On Tue, 2015-07-07 at 23:17 +0200, JM wrote:
> On Fri, May 29, 2015 at 2:14 PM, JM 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
> the
On Fri, May 29, 2015 at 2:14 PM, JM 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 the 4.0 kernel it's called
> "platform-gpio_keys-event" instead. As a workaround, ad
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
On Tue, Jun 2, 2015 at 10:00 AM, Ian Campbell wrote:
> 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 durin
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 th
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 re
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 read-only. Now if I recall correctly, I'd get
sata li
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:
I've begun testing 4.0 kernel on QNAP TS-212P. The following results likely
apply also to other devices matching kirkwood-ts219-6282.dtb like TS-210
and variants of TS-219. So, let's begin with...
The Good:
* mv_cesa works correctly (partially broken in 3.16 - #783718)
* kirkwood-cpufreq works co
9 matches
Mail list logo
