I m new in linux.
My agp is onboard chrome9 hc igp on P4M900.
In graphics card and monitor in yast my card is ‘Vesa Frame buffer Graphics’ and monitor is ‘sam samsung syncmaster’.
At very first time when I install opensuse11 i could change my display resolution from 800x600 to 1024x768 and color from 16 bit to 24 bit. That was fine.
But for some reason i formated those drive. And then i install suse again but i cannt change my display resolution and color. It remains 800x600 and 16bit.
I installed suse several time but i can not manage to change it.
I cant remember when but some how 1 time i can managed to run my display from xgl from etc/sysconfig Editor.(It might be the first time when i could change res. & color.)
But now if i change xorg to xgl my display does not run. In the startup it says ‘x server can not run’ or something like this. And it try to fix the problem and i gave my password but it cant fix it.
I need to change the resolution.
>
> I m new in linux.
> My agp is onboard chrome9 hc igp on P4M900.
>
> In graphics card and monitor in yast my card is ‘Vesa Frame buffer
> Graphics’ and monitor is ‘sam samsung syncmaster’.
>
> At very first time when I install opensuse11 i could change my display
> resolution from 800x600 to 1024x768 and color from 16 bit to 24 bit.
> That was fine.
>
> But for some reason i formated those drive. And then i install suse
> again but i cannt change my display resolution and color. It remains
> 800x600 and 16bit.
> I installed suse several time but i can not manage to change it.
>
> I cant remember when but some how 1 time i can managed to run my
> display from xgl from etc/sysconfig Editor.(It might be the first time
> when i could change res. & color.)
> But now if i change xorg to xgl my display does not run. In the
> startup it says ‘x server can not run’ or something like this. And it
> try to fix the problem and i gave my password but it cant fix it.
> I need to change the resolution.
>
> Any idea?
>
> Plz Help.
>
> Sorry for my english.
>
>
Hi
Have a look here about adding modelines to your xorg.conf file; http://en.opensuse.org/VIA
–
Cheers Malcolm °¿° (Linux Counter #276890)
SLED 10 SP2 i586 Kernel 2.6.16.60-0.25-default
up 11:38, 1 user, load average: 1.05, 0.39, 0.29
GPU GeForce Go 6600 TE/6200 TE Version: 173.14.09
I have a VIA Chrome9 HC IGP running with very very very poor performances when watching a movie at fullscreen mode. Seems that there is no graphic acceleration at all (but works perfectly under Windows XP).
I have found the driver-repository that you reported, but what about your instructions?
init 3
sax2 -r 0:chrome9
Where I must write that commands? In which configuration file? :\
Those commands are intended for a terminal, run with root permissions.
Saying “init 3” is something only average to advanced Linux users will understand.
There are various run levels in Linux which define the various states a Linux system can boot to, from single user text mode, to multple user text mode with and without networking, to a full scale GUI. I tried to explain these concepts in a wiki I started (and others made much better) here: Concepts - openSUSE
The init process is associated with controlling the level in which one boots, and “init 3” is a command that can be used some cases to force the operation system to change to run level 3.
sax2 is a program (that is being depreciated) for openSUSE that in the past was used to create an /etc/X11/xorg.conf file, where that file governed part of the graphic configuration for X windows. That file used to be compulsary, but as of openSUSE-11.2 its not necessary for all systems, but is necessary for some. I supect that file may be necessary for your system, and hence you will need to run sax2 with appropriate arguments.
I recommend you simply boot your PC to run level 3 (do this by typing “3” (no quotes) in the initial grub boot menu that lets you choose linux, linux safe, windows, … etc … so that “3” (no quotes) appears in the options line) and login into the full screen text mode as a regular user. Then type “su” ( no quotes - enter root password) to switch users to root, and then type:
sax2 -r 0:chrome9
I confess I’ve never used that specific syntax. If it had been me I would have tried:
“Chip: 0 is -> VIA VT3336: K8M890 01:00:0 0x1106 0x3230 AGP via”
So, seems that the right video card is recognized and the command “sax2 -r -m 0=chrome9” could work.
I will try it… I hope that my Linux will not crash like Win…:X does!
In particular, if you read post #33, you will see there are
xorg-x11-driver-video-unichrome
rpm - comes with openSUSE-11.2 and contains a “unichrome” and a “via” driver. That rpm is also available from x11:xorg (possibly a newer/more-cutting-edge/risky packaged version) ? I do not know.
xorg-x11-driver-video-viachrome
rpm - in the build service by a user (illuusio) - it contains only a “via” driver. Is this the same as the via in the xorg-x11-driver-video-unichrome? I do not know.
xorg-x11-driver-video-openchrome
rpm - packaged by a couple of users in OBS (illuusio and Max1) and contains an “openchrome” driver. I do not know anything about it.
xorg-x11-driver-chrome9
rpm - packaged in x11:driversVideo and contains a “via” driver. Is this the same as the above ‘via’ or different ? I do not know.
… as to which one is correct for you, I can not say.
Note, one can search for rpms (with drivers) using the openSUSE rpm search engines
Good luck. Don’t forget there may also be (with a different rpm) “via”, “openchrome” , “unichrome” drivers in addition to the “vesa” and “fbdev” drivers.
So opposed to “sax2 -r -m 0=chrome9” , you could also try (with the appropriate rpm installed as noted above):
sax2 -r -m 0=fbdev #basic frame buffer driver
sax2 -r -m 0=vesa #generic vesa driver
sax2 -r -m 0=via #via driver
sax2 -r -m 0=openchrome #openchrome driver
sax2 -r -m 0=unichrome #unichrome driver
ensuring 1st you have the correct rpm installed.
But thats just me looking at the rpm contents and speculating. We really need someone who has thoroughly explored the chrome driver availability to provide comments on each of the available drivers.
… and unfortunately none of our chrome experts have tested all those combinations and then have written about it succinctly (in the threads that I have participated in).
I have no god news… the command “sax2 -r -m 0=chrome9” doesn’t works, it terminates with an error.:’(
This is what i see in the last lines of the /var/log/SaX.log file:
(II) LoadModule: "chrome9"
(WW) Warning, couldn't open module chrome9
(II) UnloadModule: "chrome9"
(EE) Failed to load module "chrome9" (module does not exist, 0)
(EE) No drivers available.
Fatal server error:
no screens found
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
Seems that the “chrome9” module does not exists at all… where I’m wrong? :
The driver package is correctly installed… (Yast says that)
Some words about different drivers available. First, the name of the driver xorg-x11-driver-chrome9 is wrong, right is xorg-x11-driver-video-chrome9. Second, I have choosed that driver only 'cause my chipset (K8M890CE) is explicitally listed in the driver description. So I think that anybody must choose the driver that is matching with his chipset. I don’t know if the “unichrome” driver works, but I will try and I will tell you results.
By the way the command “shutdown -a now” (entered as super-user) doesn’t turn-off the PC. As result the PC prompt me again for the SU password and then nothings happens. When I was young (lol!) I remember that such command turn-off the PC. I’m confused… :\
You did nothing wrong, except follow a post that suggested that that the driver is called ‘chrome9’. It is NOT. The rpm has chrome9 in its name, but I believe inside that rpm is a driver called “via”.
unfortunately the suggested command doesn’t work. Sax2 cannot found the module name “via_chrome9”. I don’t know why it added “_chrome9” as suffix, I have used only the name “via”…:disapointed:
FATAL: Module via_chrome9 not found.
[drm] failed to load kernel module "via_chrome9"
(EE) [drm] drmOpen failed.
(EE) VIA(0): [dri] DRIScreenInit failed. Disabling DRI.
(II) VIA(0): VIAModeInit
(II) VIA(0): VIASetDisplayPath is DuoView
(WW) VIA(0): Refresh rate setting in xorg.conf is not supported!!
(WW) VIA(0): Driver will try to find another refresh rate instead.
(II) VIA(0): into 3D initial...3Dinitial? 0
(II) VIA(0): H5 3D Engine has been initilized.
(II) VIA(0): VIAInternalScreenInit
Backtrace:
0: /usr/sbin/xw(xorg_backtrace+0x37) [0x81396c7]
1: /usr/sbin/xw(xf86SigHandler+0xa0) [0x80cf7c0]
2: [0xffffe400]
3: /usr/sbin/xw(miScreenInit+0x4c) [0x8126f8c]
4: /usr/lib/xorg/modules//libfb.so(fbFinishScreenInit+0x14a) [0xb6ea4c3a]
5: /usr/lib/xorg/modules//libfb.so(fbScreenInit+0xa2) [0xb6ea4f52]
6: /usr/lib/xorg/modules//drivers/via_drv.so [0xb7279a94]
7: /usr/sbin/xw(AddScreen+0x1a9) [0x80716d9]
8: /usr/sbin/xw(InitOutput+0x743) [0x80b1333]
9: /usr/sbin/xw(main+0x1cb) [0x8071dbb]
10: /lib/libc.so.6(__libc_start_main+0xfe) [0xb7446ace]
11: /usr/sbin/xw [0x8071451]
Fatal server error:
Caught signal 8. Server aborting
I tried again, and I confirm you that the sax2 -r -m 0=via append the suffix “_chrome9” as module name (??).
I tried the command sax2 -r -m 0=unichrome9 too, but it doesn’t work… output is a little bit different but the result is the same “cannot load the module (FATAL ERROR)”…
I have investigated in the unichrome rpm file and seems that my chipset (VIA K8M890) is supported.
This is the Mesa version that comes with openSUSE-11.2 from the OSS repos.
Both the xorg-x11-driver-video-chrome9 and the xorg-x11-driver-video-unichrome provide a ‘via’ graphic kernel module (driver) so its not clear to me at all what driver is being configured when you try to run “sax2 -r -m 0=via”.
I think you should remove xorg-x11-driver-video-chrome9-5.74.33-2.1.i586 as long as you have the xorg-x11-driver-video-unichrome from OSS repos. If you want to use the xorg-x11-driver-video-chrome9-5.74.33-2.1.i586 you may need to remove the xorg-x11-driver-video-unichrome.
When removing, its probably best to remove both chrome9 and unichrome, and then re-install the rpm you want to use.
Note the xorg-x11-driver-video-unichrome-20091020-1.1.1.i586, which provides both a “via” kernel module and a “unichrome” module while the xorg-x11-driver-chrome9 provides only a “via” module.
… hence with unichrome rpm you could try:
sax2 -r -m 0=via
and if that fails
sax2 -r -m 0=unichrome
… or you could reverse the order and remove the unichrome and install the chrome9 rpm and try again:
and try the xorg-x11-driver-video-unichrome-20091117-1.1.i586.rpm from there.
and finally, if none of the above works, you could replace
xorg-x11-driver-video, xorg-x11-driver-input, xorg-x11-driver-video-chrome9, xorg-x11-driver-video-unichrome with the same rpms, but different versions, from here:
thanks, now is a little bit late for me. I must sleep. Tomorrow I will remove chrome9 and unichrome rpm both and after I will install them separately. And I will try the commands that you wrote.
Hi
I don’t have your exact chip, but a Via unichrome pro IGP (K8M800). I have used all the drivers at various stages of their development since the time of suse 10.1 (missing out 11.0) up to and including 11.2. BTW the user who recommended chrome9 gave you an 11.0 repo for it, and it probably worked ok then. In fact I was using it last year on my 11.1 and possibly 11.2 test system. However the chrome9 driver does not work now on my system. I installed it from the OBS where there is only one version available for 11.2, and I assume that is the version you downloaded, right?
The change log for chrome9 makes me immediately suspicious. At the end of Nov 2009 the driver module name changed from “chrome9” to “via” although the package is still called chrome9. Well that’s an opportunity for some other necessary change to have been overlooked. I’ve seen that in the distant past on other distros when all the diifferent driver modules had to be called “via” because the Xorg driver they were replacing was called “via”, and some packager used the wrong naming. The last change to chrome9 in January says that the driver will no longer be installed by default on Via h/w. Hmm, I wonder why not?
I changed my xorg.conf to point to “via” for the chrome9 driver to load, and on rebooting it failed, and dumped me in the console, failed to start X and no KDE login screen. I wouldn’t waste any more time on that driver, clearly the devs don’t expect it to work or didn’t bother to test it properly.
The “unichrome” driver is 2D only and I don’t believe it supports anything older than my chip (K8M800), so it will not support your K8M890. IMO you shouldn’t bother with it.
That leaves primarily the “openchrome” driver which has been the most consistent one I have used since suse 10.1 and on other distros. It claims to support K8M890 for 2D acceleration, but 3D acceleration is not working properly yet. It should easily outperform the “fbdev” driver which is notoriously slow and heavy on resources. The last alternative you could try is the “vesa” driver, which should perform better than fbdev, but you can’t configure refresh rates at different resolutions so it may not work well with your particular monitor.
My recommendation is that you remove unichrome completely, and chrome9 (wait for a new version to try). Then install “openchrome” from the build service for 11.2, supplied by user: illuusio, that is the one I am using now. Once installed you can read the man page for “openchrome” and how to configure it in xorg.conf. You can learn all about the openchrome driver and it’s development at their website here.
I don’t recommend you try “xorg-x11-driver-video-viachrome rpm - in the build service by user: illuusio)” as mentioned by oldcpu. I haven’t, and I believe the repo notes there give a warning about it.
