In my Slacko tests I did find that this can conflict with some other xorg drivers. It is included in Slacko but it is hidden away in /usr/lib/x with possibly other alternate drivers. There is a problem (bug) with that approach though as xorgwizard does not know about the modesetting driver. Consequently, it is not moved to /usr/lib/xorg/modules/drivers and so is unavailable to xorg.

I am going to add a case to xorgwizard that handles this scenario such modesetting is moved if chosen. Possibly udev rules should be written that on the detection of a cedaview or poulsbo graphics card that the modesetting driver is automatically moved. Jury is out on that one. I am already doing preliminary work on this.

pemasu, sorry for brief off topic here...

@ aarf, who unfortunately can't post here. Good you got modesetting to work in Upup with RoDoN's compile. Regarding Slacko, you must uninstall the Upup version. Then run this command

01micko. Thank you of the input. Intel gma 500 (Poulsbo), gma 600, gma 3600 (Cedarview) and 3650 (Cedarview) which uses gma500_gfx.ko and can use xorg modesetting driver have been troublesome PowerVR based graphics.

The graphics support in linux is only usable. No 3D acceleration. But it is better than nothing and intel atom based notebooks are not for power hungry usage anyway.

If you can edit xorgwizard so that gma500_gfx.ko can be used with included xorg modesetting driver, it would be great thing for these intel atom comps with above gma graphics.
Xorgwizard handled xorg driver translocation from alternate to normal location so that the xorg modesetting driver would be in use would be great.

I would include that xorgwizard of course to my builds. Thanks of your initiative. And thanks to aarf who brought this need to my attention. I didnt know of the work done in Slacko. Now I know.

I am still quite newbie for compiling ati-amd-fglrx-drivers for petting. But...I have learnt to compile and create them inside extracted ati folder and have learnt to patch the kernel module source before running the installer. So....these might even work.
I created ati-12.10 pet for modern graphics, like mine. Tested the pet with my dual graphics. And then I created ati-12.6-legacy pet.

Cave out. For me suspending does not result working waking up.
There is ati own fixes for that inside: /usr/share/doc/fglrx/examples/etc
You can try to copy the stuff to right places and test them. I havent had time to do so....maybe next time when I boot with ati and watch movies through hdmi from my 42 inch lcd tv. Then I have a reason to try them with suspending.

I created quickpet for this 3.7.2 kernel version. Under drivers sections you find those ati-amd-fglrx pets and also newest nvidia 310.19 pet.

They are in upup repo, so those who want to scan it...find them there. Nvidia 310.19 is there as sfs also. You can download it with Precise sfs downloader also...There are now quite many ways to install stuff...

Further to gma/poulsbo/cedarview issues I have patched xorgwizard to move the modesetting driver from the alternate location to the real location where Xorg can find it, I have also patched xorgwizard-automatic to move the modesetting driver if it detects one of these cards based on device ID, now my database may be incomplete, I don't know. But if your machine is over 6 months old it will almost certainly be listed. Newer ones might be too.

I have not packaged this as a pet as it is only if you have an intel atom infected with the gma 500 (Poulsbo), gma 600, gma 3600 (Cedarview) and 3650 (Cedarview) which uses gma500_gfx.ko.
The package is structured just like a pet to easily merge into the filesystem. The packages contains: a patched /usr/sbin/xorgwizard, a patched /usr/sbin/xorgwizard-automatic and a new script called xcedarview.sh, called from xorgwizard-automatic.

If you know what you are doing you can do it with no X. Ideally that's how it should be done, but for testing purposes there are 2 things to test.

1.drop to prompt (yau may already be there ) and run xorgwizard
Choose the "modesetting" driver, start x with xwin

2. From the prompt delete or move /etc/X11/xorg.conf
If you have ordinary Intel a test will be performed to see if you have a gma device and you will be informed. If you have the device you will then be informed that "modesetting" driver is moved to it's proper location or if it's not there then a "NOT FOUND" message occurs. .

