An Asus FX553VD (running on GL553VD mb) not completing the boot anymore

 The adventure began when my sister gave me her notebook PC telling that she could not complete boot into her Windows 10 OS. The notebook PC was ASUS FX553VD on GL553VD mb, with 8 GB DDR4 RAM, i7-7700HQ cpu, NVIDIA GTX1050.

That was right, the PC every time shut down during boot process. I planned to take out the SSD, the HDD, and try to boot from Live Linux USBs.

The distributions I tried were a lot (Ubuntu, Debian, Slackware, Fedora, Solus, etc.). The ending was the same, after a couple of messages related to ACPI, the PC shut down. First of all, I updated the BIOS to version 308. Nothing changed. I then had suspicion about the BIOS chip, ACPI tables, TPM module, RAM module. I planned to boot Live Linux USBs with "kernel boot parameters". The very first successful result was with "nolapic" parameter. It ended with only one working cpu core. Also, "nolapic" parameter was not a desired parameter for me. I tried other parameters, "acpi=off" was also successful also with only one core activity. I preferred to continue with "acpi=off". I moved an SSD from another PC of mine to this notebook PC and added "acpi=off" to "grub". Yes, I had ASUS FX553VD running but with only one core and without ACPI abilities. I prioritize to have more number of cores to be active. I tried "acpi=ht" instead of "acpi=off" to disable all ACPI abilities except hyperthreading, but the situation was unsuccessful ending during boot process with shut down (this might be the first clue for me, but I missed).

I also tried BSD derivatives. Most recent FreeBSD versions (currently supported versions) shut down during boot. NetBSD-10RCs could boot, but they were crashing while opening a browser, etc.

This week (mid March, 2024), I saw a Debian based distro with Openbox with the latest kernel, and wanted to give it a try. It was "Dr.Parted". It also shut down during boot. The "failsafe boot" option was there and I tried. I had the PC running again. I digged into the "kernel boot parameters" found in the "failsafe boot" lines. They were :
"components"
"noeject"
"memtest"
"noapic"
"noapm"
"nodma"
"nomce"
"nolapic"
"nomodeset"
"nosmp"
"nosplash"
"vga=normal"

I figured out that the success to boot came from "nosmp" parameter in addition to parameters I found already.

"nosmp" parameter was disabling "symmetric multiprocessing". This caused me to think about the cpu, maybe for the first time, seriously. I had no great suspicion about a cpu failure before.

I wanted to boot with "maxcpus=1" parameter instead of "nosmp" to gradualy increase active core numbers.
"maxcpus=1" parameter was successful, without suspicion.
"maxcpus=2" parameter also ended with success; I, at least, had two cores then.
"maxcpus=3" parameter ended with failure (shutdown during boot). The third core was failing. What about the fourth core ?

My plan to boot with two cores and to make the remaining cores active inside OS was on the way, then.

I booted with two cores, they were marked as "cpu 0" and "cpu 1". When I wanted to make "cpu 2" online, the OS crashed (third core, as I found previously). Another try with "cpu 3" in addition to "cpu 0" and "cpu 1" also ended with crash. Yes, the fourth core was failing, too. Making "cpu 6" online or making "cpu 7" online resulted in crashes also (hyperthreading related to third core and fourth core). I made "cpu 4" and "cpu 5" online (hyperthreading related to first two cores). It was showing 2 cores, 4 threads.

At last, my search ended with finding the defective part, cpu.
I can run Ubuntu now. But with 2 cores instead of 4, and with 4 threads instead of 8, being better than running with only one core. The other positive point is that I have all the ACPI abilities in this situation.

What I learned is to have suspicion about the cpu although reported very rarely.

Booting a second HDD containing Windows 10 within the first HDD booted from Ubuntu 20.04 (VMware example)

As a Ubuntu user, I prefer all my computers stand on this OS. However, in the school environment, there are some moments forcing me use Windows-based OSes. For instance, in order to use licensed copies of SPSS, I have an HDD running Windows 10.

My present example is about a laptop (an ASUS G750JX, 24 GB RAM, i7-4700HQ cpu, two HDD bays). The first bay is occupied by an SSD running Ubuntu 20.04. In the second bay, another SSD is ready to run Windows 10. Most of the time, it is booted from the first SSD.
Recently, I asked myself whether I can boot the second SSD within running Ubuntu or not. The answer might be VMware. After some work (especially in order not to lose any data from the second disk), I managed to boot the second disk.

All processes are in the first disk (Ubuntu). I installed VMware. When I was in the step to bind "a physical disk", the SSD cannot be selected. The reason was that I didn't have "root" permissions to do such a thing. My solution was to run VMware as "root". In a terminal window I typed "sudo vmplayer". This meant that I started VMware as "root".
I choosed "create a new virtual machine".
I choosed "I will install the operating system later".
I choosed the guest operating system as Windows 10 64-bit.
I did my settings next (RAM, cpu, etc).
Later, the folders and files were created under "/root" folder.
My virtual machine was made visible in VMware, then.
I choosed "edit virtual machine settings", then added "Hard Disk" ("use a physical disk" in the following steps), I pointed to my Windows disk, and finished.

I choosed to run the virtual machine. It was happy to see it ran.

Ubuntu on ARM : Two examples of mine

After succeeding to run a graphical environment of Ubuntu on iMac G3, I felt a deep desire to test Linux on SbC having an ARM processor.

