Search Results for 'swap'

[Member Robin]

Test

the additional “c” option makes a checksum comparison, so if nothing shows up to have been changed, everything is fine now.

Example output of the check, everything fine:

		# rsync --stats --progress --numeric-ids -axAhHSPc /mnt/Ubuntu-root/ /mnt/USBstick-root
		sending incremental file list

		Number of files: 283,193 (reg: 183,665, dir: 26,884, link: 72,525, dev: 82, special: 37)
		Number of created files: 0
		Number of deleted files: 0
		Number of regular files transferred: 0
		Total file size: 5.97G bytes
		Total transferred file size: 0 bytes
		Literal data: 0 bytes
		Matched data: 0 bytes
		File list size: 1.24M
		File list generation time: 0.220 seconds
		File list transfer time: 0.000 seconds
		Total bytes sent: 13.65M
		Total bytes received: 29.63K

		sent 13.65M bytes  received 29.63K bytes  7.98K bytes/sec
		total size is 5.97G  speedup is 436.01

At this point, everything is written on the USB-stick already.
Now we have still to do some homework for school:
first, we have to modify fstab on the freshly created stick according to the given facts when booting from the stick later. Since we will never guess, which /dev/sdXY the stick will get assigned at boot-time, we will switch to UUID-method to identify the partitions. In case of “/” there is the UUID of the hdd, which has to be replaced with the one of the root-partition of the stick, we have written down at the beginning. Also the entry of the home partition has to be corrected: We replace the /dev/sda5 entry with the UUID of our /home partition of the stick. Moreover we have to replace ext3 by ext4, since we have an ext4 filesystem now.

# cat /mnt/Speichertift-root/etc/fstab
		# /etc/fstab: static file system information.
		#
		# Use 'blkid -o value -s UUID' to print the universally unique identifier
		# for a device; this may be used with UUID= as a more robust way to name
		# devices that works even if disks are added and removed. See fstab(5).
		#
		# <file system>                            <mount point>   <type>  <options>             <dump>  <pass>
		proc                                        /proc           proc    nodev,noexec,nosuid   0       0
		#
		# / was on /dev/sda10 during installation
		#UUID=0eb91a9b-ea52-4f5b-9140-5a06f6f73d1d  /               ext4    errors=remount-ro     0       1
		# moved to new location
		UUID=76135213-70cb-4645-862b-4725026f4727   /               ext4    errors=remount-ro     0       1
		#
		#
		# swap was on /dev/sda11 during installation
		# UUID=dbb40875-198e-4fd7-b6e4-e59ee464426b none            swap    sw                    0       0
		# existing swap on /dev/sda9
		UUID=2d151628-e6f1-4e23-a8a6-7820d17b8a14   none            swap    sw                    0       0
		#
		#
		# existing home on /dev/sda5 94021be3-c160-4166-a151-92ad72b26f9a
		#/dev/sda5 /home ext3 nodev,nosuid 0 2
		# moved to new location, using ext4 now
		UUID=a4489010-a7a5-4249-b88e-4702a5672450   /home           ext4    rw,nodev,nosuid       0       2
#

In the fstab file all the lines beginning with a sharp sign (#) are comments and will be ignored by the system. In this case they contain earlier entrys and comments some of which were created during original installation of the OS by the installer-script. Here are alle the new UUIDs at its place already.
You can edit this file with a graphical text-editor (e.g. geany from antiX menu), but you’ll need root privileges to write it back to the stick after having done all amendments.
So you might key in into the still open root console window

			# geany&

btw, you don’t need to care about the tons of spaces between the entrys on a single line, they are for human readability only. It merely has to be at least 1 Space between them.

And here comes the feestyle skate, after having done all the duty:

Windows is like a submarine. Open a window and serious problems will start.

[Member Robin]

Test

Write down:

/dev/sdc (for sdc, the drive) and
/dev/sdc1 (for sdc1, the partition).

(This is an example from my setup only, you’ll have to write down what you get from your own screen).

These are the folders in your system where the programs can find that very drive and partition(s).
It is absolutely important to be sure about which device you want to adress later, since any mistake in these names will probably result in complete erasing another drive unwantingly! Don’t plug off or on anything before having gone through the following procedure completely, hence this might change these names in your system with all conseqences.

Now start from the antiX main menue the program “gparted”:
Menu–>Programs–>Systemtools
(or just type in the root console window “gparted&”, the ampersand is not a typo! it lets you work on at the console while the program is still running.)

At the upper right corner of gparted program window choose the “Drive” you just have found.
+++ WATCH OUT: A fault in choosing the correct drive here will delete your data without return!

– remove all the partitions on that drive (and only on that one)
– start the execution, wait until it is done.

Maybe you get a warning, the partitions were just in use, since they probably have been mounted automatically while plugging on the stick
In this case you’ll have to unmount before proceeding: Key in your root terminal window from above:

	
# umount /dev/sdc1

or just let it be done by the drive-unmounter from the antiX taskbar. Now the deletion of the partition should complete without complaints.

Next in the gparted window create new Partitions, according to your old system on the hdd:
1.) 1x Primary, ext 4, Name: “/”, Size as required, but bigger (or at least same size) than that partition containig the root-filesystem on your hdd, in my case this was 7,5GiB, I’ve chosen 10GiB which is 10240MiB (gparted asks for MiB)
2.) 1x Extended (size: all the rest of the Drive)
3.) 1x Logical, within the Extended one. ext4 also, named “/home”. Size may take the complete remains of the drive, as you like. At least it must have the size of the /home partition of your old system on hdd.
(at this point you’ll have to add more logical partitions if your old system you want to transfer requires them, name them as they are named in the old system. You can
get the correct names by keying in “blkid” in the still opened root-terminal from above.)
(Swap partition will not be created on this SDD, one can create this later, but there will be probably be always a swap partition on your hdd you can use, so you don’t really need one on the thumbdrive.)
If you’d like to make the system on the thumbdrive running a little faster, just read this concerning a correct allignment of your new partitions:
(Partition Alignment detailed explanation)
But it will work anyway, even without a correct alignment. Moreover I’m nearly sure gparted in the antiX version I’ve been using would manage this in the correct way automatically for you.

– start the execution, wait until is done.

– Set the Flag “boot” on primary partition.

Close the program gparted, as we don’t need it anymore, but let the root-console window still open.

The freshly partitioned stick possible won’t be readable in your old system, even if it has EXT4 drives itself. Crude thing this, but true. This is true, if the kernel of your hdd-system is older than the one on the antiX you are just working with. You can’t determine whether it’ll be readable (and bootable in consequence) by your old system, since Ext4
names itself always Ext4, instead of Ext4.01 Ext4.02 and so on, even if the versions are not backward compatible. So it can happen an Ext4 formatted USB-stick is unreadable in another PC, which understands Ext4 also, only cause of an even slightly older kernel version it still has.
So you’ll have to do some aditional steps:
In case you don’t know the version number of the old kernel by heart and don’t want to boot it up right now just for reading it out, you can look at its root partition:

