-
Search Results
-
Topic: weird screen behaviour
I post this problem in Hardware despite feeling the solution may lie with a software change. I have had these strange effects with other similar but not identical PCs and with 3 or 4 display units including old 15″ and 14″ glass monitors, a portable flat screen tv with elongated format, and a more regular shaped flat screen commercial monitor. All manual adjustments possible on the displays have been tried without success. The PCs that have offended are both MSI 64bit, but have performed quite normally under release 13 and 16, but have shown this problem under release 17 and 19. I have 2 other PCs that work normally with these same monitors leading me to think that the particular graphics chipset on these MSI mainboards is to blame.
The install of 19.3 is completely up to date. The background and windows never correspond to the physical monitor boundaries, so parts are missing usually at the top of the display. When a window is located up there I cannot see the 3 minimise maximise and close buttons. Other parts of the display are splashed around the screen apparently randomly, and I can wipe them away using the mouse cursor arrow, but any mouse or application activity soon brings them back again. It´s no use my attempting to show you a screenshot because the screen buffer looks quite correct, although I attach such a shot to emphasise the point.
AR&R does not offer the screen layouts that are possible with the current monitor, only 800×600 and 640×480, all monitors I have tried will work with much more. I searched the forum for clues and located Anticapitalista´s post about changing screen resolution but when I looked in /usr/local/bin I found no file called screen_resolution.sh so was unable to proceed with this suggestion.
I can manage to work with it by wiping away the trash using the mouse arrow so I can see the workspaces and other items, but it is getting on my nerves.
System: Host: antix1 Kernel: 4.9.235-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 8.3.0
parameters: BOOT_IMAGE=/boot/vmlinuz-4.9.235-antix.1-amd64-smp
root=UUID=4cc8d1a2-4449-48df-a00a-bc326eed2407 ro vga=0x0317 quiet
Desktop: IceWM 2.3.1 dm: SLiM 1.3.6
Distro: antiX-19.3_x64-full Manolis Glezos 15 October 2020
base: Debian GNU/Linux 10 (buster)
Machine: Type: Desktop Mobo: MICRO-STAR model: MS-7253 v: 1.0 serial: <filter> BIOS: Phoenix
v: 1.6 date: 08/16/2007
Memory: RAM: total: 1.83 GiB used: 628.7 MiB (33.5%)
RAM Report: permissions: Unable to run dmidecode. Root privileges required.
PCI Slots: Permissions: Unable to run dmidecode. Root privileges required.
CPU: Topology: Dual Core model: AMD Athlon 64 X2 6000+ bits: 64 type: MCP arch: K8 rev.F+
family: F (15) model-id: 43 (67) stepping: 3 microcode: N/A L2 cache: 2048 KiB
bogomips: 8000
Speed: 2000 MHz min/max: 1000/3000 MHz Core speeds (MHz): 1: 2000 2: 2000
Flags: 3dnow 3dnowext 3dnowprefetch apic clflush cmov cmp_legacy cr8_legacy cx16 cx8 de
extapic extd_apicid fpu fxsr fxsr_opt ht lahf_lm 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 generic retpoline, STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: VIA K8M890CE/K8N890CE [Chrome 9] vendor: Micro-Star MSI driver: N/A
bus ID: 01:00.0 chip ID: 1106:3230
Display: x11 server: X.Org 1.20.4 driver: vesa resolution: 800×600~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: VIA VT8237A/VT8251 HDA vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
bus ID: 80:01.0 chip ID: 1106:3288
Sound Server: ALSA v: k4.9.235-antix.1-amd64-smp
Network: Device-1: VIA VT6102/VT6103 [Rhine-II] vendor: Micro-Star MSI driver: via-rhine v: N/A
port: f200 bus ID: 00:12.0 chip ID: 1106:3065
IF: eth0 state: down mac: <filter>
Device-2: Qualcomm Atheros AR9271 802.11n type: USB driver: ath9k_htc bus ID: 1-3:4
chip ID: 0cf3:9271 serial: <filter>
IF: wlan0 state: up mac: <filter>
IP v4: <filter> type: dynamic scope: global broadcast: <filter>
IP v6: <filter> scope: link
WAN IP: <filter>
Drives: Local Storage: total: 149.05 GiB used: 5.03 GiB (3.4%)
ID-1: /dev/sda vendor: Hitachi model: HCP725016GLAT80 size: 149.05 GiB block size:
physical: 512 B logical: 512 B speed: <unknown> rotation: 7200 rpm serial: <filter>
rev: A4CA scheme: MBR
Optical-1: /dev/sr0 vendor: HL-DT-ST model: DVD-RAM GSA-H22N rev: 1.00
dev-links: cdrom,cdrw,dvd,dvdrw
Features: speed: 48 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram
state: running
RAID: Message: No RAID data was found.
Partition: ID-1: / raw size: 29.59 GiB size: 29.00 GiB (98.01%) used: 5.03 GiB (17.3%) fs: ext4
dev: /dev/sda5 label: rootantiX19 uuid: 4cc8d1a2-4449-48df-a00a-bc326eed2407
ID-2: swap-1 size: 4.88 GiB used: 0 KiB (0.0%) fs: swap swappiness: 10 (default 60)
cache pressure: 50 (default 100) dev: /dev/sda6 label: swap
uuid: 83528a0c-ddf6-4c12-8eb1-2e27358725a5
Unmounted: ID-1: /dev/sda1 size: 1 KiB fs: <root required> label: N/A uuid: N/A
ID-2: /dev/sda7 size: 114.57 GiB fs: ext4 label: antiX2
uuid: 281f3ca7-88f9-44d7-8c99-cdba87c5a42d
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-3:4 info: Qualcomm Atheros AR9271 802.11n type: Network driver: ath9k_htc
interfaces: 1 rev: 2.0 speed: 480 Mb/s chip ID: 0cf3:9271 serial: <filter>
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: Weltrend type: Keyboard,HID driver: hid-generic,usbhid
interfaces: 2 rev: 1.1 speed: 1.5 Mb/s chip ID: 040b:2000
Device-3: 2-2:3 info: Pixart Imaging Optical Mouse type: Mouse
driver: hid-generic,usbhid interfaces: 1 rev: 1.1 speed: 1.5 Mb/s chip ID: 093a:2510
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
Device-4: 4-2:2 info: Alcor Micro Flash Card Reader/Writer type: Mass Storage
driver: usb-storage interfaces: 1 rev: 2.0 speed: 12 Mb/s chip ID: 058f:6362
serial: <filter>
Hub: 5-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s
chip ID: 1d6b:0001
Sensors: System Temperatures: cpu: 38.0 C mobo: N/A
Fan Speeds (RPM): N/A
Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list
1: deb https: //anorien.csc.warwick.ac.uk/mxlinux/packages/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.pt.debian.org/debian/ buster-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http: //ftp.pt.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.6% command: chromium pid: 5411 mem: 160.1 MiB (8.5%)
2: cpu: 28.3% command: xorg pid: 2889 mem: 65.7 MiB (3.5%)
3: cpu: 6.9% command: chromium pid: 5349 mem: 134.9 MiB (7.1%)
4: cpu: 2.8% command: gtkdialog pid: 9376 mem: 28.9 MiB (1.5%)
5: cpu: 2.3% command: chromium pid: 4753 mem: 237.5 MiB (12.6%)
Memory top: 5
1: mem: 237.5 MiB (12.6%) command: chromium pid: 4753 cpu: 2.3%
2: mem: 188.0 MiB (10.0%) command: chromium pid: 4805 cpu: 0.2%
3: mem: 160.1 MiB (8.5%) command: chromium pid: 5411 cpu: 34.6%
4: mem: 134.9 MiB (7.1%) command: chromium pid: 5349 cpu: 6.9%
5: mem: 105.0 MiB (5.5%) command: chromium pid: 4777 cpu: 0.0%
Info: Processes: 188 Uptime: 33m Init: SysVinit v: 2.93 runlevel: 5 default: 5 Compilers:
gcc: 8.3.0 alt: 8 Client: shell wrapper v: 5.0.3-release inxi: 3.0.36Topic: Cannot change fstab
I need to change a fstab entry for get a ntfs partition automounted.
I changed the option noauto to auto. But when I reboot the change is overwritten back by the system.
Is that normal?
How can I made permanent changes to fstab?System:
Host: antix1 Kernel: 4.9.212-antix.1-amd64-smp x86_64 bits: 64
Desktop: IceWM 1.6.5
Distro: antiX-19.2.1_x64-base Hannie Schaft 29 March 2020
Machine:
Type: Desktop Mobo: BIOSTAR model: TA75M+ serial: <root required>
BIOS: American Megatrends v: 4.6.4 date: 09/13/2011
CPU:
Topology: Dual Core model: AMD A4-3300 APU with Radeon HD Graphics
bits: 64 type: MCP L2 cache: 1024 KiB
Speed: 800 MHz min/max: 800/2500 MHz Core speeds (MHz): 1: 800 2: 800
Graphics:
Device-1: AMD Sumo [Radeon HD 6410D] driver: radeon v: kernel
Display: x11 server: X.Org 1.20.4 driver: ati,radeon
unloaded: fbdev,modesetting,vesa resolution: 1920×1080~60Hz
OpenGL:
renderer: AMD SUMO2 (DRM 2.49.0 / 4.9.212-antix.1-amd64-smp LLVM 7.0.1)
v: 3.3 Mesa 18.3.6
Audio:
Device-1: AMD BeaverCreek HDMI Audio [Radeon HD 6500D and 6400G-6600G
series]
driver: snd_hda_intel
Device-2: AMD FCH Azalia driver: snd_hda_intel
Sound Server: ALSA v: k4.9.212-antix.1-amd64-smp
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
driver: r8169
IF: eth0 state: up speed: 100 Mbps duplex: full mac: 00:30:67:d0:1f:00
Drives:
Local Storage: total: 223.57 GiB used: 38.30 GiB (17.1%)
ID-1: /dev/sda vendor: Western Digital model: WDS240G2G0A-00JH30
size: 223.57 GiB
Partition:
ID-1: / size: 2.65 GiB used: 2.6 MiB (0.1%) fs: overlay source: ERR-102
ID-2: swap-1 size: 3.93 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda4
Sensors:
System Temperatures: cpu: 19.5 C mobo: N/A gpu: radeon temp: 23 C
Fan Speeds (RPM): N/A
Info:
Processes: 150 Uptime: 45m Memory: 3.35 GiB used: 921.9 MiB (26.9%)
Shell: bash inxi: 3.0.36I have made previous attempts to use connman, without success. Ceni being simple and functional causes me to avoid connman in any case. However I set up this little PC specifically to resolve the connman problems I have previously experienced, but have not been able to improve on my previous lack of success with connman. Therefore I am requesting analysis of my experience described here, and suggestions as to what may be wrong with my installation.
This PC has a basic install of 19.3 with an AMD 64-bit cpu, low on memory and hard disk but has successfully run 16.4.1 for several years with every satisfaction. Previously I used it with an ethernet connexion, which I now wish to avoid, hence no install update or upgrade has been done yet, and several changes are awaited including to the repositories.
I ran through the antix wifi switch procedure which executed correctly, and entered the wlan name (SSID) and key text as necessary. There appears to be no attempt by connman to act on the data present and search for and make the required connexion.
The wlan adapter is hanging on the end of a short USB cable and has a short antenna, it is a TP-Link TL-WN722N 150mbps unit which I have used with success on previous occasions. I wonder if it is compatible with the kernel and my installation ?
System: Host: antix1 Kernel: 4.9.235-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 8.3.0 parameters: BOOT_IMAGE=/boot/vmlinuz-4.9.235-antix.1-amd64-smp root=UUID=4cc8d1a2-4449-48df-a00a-bc326eed2407 ro vga=0x0317 quiet Desktop: IceWM 1.8.3 dm: SLiM 1.3.6 Distro: antiX-19.3_x64-full Manolis Glezos 15 October 2020 base: Debian GNU/Linux 10 (buster) Machine: Type: Desktop Mobo: MICRO-STAR model: MS-7253 v: 1.0 serial: <filter> BIOS: Phoenix v: 1.6 date: 08/16/2007 Memory: RAM: total: 1.83 GiB used: 219.1 MiB (11.7%) RAM Report: permissions: Unable to run dmidecode. Root privileges required. PCI Slots: Permissions: Unable to run dmidecode. Root privileges required. CPU: Topology: Dual Core model: AMD Athlon 64 X2 6000+ bits: 64 type: MCP arch: K8 rev.F+ family: F (15) model-id: 43 (67) stepping: 3 microcode: N/A L2 cache: 2048 KiB bogomips: 11999 Speed: 3000 MHz min/max: 1000/3000 MHz Core speeds (MHz): 1: 3000 2: 3000 Flags: 3dnow 3dnowext 3dnowprefetch apic clflush cmov cmp_legacy cr8_legacy cx16 cx8 de extapic extd_apicid fpu fxsr fxsr_opt ht lahf_lm 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 generic retpoline, STIBP: disabled, RSB filling Type: srbds status: Not affected Type: tsx_async_abort status: Not affected Graphics: Device-1: VIA K8M890CE/K8N890CE [Chrome 9] vendor: Micro-Star MSI driver: N/A bus ID: 01:00.0 chip ID: 1106:3230 Display: x11 server: X.Org 1.20.4 driver: vesa resolution: 1280x800~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: VIA VT8237A/VT8251 HDA vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus ID: 80:01.0 chip ID: 1106:3288 Sound Server: ALSA v: k4.9.235-antix.1-amd64-smp Network: Device-1: VIA VT6102/VT6103 [Rhine-II] vendor: Micro-Star MSI driver: via-rhine v: N/A port: f200 bus ID: 00:12.0 chip ID: 1106:3065 IF: eth0 state: down mac: <filter> Device-2: Qualcomm Atheros AR9271 802.11n type: USB driver: ath9k_htc bus ID: 1-4:4 chip ID: 0cf3:9271 serial: <filter> IF: wlan0 state: down mac: <filter> WAN IP: No WAN IP data found. Connected to the web? SSL issues? Drives: Local Storage: total: 149.05 GiB used: 3.51 GiB (2.4%) ID-1: /dev/sda vendor: Hitachi model: HCP725016GLAT80 size: 149.05 GiB block size: physical: 512 B logical: 512 B speed: <unknown> rotation: 7200 rpm serial: <filter> rev: A4CA scheme: MBR Optical-1: /dev/sr0 vendor: HL-DT-ST model: DVD-RAM GSA-H22N rev: 1.00 dev-links: cdrom,cdrw,dvd,dvdrw Features: speed: 48 multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram state: running RAID: Message: No RAID data was found. Partition: ID-1: / raw size: 29.59 GiB size: 29.00 GiB (98.01%) used: 3.51 GiB (12.1%) fs: ext4 dev: /dev/sda5 label: rootantiX19 uuid: 4cc8d1a2-4449-48df-a00a-bc326eed2407 ID-2: swap-1 size: 4.88 GiB used: 0 KiB (0.0%) fs: swap swappiness: 10 (default 60) cache pressure: 50 (default 100) dev: /dev/sda6 label: swap uuid: 83528a0c-ddf6-4c12-8eb1-2e27358725a5 Unmounted: ID-1: /dev/sda1 size: 1 KiB fs: <root required> label: N/A uuid: N/A ID-2: /dev/sda7 size: 114.57 GiB fs: ext4 label: antiX2 uuid: 281f3ca7-88f9-44d7-8c99-cdba87c5a42d 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: Qualcomm Atheros AR9271 802.11n type: Network driver: ath9k_htc interfaces: 1 rev: 2.0 speed: 480 Mb/s chip ID: 0cf3:9271 serial: <filter> 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: N/A type: Keyboard,HID driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 1.5 Mb/s chip ID: c0f4:01e0 Device-3: 2-2:3 info: Elan Micro Optical Mouse type: Mouse driver: hid-generic,usbhid interfaces: 1 rev: 1.1 speed: 1.5 Mb/s chip ID: 04f3:0235 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 Device-4: 4-2:2 info: Alcor Micro Flash Card Reader/Writer type: Mass Storage driver: usb-storage interfaces: 1 rev: 2.0 speed: 12 Mb/s chip ID: 058f:6362 serial: <filter> Hub: 5-0:1 info: Full speed (or root) Hub ports: 2 rev: 1.1 speed: 12 Mb/s chip ID: 1d6b:0001 Sensors: System Temperatures: cpu: 32.0 C mobo: N/A Fan Speeds (RPM): N/A Repos: Active apt repos in: /etc/apt/sources.list.d/antix.list 1: deb http: //ftp.cica.es/mirrors/Linux/MX-Packages/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.pt.debian.org/debian/ buster-updates main contrib non-free Active apt repos in: /etc/apt/sources.list.d/debian.list 1: deb http: //ftp.pt.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: 38.9% command: xorg pid: 2367 mem: 64.8 MiB (3.4%) 2: cpu: 4.0% command: yad pid: 3217 mem: 11.8 MiB (0.6%) 3: cpu: 2.2% command: [kworker/0:2] pid: 145 mem: 0.00 MiB (0.0%) 4: cpu: 1.7% command: [kworker/0:1] pid: 33 mem: 0.00 MiB (0.0%) 5: cpu: 1.7% command: gtkdialog pid: 3150 mem: 31.7 MiB (1.6%) Memory top: 5 1: mem: 70.2 MiB (3.7%) command: cmst pid: 2692 cpu: 0.9% 2: mem: 64.8 MiB (3.4%) command: xorg pid: 2367 cpu: 38.9% 3: mem: 48.2 MiB (2.5%) command: spacefm pid: 2677 cpu: 1.5% 4: mem: 31.7 MiB (1.6%) command: gtkdialog pid: 3150 cpu: 1.7% 5: mem: 16.9 MiB (0.8%) command: volumeicon pid: 2693 cpu: 0.1% Info: Processes: 172 Uptime: 2m Init: SysVinit v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Client: shell wrapper v: 5.0.3-release inxi: 3.0.36All responses will be received with interest.
- This topic was modified 2 years, 1 month ago by rokytnji.
My antiX “fu” is not strong enough for antiX-19 on an old computer
I was excited to try my hand at installing antiX-19 64-bit on an old computer I found at the recycling center. I had already setup MX-19 32-bit and antiX-19 32-bit on an old Pentium 4 with 3 GB of RAM with integrated Intel video. This “new” old computer was one step above my best P4 and I wanted to use antiX as it’s main OS.
This computer has an AMD Athlon 64 X2 3600+ dual core processor. It supports 64-bit, whereas my best P4 only supports 32-bit. It had 2 GB RAM but one of the RAM chips was bad. I moved one of the chips from the P4 over to get it back to 2GB, leaving the P4 with 3GB. This Athlon system is a Dell Dimension E521 and has integrated graphics and a few PCIe slots and the 16-bit PCIe slot has a GeForce 6600 NV43 class GPU.
I booted up a newly created LiveUSB with antiX-19.3 64-bit. It booted up good and I proceeded to partition the 250GB SATA hard drive I put in it. I created a / partition and a separate /home partition and another data partition and a swap partition, then I proceeded to install antiX-19 64-bit.
For the most part antiX-19 installed fine and is running well on this old machine. However, I soon found out that my antiX fu is not strong. My intent for this “new” old machine was to replace my old P4 HTPC and attach it to one of my 32” LCD TV’s in my lab, where I often watch more than one sports program at a time, such as now during March Madness where I can watch four games at once. My old P4 HTPC has not been used for this for a few years and was no longer connected to a big screen.
This “new” old machine had enough power to run Kodi and ESPN or NBC Sports, etc. I figured if my old P4 could run Kodi then this new machine could do it better. And I wanted it to be a new project focusing on using antiX. I had MX running on the old P4 and I knew I could set MX up but I wanted to use antiX since I knew it would be more of a challenge.
I ran into three or four problems using this machine, and a couple of them have still not been resolved. My antiX fu has been revealed as weak. But thanks to the forum it is getting a little stronger with this project.
First, I could not understand how to properly set up multiple screens in antiX. I did know that I could use arandr to set the resolutions and orientation of the screens. I had done this many times before with single screens. With a little bit of googling I was able to set the screens in my startup files. I use IceWM so I used the IceWM startup file for my xrandr statement. It works. But the login manager and the wallpapers were not set correctly.
I could not see the login entry dialog at all. It seems it was placed somewhere in the middle of my multi monitor setup and was invisible. I could type my username and password blindly and get into my desktop. But how do I get the login screen to show? I got some help in the forum and found out I had to edit a configuration file to orient the slim login to a place where it would show up. That config file is at /usr/share/slim/themes/antiX/slim.theme. I edited the “input_panel_x” and “input_panel_y” to move the sign in box to the upper left of the screen. [Note: the actual file to edit is dependent on the choice of theme. For instance: /usr/share/slim/themes/DarkCity/slim.theme]
Next, I could not figure out how to set two different wallpapers, each on one of the two monitors. There is a nice wallpaper tool in antiX and it works great for a single wall paper. But I wanted two wallpapers. As it turned out antiX does not support this out of the box. I had to learn how to use “feh” to set up the two wallpapers and I had to turn off any default “desktop manager” so as to not interfere with feh. Again, the forum members showed me that I had to turn off SpaceFM as the desktop manager and use only the “icewm” desktop. Once I did this I had my two separate wallpapers.
But a side effect of running “icewm” was that ROX became the default file manager. I had to edit another config file to allow SpaceFM as my default file manager. I ended up editing the file ~/.desktop-session/desktop-defaults.conf and changed OVERRIDE_SESSION_FM= to “true”. Then I edited /usr/share/applications/antix/desktop-defaults-follow-fm.desktop and commented out the “Exec=” line and added my own “Exec=spacefm” line. I restarted the session and now when I click on the “File Manager” item I get SpaceFM.
Before I changed to “icewm” the Conky was not fully transparent. The conky was readable but the background was from another part of the image. Once I switched to “icewm” only and was using “feh” as my wallpaper manager, the Conky was now properly transparent. Ahh, my antiX fu was improving – but still not strong.
Here’s the outline of steps needed to set two wallpapers, one each on two monitors, and correct the Conky transparency at the same time:
1. Switch your desktop away from “space” or “ROX” (In my case I chose “icewm”. I was using space-icewm). Space and ROX desktop managers conflict with the “feh” program that is used to set the multiple wallpapers. See below.
2. Comment out the line in /usr/local/bin/desktop-session that invokes the “desktop-session-wallpaper” script.
3. Run feh –bg-fill /path/to/wallpaper#1 /path/to/wallpaper#2. This will create a ~/.fehbg file.
4. Add ~/.fehbg & to your desktop startup file. I used ~/.icewm/startupSo, now my antiX fu is good enough to setup multiple monitors on antiX-19. But things did not go well when I tried to setup Kodi.
When I installed Kodi 18.9 from the Debian Multimedia repo and started it up the system crashed. It completely locked up with a black screen and I had to power down. When I restarted I had to repair the file system before I could boot. I used my Live USB and scanned and repaired the file system then rebooted again into antiX-19. I purged Kodi-18.9 and reinstalled Kodi-17.6 from the default repos. Kodi 17.6 works. But I wanted to have Kodi-18.9. Time for some stronger antiX fu. I gave it a try but my antiX fu did not turn out to be strong enough.
I am assuming that Kodi 18 may not crash if I could install the proprietary nvidia drivers for my GPU. I soon learned that antiX 19, being based on Buster, would not support the legacy nvidia driver I needed. I did some reading and found out that the drivers are supported in Stretch. So, I decided to install antiX-17.4 64-bit and try to install the legacy nvidia drivers.
I did get the legacy nvidia drivers installed in antiX-17.4. But when I tried to install Kodi 18.9 I could not find it in any repos for antiX-17. I downloaded a .deb file for Kodi 18.5 from the MX-17 repo. After the install it only started up 17.6. I purged Kodi again and tried to install Kodi 18.5 by adding the MX-17 testrepo to my source file. But it won’t install and gives me a report that it is missing dependencies.
As of now, I have been unsuccessful in getting Kodi 18 to work in antiX-17 or antiX-19. Kodi 17.6 is working. I am hopeful that I may yet learn how to install Kodi 18 and fix the dependencies. But for now, my antiX fu is not strong.
seaken64
- This topic was modified 2 years, 1 month ago by seaken64.
- This topic was modified 2 years, 1 month ago by seaken64.




