oh boy, UR testing me NOW! i'm gonna go w/ UR 'final Q, for the moment' first - then work on explaining/drawing out my BEST recollection(s) of UR other Q's - may or not be included in some of this answer.
full disclosure, i've done more than a few installs/re-installs along the way (past week or two). the OG-OS that came w/ the NIB machine (summer/fall 2024) was pre-installed w10-home. recently, i had dell replace the keyboard (a minor 'juice' spill, that caused a couple of physically sticky keys). i'm pretty sure they also said/gave me a 'new' batt. (=NO reason for what-ever or why? & @ no-charge!). i don't remember if I'd done any 'clean' win re-install or not before sending to them for that work, but definetly did so when i got it back from them - wanting to try my hand @ uprading to w10-pro a/o pro:N. wireless worked before/after&since i'd gotten it back from them (late last/earlier this-month). i think it may have just dumbed it back down to the home ver., OR it didn't like the pro/pro:N so i decided i might just as well get on to my preferred / intended LL daily driver & avoid the w11 deadline. right away it didn't pick up the wireless, so i broke out my BE-PA3U6E
https://www.bestbuy.com/site/best-buy-es...Id=6451327 & strung out a long cat5-ethernet cable from the gateway, connected right away & was able to finish the install.
since then i'd tried to google/brave search a few symptoms. there WAS something i'd found (like: "here's the solution/found a fix") that involved three terminal actions (don't remember now where/what details) that DID bring the wireless back while in/ON LL, but not thinking to make any notes or paying to much attention to it - thinking 'problem solved' i continued w/ another variety of full/clean-RE-installs. since then i've been through a number of default & factory BIOS settings, a BIOS 'update' (1.23.0 > 1.24.0) but have NOT tried to 'down-grade' the BIOS back, YET!). i THINK when i 1st tried the install (using 'live media') it 'waasNOTappening' when selecting / using the wireless "cnvi" connection option. so, other than that brief, post-three terminal find i've only been able to use ethernet connection on LL. there'd NOT been any 'dual' boots.
THIS looks to be my submission to UR 'hardware DB'):Linux Lite 7.x Series : User Submitted on 05/02/2025 06:49
System:
Kernel: 6.8.0-58-generic x86_64 bits: 64 Desktop: Xfce 4.18.1
Distro: Linux Lite 7.4 LTS
Machine:
Type: Laptop System: Dell product: Latitude 3140 v: N/A serial:
Mobo: Dell model: 0NH985 v: A01 serial: UEFI: Dell v: 1.23.0 date: 02/26/2025
CPU(s):
Topology: Quad Core model: Intel N100 bits: 64 type: MCP L2 cache: 6144 KiB
Speed: 699 MHz min/max: 700/3400 MHz Core speeds (MHz): 1: 718 2: 700 3: 700 4: 963
Graphics:
Device-1: Intel Alder Lake-N [UHD Graphics] driver: i915 v: kernel
Display: x11 server: X.Org 21.1.11 driver: modesetting unloaded: fbdev,vesa
resolution: 1366x768~60Hz
OpenGL: renderer: Mesa Intel Graphics (ADL-N) v: 4.6 Mesa 24.2.8-1ubuntu1~24.04.1
Audio:
Device-1: Intel Alder Lake-N PCH High Definition Audio driver: snd_hda_intel
Sound Server: ALSA v: k6.8.0-58-generic
Network:
Device-1: Intel cnvi driver: iwlwifi
Device-2: Realtek RTL8153 Gigabit Ethernet Adapter type: USB driver: r8152
Drives:
Local Storage: total: 58.32 GiB used: 15.89 GiB (27.3%)
ID-1: /dev/mmcblk0 type: Removable model: TY2964 size: 58.32 GiB
Message: No Optical or Floppy data was found.
