- This topic has 21 replies, 8 voices, and was last updated Jan 30-5:14 pm by Brian Masinick.
-
Posts
-
PPC
I don’t really understand the problems with this desktop computer – I was sad that the boot process of antiX 19 I had on this drive (I’m reusing the same hd from the previous dead computer) did not work- it stops in mid boot process, but since it’s a different motherboard, cpu and video card, I assume that the previous OS could not handle the change, and I half expected having to reinstall.
This log-in problem I assume happens because, for some strange reason, slimski fails to use any default user correctly – when autologing, it’s like the OS isn’t loaded correctly- it displays the desktop but it’s like antiX does not know what user is the system and refuses to launch anything other than the switch desktop commands… If only using a default user, but not auto login, it’s like initially slimski tries to log me in, fails, because of the problem with the default username, and restarts correctly a second time, then it’s able to process the default user and correctly accepts it’s user’s password, loging the user into a fully usable desktop…
I’m almost sure that’s the problem, but I have no ideas why this happens and how to solve it.
Maybe explaning the situation like this can lead to a solution… but I’m already setting up my stuff in this very nice work desktop pc!P.
- This reply was modified 3 months, 2 weeks ago by PPC.
Dave
Corrupted sectors on the hard drive possibly?
What is the output of smartctl -a /dev/sda?Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown
Hi, Dave, thanks for looking into my strange “problem”!
Like I said, I assume this is some kind of interaction with this hardware and slimski, not an hardware failure.
I installed antiX 21 once, on one partition, formatted as btrfs and then antiX 22, in the same partition, formatted as ext4, and then another partition formatted as ext4 (using another partition as home, formatted as ext4), and I always have the same problem – configuring a default username under slimski results in, after the first log in screen I see the terminal for a second or so, then I get back to the login screen. If I enter my password on that second login screen, I log into a normal desktop.
If I configure autologin in slimski, only the menu works, but nothing gets launched (except tint2, if it’s in the startup file, not even conky loads). the only thing that works it’s the menu that allows me to select desktops (I did not try every single entry on the menu, but I assume nothing other than that works). I can select any other desktop or the very same desktop I’m in, and then that desktop works fine.
I tried a bunch of desktops: icewm, fluxbox, jwm, zzz-icewm, min-icewm. Both problems occour (autologin and selecting default username, in slimski).As you asked, result of sudo smartctl -a /dev/sda:
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.10.142-antix.2-amd64-smp] (local build) Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Blue (SATA) Device Model: WDC WD3200AAKS-00V1A0 Serial Number: WD-WCAWF2820576 LU WWN Device Id: 5 0014ee 1ad1c3e33 Firmware Version: 05.01D05 User Capacity: 320,072,933,376 bytes [320 GB] Sector Size: 512 bytes logical/physical Device is: In smartctl database 7.3/5319 ATA Version is: ATA8-ACS (minor revision not indicated) SATA Version is: SATA 2.6, 3.0 Gb/s Local Time is: Mon Jan 30 14:39:43 2023 WET SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 6000) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 73) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x303f) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 146 143 021 Pre-fail Always - 3666 4 Start_Stop_Count 0x0032 095 095 000 Old_age Always - 5707 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 058 058 000 Old_age Always - 31096 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 095 095 000 Old_age Always - 5668 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 279 193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 5427 194 Temperature_Celsius 0x0022 124 093 000 Old_age Always - 19 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.Edit: I did not like those “pre-fails”, but I assume they don’t cause this problem…
- This reply was modified 3 months, 1 week ago by PPC.
anticapitalista
To be sure it is slimski causing the issue, try installing an antiX that shipped with slim and see if it all works ok eg antiX-19.5
Alternatively, on antiX-22 try installing another login manager ie slim or even lightdm, lxdm.I’m inclined to agree with Dave that it is a hardware problem.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
caprea
Hi PPC, there is /var/log/slimski.log. It might gives a hint.I read the whole thread but couldn’t find it mentioned.
Did you already try to create a completely fresh usb-live-stick of antiX21 or 22, best from new download, if the problem persists?@anticapitalista – I tried antiX 19.5, 64bits, full. At first boot from the LIve USB, it failed to show the desktop wallpaper. The menu showed up but did not react and left it’s fantom image in the wallpaperless desktop (as it’s usual, according to my experience, when antiX is not showing a wallpaper). After a reboot into live mode, antiX showed the login screen and from there I accessed the desktop and installed to disk, seting up autologin.
After installation I get a “Failed to execute login command” and then a loop of login screens, with my username, that, when I enter my password, just result in getting the same login screen again. Computer is unusable in this state. I’m downloading antiX 22 runit 64bits full, will install it and just be happy entering my username and password…P.
Edit: I just installed antiX 22, full, 64bits, runit – same problem as antiX 21 and 22 non runint. Fortunately, I edited slimski local config file and booted to a normal login screen, asking for my username and password. I’m updating it as I write this – that process is what wastes more time. I do think that there’s some kind of conflic between this hardware and all antiX versions’s login screens- weird, I know, but I tried 4 different versions of antiX, on different partitions, formatted differently and I always run into this problem. For now I have a fully working system, I just want to keep it for a couple of years more, or so!
Many thanks for all the advises, and input, but, except for some miraculous suggestion, I’ll just keep this pc as it is right now and count my blessings it works perfectly, once I’m logged in!- This reply was modified 3 months, 1 week ago by PPC.
Brian Masinick
I’m also inclined to think that this problem is at least partially related to hardware. PPC, if you can get any system running, regardless of what it is, try to run some hardware diagnostics, or if the on board management system can do this, do a detailed analysis, even if you think it’s OK. If something is not 100% broken, but has degraded capability, it will show up in diagnostics. I’ve seen this before on old computers. However, I have three computers in my corner that are over ten years old, and all of them work to some degree. One of them behaves as if the inside is dusty and dirty, and it will heat up if i use it too long, but otherwise works. The others are fine. Last decade I had an old desktop that lasted nearly a decade. Even though powered off, I had one or two nearby electrical storms that took out equipment within a half mile radius. I got free replacement parts from an electronics store because their electronic cash registers weren’t working; because I was a repeat customer I got a free power supply; things like fan/power supply units, disk drives, and sometimes even mother boards will go back if either a static electricity or sharp power spike gets past a surge protector or unprotected system and that, based on my decades of system use, is the most likely cause of a problem.
I also encountered similar issues in our data center at a software company where I worked. If we knew in advance of a major storm, we’d power everything off; we did have surge and filtered power sources, but major surges can get through even those protective measures when it’s a major event.
--
Brian Masinick
- You must be logged in to reply to this topic.
