-
Search Results
-
$ 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 linuxfsStill weak as kitten., Just sharing for now. All credit goes to
Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.Linux Registered User # 475019
How to Search for AntiX solutions to your problemsTopic: antiX success story
Hello people,
I just want to say “thank you” for this really great Linux-distribution! My (in my terms) not so very old laptop (about 15 years) was urgently in need for a new operating system, since Ubuntu 12.04 LTS wouldn’t have let me upgrade anymore to the next LTS. This is more than a year ago, and I had only left little spare time to find a good solution. I looked around… searched… tested. Nothing was convincing on this machine. All went as slow, as if it was a 80386-based computer and not a 1,4GHz machine. They don’t seem to bother about efficient and slender code anymore, in times of rapid and constantly increasing size and speed of new hardware. And then, finally I got what I was looking for: antiX. I coincide with its way of keeping things simple as possible, nevertheless cute and well designed. I really dislike the “modern” attitude, to replace everything which is older than 2 years without any really good reason, but I was nearly arrived at the point to give way the idea of not being able to find a secure and at the same time convenient system for my old but fast equipment. This changed the moment antiX came to my attention. Thank you very much again!
Originally this notebook was shipped with Windows XP, and as long as it got regular updates from the manufacturer there was no reason to raise difficulties by changing anything profoundly (“never touch a …”). Then I switched to sidux, and most things worked. But it was rather time-consuming to manage, often something stopped working all of a sudden and since I have to use this notebook and not to play around with re-installing previously well-oiled things after they got broken by an update… I changed to Ubuntu, expecting a long period of time without the need of reinstalling something. But this was a great mistake. They told me, not even two years later, on the upgrade-screen, that my Machine wouldn’t met the requirements any longer for the upgrade. So I had to stay with the insecure outdated system for a quite long time. Not one of the better feelings, this…So here’s the technical part of the story. I’m going to tell it in detail, since it might help other users to sail around some problems I encountered while setting up the system.
It is a RIM 2000, with an Intel 915 Pentium M processor at 1,7 GHz, 2GB RAM and 100GB HDD, Nvidia Go6600 Graphics, 1440×900 Screen, built in the early 2k-years (2005 I believe). It has internal Bluetooth, IrDA, built-in TV-card, surround audio-out, headphones, line-in, microphone-in, s-video in and out, external monitor SUB-D-connector, internal speakers, DVD-burner, firewire and internal phone-line modem, SD-card reader, and PCMCIA-slot.
The realy great thing is: All the standard functionality worked out of the box in – and that’s the drop of bitterness – in antiX 17.4, not in the actual antiX 19.1. It is some months ago when I first started the migration to antiX, and so the recent “Manolis Glezos” wasn’t out yet. I’ll give it a try again in the next few months. There was literaly no way to get antiX 19.1 to boot (double-checked the ISOs with its sha-sums). After using some bootcodes I ended up on a washy and blurry desktop, and the system perseveringly refused to accept the correct graphics-settings for my screen. And no Nvidia-drivers around to mend it. So I went back to antiX 17.4.1, which started up perfectly. Checked: Graphics (using noveau): OK. Keyboard OK. Wireless: OK. Sound OK. So I made an USB-stick in order not to touch the installed system until I had checked the rest of its features. Your USB-technique is great, I just write from the live-persistent system, fully configured. Soon it will be installed on the hard-drive finally.I’ll call it a day for now. But I’ll try to continue my writing here for interested people, what I experienced while making things work in detail, configuring, updating, installing the meltdown/spectre-kernel and so on. I have some special needs, which had to work on the notebook: – musical notation – and MIDI. Let my say so much: It works like a charm in antiX.
Yours
RobinPS: I apologize for some strange inflexions, I’m not a native speaker in English language.
- This topic was modified 2 years, 6 months ago by Robin. Reason: orthography
Windows is like a submarine. Open a window and serious problems will start.
Topic: USB Install Question
I’ve downloaded antiX-19.3_x64-full.iso to my Mac and flashed it to a 32GB USB 3.0 using Etcher. I want to run Antix from my USB with persistence for now.
When I boot to USB, it does not give me any FKeys to choose options. I’m worried that if I choose install, it will overwrite my Mac hard drive. I’ve been going to FAQ, and Video’s looking for my own answers without any luck to the following three questions:
1) Why don’t I see any FKey options before install?
2) Will I be given a choice where to install or will it automatically overwrite my hard drive?
3) Can I install to my USB or do I need a second one to install to and is that different than USB with persistence?I want to boot from a USB and run Antix from it without fear of over writing my hard drive. It would be great if I could access the hard drive and save some files to it, utilizing any free space, without overwriting any other files on there but that would be a bonus and not what I’m expecting.
Grateful for any help!