|
Bugzilla – Full Text Bug Listing |
| Summary: | utc_only true on EFIKA | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | peter czanik <peter> |
| Component: | Installation | Assignee: | Jiri Srain <jsrain> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | coolo, jsuchome |
| Version: | Alpha 2plus | ||
| Target Milestone: | --- | ||
| Hardware: | PowerPC | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | yast2 logs | ||
|
Description
peter czanik
2008-03-11 09:59:14 UTC
Created attachment 200146 [details]
yast2 logs
AFAIK the reason to let the user decide between "HW clock running on UTC" or "HW clock running on local time" was to not confuse a parallel-bootable MS Windows. Since this is not an issue on PPC, it might make sense to not offer this selection. Well, the user is asked on another PPC machine, the Pegasos, that's why I considered it a bug on the EFIKA. And there are alternative OS-es for Pegasos and EFIKA, which assume, that the clock is set to local time. So, please enable it also on EFIKA. Arch::board_chrp () should return false and EFIKA should be detected by Arch::board_pegasos () Efika detection is broken. In order to fix it properly, could you, please, provide the contents of /proc/device-tree/device_type and /proc/device-tree/model ? I don't have any efika to have a look myself... homeserver:/proc/device-tree # cat device_type efikahomeserver:/proc/device-tree # cat model EFIKA5K2homeserver:/proc/device-tree # so, it is 'efika' and 'EFIKA5K2' Inside SuSE Olaf Hering has an EFIKA. Thanks, I fixed the detection according to your data in SVN. With Beta1 efika should be detected properly and not handled like mainframes. Tested current factory (from 2008-03-25), but the dialog is still not enabled. Which version of yast2? You need at least 2.16.39. If you have >= 2.16.39, please, reopen and attach the logs. |