Bug#800367: How to say No!! in a polite though ridiculous way
Hi Andreas, Throw this in your xorg.conf Section "Module" Load"vgahw" EndSection Other than that, your xorg.conf can be empty. I hope it works. Regards, Kevin Brace The OpenChrome Project maintainer / developer
Bug#800367: How to say No!! in a polite though ridiculous way
Hi Andreas, I am not sure of your intention when you changed the title of the technical support request to "How to say No!! in a polite though ridiculous way," but please understand that I do not get paid to work on developing OpenChrome. I am not a paid developer of VIA Technologies, thin client vendors, or Linux vendors like RedHat, Canonical, etc. I do not mind becoming a paid developer, although I will rather not want to do it as a contractor. I work on this out of my own time, and I have spent my own funds (probably around $500 already) collecting VIA Technologies silicon products specifically for validation of OpenChrome code changes I have made. I have already spent 1.5 years on developing OpenChrome, and if it was not for me, nobody would have done maintenance / further development of OpenChrome past the buggy Version 0.3.3 release. Please understand that developers often do not like being forced to adopt end user's particular OS release. For now, I stick to Xubuntu / Lubuntu based OSes, and this is because I am most familiar with those OSes. I do maintain source code backward compatibility all the way to X.Org Server 1.7 / Linux 2.6.32. I do try to make sure that OpenChrome works with OSes other than Ubuntu based OSes, but the primary validation is done on Ubuntu based OSes since that's what I am most familiar with. Although I have done so for 2 to 3 months, I have tested OpenChrome Version 0.5 with Lubuntu 12.04 on Wyse Vx0 thin client. This contains P4M800 Pro chipset; the same chipset your Neoware mobile thin client has. Someone who owns several VIA Technologies based silicon products taught me how to install Lubuntu 12.04 on a USB flash memory stick that is recognized as a USB hard drive. This is now I verified that OpenChrome works with Wyse Vx0 thin client. Just to prove that OpenChrome works with your Neoware m100 mobile thin client, I recommend that you obtain a USB flash memory stick that can be recognized as a USB hard drive, install something like Lubuntu 12.04 to see if OpenChrome works or not. Just to let you know, I do own several Wyse thin clients like Vx0, Cx0, and Xx0L (mobile thin client), and do some testing from time to time. Obviously, more testing gets done during RC (Release Candidate) stage of the development. As far as I can tell, the issue you are observing with the VGA related helper module is a Debian specific issue, and it is beyond the scope of OpenChrome project. I am a digital hardware engineering background person doing device driver development, and as a result, I am not an OS build environment expert. I do not even know how to use Git beyond very basic stuff, and even that stuff was taught by one of the previous OpenChrome developer who probably could not believe that I knew so little about Git. To get assistance with your issue, you will need to find someone who is far more familar with those issues, specifically with regards to Debian. If you check the December 2016 openchrome-devel mailing list, you will find two Debian related developers who asked OpenChrome to accept changes to the build script. You may want to contact those developers who may be able to assist you better than I can. Again, I can see why you will not be happy with the way things are going or how I have responded with your issue, but this is basically the best I can do since I am mostly focused on coding side of the development. Regards, Kevin Brace The OpenChrome Project maintainer / developer > Well, now, dear chaps, there at the VIA-front, > > if you look at my installation-report: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800367 > > particularly this part: > > > lspci -knn: 00:00.0 Host bridge [0600]: VIA Technologies, Inc. > > CN700/VN800/P4M800CE/Pro > > Host Bridge [1106:0314] lspci -knn: Subsystem: VIA Technologies, > > Inc. > > CN700/VN800/P4M800CE/Pro Host Bridge [1106:0314] lspci -knn:Kernel > > driver in > > use: agpgart-via lspci -knn: 00:00.1 Host bridge [0600]: VIA Technologies, > > Inc. > > CN700/VN800/P4M800CE/Pro Host Bridge [1106:1314] lspci -knn: 00:00.2 Host > > bridge [0600]: > > VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge [1106:2314] > > lspci -knn: > > 00:00.3 Host bridge [0600]: VIA Technologies, Inc. PT890 Host Bridge > > [1106:3208] lspci > > - -knn: 00:00.4 Host bridge [0600]: VIA Technologies, Inc. > > CN700/VN800/P4M800CE/Pro Host > > Bridge [1106:4314] lspci -knn: 00:00.7 Host bridge [0600]: VIA > > Technologies, Inc. > > CN700/VN800/P4M800CE/Pro Host Bridge [1106:7314] lspci -knn: 00:01.0 PCI > > bridge [0604]: > > VIA Technologies, Inc. VT8237/VX700 PCI Bridge [1106:b198] lspci -knn: > > 00:0b.0 CardBus > > bridge [0607]: Texas Instruments PCI1510 PC card Cardbus Controll
Bug#800367: installation-report: stretch-testing on NEOWARE m100: no graphics
Hi Andreas, The issue you are having probably is outside of OpenChrome's control. There appears to be an issue finding the correct library, and I am not really familiar dealing with this kind of a situation. I guess this is called the dependencies issue, I suppose. I almost exclusively use Xubuntu / Lubuntu LTS versions for development and validation, and obviously, I am able to compile and load OpenChrome without issues. To "prove" that Neoware m100 mobile thin client's hardware is compatible with OpenChrome, you may want to download, compile, and install the latest OpenChrome code. This post I made while back is very detailed, so you should not have issues installing the latest OpenChrome code. https://lists.freedesktop.org/archives/openchrome-users/2016-February/007237.html Regards, Kevin Brace The OpenChrome Project maintainer / developer > Date: Sun, 8 Jan 2017 10:33:04 +0100 > From: Andreas Glaeser > To: 800...@bugs.debian.org, openchrome-us...@lists.freedesktop.org > Subject: [Openchrome-users] installation-report: stretch-testing on > NEOWARE m100: no graphics > Message-ID: <20170108103304.26e855a8@a68n.lokal> > Content-Type: text/plain; charset="utf-8" > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > There is some improvement visible regarding openchrome video-diver, > particularly, there > > is no xorg.conf necessary any more in order to make use of the VESA-driver, > but obviously > > X falls back to VESA automatically, which is positive in my opinion, so > people will have > > some workable graphics-output, even if openchrome-video-driver is not > workable properly on > > their hardware, without fiddling with Xorg-configuration. > > See attached logfile [Xorg.0.log] > > As far as I can tell, this is the essential part of the log, showing, why > openchrome is > not workable yet: > > . > . > .. > > [24.359] (II) LoadModule: "openchrome" > > [24.368] (II) Loading /usr/lib/xorg/modules/drivers/openchrome_drv.so > > [24.390] (EE) Failed to > > load /usr/lib/xorg/modules/drivers/openchrome_drv.so: > > /usr/lib/xorg/modules/drivers/openchrome_drv.so: undefined symbol: > > vgaHWFreeHWRec > [24.393] (II) UnloadModule: "openchrome" > > [24.393] (II) Unloading openchrome > > [24.393] (EE) Failed to load module "openchrome" (loader failed, 7) > .. > . > . > > It would be even nicer, guys, if openchrome worked properly on my hardware > instead of > falling back to VESA. Now this would really be super-great, get it? > > > > > > X.Org X server -- VIA display driver > > > > OpenChrome is a project for the development of free and open-source drivers > > for the VIA > > UniChrome video chipsets. > > > > Originally called the 'snapshot' release, since it was a snapshot of an > > experimental > > branch of the unichrome cvs code, this is a continued development of the > > open source > > unichrome driver (from http://unichrome.sf.net) which also incorporates > > support for the > > unichrome-pro chipsets. > > > > Support for hardware acceleration (XvMC) for all chipsets has subsequently > > been ripped > > out of the unichrome.sf.net driver. Therefore your only option if you wish > > to make use > > of the acceleration features of your VIA chip with free and open-source > > drivers is to > > use this version of the driver. > > > > Tags: Hardware Enablement: Graphics and Video, Implemented in: C, Role: > > Plugin, > > Purpose: Hardware Driver Other Packages Related to > > xserver-xorg-video-openchrome > > > > depends > > > > > > > > recommends > > > > > > > > suggests > > > > > > > > enhances > > > > dep: libc6 (>= 2.14) [amd64] > > GNU C Library: Shared libraries > > also a virtual package provided by libc6-udeb > > > > dep: libc6 (>= 2.4) [i386] > > > > dep: libdrm2 (>= 2.3.1) > > Userspace interface to kernel DRM services -- runtime > > > > dep: libx11-6 (>= 2:1.4.99.1) > > X11 client-side library > > > > dep: libxext6 > > X11 miscellaneous extension library > > > > dep: libxv1 > > X11 Video extension library > > > > dep: libxvmc1 > > X11 Video extension library > > > > dep: xorg-video-abi-23 > > virtual package provided by xserver-xorg-core, > > xserver-xorg-core-udeb > > > > dep: xserver-xorg-core (>= 2:1.18.99.901) > > Xorg X server - core server > > > -BEGIN PGP SIGNATURE- > Version: GnuPG v2 > > iEYEARECAAYFAlhyB1gACgkQ5+rBHyUt5wvDngCdFSjRLke0PH2QSL9qIAaaFkh4 > qV4An1UwX1ghNr0+Y64kl/5KwB4zGSEA > =GmAW > -END PGP SIGNATURE- > -- next part -- > A non-text attachment was scrubbed... > Name: Xorg.0.log.xz > Type: application/x-xz > Size: 8084 bytes > Desc: not available > URL: > <https://lists.freedesktop.org/archives/openchrome-users/attachments/20170108/ec7b5c99/attachment-0001.xz>
