Bug 15813

Summary: cdrom install not starting X on C&T 65555
Product: [Retired] Red Hat Linux Reporter: Andrea Borgia <andrea.borgia>
Component: anacondaAssignee: Brent Fox <bfox>
Status: CLOSED RAWHIDE QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1CC: pbrown
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard: Winston gold
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-12-08 01:11:50 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 Flags
Heavily customized XF86Config for 6.2
none
X config generated by RC1 installer
none
X config generated by me with Xconfigurator in RC1 post-installation checkup none

Description Andrea Borgia 2000-08-09 13:36:44 UTC
Upgrading from 6.2, the installer starts TUI without asking
(did not happen in 6.2; card is C&T 65555, DDC probe is ok in 6.2, checked now)

Comment 1 Glen Foster 2000-08-09 19:55:23 UTC
This defect is considered MUST-FIX for Winston Gold-release

Comment 2 Matt Wilson 2000-08-14 19:29:52 UTC
Did you catch any messages on why it may fail?  Do you have a PS/2 mouse?


Comment 3 borgia 2000-08-17 11:25:33 UTC
RC1 but not 6.2: "found video card controller unknown" on Alt-F3, then goes TUI.


Comment 4 Michael Fulbright 2000-08-17 15:41:46 UTC
That particular message is ok - it means it didn't find a card that requires the
agpgart module to be loaded.


Comment 5 Michael Fulbright 2000-08-17 15:42:51 UTC
Does Xconfigurator properly setup your X display?

Comment 6 Matt Wilson 2000-08-17 21:36:44 UTC
Does it "click in" to X before going to text mode?  See any X server messages
stream by?


Comment 7 borgia 2000-08-18 06:12:23 UTC
To msf: how do I know that? Xconfigurator still hasn't had a chance to come up at this stage in install...
To msw: no X messages, nada, nil, null, zilch. No screen flashes either.

Comment 8 Matt Wilson 2000-08-18 06:18:35 UTC
how much system ram do you have?  cat /proc/meminfo from VC2


Comment 9 borgia 2000-08-18 06:50:20 UTC
Do you really need the "cat" or is it enough if I tell you? It's a standard Toshiba Satellite 320cds, with 32MB.

Comment 10 Matt Wilson 2000-08-18 06:52:09 UTC
Well, I'd like to know tha the kernel is detecting the amount of ram properly...



Comment 11 borgia 2000-08-18 12:06:21 UTC
Ok, checked: kernel detects all 32MB and has 9MB free when the shell on VC-2 is available.
BTW, another test machine I have has 128MBm, the kernel sees only 64MB (due to the VIA chipset, I guess) and X starts up fine on install.

Comment 12 Matt Wilson 2000-08-21 15:37:09 UTC
On a booted system, run:

python -c "from kudzu import *; probe(CLASS_VIDEO, BUS_UNSPEC, PROBE_ALL)"

and send the output, please.


Comment 13 Matt Wilson 2000-08-21 16:10:40 UTC
Rather, run:

python -c "from kudzu import *; print probe(CLASS_VIDEO, BUS_UNSPEC, PROBE_ALL)"


Comment 14 borgia 2000-08-21 20:10:36 UTC
[(None, 'Card:Chips & Technologies CT65555', 'C&T|F65555 HiQVPro')]

Comment 15 Matt Wilson 2000-08-21 20:31:44 UTC
Ugh, there is no reason why this shouldn't work.  This is a laptop?


Comment 16 borgia 2000-08-22 04:53:34 UTC
Yes, it's a Toshiba Satellite 320cds.

Comment 17 Matt Wilson 2000-08-23 18:29:47 UTC
Could you install it in text mode and send me the X configuration it writes out,
as well as any working X configuration you can come up with?


Comment 18 Andrea Borgia 2000-08-24 18:35:33 UTC
TUI RC1 install: detects card as CT65520, Xconfigurator loops when using custom monitor (so went for similar monitor type), X setup ok.


Comment 19 Andrea Borgia 2000-08-24 18:37:10 UTC
Created attachment 2919 [details]
Heavily customized XF86Config for 6.2

Comment 20 Andrea Borgia 2000-08-24 18:37:57 UTC
Created attachment 2920 [details]
X config generated by RC1 installer

Comment 21 Andrea Borgia 2000-08-24 18:39:14 UTC
Created attachment 2921 [details]
X config generated by me with Xconfigurator in RC1 post-installation checkup

Comment 22 Andrea Borgia 2000-08-27 14:55:54 UTC
Still there in RC2. After the installation, Xconfigurator generates a valid setup.


Comment 23 Michael Fulbright 2000-11-13 16:53:01 UTC
Added pbrown because apparently Xconfigurator setup works, but anaconda does
not.  Needs to have a unified solution in the future.

Comment 24 Brent Fox 2000-12-08 01:11:46 UTC
This should be fixed with the installer that is currently in CVS.  The new installer tries to use the frame buffer if possible, and this will allow the installer to 
work on many cards that didn't work in the past.  I'm resolving this bug, but please reopen if the problem persists in future versions.

Comment 25 Aaron Brown 2000-12-13 22:20:06 UTC
Verified as resolved.