PDA

View Full Version : [ubuntu] video works fine in Hardy, not in Jaunty



Bunny Boy
November 27th, 2009, 05:07 PM
I've installed Jaunty on a computer that has been running Dapper, as a dual boot, but I can't get it to recognize my video card. It will only boot in low-graphics mode, with a series of error messages.

Here is what lshw tells me about the video card:

*-display UNCLAIMED
description: VGA compatible controller
product: KM400/KN400/P4M800 [S3 UniChrome]
vendor: VIA Technologies, Inc.
physical id: 0
bus info: pci@0000:01:00.0
version: 01
width: 32 bits
clock: 66MHz
capabilities: pm agp agp-3.0 bus_master cap_list
configuration: latency=32 mingnt=2

What do I need to do to get this working like it did in Dapper?

khelben1979
November 27th, 2009, 07:45 PM
That means that the Linux kernel recognizes the graphics hardware, but that the system is unable to configure it correctly.

Post your /etc/X11/xorg.conf in this thread.

Bunny Boy
November 27th, 2009, 08:47 PM
That means that the Linux kernel recognizes the graphics hardware, but that the system is unable to configure it correctly.

Post your /etc/X11/xorg.conf in this thread.

OK, here 'tis:

**********************************************
# xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# Note that some configuration settings that could be done previously
# in this file, now are automatically configured by the server and settings
# here are ignored.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "Device"
Identifier "Configured Video Device"
EndSection

Section "Monitor"
Identifier "Configured Monitor"
EndSection

Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
EndSection

************************************************** ***
Not much there to work with, eh?

khelben1979
November 27th, 2009, 09:59 PM
Not much there to work with, eh?

No, not much. Adding different screen resolutions manually to that configuration file can make it broken unless it's done correctly.

If you noted down the configuration file from Dapper, then you could compare those 2 configuration files to easily see what it lacks, but I assume you don't have it, so I guess it's back to google searches then.. :)

khelben1979
November 27th, 2009, 10:03 PM
In this old thread (http://ubuntuforums.org/showthread.php?t=88374) they discuss this matter as well.

The configuration file looks better there.

Bunny Boy
November 27th, 2009, 11:03 PM
If you noted down the configuration file from Dapper, then you could compare those 2 configuration files to easily see what it lacks, but I assume you don't have it, so I guess it's back to google searches then.. :)

Actually, I do have it:

*************************************************

# /etc/X11/xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the /etc/X11/xorg.conf manual page.
# (Type "man /etc/X11/xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "Files"
FontPath "/usr/share/X11/fonts/misc"
FontPath "/usr/share/X11/fonts/cyrillic"
FontPath "/usr/share/X11/fonts/100dpi/:unscaled"
FontPath "/usr/share/X11/fonts/75dpi/:unscaled"
FontPath "/usr/share/X11/fonts/Type1"
FontPath "/usr/share/X11/fonts/100dpi"
FontPath "/usr/share/X11/fonts/75dpi"
# path to defoma fonts
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

Section "Module"
Load "i2c"
Load "bitmap"
Load "ddc"
Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "type1"
Load "vbe"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc104"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "Device" "/dev/wacom" # Change to
# /dev/input/event
# for USB
Option "Type" "stylus"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "eraser"
Option "Device" "/dev/wacom" # Change to
# /dev/input/event
# for USB
Option "Type" "eraser"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "cursor"
Option "Device" "/dev/wacom" # Change to
# /dev/input/event
# for USB
Option "Type" "cursor"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "Device"
Identifier "VIA Technologies, Inc. VT8378 [S3 UniChrome] Integrated Video"
Driver "via"
BusID "PCI:1:0:0"
EndSection

Section "Monitor"
Identifier "Generic Monitor"
Option "DPMS"
HorizSync 28-80
VertRefresh 43-75
EndSection

Section "Screen"
Identifier "Default Screen"
Device "VIA Technologies, Inc. VT8378 [S3 UniChrome] Integrated Video"
Monitor "Generic Monitor"
DefaultDepth 24
SubSection "Display"
Depth 1
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
InputDevice "stylus" "SendCoreEvents"
InputDevice "cursor" "SendCoreEvents"
InputDevice "eraser" "SendCoreEvents"
EndSection

Section "DRI"
Mode 0666
EndSection

************************************************** *****
I tried copying it over, but it didn't work.

Bunny Boy
November 28th, 2009, 02:10 AM
I tried to correct the subject line. It should say Dapper instead of Hardy.

Anyway, when I downloaded the driver from VIA, I can't unpack it. -- gunzip tells me that the .tgz is not in gzip format. Any clue?

khelben1979
November 28th, 2009, 09:08 AM
I tried to correct the subject line. It should say Dapper instead of Hardy.

Anyway, when I downloaded the driver from VIA, I can't unpack it. -- gunzip tells me that the .tgz is not in gzip format. Any clue?


tar xvfz file.tgz
or

gzip -d file.tgz and then
tar xvf file.tar
should do it.

Anyway, I strongly believe that you need a tool for creating a new configuration file, since it's a newer version of x.org in Jaunty than Dapper, so just copying it over as you did is expected to fail.

About the driver you downloaded, I think it's unnecessary because you already have the driver in the Linux kernel. The driver needs to be used and that's the problem, not that your system is lacking it.

Bunny Boy
November 28th, 2009, 06:00 PM
tar xvfz file.tgz
or

gzip -d file.tgz and then
tar xvf file.tar
should do it.

Anyway, I strongly believe that you need a tool for creating a new configuration file, since it's a newer version of x.org in Jaunty than Dapper, so just copying it over as you did is expected to fail.

About the driver you downloaded, I think it's unnecessary because you already have the driver in the Linux kernel. The driver needs to be used and that's the problem, not that your system is lacking it.

I tried that xvfz, and it didn't work either, still says it's not in gzip format. What tool creates xorg.conf besides dexconf?

I did modprobe via, and then lsmod shows via, but the display still doesn't work.

khelben1979
November 28th, 2009, 06:33 PM
I tried that xvfz, and it didn't work either, still says it's not in gzip format. What tool creates xorg.conf besides dexconf?

If you had an video card from ATi or nVidia, the installer package creates a pretty big xorg.conf. I don't know what tool to use, but it seems you're stuck with Dexconf.


man dexconf if you're curious on what it can do.