antiX-19-b3-full and base versions (64 and 32 bit) available

Message
Author
User avatar
zebedeeboss
Posts: 84
Joined: Mon Dec 27, 2010 1:33 am

Re: antiX-19-b3-full and base versions (64 and 32 bit) available

#31 Post by zebedeeboss »

BitJam wrote: Sun Sep 08, 2019 1:15 am If you want to, you could see if the new nuke option would work for you. Use the boot parameters:

Code: Select all

nomodeset
xorg=vesa
bp=b9
This last one should open up a Bash shell right before we boot the system. Then try nuking the nouveau driver with these two commands:

Code: Select all

find /lib/modules/ -name nouveau.ko -delete
depmod
This will remove the nouveau module and rebuild the module dependency indexes so the system knows the module is not there any more.

If this works then the nouveau driver will not get loaded and you will get to X with the vesa driver. There should be a file created at /etc/X11/xorg.conf that tells X to load the vesa driver. If we don't create this file then you should still get to X but using the fbdev driver so the X resolution will be pegged to the resolution of the consoles, which actually might be okay/better than using vesa if you are booting UEFI.
Hi, not sure if I followed the post correctly but this did not work. Boot to usb - change the linux boot line to include the three items above, boot, get the normal start up options not a bash shell, just a normal tty root prompt. Typing the find command resulted in an error about the command appearing before the directory or visa versa - apologies forgot to take a photo.

Just as a note - this is not exclusive to antiX / MX - this is a nouveau issue where they have not done ANY work yet on any on the RTX nvidia range https://nouveau.freedesktop.org/wiki/FeatureMatrix/

Regards Zeb...
Linux User #565092
ASUS Prime X399-A | AMD Ryzen™ Threadripper 2950X Processor | 64GB Corsair VENGEANCE RGB DDR4 3000MHz | Zotac RTX™ 4070 | Gigabyte RTX3050 |49" Samsung Odyssey G9 QLED Dual-QHD 240Hz, Monitor 5120x1440 | Samsung 970 EVO Plus 1Tb

User avatar
Fritx
Posts: 59
Joined: Thu Aug 22, 2019 11:11 am

Re: antiX-19-b3-full and base versions (64 and 32 bit) available

#32 Post by Fritx »

After an upgrade, the alternativ-desktop-menu-entries are different. JWM exists multiple times, IceWM does not exist anymore.

User avatar
seaken64
Posts: 819
Joined: Wed Jan 02, 2019 2:43 pm

Re: antiX-19-b3-full and base versions (64 and 32 bit) available

#33 Post by seaken64 »

Fritx wrote: Tue Sep 10, 2019 7:45 am After an upgrade, the alternativ-desktop-menu-entries are different. JWM exists multiple times, IceWM does not exist anymore.
I've noticed the same. No IceWM choices in Other Desktop menu. This is from a full dist-upgrade on a 19b2 install. But on my 19b3 LiveUSB the menu is normal.

Seaken64
MX21-64 XFCE & W11 on Lenovo 330S LT. MX21-KDE & MX21-XFCE on Live USB.
MX18-64 & W7, Fedora on HP Core2 DT
MX21-32 XFCE w/ MX-Fluxbox on P4HT DT w/ antiX21, SUSE Tumbleweed, Q4OS, WXP
antiX21 on Compaq PIII 1 Ghz DT, w/ Debian, MX18FB, W2K

User avatar
namida12
Posts: 437
Joined: Sun Apr 01, 2007 4:54 pm

Re: antiX-19-b3-full and base versions (64 and 32 bit) available

#34 Post by namida12 »

Have tried newer kernels after having done the UEFI/Bios update in windows install Still no luck.

Removed the M2 and took tower to friends, he created a Flash drive to install windows 10 in a hard drive installed in this system, was very slow with Win10 installed. Did 2 bios upgrades, and decided to check and see if we could boot from newer kernels - Still not possible...

MX 18.3_64 Continuum May 26 2019 with Kernel 4.19.0.05-amd x86_64 runs fine on this motherboard & processor yet, Antix does have that Kernel to try with beta3 installed, but it does not boot beyond setting up battery as reported earlier. See attached image

