[opensuse] configuring my monitor
Hello again, Just trying to get my new monitor set up. I have a samsung LED monitor, but the automatic installation just put in some kind of default setting. How do I adjust the driver settings and find my new monitor to configure it correctly? George -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, Jul 27, 2011 at 06:36, George Olson <grglsn765@gmail.com> wrote:
Hello again, Just trying to get my new monitor set up. I have a samsung LED monitor, but the automatic installation just put in some kind of default setting.
How do I adjust the driver settings and find my new monitor to configure it correctly?
I think you need to provide more information.... - what video card are you using? - what monitor model are you trying to configure? - what openSUSE release are you using? - have you done a full update after installing openSUSE? So many things could be happening... you could be using an Intel video card that is misconfigured, you could have a monitor that is not giving the right EDID response, etc etc. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 07/27/2011 06:09 PM, C wrote: > On Wed, Jul 27, 2011 at 06:36, George Olson<grglsn765@gmail.com> wrote: >> Hello again, >> Just trying to get my new monitor set up. I have a samsung LED monitor, but >> the automatic installation just put in some kind of default setting. >> >> How do I adjust the driver settings and find my new monitor to configure it >> correctly? > I think you need to provide more information.... > - what video card are you using? > - what monitor model are you trying to configure? > - what openSUSE release are you using? > - have you done a full update after installing openSUSE? > > So many things could be happening... you could be using an Intel video > card that is misconfigured, you could have a monitor that is not > giving the right EDID response, etc etc. > > C. Thanks for helping me clarify. I am pretty new at this and don't always know what information to put out in the email. Video card - I am plugged into the VGA port on my motherboard, which is an msi k9vgm_v. I looked up the documentation on the motherboard, and it does not say anything about what it uses to run the video on it - it only says that it has a VGA port. So I am a bit lost on what to say on that one. Monitor model - it is a Samsung S20A300B openSUSE release - openSUSE 11.4 (x86_64) full update - I don't think so. How do I do that? When I installed thunderbird I updated the repositories, but I am not sure how to do a full update. George -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 07/27/2011 06:09 PM, C wrote: > On Wed, Jul 27, 2011 at 06:36, George Olson<grglsn765@gmail.com> wrote: >> Hello again, >> Just trying to get my new monitor set up. I have a samsung LED monitor, but >> the automatic installation just put in some kind of default setting. >> >> How do I adjust the driver settings and find my new monitor to configure it >> correctly? > I think you need to provide more information.... > - what video card are you using? > - what monitor model are you trying to configure? > - what openSUSE release are you using? > - have you done a full update after installing openSUSE? > > So many things could be happening... you could be using an Intel video > card that is misconfigured, you could have a monitor that is not > giving the right EDID response, etc etc. > > C. I did check, and according to my hardware settings in YaST, it says model SAMSUNG SA300/SA350, which I think is the correct model series. It also says height 900 width 1600, which matches the technical specifications on my monitor. The problem is, when I go to "configure desktop" under favorites on KDE, the only option for resolution that it gives is 1024x768. I would like to go to 900x1600, but I can't figure out how to do that under "configure desktop" George -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 27 of July 2011 15:58:52 George Olson wrote:
I did check, and according to my hardware settings in YaST, it says model SAMSUNG SA300/SA350, which I think is the correct model series. It also says height 900 width 1600, which matches the technical specifications on my monitor.
The problem is, when I go to "configure desktop" under favorites on KDE, the only option for resolution that it gives is 1024x768. I would like to go to 900x1600, but I can't figure out how to do that under "configure desktop"
I had the same problem here with this resolution and solved it by adding the following to /etc/X11/xorg.conf.d/50-monitor.conf above EndSection: VendorName "Unknown" ModelName "Unknown" DisplaySize 443 249 HorizSync 30.0 - 83.0 VertRefresh 56.0 - 75.0 #ModeLine "1600x900_60.00" 119 1600 1696 1864 2128 900 901 904 932 -hsync +vsync # Why does the following work, while the preceding doesn't? Who knows? Modeline "1600x900_60.00" 108 1600 1624 1704 1800 900 901 904 1000 +hsync +vsync Option "PreferredMode" "1600x900_60.00" This might work in your case.
George Regards, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2011/07/27 20:25 (GMT+0300) auxsvr@gmail.com composed:
I had the same problem here with this resolution and solved it by adding the following to /etc/X11/xorg.conf.d/50-monitor.conf above EndSection:
#ModeLine "1600x900_60.00" 119 1600 1696 1864 2128 900 901 904 932 -hsync +vsync # Why does the following work, while the preceding doesn't? Who knows? Modeline "1600x900_60.00" 108 1600 1624 1704 1800 900 901 904 1000 +hsync +vsync Option "PreferredMode" "1600x900_60.00"
You had to figure out your modeline with CVT or GTF, right? X is supposed to know how to do the same thing itself, except you have to trigger it to do so in some cases by adding to 'Section "Monitor"': 'Option "DefaultModes" "on"'. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 07/27/2011 06:09 PM, C wrote: > On Wed, Jul 27, 2011 at 06:36, George Olson<grglsn765@gmail.com> wrote: >> Hello again, >> Just trying to get my new monitor set up. I have a samsung LED monitor, but >> the automatic installation just put in some kind of default setting. >> >> How do I adjust the driver settings and find my new monitor to configure it >> correctly? > I think you need to provide more information.... > - what video card are you using? > - what monitor model are you trying to configure? > - what openSUSE release are you using? > - have you done a full update after installing openSUSE? > > So many things could be happening... you could be using an Intel video > card that is misconfigured, you could have a monitor that is not > giving the right EDID response, etc etc. > > C. So if anyone has any ideas on why my kde display configuration will not let me go to the full 1600x900 resolution while suse seems to have properly detected the monitor that I am using I would greatly appreciate it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2011/07/27 12:36 (GMT+0800) George Olson composed:
Just trying to get my new monitor set up. I have a samsung LED monitor, but the automatic installation just put in some kind of default setting.
How do I adjust the driver settings and find my new monitor to configure it correctly?
When you have common and unbroken hardware, automagic is supposed to produce ideal results without you trying to configure. You don't have one of the common and well supported gfxchips, so possibly you may not be able to. Your chipset is K8M890, which includes the "VIA Chrome9™ IGP (Integrated Graphics Processor) core". I have no idea whether this has a supported native driver. If it doesn't, it means the standard VESA modes would be all that are available. AFAIK, there are no widescreen VESA modes. Even if there were, 1600x900 is among the newest and least likely to have VESA support. Absent exchanging your Samsung 1600x900 for a 4:3 or 5:4 aspect display that VESA supports, and absent a native driver for the VIA IGP (which there may be, I simply don't know), the simplest solution may be simply spending more money, to buy an ATI or NVidia PCIe card and install it. Then automagic should be all you need. If the motherboard is also new, an even better solution may be to exchange it for one with well supported onboard video (Intel, NVidia or AMD/ATI). Before doing anything more, provide us access to the output of the command 'lspci | grep VGA', and the file /var/log/Xorg.0.log, and do a little Googling to find out the status of your gfxchip under Linux, particularly which if any driver besides VESA supports it. Maybe that's what unichrome is for, and either it's not installed, or your chip is newer than the 11.4 unichrome driver supports. Doing 'zypper in xorg-x11-driver-video-unichrome' as root and restarting X or rebooting may actually be all you need to do. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 07/28/2011 05:09 AM, Felix Miata wrote:
On 2011/07/27 12:36 (GMT+0800) George Olson composed:
Just trying to get my new monitor set up. I have a samsung LED monitor, but the automatic installation just put in some kind of default setting.
How do I adjust the driver settings and find my new monitor to configure it correctly?
When you have common and unbroken hardware, automagic is supposed to produce ideal results without you trying to configure. You don't have one of the common and well supported gfxchips, so possibly you may not be able to.
Your chipset is K8M890, which includes the "VIA Chrome9™ IGP (Integrated Graphics Processor) core". I have no idea whether this has a supported native driver. If it doesn't, it means the standard VESA modes would be all that are available. AFAIK, there are no widescreen VESA modes. Even if there were, 1600x900 is among the newest and least likely to have VESA support.
Absent exchanging your Samsung 1600x900 for a 4:3 or 5:4 aspect display that VESA supports, and absent a native driver for the VIA IGP (which there may be, I simply don't know), the simplest solution may be simply spending more money, to buy an ATI or NVidia PCIe card and install it. Then automagic should be all you need.
If the motherboard is also new, an even better solution may be to exchange it for one with well supported onboard video (Intel, NVidia or AMD/ATI).
Before doing anything more, provide us access to the output of the command 'lspci | grep VGA', and the file /var/log/Xorg.0.log, and do a little Googling to find out the status of your gfxchip under Linux, particularly which if any driver besides VESA supports it. Maybe that's what unichrome is for, and either it's not installed, or your chip is newer than the 11.4 unichrome driver supports. Doing 'zypper in xorg-x11-driver-video-unichrome' as root and restarting X or rebooting may actually be all you need to do. Thanks! - I able to get on that now -
lspci | grep VGA gave me the following: 01:00.0 VGA compatible controller: VIA Technologies, Inc. K8M890CE/K8N890CE [Chrome 9] (rev 11) I googled and found 2 drivers that say they support my chip, but I am not quite sure if they are Linux compatible drivers. Under the OS description on the driver download page, it says "probably all". Here are the names of the drivers - assuming that I looked everything up correctly: VIA K8M890CE/K8N890CE Display Driver 21. VIA K8M890CE & K8N890CE Display Driver Those could both be found from the following website: http://downloadnew.org/software/k8m890-linux-drivers/ As far as the log file, it is kind of long, but I have pasted it below. I really don't know what to look for in the log file, so I pasted the whole thing. the file /car/log/Xorg.0.log contains the following: [ 16.448] X.Org X Server 1.9.3 Release Date: 2010-12-13 [ 16.463] X Protocol Version 11, Revision 0 [ 16.463] Build Operating System: openSUSE SUSE LINUX [ 16.463] Current Operating System: Linux linux-8uzz 2.6.37.1-1.2-desktop #1 SMP PREEMPT 2011-02-21 10:34:10 +0100 x86_64 [ 16.463] Kernel command line: root=/dev/disk/by-id/ata-Hitachi_HDS721050CLA362_JP8521HR2HU93V-part2 resume=/dev/disk/by-id/ata-Hitachi_HDS721050CLA362_JP8521HR2HU93V-part1 splash=silent quiet vga=0x317 [ 16.463] Build Date: 22 February 2011 10:08:09PM [ 16.463] [ 16.463] Current version of pixman: 0.20.0 [ 16.463] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 16.463] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 16.463] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jul 27 19:57:05 2011 [ 16.463] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 16.464] (==) No Layout section. Using the first Screen section. [ 16.464] (**) |-->Screen "Default Screen" (0) [ 16.464] (**) | |-->Monitor "Default Monitor" [ 16.464] (**) | |-->Device "Default Device" [ 16.464] (==) Automatically adding devices [ 16.464] (==) Automatically enabling devices [ 16.464] (WW) The directory "/usr/share/fonts/TTF/" does not exist. [ 16.464] Entry deleted from font path. [ 16.464] (WW) The directory "/usr/share/fonts/OTF/" does not exist. [ 16.464] Entry deleted from font path. [ 16.464] (WW) The directory "/usr/share/fonts/misc/sgi" does not exist. [ 16.464] Entry deleted from font path. [ 16.464] (==) FontPath set to: /usr/share/fonts/misc:unscaled, /usr/share/fonts/Type1/, /usr/share/fonts/100dpi:unscaled, /usr/share/fonts/75dpi:unscaled, /usr/share/fonts/URW/, /usr/share/fonts/cyrillic:unscaled, /usr/share/fonts/truetype/ [ 16.464] (==) ModulePath set to "/usr/lib64/xorg/modules/updates,/usr/lib64/xorg/modules" [ 16.464] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 16.464] (II) Loader magic: 0x7dc040 [ 16.464] (II) Module ABI versions: [ 16.464] X.Org ANSI C Emulation: 0.4 [ 16.464] X.Org Video Driver: 8.0 [ 16.464] X.Org XInput driver : 11.0 [ 16.464] X.Org Server Extension : 4.0 [ 16.466] (--) PCI:*(0:1:0:0) 1106:3230:1462:7253 rev 17, Mem @ 0xc0000000/268435456, 0xdd000000/16777216, BIOS @ 0x????????/65536 [ 16.466] (II) Open ACPI successful (/var/run/acpid.socket) [ 16.466] (II) LoadModule: "extmod" [ 16.473] (II) Loading /usr/lib64/xorg/modules/extensions/libextmod.so [ 16.473] (II) Module extmod: vendor="X.Org Foundation" [ 16.473] compiled for 1.9.3, module version = 1.0.0 [ 16.473] Module class: X.Org Server Extension [ 16.473] ABI class: X.Org Server Extension, version 4.0 [ 16.473] (II) Loading extension MIT-SCREEN-SAVER [ 16.473] (II) Loading extension XFree86-VidModeExtension [ 16.473] (II) Loading extension XFree86-DGA [ 16.473] (II) Loading extension DPMS [ 16.473] (II) Loading extension XVideo [ 16.473] (II) Loading extension XVideo-MotionCompensation [ 16.473] (II) Loading extension X-Resource [ 16.473] (II) LoadModule: "dbe" [ 16.474] (II) Loading /usr/lib64/xorg/modules/extensions/libdbe.so [ 16.474] (II) Module dbe: vendor="X.Org Foundation" [ 16.474] compiled for 1.9.3, module version = 1.0.0 [ 16.474] Module class: X.Org Server Extension [ 16.474] ABI class: X.Org Server Extension, version 4.0 [ 16.474] (II) Loading extension DOUBLE-BUFFER [ 16.474] (II) LoadModule: "glx" [ 16.474] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so [ 16.474] (II) Module glx: vendor="X.Org Foundation" [ 16.474] compiled for 1.9.3, module version = 1.0.0 [ 16.474] ABI class: X.Org Server Extension, version 4.0 [ 16.474] (==) AIGLX enabled [ 16.475] (II) Loading extension GLX [ 16.475] (II) LoadModule: "record" [ 16.475] (II) Loading /usr/lib64/xorg/modules/extensions/librecord.so [ 16.475] (II) Module record: vendor="X.Org Foundation" [ 16.475] compiled for 1.9.3, module version = 1.13.0 [ 16.475] Module class: X.Org Server Extension [ 16.475] ABI class: X.Org Server Extension, version 4.0 [ 16.475] (II) Loading extension RECORD [ 16.475] (II) LoadModule: "dri" [ 16.476] (II) Loading /usr/lib64/xorg/modules/extensions/libdri.so [ 16.476] (II) Module dri: vendor="X.Org Foundation" [ 16.476] compiled for 1.9.3, module version = 1.0.0 [ 16.476] ABI class: X.Org Server Extension, version 4.0 [ 16.476] (II) Loading extension XFree86-DRI [ 16.476] (II) LoadModule: "dri2" [ 16.476] (II) Loading /usr/lib64/xorg/modules/extensions/libdri2.so [ 16.476] (II) Module dri2: vendor="X.Org Foundation" [ 16.476] compiled for 1.9.3, module version = 1.2.0 [ 16.476] ABI class: X.Org Server Extension, version 4.0 [ 16.476] (II) Loading extension DRI2 [ 16.476] (==) Matched via as autoconfigured driver 0 [ 16.476] (==) Matched openchrome as autoconfigured driver 1 [ 16.476] (==) Matched unichrome as autoconfigured driver 2 [ 16.476] (==) Matched fbdev as autoconfigured driver 3 [ 16.476] (==) Matched vesa as autoconfigured driver 4 [ 16.476] (==) Assigned the driver to the xf86ConfigLayout [ 16.476] (II) LoadModule: "via" [ 16.484] (WW) Warning, couldn't open module via [ 16.484] (II) UnloadModule: "via" [ 16.484] (EE) Failed to load module "via" (module does not exist, 0) [ 16.484] (II) LoadModule: "openchrome" [ 16.489] (WW) Warning, couldn't open module openchrome [ 16.489] (II) UnloadModule: "openchrome" [ 16.489] (EE) Failed to load module "openchrome" (module does not exist, 0) [ 16.489] (II) LoadModule: "unichrome" [ 16.496] (WW) Warning, couldn't open module unichrome [ 16.496] (II) UnloadModule: "unichrome" [ 16.496] (EE) Failed to load module "unichrome" (module does not exist, 0) [ 16.496] (II) LoadModule: "fbdev" [ 16.498] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so [ 16.498] (II) Module fbdev: vendor="X.Org Foundation" [ 16.498] compiled for 1.9.3, module version = 0.4.2 [ 16.498] ABI class: X.Org Video Driver, version 8.0 [ 16.498] (II) LoadModule: "vesa" [ 16.503] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so [ 16.503] (II) Module vesa: vendor="X.Org Foundation" [ 16.503] compiled for 1.9.3, module version = 2.3.0 [ 16.503] Module class: X.Org Video Driver [ 16.503] ABI class: X.Org Video Driver, version 8.0 [ 16.503] (II) FBDEV: driver for framebuffer: fbdev [ 16.503] (II) VESA: driver for VESA chipsets: vesa [ 16.503] (++) using VT number 7 [ 16.602] (II) Loading sub module "fbdevhw" [ 16.602] (II) LoadModule: "fbdevhw" [ 16.604] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so [ 16.604] (II) Module fbdevhw: vendor="X.Org Foundation" [ 16.604] compiled for 1.9.3, module version = 0.0.2 [ 16.604] ABI class: X.Org Video Driver, version 8.0 [ 16.604] (**) FBDEV(0): claimed PCI slot 1@0:0:0 [ 16.604] (II) FBDEV(0): using default device [ 16.604] (WW) Falling back to old probe method for vesa [ 16.605] (II) FBDEV(0): Creating default Display subsection in Screen section "Default Screen" for depth/fbbpp 16/16 [ 16.605] (==) FBDEV(0): Depth 16, (==) framebuffer bpp 16 [ 16.605] (==) FBDEV(0): RGB weight 565 [ 16.605] (==) FBDEV(0): Default visual is TrueColor [ 16.605] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0) [ 16.605] (II) FBDEV(0): hardware: VESA VGA (video memory: 3072kB) [ 16.605] (II) FBDEV(0): checking modes against framebuffer device... [ 16.605] (II) FBDEV(0): checking modes against monitor... [ 16.605] (--) FBDEV(0): Virtual size is 1024x768 (pitch 1024) [ 16.605] (**) FBDEV(0): Built-in mode "current": 78.7 MHz, 59.9 kHz, 75.7 Hz [ 16.605] (II) FBDEV(0): Modeline "current"x0.0 78.65 1024 1056 1184 1312 768 772 776 792 -hsync -vsync -csync (59.9 kHz) [ 16.605] (==) FBDEV(0): DPI set to (96, 96) [ 16.605] (II) Loading sub module "fb" [ 16.605] (II) LoadModule: "fb" [ 16.605] (II) Loading /usr/lib64/xorg/modules/libfb.so [ 16.605] (II) Module fb: vendor="X.Org Foundation" [ 16.605] compiled for 1.9.3, module version = 1.0.0 [ 16.605] ABI class: X.Org ANSI C Emulation, version 0.4 [ 16.605] (**) FBDEV(0): using shadow framebuffer [ 16.605] (II) Loading sub module "shadow" [ 16.605] (II) LoadModule: "shadow" [ 16.606] (II) Loading /usr/lib64/xorg/modules/libshadow.so [ 16.606] (II) Module shadow: vendor="X.Org Foundation" [ 16.606] compiled for 1.9.3, module version = 1.1.0 [ 16.606] ABI class: X.Org ANSI C Emulation, version 0.4 [ 16.606] (II) UnloadModule: "vesa" [ 16.606] (II) Unloading /usr/lib64/xorg/modules/drivers/vesa_drv.so [ 16.606] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 16.606] (==) FBDEV(0): Backing store disabled [ 16.609] (==) FBDEV(0): DPMS enabled [ 16.609] (==) RandR enabled [ 16.609] (II) Initializing built-in extension Generic Event Extension [ 16.609] (II) Initializing built-in extension SHAPE [ 16.609] (II) Initializing built-in extension MIT-SHM [ 16.609] (II) Initializing built-in extension XInputExtension [ 16.609] (II) Initializing built-in extension XTEST [ 16.609] (II) Initializing built-in extension BIG-REQUESTS [ 16.609] (II) Initializing built-in extension SYNC [ 16.609] (II) Initializing built-in extension XKEYBOARD [ 16.609] (II) Initializing built-in extension XC-MISC [ 16.609] (II) Initializing built-in extension SECURITY [ 16.609] (II) Initializing built-in extension XINERAMA [ 16.609] (II) Initializing built-in extension XFIXES [ 16.609] (II) Initializing built-in extension RENDER [ 16.609] (II) Initializing built-in extension RANDR [ 16.609] (II) Initializing built-in extension COMPOSITE [ 16.609] (II) Initializing built-in extension DAMAGE [ 16.623] (II) AIGLX: Screen 0 is not DRI2 capable [ 16.623] (II) AIGLX: Screen 0 is not DRI capable [ 16.630] (II) AIGLX: Loaded and initialized /usr/lib64/dri/swrast_dri.so [ 16.630] (II) GLX: Initialized DRISWRAST GL provider for screen 0 [ 16.702] (II) XKB: reuse xkmfile /var/lib/xkb/compiled/server-8AA988DD479FAABEC4FC3CCCF4CC29B4948840B4.xkm [ 16.723] (II) config/udev: Adding input device Power Button (/dev/input/event3) [ 16.723] (**) Power Button: Applying InputClass "evdev keyboard catchall" [ 16.723] (**) Power Button: Applying InputClass "LocalKeyboard" [ 16.723] (II) LoadModule: "evdev" [ 16.724] (II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so [ 16.724] (II) Module evdev: vendor="X.Org Foundation" [ 16.724] compiled for 1.9.3, module version = 2.6.0 [ 16.724] Module class: X.Org XInput Driver [ 16.724] ABI class: X.Org XInput driver, version 11.0 [ 16.724] (**) Power Button: always reports core events [ 16.724] (**) Power Button: Device: "/dev/input/event3" [ 16.726] (--) Power Button: Found keys [ 16.726] (II) Power Button: Configuring as keyboard [ 16.726] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD) [ 16.726] (**) Option "xkb_rules" "evdev" [ 16.726] (**) Option "xkb_model" "evdev" [ 16.726] (**) Option "xkb_layout" "us" [ 16.729] (II) XKB: reuse xkmfile /var/lib/xkb/compiled/server-73AC8D4822B76BE375830D90D9DD145B2CBC4E27.xkm [ 16.743] (II) config/udev: Adding input device Power Button (/dev/input/event2) [ 16.743] (**) Power Button: Applying InputClass "evdev keyboard catchall" [ 16.743] (**) Power Button: Applying InputClass "LocalKeyboard" [ 16.743] (**) Power Button: always reports core events [ 16.743] (**) Power Button: Device: "/dev/input/event2" [ 16.745] (--) Power Button: Found keys [ 16.745] (II) Power Button: Configuring as keyboard [ 16.745] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD) [ 16.745] (**) Option "xkb_rules" "evdev" [ 16.745] (**) Option "xkb_model" "evdev" [ 16.745] (**) Option "xkb_layout" "us" [ 16.758] (II) config/udev: Adding input device HDA VIA VT82xx Headphone (/dev/input/event5) [ 16.758] (II) No input driver/identifier specified (ignoring) [ 16.760] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0) [ 16.760] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall" [ 16.760] (**) AT Translated Set 2 keyboard: Applying InputClass "LocalKeyboard" [ 16.760] (**) AT Translated Set 2 keyboard: always reports core events [ 16.760] (**) AT Translated Set 2 keyboard: Device: "/dev/input/event0" [ 16.764] (--) AT Translated Set 2 keyboard: Found keys [ 16.764] (II) AT Translated Set 2 keyboard: Configuring as keyboard [ 16.764] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD) [ 16.764] (**) Option "xkb_rules" "evdev" [ 16.764] (**) Option "xkb_model" "evdev" [ 16.764] (**) Option "xkb_layout" "us" [ 16.764] (II) config/udev: Adding input device ImPS/2 Logitech Wheel Mouse (/dev/input/event1) [ 16.764] (**) ImPS/2 Logitech Wheel Mouse: Applying InputClass "evdev pointer catchall" [ 16.764] (**) ImPS/2 Logitech Wheel Mouse: always reports core events [ 16.764] (**) ImPS/2 Logitech Wheel Mouse: Device: "/dev/input/event1" [ 16.766] (--) ImPS/2 Logitech Wheel Mouse: Found 3 mouse buttons [ 16.766] (--) ImPS/2 Logitech Wheel Mouse: Found scroll wheel(s) [ 16.766] (--) ImPS/2 Logitech Wheel Mouse: Found relative axes [ 16.766] (--) ImPS/2 Logitech Wheel Mouse: Found x and y relative axes [ 16.766] (II) ImPS/2 Logitech Wheel Mouse: Configuring as mouse [ 16.766] (II) ImPS/2 Logitech Wheel Mouse: Adding scrollwheel support [ 16.766] (**) ImPS/2 Logitech Wheel Mouse: YAxisMapping: buttons 4 and 5 [ 16.766] (**) ImPS/2 Logitech Wheel Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 [ 16.766] (II) XINPUT: Adding extended input device "ImPS/2 Logitech Wheel Mouse" (type: MOUSE) [ 16.766] (**) ImPS/2 Logitech Wheel Mouse: (accel) keeping acceleration scheme 1 [ 16.766] (**) ImPS/2 Logitech Wheel Mouse: (accel) acceleration profile 0 [ 16.766] (**) ImPS/2 Logitech Wheel Mouse: (accel) acceleration factor: 2.000 [ 16.766] (**) ImPS/2 Logitech Wheel Mouse: (accel) acceleration threshold: 4 [ 16.766] (II) ImPS/2 Logitech Wheel Mouse: initialized for relative axes. [ 16.766] (II) config/udev: Adding input device ImPS/2 Logitech Wheel Mouse (/dev/input/mouse0) [ 16.766] (II) No input driver/identifier specified (ignoring) [ 16.767] (II) config/udev: Adding input device PC Speaker (/dev/input/event4) [ 16.767] (II) No input driver/identifier specified (ignoring) [ 16.790] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 16.873] (II) XKB: reuse xkmfile /var/lib/xkb/compiled/server-C37DE65A5B365D52A52EC1F2CB656087341C7EF8.xkm [ 17.470] (II) XKB: reuse xkmfile /var/lib/xkb/compiled/server-C37DE65A5B365D52A52EC1F2CB656087341C7EF8.xkm [ 21.305] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 21.305] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 1170.831] (II) XKB: reuse xkmfile /var/lib/xkb/compiled/server-D242F26DFBAACE09E168B7878D504C947F077525.xkm [ 5350.870] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 5350.870] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 5350.875] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 5650.875] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 5650.875] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 5735.036] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 5735.037] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 6560.172] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 6560.172] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 6560.177] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 6860.177] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 6860.178] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 7160.173] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 7160.173] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 7751.963] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 7751.964] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 9590.547] (II) Open ACPI successful (/var/run/acpid.socket) [ 9590.719] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 9598.956] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 11341.833] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 11341.833] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 11341.851] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 11469.792] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 11469.792] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 11492.992] (II) Open ACPI successful (/var/run/acpid.socket) [ 11493.028] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 11498.146] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 12562.586] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 12562.586] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 12562.592] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 12862.592] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 12862.592] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 13162.586] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 13162.587] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 13805.681] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 13805.681] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 13892.560] (II) Open ACPI successful (/var/run/acpid.socket) [ 13892.566] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 13896.127] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by vesafb of Linux Kernel) [ 15309.938] (II) XKB: reuse xkmfile /var/lib/xkb/compiled/server-D242F26DFBAACE09E168B7878D504C947F077525.xkm -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2011/07/29 08:24 (GMT+0800) George Olson composed:
lspci | grep VGA gave me the following: 01:00.0 VGA compatible controller: VIA Technologies, Inc. K8M890CE/K8N890CE [Chrome 9] (rev 11)
I googled and found 2 drivers that say they support my chip, but I am not quite sure if they are Linux compatible drivers. Under the OS description on the driver download page, it says "probably all". Here are the names of the drivers - assuming that I looked everything up correctly: VIA K8M890CE/K8N890CE Display Driver 21. VIA K8M890CE& K8N890CE Display Driver
Those could both be found from the following website: http://downloadnew.org/software/k8m890-linux-drivers/
NAICT those are proprietary drivers. They may provide better performance than the FOSS driver, which you should try first, since it's easier to install....
[ 16.476] (==) Matched via as autoconfigured driver 0 [ 16.476] (==) Matched openchrome as autoconfigured driver 1 [ 16.476] (==) Matched unichrome as autoconfigured driver 2 [ 16.476] (==) Matched fbdev as autoconfigured driver 3 [ 16.476] (==) Matched vesa as autoconfigured driver 4 [ 16.476] (==) Assigned the driver to the xf86ConfigLayout [ 16.476] (II) LoadModule: "via" [ 16.484] (WW) Warning, couldn't open module via [ 16.484] (II) UnloadModule: "via" [ 16.484] (EE) Failed to load module "via" (module does not exist, 0) [ 16.484] (II) LoadModule: "openchrome" [ 16.489] (WW) Warning, couldn't open module openchrome [ 16.489] (II) UnloadModule: "openchrome" [ 16.489] (EE) Failed to load module "openchrome" (module does not exist, 0) [ 16.489] (II) LoadModule: "unichrome" [ 16.496] (WW) Warning, couldn't open module unichrome [ 16.496] (II) UnloadModule: "unichrome" [ 16.496] (EE) Failed to load module "unichrome" (module does not exist, 0) [ 16.496] (II) LoadModule: "fbdev" [ 16.498] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so [ 16.498] (II) Module fbdev: vendor="X.Org Foundation" [ 16.498] compiled for 1.9.3, module version = 0.4.2 [ 16.498] ABI class: X.Org Video Driver, version 8.0 [ 16.498] (II) LoadModule: "vesa" [ 16.503] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so [ 16.503] (II) Module vesa: vendor="X.Org Foundation" [ 16.503] compiled for 1.9.3, module version = 2.3.0 [ 16.503] Module class: X.Org Video Driver [ 16.503] ABI class: X.Org Video Driver, version 8.0 [ 16.503] (II) FBDEV: driver for framebuffer: fbdev [ 16.503] (II) VESA: driver for VESA chipsets: vesa
All the above says you're running on generic (fbdev/vesa) drivers, which do not support 1600x900, and that the FOSS unichrome driver that your gfxchip probably requires (when was that motherboard made?) was not found. So, before anything else, do as I suggested 11/07/27 17:09 -0400: "...'zypper in xorg-x11-driver-video-unichrome' as root and restarting X or rebooting may actually be all you need..." If that driver package is _already_ installed (which rpm, zypper and yast2 all can in each's own way tell you), it may be that X is not automagically finding it, and so may need unichrome specified as driver in /etc/X11/xorg.conf.d/50-device.conf. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 07/29/2011 09:36 AM, Felix Miata wrote:
On 2011/07/29 08:24 (GMT+0800) George Olson composed:
lspci | grep VGA gave me the following: 01:00.0 VGA compatible controller: VIA Technologies, Inc. K8M890CE/K8N890CE [Chrome 9] (rev 11)
I googled and found 2 drivers that say they support my chip, but I am not quite sure if they are Linux compatible drivers. Under the OS description on the driver download page, it says "probably all". Here are the names of the drivers - assuming that I looked everything up correctly: VIA K8M890CE/K8N890CE Display Driver 21. VIA K8M890CE& K8N890CE Display Driver
Those could both be found from the following website: http://downloadnew.org/software/k8m890-linux-drivers/
NAICT those are proprietary drivers. They may provide better performance than the FOSS driver, which you should try first, since it's easier to install....
[ 16.476] (==) Matched via as autoconfigured driver 0 [ 16.476] (==) Matched openchrome as autoconfigured driver 1 [ 16.476] (==) Matched unichrome as autoconfigured driver 2 [ 16.476] (==) Matched fbdev as autoconfigured driver 3 [ 16.476] (==) Matched vesa as autoconfigured driver 4 [ 16.476] (==) Assigned the driver to the xf86ConfigLayout [ 16.476] (II) LoadModule: "via" [ 16.484] (WW) Warning, couldn't open module via [ 16.484] (II) UnloadModule: "via" [ 16.484] (EE) Failed to load module "via" (module does not exist, 0) [ 16.484] (II) LoadModule: "openchrome" [ 16.489] (WW) Warning, couldn't open module openchrome [ 16.489] (II) UnloadModule: "openchrome" [ 16.489] (EE) Failed to load module "openchrome" (module does not exist, 0) [ 16.489] (II) LoadModule: "unichrome" [ 16.496] (WW) Warning, couldn't open module unichrome [ 16.496] (II) UnloadModule: "unichrome" [ 16.496] (EE) Failed to load module "unichrome" (module does not exist, 0) [ 16.496] (II) LoadModule: "fbdev" [ 16.498] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so [ 16.498] (II) Module fbdev: vendor="X.Org Foundation" [ 16.498] compiled for 1.9.3, module version = 0.4.2 [ 16.498] ABI class: X.Org Video Driver, version 8.0 [ 16.498] (II) LoadModule: "vesa" [ 16.503] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so [ 16.503] (II) Module vesa: vendor="X.Org Foundation" [ 16.503] compiled for 1.9.3, module version = 2.3.0 [ 16.503] Module class: X.Org Video Driver [ 16.503] ABI class: X.Org Video Driver, version 8.0 [ 16.503] (II) FBDEV: driver for framebuffer: fbdev [ 16.503] (II) VESA: driver for VESA chipsets: vesa
All the above says you're running on generic (fbdev/vesa) drivers, which do not support 1600x900, and that the FOSS unichrome driver that your gfxchip probably requires (when was that motherboard made?) was not found. So, before anything else, do as I suggested 11/07/27 17:09 -0400:
"...'zypper in xorg-x11-driver-video-unichrome' as root and restarting X or rebooting may actually be all you need..."
If that driver package is _already_ installed (which rpm, zypper and yast2 all can in each's own way tell you), it may be that X is not automagically finding it, and so may need unichrome specified as driver in /etc/X11/xorg.conf.d/50-device.conf. Great!! That is what did it! Thanks for your help - I learned a lot in making this work!
George -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2011/07/29 10:16 (GMT+0800) George Olson composed:
"...'zypper in xorg-x11-driver-video-unichrome' as root and restarting X or rebooting may actually be all you need..."
If that driver package is _already_ installed (which rpm, zypper and yast2 all can in each's own way tell you), it may be that X is not automagically finding it, and so may need unichrome specified as driver in /etc/X11/xorg.conf.d/50-device.conf.
Great!! That is what did it!
Which, installing driver, or modifying 50-device.conf? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 07/29/2011 10:19 AM, Felix Miata wrote:
On 2011/07/29 10:16 (GMT+0800) George Olson composed:
"...'zypper in xorg-x11-driver-video-unichrome' as root and restarting X or rebooting may actually be all you need..."
If that driver package is _already_ installed (which rpm, zypper and yast2 all can in each's own way tell you), it may be that X is not automagically finding it, and so may need unichrome specified as driver in /etc/X11/xorg.conf.d/50-device.conf.
Great!! That is what did it!
Which, installing driver, or modifying 50-device.conf? Installing the driver. Once I did that and re-booted, the screen was configured correctly in 1600x900.
By the way, what does it mean when you say "X is not automatically finding it"? I have read things like this, and things like "restarting X". What does it mean to "restart X" and what is the difference between doing that and doing a complete reboot? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2011/07/29 10:25 (GMT+0800) George Olson composed:
Felix Miata wrote:
Which, installing driver, or modifying 50-device.conf?
Installing the driver. Once I did that and re-booted, the screen was configured correctly in 1600x900.
By the way, what does it mean when you say "X is not automatically finding it"? I have read things like this, and things like "restarting X". What does it mean to "restart X" and what is the difference between doing that and doing a complete reboot?
Generally speaking, the only time rebooting is necessary to implement an update in any Linux distro is when the update is a kernel, which in those many other cases means faster implementation. Everything else, at least in theory, can be implemented via a service restart, often by dropping to a lower runlevel[1], then returning to the former one. Rebooting is often simpler than figuring out which service(s) need a restart, but not X. X restart can be done via root login on a tty by 'init 3; init 5' or 'rcxdm restart' in rpm distros like openSUSE. In openSUSE last I checked (I haven't since full automagicifcation in 11.3), an X configuration change will be implemented simply by logging out, which performs an X restart automatically, unlike e.g. Mandriva, which keeps the same xdm session running on log out. [1] http://en.wikipedia.org/wiki/Runlevel#SUSE_Linux -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 07/29/2011 10:19 AM, Felix Miata wrote:
On 2011/07/29 10:16 (GMT+0800) George Olson composed:
"...'zypper in xorg-x11-driver-video-unichrome' as root and restarting X or rebooting may actually be all you need..."
If that driver package is _already_ installed (which rpm, zypper and yast2 all can in each's own way tell you), it may be that X is not automagically finding it, and so may need unichrome specified as driver in /etc/X11/xorg.conf.d/50-device.conf.
Great!! That is what did it!
Which, installing driver, or modifying 50-device.conf? Maybe I spoke too soon. The resolution is good now, but now that I am using it, it seems that 3d is not working on my monitor. windows are slow to shrink down and kind of jerk along the way sometimes.
"If that driver package is _already_ installed (which rpm, zypper and yast2 all can in each's own way tell you), it may be that X is not automagically finding it, and so may need unichrome specified as driver in /etc/X11/xorg.conf.d/50-device.conf." how do I specify unichrome as driver, and will that necessarily fix the problem with 3d? Do I just put the word "unichrome" in place of "radeon" and take away the comment line in the 50-device.conf file? Here is a copy of my 50-device.conf file: Section "Device" Identifier "Default Device" #Driver "radeon" ## Required magic for radeon/radeonhd drivers; output name ## (here: "DVI-0") can be figured out via 'xrandr -q' #Option "monitor-DVI-0" "Default Monitor" EndSection -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
< snip>
how do I specify unichrome as driver, and will that necessarily fix the problem with 3d? Do I just put the word "unichrome" in place of "radeon" and take away the comment line in the 50-device.conf file?
Here is a copy of my 50-device.conf file:
Section "Device" Identifier "Default Device"
#Driver "radeon"
## Required magic for radeon/radeonhd drivers; output name ## (here: "DVI-0") can be figured out via 'xrandr -q' #Option "monitor-DVI-0" "Default Monitor"
EndSection
Yes, if unichrome is the driver name, replace radeon with it (keeping quotes), and removing the comment #. Since the behavior has changed, I would double-check to see which driver is actually being loaded and with what parameters. Do an lsmod as root, you should see the kernel driver name in the list. And look at /var/log/Xorg.0.log for what X is actually doing with the driver. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 07/29/2011 07:02 PM, dwgallien wrote:
< snip>
how do I specify unichrome as driver, and will that necessarily fix the problem with 3d? Do I just put the word "unichrome" in place of "radeon" and take away the comment line in the 50-device.conf file?
Here is a copy of my 50-device.conf file:
Section "Device" Identifier "Default Device"
#Driver "radeon"
## Required magic for radeon/radeonhd drivers; output name ## (here: "DVI-0") can be figured out via 'xrandr -q' #Option "monitor-DVI-0" "Default Monitor"
EndSection
Yes, if unichrome is the driver name, replace radeon with it (keeping quotes), and removing the comment #.
Since the behavior has changed, I would double-check to see which driver is actually being loaded and with what parameters. Do an lsmod as root, you should see the kernel driver name in the list. And look at /var/log/Xorg.0.log for what X is actually doing with the driver. Please educate me: It looks like both the # and the ## are comments. If that's so, then what's the difference, and why? If that's not so, then what kind of notation is it, and what does it mean? Thanx--doug
-- Blessed are the peacemakers...for they shall be shot at from both sides. --A. M. Greeley -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2011/07/29 19:21 (GMT-0400) Doug composed:
Here is a copy of my 50-device.conf file:
Section "Device" Identifier "Default Device" #Driver "radeon" ## Required magic for radeon/radeonhd drivers; output name ## (here: "DVI-0") can be figured out via 'xrandr -q' #Option "monitor-DVI-0" "Default Monitor" EndSection
Please educate me: It looks like both the # and the ## are comments. If that's so, then what's the difference, and why? If that's not so, then what kind of notation is it, and what does it mean?
If you remove one instance of "#" from each line containing any instances, you get a file that specifies the radeon driver be used for the DVI-0 output. IOW, ## is for real comments, while # is for example configuration lines. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
< snip>
how do I specify unichrome as driver, and will that necessarily fix the problem with 3d? Do I just put the word "unichrome" in place of "radeon" and take away the comment line in the 50-device.conf file?
Here is a copy of my 50-device.conf file:
Section "Device" Identifier "Default Device"
#Driver "radeon"
## Required magic for radeon/radeonhd drivers; output name ## (here: "DVI-0") can be figured out via 'xrandr -q' #Option "monitor-DVI-0" "Default Monitor"
EndSection
Yes, if unichrome is the driver name, replace radeon with it (keeping quotes), and removing the comment #.
Since the behavior has changed, I would double-check to see which driver is actually being loaded and with what parameters. Do an lsmod as root, you should see the kernel driver name in the list. And look at /var/log/Xorg.0.log for what X is actually doing with the driver. Ok, how do I open the 50-device.conf file in kwrite as root so that I can edit and save it? I can't remember how to open up kwrite with root
On 07/30/2011 07:02 AM, dwgallien wrote: privileges. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2011/07/30 07:51 (GMT+0800) George Olson composed:
Yes, if unichrome is the driver name, replace radeon with it (keeping quotes), and removing the comment #.
Since the behavior has changed, I would double-check to see which driver is actually being loaded and with what parameters. Do an lsmod as root, you should see the kernel driver name in the list. And look at /var/log/Xorg.0.log for what X is actually doing with the driver.
Ok, how do I open the 50-device.conf file in kwrite as root so that I can edit and save it? I can't remember how to open up kwrite with root privileges.
Back up. Look in Xorg.0.log. If there are not already numerous lines that include UNICHROME, only then might specifying unichrome as the driver in 50-monitor.conf serve any purpose. A lot of UNICHROME lines in Xorg.0.log means it's already being used. If you need to modify that file, kwrite is not the only way. I never use kwrite to modify config files. I open MC after logging in as root in Konsole or on a tty. Going to a tty first also facilitates X restarting to initiate the configuration change. IOW, first log out of KDE, then log in as root, then open MC, with which you navigate to /etc/X11/xorg.conf.d/ and use MC's internal editor to make the change, then restart X. I suspect your 3D problem is that the FOSS unichrome driver simply doesn't support 3D well on your gfxchip. If true, it means you need VIA's proprietary driver for 3D to work OK. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 07/29/2011 08:03 PM, Felix Miata wrote:
On 2011/07/30 07:51 (GMT+0800) George Olson composed:
/snip/
Ok, how do I open the 50-device.conf file in kwrite as root so that I can edit and save it? I can't remember how to open up kwrite with root privileges.
Back up. Look in Xorg.0.log. If there are not already numerous lines that include UNICHROME, only then might specifying unichrome as the driver in 50-monitor.conf serve any purpose. A lot of UNICHROME lines in Xorg.0.log means it's already being used.
If you need to modify that file, kwrite is not the only way. I never use kwrite to modify config files. I open MC after logging in as root in Konsole or on a tty. Going to a tty first also facilitates X restarting to initiate the configuration change. IOW, first log out of KDE, then log in as root, then open MC, with which you navigate to /etc/X11/xorg.conf.d/ and use MC's internal editor to make the change, then restart X. /snip/
This seems unnecessarily complicated. Open konsole. Find the directory that the .conf file is in and change to it. Before doing anything else, (no matter how you edit the file,) either use sudo, or su root if you don't have sudo, then cp 50-device.conf 50-device.conf.bak. That will save the existing version in case you screw up. Then do nano -m 50-device.conf and edit the file. When you have done, do ctrl+x, then y then ENTER. If you were using su root, type exit. (If opensuse doesn't have nano, then it must have pico. They work exactly the same, for all practical purposes.) Now you may have to reboot to let the system recognize the change. --doug -- Blessed are the peacemakers...for they shall be shot at from both sides. --A. M. Greeley -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2011/07/29 20:46 (GMT-0400) Doug composed:
Felix Miata wrote:
If you need to modify that file, kwrite is not the only way. I never use kwrite to modify config files. I open MC after logging in as root in Konsole or on a tty. Going to a tty first also facilitates X restarting to initiate the configuration change. IOW, first log out of KDE, then log in as root, then open MC, with which you navigate to /etc/X11/xorg.conf.d/ and use MC's internal editor to make the change, then restart X.
This seems unnecessarily complicated.
Takes me all of 8 seconds to do, including making the backup of 50-device.conf.
Open konsole. Find the directory
MC can be opened in Konsole, but since X will have to be restarted to institute the config file change anyway, might as well just log out to start with. Once logged in as root, everything necessary is in place without messing with sudo or su.
that the .conf file is in and change to it. Before doing anything else, (no matter how you edit the file,) either use sudo, or su root if you don't have sudo, then cp 50-device.conf 50-device.conf.bak.
In MC, shift-F3, end, ., b, a, k, enter. IOW, lots fewer keystrokes to make the backup.
That will save the existing version in case you screw up. Then do nano -m 50-device.conf and edit the file. When you have done,
In MC, highlight the file to be edited, F4. IOW, lots fewer keystrokes.
do ctrl+x, then y then ENTER. If you were using su root, type exit. (If
No need to quit the session before you know the change(s) made got the job done. do 'init 3; init 5', and KDM will be restarted.
Now you may have to reboot to let the system recognize the change.
No need to waste time rebooting when changing X configuration. X is an application. It doesn't need a reboot to be restarted. Linux is not Windows. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday, July 30, 2011 01:46:28 PM James Knott wrote:
George Olson wrote:
I can't remember how to open up kwrite with root privileges.
Su - to root and then run KWrite.
kdesu or gnomesu are necessary for graphic applications. Otherwise application will produce error about missing display. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday, July 28, 2011 08:36:21 PM Felix Miata wrote:
Those could both be found from the following website: http://downloadnew.org/software/k8m890-linux-drivers/
NAICT those are proprietary drivers. They may provide better performance than the FOSS driver, which you should try first, since it's easier to install....
Those are windows drivers and comment about supported operating system "Probably All" means any Widows version, which can be correct only if zip file contains few drivers. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (8)
-
auxsvr＠gmail.com -
C -
Doug -
dwgallien -
Felix Miata -
George Olson -
James Knott -
Rajko M.