- This topic has 23 replies, 6 voices, and was last updated Nov 14-11:34 am by ModdIt.
-
Posts
-
dee64
$ inxi -Fxz System: Host: dee Kernel: 4.9.212-antix.1-486-smp i686 bits: 32 compiler: gcc v: 8.3.0 Desktop: IceWM 1.8.3 Distro: antiX-19.2_386-full Hannie Schaft 27 March 2020 base: Debian GNU/Linux 10 (buster) Machine: Type: Laptop System: Hewlett-Packard product: Pavilion ze5200 v: KF.F.13 serial: <filter> Mobo: Hewlett-Packard model: 0850 v: NS570 Version PQ1B60 serial: <filter> BIOS: Phoenix v: KF.F.13 date: 02/27/2004 CPU: Topology: Single Core model: Intel Pentium 4 bits: 32 type: MCP arch: Netburst Northwood rev: 7 L2 cache: 512 KiB flags: pae sse sse2 bogomips: 5315 Speed: 2658 MHz min/max: N/A Core speed (MHz): 1: 2658 Graphics: Device-1: AMD RS200M [Radeon IGP 330M/340M/345M/350M] vendor: Hewlett-Packard driver: radeon v: kernel bus ID: 01:05.0 Display: x11 server: X.Org 1.20.4 driver: ati,radeon unloaded: fbdev,modesetting,vesa resolution: 1024x768~60Hz OpenGL: renderer: Mesa DRI R100 (RS200 4337) x86/MMX/SSE2 DRI2 v: 1.3 Mesa 18.3.6 direct render: Yes Audio: Device-1: ULi M5451 PCI AC-Link Audio vendor: Hewlett-Packard driver: snd_ali5451 v: kernel bus ID: 00:06.0 Sound Server: ALSA v: k4.9.212-antix.1-486-smp Network: Device-1: ULi M7101 Power Management [PMU] vendor: Hewlett-Packard type: network bridge driver: ali1535_smbus v: N/A port: 2000 bus ID: 00:11.0 Device-2: National DP83815 Ethernet vendor: Hewlett-Packard driver: natsemi v: kernel port: 2400 bus ID: 00:12.0 IF: eth0 state: down mac: <filter> Device-3: Realtek RTL8188EUS 802.11n Wireless Network Adapter type: USB driver: r8188eu bus ID: 1-2:3 IF: wlan0 state: up mac: <filter> Drives: Local Storage: total: 37.26 GiB used: 6.16 GiB (16.5%) ID-1: /dev/sda vendor: Hitachi model: IC25N040ATCS04-0 size: 37.26 GiB Partition: ID-1: / size: 12.63 GiB used: 6.16 GiB (48.8%) fs: ext4 dev: /dev/sda5 ID-2: swap-1 size: 2.02 GiB used: 284 KiB (0.0%) fs: swap dev: /dev/sda6 Sensors: System Temperatures: cpu: 64.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 140 Uptime: 1h 10m Memory: 873.7 MiB used: 453.4 MiB (51.9%) Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.36I have been using antix 19.2 for a couple of months on this old girl she has been with me for 17yrs never let me down using win xp. An unamed linux distro f–d everything up and xp was no more, antix was the only distro that took one look up her skirt and said “I’ve got just the thing for you” and here we are. 19.2 was great until I started installing updates. Well it’s doing it again. I took the advice and started clean with a completely new install of 19.2 (finding 19.2 to download is another story) Downloaded on another machine running MX19.2, md5 and live usb maker, installed on this machine even installed Grub during the installation, wow never done that before, made a couple of small adjustments changed the wallpaper for a black screen, shrunk the toolbar, set the keyboard and time and installed XDM download manager and extension for firefox that’s it. Ran updater and installed 233 updates rebooted, failed to boot. Ran live usb Boot Repair, all good, decided I would create a snapshot before I did anything else. Ran snapshot from the menu so nothing else was running, snapshot created successfully BUT having learnt my lesson from last time I checked the md5sum that had just been created, FAILED. I reinstalled iso_template and ISO Snapshot, deleted the Snapshot just created and tried again. First sign of madness, doing the same thing over and over again and expecting a different result. md5sum failed again. I did notice that within the snapshot creation text there was a small thing, about 0.02% is this normal #xorriso : UPDATE : 99.98% done#. I know how much you tech guys love your CLI
so I ran live usb maker from the cli command centre if nothing else it showed the problem lay in the linuxfs file.
I don’t get out much so sorry if this was overly long, anyone got a clue what is going on or should I just do a clean install and ignore the bloody updates?$ ls snapshot-19_2_updates301020.iso snapshot-19_2_updates301020.iso.sha512 snapshot-19_2_updates301020.iso.md5 dee@dee:/home/snapshot $ md5sum -c snapshot-19_2_updates301020.iso.md5 snapshot-19_2_updates301020.iso: FAILED md5sum: WARNING: 1 computed checksum did NOT match I reinstalled iso_template & snapshot for good measure, deleted this snapshot and ran snapshot again. xorriso : UPDATE : 99.98% done IS THIS RIGHT 99.98% ISO image produced: 892385 sectors Written to medium : 892385 sectors at LBA 0 Writing to 'stdio:/home/snapshot/snapshot-20201030_1148.iso' completed successfully. isohybrid: Warning: more than 1024 cylinders: 1743 isohybrid: Not all BIOSes will be able to boot this device MX Snapshot completed sucessfully! Snapshot took 00:30:03 to finish. Thanks for using MX Snapshot, run MX Live USB Maker next! literally 1min later ran md5sum check dee@dee:/home/snapshot $ md5sum -c snapshot-20201030_1148.iso.md5 snapshot-20201030_1148.iso: FAILED md5sum: WARNING: 1 computed checksum did NOT match Dont think this should happen!! Ran Live usb maker via cli command centre >> check-usb-md5 check md5 for initrd.gz check md5 for linuxfs Warning: MD5 CHECK FAILED FOR linuxfs
anticapitalista
Install the latest version – antiX-19.3
Make sure you do a dist-upgrade before doing any remastering/snapshots.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Thanks for a very fast reply. Have not been able to install 19.3 it stalls before X, posted this in another thread that’s where I got the advice to reinstall 19.2 and upgrade from there.
Had to look up the thread.
I said.
Have the same problem. 19.3 Full and Base iso do not go to desktop the boot finishes at a username prompt and password prompt with the instruction to enter as root and enter “cli-installer”XECURE gave this advice.
Anyway, if 19.2 works for you, install and update it. Your system will be almost the same as installing from 19.3, so nothing to worry then.Which is exactly what I have done and it has done exactly the same thing, again.
Anyone know why?
anticapitalista
I think Xecure mentioned before that the old box may not like the firmware upgrade.
So a dist-upgrade will break it.
I know this is probably a pain to do, but can you upgrade bit by bit? (don’t upgraded any firmware)Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Xecure
Device-1: AMD RS200M [Radeon IGP 330M/340M/345M/350M]
vendor: Hewlett-Packard driver: radeon v: kernel bus ID: 01:05.0
Display: x11 server: X.Org 1.20.4 driver: ati,radeonI think the update that breaks your system is
firmware-amd-graphics (20200918-1.0antix). Use synaptic to pin your current version, or
sudo apt-mark hold firmware-amd-graphics
and then upgradeantiX Live system enthusiast.
General Live Boot Parameters for antiX.Sorry for the delay in responding, my night for cooking supper, making a stew so had to start a bit earlier.
I think Xecure mentioned before that the old box may not like the firmware upgrade.
So a dist-upgrade will break it.
I know this is probably a pain to do, but can you upgrade bit by bit? (don’t upgraded any firmware)I don’t know how to upgrade bit by bit, happy to learn. Been using linux mint for the last 10 yrs just had to tick a box in Mint update to exclude an item.
Device-1: AMD RS200M [Radeon IGP 330M/340M/345M/350M]
vendor: Hewlett-Packard driver: radeon v: kernel bus ID: 01:05.0
Display: x11 server: X.Org 1.20.4 driver: ati,radeonI think the update that breaks your system is
firmware-amd-graphics (20200918-1.0antix). Use synaptic to pin your current version, or
sudo apt-mark hold firmware-amd-graphics
and then upgradeI’m sorry I have looked in synaptics and cannot find anything called “pin” this is obviously tech speak for something so thank you for the term command. Though I think this refers to “Lock this version”?
For both of you: I take it you both are saying that I should do a clean install of 19.2 and then implement the methods you are suggesting? Obvious to some, less obvious to others!
Either way many thanks for your assistance.
Back to the kitchen.
Xecure
For both of you: I take it you both are saying that I should do a clean install of 19.2 and then implement the methods you are suggesting? Obvious to some, less obvious to others!
Yes. Sorry I didn’t explain it properly.
For now you could install antiX 19.2 again, and mark the firmware updates for holding their version (and not update). The most suspicious one based on your hardware is the graphical related firmware, the amd firmware, as it seems your intel CPU doesn’t manage the graphic environment. If you are suspicious of any other one, also hold it back.
It has been some time since I used synaptic, so probably the correct term is “Lock version”. Sorry if it was confusing. In my native language it would translate to “pin”, as in “put a pin so it doesn’t move”.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.Anonymous
“Lock version”
Bear in mind that synaptic preference is not “global” ~~ it will have no effect when apt (aka “apt-get”) operations are performedthe “global” method to achieve this is, via commandline:
sudo apt-mark hold packagenameand, for peace of mind, I usually immediately confirm the hold directive has been regiestered, via:
apt-mark show holdHello boys. I can not say that this has been fun.
I figured out how to put a hold on all firmware updates at once.
OH never mind! the long and short of it is, I have reinstalled so many times all I can say is “no more”
I have downloaded from different mirrors, to try different locations, which is a task in it’s self as not many have 19.2 anymore.This morning I decided to try one last time. I did yet another clean install but this time as soon as the new install had finished and rebooted, I ran Snapshot and guess what the md5sum failed again. How the hell can an md5sum check fail 60 secs after it has been generated? As I understand it the checksum is for security and is supposed to reveal if a file has been changed since the checksum has been created, this is what doesn’t make sense to me!
I am just going to stay with 19.2 as it is, it worked just fine before I started installing updates, I am not going to apply any updates all I have to do is figure out how to turn the updater off once and for all.
Sincerely thank you for your help.
How do I mark this thread as closed or do you do that?Checking the firmware by locking it and running updater multiple times, revealed absolutely nothing. But as the above shows it probably was not the problem. I think this computer has got the hump with me and even though I rarely have the microphone on she has found out I am retiring her.
- This reply was modified 2 years, 6 months ago by dee64.
Xecure
I think this computer has got the hump with me and even though I rarely have the microphone on she has found out I am retiring her.
Hahaha. It like a child demanding for your atention.
I don’t know what is going on with the iso snapshot, so I have no clues as to why it is acting up.
If you want to block all updates and update notifications, purge the apt-updater.
The antiX system already works well with version 19.2, so maybe the only things you need is to install new packages as needed and forget about updates. Firmware and other updates are optional.
If no-one else has any ideas, you could do that and keep the system running the same versions of programs (except maybe update browsers or some kernel updates if after installing they boot properly, for some security patches).
antiX Live system enthusiast.
General Live Boot Parameters for antiX.
Brian Masinick
With the checksum errors and related issues I wonder if the hardware is showing signs of major failure; often that is behind these kinds of errors.
I’d be looking for an inexpensive disk to replace the existing one for starters. If a reasonable one is available (maybe even a working one from another system or a cheap one from a good sale, I would make an educated guess that it would help.
--
Brian MasinickThank you for help. Yes that is what I’m going to do. I’ve just put the snapshot on a usb stick using dd command and it runs live without any obvious problems, I know it will not save data but if I can use it as a backup, it will save me having to setup everything from scratch if ever there is a fatal error.
Once again ,thank you for your help. Now to the prophet of Doom and Gloom down below.Hah!! you’re a cheery bugger! To be honest I had considered buying her a new heart and lungs but at 17 human years old, not sure how much that is in Computer years, I thought the money would be better spent on another younger model.
If you look at ebay.es you will find that everything is twice the price of ebay.com (usa) so inexpensive normally means “crap”. Purely from a technical view it is only Snapshot where the md5sum fails every thing else is fine.
Oh My God I just looked at your photo, oops sorry I had my distance glasses on not my reading glasses.ModdIt
Maybe worth checking your drive if you have not done so already. Most surviving/usable drives support SMART Monitoring.
In the console:
sudo apt-get install smartmontools
Use Smartctl to check drive.
sudo lsblk #to find your device
sudo smartctl -a /dev/sdX #will print smart data in terminal window.You may need some help in interpreting the output. If so just post pls.
Your old Laptop is worth keeping working if you are able. It was not designed to fail as
most so called modern devices are.
- You must be logged in to reply to this topic.
