Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
Not eligible to see or edit group visibility for this bug.
View Bug Activity | Format For Printing | XML | Clone This Bug
root@moon_gen_2:/etc/conf.d# hddtemp /dev/hda WARNING: Drive /dev/hda doesn't appear in the database of supported drives WARNING: But using a common value, it reports something. WARNING: Note that the temperature shown could be wrong. WARNING: See --help, --debug and --drivebase options. WARNING: And don't forget you can add your drive to hddtemp.db /dev/hda: MAXTOR STM3160212A: 34°C or °F root@moon_gen_2:/etc/conf.d# hddtemp /dev/hdb WARNING: Drive /dev/hdb doesn't appear in the database of supported drives WARNING: But using a common value, it reports something. WARNING: Note that the temperature shown could be wrong. WARNING: See --help, --debug and --drivebase options. WARNING: And don't forget you can add your drive to hddtemp.db /dev/hdb: ST3400620A: 40°C or °F root@moon_gen_2:/etc/conf.d# hddtemp /dev/hdc WARNING: Drive /dev/hdc doesn't appear in the database of supported drives WARNING: But using a common value, it reports something. WARNING: Note that the temperature shown could be wrong. WARNING: See --help, --debug and --drivebase options. WARNING: And don't forget you can add your drive to hddtemp.db /dev/hdc: MAXTOR STM3160212A: 31°C or °F root@moon_gen_2:/etc/conf.d# hddtemp /dev/hdd /dev/hdd: ST3120026A: 37°C root@moon_gen_2:/etc/conf.d# telnet localhost 7634 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. |/dev/hda|MAXTOR STM3160212A|UNK|*||/dev/hdb|ST3400620A|UNK|*||/dev/hdc|MAXTOR STM3160212A|UNK|*||/dev/hdd|ST3120026A|37|C|Connection closed by foreign host. [ebuild R ] app-admin/hddtemp-0.3_beta15-r2 USE="nls" 0 kB [0] I already reported those drives to maintainer 4 months ago; by the mean time, I patched my local hddtemp.db myself, and all was fine until this week. 2 days ago, Gentoo did an update on this app, and I am very sad to see that upstream did not consider the serial ID I provided them. Anyway, CLI provides clearly a WARNING, not an error, thus, I expect the daemon to provide readed values, and not stuck "UNK" when there is actually a value available.
Created an attachment (id=126652) [details] /tmp/emerge--info
*** This bug has been marked as a duplicate of bug 187430 ***
