Bug 23655 - installer traceback on Savage4 chipset
installer traceback on Savage4 chipset
Status: CLOSED DUPLICATE of bug 23439
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
7.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Brent Fox
Brock Organ
Florence Beta-3
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-01-09 11:09 EST by David Lawrence
Modified: 2007-04-18 12:30 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-01-09 16:20:44 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
anaconda traceback for SavageIX (714 bytes, text/plain)
2001-01-09 11:11 EST, David Lawrence
no flags Details

  None (edit)
Description David Lawrence 2001-01-09 11:09:31 EST
IBM Thinkpad T20 w/ SavageIX Mobility. Tracebacks occur when trying to load
second stage installer. This happens when I just hit enter at the boot:
prompt which causes the installer to use a default mode of 800x600x16 which
doesnt work on my machine for some reason. When I enter vga=791 then the
framebuffer server installs and graphical installer works.

When the installer fails to start the framebuffer and the native xserver it
should fall to text mode without generating tracebacks. I am attaching the
traceback output to this bug report.
Comment 1 David Lawrence 2001-01-09 11:11:19 EST
Created attachment 7304 [details]
anaconda traceback for SavageIX
Comment 2 Michael Fulbright 2001-01-09 16:20:39 EST
Assigning to a developer.
Comment 3 Brent Fox 2001-01-10 14:30:13 EST

*** This bug has been marked as a duplicate of 23439 ***

Note You need to log in before you can comment on or make changes to this bug.