Bug 64718
Summary: | gpm generates oops following Kickstart install | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Bob Cochran <cochranb> |
Component: | anaconda | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED NOTABUG | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-21 18:48:52 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Attachments: |
Description
Bob Cochran
2002-05-10 01:29:58 UTC
Created attachment 56864 [details]
This is the ks.cfg file I used for the install that triggered the gpm oops.
Created attachment 56865 [details]
This is the XF86Config-4 file generated by anaconda which I think caused the gpm oops.
Created attachment 56866 [details]
This is the XF86Config-4 file which works well for me on that particular laptop.
Looks like anaconda is generating bogus config files and symlink loops... What does /etc/sysconfig/mouse say after your installation? (XF86Config-4 isn't related to gpm at all, but the X not starting problem is.) I've long since reinstalled 7.3 from CD without using kickstart, and I didn't think to check /etc/sysconfig/mouse at the time of the oops. However I'll be happy to reinstall using kickstart. Let me know if you would like that. Yes that would help us. Closing due to inactivty, please reopen if you have additional information to add. Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |