freezes with 3D applications on VIA Unichrome K8M800, KM400

[xanmoo]

For some days now, my acer 1362LMI (sempron 2800+) can start with the via driver for K8M800.(xserver-xorg-driver-via 33.2 ubuntu4)

However most of the application using opengl (mesa) freeze the computer . This is the case with :
egoboo
tuxracer
some screen savers
torcs

openuniverse and xcompmgr/transset are ok.

I configured the video with dpkg reconfigure xserver-xorg with or without framebuffer, and I chose 16bits as color depth. I tested two kernels 2.6.15.21-i386 and 2.6.15.22-k7 with the same result.

glxgears yields around 700 FPS (16bits + Kernel K7)

I can play dvd smoothly

[lspci]
00:00.0 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
01:00.0 VGA compatible controller: VIA Technologies, Inc. S3 Unichrome Pro VGA Adapter (rev 01)

[E-val (e-val)]

Created an attachment (id=3841)
Trivial workaround

A trivial workaround for unichrome DRI module which allows you to run Trigger
but not other games.

[E-val (e-val)]

The situation appears to be more complicated than I thought initially. I've did
additional debugging and now think that all games are suffering from the same
bug in a driver - the symptoms are quite similar. However, there are many ways
to "activate" this bug, so every game (or GL app in general) has it's own
workaround. For instance, in Trigger you should avoid GL_LINEAR_MIPMAP_LINEAR,
in Torcs you should disable GL_ALPHA_TEST when rendering multitextures (it is
always connected with textures somehow) and so on. Usually, the program hangs
between return statement and the next line of code, i.e. in the sample code below:

int some_func() {
  ...
  printf("BEFORE\n");
  return 1;
}
...
while (some_func) {
  printf("AFTER\n");
}

you will see "BEFORE" line but not "AFTER".

So, I've prepared a very simple demo program (see attachement) below which hangs
my computer. Hope it will help debugging driver. More details are in attachment
comments.

[E-val (e-val)]

Created an attachment (id=4010)
Demo program

This small program is suffering from the described bug. It should display two
rotating triangles (blue and white) but it hangs instead. I've made a program
intentionally simple (no real textures - just autogenerated plain color, no GLU
calls for mipmapping etc) so it has minimum GL calls. To make the program work,
one should either change mipmapping mode or render texture on both triangles.
You will find the comments on which line to remove/modify inside the file. The
bug is highly reproducable with this program but in rare cases you may need to
run the program several times before it hang the computer.

[Gregor-pirnaver (gregor-pirnaver)]

I have the same problem on K8M800. I ran attached demo program and compter
locks up if this line is not commented out:
glDisable(GL_TEXTURE_2D);

Commenting out this line or not doesn't seem to manke any difference:
glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER,
GL_NEAREST_MIPMAP_LINEAR);

I'm running Mandriva Linux 2006 (32bit) with thac&ze
xorg-x11-6.9.0+openchrome+mesa-6.5.0+dkms-drm RPMs:
http://www.mde.djura.org/2006.0/RPMS/

[plord (peter-plord)]

This issue appears to be hitting me as well. The demo program behaves as
described, plus I get a lockup with geartrain and some of the other demos. Note
the gears works fine ( 450 fps ).