Went from American Megatrends v: P1.10 date: 06/19/2018 to v: P2.00 date: 12/18/2018 and there is no change in Kernel abilities in this Motherboard, CPU booting ability.

Code: Select all

$ inxi -F
System:    Host: antix3 Kernel: 4.9.189-antix.1-amd64-smp x86_64 bits: 64 Desktop: IceWM 1.5.5+git20190610 
           Distro: antiX-19.b3_x64-full Marielle Franco 16 August 2019 
Machine:   Type: Desktop Mobo: ASRock model: B450M Pro4 serial: <root required> UEFI [Legacy]: American Megatrends v: P2.00 
           date: 12/18/2018 
CPU:       Topology: Quad Core model: AMD Ryzen 3 2200G with Radeon Vega Graphics bits: 64 type: MCP L2 cache: 2048 KiB 
           Speed: 1600 MHz min/max: 1600/3500 MHz Core speeds (MHz): 1: 1600 2: 1600 3: 1600 4: 1600 
Graphics:  Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] driver: N/A 
           Display: x11 server: X.Org 1.20.4 driver: vesa resolution: 1920x1080~N/A 
           OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6 
Audio:     Device-1: Advanced Micro Devices [AMD/ATI] driver: snd_hda_intel 
           Device-2: Advanced Micro Devices [AMD] driver: snd_hda_intel 
           Device-3: Logitech HD Pro Webcam C920 type: USB driver: snd-usb-audio,uvcvideo 
           Sound Server: ALSA v: k4.9.189-antix.1-amd64-smp 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: 70:85:c2:a3:6e:27 
Drives:    Local Storage: total: 447.13 GiB used: 299.30 GiB (66.9%) 
           ID-1: /dev/nvme0n1 vendor: Corsair model: Force MP510 size: 447.13 GiB 
Partition: ID-1: / size: 15.62 GiB used: 5.53 GiB (35.4%) fs: ext4 dev: /dev/nvme0n1p3 
           ID-2: /home size: 419.30 GiB used: 293.77 GiB (70.1%) fs: ext4 dev: /dev/nvme0n1p4 
           ID-3: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p2 
Sensors:   Message: No sensors data was found. Is sensors configured? 
Info:      Processes: 158 Uptime: 58m Memory: 5.82 GiB used: 311.6 MiB (5.2%) Shell: bash inxi: 3.0.33 
green602@antix3:~

Above my head or knowledge...


JR
You do not have the required permissions to view the files attached to this post.

User avatar
namida12
Posts: 437
Joined: Sun Apr 01, 2007 4:54 pm

Re: antiX-19-b3-full and base versions (64 and 32 bit) available

#35 Post by namida12 »

namida12 wrote: Fri Sep 06, 2019 1:40 pm Quad Core model: AMD Ryzen 3 2200G with Radeon Vega Graphics, has problem playing video.

Trying to watch a video, it plays then fades out (screen goes black) then plays again. Sound continues properly. the 5 second long video toggles video/black screen. This did not happen in AMD Ryzen 3 2200G with B2 the video played.
Graphics: Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] driver: N/A
Display: x11 server: X.Org 1.20.4 driver: vesa resolution: 1920x1080~N/A
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6

Same mkv video plays properly on Quad Core model: AMD Athlon II X4 630 - On system or from a flash drive.
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] RV670 [Radeon HD 3690/3850] driver: radeon v: kernel
Display: x11 server: X.Org 1.20.4 driver: ati,radeon unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: AMD RV670 (DRM 2.49.0 / 4.9.189-antix.1-amd64-smp LLVM 7.0.1) v: 3.3 Mesa 18.3.6

Do I need to install AMD drivers for the Ryzen 3 2200G?

JR
Quoting my own post: MKV will not play correctly in this system - MP4, AVI video play just fine.
antix3 Kernel: 4.9.189-antix.1-amd64-smp x86_64 bits:

User avatar
Richard
Posts: 1577
Joined: Fri Dec 12, 2008 10:31 am

Re: antiX-19-b3-full and base versions (64 and 32 bit) available

#36 Post by Richard »

@moltke
Re: https://forum.mxlinux.org/viewtopic.php ... 20#p526183

