BIOS flash resulting in bad game performance?
Motherboard: K8N Neo2 Platinum
Yesterday I flashed my BIOS to version 1.C, because of problems when rebooting the computer from Windows (booting would get stuck at the Gigabit Boot Agent, until network cable was removed). The flash was successful, however I noticed a great decrease in game performance after booting into Windows. Games like WoW and F.E.A.R. Combat had their fps reduced to less then 30 fps, where 40-50 fps were not abnormal before the flash.
I talked to a few people about this and due to their advice I tried reinstalling the motherboard and graphics card drivers. To no avail. 3DMark2001 benchmarks showed a score of 11000, where I got a score of 15000 when I tested my rig a few months ago.
This morning I completely formatted my Windows drive and reinstalled Windows, including all new drivers for motherboard, graphics card, you name it. Still my 3DMark2001 score won't go beyond 11600.
I checked everything possible in BIOS and Windows:
CPU settings are ok,
memory settings are ok,
harddisks are configured for UltraDMA5,
graphics card core and mem clocks are ok,
all possibly performance reducing services and programs are shut down.
I can't think of anything else reducing my computer's performance, but can't also think of the BIOS influencing this performance.
Image of new and old benchmark:
http://www.sloefke.eu/f/benchmarks.jpg
Should I try reflashing the BIOS, and if so:
a) to which version?
b) is reinstalling of drivers really necessary?
Quote from: kakarocht on 01-September-06, 22:59:01
I'm sure that you're using liveupdate?
Nope.
Quote
tried to used the manual way to flashed it.
I flashed the BIOS manually, if that's what you're asking.
Quote
I've same mobo like yours and used Bios 1C from Syar's. Refer to my sig in order to flashed it. ALso troed to reset your BIOS by removing the CMOS battery and leave it for 10-30 min make sure you've removed the power cord as well as power connectors and load all the default setting before you need to reflashed it again. Gd luck
I don't fully understand this part of your reply. Should I first remove the battery and then reflash the BIOS? What's the difference between removing the battery and resetting the BIOS with the JBAT jumper?
And what are the modifications of the Syar BIOS compared to the MSI 1.C BIOS? Will it resolve my problem?
Similar Messages
-
BIOS flash results inconsistencies
I will be the first to admit that I don't know what the heck I'm talking about
Just looking for comments on this phenomenon.
But I noticed many people's results from BIOS flashing are inconsistent for the same BIOS version. If two people flash to the same BIOS, one may run flawlessly and the other one's goes berserk.
Could it be that different people use different options when flashing? See this thread:
Winflash help with BETA BIOS, thanks.
Not everyone uses winflash but even dos flash has command line options. Some people think only bootblock needs to be flashed whereas others think everything should be flashed. Won't different degrees of flashing give different results?
I know this isn't the only reason. Everyone has different hardware, which is probably the main reason why one BIOS doesn't work the same for everyone. But I also wonder how consistent the results would be if everyone used the same BIOS flash options?
Am I in left field here? feel free to educate me or pontificate further.HERE is the download link for Version 2.0. However, chances are very high that you will NOT be allowed to install an earlier version. If it were me, I would keep it as is and just don't try to use Fast Boot. Fast Boot is not all it's cracked up to be, loads very little faster and causes other problems at times.
C.B.
C.B.
Toshiba Sat. C75D-B7260 Win 8.1 64 Bit--Toshiba Sat. L775D-S7132 Win 7 HP SP1 64 Bit and Win 10 PRO Technical Preview--Toshiba Sat. L305-S5921 Win Vista SP2 32 Bit -
Bad game performance, but, why?
I got my new computer yesterday. It's a macintosh 2ghz 20-inch iMac, with Memory of 512 mb ram and under the memory section in about this computer it says its running at 667mhz. I have 256mb ATI Radeon X1600 graphics card and 207.96 gb free in my macintosh HD.
I have been having really crappy game performance. THe only game I have is UT2004, but I can't play it at all with the graphics turned up, and while single player works once i put them down to average quality, but even at LOWEST quality multiplayer is really hiccupy. Why is this and can I fix it?
Message was edited by: James BoshaHi there,
here is the link to explain the memory you need to buy and how to fit it yourself....(Very easy to do, by the way)
http://docs.info.apple.com/article.html?artnum=303085
With regards to how much it costs, the Apple online store will sell it to you...check it out!
Are you in the UK?
Stephen.
iMac Intel 2GHz Core Duo and iBook G4 1.2GHz Mac OS X (10.4.6) -
Hello!
My system is 64bit Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz with Nvidia G635M on my lapton. There are a lot of post in Internet saying that Left for dead 2 in Linux has more fps than in windows. But for me on Windows everything is smooth, but on Linux game freeze for a second sometimes, game video settings is the same on both systems.
I've found this post https://bbs.archlinux.org/viewtopic.php?pid=1284496 . There Svenstaro say "Your 32bit chain is completely broken..." how did he find it out? Is my 32bit chain is broken too?
kurban ~ $ primusrun steam steam://rungameid/550
Running Steam on arch rolling 64-bit
STEAM_RUNTIME is enabled automatically
Installing breakpad exception handler for appid(steam)/version(1411443970)
Installing breakpad exception handler for appid(steam)/version(1411443970)
Installing breakpad exception handler for appid(steam)/version(1411443970)
Installing breakpad exception handler for appid(steamwebhelper)/version(20140922201705)
Installing breakpad exception handler for appid(steamwebhelper)/version(1411417025)
Installing breakpad exception handler for appid(steamwebhelper)/version(20140922201705)
Installing breakpad exception handler for appid(steamwebhelper)/version(1411417025)
Installing breakpad exception handler for appid(steam)/version(1411443970)
Installing breakpad exception handler for appid(steam)/version(1411443970)
Installing breakpad exception handler for appid(steam)/version(1411443970)
Installing breakpad exception handler for appid(steam)/version(1411443970)
Installing breakpad exception handler for appid(steam)/version(1411443970)
** (steam:19824): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files
** (steam:19824): WARNING **: Error enabling/disabling networking: The name org.freedesktop.NetworkManager was not provided by any .service files
Installing breakpad exception handler for appid(steam)/version(1411443970)
Generating new string page texture 2: 48x256, total string texture memory is 49.15 KB
Generating new string page texture 3: 256x256, total string texture memory is 311.30 KB
Installing breakpad exception handler for appid(steam)/version(1411443970)
Installing breakpad exception handler for appid(steam)/version(1411443970)
Adding licenses for the following package(s): 0, 1290, 1347, 1465, 2208, 2481, 4819, 12361, 12558, 13944, 14694, 14840, 16547, 18029, 18691, 21426, 25526, 32579, 35695, 51437, 51730, 52296, 52326, 52661
roaming config store loaded successfully - 1119 bytes.
migrating temporary roaming config store
Installing breakpad exception handler for appid(steam)/version(1411443970)
Failed to init SteamVR because it isn't installed
ExecCommandLine: ""/home/kurban/.local/share/Steam/ubuntu12_32/steam" "steam://rungameid/550" "
ExecSteamURL: "steam://rungameid/550"
System startup time: 15.35 seconds
Game update: AppID 550 "Left 4 Dead 2", ProcID 20105, IP 0.0.0.0:0
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
ERROR: ld.so: object '/home/kurban/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/kurban/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/kurban/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
pid 20137 != 20106, skipping destruction (fork without exec?)
Running Steam on arch rolling 64-bit
STEAM_RUNTIME has been set by the user to: /home/kurban/.local/share/Steam/ubuntu12_32/steam-runtime
ERROR: ld.so: object '/home/kurban/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/kurban/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ExecCommandLine: "/home/kurban/.steam/root/ubuntu12_32/steam steam://open/driverhelperready"
ExecSteamURL: "steam://open/driverhelperready"
SDL video target is 'x11'
Installing breakpad exception handler for appid(steam)/version(1411443970)
Using breakpad crash handler
Setting breakpad minidump AppID = 550
Forcing breakpad minidump interfaces to load
Looking up breakpad interfaces from steamclient
Calling BreakpadMiniDumpSystemInit
Looking up breakpad interfaces from steamclient
Calling BreakpadMiniDumpSystemInit
Steam_SetMinidumpSteamID: Caching Steam ID: 76561198079673489 [API loaded yes]
Steam_SetMinidumpSteamID: Setting Steam ID: 76561198079673489
[1012/181431:ERROR:resource_bundle.cc(411)] Failed to load /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/cef_gtk.pak
Some features may not be available.
[1012/181431:ERROR:object_proxy.cc(239)] Failed to call method: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files
[1012/181431:WARNING:proxy_service.cc(646)] PAC support disabled because there is no system implementation
SDL video target is 'x11'
SDL failed to create GL compatibility profile (whichProfile=0!
This system supports the OpenGL extension GL_EXT_framebuffer_object.
This system supports the OpenGL extension GL_EXT_framebuffer_blit.
This system supports the OpenGL extension GL_EXT_framebuffer_multisample.
This system DOES NOT support the OpenGL extension GL_APPLE_fence.
This system supports the OpenGL extension GL_NV_fence.
This system supports the OpenGL extension GL_ARB_sync.
This system supports the OpenGL extension GL_EXT_draw_buffers2.
This system supports the OpenGL extension GL_EXT_bindable_uniform.
This system DOES NOT support the OpenGL extension GL_APPLE_flush_buffer_range.
This system supports the OpenGL extension GL_ARB_map_buffer_range.
This system supports the OpenGL extension GL_ARB_vertex_buffer_object.
This system supports the OpenGL extension GL_ARB_occlusion_query.
This system DOES NOT support the OpenGL extension GL_APPLE_texture_range.
This system DOES NOT support the OpenGL extension GL_APPLE_client_storage.
This system DOES NOT support the OpenGL extension GL_ARB_uniform_buffer.
This system supports the OpenGL extension GL_ARB_vertex_array_bgra.
This system supports the OpenGL extension GL_EXT_vertex_array_bgra.
This system supports the OpenGL extension GL_ARB_framebuffer_object.
This system DOES NOT support the OpenGL extension GL_GREMEDY_string_marker.
This system supports the OpenGL extension GL_ARB_debug_output.
This system supports the OpenGL extension GL_EXT_direct_state_access.
This system DOES NOT support the OpenGL extension GL_NV_bindless_texture.
This system DOES NOT support the OpenGL extension GL_AMD_pinned_memory.
This system supports the OpenGL extension GL_EXT_framebuffer_multisample_blit_scaled.
This system supports the OpenGL extension GL_EXT_texture_sRGB_decode.
This system supports the OpenGL extension GL_NVX_gpu_memory_info.
This system DOES NOT support the OpenGL extension GL_ATI_meminfo.
This system supports the OpenGL extension GL_EXT_texture_compression_s3tc.
This system supports the OpenGL extension GL_EXT_texture_compression_dxt1.
This system DOES NOT support the OpenGL extension GL_ANGLE_texture_compression_dxt3.
This system DOES NOT support the OpenGL extension GL_ANGLE_texture_compression_dxt5.
This system DOES NOT support the OpenGL extension GLX_EXT_swap_control_tear.
GL_NV_bindless_texture: DISABLED
GL_AMD_pinned_memory: DISABLED
GL_EXT_texture_sRGB_decode: AVAILABLE
GL_NVX_gpu_memory_info: AVAILABLE
GL_ATI_meminfo: UNAVAILABLE
GL_NVX_gpu_memory_info: Total Dedicated: 2097152, Total Avail: 2097152, Current Avail: 2066364
GL_MAX_SAMPLES_EXT: 32
Did not detect any valid joysticks.
Querying for subscribed files
IDirect3DDevice9::Create: BackBufWidth: 1366, BackBufHeight: 768, D3DFMT: 3, BackBufCount: 2, MultisampleType: 2, MultisampleQuality: 0
GL sampler object usage: ENABLED
GL prefer MapBufferRange: NO
BinkOpen( /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/media/valve.bik )
ConVarRef volume doesn't point to an existing ConVar
BinkOpen( /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/media/l4d2_intro.bik )
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x0000000E) differs from mask derived from shader name (0x0000001F) for shader ps-file shadow_ps20b ps-index 1 ps-combo 0
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x000000E0) differs from mask derived from shader name (0x000000C0) for shader ps-file water_ps20b ps-index 8 ps-combo 0
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x0000000E) differs from mask derived from shader name (0x0000001F) for shader ps-file shadow_ps20b ps-index 0 ps-combo 0
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x000000E0) differs from mask derived from shader name (0x000000C0) for shader ps-file water_ps20b ps-index 1272 ps-combo 0
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x000000E0) differs from mask derived from shader name (0x000000C0) for shader ps-file water_ps20b ps-index 1272 ps-combo 1Installing breakpad exception handler for appid(hl2_linux)/version(1.0)
Looking up breakpad interfaces from steamclient
Calling BreakpadMiniDumpSystemInit
Steam_SetMinidumpSteamID: Caching Steam ID: 76561198079673489 [API loaded yes]
Steam_SetMinidumpSteamID: Setting Steam ID: 76561198079673489
warning: Unknown nb_ctl request: 4
warning: Unknown nb_ctl request: 4
warning: Unknown nb_ctl request: 4
warning: Unknown nb_ctl request: 4
warning: Unknown nb_ctl request: 4
warning: Unknown nb_ctl request: 4
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x000000E0) differs from mask derived from shader name (0x000000C0) for shader ps-file water_ps20b ps-index 20 ps-combo 0
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x000000E0) differs from mask derived from shader name (0x000000C0) for shader ps-file water_ps20b ps-index 464 ps-combo 0
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x000000E0) differs from mask derived from shader name (0x000000C0) for shader ps-file water_ps20b ps-index 464 ps-combo 1
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x000000E0) differs from mask derived from shader name (0x000000C0) for shader ps-file water_ps20b ps-index 392 ps-combo 0
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x000000E0) differs from mask derived from shader name (0x000000C0) for shader ps-file water_ps20b ps-index 392 ps-combo 1
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x000000E0) differs from mask derived from shader name (0x000000C0) for shader ps-file water_ps20b ps-index 504 ps-combo 0
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x000000E0) differs from mask derived from shader name (0x000000C0) for shader ps-file water_ps20b ps-index 504 ps-combo 1
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x000000E0) differs from mask derived from shader name (0x000000C0) for shader ps-file water_ps20b ps-index 80 ps-combo 0
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x000000E0) differs from mask derived from shader name (0x000000C0) for shader ps-file water_ps20b ps-index 120 ps-combo 0
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x000000E0) differs from mask derived from shader name (0x000000C0) for shader ps-file water_ps20b ps-index 72 ps-combo 0
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x000000E0) differs from mask derived from shader name (0x000000C0) for shader ps-file water_ps20b ps-index 888 ps-combo 0
Loaded program cache file "glbaseshaders.cfg", total keyvalues: 738, total successfully linked: 738
Loaded program cache file "glshaders.cfg", total keyvalues: 0, total successfully linked: 0
Precache: Took 2091 ms, Vertex 1072, Pixel 870
Game.so loaded for "Left 4 Dead 2"
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x0000000E) differs from mask derived from shader name (0x0000001F) for shader ps-file shadow_ps20b ps-index 1 ps-combo 0
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x0000000E) differs from mask derived from shader name (0x0000001F) for shader ps-file shadow_ps20b ps-index 0 ps-combo 0
Unable to remove /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/textwindow_temp.html!
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_000.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_000.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_011.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_011.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_007.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_007.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/update/pak01_000.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/update/pak01_000.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_008.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_008.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2_dlc3/pak01_000.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2_dlc3/pak01_000.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2_dlc3/pak01_003.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2_dlc3/pak01_003.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2_dlc2/pak01_001.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2_dlc2/pak01_001.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2_dlc1/pak01_000.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2_dlc1/pak01_000.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2_dlc2/pak01_000.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2_dlc2/pak01_000.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_002.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_002.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_003.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_003.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_010.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_010.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_009.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_009.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_001.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_001.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_004.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_004.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_005.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_005.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_006.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_006.vpk was never closed
/home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/./hl2.sh: line 67: 20163 Segmentation fault ${GAME_DEBUGGER} "${GAMEROOT}"/${GAMEEXE} "$@"
Game removed: AppID 550 "Left 4 Dead 2", ProcID 20163
Installing breakpad exception handler for appid(steam)/version(1411443970)
[1012/181603:ERROR:renderer_main.cc(227)] Running without renderer sandbox
kurban ~ $ pacman -Qs lib32
local/lib32-acl 2.2.52-2
Access control list libraries (32-bit)
local/lib32-alsa-lib 1.0.28-1
An alternative implementation of Linux sound support (32 bit)
local/lib32-alsa-plugins 1.0.28-1
Extra alsa plugins (32-bit)
local/lib32-atk 2.12.0-1
A library providing a set of interfaces for accessibility (32-bit)
local/lib32-attr 2.4.47-1
Extended attribute support library for ACL support (32-bit)
local/lib32-bzip2 1.0.6-2
A high-quality data compression program (32-bit)
local/lib32-cairo 1.12.16-1
Cairo vector graphics library (32-bit)
local/lib32-curl 7.38.0-1
An URL retrieval utility and library (32-bit)
local/lib32-db 5.3.28-1
The Berkeley DB embedded database system
local/lib32-e2fsprogs 1.42.12-1
Ext2 filesystem libraries (32-bit)
local/lib32-elfutils 0.159-1
Collection of libraries for working with ELF object files and DWARF debugging information (32-bit)
local/lib32-expat 2.1.0-2
An XML Parser library written in C (32 bit)
local/lib32-flac 1.3.0-1
Free Lossless Audio Codec (32-bit)
local/lib32-flashplugin 11.2.202.406-1
Adobe Flash Player for 32-bit Mozilla-based browsers
local/lib32-fontconfig-infinality-ultimate 2.11.1-3 (infinality-bundle-multilib)
A library for configuring and customizing font access (32-bit, infinality-bundle)
local/lib32-freetype2-infinality-ultimate 2.5.3-11 (infinality-bundle-multilib)
TrueType font rendering library with Infinality patches and custom settings by bohoomil (32-bit, infinality-bundle).
local/lib32-gcc-libs 4.9.1-2
Runtime libraries shipped by GCC (32-bit)
local/lib32-gdk-pixbuf2 2.30.8-1
An image loading library (32-bit)
local/lib32-gettext 0.19.2-1
GNU internationalization library (32-bit)
local/lib32-glew 1.11.0-1
A cross-platform C/C++ extension loading library (32 bit)
local/lib32-glib2 2.40.0-1
Common C routines used by GTK+ 2.4 and other libs (32-bit)
local/lib32-glibc 2.20-2
GNU C Library (32-bit)
local/lib32-glu 9.0.0-2
Mesa OpenGL utility library (32 bits)
local/lib32-gmp 6.0.0-1
A free library for arbitrary precision arithmetic (32-bit)
local/lib32-gtk2 2.24.24-1
The GTK+ Toolkit (v2) (32-bit)
local/lib32-harfbuzz 0.9.35-1
OpenType text shaping engine. (32-bit)
local/lib32-icu 53.1-1
International Components for Unicode library (32 bit)
local/lib32-jack 0.124.1-1
A low-latency audio server (32-bit)
local/lib32-json-c 0.12-1
A JSON implementation in C (32-bit)
local/lib32-keyutils 1.5.9-1
Linux Key Management Utilities (32-bit)
local/lib32-krb5 1.12.2-1
The Kerberos network authentication system (32-bit)
local/lib32-lcms2 2.6-1
Small-footprint color management engine, version 2 (32-bit)
local/lib32-libasyncns 0.8-7
A C library for Linux/Unix for executing name service queries asynchronously (32-bit)
local/lib32-libcap 2.24-1
POSIX 1003.1e capabilities (32-bit)
local/lib32-libcups 1.7.5-1
The CUPS Printing System - client libraries (32-bit)
local/lib32-libdbus 1.8.8-1
DBus library (32-bit)
local/lib32-libdrm 2.4.58-1
Userspace interface to kernel DRM services (32-bit)
local/lib32-libffi 3.1-1
A portable, high level programming interface to various calling conventions (32-bit)
local/lib32-libgcrypt 1.6.2-1
General purpose cryptographic library based on the code from GnuPG (32-bit)
local/lib32-libglade 2.6.4-6
Allows you to load glade interface files in a program at runtime (32-bit)
local/lib32-libgpg-error 1.16-1
Support library for libgcrypt (32-bit)
local/lib32-libice 1.0.9-1
X11 Inter-Client Exchange library (32-bit)
local/lib32-libjpeg-turbo 1.3.1-1
libjpeg derivative with accelerated baseline JPEG compression and decompression (32-bit)
local/lib32-libldap 2.4.40-1
Lightweight Directory Access Protocol (LDAP) client libraries (32-bit)
local/lib32-libmng 2.0.2-1
A collection of routines used to create and manipulate MNG format graphics files (32-bit)
local/lib32-libogg 1.3.1-1
Ogg bitstream and framing library (32-bit)
local/lib32-libpciaccess 0.13.2-1
X11 PCI access library (32-bit
local/lib32-libpng 1.6.13-1
A collection of routines used to create PNG format graphics files (32-bit)
local/lib32-libpng12 1.2.51-2
A collection of routines used to create PNG format graphics files (32-bit, 1.2 branch)
local/lib32-libpulse 5.0-1
A featureful, general-purpose sound server (32-bit client libraries)
local/lib32-libsamplerate 0.1.8-2
Secret Rabbit Code - aka Sample Rate Converter for audio (32-bit)
local/lib32-libsm 1.2.2-1
X11 Session Management library (32-bit)
local/lib32-libsndfile 1.0.25-3
A C library for reading and writing files containing sampled sound (32-bit)
local/lib32-libssh2 1.4.3-2
A library implementing the SSH2 protocol as defined by Internet Drafts (32-bit)
local/lib32-libtasn1 4.1-1
The ASN.1 library used in GNUTLS (32 bit)
local/lib32-libtiff 4.0.3-2
Library for manipulation of TIFF images (32-bit)
local/lib32-libtxc_dxtn 1.0.1-5
S3 Texture Compression (S3TC) library for Mesa (32-bit)
local/lib32-libvdpau 0.8-1
Nvidia VDPAU library
local/lib32-libvorbis 1.3.4-1
Vorbis codec library (32-bit)
local/lib32-libx11 1.6.2-1
X11 client-side library (32-bit)
local/lib32-libxau 1.0.8-1
X11 authorisation library (32-bit)
local/lib32-libxcb 1.11-1
X11 client-side library (32-bit)
local/lib32-libxcomposite 0.4.4-2
X11 Composite extension library (32-bit)
local/lib32-libxcursor 1.1.14-1
X cursor management library (32-bit)
local/lib32-libxdamage 1.1.4-2
X11 damaged region extension library (32-bit)
local/lib32-libxdmcp 1.1.1-2
X11 Display Manager Control Protocol library (32-bit)
local/lib32-libxext 1.3.3-1
X11 miscellaneous extensions library (32-bit)
local/lib32-libxfixes 5.0.1-1
X11 miscellaneous 'fixes' extension library (32-bit)
local/lib32-libxft 2.3.2-1
FreeType-based font drawing library for X (32-bit)
local/lib32-libxi 1.7.4-1
X11 Input extension library (32-bit)
local/lib32-libxinerama 1.1.3-1
X11 Xinerama extension library (32-bit)
local/lib32-libxml2 2.9.1-1
XML parsing library, version 2 (32-bit)
local/lib32-libxmu 1.1.2-1
X11 miscellaneous micro-utility library (32-bit)
local/lib32-libxrandr 1.4.2-1
X11 RandR extension library (32-bit)
local/lib32-libxrender 0.9.8-1
X Rendering Extension client library (32-bit)
local/lib32-libxshmfence 1.1-1
a library that exposes a event API on top of Linux futexes (32-bit)
local/lib32-libxss 1.2.2-2
X11 Screen Saver extension library (32-bit)
local/lib32-libxt 1.1.4-1
X11 toolkit intrinsics library (32-bit)
local/lib32-libxtst 1.2.2-1
X11 Testing -- Resource extension library (32-bit)
local/lib32-libxv 1.0.10-1
X11 Video extension library (32-bit)
local/lib32-libxxf86vm 1.1.3-1
X11 XFree86 video mode extension library (32-bit)
local/lib32-llvm-amdgpu-lib-snapshot 20130403-2
Low Level Virtual Machine with AMDGPU enabled to build r600g shader llvm support (32-bits)
local/lib32-llvm-libs 3.5.0-1
Low Level Virtual Machine (runtime library)(32-bit)
local/lib32-mesa 10.3.0-3
an open-source implementation of the OpenGL specification (32-bit)
local/lib32-mesa-demos 8.2.0-2
Mesa demos and tools (32-bit)
local/lib32-mesa-dri 10.3.0-3
Mesa DRI drivers (32-bit)
local/lib32-mesa-libgl 10.3.0-3
Mesa 3-D graphics library (32-bit)
local/lib32-mesa-vdpau 10.3.0-3
Mesa VDPAU drivers (32-bit)
local/lib32-ncurses 5.9-3
System V Release 4.0 curses emulation library (32-bit)
local/lib32-nspr 4.10.7-1
Netscape Portable Runtime (32-bit)
local/lib32-nss 3.17-1
Mozilla Network Security Services (32-bit)
local/lib32-nvidia-utils 343.22-1
NVIDIA drivers utilities (32-bit)
local/lib32-openssl 1.0.1.i-1
The Open Source toolkit for Secure Sockets Layer and Transport Layer Security (32-bit)
local/lib32-p11-kit 0.20.7-3
Library to work with PKCS#11 modules (32-bit)
local/lib32-pango 1.36.6-1
A library for layout and rendering of text (32-bit)
local/lib32-pcre 8.35-1
A library that implements Perl 5-style regular expressions (32-bit)
local/lib32-pixman 0.32.6-1
Pixman library (32-bit)
local/lib32-portaudio 19_20140130-1
A free, cross-platform, open source, audio I/O library. (32 bit)
local/lib32-primus 20131226-1
Faster OpenGL offloading for Bumblebee (32-bit)
local/lib32-qt4 4.8.6-1
A cross-platform application and UI framework (32-bit)
local/lib32-readline 6.3.006-1
GNU readline library (32-bit)
local/lib32-sqlite 3.8.6-1
A C library that implements an SQL database engine (32-bit)
local/lib32-systemd 216-2
system and service manager (32-bit)
local/lib32-util-linux 2.25.1-2
Miscellaneous system utilities for Linux (32-bit)
local/lib32-v4l-utils 1.2.1-1
Userspace tools and conversion library for Video 4 Linux (32-bit)
local/lib32-wayland 1.6.0-1
A computer display server protocol
local/lib32-xz 5.0.5-1
Library and command line tools for XZ and LZMA compressed files (32-bit)
local/lib32-zlib 1.2.8-1
Compression library implementing the deflate compression method found in gzip and PKZIP (32-bit)
kurban ~ $ pacman -Qs nvidia
local/bumblebee 3.2.1-5
NVIDIA Optimus support for Linux through VirtualGL
local/cpyrit-cuda 0.4.0-2
Pyrit support for Nvidia-CUDA.
local/cuda 6.5.14-1
NVIDIA's GPU programming toolkit
local/lib32-libvdpau 0.8-1
Nvidia VDPAU library
local/lib32-nvidia-utils 343.22-1
NVIDIA drivers utilities (32-bit)
local/libcl 1.1-4
OpenCL library and ICD loader from NVIDIA
local/libvdpau 0.8-1
Nvidia VDPAU library
local/nvidia 343.22-2
NVIDIA drivers for linux
local/nvidia-utils 343.22-1
NVIDIA drivers utilities
local/opencl-nvidia 343.22-1
OpenCL implemention for NVIDIA
kurban ~ $ pacman -Qs bumblebee
local/bumblebee 3.2.1-5
NVIDIA Optimus support for Linux through VirtualGL
local/lib32-primus 20131226-1
Faster OpenGL offloading for Bumblebee (32-bit)
local/primus 20131226-1
Faster OpenGL offloading for Bumblebee
kurban ~ $ pacman -Qs mesa
local/glu 9.0.0-3
Mesa OpenGL Utility library
local/lib32-glu 9.0.0-2
Mesa OpenGL utility library (32 bits)
local/lib32-libtxc_dxtn 1.0.1-5
S3 Texture Compression (S3TC) library for Mesa (32-bit)
local/lib32-mesa 10.3.0-3
an open-source implementation of the OpenGL specification (32-bit)
local/lib32-mesa-demos 8.2.0-2
Mesa demos and tools (32-bit)
local/lib32-mesa-dri 10.3.0-3
Mesa DRI drivers (32-bit)
local/lib32-mesa-libgl 10.3.0-3
Mesa 3-D graphics library (32-bit)
local/lib32-mesa-vdpau 10.3.0-3
Mesa VDPAU drivers (32-bit)
local/libtxc_dxtn 1.0.1-5
S3 Texture Compression (S3TC) library for Mesa
local/mesa 10.3.0-3
an open-source implementation of the OpenGL specification
local/mesa-demos 8.2.0-3
Mesa demos and tools
local/mesa-dri 10.3.0-3
Mesa DRI drivers
local/mesa-libgl 10.3.0-3
Mesa 3-D graphics library
At topic, that I pointed to, author wrote that he deleted lib32-libtxc_dxtn, but I can't because lib32-mesa-dri requires lib32-libtxc_dxtn
Last edited by remutik4 (2014-10-12 14:28:26)Hello!
My system is 64bit Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz with Nvidia G635M on my lapton. There are a lot of post in Internet saying that Left for dead 2 in Linux has more fps than in windows. But for me on Windows everything is smooth, but on Linux game freeze for a second sometimes, game video settings is the same on both systems.
I've found this post https://bbs.archlinux.org/viewtopic.php?pid=1284496 . There Svenstaro say "Your 32bit chain is completely broken..." how did he find it out? Is my 32bit chain is broken too?
kurban ~ $ primusrun steam steam://rungameid/550
Running Steam on arch rolling 64-bit
STEAM_RUNTIME is enabled automatically
Installing breakpad exception handler for appid(steam)/version(1411443970)
Installing breakpad exception handler for appid(steam)/version(1411443970)
Installing breakpad exception handler for appid(steam)/version(1411443970)
Installing breakpad exception handler for appid(steamwebhelper)/version(20140922201705)
Installing breakpad exception handler for appid(steamwebhelper)/version(1411417025)
Installing breakpad exception handler for appid(steamwebhelper)/version(20140922201705)
Installing breakpad exception handler for appid(steamwebhelper)/version(1411417025)
Installing breakpad exception handler for appid(steam)/version(1411443970)
Installing breakpad exception handler for appid(steam)/version(1411443970)
Installing breakpad exception handler for appid(steam)/version(1411443970)
Installing breakpad exception handler for appid(steam)/version(1411443970)
Installing breakpad exception handler for appid(steam)/version(1411443970)
** (steam:19824): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files
** (steam:19824): WARNING **: Error enabling/disabling networking: The name org.freedesktop.NetworkManager was not provided by any .service files
Installing breakpad exception handler for appid(steam)/version(1411443970)
Generating new string page texture 2: 48x256, total string texture memory is 49.15 KB
Generating new string page texture 3: 256x256, total string texture memory is 311.30 KB
Installing breakpad exception handler for appid(steam)/version(1411443970)
Installing breakpad exception handler for appid(steam)/version(1411443970)
Adding licenses for the following package(s): 0, 1290, 1347, 1465, 2208, 2481, 4819, 12361, 12558, 13944, 14694, 14840, 16547, 18029, 18691, 21426, 25526, 32579, 35695, 51437, 51730, 52296, 52326, 52661
roaming config store loaded successfully - 1119 bytes.
migrating temporary roaming config store
Installing breakpad exception handler for appid(steam)/version(1411443970)
Failed to init SteamVR because it isn't installed
ExecCommandLine: ""/home/kurban/.local/share/Steam/ubuntu12_32/steam" "steam://rungameid/550" "
ExecSteamURL: "steam://rungameid/550"
System startup time: 15.35 seconds
Game update: AppID 550 "Left 4 Dead 2", ProcID 20105, IP 0.0.0.0:0
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
(steam:19824): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're it's parent.
ERROR: ld.so: object '/home/kurban/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/kurban/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/kurban/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
pid 20137 != 20106, skipping destruction (fork without exec?)
Running Steam on arch rolling 64-bit
STEAM_RUNTIME has been set by the user to: /home/kurban/.local/share/Steam/ubuntu12_32/steam-runtime
ERROR: ld.so: object '/home/kurban/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/kurban/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ExecCommandLine: "/home/kurban/.steam/root/ubuntu12_32/steam steam://open/driverhelperready"
ExecSteamURL: "steam://open/driverhelperready"
SDL video target is 'x11'
Installing breakpad exception handler for appid(steam)/version(1411443970)
Using breakpad crash handler
Setting breakpad minidump AppID = 550
Forcing breakpad minidump interfaces to load
Looking up breakpad interfaces from steamclient
Calling BreakpadMiniDumpSystemInit
Looking up breakpad interfaces from steamclient
Calling BreakpadMiniDumpSystemInit
Steam_SetMinidumpSteamID: Caching Steam ID: 76561198079673489 [API loaded yes]
Steam_SetMinidumpSteamID: Setting Steam ID: 76561198079673489
[1012/181431:ERROR:resource_bundle.cc(411)] Failed to load /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/cef_gtk.pak
Some features may not be available.
[1012/181431:ERROR:object_proxy.cc(239)] Failed to call method: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.NetworkManager was not provided by any .service files
[1012/181431:WARNING:proxy_service.cc(646)] PAC support disabled because there is no system implementation
SDL video target is 'x11'
SDL failed to create GL compatibility profile (whichProfile=0!
This system supports the OpenGL extension GL_EXT_framebuffer_object.
This system supports the OpenGL extension GL_EXT_framebuffer_blit.
This system supports the OpenGL extension GL_EXT_framebuffer_multisample.
This system DOES NOT support the OpenGL extension GL_APPLE_fence.
This system supports the OpenGL extension GL_NV_fence.
This system supports the OpenGL extension GL_ARB_sync.
This system supports the OpenGL extension GL_EXT_draw_buffers2.
This system supports the OpenGL extension GL_EXT_bindable_uniform.
This system DOES NOT support the OpenGL extension GL_APPLE_flush_buffer_range.
This system supports the OpenGL extension GL_ARB_map_buffer_range.
This system supports the OpenGL extension GL_ARB_vertex_buffer_object.
This system supports the OpenGL extension GL_ARB_occlusion_query.
This system DOES NOT support the OpenGL extension GL_APPLE_texture_range.
This system DOES NOT support the OpenGL extension GL_APPLE_client_storage.
This system DOES NOT support the OpenGL extension GL_ARB_uniform_buffer.
This system supports the OpenGL extension GL_ARB_vertex_array_bgra.
This system supports the OpenGL extension GL_EXT_vertex_array_bgra.
This system supports the OpenGL extension GL_ARB_framebuffer_object.
This system DOES NOT support the OpenGL extension GL_GREMEDY_string_marker.
This system supports the OpenGL extension GL_ARB_debug_output.
This system supports the OpenGL extension GL_EXT_direct_state_access.
This system DOES NOT support the OpenGL extension GL_NV_bindless_texture.
This system DOES NOT support the OpenGL extension GL_AMD_pinned_memory.
This system supports the OpenGL extension GL_EXT_framebuffer_multisample_blit_scaled.
This system supports the OpenGL extension GL_EXT_texture_sRGB_decode.
This system supports the OpenGL extension GL_NVX_gpu_memory_info.
This system DOES NOT support the OpenGL extension GL_ATI_meminfo.
This system supports the OpenGL extension GL_EXT_texture_compression_s3tc.
This system supports the OpenGL extension GL_EXT_texture_compression_dxt1.
This system DOES NOT support the OpenGL extension GL_ANGLE_texture_compression_dxt3.
This system DOES NOT support the OpenGL extension GL_ANGLE_texture_compression_dxt5.
This system DOES NOT support the OpenGL extension GLX_EXT_swap_control_tear.
GL_NV_bindless_texture: DISABLED
GL_AMD_pinned_memory: DISABLED
GL_EXT_texture_sRGB_decode: AVAILABLE
GL_NVX_gpu_memory_info: AVAILABLE
GL_ATI_meminfo: UNAVAILABLE
GL_NVX_gpu_memory_info: Total Dedicated: 2097152, Total Avail: 2097152, Current Avail: 2066364
GL_MAX_SAMPLES_EXT: 32
Did not detect any valid joysticks.
Querying for subscribed files
IDirect3DDevice9::Create: BackBufWidth: 1366, BackBufHeight: 768, D3DFMT: 3, BackBufCount: 2, MultisampleType: 2, MultisampleQuality: 0
GL sampler object usage: ENABLED
GL prefer MapBufferRange: NO
BinkOpen( /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/media/valve.bik )
ConVarRef volume doesn't point to an existing ConVar
BinkOpen( /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/media/l4d2_intro.bik )
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x0000000E) differs from mask derived from shader name (0x0000001F) for shader ps-file shadow_ps20b ps-index 1 ps-combo 0
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x000000E0) differs from mask derived from shader name (0x000000C0) for shader ps-file water_ps20b ps-index 8 ps-combo 0
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x0000000E) differs from mask derived from shader name (0x0000001F) for shader ps-file shadow_ps20b ps-index 0 ps-combo 0
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x000000E0) differs from mask derived from shader name (0x000000C0) for shader ps-file water_ps20b ps-index 1272 ps-combo 0
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x000000E0) differs from mask derived from shader name (0x000000C0) for shader ps-file water_ps20b ps-index 1272 ps-combo 1Installing breakpad exception handler for appid(hl2_linux)/version(1.0)
Looking up breakpad interfaces from steamclient
Calling BreakpadMiniDumpSystemInit
Steam_SetMinidumpSteamID: Caching Steam ID: 76561198079673489 [API loaded yes]
Steam_SetMinidumpSteamID: Setting Steam ID: 76561198079673489
warning: Unknown nb_ctl request: 4
warning: Unknown nb_ctl request: 4
warning: Unknown nb_ctl request: 4
warning: Unknown nb_ctl request: 4
warning: Unknown nb_ctl request: 4
warning: Unknown nb_ctl request: 4
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x000000E0) differs from mask derived from shader name (0x000000C0) for shader ps-file water_ps20b ps-index 20 ps-combo 0
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x000000E0) differs from mask derived from shader name (0x000000C0) for shader ps-file water_ps20b ps-index 464 ps-combo 0
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x000000E0) differs from mask derived from shader name (0x000000C0) for shader ps-file water_ps20b ps-index 464 ps-combo 1
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x000000E0) differs from mask derived from shader name (0x000000C0) for shader ps-file water_ps20b ps-index 392 ps-combo 0
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x000000E0) differs from mask derived from shader name (0x000000C0) for shader ps-file water_ps20b ps-index 392 ps-combo 1
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x000000E0) differs from mask derived from shader name (0x000000C0) for shader ps-file water_ps20b ps-index 504 ps-combo 0
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x000000E0) differs from mask derived from shader name (0x000000C0) for shader ps-file water_ps20b ps-index 504 ps-combo 1
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x000000E0) differs from mask derived from shader name (0x000000C0) for shader ps-file water_ps20b ps-index 80 ps-combo 0
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x000000E0) differs from mask derived from shader name (0x000000C0) for shader ps-file water_ps20b ps-index 120 ps-combo 0
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x000000E0) differs from mask derived from shader name (0x000000C0) for shader ps-file water_ps20b ps-index 72 ps-combo 0
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x000000E0) differs from mask derived from shader name (0x000000C0) for shader ps-file water_ps20b ps-index 888 ps-combo 0
Loaded program cache file "glbaseshaders.cfg", total keyvalues: 738, total successfully linked: 738
Loaded program cache file "glshaders.cfg", total keyvalues: 0, total successfully linked: 0
Precache: Took 2091 ms, Vertex 1072, Pixel 870
Game.so loaded for "Left 4 Dead 2"
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x0000000E) differs from mask derived from shader name (0x0000001F) for shader ps-file shadow_ps20b ps-index 1 ps-combo 0
IDirect3DDevice9::CreatePixelShader: shaderapi's centroid mask (0x0000000E) differs from mask derived from shader name (0x0000001F) for shader ps-file shadow_ps20b ps-index 0 ps-combo 0
Unable to remove /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/textwindow_temp.html!
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_000.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_000.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_011.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_011.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_007.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_007.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/update/pak01_000.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/update/pak01_000.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_008.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_008.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2_dlc3/pak01_000.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2_dlc3/pak01_000.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2_dlc3/pak01_003.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2_dlc3/pak01_003.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2_dlc2/pak01_001.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2_dlc2/pak01_001.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2_dlc1/pak01_000.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2_dlc1/pak01_000.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2_dlc2/pak01_000.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2_dlc2/pak01_000.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_002.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_002.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_003.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_003.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_010.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_010.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_009.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_009.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_001.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_001.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_004.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_004.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_005.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_005.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_006.vpk was never closed
File /home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/left4dead2/pak01_006.vpk was never closed
/home/kurban/.local/share/Steam/SteamApps/common/Left 4 Dead 2/./hl2.sh: line 67: 20163 Segmentation fault ${GAME_DEBUGGER} "${GAMEROOT}"/${GAMEEXE} "$@"
Game removed: AppID 550 "Left 4 Dead 2", ProcID 20163
Installing breakpad exception handler for appid(steam)/version(1411443970)
[1012/181603:ERROR:renderer_main.cc(227)] Running without renderer sandbox
kurban ~ $ pacman -Qs lib32
local/lib32-acl 2.2.52-2
Access control list libraries (32-bit)
local/lib32-alsa-lib 1.0.28-1
An alternative implementation of Linux sound support (32 bit)
local/lib32-alsa-plugins 1.0.28-1
Extra alsa plugins (32-bit)
local/lib32-atk 2.12.0-1
A library providing a set of interfaces for accessibility (32-bit)
local/lib32-attr 2.4.47-1
Extended attribute support library for ACL support (32-bit)
local/lib32-bzip2 1.0.6-2
A high-quality data compression program (32-bit)
local/lib32-cairo 1.12.16-1
Cairo vector graphics library (32-bit)
local/lib32-curl 7.38.0-1
An URL retrieval utility and library (32-bit)
local/lib32-db 5.3.28-1
The Berkeley DB embedded database system
local/lib32-e2fsprogs 1.42.12-1
Ext2 filesystem libraries (32-bit)
local/lib32-elfutils 0.159-1
Collection of libraries for working with ELF object files and DWARF debugging information (32-bit)
local/lib32-expat 2.1.0-2
An XML Parser library written in C (32 bit)
local/lib32-flac 1.3.0-1
Free Lossless Audio Codec (32-bit)
local/lib32-flashplugin 11.2.202.406-1
Adobe Flash Player for 32-bit Mozilla-based browsers
local/lib32-fontconfig-infinality-ultimate 2.11.1-3 (infinality-bundle-multilib)
A library for configuring and customizing font access (32-bit, infinality-bundle)
local/lib32-freetype2-infinality-ultimate 2.5.3-11 (infinality-bundle-multilib)
TrueType font rendering library with Infinality patches and custom settings by bohoomil (32-bit, infinality-bundle).
local/lib32-gcc-libs 4.9.1-2
Runtime libraries shipped by GCC (32-bit)
local/lib32-gdk-pixbuf2 2.30.8-1
An image loading library (32-bit)
local/lib32-gettext 0.19.2-1
GNU internationalization library (32-bit)
local/lib32-glew 1.11.0-1
A cross-platform C/C++ extension loading library (32 bit)
local/lib32-glib2 2.40.0-1
Common C routines used by GTK+ 2.4 and other libs (32-bit)
local/lib32-glibc 2.20-2
GNU C Library (32-bit)
local/lib32-glu 9.0.0-2
Mesa OpenGL utility library (32 bits)
local/lib32-gmp 6.0.0-1
A free library for arbitrary precision arithmetic (32-bit)
local/lib32-gtk2 2.24.24-1
The GTK+ Toolkit (v2) (32-bit)
local/lib32-harfbuzz 0.9.35-1
OpenType text shaping engine. (32-bit)
local/lib32-icu 53.1-1
International Components for Unicode library (32 bit)
local/lib32-jack 0.124.1-1
A low-latency audio server (32-bit)
local/lib32-json-c 0.12-1
A JSON implementation in C (32-bit)
local/lib32-keyutils 1.5.9-1
Linux Key Management Utilities (32-bit)
local/lib32-krb5 1.12.2-1
The Kerberos network authentication system (32-bit)
local/lib32-lcms2 2.6-1
Small-footprint color management engine, version 2 (32-bit)
local/lib32-libasyncns 0.8-7
A C library for Linux/Unix for executing name service queries asynchronously (32-bit)
local/lib32-libcap 2.24-1
POSIX 1003.1e capabilities (32-bit)
local/lib32-libcups 1.7.5-1
The CUPS Printing System - client libraries (32-bit)
local/lib32-libdbus 1.8.8-1
DBus library (32-bit)
local/lib32-libdrm 2.4.58-1
Userspace interface to kernel DRM services (32-bit)
local/lib32-libffi 3.1-1
A portable, high level programming interface to various calling conventions (32-bit)
local/lib32-libgcrypt 1.6.2-1
General purpose cryptographic library based on the code from GnuPG (32-bit)
local/lib32-libglade 2.6.4-6
Allows you to load glade interface files in a program at runtime (32-bit)
local/lib32-libgpg-error 1.16-1
Support library for libgcrypt (32-bit)
local/lib32-libice 1.0.9-1
X11 Inter-Client Exchange library (32-bit)
local/lib32-libjpeg-turbo 1.3.1-1
libjpeg derivative with accelerated baseline JPEG compression and decompression (32-bit)
local/lib32-libldap 2.4.40-1
Lightweight Directory Access Protocol (LDAP) client libraries (32-bit)
local/lib32-libmng 2.0.2-1
A collection of routines used to create and manipulate MNG format graphics files (32-bit)
local/lib32-libogg 1.3.1-1
Ogg bitstream and framing library (32-bit)
local/lib32-libpciaccess 0.13.2-1
X11 PCI access library (32-bit
local/lib32-libpng 1.6.13-1
A collection of routines used to create PNG format graphics files (32-bit)
local/lib32-libpng12 1.2.51-2
A collection of routines used to create PNG format graphics files (32-bit, 1.2 branch)
local/lib32-libpulse 5.0-1
A featureful, general-purpose sound server (32-bit client libraries)
local/lib32-libsamplerate 0.1.8-2
Secret Rabbit Code - aka Sample Rate Converter for audio (32-bit)
local/lib32-libsm 1.2.2-1
X11 Session Management library (32-bit)
local/lib32-libsndfile 1.0.25-3
A C library for reading and writing files containing sampled sound (32-bit)
local/lib32-libssh2 1.4.3-2
A library implementing the SSH2 protocol as defined by Internet Drafts (32-bit)
local/lib32-libtasn1 4.1-1
The ASN.1 library used in GNUTLS (32 bit)
local/lib32-libtiff 4.0.3-2
Library for manipulation of TIFF images (32-bit)
local/lib32-libtxc_dxtn 1.0.1-5
S3 Texture Compression (S3TC) library for Mesa (32-bit)
local/lib32-libvdpau 0.8-1
Nvidia VDPAU library
local/lib32-libvorbis 1.3.4-1
Vorbis codec library (32-bit)
local/lib32-libx11 1.6.2-1
X11 client-side library (32-bit)
local/lib32-libxau 1.0.8-1
X11 authorisation library (32-bit)
local/lib32-libxcb 1.11-1
X11 client-side library (32-bit)
local/lib32-libxcomposite 0.4.4-2
X11 Composite extension library (32-bit)
local/lib32-libxcursor 1.1.14-1
X cursor management library (32-bit)
local/lib32-libxdamage 1.1.4-2
X11 damaged region extension library (32-bit)
local/lib32-libxdmcp 1.1.1-2
X11 Display Manager Control Protocol library (32-bit)
local/lib32-libxext 1.3.3-1
X11 miscellaneous extensions library (32-bit)
local/lib32-libxfixes 5.0.1-1
X11 miscellaneous 'fixes' extension library (32-bit)
local/lib32-libxft 2.3.2-1
FreeType-based font drawing library for X (32-bit)
local/lib32-libxi 1.7.4-1
X11 Input extension library (32-bit)
local/lib32-libxinerama 1.1.3-1
X11 Xinerama extension library (32-bit)
local/lib32-libxml2 2.9.1-1
XML parsing library, version 2 (32-bit)
local/lib32-libxmu 1.1.2-1
X11 miscellaneous micro-utility library (32-bit)
local/lib32-libxrandr 1.4.2-1
X11 RandR extension library (32-bit)
local/lib32-libxrender 0.9.8-1
X Rendering Extension client library (32-bit)
local/lib32-libxshmfence 1.1-1
a library that exposes a event API on top of Linux futexes (32-bit)
local/lib32-libxss 1.2.2-2
X11 Screen Saver extension library (32-bit)
local/lib32-libxt 1.1.4-1
X11 toolkit intrinsics library (32-bit)
local/lib32-libxtst 1.2.2-1
X11 Testing -- Resource extension library (32-bit)
local/lib32-libxv 1.0.10-1
X11 Video extension library (32-bit)
local/lib32-libxxf86vm 1.1.3-1
X11 XFree86 video mode extension library (32-bit)
local/lib32-llvm-amdgpu-lib-snapshot 20130403-2
Low Level Virtual Machine with AMDGPU enabled to build r600g shader llvm support (32-bits)
local/lib32-llvm-libs 3.5.0-1
Low Level Virtual Machine (runtime library)(32-bit)
local/lib32-mesa 10.3.0-3
an open-source implementation of the OpenGL specification (32-bit)
local/lib32-mesa-demos 8.2.0-2
Mesa demos and tools (32-bit)
local/lib32-mesa-dri 10.3.0-3
Mesa DRI drivers (32-bit)
local/lib32-mesa-libgl 10.3.0-3
Mesa 3-D graphics library (32-bit)
local/lib32-mesa-vdpau 10.3.0-3
Mesa VDPAU drivers (32-bit)
local/lib32-ncurses 5.9-3
System V Release 4.0 curses emulation library (32-bit)
local/lib32-nspr 4.10.7-1
Netscape Portable Runtime (32-bit)
local/lib32-nss 3.17-1
Mozilla Network Security Services (32-bit)
local/lib32-nvidia-utils 343.22-1
NVIDIA drivers utilities (32-bit)
local/lib32-openssl 1.0.1.i-1
The Open Source toolkit for Secure Sockets Layer and Transport Layer Security (32-bit)
local/lib32-p11-kit 0.20.7-3
Library to work with PKCS#11 modules (32-bit)
local/lib32-pango 1.36.6-1
A library for layout and rendering of text (32-bit)
local/lib32-pcre 8.35-1
A library that implements Perl 5-style regular expressions (32-bit)
local/lib32-pixman 0.32.6-1
Pixman library (32-bit)
local/lib32-portaudio 19_20140130-1
A free, cross-platform, open source, audio I/O library. (32 bit)
local/lib32-primus 20131226-1
Faster OpenGL offloading for Bumblebee (32-bit)
local/lib32-qt4 4.8.6-1
A cross-platform application and UI framework (32-bit)
local/lib32-readline 6.3.006-1
GNU readline library (32-bit)
local/lib32-sqlite 3.8.6-1
A C library that implements an SQL database engine (32-bit)
local/lib32-systemd 216-2
system and service manager (32-bit)
local/lib32-util-linux 2.25.1-2
Miscellaneous system utilities for Linux (32-bit)
local/lib32-v4l-utils 1.2.1-1
Userspace tools and conversion library for Video 4 Linux (32-bit)
local/lib32-wayland 1.6.0-1
A computer display server protocol
local/lib32-xz 5.0.5-1
Library and command line tools for XZ and LZMA compressed files (32-bit)
local/lib32-zlib 1.2.8-1
Compression library implementing the deflate compression method found in gzip and PKZIP (32-bit)
kurban ~ $ pacman -Qs nvidia
local/bumblebee 3.2.1-5
NVIDIA Optimus support for Linux through VirtualGL
local/cpyrit-cuda 0.4.0-2
Pyrit support for Nvidia-CUDA.
local/cuda 6.5.14-1
NVIDIA's GPU programming toolkit
local/lib32-libvdpau 0.8-1
Nvidia VDPAU library
local/lib32-nvidia-utils 343.22-1
NVIDIA drivers utilities (32-bit)
local/libcl 1.1-4
OpenCL library and ICD loader from NVIDIA
local/libvdpau 0.8-1
Nvidia VDPAU library
local/nvidia 343.22-2
NVIDIA drivers for linux
local/nvidia-utils 343.22-1
NVIDIA drivers utilities
local/opencl-nvidia 343.22-1
OpenCL implemention for NVIDIA
kurban ~ $ pacman -Qs bumblebee
local/bumblebee 3.2.1-5
NVIDIA Optimus support for Linux through VirtualGL
local/lib32-primus 20131226-1
Faster OpenGL offloading for Bumblebee (32-bit)
local/primus 20131226-1
Faster OpenGL offloading for Bumblebee
kurban ~ $ pacman -Qs mesa
local/glu 9.0.0-3
Mesa OpenGL Utility library
local/lib32-glu 9.0.0-2
Mesa OpenGL utility library (32 bits)
local/lib32-libtxc_dxtn 1.0.1-5
S3 Texture Compression (S3TC) library for Mesa (32-bit)
local/lib32-mesa 10.3.0-3
an open-source implementation of the OpenGL specification (32-bit)
local/lib32-mesa-demos 8.2.0-2
Mesa demos and tools (32-bit)
local/lib32-mesa-dri 10.3.0-3
Mesa DRI drivers (32-bit)
local/lib32-mesa-libgl 10.3.0-3
Mesa 3-D graphics library (32-bit)
local/lib32-mesa-vdpau 10.3.0-3
Mesa VDPAU drivers (32-bit)
local/libtxc_dxtn 1.0.1-5
S3 Texture Compression (S3TC) library for Mesa
local/mesa 10.3.0-3
an open-source implementation of the OpenGL specification
local/mesa-demos 8.2.0-3
Mesa demos and tools
local/mesa-dri 10.3.0-3
Mesa DRI drivers
local/mesa-libgl 10.3.0-3
Mesa 3-D graphics library
At topic, that I pointed to, author wrote that he deleted lib32-libtxc_dxtn, but I can't because lib32-mesa-dri requires lib32-libtxc_dxtn
Last edited by remutik4 (2014-10-12 14:28:26) -
Bad Game Performance on MacBook Pro Retina
I've been getting below average performance on my the 15" Retina (2012) with all sorts of games lately. I did the SMC Reset and nothing works. I tested it out on Bootcamp with Windows 8 and Windows 7 and the gaming performance seems to be lower than what it usually was.
I have a feeling it may be related to the Throttling done on my GPU, I tested it out on windows and it seems that my GPU Clock is usually running at around 500 to 725 it never reaches the 900MHz and the tempratures is always around 95 degrees.
Any ideas ?If you are serious about games, get a PC. Macs are not good gaming platforms.
Ciao. -
Z87 GD65 bios flash result in freeze.
Hey guys,
First time MSI customer here.
I bought the GD65-Gaming, it came with bios v1.1, downloaded v1.9, formatted a USB stick to FAT32, copied the file E7845IMS.190 to the root of the USB stick, went to bios, m-flash chose the 2nd option (bios + ME), chose the file and it just froze. I waited 3-4 minutes and nothing was showing on the screen and i was not able to move the mouse cursor. I tried two different USB keys, one NTFS and one FAT32. none of which worked.
Am Running 4770k , gtx 670, 16gb kingston beast @ 1333mhz and Windows 7 ultimate 64bit edition.
Please help me resolve this, I'm pleading you.
Thanks in advance,
MikeQuote
I don't have a floppy disk..
i didn't told to use a floppy disk [BIOS is too big for floopy too, won't fit and its not relative storage and its something retired not used from long time]
use an USB key instead -
Bad game performance: "Tibia" - need help to find the error
hi
im playing a game called tibia (www.tibia.com) for a long time, back on windows i had no problems with the programm(except that windows itself crashed sometimes while playing ;P).
since some time they made an linux client again and i tryed it on my pc, running arch with all updates.
my problem is that sometimes when (probably to much) pictures like garbage and player are shown on the screen(its an 2d mud inspired by ultima) i get performence issues, the program is freezing 2 seconds before i can view another level, just to say an example.
via "top" i watched what kicks in that uses my cpu so much and it is X.
ok, now i dont realy know where this post belongs, more here or into newbie's corner, but:
as i said before i have every possible update for arch and the installed programms.
i got an geforce fx 5200 with the newest driver(manualy installed because the installer via pacman whont have the new driver because of an outdatet kernel, atleast that was what i remember).
my problem now is that i just dont know where the error is.
i know of people, using the same client as i that dont have that issues.
i already bugged the support forums but as far as i saw they dont realy like arch user, atleast they dont answer to their questions. ;P
i whant to know if MAYBE someone is here who plays tibia and can tell me that he got the same problems like i do or not.
or you could give me hints what i could try to solve this problem.
to write it in one short line:
the problem is that the process "X" sometimes kicks in, using 100% of the cpu, this happens only while playing "tibia"
thank youLook at Steps #4, #6, #9 and #12.
http://helpx.adobe.com/dreamweaver/kb/troubleshoot-javascript-errors-dreamweaver-cs4.html
Nancy O. -
1.9 bad bios Flash - yes again
I updated my bios through Live Update to 1.9 and ended up with a corrupt bios. I followed the instructions here for recovering from this but have had no success. When I put the floppy in and turn on the power the screen flashes with "Award Block Bios Ver 1.0 - Bios Rom Checksum Error - Detecting Floppy Drive A Media - Drive Media 1.44MB and then it just shuts down. I pretty sure I followed the instructions to the letter so I am really stumped. The one thing that may have a bearing is that my file system is NTFS but i don't know. What I did
I formatted a floppy ticking "Create an ms-dos startup disk", this was my boot disk.
I then copied the award bios program and bios file to this floppy.
Then I created an autoexec.bat file as per the instructions, it was simply "awfl859G w7030NMS.190". I then used this disk to recover the system/bios with no luck. I am beginning to think I am sunk and would appericate any assistance on what else I might do or indeed if I am missing something. My mobo is a K8N Neo Plat and had Bios 1.7 installed previous to this.Here is what Syar said today in an other thread:
"To try to boot properly and do a reflash :
Turn off , remove AC .
Disconnect drives from the controller(s) , any usb devices , use a ps2 keyboard and only one memory module in slot1 .
reset cmos with a minimal hw setup (do a long one with battery removed , give it 15 minutes )
Revert the cmos jumper to "keep" mount the battery and restore AC .
Try booting to a startup msdos floppy .
Problem with liveupdate is that it doesnt update/flash bootblock .
With some bios - bios versions this gives bad results as perhaps some dependency is broken .
If it wont work you need the bios chip reprogrammed some other way (eprom programmer/hotflash/badflash.com service etc)"
The only thing I would add is maybe it could work if you created a windows 98 floppy boot disk with cd rom support plus a cd with the flash programs (flash utility and old bios that worked before) on it. Boot with the floppy and once the cd is recognized copy the flash programs to virtual ramdrive c: and then run the flash program with the correct switches from ramdrive c:
Don't know if that will work as Syar says (with or without floppy-cd combination) but please post back and let us know how it goes. Good luck.
EDIT- In case you are too young to know dos - The dos commands to get programs from cdrom drive d to virtual drive c and then to flash from drive c would be as follows:
D: [enter]
copy *.* c: [enter]
c: [enter]
then type [the flash program] [the bios file name] /py /sn /wb /cc /cd /cp /f /e [enter] -
User guide: MSI HQ USB BIOS Flash Tool
Guide based on USB tool v1.17c
HOW TO properly use the MSI Forum HQ USB Flashing Tool to update your BIOS
This user guide provides a step-by-step explanation for properly using the >>MSI Forum HQ USB Flashing Tool<< to prepare a USB Flash Drive for a safe BIOS-Flash in a pure DOS Environment. The tool itself will not perform the actual flashing operation. It will "only" help you to get your USB Stick set up for an automated DOS flashing procedure which requires final confirmation. (If you should run into any problems before you are prompted for final confirmation in DOS, no attempt to flash has been made yet and there is no danger of a bad flash.)
NOTE: If you are having problems getting your USB device to boot correctly, you may need to format it correctly as the geometry data may be incorrect. You can do that by pickup option "Fix My USB key" from the Tool or by using >>> THIS <<< tool here! For future usage you can skip this step, it need to be done only once if your stick need adjustment.
Symptoms that your USB key need a fix after booting from the USB key:
* Error: "No bootable partition in table"
* Blinking cursor in a top left corner and nothing happens
* "RIVER2 MSI"
* "Error loading operating system"
* "Missing operating system"
* "Disk in drive is not a bootable"
* Booting from selected USB key is IGNORED, the other/typical OS continue to load as usual
If still no change after using "Fix My USB key" Tool's option or HP Formatter Tool as alternative.
Then try with different USB key, the issue is there.
Note: Those USB keys who support "U3 Smart", this "feature" must be removed before proceed.
Refer to followed link: http://u3.sandisk.com/launchpadremoval.htm
Read the three notes that follow first before you move on:
1. Note: Before you even think about flashing a different BIOS, be sure that your system is stable. If it is not stable, make it stable first. (Read >>here<<.)
2. Note: Make sure your system meets the preconditions and system requirements mentioned below before you attempt to use the tool.
3. Note: Do know that flashing your BIOS, be it with the help of the tool or otherwise, is done at your own risk.
Contents of the Guide:
0. Preconditions & System Requirements
1. Basic Description of Functionality
2. Installing/Starting the tool.
3. Choosing a Preparation Method
3.1. Method 1: Processing a BIOS Archive Directly (ZIP/RAR)
3.2. Method 2: Processing a BIOS File Directly
3.3. Method 3: SureHands Live Update
3.4. Method 4: Geometry Change
4. Selecting the USB Flash Drive for preparation
5. BIOS Settings, Booting & Flashing
5.1. BIOS Settings to Check
5.2. Booting from USB Flash Drive
5.3. Flashing Procedure/Running MemTest86+ & CMOS-Clear
6. FAQ: Common Problems & Solutions
7. Version History
0. Preconditions & System Requirements
The main precondition for using the tool is a working & healthy Windows installation on the system that needs the BIOS flash. The Tool is designed to work with MSI Retail Boards & Laptops only.
Please note mainboards of other brands and OEM boards that are manufactured by MSI but sold by Medion, HP, NEC and others are not supported. If you have an OEM board that needs a BIOS update read this topic: >>OEM boards manufactured by MSI<<
Supported Operating Systems: All current Windows Versions (32bit & 64bit, any service pack (SP)): Windows NT, Windows 2000, Windows 2003, Windows XP, Windows Vista, and Windows 7.
The second requirement is that you have a fully functional USB Flash Drive that uses the FAT file system (FAT/FAT32). NTFS is not supported. If your USB Flash Drive is using the NTFS File System, reformat it to FAT or FAT32.
As the tool also provides a Live Update Option ("SureHands"), you'll need a working internet connection if you want to choose this method. Not all boards are supported at this point.*
* Check section 3.3 of this guide to see if your board is currently supported by the SureHands feature.
1. Basic Description of Functionality
The MSI Forum HQ USB Flashing Tool will help you to easily prepare an USB flash drive for an automated BIOS flash in a pure DOS environment, which is the safest way to perform such a procedure. The tool will also allow you to run MemTest86+ in a pure DOS environment. However, the preparation of your USB Stick is done in Windows and basically includes two steps:
(1) The device will be made bootable.
(2) All necessary files (incl. BIOS file, actual flasher and MemTest86+ executable) and all DOS commands that are needed to flash/test memory will automatically be implemented.
Because the tool does not reformat your USB Flash Drive*, no files that may currently be on the stick will be lost during the procedure. Just make sure that there is still some free drive space, otherwise there will not be enough room for the files that are needed for BIOS Flashing.
* Excluding the Geometry Change method which will destroy all data on the USB storage device.
2. Installing/Starting the tool
Treat the forum's USB Flashing Tool like a regular application. Download it to and run it from your hard drive, there is no need to copy & start it from the USB Flash Drive that you want to use for flashing. Both, the installer version and the stand-alone version, do precisely the same job. Which of the two versions you use, is solely up to you and your preferences. The stand-alone version can be started directly by clicking on the executable file. The installer version will perform an installation and provide you with an entry in your start menu and a desktop shortcut to start the tool.
When you start the tool a DOS box should open up to provide you with status messages and prompts. Do not close that box unless you want to abort the preparation procedure!
Please ensure that you connect the USB flash drive you wish to use before starting the Tool!
NOTE: If you do not connect your USB storage device before starting the tool, or the tool doesn't detect it. You can still insert the drive letter, as the tool will continue as normal.
The tool will first check, if an MSI mainboard is installed in your system and show you its model name and PCB Version in a message box. Click >OK< to continue to choose the tool's preparation method that you want to use to prepare your USB Flash Drive.
3. Choosing a Preparation Method
If your MSI Retail Board is properly detected and you have pressed the >OK< button in the message box, an option box will pop up that allows you to choose between three different operating modes. The options you can choose from are more or less self-explanatory, however, read the detailed description if you are unsure how to proceed at this point:
3.1. Method 1: Processing a BIOS Archive Directly (ZIP/RAR)
Official MSI BIOS-Updates that can be downloaded from the product site of your board model do usually come as .ZIP or .RAR archives that contain the actual BIOS File and the corresponding AWARD or AMI flashing utility (depending on the BIOS Type of your board). If you have downloaded such an archive, you should choose the first method from the option box.
You do not need to extract the files from the BIOS archive. The tool will ask you to point it to the archive you downloaded and automatically extract the BIOS File and the AMI or AWARD flashing utility and put it them on your USB Flash Drive. You don't have to worry about anything else. All you have to do is to remember where you saved the ZIP or RAR file you downloaded:
3.2. Method 2: Processing a BIOS File Directly
If you do not have a ZIP or RAR archive that already contains a BIOS File and the proper flashing utitility, but only the plain unpacked BIOS File, choose the second Method from the option box. In most cases BETA BIOS Files supplied by MSI Support or shared here in the Forum do not come with the proper flashing utility. If the MSI Forum HQ USB Flashing Tool is told to process a plain BIOS File, it will automatically check the type of BIOS File (AMI or AWARD) and then select the proper flashing utility that needs to be used. All you need to do is point the tool to the BIOS-File that is supposed to be flashed:
3.3. Method 3: SureHands Live Update
"SureHands Live Update" is the third operation method you can choose from the option box. It provides a much safer and more reliable alternative to MSI Live Update as the actual BIOS Flash is performed in a pure DOS environment as well. If you decide to use this option, you do not to supply the tool with a BIOS-Archive or a BIOS-File.
Not all MSI Retail Boards are currently supported. With every update of the USB Flashing Tool more boards will be added. At present, you can use the "SureHands" Live Update method with the following boards only (the list will be updated regularly):
AMD based boards:
K8N Neo4-F (MS-7125, PCB 3.0)
K8NGM2-FID (MS-7207, PCB 2.0)
K8N Diamond Plus (MS-7220, PCB 1.0)
K8N Neo3 (MS-7135, PCB 1.0 & 2.0)
K9A Platinum (MS-7280, PCB 1.0)
K9A2 Platinum (MS-7376, PCB 1.0)
K9A2 CF-F (MS-7388, PCB 1.0)
K9N Neo-F (MS-7260, PCB 1.0 & 2.0)
K9VGM-V (MS-7253, PCB1.0)
K9N2GM-F V2 (MS-7509, PCB 1.0)
K9N Neo V2 / V3 (MS-7369, PCB 1.1)
K9N Platinum & K9N SLI Platinum (MS-7250, PCB1.0)
K9N2 Diamond (MS-7375, PCB 1.1)
K9N2 SLI Platinum (MS-7374, PCB 1.1)
K9N2 Zilent (MS-7374, PCB 1.1)
K9N2 Neo-F (MS-7511, PCB 1.1)
DKA790GX Platinum (MS-7550, PCB 1.1)
790FX-GD70 (MS-7577, PCB 1.0)
790GX-G65 (MS-7576, PCB 1.0)
Intel based boards
HydroGenX48C & X48C Platinum (MS-7353, PCB 3.0)
X48 Platinum (MS-7353, PCB 1.0)
X38 Diamond Plus
X38 Diamond (MS-7353, PCB 1.0)
X38 Platinum (MS-7353, PCB 1.0)
EFINITY-FP (MS-7395(E), PCB 1.0)
P35 Neo Combo-F (MS-7365, PCB 1.0)
P35 Neo2 Series (MS-7345, PCB 1.1)
P35 Platinum (MS-7345, PCB 1.1)
P35 Neo-F (MS-7360, PCB 1.0)
G33 Platinum (MS-7345, PCB 1.1 & PCB 1.2)
P965 Platinum (MS-7238, PCB 1.1)
975X Platinum PowerUp Edition (MS-7246, PCB 2.1)
865PE Neo2-P Platinum Edition (MS-6728, PCB 2.0C)
P7N SLI Platinum (MS-7380, PCB 1.0)
P7N2 Diamond (MS-7523 PCB 1.0)
P7N Diamond (MS-7510, PCB 1.0)
P7N SLI Platinum (MS-7380, PCB 1.0)
P6N Diamond (MS-7320, PCB 1.0)
P6N SLI Platinum (MS-7350, PCB 1.0)
P6N SLI-FI (MS-7350 PCB 2.0)
P6N SLI V2 (MS-7346 PCB 1.0)
ECLIPSE SLI (MS-7520, PCB 1.0)
ECLIPSE Plus (MS-7566, PCB 1.0)
P35 Neo3-F (MS-7395, PCB 1.0)
After selecting "SureHands" from the option box, the tool will automatically check for all available official BIOS-Versions for your mainboard. It will also look for the latest available BETA BIOS Version for you board and save that information in a TXT-File on your Desktop:
Note: The SureHands option will not provide you with the latest BETA BIOS, it will only provide the information.
When the tool is done scanning for official BIOS releases for your board, it will give you the possibility to manually choose the BIOS Version you want to flash. SureHands Live Update will not automatically select the latest version and use it for flashing, it will give you the chance of choosing between all available official BIOS releases that are available:
Note that the "May not exist" comment that appears behind some versions does not mean that the BIOS does not exist. If you know the latest BIOS for your board is e.g. v1.8, SureHands will retrieve it even though there may be such a comment. That message is part of a prediction feature that tries to determine future BIOS Releases. If a BIOS version that was predicted by the SureHands feature is not available yet, the tool will tell you if it cannot retrieve the files and ask you to select an earlier version.
3.4 Geometry Change
If the tool fails to make your USB storage device bootable then you will need to use this mode. It will make your drive bootable, select it:
Select your drive then let the tool do it's business.
Once the process is complete, run the tool again via method 1, 2 or 3, restart your computer and try booting from the USB storage device again.
NOTE: This method will destroy ALL data on the USB storage device!
NOTE: This method is available in v1.17 and beyond.
4. Selecting the USB Flash Drive for preparation
When you have chosen one of the three methods from the option list and pointed the tool at the corresponding archive, BIOS File or selected the desired BIOS Version from the list in case you chose to use SureHands Live Update, the MSI Forum HQ USB Flashing Tool will prompt you to enter the drive letter of the USB Flash Drive you want to use for flashing:
Note that certain drive letters are reserved and will therefore not be accepted by the tool (currently A:, B: and C:). If you are sure you have connected an USB Flash Drive to the system that works properly but it does not appear in the table that appears in the DOS box, enter the corresponding drive letter anyway and see if the tool accepts it. This can happen in rare cases, but it is usually no problem.
The tool will check the selected drive and will provide you with status messages. If everything is okay, the message should look like this:
The tool will attempt to make the device bootable and automatically write all files that are needed for flashing to the drive to prepare it for flashing. If the procedure was successful, you will get the following message in the DOS box:
5. BIOS-Settings, Booting & Flashing
If the Tool has prepared your drive for booting & flashing, no BIOS flash attempt has been made yet. Only the preparation process. In order to initiate the flashing procedure, you have to restart your system and make it boot from the USB Flash drive. Before you move on to do that, enter the BIOS Setup and check a few options:
5.1. BIOS Settings to Check
Check USB-related Options in BIOS:
- USB Controller
- USB 2.0 Controller
- USB Legacy Support
- USB Storage Support
- Boot from other devices
- etc.
Not all of these options may be found in BIOS and the precise name may vary as well. Just make sure you checked for such options and that they are enabled (if present).
Another option you should check for is "Boot Sector Protection". If such an option is present in your BIOS, make sure it is disabled because it may make a BIOS Flash impossible.
@all Overclockers: In case your system is currently overclocked, make sure you roll back to default clock and voltage settings before you attempt to start the flashing procedure. Otherwise you increase the risk of an unsuccesful flash, and you most probably don't want something like that to happen.
5.2. Booting from USB Flash Drive
To boot from your USB drive you can either change the boot sequence in BIOS accordingly or just press F11 during POST* to get access to the BIOS Boot Menu. From here, you can select you drive directly without having to adjust the boot sequence in BIOS. Note that your USB Flash Drive may be listed as a hard drive (if you choose that entry you will get another list to choose from).
* Not all mainboards use F11, for the boot menu. If F11 fails for you, please consult your manual for the correct key.
Note: If you have problems booting from your drive, look at the FAQ-Section of this guide and see if any of the tips resolve the issue.
5.3. Flashing Procedure/Running MemTest86+
As soon as the system boots from the drive, DOS will be loaded and you will be displayed with two options. One option will start MemTest86+, the other will begin the flashing procedure. If no choice is made, MemTest86+ will automatically start.
The flashing procedure will automatically be initiated from there. You will see status messages on the screen that will supply you with information and also prompt you for final confirmation for the actual BIOS-Flash. A backup of you current BIOS will automatically be saved to a file on the drive (backup.bin) before the flashing actually starts. You do not need to enter any commands in DOS. All you have to do is acknowledge the information on the screen by pressing a key.
The flash itself will only take a couple of seconds (20-30s at the most). If the flashing is successfully completed, shutdown the system and clear CMOS with main A/C power cable removed from PSU. Read the >>Clear CMOS Guide<< for further information.
After clearing CMOS you have completed the BIOS-Flash.
Guide created by Jack The Newbie and the forum teamVersion updated to 1.18x:
* Mode 3 Sure Hands, Live Update:
- Removed beta BIOS query check[global]
- Fixed issue K9N2 Diamond unable to be detected as supported unit if onboard is installed BIOS version 2.4,
add dynamic detection for future versions.
- Fixed issue 790FX-GD70 unable to be detected as supported unit and add dynamic detection for future versions.
- Fixed issue 790GX-G65 unable to be detected as supported unit and add dynamic detection for future versions.
- Add support for 785G-E65, add dynamic detection for future versions, prediction BIOS range 3.1 - 3.A
- Add support for 785G-E53, add dynamic detection for future versions, prediction BIOS range 3.1 - 3.A
- Add support for 790GX-G65 Winki ED, prediction BIOS range 2.1 - 2.A
- Fixed issue P7N Diamond unable to be detected as supported unit if onboard BIOS installed is 1.3 and above,
add dynamic detection for future versions.
- Add support for K9A2 Neo2, prediction BIOS range 7.4 - 7.D
- Add support for 790XT-G45, prediction BIOS range 2.2 - 2.B
- Add support for 770T-C45, prediction BIOS range 8.4 - 8.D
- Add support for 770T-C35, prediction BIOS range 8.4 - 8.D
- Fixed issue K9A2 Platinum[V1,V2] unable to be detected as supported unit if onboard BIOS installed is 1.9,
add dynamic detection for future versions, prediction BIOS range extended to 1.F0
- 790GX-G65 board prediction BIOS range extended to ver: 1.D0
- 790GX-G65 board update bios base ver from 1.xx to 4.xx [following new msi rule for this board jumping from 1.xx to 4.xx]
- Add support for 770-C35|C45 boards [p1] BIOS range 1.40 - 1.D0
- Add support for 770-G45 board [p2] BIOS range A10 - AA0
* Add "Exit" option to navigation screen
* Update version info related to boot part
* Update boot part to handle newest features
* Modify Self update sequence of Installer version
* Update internal version check ID
* Mode 4 minor update
* Build and add new Tool's module for newest features
* W32 Tool's exit time part decreased by 10 seconds
* On received OS reboot user request, time delay before execution decreased by 15 seconds
* Update EC decoder
* Update start-up information screen
* Auto store start-up detected information to user's desktop ==> [MSIHQ_INFO.TXT]
Details:
Easy to show machine information on request, instead write down from the screen manually, now just copy/paste can be used from MSIHQ_INFO.TXT
User can check and compare information before and after the BIOS update
Also usefull if didn't remember what was his original BIOS or EC versions before the update, Tool will auto store it there.
And easy can be checked if needs. E.g Tool's log file of each Tool's execution, each report will include date and time as well.
F.A.Q example:
Q: I flashed BIOS on my notebook and now it doesn't work properly.. And i don't remember what was my old BIOS version.. What can i do?
A: Take a look in MSIHQ_INFO.TXT at your desktop, there is auto recorded your detailed information about your notebook before the BIOS update.
So you can easy find what was your original BIOS & EC versions.
Is it OEM one or not, and the exact original BIOS & EC versions.
So you can roll back easy or if crossflashing were done to reflash to correct versions.
Example question:[this board now use 4.xx bios, but don't have time to make a new images.]
It's just example, do not mean that this BIOS used in the example is bad. But generally often can need to roll back to older version.
Or to use Sure Hands because[The BIOS is N/A for manual download, By SureHands no need to browse/search/download and point to the BIOS version, also eliminate any chances to pickup the wrong BIOS, and not at last its more quickly[save a time]]
Q: I flashed my BIOS via MSI Live Update, but the new BIOS has an issues.
How i can roll back to my old BIOS version?
The MSI LiveUpdate can only update to the latest BIOS version, which is not good for me.
And i can't download my old BIOS version manually... Because "This BIOS can only update via Live Update function"
http://eu.msi.com/index.php?func=downloaddetail&type=bios&maincat_no=1&prod_no=1739
How i can re-flash to my original BIOS version and from where can i get it?
A: Run >>Use the MSI HQ Forum USB flasher<<,
then choose Mode 3 [Live Update{aka SureHands}]:
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at 21:09:45,15
Mainboard: 790GX-G65 (MS-7576)
PCB Version: 1.0
BIOS Version: V1.3
BIOS Date: 05/08/2009
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at 21:22:38,42
Mainboard: 790GX-G65 (MS-7576)
PCB Version: 1.0
BIOS Version: V1.6
BIOS Date: 11/30/2009
Then choose your old BIOS version from the list:
The followed image used below is a sample from Eclipse board,[no time to make accurate image] but will look similar for others boards too:
In a list will be noticed that there is a future BIOS versions.
Some of them will be not released yet. If you pick some of those the Tool will note you:
It's a part of Tool's BIOS prediction system called "Crystal Ball", when MSI release a future BIOSes for your board,
Tool can find them immediately. By that way the Tool no need to be updated to be actual in each moment
* Add new feature "True BIOS Version Ready"
- Updated Mode 1
- Updated Mode 2
- Updated Mode 3
Details:
Q: What "True BIOS Version Ready" means? Does the Tool show the wrong BIOS version until now?
A: Of course not, the Tool always show accurate info.
The same as CPU-Z/Everest of whatever other Tool.
However Tool also detect EC-FW versions for notebooks:
The "True BIOS Version Ready" Tool's feature is aimed to eliminate user's mass confusion about MSI BIOS versions.
And not only users are confused, but MSI's Live Update is confused too... which confuse users even more..
Few typical real examples of confusion:
"K9A2 CF wont flash to Bios v. 1.A !!!"
Quote from: Fingon on 25-October-09, 16:53:15
Hi MSI,
I have a problem. I have bought a new processor: AMD Phenom II x545. I looked on the support page of my MB (MSI K9A2 CF) and there the CPU is supported from the bios version 1.A. So I wanted to flash the Bios the the newest version (1.A). I used the MSI live update 4 program to flash it via windows mode. But everytime it boots it writes "CMOS checksum BAD", then I hit F1 to Bios and I see the version of my BIOS fell to the oldest version 1.1. Then I tried to flash it thru Flash disc (with boot files) and dos mod. The result is the same. I can flash my MB to version 1.8 but when I try the 1.A it wont flash it and my Bios fell to the oldest version (1.1). I realised that the exe files in version 1.1-1.8 are the same (afud412.exe) but the exe file in 1.A is different (afud4310.exe).
My questions are:
1) How to flash my MB to the version 1.A ?
2) Is version 1.A really needed for AMD Phenom II x545? I guess yes, because CPU was avaible in July 2009 and the bios 1.A went out in June 2009. I am able to flash it only to version 1.8 (december 2008).
Thank you for any help!!
EDIT: After reading this topic: https://forum-en.msi.com/index.php?topic=129204.0 I realised I have the VERSION 1 of this board (I purchased it right after the launch of the MB (November 2007). It means it doesnt support CPU over 95W, but my Phenpom II x545 has only 80W. I still cant update Bios to the 1.A version.
So my third question is:
3) Is the Bios update 1.A only for version 2 of this MB?
Thx for replies!
Quote from: Jack t.N. on 25-October-09, 17:16:16
A CMOS Checksum error is normal and expected after a BIOS Flash and/or a CMOS Clear. The fact that this message appears, shows, that there was actually something programmed to the chip.
If you haven't done that yet, please clear CMOS with the main A/C power cable removed from your PSU and load "Optimized Defaults" in BIOS Setup.
The BIOS Version should be shown on the POST Status Screen and there should be a date behind it. Please check the BIOS Date and write it down:
Are you absolutely and entirely sure that what you see is "1.1" and not "1.10"? Because v1.A0 is actually just the hexadecimal notation for v1."10" (one dot ten). The hexadecimal notation is only used in the BIOS File Ending. Once flashed, the BIOS will not identify itself in hexadecimal notation but in decimal code (which means you will never see "v1.A0" after the flash but "v1.10" instead.
Here is a piece of well-meant advice for now and the future: MSI Live Update should be avoided under all circumstances when it comes to BIOS Updates and/or information retrieval regarding your current BIOS Version. Why? Because this tool is stupid and one of there most risky applications for performing a BIOS Flash. Please uninstall it completely.
Why do I call it stupid? I call it stupid because it does not differentiate between hexadecimal notation and decimal notation. It will show you that "v1.A0" is available. The it will flash it, if you allow it to do so. Of course, a v1.A0 Version will always come out as "v1.10" (one dot ten). When you re-run MSI Live Update it will not recognize that v1.A0=v1.10 and tell you again that there is a newer version available (1.A0, which, again, is the same as v1.10, which was just properly flashed).
I believe that the update went just fine, that you are currently using v1.A0=v1.10 and that MSI Live Update is actually just creating a pseudo-problem which is currently confusing you. The pseudo-problem will immediately be out of the world, if you uninstall MSI Live Update and rely on the BIOS ID String as it appears on the POST Status Screen (this includes the date shown there).
If a BIOS Update should ever be necessary again, please make sure that you won't use MSI Live Update but >>Use the MSI HQ Forum USB flasher<< instead.
Quote from: Fingon on 25-October-09, 18:03:44
Thank you for the quick reply!!
Thats exactly what I have JUST found in this post by Svet: https://forum-en.msi.com/index.php?topic=127672.msg974800#msg974800
Yes it is 1.10 of course!! I didnt know that 1.10 = 1.A0 ! Thank you for the reply. Then the MSI live update 4 program is dump that he wanted from me another update of Bios.
So thank you! Problem is solved.
Edit: Yes, because of MSI live update I learned how to flash bios via flash disc. :-) But I was still confused by that 1.10 and of course by program saying me I should update again.. :-P
Quote from: Lostsoul777 on 14-August-09, 05:46:25
I had the same problem with 1.90 bios, so i updated to 1A, i just want to know why Bios Version says: v.1.10 instead v.1A?
Quote from: LinuxGuy on 29-December-09, 01:17:45
My computer does not have a floppy drive. How do I update the BIOS? (I tried the online utility 3 times. It always updates the BIOS "successfully" and when I restart my PC, I have to do either F1 to config or F2 to load setup defaults. So it looks like it's working, but the online update says that I have versions H.10 and version H.A0 is available (or maybe the other way around). So either the BIOS is getting updated, but the online tool is not recognizing this or it's not getting updated. Either way, I would like to manually flash it in DOS. Is it safe to burn the setup files to CD and boot from CD into DOS?
That's the same BIOS version... Just the "MSI Live Updater" is not very smart...
H.A=H.10=17.A=17.10 [A=10, H=17], the last "0" suffix in H.A0 means its official version.
Quote
I tried the online utility 3 times. It always updates the BIOS "successfully" and when I restart my PC, I have to do either F1 to config or F2 to load setup defaults.
So it looks like it's working, but the online update says that I have versions H.10 and version H.A0 is available (or maybe the other way around).
So ignore this MSI Live Updater's no sense, and stop flashing your BIOS. You already have the latest version installed.
The Tool now will detect and shows BIOS versions alias when the MSI BIOS version is known with more than one name.
So no more flashing and flashing and flashing to the same version because of MSI LiveUpdate suggest again BIOS update...
Also no more confusion:
"What's my BIOS version?" -> I flashed my BIOS to 1.A0 [A7520IMS.1A0], but BIOS says its 1.10
And MSI Live Update also says that i have 1.10 and 1.A0 is available and i should update it. I flashed it again, but its still 1.10?
What's going on?
Just run the MSIHQ USB Flash Tool and will show you all that you need to know
Examples[with real/accurate info]:
MSI Eclipse:
BIOS version 1.9:
BIOS version 1.10:[Tool now shows both BIOS versions alias]
Report stored respective in MSIHQ_INFO.TXT at user's desktop:
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at 5:30:55,34
Mainboard: Eclipse SLI (MS-7520)
PCB Version: 1.0
BIOS Version: V1.9
BIOS Date: 09/22/2009
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at 5:37:25,66
Mainboard: Eclipse SLI (MS-7520)
PCB Version: 1.0
BIOS Version: V1.A (aka Version: V1.10)
BIOS Date: 10/27/2009
More examples =>K9N6SGM-V / K9N6PGM-FI / K9N6PGM-F :
More examples =>945GCM5-F V2 (FSB 1333) :
Report stored respective in MSIHQ_INFO.TXT at user's desktop:
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at 5:47:34,35
Mainboard: MS-7267
PCB Version: 4.0
BIOS Version: VH.9 (aka Version: V17.9)
BIOS Date: 11/20/2008
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in ба 30.12.2009 Ј. at 5:52:46,26
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VH.A (aka Version: V17.10)
BIOS Date: 06/02/2009
More examples =>780GT-E63 [N/A at MSI web yet] :
For MSI Notebooks such decoding isn't need, examples:
* Add new feature "Triple BIOS flash Recovery Ready"
- Updated Mode 1
- Updated Mode 2
- Updated Mode 3
Details:
The feature include 3 auto prepared BIOS backups for followed purpose:
* Internal BIOS recovery:
- In a failure case Tool perform auto flash recovery [3 attempts, check for success after each and stop flashing if successful] before give control to BK_IO2, notice users about results and give control for manual attempts[if need]. [This a case if system isn't lockup/reboot, if bad flash occur]
- This mode also have own store up to 5 backups[+1, the last saved copy is always backup.bin, if there was older one they become backup1.bin .. till 5]
* BIOS backup stored as AMIBOOT.ROM [AMI BIOS only] [Auto clean up older if there is any, before take a new backup to avoid recovery confusion]
* BIOS backup detected and stored for M-Flash style boot/recovery [AMI BIOS only] [Auto clean up older if there is any, before take a new backup to avoid recovery confusion]
Performing test simulations with random generated BIOS versions[including betas] for M-Flash boot/recovery style, some examples:
Copy/paste Tool log file:
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:00:53,46
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VD.XB2 (aka Version: V13.33B2)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.DX2
Where:
* V13.33B2 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VD.XB2 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.DX2 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:12:23,95
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VK.VB7 (aka Version: V20.31B7)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.KV7
Where:
* V20.31B7 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VK.VB7 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.KV7 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:18:34,46
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: V3.9
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.390
Where:
* V3.9 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* MSIHQ Tool "True BIOS Ready" detection feature isn't need here, since this BIOS version can be known only with one name.
* A7267IMS.390 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:22:24,04
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: V8.1B9
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.819
Where:
* V8.1B9==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* MSIHQ Tool "True BIOS Ready" detection feature isn't need here, since this BIOS version can be known only with one name.
* A7267IMS.819 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:25:38,51
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: V4.E (aka Version: V4.14)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.4E0
Where:
* V4.14 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* V4.E ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.4E0 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:28:16,62
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: V1.BB1 (aka Version: V1.11B1)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.1B1
Where:
* V1.11B1 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* V1.BB1 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.1B1 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:31:57,78
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VI.FB5 (aka Version: V18.15B5)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.IF5
Where:
* V18.15B5 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VI.FB5 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.IF5 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:36:02,40
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: V7.O (aka Version: V7.24)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.7O0
Where:
* V7.24 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* V7.O ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.7O0 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:39:11,84
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VC.8B6 (aka Version: V12.8B6)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.C86
Where:
* V12.8B6 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VC.8B6 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.C86 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:49:38,46
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VG.PB6 (aka Version: V16.25B6)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.GP6
Where:
* V16.25B6 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VG.PB6 ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.GP6 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3]
MSIHQ: Information detected by MSIHQ Tool ver: 1.18x
MSIHQ: Report generated in 03.01.2010 г. at 7:53:17,26
Mainboard: 945GCM5-F V2 (MS-7267)
PCB Version: 4.0
BIOS Version: VU.H (aka Version: V30.17)
BIOS Date: 06/02/2009
Co-respond BIOS backup created ==> A7267IMS.UH0
Where:
* V30.17 ==> MSIHQ Tool detection [The same as CPU-Z, Everest]
* VU.H ==> MSIHQ Tool "True BIOS Ready" detection feature
* A7267IMS.UH0 ==> MSIHQ Tool BIOS recovery created by "Triple BIOS flash recovery Ready", part M-flash boot/recovery [1/3] -
BIOS FLASHING
We do not recommend using the MSI LiveUpdate tool to update your BIOS! It may be okay for updating your drivers, but please do not use it to flash the BIOS in Windows!
Windows-based flashing - If you REALLY insist on flashing the BIOS under Windows, if you encounter any error during flashing, whatever you do, DON'T restart your PC! Try again until the flash is successful, otherwise your board will not start! Disable any anti-virus program (along with any other programs) prior to flashing.
Boards with built-in M-Flash function - While M-Flash work's properly most of the time, it has still proved to be less reliable than the forum tool / manual flash.
Before flashing your BIOS, you must ensure your system is fully stable! Any instabilities can cause a bad flash and create an expensive paper weight. Included with the forum flash tool is MEMTEST, we recommend running this for 2 or more passes prior to a flash.
If you do not understand what your BIOS is, or what it does, please read: >> BIOS. What it is, and all you need to know <<
Our first choice we recommend you use is our own USB flashing tool, developed by Svet.
It is important to note, that the only way to flash the ME extension of the BIOS of modern Intel boards is through the use special processes. The bios versions posted by moderators here: >>BIOSes<< include the additional files to accomplish this. These bios are all official and are directly from MSI.
>>>MSI Forum HQ USB Flashing Tool<<<
If you are unable to use the MSI HQ USB BIOS Flashing Tool
>>How to create a dos bootable USB stick>>
It is important to note that if any BIOS, EC FIRMWARE or any other type of FIRMWARE downloaded from MSI for a manual flash contains an BAT file it must be used. Not doing so will cause the flash to fail and require RMA.
For Intel Users, flash via FPT
Socket LGA 1150 : >>ME 9 FPT files & Instruction>>
Many of the bios versions posted here: >>BIOSes<< Contain a .bat file. All you need to do is extract all of the contents of the archive into the root directory of a DOS bootable USB stick and run the bat file from pure DOS.
Socket LGA 1155 & 2011: >>ME 7&8 FPT Files and instruction<<
Linux users
See this topic: >>Flash your BIOS, the Linux way! [beware the dangers!!]<<
Modified and BETA BIOSes
Use only at your own risk! All BETA BIOS versions posted by the moderators of this forum are directly from MSI and will not effect your warranty.The use of user modified BIOS versions may damage the board and may void your warranty. Exercise extreme caution in regards to user posted BIOS versions. Please also be aware that MSI and this forum can not be held responsible if you trash your mobo by using a modded, beta or otherwise incorrect BIOS.
WHEN IT ALL GOES WRONG...
BIOS RECOVERY
In many cases, provided the 'bootblock' of your BIOS is not corrupted during a bad flash, the BIOS can often be recovered by following the recovery procedures detailed below. NOTE: this recovery method should not be followed for normal practice of updating your BIOS!
For Modern MSI Systems, refer to:
<<Multi-Bios Equipped Mainboards>>
<<Single-Bios Equipped Mainboards>>
Legacy Systems:
For Award BIOS
Make a bootable floppy disk*
Copy the Award flash utility & BIOS file to the said floppy disk
Create an autoexec.bat with "Award_Flash_Utility BiosFilename" in the content (e.g. awdfl823K w6378vms.130)
Sample on how to create an autoexec:
a. On Windows, open the notepad
b. On the notepad, write "awdfl823K w6378vms.130" (without the " ")**
c. Save the file as autoexec.bat
Boot up system with the said floppy (it will take less than 2 minutes before screen comes out)
Re-flash the BIOS & reboot.
*Need a bootable floppy disk? Look here: http://www.bootdisk.com
**Make sure you enter the correct filenames for your flasher program and BIOS ROM file!
For AMI BIOS
Rename the desired AMI BIOS file to AMIBOOT.ROM and save it on a floppy disk. e.g. Rename A569MS23.ROM to AMIBOOT.ROM
Insert this floppy disk in the floppy drive. Turn On the system and press and hold Ctrl-Home to force update. It will read the AMIBOOT.ROM file and recover the BIOS from the A drive.
When 4 beeps are heard you may remove the floppy disk and restart the computer.
For new boards with AMI BIOS core 8 (4MB)
Discovered by Jack The Newbie:
Of course, the steps are similar to the standard AMI BIOS Recovery Procedure for internal floppy drives (rename corresponding BIOS File to AMIBOOT.ROM, hit CTRL + HOME after starting the system).
What has to be done (tested on P45 Platinum):
1. An optical SATA Drive needs to be connected to one of the Intel ICH10R SATA ports. {After a lot of testing, I found that it does not work with the same optical drive connected to the SATA Ports hosted by the secondary JMicron Controller. Also, using an optical drive on the JMicron IDE/PATA port does not help either.}
2. A proper BIOS File has to be renamed to AMIBOOT.ROM and burned on an empty CD.
3. CMOS-Clear with main A/C power cable removed from PSU has to be performed. {If this step is not done, the system will reboot after pressing CTRL + Home and will not proceed with recovery procedure.}
4. Press CTRL + Home to trigger BIOS Recovery. -> The system should enter BIOS Recovery Routine. {Will basically work with both USB & PS/2 keyboard. However, a PS/2 Keyboard is recommended as the system will respond earlier to PS/2 Keyboard than to USB Devices.}
What should happen now:
1. After pressing CTRL + HOME the LED Status should change to "Intializing Hard Disk Controller" and there should be access to the optical drive connected to the Intel ICH10R SATA ports.
2. It can take up to 30+ seconds until the BIOS File that was renamed to AMIBOOT.ROM is found. {Drive Bay can be opened to try a different CD without turning off or restarting the system.}
3. When the system finds the BIOS File, LED Status will change to "Testing RTC" and there should be a message on the screen indicating that the Flash Recovery Procedure has started.
4. Since the BIOS File is 4MB in size, it will take a while until the BIOS is actually reflashed.
Its also possible that BIOS recovery on boards with AMIBIOS8 can be done using a FAT-formatted USB stick, containing the renamed BIOS file. Be warned, in some circumstances it may take several moments before recovery procedure actually begins. See Bas' reply below for further information.
BIOS recovery on Wind netbooks
See this post here:
https://forum-en.msi.com/index.php?topic=130509.msg982711#msg982711
BIOS recovery on non-UEFI notebooks
In order to recovery this type of system you will need an FAT32 formatted USB stick.
Download the applicable bios from MSI's website and rename this bios.
It must be re-named to either AMIBOOT.ROM or xxxxIMS.ROM / xxxxAMS.ROM You may need to try each way to determine which one is necessary.
Then place the renamed bios onto the root directory of the FAT32 formatted USB stick.
Now you are ready to cover the Notebook.
To do this, remove the AC power cord and battery. Once that has been completed, install the USB stick you prepared earlier.
Now, apply AC power (leaving the battery disconnected) and turn on the notebook. Recovery should begin after 5 minutes.
IF ALL ELSE FAILS...
Locate the BIOS chip on your mainboard. If it is soldered directly to the PCB like...
...then you have no choice but to return the board to your supplier, or to MSI, for replacement.
To request an RMA from MSI, open a support ticket at https://register.msi.com/ocss/
If your BIOS chip is in a socket, like...
...then you may be able to source a replacement BIOS chip, either from MSI, or from a website such as www.badflash.com
Updated 11/21/2013, original post by StuA.) Download >>this<< bios archive and place it on your desktop. Do not decompress.
B.) Download and install the >>MSI HQ Forum USB flasher<< .
C.) Insert your FAT32 formatted usb stick.
D.) Make sure that all win 8 options are disabled. (Fast Boot etc) Also make sure the legacy USB is enabled.
E.) Start the forum flash tool and select option 1. Then point the tool at the compressed archive we downloaded earlier. Then to your USB Flash Drive.
F.) Boot to the USB from working bios B.
G.) Once it booted successfully switch to bios A without powering down or rebooting
H.) Now follow the directions and let the tool flash bios A with desired version -
Ok this is a quick question regarding BIOS flashing,
When flashing the BIOS of the K9A Platinum, I should follow the AMI BIOS Flash Procedure
Instructions NOT the Award BIOS Flash Procedure or Flashing the BIOS for Non-FAT file system instructions, right? (my hdd drives are NTFS formatted).Quote from: AlexTG on 15-July-07, 22:28:40
I downloaded yesterday the Windows Proggie AMI gives for flashing the BIOS ... works like a charm
nice as well
so 1.6 is hurting VGA performance you got 8800 GTX with lower scores when using 1.6 and just fine scores with 1.5.
crackedd got the same result, but with x1950 VGA.(https://forum-en.msi.com/index.php?topic=109699.msg814859#msg814859) -
Can't Enable XMP after BIOS flash to V1.4 on P55-GD85
I didn't put this in the BIOS section because while the BIOS is involved, I don't think it's necessarily a BIOS issue. However, if it should go there please move it.
While not new to computers by any stretch I committed the cardinal sin of updating my BIOS when I didn't absolutely have to. While their were some issues I'd hoped would be fixed with a new BIOS revision, they weren't critical.
I have a i7 860 Lynnfield system running Win 7 Home Premium 64 with a MSI P55-GD85 mobo which has been running fine since being built in March of this year. This was the first BIOS flash since I've built the system. The system came with either V1.0 or V1.1 (I think it was V1.1). I checked using Live Update (yes, I now know this is bad) and found there had been several udpates since my current version. I went ahead and used Live Update to flash the BIOS (yes, I know...not a good idea). Contrary to the horror stories the flash itself went fine. I watched it flash the BIOS and everything verified fine. Of course after the update I had to reset my BIOS settings to get the system to run which went fine. The problem is that the one thing I can't do is enable the XMP option for the memory without the system crashing. If I enable this option the system will POST and then do a memory dump before ever getting to the desktop. Without turning this option on I can't take full advantage of my RAM. I am running G.SKILL Trident 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 2000 (PC3 16000) which are XMP compliant and ran without issue up until the BIOS update. It is possible that there is some other setting that I didn't reset after the BIOS change to allow this to work that I am missing. I know I did a bunch of tweaking and changing of settings trying to get things to run correctly when I first built the system. I've gone over and over the BIOS and can't find anything else to try to get me to allow to enable the XMP option without crashing. By simply enabling that option my system would normally run stable at about 3.6-3.7GHz.
Does anyone have any ideas as to why this might be happening or what I can do about it? About the only other thing I can think of is to reflash the BIOS back to a previous version to see if that helps. I am sure there is something I am missing as there is no reason the BIOS shouldn't allow the XMP feature to be enabled without crashing. Any help would be most appreciated. Thanks.Have you try to increase your RAM voltage to 1.55v ~1.6v?
-
Thinkpad R40 type 2682 - 6GU Bios flash problems
Hello all! I made sure to check all of the R40 threads for information on this, and have been unable to find anything, I was hoping you could help me!
I recently purchased a Thinkpad R40 type 2682 - 6GU, and absolutely love it! I maxed out the RAM (1 gig), and it came equipped with Windows XP professional. It has the internal 802.11a/b wireless pci card.
I just purchased the IBM Thinkpad MiniPCI Atheros 802.11g card, and saw that I will need the latest BIOS
Version: 1.27
Release Date: 2006/06/30
1ouj24us.exe
installed for the card to work. I checked, and I currently have 1.14 .
I downloaded the file straight from the Lenova Support & Downloads site. I read the readme file, and followed all of the instructions, and it isn't doing anything. I will give a detailed description of what I am doing, to see if you can pinpoint something I am doing wrong, or a setting somewhere I need to change.
1. saved file as C:\bios\1ouj24us.exe
2. opened start menu --> run
3. typed in c:\bios\1ouj24us.exe --> enter
4. clicked "run"
5. accepted EULA
6. chose "next" through the first 4 messages
7. chose "next" on the next 1 of 4 messages
At this point, the computer restarts, logs into windows (no user accounts or passwords setup yet to avoid the mess of that during BIOS flash), loads like normal, and no further process on the BIOS flash. I have done this at least 20 times on the same machine, and it still has BIOS ver 1.14 .
Can you please help?!?
Thanks in advance,
LeeIf it's a genuine IBM card, there should be a sticker on it saying FRU P/N 39T0081 or something like that, but would include a FRU P/N part regardless of the actual number.
A generic card will throw a "1802 error" in a R40, where the original one won't.
You can't update BIOS on a machine that has a bad battery or charging issues, BTW.
Cheers,
George
In daily use: R60F, R500F, T61, T410
Collecting dust: T60
Enjoying retirement: A31p, T42p,
Non-ThinkPads: Panasonic CF-31 & CF-52, HP 8760W
Starting Thursday, 08/14/2014 I'll be away from the forums until further notice. Please do NOT send private messages since I won't be able to read them. Thank you. -
Where does HP BIOS flash update tool save old BIOS backup by default
Where does this HP BIOS flash update tool save old BIOS backup by default ?
http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=ob-69499-1&lc=en&dlc=en&cc=us&...I think the gpu has failed again, if the bios was dead you would get no beeps, it is the bios that generates the hardware failure beeps.
Home brew reflows generally do not last too long or can cause more damage.
The reason the gpu comes loose on most of that vintage was due to 2 problems
1. Overheating
2. Poor quality solder used when the gpu and other motherboard components were flowed at the factory.
Reflowing it does not always work because of the quality of the ball solder they used, also you only get one reflow attempt, doing more than one weakens the original solder even more. Most likely the seller reflowed it shortly before selling it to you.
Proper repair is what is called a reball (solder replacement) of the gpu, not may repair facilities have the equipment to performed this, and is usually expensive procedure depending on the motherboard design. -
Bios flashed, rma, windows still wont load
Evening,
I flashed with live update (yes i know now..) and it went wrong. Board, P55-cd53, sent to MSI who reprogrammed it. Unfortunately windows wouldnt load. I think i have tried every described method posted here, even flashed back to the old version, to no avail. I even tried a boot dvd with ubuntu but even that OS wont run (either with or without installation). The pc simply reboots when trying to execute these commands.
If i were to replace any hardware: what would it be?
System specs
P55-CD53
intel i5 750
ocz-gold-low-voltage-ocz3g1333lv4gk
Msi hawk 5770
Samsung spinpoint f3 500gb
Cooler master real power M520
Thanks,
HarryQuote from: Svet on 10-October-10, 16:16:23
Before this bios flash it was worked fine?
I was having regular BSOD, especially when leaving the pc on overnight. Other than that everything worked fine.
Quote
Do >>Clear CMOS Guide<< with power cord removed.
Then Load BIOS Defaults
I did this before sending it back to MSI. I haven't done this after i received the mb back from MSI. Will try today.
Quote
Check memory voltage in BIOS setup, you may need to apply voltage recommended by your memory vendor for your sticks
Also do check with >>Memtest86<<
Memtest came with the Ubuntu-disc. I ran it and the Memtest results were shocking. I only did 5 runs but received thousands of failures.
I will replace the OCZ rightaway instead of finetuning them in BIOS.
Also adressed to Jack: Would the G-skill F3-12800CL9D-4GBNQ be a good choice? Right out of the box without adjusting anything inside BIOS?
Quote
Else reinstall OS
So far i haven't been able to reinstall or repair (from disc and usb) my windows 7 at all, not even Ubuntu.
System just keeps telling me 'the ntoskrnl is missing or corrupt' and keeps doing restart loops.
Would replacing the DRAM solve my problems likely or would it cost me a new MB or HDD too (if al else fails)?
Thanks,
Harry
Maybe you are looking for
-
Problem with explicit cursor fetching in oracle 8.1.7
Is there any cursor attribute which can fetch the previous or next record from the cursor using pl/sql. thanks in advance
-
Mapping error :Collecting file : BpmPatternCollectTime
Hi I am trying to use Multimapping with BPM, for 3 files correlated based in some field value but mY collectpattern is not workin, Workflow shows errror in Message Mapping Runtime exception Attach Mapping http://img255.imageshack.us/my.php?image=map
-
Updating a JTree without application restart
I would like to update the JTree in my application without restarting the application. The JTree elements come from a file, therefore, I update the file and want the JTree to be refreshed! I understand that this is done with swing and model and alrea
-
I cannot increase the volume of Maps or Mapquest on my Iphone 4S loug enough to hear it. Are there better navigation apps or does anyone know how to make the volume louder?
-
Password validation script checking against stored passwords
I am able to create a script to check and validate for the password complexities outlined by our Active Directory GPO, but is there a way to check the password against the 1-24 stored passwords to validate that it hasn't been used before? Thanks