LocalAI iOS Client [question] - Lemmy.World

I’m trying to find an iOS client that lets me point to my self hosted LocalAI instance. Thanks!

Degraded gaming performance after waking from sleep. - Lemmy.World

Operating System: Arch Linux KDE Plasma Version: 6.2.4 KDE Frameworks Version: 6.9.0 Qt Version: 6.8.1 Kernel Version: 6.12.7-arch1-1 (64-bit) Graphics Platform: Wayland GPU: NVIDIA GeForce RTX 4090/PCIe/SSE2 GPU DRIVER: 565.77 Pretty straight forward issue. Rocket League for example: Butter smooth game play before sleep. After sleep mild to moderate stuttering. - Looking at processes, I don’t see anything hung or stuck using high resources… - I’ve tried restarting sddm and kwin_wayland --replace. - Scanned logs before and after sleep, didn’t see anything stand out. I feel like this started happening around the first release of the 6.12 kernel. Or maybe last couple NVIDIA driver releases. With that in mind, since it’s the 6.12 kernel, I have set my scheduler to “scx_lavd --autopilot”. Anyone experiencing similar issues?

Tim - Lemmy.World

Wroom 32 + Core1262-868M - Lemmy.World

I read through the Meshtastic firmware code and found the file variant.h for the Meshtastic-DIY-v1_1 [https://github.com/meshtastic/firmware/blob/master/variants/diy/v1_1/variant.h] build. Notice it’s not the DIY-v1. Instead v1_1. My understanding from that file is that I should be able to wire the following: ESP32 WROOM-32 dev [https://a.co/d/8K73gda] Pin,Core1262-868M [https://www.waveshare.com/core1262-868m.htm] Pin,Function 3V3,VCC,Power (3.3V) GND,GND,Ground 18,SCK,SPI Clock 19,MISO,SPI Data In 23,MOSI,SPI Data Out 5,CS,SPI Chip Select 33,DIO1,LoRa IRQ 32,DIO2,LoRa BUSY 27,RESET,LoRa Reset 14,RXEN,RF switch RX control 13,TXEN,RF switch TX control — Unfortunately after building out the DIY_v1_1 firmware, wiring it up and flashing it I get thrown into a boot loop only after setting the region. I will provide logs once I’m able to do so, just wanted to submit this while I had time. I’m curious if I was misunderstanding the compatibility with a Core1262-868M or if anyone has any tips. Thanks. Update : I have it working

Useless Calendar Widget - Lemmy.World

The most useless calendar widget is made by Apple. I constantly forget that someone’s birthday or something important is coming up later in the week. Now I understand that you can set up alerts and you can set up reminders for stuff. I also understand that you can choose a different size widget. But depending on the size and the amount of events it’s possible it won’t even show you what’s going on the next day in the larger widget as well. This is forced me to use third-party widgets to display calendar events for the week on my home screen. I hate it because I have no idea if it’s stealing my data.

VP Nominee - Tim Walz's Shoes - Lemmy.World

[https://lemmy.world/pictrs/image/fa013772-7cca-483f-9d4d-d91f917f1854.jpeg]https://www.reddit.com/r/gratefuldead/s/dX0mlQ2elf [https://lemmy.world/pictrs/image/e9e3935b-f45f-4f62-87db-2de18122594c.webp]

Are the lemmy news communities posts on Gaza full of nazis, unchecked disinformation efforts, or confused college kids? It's sickening. - Lemmy.World

Sleeping with NVIDIA ? - Lemmy.World

I’m trying to understand if its just my setup or if sleeping on NVIDIA is a current problem for all users. It used to work, but I haven’t been able to get it to work for the past few months. I am aware AMD cards tend to work better for this, I have two of them. I’m specifically asking about the current state of NVIDIA, not a different hardware solution. As I said, it was working. KDE Plasma 5.27.10 Kernel: 6.7.5-arch1-1 Driver Version: 550.40.07 nvidia-powerd.service nvidia-suspend.service enabled

What does your kernel boot parameters look like? What modules are you loading? On which hardware? Why? - Lemmy.World

Current GFX Driver issues aside, it does seem like we’re nearing a point where every distro install mostly will just work right out of the box. Sure, there will be some niche cases, but we won’t have to focus on specific GFX hardware types as much. This brings me to one major gap I see in users getting the most out of their hardware when running Linux. I’m going to provide my hardware and software setup ( that is relevant ). Explain which drivers I’m using along with any special settings and why. Now, the need for certain settings and software has changed over the years and sometimes it can be hard to find out best practice for this stuff. I understand I might have incorrect information, so please lets educate everyone. Let me know what I need to change and let us know what your hardware is and what you needed to do to get full control of it. ### Hardware. Motherboard : Asus ROG Crosshair VIII Dark Hero CPU : Ryzen 9 5950X RAM : 4x F4-4266C17-16GVKB Display : Sony Bravio 4k 120hz TV (HDMI) , ACER 1440p 144hz (DP) BOTH with GSYNC — ### OS ➜ ~ cat /etc/os-release NAME="Arch Linux" PRETTY_NAME="Arch Linux" ID=arch BUILD_ID=rolling ANSI_COLOR="38;2;23;147;209" HOME_URL="https://archlinux.org/" DOCUMENTATION_URL="https://wiki.archlinux.org/" SUPPORT_URL="https://bbs.archlinux.org/" BUG_REPORT_URL="https://bugs.archlinux.org/" PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/" LOGO=archlinux-logo — ### Software and Configuration ➜ ~ dkms status nvidia/545.29.06, 6.7.0-zen3-1-zen, x86_64: installed xone/0.3, 6.7.0-zen3-1-zen, x86_64: installed zenpower3/0.2.0, 6.7.0-zen3-1-zen, x86_64: installed xone This package allows my XBOX Elite 2 to work with the dongle. I have heard the bluetooth experience has improved over the years, but I never bothered because XONE is nearly flawless. zenpower3 Zenpower3 is a Linux kernel driver for reading temperature, voltage(SVI2), current(SVI2) and power(SVI2) for AMD Zen family CPUs — ➜ ~ cat /boot/loader/entries/linux-zen.conf title Arch Linux (linux-zen) linux /vmlinuz-linux-zen initrd /amd-ucode.img initrd /initramfs-linux-zen.img options root=PARTUUID="dd934a5c-e6d3-421a-b4d0-0bb3ad99f23d" rw rootfstype=ext4 zswap.enabled=1 amd_pstate=passive acpi_enforce_resources=lax amd_iommu=on iommu=pt kvm.ignore_msrs=1 nvidia-drm.modeset=1 nvidia-modeset.hdmi_deepcolor=1 nvidia-drm.fbdev=1 nvidia.NVreg_PreserveVideoMemoryAllocations=0 nvidia.NVreg_TemporaryFilePath=/var/tmp quiet amd_pstate=passive The amd_pstate CPU power scaling driver is not active by default, but can be manually enabled when using a supported CPU (Zen 2 and newer) by adding amd_pstate=passive, amd_pstate=active or amd_pstate=guided as a kernel parameter. **acpi_enforce_resources=lax ** This allows lm-senors and sensorsd to see and control additional parts of my hardware like fans and RGB. Without it software doesn’t know it exits. amd_iommu=on iommu=pt kvm.ignore_msrs=1 This is for running virtual machines on my system. **nvidia-drm.modeset=1 nvidia-modeset.hdmi_deepcolor=1 nvidia-drm.fbdev=1 nvidia.NVreg_PreserveVideoMemoryAllocations=0 nvidia.NVreg_TemporaryFilePath=/var/tmp ** my understanding this is what is required to use all of the latest features on the latest nvidia drivers. Also wayland support. — ➜ ~ cat /etc/mkinitcpio.conf MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm xone-dongle nct6775) BINARIES=() FILES=() HOOKS=(base udev autodetect keyboard keymap modconf block filesystems fsck) While I understand you can tell your OS to load them using modprobe.d, i choose to bake them right in from boot. nvidia nvidia_modeset nvidia_uvm nvidia_drm - nvidia stuff **xone-dongle ** enables my xbox wireless dongle **nct6775 ** without this, I cannot control or see my fans. — ➜ ~ cat /etc/fancontrol # This file was created by Fancontrol-GUI INTERVAL=10 DEVPATH=hwmon0=devices/platform/nct6775.656 hwmon5=devices/pci0000:00/0000:00:18.3 DEVNAME=hwmon0=nct6798 hwmon5=zenpower FCTEMPS=hwmon0/pwm1=hwmon5/temp1_input hwmon0/pwm2=hwmon5/temp1_input hwmon0/pwm3=hwmon5/temp1_input hwmon0/pwm6=hwmon5/temp4_input FCFANS=hwmon0/pwm1=hwmon0/fan1_input hwmon0/pwm2=hwmon0/fan2_input hwmon0/pwm3=hwmon0/fan3_input hwmon0/pwm6=hwmon0/fan6_input MINTEMP=hwmon0/pwm1=60 hwmon0/pwm2=60 hwmon0/pwm3=60 hwmon0/pwm6=30 MAXTEMP=hwmon0/pwm1=83 hwmon0/pwm2=83 hwmon0/pwm3=83 hwmon0/pwm6=73 MINSTART=hwmon0/pwm1=0 hwmon0/pwm2=0 hwmon0/pwm3=0 hwmon0/pwm6=0 MINSTOP=hwmon0/pwm1=100 hwmon0/pwm2=100 hwmon0/pwm3=100 hwmon0/pwm6=103 MINPWM=hwmon0/pwm1=0 hwmon0/pwm2=0 hwmon0/pwm3=0 hwmon0/pwm6=0 MAXPWM=hwmon0/pwm1=255 hwmon0/pwm2=255 hwmon0/pwm3=255 hwmon0/pwm6=255 AVERAGE=hwmon0/pwm1=3 hwmon0/pwm2=3 hwmon0/pwm3=3 hwmon0/pwm6=3 This is my fancontrol config file. ( after running pwmconfig ) — ➜ ~ sensors iwlwifi_1-virtual-0 Adapter: Virtual device temp1: N/A asusec-isa-0000 Adapter: ISA adapter CPU Core: 996.00 mV CPU_Opt: 935 RPM Water_Flow: 0 RPM Chipset: +62.0°C CPU: +54.0°C Motherboard: +36.0°C T_Sensor: +38.0°C VRM: +54.0°C Water_In: -40.0°C Water_Out: -40.0°C CPU: 37.00 A nvme-pci-0400 Adapter: PCI adapter Composite: +40.9°C (low = -0.1°C, high = +84.8°C) (crit = +94.8°C) Sensor 1: +41.9°C (low = -273.1°C, high = +65261.8°C) Sensor 2: +40.9°C (low = -273.1°C, high = +65261.8°C) Sensor 8: +40.9°C (low = -273.1°C, high = +65261.8°C) nvme-pci-0c00 Adapter: PCI adapter Composite: +29.9°C (low = -0.1°C, high = +74.8°C) (crit = +79.8°C) nct6798-isa-0290 Adapter: ISA adapter in0: 1.27 V (min = +0.00 V, max = +1.74 V) in1: 1000.00 mV (min = +0.00 V, max = +0.00 V) ALARM in2: 3.39 V (min = +0.00 V, max = +0.00 V) ALARM in3: 3.30 V (min = +0.00 V, max = +0.00 V) ALARM in4: 1.74 V (min = +0.00 V, max = +0.00 V) ALARM in5: 592.00 mV (min = +0.00 V, max = +0.00 V) in6: 1.06 V (min = +0.00 V, max = +0.00 V) ALARM in7: 3.39 V (min = +0.00 V, max = +0.00 V) ALARM in8: 3.26 V (min = +0.00 V, max = +0.00 V) ALARM in9: 1.79 V (min = +0.00 V, max = +0.00 V) ALARM in10: 16.00 mV (min = +0.00 V, max = +0.00 V) ALARM in11: 176.00 mV (min = +0.00 V, max = +0.00 V) ALARM in12: 1.02 V (min = +0.00 V, max = +0.00 V) ALARM in13: 1.49 V (min = +0.00 V, max = +0.00 V) ALARM in14: 896.00 mV (min = +0.00 V, max = +0.00 V) ALARM fan1: 910 RPM (min = 0 RPM) fan2: 967 RPM (min = 0 RPM) fan3: 715 RPM (min = 0 RPM) fan4: 0 RPM (min = 0 RPM) fan5: 0 RPM (min = 0 RPM) fan6: 3802 RPM (min = 0 RPM) fan7: 0 RPM (min = 0 RPM) SYSTIN: +36.0°C (high = +80.0°C, hyst = +75.0°C) (crit = +125.0°C) sensor = thermistor CPUTIN: +52.5°C (high = +80.0°C, hyst = +75.0°C) (crit = +125.0°C) sensor = thermistor AUXTIN0: +22.0°C (high = +80.0°C, hyst = +75.0°C) (crit = +125.0°C) sensor = thermistor AUXTIN1: +127.0°C (high = +80.0°C, hyst = +75.0°C) ALARM (crit = +125.0°C) sensor = thermistor AUXTIN2: +102.0°C (high = +80.0°C, hyst = +75.0°C) ALARM (crit = +125.0°C) sensor = thermistor AUXTIN3: +32.0°C (high = +80.0°C, hyst = +75.0°C) (crit = +100.0°C) sensor = thermistor AUXTIN4: +50.0°C (high = +80.0°C, hyst = +75.0°C) (crit = +100.0°C) PECI Agent 0 Calibration: +54.0°C (high = +80.0°C, hyst = +75.0°C) PCH_CHIP_CPU_MAX_TEMP: +0.0°C PCH_CHIP_TEMP: +0.0°C PCH_CPU_TEMP: +0.0°C PCH_MCH_TEMP: +0.0°C TSI0_TEMP: +65.4°C TSI1_TEMP: +62.0°C intrusion0: ALARM intrusion1: ALARM beep_enable: disabled hidpp_battery_0-hid-3-a Adapter: HID adapter in0: 3.81 V zenpower-pci-00c3 Adapter: PCI adapter SVI2_Core: 1.41 V SVI2_SoC: 1.07 V Tdie: +65.6°C (high = +95.0°C) Tctl: +65.6°C Tccd1: +70.0°C Tccd2: +60.0°C SVI2_P_Core: 51.91 W SVI2_P_SoC: 18.35 W SVI2_C_Core: 37.55 A SVI2_C_SoC: 17.07 A nvme-pci-0100 Adapter: PCI adapter Composite: +55.9°C (low = -5.2°C, high = +79.8°C) (crit = +84.8°C) nvme-pci-0d00 Adapter: PCI adapter Composite: +3.9°C (low = -0.1°C, high = +69.8°C) (crit = +89.8°C) This is what my sensors output looks like now that all the hardware is accounted for. It DOES NOT look this complete out of the box. — I have a heavily custom bios config to boost my CPU as much as possible while using all of the features I paid for. End result is linux seeing the proper MIN and MAX clock speeds. ➜ ~ printf %.0f\\\n $(cat /proc/cpuinfo | grep MHz | awk '{print $4}' | sort -n | tail -1 ) 5274 ➜ ~ cat /etc/cpupower_gui.d/cpg-Default.profile # name: Default # CPU Min Max Governor Online 0 550 5274 schedutil True 1 550 5274 schedutil True 2 550 5274 schedutil True 3 550 5274 schedutil True 4 550 5274 schedutil True 5 550 5274 schedutil True 6 550 5274 schedutil True 7 550 5274 schedutil True 8 550 5274 schedutil True 9 550 5274 schedutil True 10 550 5274 schedutil True 11 550 5274 schedutil True 12 550 5274 schedutil True 13 550 5274 schedutil True 14 550 5274 schedutil True 15 550 5274 schedutil True 16 550 5274 schedutil True 17 550 5274 schedutil True 18 550 5274 schedutil True 19 550 5274 schedutil True 20 550 5274 schedutil True 21 550 5274 schedutil True 22 550 5274 schedutil True 23 550 5274 schedutil True 24 550 5274 schedutil True 25 550 5274 schedutil True 26 550 5274 schedutil True 27 550 5274 schedutil True 28 550 5274 schedutil True 29 550 5274 schedutil True 30 550 5274 schedutil True 31 550 5274 schedutil True My current default cpupower config detailing my idle and max clock speeds an the schedutil governor for a balanced experience. Obviously I use gamemoded and switch to PERFORMANCE if I launch a game. — I have noticed a lot of users simply not using their hardware properly due to the incredible amount of research and time goes into each individual setup. Here’s what I did, nothing too crazy, but at the end of the day I feel like I’m getting my money’s worth on a platform getting 3rd class support from vendors. Maybe it will help someone out there.