FC3 - wrong screen resolution - A bug?

[Jim Cornette]

NOTE: Problem is more dfficult than I have experienced myself. Others 
might have s3virge graphics card experience. Read on with this pre-warning.

Truls Gulbrandsen wrote:

> | | |
> | | | Jim
> | | |
> | | | Monitor and Graphics
> | | | Video Integration    Integrated
> | | | Installed Video Memory    4 MB
> | | | Included Video Card    Graphic card - AGP - S3 Trio3D integrated
> | | |
> | | |
> | | |>
> | | |> Regards,
> | | |> Truls
> | | |
> | | |
> | | Thanks for feedback.
> | |
> | | Yes the correct video card is Trio 64 3D and it is listed.  So I went
> | | system settings ==> display and set the correct video card.
> | |
> | | Then I got an error message saying that the system would log out of X
> | | and correct an error.  It never came back.  So I rebooted but now the
> | | boot sequence goes to:
> | |
> | | Starting udev: (ok)
> | | Initializing hardware..... storage network audio done  (ok)
> | | Configuring kernel parameters:
> | |
> | | and there it hangs unresponsive.
> | |
> | | Probably I have to start the install process over again?
> | |
> | | Regards,
> | | Truls
> |
> | I found that when hittin ctrl-C after the system hangs it actually
> | continues to boot and gives me a command line.
> |
> | The problem is that system settings - display did not update my
> | xorg.conf file correctly.  The driver name for the video card was not
> | replaced with the corect one but ended up as mix of "Vesa" and "S3Trio3D"
> |
> | I tried to correct this using vi but am not able to open the file in
> | edit modus.  I'm told it is a read only file.
> |
> | Any suggestions?
> |
> | Truls
> Ok, I have followed all advices given under this thread without success.

I wish it was easier to get you up and running than it is. Anyway, I 
would like for you to get up and running w/ a higher resolution than you 
get now.

> 
> So, I did a fresh install of FC3 from the cds and the following happens.
> 
> Upon installation fc doesn't recognize my video card and set it up as
> VESA generic.  That works in the way that my screen background seem to
> have the correct resolution but applications and icons etc. seems work
> at 640x480.

Reading briefly through 'info s3virge' (there are man and info pages for 
the X drivers. Your card type was listed. There was a mention of the 
chipsets supported in this file. There also was a mention that you can 
add "trio 3d" in the device section of your xorg.conf file in order to 
evade auto-detection. the explanation is below from an excerpt from the 
info page for the s3virge driver. I don't understand it exactly, but 
reading the man page and info page yourself might cue you in regarding 
the options.

EXCERPT (info for S3Virge)

CONFIGURATION DETAILS
Please refer to xorg.conf(5x) for general configuration details. This
section only covers configuration details specific to this driver.
All options names are case and white space insensitive when parsed by
the server, for example, "virge vx" and "VIRGEvx" are equivalent.

The driver auto-detects the chipset type, but the following ChipSet
names may optionally be specified in the config file ""Device"" sec-
tion, and will override the auto-detection:

"virge", "86c325", "virge vx", "86c988", "virge dx", "86c375",
"virge gx", "86c385", "virge gx2", "86c357", "virge mx", "86c260",
"virge mx+", "86c280", "trio 3d", "86c365", "trio 3d/2x",
"86c362", "86c368".


> 
> Then, when I change to video card S3 Trio64 3D and reboot I'm back to
> the original problem.  The systems load all the way to:

What happens with replacing "vesa" with "s3virge" ? Does it autodetect 
your card correctly?

> 
> Starting udev: (ok)
> Initializing hardware..... storage network audio done  (ok)
> Configuring kernel parameters:
> 
> ~  <then I have to enter Ctrl-C to make it continue>
> 
> INIT: Entering runlevel: 5

Try booting into runlevel 3 by editing your boot loader and removing the 
rhgb quiet parameters and adding the number 3 after a space. Log into a 
terminal with your normal user account, then typing startx to start X in 
the normal way. Then after X launches or tries to launch, check 
/var/log/Xorg.0.log for any errors.

> Starting readahead early: (ok)
> Checking for new hardware: (ok)
> touch: cannot touch '/var/touch/subsys/kudzu': Read-only file system
> Applying iptables: firewal rules (ok)
> touch: cannot touch '/var/touch/subsys/iptables': Read-only file system
> Starting pcmcia: (ok)
> etc
> etc
> 
> Am I doing something wrong or the system?


There are bits of information that might lead to some reader catching 
onto what might be wrong with your setup, auto-configuration tools etc.

/sbin/lspci output, the xorg.conf file and /var/log/Xorg.0.log allow 
others to get a picture as to what your system is doing.
Someone helped find out why one xorg.conf file worked for me and an 
autogenerated version did not on another graphics card type.

I don't want to chance messing up your system and want you to consider 
this hints to lead you into a direction that will get your GUI up and 
running.

Bailing out, because this is over my head for a solution.

Jim

> 
> Regards
> Truls