On Sun, Nov 27, 2016 at 7:50 AM, Ryan Tandy wrote:
> Control: tag -1 patch
>
> On Sat, Nov 26, 2016 at 12:59:21PM -0800, Ryan Tandy wrote:
>>
>> Unfortunately dmesg and kern.log are flooded with messages like:
>>
>> [ 161.781360] Bad eraseblock 32764 at 0x0001fff0
>> [ 161.786261] Bad eraseb
Control: tag -1 patch
On Sat, Nov 26, 2016 at 12:59:21PM -0800, Ryan Tandy wrote:
Unfortunately dmesg and kern.log are flooded with messages like:
[ 161.781360] Bad eraseblock 32764 at 0x0001fff0
[ 161.786261] Bad eraseblock 32765 at 0x0001fff4
[ 161.791159] Bad eraseblock 32766 at 0
Processing control commands:
> tag -1 patch
Bug #845611 [linux-image-4.8.0-1-marvell] linux-image-4.8.0-1-marvell: hard
drive not detected on LinkStation Pro (LS-GL)
Added tag(s) patch.
--
845611: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845611
Debian Bug Tracking System
Contact ow...@b
On Sun, Nov 27, 2016 at 01:20:10AM +0900, Roger Shimizu wrote:
- start your device by kernel 4.3 first.
- confirm your have flash-kernel and linux-image-4.8.0-1-marvell installed.
- cp /usr/lib/linux-image-4.8.0-1-marvell/orion5x-kuroboxpro.dtb
/etc/flash-kernel/dtbs/orion5x-linkstation-lsgl.dtb
Dear Ryan,
On Fri, Nov 25, 2016 at 4:24 PM, Ryan Tandy wrote:
>
> [ 611.971107] scsi host0: sata_mv
> [ 611.984111] scsi host1: sata_mv
> [ 611.984881] ata1: SATA max UDMA/133 irq 30
> [ 611.984916] ata2: SATA max UDMA/133 irq 30
> [ 612.302763] ata1: SATA link down (SStatus 0 SControl 300)
On Fri, Nov 25, 2016 at 05:02:06PM +, Ian Campbell wrote:
Oh, so the issue is not that you are missing a second disk, but rather
that the one disk you do have seems to not be detected? You theory is
that it is actually only the second port which is connected to anything
in this hw?
Yes, exa
On Fri, 2016-11-25 at 08:56 -0800, Ryan Tandy wrote:
> On Fri, Nov 25, 2016 at 04:24:31PM +, Ian Campbell wrote:
> >
> > Is it possible that there are multiple variants of this one with
> > differing numbers of disks?
> >
> > It's a little tricky to google for but all the LS-GL's I can see
>
On Fri, Nov 25, 2016 at 04:24:31PM +, Ian Campbell wrote:
Is it possible that there are multiple variants of this one with
differing numbers of disks?
It's a little tricky to google for but all the LS-GL's I can see _look_
like they are single disk (see [*] below). Or maybe the naming is jus
On Fri, 2016-11-25 at 08:10 -0800, Ryan Tandy wrote:
> On Fri, Nov 25, 2016 at 07:42:37AM +, Ian Campbell wrote:
> >
> > Assuming orion5x-linkstation.dtsi is correctly relating to your
> > platform you would appear to want one of:
> > $ git grep orion5x-linkstation.dtsi arch/arm/boot/dts/*.
On Fri, Nov 25, 2016 at 07:42:37AM +, Ian Campbell wrote:
Assuming orion5x-linkstation.dtsi is correctly relating to your
platform you would appear to want one of:
$ git grep orion5x-linkstation.dtsi arch/arm/boot/dts/*.dts
arch/arm/boot/dts/orion5x-kuroboxpro.dts:#include "orion5x-link
On Thu, 2016-11-24 at 23:24 -0800, Ryan Tandy wrote:
> whereas the new orion5x-linkstation.dtsi contains this code:
>
> &sata {
> status = "okay";
> nr-ports = <1>;
> };
A .dtsi is an include file, not the final thing for any given device,
for that you need a .dts (which is compil
Package: linux-image-4.8.0-1-marvell
Version: 4.8.7-1
Severity: normal
Tags: upstream
I found that on recent d-i images, the kernel does not detect the hard
drive on my LinkStation. I tried some older images and found that kernel
4.3.3-5 worked and kernel 4.6.2-2 did not.
I suspect the problem
12 matches
Mail list logo
