Search Results for 'swap'

[Member namida12]

My 1440 monitor is not recognized I get a resolution: 1280×1024

Going to control center> Session> Set Screen Resolution (ARandR) There is only the one resolution 1280×1024 listed. Have never had this problem recently…

$ inxi -F
System:    Host: antix1 Kernel: 4.9.0-279-antix.1-amd64-smp x86_64 bits: 64 Desktop: IceWM 2.8.0 
           Distro: antiX-21-b2_x64-full Grup Yorum 6 September 2021 
Machine:   Type: Desktop Mobo: ASRock model: B450M Pro4 serial: <superuser required> 
           UEFI: American Megatrends v: P3.90 date: 12/09/2019 
CPU:       Info: Quad Core model: AMD Ryzen 5 3400G with Radeon Vega Graphics bits: 64 type: MT MCP cache: 
           L2: 2 MiB 
           Speed: 1400 MHz min/max: 1400/3700 MHz Core speeds (MHz): 1: 1400 2: 2300 3: 2300 4: 1400 5: 1400 
           6: 1400 7: 1400 8: 1400 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Picasso driver: N/A 
           Display: x11 server: X.Org 1.20.11 driver: loaded: N/A unloaded: fbdev resolution: 1280x1024 
           OpenGL: renderer: llvmpipe (LLVM 11.0.1 256 bits) v: 4.5 Mesa 20.3.5 
