Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux? |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
|
02-04-2023, 03:31 PM
|
#1
|
Member
Registered: Feb 2007
Location: Winnipeg, MB CAN
Distribution: LMDE, Ubuntu, Mint
Posts: 57
Rep:
|
Computer crashing after not using for two months
I have a second older desktop running Mint.
Asus M2A-VM mainboard
AMD Athlon 64x2 Dual core 4200+ 2200MHZ
512k x2
IDE Hard drive
DVD player/burner (SATA)
No wireless devices.
Believe it has 4 GB of RAM, 2 sticks ( Didn't record that)
Use on board graphics
I was away for 2 months and brought back with me a larger monitor, hooked it up and when I started the computer it loaded to the Mint start up page then froze. Second start up there was screen tearing on one side. Hooked up the monitor that was connected before and still no go, black screen. Now this computer worked fine with no issues prior to me being away running Mint 19.3 xfce. Searched on-line for possible solutions (exhausted that avenue) and this is what I have done so far in no particular order. On start-up Post beep can be heard.
Cleared RTC RAM, used the jumpers; Removed both RAM sticks cleaned and re-installed; Replaced the power supply with a working one, all fans are running; Replaced the CMOS battery; Updated the BIOS to 1603; Reinstalled Mint 19.3 from DVD, (erased drive).
When the computer freezes and it does so whenever not at any particular instance, the fans are all running, Num Lock works, mouse frozen and screen frozen, other keyboard keys don't work. Sometimes using the REISUB trick works other times not and the reset button on the case has to be pressed. I have tried to install Mint 20.0 however having issues with that now, freezes while installing from DVD. Noticed that errors come up about "ACPI AE not found", several lines of that although it doesn't stay on the screen long enough to view all. Research has indicated this is not a serious issue.
At one time I had HTOP running and visible when it crashed and can provide the details:
CPU 54.8%; MEM 15.3%; last item running - usr/lib/firefox/firefox; and then from the bars along the top left
1 98.1%
2 98.1%
Mem 1.31G
SWP 341M
I know information from various commands is helpful in viewing possible issues however I am not able to get the upgrade installed which is a problem on its on. As mentioned it freezes while installing the upgrade. The computer does not run hot so heat isn't an issue. I have a large case lots of room inside and all fans work. While I can't recall the exact temperatures, the CPU and MB are both running well under 40C which from what I have seen is very good. Checked the hard drive and while it is old, still indicated it was good even though there were some failings and old age. I am starting to think that the hard drive could be an issue but not certain of that since the crash comes when trying to install the upgraded version of Mint from DVD.
I don't want to spend a ton of money on this unit, it was a computer that was surplus after I upgraded and I have set it up with Linux and was excited about having a larger monitor for it only to now end up spending all my free time trying to figure out what the issue is. I find it odd that it worked fine before I went away. I am providing this information on my main computer so I am not able to cut and paste further details at this time. Should I be able to get the other one working to the point where I can copy results and provide them I will do so. I thought I would come here to see if someone has any ideas or suggestions I can look at. I hate to get rid of the computer, it worked, I spent some money on it,(a new PSU for the main computer and the used one into the problem computer) but don't want to upgrade it to the point of it being better than my main computer.
I thank all of you for looking at this and providing suggestions.
Last edited by TooTall; 02-04-2023 at 03:33 PM.
|
|
|
02-04-2023, 03:53 PM
|
#2
|
Member
Registered: Jan 2022
Location: Hanover, Germany
Distribution: Slackware
Posts: 305
Rep:
|
The Asus M2A-VM (socket AM2+) is quite old. Therefore a "switch to death" is possible. If you are quite lucky under the circumstances only onboard graphics or a memory module has died. - Insert an old PCIe x16 graphics card and try it again.
- Run memtest86+ to check both memory modules
|
|
|
02-04-2023, 06:07 PM
|
#3
|
LQ Guru
Registered: Apr 2010
Location: Continental USA
Distribution: Debian, Ubuntu, RedHat, DSL, Puppy, CentOS, Knoppix, Mint-DE, Sparky, VSIDO, tinycore, Q4OS, Manjaro
Posts: 6,055
|
I would unplug it, let it cool, open and check all connections. Focus on the cards (including memory) and making sure the sockets and connectors are clean, then seat them securely. In that two months some dust or corrosion may have settled into a bad place.
The vendor support site may have a guide to the meaning of the beep codes. If cleaning and reseating does not fix anything, this may guide you to the faulty hardware.
|
|
1 members found this post helpful.
|
02-04-2023, 06:14 PM
|
#4
|
Member
Registered: Feb 2007
Location: Winnipeg, MB CAN
Distribution: LMDE, Ubuntu, Mint
Posts: 57
Original Poster
Rep:
|
On board graphics is good. When I did have it running picture is fine. The PSU may have been an issue as it booted up fine after I changed out the PSU but something else is not working properly. How long should I run the memory test for?
The beep code is the normal motherboard post beep you get so the MB is working ok. I had to re adjust BIOS settings after clearing the CMOS with the jumpers. The mother board while it may be old is in good shape still and worked fine until I came back home.
I did re-open the case and made sure everything was seated properly.
|
|
|
02-04-2023, 07:35 PM
|
#5
|
Senior Member
Registered: Oct 2003
Location: Elgin,IL,USA
Distribution: KDE Neon
Posts: 1,244
|
Check the the capacitors for bulges or a rust like material on them. Capacitors should be flat on top and start to bulge as they fail, and when they leak it looks sort of like rust.
The voltage problems they cause as they fail can be very random.
|
|
|
02-04-2023, 07:58 PM
|
#6
|
LQ Veteran
Registered: Mar 2008
Location: Waaaaay out West Texas
Distribution: antiX 23, MX 23
Posts: 7,279
|
Check hard drive health
https://www.fosslinux.com/939/how-to...and-ubuntu.htm
I don't subject my ide gear like in the motorcle shop outdoors in a metal quonset hut to mint linux background processes running constantly on my old hard drives.
ran inxi -zv8 in rox terminal as sudo. My desktop after initial install. link Edit: click on small image to get full resolution.
Code:
System:
Kernel: 5.10.57-antix.1-amd64-smp arch: x86_64 bits: 64 compiler: gcc
v: 10.2.1 parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.57-antix.1-amd64-smp
root=UUID=12799d61-59de-4d35-b6f1-2fb049e9a814 ro quiet
Desktop: IceWM v: 3.0.0 dm: slimski v: 1.5.0
Distro: antiX-21_x64-full Grup Yorum 31 October 2021
base: Debian GNU/Linux 11 (bullseye)
Machine:
Type: Desktop System: Acer product: Aspire T180 v: R01-B3 serial: <filter>
Mobo: Acer model: EM61SM/EM61PM serial: N/A BIOS: Phoenix v: R01-B3
date: 02/07/2007
Battery:
Message: No system battery data found. Is one present?
Memory:
RAM: total: 2.67 GiB used: 1008.8 MiB (36.9%)
Array-1: capacity: 16 GiB slots: 4 EC: None max-module-size: 4 GiB
Device-1: A0 info: single-bank type: N/A size: 512 MiB speed: N/A
volts: N/A width (bits): data: 64 total: 64 manufacturer: N/A part-no: N/A
serial: N/A
Device-2: A1 info: single-bank type: N/A size: 512 MiB speed: N/A
volts: N/A width (bits): data: 64 total: 64 manufacturer: N/A part-no: N/A
serial: N/A
Device-3: A2 info: double-bank type: N/A size: 1024 MiB speed: N/A
volts: N/A width (bits): data: 64 total: 64 manufacturer: N/A part-no: N/A
serial: N/A
Device-4: A3 info: double-bank type: N/A size: 1024 MiB speed: N/A
volts: N/A width (bits): data: 64 total: 64 manufacturer: N/A part-no: N/A
serial: N/A
PCI Slots:
Slot: 1 type: PCI bits: 32 status: available length: long volts: 5.0
bus-ID: N/A
Slot: 2 type: PCI bits: 32 status: in use length: long volts: 5.0
bus-ID: N/A
Slot: 3 type: PCI bits: 32 status: in use length: long volts: 5.0
bus-ID: N/A
Slot: 4 type: PCIe bits: 32 status: in use length: long volts: 5.0
bus-ID: N/A
Slot: 5 type: PCIe bits: 32 status: in use length: long volts: 5.0
bus-ID: N/A
Slot: 6 type: PCIe bits: 32 status: in use length: long volts: 5.0
bus-ID: N/A
Slot: 0 type: PCI bits: 32 status: in use length: long volts: 5.0
bus-ID: N/A
CPU:
Info: model: AMD Athlon 64 3800+ socket: 940 (M2) note: check bits: 64
type: UP arch: K8 process: AMD 65-130nm family: 0xF (15)
model-id: 0x4F (79) stepping: 2 microcode: N/A
Topology: cpus: 1x cores: 1 smt: <unsupported> cache:
L1: 2x 128 KiB (256 KiB) desc: d-1x64 KiB; i-1x64 KiB
L2: 2x 512 KiB (1024 KiB) desc: 1x512 KiB
Speed (MHz): 2400 min/max: 1000/2400 base/boost: 2412/3000 scaling:
driver: powernow-k8 governor: performance volts: 1.4 V ext-clock: 201 MHz
core: 1: 2400 bogomips: 4821
Flags: 3dnow 3dnowext 3dnowprefetch apic clflush cmov cpuid cr8_legacy
cx16 cx8 de extapic extd_apicid fpu fxsr fxsr_opt lahf_lm lm mca mce mmx
mmxext msr mtrr nopl nx pae pat pge pni pse pse36 rdtscp rep_good sep sse
sse2 svm syscall tsc vme vmmcall
Vulnerabilities:
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass status: Not affected
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2
mitigation: Full AMD retpoline, STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: NVIDIA C61 [GeForce 6100 nForce 405] vendor: Elite Systems
driver: nvidiafb v: kernel alternate: nouveau non-free: series: 304.xx
status: legacy (EOL) last: release: 304.137 kernel: 4.13 xorg: 1.19
arch: Curie process: 90-130nm built: 2003-13 bus-ID: 00:0d.0
chip-ID: 10de:03d1 class-ID: 0300
Display: x11 server: X.Org v: 1.20.11 driver: X: loaded: fbdev,nouveau
unloaded: modesetting,vesa alternate: nv gpu: nvidiafb display-ID: :0.0
screens: 1
Screen-1: 0 s-res: 1600x900 s-dpi: 96 s-size: 423x238mm (16.65x9.37")
s-diag: 485mm (19.11")
Monitor-1: default res: 1600x900 hz: 60 size: N/A modes: N/A
OpenGL: renderer: llvmpipe (LLVM 11.0.1 128 bits) v: 4.5 Mesa 20.3.5
compat-v: 3.1 direct render: Yes
Audio:
Device-1: NVIDIA MCP61 High Definition Audio vendor: Elite Systems
driver: snd_hda_intel v: kernel bus-ID: 00:05.0 chip-ID: 10de:03f0
class-ID: 0403
Sound Server-1: ALSA v: k5.10.57-antix.1-amd64-smp running: yes
Network:
Device-1: Marvell 88E8056 PCI-E Gigabit Ethernet vendor: Elite Systems
driver: sky2 v: 1.30 pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: ac00
bus-ID: 03:00.0 chip-ID: 11ab:4364 class-ID: 0200
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
IP v4: <filter> scope: global broadcast: <filter>
IP v6: <filter> scope: link
WAN IP: <filter>
Bluetooth:
Message: No bluetooth data found.
Logical:
Message: No logical block device data found.
RAID:
Message: No RAID data found.
Drives:
Local Storage: total: 1.82 TiB used: 4.44 GiB (0.2%)
ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST2000DM001-1CH164
family: Barracuda 7200.14 (AF) size: 1.82 TiB block-size: physical: 4096 B
logical: 512 B sata: 3.1 speed: 3.0 Gb/s type: HDD rpm: 7200
serial: <filter> rev: CC27 temp: 42 C scheme: MBR
SMART: yes state: enabled health: PASSED on: 321d 7h cycles: 240
read: 855.5 GiB written: 1.7 TiB Pre-Fail: attribute: Spin_Retry_Count
value: 100 worst: 100 threshold: 97
Optical-1: /dev/sr0 vendor: HL-DT-ST model: DVD-RW_GSA-H41N rev: RA00
dev-links: cdrom,cdrw,dvd,dvdrw
Features: speed: 40 multisession: yes audio: yes dvd: yes
rw: cd-r,cd-rw,dvd-r state: running
Partition:
ID-1: / raw-size: 162.11 GiB size: 158.51 GiB (97.78%)
used: 4.44 GiB (2.8%) fs: ext4 block-size: 4096 B dev: /dev/sda2
maj-min: 8:2 label: rootantiX21
uuid: 12799d61-59de-4d35-b6f1-2fb049e9a814
Swap:
Kernel: swappiness: 10 (default 60) cache-pressure: 50 (default 100)
ID-1: swap-1 type: partition size: 39.06 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/sda1 maj-min: 8:1 label: N/A
uuid: fa6b228c-d778-418b-bacd-b73f51d4da32
Unmounted:
ID-1: /dev/sda4 maj-min: 8:4 size: 1 KiB fs: N/A label: N/A uuid: N/A
ID-2: /dev/sda5 maj-min: 8:5 size: 830.92 GiB fs: ext3 label: /data1
uuid: 28035362-9082-4272-91da-5eb5eb9d0e20
ID-3: /dev/sda6 maj-min: 8:6 size: 830.92 GiB fs: ext4 label: /data2
uuid: 43fa0766-2bd8-4235-a7e4-1cc7b50fc89b
USB:
Hub-1: 1-0:1 info: Full speed or root hub ports: 8 rev: 2.0 speed: 480 Mb/s
chip-ID: 1d6b:0002 class-ID: 0900
Hub-2: 2-0:1 info: Full speed or root hub ports: 8 rev: 1.1
speed: 12 Mb/s chip-ID: 1d6b:0001 class-ID: 0900
Device-1: 2-8:2 info: Alcor Micro 8-in-1 Media Card Reader
type: Mass Storage driver: usb-storage interfaces: 1 rev: 1.1
speed: 12 Mb/s power: 100mA chip-ID: 058f:9360 class-ID: 0806
serial: <filter>
Sensors:
System Temperatures: cpu: 48.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos:
Packages: apt: 1575 lib: 747
Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://mirrors.rit.edu/mxlinux/mx-packages/antix/bullseye bullseye main nosystemd nonfree
Active apt repos in: /etc/apt/sources.list.d/bullseye-backports.list
1: deb http://deb.debian.org/debian bullseye-backports main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://ftp.us.debian.org/debian/ bullseye-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://ftp.us.debian.org/debian/ bullseye main contrib non-free
2: deb http://security.debian.org/ bullseye-security main contrib non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Processes:
CPU top: 5 of 130
1: cpu: 29.6% command: firefox-esr pid: 7532 mem: 521.2 MiB (19.0%)
2: cpu: 11.9% command: firefox-esr pid: 7674 mem: 202.5 MiB (7.3%)
3: cpu: 4.0% command: xorg pid: 6399 mem: 97.0 MiB (3.5%)
4: cpu: 3.1% command: sudo pid: 10803 mem: 4.81 MiB (0.1%)
5: cpu: 1.7% command: firefox-esr pid: 7651 mem: 168.7 MiB (6.1%)
Memory top: 5 of 130
1: mem: 521.2 MiB (19.0%) command: firefox-esr pid: 7532 cpu: 29.6%
2: mem: 202.5 MiB (7.3%) command: firefox-esr pid: 7674 cpu: 11.9%
3: mem: 168.7 MiB (6.1%) command: firefox-esr pid: 7651 cpu: 1.7%
4: mem: 114.4 MiB (4.1%) command: firefox-esr pid: 7607 cpu: 1.1%
5: mem: 97.0 MiB (3.5%) command: xorg pid: 6399 cpu: 4.0%
Info:
Processes: 130 Uptime: 45m wakeups: 1 Init: SysVinit v: 2.96 runlevel: 5
default: 5 tool: service Compilers: gcc: 10.2.1 alt: 10 Shell: Bash (sudo)
v: 5.1.4 running-in: roxterm inxi: 3.3.19
Good luck. By the way. Mint has the inxi command also.
https://community.linuxmint.com/soft...iew/lm-sensors
Last edited by rokytnji; 02-04-2023 at 08:06 PM.
|
|
|
02-04-2023, 08:34 PM
|
#7
|
LQ Veteran
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 21,314
|
Quote:
Originally Posted by TooTall
I don't want to spend a ton of money on this unit, it was a computer that was surplus after I upgraded and I have set it up with Linux and was excited about having a larger monitor for it only to now end up spending all my free time trying to figure out what the issue is.
|
Pull the disk out and check it in an external housing. If you have to install it (internally) in another computer.
Then make the call on whether it's worthwhile pursuing problems. Me, I'd ditch the box and just keep the disk if it's ok.
|
|
|
02-04-2023, 11:25 PM
|
#8
|
LQ Guru
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE 24/7; Debian, Knoppix, Mageia, Fedora, OS/2, others
Posts: 6,302
|
Very high probability uteck's response is on point. That motherboard was made when when manufacturer's were rampantly supplied with capacitors destined to fail prematurely. Bad caps put Abit and other manufacturers out of business. It caused Dell and HP to replace many motherboards even after warranty expiration. If the largest caps were made by OST, they are liable to fail without any external leaking or bulging to make failing evident.
|
|
|
02-05-2023, 06:06 AM
|
#9
|
Member
Registered: Jan 2022
Location: Hanover, Germany
Distribution: Slackware
Posts: 305
Rep:
|
Quote:
Originally Posted by TooTall
How long should I run the memory test for?
|
Three passes without errors should be enough.
|
|
|
02-05-2023, 07:34 AM
|
#10
|
Member
Registered: Feb 2007
Location: Winnipeg, MB CAN
Distribution: LMDE, Ubuntu, Mint
Posts: 57
Original Poster
Rep:
|
I'm running the memory test now from the DVD and will let it run for a few hours. I noticed that it indicates the following and not sure if this is anything as I haven't noticed before:
Slot 0 -1024 MB DDR2666-Kingston 9905316-005-A0415
Slot 1 -1024
The second line is blank.
I'll report back after the test runs and I have had an opportunity to view the MB up close.
|
|
|
02-05-2023, 01:09 PM
|
#11
|
Member
Registered: Feb 2007
Location: Winnipeg, MB CAN
Distribution: LMDE, Ubuntu, Mint
Posts: 57
Original Poster
Rep:
|
Ram memory test for 4 hours 20 minutes, no errors found or reported.
Going to check capacitors next with magnifying glass.
|
|
|
02-05-2023, 01:22 PM
|
#12
|
LQ Guru
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE 24/7; Debian, Knoppix, Mageia, Fedora, OS/2, others
Posts: 6,302
|
If your replacement PSU was more than 3 years old, its caps should be checked too. Bad caps in a PSU can cause invisible motherboard damage.
|
|
|
02-05-2023, 01:35 PM
|
#13
|
LQ Guru
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 17,212
|
Two months away, and you're in Canada... I'd be thinking of damp.
When I was fixing hardware I used to keep a glass fibre brush from RS. It was adjustable and would clean up contacts without leaving residue. I made a lot of money by cleaning things like DIMM edges where they sit into sockets, and the sockets too.
Listen for capacitor noise. degraded electrolyte will leak current, and put spikes on a voltage line. Getting the offending capacitor warm often fixes it, but replacing is better.
Another area that hasn't been mentioned is power supply plugs. Sometimes reseating them helps. I wouldn't go with the 'dying part' approach of many posters, because the thing boots, doesn't it? I would check individual voltage on each power line if you can.
If you're still in trouble, think about socketed chips, if you can safely move them. And if it's frozen, get it warm!
|
|
|
02-05-2023, 04:09 PM
|
#14
|
Member
Registered: May 2022
Location: New Mexico, USA
Distribution: Slackware 15.0 & 64 bit-current, antiX
Posts: 118
Rep:
|
Does it run a live ISO of linux good, might be the HDD getting errors as ROKY said. I
recommend a base or full antiX 19 or 21 iso for that quick test. If it boots and runs.
Last edited by linuxdaddy; 02-05-2023 at 04:12 PM.
Reason: added to it
|
|
|
02-05-2023, 05:35 PM
|
#15
|
Member
Registered: Feb 2007
Location: Winnipeg, MB CAN
Distribution: LMDE, Ubuntu, Mint
Posts: 57
Original Poster
Rep:
|
Quote:
Originally Posted by mrmazda
If your replacement PSU was more than 3 years old, its caps should be checked too. Bad caps in a PSU can cause invisible motherboard damage.
|
I purchased a new PSU for my main computer and put the PSU I removed from the main one and put it in the one that is in question. I know it works and nothing wrong with that PSU.
|
|
|
All times are GMT -5. The time now is 02:44 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|