Recommended Posts

So I'm re-building an old emachines I was given, and I have a couple of questions.

It has 1 GB of RAM and an Intel Pentium 4 @ 3.00 Ghz that reads "EM64T Capable". I installed the 64 bit version of Ubuntu 12.10, but it seems to be "really" sluggish at times, particularly if I try watching a full screen flash video from pretty much any website. I see in the BIOS that Hyperthreading is available and enabled.

Anyway, I'm wondering if the 32 bit version would offer better performance, or if it wouldn't make a difference since this processor is apparently 64 bit. It's an emachines W3615 that was given to me by a neighbor who didn't want it, so I replaced the CPU fan because the old one had worn out and was rattling around inside its housing, put some fresh thermal paste on it and cleaned it out, and I'm giving it to my mother-in-law to use as a general web browsing computer, but it's performance is not all that pleasing at times.

I guess my question is, given the information above, what could I do to improve performance of Ubuntu? I'm currently using Unity, but in my experience using 12.04 a while back, switching from Unity to Ubuntu's version of Gnome 2 didn't really make any difference as far as system performance, so I'm hesitant to start messing around with other desktop environments.

Another question. I've applied fresh thermal paste and put a new fan on top of the heat-sink blowing down. When I first started the computer the CPU was at around 52 degrees celsius according to the "Hardware Monitoring" section in the BIOS. That was after having been shut off for a few days and having just had the thermal paste and heat-sink re-applied, so that was as cold as it was going to get. I booted Ubuntu, played a few high def videos on YouTube to get the CPU cranking and the fan speed has increased, then I rebooted to get into the BIOS and look at the temps. (lmsensors says there are no sensors installed that it supports) I've had it sitting there for about 10 minutes now and it has hung right around 90 degrees celsius, meanwhile my own personal desktop is hanging out at a cool 18 degrees celsius(also running Ubuntu 12.10 64 bit). It's worth mentioning I guess that the CPU fan came out of a Dell PC and had a different wiring configuration so I had to splice the connector from the old fan onto the new fan since the new one wouldn't plug onto the connector on the motherboard. The connections are insulated from each other and the fan is running fine and even changes speed when the CPU is under load, so I don't think that's the issue, and the wires on the two fans were all the same color and the fans were the same size, they just had different connectors so I had to swap them out.

Link to comment
https://www.neowin.net/forum/topic/1135180-high-temps-on-an-old-pc/
Share on other sites

Tho I have no experience in ubuntu, my guess, and this is just a guess would be yes.

(Even if there's a remotely tiny chance that the 32 bit OS has that similarity with windows, as in 32bit can use fewer resources etc...)

And for the temp issue, hm... you got me, usually vaccuming out the fins on the heatsink, new paste (when needed) and the occasional repair or replacement of fan is sufficient to cool your cpu

if your base has a removable side panel, try running it without the panel to see if it's still hitting those temps?

(that's all I had dude, sorry)

Flash always performs poorly, but it sounds exceptionally bad in your case. As far as I know, it sounds like you have done everything right with the hardware. I used to have an EM64T capable Pentium 4 (Prescott) and it always performed poorly running a 64-bit OS. I recommend that you try installing 32-bit Ubuntu 12.10, and see how much of a difference that makes.

Also, you may want to try installing the firmware for your video card (if its an NVIDIA card using the open-source nouveau driver) and the OpenGL 3D acceleration libraries.


sudo apt-get install linux-firmware linux-firmware-nonfree nouveau-firmware libgl1-mesa-glx libgl1-mesa-dri-experimental
[/CODE]

Just to elaborate on my question,

I use to have an IBM Thinkpad designed to run XP - I installed Ubuntu and I noticed the temperature was going wild. IF I watched anything with Flash the fans would spin up, I never diagnosed this as the machine was old and needed replacing.

(P.s. I will provide more feedback IF the 32-bit OS does not resolve the issue.)

Just to elaborate on my question,

I use to have an IBM Thinkpad designed to run XP - I installed Ubuntu and I noticed the temperature was going wild. IF I watched anything with Flash the fans would spin up, I never diagnosed this as the machine was old and needed replacing.

(P.s. I will provide more feedback IF the 32-bit OS does not resolve the issue.)

Check BIOS for fan control options. I've noted that many of the control packages for chipset drivers, etc, are not as well (if at all) configured to run *nix operating systems. Usually, especially on a desktop, you can disable fan control (sometimes referred to as "Quiet Mode") in bios and let it run at a set RPM.

If I had to guess, I'd say your chipset drivers for ubuntu aren't signaling bios to scale fan/air movement appropriately based on system load. Passing this control back to bios or disabling it entirely should show a marked improvement in temperature control.

Check BIOS for fan control options. I've noted that many of the control packages for chipset drivers, etc, are not as well (if at all) configured to run *nix operating systems. Usually, especially on a desktop, you can disable fan control (sometimes referred to as "Quiet Mode") in bios and let it run at a set RPM.

If I had to guess, I'd say your chipset drivers for ubuntu aren't signaling bios to scale fan/air movement appropriately based on system load. Passing this control back to bios or disabling it entirely should show a marked improvement in temperature control.

Thanks - this machine, however, has not been in use for over 5 years. I only needed the machine temporarily: IF time = money, my money was best spent on upgrading anyways.

This topic is now closed to further replies.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      592
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!