-
Search Results
-
Askic
Hello,
recently I have installed antix in dual boot with windows XP on my old Ideapad S10e notebook. The existing HDD already had two partitions: NTFS for win XP and FAT32 for recovery.
Wehn installing antiX, I didn’t want to destroy existing system, so I used Gparted tool to create two additional paritions, for root and /home. I also left 2 GB unallocated space for linux swap.
I have installed antiX successfully and it works in dual boot with win XP without problems.However, when I tried later to format unallocated space as linux swap using Gparted tool, I got error message that max 4 primary partitions can exists.
Does it mean there is no possibility to add linux swap partition?
Currently there are four partitions, 2 for win Xp and 2 for antiX. Please have a look at the attached picture.
Since I don’t have linux swap partition, is it going to affect the performance of antix?- This topic was modified 2 years, 5 months ago by christophe. Reason: op stated solved
Attachments:
In reply to: Close lid – laptop hangs
dortega
Thank you for helping.
Yes, I remember trying to change this in acpi-support file
LID_SLEEP=false
It didn’t work. And it doesn’t work now. I did it right – I uncommented the line and changed to “false” then did a reboot. Even worse – somehow now my acpi-support file is blank! It wasn’t blank after the first reboot because I checked if the line remained the same. After the second reboot (reboot needed because I was checking if lid switch worked) I tried to press the lid switch WHILE the system was booting (and it hanged) – maybe it damaged the acpi-support file along the way (?)On GRUB the lid switch works. Screen blanks while the switch is pressed and then comes back.
As soon as the kernel boots pressing the lid switch hangs the system to the same black screen with mouse pointer.Here is my system info:
System:
Host: dell Kernel: 4.9.212-antix.1-486-smp i686 bits: 32 compiler: gcc
v: 8.3.0 Desktop: Fluxbox 1.3.7
Distro: antiX-19.2_386-full Hannie Schaft 27 March 2020
base: Debian GNU/Linux 10 (buster)
Machine:
Type: Portable System: Dell product: Latitude D505 v: N/A serial: <filter>
Mobo: Dell model: 0H2049 serial: <filter> BIOS: Dell v: A11
date: 11/03/2006
CPU:
Topology: Single Core model: Intel Pentium M bits: 32 type: MCP
arch: M Banias rev: 5 L2 cache: 1024 KiB
flags: sse sse2 bogomips: 2797
Speed: 1400 MHz min/max: 600/1400 MHz Core speed (MHz): 1: 1400
Graphics:
Device-1: Intel 82852/855GM Integrated Graphics vendor: Dell Latitude D505
driver: i915 v: kernel bus ID: 00:02.0
Display: x11 server: X.Org 1.20.4 driver: intel
unloaded: fbdev,modesetting,vesa resolution: 1024x768~60Hz
OpenGL: renderer: Mesa DRI Intel 852GM/855GM x86/MMX/SSE2
v: 1.3 Mesa 18.3.6 direct render: Yes
Audio:
Device-1: Intel 82801DB/DBL/DBM AC97 Audio vendor: Dell Latitude D505
driver: snd_intel8x0 v: kernel bus ID: 00:1f.5
Sound Server: ALSA v: k4.9.212-antix.1-486-smp
Network:
Device-1: Intel PRO/Wireless 2200BG [Calexico2] Network driver: ipw2200
v: 1.2.2kmprq port: d080 bus ID: 01:03.0
IF: eth1 state: up mac: <filter>
Device-2: Intel 82801DB PRO/100 VE Ethernet vendor: Dell Latitude D500
driver: e100 v: 3.5.24-k2-NAPI port: ecc0 bus ID: 01:08.0
IF: eth0 state: down mac: <filter>
Drives:
Local Storage: total: 55.90 GiB used: 7.48 GiB (13.4%)
ID-1: /dev/sda vendor: Samsung model: HM060HC size: 55.90 GiB
Partition:
ID-1: / size: 14.36 GiB used: 3.94 GiB (27.4%) fs: ext4 dev: /dev/sda1
ID-2: /home size: 36.51 GiB used: 3.54 GiB (9.7%) fs: ext4 dev: /dev/sda2
ID-3: swap-1 size: 3.91 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda3
Sensors:
System Temperatures: cpu: 51.0 C mobo: N/A
Fan Speeds (RPM): cpu: 2215
Info:
Processes: 148 Uptime: 1m Memory: 1.96 GiB used: 205.8 MiB (10.3%)
Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3
inxi: 3.0.36PPC
@Xecure – thinking about trying your antiX version on my parents old 32 bits laptop, I downloaded the iso and tried it as a live cd, on virtual box:
– Conky says it uses 70.4Mb out of the box
– Menus look fine, even the desktop entries
– I missed the Old log in screen picture!- it comes out every time, that’s not bad- it’s a nice security feature (that I myself don’t normally use) not using auto-log-on – it’s a tiny detail, I can change the log-on wallpaper to the blured lines one, to better match the default wallpaper (or change the default wallpaper to match the very nice log-on)
– Virtualbox video from the grub screen does not seem to work- safe video mode works fine- it even allows viewing youtube videos comfortably on smtube
– extremely fast and light on RAM!
– My virtual system has only half Gig of RAM- I did that on purpose, to test how antiX would behave that way- Firefox slows to a crawl in no time, because of heavy swap use- as is to be expected!
– I tried twice installing Palemoon- it freezes the system, after installing from package manager…
– It would be nice if we had some kind of portable office we could test in 32bits (LibreOffice appimages are 64 bits only)- since Palemoon gave me trouble on a VM, I won’t even try LO)
– As it is, except for the palemoon trouble (it could be VM related), it’s a nice, fast, light, and very legacy compatible system…EDIT: just to see how low this could go: I booted the live VM in min-fluxbox: “free -h” on rox-term reports “47Mb” being used đź !!! If this system doesn’t run on a computer it’s because it’s on the bottom of a trash compactor đ
P.
- This reply was modified 2 years, 5 months ago by PPC.
marcelocripe
Test on the computer that has the Gigabyte GA-8S661FXM-775 motherboard and SIS video card, using the ISO âantiX-19-legacy-bet1_386-base.isoâ
It worked similar to the test of the other motherboard with SIS video, flaws in the menus. And the video is similar to antiX 19.3 full 64 or 32 bytes in compatible video driver.
He did not display the message he had displayed on the other computer.
Due to the amount of memory of 512 MB, I was unable to play a video on Youtube with Firefox. The internet connection is via cable. Testing video and audio with MSTube, the video played with much higher quality than in Firefox. Consumption of RAM memory during the video in execution, according to Conky consumption of about 287 MB and in the htop consumption of RAM memory in about 323 MB and processing between 99.2 and 100%.
I had forgotten to report that in the three tests the audio and the cable network connection worked perfectly.
Thank you.
marcelocripe
(Original text in Brazilian Portuguese)———-
Teste no computador que possui a placa~mĂŁe Gigabyte GA-8S661FXM-775 e placa de vĂdeo SIS, utilizando a ISO âantiX-19-legacy-bet1_386-base.isoâ
Funcionou semelhante ao teste da outra placa mĂŁe com vĂdeo SIS, falhas nos menus. E o vĂdeo estĂĄ semelhante ao antiX 19.3 full 64 ou 32 bites em driver de vĂdeo compatĂvel.
NĂŁo exibiu a mensagem que havia exibido no outro computador.
Devido a quantidade de memĂłria de 512 MB, nĂŁo consegui tocar um vĂdeo no Youtube com o Firefox. A conexĂŁo com a internet Ă© via cabo. Teste de vĂdeo e ĂĄudio com o MSTube, o vĂdeo tocou com qualidade muito superior do que no Firefox. Consumo de memĂłria RAM durante o vĂdeo em execução, segundo o Conky consumo de cerca 287 MB e no htop consumo de memĂłria RAM em cerca de 323 MB e processamento entre 99.2 e 100%.
Eu havia me esquecido de informar que nos trĂȘs testes o ĂĄudio e a conexĂŁo de rede via cabo funcionaram perfeitamente.
Muito obrigado.
marcelocripe
(Texto original em PortuguĂȘs do Brasil)demo@antix1:~ $ inxi -Fxz System: Host: antix1 Kernel: 4.4.240-antix.2-486-smp i686 bits: 32 compiler: gcc v: 8.3.0 Desktop: IceWM 1.9.2 Distro: antiX-19-legacy-bet1_386-base Lazarus 23 November 2020 base: Debian GNU/Linux 10 (buster) Machine: Type: Desktop System: Hewlett-Packard product: HP dx2090 MT (AA123AV) v: N/A serial: <filter> Mobo: Hewlett-Packard model: 0A30 serial: <filter> BIOS: Award v: F12 date: 04/25/2006 CPU: Topology: Single Core model: Intel Celeron bits: 64 type: MCP arch: Netburst Smithfield rev: 9 L2 cache: 256 KiB flags: lm nx pae sse sse2 sse3 bogomips: 6401 Speed: 3201 MHz min/max: N/A Core speed (MHz): 1: 3201 Graphics: Device-1: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter vendor: Gigabyte SiS661FX GUI 2D/3D Accelerator driver: N/A bus ID: 01:00.0 Display: x11 server: X.Org 1.16.4 driver: fbdev unloaded: modesetting,vesa resolution: 1024x768~N/A OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.1 Mesa 18.3.6 direct render: Yes Audio: Device-1: Silicon Integrated Systems [SiS] SiS7012 AC97 Sound vendor: Gigabyte driver: snd_intel8x0 v: kernel bus ID: 00:02.7 Sound Server: ALSA v: k4.4.240-antix.2-486-smp Network: Device-1: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet vendor: Gigabyte driver: sis900 v: kernel port: a800 bus ID: 00:04.0 IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> Drives: Local Storage: total: 7.27 GiB used: 14.4 MiB (0.2%) ID-1: /dev/sda type: USB vendor: Kingston model: DT 101 G2 size: 7.27 GiB Partition: ID-1: / size: 320.0 MiB used: 2.4 MiB (0.8%) fs: overlay source: ERR-102 Sensors: Message: No sensors data was found. Is sensors configured? Info: Processes: 118 Uptime: 9m Memory: 429.8 MiB used: 83.8 MiB (19.5%) Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.36 demo@antix1:~ $ inxi -G Graphics: Device-1: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter driver: N/A Display: x11 server: X.Org 1.16.4 driver: fbdev unloaded: modesetting,vesa resolution: 1024x768~N/A OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.1 Mesa 18.3.6 demo@antix1:~ $ inxi -v8 System: Host: antix1 Kernel: 4.4.240-antix.2-486-smp i686 bits: 32 compiler: gcc v: 8.3.0 parameters: vga=0x0317 lang=pt_BR tz=America/Sao_Paulo quiet splasht disable=lx Desktop: IceWM 1.9.2 dm: SLiM 1.3.6 Distro: antiX-19-legacy-bet1_386-base Lazarus 23 November 2020 base: Debian GNU/Linux 10 (buster) Machine: Type: Desktop System: Hewlett-Packard product: HP dx2090 MT (AA123AV) v: N/A serial: <root required> Chassis: type: 3 serial: <root required> Mobo: Hewlett-Packard model: 0A30 serial: <root required> BIOS: Award v: F12 date: 04/25/2006 Memory: RAM: total: 429.8 MiB used: 87.7 MiB (20.4%) RAM Report: permissions: Unable to run dmidecode. Root privileges required. PCI Slots: Permissions: Unable to run dmidecode. Root privileges required. CPU: Topology: Single Core model: Intel Celeron bits: 64 type: MCP arch: Netburst Smithfield family: F (15) model-id: 4 stepping: 9 microcode: 3 L2 cache: 256 KiB bogomips: 6401 Speed: 3201 MHz min/max: N/A Core speed (MHz): 1: 3201 Flags: acpi apic bts cid clflush cmov constant_tsc cx16 cx8 de ds_cpl dtes64 dts fpu fxsr ht lahf_lm lm mca mce mmx monitor msr mtrr nx pae pat pbe pebs pge pni pse pse36 sep ss sse sse2 tm tm2 tsc vme xtpr Vulnerabilities: Type: itlb_multihit status: Processor vulnerable Type: l1tf status: Vulnerable Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled Type: meltdown status: Vulnerable Type: spec_store_bypass status: Vulnerable Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling Type: srbds status: Not affected Type: tsx_async_abort status: Not affected Graphics: Device-1: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter vendor: Gigabyte SiS661FX GUI 2D/3D Accelerator driver: N/A bus ID: 01:00.0 chip ID: 1039:6330 Display: x11 server: X.Org 1.16.4 driver: fbdev unloaded: modesetting,vesa alternate: sis resolution: 1024x768~N/A OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.1 Mesa 18.3.6 direct render: Yes Audio: Device-1: Silicon Integrated Systems [SiS] SiS7012 AC97 Sound vendor: Gigabyte driver: snd_intel8x0 v: kernel bus ID: 00:02.7 chip ID: 1039:7012 Sound Server: ALSA v: k4.4.240-antix.2-486-smp Network: Device-1: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet vendor: Gigabyte driver: sis900 v: kernel port: a800 bus ID: 00:04.0 chip ID: 1039:0900 IF: eth0 state: up speed: 100 Mbps duplex: full mac: XX:XX:XX:XX:XX:XX (I changed the MAC to XX/ Eu alterei o MAC para XX) IP v4: 192.168.0.106/24 scope: global broadcast: 192.168.0.255 IP v6: fe80::20f:eaff:fed1:9e59/64 scope: link WAN IP: 138.99.61.252 Drives: Local Storage: total: 7.27 GiB used: 14.4 MiB (0.2%) ID-1: /dev/sda type: USB vendor: Kingston model: DT 101 G2 size: 7.27 GiB block size: physical: 512 B logical: 512 B serial: 001CC0EC330FEB816605000A rev: PMAP scheme: MBR Floppy-1: /dev/fd0 Optical-1: /dev/sr0 vendor: TSSTcorp model: CDDVDW SH-S223C rev: SB04 dev-links: cdrom,cdrw,dvd,dvdrw Features: speed: 52 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram state: running RAID: Message: No RAID data was found. Partition: ID-1: / raw size: N/A size: 320.0 MiB used: 2.4 MiB (0.8%) fs: overlay source: ERR-102 label: N/A uuid: N/A ID-2: /live/boot-dev raw size: 767.0 MiB size: <root required> used: <root required> fs: N/A dev: /dev/ventoy label: N/A uuid: N/A ID-3: /live/linux raw size: 736.9 MiB size: <root required> used: <root required> fs: squashfs dev: /dev/loop0 label: N/A uuid: N/A ID-4: /media/VTOYEFI raw size: 32.0 MiB size: 31.9 MiB (99.75%) used: 12.0 MiB (37.4%) fs: vfat dev: /dev/sda2 label: VTOYEFI uuid: ADB8-4480 Unmounted: ID-1: /dev/dm-0 size: 767.0 MiB fs: <root required> label: N/A uuid: N/A ID-2: /dev/sda1 size: 7.24 GiB fs: exfat label: Ventoy uuid: 4E21-0000 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-4:2 info: Toshiba Kingston DataTraveler 102/2.0 / HEMA Flash Drive 2 GB / PNY Attache 4GB Stick type: Mass Storage driver: usb-storage interfaces: 1 rev: 2.0 speed: 480 Mb/s chip ID: 0930:6545 serial: 001CC0EC330FEB816605000A Hub: 2-0:1 info: Full speed (or root) Hub ports: 3 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001 Hub: 3-0:1 info: Full speed (or root) Hub ports: 3 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 Sensors: Message: No sensors data was found. Is sensors configured? Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list 1: deb http://repo.antixlinux.com/buster buster main nonfree nosystemd 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.br.debian.org/debian/ buster-updates main contrib non-free Active apt repos in: /etc/apt/sources.list.d/debian.list 1: deb http://ftp.br.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: 1.8% command: slim pid: 3194 mem: 9.81 MiB (2.2%) 2: cpu: 1.4% command: x pid: 3232 mem: 38.6 MiB (8.9%) 3: cpu: 0.5% command: conky pid: 3421 mem: 10.2 MiB (2.3%) 4: cpu: 0.4% command: icewm pid: 3321 mem: 13.2 MiB (3.0%) 5: cpu: 0.3% command: rox pid: 3419 mem: 24.8 MiB (5.7%) Memory top: 5 1: mem: 38.6 MiB (8.9%) command: x pid: 3232 cpu: 1.4% 2: mem: 25.5 MiB (5.9%) command: roxterm pid: 3630 cpu: 0.2% 3: mem: 24.8 MiB (5.7%) command: rox pid: 3419 cpu: 0.3% 4: mem: 16.6 MiB (3.8%) command: volumeicon pid: 3346 cpu: 0.0% 5: mem: 13.4 MiB (3.1%) command: fbxkb pid: 3360 cpu: 0.0% Info: Processes: 118 Uptime: 9m 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 demo@antix1:~ $ inxi -v CPU: Single Core Intel Celeron (-MCP-) speed: 3201 MHz Kernel: 4.4.240-antix.2-486-smp i686 Up: 9m Mem: 83.3/429.8 MiB (19.4%) Storage: 7.27 GiB (0.2% used) Procs: 118 Shell: bash 5.0.3 inxi: 3.0.36 demo@antix1:~ $ lspci -v 00:00.0 Host bridge: Silicon Integrated Systems [SiS] 661FX/M661FX/M661MX Host (rev 11) Subsystem: Silicon Integrated Systems [SiS] 661FX/M661FX/M661MX Host Flags: bus master, medium devsel, latency 32 Memory at e8000000 (32-bit, non-prefetchable) Capabilities: <access denied> Kernel driver in use: agpgart-sis Kernel modules: sis_agp 00:01.0 PCI bridge: Silicon Integrated Systems [SiS] AGP Port (virtual PCI-to-PCI bridge) (prog-if 00 [Normal decode]) Flags: bus master, 66MHz, fast devsel, latency 32 Bus: primary=00, secondary=01, subordinate=01, sec-latency=32 I/O behind bridge: 00009000-00009fff Memory behind bridge: ed000000-ed0fffff Prefetchable memory behind bridge: e0000000-e7ffffff Kernel modules: shpchp 00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS964 [MuTIOL Media IO] LPC Controller (rev 36) Flags: bus master, medium devsel, latency 0 Kernel modules: i2c_sis630 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 IDE Controller (rev 01) (prog-if 80 [ISA Compatibility mode-only controller, supports bus mastering]) Subsystem: Gigabyte Technology Co., Ltd 5513 IDE Controller Flags: bus master, medium devsel, latency 32, IRQ 16 I/O ports at 01f0 I/O ports at 03f4 I/O ports at 0170 I/O ports at 0374 I/O ports at f000 Kernel driver in use: pata_sis 00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] SiS7012 AC'97 Sound Controller (rev a0) Subsystem: Gigabyte Technology Co., Ltd SiS7012 AC'97 Sound Controller Flags: bus master, medium devsel, latency 32, IRQ 18 I/O ports at a000 I/O ports at a400 Capabilities: <access denied> Kernel driver in use: snd_intel8x0 Kernel modules: snd_intel8x0 00:03.0 USB controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f) (prog-if 10 [OHCI]) Subsystem: Gigabyte Technology Co., Ltd USB 1.1 Controller Flags: bus master, medium devsel, latency 32, IRQ 20 Memory at ed104000 (32-bit, non-prefetchable) Kernel driver in use: ohci-pci 00:03.1 USB controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f) (prog-if 10 [OHCI]) Subsystem: Gigabyte Technology Co., Ltd USB 1.1 Controller Flags: bus master, medium devsel, latency 32, IRQ 21 Memory at ed100000 (32-bit, non-prefetchable) Kernel driver in use: ohci-pci 00:03.2 USB controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f) (prog-if 10 [OHCI]) Subsystem: Gigabyte Technology Co., Ltd USB 1.1 Controller Flags: bus master, medium devsel, latency 32, IRQ 22 Memory at ed101000 (32-bit, non-prefetchable) Kernel driver in use: ohci-pci 00:03.3 USB controller: Silicon Integrated Systems [SiS] USB 2.0 Controller (prog-if 20 [EHCI]) Subsystem: Gigabyte Technology Co., Ltd USB 2.0 Controller Flags: bus master, medium devsel, latency 32, IRQ 23 Memory at ed102000 (32-bit, non-prefetchable) Capabilities: <access denied> Kernel driver in use: ehci-pci 00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 90) Subsystem: Gigabyte Technology Co., Ltd SiS900 PCI Fast Ethernet Flags: bus master, medium devsel, latency 64, IRQ 19 I/O ports at a800 Memory at ed103000 (32-bit, non-prefetchable) [virtual] Expansion ROM at 1c000000 [disabled] Capabilities: <access denied> Kernel driver in use: sis900 Kernel modules: sis900 00:05.0 IDE interface: Silicon Integrated Systems [SiS] RAID bus controller 180 SATA/PATA [SiS] (rev 01) (prog-if 85 [PCI native mode-only controller, supports bus mastering]) Subsystem: Gigabyte Technology Co., Ltd RAID bus controller 180 SATA/PATA [SiS] Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 17 I/O ports at ac00 I/O ports at b000 I/O ports at b400 I/O ports at b800 I/O ports at bc00 I/O ports at c000 Capabilities: <access denied> Kernel driver in use: sata_sis 00:0b.0 Modem: Motorola SM56 Data Fax Modem (rev 04) (prog-if 00 [Generic]) Subsystem: Motorola SM56 Data Fax Modem Flags: stepping, medium devsel, IRQ 19 Memory at ed105000 (32-bit, non-prefetchable) I/O ports at c400 Capabilities: <access denied> 01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd SiS661FX GUI 2D/3D Accelerator Flags: 66MHz, medium devsel, IRQ 5 BIST result: 00 Memory at e0000000 (32-bit, prefetchable) Memory at ed000000 (32-bit, non-prefetchable) I/O ports at 9000 Expansion ROM at <unassigned> [disabled] Capabilities: <access denied> demo@antix1:~ $ cat/proc/cmdline bash: cat/proc/cmdline: Arquivo ou diretĂłrio inexistente demo@antix1:~marcelocripe
Test on the computer that has the Asus P5V800-MX motherboard and VIA graphics card, using the ISO “antiX-19-legacy-bet1_386-base.iso”
It worked even better than with SIS video, less flaws in the menus. And the video is similar to antiX 19.3 full 64 or 32 bytes in compatible video driver.
Did not display the message you had displayed on the other computer
I repeated the test, playing a 21 min YouTube video with Firefox, with an internet connection via cable. The video played at a low quality, but for computer specifications, it was excellent. Consumption of RAM memory during the video being played, according to Conky consumption of approximately 395 MB and in the htop consumption of RAM memory of approximately 450 MB and processing at 100%. The purpose of this test with Youtube directly in the browser is to simulate a user action where it forces the computer to the maximum.
marcelocripe
(Original text in Brazilian Portuguese)———-
Teste no computador que possui a placa~mĂŁe Asus P5V800-MX e placa de vĂdeo VIA, utilizando a ISO “antiX-19-legacy-bet1_386-base.iso”
Funcionou ainda melhor do que com o vĂdeo SIS, menos falhas nos menus. E o vĂdeo estĂĄ semelhante ao antiX 19.3 full 64 ou 32 bites em driver de vĂdeo compatĂvel.
NĂŁo exibiu a mensagem que havia exibido no outro computador
Eu repeti o teste, tocando um vĂdeo no Youtube de 21 min com o Firefox, com conexĂŁo Ă internet via cabo. O vĂdeo tocou com uma qualidade baixa, mas para as especificaçÔes do computador, ficou excelente. Consumo de memĂłria RAM durante o vĂdeo em execução, segundo o Conky consumo de cerca 395 MB e no htop consumo de memĂłria RAM em cerca de 450 MB e processamento em 100%. O objetivo deste teste com o Youtube diretamente no navegador Ă© de simular uma ação do usuĂĄrio onde força o computador ao mĂĄximo.
marcelocripe
(Texto original em PortuguĂȘs do Brasil)demo@antix1:~ $ inxi -Fxz System: Host: antix1 Kernel: 4.4.240-antix.2-486-smp i686 bits: 32 compiler: gcc v: 8.3.0 Desktop: IceWM 1.9.2 Distro: antiX-19-legacy-bet1_386-base Lazarus 23 November 2020 base: Debian GNU/Linux 10 (buster) Machine: Type: Desktop Mobo: ASUSTeK model: P5V800-MX v: Rev 1.xx serial: <filter> BIOS: American Megatrends v: 0802 date: 07/12/2006 CPU: Topology: Single Core model: Intel Celeron bits: 64 type: MCP arch: Netburst Smithfield rev: 9 L2 cache: 256 KiB flags: lm pae sse sse2 sse3 bogomips: 5054 Speed: 2527 MHz min/max: N/A Core speed (MHz): 1: 2527 Graphics: Device-1: VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] vendor: ASUSTeK driver: N/A bus ID: 01:00.0 Display: x11 server: X.Org 1.16.4 driver: openchrome unloaded: fbdev,modesetting,vesa resolution: 800x600~85Hz OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.1 Mesa 18.3.6 direct render: Yes Audio: Device-1: VIA VT8237A/VT8251 HDA vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 02:01.0 Sound Server: ALSA v: k4.4.240-antix.2-486-smp Network: Device-1: VIA VT6102/VT6103 [Rhine-II] vendor: ASUSTeK A7V600-X driver: via-rhine v: N/A port: d400 bus ID: 00:12.0 IF: eth0 state: down mac: <filter> Drives: Local Storage: total: 81.80 GiB used: 14.4 MiB (0.0%) ID-1: /dev/sda vendor: Maxtor model: STM380815AS size: 74.53 GiB ID-2: /dev/sdb type: USB vendor: Kingston model: DT 101 G2 size: 7.27 GiB Partition: ID-1: / size: 724.0 MiB used: 2.4 MiB (0.3%) fs: overlay source: ERR-102 ID-2: swap-1 size: 1.89 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda3 Sensors: Message: No sensors data was found. Is sensors configured? Info: Processes: 123 Uptime: 9m Memory: 936.3 MiB used: 87.7 MiB (9.4%) Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.36 demo@antix1:~ $ inxi -G Graphics: Device-1: VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] driver: N/A Display: x11 server: X.Org 1.16.4 driver: openchrome unloaded: fbdev,modesetting,vesa resolution: 800x600~85Hz OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.1 Mesa 18.3.6 demo@antix1:~ $ inxi -v8 System: Host: antix1 Kernel: 4.4.240-antix.2-486-smp i686 bits: 32 compiler: gcc v: 8.3.0 parameters: vga=0x0317 lang=pt_BR tz=America/Sao_Paulo quiet splasht disable=lx Desktop: IceWM 1.9.2 dm: SLiM 1.3.6 Distro: antiX-19-legacy-bet1_386-base Lazarus 23 November 2020 base: Debian GNU/Linux 10 (buster) Machine: Type: Desktop Mobo: ASUSTeK model: P5V800-MX v: Rev 1.xx serial: <root required> BIOS: American Megatrends v: 0802 date: 07/12/2006 Memory: RAM: total: 936.3 MiB used: 91.8 MiB (9.8%) RAM Report: permissions: Unable to run dmidecode. Root privileges required. PCI Slots: Permissions: Unable to run dmidecode. Root privileges required. CPU: Topology: Single Core model: Intel Celeron bits: 64 type: MCP arch: Netburst Smithfield family: F (15) model-id: 4 stepping: 9 microcode: 3 L2 cache: 256 KiB bogomips: 5054 Speed: 2527 MHz min/max: N/A Core speed (MHz): 1: 2527 Flags: acpi apic bts cid clflush cmov constant_tsc cx16 cx8 de ds_cpl dtes64 dts fpu fxsr ht lahf_lm lm mca mce mmx monitor msr mtrr pae pat pbe pebs pge pni pse pse36 sep ss sse sse2 tm tm2 tsc vme xtpr Vulnerabilities: Type: itlb_multihit status: Processor vulnerable Type: l1tf status: Vulnerable Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled Type: meltdown status: Vulnerable Type: spec_store_bypass status: Vulnerable Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling Type: srbds status: Not affected Type: tsx_async_abort status: Not affected Graphics: Device-1: VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] vendor: ASUSTeK driver: N/A bus ID: 01:00.0 chip ID: 1106:3344 Display: x11 server: X.Org 1.16.4 driver: openchrome unloaded: fbdev,modesetting,vesa resolution: 800x600~85Hz OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.1 Mesa 18.3.6 direct render: Yes Audio: Device-1: VIA VT8237A/VT8251 HDA vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 02:01.0 chip ID: 1106:3288 Sound Server: ALSA v: k4.4.240-antix.2-486-smp Network: Device-1: VIA VT6102/VT6103 [Rhine-II] vendor: ASUSTeK A7V600-X driver: via-rhine v: N/A port: d400 bus ID: 00:12.0 chip ID: 1106:3065 IF: eth0 state: down mac: XX:XX:XX:XX:XX:XX (I changed the MAC to XX/ Eu alterei o MAC para XX) WAN IP: No WAN IP data found. Connected to the web? SSL issues? Drives: Local Storage: total: 81.80 GiB used: 14.4 MiB (0.0%) ID-1: /dev/sda vendor: Maxtor model: STM380815AS size: 74.53 GiB block size: physical: 512 B logical: 512 B speed: 3.0 Gb/s serial: 5RA8KAGS rev: B scheme: MBR ID-2: /dev/sdb type: USB vendor: Kingston model: DT 101 G2 size: 7.27 GiB block size: physical: 512 B logical: 512 B serial: 001CC0EC330FEB816605000A rev: PMAP scheme: MBR Floppy-1: /dev/fd0 Optical-1: /dev/sr0 vendor: HL-DT-ST model: DVD-RAM GSA-H54N rev: 1.00 dev-links: cdrom,cdrw,dvd,dvdrw Features: speed: 1 multisession: yes audio: yes dvd: no rw: none state: running RAID: Message: No RAID data was found. Partition: ID-1: / raw size: N/A size: 724.0 MiB used: 2.4 MiB (0.3%) fs: overlay source: ERR-102 label: N/A uuid: N/A ID-2: /live/boot-dev raw size: 767.0 MiB size: <root required> used: <root required> fs: N/A dev: /dev/ventoy label: N/A uuid: N/A ID-3: /live/linux raw size: 736.9 MiB size: <root required> used: <root required> fs: squashfs dev: /dev/loop0 label: N/A uuid: N/A ID-4: /media/VTOYEFI raw size: 32.0 MiB size: 31.9 MiB (99.75%) used: 12.0 MiB (37.4%) fs: vfat dev: /dev/sdb2 label: VTOYEFI uuid: ADB8-4480 ID-5: swap-1 size: 1.89 GiB used: 0 KiB (0.0%) fs: swap swappiness: 60 (default) cache pressure: 100 (default) dev: /dev/sda3 label: N/A uuid: e33c0fb1-fafa-4a12-b1f8-8c17b554a89d Unmounted: ID-1: /dev/dm-0 size: 767.0 MiB fs: <root required> label: N/A uuid: N/A ID-2: /dev/sda1 size: 36.32 GiB fs: ext4 label: N/A uuid: f495c019-7e84-41d4-98ac-ef47d3bb2467 ID-3: /dev/sda2 size: 36.32 GiB fs: ext4 label: rootantiX19 uuid: b581b717-125a-4e5e-af99-9801969e56b0 ID-4: /dev/sdb1 size: 7.24 GiB fs: exfat label: Ventoy uuid: 4E21-0000 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-4:4 info: Toshiba Kingston DataTraveler 102/2.0 / HEMA Flash Drive 2 GB / PNY Attache 4GB Stick type: Mass Storage driver: usb-storage interfaces: 1 rev: 2.0 speed: 480 Mb/s chip ID: 0930:6545 serial: 001CC0EC330FEB816605000A Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001 Device-2: 2-1:2 info: Dell RT7D50 Keyboard type: Keyboard driver: hid-generic,usbhid interfaces: 1 rev: 1.1 speed: 1.5 Mb/s chip ID: 413c:2005 Device-3: 2-2:3 info: Trust B.V. Optical Mouse type: Mouse driver: hid-generic,usbhid interfaces: 1 rev: 1.1 speed: 1.5 Mb/s chip ID: 15d9:0a4f 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: Message: No sensors data was found. Is sensors configured? Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list 1: deb http://repo.antixlinux.com/buster buster main nonfree nosystemd 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.br.debian.org/debian/ buster-updates main contrib non-free Active apt repos in: /etc/apt/sources.list.d/debian.list 1: deb http://ftp.br.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: 2.5% command: slim pid: 3346 mem: 10.0 MiB (1.0%) 2: cpu: 2.5% command: x pid: 3377 mem: 40.2 MiB (4.2%) 3: cpu: 0.9% command: conky pid: 3573 mem: 10.1 MiB (1.0%) 4: cpu: 0.6% command: icewm pid: 3473 mem: 12.9 MiB (1.3%) 5: cpu: 0.4% command: rox pid: 3580 mem: 24.7 MiB (2.6%) Memory top: 5 1: mem: 40.2 MiB (4.2%) command: x pid: 3377 cpu: 2.5% 2: mem: 26.2 MiB (2.7%) command: roxterm pid: 4040 cpu: 0.4% 3: mem: 24.7 MiB (2.6%) command: rox pid: 3580 cpu: 0.4% 4: mem: 16.5 MiB (1.7%) command: volumeicon pid: 3497 cpu: 0.1% 5: mem: 13.0 MiB (1.3%) command: fbxkb pid: 3511 cpu: 0.1% Info: Processes: 123 Uptime: 11m 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 demo@antix1:~ $ inxi -v CPU: Single Core Intel Celeron (-MCP-) speed: 2527 MHz Kernel: 4.4.240-antix.2-486-smp i686 Up: 12m Mem: 87.5/936.3 MiB (9.3%) Storage: 81.80 GiB (0.0% used) Procs: 123 Shell: bash 5.0.3 inxi: 3.0.36 demo@antix1:~ $ lspci -v 00:00.0 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge Subsystem: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge Flags: bus master, medium devsel, latency 8 Memory at f0000000 (32-bit, prefetchable) Capabilities: <access denied> Kernel driver in use: agpgart-via Kernel modules: via_agp 00:00.1 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge Subsystem: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge Flags: bus master, medium devsel, latency 0 00:00.2 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge Subsystem: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge Flags: bus master, medium devsel, latency 0 00:00.3 Host bridge: VIA Technologies, Inc. PT890 Host Bridge Flags: bus master, medium devsel, latency 0 Kernel modules: via_agp 00:00.4 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge Subsystem: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge Flags: bus master, medium devsel, latency 0 00:00.7 Host bridge: VIA Technologies, Inc. CN700/VN800/P4M800CE/Pro Host Bridge Flags: bus master, medium devsel, latency 0 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237/VX700 PCI Bridge (prog-if 00 [Normal decode]) Flags: bus master, 66MHz, medium devsel, latency 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 Memory behind bridge: fc900000-fe9fffff Prefetchable memory behind bridge: d7f00000-dfefffff Capabilities: <access denied> Kernel modules: shpchp 00:0f.0 IDE interface: VIA Technologies, Inc. VT8251 AHCI/SATA 4-Port Controller (prog-if 8f [PCI native mode controller, supports both channels switched to ISA compatibility mode, supports bus mastering]) Subsystem: VIA Technologies, Inc. VT8251 AHCI/SATA 4-Port Controller Flags: bus master, medium devsel, latency 64, IRQ 26 I/O ports at ec00 I/O ports at e880 I/O ports at e800 I/O ports at e480 I/O ports at e400 Memory at febffc00 (32-bit, non-prefetchable) Capabilities: <access denied> Kernel driver in use: ahci 00:0f.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 07) (prog-if 8a [ISA Compatibility mode controller, supports both channels switched to PCI native mode, supports bus mastering]) Subsystem: VIA Technologies, Inc. VT82C586/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE Flags: bus master, medium devsel, latency 32 [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [virtual] Memory at 000003f0 (type 3, non-prefetchable) [virtual] Memory at 00000170 (32-bit, non-prefetchable) [virtual] Memory at 00000370 (type 3, non-prefetchable) I/O ports at fc00 Capabilities: <access denied> Kernel driver in use: pata_via 00:10.0 USB controller: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller (rev 90) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller Flags: bus master, medium devsel, latency 64, IRQ 20 I/O ports at e080 Capabilities: <access denied> Kernel driver in use: uhci_hcd 00:10.1 USB controller: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller (rev 90) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller Flags: bus master, medium devsel, latency 64, IRQ 22 I/O ports at e000 Capabilities: <access denied> Kernel driver in use: uhci_hcd 00:10.2 USB controller: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller (rev 90) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller Flags: bus master, medium devsel, latency 64, IRQ 21 I/O ports at dc00 Capabilities: <access denied> Kernel driver in use: uhci_hcd 00:10.3 USB controller: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller (rev 90) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. VT82xx/62xx UHCI USB 1.1 Controller Flags: bus master, medium devsel, latency 64, IRQ 23 I/O ports at d880 Capabilities: <access denied> Kernel driver in use: uhci_hcd 00:10.4 USB controller: VIA Technologies, Inc. USB 2.0 (rev 90) (prog-if 20 [EHCI]) Subsystem: VIA Technologies, Inc. USB 2.0 Controller Flags: bus master, medium devsel, latency 64, IRQ 22 Memory at febff800 (32-bit, non-prefetchable) Capabilities: <access denied> Kernel driver in use: ehci-pci 00:11.0 ISA bridge: VIA Technologies, Inc. VT8251 PCI to ISA Bridge Subsystem: VIA Technologies, Inc. VT8251 PCI to ISA Bridge Flags: medium devsel Capabilities: <access denied> Kernel modules: i2c_viapro 00:11.7 Host bridge: VIA Technologies, Inc. VT8237/8251 Ultra VLINK Controller Subsystem: VIA Technologies, Inc. VT8237/8251 Ultra VLINK Controller Flags: bus master, medium devsel, latency 128 Capabilities: <access denied> 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102/VT6103 [Rhine-II] (rev 7c) Subsystem: ASUSTeK Computer Inc. A7V600-X Motherboard Flags: bus master, medium devsel, latency 64, IRQ 23 I/O ports at d400 Memory at febff400 (32-bit, non-prefetchable) Capabilities: <access denied> Kernel driver in use: via-rhine Kernel modules: via_rhine 00:13.0 PCI bridge: VIA Technologies, Inc. VT8251 Host Bridge (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=04, sec-latency=0 Memory behind bridge: fea00000-feafffff Kernel modules: shpchp 00:13.1 PCI bridge: VIA Technologies, Inc. VT8251 PCI to PCI Bridge (prog-if 01 [Subtractive decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=05, subordinate=05, sec-latency=0 01:00.0 VGA compatible controller: VIA Technologies, Inc. CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] (rev 01) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 11 Memory at d8000000 (32-bit, prefetchable) Memory at fd000000 (32-bit, non-prefetchable) Expansion ROM at fe9f0000 [disabled] Capabilities: <access denied> 02:00.0 PCI bridge: VIA Technologies, Inc. VT8251 PCIE Root Port (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 24 Bus: primary=02, secondary=03, subordinate=03, sec-latency=0 Capabilities: <access denied> Kernel driver in use: pcieport Kernel modules: shpchp 02:00.1 PCI bridge: VIA Technologies, Inc. VT8251 PCIE Root Port (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 25 Bus: primary=02, secondary=04, subordinate=04, sec-latency=0 Capabilities: <access denied> Kernel driver in use: pcieport Kernel modules: shpchp 02:01.0 Audio device: VIA Technologies, Inc. VT8237A/VT8251 HDA Controller Subsystem: ASUSTeK Computer Inc. VT8237A/VT8251 HDA Controller Flags: bus master, fast devsel, latency 0, IRQ 27 Memory at feafc000 (32-bit, non-prefetchable) Capabilities: <access denied> Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel demo@antix1:~ $ cat/proc/cmdline bash: cat/proc/cmdline: Arquivo ou diretĂłrio inexistenteIn reply to: No Sound
omx
New user alert!
Same problem, how might I get sound working,,, thanks
System:
Host: antix1 Kernel: 4.9.235-antix.1-amd64-smp x86_64 bits: 64
compiler: gcc v: 8.3.0 Desktop: IceWM 1.9.2
Distro: antiX-19.3_x64-base Manolis Glezos 14 October 2020
base: Debian GNU/Linux 10 (buster)
Machine:
Type: Desktop Mobo: Gigabyte model: GA-890GPA-UD3H v: x.x serial: <filter>
BIOS: Award v: FA date: 04/07/2010
CPU:
Topology: Quad Core model: AMD Phenom II X4 965 bits: 64 type: MCP
arch: K10 rev: 3 L2 cache: 2048 KiB
flags: lm nx pae sse sse2 sse3 sse4a svm bogomips: 27319
Speed: 2200 MHz min/max: 800/3400 MHz Core speeds (MHz): 1: 2200 2: 3400
3: 800 4: 800
Graphics:
Device-1: NVIDIA G98 [Quadro NVS 450] driver: nouveau v: kernel
bus ID: 03:00.0
Device-2: NVIDIA G98 [Quadro NVS 450] driver: nouveau v: kernel
bus ID: 04:00.0
Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa
resolution: 1920×1080~60Hz, 1920×1080~60Hz
OpenGL: renderer: NV98 v: 3.3 Mesa 18.3.6 direct render: Yes
Audio:
Device-1: AMD SBx00 Azalia vendor: Gigabyte driver: snd_hda_intel
v: kernel bus ID: 00:14.2
Sound Server: ALSA v: k4.9.235-antix.1-amd64-smp
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
vendor: Gigabyte driver: r8169 v: 2.3LK-NAPI port: be00 bus ID: 06:00.0
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Ralink RT3062 Wireless 802.11n 2T/2R driver: rt2800pci v: 2.3.0
port: be00 bus ID: 07:07.0
IF: wlan0 state: down mac: <filter>
Drives:
Local Storage: total: 585.00 GiB used: 2.97 GiB (0.5%)
ID-1: /dev/sda vendor: SanDisk model: SDSSDP128G size: 119.24 GiB
ID-2: /dev/sdb vendor: Seagate model: ST500DM002-1BD142 size: 465.76 GiB
Partition:
ID-1: / size: 114.87 GiB used: 2.97 GiB (2.6%) fs: ext4 dev: /dev/sda1
ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2
Sensors:
System Temperatures: cpu: 51.1 C mobo: N/A
Fan Speeds (RPM): N/A
GPU: device: nouveau temp: 76 C device: nouveau temp: 72 C
Info:
Processes: 202 Uptime: 3h 29m Memory: 5.83 GiB used: 922.9 MiB (15.5%)
Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3
inxi: 3.0.36Topic: Installation completed error
grudovoff
Hello everyone I’m new to Linux and decided to try AntiX (I used to sit on Manjaro XFCE). Used automatic disk partitioning and at the end of the installation gave an error related to GRUB: “GRUB installation failed. You can reboot to the live medium and use the GRUB Rescue menu to repair the installation.”
QSI:System: Host: antix1 Kernel: 4.9.235-antix.1-486-smp i686 bits: 32 compiler: gcc v: 8.3.0 parameters: vga=0x0317 lang=ru_RU quiet splasht disable=lxF Desktop: IceWM 1.8.3 dm: SLiM 1.3.6 Distro: antiX-19.3_386-full Manolis Glezos 15 October 2020 base: Debian GNU/Linux 10 (buster) Machine: Type: Desktop Mobo: ASUSTeK model: P5GDC Pro v: Rev 1.xx serial: <filter> BIOS: American Megatrends v: 1007.002 date: 06/22/2005 CPU: Topology: Single Core model: Intel Pentium 4 bits: 64 type: MT arch: Netburst Smithfield family: F (15) model-id: 4 stepping: 1 microcode: 17 L2 cache: 1024 KiB flags: lm pae sse sse2 sse3 bogomips: 11238 Speed: 2810 MHz min/max: N/A Core speeds (MHz): 1: 2810 2: 2810 Vulnerabilities: Type: itlb_multihit status: KVM: Vulnerable Type: l1tf status: Vulnerable Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable Type: meltdown status: Vulnerable Type: spec_store_bypass status: Vulnerable Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling Type: srbds status: Not affected Type: tsx_async_abort status: Not affected Graphics: Device-1: NVIDIA G94 [GeForce 9600 GS] vendor: Pegatron driver: nouveau v: kernel bus ID: 04:00.0 chip ID: 10de:0623 Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa resolution: 1440x900~60Hz OpenGL: renderer: NV94 v: 3.3 Mesa 18.3.6 direct render: Yes Audio: Device-1: Intel 82801FB/FBM/FR/FW/FRW High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:2668 Device-2: Ensoniq 5880B / Creative Labs CT5880 driver: snd_ens1371 v: kernel bus ID: 01:0a.0 chip ID: 1274:5880 Sound Server: ALSA v: k4.9.235-antix.1-486-smp Network: Device-1: Marvell 88E8053 PCI-E Gigabit Ethernet vendor: ASUSTeK driver: sky2 v: 1.30 port: c800 bus ID: 02:00.0 chip ID: 11ab:4362 IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter> Drives: Local Storage: total: 150.93 GiB used: 3.58 GiB (2.4%) ID-1: /dev/sda vendor: Hitachi model: HDS721616PLA380 size: 149.05 GiB block size: physical: 512 B logical: 512 B speed: 1.5 Gb/s serial: <filter> rev: ABEA scheme: MBR ID-2: /dev/sdb type: USB vendor: Transcend model: JetFlash Transcend 2GB size: 1.88 GiB block size: physical: 512 B logical: 512 B serial: <filter> rev: 8.07 scheme: MBR Partition: ID-1: / raw size: N/A size: 1.15 GiB used: 89.1 MiB (7.5%) fs: overlay source: ERR-102 Sensors: Message: No sensors data was found. Is sensors configured? Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list 1: deb http://mirror.truenetwork.ru/mxlinux/antix/buster buster main nonfree nosystemd 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.ru.debian.org/debian/ buster-updates main contrib non-free Active apt repos in: /etc/apt/sources.list.d/debian.list 1: deb http://ftp.ru.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 Info: Processes: 174 Uptime: 43m Memory: 1.47 GiB used: 694.2 MiB (46.1%) 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.36marcelocripe
Original title in Brazilian Portuguese: How to use antiX on computers with a motherboard with SIS or VIA chipset
Hello Anticapitalista and antiX Developers
You already know that I am a beginner in this “world of Linux distributions”, I arrived here at antiX in June 2020, since then, I am learning a lot from our colleagues in the forum. I know I still have a lot to learn, so my considerations below are still of a limited view on the subject.
The information I searched for on the internet indicates “that most drivers are in the kernel”
Motherboard of the brand ASUS, as it will be in the following example, of the model P5S800-VM (with chipset SIS), when they arrived in Brazil they were the dream of consumption of several computer users (including mine), at the time who did not have financial conditions to buy an ASUS or Gigabyte motherboard, I bought MSI 238318 or STI 910090 (with Via chipset) or one made in China and then suffered to find the drives, Two other computers from the NGO arrived for me to prepare, but because they are computers with motherboard with SIS chipset and another with VIA antiX 19.3 or 19.2 make the video very slow, failing and with “ghosts”. It is impossible to use the operating system like that.
I applied all the teachings on the topic https://www.antixforum.com/forums/topic/how-to-set-the-set-gfxmode-1024x768x16-1024×768/ to identify ASUS P5S800- branded motherboard devices VM. (Commands are available after the original Brazilian Portuguese text)
Due to the teachings of the topic I mentioned earlier, antiX 16.3 will certainly work, with these two computers that have only 1GB of DDR RAM. I will need to install a full 32-bit version in order to save as much RAM as possible, but I have some doubts:
1-antiX 16.3 had its “end of life” on June 6, 2020 or I can also understand that it was discontinued. Do the repositories still work for antiX 16.3 full 32 bits and antiXfull 64 bits?
2- If the repositories still work for antiX 16.3 32 bits and antiX 64 bits, how much longer will they be available?
The antiX 16.3 64 bits that I prepared for the computer with the VIA motherboard and 2GB of DDR RAM, from the topic I mentioned earlier. At the time, for example, I was unable to install the LibreOffice translations that already come with antiX. What I did to get around this, was to download the LibreOfficetraduced AppImage for PT-BR and the other programs were with AppIamge. I managed to make antiX 16.3 64 bits friendly to the end user with the programs and with the Menu translated to PT-BR added in the Personal Menu. All of these were palliative solutions, but 32-bit AppImage practically does not exist, it will be difficult to use antiX 16.3 32 bits. I still don’t know how to prepare AppImage to be able to use in antiX 16.3 32 bits. When I learn to create AppImage, if ever I will learn to do it, as I cannot find consultation material in Portuguese teaching how to create the 32-bit AppImage. All the material is available for consultation in the English language and usually refer to to 64 bits. Translations remain a daily challenge, it is not enough to translate the words, it is necessary to adapt the text so that the words can make complete sense in the sentences, but this is not always possible, as they depend on the context being used. Therefore, I continue to dedicate myself to make each text the best possible on the site transifex for PT-BR for antiX.
After this long introduction, there are the next questions, which are the important ones in this topic:
3-Would it be possible to create antiX 19.3 with the antiX 16.3 kernel?
Since I got here (on antiX and the forum), I have stopped searching for other Linux distributions. I already know that this is my place, I met excellent people here. But if it is not possible to use an antiX due to the drivers, unfortunately, I will have to continue the search, just so that I can continue saving old computers (that are working) from being thrown in the trash.
I hope, Anticapitalista, that you and the developers can evaluate this topic and analyze if this is possible or if it is feasible to accomplish. I know that there are already several antiX options and these options require a lot of work time to be produced and made available.
Regardless of the answer, I thank you for creating and making antiX available.
Thank you.
marcelocripe
(Original text in Brazilian Portuguese)———-
TĂtulo original em PortuguĂȘs do Brasil: Como utilizar o antiX em computadores com placa-mĂŁe com chipset SIS ou VIA
OlĂĄ Anticapitalista e Desenvolvedores do antiX
VocĂȘs jĂĄ sabem que eu sou iniciante neste “mundo das distribuiçÔes Linux”, cheguei aqui no antiX em Junho de 2020, desde entĂŁo, eu estou aprendendo muito com os nossos colegas do fĂłrum. Eu sei que ainda tenho muito o que aprender, por isso as minhas consideraçÔes a seguir ainda sĂŁo de uma visĂŁo limitada sobre o assunto.
As informaçÔes que eu pesquisei na internet indicam “que a maioria dos drivers estĂŁo no kernel”
Placa-mĂŁe da marca ASUS, como serĂĄ no exemplo a seguir, do modelo P5S800-VM (com chipset SIS), quando chegaram no Brasil eram o sonho de consumo de vĂĄrios usuĂĄrios de computador (inclusive o meu), na Ă©poca quem nĂŁo tinha condiçÔes financeiras de comprar placa-mĂŁe ASUS ou Gigabyte, comprava MSI 238318 ou STI 910090 (com chipset Via) ou alguma fabricada na China e depois sofria para encontrar os drives, Chegaram outros dois computadores da ONG para eu preparar, mas por serem computadores com placa-mĂŁe com chipset SIS e outra com VIA o antiX 19.3 ou 19.2 ficam com o vĂdeo muito lento, falhando e com “fantasmas”. Ă impossĂvel utilizar o sistema operacional assim.
Â
Eu apliquei todos os ensinamentos do tĂłpico https://www.antixforum.com/forums/topic/how-to-set-the-set-gfxmode-1024x768x16-1024×768/ para identificar os dispositivos da placa-mĂŁe da marca ASUS P5S800-VM. (Os comandos estĂŁo disponĂveis apĂłs o texto original em PortuguĂȘs do Brasil)Devido aos ensinamentos do tĂłpico que citei anteriormente, o antiX 16.3 certamente irĂĄ funcionar, com estes dois computadores que possuem apenas 1GB de memĂłria RAM DDR. Eu precisarei instalar o uma versĂŁo full 32 bits para poder economizar o mĂĄximo possĂvel de memĂłria RAM, mas tenho algumas dĂșvidas:   Â
1-O antiX 16.3 teve o seu “fim de vida” no dia 06 de junho de 2020 ou tambĂ©m posso compreender que foi descontinuado. Os repositĂłrios ainda funcionam para antiX 16.3 full 32 bits e para o antiXfull 64 bits?
2- Se os repositĂłrios ainda funcionam para antiX 16.3 32 bits e para o antiX 64 bits, por quanto tempo mais estarĂŁo disponĂveis?
O antiX 16.3 64 bits que eu preparei para o computador com a placa-mĂŁe VIA e 2GB de memĂłria RAM DDR, do tĂłpico que citei anteriormente. Na ocasiĂŁo, por exemplo, eu nĂŁo consegui instalar as traduçÔes do LibreOffice que jĂĄ vem com o antiX. O que eu fiz para contornar isso, foi baixar o AppImage do LibreOfficetraduzidos para PT-BR e os demais programas foram com os AppIamge. Eu consegui tornar antiX 16.3 64 bits amigĂĄvel para o usuĂĄrio final com os programas e com o Menu traduzido para PT-BR adicionado no Menu Pessoal. Todas estas foram soluçÔes paliativas, mas AppImage de 32 bits praticamente nĂŁo existem, ficarĂĄ difĂcil utilizar o antiX 16.3 32 bits. Eu ainda nĂŁo sei preparar AppImage para poder usar no antiX 16.3 32 bits. Quando eu aprender a criar AppImage, se Ă© que um dia eu conseguirei aprender a fazer isso, pois nĂŁo encontro material de consulta em PortuguĂȘs ensinando a criar o AppImage de 32 bits Todo o material estĂĄ disponĂvel a para consulta em idioma InglĂȘs e normalmente se referem a 64 bits. As traduçÔes continuam sendo um desafio diĂĄrio, nĂŁo basta traduzir as palavras, Ă© preciso adaptar o texto para que as palavras possam fazer sentido completo nas frases, mas nem sempre isso Ă© possĂvel, pois dependem do contexto que estĂŁo sendo utilizadas. Por isso, continuo me dedicando para fazer cada texto o melhor possĂvel no site transifex para PT-BR para o antiX.      Â
Depois desta longa introdução, vem as prĂłxima perguntas, sendo estas as importantes deste tĂłpico:Â
3-Seria possĂvel criar o antiX 19.3 com o kernel do antiX 16.3? Â
Desde que eu cheguei aqui (no antiX e no fĂłrum), eu parei de pesquisar outras distribuiçÔes Linux. Eu jĂĄ sei que aqui Ă© o meu lugar, eu encontrei aqui pessoas excelentes. Mas se nĂŁo for possĂvel utilizar um antiX devido aos drivers, infelizmente, eu terei que continuar a busca, sĂł para eu poder continuar salvando computadores antigos (que estĂŁo funcionando) de serem jogados no lixo.
Eu espero, Anticapitalista, que vocĂȘ e os desenvolvedores possam avaliar este tĂłpico e analisar se isso Ă© possĂvel ou se Ă© viĂĄvel de ser realizado. Eu sei que jĂĄ existem vĂĄrias opçÔes de antiX e estas opçÔes exigem bastante tempo de trabalho para serem produzidas e disponibilizadas.
Independentemente da resposta, eu agradeço por criarem e disponibilizarem o antiX.
Muito obrigado. Â
marcelocripe
(Texto original em PortuguĂȘs do Brasil)demo@antix1:~
$ inxi -Fxz
System:
Host: antix1 Kernel: 4.9.235-antix.1-486-smp i686 bits: 32 compiler: gcc
v: 8.3.0 Desktop: IceWM 1.8.3
Distro: antiX-19.3_386-full Manolis Glezos 15 October 2020
base: Debian GNU/Linux 10 (buster)
Machine:
Type: Desktop Mobo: ASUSTeK model: P5S800-VM v: Rev 1.xx serial: <filter>
BIOS: American Megatrends v: 1022.001 date: 05/11/2006
CPU:
Topology: Single Core model: Intel Celeron bits: 64 type: MCP
arch: Netburst Smithfield rev: 9 L2 cache: 256 KiB
flags: lm pae sse sse2 sse3 bogomips: 5306
Speed: 2653 MHz min/max: N/A Core speed (MHz): 1: 2653
Graphics:
Device-1: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or
662/761Gx PCIE VGA Display Adapter
vendor: ASUSTeK driver: N/A bus ID: 01:00.0
Display: x11 server: X.Org 1.20.4 driver: vesa resolution: 1024×768~N/A
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6
direct render: Yes
Audio:
Device-1: Silicon Integrated Systems [SiS] SiS7012 AC97 Sound
vendor: ASUSTeK driver: snd_intel8x0 v: kernel bus ID: 00:02.7
Sound Server: ALSA v: k4.9.235-antix.1-486-smp
Network:
Device-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter
vendor: ASUSTeK P5P800-MX Mainboard driver: 8139too v: 0.9.28 port: e400
bus ID: 00:0b.0
IF: eth0 state: down mac: <filter>
Drives:
Local Storage: total: 7.27 GiB used: 14.3 MiB (0.2%)
ID-1: /dev/sda type: USB vendor: Kingston model: DT 101 G2 size: 7.27 GiB
RAID:
Hardware-1: Silicon Integrated Systems [SiS] RAID bus controller 180
SATA/PATA [SiS]
driver: sata_sis v: 1.0 bus ID: 00:05.0
Partition:
ID-1: / size: 744.0 MiB used: 2.3 MiB (0.3%) fs: overlay source: ERR-102
Sensors:
Message: No sensors data was found. Is sensors configured?
Info:
Processes: 133 Uptime: 12m Memory: 964.9 MiB used: 103.2 MiB (10.7%)
Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3
inxi: 3.0.36demo@antix1:~
$ inxi -G
Graphics:
Device-1: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or
662/761Gx PCIE VGA Display Adapter
driver: N/A
Display: x11 server: X.Org 1.20.4 driver: vesa resolution: 1024×768~N/A
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6demo@antix1:~
$ inxi -v8
System:
Host: antix1 Kernel: 4.9.235-antix.1-486-smp i686 bits: 32 compiler: gcc
v: 8.3.0
parameters: vga=0x0317 lang=pt_BR tz=America/Sao_Paulo quiet splasht
disable=lxF xorg=safe
Desktop: IceWM 1.8.3 dm: SLiM 1.3.6
Distro: antiX-19.3_386-full Manolis Glezos 15 October 2020
base: Debian GNU/Linux 10 (buster)
Machine:
Type: Desktop Mobo: ASUSTeK model: P5S800-VM v: Rev 1.xx
serial: <root required> BIOS: American Megatrends v: 1022.001
date: 05/11/2006
Memory:
RAM: total: 964.9 MiB used: 105.8 MiB (11.0%)
RAM Report:
permissions: Unable to run dmidecode. Root privileges required.
PCI Slots:
Permissions: Unable to run dmidecode. Root privileges required.
CPU:
Topology: Single Core model: Intel Celeron bits: 64 type: MCP
arch: Netburst Smithfield family: F (15) model-id: 4 stepping: 9
microcode: 3 L2 cache: 256 KiB bogomips: 5306
Speed: 2653 MHz min/max: N/A Core speed (MHz): 1: 2653
Flags: acpi apic bts cid clflush cmov constant_tsc cx16 cx8 de ds_cpl
dtes64 dts fpu fxsr ht lahf_lm lm mca mce mmx monitor msr mtrr pae pat pbe
pebs pge pni pse pse36 sep ss sse sse2 tm tm2 tsc vme xtpr
Vulnerabilities: Type: itlb_multihit status: KVM: Vulnerable
Type: l1tf status: Vulnerable
Type: mds
status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled
Type: meltdown status: Vulnerable
Type: spec_store_bypass status: Vulnerable
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2
mitigation: Full generic retpoline, STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or
662/761Gx PCIE VGA Display Adapter
vendor: ASUSTeK driver: N/A bus ID: 01:00.0 chip ID: 1039:6330
Display: x11 server: X.Org 1.20.4 driver: vesa resolution: 1024×768~N/A
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6
compat-v: 3.1 direct render: Yes
Audio:
Device-1: Silicon Integrated Systems [SiS] SiS7012 AC97 Sound
vendor: ASUSTeK driver: snd_intel8x0 v: kernel bus ID: 00:02.7
chip ID: 1039:7012
Sound Server: ALSA v: k4.9.235-antix.1-486-smp
Network:
Device-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter
vendor: ASUSTeK P5P800-MX Mainboard driver: 8139too v: 0.9.28 port: e400
bus ID: 00:0b.0 chip ID: 10ec:8139
IF: eth0 state: down mac: XX:XX:XX:XX:XX:XX (I changed the MAC to XX/eu alterei o MAC para XX)
WAN IP: No WAN IP data found. Connected to the web? SSL issues?
Drives:
Local Storage: total: 7.27 GiB used: 14.3 MiB (0.2%)
ID-1: /dev/sda type: USB vendor: Kingston model: DT 101 G2 size: 7.27 GiB
block size: physical: 512 B logical: 512 B
serial: 001CC0EC330FEB816605000A rev: PMAP scheme: MBR
Floppy-1: /dev/fd0
RAID:
Hardware-1: Silicon Integrated Systems [SiS] RAID bus controller 180
SATA/PATA [SiS]
driver: sata_sis v: 1.0 port: 0000 bus ID: 00:05.0 chip ID: 1039.0180
rev: 01
Partition:
ID-1: / raw size: N/A size: 744.0 MiB used: 2.3 MiB (0.3%) fs: overlay
source: ERR-102 label: N/A uuid: N/A
ID-2: /live/boot-dev raw size: 1.17 GiB size: <root required>
used: <root required> fs: N/A dev: /dev/ventoy label: N/A uuid: N/A
ID-3: /live/linux raw size: 1.14 GiB size: <root required>
used: <root required> fs: squashfs dev: /dev/loop0 label: N/A uuid: N/A
ID-4: /media/VTOYEFI raw size: 32.0 MiB size: 31.9 MiB (99.75%)
used: 12.0 MiB (37.4%) fs: vfat dev: /dev/sda2 label: VTOYEFI
uuid: ADB8-4480
Unmounted:
ID-1: /dev/dm-0 size: 1.17 GiB fs: <root required> label: N/A uuid: N/A
ID-2: /dev/sda1 size: 7.24 GiB fs: exfat label: Ventoy uuid: 4E21-0000
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-4:2 info: Toshiba Kingston DataTraveler 102/2.0 / HEMA Flash
Drive 2 GB / PNY Attache 4GB Stick
type: Mass Storage driver: usb-storage interfaces: 1 rev: 2.0
speed: 480 Mb/s chip ID: 0930:6545 serial: 001CC0EC330FEB816605000A
Device-2: 1-8:3 info: Alcor Micro Flash Card Reader/Writer
type: Mass Storage driver: usb-storage interfaces: 1 rev: 2.0
speed: 480 Mb/s chip ID: 058f:6362 serial: 058F312D81B
Hub: 2-0:1 info: Full speed (or root) Hub ports: 3 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Hub: 3-0:1 info: Full speed (or root) Hub ports: 3 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
Sensors:
Message: No sensors data was found. Is sensors configured?
Repos:
Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb http://mirror.ufam.edu.br/mx/antix/buster buster main nonfree nosystemd
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.br.debian.org/debian/ buster-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://ftp.br.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: 34.5% command: xorg pid: 3302 mem: 47.3 MiB (4.8%)
2: cpu: 0.9% command: [rcu_sched] pid: 7 mem: 0.00 MiB (0.0%)
3: cpu: 0.6% command: slim pid: 3284 mem: 10.2 MiB (1.0%)
4: cpu: 0.6% command: conky pid: 3640 mem: 10.4 MiB (1.0%)
5: cpu: 0.5% command: [ksoftirqd/0] pid: 3 mem: 0.00 MiB (0.0%)
Memory top: 5
1: mem: 47.3 MiB (4.8%) command: xorg pid: 3302 cpu: 34.5%
2: mem: 26.0 MiB (2.6%) command: roxterm pid: 4081 cpu: 0.2%
3: mem: 25.5 MiB (2.6%) command: rox pid: 3558 cpu: 0.1%
4: mem: 16.4 MiB (1.6%) command: volumeicon pid: 3571 cpu: 0.0%
5: mem: 14.3 MiB (1.4%) command: fbxkb pid: 3591 cpu: 0.0%
Info:
Processes: 133 Uptime: 14m 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.36demo@antix1:~
$ lspci -v
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 661FX/M661FX/M661MX Host (rev 11)
Subsystem: ASUSTeK Computer Inc. 661FX/M661FX/M661MX Host
Flags: bus master, medium devsel, latency 32
Memory at e0000000 (32-bit, non-prefetchable)
Capabilities: <access denied>
Kernel driver in use: agpgart-sis00:01.0 PCI bridge: Silicon Integrated Systems [SiS] AGP Port (virtual PCI-to-PCI bridge) (prog-if 00 [Normal decode])
Flags: bus master, 66MHz, fast devsel, latency 64
Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
I/O behind bridge: 0000d000-0000dfff
Memory behind bridge: dfe00000-dfefffff
Prefetchable memory behind bridge: cfd00000-dfcfffff
Kernel modules: shpchp00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS964 [MuTIOL Media IO] LPC Controller (rev 36)
Flags: bus master, medium devsel, latency 0
Kernel modules: i2c_sis63000:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 IDE Controller (rev 01) (prog-if 80 [ISA Compatibility mode-only controller, supports bus mastering])
Subsystem: ASUSTeK Computer Inc. 5513 IDE Controller
Flags: bus master, medium devsel, latency 128, IRQ 16
I/O ports at 01f0
I/O ports at 03f4
I/O ports at 0170
I/O ports at 0374
I/O ports at ffa0
Capabilities: <access denied>
Kernel driver in use: pata_sis00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] SiS7012 AC’97 Sound Controller (rev a0)
Subsystem: ASUSTeK Computer Inc. SiS7012 AC’97 Sound Controller
Flags: bus master, medium devsel, latency 64, IRQ 18
I/O ports at e800
I/O ports at ec00
Capabilities: <access denied>
Kernel driver in use: snd_intel8x0
Kernel modules: snd_intel8x000:03.0 USB controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f) (prog-if 10 [OHCI])
Subsystem: ASUSTeK Computer Inc. USB 1.1 Controller
Flags: bus master, medium devsel, latency 64, IRQ 20
Memory at dfff4000 (32-bit, non-prefetchable)
Kernel driver in use: ohci-pci00:03.1 USB controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f) (prog-if 10 [OHCI])
Subsystem: ASUSTeK Computer Inc. USB 1.1 Controller
Flags: bus master, medium devsel, latency 64, IRQ 21
Memory at dfff5000 (32-bit, non-prefetchable)
Kernel driver in use: ohci-pci00:03.2 USB controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f) (prog-if 10 [OHCI])
Subsystem: ASUSTeK Computer Inc. USB 1.1 Controller
Flags: bus master, medium devsel, latency 64, IRQ 22
Memory at dfff6000 (32-bit, non-prefetchable)
Kernel driver in use: ohci-pci00:03.3 USB controller: Silicon Integrated Systems [SiS] USB 2.0 Controller (prog-if 20 [EHCI])
Subsystem: ASUSTeK Computer Inc. USB 2.0 Controller
Flags: bus master, medium devsel, latency 64, IRQ 23
Memory at dfff7000 (32-bit, non-prefetchable)
Capabilities: <access denied>
Kernel driver in use: ehci-pci00:05.0 RAID bus controller: Silicon Integrated Systems [SiS] RAID bus controller 180 SATA/PATA [SiS] (rev 01) (prog-if 85)
Subsystem: ASUSTeK Computer Inc. RAID bus controller 180 SATA/PATA [SiS]
Flags: bus master, 66MHz, medium devsel, latency 128, IRQ 17
I/O ports at eff0
I/O ports at efe4
I/O ports at efa8
I/O ports at efe0
I/O ports at ef90
I/O ports at 0000
Kernel driver in use: sata_sis00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter (rev 10)
Subsystem: ASUSTeK Computer Inc. P5P800-MX Mainboard
Flags: bus master, medium devsel, latency 64, IRQ 19
I/O ports at e400
Memory at dfff3c00 (32-bit, non-prefetchable)
Capabilities: <access denied>
Kernel driver in use: 8139too
Kernel modules: 8139cp, 8139too01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. SiS Real 256E (ASUS P5S800-VM motherboard)
Flags: 66MHz, medium devsel, IRQ 11
BIST result: 00
Memory at d0000000 (32-bit, prefetchable)
Memory at dfee0000 (32-bit, non-prefetchable)
I/O ports at dc00
[virtual] Expansion ROM at 000c0000 [disabled]
Capabilities: <access denied>demo@antix1:~
$ cat /proc/cmdline
vga=0x0317 lang=pt_BR tz=America/Sao_Paulo quiet splasht disable=lxF xorg=safe
demo@antix1:~In reply to: Partition size advice needed for release 19
fatmac
For my use, just a user, internet, music, videos, photos, etc, I have a root (/) of about double the actual installed size, I only add a few extras normally, so plenty of room – if I expect to do some heavy processing, like remastering/rebuilding an .iso file, I may add some swap, but normally don’t bother – the rest becomes my /home directory.
Linux (& BSD) since 1999
In reply to: Partition size advice needed for release 19
rokytnji
I think if you go to the upgrade thread. I mention in during my chromebook upgrade and then a clean re-install.
How much GB a virgin reinstall takes up. Mine was full 64 bit iso.https://www.antixforum.com/forums/topic/upgrading-antix-17-to-antix-19/page/2/
This is a long in the tooth install on this IBM T430 . Install is
harry@biker:~ $ inxi -F System: Host: biker Kernel: 4.9.193-antix.1-amd64-smp x86_64 bits: 64 Desktop: IceWM 1.9.2 Distro: antiX-19_x64-full Marielle Franco 16 October 2019 Machine: Type: Laptop System: LENOVO product: 2347DS2 v: ThinkPad T430 serial: <root required> Mobo: LENOVO model: 2347DS2 serial: <root required> UEFI [Legacy]: LENOVO v: G1ET41WW (1.16 ) date: 05/25/2012 Battery: ID-1: BAT0 charge: 13.8 Wh condition: 13.8/56.2 Wh (25%) CPU: Topology: Dual Core model: Intel Core i5-3320M bits: 64 type: MT MCP L2 cache: 3072 KiB Speed: 2454 MHz min/max: 1200/3300 MHz Core speeds (MHz): 1: 2454 2: 2235 3: 2110 4: 2430 Graphics: Device-1: Intel 3rd Gen Core processor Graphics driver: i915 v: kernel Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa resolution: 1600x900~60Hz OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile v: 4.2 Mesa 18.3.6 Audio: Device-1: Intel 7 Series/C216 Family High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k4.9.193-antix.1-amd64-smp Network: Device-1: Intel 82579LM Gigabit Network driver: e1000e IF: eth0 state: down mac: 00:21:cc:d0:5f:88 Device-2: Intel Centrino Advanced-N 6205 [Taylor Peak] driver: iwlwifi IF: wlan0 state: up mac: 60:67:20:95:09:dc Drives: Local Storage: total: 465.76 GiB used: 47.58 GiB (10.2%) ID-1: /dev/sda vendor: Seagate model: ST500LT012-1DG142 size: 465.76 GiB Partition: ID-1: / size: 19.10 GiB used: 5.41 GiB (28.3%) fs: ext4 dev: /dev/sda3 ID-2: /home size: 433.48 GiB used: 42.17 GiB (9.7%) fs: ext4 dev: /dev/sda2 ID-3: swap-1 size: 4.82 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda1 Sensors: System Temperatures: cpu: 47.0 C mobo: N/A Fan Speeds (RPM): cpu: 3640 Info: Processes: 188 Uptime: 3h 10m Memory: 15.47 GiB used: 1.15 GiB (7.4%) Shell: bash inxi: 3.0.36
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 problemsIn reply to: Partition size advice needed for release 19
sybok
Hi,
1) I usually have 4 partitions:
/ = root
/data = another partition where I move most of the large stuff from ‘/home’, e.g. movies, music etc. <– easy to share with other Linux installations
/home = large enough to enable download/save of large files
swap (advised to have one for each Linux installation)
2) Partition sizes:
The size of ‘/’ partition depends on what you plan to do with your antiX.
Do you plan to install a lot of and/or large additional software/programs?
My home installation has 20 GB and 11 GB are already used up and I don’t think I’ve installed that many programs but rather large ones (e.g. gimp, chromium, callibre and some others).
3) If all fails, you can re-size:
In case you find out that the sizes (in installed system) do not suit you, it is possible to boot from live USB/CD/DVD and re-size the partitions of your installation.
This is a potentially risky operation (my live-USB Linux froze and messed up the partitions being processed), advised not to do without backup!Hope that helps.
- This reply was modified 2 years, 5 months ago by sybok. Reason: Item 3) stated in a clearer way
Robin
And here comes the feestyle skate, after having done all the duty:
No, not really, its not optional, what comes next. We have do adapt grub on the USB-drive.
Since the old system runs on grub2, we’ll stick to it.
If you find another bootloader on your old system, you’ll have to puzzle out how to transform its config so it will boot from the USB-drive.We just need a chroot-environment:
In order to alow grub to get all the relevant information of our running system we have to create some folders and
mount the following devices to them. You can name the base folder (chroot-USBstick) as you like and place them where you like in your filesystem, but for a clear view I prefer to use suggestive names.
You’ll have to type the commands in the still opened root console window.# mkdir /mnt/chroot-USBstick # mount /dev/sdc1 /mnt/chroot-USBstick # mount -o bind /dev /mnt/chroot-USBstick/dev # mount -t proc /proc /mnt/chroot-USBstick/proc # mount -o bind /sys /mnt/chroot-USBstick/sysNow we actually switch to the root of our new system on the USBstick. “root” refers at this point not any longer to the actual root of the antiX live system in this console window, but to the root of the system we are just going to trim. Every command is executed as if the system was running already, and it uses the therein installed versions of programs, rather than the ones you have at hand within the antiX live system. So consequently it writes all its configs to the correct places in the filsystem of the USB stick instead of changing things in the antiX live system.
# chroot /mnt/chroot-USBstickNow we make write Grub itself into the MBR of the USB-stick:
# update-grub2 # grub-install /dev/sdcLet grub update its config on the USB-stick:
# update-grubAnd now we leave our chroot-environment again.
# exitBe aware of any messages grub will write on the output. If there are any errors, you’ll have to sort them out, in order to make the stick actually bootable.
Now back in the “real” System, we should unmount the chroot folders:# umount /mnt/chroot-USBstick/proc # umount /mnt/chroot-USBstick/dev # umount /mnt/chroot-USBstick/sys # umount /mnt/chroot-USBstickClose the root console window.
We are done with it.Are we? Well, in my case there were some serious error messages, telling me grub wasn’t able to write to the drive at all. So my stick won’t boot so far. Don’t even need to try. Wandering what was going on, I did some research and found out, that older versions of grub actually didnt cope with some of the Ext4 options even kernels of the same age provided, and even if the grub version was delivered with a distribution which had these options in its kernel already. Since I knew, that the installed version worked very well on the original partitions, which some of them were ext4 already, I decided to look into the options which were set on these partitions. Here’s the result:
To be honest, I first tried to install (via downloading packages and dpkg, since the ancient apt refused to work due to format-change) a new version of grub in the old system within the chroot environment. But it failed, entangled in tons of unfullfilled (and unfullfilable!) dependencies, even worse the more I tried to sort them out by installing all the packages dpkg asked me for.
Never mind, the nice thing about these USB-sticks is: you can repair nearly anything with some Keystrokes only.
Since it was the root-filesystem only which was concerned, it doesn’t need anything but to let rsync check it again against the original, just as in the beginning, but letting it rewrite only these files which have been changed during the procedure.
First make sure to save the new version of fstab (and every config you already might have altered willingly) from the stick anywhere else, it will be reset too, but you can as well redo the little amendmends in it again when having forgotten to save it eslewhere before starting next step:# mount /dev/sdc1 /mnt/USBstick-root # rsync --stats --progress --numeric-ids -axAhHSPc /mnt/Ubuntu-root/ /mnt/USBstick-root(the folders to mount the devices on actually exist from the original transfer above, if not, create them again as described there.)
Now we’ll give him another chance, before replacing ext4 with ext3 finally (which should solve the problem actually, but I have’nt tried since ext4 worked after the following step perfectly for me):
Let’s check for any differences in the options between the ext4 created by gparted in antiX and the ext4 filesystems created by the older ubuntu system, which are on the original hdd partitions.
Meanwhile you should know some suitable commands for this task, we have used them above already:# dumpe2fs /dev/sdc1 |grep "Filesystem features:" 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 uninit_bg dir_nlink extra_isize # dumpe2fs /dev/sda10 |grep "Filesystem features:" dumpe2fs 1.43.4 (31-Jan-2017) Filesystem features: has_journal ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isizeAs you can clearly see the options are identical except for two entrys:
needs_recovery
64bit
The first one is not really an option and will vanish when you check the filesystem. But “64bit” is an entry, which should be supported by kernel since ver 2.6.28, and the ubuntu is 3.2.0 already, what the heck does grub not recognize it years after beeing implemented in kernel? Nevertheless we have to deactivate it to give the stick a chance before reformatting the whole thing to ext3 or even ext2. There is a good chance it will work after deactivating this option, since the new filesystem on the stick then will have exactly the same option-settings as the original ext4 filesystem from ubuntu has had.
So let’s start the engine:# tune2fs -O ^64bit /dev/sdc1 # e2fsck -f /dev/sdc1 # resize2fs -s /dev/sdc1 resize2fs 1.43.4 (31-Jan-2017) Converting the filesystem to 32-bit. The filesystem at /dev/sdc1 is now 2621440 (4k) blocks long.This will last some time, since the whole filesystem on the partition is converted from 64bit to 32bit.
After having finished this, redo the steps from above from that point where we were creating the chroot-environment and chroot to the root of the USBstick in order to put grub2 in train.
Well, this time the old grub2 from Ubuntu within chroot works like a charm. Not any error message. So I am sure the stick will be bootable now. I don’t believe that it is necessary to deactivate the 64bit option at the home partition as well, since grub dosn’t have to do anything with it and the kernel is able to cope with. So let us leave this unchanged, on can do it later if it turns out to be really necessery.After having left chroot as before, and after unmounting everything not needed anymore, I gave the new stick a try.
And yes, the old system boots actually flawlessly without any complaints from USBstick now, as if never anything had changed. One drawback might be, that it is noticable slower than booting from hdd. I’ll try to check for the reason of this behaviour when I have some spare time so I can possibly sort it out. Maybe the 64bit home file system slows things down, since this notebook is a native 32bit system. But hey, its for backup purposes only, not for everyday usage!
The only thing I’ll have to keep in mind after repartitioning the hdd is to actualize fstab on that stick in order to set the correct UUID for the then new swap-partition on the hdd.Since all Data from the other partitions will become backuped elsewhere soon, I am now at the point to start installing antiX on the hdd.
For every newcomer who is encouraged to experiment now with these commands on his own: What we have used above are really powerful commands, and adding some other options of them at the commandline with root privileges might really damage your system, when accidently entered whithout knowing exactly what you are doing. So be careful!
Suggestions for further improvement or simplification of the process are welcome.
Greetings & have fun with it
RobinWindows is like a submarine. Open a window and serious problems will start.
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 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.01At 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 all the new UUIDs at its place already, but remember, this is an example for you only, you have to use your own UUIDs. Btw, if you wonder where do these originate from: these UUIDs get always freshly created by the partitioning tool during the partitioning and formatting of a disk.
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.
- This reply was modified 2 years, 5 months ago by Robin.
- This reply was modified 2 years, 5 months ago by Robin. Reason: always getting this silly 403 while posting this drives me mad
- This reply was modified 2 years, 5 months ago by Robin. Reason: some typos
Windows is like a submarine. Open a window and serious problems will start.
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 could’nt 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 successively 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 been 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, preformatted 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 really down. Everything from 2.0 upwards 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 prefer 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 # lsblkExample Output of lsusb and lsblk (before pluging in the 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 connectors, you’ll have to look for the description at the end of the line for the word “2.0 root hub” (or even 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. Nice to know it sits on USB2.0 bus also. On one of the USB 1.1 plugs you can see the mouse (Bus 002, Device 002 in my example)
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 transferred to the stick. They’ll get stored elsewhere later on to free up the harddrive completely, which will be a really easy job then. 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 # lsblkExample 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 romAfter plugging the new stick to an USB-connector, it should better 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 distinguish optically from outside. You’ll have to adapt the concept to what you will find at your PC, maybe you even find USB3.0Compare 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 for now (It will be changed when you plug it later again, depending on what else drives you have pluged in which order before, it might be /dev/sdd or /dev/sde then). 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:
/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 and address that very drive and its partition(s).
It is absolutely important to be sure about which device you want to address 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/sdc1You can check whether you have successfuly unmounted the device completely by typing
# mount |grep "sdc"The answer of this command needs getting used to a little, since you are done when it doesn’t answer anything. If it comes up with something, you haven’t been successfull still.
Or just let all this be done by the drive-unmounter from the antiX taskbar. Now the deletion of the partition in gparted 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 text 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.
- This topic was modified 2 years, 5 months ago by Robin. Reason: fix some typos
- This topic was modified 2 years, 5 months ago by Robin. Reason: tiny amendment
Windows is like a submarine. Open a window and serious problems will start.
Test
And here comes the feestyle skate, after having done all the duty:
No, not really, its not optional, what comes next. We have do adapt grub on the USB-drive.
Since the old system runs on grub2, we’ll stick to it.
If you find another bootloader on your old system, you’ll have to puzzle out how to transform its config so it will boot from the USB-drive.We just need a chroot-environment:
In order to alow grub to get all the relevant information of our running system we have to create some folders and
mount the following devices to them. You can name the base folder (chroot-USBstick) as you like and place them where you like in your filesystem, but for a clear view I prefer to use suggestive names.
You’ll have to type the commands in the still opened root console window.# mkdir /mnt/chroot-USBstick # mount /dev/sdc1 /mnt/chroot-USBstick # mount -o bind /dev /mnt/chroot-USBstick/dev # mount -t proc /proc /mnt/chroot-USBstick/proc # mount -o bind /sys /mnt/chroot-USBstick/sysNow we actually switch to the root of our new system on the USBstick. “root” refers at this point not any longer to the actual root of the antiX live system in this console window, but to the root of the system we are just going to trim. Every command is executed as if the system was running already, and it uses the therein installed versions of programs, rather than the ones you have at hand within the antiX live system. So consequently it writes all its configs to the correct places in the filsystem of the USB stick instead of changing things in the antiX live system.
# chroot /mnt/chroot-USBstickNow we make write Grub itself into the MBR of the USB-stick:
# update-grub2 # grub-install /dev/sdcLet grub update its config on the USB-stick:
# update-grubAnd now we leave our chroot-environment again.
# exitBe aware of any messages grub will write on the output. If there are any errors, you’ll have to sort them out, in order to make the stick actually bootable.
Now back in the “real” System, we should unmount the chroot folders:# umount /mnt/chroot-USBstick/proc # umount /mnt/chroot-USBstick/dev # umount /mnt/chroot-USBstick/sys # umount /mnt/chroot-USBstickClose the root console window.
We are done with it.Are we? Well, in my case there were some serious error messages, telling me grub wasn’t able to write to the drive at all. So my stick won’t boot so far. Don’t even need to try. Wandering what was going on, I did some research and found out, that older versions of grub actually didnt cope with some of the Ext4 options even kernels of the same age provided, and even if the grub version was delivered with a distribution which had these options in its kernel already. Since I knew, that the installed version worked very well on the original partitions, which some of them were ext4 already, I decided to look into the options which were set on these partitions. Here’s the result:
To be honest, I first tried to install (via downloading packages and dpkg, since the ancient apt refused to work due to format-change) a new version of grub in the old system within the chroot environment. But it failed, entangled in tons of unfullfilled (and unfullfilable!) dependencies, even worse the more I tried to sort them out by installing all the packages dpkg asked me for.
Never mind, the nice thing about these USB-sticks is: you can repair nearly anything with some Keystrokes only.
Since it was the root-filesystem only which was concerned, it doesn’t need anything but to let rsync check it again against the original, just as in the beginning, but letting it rewrite only these files which have been changed during the procedure.
First make sure to save the new version of fstab (and every config you already might have altered willingly) from the stick anywhere else, it will be reset too, but you can as well redo the little amendmends in it again when having forgotten to save it eslewhere before starting next step:# mount /dev/sdc1 /mnt/USBstick-root # rsync --stats --progress --numeric-ids -axAhHSPc /mnt/Ubuntu-root/ /mnt/USBstick-root(the folders to mount the devices on actually exist from the original transfer above, if not, create them again as described there.)
Now we’ll give him another chance, before replacing ext4 with ext3 finally (which should solve the problem actually, but I have’nt tried since ext4 worked after the following step perfectly for me):
Let’s check for any differences in the options between the ext4 created by gparted in antiX and the ext4 filesystems created by the older ubuntu system, which are on the original hdd partitions.
Meanwhile you should know some suitable commands for this task, we have used them above already:# dumpe2fs /dev/sdc1 |grep "Filesystem features:" 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 uninit_bg dir_nlink extra_isize # dumpe2fs /dev/sda10 |grep "Filesystem features:" dumpe2fs 1.43.4 (31-Jan-2017) Filesystem features: has_journal ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isizeAs you can clearly see the options are identical except for two entrys:
needs_recovery
64bit
The first one is not really an option and will vanish when you check the filesystem. But “64bit” is an entry, which should be supported by kernel since ver 2.6.28, and the ubuntu is 3.2.0 already, what the heck does grub not recognize it years after beeing implemented in kernel? Nevertheless we have to deactivate it to give the stick a chance before reformatting the whole thing to ext3 or even ext2. There is a good chance it will work after deactivating this option, since the new filesystem on the stick then will have exactly the same option-settings as the original ext4 filesystem from ubuntu has had.
So let’s start the engine:# tune2fs -O ^64bit /dev/sdc1 # e2fsck -f /dev/sdc1 # resize2fs -s /dev/sdc1 resize2fs 1.43.4 (31-Jan-2017) Converting the filesystem to 32-bit. The filesystem at /dev/sdc1 is now 2621440 (4k) blocks long.This will last some time, since the whole filesystem on the partition is converted from 64bit to 32bit.
After having finished this, redo the steps from above from that point where we were creating the chroot-environment and chroot to the root of the USBstick in order to put grub2 in train.
Well, this time the old grub2 from Ubuntu within chroot works like a charm. Not any error message. So I am sure the stick will be bootable now. I don’t believe that it is necessary to deactivate the 64bit option at the home partition as well, since grub dosn’t have to do anything with it and the kernel is able to cope with. So let us leave this unchanged, on can do it later if it turns out to be really necessery.After having left chroot as before, and after unmounting everything not needed anymore, I gave the new stick a try.
And yes, the old system boots actually flawlessly without any complaints from USBstick now, as if never anything had changed. One drawback might be, that it is noticable slower than booting from hdd. I’ll try to check for the reason of this behaviour when I have some spare time so I can possibly sort it out. Maybe the 64bit home file system slows things down, since this notebook is a native 32bit system. But hey, its for backup purposes only, not for everyday usage!
The only thing I’ll have to keep in mind after repartitioning the hdd is to actualize fstab on that stick in order to set the correct UUID for the then new swap-partition on the hdd.Since all Data from the other partitions will become backuped elsewhere soon, I am now at the point to start installing antiX on the hdd.
For every newcomer who is encouraged to experiment now with these commands on his own: What we have used above are really powerful commands, and adding some other options of them at the commandline with root privileges might really damage your system, when accidently entered whithout knowing exactly what you are doing. So be careful!
Suggestions for further improvement or simplification of the process are welcome.
Greetings & have fun with it
RobinWindows is like a submarine. Open a window and serious problems will start.
Forum for users of antiX Linux. Mean and Lean and Proudly anti-fascist.
