Jump to content
Search In
  • More options...
Find results that contain...
Find results in...


  • Content Count

  • Joined

  • Last visited


This user doesn't have any awards

About X01X012013

  • Title

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Update: I tried a new power supply and it still didn't work, tried a new motherboard + CPU and it now works. So either the old motherboard broke or the old CPU broke. I don't have a way to narrow it down further but most likely the old CPU broke.
  2. Unfortunately nothing worked... I'll try get some spare parts for further testing.
  3. I built this PC just over 4 years ago, and it's been working until yesterday evening. This morning, it doesn't turn on anymore. All fans spin but no POST. This happened once a few days or weeks ago (can't remember exactly), but it worked again after turning it off and on. Today, however, I turned it off and on multiple times and it still doesn't work. I checked EZ Debug LEDs and the CPU one turns on as soon as I press the power button and it stays on. Fans are OK, the lights on my PS/2 keyboard flashes once but USB mouse doesn't get power. I uninstalled the heatsink to reseat the CPU and I noticed that the heatsink was never properly installed... I reseated the CPU and it still doesn't work. I also tried a few other things including unplugging peripherals and graphics card. Nothing worked. It looks like the CPU, motherboard, or the power supply became faulty. I unfortunately don't have any spare parts to test. I think most likely the CPU broke, but I also heard the CPU doesn't break that easily. My computer never shut down due to overheat, even under heavy load. Any idea where to go from here? Spec: CPU: Intel Core i5-6500 3.2GHz Quad-Core Motherboard: MSI H170A PC Mate ATX LGA1151 RAM: 4x4GB Kingston HyperX DDR4 Storage: Western Digital Caviar Blue 1TB 3.5" 7200RPM Power supply: Corsair CSM 650W 80+ Gold Graphics card: EVGA GeForce GTX 950 OS: Windows 10
  4. Well, after 4h of command line kongfu, I was able to make it to work, here is the summary of what I did: Debian installer, for some reason, isn't able to install a desktop environment for you, just skip that step, finish installing, and reboot. Log in as root, then add these to /etc/network/interfaces : auto wlan0 iface wlan0 inet dhcp wpa-ssid (put ssid here) wpa-psk (put password here) Then run ifup wlan0 to connect to Wi-Fi. Run apt update, then apt install gnome Press Super(or the Windows key)+F2, log in, mount installation USB to /media/cdrom0, enter the folder so it can't be unmounted. Go back with Super+F1 and wait for it to install. After that finishes, reboot, log-in, open a terminal, su, add this line to /etc/apt/sources.list : deb http://httpredir.debian.org/debian/ jessie main contrib non-free Also remove the cdrom line, we don't need that anymore. apt update, apt install firmware-linux-nonfree, and reboot. Most of the things should be working now, just some minor battery and Wi-Fi status weirdness along with some animation glitch (bad graphics chip driver?) I used the same USB drive, so I think Ubuntu is just not compatible with my hardware. Quite disappointed in the level of difficulty of installing a Linux distribution, I'd expect it to be more straight forward. Also, unlike many people said, X is noticeably slower than NT's kernel GUI. It does use significantly less RAM, but unless RAM is is the bottleneck, Windows 10 will not be slower than a Linux distro that has a desktop for daily tasks.
  5. OK, I tried Debian, it worked... except the desktop environment. I think it's a driver issue.
  6. Eh... That's a bit too complex. I'll try Debian and see if that works.
  7. My Internet is pretty trash until I can get my ISP to upgrade my router. It is currently only 2.4GHz which goes down whenever someone uses microwave oven.
  8. I'm not sure how to check that, and Rufus adds extra files to make it bootable, that might change the hash.
  9. I was expecting installation of Ubuntu to be pretty easy, apparently I'm wrong. The installation stops after this error: The computer is Asus K55N laptop. I checked the ISO hash, it matches the hash on the official website: http://releases.ubuntu.com/17.04/SHA256SUMS Any idea what could be the cause? I used Rufus 2.14 to create the boot media (onto an USB).
  10. @Wild Penquin You got a good point, I'll use command line utility for the prototype, it's just one file that needs to be replaced if we are switching to API. I see that the other project (Nvidiux) uses `nvidia-settings --query` to read information, so there might not be an API. Also, it would really only pull data once every few seconds, and I can make different monitors update at different time, it should be fine.
  11. That is interesting, I'll definitely look into Nvidiux. Thanks for the information Can you help me a bit on how to create profile scripts? GPUGraphicsClockOffset seem to take in an index at the end, which is the PowerMizer power level, what should I do? Once I know how to write the script, I can easily wrap it in a GUI The monitoring I want is icons on the top bar, not really graphs on the desktop. I do want to be able to get a nice graph when I need it, I want something that feels like this: http://canvasjs.com/editor/?id=http://canvasjs.com/example/gallery/dynamic/realtime_line/ Those desktops looks amazing, but I pretty much never look on my desktop so I don't know how useful that will be...
  12. That's still not good enough, I want multiple profiles with different overclocking/underclocking and fan curve that I can switch with 2 clicks. I also want GUI interface to modify each profile (and create new ones). Also, that doesn't look fancy, I want modern, animated, and interactive interface. Fanciness is less of a priority, and I'll do that last, but if we are going fancy that is not good enough, I want live graph controlled by sliders.
  13. Well, they might have some proprietary API, but since we don't have access to that, so I guess parsing command-line utility output is the only way to go. That might be "insane" but that's all we got now. The core communication code is subject to be replaced by something "sane", but the rest of the code can stay the same. Notes for myself: Interesting... But it only does half of what we need... Because I kind of want graphs on clockrate, temperature, VRAM usage, etc, I think we can just put a few other common sensors (CPU temp, RAM usage) in the list. I think Node.JS exposes some sensors, so it wouldn't be too hard. There must be some Node modules that help with common sensors too. What we really need is to be able to control and monitor the GPU.