How to install XF86 Geode video driver?
-
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 512 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].
-
technosaurus
- Posts: 4853
- Joined: Mon 19 May 2008, 01:24
- Location: Blue Springs, MO
- Contact:
Updated with flatpanel support
- Attachments
-
- xf86-video-geode-2.11.6-i486.pet
- (118.28 KiB) Downloaded 542 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].
Well... I tried the new drivers and all kinds of variations in xorg.conf with no luck 
However the problem may not be in the drivers but in the inability of puppy to detect the DCON the special custom chip that controls the XO-1 display. So the xwin fails because it can not find the display. The dcon driver is present in the kernel but somehow I have to instruct puppy to use it...
However the problem may not be in the drivers but in the inability of puppy to detect the DCON the special custom chip that controls the XO-1 display. So the xwin fails because it can not find the display. The dcon driver is present in the kernel but somehow I have to instruct puppy to use it...