-
Search Results
-
Xecure
Thanks for the important feedback, marcelocripe.
To summarize, your experience with the vesa driver was:
– better resolution, no graphical glitches (no information about how it compared to previous performance) compared to the openchrome driver on VIA based machines.
– No graphical glitches but worked a bit slower (slower response) compared to using the fbdev driver on SIS based machines.In more detail:
1. Computer Gigabyte GA-8S661FXM-775 and SIS video chip.
Before (with graphical glitches and fbdev driver):
driver: fbdev resolution: 1024x768~N/A
Now (no graphical glitches but slower response on vesa driver):
driver: vesa resolution: 1024×768~61Hz2. Computer Asus P5V800-MX and VIA video chip.
Before (smaller resolution but higher refresh rate, using openchrome driver):
driver: openchrome resolution: 800x600~85Hz
Now (higher resolution on vesa driver):
driver: vesa resolution: 1024×768~N/A3. Computer ASUS P5S800-VM and SIS video chip.
Before (fbdev driver, not sure if there are graphical glitches)
– no inxi -G info (we asume similar to the other machine with SIS video chip).
Now (No glitches, not sure about response speed, on vesa driver)
driver: vesa resolution: 1024×768~N/AIt would be good to know if using fbdev with 24 bits color depth as linuxdaddy suggests can improve the experience on SIS machines without changing to a vesa driver (mainly the icons that disappear issue, that will probably influence other strange graphical behaviors). If all SIS video chips have a slower response on vesa, maybe fbdev with proper color depth can have an improved experience. Or maybe if compiling with linuxdaddy’s suggested driver may be even better.
“Centro de Controle”, em Sistema, clicando em “Gerenciador de Pacotes Synaptic”, abre o programa “Gerenciador de Aplicativos via Terminal” ou em inglês “Command line apt-based package manager”.
This is normal. On antiX base, Synaptic package manager is not installed. What is wrong is the translated text for pt_BR. That button in the menu in English is “Manage Packages”, and will launch Synaptic Package Manager if it is installed. If it is not installed, it will launch cli-aptiX instead. So the translation shouldn’t mention Synaptic package manager, but only “Package manager”. Anyway, that is not an error so we can consider it normal behavior.
Linuxdaddy, I would like to know more to be able to help you both in the development,
Your tests and experience are the most important feedback to let us know how everything is going. That is more than enough.
If there is a way to install with “vesa” and after installation always start with “vesa” I believe that it will no longer present the problems in the display of ISO menus “antiX-19-legacy-bet1_386-base.iso” that occur in normal mode.
For live booting, using “xorg=safe” is enough (I think). For installed systems, uninstalling xserver-xorg-video-fbdev for SIS systems and xserver-xorg-video-openchrome for VIA computers should be enough, but that is not possible right now, as I didn’t install them separately from main xserver-xorg package.
I will improve that aspect and hopefully tomorrow get a new iso out, which you can test next week and weekend. Sleep well and make use only on big chunks of time. You say you spend a lot of time during the week moving on public transport, and getting home late and tired. Rest and leave the tests for the weekend.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.Xecure
Thanks for the tests, marcelo. If it is similar experience to antiX 16 but better than the default 19 for those old sis and via chips, then we are improving. If the experience is worse than original antiX 19, then this project is going nowhere.
I will try to figure out what is going on with the menu script, but probably it would be fixed as linuxdaddy suggests.As far as the menus repeating hit refresh menu upon first boot and that straightens them up.
Thanks for helping, linuxdaddy. If you can test it on your sis machine and it boots to a graphical interface using openchrome xorg driver, then we can confirm that this project has a future. It isn’t the safest antiX version, but it can complement it for machines that have problems booting with the original.
I will try building a new iso on the weekend and see if some improvements can be made (including autolog-in and figuring out the icon and menu problems).
About the firmware package firmware-netronome, as it doesn’t seem to be common, I will remove it from the lists.Thanks everyone for your input.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.Xecure
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: 800×600~85Hz
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.1 Mesa 18.3.6
direct render: YesThis is what we were aiming for. There is good news here.
If possible, I would like you to write how good or bad the experience of using this test iso is compared to using antiX 16. Is video, display and transitions as fluid as in antiX 16? Does things load or move as slow as when you were using antiX 19? Any Graphical glitches? Any screen blinking? Does resizing the screen resolution in arandr break the display?
flaws in the menus
If possible, when you have time, could you share a screenshot so we can better understand what this is? If this is related to item duplication, text using strange symbols or missing items, etc. It would be good to know if this can be solved easily of if something I did broke some of the scripts the antiX system uses.
Overall, it seems to be a positive experience. Hopefully we can find out the errors and I can continue learning how the build-iso and the antiX system works so we can improve on a next iteration.
@Xecure, não é ganancia. É felicidade, euforia, ansiedade e esperança.
I understand the excitement, but you need to relax a bit. This is a test and can lead nowhere, so we need to take this with a cool head.
I was meaning the “greedy” part as wanting as many people to get involved as possible, but everyone, as you, have their life and possibly a project like this consumes a lot of time. If the few of us can spearhead this project, we can do as some other linux communities and have a “Community Release”.
See this topic to understand between Official release and Community release in the Manjaro project:
https://classicforum.manjaro.org/index.php?topic=17398.0Community Editions have the consent of the Official team, but are in the hands of the community (and we take responsibility, not the official team). We shouldn’t ask too much and try to figure out as much as possible ourselves. We can also customize it as much as we want, so some things may look different or other programs may be the default (we could probably replace firefox-esr with non-pae palemoon, as the aim is for legacy and abandoned hardware).
antiX Live system enthusiast.
General Live Boot Parameters for antiX.
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 inexistenteXecure
Xecure, here was someone with another distro, same issue solved, but its too advanced for me…
https://forum.peppermintos.com/index.php/topic,5761.0.htmlThe problem here is that they don’t list the driver for the card, but they do for the Display.
Graphics: Card: VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] Display Server: X.Org 1.18.4 drivers: vesa (unloaded: fbdev) Resolution: 1024x768@0.00hzFor marcelocripe, the driver for the graphic card does not load.
Graphics Device-1: VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] vendor: Micro-Star MSI driver: N/A Display: server: X.org 1.20.4 driver: fbdev,modesetting,vesa unloaded: openchrome tty: 128×48marcelocripe, you could try as BoBC suggests. Boot an antiX 19 live system, and try adding the boot parameter
xorg=vesa
Or even
xorg=openchrome
If nothing comes up, please try booting an antiX 17.4.1 live system (adding the same boot parameter) and see if a graphical environment loads properly.I suspect your system is UEFI Bios, but just in case I will explain the steps for both.
On Legacy BIOS, antiX will boot with an interface that has at the bottom many “Fn” Options. It looks something like this:
In the middle, there will be a line containing the boot options. Add the xorg=vesa parameter at the end of the line and hit EnterOn UEFI BIOS systems, antiX boot menu will look something like
Hitting ‘e’ you can see the boot parameters (example below, don’t copy)
In the same line as “menus”, before it, add “xorg=vesa”. Then hit F10 to boot and see if it works.Looking at BobC’s linked thread, I can see two main differences between their system and marcelocripe’s system:
marcelocripe: Server: X.Org 1.20.4, kernel 4.9
theotherguys: Server: X.Org 1.18.4, kernel 4.8
If Xorg version is not the problem, it could be a kernel problem. Probably kernel 4.4 in the repos could fix the problem (if it is kernel related). I tried to build an iso with 4.4 to share here but my computer doesn’t boot with it, so I cannot test if it would work.Let us see how this evolves once marcelocripe has time to test these out.
If it is too much of a bother, we can stop after testing BobC’s xorg=vesa suggestion. All these tests take time and sooner or later will drain oneself of energy. We are not trying to pressure you to do more than you are willing to do, marcelocripe.
antiX Live system enthusiast.
General Live Boot Parameters for antiX.
Forum for users of antiX Linux. Mean and Lean and Proudly anti-fascist.