Curious.

In MX I get the following results.

I have 2 external hdd drives in fstab
and several USB pen drives.
They are all mounted at boot, if plugged in.

If not plugged, I notice a quick warning that it didn't mount. If plugged in after boot, they get mounted automatically.

My netbook with MX and antiX-17.x did also.
It has ax19b2 at present but not at hand.

I think there are differences in mount handling between ax and MX. Maybe show your /etc/fstab to see what might have changed?
Might give a clue.
Thinkpad T430 & Dell Latitude E7450, both with MX-21.3.1
kernal 5.10.0-26-amd64 x86_64; Xfce-4.18.0; 8 GB RAM
Intel Core i5-3380M, Graphics, Audio, Video; & SSDs.

User avatar
Moltke
Posts: 229
Joined: Tue Dec 19, 2017 6:07 pm

Re: antiX-19-b3-full and base versions (64 and 32 bit) available

#37 Post by Moltke »

Richard wrote: Sat Sep 14, 2019 3:36 am @moltke
Re: https://forum.mxlinux.org/viewtopic.php ... 20#p526183

Curious.

In MX I get the following results.

I have 2 external hdd drives in fstab
and several USB pen drives.
They are all mounted at boot, if plugged in.

If not plugged, I notice a quick warning that it didn't mount. If plugged in after boot, they get mounted automatically.

My netbook with MX and antiX-17.x did also.
It has ax19b2 at present but not at hand.

I think there are differences in mount handling between ax and MX. Maybe show your /etc/fstab to see what might have changed?
Might give a clue.
Not sure Im following. What is it exactly your point? I don't want it to be auto-mounted but have the option to if click on it, which it doesn't, instead I get that error message and have to manually mount it from terminal

Code: Select all

sudo mount /dev/sda1 /mnt
I really dont mind that much doing this but it'd be nice being able to simply open spacefm, click on the usb device and voila! It gets mounted, unfortunately, it doesn't. It seems to me that it has something to do with nfts only since fat works just fine.
Without each other's help there ain't no hope for us :happy:

User avatar
Richard
Posts: 1577
Joined: Fri Dec 12, 2008 10:31 am

Re: antiX-19-b3-full and base versions (64 and 32 bit) available

#38 Post by Richard »

that's the fact that my usb hdd won't mount, instead I have to manually.
Sorry, my error. I misunderstood your intention.
Thinkpad T430 & Dell Latitude E7450, both with MX-21.3.1
kernal 5.10.0-26-amd64 x86_64; Xfce-4.18.0; 8 GB RAM
Intel Core i5-3380M, Graphics, Audio, Video; & SSDs.

User avatar
Richard
Posts: 1577
Joined: Fri Dec 12, 2008 10:31 am

Re: antiX-19-b3-full and base versions (64 and 32 bit) available

#39 Post by Richard »

@moltke,
Please post your /etc/fstab contents.

I use the defaults option on mine; but,
if you add noauto after defaults then it won't mount at boot but should when you click it in Spacefm.

Note: if using defaults, then will also need
to add after defaults:
owner - if you are owner
user - if you want to allow others to mount

HTH
Thinkpad T430 & Dell Latitude E7450, both with MX-21.3.1
kernal 5.10.0-26-amd64 x86_64; Xfce-4.18.0; 8 GB RAM
Intel Core i5-3380M, Graphics, Audio, Video; & SSDs.

User avatar
Moltke
Posts: 229
Joined: Tue Dec 19, 2017 6:07 pm

Re: antiX-19-b3-full and base versions (64 and 32 bit) available

#40 Post by Moltke »

Richard wrote: Mon Sep 16, 2019 4:56 am @moltke,
Please post your /etc/fstab contents.

I use the defaults option on mine; but,
if you add noauto after defaults then it won't mount at boot but should when you click it in Spacefm.

Note: if using defaults, then will also need
to add after defaults:
owner - if you are owner
user - if you want to allow others to mount