My first SbC was a "Cubietruck" (aka Cubieboard-3) which was released in Autumn 2013. It was on my hands on November 2013. It had an Allwinner A20 cpu (dual-core). The operating systems I tried were Lubuntu, Fedora and Cubian. Later, Ubuntu was also available. "Cubietruck" had some superiorities compared to other SbCs (VGA or HDMI as video output; NAND or micro-SD as boot media; ability to run SATA drive; wi-fi and Bluetooth and infrared availability; digital audio output through optic port). Yes, it's not the most powerful SbC, but as a personal computer for browsing web pages or for multimedia purposes or for office applications, it was found sufficient. Now, the operating system runs on a SATA-HDD (significantly faster than NAND or micro-SD).

In the fifth month of my first SbC experience, I wished to try another SbC, having a more powerful processor. My search resulted in "ODROID-U3". The processor was very powerful compared to "Cubietruck". It was an Exynos 4412 (quad-core at 1.7 GHz). It had inferiorities compared to "Cubietruck" (only HDMI; micro-SD or eMMC as boot media; no SATA support; no wi-fi; no Bluetooth). But it was really an acceptable choice for me who wanted to try it as a replacement for x86-based computers with very low energy consumption and portability. Needless to say that "ODROID-U3" was a very powerful device. I added a wi-fi dongle (to one of the three USB-2.0 ports). Ubuntu was installed and run (now 14.04). It had a great community and also a monthly magazine was available (http://magazine.odroid.com). I have to express that my home computer is this "ODROID-U3" now (using it for adding this post also). I also want to tell that the operating system is running on an USB-HDD (thanks to ODROID magazines).

To see a very low power consumption (running with an adapter 5V DC and 2 A max) while performing everyday computing tasks kept me a little bit away from my old PCs.

Ubuntu 12.04 on iMac G3 350MHz PPC750 512MB RAM

Situation :

- An iMac G3 350MHz PPC750 running Mac OS 9 with old browsers (not upgradeable) limited the ability to search the internet

- 64MB RAM was enough for running Mac OS 9, but if using Mac OS X 10.4 (latest Mac OS X for iMac G3) would be the case, additional RAM was necessary

- In search of recent software, Mac OS X 10.4, being at least 4 years old, would not be the first choice, and although some work would probably be necessary, Ubuntu 12.04 was thought to be tried



Homework :

- Additional RAM (a 512MB SDRAM was found and mounted)

- Ubuntu 12.04 "mini.iso" for PowerPC architecture (downloaded and burned to CD)

- Finding and reading documents about probable problems and their solutions (lots of documents were downloaded and read)



What was done :

- while pressing the power button, CD was inserted, "C" key was pressed and kept still until iMac started to read from CD and a black-white text screen was visible
(if the keyboard layout is not QWERTY, the key to be pressed may vary, being the third from left in the lowest row)

- a few seconds after the first screen, a second screen where the default selection was said to be "install" was visible, and "cli" was typed and "return" key was pressed
("cli" is the short form of "command line install")
(if the keyboard layout is not QWERTY, the keys to be pressed to type "cli" may vary, "c" being the third from left in the lowest row, "l" being the ninth from left in the middle row and "i" being the eighth from left in the upper row)


- "mini.iso" CD went on, asking questions about language, region, keyboard layout, etc., then partitioning, and so on
(needless to say that installation in such a system through the network lasted more than one hour)

- when prompted, "no automatic updates" was selected

- installation was completed and iMac went for a reboot
(time to take the CD out)

- iMac booted from the hard disk drive and a login screen was there to run Ubuntu 12.04 in the command line

- login was completed and "xinit" package was installed with the command
"sudo apt-get install xinit"

- the command "nano" was typed and entered to write an "xorg.conf" file;
the "xorg.conf" file was copied to "/etc/X11" folder with root privilages
(the "xorg.conf" file is as follows)
Section "Device"
    Identifier "ATI Technologies Inc Rage 128"
    Driver "r128"
    Option "NoInt10" "true"
    Option "CCEusecTimeout" "100000"
    Option "UseFBDev" "false"
    Option "XAANoOffscreenPixmaps"
    Option "SWcursor" "true"
EndSection

Section "Module"
    Load "i2c"
    Load "ddc"
    Load "dri"
    Load "dri2"
    Load "record"
    Load "extmod"
    Load "freetype"
    Load "type1"
EndSection

Section "DRI"
    Mode 0666
EndSection

Section "Monitor"
    Identifier "iMac"
    VendorName "iMac"
    ModelName "Monitor Model"
    Option "DPMS"
    HorizSync 58-62
    VertRefresh 75-117
EndSection

Section "Screen"
    Identifier "Default Screen"
    Device "ATI Technologies Inc Rage 128"
    Monitor "iMac"
    DefaultDepth 24
    Subsection "Display"
        Depth 16
        Modes "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection "Display"
        Depth 24
        Modes "1024x768" "800x600" "640x480"
    EndSubSection
EndSection

- the command "xinit" was typed and entered; "X" screen was there
(time to select window manager, display manager, browser, ...)



What I chose :

- "fluxbox" as window manager (sudo apt-get install fluxbox)
"lxde" may be a good choice also (sudo apt-get install lxde),
but not "lubuntu-desktop" (sudo apt-get install lubuntu-desktop)

- "slim" as display manager
(if the choice will be "lxde", its own display manager -lxdm- will be there, making this step unnecessary)

- "dillo" and "firefox" as browsers

- "mc" as file manager (not a graphical one)
(if the choice will be "lxde", its own file manager -pcmanfm- will be there, making this step unnecessary)

- "hardinfo" to view system information and details

- "ssh" to connect to and to be connected by other computers

- "remmina" to connect to desktops of other computers



Feelings in short :

- Recent operating system with recent browser software running in a computer this old made us happy

for Hasan Ali Yücel

 

first of all

"... searching curiously, creating time for hobbies, never forgetting the primary goal -learning, ..."