ibm450

  • Oct 25, 2024
  • Joined Oct 4, 2021
  • 0 best answers
  • did u add workgroup/samba into your credentials file?

    credentials

    username=tolga
    domain=workgroup
    password=xxxxxx

    i also add 777 into my mount options, i dont care, im the only one using it:

    fstab

    # -------------------------------------------------- #
    # Server mount points
    # -------------------------------------------------- #
    //192.168.0.14/documents/TEST /mnt/Mint21-Doc cifs credentials=/etc/samba/credentials,file_mode=0777,dir_mode=0777 0 0
    sudo eopkg it cifs-utils
    sudo chmod 600 /etc/samba/credentials
    sudo chown root:root /etc/samba/credentials
     sudo systemctl daemon-reload
     sudo mount -a

    if your using the gnome version u may have to manually add the mount point manually, gnome is poor in this compared to kde: obviously change to suit
    echo "file:///mnt/MINT Documents" >> ~/.config/gtk-3.0/bookmarks

    nautilus -q

    personal alias:
    alias tolga-samba='echo "Restarting Samba" -- sleep 2 && sudo systemctl enable smb.service nmb.service && sudo systemctl restart smb.service nmb.service'
    alias tolga-solus='sudo mount -a && sudo systemctl daemon-reload && sudo udevadm control --reload-rules && sudo udevadm trigger && sudo sysctl --system'

  • Ok.. found and interesting issue. The latest update/kernel is causing my laptop to run HOT when viewing YouTube or running a vm

    Hp folio 9470m

  • Wow 👌 I have nvidia gt1030 on pascal architecture so I'll be interested to join in on the testing team especially when nvidia 560 drivers come out with full open source compatibility

  • how to install the nvidia cuda libraries and packages in solus please

  • Staudey

    Ok, these are the steps taken

    sudo clr-boot-manager mount-boot

    cd /boot/loader

    sudo gedit loader.conf

    added console-mode max into the loader.conf

    so it looks like this:

    timeout 3
    console-mode max
    default Solus-current-6.8.12-293.conf

    saved and exit. i didnt execute sudo clr-boot-manager update as that wipes out the extra enteries in loader.conf

    At reboot, i got the full resoultion on the systemD boot?

    Your thoughts on how to keep this permanent ?

    Quick access:

    alias boot="sudo clr-boot-manager mount-boot && cd /boot/loader && sudo gedit loader.conf"

    console-mode options:

    console-mode max
    console-mode auto
    console-mode 0
    console-mode 1
    console-mode 2
    console-mode keep
    • ok found this on the live iso in the isolinux.cfg

      ui vesamenu.c32
      timeout 50
      default live
      
      MENU RESOLUTION 1024 768
      menu title Solus 4.5 (GNOME)
      menu background splash.png
      MENU COLOR screen       37;40      #80ffffff #00000000 std
      MENU COLOR border       30;44   #40ffffff #a0000000 std
      MENU COLOR title        1;36;44 #ffffffff #a0000000 std
      MENU COLOR sel          7;37;40 #e0ffffff #20ffffff all
      MENU COLOR unsel        37;44   #50ffffff #a0000000 std
      MENU COLOR help         37;40   #c0ffffff #a0000000 std
      MENU COLOR timeout_msg  37;40   #80ffffff #00000000 std
      MENU COLOR timeout      1;37;40 #c0ffffff #00000000 std
      MENU COLOR msg07        37;40   #90ffffff #a0000000 std
      MENU COLOR tabmsg       31;40   #ffDEDEDE #00000000 std
      MENU HIDDEN
      MENU HIDDENROW 7
      MENU WIDTH 78
      MENU MARGIN 15
      MENU ROWS 4
      MENU VSHIFT 17
      MENU HSHIFT 25
      MENU TABMSGROW 11
      
      label live
        menu label Start Solus
        kernel /boot/kernel
        append initrd=/boot/initrd.img root=live:CDLABEL=SolusLiveGNOME ro rd.luks=0 rd.md=0 rd.live.overlay.overlayfs=1 quiet splash --
      menu default
      label live-nomodeset
        menu label Start Solus (nomodeset -- NVIDIA compatibility mode)
        kernel /boot/kernel
        append initrd=/boot/initrd.img root=live:CDLABEL=SolusLiveGNOME ro rd.luks=0 rd.md=0 rd.live.overlay.overlayfs=1 quiet splash nomodeset --
      label live-debug
        menu label Start Solus (verbose debugging mode)
        kernel /boot/kernel
        append initrd=/boot/initrd.img root=live:CDLABEL=SolusLiveGNOME ro rd.luks=0 rd.md=0 rd.live.overlay.overlayfs=1 rd.debug rd.live.debug systemd.log_level=debug --
      label local
        menu label Boot from local drive
        localboot 0x80

      So it is possible but where do i amend the same resolution into my systemd boot menu

      • Staudey replied to this.
      • Do not create multiple threads for the same thing. Locking.

      • ok found this on the live iso in the isolinux.cfg

        ui vesamenu.c32
        timeout 50
        default live
        
        MENU RESOLUTION 1024 768
        menu title Solus 4.5 (GNOME)
        menu background splash.png
        MENU COLOR screen       37;40      #80ffffff #00000000 std
        MENU COLOR border       30;44   #40ffffff #a0000000 std
        MENU COLOR title        1;36;44 #ffffffff #a0000000 std
        MENU COLOR sel          7;37;40 #e0ffffff #20ffffff all
        MENU COLOR unsel        37;44   #50ffffff #a0000000 std
        MENU COLOR help         37;40   #c0ffffff #a0000000 std
        MENU COLOR timeout_msg  37;40   #80ffffff #00000000 std
        MENU COLOR timeout      1;37;40 #c0ffffff #00000000 std
        MENU COLOR msg07        37;40   #90ffffff #a0000000 std
        MENU COLOR tabmsg       31;40   #ffDEDEDE #00000000 std
        MENU HIDDEN
        MENU HIDDENROW 7
        MENU WIDTH 78
        MENU MARGIN 15
        MENU ROWS 4
        MENU VSHIFT 17
        MENU HSHIFT 25
        MENU TABMSGROW 11
        
        label live
          menu label Start Solus
          kernel /boot/kernel
          append initrd=/boot/initrd.img root=live:CDLABEL=SolusLiveGNOME ro rd.luks=0 rd.md=0 rd.live.overlay.overlayfs=1 quiet splash --
        menu default
        label live-nomodeset
          menu label Start Solus (nomodeset -- NVIDIA compatibility mode)
          kernel /boot/kernel
          append initrd=/boot/initrd.img root=live:CDLABEL=SolusLiveGNOME ro rd.luks=0 rd.md=0 rd.live.overlay.overlayfs=1 quiet splash nomodeset --
        label live-debug
          menu label Start Solus (verbose debugging mode)
          kernel /boot/kernel
          append initrd=/boot/initrd.img root=live:CDLABEL=SolusLiveGNOME ro rd.luks=0 rd.md=0 rd.live.overlay.overlayfs=1 rd.debug rd.live.debug systemd.log_level=debug --
        label local
          menu label Boot from local drive
          localboot 0x80

        So it is possible but where do i amend the same resolution into my systemd boot menu

      • Add, if not already, into your environment or bashrc.

        I add these into my NixOS, fedora and now, solus and it does help

        ###---------- Nvidia session ----------###
        export LIBVA_DRIVER_NAME=nvidia                       # Specifies the VA-API driver to use for hardware acceleration
        export WLR_NO_HARDWARE_CURSORS=1             # Disables hardware cursors for Wayland to avoid issues with some Nvidia drivers
        export __GLX_VENDOR_LIBRARY_NAME=nvidia      # Specifies the GLX vendor library to use, ensuring Nvidia's library is used
        export __GL_SHADER_CACHE=1                                 # Enables the GL shader cache, which can improve performance by caching compiled shaders
        export __GL_THREADED_OPTIMIZATION=1             # Enables threaded optimization in Nvidia's OpenGL driver for better performance
        export CLUTTER_BACKEND=wayland                       # Specifies Wayland as the backend for Clutter
        export MOZ_ENABLE_WAYLAND=1                           # Enables Wayland support in Mozilla applications (e.g., Firefox)
        export NIXOS_OZONE_WL=1                                     # Enables the Ozone Wayland backend for Chromium-based browsers
        export NIXPKGS_ALLOW_UNFREE=1                        # Allows the installation of packages with unfree licenses in Nixpkgs
        export QT_WAYLAND_DISABLE_WINDOWDECORATION=1     # Disables window decorations in Qt applications when using Wayland
        export SDL_VIDEODRIVER=wayland                        # Sets the video driver for SDL applications to Wayland
        export MOZ_DBUS_REMOTE=1
        export MOZ_ALLOW_DOWNGRADE=1                    # Don't throw "old profile" dialog box.
        • Whats your favourite kernel parm's

          I used:

          io_delay=none rootdelay=0 threadirqs irqaffinity noirqdebug iomem=relaxed mitigations=off zswap.enabled=1 zswap.compressor=lz4 zswap.max_pool_percent=10 zswap.zpool=zsmalloc

        • Didnt work, and followed as per to the instructions:

          sudo clr-boot-manager mount-boot
          sudo mkdir -p /boot/efi/
          sudo mkdir -p /boot/efi/loader/entries
          sudo clr-boot-manager list-kernels
          ls /usr/lib/kernel
          ls /lib/modules
          sudo nano /boot/efi/loader/entries/solus-current.conf
          title Solus
          linux /usr/lib/kernel/com.solus-project.current.6.8.12-293
          initrd /usr/lib/kernel/initrd-com.solus-project.current.6.8.12-293
          options root=UUID=745a6698-6370-441f-9f94-fafd699ac04f quiet
          sudo nano /boot/efi/loader/loader.conf
          timeout 3
          default solus-current
          console-mode max
          editor no
          sudo clr-boot-manager update
          reboot
        • Hi all
          I implemented the following as I didn't like the restriction of choosing or accessing my bios at boot:

          sudo clr-boot-manager set-timeout 3
          sudo clr-boot-manager update

          My question is, just like in NixOS in the boot loader configuration, you can set the console mode to max. How can a similar configuration be applied to the clr Linux kernel or its corresponding grub entry?

          I've managed to disable mitigations by setting the kernel parameter successfully, but achieving maximum resolution for the console (systemD) remains elusive

          Example like mine in my NixOS:

          https://github.com/tolgaerok/nixos-2405-gnome/blob/8817bc75f9617300a771d1b4d5cac39502b6be35/core/boot/efi/efi.nix#L29

        • Thanks for the link I used the documentations before

        • Hey everyone,

          I've been a dedicated Fedora and NixOS user, but recently, I decided to try something different and went for good old Solus KDE. The last time I used Solus was when Ikey was the main developer. He did some amazing things not only for Linux Mint back in the day but also for SolusOS in its early stages.

          I'm genuinely impressed with the Intel optimizations and tweaks that have gone into this project. However, I can't say the same about its package manager.

          Now, here's my question: How and where can I get Fortune and Lolcat to install on Solus? Any guidance would be appreciated!