Bug 76432
| Summary: | Anaconda freezes on "Probing for monitor type:" | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <jim> | ||||
| Component: | installer | Assignee: | Michael Fulbright <msf> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | Brock Organ <borgan> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 8.0 | CC: | chris.tolley, lown | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i586 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2003-06-18 20:46:30 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
Need Real Name
2002-10-21 18:46:55 UTC
Please try adding 'skipddc' to the boot commandline. I have tried the suggested work around "linux skipddc" and it did not help with the problem. Anaconda still locked up in the same place. Here is some additional system information from my computer: Proliant 1600 P(?) 450 with 512 cache Loaded: sym53c8xx driver Loaded: Cirrus Logic GD544x video card I have exactly the same problem on a Compaq 1850r. I also have tried the suggested work around "linux skipddc" and it did not help with the problem. Anaconda still locked up in the same place. Here is some additional system information from my computer: Proliant 1850r PII 500 with 512 cache Loaded: sym53c8xx driver Loaded: ATI Mach64 Rage II video card I know there are other postings with similar problems starting with version 7.3 and various solutions that have a poor success rate. Does it ever print out a monitor type? Also try switching to VC# (cntl-alt-f3) before the monitor probe is attempted and see what the last few lines are. Here is what is reported on the screen: Running anaconda, the Red Hat Linux system installer - please wait... Probing for video card: Cirrus Logic GD544x Probing for monitor type: Unable to probe _(blinking) The system is now halted. After pressing "cntrl+alt+f3", the following information is displayed: * Running anaconda script /usr/bin/ananconda * Probing for video card: Cirrus Logic GD544x * ddcprobe returned bogus values: ID: None Name: None HorizSync: None VertSync: None * Probing for monitor type: Unable to probe The monitor that I am using, is normally attached to a different Linux machine. It is a Compaq V720. Created attachment 89933 [details]
anaconda with debugging info
Please save the attachment I just added to an ext2 floppy named as 'anaconda'. Boot with 'linux updates' and insert the update floppy when asked. When the machine hangs look on VC3 and let me know what the line starting with 'skipddcprobe' says (it should have 3 #'s). I am out of the office right now. I will be back in the office 2/17/03. I will try what you asked for when I return. Thanks! This bug also seems to effect 7.3 builds, in addition to 8.0, and also effects Compaq Prolaint 1850R's. I believe it has nothing to do with the monitor hardware. I yanked my video cable loose before it began to probe and it still hung the system with "Unable to Probe". I do all my installs/upgrades via network and use: linux text noprobe during the initial boot with a bootnet.img floppy (so I can enter module options). Whatever scripting is included in the secondary install images, it does not honor the "noprobe" option. I realize that this is a kernel option during initial boot, but shouldn't it be possible to set this as an environment variable for the other scripts to inherit? At any rate, I'm going to pull apart the netstg1.img and stage2.img and comment out the scripting that insists on probing for a monitor during text installs... If anyone is interested in my findings, I'll post them back here. I added the 'skipddc' option in 8.0 to do what you are attempting to do. I was able to verify that the ddc probe does not occur when it is used. It unclear what the issue here is - I've only seen it on this hardware and unfortunately I do not have it here so I cannot fix this issue. As time allows I can try to answer question you may have as you look into this issue. Closing due to inactivity - please reopen if you have additional information to add. |