Intel G33 G31 Motherboard Drivers Free Download

0 views
Skip to first unread message

Emir Ballard

unread,
Aug 3, 2024, 3:31:46 PM8/3/24
to icetclimob

Dear Intel Community,

I notice artifacts for my GPU - Intel G31/G33 after Ubuntu 20.04.2.0 installation. I used Mesa graphic driver. I don't know what version it is was but I returned back to Windows 7 OS and now I still have these artifacts. I used Ubuntu 20.04.2.0 with liveUSB because I wanted recovery some files from my secondary hard drive.

This was coincidence or this was real chance that Ubuntu 20.04.2.0 operating system could destroy my hardware (GPU)? Can you tell me?

I didn't changed any settings in BIOS but I readed that maybe solution can be drop frequency of the GPU. How I can do this?

I hope that someone can help. I really want to get help because I still use this old computer.

We would like to inform you that due to the Graphics Drivers for Intel G31/G33 Express Chipset has been discontinued, Intel Customer Service no longer supports inquiries for it, but perhaps fellow community members have the knowledge to jump in and help. You may also find the Discontinued Products website helpful to address your request.

- CPU: Intel Core 2 Quad Q8200


After installing Ubuntu 20.04.2 I noticed artifacts like I said. Is it a option that GPU was damaged because problem with the buggy linux driver?

What person from Intel Community have knowledge about old drivers and firmware for Intel G31? Can you tell me? If someone from community can help please answer me. I will very apreciate for this.

For something this old, I can only provide general recommendations. Remember that the GMCH is using DRAM as VRAM for its graphics engine. Often, when artifacts are seen, it is the result of using bad or incompatible DRAM. Are you seeing the same issues when you are in the BIOS Setup?

@n_scott_pearson thank you for your answer. I think that RAM is good because before I used Ubuntu 20.04 my machine worked fine. I also noticed that these artifacts are visable randomly. This is not on all time in my screen. This looks strange. On BIOS I didn't see these artifacts. Is this possible that linux driver change something in firmware of my GPU? If yes, how I can restore it to default?

There is no 'firmware' in the processor (per se) that Linux could interfere with. Linux has the ability - and I believe this is enabled by default - to install any microcode updates that are available for your processor. It is possible, though highly unlikely, that this is playing a role here.

@n_scott_pearson thank you very much for your answer. This graphic card Intel G31 is located on the motherboard, not in the processor. So the firmware for this GPU is included in BIOS of the motherboard or in the processor? Maybe linux updated microcode because Ubuntu 20.04 is new system but I didn't download update for Ubuntu OS. I returned quickly to Windows 7 OS because I believed that this is problem with Ubuntu and still I think that this OS could did something wrong with my machine. Is it option that drivers for my GPU in Ubuntu make someting wrong with firmware? If not maybe this did for example too high frequency or something similar and now I have problems?

If I will reflash BIOS of the motherboard this will reset firmware of the GPU? If firmware is located in BIOS on the motherboard? Or GPU have own BIOS and this is not BIOS of the motherboard? Do you know?

Sorry, I was lumping the two (processor and chipset) together for brevity. The driver for the GMCH may load some firmware, but this would only be temporary and gone once a hard power cycle occurs. Installing a BIOS update may include a more-permanent version of the firmware (the "Video BIOS") but no O/S should be able to affect this in any permanent way (though BIOS and especially Firmware Hub security back then was not as good). You can certainly try updating (or re-updating) the BIOS to the latest available version.

@n_scott_pearson thank you for your answer. So the "Video BIOS" is located in motherboard because Intel G31 GPU is located in the motherboard but if I will update motherboard BIOS this probably don't change VIDEO BIOS? This is separated BIOS dedicated for GPU but how it can be updated or reflashed? Intel company didn't share with this firmware? How I can do this?

My story with hardware issues will not end. I don't use old computer with G31 GPU any more and I recycled it. Now I bought new notebook with i3 11 gen and I have similar hardware issues. I noticed also strange behavior on my another computers. I don't use Linux family operating system anymore and all my machines runs Windows so I think that these issues might be related to malware. I think that is it comes from exploits in Ubuntu OS in my old hardware. My old PC probably was compromised next this infect my home router so that is why my new hardware also have issues. Of course I reinstalled Windows and wiped all data on SSD drive on all machines but this looks like firmware level issues so this can be BIOS rootkit or other malware in low level (firmware).

So I have question. How I can fix it? I know that is almost impossible in home environment so maybe someone from cybersecurity specialist can create vaccine for this malware? I know that Ingel have specialist because you owned McAfee Antivirus company in the past.

What is the symptomps? I have black artifacts in some scenarios. For example when loading images, websites etc. I also have issue with mouse which click right button itself and sometimes my apps like Chrome browser will close itself so this is not normal.

I think that this malware can be in GPU firmware so maybe Intel specialist should look on code from my machine to prevent this infection for other users?

