Good First Issues in Makefile

@MrChromebox updated https://review.coreboot.org/c/coreboot/+/85278 Note that the coreboot matrix thread We understand that both can't be used at the same time INTEL_CHIPSET_LOCKDOWN=y vs # CONFIG_INTEL_CHIPSET_LOCKDOWN is not set + CONFIG_SOC_INTEL_COMMON_SPI_LOCKDOWN_SMM=y Other message in thread: Note that as of now, patches for different platforms grew in forks who use this, and afaik it's mostly heads So PR0 patches are Work for alder lake and meteorlake under dasharo fork (seems self-contained under Dasharo/coreboot@a4f9bd2) community attempt under ready to merge kano (26.03) under https://github.com/linuxboot/heads/pull/2133/changes#diff-f1f6f628ec68a607e292baa7e86c813f2d966fc7420b31b7f24ea7f346aed525 Starlabs patch on top of coreboot upstream 26.07.01 (untested yet AFAIK) https://github.com/linuxboot/heads/pull/2164/changes#diff-12e023b0ef7b98398ffcbd169c5a0f38520f4e87642cc55dd9ffecbadfb3e180 So upstream https://review.coreboot.org/c/coreboot/+/85278 still lack implementa

Skylake+ and possibly other platforms (t480*) From discussion on coreboot matrix thread Turns out the PCH-H datasheets are just wrong and the pad_cfg_lock_offset value for GPIO community 0 was wrong. I fixed it to match edk2-platforms and the Linux pin-ctrl driver and locking seems to be working with my original patch, though with the SBI method instead of the PCR method: https://review.coreboot.org/c/coreboot/+/90885 I will push some patches later Locking them in SMM as is done in the patch train of https://review.coreboot.org/c/coreboot/+/95545 does not appear to be working on Skylake even with the corrected offsets. AlderLake Also patchtrain for alderlake (nv4x_adl), would needs backporting https://review.coreboot.org/q/topic:%22tpm_gpio_pltrst_lock%22 to be applied downstream until next release of Dasahro+Heads Referred from Dasharo/coreboot#959 (comment) TODO update downstream forks used patchtrains test against nv4xadl update https://github.com/tlaurion/tpm-gpio-fail upda

Expected Behavior Install OMR and put the IP address and API key, expected to be working Current Behavior Freshly install OMR and VPS, put the IP address and API Key, the OMR is not working. Keep getting direct output Specifications OpenMPTCProuter version: 0.64.2-6.18 OpenMPTCProuter VPS version: Not sure, but I did install the last one, run uname -a , getting kernel 6.18 OpenMPTCProuter VPS provider: local VPS at Indonesia OpenMPTCProuter platform: x86_64 Hyper-V

For those who follows, its been a couple of PR that I try to save them, since there is 4kb left in master of freed ME space on those boards for maximized-hotp builds. I plan to merge #2206 soon, and the code comments alone of that pr are now consuming that 4kb compressedfreed space. It's your time to shine: you're technical, own a x220/t420, want to jump in under #1991 or any other quests under #590 to revive them, be my guest. Flagging this u=issue with help needed and pinning, Sorry folks, 8mb spi boards not a priority of mine. Is it one of yours? Shine :)

Expected Behavior After a fresh OpenMPTCProuter installation and a fresh OpenMPTCProuter VPS installation, entering the VPS IP address and server key in the setup wizard should establish the VPN tunnel. The dashboard should show "VPN tunnel UP" and the omrvpn interface should be available. The same setup, VPS provider, WAN connections and wizard configuration work correctly with an older OpenMPTCProuter version. Current Behavior With OpenMPTCProuter v0.64.1, the dashboard permanently shows "VPN tunnel DOWN" after a fresh installation. This was reproduced with: A fresh OpenMPTCProuter router installation A fresh VPS installation A new Hetzner Cloud VPS New VPS key / server key Both virtualized x86_64 hardware and physical x86_64 hardware Two WAN connections: DSL and 5G The VPS is reachable from both WAN connections: OMR admin/API communication to the VPS works. The router can retrieve VPS configuration. UDP traffic to the MQVPN server port 65443 reaches the VPS. The VPS sends replies

