Gt 1030 Bios

[Yazmín Bohon]

Ihave Inspiron 3470 with i3-9100, 8GB RAM, Win 10 installed on M.2 SSD 250GB.

I bought (not from Dell) Gigabyte GT 1030 Low Profile, 2GB GDDR5 that consumes 30W and draws all the power from the motherboard.

The problem is, the graphics card fits perfectly and the fan spins but not detected in the BIOS.

I've tried changed settings in BIOS, especially disabling secure boot and altered many other options relating to this one by one.

I know that Gigabyte GT 1030 suggested PSU to be 300W, and my Inspiron is only about 200W, but I've seen people using similar combinations as mine without any power problems.

Have you tried clearing the BIOS using the CMOS jumper per the service manual? It may need to be cleared to detect the new card. Also what happens when you install the 1030 drivers or can you install the drivers?

What you describe is *exactly* how my Headland HT12 286 mainboard behaves when no or a flat battery is present. Add a new battery, give it a few minutes, and then try again. It will most likely work without any issues then.

Edit: forgot to mention keyboard LEDs behaviour. With the original AMI bios/KBC, the leds blink right after the memory test (i think they should blink immediately after power on). With Phoenix chips, the leds blink at power on and then i get 3-1-3 beeps and code 22 on the display, all of these within a second or so.

The traces were still good on the motherboard. With flux on the copper traces, heat from the iron will let the solder just flow to those parts. It will basically paint itself down neatly on the copper. Rosin core solder and a flux pen help do the job.

As Auzner said. I actually used old-fashioned rosin flux, which i melted with the soldering iron on minimum heat and deposed all over the affected area, then at around 350 degrees C i have tinned the tracks. I use a DYI (not buit by me but bought from someone that builds them) soldering station for most of the stuff, and a non thermo-controlled, 40-watt iron mainly for desoldering stuff.

About the errors when booting without KBC. When using the Phoenix bios, i get the same error code 22 with or without the controller. Swapped back to the original AMI bios, and although i am pretty sure that initially the board was completely dead when starting without KBC, now if i do that it displays a "8042 gate A20 error" and gives continuous and rather annoying beeps.

- pin 31 is connected to GND on the working board but left floating on the bad one, pulled it down with 100 ohm resistor and it didn't change anything.

- on the good board there are 4 jumpers that can short pins 23, 27, 30, 32 to something that i haven't identified yet (it's not +5v or gnd), here's what stason.org page on that board says about these jumpers: Note: Make sure that the BIOS and the keyboard controller are compatible before shorting a controller pin for speed change via software.

- there are some differences in the supporting circuitry (bad board has quite a few more 74LS chips), so for example pin 21 of the KBC that on the good board connects directly to pin 9 (Reset) of the VL82C101 system controller, on the bad board goes first through not one but two buffers from a 7407 chip (and there is something that connects in between the two buffers).

Had no time for that, and besides i think it might be futile without an oscilloscope or logic analyzer (only have a couple of multimeters).

For a quick and dirty test i replaced once again the bios/kbc with some Award ones from (another) working board. This one seems to give the most details about the problem:

After displaying the above, the system hangs with Code 26 on the POST card. The CMOS battery failed message keeps appearing even when i connect an external battery pack and the RTC chip receives power. I'll keep searching, but after triple-checking all connections from the kbc and all the corroded/repaired traces i'm thinking more and more that the problem lies elsewhere (chipset, support chips).

Found the problem, it was inside the VL82C100 peripheral controller. Took my chance and transplanted the chip from another board which had it socketed - it was so tight that i couldn't extract it with the PLCC tool, i only managed to chip away one corner of the package (hence the ugly diagonal scratch). I had to desolder the socket with the chip still in it and then tear it to pieces.

I also tried to solder a PLCC84 SMD socket on the DTK board, to have the chip easily removable in case it didn't solve the problem, but found this to be impossible: the solder pads on the board didn't extend inwards as much as i needed to get a reliable solder joint. Fortunately the problem is now gone so there's no need to remove it again. For the removal of the defective chip i long planned to get a hot air station, but in the end took it off with only soldering iron and copper braid.

So now the donor board is in a non-working state, but i'm okay with that. It's an Essex Electric for which i cannot find any documentation online, it has quite a few undocumented jumpers and also some options like onboard floppy controller (missing) and onboard serial ports. I know i can easily bring it back to life if i find a replacement VL82C100 chip - if someone has one, please contact me.

