How to install XF86 Geode video driver?
How to install XF86 Geode video driver?
Hi,
My UMPC is GeodeLX 800 based with 1024x600 screen. Dingo works with 1024x768 and to make max windows at 1024x600, I am using Dingo margin setting. But still a problem when doing presentation which is 1024x768 on projector screen
I found AMD Geode driver tarball but I don't know hot to install and set. I tried to compile but lots of error. Since I am a Linux newbie, please help to give me detailed instruction.
The tar files attached in this post
TIA,
Zoegy
My UMPC is GeodeLX 800 based with 1024x600 screen. Dingo works with 1024x768 and to make max windows at 1024x600, I am using Dingo margin setting. But still a problem when doing presentation which is 1024x768 on projector screen
I found AMD Geode driver tarball but I don't know hot to install and set. I tried to compile but lots of error. Since I am a Linux newbie, please help to give me detailed instruction.
The tar files attached in this post
TIA,
Zoegy
- ttuuxxx
- Posts: 11171
- Joined: Sat 05 May 2007, 10:00
- Location: Ontario Canada,Sydney Australia
- Contact:
Here's your pet you need, enjoy
ttuuxxx
ttuuxxx
- Attachments
-
- xf86-video-geode.pet
- (130.82 KiB) Downloaded 1428 times
http://audio.online-convert.com/ <-- excellent site
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
Can't get Xorg working with Geode Driver
Please, can someone give me step by step instructions on how to make it work ?
Even a simple geode_drv.so binary that I can put in Dingo would be great !
I'm trying to adapt Puppy to make a sort of 'smart thin client'.
Thanks in advance, Jacopo
Even a simple geode_drv.so binary that I can put in Dingo would be great !
I'm trying to adapt Puppy to make a sort of 'smart thin client'.
Thanks in advance, Jacopo
Puppy, Geode and General Software BIOS
It seems that Geode mobos with General Software BIOS have problems with Xorg > 1.2 (because of a few bugs in x86emu). Ubuntu has a fix. Is someone able to make it work on Puppy, too ? That would be great ! J.
- ttuuxxx
- Posts: 11171
- Joined: Sat 05 May 2007, 10:00
- Location: Ontario Canada,Sydney Australia
- Contact:
Re: Puppy, Geode and General Software BIOS
just give me the link to fix page and I'll see what I can doJacopo wrote:It seems that Geode mobos with General Software BIOS have problems with Xorg > 1.2 (because of a few bugs in x86emu). Ubuntu has a fix. Is someone able to make it work on Puppy, too ? That would be great ! J.
ttuuxxx
http://audio.online-convert.com/ <-- excellent site
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
- ttuuxxx
- Posts: 11171
- Joined: Sat 05 May 2007, 10:00
- Location: Ontario Canada,Sydney Australia
- Contact:
Here you go, it works only with xorg not xvesa
hope it works
the drivers are
/usr/lib/xorg/modules/drivers/geode_drv.so
/usr/lib/xorg/modules/drivers/ztv_drv.so
and a link to /usr/lib/xorg/modules/drivers/amd_drv.so from /usr/lib/xorg/modules/drivers/geode_drv.so
ttuuxxx
hope it works
the drivers are
/usr/lib/xorg/modules/drivers/geode_drv.so
/usr/lib/xorg/modules/drivers/ztv_drv.so
and a link to /usr/lib/xorg/modules/drivers/amd_drv.so from /usr/lib/xorg/modules/drivers/geode_drv.so
ttuuxxx
- Attachments
-
- xserver-xorg-video-geode_2.8.0-7.pet
- (140.29 KiB) Downloaded 1198 times
http://audio.online-convert.com/ <-- excellent site
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
- ttuuxxx
- Posts: 11171
- Joined: Sat 05 May 2007, 10:00
- Location: Ontario Canada,Sydney Australia
- Contact:
if the one above doesn't work try this one
ttuuxxx
ps tell us how it went
ttuuxxx
ps tell us how it went
http://audio.online-convert.com/ <-- excellent site
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
Have tried both versions above without success.
The amd driver seems to work.
I am running a Puppy 4.1 retro kernel on a fit-pc slim, see http://www.fit-pc.com/forum/viewtopic.php?t=582
I get the same error in Xorg.0.log for both drivers, the new driver seems to have another version than the server:
II) LoadModule: "geode"
(II) Loading /usr/X11R7/lib/xorg/modules/drivers//geode_drv.so
(II) Module geode: vendor="X.Org Foundation"
compiled for 1.4.0.90, module version = 2.8.0
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 2.0
(EE) module ABI major version (2) doesn't match the server's version (1)
(II) UnloadModule: "geode"
.
.
(EE) No drivers available.
Fatal server error:
no screens found
/Johan
The amd driver seems to work.
I am running a Puppy 4.1 retro kernel on a fit-pc slim, see http://www.fit-pc.com/forum/viewtopic.php?t=582
I get the same error in Xorg.0.log for both drivers, the new driver seems to have another version than the server:
II) LoadModule: "geode"
(II) Loading /usr/X11R7/lib/xorg/modules/drivers//geode_drv.so
(II) Module geode: vendor="X.Org Foundation"
compiled for 1.4.0.90, module version = 2.8.0
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 2.0
(EE) module ABI major version (2) doesn't match the server's version (1)
(II) UnloadModule: "geode"
.
.
(EE) No drivers available.
Fatal server error:
no screens found
/Johan
- technosaurus
- Posts: 4853
- Joined: Mon 19 May 2008, 01:24
- Location: Blue Springs, MO
- Contact:
Xorg video driver geode 2.10.1
I compiled xorg_video_geode-2.10.1 to try and get xorg to work on my DecTop - I did strip the driver binaries down afterward to cut the size by ~75% - installs fine - for GX2 must use X -configure and then edit xorg.conf due to some (default) EXA issues and add
to use XAA acceleration instead
Code: Select all
Option "AccelMethod" "XAA"
- Attachments
-
- xorg_geode-2.10.1.pet
- compiled from source on puppy 4.1
- (125.46 KiB) Downloaded 1420 times
Hi, I've been testing linux distros for a while and everytime the same problem appears, the AMD Geode video driver messes up things.
Being new to the Linux world found this puppy which is lovely for a low resources computer such as the mounted on Geodes but again, the problem with the video persists.
Read this thread but I'm a little confused, would there be a problem to explain step by step how to get the drivers you posted working?
Being new to the Linux world found this puppy which is lovely for a low resources computer such as the mounted on Geodes but again, the problem with the video persists.
Read this thread but I'm a little confused, would there be a problem to explain step by step how to get the drivers you posted working?
Finally, I can use Geode driver on my laptop. But unfortunately not with Puppy. Slackware solved my problem. Puppy always replace the already modified xorg.conf.
In slackware, if xorg.conf resulting unexpected results, the x won't start. But if correct, the x is very beautiful. Slackware will not replace the error containing xorg.conf
This is what I did in Slackware (ver 12.1) :
1. Using the original kernel, lxfb may or may not freeze the x after loading x. I blacklist lxfb module to get my x works for the first time.
2. I recompile the kernel. I allowed lxfb modules work but not vesafb. Vesafb make my computer freeze after quit from x. There's no way to blacklist vesafb since it is incorporated in kernel and can't be compiled as module. Vesafb can be blacklisted by not ticking console frame buffer option (in gconfig or xconfig). For the safest option, blacklisting both lxfb and vesafb is just fine or still allowing lxfb when compiling but if causes problem when starting x, we can blacklist it in blacklist file in modprobe.d folder (which we can't do it for vesafb). In my case lxfb no longer causing problem after kernel recompiling.
3. Install the kernel and and its modules and doing it in text mode (Doing it in x will mess the bootup)
4. Modify the xorg.conf
For standard screen, xorgconfig can be used, but for non standard screen like mine, execute gtf [xres] [yres] [vertrefresh] -x, add the result (modeline blah....blah....) to xorg.conf, add PanelGeometry (my case is 1024x600) option into xorg.conf. Replace "vesa" driver with "geode"
5. Reinstall grub (maybe not necessary in Puppy, I did it in Slackware after installing new kernel or LILO will take over)
5. Reboot
I think the problem in Puppy is in xwin script. Xwin must be modified to force x to use the modified xorg.conf (with geode driver). I replace the device driver section with geode but puppy always replace it with nsc or vesa. Below is screenshot of my NB screen.
I hope those approach in Slackware can be doable in Puppy.
BTW, I am sorry for my English. It's my third language
In slackware, if xorg.conf resulting unexpected results, the x won't start. But if correct, the x is very beautiful. Slackware will not replace the error containing xorg.conf
This is what I did in Slackware (ver 12.1) :
1. Using the original kernel, lxfb may or may not freeze the x after loading x. I blacklist lxfb module to get my x works for the first time.
2. I recompile the kernel. I allowed lxfb modules work but not vesafb. Vesafb make my computer freeze after quit from x. There's no way to blacklist vesafb since it is incorporated in kernel and can't be compiled as module. Vesafb can be blacklisted by not ticking console frame buffer option (in gconfig or xconfig). For the safest option, blacklisting both lxfb and vesafb is just fine or still allowing lxfb when compiling but if causes problem when starting x, we can blacklist it in blacklist file in modprobe.d folder (which we can't do it for vesafb). In my case lxfb no longer causing problem after kernel recompiling.
3. Install the kernel and and its modules and doing it in text mode (Doing it in x will mess the bootup)
4. Modify the xorg.conf
For standard screen, xorgconfig can be used, but for non standard screen like mine, execute gtf [xres] [yres] [vertrefresh] -x, add the result (modeline blah....blah....) to xorg.conf, add PanelGeometry (my case is 1024x600) option into xorg.conf. Replace "vesa" driver with "geode"
5. Reinstall grub (maybe not necessary in Puppy, I did it in Slackware after installing new kernel or LILO will take over)
5. Reboot
I think the problem in Puppy is in xwin script. Xwin must be modified to force x to use the modified xorg.conf (with geode driver). I replace the device driver section with geode but puppy always replace it with nsc or vesa. Below is screenshot of my NB screen.
I hope those approach in Slackware can be doable in Puppy.
BTW, I am sorry for my English. It's my third language
- technosaurus
- Posts: 4853
- Joined: Mon 19 May 2008, 01:24
- Location: Blue Springs, MO
- Contact:
I forgot to mention that I deleted all of the other xorg drivers - I did it only to save a little space but apparently it helped me out in other ways. I will recompile a new driver when 2.12 is released which will have RandR and incorporate nsc and cyrix (thus avoiding these conflicts) and for the rest of the xorg.conf I used one that Xubuntu Intrepid created - all I needed to change was to add the ..."XAA" line
- technosaurus
- Posts: 4853
- Joined: Mon 19 May 2008, 01:24
- Location: Blue Springs, MO
- Contact:
Here is a new one to try - I don't have my DECtop available to test at the moment
- Attachments
-
- xf86-video-geode-2.11.6-i486.pet
- (118.13 KiB) Downloaded 516 times
Check out my [url=https://github.com/technosaurus]github repositories[/url]. I may eventually get around to updating my [url=http://bashismal.blogspot.com]blogspot[/url].
I tried the 2.11.6 geode drivers but did not work for me.technosaurus wrote:Here is a new one to try - I don't have my DECtop available to test at the moment
However there are several caveats.
I'm using a full install of pup431 (with devx431 also in full install) running off a USB stick on an OLPC XO-1 laptop.
Since I did not have a running window manager, from the console I installed the pet manually by untarring and copying to the ...../drivers.
Running xwin either with the default configuration or with XAA acceleration or with the OLPC xorg.conf configuration (EXA) failed.
Xorg.0.log indicates failure parsing the "Mode" entry in Monitor section.
One other strange complain that xwin had, was the "Module usbhid not found". I'm using a modified OLPC 2.6.31 kernel and lsmod indicates that usbhid is loaded, is not used and is using the usbcore module
I guess there is more to it than the drivers
I am getting crazy with this too.
I got a new TFT Display (ASUS VW161D) for my unit (FSC A220 ThinClient) and now I am getting the problem to be able to use the nativ resolution of the TFT (1360x768).
With the PET installed I could use the 4:3 modes without any trouble but now I run out of SYNC everytime I try to use the 1360x768 mode.
Could anyone be helpful with this?
Regards
I got a new TFT Display (ASUS VW161D) for my unit (FSC A220 ThinClient) and now I am getting the problem to be able to use the nativ resolution of the TFT (1360x768).
With the PET installed I could use the 4:3 modes without any trouble but now I run out of SYNC everytime I try to use the 1360x768 mode.
Could anyone be helpful with this?
Regards
problem ist SOLVED for me...
modified the xorg.conf with:
Section "Monitor"
Identifier "ASUS"
HorizSync 30-90
VertSync 50-60
UseModes "Custom"
EndSection
Section "Modes"
Identifiert "Custom"
ModeLine "1360x768" 85.5 1360 1424 1536 1792 768 771 777 795 +hsync +vsync
EndSection
Hope this help other a little bit
USED THE 2.10.1 Driver with the added Line
Option "AccelMode" "XAA"
Ciao
modified the xorg.conf with:
Section "Monitor"
Identifier "ASUS"
HorizSync 30-90
VertSync 50-60
UseModes "Custom"
EndSection
Section "Modes"
Identifiert "Custom"
ModeLine "1360x768" 85.5 1360 1424 1536 1792 768 771 777 795 +hsync +vsync
EndSection
Hope this help other a little bit
USED THE 2.10.1 Driver with the added Line
Option "AccelMode" "XAA"
Ciao
- technosaurus
- Posts: 4853
- Joined: Mon 19 May 2008, 01:24
- Location: Blue Springs, MO
- Contact:
Sounds like I must have uploaded the wrong driver - you can compile it with or without tft support for gx2. I compiled it both ways (because I couln't find reference as to why that option was even available) It only takes a couple minutes to compile, so I can upload a new one tonight. Sorry for the inconvenience, I should have my Dectop back soon to test.
Check out my [url=https://github.com/technosaurus]github repositories[/url]. I may eventually get around to updating my [url=http://bashismal.blogspot.com]blogspot[/url].