Bug 7919
| Summary: | Installation not possible when using PGX32/PCI framebuffer as only fb in system | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Bill Bradford <mrbill> |
| Component: | installer | Assignee: | Jay Turner <jturner> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.1 | CC: | mrbill, srevivo |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | sparc | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2000-01-27 18:06:49 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: | |||
|
Description
Bill Bradford
1999-12-21 02:13:54 UTC
Are y'all ever gonna even look at this one, or are you just gonna ignore it? I'd really like to run RH on what is supposedly a suported platform... davem solved this one - the way that Sun tells you how to disable the onboard framebuffer conflicts with the way that RedHat probes the hardware. Problem solved. From Dave Miller
(here's the solution):
How did you "disable" the onboard mach64?
Did you do it by changing pcia-probe-list or pcib-probe-list
firmware environment variables? If so, don't do that.
Unfortunately this is how Sun's documentation which comes with
the PGX32 states you should make the PGX32 your console. Revert
pcia-probe-list and pcib-probe-list to their original settings
("1,2,3,4" and "1,2,3" respectively) and instead do this:
1) Find the "TSI,gfxp" device in the firmware device tree,
there is a fast way to do this, with the "display" command
or something like this but here is how bozos like me do
it the hard way. (neat trick of the day, if you forget some
firmware command word, but know some substring of it, you
can do a grep on the entire firmware forth vocabulary with
the "sifting" command, such as "sifting display")
Get to the "ok" prompt, and walk around the device tree with
"cd xxx" and "ls" commands, start at root with "cd /".
Go into the PCI bus tree, with "cd pci".
Next go into the PCI bridge where expansion PCI cards
live, with "cd pci@1" ("pci@1,1" are where onboard
devices live fyi)
Find the "TSI,gfxp" node, cd into it. Now type "pwd"
Write this output down.
2) Take the device path obtained in #1 and set your console
to it like this: "setenv output-device $TSI_PATH"
Where $TSI_PATH is replaced with the path to the PGX32
card.
"reset" and you're in buisness.
For the intellectually curious, these pci{a,b}-probe-list environment
variables are Sun's awful way of "hiding" devices from the OS. It
works for Solaris because they use only the firmware software device
tree for probing, it fails for Linux which actually probes the raw
hardware to find PCI devices. So if you try to "hide" devices, Linux
will see it but won't have critical information it needs from the
firmware device tree, and the card won't be initialized as it would
be if the firmware had probed it at all.
This issue comes up on CP1400/CP1500 compact-PCI machines from
Sun Microelectronics as well, they do it there to try and hide
the second onboard ethernet interface if you have not purchased
the machine with the I/O expansion board which is where the
twisted-pair jack for the second ethernet is.
|