Well, i got myself a new soldering/desoldering station (ZD-917) a couple of weeks ago, and that reignited my interest in my broken boards. I already found a toasted MC14069 hex inverter on this board, but unfortunately after replacing it the board is still as dead as before.

On the DTK board i checked all 14 or so logic chips (desoldered them using the station, tested them in the TL866CS programmer) and all were ok, so i took the risk of exchanging the peripheral controller. I wasn't 100% sure that it is faulty, it was more like a hunch. I must say that the Award bios helped me with that - check that "Interrupt controller #1 failed" message a couple of posts back. And since the interrupt controllers are inside the VL82C100...

I recently had the need to update the firmware on an HP LSI22320-HP U320 SCSI card. The HP firmware was resulting in Domain Validation (a SCSI technique to determine appropriate/supported SCSI speed for each SCSI device) errors. I wanted a more up to date version. I turned to the Broadcom LSI22320SE driver site and found an updated firmware download, in a file named Fusion-MPT_IT_FW10334_BIOS_50703pt_FLASH_10304.zip.

I created a USB boot disk with FreeDOS using Rufus (a great tool I only just found). I copied the relevant files (dos4gw.exe, flsh1030.exe, mptps.rom and it_1030.fw) to the USB stick. I booted up and tried to update. I managed to apply the firmware (it_1030.fw) but not the BIOS (mptps.rom). The error displayed was:

I installed NVIDIA driver version 390.59 for GT 1030 graphics card on my Ubuntu 16.04 kernel version 4.15.0-24. I had a login screen loop problem that I have fixed by reinstalling the driver again and again every time (I got the idea from Ask Ubuntu forums).

I updated the driver with version 390.67, but this time I got a double problem: I lost the kernel built-in Ethernet driver r8169 after every suspend/resume cycle that I replaced by a proprietary driver r8168-dkms, and the system reboots rather than hibernates when I resume after suspend.

Hi guys, I've installed a sapphire rx6400 card on my hp prodesk 600 g5 and since then there is no image in my monitor until windows boots. If I want to access the bios I have to plug the monitor to one of the video outputs from the mobo.

Hi, thanks for your replacement! Unfortunately that was my first thought but there is no such an option in the hp bios. Was reading through the bios manual and that option is only available for desktop apparently (and it seems that a SFF pc is not a desktop)... I will look around if there is a way to make this option to show in the bios..

I believe that when the Nvidia card (gt1030) was installed it was recognized by the bios and those options (integrated video and vga boot device) appeared in the bios menu. Fortunately I still hace that card. I will install it over the weekend and see if the BIOS recognize that card and shows more options.

Could it be that the BIOS doesn't recognize the rx6400? It is strange cause windows/linux does. If the monitor is in standby/idle when I power the pc, it wakes up, but shortly after shows a message that says no signal until windows starts to boot.

I suspect it's that the BIOS is not treating the card as the primary display device. Typically there is an option in the BIOS to set which display (Integrated or PCIe) is the primary, and gets the boot output. Once Windows loads the AMD driver the RX 6400 gets output.

Aside from the display output issue, and you may already be aware, your HP system only supports PCIe 3.0 so even though the RX 6400 is a PCIe 4.0 card it is restricted to PCIe 3.0 speed. Even worse, it is only an x4 lane card, and PCIe 3.0 x4 has a max bandwidth of less than 4GB/s, so performance is being impacted. Given that your options are limited due to the SFF needing a half-height card, and the RX 6400 would still outperform a GT 1030, but probably getting only half of the performance the card should be.

Well I have swapped the cards just to confirm. Effectively, the 1030 is recognized by the hp bios and I can see the bios through the card video output (and I can disable the igpu), but the rx6400 is not. I'll have to live with that for a while..

When I boot into windows I get a message on my laptop's screen saying "console does not support current video mode", and the external display connected to the GPU just stays showing the HP logo, and the laptop display stays blank. On my laptop's screen I see this message, which makes it seem like HP has locked down the BIOS, meaning I can't use an eGPU, and there is no way to disable the iGPU and the iGPU does not want to give proper priority to the eGPU.

Funny thing is, when using the BIOS and a windows install/repair USB, the 1030 outputs everything perfectly onto the external monitor with the laptop's screen turned off like with a working eGPU setup, but when Windows loads and drivers start turning on, HP's stupid restrictions prevent the eGPU setup from working.

3a8082e126