Hi Cuneytm > I noticed the original driver is around 300K whereas the new one is 1.4MB. > Just wondering if its worth to replace the existing driver with the new > one > if there is no noticeable difference like you said.
guess that is a debug build, many symbols and other stuff in the image. should not be a problem, although i had concerns, the paging will evict unused pages and hence free the symbols in the image from physical memory if they haven't touched. > I am not sure how the driver is handled, perhaps loaded in memory at all > times? yes, as long as the x-server runs, it must have the low-level driver mapped in memory. > I tried to locatethe Xorg.log for such entries like you mentioned; > (II) VIA(0): Benchmarking video copy. Less is better. > (--) VIA(0): Timed libc YUV420 copy... 1813278. Throughput: 326.4 MiB/s. > (--) VIA(0): Timed kernel YUV420 copy... 1777349. Throughput: 333.0 MiB/s. > (--) VIA(0): Timed SSE YUV420 copy... 1019839. Throughput: 580.4 MiB/s. > (--) VIA(0): Timed MMX YUV420 copy... 1640572. Throughput: 360.8 MiB/s. > > But i dont see anything close to it, almost no mention of VIA driver. did you assign a graphics card to the thinclient, the unicrome chipset? else, the x-server would fall back to vesa or whatever the default is. > Then i check again, after i replace the driver and kill x11 > (ctrl+alt+bckspace) and still nothing about the VIA entries as such.. > The driver file is replaced for sure but curious why i dont see anything > in > logs. hmmm... nothing on stdout for a "grep via /var/log/Xorg.0.log" ??? strange... > If i want to deploy this to all the thinclients, do i need to repeat the > task for each and every thinclient (i..e add kernel parameters and login > to > replace the file) or is it changing from the central image (i.e. one > change > will effect all other thinclients) ? yes, in fact you must replace the driver and restart the x-server every boot for any unichrome thinclient. another approach were: the image with the base system is a "base.sfs", a squash fs image. you can unpack this image (squashfs tools), change the files you want and create a new squashfs (squashfs tools) with the new files. but since i can't notice any difference, you can go with the openchrome-0.2.1 which comes with openthinclient-0.3.0, IMHO. also i would wait for the 0.3.1 release where the new NON-DEBUG-BUILD-0.2.9 driver should be included. i did more testing overhere and it seems the unichrome chipset/memory is out of steam for 32 bit frame buffers. on 16-bit it performes pretty good. no difference to a local desktop experience for apps like internet explorer and basic office stuff. even photoshop 7 scrools that smooth of my ass... but it kills the server ;) > On a related note, i am trying to figure on how to work with the existing > packages (under os folder specifically). > For instance, the artwork package under os folder. If i download and > change > the artwork then run tcos_buildpackage and tcod_uploaddebs and load the > package to OTCM - install it. > The thinclient takes considerable time before the login screen appears, on > text console where it hangs at building tcos image for sometime. > Even if i wait and manage to login, i see the changes are not reflected. > Do you have any knowledge on working with existing OS packages? no i don't, sorry. seems like something went wrong while the build or there is a bug in the package(s). may be some log will give you a glue what went wrong. we also have planned to change the bg-image -- corporated design and that shit, customers omg! -- but we must do other stuff too. i love my job but hate the work (sometime ;) > All the best! same2u and gd'luck -jolt ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ The Open Source Thin Client Solution http://openthinclient.org [email protected] https://lists.sourceforge.net/lists/listinfo/openthinclient-user
