Bug#590105: #590105

[Benjamin Cama <benoar@free.fr>]

Hi Antonios,

Le dimanche 27 février 2011 à 14:54 +0000, Antonios Galanopoulos a
écrit :
> The problem persists with the new 2.6.37 based installer although the 
>  dmesg output from Benjamin is much different from mine and the original 
>  bug reporter.
> 
>  The relevant dmesg output:
> 
>  [   29.436956] libata version 3.00 loaded.
>  [   29.507060] sata_mv sata_mv.0: version 1.28
>  [   29.512272] sata_mv sata_mv.0: slots 32 ports 2
>  [   29.523390] scsi0 : sata_mv
>  [   29.528183] scsi1 : sata_mv
>  [   29.533771] ata1: SATA max UDMA/133 irq 29
>  [   29.537947] ata2: SATA max UDMA/133 irq 29
>  [   29.886113] ata1: SATA link down (SStatus 0 SControl 300)
>  [   30.236116] ata2: SATA link down (SStatus 0 SControl 300)

So, 2.6.37 is the same as 2.6.32 for you too, right?

>  My NAS hasnt't got a serial and is not a wsgl so  I thought it will not 
>  work. I am more than happy to do so if it helps.

Actually, looking at what /proc/cpuinfo gave me with Martin's version,
i.e. a correct "Linkstation Mini" machine type, the fix might just be
that my machine type was not enabled in the lspro kernel.

I tried looking for your machine type in upstream sources, but didn't
even found it in the latest kernel; are you sure your NAS is even
supported upstream? Does Buffalo give kernel sources for your NAS
version?

BTW, I don't even know if machine type can be autodetected? As making
separate images for each NAS would be quite cumbersome.

Regards,
benjamin