| Author |
Replies |
| ovisan |
Thursday 7 June 2012 at 14:39 |
| Rank: Member
|
Also with this patch it freezes the system while playing. All i can do is reboot, nothing else responds. Maybe you should look into that ATI fix, before Blizzard patch 1.0.2 it was working nice. Seems now it can be also related to the ATI fix, please check it.
My specs: Ubuntu 12.04 x86-64, latest playonlinux
ATI Radeon HD 6770 |
| Quentin PÂRIS |
Thursday 7 June 2012 at 14:45 |
| Rank: Admin
|
Can you send the log while freezing? |
| ovisan |
Thursday 7 June 2012 at 14:49 |
| Rank: Member
|
It's freezing my entire system and i need to reboot my PC. If there's a log stored somewhere, please tell me the location and i'll gladly forward it :-)
Thanks for this. |
| Quentin PÂRIS |
Thursday 7 June 2012 at 14:50 |
| Rank: Admin
|
PlayOnLinux tools menu -> Virtual drive (second part) -> DiabloIII |
| ovisan |
Thursday 7 June 2012 at 14:59 |
| Rank: Member
|
Sent the log trough mail, 6.6 MB...
Thank you, please let me know what's wrong. |
| Obsi |
Thursday 7 June 2012 at 15:05 |
| Rank: Guest
|
That's my log, same issue here :/ some ideas?
-1.-1.-1.-1",
"playable" : true
}
Firing Event: "database flush event"
Handle Event: "database flush event"
Request Issued: GET /version/diablo3_itit
Response: 200
{
"state" : 1004.000000,
"local_version" : "1.0.2.9950",
"playable" : true
}
Request Issued: POST /update
{
"monitor_pid":62,
"uid":"diablo3_itit"
}
Database Insert: /update/diablo3_itit
Response: 200
{
"response_uri" : "/update/diablo3_itit",
"result_uri" : "/game/diablo3_itit"
}
Firing Event: "database flush event"
Handle Event: "database flush event"
Request Issued: GET /update/diablo3_itit
Response: 200
{
"state" : 1004.000000,
"playable" : true,
"progress" : 100.000000,
"download_rate" : 0.000000
}
Request Issued: DELETE /update/Client
Database Remove: /update/Client
Deferred delete of 'async_task' Resource
Queue 'async_task' Resource for delete
Response: 200
{}
Request Issued to non-existent Uri: GET - /gamesession/diablo3_itit
Response: 404
(null)
Request Issued to non-existent Uri: GET - /backfill/diablo3_itit
Response: 404
(null)
Removing uri "/update/diablo3_itit" since it has no process interested in it.
Re[06/07/12 14:50:22] - Running wine-1.5.5-DiabloIII_v3 Diablo III Launcher.exe -opengl
Argument[0]: 'C:/users/Public/Application Data/Battle.net/Agent/Agent.998/Agent.exe'
Argument[1]: '--locale=itIT'
Agent is running as Administrator.
Database Insert: /option
Database Insert: /agent
Database Insert: /
Database Insert: /version
Database Insert: /repair
Database Insert: /update
Database Insert: /game/diablo3_itit
Database Insert: /install
Database Insert: /gamesession
Database Insert: /backfill
Database Insert: /game
Database Insert: /game/client
Database Insert: /spawned
Database Insert: /agent/download
Database Insert: /register
Initialize HttpProtocol Server Called.
Agent started on port #6881
Executing operation: disable_firewall applicationPath="C:\users\Public\Application Data\Battle.net\Agent\Agent.998\Agent.exe" applicationName="Blizzard Agent"
AgentAsAdmin failed to add a firewall exception for 'C:\users\Public\Application Data\Battle.net\Agent\Agent.998\Agent.exe'.
Registered Periodic Event: "auth validation event" with a resolution of 10000 and a start delay of 10000
Registered Event: "shutdown event"
Registered Event: "database flush event"
Request Issued: GET /agent
Response: 200
{
"update" : {},
"install" : {},
"backfill" : {},
"pid" : 43.000000,
"state" : 1007.000000,
"version" : "1.0.0.998",
"type" : "retail",
"authorization" : "E04920D8AA35BE15E9D412CCF1763872"
}
Request Issued: GET /agent
Response: 200
{
"update" : {},
"install" : {},
"backfill" : {},
"pid" : 43.000000,
"state" : 1004.000000,
"playable" : true,
"version" : "1.0.0.998",
"type" : "retail",
"authorization" : "59F558F67AC68BAF98D27AEFF59EA406"
}
Request Issued: GET /game/client
Response: 200
{
"install_dir" : "C:/users/Public/Application Data/Battle.net/Client",
"launch_path" : "C:/users/Public/Application Data/Battle.net/Client/Blizzard Launcher.exe",
"current_version" : 0.000000,
"supports_multibox" : false,
"switcher" : false,
"use_sparse" : false,
"operations" : [],
"playable" : true,
"ever_playable" : true,
"last_played" : 0.000000,
"update_progress" : 0.000000,
"needs_rebase" : false,
"product" : "Clnt",
"patch_url" : "http://itIT.patch.battle.net:1119/patch",
"config_url" : "",
"mfil_hash" : "2E006E00650074002000550070006400",
"torrent_hash" : "636F72643E0A3C2F70617463683E0000",
"patch_application_complete" : false,
"perform_ogg_to_wav" : false,
"download_complete" : false,
"speed" : 0.000000,
"baseline" : ""
}
Request Issued to non-existent Uri: GET - /gamesession/client
Response: 404
(null)
Request Issued: POST /gamesession
{
"uid" : "client",
"launch_arguments" : [
"--gamepath=C:\\Program Files\\Diablo III",
"--game=diablo3_itit"
]
}
Agent::Product::StartSession() - Begin Waiting
Agent::Product::StartSession() - End Waiting
Launching C:/users/Public/Application Data/Battle.net/Client/Blizzard Launcher.exe w/ --gamepath=C:\Program Files\Diablo III
--game=diablo3_itit
**********************************************
GameSession: Could not set the process of the pid 58 to the foreground.
Database Insert: /gamesession/client
Database Insert: /gamesession/client/1
Response: 200
{
"response_uri" : "/gamesession/client"
}
Request Issued: GET /agent
Response: 200
{
"update" : {},
"install" : {},
"backfill" : {},
"pid" : 43.000000,
"state" : 1004.000000,
"playable" : true,
"version" : "1.0.0.998",
"type" : "retail",
"authorization" : "0FDDC777C8A6CC8490C3568BCE50193F"
}
Request Issued: GET /agent
Response: 200
{
"update" : {},
"install" : {},
"backfill" : {},
"pid" : 43.000000,
"state" : 1004.000000,
"playable" : true,
"version" : "1.0.0.998",
"type" : "retail",
"authorization" : "999C6CE08A6F469DB023F95A3D736444"
}
Request Issued: POST /install
{
"uid" : "diablo3_itit",
"install_dir" : "C:/Program Files/Diablo III"
}
Firing Event: "database flush event"
Response: 200
{}
Handle Event: "database flush event"
Request Issued: GET /game/Client
Response: 200
{
"install_dir" : "C:/users/Public/Application Data/Battle.net/Client",
"launch_path" : "C:/users/Public/Application Data/Battle.net/Client/Blizzard Launcher.exe",
"current_version" : 0.000000,
"supports_multibox" : false,
"switcher" : false,
"use_sparse" : false,
"operations" : [],
"playable" : true,
"ever_playable" : true,
"last_played" : 0.000000,
"update_progress" : 0.000000,
"needs_rebase" : false,
"product" : "Clnt",
"patch_url" : "http://itIT.patch.battle.net:1119/patch",
"config_url" : "",
"mfil_hash" : "2E006E00650074002000550070006400",
"torrent_hash" : "636F72643E0A3C2F70617463683E0000",
"patch_application_complete" : false,
"perform_ogg_to_wav" : false,
"download_complete" : false,
"speed" : 0.000000,
"baseline" : ""
}
Request Issued: GET /game/diablo3_itit
Response: 200
{
"install_dir" : "C:/Program Files/Diablo III",
"launch_path" : "C:/Program Files/Diablo III/Diablo III.exe",
"selected_locale" : "itIT",
"current_version" : 9950.000000,
"supports_multibox" : false,
"switcher" : false,
"use_sparse" : false,
"operations" : [],
"playable" : true,
"ever_playable" : true,
"last_played" : 0.000000,
"update_progress" : 100.000000,
"needs_rebase" : false,
"product" : "D3",
"patch_url" : "http://itIT.patch.battle.net:1119/patch",
"config_url" : "http://ak.worldofwarcraft.com.edgesuite.net/d3-pod-retail/EU/d3-9950-F98F3243F9CA35A2D8B023009748F806-ruRU.xml",
"mfil_hash" : "8F3D3879B78D56D0C732B10B2957826B",
"torrent_hash" : "9BF58CA74D2347990D82F0B9C7D7DAE1",
"installed_locales" : [
"itIT"
],
"display_locales" : [
"enGB",
"esMX",
"ptBR",
"koKR",
"zhTW",
"deDE",
"esES",
"frFR",
"itIT",
"plPL",
"ruRU"
],
"base_bytes" : [
18771.621218,
38140.970230,
15168.461584
],
"patch_application_complete" : true,
"perform_ogg_to_wav" : false,
"download_complete" : true,
"speed" : 920662.000000,
"baseline" : ""
}
Request Issued to non-existent Uri: GET - /install/diablo3_itit
Response: 404
(null)
Request Issued to non-existent Uri: GET - /update/diablo3_itit
Response: 404
(null)
Request Issued to non-existent Uri: GET - /gamesession/diablo3_itit
Response: 404
(null)
Request Issued to non-existent Uri: GET - /backfill/diablo3_itit
Response: 404
(null)
Request Issued: GET /agent
Response: 200
{
"update" : {},
"install" : {},
"backfill" : {},
"pid" : 43.000000,
"state" : 1004.000000,
"playable" : true,
"version" : "1.0.0.998",
"type" : "retail",
"authorization" : "999C6CE08A6F469DB023F95A3D736444"
}
Request Issued: POST /update
{"uid":"Client"}
Database Insert: /update/Client
Response: 200
{
"response_uri" : "/update/client",
"result_uri" : "/game/client"
}
Request Issued: GET /update/Client
Response: 200
{
"state" : 1007.000000
}
Firing Event: "database flush event"
Handle Event: "database flush event"
Request Issued: GET /update/Client
Response: 200
{
"state" : 1004.000000,
"playable" : true
}
Request Issued: POST /version
{
"uid":"diablo3_itit"
}
Database Insert: /version/diablo3_itit
Response: 200
{
"response_uri" : "/version/diablo3_itit"
}
Request Issued: GET /version/diablo3_itit
Response: 200
{
"state" : 1007.000000,
"local_version" : "-1.-1.-1.-1",
"playable" : true
}
Firing Event: "database flush event"
Handle Event: "database flush event"
Request Issued: GET /version/diablo3_itit
Response: 200
{
"state" : 1004.000000,
"local_version" : "1.0.2.9950",
"playable" : true
}
Request Issued: POST /update
{
"monitor_pid":62,
"uid":"diablo3_itit"
}
Database Insert: /update/diablo3_itit
Response: 200
{
"response_uri" : "/update/diablo3_itit",
"result_uri" : "/game/diablo3_itit"
}
Firing Event: "database flush event"
Handle Event: "database flush event"
Request Issued: GET /update/diablo3_itit
Response: 200
{
"state" : 1004.000000,
"playable" : true,
"progress" : 100.000000,
"download_rate" : 0.000000
}
Handle Event: "auth validation event"
Handle Event: "auth validation event"
Request Issued: DELETE /update/Client
Database Remove: /update/Client
Deferred delete of 'async_task' Resource
Queue 'async_task' Resource for delete
Response: 200
{}
Request Issued to non-existent Uri: GET - /gamesession/diablo3_itit
Response: 404
(null)
Request Issued to non-existent Uri: GET - /backfill/diablo3_itit
Response: 404
(null)
Remo[06/07/12 15:00:32] - Running wine-1.5.5-DiabloIII_v3 winecfg
fixme:iphlpapi:NotifyAddrChange (Handle 0x24ae8ec, overlapped 0x24ae8d0): stub
wine: configuration in '/home/obsidian/.PlayOnLinux/wineprefix/DiabloIII' has been updated.
|
| Quentin PÂRIS |
Thursday 7 June 2012 at 15:07 |
| Rank: Admin
|
Have you read if your symptome is described here? http://appdb.winehq.org/objectManager.php?sClass=version&iId=25953
In the logfile, I can read several launch yesterday. When was the first crash? |
| Quentin PÂRIS |
Thursday 7 June 2012 at 15:09 |
| Rank: Admin
|
@ Obsi
[06/07/12 15:00:32] - Running wine-1.5.5-DiabloIII_v3 winecfg
fixme:iphlpapi:NotifyAddrChange (Handle 0x24ae8ec, overlapped 0x24ae8d0): stub
wine: configuration in '/home/obsidian/.PlayOnLinux/wineprefix/DiabloIII' has been updated.
Obviously, you didn't try to run Diablo III with wine-1.5.5-DiabloIII_v3... |
| ovisan |
Thursday 7 June 2012 at 15:13 |
| Rank: Member
|
The first crash was after Diablo 3 client was updated and Europe servers were patched, so yesterday afternoon EST. The i had playonlinux with wine 1.5.4 - Diablo3 |
| ovisan |
Thursday 7 June 2012 at 15:19 |
| Rank: Member
|
The log from today it's the most relevant, tried to play several times and it froze while playing. |
| Quentin PÂRIS |
Thursday 7 June 2012 at 15:34 |
| Rank: Admin
|
What if you run setarch i386 -3 playonlinux ? |
| ovisan |
Thursday 7 June 2012 at 15:38 |
| Rank: Member
|
Tried that too (posted in the "Diablo III installers updated (AMD users who had problems are concerned)!" thread). It's the same, i tried also 'setarch i386 -3 -L -B -R wine Diablo\ III.exe' but it's the same... |
| Dé |
Thursday 7 June 2012 at 15:39 |
| Rank: Guest
|
Well, i am stucked at authenticating credentials.... |
| ovisan |
Thursday 7 June 2012 at 15:42 |
| Rank: Member
|
For De: check the instructions, you need to run
echo 0|sudo tee /proc/sys/kernel/yama/ptrace_scope
and then start playonlinux and run Diablo 3. It will pass Authenticating credentials. |
| Dé |
Thursday 7 June 2012 at 15:49 |
| Rank: Guest
|
Thanks a lot Ovisan, now worked, is good to see people like you around, God bless you. |
| ovisan |
Thursday 7 June 2012 at 15:53 |
| Rank: Member
|
You'r welcome, happy gaming :-).
Bless you too. |
| DancingBear |
Thursday 7 June 2012 at 16:59 |
| Rank: Guest
|
Keep an eye on this thread for future reference.
were trying to keep all diablo 3 linux issues here: http://us.battle.net/d3/en/forum/topic/5592457019 |
| Quentin PÂRIS |
Thursday 7 June 2012 at 18:16 |
| Rank: Admin
|
@DancingBear
If it's not a problem for you, I prefer that people report PlayOnLinux's related bug on PlayOnLinux's website. Same for wine related bug, they should be reported on wine's website.
Furthermore, if users found solution for problem, it's really faster for us if the solution is posted here.
POL supports hundred games, imagine the amount of work it would represent we had to check each game forums.
Anyway, the problem should be fixed now, and setarch is no longer needed |
| Obsi |
Thursday 7 June 2012 at 19:22 |
| Rank: Guest
|
Well Admin, i tryed setarch command, i changed emulation from xp to 7 to 2000 to vista, i tryed to set wine version to 1.5.5-diabloiii_v3. Nothing, game still freezes in some playing minutes or at login screen when i click on "login", it hangs and in both cases I have to hard reboot the system 
well I'm with this specs:
Ati mobility radeon HD 4650
intel core duo 2.6 hgz
Linux Mint Maya 13
Till yesterday night at 3:00 o'clock (italian time) I was able to play flawlessly. Today I woke up, got the patch from blizz and that's it :/
Referred to you previous comment, i can't understand what log you need, i reported the one you adviced before: Tools-->Debugger-->Virtual Drives--> DiabloIII.
Greeting and thanks for prompt answers and all your work, hugs to the staff! |
| Quentin PÂRIS |
Thursday 7 June 2012 at 19:35 |
| Rank: Admin
|
Obsi : What if you run Diablo III in desktop mode? (Configure -> Wine -> Configure wine -> Display) |
| Obsi |
Thursday 7 June 2012 at 19:44 |
| Rank: Guest
|
I'm running it in emulated desktop, same. It crushed right now |
| Quentin PÂRIS |
Thursday 7 June 2012 at 20:28 |
| Rank: Admin
|
What if you you set DirectDrawRenderer to gdi under PlayOnLinux's Configure->Display? |
| Obsi |
Thursday 7 June 2012 at 23:42 |
| Rank: Guest
|
same :'( |
| Obsi |
Friday 8 June 2012 at 0:43 |
| Rank: Guest
|
The problem is:
1) I try, "sudo echo bla bla bla" command, before starting the game, it freezes at login
2) I don't use "sudo echo" command, it does not go past autentication credentials.
In both cases I'm using 1.5.5-diabloIII_V3.
If I roll down to 1.5.4-diabloIII wine version, it works with "sudo echo", but in a few minutes of gameplay, it freezes and I must hard reboot.
If I use "setarch i386 -3 playonlinux", same as above, with sudo echo, it freezes, without no way to go past credentials.
gdi or opengl does not seem to change nothing, it freezes anyway. Emulate desktop does not help. Well, I'm without ideas left
I tryed in backbuffer but it displays all black, with orange tiles where should be text, only working with fbo and pbuffer, but does not change the result.
I try to delete the prefix and reinstall the game? Maybe somewhat went wrong? I read other people work, but not for me, and don't know how to resolve  |
| solushed |
Friday 8 June 2012 at 5:51 |
| Rank: Member
|
Quote: The problem is:
1) I try, "sudo echo bla bla bla" command, before starting the game, it freezes at login
2) I don't use "sudo echo" command, it does not go past autentication credentials.
In both cases I'm using 1.5.5-diabloIII_V3.
If I roll down to 1.5.4-diabloIII wine version, it works with "sudo echo", but in a few minutes of gameplay, it freezes and I must hard reboot.
If I use "setarch i386 -3 playonlinux", same as above, with sudo echo, it freezes, without no way to go past credentials.
gdi or opengl does not seem to change nothing, it freezes anyway. Emulate desktop does not help. Well, I'm without ideas left
I tryed in backbuffer but it displays all black, with orange tiles where should be text, only working with fbo and pbuffer, but does not change the result.
I try to delete the prefix and reinstall the game? Maybe somewhat went wrong? I read other people work, but not for me, and don't know how to resolve
I tried all he tried... I even re-installed diablo (went through the 8gb download again) attempted to log in after it and nothing ):
can someone explain how to "Just set wine 1.5.5-DiabloIII_v3 to your virtual drive" perhaps I've done that wrong? Though according to main post if I re-installed diablo I didn't need to do that. |
| solushed |
Friday 8 June 2012 at 5:55 |
| Rank: Member
|
Also I'm using ubuntu 12.04 lts 32 bit not 64 bit, could it have something to do with it? |
| roboso |
Friday 8 June 2012 at 10:08 |
| Rank: Member
|
use reset game preferences into launcer!!!! |
| ovisan |
Friday 8 June 2012 at 10:50 |
| Rank: Member
|
Frozed again while playing. What happens is that suddenly the sound stops and then the freeze happens, and after a couple of seconds the sound comes back but the graphics are frozen, i can move the mouse though.
As mentioned above, this didn't happen before blizzard's patch 1.0.2 |
| Obsi |
Friday 8 June 2012 at 11:59 |
| Rank: Guest
|
Quote: use reset game preferences into launcer!!!!
Never tought about it! I'll give it a try. Someone else has got ideas? I think that Quentin is working on it and will be fixed as soon as possible :P |
| Obsi |
Friday 8 June 2012 at 12:06 |
| Rank: Guest
|
Quote: use reset game preferences into launcer!!!!
Never tought about it! I'll give it a try. Someone else has got ideas? I think that Quentin is working on it and will be fixed as soon as possible :P
well, just tryied with 1.5.5-diabloIII_V3, it simply freezes on Login button. Now i try on 1.5.4-diabloIII. |
| Obsi |
Friday 8 June 2012 at 12:20 |
| Rank: Guest
|
Quote: use reset game preferences into launcer!!!!
Never tought about it! I'll give it a try. Someone else has got ideas? I think that Quentin is working on it and will be fixed as soon as possible :P
well, just tryied with 1.5.5-diabloIII_V3, it simply freezes on Login button. Now i try on 1.5.4-diabloIII.
2 minutes gameplay and freezed! |
| Quentin PÂRIS |
Friday 8 June 2012 at 12:25 |
| Rank: Admin
|
Can you tell me what distro and graphic cards you have, people having crash problems? (And others to) |
| Obsi |
Friday 8 June 2012 at 12:33 |
| Rank: Guest
|
I'am on Linux Mint Maya 13, video with
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI M96 [Mobility Radeon HD 4650] |
| Obsi |
Friday 8 June 2012 at 12:37 |
| Rank: Guest
|
I noticed this in the log file, is it helpful?
fixme:shell:SetCurrentProcessExplicitAppUserModelID L"BlizzardEntertainment.DiabloIII.retail": stub
fixme rocess:GetLogicalProcessorInformation (0xfbe368,0xfbe968): stub
fixme:msgack_message msg 80 (WM_SETICON) not supported yet
fixme:msgack_message msg 80 (WM_SETICON) not supported yet
fixmerocess:GetLogicalProcessorInformation (0xfbe368,0xfbe968): stub
fixmerocess:GetLogicalProcessorInformation (0xfbe368,0xfbe968): stub
fixmerocess:GetLogicalProcessorInformation (0xfbe368,0xfbe968): stub
fixmerocess:GetLogicalProcessorInformation (0xfbe368,0xfbe968): stub
fixmerocess:GetLogicalProcessorInformation (0xfbe368,0xfbe968): stub
fixmerocess:GetLogicalProcessorInformation (0xfbe368,0xfbe968): stub
fixmerocess:GetLogicalProcessorInformation (0xfbe368,0xfbe968): stub
fixmerocess:GetLogicalProcessorInformation (0xfbe368,0xfbe968): stub
fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do!
fixmerocess:GetLogicalProcessorInformation (0x14be334,0x14be934): stub
fixmerocess:GetLogicalProcessorInformation (0x14be304,0x14be904): stub
fixmerocess:GetLogicalProcessorInformation (0xfbe368,0xfbe968): stub
fixmerocess:GetLogicalProcessorInformation (0xfbe368,0xfbe968): stub
fixmerocess:GetLogicalProcessorInformation (0xfbe368,0xfbe968): stub
fixmerocess:GetLogicalProcessorInformation (0x14be334,0x14be934): stub
fixmerocess:GetLogicalProcessorInformation (0x14be304,0x14be904): stub
fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do!
fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do!
fixmerocess:GetLogicalProcessorInformation (0x14be334,0x14be934): stub
fixmerocess:GetLogicalProcessorInformation (0x14be304,0x14be904): stub
fixmerocess:GetLogicalProcessorInformation (0xfbe368,0xfbe968): stub
fixmerocess:GetLogicalProcessorInformation (0xfbe368,0xfbe968): stub
fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do!
fixmerocess:GetLogicalProcessorInformation (0x14be334,0x14be934): stub
fixmerocess:GetLogicalProcessorInformation (0x14be304,0x14be904): stub
fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do!
fixmerocess:GetLogicalProcessorInformation (0x14be334,0x14be934): stub
fixmerocess:GetLogicalProcessorInformation (0x14be304,0x14be904): stub
fixmerocess:GetLogicalProcessorInformation (0xfbe368,0xfbe968): stub
fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do!
fixmerocess:GetLogicalProcessorInformation (0x267e358,0x267e354): stub
fixmerocess:GetLogicalProcessorInformation (0x267e358,0x267e354): stub
fixme:win:EnumDisplayDevicesW ((null),0,0x33af3c,0x00000000), stub!
fixme:ddrawirectDrawEnumerateExA flags 0x00000003 not handled
fixmerocess:GetLogicalProcessorInformation (0xfbe368,0xfbe968): stub
fixmerocess:GetLogicalProcessorInformation (0xfbe368,0xfbe968): stub
fixmerocess:GetLogicalProcessorInformation (0xfbe368,0xfbe968): stub
fixmerocess:GetLogicalProcessorInformation (0x33f348,0x33f948): stub
fixmerocess:GetLogicalProcessorInformation (0x33f604,0x33fc04): stub
fixmerocess:GetLogicalProcessorInformation (0xfbe368,0xfbe968): stub
fixmerocess:GetLogicalProcessorInformation (0x235bf88,0x235c588): stub
fixmerocess:GetLogicalProcessorInformation (0x235bf88,0x235c588): stub
fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do!
fixmerocess:GetLogicalProcessorInformation (0x245e358,0x245e958): stub
fixmerocess:GetLogicalProcessorInformation (0x245e358,0x245e958): stub
fixmerocess:GetLogicalProcessorInformation (0xfbe368,0xfbe968): stub
fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do!
fixmerocess:GetLogicalProcessorInformation (0x245e358,0x245e958): stub
fixmerocess:GetLogicalProcessorInformation (0x245e358,0x245e958): stub
fixmerocess:GetLogicalProcessorInformation (0xfbe368,0xfbe968): stub
fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do!
fixmerocess:GetLogicalProcessorInformation (0x245e358,0x245e958): stub
fixmerocess:GetLogicalProcessorInformation (0x245e358,0x245e958): stub
fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do!
fixmerocess:GetLogicalProcessorInformation (0x245e358,0x245e958): stub
fixmerocess:GetLogicalProcessorInformation (0x245e358,0x245e958): stub
fixmerocess:GetLogicalProcessorInformation (0x33ef10,0x33f510): stub
fixmerocess:GetLogicalProcessorInformation (0x33f008,0x33f608): stub
fixmerocess:GetLogicalProcessorInformation (0x33f008,0x33f608): stub
fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
fixme:win:EnumDisplayDevicesW ((null),0,0x33f678,0x00000000), stub!
err:d3d:context_create wglSwapIntervalEXT failed to set swap interval 0 for context 0x15a0a8, last error 0x591
fixme:d3d:query_init Unhandled query type 0x11.
fixme:d3d:query_init Unhandled query type 0x12.
fixme:d3d:query_init Unhandled query type 0xe.
fixme:d3d:query_init Unhandled query type 0xd.
fixme:d3d:query_init Unhandled query type 0x6.
fixme:d3d:query_init Unhandled query type 0xf.
fixme:d3d:query_init Unhandled query type 0x5.
fixme:win:EnumDisplayDevicesW ((null),0,0x33f2e0,0x00000000), stub!
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x34324644 (as fourcc: DF24) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x34324644) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x36314644 (as fourcc: DF16) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x36314644) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x36314644 (as fourcc: DF16) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x36314644) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x36314644 (as fourcc: DF16) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x36314644) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x5a574152 (as fourcc: RAWZ) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x5a574152) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x5a574152 (as fourcc: RAWZ) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x5a574152) in the format lookup table
fixme:d3d:debug_d3dformat Unrecognized 0x5a574152 (as fourcc: RAWZ) WINED3DFORMAT!
fixme:d3d:wined3d_get_format Can't find format unrecognized (0x5a574152) in the format lookup table
fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0xed6e9a8): stub
fixmerocess:GetLogicalProcessorInformation (0x33f6d0,0x33fcd0): stub
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d |
| Quentin PÂRIS |
Friday 8 June 2012 at 12:48 |
| Rank: Admin
|
32bits or 64bits ? |
| Obsi |
Friday 8 June 2012 at 12:50 |
| Rank: Guest
|
@ Quentin: sorry :| 32bits forgot it |
| roboso |
Friday 8 June 2012 at 12:56 |
| Rank: Member
|
ubuntu 64 ati hd6XXX cayman. |
| Quentin PÂRIS |
Friday 8 June 2012 at 13:33 |
| Rank: Admin
|
So it seems to be a ATI problem then... I will test on my nvidia machine to confirm |
| kirex |
Friday 8 June 2012 at 14:09 |
| Rank: Guest
|
Frozed in login user, I have:
POL 4.1.1 - 1.5.5-diabloIII_V3
Debian SID 3.2.0-2-amd64
VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Whistler [AMD Radeon HD 6600M Series]
|
| Obsi |
Friday 8 June 2012 at 14:13 |
| Rank: Guest
|
@ Quentin: oh shiX, hope it will be fixed in next patch :/ let us know.
greetings. |
| solushed |
Friday 8 June 2012 at 14:35 |
| Rank: Member
|
Quote: Can you tell me what distro and graphic cards you have, people having crash problems? (And others to)
Ubuntu 12.04 LTD 32 bits
on-xfx1-pl is the graphic card xfx one |
| Quentin PÂRIS |
Friday 8 June 2012 at 15:06 |
| Rank: Admin
|
Read the latest comment here : "http://appdb.winehq.org/objectManager.php?sClass=version&iId=25953&iTestingId=71591"
And tell me if it works |
| Obsi |
Friday 8 June 2012 at 16:06 |
| Rank: Guest
|
If you mean "how to fix everything", no it does not work not for me at least, i'm 32bit but tryed anyway, no way to fix that. |
| solushed |
Friday 8 June 2012 at 16:35 |
| Rank: Member
|
Same here ): |
| gambitho |
Friday 8 June 2012 at 17:08 |
| Rank: Guest
|
The same...
Game freezes the system after 3-15 minutes gameplay.
Still can kill by ssh connecting
Ubuntu 12.04 64bit
ATI HD4770 with Catalyst drivers |
| ovisan |
Friday 8 June 2012 at 17:11 |
| Rank: Member
|
Samse as gambitho, freeze bwtween 3-15 minutes of gameplay. |
| a2r |
Friday 8 June 2012 at 17:51 |
| Rank: Guest
|
Did anyone try it with the open source drivers? |
| ovisan |
Friday 8 June 2012 at 18:42 |
| Rank: Member
|
a2r: it worked fine before 1.0.2 patch with the existing drivers, why would that change? |
| roboso |
Friday 8 June 2012 at 21:40 |
| Rank: Member
|
hello
then gallium + ati does not work
gallium + nvidia working but low fps
gallium
by diego on Friday May 25th 2012, 1:32
has anyone tried the new driver gallium?
[post new] [reply to this]
RE: gallium by Alexey Loukianov on Friday May 25th 2012, 6:01
RE: gallium
by Alexey Loukianov on Friday May 25th 2012, 6:01
Could you be more specific? It's hard to understand what are you trying to ask.
[post new] [reply to this]
RE: gallium by obsidian on Friday May 25th 2012, 7:34
RE: gallium
by obsidian on Friday May 25th 2012, 7:34
Tryed them, and are very laggy for me, i got something like 10-14 fps. Had to install fglrx drivers for my ati, and work like a charm.
[post new] [reply to this]
RE: gallium by Patrick O. on Friday May 25th 2012, 22:38
RE: gallium
by Patrick O. on Friday May 25th 2012, 22:38
I have a AMD HD 5570 and am running the gallium r600g driver. With all settings on low and the resolution set to 1024x786 I get ~30 fps. The game is quite playable in most parts.
The problem arises when there is lots of fire/rain/mobs. The game gets laggy. Beating the boss of Act I was much more difficult than it should have been simply because it seemed like I was always a second or two behind the game, and could not dodge any attack.
[post new] [reply to this]
RE: gallium by Mike Mestnik on Tuesday May 29th 2012, 21:08
RE: gallium
by Mike Mestnik on Tuesday May 29th 2012, 21:08
Don't you find that you walk and attack vary slowly. I've been keeping tabs on a bug where your player stats are tied to your FPS, I'm certain you are being robbed of speed.
us.battle.net/d3/en/forum/topic/5150106576
One definitive test is to join a multi-player game and see if you can race other players. The other players should see you 'jerk' or skip every step. As in take a step, pause, take another step, and another pause... Accounting for the difference in the speed you should have with your player stats and the speed you actually move.
[post new] [reply to this]
RE: gallium by Patrick O. on Tuesday May 29th 2012, 23:40
RE: gallium
by Patrick O. on Tuesday May 29th 2012, 23:40
Almost certainly I have some slow-down issues when things get a bit heated, or when there is a lot going on in the background (like the butcher fight).
I'd say about 50% of the time, things are going smoothly, 25% of the time, I'm running a bit slow. 20% of the time, things are choppy, and the remaining 5% can be disastrous.
It's still fun the play the game though. I'll probably try to upgrade my old CPU soon anyways.
[post new] [reply to this]
RE: gallium by Mike Mestnik on Wednesday May 30th 2012, 10:37
RE: gallium
by Mike Mestnik on Wednesday May 30th 2012, 10:37
Could you please report your experience on the Bnet forum so that Blizzard is aware. Make sure to clearly state that you are talking about movement speed as a player stat and not frame rate as a client side metric.
Blizzard needs to be made aware that varying frame rates effect game play and not just the way the game looks, but instead imposes an actual change to the arithmetic that effects player position.
Thank you.
[post new] [reply to this] |
| a2r |
Friday 8 June 2012 at 23:52 |
| Rank: Guest
|
ovisan: well, everyone who gots the freezes is an ati user. the freezes where there before 1.0.2, at least in my case. it worked after compiling the diabloIII_v2 wine.
Maybe the whole freeze thing is a driver problem, maybe the opensource driver isn't affected. |
| gambitho |
Saturday 9 June 2012 at 10:10 |
| Rank: Guest
|
Today I tried to connect ~15-20 times and every time freezes on authentication or just after push the login button. It is realy sad that I can only kill Diablo by ssh ;)
a2r
I tried open drivers before patch 1.0.2, because before this patch I had freezes too (but it was only in ~5% cases just after push login button, never during the gameplay) . And open drivers nothing change. |
| Quentin PÂRIS |
Saturday 9 June 2012 at 10:28 |
| Rank: Admin
|
What if you add "-opengl" in program argument? |
| gambitho |
Saturday 9 June 2012 at 10:49 |
| Rank: Guest
|
I tired with this argument and without it. This nothing changed. |
| Quentin PÂRIS |
Saturday 9 June 2012 at 11:04 |
| Rank: Admin
|
Even the game fps?
How did you add it? |
| ovisan |
Saturday 9 June 2012 at 11:54 |
| Rank: Member
|
a2r: yes, i agree that ati users are affected, in my case it was working perfectly fine before 1.0.2 patch, when i was playing for few hours with no problem. The freezes others had at login were easy to woraround them by running
echo 0|sudo tee /proc/sys/kernel/yama/ptrace_scope, setting gdi and 1024 MB Ram for video, starting the game with setarch i386 -3 -L -B -R wine Diablo\ III.exe, etc...
That was all fine and this solutions worked, but now, after the patch everything changed, meaning that while playing (the timeframe varies 1-30 min) the sound suddenly mutes for a second or so, and then the sound comes back. When the sound mutes the system freeze happens and it's hard to debug because being a system freeze the log is no longer populated, hence all you can do is hard reboot, nothing else works. Tried to play also in window mode but the same thing happens.
I am excluding ati drivers as the source of the problem, because it was working fine before that patch 1.0.2. Now the problem comes somewhere from the updated diablo client, it's the only logical conclusion IMHO.
If you guys have other ideas/solutions i am happy to hear about them and also i am happy to test any changes the Admin/wine people make.
Cheers. |
| ovisan |
Saturday 9 June 2012 at 11:59 |
| Rank: Member
|
as gambitho states, i had also freezes at login, but never in game while playing, and that was before 1.0.2. Now i have the problem mentioned above.
Again, please let me know if i can test the changes you may think of, i'll be happy to.
Thanks guys. |
| Obsi |
Saturday 9 June 2012 at 13:25 |
| Rank: Guest
|
Idea, has someone tryed for ati radeon video card, to install catalyst 12.6 beta drivers? Admin what do you think? |
| Obsi |
Saturday 9 June 2012 at 13:29 |
| Rank: Guest
|
Quote: Random Crash While In-Game
by o.O on Saturday June 9th 2012, 2:00
All,
I've experimented with Ubuntu instance from 10.x to 12.x, and now I'm on 11.10 (all 64-bit). I've followed comments on this forum, PoL forum, and the bnet forums, and finally got to the point where I had D3 installed and past the authentication issue (with a token), and it would crash randomly before, during, or 30 min after authentication (while playing). Some seem to think it's a Warden issue, but my experience with compiling Wine, using PoL, and reverting to Win7, it seems like my problems stemmed from an old driver issue in Ubuntu 11.10. I uninstalled the system proprietary ATI drivers, downloaded the latest Catalyst (12.4) drivers from the ATI website, built them, and installed them..... so far so good. No random crashes or force reboots...
Root issue: I think it's related to old drivers overheating the video card. I don't have any details to go on other than some obscure post somewhere else having a similar problem prompting me to install the ATI proprietary drivers.
Sorry!
I just took it from WineHQ, the dude takes the problet that it is, IMHO too, the overheating, i noticed, in fact, that in-games-freezes, video card was HOT as hell on my laptop. It could be a solution? |
| Quentin PÂRIS |
Saturday 9 June 2012 at 15:55 |
| Rank: Admin
|
Yes, it could be the problem! Try to upgrade your drivers |
| Obsi |
Saturday 9 June 2012 at 16:04 |
| Rank: Guest
|
Unfortunately admin, tryed to install them, I'm with Linux Mint 13 maya and a
display: :0 screen: 0
OpenGL vendor string: Advanced Micro Devices, Inc.
OpenGL renderer string: ATI Mobility Radeon HD 4650
OpenGL version string: 3.3.11627 Compatibility Profile Context
compiled and installed new drivers, but when i do "fglrxinfo" it reports something like no adaptive device found. Can you address us linux mint /ubuntu users with/for a nice working guide? thanks for all your work. |
| Quentin PÂRIS |
Saturday 9 June 2012 at 16:15 |
| Rank: Admin
|
I have no idea, I'm not a AMD specialist ;) You should look for information in your distro forums |
| Clicksights |
Saturday 9 June 2012 at 16:40 |
| Rank: Member
|
The new patch works perfect, but some how my framerates are way to slow.
I still run pol in optirun mode, but it seems it is some how not working ok. |
| Obsi |
Saturday 9 June 2012 at 16:51 |
| Rank: Guest
|
Well, Catalyst 12.6 beta are only for 5000 to 7000 series ati radeon V.C. Ati radeon users mouinting a less serie cannot install beta (from the amd/ati site i read that there is a specific profile for diablo 3 ). Last driver for us 4000 series or less, are 12.4, that are the ones in the ubuntu/mint repos, named as: fglrx-update. Too bad, the problem is not solved, not for me at least.
I'm going to play with settings in "aticonfig" to let me see if there's something to workaround that issue, I'll let you know...
Obsidian |
| ovisan |
Saturday 9 June 2012 at 17:18 |
| Rank: Member
|
Obsi: i've tested with Catalyst 12.6, but this drivers are way too unstable, sometimes i coudn't even have gnome shell started and had to revert to Catalyst 12.4. Before the patch 1.0.2 i had also Catalyst 12.4 and it worked fine. I still think it's something related to the new updated Diablo client. |
| Quentin PÂRIS |
Saturday 9 June 2012 at 17:22 |
| Rank: Admin
|
Ovisan it works perfectly for nvidia cards. So it must be related to ATI drivers |
| Obsi |
Saturday 9 June 2012 at 17:28 |
| Rank: Guest
|
I agree with ovisan, is a problem with last game update, but it comes only for ati users. Anyway, no luck till now |
| ovisan |
Saturday 9 June 2012 at 17:43 |
| Rank: Member
|
Tinou: as i said before, until the patch it was working with ATI drivers too with no problem. On my system only the Diablo client was updated, the ati drivers are still the same. If the diablo client is more sensible now to ati drivers, that may be, but still we need to fix it. Buying an nvidia card is not an option, i'd better wait 1.0.3 patch from blizzard, maybe that will fix it. That's all folks, all software sucks.
|
| Quentin PÂRIS |
Saturday 9 June 2012 at 18:09 |
| Rank: Admin
|
Ovisan, or the latest Diablo III version uses some stuff that are not supported by Linux amd drivers. Anyway, it is not a Diablo III problem. It could be a wine problem though |
| ovisan |
Saturday 9 June 2012 at 18:45 |
| Rank: Member
|
Tinou, that may be true also, fact is that there is a problem somewhere for all ATI linux users. I'll search more and see if someone will solve the problem. |
| roboso |
Saturday 9 June 2012 at 19:13 |
| Rank: Member
|
http://support.amd.com/us/kbarticles/Pages/AMDCatalyst126beta.aspx
work work work, 64bit.... YEEEEEEEEEEEEEEEEEEE BUDDY |
| Obsi |
Saturday 9 June 2012 at 23:46 |
| Rank: Guest
|
@roboso: happy that works, but we're stuck anyway xD I can't be so happy btw :'( |
| aurelienbis |
Sunday 10 June 2012 at 0:34 |
| Rank: Guest
|
I'm under Ubuntu 12.04 32bits.
Graphic card : ATI Mobility Radeon HD 5400 Series
Using 1.5.5-DiabloIII_v3
Same problem as every ATI user. Game freeze immediatly after clicking log in.
If I use 1.5.4-DiabloIII, I can connect but game freezes after a few minutes.
I'm gonna try to install last catalyst (http://support.amd.com/us/kbarticles/Pages/AMDCatalyst126beta.aspx). |
| aurelienbis |
Sunday 10 June 2012 at 1:05 |
| Rank: Member
|
It's just getting worst for me. The game don't event start. |
| roboso |
Sunday 10 June 2012 at 1:57 |
| Rank: Member
|
Hardware:
AMD Radeon HD 7900 Series
AMD Radeon HD 7800 Series
AMD Radeon HD 7700 Series
AMD Radeon HD 6000 Series
AMD Radeon HD 5000 Series
The driver only works on these cards for now.
However it is a driver issue, as long as amd does not do a fix can not fix anything. |
| Obsi |
Sunday 10 June 2012 at 4:00 |
| Rank: Guest
|
Well then, i uninstalled fglrx drivers from my package manager, in linux mint 13 maya, so I guess it will work on ubuntu too, then downloaded amd ati radeon catalyst 12.4 drivers from the official site, installed it, and it works  I'm almost 2 hours playing without freezes
Now the explanations:
I reccomend: FIRST REMOVE YOUR PREVIOUS DRIVERS
1) Follow this to remove COMPLETELY your repo fglrx drivers for amd radeon (drivers provided by ubuntu repos): http://askubuntu.com/questions/98827/ati-driver-re-install-fail (the guide to follow is just the first answer to the question that you will find it will begin with "For 64bit systems before doing anything.")
2) if you have got kernel 3.2 (type uname -r in command shell to discover it) then follow this guide, you need to patch ati radeon drivers to install it on the 3.2 kernel, because for some reasons it's not compatible (don't ask why amd is so messy).
GUIDE FOR KERNEL 3.2: http://ubuntuforums.org/showthread.php?t=1969827
3) if you have got other kernels, then google the proper question like: "ati radeon drivers 12.4 kernel 3.X patch" ( X stands for your kernel second number version) someone probably had patched it
Well, i tryed to be at least the more clear as possible to explain how to do it :/ really hope it will help :P I don't really know why proprietary drivers in repos do that issue, I noticed that is the same version that I installed manually  . If it will be helpful to you all I'd really like Admin Quentin sticks it in news so everyone can enjoy the game again and the guide is "pret a porter"  . |
| Obsi |
Sunday 10 June 2012 at 4:02 |
| Rank: Guest
|
I re-read my guide again, well, sorry for my bad English -.-''' |
| gambitho |
Sunday 10 June 2012 at 9:26 |
| Rank: Guest
|
Yesterday evening after Obsi citation I decided to remove graphic drivers. I made that in this way (kUbuntu): System -> Additional Drivers -> and remove installed drivers. After this step my Catalyst drivers was removed too. I rebooted computer (it was recommended) and installed the newest Catalyst drivers.
Yesterday I launched Diablo without freeze on login screen (1st success) and played normally about 40-60min (2nd success)! But it could was just a luck, so I didn't wrote here about that.
Today I launched Diablo 5-10 times in a raw and login to the game without freezes! Then my first steps go here to wrote about it But firstly I read Obsi guide that he described the same solution
So I can confirm that REMOVING all graphic drivers and install Catalyst drivers again WORK like a charm!
Thank you ALL for help!
P.S.
Quote: Even the game fps?
How did you add it?
I know it is late to answer on this, but yesterday I was out of the home.
To launch the game I use this script:
Terminal output: #!/bin/bash
echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope
setarch i386 -3 wine ~/.wine/drive_c/Program\ Files\ \(x86\)/Diablo\ III/Diablo\ III.exe -launch -opengl |
| Quentin PÂRIS |
Sunday 10 June 2012 at 12:22 |
| Rank: Admin
|
Thank you gambitho.
Do you have a command to detect catalyst driver version? |
| roboso |
Sunday 10 June 2012 at 12:59 |
| Rank: Member
|
sudo apt-get install build-essential cdbs fakeroot dh-make debhelper debconf libstdc++6 dkms libqtgui4 wget execstack libelfg0 dh-modaliases
sudo apt-get remove --purge fglrx fglrx_* fglrx-amdcccle* fglrx-dev*
wget http://www2.ati.com/drivers/hotfix/catalyst_12.6_hotfixes/amd-driver-installer-8.98-x86.x86_64.zip
unzip http://www2.ati.com/drivers/hotfix/catalyst_12.6_hotfixes/amd-driver-installer-8.98-x86.x86_64.zip
for system 64 bit, type in:
sudo apt-get install ia32-libs
chmod 755 amd-driver-installer-8.98-x86.x86_64.run
sh ./amd-driver-installer-12-3-x86.x86_64.run --buildpkg Ubuntu/precise
sudo dpkg -i fglrx*.deb
sudo aticonfig --initial -f
sudo reboot
|
| aurelienbis |
Sunday 10 June 2012 at 14:20 |
| Rank: Member
|
No way, even after uninstall and reinstall graphic drivers via System settings => Additional drivers, the game still freezes after a few minutes. |
| Quentin PÂRIS |
Sunday 10 June 2012 at 14:47 |
| Rank: Admin
|
aurelienbis: Please read what is said before asking. The solution is explained just above |
| kirex |
Sunday 10 June 2012 at 14:49 |
| Rank: Guest
|
Catalyst 12.6 the driver did not freeze the game but once after about 40 minutes the game suddenly switch off dIII. |
| aurelienbis |
Sunday 10 June 2012 at 15:16 |
| Rank: Member
|
Quote: Yesterday evening after Obsi citation I decided to remove graphic drivers. I made that in this way (kUbuntu): System -> Additional Drivers -> and remove installed drivers. After this step my Catalyst drivers was removed too. I rebooted computer (it was recommended) and installed the newest Catalyst drivers.
Isn't it what I did ? I tried installing newest catalyst driver (12.4) by konsole too, but Diablo don't start at all. |
| aurelienbis |
Sunday 10 June 2012 at 15:20 |
| Rank: Member
|
Obsi says there's another way to uninstall Catalyst. I really don't know what to do.
Maybe it's the installation I'm doing wrong ?
I used sudo ./amd* --force
Is it bad ? |
| Quentin PÂRIS |
Sunday 10 June 2012 at 15:27 |
| Rank: Admin
|
Newest is 12.6, not 12.4... Please read
And yes, sometimes, the game switch off, even with nvidia card. But it's rare. It's largely playable |
| aurelienbis |
Sunday 10 June 2012 at 15:54 |
| Rank: Member
|
Quote: Hardware:
via
AMD Radeon HD 7900 Series
AMD Radeon HD 7800 Series
AMD Radeon HD 7700 Series
AMD Radeon HD 6000 Series
AMD Radeon HD 5000 Series
The driver only works on these cards for now.
I have the HD 5400. If I install 12.6, i've got a watermark in bottom right that says "amd - test use only" and the game won't launch neither.
When I install driver via System settings => Additional drivers, the game launches but systematicaly freeze after a few minutes. I must hard reboot.
And when I install 12.4 with terminal using --force option, the game won't start, as with 12.6 but at least I don't have the watermark.
As I said, I suppose that I'm doing something wrong with uninstallation or installation, and people are giving different solutions, but I'm quite lost and don't know which way I should do it correctly.
Thanks for helping. |
| Obsi |
Sunday 10 June 2012 at 15:57 |
| Rank: Guest
|
Here you are
1.1) Facultative --> (For 64bit systems before doing anything:
sudo apt-get install ia32-libs)
1.2)Run each of these, one at the time, if getting any faults ignore it:
-sudo sh /usr/share/ati/fglrx-uninstall.sh
-sudo apt-get remove --purge fglrx fglrx_* fglrx-amdcccle* fglrx-dev*
2)Remove your xorg.conf file:
-sudo rm /etc/X11/xorg.conf
3) Re-install xorg:
-sudo apt-get install --reinstall libgl1-mesa-glx:i386 libgl1-mesa-glx:amd64 libgl1-mesa-dri:i386 libgl1-mesa-dri:amd64 xserver-xorg-core
4)Configure xorg:
-sudo dpkg-reconfigure xserver-xorg
5) Reboot:
-sudo reboot |
| aurelienbis |
Sunday 10 June 2012 at 16:01 |
| Rank: Member
|
Then I make amd...12.4.run running as executable, then open in terminal and it should work ? |
| Obsi |
Sunday 10 June 2012 at 16:10 |
| Rank: Guest
|
first follow the guide to completely uninstall it, then follow with this:
http://ubuntuforums.org/showthread.php?t=1969827
just copy-paste one by one the command in shell command and it's done ^^ |
| aurelienbis |
Sunday 10 June 2012 at 16:19 |
| Rank: Member
|
I didn't found this one.
So I'm gonna uninstall as you said, then follow your link for installation. I'll come for a feedback after this. |
| aurelienbis |
Sunday 10 June 2012 at 16:53 |
| Rank: Member
|
Quote: aurelien@aurelien-Studio-1558:~$ sudo sh /usr/share/ati/fglrx-uninstall.sh
[sudo] password for aurelien:
sh: 0: Can't open /usr/share/ati/fglrx-uninstall.sh
Quote: aurelien@aurelien-Studio-1558:~$ sudo apt-get remove --purge fglrx fglrx_* fglrx-amdcccle* fglrx-dev*
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'fglrx-updates' for regex 'fglrx_*'
Note, selecting 'fglrx-driver-dev' for regex 'fglrx_*'
Note, selecting 'fglrx-amdcccle-updates' for regex 'fglrx_*'
Note, selecting 'fglrx' for regex 'fglrx_*'
Note, selecting 'fglrx-driver' for regex 'fglrx_*'
Note, selecting 'xfree86-driver-fglrx-dev' for regex 'fglrx_*'
Note, selecting 'fglrx-control' for regex 'fglrx_*'
Note, selecting 'fglrx-amdcccle' for regex 'fglrx_*'
Note, selecting 'fglrx-dev' for regex 'fglrx_*'
Note, selecting 'fglrx-modaliases' for regex 'fglrx_*'
Note, selecting 'fglrx-glx' for regex 'fglrx_*'
Note, selecting 'fglrx-kernel-source' for regex 'fglrx_*'
Note, selecting 'xorg-driver-fglrx' for regex 'fglrx_*'
Note, selecting 'fglrx-control-qt2' for regex 'fglrx_*'
Note, selecting 'fglrx-updates-dev' for regex 'fglrx_*'
Note, selecting 'xorg-driver-fglrx-dev' for regex 'fglrx_*'
Note, selecting 'xfree86-driver-fglrx' for regex 'fglrx_*'
Note, selecting 'fglrx-amdcccle-updates' for regex 'fglrx-amdcccle*'
Note, selecting 'fglrx-amdcccle' for regex 'fglrx-amdcccle*'
Note, selecting 'xfree86-driver-fglrx-dev' for regex 'fglrx-dev*'
Note, selecting 'fglrx-dev' for regex 'fglrx-dev*'
Note, selecting 'xorg-driver-fglrx-dev' for regex 'fglrx-dev*'
Package fglrx-amdcccle-updates is not installed, so not removed
Package fglrx-dev is not installed, so not removed
Package fglrx-updates is not installed, so not removed
Package fglrx-updates-dev is not installed, so not removed
The following package was automatically installed and is no longer required:
dkms
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
fglrx* fglrx-amdcccle*
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
After this operation, 129 MB disk space will be freed.
Do you want to continue [Y/n]? Y
(Reading database ... 246225 files and directories currently installed.)
Removing fglrx-amdcccle ...
dpkg: warning: while removing fglrx-amdcccle, directory '/usr/share/ati' not empty so not removed.
Removing fglrx ...
Removing all DKMS Modules
Done.
update-alternatives: removing manually selected alternative - switching i386-linux-gnu_gl_conf to auto mode
update-alternatives: using /usr/lib/pxpress/ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_GL.conf (i386-linux-gnu_gl_conf) in auto mode.
update-alternatives: warning: skip creation of /usr/bin/amdcccle because associated file /usr/lib/fglrx/bin/amdcccle (of link group i386-linux-gnu_gl_conf) doesn't exist.
update-alternatives: warning: skip creation of /usr/share/applications/ubuntu-amdcccle.desktop because associated file /usr/share/fglrx/amdcccle.desktop (of link group i386-linux-gnu_gl_conf) doesn't exist.
update-alternatives: warning: skip creation of /usr/share/applications/ubuntu-amdccclesu.desktop because associated file /usr/share/fglrx/amdccclesu.desktop (of link group i386-linux-gnu_gl_conf) doesn't exist.
update-alternatives: warning: skip creation of /etc/OpenCL/vendors/amdocl64.icd because associated file /usr/lib/fglrx/etc/OpenCL/vendors/amdocl64.icd (of link group i386-linux-gnu_gl_conf) doesn't exist.
update-alternatives: warning: skip creation of /usr/bin/amdupdaterandrconfig because associated file /usr/lib/fglrx/bin/amdupdaterandrconfig (of link group i386-linux-gnu_gl_conf) doesn't exist.
update-alternatives: warning: skip creation of /usr/bin/amdxdg-su because associated file /usr/lib/fglrx/bin/amdxdg-su (of link group i386-linux-gnu_gl_conf) doesn't exist.
update-alternatives: warning: skip creation of /usr/lib32/libaticalcl.so because associated file /usr/lib32/fglrx/libaticalcl.so (of link group i386-linux-gnu_gl_conf) doesn't exist.
update-alternatives: warning: skip creation of /usr/lib32/libaticalrt.so because associated file /usr/lib32/fglrx/libaticalrt.so (of link group i386-linux-gnu_gl_conf) doesn't exist.
update-alternatives: warning: not replacing /usr/lib/i386-linux-gnu/xorg/extra-modules with a link.
update-alternatives: removing manually selected alternative - switching x86_64-linux-gnu_gl_conf to auto mode
update-alternatives: using /usr/lib/pxpress/alt_ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) in auto mode.
update-alternatives: using /usr/lib/i386-linux-gnu/mesa/ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_GL.conf (i386-linux-gnu_gl_conf) in auto mode.
update-alternatives: warning: not replacing /usr/lib/i386-linux-gnu/xorg/extra-modules with a link.
update-initramfs: deferring update (trigger activated)
Purging configuration files for fglrx ...
update-initramfs: deferring update (trigger activated)
dpkg: warning: while removing fglrx, directory '/usr/lib/i386-linux-gnu/xorg/extra-modules' not empty so not removed.
Processing triggers for bamfdaemon ...
Rebuilding /usr/share/applications/bamf.index...
Processing triggers for ureadahead ...
ureadahead will be reprofiled on next reboot
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-3.2.0-25-generic-pae
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
Quote: aurelien@aurelien-Studio-1558:~$ sudo rm /etc/X11/xorg.conf
(nothing seems to happen)
Quote: aurelien@aurelien-Studio-1558:~$ sudo apt-get install --reinstall libgl1-mesa-glx:i386 libgl1-mesa-glx:amd64 libgl1-mesa-dri:i386 libgl1-mesa-dri:amd64 xserver-xorg-core
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package libgl1-mesa-glx:amd64
E: Unable to locate package libgl1-mesa-dri:amd64
Quote: aurelien@aurelien-Studio-1558:~$ sudo dpkg-reconfigure xserver-xorg
(nothing seems to happen)
With all those "can't open, warning, unable to locate", I don't know if there isn't already a problem.
|
| aurelienbis |
Sunday 10 June 2012 at 17:08 |
| Rank: Member
|
There is definitely a problem, i can't boot the computer after doing this. I must reinstall 12.4 since a terminal, but there is a problem while installation. (sudo ./amd*)
But I didn't needed to use --force this time. |
| aurelienbis |
Sunday 10 June 2012 at 17:12 |
| Rank: Member
|
If I try to launch D3, debugger give me this :
Quote: Handle Event: "auth validation event"
Handle Event: "auth validation event"
Removing uri "/update/client" since it has no process interested in it.
Request Issued: DELETE /update/Client
Database Remove: /update/Client
Queue 'async_task' Resource for delete
Deferred delete of 'async_task' Resource
Removing uri "/update/diablo3_enus" since it has no process interested in it.
Request Issued: DELETE /update/diablo3_enus
Database Remove: /update/diablo3_enus
Queue 'async_task' Resource for delete
Registered Periodic Event: "shutdown event" with a resolution of 10000 and a start delay of 0
Deferred delete of 'async_task' Resource
Handle Event: "shutdown event"
Handle Event: "auth validation event"
Agent is shutting down
Database Remove: /option
Database Remove: /version/diablo3_enus
Database Remove: /gamesession/client
Database Remove: /gamesession/client/1
Queue 'default' Resource for delete
Deferred delete of 'default' Resource
Database Remove: /agent
Database Remove: /agent/download
Queue 'default' Resource for delete
Database Remove: /
Database Remove: /register
Deferred delete of 'default' Resource
Queue 'registerroot' Resource for delete
Database Remove: /game
Database Remove: /game/diablo3_enus
Deferred delete of 'registerroot' Resource
Queue 'game' Resource for delete
Database Remove: /game/client
Deferred delete of 'game' Resource
Queue 'game' Resource for delete
Deferred delete of 'game' Resource
Queue 'gameroot' Resource for delete
Deferred delete of 'gameroot' Resource
Database Remove: /repair
Queue 'repairroot' Resource for delete
Deferred delete of 'repairroot' Resource
Queue 'agentroot' Resource for delete
Deferred delete of 'agentroot' Resource
Database Remove: /gamesession
Queue 'composite' Resource for delete
Firing Event: "database flush event"
Queue 'gamesessionroot' Resource for delete
Database Remove: /backfill
Queue 'backfillroot' Resource for delete
Database Remove: /spawned
Queue 'spawnedroot' Resource for delete
Queue 'optionroot' Resource for delete
Database Remove: /version
Queue 'async_task' Resource for delete
Queue 'versionroot' Resource for delete
Database Remove: /update
Queue 'updateroot' Resource for delete
Database Remove: /install
Queue 'installroot' Resource for delete
Queue 'root' Resource for delete
Deferred delete of 'composite' Resource
Deleting remaining resources
Deferred delete of 'gamesessionroot' Resource
Deferred delete of 'backfillroot' Resource
Deferred delete of 'spawnedroot' Resource
Deferred delete of 'optionroot' Resource
Deferred delete of 'async_task' Resource
Deferred delete of 'versionroot' Resource
Deferred delete of 'updateroot' Resource
Deferred delete of 'installroot' Resource
Deferred delete of 'root' Resource
ryInternal entry already in cache - don't know what to do!
fixmerocess:GetLogicalProcessorInformation (0xfbe334,0xfbe934): stub
fixmerocess:GetLogicalProcessorInformation (0xfbe304,0xfbe904): stub
fixmerocess:GetLogicalProcessorInformation (0x15be368,0x15be968): stub
fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do!
fixmerocess:GetLogicalProcessorInformation (0xfbe334,0xfbe934): stub
fixmerocess:GetLogicalProcessorInformation (0xfbe304,0xfbe904): stub
fixmerocess:GetLogicalProcessorInformation (0x15be368,0x15be968): stub
fixmerocess:GetLogicalProcessorInformation (0x15be368,0x15be968): stub
fixmerocess:GetLogicalProcessorInformation (0x15be368,0x15be968): stub
fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do!
fixmerocess:GetLogicalProcessorInformation (0xfbe334,0xfbe934): stub
fixmerocess:GetLogicalProcessorInformation (0xfbe304,0xfbe904): stub
fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do!
fixmerocess:GetLogicalProcessorInformation (0xfbe334,0xfbe934): stub
fixmerocess:GetLogicalProcessorInformation (0xfbe304,0xfbe904): stub
fixmerocess:GetLogicalProcessorInformation (0x15be368,0x15be968): stub
fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
fixme:winsock:WSAIoctl WS_SIO_UDP_CONNRESET stub
fixme:win:FlashWindowEx 0x33d3d4
fixme:wininet:CommitUrlCacheEntryInternal entry already in cache - don't know what to do!
fixmerocess:GetLogicalProcessorInformation (0x267e358,0x267e354): stub
fixmerocess:GetLogicalProcessorInformation (0x267e358,0x267e354): stub
X Error of failed request: BadRequest (invalid request code or no such operation)
Major opcode of failed request: 139 (ATIFGLEXTENSION)
Minor opcode of failed request: 66 ()
Serial number of failed request: 1701
Current serial number in output stream: 1701
fixmerocess:GetLogicalProcessorInformation (0x32f3c8,0x32f3c4): stub
fixmerocess:GetLogicalProcessorInformation (0x32f3c8,0x32f3c4): stub
It's getting on my nerves. Can you confirm that all messages I have got while trying to uninstall are normal ?
Thanks. |
| Quentin PÂRIS |
Sunday 10 June 2012 at 17:49 |
| Rank: Admin
|
Citation: X Error of failed request: BadRequest (invalid request code or no such operation)
Major opcode of failed request: 139 (ATIFGLEXTENSION)
It's a ATI driver problem, you have to update your driver to 12.6. |
| gambitho |
Sunday 10 June 2012 at 20:04 |
| Rank: Guest
|
I'm using 12.4 drivers. Those are recommend for my gc (HD 4770).
[quote=atisysteminfo]
ATI System configuration report started Sun Jun 10 18:57:38 CEST 2012 on art.
==========uname -a==========
Linux art 3.2.0-24-generic #39-Ubuntu SMP Mon May 21 16:52:17 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
==========/etc/issue (11:32)==========
Ubuntu 12.04 LTS
\l
==========/proc/version (18:57)==========
Linux version 3.2.0-24-generic (buildd@crested) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #39-Ubuntu SMP Mon May 21 16:52:17 UTC 2012
==========gcc --version==========
gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3
Copyright (C) 2011 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
==========/usr/bin/fglrxinfo==========
libGL: AtiGetClientDriverName: 8.96.4 fglrx (screen 0)
libGL: OpenDriver: trying /usr/lib32/dri/fglrx_dri.so
libGL: OpenDriver: trying /usr/lib/dri/fglrx_dri.so
ukiDynamicMajor: found major device number 250
ukiDynamicMajor: found major device number 250
ukiOpenByBusid: Searching for BusID PCI:1:0:0
ukiOpenDevice: node name is /dev/ati/card0
ukiOpenDevice: open result is 6, (OK)
ukiOpenByBusid: ukiOpenMinor returns 6
ukiOpenByBusid: ukiGetBusid reports PCI:1:0:0
display: :0.0 screen: 0
OpenGL vendor string: Advanced Micro Devices, Inc.
OpenGL renderer string: ATI Radeon HD 4770
OpenGL version string: 3.3.11631 Compatibility Profile Context
==========ldd /usr/bin/fglrxinfo==========
linux-vdso.so.1 => (0x00007fff9987b000)
libGL.so.1 => /usr/lib/libGL.so.1 (0x00007f5aa32d6000)
libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007f5aa2fa2000)
libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x00007f5aa2d90000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f5aa29d3000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f5aa27b6000)
libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007f5aa2597000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f5aa2393000)
/lib64/ld-linux-x86-64.so.2 (0x00007f5aa34fd000)
libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007f5aa2190000)
libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007f5aa1f89000)[/quote] |
| staredit |
Sunday 10 June 2012 at 20:43 |
| Rank: Member
|
So On my old version of linux the 12.6 Catalyst was failing to work, but now just pressing enter seems to initiate an install...
I guess this is all I need to do to get the proper drivers on 12.04?
If this works I'm going to be hyper excited Windows has betrayed me so many times I'd really like to master and use Linux from now on. |
| aurelienbis |
Sunday 10 June 2012 at 20:49 |
| Rank: Member
|
Quote:
It's a ATI driver problem, you have to update your driver to 12.6.
12.6 is not supposed to work with HD 5400... |
| aurelienbis |
Sunday 10 June 2012 at 20:57 |
| Rank: Member
|
It's the second time you tell me to install 12.6, it's the second time I tell you it doesn't work. My GC is not on the list of compatible with 12.6. We won't go anywhere like this. |
| staredit |
Sunday 10 June 2012 at 20:59 |
| Rank: Member
|
Oh fudge... I'm on a 5450
So I'm just out of luck?
I guess I'll complete the installation anyway (it's taking quite a while for some reason, but its moving) and see if anything happens. |
| aurelienbis |
Sunday 10 June 2012 at 21:01 |
| Rank: Member
|
Tell me if it works. I think you'll have a watermark on bottom right (if v12.6) |
| staredit |
Sunday 10 June 2012 at 21:01 |
| Rank: Member
|
"Applicable Products:
This article applies to the following configuration(s):
Hardware:
AMD Radeon HD 7900 Series
AMD Radeon HD 7800 Series
AMD Radeon HD 7700 Series
AMD Radeon HD 6000 Series
AMD Radeon HD 5000 Series"
Per the AMD website it will work for the 5000 series. I haven't tried as much as you though, but at least it seems like it's supposed to work... |
| aurelienbis |
Sunday 10 June 2012 at 21:10 |
| Rank: Member
|
Not sure. I don't see why they would tell 7700,7800 and 7900 while they could tell only 7000 series.
If they say 5000, i think 5400 is different. |
| staredit |
Sunday 10 June 2012 at 21:14 |
| Rank: Member
|
Well, you might well be right, but I'm like a third done now, so I might as well see what there is to be seen...
Any expert here knows what cards these drivers are meant for? |
| Quentin PÂRIS |
Sunday 10 June 2012 at 21:26 |
| Rank: Admin
|
Please read the latest news
Please use the forum to post your problems. Thank you |
| aurelienbis |
Sunday 10 June 2012 at 21:33 |
| Rank: Member
|
Ahem... I think I could install it as it is supposed to be. I'll try to play a little and if there is no freeze I'll copy the way to do it. |
| Quentin PÂRIS |
Sunday 10 June 2012 at 21:46 |
| Rank: Admin
|
It would be helpfup. Thank you |
| aurelienbis |
Sunday 10 June 2012 at 22:40 |
| Rank: Member
|
Okay, so I played for one hour. With low definition, i had like 3 or 4 freezes but they lasts only 10 seconds. Only one freeze made me hard reboot, but it may be due to overheating.
That's the procedure I followed for updating graphic driver with catalyst 12.4.
(remind :
Ubuntu 12.04 32bits
ATI Radeon HD 5400
1.5.5-DiabloIII-v3)
1) Make a copy of what's following, or print it. You may have problem after the first or second reboot.
2) Uninstall old driver throught System setting => Additional driver.
Reboot
3) Uninstall old drivers using these commands :
Quote: 1)Run each of these, one at the time, if getting any faults ignore it:
-sudo sh /usr/share/ati/fglrx-uninstall.sh
-sudo apt-get remove --purge fglrx fglrx_* fglrx-amdcccle* fglrx-dev*
2)Remove your xorg.conf file:
-sudo rm /etc/X11/xorg.conf
3) Re-install xorg:
-sudo apt-get install --reinstall libgl1-mesa-glx:i386 libgl1-mesa-glx:amd64 libgl1-mesa-dri:i386 libgl1-mesa-dri:amd64 xserver-xorg-core
4)Configure xorg:
-sudo dpkg-reconfigure xserver-xorg
5) Reboot:
-sudo reboot
I had a lot of errors, but just ignored them. At this point, after reboot, i could not access left or top toolbar. Only desktop and terminal, that's why i needed to make a copy before.
3) Install new driver (catalyst 12.4) :
Quote:
sudo apt-get install build-essential cdbs dh-make dkms execstack dh-modaliases fakeroot
cd ~/; mkdir catalyst12.4; cd catalyst12.4/
wget http://www2.ati.com/drivers/linux/amd-driver-installer-12-4-x86.x86_64.run
chmod +x amd-driver-installer-12-4-x86.x86_64.run
./amd-driver-installer-12-4-x86.x86_64.run --extract driver
cd driver/common/lib/modules/fglrx/build_mod/
wget -O fglrx.patch http://ubuntuone.com/5gNgEmVfzs3ytD5QZ2YGCi
patch -p1 < fglrx.patch
cd ~/catalyst12.4/driver/ (=> for me it was just ~/driver , then you'll maybe have to find your folder using ls command)
./ati-installer.sh 8.961 --buildpkg Ubuntu/precise
sudo dpkg -i fglrx*.deb
sudo reboot
4) After this reboot, i had a black screen. Then i tape Alt+ctrl+F2, login and wrote startx. (it was maybe useless but i did it anyway xD)
One last sudo reboot.
Game was working after this.
|
| aurelienbis |
Monday 11 June 2012 at 0:31 |
| Rank: Member
|
2 hours without freeze. I confirm that it is correct. (before it was only 3 minutes) |
| staredit |
Monday 11 June 2012 at 1:31 |
| Rank: Member
|
Hmmmm... The game seems to be treating me like I have no drivers at all (gives me the line about the graphics card lacking required features). Will try again. |
| staredit |
Monday 11 June 2012 at 1:45 |
| Rank: Member
|
So, with me it still isn't recognizing any graphics card drivers even though step 3 seemed to go very well. Is there anything I need to do to make diablo 3 recognize the 12.4 catalyst? That seems to be the issue.
I'd also note that neither the side bar or top bar were ever unusable. |
| aurelienbis |
Monday 11 June 2012 at 8:26 |
| Rank: Member
|
Go in PoL => Configure => General => Enable debugging and show what's said. |
| staredit |
Monday 11 June 2012 at 18:23 |
| Rank: Member
|
When I type fglrxinfo in the terminal I get this. I think is confirms that my Drivers failed somewhere along the way... Same thing shows up at the end of the debug log when running D3. I guess this is problem one, then. Trying to google my way through it now, but IF you know the fix for it I'd be happy to hear it
X Error of failed request: BadRequest (invalid request code or no such operation)
Major opcode of failed request: 139 (ATIFGLEXTENSION)
Minor opcode of failed request: 66 ()
Serial number of failed request: 13
Current serial number in output stream: 13
|
| Quentin PÂRIS |
Monday 11 June 2012 at 19:04 |
| Rank: Admin
|
Please use the forum. Thank you |
| ovisan |
Tuesday 12 June 2012 at 19:49 |
| Rank: Member
|
Thanks Obsi, reinstalling the drivers as specified helped. The freeze was gone.
Ocassionally the game it's closing but it's very rare. |
