new ATI drivers 8.16.20 do not allow for 1280x800

ckenda1 · Tux's lil' helper Joined: 19 Feb 2004 Posts: 126

Just a FYI for all you WS laptop users out there. The new ATI drivers (8.16.20) apparently do not allow for a screen resolution of 1280x800 anymore. ATi did this with the windows driver a while back, by removing this mode.

I do however have the 1280x800 running with 8.14.13-r2 and kernel 2.6.12.r9. Full with 3D acceleration.

If for some reason I am mistaken about the 1280x800 res and someone does have it working with 8.16.20, please share your knowledge.

Thanks!

RR64 · n00b Joined: 06 Aug 2005 Posts: 34

ckenda1 · Tux's lil' helper Joined: 19 Feb 2004 Posts: 126

kernel 2.6.12-gentoo-r9 .config
xorg.conf (ati-drivers 8.14.13-r2)

Check to see what version of ati-drivers will be installed

peralta_jm · n00b Joined: 24 Aug 2005 Posts: 5

Well, I have installed the new ati-drivers (8.16.20) on my HP zv6000 laptop and they are working fine -WITHOUT 3d acceleration (

RR64 · n00b Joined: 06 Aug 2005 Posts: 34

ckenda1 - Still no go

. I even went as far as to use the same kernel as you. I have the gentoo-2.6.12-r6 kernel. Any other ideas or info you would need?

I'm very sick of this:x. I'll keep trying to find something that works on my laptop. Hopefully ati will release a driver in the next two months that will alleviate this. The only thing that stopped me from buying the last model before this is I kept telling myself that this laptop will soon become fully support with no patches needed.

_________________
OLD SETUP
Hp zv6130us laptop
AMD64 Athlon 3200+
80g Harddrive
512 ddr ram
ATI Radeon Xpress 200M 128 dedicated memory
64bit OS gentoo-2.6.12-r9

Newsetup to be posted as soon as its running

hijjt · n00b Joined: 15 Oct 2003 Posts: 9

Well I have had crazyness in the past with this and find that it goes much easier with the x86_64 version of gentoo than the 32bit version, I have had both workin at one point or another.

One thing you have to make sure of is the AMD Opteron/Athlon64 on-CPU Gart support is set in your kernel along with your AGP Chipset if you are using a 32-bit gentoo install. Ati drivers are really strict about how you configure AGP. I find that it is hit and miss with choosing either module or compiled in.

64-bit I didn't do anything special and it basically worked, I have never had any luck using the AGP GART that is included with the Ati drivers so I always use the kernel ones.

The 32-bit drivers didnt work with the 2.6.12 kernel GART in the 8.14 series drivers as far as I know.

lelik · Posted: Thu Sep 01, 2005 8:22 pm Post subject:

peralta_jm,

I have very similar notebook (Compaq R4025 with ATI MOBILITY RADEON Xpress 200). I am struggling to get DRI working since kernel 2.6.11 and ati-divers-8.13.3 (I remember it working, but now I start doubting myself).
Ati-drivers 8.13.3, 8.13.4 and 8.16.20 all work with kernel 2.6.12 and dri disabled.
Ati-divers 8.14.3, 8.14.3-r1, 8.14.3-r2, 8.14.3-r3 will not work at all.
:cry:

I even was ready to downgrade my kernel to 2.6.11, but it disappeared from portage.
:evil:

Anyone got the DRI working for the Xpress chip?
A..N..Y..O..N..E..?

Eagle3386 · Posted: Wed Sep 28, 2005 3:24 pm Post subject:

Yes, I got my Laptop (Fujitsu-Siemens Amilo A 1650, AMD Athlon64 3700+, ATI Xpress 200M-chipset) working with DRI!

Solution is simple, but it takes a little bit of time.. - Anyway, Id like to share my knowledge and give you a manual for getting it to work:

First of all, do this to get your PCI-ids up-to-date:

ronc · n00b Joined: 08 Jun 2004 Posts: 70

I'm using a zv6000 laptop, with the Radeon card. I went through your procedure, but it didn't work for me. I'm not quite sure where it went wrong. I was able to emerge the right ati-drivers ebuild (but I had to edit /etc/portage/package.keywords to include but the specific ati-drivers build, as well as eselect-opengl-1.0.2-r1 and eselect-0.9.6).

I did notice a !! warning as the packages were being built, something about DRM not being enabled. Is there any way you could post your kernel configuration file online so that I can try it again? Something else that may be useful would be to post the xorg.conf file as well. Someone else had done so (earlier in the thread) but the link to the xorg.conf file is broken.

Eagle3386 · Posted: Thu Sep 29, 2005 10:57 pm Post subject:

Yes, thats true.

I had almost forgotten that theres this DRM-problem..

Anyway, AFAIR those ati-drivers give you ati-powered DRM and therefore the DRM-part of Xorg has to be disabled.

Posting my logfiles isnt a problem - so here well go!

First, my xorg.conf - Im posting the WHOLE file:

ronc · n00b Joined: 08 Jun 2004 Posts: 70

First, thank you very much for the help. I appreciate it.

Second, it didn't work. I emerged gentoo-sources 2.6.13-r2, compiled the kernel with your .config file, and rebooted. Then I copied your xorg.conf file to /etc/X11/xorg.conf and ran startx. What I got was a parse error from the xorg.conf file at the last line. This is the puzzling part, because it said that "ice" was not a valid option. I looked in your file, and online, looking for where "ice" was a stated option, and didn't find it.

Am I missing something?

By the way, with your kernel config, PCMCIA ins't working. Is it working for you?

Thanks again.

Eagle3386 · Posted: Fri Sep 30, 2005 11:52 am Post subject:

First of all: I've opened a bug at bugs.gentoo.org to get the 8.16.20-drivers at least at the "testing"-section of the portage-tree..

Secondly, I'm quite confused about that it didn't work for you.
Maybe you copy the xorg.conf-text once again - also look if you're using KDM as your login-manager.
Several other settings might need to be changed, too..

To be honest: ATM I'm not using PCMCIA because of that I don't even have a PCMCIA-card.
Nevertheless I'm going to buy a TV-card for the PCMCIA-slot in the nearer future.

Therefore I'd like to know why do you think my PCMCIA isn't working and - of course

- I'd like to recieve some suggestions about fixing it..

Thanks a lot in advance,

Martin..

_________________
One. Life. Live. It.
««««««»»»»»»
Proudly translating Kuroo for German users.
(Yes, I'm giving back what the community greatly offers to me.)

ronc · n00b Joined: 08 Jun 2004 Posts: 70

I got X to work. My bad. Your code was good, my transcription wasn't. I corrected the error on my end and X fired up as it should.

The problem with PCMCIA is with the yenta driver. The kernel compilation fails if you have the yenta driver compiled in. This didn't happen with the 2.6.12-gentoo-r10 kernel. That is why I'm a little surprised with the results on this kernel.

With the 2.6.12-gentoo-r10 kernel, all I had to do was compile in all the options for the PCMCIA bus, and voila, everything worked. Not so with the later kernel.

That's okay, like you, I'm not using the PCMCIA bus right now, but unlike you, I don't have plans to use it.

By the way, did you get wireless working? I'm having trouble loading the right 64-bit driver for the wireless card using ndiswrapper.

Eagle3386 · Posted: Fri Sep 30, 2005 2:45 pm Post subject:

Well, was it a typo or something you had to change?

(I'm just interested in what the bug was..

)

What about this yenta-driver? - And the most important question:
If you say, that driver doesn't work, why didn't the compile-procedure give any error?! O.o

Also, I'd like to know if you got any tip for me how to fix this?

The ndiswrapper is the "next big thing" I'm going to do.
Nevertheless, I searched at gentoo-wiki.com and found something for you (scroll down the page till "4.4 Ethernet Card Configuration"):

http://gentoo-wiki.com/HARDWARE_Gentoo_Linux_64bit_on_HP_Pavilion_zv6000_series_notebook

This should do it, right?

_________________
One. Life. Live. It.
««««««»»»»»»
Proudly translating Kuroo for German users.
(Yes, I'm giving back what the community greatly offers to me.)

peralta_jm · n00b Joined: 24 Aug 2005 Posts: 5

Hi. I also spent quite a while trying to get my xpress 200M working with DRI. I finally got it working after I found a post in a forum of HP zv6000/Compac R4000 owners.

Check my post on this thread to find how I got this stuff working:

https://forums.gentoo.org/viewtopic-t-327001-highlight-sideport.html

ronc · n00b Joined: 08 Jun 2004 Posts: 70

The "bug" believe it or not was the line:

### EOF ###

I didn't take that out the first time. I didn't feel the need to because it started with a # character. However, the next morning (bright and refreshed) I noticed the line, and decided to take it out (as it wasn't necessary, obviously). Then X fired right up.

Eagle3386 · Posted: Fri Sep 30, 2005 3:00 pm Post subject:

Hehe, great!

But anyway, if this happens, another "EOF" must be present in the file. Because if not, X would fail..

(Therefore I think you didn't replace the file, but insert the text from my post..

)

Last (but not least

), I'd still like to know if you got any ideas on how to fix my PCMCIA-problem?!

And is the How-To from gentoo-wiki.com working for you?

_________________
One. Life. Live. It.
««««««»»»»»»
Proudly translating Kuroo for German users.
(Yes, I'm giving back what the community greatly offers to me.)

ronc · n00b Joined: 08 Jun 2004 Posts: 70

I think the problem with PCMCIA lies with that yenta driver. If you would be able to compile in the yenta driver, you wouldn't have any problem. Incidentally, that is the only driver not compiled into my 2.6.13 kernel -- and I have PCMCIA problems. The exact same settings (except that the yenta driver is compiled in) with my 2.6.12 kernel, and PCMCIA works fine.

Once 2.6.13 compile doesn't caugh with the yenta driver, you'll be in PCMCIA heaven (or at least nirvana). I suspect that there is a bug track on the yenta driver problem with 2.6.13 (or at least there should be). I did get a compilation error issue when I tried to compile in that driver.

ronc · n00b Joined: 08 Jun 2004 Posts: 70

I found the HOW-TO from the Gentoo Wiki for the zv6000. In fact, it was the presence of that HOW-TO that encouraged me to purchase the machine. I had hoped it wouldn't be this much trouble. However, I tried Umbutu (which never could fire up X correctly) and Fedora Core (which is easy to load, but broke down when I tried to load gcc from the CD's). All that reminded me of why I like Gentoo.

Eagle3386 · Posted: Fri Sep 30, 2005 3:39 pm Post subject:

Well, then I'll try and if any error occurs, Bugzilla at bugs.gentoo.org is waiting for me..

I came to Gentoo because Mandriva 2005 didn't work (installed the full dvd 2 or 3 times but the system got always a kernel panic.. O.o) and the first time, I wanted Gentoo with Stage 1 - now, that my system is up (I used Stage 3 with genkernel

) and everything works well, I must say that the whole bunch of comands (starting with Stage 1 and doing the bootstrap) was useless.

Just get genkernel, do the Stage 3-procedure and if Gentoo boots correctly, start building your own kernel and add the stuff you need step-by-step.. - Doing it this way is more comfortable and saves *many* nerves..

_________________
One. Life. Live. It.
««««««»»»»»»
Proudly translating Kuroo for German users.
(Yes, I'm giving back what the community greatly offers to me.)

Eagle3386 · Posted: Fri Sep 30, 2005 3:52 pm Post subject:

Oh, I almost forgot a big question of mine:

How to change my refresh rate to *more* than 60 Hz - KDE won't let me choose *any* other refresh rate except that one.
Under Win2k, my LCD-panel (notebook-builtin

) can be used at even 85 Hz!
_________________
One. Life. Live. It.
««««««»»»»»»
Proudly translating Kuroo for German users.
(Yes, I'm giving back what the community greatly offers to me.)

ronc · n00b Joined: 08 Jun 2004 Posts: 70

You know, that is a good question. Unfortunately, I don't know the answer to that.

By the way, do you have a zv6000? If so, how is the battery life on yours? Mine only last about 30 minutes (just sitting there, not really doing anything). It is less than 15 minutes if I try to compile a kernel or something like that. In short, I have to use A/C power all the time.

ronc · n00b Joined: 08 Jun 2004 Posts: 70

I think you mentioned that you got KDE working, right? Did you have any masking issues with ivman? I didn't with hal and dbus, just with ivman.

Eagle3386 · Posted: Fri Sep 30, 2005 5:53 pm Post subject:

That's bad.. - I searched via Google and asked many people, but noone has a solution..

Anyway, to answer your question about my laptop: as already mentioned in my first post in this topic, I'm using a Fujitsu-Siemens Amilo A 1650 with an AMD Athlon64 3700+ (Clawhammer-core).

Nevertheless I will *NEVER* (I repeat: N-E-V-E-R) buy a notebook from Fujitsu-Siemens again!
Why? - Because of this &%#!?@-support, the &%#!?@-battery-lifetime and last (but *really* not least) the bad keyboard-design.

To make it clearer:

Support is a piece of crap - you'll have to write mails more than 3 times to get *ONE* answer.
Battery is (official stated) empty after ~2.5 hours - this is due to the fact that the battery has only 6 cells, but notebooks from i. e. Acer got 8 or even 9 cells and they last (official stated) ~4.5 hours.

And even loading the battery is horror: Fujitsu-Siemens claims that the battery takes ~4.5 hours of loading (notebook *not* powered off!) - while I can use it with battery only ~2.5 hours. This deal is a piece of shit and not more.
(Sorry for the "bad" words, but this *really* sucks!)

The keyboard itself is bad, because if I want to press "Pos1" or "End", I'll have to press "FN" + "PgUp" / "PgDn".
(And the "greatest" thing is, "Del" is at the top-right, but "Pos1" / "End" is at the bottom right.. :roll:

)

The next notebook is an Acer - I swear!

The thing with KDE is working correctly, also that "auto-mount-via-dbus-hal-ivman"-thing.
But to be honest, trying to do this *without* KDE (= using that dbus-hal-ivman-thing in the console after shutting down / before booting up KDE) results in a kernel panic (at least it did so twice..

).
Maybe I'll fix this, but for now, I'm using KDE for this..

I followed this How-To: http://gentoo-wiki.com/HOWTO_ivman
_________________
One. Life. Live. It.
««««««»»»»»»
Proudly translating Kuroo for German users.
(Yes, I'm giving back what the community greatly offers to me.)

ronc · n00b Joined: 08 Jun 2004 Posts: 70

The wiki suggested that I unmask the packages as needed. However, I ran into the problem where:

- sys-fs/cryptsetup-lucks-1.0-r1 (masked by: missing keyword)
- sys-fs/cryptsetup-lucks-1.0.1 (masked by: ~amd64 keyword)
- sys-fs/cryptsetup-lucks-1.0 (masked by: missing keyword)

The ~amd64 keyword issue was remedied easily by adding a line to /etc/portage/packages.keywords. However the portage manual says to start a bugzilla on the other "missing keyword" entries.

As an alternative, I emerged gnome. However I couldn't emerge xdm. Right now, I'm in the process of depenency unmasking/keywording hell.