puppy 4.3beta2/3 Ati Catalyst 9.9 graficsdriver

[MU]

# modprobe fglrx
FATAL: Module fglrx not found.

This just should happen in two cases:
1.) you use a Puppy with a different kernel.
To test that, type:
uname -r
This should return:
2.6.30.5

2.) Not enough diskspace
The pet installs a huge archive:
/usr/local/graficsdrivers/atilatest.tgz
Do you have that? It is around 30MB.

If yes:
3.) when you run xorgwizard and choose the Ati driver, that archive is extracted.
This creates (beside others) the file:
/lib/modules/2.6.30.5/kernel/drivers/char/drm/fglrx.ko
Do you have that?

If not, then something went wrong with extraction.
Maybe not enough free diskspace?
What do you get please by typing:
df -m

If you DO have that file, then it was not properly registered to the kernel. In that case, please type:
depmod -a
and exit X and run xorgwizard again.

Please let me know your results, so that I can fix it in the pet, if it contains any error.
Mark

[Flash]

Just for fun I went ahead and installed the .pet again, but before I could post Xorg.0.log my system froze so solid the only way I could get it to work again was a hard reboot.

So I did it again.

Yes, I have the file /usr/local/graficsdrivers/atilatest.tgz

Yes, I have the file /lib/modules/2.6.30.5/kernel/drivers/char/drm/fglrx.ko

# uname -r
2.6.30.5
#

# df -m
Filesystem 1M-blocks Used Available Use% Mounted on
tmpfs 1599 115 1485 8% /initrd/pup_rw
tmpfs 1599 7 1593 1% /initrd/pup_ro1
tmpfs 103 102 1 100% /initrd/mnt/tmpfs
/dev/loop0 102 102 0 100% /initrd/pup_ro2
unionfs 1599 115 1485 8% /
#

I ran depmod -a then reran xorgwizard, with this result:

# modprobe fglrx
FATAL: Error inserting fglrx (/lib/modules/2.6.30.5/kernel/drivers/char/drm/fglrx.ko): Cannot allocate memory
#

[MU]

ok, I see:
your log tells me:

(--) PCI:*(1:5:0) ATI Technologies Inc ATI Radeon Xpress 1200 Series rev 0,

The 1200 is not supported by driver 9.9, only by 9.3.
But as explained in the first message, the 9.3 works erratic with Kernel 2.6.30.5.
You might get a correct resolution, but the driver will crash with 3D applications.

An alternative for that chip might be the free Xorg drivers:
http://www.murga-linux.com/puppy/viewtopic.php?t=46266

But I don't know, if the 1200 has 3D support with those free drivers.
If you want to try those, do it ONLY with a new savefile, as they overwrite Puppys existing xorg with an incompatible version.
That free driver pet is only intended for those cases, where everything else fails.

Mark

[MU]

oh yes, and if you want to use xorg again with the vesa driver, just run xorgwizard, and choose "xorgwizard - force vesa".

This will extract working opengl drivers.
You then have no accellerated 3D, but at least such applications should no longer crash (they just run slow then).

Without this, you would run a mix of catalyst and free Xorg libraries.

Mark

[Flash]

Okay, Mark. Thanks for all your trouble.

Since I'm running Puppy from a multisession DVD I'll just shut down without saving. Next time I boot, I'll be back to Xvesa.

I'll give the free Xorg drivers a try next.

[Philh]

Flash
Is your monitor displaying at 1280x1024 with xorg set to 1440x900
If so have you tried modelines
See my post here
http://www.murga-linux.com/puppy/viewtopic.php?t=47572

Though I dont know if it will work with your graphics chip.

[Flash]

Thanks, Phil. I haven't tried your method yet, but I'll keep it in my back pocket. (By the way, how do I tell the actual resolution that's being displayed?)

I discovered Patriot's post of Xorg driver updates. It looked a lot simpler to try his new ati driver than to edit various files by hand, so that's what I did first.

It seems to have worked. After installing the new ati driver I ran xorgwizard and chose 1440 x900, then adjusted the image of the LCD screen. Now all the icons are safely visible and everything that's supposed to be round is round.

[Philh]

On my monitor When I press the menu buttons to change brightness or anything it displays what resolution it is set to.
Ive found it works as far back as 216. Once you have the values its just a matter of copying into xorg.conf whenever you need to.
But good to have other ways.

[exProphecy]

What version of Catalyst do I use for my ATI Radeon Mobility x700? I'm using 2.6.30.5 kernel.

[Flash]

What version of Catalyst do I use for my ATI Radeon Mobility x700? I'm using 2.6.30.5 kernel.

I recommend that you try Patriot's ati driver first. Mark's is a big boy (around 30 MB if I remember.)

Just make sure you can go back if it doesn't work for you. One way to do that would be to boot from live CD with "pfix=ram" boot option so Puppy doesn't use your save file. Then download and install the driver so you can play with it. If it works to your satisfaction, reboot and install.

[exProphecy]

What version of Catalyst do I use for my ATI Radeon Mobility x700? I'm using 2.6.30.5 kernel.

I recommend that you try Patriot's ati driver first. Mark's is a big boy (around 30 MB if I remember.)

Just make sure you can go back if it doesn't work for you. One way to do that would be to boot from live CD with "pfix=ram" boot option so Puppy doesn't use your save file. Then download and install the driver so you can play with it. If it works to your satisfaction, reboot and install.

Oh okay but.. which one should I use? hehe

I tried MU's but it did not work. I didn't expect it to because he said it was for NEWER cards so yea

[panzerpuppy]

@MU: WOW

(read the next post)

[panzerpuppy]

Catalyst 9.10 is out and it brings something GREAT for all RadeonHD users:

XvBA video acceleration through VA-API

You need the latest XvBA .deb package from here:

http://www.splitted-desktop.com/~gbeauc ... vba-video/

and a modern RadeonHD video card (Radeon HD4000 series is highly recommended)

Software supporting VA-API currently includes MPlayer, FFmpeg, and the Helix media player.

XvBA works only with Catalyst 9.10 or higher.

XvBA backend for VA API supporting the following codecs:
- MPEG-4 AVC (H.264)
- Windows Media Video 9 Advanced (VC-1 Advanced profile)