new kernels available

Forum Forums News Announcements new kernels available

  • This topic has 20 replies, 8 voices, and was last updated Aug 7-11:45 am by Xecure.
Viewing 6 posts - 16 through 21 (of 21 total)
  • Author
    Posts
  • #36259
    Member
    XecureXecure

    is that still good or do I need to upgrade to 4.19.120.

    Warning: This is my opinion. The following is based on what I believe is OK, but others may disagree. Most will encourage you to update to the newest kernel for security reasons.

    In my opinion, you are still good. The update is recommended but not a necessary thing. I have spent many months not updating the kernel because it worked just fine. I took advantage of the new announcement by anticapitalista to make an excuse and install the new kernel, so now I am “up to date”. For your case, updating between 4.19.xxx is extremely easy and will rarely lead to compatibility problems.

    A lot of people are obsessed with having all packages completely up to date every single day (reason why a lot of people were giving bad reviews of antiX in Distrowatch and sparked the creativity of the forum members to find a solution, now available for all new antiX versions), but I believe it is ok to update once o week or less often. Updates are to fix things or add new ones. Most of the time, things will work and updating is just an extra (and sometimes, an update can break the program you were just perfectly using the day before). I believe this is the mentality of someone living in Stable. When things are broken is when you check daily, hoping for an update to come out soon. For people who want the bleeding edge and sometimes need to update daily, living in sid is what they enjoy.

    What I usually do is the old sudo apt update && sudo apt dist-upgrade every week or so, and not daily. Every few months I update the kernel, which is very easy with antiX. I like to use cli-aptiX to see the version I specifically want to install and the ones already installed, though most will use the antiX package manager. Once installed, reboot and it automatically starts the newest installed update. That simple.

    If you are asking “should I install the newest 4.19.xxx kernel?”, I would say, if at some point you spend time searching and installing new packages using apt or synaptic, you can also make use of that time and update the kernel. Don’t feel nervous about it, as most times it will be harmless.

    If you are asking because you are afraid it will break your system, then you don’t have to worry. If after updating the kernel you find your system not working properly, simply restart and, in the grub menu, select the previous working kernel and you will be back to your working system (you then remove the just installed kernel to avoid future problems).

    If you are asking because you are in a live-USB system and would need to remaster after installing the new kernel and really don’t feel like it, then wait and install it next time you need to remaster.

    With all so many words, all that I am trying to say is: “It’s up to you”.

    #36261
    Member
    Noman01Noman01

    Thanks so much for the feed back, will go ahead and update just to keep things current.

    • This reply was modified 2 months, 2 weeks ago by Noman01.

    If we put as much effort into helping each other as we do trying to control and run other people’s lives, we would have a much better world.

    AntiX 19.1 runit 32bit

    #39864
    Member
    namida12namida12

    Typing this from another computer, not the Ryzen 5 3400G that will not boot:

    Cannot boot newer Kernel, installed 5.6.10 from package manager

    starts to boot – I get a black screen, about 20 seconds then line after line rapidly scroll.

    Then it appears is is going to boot yet I have a few errors
    [ 66.816718] kfd kfd: error getting iommu info. is the iommu enabled?
    [ 66.816723] kfd kfd: Error initiallizing iommuv2
    [ 66.816825] kfd kfd: device 1002:15d8 NOT added due to errors
    [ 66.877416] udevd[607]: error opening ATTR{/sys/devices/pci0000:00/0000:00:08:.1/0000:07:00.0/firmware/amdgpu!picasso_ta.bin/loading) for writing: No such file or Directory

    Then just before it stops <———-
    [ ok ] Starting slim:slim
    [ ok ] Starting OpenBSD Secure Shell server: sshd
    Applying power save settings…done
    Applying battery charge thresholds…done
    [ ok ] Virtualbox Additions disabled, not in a Virtual Machine

    Welcome to antiX. Powered by Debian.
    green611 login: [ 68.861662] [drm:mod_hcdcp_add_display_topology {amdgpu}} *ERROR* Failed to add display topology, DTM TA is not Initialized

    I included inxi -F from older Kernel to show system info

    $ inxi -F
    System:    Host: green611 Kernel: 4.19.100-antix.1-amd64-smp x86_64 bits: 64 Desktop: IceWM 1.6.6 
               Distro: antiX-19.2-4.19_kernel_x64-full Hannie Schaft 6 April 2020 
    Machine:   Type: Desktop Mobo: ASRock model: B450M Pro4 serial: <root required> UEFI [Legacy]: American Megatrends v: P3.90 
               date: 12/09/2019 
    CPU:       Topology: Quad Core model: AMD Ryzen 5 3400G with Radeon Vega Graphics bits: 64 type: MT MCP L2 cache: 2048 KiB 
               Speed: 1945 MHz min/max: 1400/3700 MHz Core speeds (MHz): 1: 1300 2: 1354 3: 1647 4: 1370 5: 1334 6: 1406 7: 1407 
               8: 1260 
    Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Picasso 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] 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: ALSA v: k4.19.100-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: a8:a1:59:0d:db:5a 
    Drives:    Local Storage: total: 465.76 GiB used: 182.40 GiB (39.2%) 
               ID-1: /dev/nvme0n1 vendor: Western Digital model: WDS500G3XHC-00SJG0 size: 465.76 GiB 
    Partition: ID-1: / size: 14.70 GiB used: 5.35 GiB (36.4%) fs: ext4 dev: /dev/nvme0n1p2 
               ID-2: /home size: 434.06 GiB used: 177.05 GiB (40.8%) fs: ext4 dev: /dev/nvme0n1p4 
               ID-3: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p3 
    Sensors:   System Temperatures: cpu: 37.6 C mobo: N/A 
               Fan Speeds (RPM): N/A 
    Info:      Processes: 217 Uptime: 2m Memory: 13.62 GiB used: 672.3 MiB (4.8%) Shell: bash inxi: 3.0.36 
    
    • This reply was modified 5 days, 18 hours ago by namida12. Reason: adding inxi-F info from older Kernel
    • This reply was modified 5 days, 18 hours ago by namida12.
    • This reply was modified 5 days, 16 hours ago by namida12.
    #39885
    Member
    namida12namida12

    Found this info enabling iommu in my ASRock motherboard – Checked it was disabled. I change that to enable.

    ASRock X570M Pro4 – How do I enable IOMMU? from ASRock

    Advanced –> AMD CBS –> NBIO –> there is an Option for IOMMU. Was disabled, changed to enable

    these errors disappeared

    [ 66.816718] kfd kfd: error getting iommu info. is the iommu enabled?
    [ 66.816723] kfd kfd: Error initiallizing iommuv2
    [ 66.816825] kfd kfd: device 1002:15d8 NOT added due to errors

    Currently still stuck with these errors

    [ 66.877416] udevd[607]: error opening ATTR{/sys/devices/pci0000:00/0000:00:08:.1/0000:07:00.0/firmware/amdgpu!picasso_ta.bin/loading) for writing: No such file or Directory
    and 
    Welcome to antiX. Powered by Debian.
    green611 login: [ 68.861662] [drm:mod_hcdcp_add_display_topology {amdgpu}} *ERROR* Failed to add display topology, DTM TA is not Initialized

    I can sign in with user name and password, but stuck in command line.
    startx fails…

    • This reply was modified 5 days, 13 hours ago by namida12.
    • This reply was modified 4 days, 21 hours ago by namida12.
    #39895
    Member
    namida12namida12

    When I could not post here, or had duplicate posting error, I posted in the antiX section of MX forums and have had responses there.

    https://forum.mxlinux.org/viewtopic.php?f=40&t=59673&p=590680#p590680

    I do not know how to copy and post from the inxi -F command without a mouse, but it shows no graphic driver.

    
    Kernel: 4.19.100-antix.1-amd64-smp x86_64 
    Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Picasso 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
    
    
    Kernel: 5.6.10-antix.1-amd64-smp x86_64
    Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Picasso driver: amdgpu v: kernel
               Display: x11 server: X.Org 1.20.4 driver: none unloaded: vesa resolution: 240x67
               Message: Advanced graphics data unavailable in console. Try -G --display
    
    inxi -G --display
    Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Picasso driver: amdgpu v: kernel
               Display: x11 server: X.Org 1.20.4 driver: none unloaded: vesa resolution: 240x67
               Message: No advanced graphics data found on this system
    

    JR

    #39947
    Member
    XecureXecure

    What i see:
    kernel 4.19; cannot load amd driver. Xorg uses vesa as driver.
    kernel 5.6; can load amd kernel but Xorg cannot. You may be missing a package (xserver-xorg-video-amdgpu, xserver-xorg-video-ati or something similar), some new firmware (as suggested in the mx forum), mesa-utils package or who knows.
    If you want to also use vesa with kernel 5.6, try the boot parameter nomodeset

Viewing 6 posts - 16 through 21 (of 21 total)
  • You must be logged in to reply to this topic.