 |
 |
|
Ati Radeon Graphics Driver |
|
|
|
|
|
|
| 3d |
|
|
By miqlas - Posted on July 21, 2005 - 16:34:07 (#17283)
Current version when comment was posted: 5.1 |
|
|
Hello!
I found an interresting link:
http://r300.sourceforge.net/R300.php
this is an open source driver for linux with mesa 3d.
Can anyone port this to BeOS/Zeta?
Please!
Thanks!
miq
|
|
| VIVO |
|
|
By Euan - Posted on July 17, 2005 - 00:37:28 (#17228)
Current version when comment was posted: 5.1 |
|
|
VIVO stuff at this moment only works with Rage Theatre 1 based devices. Rage Theatre 2, or 200 don't work yet.
|
|
| Zeta R1 and 9800 AIW |
|
|
By z_eight_a - Posted on July 15, 2005 - 15:37:53 (#17216)
Current version when comment was posted: 5.1 |
|
|
I'm using Zeta R1 and can't get the VIVO features of my 9800 AIW card to work, can someone help me please?
|
|
| Re: battlefield 2 |
|
|
By ModeenF - Posted on July 13, 2005 - 08:57:48 (#17197)
Current version when comment was posted: 5.1 |
|
|
lol no battlefield 2 are linux and windows only..
this are BEOS/Haiku/Zeta driver
|
|
| PCIe? |
|
|
By Euan - Posted on July 13, 2005 - 08:55:51 (#17196)
Current version when comment was posted: 5.1 |
|
|
No idea. Try and get a Syslog. Rudolf of NV driver fame apparently has PCIe stuff working. I guess I can look into that as well sometime this week if I have time.
|
|
| X800 in PCIe |
|
|
By mconrad - Posted on July 13, 2005 - 08:40:40 (#17195)
Current version when comment was posted: 5.1 |
|
|
Does the updated driver for X800 XT support the card in a PCI-e slot? I can't seem to get mine to work and am wondering if that's the issue.
Thanks!
|
|
| . |
|
|
By pmknuke - Posted on July 13, 2005 - 07:18:41 (#17193)
Current version when comment was posted: 5.1 |
|
|
|
| battlefield 2 |
|
|
By pmknuke - Posted on July 13, 2005 - 07:14:12 (#17192)
Current version when comment was posted: 5.1 |
|
|
Can this update help run battlefield 2 ?
|
|
| yup, beshare, zeta, and X800 == lockup |
|
|
By Euan - Posted on July 13, 2005 - 01:36:22 (#17191)
Current version when comment was posted: 5.1 |
|
|
|
| if it works.. |
|
|
By kvdman - Posted on July 12, 2005 - 20:46:35 (#17190)
Current version when comment was posted: 5.1 |
|
|
you should be able to use beshare...lol
|
|
| I have interesting problem with Radeon driver and Zeta |
|
|
By Garjala - Posted on July 12, 2005 - 17:30:17 (#17187)
Current version when comment was posted: 5.1 |
|
|
If I install driver to Zeta I get 2D acceleration ok, but behare chat crashes computer immediately. All other programs work fine (tested almost all games from Zeta etc.) Any ideas? And, yes, crash only happens if driver is installed
|
|
| If you get only 8bit 800x600 it is not working |
|
|
By Garjala - Posted on July 12, 2005 - 17:27:54 (#17186)
Current version when comment was posted: 5.1 |
|
|
If it works, you should be able to select all common screen resolutions. I use 1280x1024x32.
|
|
| Radeon Mobility 7500 |
|
|
By kvdman - Posted on July 12, 2005 - 04:34:16 (#17179)
Current version when comment was posted: 5.1 |
|
|
The newest version of this driver does not work for my laptop and my radeon mobility 7500 M6. When I boot with this driver I am presented with a white haze across my screen, however version 3.2.8 of this driver works fine.
I looked at the device ids, and it seems, this line (which is the ID for my card):
#define DEVICE_ID_RADEON_LW 0x4c57
was under a different section than the /M6's. Sorry I forget which one. So I erased the line where it was and put it under the M6's. I then recompiled the driver.
I have it installed now, and it works, but only in 8 bits and 800x600 resolution.
Did I do this correctly?
|
|
| Experimental driver available for test |
|
|
By Euan - Posted on July 12, 2005 - 01:26:48 (#17177)
Current version when comment was posted: 5.1 |
|
|
Hi all,
I've rewrote my patch for the X800, and have uploaded the address below. Feel free to abuse it. It is a very simple hack that gets round the problem of the new X series cards having a new bios layout. Use it entirely at your own risk. It might work fine on my PC but it might just explode your monitor in to a million pieces. I've never seen it happen but there's always a first time. ;)
The binary drivers:
http://euank.users.btopenworld.com/Radeon_X_series_Experimental_binary.zip
The source code (only bios.c and detect.c changed).
http://euank.users.btopenworld.com/Radeon_X_series_Experimental_patch.zip
PS, I've added the IDs for all known X300s, X600, X700, X800, X850 cards (perhaps not mobility versions though).
PPS no video in, out, left, right...
Goodluck
|
|
| 2 IDs |
|
|
By orbital - Posted on July 10, 2005 - 00:40:34 (#17155)
Current version when comment was posted: 5.1 |
|
|
I believe that there is one device ID per output. The second one is for secondary. My x700 has 5e4b for primary and 5e6b for secondary. Check out http://pciids.sourceforge.net/iii/?i=1002 for a nice list.
|
|
| Zeta seems to use that code too |
|
|
By Garjala - Posted on July 9, 2005 - 22:01:05 (#17154)
Current version when comment was posted: 5.1 |
|
|
It seems that Zeta sees 2 codes for my card, so both numbers are basically correct: the one I said and the one you found. I never realized before that it could use 2 IDs for same card.
|
|
| Almost there... |
|
|
By orbital - Posted on July 9, 2005 - 19:15:58 (#17153)
Current version when comment was posted: 5.1 |
|
|
Garjala, thanks for the files. To cut a long story short, I've tried editing the files but only get to a point where the screen is black with garbled white lines; ironically, only the cursor is clearly seen.
I assumed your device ID was 4a69 but I can't find any reference to it in the radeon2 file. The closest was 4a49, which is also a x800 device ID.
In short, I'm slightly further than I was before. My card is recognised but I just get a garbled display. Before, the monitor just never got a video signal. I'll have another go with the files later.
I've emailed Euan for the sources and he says he's looking for them in his backups.
For anyone else that's also wondering about getting their x600/x700/x800 to work, Euan points out that the procedure requires the adding of the device ID and replacing code which reads PLL values off the BIOS with constants, essentially hardcoding the values.
Anyway, thank you Garjala for taking the time to send me the files.
|
|
| Binaries sent, check your mail |
|
|
By Garjala - Posted on July 9, 2005 - 14:53:14 (#17152)
Current version when comment was posted: 5.1 |
|
|
I just sent the binaries, if email address you gave earlier is valid, you should have it now.
|
|
| Binaries are welcome |
|
|
By orbital - Posted on July 9, 2005 - 13:54:01 (#17151)
Current version when comment was posted: 5.1 |
|
|
Garjala, I'm willing to try the binaries as I can hexedit the device ID, in 'radeon', but leave the other binaries alone.
Thanks.
|
|
| Unfortunately I only have bin version |
|
|
By Garjala - Posted on July 9, 2005 - 10:58:00 (#17149)
Current version when comment was posted: 5.1 |
|
|
Unfortunately Euan sent me only bins, so I do not have sources at all. You can try to mail him and ask if he would be willing to mail them to you and if possible to bebits too (I bet that there are others too who want X600/X700/X800 support)
|
|
| Radeon x700 Pro |
|
|
By orbital - Posted on July 8, 2005 - 23:59:37 (#17144)
Current version when comment was posted: 5.1 |
|
|
Hi all,
I recently installed a Sapphire x700 Pro and can't seem to get BeOS 5 to work with it. I've tried modifying Thomas' sources, adding the device ID (5e4b) and trying to apply the signature (RV410) to the code but none of this works.
I've been reading through the Talkbacks and it seems Euan and Garjala have working drivers for the x800s. I understand that the x700 is of the same family so would one of you be kind enough to send me the source and/or the binaries? (news [dot] replies [at] gmx.net)
I have the BIOS extracted and I'd be grateful if anyone could give me some pointers as to how I can modify the code further, such as the PLLs.
I've been running BeOS 5PE for quite a while now and I don't really want to have to give it up or go back to the VESA mode.
Thank you all.
|
|
| Crashes in Zeta |
|
|
By Garjala - Posted on July 8, 2005 - 21:31:48 (#17142)
Current version when comment was posted: 5.1 |
|
|
Zeta Radeon driver does not support my HIS Radeon X800 Pro vivo, so I tested modded version to which Euan added my card ID. That driver works perfectly in BeOS R5 Pro, but has strange problem in Zeta: if I install it, start Beshare and type some text to chat and press enter whole system stalls totally (happens ONLY with radeon driver installed). No KDL, so I guess that either input_server or app_server crashes (nothing updates after that, not even clock). Any ideas about how I could get rid of this crash? All other apps I have tested work just fine.
|
|
| Got it working (really!) |
|
|
By adamk - Posted on June 25, 2005 - 03:08:49 (#16998)
Current version when comment was posted: 5.1 |
|
|
I had to set the "video format" drop down to "disabled" :-)
Adam
|
|
| Here you go... |
|
|
By adamk - Posted on June 23, 2005 - 23:25:53 (#16976)
Current version when comment was posted: 5.1 |
|
|
As far as I can tell, there are two monitors detected. Here's the full serial debug output:
http://68.44.156.246/beos-boot.log.gz
Adam
|
|
| To Adam... |
|
|
By Tek_No - Posted on June 23, 2005 - 23:23:33 (#16975)
Current version when comment was posted: 5.1 |
|
|
Is your Radeon card detecting your second monitor?
To check this you could enable "debug output to syslog" in your kernel configuration and see if the second monitor is being recognized...
Also be sure to have the second monitor connected to your system before booting the OS...
Take care,
Tek_No
|
|
| Well not quite... |
|
|
By adamk - Posted on June 23, 2005 - 22:59:07 (#16974)
Current version when comment was posted: 5.1 |
|
|
Dualhead doesn't work :-( It refuses to even activate the secondary monitor, which just goes to sleep.
Adam
|
|
| Good job :) |
|
|
By Tek_No - Posted on June 23, 2005 - 16:00:19 (#16967)
Current version when comment was posted: 5.1 |
|
|
Good job, adamk!
Take care,
Tek_No
|
|
| Radeon 9550 working. |
|
|
By adamk - Posted on June 23, 2005 - 14:13:33 (#16963)
Current version when comment was posted: 5.1 |
|
|
FYI, I got the 9550 working. The problem is that I had the wrong device ID... "Devices" listed it as a 4173, but I checked under Linux and there were two display devices listed, one with ID 4173 and one with 4153. It also listed it as an rv350. I plugged that info into detect.c and recompiled. It appears to be working.
|
|
| To vaskas |
|
|
By Tek_No - Posted on June 23, 2005 - 12:32:12 (#16962)
Current version when comment was posted: 5.1 |
|
|
Well, I used the trial version of PowerStrip (see my original fix) to list the "pixel clock".
This is a Windows program though...
Take care,
Tek_No
|
|
| hm.. |
|
|
By vaskas - Posted on June 23, 2005 - 00:24:09 (#16957)
Current version when comment was posted: 5.1 |
|
|
Hi Tek_No!
Changing the datatype from uint to uint32 gave no difference. But the second idea seems to be cool.
But how do I know to what value I need to set the dot clock after I set panel_xres and panel_yres to 1024 and 768 accordingly? ;-)
|
|
| 9550 support? |
|
|
By adamk - Posted on June 22, 2005 - 22:44:25 (#16954)
Current version when comment was posted: 5.1 |
|
|
Has anyone gotten the driver to work with a radeon 9550? The binary doesn't support it, so I tried editing detect.c to add the device ID. I tried it as an r300, rv350, rv360, r350, and r360, but none worked :-(
Any ideas?
|
|
| To vaskas and Philippe |
|
|
By Tek_No - Posted on June 22, 2005 - 00:04:31 (#16938)
Current version when comment was posted: 5.1 |
|
|
Hey guys,
not so easy to give you a decent answer on this one as I can't test this over here :(
It seems to be working for people with a "lower value for the dot clock so (pure guess: didn't check this so far) maybe the dot clock is being stored into a variable whose datatype is not big enough to store the value: to check you could check the .h files to see where the dot clock is being stored in...
Another thing that might work is to force the detection phase to use a lower resolution (panel_xres and panel_yres) e.g. 1024x768 so that you can use a lower value for the dot clock...
Take care,
Tek_No
|
|
| what I've got |
|
|
By vaskas - Posted on June 21, 2005 - 22:42:44 (#16937)
Current version when comment was posted: 5.1 |
|
|
I've come to rs200: the driver worked for exeternal display (I was happy), but not the laptop's. My pixel clock is 122850.
Similar situation to Philippe's. Will be trying myself and waiting for your ideas.
|
|
| To vaskas again... |
|
|
By Tek_No - Posted on June 21, 2005 - 15:27:16 (#16934)
Current version when comment was posted: 5.1 |
|
|
Yes, could be that you need to change another code line (see my trial and error remark) as the one I used was only an example...
Be also sure to try the "Disable BIOS calls" feature on your laptop (see Safe Mode) as this seems to be an option needed for more and more modern laptops...
Take care,
Tek_No
|
|
| also.. |
|
|
By vaskas - Posted on June 21, 2005 - 15:04:29 (#16933)
Current version when comment was posted: 5.1 |
|
|
Even the workaround with bios.c and Pixel Timing doesn't work, still the same vertical geen stripes and horizontal white stripes as well.. I think, then m9 is not the right card type for me and I should go on trying others.
|
|
| bad.. |
|
|
By vaskas - Posted on June 21, 2005 - 14:29:56 (#16932)
Current version when comment was posted: 5.1 |
|
|
Yes, It really seems that the system hangs.
I've tried to connect an exeternal monitor (17" BenQ TFT) and it turns off and produces the "No input signal" after the icons are passed and BeOS is going to swith to graphical mode :-(
|
|
| For Tek_No.. |
|
|
By vaskas - Posted on June 21, 2005 - 14:00:48 (#16931)
Current version when comment was posted: 5.1 |
|
|
I've done the things you described.
Corrected the value to 0x5835 and so on.
Unfortunately, after all the icons are passed by my Dano, the display flashes with vertical green stripes, and it seems that the whole system hangs ;-((
Thank you for the help by the way ;-)
|
|
| To vaskas... |
|
|
By Tek_No - Posted on June 21, 2005 - 12:37:19 (#16929)
Current version when comment was posted: 5.1 |
|
|
At first look your card ID is NOT included in Thomas's supported card list so this could be good ;)
What you could try to do is to add your card to that list. Have a look at my previous talkback (the one with the fix for the pixel clock): in there I'm editing and changing the "bios.c" file.
To add you card ID to the list you don't need the "bios.c" file but the "detect.c" file which can be found in the same folder as the "bios.c" file.
First make a duplicate of "detect.c" for backup purposes.
Open "detect.c" in e.g. StyledEdit and have a look at the code: you'll see lines like:
{ 0x4c66, rt_m9, "Radeon Mobility 9000 Lf" },
As we don't know what exactly your Radeon 9000 is based on we need to use "trial-and-error":
change e.g. the above line to read:
{ 0x5835, rt_m9, "Radeon Mobility 9000 Lf" },
Now follow all the other steps I described in my other talkback:
- save and exit "detect.c"
- open the Radeon .proj file
- ALT-U to update project file
- ALT-M to make driver
- exit project file
- copy Radeon driver to the linked folder
- reboot and check
As already said: we don't know if your Radeon is a rv250, m9, rv280, ... based on so we need to use trial-and-error and maybe (probably) need to change another codeline to reflect your card in case your card is not being picked up correctly...
Hope all this makes some sense to you ;)
Take care,
Tek_No
|
|
| Re: To Philippe: Asus laptop? - result |
|
|
By Philippe Houdoin - Posted on June 21, 2005 - 10:07:33 (#16924)
Current version when comment was posted: 5.1 |
|
|
## did you already have the chance to check
## this out on your Asus laptop?
#
# Chance? Several of them!
# Time? No. Not yet.
#
# But be sure I'll ASAP.
I checked last night.
Alas, didn't worked.
I guess it's because my pixel clock, 120706 (1680x1050@60Hz :-) ) is higher than expected by other PLL logic somewhere in the driver and/or accelerant, so forcing the fp timing doc clock value didn't fix it alone.
Time to run diff xfree86 radeon driver code with Thomas's one...
# Is this working for you or not?
Can't tell yet but it looks like a good workaround allready.
When I looked at the code, I've felt that was an issue somewhere in the clock multipliers and/or BIOS flat setup reading.
I guess BIOS clock setting is no more express per 10, but some bit indicates somehow we must multiply (or not) the pixel clock reg value... :-|
Nice job done, Tek_No.
|
|
| That's what I've got.. |
|
|
By vaskas - Posted on June 21, 2005 - 09:33:37 (#16922)
Current version when comment was posted: 5.1 |
|
|
Hi, Tek_No!
My Card ID is 5835
|
|
|
|
|
|
|
|
|
 |
|
|
|
|
|
|
|
|
 |
| |
Recent Downloads - # 2
Total Downloads - # 2
Total Views - # 2
User Ratings - # 629
|
|
|
|
 |
| |
Video Drivers
|
|
|
|
 |
|
1. BePodder - 9.80
2. QEMU - 9.68
3. ScummVM - 9.57
4. cpu_fix - 9.42
5. Jukebox - 9.40
6. libdl.so - 9.40
7. Haiku AGP busm... - 9.35
8. vim6 - 9.31
9. Beezer - 9.26
10. HandBrake - 9.25
|
|
|
|
 |
|
1. BeOS 5 Perso... - 13,605
2. Realtek RTL8... - 13,115
3. Ati Radeon G... - 12,584
4. Ensoniq Audio... - 7,566
5. ATI Rage 128... - 7,442
6. USB Joystick... - 5,665
7. Broadcom 440x... - 5,411
8. S3 Trio 64 v2... - 4,727
9. USB Serial dr... - 4,708
10. Intel Extreme... - 4,471
|
|
|
|
 |
| You are not logged in.
Login
|
|
|
|
 |
|
