From Fedora Project Wiki
(Add some examples to the expected results) |
m (corre3cted output) |
||
Line 24: | Line 24: | ||
#: <pre> | #: <pre> | ||
#: $ xdriinfo | #: $ xdriinfo | ||
#: Screen 0: | #: Screen 0: not direct rendering capable</pre> | ||
}} | }} | ||
[[Category:User Interface]] | [[Category:User Interface]] |
Revision as of 18:40, 30 June 2010
Description
A complete installation using the vesa driver for installation. Note that graphical install requires 256MB RAM.
How to test
- Boot the installer using any available means(boot.iso, CD, DVD, Live or PXE)
- At the initial screen, select the option labelled Install system with basic video driver
- To use the vesa driver during installation from a live image, press Tab key at the initial bootloader screen and add the parameters:
xdriver=vesa nomodeset
- To use the vesa driver during installation from a live image, press Tab key at the initial bootloader screen and add the parameters:
- Proceed with normal installation
Expected Results
- The installer boot screen displays the option, Install system with basic video driver
- The graphical installer displays properly and uses the vesa driver. Confirm vesa driver usage by inspecting
/tmp/X.log
. You should see output similar to the following:- [ 71.321] (II) VESA(0): initializing int10
- [ 71.325] (II) VESA(0): Primary V_BIOS segment is: 0xc000
- [ 71.326] (II) VESA(0): VESA BIOS detected
- [ 71.326] (II) VESA(0): VESA VBE Version 2.0
- [ 71.326] (II) VESA(0): VESA VBE Total Mem: 4096 kB
- [ 71.326] (II) VESA(0): VESA VBE OEM: VGABIOS Cirrus extension
- [ 71.326] (II) VESA(0): VESA VBE OEM Software Rev: 1.0
- [ 71.326] (II) VESA(0): VESA VBE OEM Vendor: VGABIOS Cirrus extension
- [ 71.326] (II) VESA(0): VESA VBE OEM Product: VGABIOS Cirrus extension
- [ 71.326] (II) VESA(0): VESA VBE OEM Product Rev: 1.0
- The installed system is configured with a boot argument:
xdriver=vesa
. This can be confirmed by inspecting/etc/grub.conf
or/proc/cpuinfo
on the installed system. - When X starts on the installed system, it should be using the vesa driver. Confirm by running
xdriinfo
- $ xdriinfo
- Screen 0: not direct rendering capable