Expected Behavior Current Behavior trying to install AI on VPS: sudo RESET_DATA="true" bash ./install_omr-ai.sh ==> Installing base dependencies... ==> Verifying and importing InfluxData GPG key... [14:54:13] Key fingerprint verified: *********** ==> Adding InfluxData apt repository... ==> Installing influxdb3-core... Reading package lists... Done Building dependency tree... Done Reading state information... Done influxdb3-core is already the newest version (3.11.4-1). The following packages were automatically installed and are no longer required: exim4-base exim4-config libidn12 liblockfile-bin liblockfile1 libmbedcrypto16 libmbedtls21 libmbedx509-7 libnsl2 linux-image-6.12.100+deb13-arm64 Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. ==> Writing /etc/influxdb3/influxdb3-core.conf... ==> Enabling and (re)starting influxdb3-core to apply config... ==> Waiting for InfluxDB 3 HTTP API... [14:54:18] InfluxDB 3 is up (HTTP 200

Before filing a bug report Follow-up to #2008 and #2186. #2186 merged in master. Hardware details Board: novacustom-v540tu (failing). Working: x230 (EOL_x230-maximized), novacustom-nv4x_adl. GPU: iGPU-only (Intel Meteor Lake, device ID 7d55). Heads/Dasharo: Dasharo Heads-v0.2.1-3144-g7850f7a (DMI BIOS string), vendor-installed by Novacustom. ROM: vendor (Dasharo) image, maximized. Please describe the problem Describe the bug #2186 ("initrd: boot dd-written hybrid ISOs in mount-usb and usb-autoboot") fixes #2008 ("kicksecure iso doesn't boot under Heads") on x230 and novacustom-nv4x_adl. On novacustom-v540tu the Kicksecure ISO fails to boot only in live-amnesic mode ("LIVE Mode | USER Session | disposable use"): the machine auto-reboots before/at the LXQt desktop. The failure is specific to the live-amnesic USER session. Non-live-amnesic modes boot fine on the same machine: "LIVE Mode | SYSMAINT Session" (sysmode) boots to console, and the other grub entries are unaffected. To Reprodu

Hi , i'm facing issue with new Z8102AX and 5g Modems with modemmanger, i would really appreciate if anyone can put me in right direction if i change device type to USB it starts working but still no info in dashboard cellular Network. in dashboard Cellular Network packet service State is detached and signal quality is 0% in network interfaces shows error: Error: Unknown error (MM_3GPP_OPERATOR_REGISTRATION_FAILED) Or Error: Unable to set allowed mode list. after some time here is what i see in log ,one thing i noticed is saying modem is not handled by modemmanager root@OpenMPTCProuter:~# mmcli -m 0 -------------------------------- General | path: /org/freedesktop/ModemManager1/Modem/0 | device id: f1af8811f8e2e09606107221e6403e87a79339a6 -------------------------------- Hardware | manufacturer: Quectel | model: RM500U-EA | firmware revision: RM500UEAAAR03A13M2G_01.300.01.300 |

This comes often from community members suggesting crypto donation ,latest today in qubes matrix room. But problem is burden on me, I would need to receive the donations, without the burden of converting to fiat and legal/accounting burden. Present thoughts (require time, not replicated by any other small team based teams AFAIK) Switch OpenCollective's Fiscal Host from Open Source Collective to Open Collective Europe which Could theoretically provide Tax deduction papers to donor (fiat donations) Could theoretically deal with crypto->fiat conversion to collective once converted, though they require collective to Have a minimum balance of €2,000. QubesOS/Whonix and other projects accepts crypto donations by providing direct wallet addresses. Issue there is as said prior: burden is for me to have legal/accounting burden. Others avenues not yet considered.

Is your feature request related to a problem? Please describe. I'm proposing here just a minor convenience feature. https://osresearch.net/InstallingOS/ says: For certain OSes, Heads boot process supports standard OS ISO bootable media (where the USB drive contains the ISO installation media alongside of its detached signature) ... The "certain OSes" list excludes Debian & Ubuntu: major distros popular with power users and casual users respectively. Describe the solution you'd like Instead of publishing (as Arch, PureOS, QubesOS, and Tails do) an ISO & a detached signature for it, Debian & Ubuntu publish: an ISO a checksum file for the ISO a detached signature for the checksum file. It would be great if Heads: Adds the Debian signing keys to initrd/etc/distro/keys Adds the Ubuntu signing keys, too. Updates initrd/bin/kexec-iso-init.sh to look not only for detached sigs (as at present), but also for checksum files with detached signatures: if found, then to verify the checksum file

For my connection i utilize starlink as a second WAN, in order to reduce NAT port exhaustion i'd like to enable OMR bonding over IPv6. For starlink as it's assigned a global v6 dynamic subnet it would be ideal for OMR to establish using SLACC or DHCP. Currently when an interface is enabled for ipv4 DHCP, it does not seem to have the option available. I can confirm that other devices within the starlink VLAN do establish IPv6 connectivity natively via SLAAC. This differs to my primary wan where i have statically allocated v6 connectivity. I suspect my instance may be locked in IPv6 mode as initally it would obtain IPv6 for starlink when i first installed it (however at that time i did not have Ipv6 on my primary) Expected Behavior Both connections should obtain IPv6 and be able to OMR bond across IPv6 aswell as IPv4. Current Behavior Static allocated IPv6 has been established however SLAAC is not working for starlink connection. Specifications OpenMPTCProuter version: 0.63-6.12 Open

Expected Behavior In MPTCP, the "master channel" (or primary subflow) is typically selected automatically based on the lowest round-trip time (RTT) and connection stability. But it chooses channel with no ping to VPS server at all Current Behavior The system choosing channel with epty ping to VPS server If there is a posibility to edit the behavior in a script i need to change it as fast as i can ss -Mani shows that system tryes to establish connection via channel with no ping (SYN-SENT) i did few tests and some times it chooses corect channel so i gues it chooses randomly but i need that it chooses channek with ping to VPS server Specifications OpenMPTCProuter version: openmptcprouter v0.63-6.12 (r0+30806-070d8eb4d5)](https://openwrt.org/) OpenMPTCProuter VPS version: Debian 13 MPTCP6.6 OpenMPTCProuter VPS provider: OpenMPTCProuter platform: mini PC with 6 2.5G ports Intel(R) Pentium(R) Gold 7505 @ 2.00GHz

Expected Behavior When VPS connection is lost Internet supposed to be working t , pages can download. Current Behavior OMR constantly trying to connect to unreacheble VPS (maybe it is normal) pages not loading with error SSL error: error:00000005:lib(0)::reason(5) ping works But if in wizard disable VPS server pages can load. Specifications OMR router: openmptcprouter v0.63-6.12 r0+30806-070d8eb4d5 OMR server: Debian server 6.6

I compiled NPS in openmptcprouter. When I didn't configure the aggregated cloud server, my NPS could connect normally. However, as soon as the aggregated cloud server was connected, NPS couldn't connect anymore. After I restarted the aggregated cloud server, it was able to connect again. I have no idea why NPS can't establish the aggregated tunnel.

Package Name flashprog Maintainer none OpenWrt Version ANY OpenWrt Target/Subtarget ANY Steps to Reproduce The last time the flashrom package got updated in OpenWrt was the beginning of the year 2023. Since then there was a important change in the flashrom ecosystem. There was a split at the core developers. Now there are two independent projects out there each containing different functionality. Sometimes you need flashrom, sometimes you need flashrprog. It is important to have both packages in OpenWrt to have the full functionality for flashing related workloads. https://flashprog.org Actual Behaviour Currently only flashrom is part of the OpenWrt packages. Just updating it #29590 , wont add all the functions that have been added since 2023 to the flashing functionality toolset. Confirmation Checklist The package is maintained in this repository. I understand that issues related to the base OpenWrt repository or LuCI repository will be closed. I am reporting an issue for OpenWrt,

Package Name smartdns Maintainer Nick Peng [email protected] OpenWrt Version 25.12.2 OpenWrt Target/Subtarget mediatek/filogic Steps to Reproduce Install OpenWRT package smartdns 46.1. Observe /etc/init.d/smartdns set_main_dns() behavior: adds LAN IP with CIDR to dhcp_option causing DHCP/DNS issues. Compare with upstream smartdns 47.1, where CIDR is removed and uci batch used. Actual Behaviour On modern OpenWRT (DSA), network.lan.ipaddr contains CIDR notation: 192.168.1.1/24 Causes broken DHCP DNS assignment (6,192.168.1.1/24) → clients receive invalid DNS entries. Bug traced to /etc/init.d/smartdns in OpenWRT package. Upstream smartdns 47.1 has corrected this (sed 's/\/.*//g') and uses uci batch. Confirmation Checklist The package is maintained in this repository. I understand that issues related to the base OpenWrt repository or LuCI repository will be closed. I am reporting an issue for OpenWrt, not an unsupported fork.

We recently ran into a tricky issue while deploying ReportPortal 5.14.x on a Kubernetes cluster behind an internal corporate proxy registry. The Analyzer backend was fully healthy, but the UI kept showing: “Service Analyzer is not running” Even though: Analyzer StatefulSet was working /info endpoint returned 200 via Nginx sidecar API → Analyzer communication was fine All backend operations worked (indexing, clustering, model training, etc.) After deep debugging, here’s the full breakdown and solution. ✅ 1. Analyzer Backend Was Healthy (Root Cause NOT Here) Analyzer core doesn’t provide /info, so Kubernetes & UI health checks fail. To fix that, I added an Nginx sidecar that exposes a proper JSON /info endpoint: JSON{"status":"UP","service":"analyzer","port":5001}Show more lines After updating: RP_ANALYZER_URL=http://analyzer:8080 → API succeeded → Analyzer backend fully passed health checks. So the UI banner issue was NOT caused by Analyzer itself.

Package Name watchcat Maintainer @roger- OpenWrt Version 25.12.0-rc5 OpenWrt Target/Subtarget ipq40xx/generic Steps to Reproduce Watchcat is not recognizing ping responses if the ping transverses through a mesh network. Using the diagnostic tool on the same router, ping responses are coming in normally. When Watchcat pings the same address, Watchcat sees no response. This issue was not present with 25.10.X and prior. Actual Behaviour Diagnostic Ping response from 192.168.1.1 to 192.168.1.12 over a mesh: 64 bytes from 192.168.1.12: seq=2 ttl=64 time=1.353 ms Watchcat Ping response missing from 192.168.1.1 to 192.168.1.12 over a mesh:: watchcat[4123]: Could not reach 192.168.1.12 for 1500. Rebooting after reaching 3600 Confirmation Checklist The package is maintained in this repository. I understand that issues related to the base OpenWrt repository or LuCI repository will be closed. I am reporting an issue for OpenWrt, not an unsupported fork.

graphql-ws is dead and needs to be replaced by a subscription service in graphql-server in order to finish upgrading to v3: graphql-python/graphql-ws#66 (comment) This code will need to be updated for that new service and tested to check it works: aiohttp-demos/demos/graphql-demo/graph/api/contrib.py Lines 180 to 190 in 77791e0 class CustomAiohttpSubscriptionServer(AiohttpSubscriptionServer): def get_graphql_params(self, connection_context, *args, **kwargs): params = super().get_graphql_params( connection_context, *args, **kwargs, )