Key in into the still open root console window

	# dumpe2fs /dev/sdc1 |grep "Filesystem features:"

the result should look something like

		dumpe2fs 1.43.4 (31-Jan-2017)
		Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery extent 64bit flex_bg sparse_super large_file huge_file metadata_csum uninit_bg dir_nlink extra_isize

This output will show you which features are actually active on the Ext4 filesystem just created on the stick.
Now we’ll have to compare it with the capabilities of the Ext4 filesystem provided by your old system

Mount your root partition of hdd, in my case it was /dev/sda10 to a place you like or let antiX mounter script do it for you.
I mounted it to /media/sda10, so I had to key in for
looking into the grub config file:

		# cat /media/sda10/boot/grub/grub.cfg |grep "menuentry"
			menuentry 'Ubuntu, with Linux 3.2.0-126-generic' --class ubuntu --class gnu-linux --class gnu --class os {

or read the names of the subfolders in the folder:

		# ls /media/sda10/lib/modules
			3.2.0-125-generic  3.2.0-126-generic

In any case counts the highest version number which is present there.

You will find for each feature in the output from dump2fs above an entry in the list provided in
Ext4 Kernel Support
and you should look carefully, if there is a feature in your Ext4 filesystem active which has been implemented only in a kernelversion higer than that you have found for the OS you want to transfer to the stick.
If you find all the features supported by the Ext4 provided by your old system everything is fine, you don’t have to do the following steps and can directly go ahead to the file transfer below.

But if not, as it was in my case, you’ll have to deactivate the features of the filesystem on the stick which are not supported. In my case it was a feature called “metadata_csum” which was the culprit, it is in Ext4 not before kernel version 3.18 and ubuntu didn’t provide a new kernel since 3.2.0-126 for the lts-system on that notebook.
So if we want to have the old system boot from the stick, we’ll have to make it suitable for the old kernel.
(Alternatively you could have done all the steps before from within your old system, but there was in my case no gparted installed, and you won’t get it installed these days anymore from the repos. They are not existant anymore at ubuntu servers.)
Another way around would be to homebrew a new kernel from source, at least 3.18 (cause of metadata_csum) for the old system, which doesn’t make any sense in my opinion, for the system gets conserved for backup purposes only. So I’ll stick to what I can get.
So, to make things short, key in the still open root console window:

	# tune2fs -O +uninit_bg /dev/sdc1
	# tune2fs -O +uninit_bg /dev/sdc5
	# tune2fs -O ^metadata_csum /dev/sdc1
	# tune2fs -O ^metadata_csum /dev/sdc5

(for details about what you are doing: $ man tune2fs in another console window)

Windows is like a submarine. Open a window and serious problems will start.

[Member Robin]

Test:

Example Output of lsusb and lsblk (before pluging in new stick):

# lsusb
Bus 001 Device 003: ID 090c:2000 Silicon Motion, Inc. - Taiwan			<--after knowing which bus is capable of USB2.0 we can see antiX live stick is pluged in one of the proper slots already.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub   <--here we have the USB2.0 Hub, look for which bus-Number it has
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 093a:2533 Pixart Imaging, Inc.              <--this is an USB-mouse only, at one of the USB1.1 plugs.
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
# lsblk
NAME    MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
loop0     7:0    0  2,6G  1 loop /live/linux	  <- these two loop-entrys belong to the antiX live system.
loop1     7:1    0  1,5G  0 loop /home					it is *not* your home-partition on your hdd, it contains antiX user "demo".
sda       8:0    0 93,2G  0 disk 				  <--here starts the hdd
├─sda1    8:1    0    8G  0 part /media/_daten1	  <--this is the primary partition, originally used by another OS, nowadays used as file-storage
├─sda2    8:2    0    1K  0 part 				  <--this is the extended partition (look at its size)
├─sda5    8:5    0   20G  0 part /media/_home	  <--this is the first logical partition within the extended partition
├─sda6    8:6    0   10G  0 part /media/_daten2	  <--another partition previously used by an even older OS , now file-storage
├─sda7    8:7    0 42,5G  0 part /media/_daten3   <--this was preveously the home-partition of that even older OS, now file-storage
├─sda8    8:8    0    3G  0 part /media/_daten4   <--another historically grown partition now in use as file-storage. 
├─sda9    8:9    0  2,2G  0 part [SWAP]			  <--this is the swap-partition of the old ubuntu system
└─sda10   8:10   0  7,5G  0 part /media/sda10	  <--this is actually the root partition of the old ubuntu system.
sdb       8:16   1 29,5G  0 disk 					<--here starts the USB stick with antiX on it, even if it is named "disk" here.
├─sdb1    8:17   1 29,5G  0 part /live/boot-dev		<--this is one of its partitions
└─sdb2    8:18   1   50M  0 part /media/antiX-uefi	<--and that is the other one.
sr0      11:0    1 1024M  0 rom  					<--finally we have a cd/dvd-drive.

This PC has as well 1.x as 2.0 USB conectors, you’ll have to look for the desciption at the end of the line for the word “2.0 root hub” (or evern higher) and then at the beginning of that line where is written the bus number, in this example it is bus 001. Now look for what else is connected to that very bus number. In this case there is a Bus001 Device 003, which is the Live antix USB stick. On one of the USB 1.1 plugs you can see the mouse (Bus 002, Device 002)

The partition order and usage is a little confused, since it is historicaly grown 😉 Never mind, it’ll work anyway, since the partitions used for file-storage don’t need to be transfered to the stick. They’ll get stored elewhere later on to free up the harddrive completely, which is a really easy job. The concern for today is to move the existing OS to a stick from within antiX live and make it bootable at its new residence.

Plug in the fresh USB-Stick. key in again:

	# lsusb
	# lsblk

Example output (after pluging new stick):

#lsusb
Bus 001 Device 003: ID 090c:2000 Silicon Motion, Inc. - Taiwan
Bus 001 Device 004: ID 058f:6387 Alcor Micro Corp. Flash Drive	<--the new USB-stick, connected also to USB2.0 capable slot.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 093a:2533 Pixart Imaging, Inc. 
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
#lsblk
NAME    MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
loop0     7:0    0  2,6G  1 loop /live/linux
loop1     7:1    0  1,5G  0 loop /home
sda       8:0    0 93,2G  0 disk 
├─sda1    8:1    0    8G  0 part /media/_daten1
├─sda2    8:2    0    1K  0 part 
├─sda5    8:5    0   20G  0 part /media/_home
├─sda6    8:6    0   10G  0 part /media/antiX
├─sda7    8:7    0 42,5G  0 part /media/_daten3
├─sda8    8:8    0    3G  0 part /media/_daten4
├─sda9    8:9    0  2,2G  0 part [SWAP]
└─sda10   8:10   0  7,5G  0 part /media/sda10
sdb       8:16   1 29,5G  0 disk 
├─sdb1    8:17   1 29,5G  0 part /live/boot-dev
└─sdb2    8:18   1   50M  0 part /media/antiX-uefi
sdc       8:32   1 58,6G  0 disk 									<--here we are!
└─sdc1    8:33   1 58,6G  0 part /media/sdc1-usb-Generic_Flash_Di	<--and this is the (empty) partition the manufacturer has put on it.
sr0      11:0    1 1024M  0 rom  

After pluging the new stick to an USB-connector, it should be also located at bus 001, since we know by now this is the one which provides USB2.0 in this case. If not, try another plug and restart this procedure.
The Plugs aren’t to distingusih optically from outside. You’ll have to adapt the concept to what you will find at your PC, maybe you even find USB3.0

Compare the output of the first with the second lsblk command. The enty which hasn’t been present there before is the devicename of the USB-stick. You can clearly see the new device sdc in the example output, which refers to the drive as a whole, and the device sdc1 which is the partition, it has only one in this case, otherwise there would be entrys like sdc2 sdc3 and so on. These new entries are what we are looking for.
Write down:

Windows is like a submarine. Open a window and serious problems will start.

[Member Robin]

Test
some part of a guidance for beginners I just wrote and tried to submit causes a 403 repeatedly:

A potentially unsafe operation has been detected in your request to this site
Your access to this service has been limited. (HTTP response code 403)

I am posting from antiX 17.4.1 using firefox 78.4.1esr-1~deb9u1. Don’t see where an “unsafe operation” should come from.
Already disconnected and reconnected from internet in order to get a new IP just in case somebody to whom the first IP was assigned to just before me has done some mischief. Didn’t help.

So I’ll now cut the text in parts, post them here separately first to figure out which part causes the blocking.
—-starts form here—

I just want to share my experiences for the benefit of other antiX users who might want to pursue a similar strategy.
The text is written for the real beginner, step by step and as detailed as possible, so the old-timer might feel a little impatient and bored while reading. But I’m sure he could amend some improvements of the workflow in the end.

As I’ve stated elsewhere here in the forum, my final goal is to have the antiX system installed on the hdd of my notebook.
But what about the old, well oiled and fine tuned system installed on it? I prefer to keep it, since there are many helper programs installed, which I’ll probably won’t notice missing before I need one of them again, which then isn’t installed on the antiX system yet and then I couldn’t remember its name, which causes me researching for some hours again.
Moreover there are some homebrew shellscripts for solving dedicated problems stored on it, which I also don’t remember exactly what and where, but if I need one, I’ll know: It has bin there and there.
From past times I remember, when dd-ing the complete hdd or partition two things will happen:
The resulting partition-images are not really handy, they need to be cut into parts, compressed to fit on
a couple of DVD and I’ll probably never again have the diskspace to recreate and re-open them when I’d like to
search them for a script or program I perfectly know I’ve had at hand for a special task in the old system.
The second thing to happen is: Taking the before said into account, I will litter them, after having stored
them for years without having any way to make use of them.
So this time I decided to manage things the another way around:
I want to move the complete existing system from hdd to an usb-stick, keeping it bootable and usable, just as antiX runs now from the stick. The roles will be changed after that. antiX will boot form hdd, and the old system will boot from the stick.

I’ll repartition the hdd to current needs (it’s still partitioned as historically grown by succesively installing
different operating systems, which means: a couple of pretty small partitions, in a crude order spread over the hdd. I’d prefer to make a clean cut and from now on use GPT instead of MBR, which should be possible even when this notebook does only provide BIOS, (no EFI). Then I’ll create one small (2 GiB) Boot partition, one 12GiB for / (root), one swap (4GB) and all the remaining space will be used for the /home partition. I’ll try to use Extlinux instead of grub now, the isolinux/syslinux bootprocess on antiX-live/persist has ben convincing. And after these preliminaries I’ll finally install antiX in the newly created hdd structure. That is the line of approach.

Back to the first step:
Exporting the complete system to a memory stick. Sounds easy, but there are some pitfalls. Sounds difficult on the other hand, but it isn’t really.

First I had to prepare the USB-memory-stick. It is a cheap standard 64GB USB2/3 type, preformated for use on Windows-systems. I’ll give a step by step explanation of the complete process just in case someone wants to undertake the same procedure before installing antiX.

(make sure to use the fastest USB your PC provides. Some older models have USB 1.x and 2.0 both, and using the 1.0 only will slow things realy down. Everything from 2.0 should be ok, but it works even with 1.0, if you have no choice. You can check with lsusb as described below.)

Boot from antiX live-USB-Stick (or from CD/DVD). Don’t use a frugal install for this since it uses the hdd, possibly partitions you need to be untouched (unchanged) during the process.

Open a terminal (Menu–>Terminal), type “sudo su” and give your sudoer-password. (As you probably know, since it can be found in the antiX manuals, the standard PW for a non-persistent live system is “demo”.) Keep this terminal open until we’ve finished. Some people prefere to prefix every single command they key in with “sudo”. You can do it that way as well, omit simply the line “sudo su” and set sudo in front of each command instead.
hint:
– the “#” shows that you are in the role of “root” in that very moment, the command you key in is executed with root privileges.
– the “$” denotes that you are in simple user context and the commands are executed with the restricted privileges of the actual user.

You’ll always find these marks in the terminal somewhere at the beginning of the commandline.
Don’t key in these signs, only the commands behind them.

 
        sudo su
	demo		<--- sudoer pw in antiX live, key in when asked.
	# lsusb
	# lsblk

Example Output of lsusb and lsblk (before pluging in new stick):

Windows is like a submarine. Open a window and serious problems will start.

Hi,
I decided to give new life to my Notebook (Samsung N130 with CPU Atom N230, RAM 2Gb, SSD 240GB).
I downloaded anitx19.3, put it on a Usb key with Rufus under Windows 10. Then moved to the Samsung notebook and booted. Everything is ok.
I was able to configure WiFi and get access to Internet.
So I decided to install it on my HD (actually a SSD). The disk layout was set up by me with 8Gb boot, 4Gb swap and the rest to root. The first disappointment came when trying to configure the keyboard: I have an an Italian keyboard with 88 keys but such device is not present in the list of accepted keyboards, morevover there is no way to test it typing some characters in a box: [{ ]} and èé +*;, -_\| and so on, just to be sure the keyboard is usable; of course the selected keyboard is not working as expected (terminate installation, open terminal, type some chars wrong!), start again.
Eventually the keyboard reached an acceptable compromise: the US keyboard always works well. –
Configure the WiFi: this is a real nigthmare. There at least three entriees in the menu to configure a WiFi network, only the first one works. When trying to configure the WiFi some rows appear in a terminal window. One must pay a lot of attention since there at least two blocking errors: a file (/run/wpa_supplicant/wlan0) which can’t be deleted and the directory (/run/wpa_supplicant). Why they can’t be deleted by the proc?
No hope: the wpa_supplicant seems to finish correctly but there no way to get an address from DHCP nor to set a fixed address: no response from DHCP (on CentOS linux) and 260 minutes stuck on updating initrams when setting a fixed address (what? initrams? why?). Besides that the WiFi configuration hangs up the notebook: no mouse, no keyboard, Alt-CtrlDel displays a panel but without keyboard is useless. Only exit Power down. The DHCP system, a CentOS 7 Linux shows no entry in the log, it looks as the notebook can’t access the Wifi. Yes, the wpa_supplicant terminated correctly. IFCONFIG shows the adapter as UP with no IP address.

I am now considering to give it up, the idea was interesting, but the practice shows an implementation with poor error checking and a nature to the SEATTLE mind( I do know what is right for you and I’m doing it).
Regards,
Stefano

[Member Dzhigit]

I decided to install it in a vm because it has been a long time, and document the installation process. It is localized in:

olsztyn wrote:

English and US

I was thinking maybe your ISO was corrupted. I could not find the checksums. So I downloaded it twice to reduce the chance it was corrupted. The result:

• 6f0102e904a793b3674f8d0fedd6d93f orel-current.iso
• bc14f85c40ba32718fdbd3891e3889f9668b2dd0a1646291c82667ca2bb461c7 orel-current.iso

First I made the virtual storage with qemu-image create -f qcow2 storage.qcow 20G

I started the virtual machine with this command:

qemu-system-x86_64 \
-device virtio-serial-pci \
-spice unix,addr=/tmp/vm_spice.socket,disable-ticketing \
-device virtserialport,chardev=spicechannel0,name=com.redhat.spice.0 \
-chardev spicevmc,id=spicechannel0,name=vdagent \
-machine q35,accel=kvm \
-m 8G \
-cpu host \
-smp 4 \
-vga qxl \
-nic user,model=virtio-net-pci \
-audiodev pa,id=snd0 \
-device ich9-intel-hda \
-device hda-output,audiodev=snd0 \
-drive file=storage.qcow,if=virtio \
-cdrom orel-current.iso

And in another terminal tab remote-viewer spice+unix:///tmp/vm_spice.socket

1. F1 menu shows language selection. You can choose Russian or English.
2. Select “Install” (I did not select the graphical installer)
3. Select English language in the installer
4. Select United States for locale settings
5. Accept the license agreement (this is part of the reason why I do not use the system)
6. Select American English keymap (the installer hung on an empty blue screen for a while)
7. I kept the default host name, “astra”
8. For the user name, I typed “dzhigit”
9. For the password, I chose 123
10. Reenter password to verify
11. Error about entering password less than 8 symbols, I changed to 12345678 (why didn’t it do this before verify the password?)
12. For the time zone, select “Go Back” in the bottom left
13. Go to “Choose language”
14. Select English
15. Country or territory, select United States
16. Time zone, I chose Eastern (screen was blank for a while after this)
17. Partitioning method, I chose “Guided – use entire disk”
18. I selected the only disk in my list, the VirtIO storage device
19. Usually I put /home on separate partition, but this is quick installation, I put all in one partition
20. Finish partitioning and write changes to disk
21. Select “Yes” to answer “Write the changes to disks?” (also it created a swap partition)
22. Wait for it to copy the files
23. I kept defaults but deselected “Fly apps for working on devices with touchscreen” (this OS is also meant for phone/tablet) I had “Base packages,” “Fly desktop,” “Games,” “Internet suite,” “Office suite,” and “Multimedia”
24. Wait for files to copy (I think it said 1347 files but the number disappeared too quickly for me to say for sure)
25. “Additional OS settings,” I did not select anything, but normally I would consider “Enable password entry for sudo” (you may also want “Enable autologin to X session”)
26. I installed GRUB to MBR
27. I selected my VirtIO disk, /dev/vda
28. Installation is complete, I selected “Continue”
29. The installer took some time to run postinst steps
30. In the GRUB menu I selected the generic (non-hardened) kernel
31. Enter user name and password into Fly desktop manager and it will take you to Fly desktop environment
32. After installation, I purged i386 packages to free up storage and removed the i386 architecture
33. I tried to find neofetch or screenfetch, but it wasn’t in the repo, so I added Yandex mirror, but it still wasn’t there
34. Installed debian-archive-keyring and after large update, I added Stretch mirror in Synaptic and installed screenfetch and neofetch from Debian Stretch

No bugs were encountered.

Attachments:

1. 

   астра_линукс_орёл.jpeg
   

2. 

   астра_линукс_орёл_neofetch.jpeg
   

[Member ThakurMsh]

@skidoo, …disk partitioning…
@xecure,

th@anx:~
$ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 111,8G  0 disk 
├─sda1   8:1    0   256M  0 part /boot/efi
├─sda2   8:2    0 109,5G  0 part /
└─sda3   8:3    0     2G  0 part [SWAP]
sr0     11:0    1   5,7M  0 rom  /media/sr0

th@anx:~
$ blkid
/dev/sda1: UUID="1BA2-9BD6" TYPE="vfat" PARTLABEL="ESP" PARTUUID="8d82a762-b9cb-4a6e-9b58-13b880c663f9"
/dev/sda2: LABEL="rootantiX19" UUID="5f5cee75-af3f-4235-bf1f-43912d6f0ef3" TYPE="ext4" PARTLABEL="primary" PARTUUID="a3453ec6-21a9-4eb0-a2bf-624cdcceb4de"
/dev/sda3: LABEL="swapantiX" UUID="ef1cb892-6cf9-4c0f-8a7a-f22bfefbc70b" TYPE="swap" PARTLABEL="primary" PARTUUID="443a0dbc-1343-47c2-977c-7b08425632ca"
/dev/sr0: UUID="2018-11-29-11-25-39-00" LABEL="4G USB M-PM-<M-PM->M-PM-4M-PM-5M-PM-<" TYPE="iso9660" PTTYPE="mac"

then the question arises:
I have a disk of 120G, but if you add it up, it will be 112G
what is it? Disk /dev/ram*`

• This reply was modified 2 years, 5 months ago by ThakurMsh.
• This reply was modified 2 years, 5 months ago by ThakurMsh.
• This reply was modified 2 years, 5 months ago by ThakurMsh.

[Member Xecure]

I don’t understand what you are asking.
The “breakdown” of the disk is only:

Disk /dev/sda: 111,8 GiB, 120034123776 bytes, 234441648 sectors
Disk model: Samsung SSD 850
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 4DFAD128-5AEE-48D9-8F24-791482E420F0

Device Start End Sectors Size Type
/dev/sda1 2048 526335 524288 256M Linux filesystem
/dev/sda2 526336 230182911 229656576 109,5G Linux filesystem
/dev/sda3 230182912 234377215 4194304 2G Linux filesystem

The rest is Ram “sectors”. Not relevant to your Hard disk.

What I see is:
DISK: Samsung SSD 850 (111,8 GiB) – Partition table: GPT
– Partition 1 (/dev/sda1): Size: 256M – Type:Linux (can it be the /boot partition? not sure)
– Partition 2 (/dev/sda2): Size: 109,5G – Type:Linux (definitely the root or system partition, where ALL antiX system is housed)
– Partition 3 (/dev/sda3): Size: 2G – Type:Linux (This is the SWAP partition, that will be used for hibernation or when you need more RAM, and other things).

fdisk isn’t very good for what you want to figure out. Why not use
lsblk
or
blkid
to see real valuable info about your partitions?

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member catfood]

Using:
antiX-19.3-sid_x64-core.iso
sha256 verified, but my gpg -recv keys sites all seem to be acting up lately for full gpg verify

lsblk partially posted above
loop0 /live/linux
sda
-sda1 9G ext4
-sda2 7G ext4
-sda3 2G swap
sr0 /live/boot

The first attempt was in the cli-installer, so no reboot there.
Then made partitions with parted, and set fs types with fdisk(which have stayed since reboots).
lsblk showed my partitions fine every time, but always stuck mid installer, so guessing Dave’s answer is right.

These settings above are all being tried in virtual box, but I was getting same issue on a netbook trying to keed old debian sid home, but install antix sid over debian 10 sid there. Those partitions have been set in stone for a few years there, but same fail. It’s not urgent for VB testing, but when I put it on hardware, a separate home has saved me a lot of extra backups when I break things.

I don’t know enough to splice the git tar into the sid iso, and without a home directory created yet, no idea how to extract into primordial install void and use 😀
I will try again later after I see my antix live usb get a cli-installer in it’s apt updgrades.
Thank you everyone.

Howdy Jessie.

[Member sybok]

Hi, please clarify some of the below questions:
0) Check/Verify integrity of the downloaded ISO using check-sums.
1) Which version of antiX core (19.3?, 32/64-bit?) did you use?
2) How did you “try” to partition the drive?
The word “try” makes me suspect that something went wrong already in this step (but how would the installer see them).
3) Could you please post the output of lsblk?
4) Suggestion: Assuming you input the partition as text (antiX core), I wonder what would happen if you provide ‘/dev/sda2’.

Comment:
5) The partitions sizes seem to me to be fine; I recall an old suggestion saying swap = RAM/2.

• This reply was modified 2 years, 6 months ago by sybok. Reason: Typo fixed
• This reply was modified 2 years, 6 months ago by sybok.
• This reply was modified 2 years, 6 months ago by sybok. Reason: New suggestion: /dev/sda2

Hi, I’m trying to install antiX core and wanted to use a separate home. I tried partitioning the drive in the antiX-core live cli-installer.I also tried partitioning separately before installer, but both fail the same.

Root seems to wipe and be ready to install on sda1 fine, then:

Do you want to use a separate ‘/home’ partition (y/N)? y
/home partition (hda1, sda2, etc): sda2
sda2 invalid. Retry:

Currently trying with
sda
-sda1 9G ext4
-sda2 7G ext4
-sda3 2G swap

Is there a size requirement on /home? or some other obvious thing I missed?
Thanks.

• This topic was modified 2 years, 6 months ago by anticapitalista. Reason: solved

Howdy Jessie.

[Member akathaddeus]

Hope you guys can find the cause. It was up for two days on 4.14 32 bit before the last reboot and it has been up two days since. Should have confidence in a week or so.

Both the default 4.9 kernels freeze. Until I came across the 4.18+ post I had tried 64 bit Debian Buster Stable, 64 bit OpenSUSE Leap and 32 bit Opensuse Tumbleweed using lightweight desktops also without success. Did not try 4.4 because after the 5.5 test as the 4.18+ post observation by then was given more weight. The T7200 before the upgrade had ran for 14 years on kernel 2.6 with no unresolved downtime so very confident about the hardware.

All the tested OSes installed and operated great during the upgrade (AntiX was the fastest) but all would on average freeze sometime during the next 24 hours.

System:    Host: xxxxxx Kernel: 4.14.14-antix.1-486-smp i686 bits: 32 compiler: gcc v: 7.2.0
           parameters: BOOT_IMAGE=/boot/vmlinuz-4.14.14-antix.1-486-smp root=UUID=24c84370-a852-458a-ac26-c80966c5bbde ro
           vga=791 quiet
           Console: tty 0 dm: SLiM 1.3.6 Distro: antiX-19.2_386-full Hannie Schaft 27 March 2020
           base: Debian GNU/Linux 10 (buster)
Machine:   Type: Desktop Mobo: Gigabyte model: 8I945GMMFY-RH v: x.x serial: N/A BIOS: Award v: F1 date: 04/26/2006
Memory:    RAM: total: 2.95 GiB used: 350.3 MiB (11.6%)
           Array-1: capacity: 2 GiB slots: 2 EC: None max module size: 1 GiB
           Device-1: A0 size: 1 GiB info: double-bank speed: 66 MT/s type: Unknown detail: none bus width: 64 bits
           total: 64 bits manufacturer: N/A part-no: None serial: None
           Device-2: A1 size: No Module Installed
PCI Slots: Slot: 0 type: 32-bit PCI PCI status: Available length: Long
           Slot: 1 type: 32-bit PCI PCI status: Available length: Long
CPU:       Topology: Dual Core model: Intel Core2 T7200 bits: 64 type: MCP arch: Core Merom family: 6 model-id: F (15)
           stepping: 6 microcode: D1 L1 cache: 20 KiB L2 cache: 4096 KiB bogomips: 7980
           Speed: 1207 MHz min/max: 600/1200 MHz Core speeds (MHz): 1: 1025 2: 1024
           Flags: acpi aperfmperf apic arch_perfmon bts clflush cmov constant_tsc cpuid cx16 cx8 de ds_cpl dtes64 dtherm dts
           est fpu fxsr ht lahf_lm lm mca mce mmx monitor msr mtrr nx pae pat pbe pdcm pebs pge pni pse pse36 retpoline sep ss
           sse sse2 ssse3 tm tm2 tpr_shadow tsc vme vmx xtpr
           Vulnerabilities: Type: meltdown status: Vulnerable
           Type: spectre_v1 status: Vulnerable
           Type: spectre_v2 status: Vulnerable: Minimal generic ASM retpoline
Graphics:  Device-1: Intel Mobile 945GM/GMS 943/940GML Express Integrated Graphics vendor: Gigabyte driver: i915 v: kernel
           bus ID: 00:02.0 chip ID: 8086:27a2
           Display: server: X.org 1.20.4 driver: intel unloaded: fbdev,modesetting,vesa tty: 147x121
           Message: Advanced graphics data unavailable in console for root.
Audio:     Device-1: Intel NM10/ICH7 Family High Definition Audio vendor: Gigabyte GA-8I945PG-RH Mainboard
           driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:27d8
           Sound Server: ALSA v: k4.14.14-antix.1-486-smp
Network:   Device-1: Intel 82573L Gigabit Ethernet vendor: Gigabyte driver: e1000e v: 3.2.6-k port: a000 bus ID: 02:00.0
           chip ID: 8086:109a
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: xxxxxx
           IP v4: xxxxxx scope: global broadcast: xxxxxx
           IP v6: fe80::216:e6ff:fe5c:58e4/64 scope: link
           WAN IP: xxxxxx
Drives:    Local Storage: total: 111.79 GiB used: 3.65 GiB (3.3%)
           ID-1: /dev/sda vendor: Samsung model: SSD 840 EVO 120GB size: 111.79 GiB block size: physical: 512 B logical: 512 B
           speed: <unknown> serial: S1D5NSBF198826M rev: BB6Q scheme: MBR
           Floppy-1: /dev/fd0
           Optical-1: /dev/sr0 vendor: LITE-ON model: DVDRW LH-20A1P rev: KL0N dev-links: cdrom,cdrw,dvd,dvdrw
           Features: speed: 48 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram state: running
RAID:      Hardware-1: Silicon Image SiI 3132 Serial ATA Raid II Controller driver: sata_sil24 v: kernel port: 9000
           bus ID: 01:00.0 chip ID: 1095.3132 rev: 01
Partition: ID-1: / raw size: 109.76 GiB size: 107.53 GiB (97.97%) used: 3.65 GiB (3.4%) fs: ext4 block size: 4096 B
           dev: /dev/sda1 label: rootantiX19 uuid: 24c84370-a852-458a-ac26-c80966c5bbde
           ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap swappiness: 10 (default 60)
           cache pressure: 50 (default 100) dev: /dev/sda2 label: swapantiX uuid: 1a8fb0af-afb7-411d-a619-ea7b059673b5
Unmounted: Message: No unmounted partitions found.
USB:       Hub: 1-0:1 info: Full speed (or root) Hub ports: 8 rev: 2.0 speed: 480 Mb/s chip ID: 1d6b:0002
           Device-1: 1-1:2 info: Realtek USB 2.0 Card Reader type: Mass Storage driver: usb-storage interfaces: 1 rev: 2.0
           speed: 480 Mb/s chip ID: 0bda:0103 serial: 050304014271000121
           Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001
           Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001
           Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001
           Hub: 5-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001
Sensors:   System Temperatures: cpu: 30.0 C mobo: N/A
           Fan Speeds (RPM): N/A
Repos:     Active apt repos in: /etc/apt/sources.list
           1: deb http://mirror.datamossa.io/mxlinux/antix/buster/ buster main nosystemd nonfree
           No active apt repos in: /etc/apt/sources.list.d/antix.list
           Active apt repos in: /etc/apt/sources.list.d/buster-backports.list
           1: deb http://deb.debian.org/debian/ buster-backports main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
           1: deb http://ftp.au.debian.org/debian/ buster-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list
           1: deb http://ftp.au.debian.org/debian/ buster main contrib non-free
           2: deb http://security.debian.org/ buster/updates main contrib non-free
           No active apt repos in: /etc/apt/sources.list.d/onion.list
           No active apt repos in: /etc/apt/sources.list.d/various.list
Processes: CPU top: 5
           1: cpu: 0.4% command: su pid: 31046 mem: 3.14 MiB (0.1%)
           2: cpu: 0.4% command: bash pid: 31047 mem: 3.96 MiB (0.1%)
           3: cpu: 0.1% command: [kworker/0:1] pid: 20 mem: 0.00 MiB (0.0%)
           4: cpu: 0.1% command: nxserver.bin pid: 2138 mem: 58.5 MiB (1.9%)
           5: cpu: 0.1% command: nxnode.bin pid: 2694 mem: 55.7 MiB (1.8%)
           Memory top: 5
           1: mem: 58.5 MiB (1.9%) command: nxserver.bin pid: 2138 cpu: 0.1%
           2: mem: 56.3 MiB (1.8%) command: apt-notifier.py started by: python pid: 2593 cpu: 0.0%
           3: mem: 55.7 MiB (1.8%) command: nxnode.bin pid: 2694 cpu: 0.1%
           4: mem: 32.9 MiB (1.0%) command: xorg pid: 2091 cpu: 0.0%
           5: mem: 30.7 MiB (1.0%) command: nxclient.bin pid: 2711 cpu: 0.0%
Info:      Processes: 122 Uptime: 2d 1h 50m Init: SysVinit v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8
           Shell: bash v: 5.0.3 running in: tty 0 (SSH) inxi: 3.0.36

`

[Member PFO]

Hey DAWGS,

Here is the digital-daddy-wack readout of the 32 BIT – CD loaded 19.2.1 Basic HP celeron M Laptop. Burned a CD, because the hardware is too old to burn DVDs like most WIN XP boxes here in SE Europe – SO I have to work within the environment where I`ve landed.
_________________________________________________________________

System:
Host: antix1 Kernel: 4.9.212-antix.1-486-smp i686 bits: 32 compiler: gcc
v: 8.3.0 Desktop: IceWM 1.6.5 dm: SLiM 1.3.6
Distro: antiX-19.2.1_386-base Hannie Schaft 29 March 2020
base: Debian GNU/Linux 10 (buster)
Machine:
Type: Laptop System: Hewlett-Packard
product: HP Compaq nx6110 (EK048ES#AKN) v: F.0A serial: <filter> Chassis:
type: 10 serial: <filter>
Mobo: Hewlett-Packard model: 3088 v: KBC Version 39.1C serial: <filter>
BIOS: Hewlett-Packard v: 68DTD Ver. F.0A date: 07/25/2005
Battery:
ID-1: C171 charge: 8.8 Wh condition: 8.8/8.8 Wh (100%) volts: 12.5/10.8
model: Hewlett-Packard Primary type: Li-ion serial: <filter> status: Full
Memory:
RAM: total: 486.0 MiB used: 316.3 MiB (65.1%)
RAM Report:
permissions: Unable to run dmidecode. Root privileges required.
CPU:
Topology: Single Core model: Intel Celeron M bits: 32 type: MCP
arch: M Dothan rev: 8 L2 cache: 1024 KiB bogomips: 3000
Speed: 1500 MHz min/max: N/A Core speed (MHz): 1: 1500
Flags: acpi apic bts clflush cmov cx8 de dts fpu fxsr mca mce mmx msr mtrr
pae pbe pge pse sep ss sse sse2 tm tsc vme
Graphics:
Device-1: Intel Mobile 915GM/GMS/910GML Express Graphics
vendor: Hewlett-Packard NX6110/NC6120 driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:2592
Display: x11 server: X.Org 1.20.4 driver: intel
unloaded: fbdev,modesetting,vesa resolution: 1024×768~60Hz
OpenGL: renderer: Mesa DRI Intel 915GM x86/MMX/SSE2 v: 1.4 Mesa 18.3.6
direct render: Yes
Audio:
Device-1: Intel 82801FB/FBM/FR/FW/FRW AC97 Audio
vendor: Hewlett-Packard NX6110/NC6120 driver: snd_intel8x0 v: kernel
bus ID: 00:1e.2 chip ID: 8086:266e
Sound Server: ALSA v: k4.9.212-antix.1-486-smp
Network:
Device-1: Broadcom Limited BCM4318 [AirForce One 54g] 802.11g Wireless LAN
vendor: Hewlett-Packard driver: b43-pci-bridge v: N/A port: 2580
bus ID: 02:04.0 chip ID: 14e4:4318
Device-2: Broadcom Limited BCM4401-B0 100Base-TX
vendor: Hewlett-Packard NX6110/NC6120 driver: b44 v: 2.0 port: 2580
bus ID: 02:0e.0 chip ID: 14e4:170c
IF-ID-1: eth0 state: down mac: <filter>
IF-ID-2: wlan0 state: up mac: <filter>
IP v4: <filter> scope: global broadcast: <filter>
IP v6: <filter> scope: link
WAN IP: <filter>
Drives:
Local Storage: total: 55.89 GiB used: 3.88 GiB (6.9%)
ID-1: /dev/sda vendor: Hitachi model: IC25N060ATMR04-0 size: 55.89 GiB
speed: <unknown> serial: <filter> rev: AD5A scheme: MBR
Optical-1: /dev/sr0 vendor: MATSHITA model: UJ-840D rev: 1.02
dev-links: cdrom,cdrw,dvd,dvdrw
Features: speed: 24 multisession: yes audio: yes dvd: yes
rw: cd-r,cd-rw,dvd-r state: running
RAID:
Message: No RAID data was found.
Partition:
ID-1: / size: 9.07 GiB used: 3.81 GiB (42.0%) fs: ext4 dev: /dev/sda2
label: rootantiX19 uuid: 7acf51af-55b9-40b7-a592-2fcb87c1c938
ID-2: swap-1 size: 2.59 GiB used: 78.3 MiB (3.0%) fs: swap dev: /dev/sda3
label: N/A uuid: ad1f8051-2f56-42a1-b516-2cb2fdd0e7bc
Unmounted:
ID-1: /dev/sda1 size: 9.38 GiB fs: ntfs label: N/A uuid: 96B04EF6B04EDC7D
USB:
Hub: 1-0:1 info: Full speed (or root) Hub ports: 8 rev: 2.0
speed: 480 Mb/s chip ID: 1d6b:0002
Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Hub: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Hub: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Hub: 5-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Sensors:
System Temperatures: cpu: 51.0 C mobo: 40.0 C
Fan Speeds (RPM): N/A
Info:
Processes: 132 Uptime: 37m Init: SysVinit v: 2.93 runlevel: 5 default: 5
Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3 running in: roxterm
inxi: 3.0.36
PFO@antix1:~
$
PFO@antix1:~
$ inxi -Fxz
System:
Host: antix1 Kernel: 4.9.212-antix.1-486-smp i686 bits: 32 compiler: gcc
v: 8.3.0 Desktop: IceWM 1.6.5
Distro: antiX-19.2.1_386-base Hannie Schaft 29 March 2020
base: Debian GNU/Linux 10 (buster)
Machine:
Type: Laptop System: Hewlett-Packard
product: HP Compaq nx6110 (EK048ES#AKN) v: F.0A serial: <filter>
Mobo: Hewlett-Packard model: 3088 v: KBC Version 39.1C serial: <filter>
BIOS: Hewlett-Packard v: 68DTD Ver. F.0A date: 07/25/2005
Battery:
ID-1: C171 charge: 8.8 Wh condition: 8.8/8.8 Wh (100%)
model: Hewlett-Packard Primary status: Full
CPU:
Topology: Single Core model: Intel Celeron M bits: 32 type: MCP
arch: M Dothan rev: 8 L2 cache: 1024 KiB
flags: pae sse sse2 bogomips: 3000
Speed: 1500 MHz min/max: N/A Core speed (MHz): 1: 1500
Graphics:
Device-1: Intel Mobile 915GM/GMS/910GML Express Graphics
vendor: Hewlett-Packard NX6110/NC6120 driver: i915 v: kernel
bus ID: 00:02.0
Display: x11 server: X.Org 1.20.4 driver: intel
unloaded: fbdev,modesetting,vesa resolution: 1024×768~60Hz
OpenGL: renderer: Mesa DRI Intel 915GM x86/MMX/SSE2 v: 1.4 Mesa 18.3.6
direct render: Yes
Audio:
Device-1: Intel 82801FB/FBM/FR/FW/FRW AC97 Audio
vendor: Hewlett-Packard NX6110/NC6120 driver: snd_intel8x0 v: kernel
bus ID: 00:1e.2
Sound Server: ALSA v: k4.9.212-antix.1-486-smp
Network:
Device-1: Broadcom Limited BCM4318 [AirForce One 54g] 802.11g Wireless LAN
vendor: Hewlett-Packard driver: b43-pci-bridge v: N/A port: 2580
bus ID: 02:04.0
Device-2: Broadcom Limited BCM4401-B0 100Base-TX
vendor: Hewlett-Packard NX6110/NC6120 driver: b44 v: 2.0 port: 2580
bus ID: 02:0e.0
IF-ID-1: eth0 state: down mac: <filter>
IF-ID-2: wlan0 state: up mac: <filter>
Drives:
Local Storage: total: 55.89 GiB used: 3.92 GiB (7.0%)
ID-1: /dev/sda vendor: Hitachi model: IC25N060ATMR04-0 size: 55.89 GiB
Partition:
ID-1: / size: 9.07 GiB used: 3.81 GiB (42.0%) fs: ext4 dev: /dev/sda2
ID-2: swap-1 size: 2.59 GiB used: 119.1 MiB (4.5%) fs: swap dev: /dev/sda3
Sensors:
System Temperatures: cpu: 48.0 C mobo: 36.0 C
Fan Speeds (RPM): N/A
Info:
Processes: 137 Uptime: 57m Memory: 486.0 MiB used: 317.8 MiB (65.4%)
Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3
inxi: 3.0.36
_____________________________________________________________________________________

This should help you to understand my somewhat primitive but certainly workable situation.

I`m reviewing your posts and will be back to you this evening (GST +1)

Carrion-on til you are carrion . . .
PFO

[Member Raudonkepuris]

Deleted the config – same thing.

here’s the inxi output:

System:    Host: antix Kernel: 4.9.212-antix.1-486-smp i686 bits: 32 compiler: gcc v: 8.3.0 Desktop: dwm 6.1 
           Distro: antiX-19.2_386-core Hannie Schaft 27 March 2020 base: Debian GNU/Linux 10 (buster) 
Machine:   Type: Laptop System: FUJITSU SIEMENS product: AMILO PRO V2055 v: 20 serial: <filter> 
           Mobo: FUJITSU SIEMENS model: AMILO PRO V2055 v: 0.3A serial: <filter> BIOS: FUJITSU SIEMENS v: 1.0C-2A16-8A20 
           date: 07/21/2006 
Battery:   ID-1: BAT0 charge: 27.6 Wh condition: 27.6/48.8 Wh (57%) model: SMP SMP-LMXXSS6 status: Full 
CPU:       Topology: Single Core model: Intel Celeron M 410 bits: 32 type: MCP arch: M Yonah rev: 8 L2 cache: 1024 KiB 
           flags: nx pae sse sse2 sse3 bogomips: 2925 
           Speed: 1463 MHz min/max: N/A Core speed (MHz): 1: 1463 
Graphics:  Device-1: VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] vendor: Fujitsu Solutions driver: N/A 
           bus ID: 01:00.0 
           Display: server: X.Org 1.20.4 driver: openchrome unloaded: fbdev,modesetting,vesa resolution: 1280x800~60Hz 
           Message: Unable to show advanced data. Required tool glxinfo missing. 
Audio:     Device-1: VIA VT8233/A/8235/8237 AC97 Audio vendor: Fujitsu Solutions driver: snd_via82xx v: kernel bus ID: 00:11.5 
           Sound Server: ALSA v: k4.9.212-antix.1-486-smp 
Network:   Device-1: Broadcom Limited BCM4318 [AirForce One 54g] 802.11g Wireless LAN vendor: Gemtek driver: b43-pci-bridge 
           v: N/A bus ID: 00:06.0 
           Device-2: VIA VT6102/VT6103 [Rhine-II] vendor: Fujitsu Solutions driver: via-rhine v: N/A port: 2000 
           bus ID: 00:12.0 
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> 
           IF-ID-1: wlan0 state: down mac: <filter> 
Drives:    Local Storage: total: 55.89 GiB used: 9.61 GiB (17.2%) 
           ID-1: /dev/sda vendor: Fujitsu model: MHV2060BH size: 55.89 GiB 
Partition: ID-1: / size: 52.76 GiB used: 9.61 GiB (18.2%) fs: ext4 dev: /dev/sda1 
           ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 
Sensors:   Missing: Required tool sensors not installed. Check --recommends 
Info:      Processes: 112 Uptime: 56m Memory: 1.41 GiB used: 96.6 MiB (6.7%) Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 
           Shell: zsh v: 5.7.1 inxi: 3.0.36 

I just noticed that it’s not 19.3 but 19.2, I’ll go ahead and install 19.3 on my machine and report results after.

I’ve recently revived an old laptop with antix, now I’m trying to run retroarch on it. I installed it via this command that I found on their website:

sudo add-apt-repository ppa:libretro/stable && sudo apt-get update && sudo apt-get install retroarch*

but now I’m getting a weird error, this laptop has VN800 chipset, which in my mind shouldn’t be interfering with retroarch.

here’s the error:

[INFO] RetroArch 1.7.3 (Git b2ceb50)
[INFO] === Build =======================================
Capabilities: MMX MMXEXT SSE1 SSE2 SSE3 
Built: Jun  7 2018
[INFO] Version: 1.7.3
[INFO] Git: b2ceb50
[INFO] =================================================
[INFO] Environ SET_PIXEL_FORMAT: RGB565.
[INFO] Version of libretro API: 1
[INFO] Compiled against API: 1
[INFO] [Audio]: Set audio input rate to: 29970.03 Hz.
[INFO] [Video]: Video @ 960x720
[ERROR] [Wayland]: Failed to connect to Wayland server.
[INFO] [GLX]: GLX_OML_sync_control and GLX_MESA_swap_control supported, using better swap control method...
[INFO] [GL]: Found GL context: x
[INFO] [GL]: Detecting screen resolution 1280x800.
[INFO] [GLX]: Window manager is dwm.
[INFO] [GLX]: X = 0, Y = 0, W = 960, H = 720.
[INFO] [GLX]: Found swap function: glXSwapIntervalEXT.
[INFO] [GLX]: glXSwapIntervalEXT(1)
[INFO] [GL]: Vendor: VMware, Inc., Renderer: llvmpipe (LLVM 7.0, 128 bits).
[INFO] [GL]: Version: 3.1 Mesa 18.3.6.
[INFO] [GL]: Using resolution 698x775
[INFO] [GL]: Default shader backend found: glsl.
[INFO] [Shader driver]: Using GLSL shader backend.
[INFO] [GLSL]: Checking GLSL shader support ...
[WARN] [GL]: Stock GLSL shaders will be used.
[INFO] [GLSL]: Found GLSL vertex shader.
[INFO] [GLSL]: Found GLSL fragment shader.
[INFO] [GLSL]: Linking GLSL program.
[INFO] [GLSL]: Found GLSL vertex shader.
[INFO] [GLSL]: Found GLSL fragment shader.
[INFO] [GLSL]: Linking GLSL program.
[INFO] [GLSL]: Found GLSL vertex shader.
[INFO] [GLSL]: Found GLSL fragment shader.
[INFO] [GLSL]: Linking GLSL program.
[INFO] Setting up menu pipeline shaders for XMB ... 
[INFO] [GLSL]: Found GLSL vertex shader.
[INFO] [GLSL]: Found GLSL fragment shader.
[INFO] [GLSL]: Linking GLSL program.
[INFO] [GLSL]: Found GLSL vertex shader.
[INFO] [GLSL]: Found GLSL fragment shader.
[INFO] [GLSL]: Linking GLSL program.
[INFO] [GLSL]: Found GLSL vertex shader.
[INFO] [GLSL]: Found GLSL fragment shader.
[INFO] [GLSL]: Linking GLSL program.
[INFO] [GLSL]: Found GLSL vertex shader.
[INFO] [GLSL]: Found GLSL fragment shader.
[INFO] [GLSL]: Linking GLSL program.
[INFO] [GLSL]: Found GLSL vertex shader.
[INFO] [GLSL]: Found GLSL fragment shader.
[INFO] [GLSL]: Linking GLSL program.
[INFO] [GLSL]: Found GLSL vertex shader.
[INFO] [GLSL]: Found GLSL fragment shader.
[INFO] [GLSL]: Linking GLSL program.
[INFO] Resetting shader to defaults ... 
[INFO] [GL]: Using 4 textures.
[INFO] [GL]: Loaded 1 program(s).
[INFO] [GL]: Using GL_RGB565 for texture uploads.
[INFO] [Joypad]: Found joypad driver: "udev".
[INFO] [Font]: Using font rendering backend: freetype.
[INFO] [X11]: Suspending screensaver (X11, xdg-screensaver).
[INFO] [Video]: Found display server: x11
[INFO] [PulseAudio]: Requested 24576 bytes buffer, got 18432.
[INFO] [Menu]: Found menu display driver: "menu_display_gl".
[INFO] [Font]: Using font rendering backend: freetype.
[INFO] [Font]: Using font rendering backend: freetype.
[INFO] [LED]: LED driver = 'null' 0x86ad20
[INFO] SRAM will not be saved.
[INFO] Loading history file: [/home/user/.config/retroarch/content_history.lpl].
[INFO] Loading history file: [/home/user/.config/retroarch/content_favorites.lpl].
[INFO] Loading history file: [/home/user/.config/retroarch/content_music_history.lpl].
[INFO] Loading history file: [/home/user/.config/retroarch/content_video_history.lpl].
[INFO] Loading history file: [/home/user/.config/retroarch/content_image_history.lpl].
[INFO] [GL]: VSync => on
[INFO] [GLX]: glXSwapIntervalEXT(1)
[INFO] [PulseAudio]: Unpausing.
[INFO] [GL]: VSync => on
[INFO] [GLX]: glXSwapIntervalEXT(1)
[INFO] [PulseAudio]: Pausing.

what happens is that when I launch retro arch, it opens a new black window with the name “broken” hangs for a few seconds and closes.