kernel does not recognize Western Digital Caviar SE WD3200AAJS 320GB 7200 RPM SATA 3.0Gb/s Hard Drive (2nd generation)
Bug #257790 reported by
kc77
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Fix Released
|
Medium
|
|||
linux (Ubuntu) |
Fix Released
|
Medium
|
Manoj Iyer | ||
Jaunty |
Fix Released
|
Medium
|
Manoj Iyer |
Bug Description
I have M2N-SLI deluxe motherboard. In the latest linux kernels the Western Digital Caviar SE WD3200AAJS 320GB 7200 RPM SATA 2nd Generation Hard Drive is not recognized by the kernel. This hard drive works in Windows and works in older kernels (Gutsy) but in Hardy it does not. This most likely effects any of the latest kernels as it effects newer versions of Clonezilla, while older versions work fine.
Changed in linux: | |
importance: | Undecided → Medium |
status: | Incomplete → Triaged |
Changed in linux: | |
status: | Unknown → Fix Released |
Changed in linux (Ubuntu Jaunty): | |
assignee: | nobody → manjo |
tags: | added: hw-specific |
tags: |
added: verification-done removed: verification-needed |
Changed in linux: | |
importance: | Unknown → Medium |
To post a comment you must log in.
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information. /wiki.ubuntu. com/KernelTeamB ugPolicies . Thanks in advance!
Please include as attachments, from Gutsy or Hardy, the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https:/