Puppy Linux Discussion Forum

scsijon · Posted: Sun 13 Jan 2013, 22:18 Post subject:

David, which radeon driver did you install please and from what repositry? /root/.packages/user-installed-packages and the particular line will give it to you.

Both, thanks for the data I shall look at them this evening.

Anyone, I have found some interesting information on screen matrixes and x11/xorg interaction, apparently our well known sizes of 4 x 3 (standard screen matrix) and 16 x 9 (widescreen matrix) are not alone, there are also 5 x 4 for standard screens and 16 x 10 for widescreens. And depending on the x11/xorg reading tables and the particular videocard's internal settings you may get either set depending on what is connected and what scan frequencies are being used. On top of that the earlier videocard's don't have the ability to differentiate a CRT and LCD screen and that can also effect things. No wonder video is a major problem in all the varying systems.

davids45 · Joined: 26 Nov 2006 Posts: 961 Location: Chatswood, NSW

G'day scsijon,

Billtoo · Joined: 07 Apr 2009 Posts: 3166 Location: Ontario Canada

I did a frugal install to the hard drive with the puppy universal installer.

Mage2, version 0.0.10 on Mon 14 Jan 2013
Chip description:
X Server: Xorg
Driver used: intel
X.Org version: 1.11.4
dimensions: 1280x1024 pixels (338x270 millimeters)
depth of root window: 24 planes
Computer
Processor 4x Intel(R) Core(TM) i3 CPU 540 @ 3.07GHz
Memory 6025MB (114MB used)
Mon 14 Jan 2013 06:56:48 AM EST
Display
Resolution 1280x1024 pixels
OpenGL Renderer Gallium 0.4 on llvmpipe (LLVM 0x300)
X11 Vendor The X.Org Foundation
OpenGL
Vendor VMware, Inc.
Renderer Gallium 0.4 on llvmpipe (LLVM 0x300)
Version 2.1 Mesa 8.0.2
Direct Rendering Yes
Compact Wireless-G USB Adapter rt73

I added glxinfo from ppm to get the opengl info above.
Mage2 is working well on this pc.

scsijon · Posted: Mon 14 Jan 2013, 17:03 Post subject:

thanks david, that's wierd as it's the same driver as I have in the driver patch-pet on the last page. I shall rebuild it in case something didn't package correctly.

Thank you BillToo, did you add either of the patches on p11? as the ddcprobe pet may have been needed anyway. Can I have a sys-info report please anyway (under system-status and config) just to check against.

Billtoo · Joined: 07 Apr 2009 Posts: 3166 Location: Ontario Canada

scsijon · Posted: Fri 18 Jan 2013, 04:54 Post subject:

thanks bill, it looks like intel has no problem with the old ddcprobe, however just about everything else does, figures!

Note for all, that i'm working with joe wing on a problem on his new JWM (653+), otherwise mage2-0011 is ready, I'll give it a week and if he/we can't work out what's wrong and fix it (after all it may be my end, not his) I'll release mage2-0011 as is.

EDIT1: JWM: I've worked through one jwm problem with joe wing and now a second is being dealt with by him for me.

There will be a couple of changes puppy woof builders (not users) will need to do as he has changed a few things slightly, and I believe better, but the new builds are both faster as well as more pleasing to use! At present we are up to build jwm-659. I shall release a pet that should be just a 'plug-in' for everyone when the current problem has been resolved.

futwerk · Joined: 07 May 2011 Posts: 337

new backgrounds.

disciple · Posted: Mon 11 Feb 2013, 21:23 Post subject:

Hi, have you guys checked out the qt based Opie palmtop environment for suitable apps for qt puppy?

thunor · Posted: Tue 05 Mar 2013, 13:56 Post subject:

I've installed and am using this now (very nice) but I'm on a Compaq Presario C500 laptop with Intel integrated graphics and selecting "intel" from the list at set-up caused probe to give me a black screen forever. I powered off/on and selected "vesa" and I've now got a speedy enough 1024x768 desktop.

I did have to copy across three wireless drivers into /lib/firmware/b43 (b0g0bsinitvals5.fw, b0g0initvals5.fw and ucode5.fw) but other people have worked that out too.

So, any ideas on the Intel driver? Is it not present? If so can somebody recommend a link to a suitable package.

The information from "lspci -v" appears to me to be lacking in detail for everything. I'm guessing by the driver name that this is the graphics hardware (Intel Graphics Media Accelerator 950):

scsijon · Posted: Tue 05 Mar 2013, 18:31 Post subject:

@thunor, can you attach a lighthouse sysinfo report please, as unlike the normal puppy the intel driver in mage2 from mageia contains the i810 driver component variations. The i810 is severly depreciated and not suitable for series3 kernels according to the intel driver site.

However you are suppose to have a GMA950 == i945Gxx so that should be ok as is, in the meantime, I shall research further.

EDIT: I have found only one driver referanced against linux for this but it's a series2 kernel and there is a note that it is not supported well under linux. I shall chase further so I can only sugest you stick to vesa until I have something for you.

EDIT2: It is interesting that on the intel site it lists that for linux the GMA950 chip across most video matrixes mainly uses vesa drivers with series 3 kernels.

Standard timings supported
640 x 480 at 60Hz - IBM VGA
640 x 480 at 67Hz - Mac II
640 x 480 at 72Hz - VESA
640 x 480 at 75Hz - VESA
720 x 400 at 70Hz - IBM VGA
800 x 600 at 56Hz - VESA
800 x 600 at 60Hz - VESA
800 x 600 at 72Hz - VESA
800 x 600 at 75Hz - VESA
832 x 624 at 75Hz - Mac II
1024 x 768 at 60Hz - VESA
1024 x 768 at 70Hz - VESA
1024 x 768 at 75Hz - VESA
1152 x 864 at 75Hz - VESA
1280 x 960 at 60Hz - VESA
1280 x 1024 at 60Hz - VESA
1280 x 1024 at 75Hz - VESA
1440 x 900 at 60Hz - CMO
1440 x 1440 at 60Hz - VESA

I shall investigate further.

thunor · Posted: Wed 06 Mar 2013, 11:08 Post subject:

scsijon · Posted: Wed 06 Mar 2013, 18:24 Post subject:

@thunor: No, don't worry about it. I have chased your problem down to being a ESD read from monitor problem that is known to Intel against the GMA950 and a number of other GMA's when using LCD Monitors. It was suppose to be fixed for linux a couple of releases ago, but I saw last night that it's still marked unresolved in their problem lists.

@ALL: I've had enough of the autostartxorg program (whatever it's name is) and i'm going back to doing like BarryK still does and I did to start with in mage2 and have the user setup xorgwizard manually first before going into xwin! Yes, thunor's problem with it is the last straw and 'I'm spitting the dummy', some video chips are ok, others not, etc., etc..

I have received a fix patch for the xorg driver problem from the mageia2 packager concerned, and I have what I consider a good jwm with version 691. I now intend building the next mage2 beta this coming weekend, and will be internally testing next week. Hopefully it should appear the following weekend for wider testing, unless a problem ocurs that is a 'show stopper'. It will be known as mage2-0.0.12.

futwerk · Joined: 07 May 2011 Posts: 337

a couple of new backgrounds.

simargl · Joined: 11 Feb 2013 Posts: 572

scsijon · Posted: Fri 08 Mar 2013, 20:47 Post subject: