Nforce4 chipset driver abit kn9

Cons: realtek. Overall Review: if you still use the old ide drives, they were kind of a pain to attach to if you have your disk drives already in the case. Sold by: Newegg Shipped by Newegg. Learn More. This item is currently out of stock and it may or may not be restocked. Out of Stock. Add To Wish List. Are you an E-Blast Insider?

A full-featured motherboard with plenty of power, the Abit KN9 is great motherboard for anyone needing to replace or upgrade their system. It also includes a gigabit Ethernet port, 7. Build a powerful system; the Abit KN9 is a perfect motherboard to use as a foundation. Gigabit LAN is ideal for supercharged seamless streaming of Internet audio and video content. Heatpipes do without an active fan, cutting down on noise pollution from your case and enhancing the stability of components on your motherboard.

Verified Owner. Did you? Yes No. George T. It's working!! Joseph B. DO NOT place knn9 caps on these connectors. Hardware Setup After doing this to all the slots, you can slide the board into position aligned with slots. Close the chassis and switch on the power supply unit or plug in the power cord. Click on this tab to enter the menu for installing utilities exclusively developed by ABIT. These indicators kn99 as a reminding device to display the power status of this motherboard with power source connected.

This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are as essential for the working of basic functionalities of the website.

We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.

Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website.

These cookies do not store any personal information. Previous Story Next Story. This website uses cookies to improve your experience. Suspend works. Resume forgets to restore the console display, i. I could log in via network or blind login and type commands on tty[], since I suspended from runlevel 3. From a first glance, nothing else seems to be broken after resume. Monitor stays in power save mode, so nothing is visible. Now, please go to linux Yes it breaks with the same behaviour as described before.

That's unfortunate, because we can't revert this change and the breakage is almost certainly related to your system's BIOS. Please switch to the latest mainline kernel, by going to linux If it returns to the command prompt, please attach the output of dmesg generated right then. Wysocki UTC Sorry, my fault. I patched the current master with all necessary patches and enabled the corresponding debug parts in the kernel.

Freezing remaining freezable tasks I suspect that a serial console won't make any difference. I don't know if it helps, but I have dmesg output before right before crashing the system, I can post it if it helps. Wysocki UTC Thanks. The result of your last suggestion looks like this: Freezing user space processes Wysocki UTC That will be hard to fix. Enabling ACPI debugging might be helpful as well. I'll try to reproduce the problem on it tomorrow. Comment 24 Carlos Corbacho UTC Created attachment [details] Trace output from console during suspend In the meantime, here's the console output from my machine after suspend-to-RAM as per your comment 20 instructions - copied by hand, so apologies for any typos.

Main difference between my machine and Arthur's is that my board is non-SLI. This is with the kn9c12 firmware. I never compiled nvidia's driver for any of the kernels discussed in this thread, so I'm very sure no nvidia.

So this is quite likely also true for Arthur's board. Wysocki UTC Thanks a lot for narrowing this, outstanding work! Do you use any hwmon drivers by chance? Please attach your. Very interesting. I'd much rather figure out what the magic IO resource is that clashes. It's almost certainly some hidden and undocumented or badly documented ACPI IO area that the kernel doesn't know about, because it's not a regular PCI BAR resource, but some northbridge or southbridge magic register range.

Because otherwise we'll just end up bouncing back and forth between different random IO allocations, and they are all almost guaranteed to cause the same problems, just on different boards! It's sometimes possible to even just guess what the registers are, even if things are undocumented. In particular, that E range is almost certainly programmed into the host bridge or possibly a "LPC controller" or similar, and it will probably show up as the bytes "20 14" in the output from lspci, so we can guess which register it is that sets the base.

I'm adding Brice Goglin to the Cc, since he was the one that created those quirks, which implies that he probably has access to documentation on that thing. Unfortunately, on my mainboard this patch doesn't solve the problem. System freezes, power LED stays on. Magic chipset register areas can potentially be mapped this way.

I this on a few boxes and the script worked, but save any work in case you get lockups. This probably won't work, if the APCI ports aren't reserved.

The way suspend-to-ram works is that there's a magic port that the CPU reads from, which just basically turns the CPU off. Same goes for C-states, and while we should recover from that gracefully ie the CPU comes back at wakeup events , if you don't do the right setup, that can also just hang the machine.. I met one case: when some cards insert, i can not use mcp55 on die nic.

So, the patch doesn't work and can be safely ignored feel free to jump off the CC list if this is now no longer relevant to you. However, we are still stuck with the problem that Linus' suspend commit in question is the cause here of a wedged suspend as confirmed by Arthur, the original bug submitter.

So, now that I've wasted everyone's time by CC'ing you all for a patch that doesn't work - what do we need to do to try and hunt down the real cause of why the 0xE port write wedges suspend? Comment 43 Carlos Corbacho UTC Created attachment [details] dmesg with debugging from Abit KN9 Output of dmesg after boot from Abit KN9 warning - lots of debugging options enabled so there's a lot to trawl through.

Sorry guys, I can't help much here, I don't have any doc about this the MSI config is the only details I had about this chipset. Comment 48 Carlos Corbacho UTC Created attachment [details] dmesg with device suspend debugging patch Here's the dmesg output after applying your patches and running your given suspend commands.

I'm having trouble sorting out which report is for which BIOS and some of them don't have any dmesg posted , but I believe in these cases that memory region is indeed reported as reserved by the BIOS, and no PCI resources should end up allocated there. I wonder if this is the culprit from Arthur Erhardt's dmesg : pnpacpi: exceeded the max number of mem resources: 12 pnpacpi: exceeded the max number of mem resources: 12 which means we're ignoring some of the memory reservations.

I wonder if some IO reservations are also being ignored? Why do we have this silly hard limit of number of resources anyway? If we just ignore random reservations provided by the BIOS, we shouldn't be surprised if things break randomly. This warning at the very least should be much louder i.

I suspect it's board specific. And the culprit here is Before the PM code rearranging of 2. ACPI 3. So, 2. So, any pre ACPI 3. Sorry, but you're wrong. For example, section 9. OSPM places all device drivers into their respective Dx state.

If the device is enabled for wake, it enters the Dx state associated with the wake capability. If the device is not enabled to wake the system, it enters the D3 state. The OS places all device drivers into their respective Dx state.

If the device is enabled for wakeup, it enters the Dx state associated with the wakeup capability.