I hope that you can help.

I think that is not damaged RAM or GPU. It looks like bug because only some interface of Windows 7 looks like artifacts. When I play videos on full screen for example I don't have any artifacts. Very strange behaviour and this looks like microcode or driver are buggy now after trying Ubuntu.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

Recently I installed Windows 8 in my desktop. It's actually 1440*900 monitor. The motherboard manufacturer didn't provided Windows 8 drivers yet. I guess, they wont as it's 2008 model. I have drivers for 7 which gave me correct resolution. But Windows 8 don't comes with 1440*900 driver for my monitor. Is there any way I can suppress the "Best driver installed bla bla" and use the drivers of Windows 7?

Display, Resolution, Graphics drivers mainly based on motherboard drivers. Since I have Intel G33/G31 Motherboard, I can't find the drivers from the official site. But however DownloadAtoZ.com offered me a driver. Though I got this site while Googling, I find it's worth to try since the download link actually points to WindowsUpdate.com.

Looking at the update driver window from device manager, you choose the "Let me pick" option, and then the "Have Disk" option, you will see the old Install from disk window with the A: drive shown. Browse and choose your driver files from this window and you will be able to Install any driver you want. Even if it don't work afterwards. But it is a way to force a driver install on Windows 8.1.

Extract umbpci_e.zip, hiram.zip and himem334-unofficial-rp.zip to a temporary folder (can name it DOS or something like that). Burn the temporary folder to a writable cdrw. You can do this in your favorite OS.

After fat32 partition is ready, and you know what you're doing, copy the Win98 folder from the Windows 98SE CD to the C drive (your fat32 partition). This is needed when 98SE prompts to insert 98 cd during driver installs and you have 32-bit HDD drivers disabled (because 98SE doesn't like modern HDD controllers usually, and Cdrom drives aren't available after setup this way).

Insert your Windows 98SE CD. Reboot PC and boot from CD. Select to "Boot From CD-Rom" choice at startup menu. Select to "Start computer with CD-ROM support" choice at next startup menu. Assuming cd driver letter is D (default), start setup without acpi: [code]D:\win98\setup /pi[/code] When setup initializes it prompts to perform a routine check, hit enter to continue. When scandisk finishes without errors, setup will continue as normal. Proceed with setup until prompted to reboot (when prompted to create startup disk during setup, click next and click cancel to avoid making floppy; and click ok to proceed setup).

This is the hard part... Upon reboot, boot from Windows 98SE cd again: select to "Boot From CD-Rom" choice at startup menu, and select to "Start computer with CD-ROM support" choice at next startup menu. Assuming C is your fat32 drive (which Windows 98SE has just used), go to the windows\command folder and do the following like this: [code]cd C:\windows\command
edit ..\system.ini[/code] Go to [386Enh] section and add some lines so it looks like this: [code][386Enh]
LocalLoadHigh=0
MaxPhysPage=40000[/code] Go to [vcache] section and add some lines so it looks like this: [code][vcache]
MaxFileCache=65536[/code] Do ctrl+S to save system.ini (or save via menu). Open system.cb while you're still in edit (same folder as system.ini), and add the same lines and the missing section headings for those lines so it looks like this: [code]
[386Enh]
LocalLoadHigh=0
MaxPhysPage=40000

[vcache]
MaxFileCache=65536

[/code] Save this file too. Close edit. Swap Windows 98SE CD for the cdrw you burned with the temporary folder. Copy the files from temporary folder in CDRW to your C drive like this (assuming you named temporary folder "DOS"): [code]mkdir C:\DOS
copy D:\DOS\*.* C:\DOS[/code] Change attributes of config.sys in C:\ and open config.sys with edit: [code]attrib -R -H -S C:\config.sys
edit C:\config.sys[/code] Comment out lines containing himem.sys and emm386.exe so they look like this (assuming you installed Windows to default folder): [code];DEVICE=C:\WINDOWS\HIMEM.SYS
;DEVICE=C:\WINDOWS\EMM386.EXE RAM[/code] Add the following lines under DOS=HIGH,UMB,AUTO so it looks like this: [code]DOS=HIGH,UMB,AUTO
DEVICE=C:\DOS\UMBPCI.SYS
DEVICE=C:\DOS\HIRAM.EXE
DEVICEHIGH=C:\DOS\HIMEMX.EXE /MAX=2097152[/code] Restore attributes to config.sys: [code]attrib +R +S +H C:\config.sys[/code]

Reboot PC, and boot Windows 98SE in safe mode (can hold right-shift key, or hold f8 during boot). Right-click "My Computer", click properties, go to "Performance" tab in "System Properties" window, and click "File System..." button. Click "Troubleshooting" tab, and click box "Disable all 32-bit protected-mode disk drivers"; click "OK" button and reboot. Proceed with Windows 98SE setup as normal.

c80f0f1006
Reply all
Reply to author
Forward
0 new messages