This is RoDoN's pet just moved. Why is this necessary? Well .. if you have an nvidia and use xorgwizard then it's "modesetting" gets chosen and X crashes unrecoverably! That's why I moved in the first place.

01micko. Thanks !!!
I will check them out soon. What do you think of the poulsbo.ko stub driver. It might inhibit the use of gma500_gfx.ko and modesetting driver.
Would it be still reasonable to blacklist it in the build with MODULESCONFIG ?
Post edited because RoDon above answered it already.

Heh. RoDon beat with 2 seconds. Congratulation. You won ice cream. I will fax it to you.Last edited by pemasu on Tue 15 Jan 2013, 02:18; edited 2 times in total

Yes RoDon is correct, I should have mentioned that. My next slacko will be with out it (only k3.3x and above exhibits this, there is a test for it in my xorgwizard-automatic)._________________Puppy Linux Blog - contact me for access

I am still quite newbie for compiling ati-amd-fglrx-drivers for petting. But...I have learnt to compile and create them inside extracted ati folder and have learnt to patch the kernel module source before running the installer. So....these might even work.
I created ati-12.10 pet for modern graphics, like mine.

And mine, too (Radeon HD5450 card).

Ran your ati pet and then downloaded the ~50MB driver package with no problem.
I installed first to a Frugal Upup-3.7.2 with a 256MB save-file. A red warning about the save-file remaining (~80MB) and I increased the save file size to 512MB for next boot. But the new driver did load and run well after I did the 'aticonfig --initial' step and restarted X.

But on shutting down to 'reboot' there was a problem - the computer did not shut down and the text displayed seemed to be part of the start up messages and the computer hung. I hit the 'reset' button and re-booted the Frugal-3.7.2 which started up with the ATI driver and a good display. Shutting down now went as expected with no strange message or hanging.

I then installed the ati-fglrx driver on my Full Upup-3.7.2 with the same result. Good install, good initial display, but again hanging on trying to reboot the first time; 'reset' and re-booting to the Full Upup and everything was good.

Hi,
@keef
thanks again for your post !
I presume it would no longer be necessary to compile the xf86-input-acom driver ... related to the present distro as also puppies with «new» kernel as uPup-54X7 and dPup-Exprimo-3.6.2, and maybe others!
Please consider and readhttp://www.murga-linux.com/puppy/viewtopic.php?p=677882#677882
I suggest we to continue posting about wacom subject in the thread Forum index/House Training/Howto/«How to set up a Wacom Tablet».
Hope this helps
CharlieLast edited by charlie6 on Tue 15 Jan 2013, 12:49; edited 1 time in total

I compiled TurionPowerControl and then added my usual p-state voltage configuration via rc.local. It is working perfectly, thanks for cpuid and msr.

Amazingly, almost immediately you have posted a fglrx legacy .pet. I have installed that and it is worked with no problem.

I notice that it does not install the GLX stuff which I thought ATI pets normally do. I don't play 3D games, so I don't need it. I expect I could install it from the Ubuntu repo.

Maybe other Puppies come with GLX installed, and I haven't noticed. The r600g has it built-in.

If this is not the expected behaviour, please tell me and I will investigate the log files further.

My main interest is playing pack my MPEG video recordings. Now I can try installing the latest XBMC-XVBA package from the wsnipex PPA on launchpad. Then I can compare it with software decoding using VLC and the Xorg r600g driver.

LateAdopter and davids45. There was missing files. My way to create packages seems to miss some installer stage. fglrx_dri.so was placed to wrong location. Also some other scripts and files were missing.

I tested the reuploaded ati pet and it should work now. Suspending started to work for me, radeon will be blacklisted, dri has been enabled.
I have reuploaded both ati pets. Oh yeah...ati-12.6 legacy fglrx.ko needed heavy patching. It is possible that the fglrx.ko kernel module is defective due to that heavy patching. Kernel 3.7 might still miss some crucial patch. Time will tell...
I cant test 12.6-legacy pet. I dont have suitable ati card.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum