I have installed a brand new SSD samsung 830, 128GB on ASUS P5N-D board which integrates a - Chipset NVIDIA 750i SLI controller, the SSD works just fine in windows.
In Linux Opensuse 12.1, Samsung SSD 830 is not working, it is not correctly recognised and device is not created (dmesg snippet):
2.551039] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
2.554233] ata4.00: native sectors (250069680) is smaller than sectors (2251799813685248)
2.554238] ata4.00: ATA-9: SAMSUNG SSD 830 Series, CXM03B1Q, max UDMA/133
2.554241] ata4.00: 2251799813685248 sectors, multi 1: LBA48 NCQ (depth 31/32)
2.557156] ata4.00: model number mismatch 'SAMSUNG SSD 830 Series' != 'MSUNG SSD 830 Series \xffffff80'
2.557158] ata4.00: revalidation failed (errno=-19)
2.557357] ata4: limiting SATA link speed to 1.5 Gbps
2.557359] ata4.00: limiting speed to UDMA/133:PIO3
current kernel version:
Linux flagship 3.1.9-1.4-desktop #1 SMP PREEMPT Fri Jan 27 08:55:10 UTC 2012 (efb5ff4) x86_64 x86_64 x86_64 GNU/Linux
I have forgotten to update the kernel (I’m a bit conservative on kernel updates) , I have now:
Linux flagship 3.1.10-1.16-desktop #1 SMP PREEMPT Wed Jun 27 05:21:40 UTC 2012 (d016078) x86_64 x86_64 x86_64 GNU/Linux
And the device appears as /dev/sdc, I’ll do further testing.
It is definively an issue related to linux kernel and the best solution is to update the kernel.
I’m sorry for false alarm, I’ll left here this thread in order to help other guys with older opensuse versions or kernel release to track the problem.
On 08/29/2012 08:26 AM, fabtar wrote:
>
> I have solved the problem,
>
> I have forgotten to update the kernel (I’m a bit conservative on kernel
> updates) , I have now:
> Linux flagship 3.1.10-1.16-desktop #1 SMP PREEMPT Wed Jun 27 05:21:40
> UTC 2012 (d016078) x86_64 x86_64 x86_64 GNU/Linux
>
>
> And the device appears as /dev/sdc, I’ll do further testing.
> It is definively an issue related to linux kernel and the best solution
> is to update the kernel.
> I’m sorry for false alarm, I’ll left here this thread in order to help
> other guys with older opensuse versions or kernel release to track the
> problem.
Yes, the kernel developers do make progress. In your case, it seems that the fix
was backported to 3.1.10 by openSUSE, but for other cases, that may not be possible.
When I read your first post, I was about to suggest that you try running a Live
CD from 12.2RC2 to see if the problem had been fixed in kernel 3.4. Now, I am
quite certain that it would have been.
Your reluctance to change kernels is understandable, but when you find a problem
with new hardware, it may be too new for your kernel. After all, kernel 3.1 is
basically 18 months old. That is an eternity for kernels and SSD hardware. You
should investigate the zypper mechanism for retaining more that one kernel as
that gives you a recovery mechanism when something goes wrong.