Is 4.9 kernel EOL?Nvidia GeForce4, NV17M issues with 4.19[Solved]

Forum Forums New users New Users and General Questions Is 4.9 kernel EOL?Nvidia GeForce4, NV17M issues with 4.19[Solved]

  • This topic has 25 replies, 3 voices, and was last updated Jan 7-6:37 am by andfree.
Viewing 11 posts - 16 through 26 (of 26 total)
  • Author
    Posts
  • #96672
    Moderator
    caprea
      Helpful
      Up
      1
      ::

      To add a boot-parameter permanently you have to change the “GRUB_CMDLINE_LINUX_DEFAULT” in
      /etc/default/grub

      Example , mine looks like that
      GRUB_CMDLINE_LINUX_DEFAULT="quiet"
      If I wanted to add your code , it would have to be changed to
      GRUB_CMDLINE_LINUX_DEFAULT="quiet nouveau.modeset=1"

      After you saved the changes run
      sudo update-grub

      It’s better to first try a boot parameter. You can do this by pressing the letter e on the boot screen.
      From the following screen go (with up and down, left and right arrows) to the line that starts with linux.
      Add your boot-parameter to the end (possibly it’s running over two lines) (use a space character and then your parameter) of that line and then press F10
      The PC will now boot for one time with the command for trying it out.

      You should control if the system is booted with your changes with the command

      cat /proc/cmdline
      

      If the parameter helps you can add it to /etc/default/grub permanently. Don’t forget to update grub afterwards.

      #96724
      Member
      andfree
        Helpful
        Up
        0
        ::
        $ cat /proc/cmdline
        BOOT_IMAGE=/boot/vmlinuz-4.19.0-256-antix.1-486-smp root=UUID=acc3c939-114e-4a66-a7a7-84666f9cfe27 ro quiet nouveau.modeset=1

        Thank you, but it doesn’t seem to make any difference.

        #96738
        Moderator
        caprea
          Helpful
          Up
          1
          ::

          Pity, did you do any attempts to install a nvidia driver on that system, this can cause sometimes backlistings of nouveau
          Please check if an /etc/X11/xorg.conf file exists .
          Could you post a inxi -Gxxx with that boot parameter active ?
          We could try to write a xorg.conf or 20-nouveau.conf, let’s see if I can find a good template for nouveau on the net.
          Does the newest antiX kernel 5.10.142 boot your system and did you already try it?

          • This reply was modified 4 months, 1 week ago by caprea. Reason: fixed typo
          #96740
          Member
          andfree
            Helpful
            Up
            0
            ::

            Does the newest antiX kernel 5.10.142 boot your system and did you already try it?

            Unbelievable. It seems to be OK. I hadn’t tried it, because I couldn’t think such a possibility as realistic. Many thanks.

            #96741
            Moderator
            caprea
              Helpful
              Up
              0
              ::

              This is a very pleasant solution.
              Please inxi -Gxxx
              or better inxi -zv7
              Please for information, I assume the parameter is not needed for 5.10.142 ?

              • This reply was modified 4 months, 1 week ago by caprea.
              #96744
              Member
              sybok
                Helpful
                Up
                0
                ::

                ‘inxi -Gxxx’ already present in https://www.antixforum.com/forums/topic/is-4-9-kernel-reaching-eol/#post-96590 (at the end of the code/quoted text).

                • This reply was modified 4 months, 1 week ago by sybok.
                #96746
                Moderator
                caprea
                  Helpful
                  Up
                  0
                  ::

                  Yes, I would like an inxi with the new 5.10.142-kernel, to see if the drivers are loaded correctly now.

                  #96852
                  Member
                  andfree
                    Helpful
                    Up
                    1
                    ::
                    $ inxi -zv7
                    System:
                      Kernel: 5.10.142-antix.2-486-smp arch: i686 bits: 32 compiler: gcc
                        v: 10.2.1 Desktop: IceWM v: 3.3.0 dm: slimski v: 1.5.0
                        Distro: antiX-21_386-base Grup Yorum 31 October 2021
                        base: Debian GNU/Linux 11 (bullseye)
                    Machine:
                      Type: Laptop System: TOSHIBA product: Satellite 2450 v: PS245E-03TE0-GK
                        serial: <superuser required> Chassis: type: 10 v: Version 1.0
                        serial: <superuser required>
                      Mobo: TOSHIBA model: Portable PC v: Version A0
                        serial: <superuser required> BIOS: TOSHIBA v: Version 1.30 date: 03/20/2003
                    Memory:
                      RAM: total: 997.7 MiB used: 525 MiB (52.6%)
                      RAM Report:
                        permissions: Unable to run dmidecode. Root privileges required.
                    CPU:
                      Info: single core model: Intel Pentium 4 bits: 32 arch: Netburst Northwood
                        rev: 7 cache: 512 KiB note: check
                      Speed (MHz): 2793 min/max: N/A core: 1: 2793 bogomips: 5586
                      Flags: acpi bts cid clflush cmov cpuid cx8 de dts fpu fxsr ht mca mce mmx
                        msr mtrr pae pat pbe pebs pge pse pse36 sep ss sse sse2 tm tsc vme xtpr
                    Graphics:
                      Device-1: NVIDIA NV17M [GeForce4 420 Go] vendor: Toshiba driver: nouveau
                        v: kernel arch: Kelvin ports: active: LVDS-1 empty: TV-1,VGA-1
                        bus-ID: 01:00.0 chip-ID: 10de:0175 class-ID: 0300
                      Display: server: X.Org v: 1.20.11 driver: X: loaded: nouveau
                        unloaded: fbdev,modesetting,vesa alternate: nv gpu: nouveau
                        display-ID: :0.0 screens: 1
                      Screen-1: 0 s-res: 1024x768 s-dpi: 96 s-size: 270x203mm (10.63x7.99")
                        s-diag: 338mm (13.3")
                      Monitor-1: LVDS-1 res: 1024x768 hz: 60 size: N/A modes: max: 1024x768
                        min: 640x350
                      OpenGL: renderer: Mesa DRI nv17 x86/MMX/SSE2 v: 1.2 Mesa 20.3.5
                        direct render: Yes
                    Audio:
                      Device-1: Intel 82801DB/DBL/DBM AC97 Audio vendor: Toshiba
                        driver: snd_intel8x0 v: kernel bus-ID: 00:1f.5 chip-ID: 8086:24c5
                        class-ID: 0401
                      Sound Server-1: ALSA v: k5.10.142-antix.2-486-smp running: yes
                    Network:
                      Device-1: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter
                        vendor: Toshiba driver: 8139too v: 0.9.28 port: ce00 bus-ID: 02:09.0
                        chip-ID: 10ec:8139 class-ID: 0200
                      IF: eth0 state: down mac: <filter>
                      Device-2: Qualcomm Atheros TP-Link TL-WN821N v2 / TL-WN822N v1 802.11n
                        [Atheros AR9170]
                        type: USB driver: carl9170 bus-ID: 1-3:2 chip-ID: 0cf3:1002
                        class-ID: ff00 serial: <filter>
                      IF: wlan0 state: up mac: <filter>
                      IP v4: <filter> scope: global broadcast: <filter>
                      IP v6: <filter> type: dynamic mngtmpaddr scope: global
                      IP v6: <filter> scope: link
                      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: 93.16 GiB used: 31.81 GiB (34.1%)
                      ID-1: /dev/sda vendor: Toshiba model: MK1032GAX size: 93.16 GiB
                        speed: <unknown> type: N/A serial: <filter> rev: 1A scheme: MBR
                      Optical-1: /dev/sr0 vendor: TOSHIBA model: DVD-ROM SD-R6012 rev: 1334
                        dev-links: cdrom,cdrw,dvd,dvdrw
                      Features: speed: 24 multisession: yes audio: yes dvd: yes
                        rw: cd-r,cd-rw,dvd-r state: running
                    Partition:
                      ID-1: / size: 89.65 GiB used: 31.81 GiB (35.5%) fs: ext4 dev: /dev/sda1
                        label: rootantiX21 uuid: acc3c939-114e-4a66-a7a7-84666f9cfe27
                    Swap:
                      ID-1: swap-1 type: partition size: 1.5 GiB used: 3.5 MiB (0.2%)
                        priority: -2 dev: /dev/sda2 label: swapantiX
                        uuid: 79119e85-3abd-4361-991c-23c420848b20
                    Unmounted:
                      Message: No unmounted partitions found.
                    USB:
                      Hub-1: 1-0:1 info: Full speed or root hub ports: 6 rev: 2.0 speed: 480 Mb/s
                        chip-ID: 1d6b:0002 class-ID: 0900
                      Device-1: 1-3:2 info: Qualcomm Atheros TP-Link TL-WN821N v2 / TL-WN822N
                        v1 802.11n [Atheros AR9170]
                        type: Network driver: carl9170 interfaces: 1 rev: 2.0 speed: 480 Mb/s
                        power: 500mA chip-ID: 0cf3:1002 class-ID: ff00 serial: <filter>
                      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: 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-4: 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
                    Sensors:
                      Message: No sensor data found. Is lm-sensors configured?
                    Info:
                      Processes: 122 Uptime: 22m wakeups: 2 Init: runit v: N/A runlevel: 2
                      default: 5 Compilers: gcc: 10.2.1 alt: 10 Packages: apt: 1555 Shell: Bash
                      v: 5.1.4 running-in: urxvt inxi: 3.3.19

                    I assume the parameter is not needed for 5.10.142

                    Right.

                    This kernel is supported till December 2026, isn’t it?

                    • This reply was modified 4 months ago by andfree.
                    #96919
                    Member
                    andfree
                      Helpful
                      Up
                      1
                      ::

                      A little more info:

                      Flags: acpi bts cid clflush cmov cpuid cx8 de dts fpu fxsr ht mca mce mmx msr mtrr pae pat pbe pebs pge pse pse36 sep ss sse sse2 tm tsc vme xtpr

                      This made me think to give a try to the pae version of the 5.10.142 kernel, but, when I booted it, the problem appeared again. So, I’ll stick with the non-pae version. I hope it will be OK till Dec, 2026. Once again, thanks for your help.

                      #96984
                      Moderator
                      caprea
                        Helpful
                        Up
                        0
                        ::

                        Thanks andfree. So, if I understand you right, you say that the non-pae kernel boots in the right resolution( with the right driver nouveau) and the pae kernel doesn’t on this PAE laptop.
                        Makes no sense to me, strange. I would say the 5.10 kernel is a longterm kernel.Then the year 2026 would apply. But only anticapitalista knows for sure.

                        #96988
                        Member
                        andfree
                          Helpful
                          Up
                          0
                          ::

                          you say that the non-pae kernel boots in the right resolution( with the right driver nouveau) and the pae kernel doesn’t on this PAE laptop.
                          Makes no sense to me, strange.

                          I actually said that the non-pae kernel is the only one that boots in the right resolution (with the right driver nouveau on its own; no need for me to do something for this).
                          I didn’t remember that this was a PAE laptop. I used non-pae kernels & I thought I had reasons to do so. I can’t explain it & I can’t find any older post of mine that would make it more sensible.

                          • This reply was modified 4 months ago by andfree.
                        Viewing 11 posts - 16 through 26 (of 26 total)
                        • You must be logged in to reply to this topic.