I'm using Mesa 6.5 ( downloaded from mesa3d.org ), xorg 7.0 ( xorg-server
1.0.2-r3 from gentoo ) and the openchrome ( http://openchrome.org/ ) driver. I
have a K8M800 chipset and am running on a x86_64 notebook.

I've built mesa 6.5 with debug enabled and set LD_LIBRARY_PATH to point to the
libs in my build tree. I see the following on the command line :-

  bash$ ./geartrain
  __driCreateNewScreen_20050727 - succeeded
  Mesa warning: couldn't open libtxc_dxtn.so, software DXTn
compression/decompression unavailable

The initial geartrain window appears and then the display is locked. Sometimes,
the whole machine is locked up.

Please advise if there is anything I can do to aid debugging this further.

[xanmoo (jeanpat-pommier)]

For some days now, my acer 1362LMI (sempron 2800+) can start with the via driver for K8M800.(xserver-xorg-driver-via 33.2 ubuntu4)

However most of the application using opengl (mesa) freeze the computer . This is the case with :
egoboo
tuxracer
some screen savers
torcs

openuniverse and xcompmgr/transset are ok.

I configured the video with dpkg reconfigure xserver-xorg with or without framebuffer, and I chose 16bits as color depth. I tested two kernels 2.6.15.21-i386 and 2.6.15.22-k7 with the same result.

glxgears yields around 700 FPS (16bits + Kernel K7)

I can play dvd smoothly

[Vytas (vytas)]

What happens when it freezes? If it is only Xorg lockup, try pressing Alt+F1. Does it help? How often does it freeze, every time you run the mentioned programs, or just sometimes? at the launch time, or after use?

I had issues with my Xorg locking up after prolonged and extensive 3D usage, but it was hardware related (Windows responded with a reboot at the same use cases), most probably that was overheating

[xanmoo (jeanpat-pommier)]

The keyboard does not answer (no Alt F1, can't restart gdm too).
It freezes every time I try to start one of the mentionned applications.

[Tomy Weber (tomy)]

I have the same problem on my MSI K8MM-V motherboard with the VIA K8M800 UnichromePro graphics chip -- planetpenquin-racer (aka tuxracer) starts but freezes the computer at the beginning of the race but the sound continues. Ctrl-Alt-Fx does nothing and I am forced to power down.

I also have a MSI KM4AM-V motherboard with the VIA KM400 Unichrome graphics chip. This works fine using the same "via" driver in xorg.conf.

Both computers have a fresh install of dapper beta2.

[xanmoo (jeanpat-pommier)]

see that thread
http://wiki.openchrome.org/pipermail/openchrome-users/2006-May/001203.html

[Tomy Weber (tomy)]

The discouraging sentence in that thread is:
">Thomas said that the unichrome part of Mesa is unmaintained. :( "

This bug causes computers with the UnichromePro graphics chip to randomly freeze if Ubuntu Dapper Drake is installed.

Why? Because Dapper Drake is set (by default) to randomly choose a screen saver and several of the screen savers freeze the computer solid. You must power down. Several times I have had corrupted disk space because of this bug.

Nobody is working on this?? It has been six months since this bug was reported.

Could I pay someone to fix this???

Tomy

I am an end-user not a developer. If I knew how to fix this I would certainly help.

[Andy (shadowfirebird)]

I have the same problem. <https://launchpad.net/distros/ubuntu/+bug/57062>

Can anyone tell me what the chances are of this getting looked at?

[Gaurish Sharma (gslive)]

well i think this a serious problem and needs more info to fix the bug.

[Gaurish Sharma (gslive)]

well i am also unsing this chipset and faceing the same problem. so i am pretty sure this bug report is right!.well we need to repair it fast.

[Jonathan Kyle Mitchell (kmitch87-deactivatedaccount)]

This problem is also very similar to bug #62093

[Jonathan Kyle Mitchell (kmitch87-deactivatedaccount)]

To simplify things for the Ubuntu bug team, I have marked bug #62093 and bug #57062 as duplicates of this report.

[Nick_Hill (nick-nickhill)]

I now have what appears to be the same problem with Wine on Edgy.

See bug #68761

It appears Wine now uses 3d, and we will start to see 3d calls in classpath.

I think the bug importance should be escalated. The bug also has security and data integrity implications as this can be used by a userspace program to cause DOS.

[Surricani (surricani)]

I can confirm.

I have a ASUS ASPIRE 1360LM laptop with a Via Unichrome Pro IGP.

The video card is a K8M800 and works very well with 2d applications like photo, web, email, video, ecc...

The problem is when I run 3d applications...

Tha systems freeze and I can'd to anything. No alt+FX, no ssh... nothing!

I can only reboot pressing the power button per some seconds.

I have this problem since Ubuntu Dapper Drake. Now I have Ubuntu Edgy and It's the same.

I've seen this strage kernel messages when I switch from virtual consoles to X:

irq 185: nobody cared (try booting with the "irqpoll" option)
 <c0139a14> __report_bad_irq+0x24/0x80 <c01745bd> touch_atime+0x5d/0xb0
 <c0139aef> note_interrupt+0x7f/0x240 <c0139383> handle_IRQ_event+0x33/0x60
 <c0139483> __do_IRQ+0xd3/0x100 <c0105169> do_IRQ+0x19/0x30
 <c010361e> common_interrupt+0x1a/0x20
handlers:
[<c022ba60>] (via_driver_irq_handler+0x0/0x1c0)
Disabling IRQ #185
irq 185: nobody cared (try booting with the "irqpoll" option)
 <c0139a14> __report_bad_irq+0x24/0x80 <c0139aef> note_interrupt+0x7f/0x240
 <c0139383> handle_IRQ_event+0x33/0x60 <c0139483> __do_IRQ+0xd3/0x100
 <c0105169> do_IRQ+0x19/0x30 <c010361e> common_interrupt+0x1a/0x20
 <c0101aca> default_idle+0x2a/0x60 <c0101b3c> cpu_idle+0x3c/0x60
 <c04486ce> start_kernel+0x26e/0x320 <c0448210> unknown_bootoption+0x0/0x250
handlers:
[<c022ba60>] (via_driver_irq_handler+0x0/0x1c0)
Disabling IRQ #185

I hope this can be useful...

[xanmoo (jeanpat-pommier)]

Same problem.

What should we do ? Protesting at http://forums.viaarena.com/categories.aspx?catid=28&entercat=y

until via decides to release informations to produce a good driver?

[xanmoo (jeanpat-pommier)]

I forget to mention that the bug happens under edgy running on an acer 1362LMI K8M800 laptop

[DominikBodi (dominik-bodi)]

*** Bug 7456 has been marked as a duplicate of this bug. ***

[DominikBodi (dominik-bodi)]

Surricani: Your problem with the lost IRQ probably has nothing to do with this bug report. Please check out https://wiki.ubuntu.com/DebuggingIRQProblems
and, if necessary, file a separate bug.

For all the others: It would be helpful if you could have a look at https://wiki.ubuntu.com/TriagingXBugs and https://wiki.ubuntu.com/DebuggingXAutoconfiguration and post your logfiles here. Thanks in advance.

[Surricani (surricani)]

Thanks for the information about IRQ problems... but the problems (about irq) persist. I know, this is another story/bug...

Also the lockup for 3d applications persist.

So, all work fine. 2d is very good... But when I run 3d application the screen become black and the system freeze. I can only press the power button for some seconds and reboot the system. No alt+Fx or remote connection works. It seems that all system stop.

I can't give you a dump or detailed log because I have to reboot the system and nothing is saved.

But I can give you the following information:

lspci

00:00.0 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.1 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.2 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.3 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.4 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:00.7 Host bridge: VIA Technologies, Inc. K8M800 Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South]
00:0b.0 CardBus bridge: Texas Instruments PCI7420 CardBus Controller
00:0b.1 CardBus bridge: Texas Instruments PCI7420 CardBus Controller
00:0b.2 FireWire (IEEE 1394): Texas Instruments PCI7x20 1394a-2000 OHCI Two-Port PHY/Link-Layer Controller
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
00:11.6 Communication controller: VIA Technologies, Inc. AC'97 Modem Controller (rev 80)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:00.0 VGA compatible controller: VIA Technologies, Inc. S3 Unichrome Pro VGA Adapter (rev 01)

lspci -n:

00:00.0 0600: 1106:0204
00:00.1 0600: 1106:1204
00:00.2 0600: 1106:2204
00:00.3 0600: 1106:3204
00:00.4 0600: 1106:4204
00:00.7 0600: 1106:7204
00:01.0 0604: 1106:b188
00:0b.0 0607: 104c:ac8e
00:0b.1 0607: 104c:ac8e
00:0b.2 0c00: 104c:802e
00:10.0 0c03: 1106:3038 (rev 80)
00:10.1 0c03: 1106:3038 (rev 80)
00:10.2 0c03: 1106:3038 (rev 80)
00:10.3 0c03: 1106:3104 (rev 82)
00:11.0 0601: 1106:3177
00:11.1 0101: 1106:0571 (rev 06)
00:11.5 0401: 1106:3059 (rev 50)
00:11.6 0780: 1106:3068 (rev 80)
00:12.0 0200: 1106:3065 (rev 74)
00:18.0 0600: 1022:1100
00:18.1 0600: 1022:1101
00:18.2 0600: 1022:1102
00:18.3 0600: 1022:1103
01:00.0 0300: 110...

[DominikBodi (dominik-bodi)]

the interrupt problem might be worked around with by using the "irqpoll" kernel command line option. I'll do some research on freedesktop.org bugzilla.

[DominikBodi (dominik-bodi)]

Thanks for the additional info. Judging the bug reports I found at freedesktop.org, I think we can safely confirm this bug. It seems the lost interrupts might have something to do with it actually.

Unfortunately, there doesn't seem to be much activity there. According to the comments at https://bugs.freedesktop.org/show_bug.cgi?id=7456 this seems to be a well-known problem. Unfortunately, the comments also claim nobody's actively maintaining the via unichrome driver at the moment.

As a workaround, you could always use the vesa driver instead of the via one. That would prevent the lock-ups. However, opengl performance would suffer when using the vesa driver.

Btw, you can also paste your logfiles and debug output snippets into files and use the "attach file" option. That makes the comments a wee bit more readable.

Regards, Dominik

[Nick_Hill (nick-nickhill)]

Ubuntu bug:
https://launchpad.net/distros/ubuntu/+source/xserver-xorg-video-via/+bug/43154

Which has 3 bugs, has been associated with this bug.
affecting: Screensavers, Wine (windows non-emulator) with any application,
Games, Potentially classpath when 3D enabled.

[Surricani (surricani)]

I can confirm that the IRQ problem is related to the via driver, because when i set the string

Option "DisableIRQ" "true"

in the xorg.conf the kernel message go away.

[ahaslam (anthonyhaslam)]

Is anyone on this problem?

[Georg Duffner (mcduff)]

there is the openchrome project which provides opensource-drivers for the via chipsets (http://www.openchrome.org/). they know about these problems but developement seems quite slow over there.

[Surricani (surricani)]

I have always problems. No 3d with edgy end VIA K8M800

2007/2/13, Georg Duffner <email address hidden>:
> there is the openchrome project which provides opensource-drivers for
> the via chipsets (http://www.openchrome.org/). they know about these
> problems but developement seems quite slow over there.
>
> --
> computer freezes with some applications using 3D
> https://launchpad.net/bugs/43154
>

[ahaslam (anthonyhaslam)]

I've been using the openchrome svn for some time, the problem still persists. Of course this is apparent under every Distro, but this seems to be the only place where such a large number of users have confirmed the issue. I suppose my question should have been, 'are the Ubuntu dev's planning to help, or are we hoping that mesa becomes maintained?'

Tony.

[Andy (shadowfirebird)]

I've come to the conclusion that the sensible solution is to buy a new graphics card.

For those with laptops I accept that that is not much help.

But it does not appear to me that anyone is actively working to fix this problem.

[Martin Fischer (martin-fischer)]

Thats a big Problem, because in Austria ( and possibly in lot more Country's) Computers sold as Linux PC(!) with Asus K8V-MX Motherboard and Mandriva Linux.

People who want to change the Platform and buy an esp chilliGREEN Experience that can't handle 3D will never come back.

[Timo Aaltonen (tjaalton)]

Can you try with Feisty Herd5?

[Timo Aaltonen (tjaalton)]

Raising severity so that this stands out from the rest of the bugs.

[Timo Aaltonen (tjaalton)]

Please someone test Feisty beta?

[Surricani (surricani)]

I've tested it one hour ago...

Same results... :-(

2007/3/25, Timo Aaltonen <email address hidden>:
> Please someone test Feisty beta?
>
> ** Changed in: xserver-xorg-video-via (Ubuntu)
> Status: Confirmed => Needs Info
>
> --
> computer freezes with some applications using 3D
> https://launchpad.net/bugs/43154
>

[Gaurish Sharma (gslive)]

Is this bug fixed in Feisty?

[Surricani (surricani)]

I don't think.

I tried the beta release but the problem persist.

2007/3/30, gary4gar <email address hidden>:
> Is this bug fixed in Feisty?
>
> --
> computer freezes with some applications using 3D
> https://launchpad.net/bugs/43154
>

[Gaurish Sharma (gslive)]

then why the status is changed to
** Changed in: Ubuntu
      Status: Confirmed => Rejected

** Changed in: xorg (Ubuntu)
      Status: Confirmed => Rejected

On 3/30/07, Surricani <email address hidden> wrote:
>
> I don't think.
>
> I tried the beta release but the problem persist.
>
> 2007/3/30, gary4gar <email address hidden>:
> > Is this bug fixed in Feisty?
> >
> > --
> > computer freezes with some applications using 3D
> > https://launchpad.net/bugs/43154
> >
>
> --
> computer freezes with some applications using 3D
> https://launchpad.net/bugs/43154
>

--
Regards,
Gaurish Sharma

[Timo Aaltonen (tjaalton)]

because the bug was added to many bogus components, which I closed. xserver-xorg-video-via is left.

[Georg Duffner (mcduff)]

i can confirm that this bug persists in feisty. setting xserver-xorg-video-via to confirmed

[xanmoo (jeanpat-pommier)]

Is there someone working on the via driver at x.org?
 I remember that I read that the driver was not maintained and it seems to be still the case:

http://xorg.freedesktop.org/wiki/via?highlight=%28via%29

[Timo Aaltonen (tjaalton)]

Please test a new version for Feisty at:

http://users.tkk.fi/~tjaalton/dpkg

this is the unichrome-driver.

[Joao SANSAO (jsansao)]

just tested the unichrome-driver, in feisty, and it also has the freezing problem, as I tried to open supertuxkart to test. It lasted up a little longer, in comparison with the previous one. But it did crash anyway.

In addition, in normal graphics, color gradients aren't rendered smoothly, even in 24 bits. However, under 16 bit resolution, it did look better.

[Gaurish Sharma (gslive)]

As the next realese date closing in
the big question
will we able to fix this bug on time?

On 4/3/07, Joao SANSAO <email address hidden> wrote:
>
> just tested the unichrome-driver, in feisty, and it also has the
> freezing problem, as I tried to open supertuxkart to test. It lasted up
> a little longer, in comparison with the previous one. But it did crash
> anyway.
>
> In addition, in normal graphics, color gradients aren't rendered
> smoothly, even in 24 bits. However, under 16 bit resolution, it did look
> better.
>
> --
> computer freezes with some applications using 3D
> https://bugs.launchpad.net/bugs/43154
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Regards,
Gaurish Sharma

[Timo Aaltonen (tjaalton)]

Did you test my package, or the one that is in feisty now?

[Joao SANSAO (jsansao)]

your package, I downloaded it, and did:

$ dpkg-source -x xserver-xorg-video-unichrome_0.2.6.99-0ubuntu1.dsc
$ cd xserver-xorg-video-unichrome-0.2.6.99
$ sudo dpkg-buildpackage

Then it builded the package. I tried to install it, but it had conflict problem with the via driver. So I removed the via driver and just did:
$sudo dpkg -i xserver-xorg-video-unichrome*.deb

Then it installed correctly. But it did freeze with apps like supertuxkart.

 I've the same acer 1362lmi of others, with K8M800.

[Julia (julia-whalespout)]

I have related problems with a VIA K8N800 on my Acer Aspire 1522 laptop. I can't get a fully functioning driver in Ubuntu, Kubuntu, or SUSE. I've tried Edgy and Feisty in both Ubuntu and Kubuntu. I've tried compiling drivers straight from VIA, as well as other Unichrome and Openchrome drivers. This video adapter works flawlessly in Windows, so it's not the hardware.

First I tried like crazy to get an extended desktop going on an external monitor, and finally gave up. Just now I tried to get some applications going in Wine, but received the following error: libGL warning: 3D driver claims to not support visual 0x46

Of course Google Earth doesn't work, or anything else that requires 3D.

We should be aware that this is not really an Ubuntu problem, but a VIA problem. As I understand it, VIA doesn't release fully functional drivers for Linux, nor apparently do they release the necessary information for others to do so. Perhaps they would respond with enough pressure from users, but I don't know.

Perhaps something could move forward at Openchrome?

If anybody knows of any progress on this, or has gotten any response from someone who might help, would you post here? Since I can't use Linux to get my work done, and can't afford a different computer, I'm headed back to Windows - for now.

[Gaurish Sharma (gslive)]

whats the current status of the bug?
has it has been fixed on 7.04
is someone working of its fix & its just left idle
its going to be a year since the bug was last reported

                      Bug #43154, first reported on 2006-05-05 by
xanmoo<https://bugs.launchpad.net/%7Ejeanpat-pommier>

On 4/4/07, Julia <email address hidden> wrote:
>
> I have related problems with a VIA K8N800 on my Acer Aspire 1522
> laptop. I can't get a fully functioning driver in Ubuntu, Kubuntu, or
> SUSE. I've tried Edgy and Feisty in both Ubuntu and Kubuntu. I've
> tried compiling drivers straight from VIA, as well as other Unichrome
> and Openchrome drivers. This video adapter works flawlessly in Windows,
> so it's not the hardware.
>
> First I tried like crazy to get an extended desktop going on an external
> monitor, and finally gave up. Just now I tried to get some applications
> going in Wine, but received the following error: libGL warning: 3D
> driver claims to not support visual 0x46
>
> Of course Google Earth doesn't work, or anything else that requires 3D.
>
> We should be aware that this is not really an Ubuntu problem, but a VIA
> problem. As I understand it, VIA doesn't release fully functional
> drivers for Linux, nor apparently do they release the necessary
> information for others to do so. Perhaps they would respond with enough
> pressure from users, but I don't know.
>
> Perhaps something could move forward at Openchrome?
>
> If anybody knows of any progress on this, or has gotten any response
> from someone who might help, would you post here? Since I can't use
> Linux to get my work done, and can't afford a different computer, I'm
> headed back to Windows - for now.
>
> --
> computer freezes with some applications using 3D
> https://bugs.launchpad.net/bugs/43154
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Regards,
Gaurish Sharma

[Surricani (surricani)]

The problem persist.

No 3d with this video card and any Linux distribution.

I've installed Feisty Fawn (the released, not beta) and I had same problems.

I've had the IRQ problem and freeze on 3d applications.

The IRQ problems goes away adding "DisableIRQ" "true" in xorg.conf but the 3d freeze persist.

I have an Acer Aspire 1362LM with via k8n800.

[Surricani (surricani)]

I forget to include this new kernel "error":

[84694.924000] agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
[84694.924000] agpgart: Xorg tried to set rate=x12. Setting to AGP3 x8 mode.
[84694.924000] agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode
[84694.924000] agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode
[84694.932000] [drm:via_mem_alloc] *ERROR* Attempt to allocate from uninitialized memory manager.

[telek (theodore-mcdougal-logan)]

Just wanted to say I have a Via Epia CLE266/M10000 motherboard and have run into the same on gentoo.

As such I have a few observations that may or may not help:
The issue appears to have started after upgrading to libdrm-2.3.0 from libdrm-2.0.2 or earlier.
x11-drm module dated 20060608 works for 2d, however after running one XV window, say under mplayer, the second segfaults the X server. OpenGL programs like Quake3 work fine fullscreen, although windowed GL apps like secondlife create artifacting outside of their window (offset down and to the right by about 1/4 of the image size.

x11-drm 20070314 is actually worse, xdm when started doesn't show the text boxes on the login page, although actual username and password typing works. Once in a windowmanager initial xterms will show up, but rather than having their text window visible they 'show through' to the desktop, which stays checkerboarded and doesn't load any background images. Furthermore exiting/CTRL-ALT-BKSPing the X session causes a hard lock when the next X server attempts to initialize.

Given these issues I'm reverted to libdrm-2.0.2 to determine if that solves my issues, and if not, also reverted to the 2005 era via drm modules. If both these solutions fail then I'll have run out of details I changed between when 3d/Xv was working fine, and now.

Best of luck to the rest of you and hopefully some developers can be found who'd be willing to look into the issue.

[NoWhereMan (e.vacchi) (uncommonnonsense)]

on a VIA mainboard I found that using acpi=force irqpoll corrects a lot of problems; btw the Mesa driver is not maintained and there's no kernel parameter to fix such an issue :( I wanted compiz :'(

[xanmoo (jeanpat-pommier)]

by another computer :-(

[narr (todespudel-1-deactivatedaccount)]

I'm not sure if I got the same problem:
Everything worked fine until Feisty.
My card is a KM400 and since Feisty I get complete freezes (but the mouse cursor is still moveable) when i run ANY 3d related application. Even a simple glxinfo freezes the system.
I don't find any error messages in the logs and i can start the X-Server with via specified in the xorg.conf but as soon as 3D is required the fun is over.

I solved this problem for me by downgrading libgl1-mesa-glx and libgl1-mesa-dri from 6.5.2-3ubuntu7 (Feisty) to 6.5.1~20060817-0ubuntu3 (Edgy).

My card has never worked by default, even if Ubuntu recognizes it in the installation process (which it does since Edgy, I guess).
Additional options which I have always needed to get it working are:
 Option "VBEModes" "true"
 Option "DisableIRQ"
 Option "EnableAGPDMA"

[Xavier Guillot (valeryan-24)]

Hello,

I also have the same problem since I upgraded to Feisty (re-installation) : sometimes, when I watch a video with Videolan, Ubuntu totally freezes, nothing works more (mouse, keyboard...), the only solution is to reboot with reset button.

My computer : CPU Athlon 64 4000 / Motherboard ASUS A8N-SLI SE / Graphic Card ATI Radeon X1300

All the remaining works fine, except this freeze.

[Bryce Harrington (bryce)]

Another similar freeze with 3D apps on Unichrome has been reported with the KM400, which I assume is this same bug: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/118163

The user was able to workaround it by downgrading from mesa 6.5.2 to 6.5.1.

[xanmoo (jeanpat-pommier)]

I don't think that the freezes you meet is related to the Via GPU since you have an ATI.

by the way, I send this post on Via forum

http://forums.viaarena.com/messageview.aspx?catid=28&threadid=78349&highlight_key=y&keyword1=k8M800

even if it is absolutly not usefull.

[Surricani (surricani)]

Well done.

Also my next computer will not have VIA Chips...

2007/6/18, xanmoo <email address hidden>:
> I don't think that the freezes you meet is related to the Via GPU since
> you have an ATI.
>
> by the way, I send this post on Via forum
>
> http://forums.viaarena.com/messageview.aspx?catid=28&threadid=78349&highlight_key=y&keyword1=k8M800
>
> even if it is absolutly not usefull.
>
> --
> freezes with 3D applications on VIA Unichrome K8M800, KM400
> https://bugs.launchpad.net/bugs/43154
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[NoWhereMan (e.vacchi) (uncommonnonsense)]

I totally agree

[Shankargiri (shankargiri)]

(In reply to comment #2)
> The situation appears to be more complicated than I thought initially. I've did
> additional debugging and now think that all games are suffering from the same
> bug in a driver - the symptoms are quite similar. However, there are many ways
> to "activate" this bug, so every game (or GL app in general) has it's own
> workaround. For instance, in Trigger you should avoid GL_LINEAR_MIPMAP_LINEAR,
> in Torcs you should disable GL_ALPHA_TEST when rendering multitextures (it is
> always connected with textures somehow) and so on. Usually, the program hangs
> between return statement and the next line of code, i.e. in the sample code below:
>
> int some_func() {
> ...
> printf("BEFORE\n");
> return 1;
> }
> ...
> while (some_func) {
> printf("AFTER\n");
> }
>
> you will see "BEFORE" line but not "AFTER".
>
> So, I've prepared a very simple demo program (see attachement) below which hangs
> my computer. Hope it will help debugging driver. More details are in attachment
> comments.

I looked into this a bit more and I infer the following. I realise that you looked at the bug in terms of high-level errors at the mesa DRI code. I however, went lower than that to the exact root cause. My observations may be different from yours, but here I go.
1. Debugging into this using gdb caused a hard lock in the glFlush() portion of glx code, which in turn goes to the __mesa_Flush() in unichrome_dri.so. The locking happens at different points of the code and therefore I figured that it is an asynchronous event driven code that is causing this lock.
2. I finally went into the DRM portion of the code(libdrm) which ioctl's the kernel for running various kernel level code from user space.
3. Adding printk's to DRM code finally isolated the problem. There is a function in via_irq.c called via_driver_vblank_wait(), which is probably serviced when the VIA_IRQ_VBLANK_PENDING interrupt bit is set. It calls viadrv_acknowledge_irqs().
4. This reads the VIA_INTERRUPTS_REG using the VIA_READ macro(which is a readl PCI post), 'or' it with the VIA_IRQ_VBLANK_PENDING bit. QUESTION: If it is interrupt driven, this bit should already be set. Why is it being set during acknowledge? Then it writes the VIA_INTERRUPTS_REG back using VIA_WRITE.
5. Looking at the sequence of printk's I see that VIA_READ and VIA_WRITE happens several times and that at one point VIA_READ simply locks.

Observations:

1. Since this locking is happening in a mmio PCI Posting, it probably means there is some bus arbitration problems(memory space must be mapped to agpgart). So is the bug in agpgart? Or is there something in the hardware that says you cannot read and write to HW registers using PCI posts continuously and maybe you should introduce gaps or delays between READ's and WRITE's?
2. Since the hw is mmio, I would imagine that PCI posting(reading and writing together) although non-blocking would be properly handled by the bus aribitration queue. It would be a great help if we had the manufacturer specs. This is wierder because it happens only to a few via chipsets(Unichrome Pro B).
3. I think it must be related to certain HW timing differences between the chipsets....

[E-val (e-val)]

(In reply to comment #9)
First of all, thank you for the information: very nice job! I suspected it's something to deal with VBLANK IRQ - and now we know this for sure. This lock-up is often connected to timing issues in wikis so this partially support your conclusion. Unfortunately, I know a little about low-level hardware programming and can't imagine how to fix it but I'm sure the maintainer of this DRI driver (when it'll have one) would be be able to use your data to fix the problem.

[Shankargiri (shankargiri)]

(In reply to comment #10)
> (In reply to comment #9)
> First of all, thank you for the information: very nice job! I suspected it's
> something to deal with VBLANK IRQ - and now we know this for sure. This lock-up
> is often connected to timing issues in wikis so this partially support your
> conclusion. Unfortunately, I know a little about low-level hardware programming
> and can't imagine how to fix it but I'm sure the maintainer of this DRI driver
> (when it'll have one) would be be able to use your data to fix the problem.
>

Thank you. It just occured to me that this could be in some way related to [Bug 8641] New: interrupts not properly handled for VIA K8M00 / UniChrome Pro. This bug has to do with setting and clearing of interrupts not working properly. And according to description, rewriting the status register does not clear the interrupt. And the kernel disables the IRQ too. So just maybe, if someone fixes this, our bug could be fixed too!

Just a thought.

[E-val (e-val)]

> It just occured to me that this could be in some way related to [Bug
8641] New: interrupts not properly handled for VIA K8M00 / UniChrome Pro.

It probably has something to do with it, but what's the bug number and/or Bugzilla where it was reported? Looking for #8641 in this Bugzilla leads to closed one: "xcb should provide (and use in generated C files) opcode defines."

[E-val (e-val)]

(In reply to comment #12)

> It probably has something to do with it, but what's the bug number and/or
> Bugzilla where it was reported? Looking for #8641 in this Bugzilla leads to
> closed one: "xcb should provide (and use in generated C files) opcode defines."

I found it - it's in the kernel Bugzilla: http://<email address hidden>/msg31026.html

These problems look like being connected for me. I'm not a kernel hacker (although I've read both Linux Kernel Development, 2nd Edition and Understanding Linux Kernel ;-) but if you'd need someone with real hardware to help debugging, I'm ready to do this job.

[Shankargiri (shankargiri)]

(In reply to comment #13)
> (In reply to comment #12)
>
> > It probably has something to do with it, but what's the bug number and/or
> > Bugzilla where it was reported? Looking for #8641 in this Bugzilla leads to
> > closed one: "xcb should provide (and use in generated C files) opcode defines."
>
> I found it - it's in the kernel Bugzilla:
> http://<email address hidden>/msg31026.html
>
> These problems look like being connected for me. I'm not a kernel hacker
> (although I've read both Linux Kernel Development, 2nd Edition and
> Understanding Linux Kernel ;-) but if you'd need someone with real hardware to
> help debugging, I'm ready to do this job.
>

Thanks for your offer. We probably would need the real hardware to trigger the same kind of conditions needed to cause this failure. Your dmesg logs should report the error about IRQs as soon as X is loaded. I'm pretty sure we would all see the error message.

I'm not a real kernel hacker either. ;-) It seems to me that if we approach this problem from both ends(both bugs) we may stand a better chance of solving this quickly. Although there is still the possiblity that they may entirely be unrelated.

Another thing we can verify is to put printk's in the kernel in exactly the same way I said and run different games and 3d applications and verify that the same root cause persists. If they are the same, we get added confirmation about the root cause.

We can, in the meantime continue working on this in our spare time and hope for a breakthrough quickly. What seems to be the priority to me is to eliminate libGL, libGLX and pinpoint the bug on the kernel DRM code. All my investigations point to it, but it is always good to be more sure. ;-)

[Bryce Harrington (bryce)]

Upstream has traced this to a kernel bug:

http://<email address hidden>/msg31026.html

[Nick_Hill (nick-nickhill)]

I have opened a bounty for this bug:
https://launchpad.net/bounties/nick-hill

(I thought the name field was for my name, not bug name, so my name in the URL!). Anyway, it is open. Anyone welcome to up the stakes!

[Shankargiri (shankargiri)]

Update: http://bugzilla.kernel.org/show_bug.cgi?id=8641
I have submitted a patch to this bug that deals with the IRQ interrupt bug. It seems to work, but sadly, this doesn't solve the lockup issue we face here. Maybe the two are not related. Can someone confirm the patch works?

[E-val (e-val)]

> Update: http://bugzilla.kernel.org/show_bug.cgi?id=8641
> I have submitted a patch to this bug that deals with the IRQ interrupt bug. It
> seems to work, but sadly, this doesn't solve the lockup issue we face here.
> Maybe the two are not related. Can someone confirm the patch works?

Thanks for the information, I'll try to put the patch to work. In the meantime I 've seen no traces of spurious IRQ you've observed in dmesg output, so probably these to issues are really different (although IRQ handler definitely plays a role in both cases ;-).

[Shankargiri (shankargiri)]

I agree. The spurious interrupt issue was specifically for the K8M800 device, that is device id, 3108. So if you do not have this device, then you probably wouldn't see this issue.

[Shankargiri (shankargiri)]

Have an update for this. Please check http://bugzilla.kernel.org/show_bug.cgi?id=8641
(Sometimes the link is not resolved properly. So here it is again without the full url. bugzilla.kernel.org/show_bug.cgi?id=8641

[E-val (e-val)]

(In reply to comment #18)
> Have an update for this. Please check
> http://bugzilla.kernel.org/show_bug.cgi?id=8641
> (Sometimes the link is not resolved properly. So here it is again without the
> full url. bugzilla.kernel.org/show_bug.cgi?id=8641
>

Sound sane to me. Have you seen http://sourceforge.net/docman/display_doc.php?docid=23693&group_id=102048
AFAIK there is noone around with the knowledge of VIA 3D spec so miss and try is the only way.

Isn't it possible to check your conclusions by masking the annoying interrupt on PIC and enabling it, say, 10 times per second via dynamic timer? It's a huge hack but it will show the cause of the starvation (although I'm almost sure it's IRQ).

[E-val (e-val)]

> Sound sane to me.

But the question is: why do we observe random lookups (i.e. one game runs fine second game locks up) if IRQ acknowledge code is incorrect?

[Shankargiri (shankargiri)]

Good question. ;-) I have no answers to that one.

But notice that the bug is not at all random. The bug is fully reproducible each and everytime it happens, and in exactly the same way. Therefore, I can only speculate that in all the offending code, some action is being done in the code that causes a large number of VBLANK's. One operation would be a glFlush I think(which, incidently, seems to be the trigger for the small test case you have written in c). AFAIK it seems to me that a combination of calls that force a lot of VBLANK's seems to be the immediate trigger.

Maybe the way the game uses and clears the texture memory or the way drawing is done on screen is responsible for this. In that case, this speculation makes some sense. Each application has different methods of drawing, texture manipulation etc. So a combination of different methods of calling the DRM handler may be the trigger to this.

But again, your statement is very logical. If the IRQ ACK is not accurate, the interrupts should fire continuously, but it happens under only certain conditions.

Again, note the critical change in behavior. No longer hard lock, but barely responsive. That means something is eating the processor cycles, maybe a sleeping spinlock in a thread or something similar.

We have some work to do! ;-)

[Thomas-tungstengraphics (thomas-tungstengraphics)]

Hi.

The IRQ issue on K8M800 has been around for ages. I'm not saying it can't be fixed (sometimes when my K8M800 has been running for quite some time it will work nicely), but trying to initialize it from scratch it always fails. The reason is that K8M800 fires a huge amount of spurious interrupts.

If irq debug is turned off, the handler slows down the machine considerably trying to handle the interrupts.

The problem is probably a hardware bug. The same problem occurs on certain variants of KM400. I once asked via about it and they claimed that IRQ functionality was never verified on these chips since they didn't do video capture. Hence no use for IRQs in VIAs windows drivers.

The only sane thing to do is to not enable IRQs for these chips.

Regarding the texture lockup issue,
the same code works much better on other chips with the same 3D engine.
It might just be a memory timing issue on K8M800, which means that tracking it down using software can be very difficult.

/Thomas

[Shankargiri (shankargiri)]

Appreciate your comments. You may have saved us a long time in going off in some wrong direction. ;-) As of now, turning IRQ off in the X Driver causes more frequent lockups than before. Even a simple glxinfo is a candidate for this lockup. I know timing problems are hell of a lot difficult to find, but we have no choice. Lacking open specs from the manufacturer, we have to do some blind hit and misses to get it.

Another thing, if it is a memory timing issue, I assume this will lockup during a readl, writel or during writes to some buffers. Maybe, if we can isolate this, we have a better chance to understand what the issue is.

[Kai Springer (kai-springer)]

The problem even still exists in Gutsy Herd 3. Complete freeze when opening one of the 3D screensavers or games like described above.

[Thomas-tungstengraphics (thomas-tungstengraphics)]

It's a little more complicated than that. The Unichromes have an AGP command queue which feeds a "Virtual Queue" in vram. If the lockup occurs during a texture read, it's hard to tell exactly what primitive caused it, because it may be in the middle of reading 2MB of data.

The AGP command queue has never been completely stable, so first thing would be to turn that off. "EnableAGPDMA" to "false" would eliminate AGP-related lockups.

Then the Virtual command queue can also be turned off using a 2D driver option, but I can't remember which ATM.

After that, all command register writes should stall until the device is ready to accept them, which may help tracking this issue down.

/Thomas

[Shankargiri (shankargiri)]

Appreciate that piece of wisdom. :-) Will certainly try as you advise. Will keep posting on progress as and when time permits. Thanks again.

[Gaurish Sharma (gslive)]

how to use fix???

[Bryce Harrington (bryce)]

The upstream fix notice was a false alarm. Sounds like it's still not quite fixed yet.

For details, please see the upstream bug report: https://bugs.freedesktop.org/show_bug.cgi?id=5092

[Gaurish Sharma (gslive)]

Will a fix be ever released??
to me chances look dimmed

On 8/1/07, Bryce Harrington <email address hidden> wrote:
>
> The upstream fix notice was a false alarm. Sounds like it's still not
> quite fixed yet.
>
> For details, please see the upstream bug report:
> https://bugs.freedesktop.org/show_bug.cgi?id=5092
>
> --
> freezes with 3D applications on VIA Unichrome K8M800, KM400
> https://bugs.launchpad.net/bugs/43154
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Regards,
Gaurish Sharma
This email is licensed under http://creativecommons.org/licenses/by-nc/3.0/

[josevillavi85 (josevillavi85)]

I have to confirm that this bug is still present in kubuntu gutsy Herd 4 (system update until 14/08/07)

Videocard: VIA S3 Unichrome Pro VGA Adapter

still hoping this problem is solved.

In the same system with an nvidia card, that problem doesn't exist.

Bye

[Tim Gelvin (timgelvin)]

I'm running the MSI K8T890M2-V/K8M890M2-V with the VIA KT890/K8M890 chipset... keep in mind that this board is 64bit and using Feisty 64bit... I'm having the same problems and with 2D applications... but I'm not using any VIA drivers at all only what Feisty has which is some sort of generic driver for all videos. This is a much more serious problem than VIA realizes.

[mrsuicide (mrsuicide)]

Still in Gusty Herd 5.

Glxgears won't freeze. Glxinfo segfaults. Wine and some other OpenGL applications freeze the system.

I have an builtin VIA Unichrome CLE 266 in my notebook: VIA Technologies, Inc. VT8623 [Apollo CLE266]

[toketin (toketin)]

i've archlinux and kernel 2.6.22-6, i use openchrome driver video, my xorg.conf driver section is this:
Section "Device"
        Identifier "Card0"
        Driver "via"
        Option "DisableIRQ"
        Option "EnableAGPDMA"
        VendorName "All"
        BoardName "All"
EndSection
but if i try to run glxinfo the system freezes and i have to shut down the pc from the button on the case.
I've a video card Via/S3G UniChrome Pro Igp (64 MB) and the motherboard chipset is Via K8M800/K8N800.

[mikko (mikko-)]

I'm not sure if this helps but I attach valgrind and gdb reports from glxinfo.
Is there any way to disable glx in gutsy?? It was possible in Feisty but now in gutsy there's no "module" section in xorg.conf. So I can not comment out "glx"

[Furn (furn101)]

I installed Feisty Fawn this week on my computer. Linux is running on a Gateway MX6425 with ATI radeon 200M video card and i have compiz fusion installed with flgrx. Short time after the screensaver runs, my screen was freezing... no possible ways to defreeze it... must reboot. I now see that i'm not the only one to have or had this problem. I'm a noob so i cant help with technical issues, but whith luck, i think i have resolved my problem. I installed the xscreensaver with the synaptic to be able to use the xscreensaver-demo and configure the screensaver from that application. It's running now for 6 hours and it hasn't freeze. I hope this post can bring glimmer of solution.

[mikko (mikko-)]

I found a solution to disable glx. I add these lins to xorg.xonf, I haven't had any lockups after that. Also wine starts fine.

Section "Module"
        Disable "dri"
        Disable "glx"
EndSection

[mrsuicide (mrsuicide)]

You need only this one: Disable "dri"

You will use software rendering in this case.

[toketin (toketin)]

i've tried to put both disable "dri" and "glx" and only disable "dri" but when i reboot x it doesn't start, because there's an error, the string disable... and i have to re-write in xorg.conf the line Load "dri" in order to make x running.....

[mikko (mikko-)]

Do you use openchrome driver still? I use standard xorg via driver and disabling dri works.
Have you done this:
Section "Module"
        Disable "dri"
EndSection

or:
Section "Module"
        #Load "dri"
EndSection

[NoWhereMan (e.vacchi) (uncommonnonsense)]

if you don't need dri, try using vesa, I see a huge boost in performances with 2d compositing (xfwm4 and xcompmgr)

[toketin (toketin)]

i've tried the via driver now and in xorg.conf changed before in Disable "dri" but the word disable isn't recognized, so i've written #Load "dri" but it doesn't work the 3d, for example if i start googleearth the system freezes

[toketin (toketin)]

now, with the line #Load "dri", when i start googleearth it reboots automatically the gnome session..... and so i've to re-enter in gnome

[donrom (donnyromero)]

hey all...brand new to this, and brand new to linux.... I'm having the same types of problems with my
card... tried almost everything I can think of... latest glxinfo gives me:
name of display: :0.0
do_wait: drmWaitVBlank returned -1, IRQs don't seem to be working correctly.
Try running with LIBGL_THROTTLE_REFRESH and LIBL_SYNC_REFRESH unset.
display: :0 screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.2

glxgears is at around 566 ps

beryl --test-only yields:
Detected xserver : AIGLX

Checking Display :0.0 ...

Checking for XComposite extension : passed (v0.3)
Checking for XDamage extension : passed
Checking for RandR extension : passed
Checking for XSync extension : passed

Checking Screen 0 ...

Checking for GLX_SGIX_fbconfig : passed
Checking for GLX_EXT_texture_from_pixmap : passed
Checking for non power of two texture support : failed

Support for non power of two textures missing

Been up for hours trying to find a fix!!! HELP!!!!!!!!!!!

[xanmoo (jeanpat-pommier)]

Until xorg is debugged there's no hope.

[tech0007 (tech0007)]

Hi all,

I think I'm having the same issue. I have P4 1.5 GHz / ASUS P4V8X-MX board / 256 MB RAM. I don't know if the via driver is right for me. I'm currently using vesa. When I change the driver in xorg.conf from vesa to via, X won't startup. Can somebody pls tell me if i'm using the correct driver for my hardware? Thanks.

@myubuntu:~$ glxinfo
name of display: :0.0
X Error of failed request: BadAlloc (insufficient resources for operation)
  Major opcode of failed request: 142 (GLX)
  Minor opcode of failed request: 3 (X_GLXCreateContext)
  Serial number of failed request: 16
  Current serial number in output stream: 17

@myubuntu:~$ lspci
00:00.0 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
00:00.1 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
00:00.2 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
00:00.3 Host bridge: VIA Technologies, Inc. PT890 Host Bridge
00:00.4 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
00:00.7 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge
00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID Controller (rev 80)
00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 81)
00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge [KT600/K8T800/K8T890 South]
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
00:11.6 Communication controller: VIA Technologies, Inc. AC'97 Modem Controller (rev 80)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78)
01:00.0 VGA compatible controller: VIA Technologies, Inc. UniChrome Pro IGP (rev 01)

[NoWhereMan (e.vacchi) (uncommonnonsense)]

as I said, tech0007 the via driver sucks, if you don't need 3d, stick with vesa

[Gaurish Sharma (gslive)]

better get a second grafix card like nvidia 5200FX @1000 bucks or even less

On 10/7/07, tech0007 <email address hidden> wrote:
>
> Hi all,
>
> I think I'm having the same issue. I have P4 1.5 GHz / ASUS P4V8X-MX
> board / 256 MB RAM. I don't know if the via driver is right for me.
> I'm currently using vesa. When I change the driver in xorg.conf from
> vesa to via, X won't startup. Can somebody pls tell me if i'm using the
> correct driver for my hardware? Thanks.
>
> @myubuntu:~$ glxinfo
> name of display: :0.0
> X Error of failed request: BadAlloc (insufficient resources for
> operation)
> Major opcode of failed request: 142 (GLX)
> Minor opcode of failed request: 3 (X_GLXCreateContext)
> Serial number of failed request: 16
> Current serial number in output stream: 17
>
> @myubuntu:~$ lspci
> 00:00.0 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host
> Bridge
> 00:00.1 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host
> Bridge
> 00:00.2 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host
> Bridge
> 00:00.3 Host bridge: VIA Technologies, Inc. PT890 Host Bridge
> 00:00.4 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host
> Bridge
> 00:00.7 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host
> Bridge
> 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge
> 00:0f.0 RAID bus controller: VIA Technologies, Inc. VIA VT6420 SATA RAID
> Controller (rev 80)
> 00:0f.1 IDE interface: VIA Technologies, Inc.
> VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
> 00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1Controller (rev 81)
> 00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1Controller (rev 81)
> 00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1Controller (rev 81)
> 00:10.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1Controller (rev 81)
> 00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 86)
> 00:11.0 ISA bridge: VIA Technologies, Inc. VT8237 ISA bridge
> [KT600/K8T800/K8T890 South]
> 00:11.5 Multimedia audio controller: VIA Technologies, Inc.
> VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
> 00:11.6 Communication controller: VIA Technologies, Inc. AC'97 Modem
> Controller (rev 80)
> 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev
> 78)
> 01:00.0 VGA compatible controller: VIA Technologies, Inc. UniChrome Pro
> IGP (rev 01)
>
> --
> freezes with 3D applications on VIA Unichrome K8M800, KM400
> https://bugs.launchpad.net/bugs/43154
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Regards,
Gaurish Sharma
This email is licensed under http://creativecommons.org/licenses/by-nc/3.0/

[NoWhereMan (e.vacchi) (uncommonnonsense)]

if I could, I would, but we're talking about a laptop, like most people here.

...by the way I don't have 1000 bucks to spend for a graphic card :D

[Gaurish Sharma (gslive)]

then you stay on VESA or stay away from linux, windows support for unicrome
is far much better than the same in linux:(

  its had been more than a year of reporting this bug still no avail:(

On 10/8/07, NoWhereMan <email address hidden> wrote:
>
> if I could, I would, but we're talking about a laptop, like most people
> here.
>
> ...by the way I don't have 1000 bucks to spend for a graphic card :D
>
> --
> freezes with 3D applications on VIA Unichrome K8M800, KM400
> https://bugs.launchpad.net/bugs/43154
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Regards,
Gaurish Sharma
This email is licensed under http://creativecommons.org/licenses/by-nc/3.0/

[Timo Aaltonen (tjaalton)]

The VIA driver situation is messy, to be honest. Ubuntu has -via, -openchrome and -unichrome. You could try -openchrome which is the latest addition..

[Gaurish Sharma (gslive)]

Is it better than the default factory driver??

On 10/8/07, Timo Aaltonen <email address hidden> wrote:
>
> The VIA driver situation is messy, to be honest. Ubuntu has -via,
> -openchrome and -unichrome. You could try -openchrome which is the
> latest addition..
>
> --
> freezes with 3D applications on VIA Unichrome K8M800, KM400
> https://bugs.launchpad.net/bugs/43154
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Regards,
Gaurish Sharma
This email is licensed under http://creativecommons.org/licenses/by-nc/3.0/

[tech0007 (tech0007)]

HI all,

This bug is still not fixed in Gutsy! Will somebody fix this pleaaaaase!

[Ben Cook2 (sourtooth)]

Check This Out:
http://forums.viaarena.com/messageview.aspx?catid=23&threadid=65862&enterthread=y
Apparently This Chipset Hates Direct X As Well....
So:
Windoze Users Only Have OpenGL ( Most Games Are DirectX )
Linux Users Have Only 2D Generic Drivers
This Means That The K8M800 Has MAJOR Issues

[ahaslam (anthonyhaslam)]

Ben, did you look at the date there? It took a while for Via to release decent Windows drivers.

[Gaurish Sharma (gslive)]

Openchrome I last checked is really trying to give max support esp 2D.DRI is
not supported.VIA is opposing to open their specifications for onboard gfx
inspite lot of push.

Let us try to report VIA support problem.it needs someone getting backing
from company like Novell to ask VIA to open their specs.

--
Regards,
Gaurish Sharma
This email is licensed under http://creativecommons.org/licenses/by-nc/3.0/

[Jelle de Jong (jelledejong)]

Hello everybody, I got a lot of messages about freezing and lock-ups on via systems, i solved this by doing the following, please report if this worked:

# step 1: Installation of 368 kernel as a solution for system lockups on system with the VIA CN700 chipset and VIA C7 cpu
sudo apt-get remove libc6-i686
sudo apt-get install linux-image-386

# note 1: Check libc6
sudo dpkg -S libc6-i686
sudo dpkg -l libc6

# step 3: reboot system
sudo reboot

# note 2: Check the kernel version
uname -a

# step 4: Recompile the openchrome driver with the following script and provide some feedback to on the topic:
http://ubuntuforums.org/showthread.php?p=3679548

[Djainette (djainette)]

It seems that openchrome people are the best qualified to deal with this issue. Has anyone already filled a report there ? I couldn't find anything in their forum, but I may have missed it.
http://wiki.openchrome.org/tikiwiki/tiki-forums.php

[Jelle de Jong (jelledejong)]

No, I think they will not agree with this. 3D handled by the mesa project not he 2D openchrome project

[NoWhereMan (e.vacchi) (uncommonnonsense)]

On 11/5/07, Djainette <email address hidden> wrote:
> It seems that openchrome people are the best qualified to deal with this issue. Has anyone already filled a report there ? I couldn't find anything in their forum, but I may have missed it.
> http://wiki.openchrome.org/tikiwiki/tiki-forums.php

 http://wiki.openchrome.org/tikiwiki/tiki-index.php?page=3DStatus

[Djainette (djainette)]

According to this bug ( https://bugs.freedesktop.org/show_bug.cgi?id=5092 ), dri isn't the only component responsible.

[De Jonge (dejonge)]

Hi all, I just wanted to let you all know that I'm glad I finally found this thread. My Linux box has been crashing with 3D stuff so many times... I thought XMoto (2D motocross platform game) was fun to play, but my Linux box kept crashing. Some screen savers also mess things up and wine just keeps giving me errors that no one else had ever heard of. So now I know, it's that North Bridge VIA K8M800 Chipset (UniChrome Pro 3D) that came with my ASRock K8Upgrade-VM800 motherboard. I thought it'd be something like that. By the way, I use Debian GNU/Linux, stable version (but the problem was also present when I used testing). I agree with gary4gar that the best thing for now is to buy a second graphics card like the NVIDIA's GeForce FX 5200 or something. He wrote it's "@1000 bucks or even less", but I think he meant @100, because for example Amazon sells it (eVGA e-GeForce FX 5200 128 MB GPU) for $45.24. http://www.linuxcompatible.org/NV34_GeForce_FX_5200_c12642.html This thread started out with a bug submit on 2006-05-05, that's 1.5 years ago. I think we can all agree that Linux distro's failed here. We are better off just buying an additional video card.

[Djainette (djainette)]

Via recently released a new driver. Did anyone try it ?

[Kai Springer (kai-springer)]

Well, yeah. It's easily installed within a few minutes. Just start the .run file and that's it. Charming. Problem is, it doesn't work. Xorg.log says "wrong VGA bios checksum". I'll attach my xorg.log.

[K|Ke (kike1965)]

installed the driver without any problem.

:)

--
K|Ke
Linux Registered User # 417515

       .--.
      |o_o |
      |:_/ |
     // \ \
    (| | )
   /'\_ _/`\
   \___)=(___/

"ALBEDO: El poder reflectante de un planeta u otro cuerpo no luminoso. Un
reflector perfecto tendría una Albedo de 100%. El Albedo de la Tierra es 39%
ó 0.39."

[ahaslam (anthonyhaslam)]

Kai, it takes more than the .run ;)

I've not tried it yet as that laptop is no longer mine, though I'm sure I'll be trying it soon.
If it works properly, would it be possible to implement in coming Ubuntu releases?

Nice find Djainette ;)

[Gaurish Sharma (gslive)]

anyone tried it on gutsy??
i tried it on hardy alpha 1 but its installer refused to run on 2.6.24
the installer only runs for default gutsy kernel 2.6.22-generic

:-(

[stinke (redhat-tux)]

Same results as Kai.

I used the X-Drivers from one of the binary releases and compiled the drm.ko and via.ko
from the source package.
I commented out the BIOS checksum code but the X-Drivers part of the source
package is impossible to build using the provided build chain. It's a huge mess.

Next notebook is all Intel, thats for sure.

[Gaurish Sharma (gslive)]

Via released a new driver.
Anyone tried it?

[E-val (e-val)]

> Via released a new driver.
> Anyone tried it?
Which one? AFAIK, Via drivers have nothing to do with DRI - please correct me if I'm wrong.

[libv (libv)]

VIA provides only binaries for DRI modules these days, so they should not be considered in the context of this bugreport. We are not even able to find the time to fix bugs in a free dri driver, so feel free to explain how we could support binary only drivers.

[Gaurish Sharma (gslive)]

(In reply to comment #28)
> VIA provides only binaries for DRI modules these days, so they should not be
> considered in the context of this bugreport. We are not even able to find the
> time to fix bugs in a free dri driver, so feel free to explain how we could
> support binary only drivers.
>
[quote]stinke on Ubuntu lauchpad[/quote
Okay, so someone has reported the new release in the
DRI Mailing List [1] and it's been commented.

It doesn't look like Valentine Sinitsyn and Luc Verhaegen
have really had a look at the sources (yet).
From what I can tell everything except the libddmpeg.so
is provided as source code in the package,
contrary to what they are saying.

The only question is if what is provided can resolve the Texture issue
for the K8M800. I've read some very contrary reports in [2]
and the Via Arena forum. OTOH I'm not sure those people
are using this new code at all as it shouldn't even start X
with the VIA BIOS checksum of the K8M800
(or maybe just mine? Can someone verify?).

I'll see this evening If I can compile the X driver without
the checksum check and see what happens.

[E-val (e-val)]

> It doesn't look like Valentine Sinitsyn and Luc Verhaegen
Just to make it clear: I'm only the original bug reporter, not Unichrome-DRI/Unichrome/OpenChrome developer.

> have really had a look at the sources (yet).
> From what I can tell everything except the libddmpeg.so
> is provided as source code in the package,
> contrary to what they are saying.
In fact, I've already skimmed through the code VIA released on Dec, 13th. DRI part looks pretty much like the thing you can find in current Mesa tree (although I haven't done any thorough comparison and if there is a one-liner, I would definitely miss it). The archive is 14 Mb and most of it is precompiled .so libraries for different distros (outdated ones, unfortunately). I was not able to figure out whether they are just compiled sources or contain some proprietary code. It would be really nice if they don't but the release notes are somewhat misleading:

   This software package supports 2D, 3D, TV-Out, hardware video mpeg2/4 and
   hardware video overlay. Aiglx function can be supported on Fedora Core Linux
   6/7, ubuntu Desktop 7.04.Other distributions only support 2D, TV-Out,
   hardware video mpeg2/4 and hardware video overlay.

Distros in the list are among those you can find precompiled .so for.
Anyway, if the code works, it would be really nice. Unfortunately, I'll hardly have an opportunity to test it in the coming days, but if you have some news on the subject (link missed from the previous post would be helpful, too), please let me/us know.

[stinke (redhat-tux)]

> Just to make it clear: I'm only the original bug reporter, not
> Unichrome-DRI/Unichrome/OpenChrome developer.

Right, you're not. It wasn't meant to be offensive. Also not to Luc.
Instead it's good news more people are interested in this release.
Lets hope it's worth it.

Meaning, I'm just about where you are. From the original post on Launchpad:

I used the X-Drivers from one of the binary releases and compiled the drm.ko and via.ko
from the source package.
I commented out the BIOS checksum code but the X-Drivers part of the source
package is impossible to build using the provided build chain. It's a huge mess.

I'm working on it ...

[E-val (e-val)]

> Right, you're not. It wasn't meant to be offensive. Also not to Luc.
Heh. Confusing me with driver developer looked like a compliment, not the offense. ;-)

> It's a huge mess.
Absolutely!

[Benno Schulenberg (bennoschulenberg)]

(In reply to comment #31)
> it's good news more people are interested in this release.
> Lets hope it's worth it.

Nothing is worth it when it doesn't come with source. As a user you may be interested only in having things work, developers are interested only in the source that makes it work. So please stop talking here on this bug -- email each other when you want to discuss things -- until you can post a patch that fixes this, or can provide specific information that clarifies the bug.

[stinke (redhat-tux)]

> Nothing is worth it when it doesn't come with source.

Good god it DOES!
Futher more I did not choose to comment my findings (thats all I've
been up too) on THIS list in the first place.

I'm trying to put some sense in what
(if something) was done with the VIA/DRM Kernel Modules, Mesa DRI code,
and XFree driver and find out if they managed to fix the issue.

Gah! Just RTF comments...

[Lverhaegen (lverhaegen)]

(In reply to comment #29)
> >
> [quote]stinke on Ubuntu lauchpad[/quote
> Okay, so someone has reported the new release in the
> DRI Mailing List [1] and it's been commented.

What release would that be and why do i not see anything in the mesa tree?

> It doesn't look like Valentine Sinitsyn and Luc Verhaegen
> have really had a look at the sources (yet).

Have you?

> From what I can tell everything except the libddmpeg.so
> is provided as source code in the package,
> contrary to what they are saying.

What about: uma_dri.so, libOGL.so, libGL.so.1.2 ?

See any code for those?

And what about the libS3G.a binaries in the drm directory?

Could it also be that you mistake what code there is for drm and agp as fully free source, ignoring the large binary blobs in the process?

If you say out loud that maybe some people should look at some things, maybe you should verify for yourself first. Especially when you're questioning the person who has been tracking VIA movements for the past 4.5ys, and who has kicked VIA up the rear end more than once for crap licenses in their x driver sources, and got them fixed.

Now, since another fable is helped out of this world, now i can, for my part, stf and do something useful.

[stinke (redhat-tux)]

> What release would that be and why do i not see anything in the mesa tree?

That was a reference to this thread which the person who copied my text
didn't include.

> Have you?

Yes and I can't see the files you are referring to further below in your
post.

Filename is
CLE266CN400CN-CX700CN800XORG40072-kernel-src_20071213d.tar.tgz

from 13th December

> What about: uma_dri.so, libOGL.so, libGL.so.1.2 ?

> See any code for those?

No and I don't have those files.

> If you say out loud that maybe some people should look at some things, maybe
> you should verify for yourself first... blah blah blah I rule bla bla

Where did I say that. I had assumed you have not looked inside this
particular file. Apparently I was right.

Thats not saying you should. I couldn't care less if you do or don't.

Furthermore, I'm not the person to comment the quality or value
of this new release. So far noone here did and thats what
we're all actually waiting for.

But instead I'm being attacked for what exactly?

[stinke (redhat-tux)]

Okay, so someone has reported the new release in the
DRI Mailing List [1] and it's been commented.

It doesn't look like Valentine Sinitsyn and Luc Verhaegen
have really had a look at the sources (yet).
From what I can tell everything except the libddmpeg.so
is provided as source code in the package,
contrary to what they are saying.

The only question is if what is provided can resolve the Texture issue
for the K8M800. I've read some very contrary reports in [2]
and the Via Arena forum. OTOH I'm not sure those people
are using this new code at all as it shouldn't even start X
with the VIA BIOS checksum of the K8M800
(or maybe just mine? Can someone verify?).

I'll see this evening If I can compile the X driver without
the checksum check and see what happens.

[1] https://bugs.freedesktop.org/show_bug.cgi?id=5092
[2] http://ubuntuforums.org/showthread.php?p=3930979

[Gaurish Sharma (gslive)]

^^^^
posted your comment on DRI :)

[stinke (redhat-tux)]

Thanks, I saw it. I don't have an account there.

:)

[E-val (e-val)]

> No and I don't have those files.
Confirm. I don't have those files in my archive (md5: eed5daf69f0b970aec0a654fdfcb731e) either. Blobs there are standard parts of Mesa DRI driver (unichrome_dri.so and libGL.so). The only strange part is libglx.so, but according to vinstall script it's used on FC6/7 only. But whether those blobs can be generated for the sources provided and what are the licensing terms for them (and last but not least does them suffer from the bug 5092) is still unknown, so I'd rather agree with #33 - lets stop posting here unless we have some specific information regarding the bug.

[FKtPp (m-pupil)]

(In reply to comment #37)
> > No and I don't have those files.
> Confirm. I don't have those files in my archive (md5:
> eed5daf69f0b970aec0a654fdfcb731e) either. Blobs there are standard parts of
> Mesa DRI driver (unichrome_dri.so and libGL.so). The only strange part is
> libglx.so, but according to vinstall script it's used on FC6/7 only. But
> whether those blobs can be generated for the sources provided and what are the
> licensing terms for them (and last but not least does them suffer from the bug
> 5092) is still unknown, so I'd rather agree with #33 - lets stop posting here
> unless we have some specific information regarding the bug.
>

Yes, the driver package contains some binary libraries. I've tried to compile the source on my Debian sid amd64 machine, and find out regardless it would work or not all necessary .so should be able to generated from the given source.

Via utils and mpeg decoding binaries didn't come with source, but I don't care about them.

The dri libraries was written against mesalib 6.5.2- which need some modification to successfully compiled in current mesalib 7.0.2+. But the result .so still crash my X when working with my old drm kernel module.

The drm kernel modules was written against kernel 2.6.18-(for Debian) which was also a bit out of date and will cause lot of compile warnings. And the result .ko refused to work with exist X. According the xorg.log AIGLX report "operation not perrmitted" will initialing and glxinfo also report "operation not permitted", this is really strange, my /etc/dri/card0 was already set to 0666 and I have correct DRI section in my xorg.conf file.

I also tried to compile the v4l modules, but failed.

The 2D driver compiled, but didn't work in my environment.

Anyone else working on this? Any good news?

[Benno Schulenberg (bennoschulenberg)]

(In reply to comment #38)
You appear to know your way around source code; you may wish to join #unichrome on Freenode.net.

[Gaurish Sharma (gslive)]

Is there anyone who successfully installed the driver & the freezing problem is there or "it just works"?

[ahaslam (anthonyhaslam)]

Via's new source release gave me a black screen on Debian Etch.

[Timo Aaltonen (tjaalton)]

Please try hardy alpha3 livecd, which defaults to openchrome now, and it has a newer mesa which might have a fix for this.

[ahaslam (anthonyhaslam)]

K8M800 laptop still freezes with hardy alpha3. Only tested the 'antinspect' screensaver, it took two seconds to lock up.

[Gaurish Sharma (gslive)]

Dear Friends,

I have just read and signed the online petition:

   "DECENT VIA GRAPHICS DRIVERS FOR LINUX"

hosted on the web by PetitionOnline.com, the free online petition
service, at:

   http://www.PetitionOnline.com/vialinux/

I personally agree with what this petition says, and I think you might
agree, too. If you can spare a moment, please take a look, and consider
signing yourself.

Best wishes,

Gaurish Sharma

[mikko (mikko-)]

Alpha 4 livecd, freeze when I tried to start F-spot, Via K8M800

https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/89467

[Edney Matias da Silva (edney)]

Hi!

Just to add, same problem here and know X crashes when loging into kde4.

lspci output
00:00.0 Host bridge: VIA Technologies, Inc. VT8378 [KM400/A] Chipset Host Bridge
01:00.0 VGA compatible controller: VIA Technologies, Inc. VT8378 [S3 UniChrome] Integrated Video (rev 01)

I'd tried it with -openchrome and -via driver availble in ubuntu repository redering the same results.

uname -a
2.6.22-14-generic

Running Ubuntu 7.10 with kde packages from http://ppa.launchpad.net/kubuntu-members-kde4/ubuntu gutsy main.

Signing the petition (http://www.petitiononline.com/vialinux/).

See ya.

[tech0007 (tech0007)]

Hi,

Installed the 0.8 binary driver from www.viaarena.com. Wine, f-spot, and a few 3d apps/games are now working fine, (google earth complains that I only have less than 16mb of video). But I still have 3 major issues:

1. glxinfo yields:
libGL warning: 3D driver claims to not support visual 0x22
libGL warning: 3D driver claims to not support visual 0x23
libGL warning: 3D driver claims to not support visual 0x24
libGL warning: 3D driver claims to not support visual 0x25
libGL warning: 3D driver claims to not support visual 0x26
libGL warning: 3D driver claims to not support visual 0x27
libGL warning: 3D driver claims to not support visual 0x28
libGL warning: 3D driver claims to not support visual 0x29
libGL warning: 3D driver claims to not support visual 0x2a
libGL warning: 3D driver claims to not support visual 0x2b
libGL warning: 3D driver claims to not support visual 0x2c
libGL warning: 3D driver claims to not support visual 0x2d
libGL warning: 3D driver claims to not support visual 0x2e
libGL warning: 3D driver claims to not support visual 0x2f
libGL warning: 3D driver claims to not support visual 0x30
libGL warning: 3D driver claims to not support visual 0x31

2. 3d apps and games that require textures locks up X so I have to do ctrl-alt-bckspce.

3. Still no compiz.

lspci | grep VGA
01:00.0 VGA compatible controller: VIA Technologies, Inc. UniChrome Pro IGP (rev 01)

[Djainette (djainette)]

Still buggy in Hardy alpha 5. Xorg was supposed to fix the problem.
And Vesa won't even start (no screen found)

[Djainette (djainette)]

Vote !
http://brainstorm.ubuntu.com/idea/1313/

[Timo Aaltonen (tjaalton)]

Uh, votes mean nothing.. you should need upstream attention, and looking at the upstream bug they are asking for people to help debugging this. So head on to #unichrome (irc channel) on freenode.net, and help the developers.

[Djainette (djainette)]

Iv' just tried re-enabling DRI with Hardy beta. It seems to be working so far. I've tried glxgears, winecfg and the GLMatrix screensaver.

[Gerson "fserve" Barreiros (fserve)]

with the new via (0.8) for 7.10 ubuntu i got 3D, and (!) Compiz working (just need to add to whitelist btw...) but with black boarders : (

and i got a problem too, my screen (1440x900) was splitted

and the "superior part" was a mirror from the "Inferior part"

weird problem, with a monitor on VGA port, the monitor was ok. nice to see compiz running...

with that "split" problem i needed to go back to xserver-xorg-driver-via. ~750fps on glxgears need at least 32mb ram to play games with wine/cedega (played starcraft/total annihilation) dont have tested with linux games, i will try xmoto but on old versions i got that problem where X Freezes.

only alt+sysrq+k saves when x freezes.

[NoWhereMan (e.vacchi) (uncommonnonsense)]

On Mon, Apr 21, 2008 at 7:32 AM, Gerson fserve Barreiros
<email address hidden> wrote:
> with the new via (0.8) for 7.10 ubuntu i got 3D, and (!) Compiz working
> (just need to add to whitelist btw...) but with black boarders : (

I'm interested in this; what does "with black borders" mean exactly?

[xanmoo (jeanpat-pommier)]

The gpu was even not recognized during Hardy installation (see attached file for lspci output),whereas the graphic cards (K8M800) was detected with gutsy.

glxinfo yields

glxinfo
name of display: :0.0
display: :0 screen: 0
direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)
server glx vendor string: SGI
server glx version string: 1.2

[xanmoo (jeanpat-pommier)]

I modified the xorg.conf file to activate 3D acceleration. The computer still freeze with some 3D app.
The performance of the via driver compared to the vesa driver are poor: glxgears yields around 400FPS with via vs 200 FPS with vesa (acer 1362LMI S3 unichrome Pro K8M800) at 1024x768 24 bits .

[Recouper (grant-howat)]

Well, I'm getting the issue with n nVidia card. My whole mother board is VIA K8M890CE, so maybe it's the host bridge that's doing it. But if you're thinking of just getting a new gfx card to fix this issue, just beware, it may not fix this.
Man, the frustration!
For quite a while now I was thinking that this was an nVidia issue. Graphics problem... must be the graphics card/driver. But it looks like there's a little more to it than that. 3D games hang my system in matter of seconds and Compiz-Fusion can go for about five minutes... if I'm lucky.
BTW, I signed that petition mentioned a little further back.
Good luck to the rest of you struggling with this.

[Gaurish Sharma (gslive)]

@Recouper
I have a K8M800 board & i have been using a nVidia card for past 2 years.
No problems faced yet.

[Edd (eduard-budulea)]

Hi, I have a wibrain tablet (chipset vx700) that the producers have put some deb packages for ubuntu 7.04 and 8.04.
They work for all via graphics. The problem is that you will be stuck with the kernel versions that are there.
look at:
http://code.google.com/p/wibrain-b1l/downloads/list
after the instalation the graphics package will modify your xorg.conf to make it work with an lcd of 1024x600, you have to adjust it again.
I can confrm that this packages works with compiz on 7.04 and 8.04
have fun, I know this is not a true solution but better then nothing.

[xanmoo (jeanpat-pommier)]

I have removed ubuntu from my acer 1362LMI. Did you try hardy? Does it fix the K8M800 VIA IGP Pro freeze issue?

[xanmoo (jeanpat-pommier)]

oops
I meant intrepid ibex

[Gaurish Sharma (gslive)]

No, the issue it not fixed.
Its not a Ubuntu problem, rather a upstream bug which is not likely to
get fixed soom. it occurs in all linux distros.
Regards,
Gaurish Sharma
www.gaurishsharma.com

On Mon, Sep 22, 2008 at 4:23 AM, xanmoo <email address hidden> wrote:
> oops
> I meant intrepid ibex
>
> --
> freezes with 3D applications on VIA Unichrome K8M800, KM400
> https://bugs.launchpad.net/bugs/43154
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[datatec (datatec)]

This is even worse for my box, using ibex beta, live cd and installed os freeze when it boots up to the login screen.

it basically justs shows a offblue screen an empty space for the login info and a frozen please wait spin circle (no motion)

If I move the mouse around a lot then suddenly a few of these wait circles appear on the screen (I assume at locationss where the mouse was)

I have tried this in video safe mode, using startx from the command prompt. always ends the same. :(

This box works perfectly with hardy. Isn't there any way to fix it for the ibex release?

if it helps to diagnose:
Gigabyte GA-K8VM800M-R2 FB
AND SEMPRON 2600+ using the UniChrome TM2 onboard graphics

[Gaurish Sharma (gslive)]

@datatec

Try Using VESA driver.

Regards,
Gaurish Sharma
www.gaurishsharma.com

On Tue, Oct 14, 2008 at 6:33 PM, datatec <email address hidden> wrote:
> This is even worse for my box, using ibex beta, live cd and installed os
> freeze when it boots up to the login screen.
>
> it basically justs shows a offblue screen an empty space for the login
> info and a frozen please wait spin circle (no motion)
>
> If I move the mouse around a lot then suddenly a few of these wait
> circles appear on the screen (I assume at locationss where the mouse
> was)
>
> I have tried this in video safe mode, using startx from the command
> prompt. always ends the same. :(
>
> This box works perfectly with hardy. Isn't there any way to fix it for
> the ibex release?
>
> if it helps to diagnose:
> Gigabyte GA-K8VM800M-R2 FB
> AND SEMPRON 2600+ using the UniChrome TM2 onboard graphics
>
> --
> freezes with 3D applications on VIA Unichrome K8M800, KM400
> https://bugs.launchpad.net/bugs/43154
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[muzzamo (murray-waters)]

Gaurish: whats the easiest way to force it to use the vesa driver?

[Timo Aaltonen (tjaalton)]

open for mesa already.

[viric (viriketo)]

More than a year passed... does anybody know anything new? I tried mesa 7.4, xorg server 1.5.3, libdrm 2.4.7, linux 2.6.28.9, openchrome 0.2.903. And I see the same hanging problem, maybe related to textures, because glxgears works well, but no other gl apps.

I have some self-made gl programs which only put points (no wireframe, no surfaces, ...), and that also hangs all.

[Bartosz Kosiorek (gang65)]

This bug was fixed in the openchrome svn 749. The 3D application will not freeze any more. It use software rendering

[Chris George (cgeorge-technatica)]

Thanks. I no longer have the laptop in question though.

On Thu, Aug 13, 2009 at 2:03 PM, Bartosz<email address hidden> wrote:
> This bug was fixed in the openchrome svn 749. The 3D application will
> not freeze any more. It use software rendering
>
> --
> freezes with 3D applications on VIA Unichrome K8M800, KM400
> https://bugs.launchpad.net/bugs/43154
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
" Carpe Diem! Rejoice while you are alive;
enjoy the day; live life to the fullest;
make the most of what you have."

- Horace

[reh4c (gene-hoffler)]

I appreciate all of the developers' hard work as well, but I no longer have my laptop either.

--- On Thu, 8/13/09, Chris George <email address hidden> wrote:

From: Chris George <email address hidden>
Subject: Re: [Bug 43154] Re: freezes with 3D applications on VIA Unichrome K8M800, KM400
To: <email address hidden>
Date: Thursday, August 13, 2009, 9:54 PM

Thanks. I no longer have the laptop in question though.

On Thu, Aug 13, 2009 at 2:03 PM, Bartosz<email address hidden> wrote:
> This bug was fixed in the openchrome svn 749. The 3D application will
> not freeze any more. It use software rendering
>
> --
> freezes with 3D applications on VIA Unichrome K8M800, KM400
> https://bugs.launchpad.net/bugs/43154
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
" Carpe Diem! Rejoice while you are alive;
enjoy the day; live life to the fullest;
make the most of what you have."

- Horace

--
freezes with 3D applications on VIA Unichrome K8M800, KM400
https://bugs.launchpad.net/bugs/43154
You received this bug notification because you are a direct subscriber
of a duplicate bug.

[Bryce Harrington (bryce)]

Closing as believed-fixed as per the last few comments.

[ahaslam (anthonyhaslam)]

Not fixed.

K8M800 locks up solid with ant-spotlight screensaver in alpha 5.

[thisma (1-launchpad-net-sniftyentertainment-com)]

I have this problem on an new install from:
Ububtu v9.10 desktop amd64 (downloaded 2010-Feb-25)

Is this fixed?
Where can I get the fix?
How do I apply the fix?

-Joshua

[Alberto Jovito (thedemon007)]

I have this problem on an new install from: Ububtu v10.10 desktop amd64 with driver vx800

[Alberto Jovito (thedemon007)]

Open wine freezes when using drivers openchrome not the case with the vesa driver if works well