Skip to main content

Topic: Tips for computer builders (Read 958 times)

  • ersi
  • [*][*][*][*][*]
Tips for computer builders
This is my advice to first-time computer builder: DON'T! The process is not easy. The components may be faulty. Accidents happen. And you don't have enough tools to find out where the problem is.

Tutorials on youtube by professionals don't help. Professionals don't get into trouble. Noobs do. Professionals have mostly forgotten how it was to be a noob. Instead, they give you the false impression that the process is easy and fun like a game of Lego with a screwdriver.

Many video tutorials tell you all you need is a screwdriver and the computer components. This is wrong. You will need at least

- two sizes of screwdrivers (preferably with magnetic tips), if your box is anything less than huge,
- pliers (very tiny pliers to pick fallen things up from tight places if your screwdriver doesn't have a magnetic tip),
- cutters (not scissors, but specialist cutters in order to avoid damaging the bundles of wires when you cut them open),
- alcohol for cleaning,
- clean (dustfree) wiping cloth,
- thermal paste (even if the stock CPU cooler has thermal paste preapplied, be ready to install the CPU multiple times, so you will have to clean the parts and apply your own thermal paste),
- a small flashlight to examine things in the case,
- tons of patience and time,

and it will still not be enough. Something will go wrong. They tell you it's max two hours of assembling things. No. It will be weeks of troubleshooting, months if you have nobody to help you.

More thorough video tutorials by professionals tell you to start by choosing the "right" case. This is a strong clue that we are dealing with someone who has forgotten real-life situations, who has lost the capacity to be useful to a first-timer. People in the real world actually already have a computer and are looking for a way to reuse some parts from there to spare money - at least the case should be reusable, if not anything else. Computer cases have been most resistant to change and innovation. There is no "right" case. There is the case you have wherein you want to build a new computer. If you as a PC build first-timer need to buy a new case, then you should not be doing this. You should take a very good look into your old case first and find a way to reuse it (and maybe a thing or two in it), but even so you will remain a noob. You won't become intermediate by staring into a box.

There is no gratification to be had from building a computer. It is not cheaper or better. It is not cheaper because you cannot afford to cheap out on any of the components. You may think you are putting together something precisely for your own needs, something that is best for you, but in truth you don't know your needs. You certainly don't know which parts correspond to your supposed needs, because you are noob. You think your idea has hatched long enough, for months even, but this is a process where no amount of planning will be enough. You will end up in frustration and overpaying on top of that.

Specifications and manuals don't help. They only tell you what things should fit together, but if the things don't fit together in reality, you are out of luck. And there will surely be some things that don't fit together, unbeknownst to you, because some parts require a surprising amount of force to connect, while the components mostly are very fragile and should be treated gently. As a noob, you will never know if you did it right. More precisely, you cannot be sure what exactly you did wrong. Either you didn't press strong enough where needed or you broke or bent something without noticing or, even if you apply the right force at the right times, the surface you work on isn't quite right. And you don't have enough tools to figure out later where the problem lies.

Something will definitely go wrong along the way. There's no escape from it. You will need someone to share the responsibility with. First-timers should be building under expert guidance the first twelve times or so. Otherwise you will be like me, like many other first-timers who did it wrong. They don't get likes on youtube, they usually don't share their stories, so you don't know about them.

Yesterday I tried to assemble my first PC by myself. The motherboard manual that I got doesn't contain anything about troubleshooting. They expect everything to work. A completely unjustified expectation.

I assembled enough things outside the case - CPU onto motherboard, stock cooler on top of it, RAM into its place, PSU connected at the necessary places. Then, outside the case, I attached the monitor and keyboard to the mobo and the PSU cable to the wall and switched the thing on. Fans spin, mobo lights up, cool. But the monitor has no signal. I thought it was something temporary. I disconnected the power and removed the power cable. I put everything into the case, added a DVD drive and a harddrive, reattached the power cable and switched the thing on again. The DVD drive opens and closes. There seems to be power in the harddrive too, so these parts are getting electricity. And the fans are spinning. The other side however, HDMI and USB and other holes, they don't get anything.

Googling I found out that this is actually a common noob problem. Noobs should not be building computers. I tried some advices. I tried removing and reinstalling RAM. I tried booting without RAM. This is the best troubleshooting list I came across http://www.mysuperpc.com/build/pc_first_boot_common_problems.shtml

They say the mobo should beep when you try to boot it up. No, it doesn't. I understand that this is a basic thing, to have a feedback signal whether things are right or wrong, but looks like modern motherboards, certainly the one I have, don't have this basic thing. The manual does not mention it nor indicate where such a beeper could be attached. Also, the mobo lights up in cool colours when turned on, but there's no indicator light to show whether the mobo recognises RAM or such. Pointless.

Basically, I tried everything short of removing and reinstalling the CPU. My next step will be to call someone who has actually assembled computers and who has an electrometre.

Let no one else undertake this useless and frustrating experiment.

  • ersi
  • [*][*][*][*][*]
Re: Tips for computer builders
Reply #50
If a distro doesn't do something similar I'd probably avoid it as deeply user-unfriendly. We're talking hundreds of kilobytes here, megabytes at most.
Sure, if your user experience involves graphics cards. Mine didn't until now.

Besides, Manjaro does do something similar. I had the vesa driver. The boot got stuck, as far as I could see, at NetworkManager, which should not be related, but occurred specifically when I inserted/removed the graphics card. I reinstalled because it was the fastest option I could figure out, I had the settings backed up already, and I had to run somewhere else the same evening.

There are very different Manjaros and, for this particular system, I had gone through, for example, changing the init from systemd to openrc, just for fun. I cannot generalise that Manjaro always fails when you add/change the graphics card. This is my first experience ever with a graphics card. I did no research prior (except checking that the card fits the motherboard), no research afterwards, and the whole operation took an hour. Good enough, I'd say, even though of course I'd want it to be smoother. For that I need more experience and research to know what precautions to take.

  • Frenzie
  • [*][*][*][*][*]
  • Administrator
Re: Tips for computer builders
Reply #51
It always involves GPUs in the sense that you want things to be painted on the screen smoothly. Without the right drivers it can take seconds for a window to show up.