HTH
First of all, sorry for the late, late ... late reply, been kind of busy. I use the defaults in mine too, mostly because I don't know much about that and honestly never have had to use any extra options before since I've been able to (as far as I recall) in every distro I've tried mount that same usb hdd in the file manager. Just to be clear; problem is that the HDD won't mount via file manager (spacefm, rox) when clicking on it, instead I have to open a terminal and mount it manually, which I don't really mind that much but still ... also, this behaviour changes/ends if I install a DE i.e xfce4, which I did, I open thunar/spacefm, click on the USB HDD and it gets mounted, it still fails to mount in rox though.

Image

I don't think it has anything to do with fstab, however, here's the contents of it:

Code: Select all

 
 # /etc/fstab: static file system information
#
# Created by make-fstab on Mon Sep 23 13:10:22 -04 2019

# <file system>                            <mount point>                               <type>     <options>                       <dump/pass>

# Added by make-fstab /dev/mmcblk0p1
UUID=F6F6-E70B                             /media/mmcblk0p1                            vfat       noauto,uid=1000,gid=users,dmask=002,fmask=113,users  0 0
# Added by make-fstab /dev/mmcblk0p2  label=swap
UUID=405b83ef-525e-44af-8f5e-9bffee96f062  swap                                        swap       defaults                        0 0
# Added by make-fstab /dev/mmcblk0p3
UUID=07A0-6A3F                             /media/mmcblk0p3                            vfat       noauto,uid=1000,gid=users,dmask=002,fmask=113,users  0 0
# Added by make-fstab /dev/sda1
UUID=473ADE5F06DA01C1                      /media/sda1                                 ntfs-3g    noauto,noexec,uid=1000,gid=users,dmask=002,fmask=113,users  0 0
# Added by make-fstab /dev/sdb1  label=antiX-Live-usb
UUID=5d2a8f98-7c71-411b-b247-11f6712b8064  /live/boot-dev                              ext4       noauto,exec                     0 0
# Added by make-fstab /dev/sdb2  label=antiX-uefi
UUID=7994-CE84                             /media/antiX-uefi                           vfat       noauto,uid=1000,gid=users,dmask=002,fmask=113,users  0 0
# Added by make-fstab /dev/sr0
/dev/sr0                                   /media/sr0                                  auto       noauto,exec,users,ro            0 0
And this is the fstab from antiX with XFCE where the usb hdd does mount if I click on it in thunar/spacefm but fails in rox, which I can't do in the other with no xfce but the defaults wms in spacefm and/or rox.

Code: Select all

# /etc/fstab: static file system information
#
# Created by make-fstab on Mon Sep 23 13:10:22 -04 2019

# <file system>                            <mount point>                               <type>     <options>                       <dump/pass>

# Added by make-fstab /dev/mmcblk0p1
UUID=F6F6-E70B                             /media/mmcblk0p1                            vfat       noauto,uid=1000,gid=users,dmask=002,fmask=113,users  0 0
# Added by make-fstab /dev/mmcblk0p2  label=swap
UUID=405b83ef-525e-44af-8f5e-9bffee96f062  swap                                        swap       defaults                        0 0
# Added by make-fstab /dev/mmcblk0p3
UUID=07A0-6A3F                             /media/mmcblk0p3                            vfat       noauto,uid=1000,gid=users,dmask=002,fmask=113,users  0 0
# Added by make-fstab /dev/sda1
UUID=473ADE5F06DA01C1                      /media/sda1                                 ntfs-3g    noauto,noexec,uid=1000,gid=users,dmask=002,fmask=113,users  0 0
# Added by make-fstab /dev/sdb1  label=antiX-Live-usb
UUID=5d2a8f98-7c71-411b-b247-11f6712b8064  /live/boot-dev                              ext4       noauto,exec                     0 0
# Added by make-fstab /dev/sdb2  label=antiX-uefi
UUID=7994-CE84                             /media/antiX-uefi                           vfat       noauto,uid=1000,gid=users,dmask=002,fmask=113,users  0 0
# Added by make-fstab /dev/sr0
/dev/sr0                                   /media/sr0                                  auto       noauto,exec,users,ro            0 0
As you might have noticed, they look the same so again, I don't think the problem's here unless there's something I'm not seeing, which I doubt but if so, please do tell me.
Without each other's help there ain't no hope for us :happy:

Post Reply

Return to “antiX”