|
Bugzilla – Full Text Bug Listing |
| Summary: | Installation hangs at timezone settings | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Hanna Lindgren <han.lind> |
| Component: | Kernel | Assignee: | Vojtech Pavlik <vojtech> |
| Status: | RESOLVED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Critical | ||
| Priority: | P5 - None | CC: | eich, lslezak |
| Version: | RC 1 | ||
| Target Milestone: | --- | ||
| Hardware: | i386 | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
YaST logs
Output from /usr/sbin/hwinfo |
||
|
Description
Hanna Lindgren
2005-09-11 21:41:39 UTC
Could you, please, try to get and attach YaST logs? http://www.opensuse.org/Bug_Reporting_FAQ#YaST Thanks Created attachment 49577 [details]
YaST logs
Thanks for logs, it seems that the hardware probing is somehow broken, could you, please try to attach the full input of the command `/usr/sbin/hwinfo` on that system? (Try to switch to the console). lslezak: yast2-tune, hwinfo.ycp, buildHwTree(), line 152 Created attachment 49580 [details]
Output from /usr/sbin/hwinfo
I don't know if this is of any help to you, but I previously had to install SUSE 9.3 with ACPI disabled. Yes, sure, I helps. So, please, try to boot to the installation with ACPI off whether it also hangs there. Thanks. I have already tested with ACPI off as well, and the same thing happens there. It seems that the problem is in kernel or it's HW related, hwinfo.ycp is OK (error in log "clients/hwinfo.ycp:152 SCR::Dir() failed" is not fatal, the module tries to get all nested atributes which not all devices have, in that case it fails). Myself, I'd suspect some problems in X related to the time changing suddenly. We've had problems with doubleclick and screen blanking in the past. Egbert, what do you think? FYI, it freezes just after the time settings dialog is displayed, but I never get any chance to edit the time settings (i.e. no sudden time changes have been made). The Xserver used to be allergic to the time being set backwards. This used to
create the stranges effects. Today we only take time deltas and only if they are
>0.
This may however theoreticall still cause problems when the time is set forward
in big steps. I cannot think of such a scenario where this would be the case
right now and mself have never observed such problems so far. It would be
interesting to know how the timezone had been changed.
Is this still a problem with 10.0 final? No info for a few weeks -> closing. Please reopen if you still have a problem with 10.0 final. |