Activity log for bug #36604
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2006-03-25 16:28:33 | Jean Privat | bug | added bug | ||
| 2006-03-25 16:29:38 | Jean Privat | powernowd: assignee | sladen | ||
| 2006-03-25 16:29:38 | Jean Privat | powernowd: statusexplanation | |||
| 2006-03-25 16:31:49 | Jean Privat | bug | added attachment 'cpuinfo' (cpuinfo) | ||
| 2006-03-25 16:32:33 | Jean Privat | bug | added attachment 'dmesg' (dmesg) | ||
| 2006-03-25 16:33:14 | Jean Privat | bug | added attachment 'dmidecode' (dmi) | ||
| 2007-03-22 02:45:03 | Paul Sladen | powernowd: assignee | sladen | ||
| 2007-03-22 04:11:30 | Paul Sladen | powernowd: status | Unconfirmed | Rejected | |
| 2007-03-22 04:11:30 | Paul Sladen | powernowd: statusexplanation | Okay, I'm going to jump and finally Reject this one---based on the fact that it's a hardware limitation. Nico: Yeah, because this is such a corner case, it's going to be a little hard. Yes, it's possible to match machines based on the 'DMI' data (use 'dmidecode' or look in /var/cache/acpi-support/*-* for the saved output). One possibility from being able to construct a cast-iron match is to apply this directly into the kernel module. |
