Last two characters of ID_REVISION (firmware version) are inverted
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
udev (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
Binary package hint: udev
When looking for the firmware version of my hard disk (/dev/sda), I found out the last two characters reported by udevadm are inverted:
$ udevadm info --name=/dev/sda --query=property | grep ID_REVISION
ID_REVISION=
I believe the above information is also used by palimpsest, see:
http://
This is very inconvenient when trying to determine if such a disk needs a firmware upgrade on a headless system.
dmesg, however, has the right information:
magicfab@winston:~$ dmesg | grep ATA-7
[ 2.902938] ata3.00: ATA-7: INTEL SSDSA2M040G2GC, 2CV102HD, max UDMA/133
I checked this on several systems and got the same inconsistent information. I haven't checked dmegs output from a live CD to see if it would include the fixed HD information, though.
I've filed a separate bug about lshw reporting only part of such information, Bug #663349.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: udev 162-2.1
ProcVersionSign
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Mon Nov 8 16:26:05 2010
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: Hewlett-Packard HP Pavilion tx1000 Notebook PC
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: udev
dmi.bios.date: 04/18/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.20
dmi.board.name: 30BF
dmi.board.vendor: Quanta
dmi.board.version: 69.2E
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP Pavilion tx1000 Notebook PC
dmi.product.
dmi.sys.vendor: Hewlett-Packard
Changed in udev (Ubuntu): | |
importance: | Undecided → Low |
description: | updated |
tags: | added: raring |
Changed in udev (Ubuntu): | |
status: | Confirmed → Fix Released |
Confirming, I see the same issue on very different hardware.