Bug 53219 - automatically generated kickstart file incorrect
Summary: automatically generated kickstart file incorrect
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 7.3
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Brent Fox
QA Contact: Brock Organ
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-09-05 06:02 UTC by Joshua Jensen
Modified: 2007-04-18 16:36 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2001-09-06 00:16:19 UTC


Attachments (Terms of Use)

Description Joshua Jensen 2001-09-05 06:02:21 UTC
Description of Problem:

In the RC2 installer, when I select 24bpp, the anaconda-ks.cfg file created in 
/root/  still gives me:

xconfig --card "ATI Rage Mobility" --videoram 8192 --hsync 31.5-48.5 --vsync 
40-70 --resolution 1024x768 --depth 32

Shouldn't that 32 be a 24 ?   I tried changing the 24 bpp spec in 
XF86Config-4 to 32 bpp, but it isn't even a valid setting (for my video card, 
anyway).

Thanks,

Joshua

Comment 1 Michael Fulbright 2001-09-05 15:55:49 UTC
Are you saying that specifying '32' instead of '24' as the Depth in your
XF86Config-4 results in a non-working configuration?

Comment 2 Joshua Jensen 2001-09-06 00:16:14 UTC
Yes, that is what I'm saying... but that is not the bug.  The bug is that I
specified 24 in the installer, and the kickstart file contains "32" instead of
24.  So, if I were to use the kickstart file, I would have a non-working
XF86Config-4 configuration (assuming that the "32" from the kickstart file was
correctly used during a kickstart).

Shouldn't I get the 24 that I am selecting in the installer in the kickstart
file as well?... or is there some similarity between 24bpp and 32bpp (I think I
remember some for whatever reason in the past) that should equate the two
settings to each other?

Joshua

Comment 3 Jeremy Katz 2001-09-06 00:35:10 UTC
24 and 32 are the same;  people think it's 32 but it always does 24bpp in the X
configuration


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