Audio:     Device-1: Advanced Micro Devices [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio 
           driver: snd_hda_intel 
           Device-2: Advanced Micro Devices [AMD] Family 17h HD Audio driver: snd_hda_intel 
           Sound Server-1: ALSA v: k4.9.0-279-antix.1-amd64-smp running: yes 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: (removed by user) 
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 
           IF: eth1 state: down mac: a8:a1:59:0d:db:5a 
Drives:    Local Storage: total: 946.42 GiB used: 1.35 GiB (0.1%) 
           ID-1: /dev/nvme0n1 vendor: PNY model: CS2130 1TB SSD size: 931.51 GiB 
           ID-2: /dev/sda type: USB vendor: SanDisk model: Cruzer U size: 14.91 GiB 
Swap:      ID-1: swap-1 type: partition size: 16 GiB used: 0 KiB (0.0%) dev: /dev/nvme0n1p2 
Sensors:   Message: No sensor data found. Is lm-sensors configured? 
Info:      Processes: 214 Uptime: 28m Memory: 13.63 GiB used: 2.21 GiB (16.2%) Shell: Bash inxi: 3.3.06 
demo@antix1:~

Running from USB: Maybe because I am using older Kernel with Ryzen CPU? I did not see a way to boot with preferred resolution. Maybe I was blind…

My error, booted with newer kernel resolution is good.

$ inxi -F
System:    Host: antix1 Kernel: 5.10.57-antix.1-amd64-smp x86_64 bits: 64 Desktop: IceWM 2.7.0 
           Distro: antiX-21-b2_x64-full Grup Yorum 6 September 2021 
Machine:   Type: Desktop Mobo: ASRock model: B450M Pro4 serial: <superuser required> UEFI: American Megatrends v: P3.90 
           date: 12/09/2019 
CPU:       Info: Quad Core model: AMD Ryzen 5 3400G with Radeon Vega Graphics bits: 64 type: MT MCP cache: L2: 2 MiB 
           Speed: 3056 MHz min/max: 1400/3700 MHz Core speeds (MHz): 1: 3056 2: 3045 3: 3057 4: 3067 5: 1374 6: 3064 7: 3063 
           8: 3003 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Picasso driver: amdgpu v: kernel 
           Display: x11 server: X.Org 1.20.11 driver: loaded: amdgpu,ati unloaded: fbdev,modesetting,vesa 
           resolution: 2560x1440~60Hz 
           OpenGL: renderer: AMD Radeon Vega 11 Graphics (RAVEN DRM 3.40.0 5.10.57-antix.1-amd64-smp LLVM 11.0.1) 
           v: 4.6 Mesa 20.3.5 
Audio:     Device-1: Advanced Micro Devices [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio driver: snd_hda_intel 
           Device-2: Advanced Micro Devices [AMD] Family 17h HD Audio driver: snd_hda_intel 
           Sound Server-1: ALSA v: k5.10.57-antix.1-amd64-smp running: yes 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 68:1c:a2:13:05:64 
           Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 
           IF: eth1 state: down mac: a8:a1:59:0d:db:5a 
Drives:    Local Storage: total: 946.42 GiB used: 1.35 GiB (0.1%) 
           ID-1: /dev/nvme0n1 vendor: PNY model: CS2130 1TB SSD size: 931.51 GiB 
           ID-2: /dev/sda type: USB vendor: SanDisk model: Cruzer U size: 14.91 GiB 
Swap:      ID-1: swap-1 type: partition size: 16 GiB used: 0 KiB (0.0%) dev: /dev/nvme0n1p2 
Sensors:   System Temperatures: cpu: 42.1 C mobo: N/A gpu: amdgpu temp: 42.0 C 
           Fan Speeds (RPM): N/A 
Info:      Processes: 207 Uptime: 7m Memory: 13.59 GiB used: 1.63 GiB (12.0%) Shell: Bash inxi: 3.3.06 
demo@antix1:~

JR

• This reply was modified 1 year, 7 months ago by namida12. Reason: added new kernel info

[Member roland]

I made 3 install attempts after creating the GTP partition table and the 4 partitions my install requires, EFI (fat32, boot & esp flags set), root (ext4), swap, home (ext4).

Creating the EFI fat32 partition, Gparted produced an exclamation mark error, but the partition existed. I set the boot & esp flags as suggested. The install failed formatting the root partition.

I then selected the ‘entire disk’ option, this install failed hanging, it did not report its last action in the log as formatting anything.

I formatted the EFI partition as fat16, without error, set the boot & esp flags as suggested, this install failed formatting the root partition.

I should install 17.4 at this point I suppose but do not like to walk awaya from such an interesting problem, and 19.4 is a big step up from 17.4.

Attachments:

1. 

   install_1_with_efi_fat32_warning.jpg
   

2. 

   install_1_fail_format_root.jpg
   

3. 

   install_3_efi_fat16.jpg
   

4. 

   install_3_fail_formatting_root.jpg
   

[Member ModdIt]

Seems we all work a bit differently but the statement you made

From what I can see, the live USB with persistence runs like crap compared with my HDD install.

is neither helpful nor fair, in the majority of cases incorrect or sub optimal usage for user case is the root.

If your device does not have at least USB 2+ port and you have a slow writing USB stick
your hardware is a major part of the percieved problem. Once the internal controller cache is full most USB sticks have a very slow write speed. The persistence option is though I agree not the fastest method, that has technical reasons, it is though very comfortable and reliable.

To maximise running performance you can use the dynamic root persistence as suggested by christophe, if your system has enough RAM or you are using swap to the internal HDD that is.

Another way is to remaster after all system changes, i.e. upgrades application installation, customisation. Use Personal as that saves desktop changes, visuals etc.

Save to either your HDD, Live USB Storage folder or to a separate USB stick.

My boot times using the remaster method are about same as my internal samsung evo SSD,
way faster than a fast HDD that is , I do not even have a USB 3 Port.
I have found huge differences in both read and especially write performance from USB sticks, majority are slower than slugs on prolonged writes, some both read and write.
No good believing the advertising..

[Member Wallon]

Dear developers,

I made a new Live usb key and made a complete installation in French (Belgium) on another USB key (ext2) with the modern kernel.

First screen (F2=Language)
fr = ok, everything is translated in french
fr_BE = it’s in English and not translated in French.

Second screen (F2=Language)
fr = ok, everything is translated in French.
fr_BE = it’s in English and not translated in French.

Here is the information of my installation in English for a better understanding;

System:
  Kernel: 5.10.57-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 10.2.1 
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.57-antix.1-amd64-smp 
  root=UUID=977df352-0155-4c80-aedc-26250529d9df ro quiet 
  Desktop: IceWM 2.8.0 vt: 7 dm: N/A 
  Distro: antiX-21-b2_x64-full Grup Yorum 6 September 2021 
  base: Debian GNU/Linux 11 (bullseye) 
Machine:
  Type: Laptop System: ASUSTeK product: F3U v: 1.0 serial: <filter> Chassis: 
  type: 10 serial: <filter> 
  Mobo: ASUSTeK model: F3U v: 1.0 serial: <filter> BIOS: American Megatrends 
  v: 208 date: 07/18/2007 
Battery:
  ID-1: BAT0 charge: 1.3 Wh (100.0%) condition: 1.3/51.3 Wh (2.5%) 
  volts: 12.4 min: 11.1 model: ASUSTEK F3---24 type: Li-ion serial: N/A 
  status: Unknown 
Memory:
  RAM: total: 1.91 GiB used: 741.8 MiB (38.0%) 
  RAM Report: 
  permissions: Unable to run dmidecode. Root privileges required. 
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required. 
CPU:
  Info: Dual Core model: AMD Athlon 64 X2 TK-55 bits: 64 type: MCP 
  arch: K8 rev.F+ family: F (15) model-id: 68 (104) stepping: 1 
  microcode: N/A cache: L2: 512 KiB bogomips: 7181 
  Speed: 1800 MHz min/max: 800/1800 MHz Core speeds (MHz): 1: 1800 2: 1800 
  Flags: 3dnow 3dnowext 3dnowprefetch apic clflush cmov cmp_legacy cpuid 
  cr8_legacy cx16 cx8 de extapic extd_apicid fpu fxsr fxsr_opt ht lahf_lm 
  lbrv lm mca mce mmx mmxext msr mtrr nopl nx pae pat pge pni pse pse36 
  rdtscp rep_good sep sse sse2 svm syscall tsc vme vmmcall 
  Vulnerabilities: Type: itlb_multihit status: Not affected 
  Type: l1tf status: Not affected 
  Type: mds status: Not affected 
  Type: meltdown status: Not affected 
  Type: spec_store_bypass status: Not affected 
  Type: spectre_v1 
  mitigation: usercopy/swapgs barriers and __user pointer sanitization 
  Type: spectre_v2 
  mitigation: Full AMD retpoline, STIBP: disabled, RSB filling 
  Type: srbds status: Not affected 
  Type: tsx_async_abort status: Not affected 
Graphics:
  Device-1: AMD RS690M [Radeon Xpress 1200/1250/1270] vendor: ASUSTeK 
  driver: radeon v: kernel bus-ID: 01:05.0 chip-ID: 1002:791f class-ID: 0300 
  Device-2: Microdia PC Camera (SN9C201 + OV9650) type: USB 
  driver: gspca_sn9c20x bus-ID: 1-7:4 chip-ID: 0c45:624f class-ID: 0000 
  Display: x11 server: X.Org 1.20.11 driver: loaded: ati,radeon 
  unloaded: fbdev,modesetting,vesa display-ID: :0.0 screens: 1 
  Screen-1: 0 s-res: 1280x800 s-dpi: 96 s-size: 338x211mm (13.3x8.3") 
  s-diag: 398mm (15.7") 
  Monitor-1: LVDS res: 1280x800 hz: 60 dpi: 98 size: 331x207mm (13.0x8.1") 
  diag: 390mm (15.4") 
  OpenGL: renderer: ATI RS690 v: 2.1 Mesa 20.3.5 direct render: Yes 
Audio:
  Device-1: AMD SBx00 Azalia vendor: ASUSTeK driver: snd_hda_intel v: kernel 
  bus-ID: 00:14.2 chip-ID: 1002:4383 class-ID: 0403 
  Sound Server-1: ALSA v: k5.10.57-antix.1-amd64-smp running: yes 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: ASUSTeK Notebook driver: r8169 v: kernel port: b800 
  bus-ID: 05:00.0 chip-ID: 10ec:8168 class-ID: 0200 
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  IP v4: <filter> scope: global broadcast: <filter> 
  IP v6: <filter> scope: global 
  IP v6: <filter> type: dynamic mngtmpaddr scope: global 
  IP v6: <filter> scope: link 
  Device-2: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter 
  driver: ath5k v: kernel port: b800 bus-ID: 06:00.0 chip-ID: 168c:001c 
  class-ID: 0200 
  IF: wlan0 state: down mac: <filter> 
  WAN IP: <filter> 
Bluetooth:
  Message: No bluetooth data found. 
Logical:
  Message: No logical block device data found. 
RAID:
  Message: No RAID data found. 
Drives:
  Local Storage: total: 140.44 GiB used: 4.73 GiB (3.4%) 
  SMART Message: Unable to run smartctl. Root privileges required. 
  ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST9120822AS 
  size: 111.79 GiB block-size: physical: 512 B logical: 512 B 
  speed: 1.5 Gb/s type: N/A serial: <filter> rev: C scheme: MBR 
  ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: SanDisk model: USB 3.2Gen1 
  size: 28.65 GiB block-size: physical: 512 B logical: 512 B type: N/A 
  serial: <filter> rev: 1.00 scheme: MBR 
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? 
  Optical-1: /dev/sr0 vendor: MATSHITA model: DVD-RAM UJ-850S rev: 1.22 
  dev-links: cdrom,cdrw,dvd,dvdrw 
  Features: speed: 24 multisession: yes audio: yes dvd: yes 
  rw: cd-r,cd-rw,dvd-r,dvd-ram state: running 
Partition:
  ID-1: / raw-size: 20 GiB size: 19.69 GiB (98.43%) used: 4.73 GiB (24.0%) 
  fs: ext2 dev: /dev/sdb2 maj-min: 8:18 label: rootantiX21 
  uuid: 977df352-0155-4c80-aedc-26250529d9df 
  ID-2: /media/wallon/DATA2 raw-size: 6.65 GiB size: 6.64 GiB (99.80%) 
  used: 64 KiB (0.0%) fs: vfat dev: /dev/sdb3 maj-min: 8:19 label: DATA2 
  uuid: F144-808B 
Swap:
  Kernel: swappiness: 10 (default 60) cache-pressure: 50 (default 100) 
  ID-1: swap-1 type: partition size: 2 GiB used: 0 KiB (0.0%) priority: -2 
  dev: /dev/sdb1 maj-min: 8:17 label: swapantiX 
  uuid: 48ea9119-2ed5-4452-a0b7-9c1aaafcd6ee 
Unmounted:
  ID-1: /dev/sda1 maj-min: 8:1 size: 6.84 GiB fs: vfat label: RECOVERY 
  uuid: 1489-5F00 
  ID-2: /dev/sda2 maj-min: 8:2 size: 67.07 GiB fs: ntfs label: VistaOS 
  uuid: A4448C70448C46D0 
  ID-3: /dev/sda3 maj-min: 8:3 size: 1 KiB fs: <superuser required> 
  label: N/A uuid: N/A 
  ID-4: /dev/sda5 maj-min: 8:5 size: 37.88 GiB fs: ntfs label: DATA 
  uuid: 7458901B588FDA6E 
USB:
  Hub-1: 1-0:1 info: Full speed (or root) Hub ports: 10 rev: 2.0 
  speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900 
  Device-1: 1-1:2 info: SanDisk Ultra Flair type: Mass Storage 
  driver: usb-storage interfaces: 1 rev: 2.1 speed: 480 Mb/s power: 224mA 
  chip-ID: 0781:5591 class-ID: 0806 serial: <filter> 
  Device-2: 1-7:4 info: Microdia PC Camera (SN9C201 + OV9650) type: Video 
  driver: gspca_sn9c20x interfaces: 1 rev: 2.0 speed: 480 Mb/s power: 500mA 
  chip-ID: 0c45:624f class-ID: 0000 
  Hub-2: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 
  speed: 12 Mb/s chip-ID: 1d6b:0001 class-ID: 0900 
  Hub-3: 2-2:2 info: Ortek Targus Number Keypad ports: 3 rev: 1.1 
  speed: 12 Mb/s power: 100mA chip-ID: 05a4:9837 class-ID: 0900 
  Device-1: 2-2.2:3 info: Logitech Optical Tilt Wheel Mouse type: Mouse 
  driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 1.5 Mb/s 
  power: 100mA chip-ID: 046d:c019 class-ID: 0301 
  Device-2: 2-2.3:4 info: Ortek Targus Number Keypad (Composite Device) 
  type: Keyboard,HID driver: hid-generic,usbhid interfaces: 2 rev: 1.1 
  speed: 12 Mb/s power: 48mA chip-ID: 05a4:9862 class-ID: 0300 
  Hub-4: 3-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 
  speed: 12 Mb/s chip-ID: 1d6b:0001 class-ID: 0900 
  Hub-5: 4-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 
  speed: 12 Mb/s chip-ID: 1d6b:0001 class-ID: 0900 
  Hub-6: 5-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 
  speed: 12 Mb/s chip-ID: 1d6b:0001 class-ID: 0900 
  Hub-7: 6-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 
  speed: 12 Mb/s chip-ID: 1d6b:0001 class-ID: 0900 
Sensors:
  System Temperatures: cpu: 60.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Repos:
  Packages: apt: 1571 lib: 746 
  Active apt repos in: /etc/apt/sources.list.d/antix.list 
  1: deb http://mirror.tiguinet.net/mx/packages/antix/bullseye bullseye main nosystemd nonfree
  Active apt repos in: /etc/apt/sources.list.d/bullseye-backports.list 
  1: deb http://deb.debian.org/debian bullseye-backports main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 
  1: deb http://ftp.be.debian.org/debian/ bullseye-updates main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/debian.list 
  1: deb http://ftp.be.debian.org/debian/ bullseye main contrib non-free
  2: deb http://security.debian.org/ bullseye-security main contrib non-free
  Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
  1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
  No active apt repos in: /etc/apt/sources.list.d/various.list 
Processes:
  CPU top: 5 of 163 
  1: cpu: 36.0% command: yad pid: 10883 mem: 29.8 MiB (1.5%) 
  2: cpu: 22.1% command: chrome pid: 10740 mem: 139.9 MiB (7.1%) 
  3: cpu: 13.3% command: chrome pid: 10804 mem: 161.9 MiB (8.2%) 
  4: cpu: 6.7% command: google-chrome-stable pid: 10409 
  mem: 210.4 MiB (10.7%) 
  5: cpu: 6.2% command: app-select started by: python3 pid: 10853 
  mem: 50.4 MiB (2.5%) 
  Memory top: 5 of 163 
  1: mem: 210.4 MiB (10.7%) command: google-chrome-stable pid: 10409 
  cpu: 6.7% 
  2: mem: 161.9 MiB (8.2%) command: chrome pid: 10804 cpu: 13.3% 
  3: mem: 139.9 MiB (7.1%) command: chrome pid: 10740 cpu: 22.1% 
  4: mem: 125.1 MiB (6.4%) command: chrome pid: 10451 cpu: 1.3% 
  5: mem: 99.9 MiB (5.1%) command: xorg pid: 2321 cpu: 3.2% 
Info:
  Processes: 163 Uptime: 42m wakeups: 2 Init: SysVinit v: 2.96 runlevel: 5 
  default: 5 tool: service Compilers: gcc: 10.2.1 alt: 10 Shell: Bash 
  v: 5.1.4 running-in: roxterm inxi: 3.3.06 

Best regards,
Wallon

[Member Xecure]

Efi system partition is fat32 with flags boot and esp.

I forgot I also have a 4GBs Swap, but that doesn’t really matter.

The most important part is that the partition table scheme is gpt.

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

[Member Hazardus]

No dice. I was trying to disable my dGPU to pass to a VM. I soon learned editing xorg.conf is an outdated practice, saw antiX had similar code in modular pieces, and found a grub option to disable on boot that I’m waiting to try (as soon as this is fixed).

When I run slim start it switches back to the oversized background environment where I can’t see/do anything in it. I edited the xorg.conf.in based on a solution I found online for nVidia cards (mine’s AMD, so I just swapped the ‘nvidia’s for ‘radeon’). I’m only a few months in to Linux and virtual machines. It’s taking a while to learn the ropes.

Please let me know what you need. I’m writing this on my antiX OS but in the ctrl+alt+F6 version (not sure what they’re called). If I do ctrl+alt+F7 it’s the same as slim start; giant wallpaper with nothing to do.

Here’s some random info that might possibly be helpful:

1. It says slim started.
2. In elogind I’m getting Unknown Option “nsdelegate” (problem with systemd?)

I installed systemd for systemctl to start services for the VM (but it seems antiX does not use this natively?). I can’t even be sure editing the xorg.conf is what started this (though I’m reasonably sure I restarted just before). Below are some outputs that may be of use.

I also sometimes get “Stopping X display manager: slim not running (/var/run/slim.lock not found)” — even though the file is indeed there (contains 4 digits).

Sometimes I get a message saying Slim failed to start <shrug>.

Here is a segment of the xorg log.

[   164.588] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   164.592] (==) Log file: "/home/account/.local/share/xorg/Xorg.1.log", Time: Sun Oct 10 08:07:13 2021
[   164.593] (==) Using config directory: "/etc/X11/xorg.conf.d"
[   164.594] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   164.594] (==) No Layout section.  Using the first Screen section.
[   164.594] (==) No screen section available. Using defaults.
[   164.594] (**) |-->Screen "Default Screen Section" (0)
[   164.594] (**) |   |-->Monitor "<default monitor>"
[   164.594] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[   164.594] (==) Automatically adding devices
[   164.594] (==) Automatically enabling devices
[   164.594] (==) Automatically adding GPU devices
[   164.594] (==) Max clients allowed: 256, resource mask: 0x1fffff
[   164.594] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[   164.594] 	Entry deleted from font path.
[   164.594] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[   164.594] 	Entry deleted from font path.
[   164.594] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[   164.594] 	Entry deleted from font path.
[   164.594] (==) FontPath set to:
	/usr/share/fonts/X11/misc,
	/usr/share/fonts/X11/100dpi/:unscaled,
	/usr/share/fonts/X11/Type1,
	/usr/share/fonts/X11/100dpi,
	built-ins
[   164.594] (==) ModulePath set to "/usr/lib/xorg/modules"
[   164.594] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[   164.594] (II) Loader magic: 0x564d10ba3e20
[   164.594] (II) Module ABI versions:
[   164.594] 	X.Org ANSI C Emulation: 0.4
[   164.594] 	X.Org Video Driver: 24.0
[   164.594] 	X.Org XInput driver : 24.1
[   164.594] 	X.Org Server Extension : 10.0
[   164.595] (++) using VT number 6

[   164.595] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31

[Member Xecure]

roland wrote:

Firstly if 3 partitions is a maximum (not counting an extended partition), why does Gparted permit them to be created in the first place?

GPT partition table has INFINITE (not really, but practically it is infinite) partition capacity. You need GPT partition table for UEFI systems. The partition limit is only on msdos partition tables (qhich don’t work with UEFI).

Also, 4GBs is more than enough for toram. My tablet also has 4GBs of RAM, and I had no trouble getting toram to work.

roland wrote:

My EFI partition was already on the laptop when it arrived with Windows10. I used the original EFI partition when I installed 17.4, I think it was 100mb, not sure about that. the 17.4 install had only 2 (swap and root+home) partitions.

I also reused the EFI partition. It worked without any problem.
As long it is formatted vfat or fat32, and has the ESP flag set in Gparted (if creating anew) it should work.

I will have a look at the partition flags in a bit and report back.

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

[Member roland]

I shall try to replicate your install Xecure, when time allows, but as I am not even slightly short of ram I am not certain that I should use the toram boot option, however I can try both ways.

However I feel there are unknowns here which I would appreciate comments on or answers to.

Firstly if 3 partitions is a maximum (not counting an extended partition), why does Gparted permit them to be created in the first place? Is the answer that the EFI partition is a special category (like extended and logical) and so is in fact permitted as an extra? If so what is the suggested size and format of this partition? If defaults are used Gparted has to allocate a fat16 (vfat?) partition to succeed. Advanced options have to be used to create a fat32 partition. What format is recommended for EFI?

My EFI partition was already on the laptop when it arrived with Windows10. I used the original EFI partition when I installed 17.4, I think it was 100mb, not sure about that. the 17.4 install had only 2 (swap and root+home) partitions. It installed clean and ran without trouble. But 19.4 will not accept an identical disk geometry, failing usually on one or another of the required formats. I deleted the EFI partition at some stage and created it afresh at 256mb. I wonder if this could be a contributory cause? Does something else have to be specified when the EFI partition is created? Some flag maybe?

Second, why does Gparted ‘grey out’ the extended and logical partition options? Is it related to the EFI system (I have no idea what this is) ? Maybe I should try using advanced options to make these selections visible?

I’ll get on with your suggestion and report back, although I’m not sure that I’m going in an organised direction here, just stabbing in the dark really.

Thanks for your contributions.

[Member Xecure]

I finally got to revive the laptop, made a backup and finally booted antiX 19.4 full (loaded to ram, as the USB port randomly disconnects). Updated only the antix-installer package, made some space on the emmc for a ext4 antix19 partition, and ran the minstaller. The custom partitions I used were only the 100MBs ESP partition (preserved automatically) and the new 7GBs ext4 partition for root (/). No swap or /home or anything else.
Successfully installed. There was no problems in the installation process and the ext4 partition was properly formated.
Rebooted and went directly to the new install.

The only difference compared to your tries is different partition layouts (only 1 root partition and 1 ESP one), and I booted toram (as trying to do it from the USB drive had it disconnect halfway and never got to install).

Try booting with toram, removing the USB device once properly booted, update the installer and try installing again.

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

[Member bunkbail]

Anonymous wrote:

testing here the assertion that the forum now rejects embedded pastebin links

https://pastebin.com/KchQvvFC

still works fine from my house…

That’s odd because the board redirected me to the edit page 6 times when I attempted to add pastebin links. The 7th attempt I decided to just post them in quotes and it finally went through.

Anyways, I finally got it done but with very crude workaround. I swapped out the 3060ti with my old 1060 card and installed everything I need including the Nvidia drivers. Everything is working fine and fast and after installing Gnome the footprint remained relatively small.

[Member Eismckwadraat19]

After this I tried to create a ”home” and a ”root” disk and reuse the ”boot disk” of linux mint, but this did not work.
In the end, I found a solution 🙂

– you first need to format your entire disk to ext4.
– After that, you need to restart the laptop.
– After that you need to create a root and a home and a swap partition.
– When installing grub you do not have to choose MBR but ESP.
– The ESP is selected by default on the USB stick, you have to change it to your hard disk.

After these steps I was finally able to install antiX linux 🙂

As a thank for your help I would like to share a song by Grub Yorum which is the name of antiX 19.4:

https://youtu.be/4vpkQD6vRK4

-I find capitalism repugnant. It is filthy, it is gross, it is alienating... because it causes war, hypocrisy and competition-

Fidel Castro

[Member roland]

The installer does not seem to think that 4 physical partitions are 1 too many. I agree that I always regarded 3 as a maximum,which is why I usually embed them in an extended partition thus allowing further physical partitions. When I tried to run an install using the defaults, allowing the installer to make all the choices for me, it created 4 partitions, 3 of which are correctly formatted for this laptop, and one which was apparently not formatted, but which I guess was intended for linux swap.

I can now get nowhere with 19.4 on this laptop despite it having run 17.4 for over 2 years after a relatively event-free install.

Any suggestions or comments will be gratefully received.

Attachments:

1. 

   installer_creates_4_partitions.jpg
   

2. 

   regular_install.jpg
   

3. 

   default_creates_4_parts.jpg
   

[Member eyekay234]

Hello, so sorry about that. Here it is

System:
Kernel: 4.9.0-264-antix.1-486-smp i686 bits: 32 compiler: gcc v: 8.3.0
Desktop: IceWM 2.7.0 Distro: antiX-19.4_386-base Grup Yorum 20 May 2021
base: Debian GNU/Linux 10 (buster)
Machine:
Type: Virtualbox System: innotek product: VirtualBox v: 1.2
serial: <filter>
Mobo: Oracle model: VirtualBox v: 1.2 serial: <filter> BIOS: innotek
v: VirtualBox date: 12/01/2006
Battery:
ID-1: BAT0 charge: 50.0 Wh (100.0%) condition: 50.0/50.0 Wh (100.0%)
volts: 10.0 min: 10.0 model: innotek 1 status: Full
CPU:
Info: Single Core model: Intel Core i7-7500U bits: 32 type: MCP
arch: Amber/Kaby Lake note: check rev: 9 cache: L2: 4 MiB
flags: avx avx2 sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 5808
Speed: 2904 MHz min/max: N/A Core speed (MHz): 1: 2904
Graphics:
Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.12.0.0
bus-ID: 00:02.0
Display: x11 server: X.Org 1.20.4 driver: loaded: vmware
unloaded: fbdev,modesetting,vesa resolution: 1366×768~60Hz
OpenGL: renderer: llvmpipe (LLVM 7.0 256 bits) v: 3.3 Mesa 18.3.6
direct render: Yes
Audio:
Device-1: Intel 82801AA AC97 Audio vendor: Dell driver: snd_intel8x0
v: kernel bus-ID: 00:05.0
Sound Server-1: ALSA v: k4.9.0-264-antix.1-486-smp running: yes
Network:
Device-1: Intel 82540EM Gigabit Ethernet driver: e1000 v: 7.3.21-k8-NAPI
port: d020 bus-ID: 00:03.0
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Intel 82371AB/EB/MB PIIX4 ACPI type: network bridge
driver: piix4_smbus v: N/A port: d200 bus-ID: 00:07.0
Drives:
Local Storage: total: 10 GiB used: 3.66 GiB (36.6%)
ID-1: /dev/sda vendor: VirtualBox model: VBOX HARDDISK size: 10 GiB
Partition:
ID-1: / size: 7.49 GiB used: 3.52 GiB (47.1%) fs: ext4 dev: /dev/sda1
ID-2: /home size: 1.74 GiB used: 140.2 MiB (7.9%) fs: ext4 dev: /dev/sda3
Swap:
ID-1: swap-1 type: partition size: 512 MiB used: 0 KiB (0.0%)
dev: /dev/sda2
Sensors:
Message: No sensor data found. Is lm-sensors configured?
Info:
Processes: 144 Uptime: 26m Memory: 1.52 GiB used: 664.3 MiB (42.6%)
Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Packages: 1342
Shell: Bash v: 5.0.3 inxi: 3.3.06

• This reply was modified 1 year, 7 months ago by eyekay234.

[Member Emiliano]

inxi -Fxz
System:
Kernel: 4.9.0-264-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 8.3.0
Desktop: IceWM 2.7.0 Distro: antiX-19.4_x64-base Grup Yorum 20 May 2021
base: Debian GNU/Linux 10 (buster)
Machine:
Type: Laptop System: ASUSTeK product: F5VL v: 1.0 serial: <filter>
Mobo: ASUSTeK model: F5VL v: 1.0 serial: <filter>
BIOS: American Megatrends v: 211 date: 11/08/2007
CPU:
Info: Dual Core model: Intel Core2 Duo T5450 bits: 64 type: MCP
arch: Core Merom rev: D cache: L2: 2 MiB
flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 6666
Speed: 1328 MHz min/max: 996/1660 MHz Core speeds (MHz): 1: 1328 2: 996
Graphics:
Device-1: AMD RV516/M64 [Mobility Radeon X2300] vendor: ASUSTeK
driver: radeon v: kernel bus-ID: 01:00.0
Display: x11 server: X.Org 1.20.4 driver: loaded: ati,radeon
unloaded: fbdev,modesetting,vesa resolution: 1280×800~60Hz
OpenGL: renderer: ATI RV515 v: 2.1 Mesa 18.3.6 direct render: Yes
Audio:
Device-1: Silicon Integrated Systems [SiS] Azalia Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel bus-ID: 00:0f.0
Sound Server-1: ALSA v: k4.9.0-264-antix.1-amd64-smp running: yes
Network:
Device-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter
vendor: ASUSTeK driver: 8139too v: 0.9.28 port: d400 bus-ID: 00:0d.0
IF: eth0 state: down mac: <filter>
Device-2: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter
vendor: AzureWave AW-GE780 802.11bg driver: ath5k v: kernel port: a800
bus-ID: 02:00.0
IF: wlan0 state: up mac: <filter>
Drives:
Local Storage: total: 238.47 GiB used: 4.47 GiB (1.9%)
ID-1: /dev/sda model: SATA3 256GB SSD size: 238.47 GiB
Partition:
ID-1: / size: 102.27 GiB used: 4.47 GiB (4.4%) fs: ext4 dev: /dev/sda3
Swap:
ID-1: swap-1 type: partition size: 4.26 GiB used: 0 KiB (0.0%)
dev: /dev/sda2
ID-2: swap-2 type: partition size: 3 GiB used: 0 KiB (0.0%) dev: /dev/sda4
Sensors:
System Temperatures: cpu: 63.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 149 Uptime: 56m Memory: 1.96 GiB used: 1.02 GiB (52.2%)
Init: SysVinit runlevel: 5 Compilers: gcc: 8.3.0 Packages: 1470
Shell: Bash v: 5.0.3 inxi: 3.3.06

sudo service saned satus
[FAIL] Usage: /etc/init.d/saned {start|stop|restart|force-reload} … failed!

simple scan does not detect the scanner

Since 19.3 was released last year, I have been happily using a live USB (full edition) on an ancient desktop (P4 CPU, 1G RAM, NVIDIA NV17 – GeForce4 MX 420) without too many issues. Yesterday I decided to boot into “safe video” mode to see what it was like. It gave me a dreadful low resolution screen (maybe 640 x 480?) with huge icons but tiny blurry/fuzzy font which was barely decipherable. So I rebooted, thinking it would return to normal – but alas, I landed at the console login.

After many hours of trying to troubleshoot this, slim suddenly reappeared but I have no idea why. Unfortunately though, it is still stuck with the 640 x 480 resolution with the tiny blurry font like “safe video” mode – it is virtually unusable. Prior to AntiX booting (eg: in PLoP, the boot menu and the scrolling boot messages) the resolution and clarity is fine. The problem only happens from the slim login stage.

Eventually, I tried swapping it for another AntiX live usb which I use on an old laptop, but this does exactly the same thing! However, when I put it back in the laptop (integrated graphics), it works fine with 1024 x 768. So I thought maybe the video hardware had somehow been reset on the desktop or something, since it did the same thing with both (unrelated) live usbs.

Next I tried an old live usb of Lubuntu on the desktop, but that works fine! I noticed it is using the NOUVEAU driver, whereas the AntiX usbs keep using the VESA driver.

So finally, I built a new AntiX live usb from an old snapshot (of the original usb above) taken last November. This also works fine on the desktop, and is using the NOUVEAU driver.

This makes me wonder if an update has changed the modules recently, because my system worked fine until yesterday, and the older snapshot (which hasn’t been updated) still works fine. Maybe booting in “safe video” mode was a red herring that just happened to coincide with the problem? The one thing the two live usbs that fail have in common is they are both fully updated.

I could start from scratch and build a new live usb for a clean start but that is not going to solve the problem if something has changed in the AntiX system, since it will break again as soon as I update it…

Can anyone cast any light on this for me? (assume fairly minimal linux expertise please…)