I'd like to use a multi-M.2 NVMe PCIe carrier card like an [Asus Hyper M.2 x16 Card v2](https://www.asus.com/Motherboard-Accessories/HYPER-M-2-X16-CARD-V2/) in an [HP Z240 tower workstation](https://web.archive.org/web/20220414145018/https://support.hp.com/us-en/document/c04887696) . Its C236 PCH and Skylake E3-1200V5 CPU support [PCIe bifurcation](https://web.archive.org/web/20170628175109/https://www.intel.com/content/www/us/en/intelligent-systems/maho-bay/core-i7-pcie-slot-bifurcation-demo.html) 1 of the x16 PCIe slot driven by the CPU. (Ref: [Intel 100 Series / C230 Series Chipset datasheet Vol 1](https://web.archive.org/web/20210304165912/https://www.intel.com/content/www/us/en/products/docs/chipsets/100-series-chipset-datasheet-vol-1.html) , p. 22; [Intel Xeon E3-1200V5 datasheet Vol 1](https://web.archive.org/web/20181030044706/https://www.intel.com/content/www/us/en/processors/xeon/xeon-e3-1200v5-vol-1-datasheet.html) , p. 24.) Configuring the CPU PCIe for bifurcated 1x8 + 2x4 mode would allow using 3 M.2 NVMe drives in the x16 slot. (The E3 CPU is incapable of 4x4 bifurcation, so one of the M.2 slots in a quad-carrier card like the aforementioned Asus must remain empty.) Unfortunately the Z240's BIOS Setup does not include options to configure PCIe bifurcation. Worse, it appears that [HP's *Sure Start*](https://web.archive.org/web/20241228141437/http://h10032.www1.hp.com/ctg/Manual/c05163901) dual BIOS [prevents BIOS modifications](https://web.archive.org/web/20211120042316/https://www.win-raid.com/t4593f36-HP-Pavillion-g-wm-AMI-Aptio-V-modding-trials.html#msg75578) which [could enable PCIe bifurcation](https://blog.donbowman.ca/2017/10/06/pci-e-bifurcation-explained/) . This [Intel video introduction to PCIe bifurcation](https://www.intel.com/content/www/us/en/intelligent-systems/maho-bay/core-i7-pcie-slot-bifurcation-demo.html) 1 states (at 02:34) that > The configuration of the CPU PCI Express bus is statically determined by the BIOS prior to initializaton. The BIOS determines the configuration by looking at the presence detect pins on the CPU, called CFG and CFG. Presumably this works even if BIOS Setup doesn't include any options to configure bifurcation. But this approach would require accessing and modifying connections to the physical CPU pads, which I'd prefer to avoid. Other BIOSes that do include options to configure bifurcation apparently override CFG and CFG. I have found no documentation as to how they do this, and would be grateful for any links you may be aware of. At this point I wonder: Is there a way to override CFG and CFG after the machine has booted to Linux? (I realize I probably won't be able to boot from one of the M.2 drives in this case, but that's not a requirement for this system.) I'd expect such a procedure may involve steps like [hot-resetting](https://unix.stackexchange.com/questions/73908/how-to-reset-cycle-power-to-a-pcie-device/474378#474378) the x16, x8 and x4 PCIe controllers and/or function-level-resetting PEG Root Ports 10, 11 & 12. (Ref: [Intel Xeon E3-1200V5 datasheet Vol 2](https://web.archive.org/web/20201020235947/https://www.intel.com/content/www/us/en/processors/xeon/xeon-e3-1200v5-vol-2-datasheet.html).) Maybe followed by [kexec](https://en.wikipedia.org/wiki/Kexec) ? Many thanks for any hints, tips or pointers you can provide! -------------- Editors note: 1 As of August 2025 the original _Configure PCI-Express\* Lanes for Simultaneous Applications_ Intel link is dead and the archived versions I found no longer play the embedded video. The 1st link has been changed to an archived version.

The drive that my /home folder lives on is showing signs of failing, and I'm trying to migrate to a new drive.  I purchased a 4TB SSD, formatted it with ext4, mounted it as an external drive with a USB/SATA connector, and rsync’ed my /home folder over. So far, so good. But when I swapped it in place of the failing drive and rebooted, my OS reported:

unable to mount local folders
structure needs cleaning

That sounds like a corrupt file system, but fsck reported no errors. Maybe the new hardware is faulty, but I ran badblocks on it, and it also came back with no errors. I formatted it again and tried again, and came up with the same error. Weirdly, if I log in as root and manually mount the new /home drive, it mounts okay, and seems to accept read/writes. However, dmesg did show some errors for /dev/sdb (that's the /home drive on this system). I've copied them below, although I'm fluent enough myself to parse them. Any ideas? For context I'm running Gentoo Linux.

[    0.914006] sd 6:0:0:0: [sdb] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
[    0.914052] sd 6:0:0:0: [sdb] Write Protect is off
[    0.914074] sd 6:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[    0.914117] sd 6:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    0.914224] sd 6:0:0:0: [sdb] Preferred minimum I/O size 512 bytes
[    0.915929]  sdb: sdb1
[    0.916093] sd 6:0:0:0: [sdb] Attached SCSI disk
[    5.012731] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[    5.012740] sd 6:0:0:0: [sdb] tag#0 Sense Key : Illegal Request [current] 
[    5.012747] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Unaligned write command
[    5.012753] sd 6:0:0:0: [sdb] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 00 08 10 00 00 00 08 00 00
[    5.012757] I/O error, dev sdb, sector 2064 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
[    5.012786] sd 6:0:0:0: [sdb] tag#1 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[    5.012792] sd 6:0:0:0: [sdb] tag#1 Sense Key : Illegal Request [current] 
[    5.012797] sd 6:0:0:0: [sdb] tag#1 Add. Sense: Unaligned write command
[    5.012802] sd 6:0:0:0: [sdb] tag#1 CDB: Read(16) 88 00 00 00 00 00 00 00 08 18 00 00 00 08 00 00
[    5.012805] I/O error, dev sdb, sector 2072 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
[    5.012817] sd 6:0:0:0: [sdb] tag#31 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
[    5.012822] sd 6:0:0:0: [sdb] tag#31 Sense Key : Illegal Request [current] 
[    5.012827] sd 6:0:0:0: [sdb] tag#31 Add. Sense: Unaligned write command
[    5.012832] sd 6:0:0:0: [sdb] tag#31 CDB: Read(16) 88 00 00 00 00 00 00 00 08 08 00 00 00 08 00 00
[    5.012836] I/O error, dev sdb, sector 2056 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
[   35.852468] sd 6:0:0:0: [sdb] tag#13 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=30s
[   35.852476] sd 6:0:0:0: [sdb] tag#13 Sense Key : Illegal Request [current] 
[   35.852483] sd 6:0:0:0: [sdb] tag#13 Add. Sense: Unaligned write command
[   35.852490] sd 6:0:0:0: [sdb] tag#13 CDB: Read(16) 88 00 00 00 00 00 00 00 08 28 00 00 05 40 00 00
[   35.852494] I/O error, dev sdb, sector 2088 op 0x0:(READ) flags 0x84700 phys_seg 168 prio class 2
[   35.852574] sd 6:0:0:0: [sdb] tag#14 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=30s
[   35.852581] sd 6:0:0:0: [sdb] tag#14 Sense Key : Illegal Request [current] 
[   35.852586] sd 6:0:0:0: [sdb] tag#14 Add. Sense: Unaligned write command
[   35.852591] sd 6:0:0:0: [sdb] tag#14 CDB: Read(16) 88 00 00 00 00 00 00 00 0d 68 00 00 05 40 00 00
[   35.852595] I/O error, dev sdb, sector 3432 op 0x0:(READ) flags 0x84700 phys_seg 168 prio class 2
[   35.852672] sd 6:0:0:0: [sdb] tag#15 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=30s
[   35.852677] sd 6:0:0:0: [sdb] tag#15 Sense Key : Illegal Request [current] 
[   35.852682] sd 6:0:0:0: [sdb] tag#15 Add. Sense: Unaligned write command
[   35.852687] sd 6:0:0:0: [sdb] tag#15 CDB: Read(16) 88 00 00 00 00 00 00 00 12 a8 00 00 03 f0 00 00
[   35.852690] I/O error, dev sdb, sector 4776 op 0x0:(READ) flags 0x80700 phys_seg 126 prio class 2
[   36.858014] EXT4-fs (sdb1): ext4_check_descriptors: Checksum for group 18880 failed (53845!=52774)
[   36.858017] EXT4-fs (sdb1): group descriptors corrupted!

One further experiment: I tried installing another drive into the bay, and it also wouldn't auto mount as /home.  I could not even mount it manually after logging in as root.  As far as I can tell, there's nothing wrong with this third drive, and I can mount it just fine via a USB/SATA adapter.  Both of the new drives are SSDs, while the old failing drive that still mounts is a hard disk. This SATA port is via a SATA/PCIE adapter, so I suppose the problem could be in the adapter.  In that case, though, it's weird that the old hard drive still works.

Issue Summary: Multiple worldwide ThinkPad models with WCN6855 hw2.1 fail to properly handle regulatory domain settings, defaulting to incorrect country codes and causing regulatory compliance issues in EU. Affected Hardware: - Primary: Lenovo ThinkPad P16s Gen 2, QCNFA765 (WCN6855 hw2.1) - Secondary: Lenovo ThinkPad T14s Gen 4, same WCN6855 hw2.1 chip - Location: Czech Republic (EU) - Common pattern: Both models have worldwide country codes (00/WW suffix) Firmware versions tested: - Custom kernel: WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.41 (2024-04-17) - Debian Live: WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.9 (2022-04-18) Problem Description: Despite kernel regulatory domain settings, both laptops fail to apply correct regulatory rules: 1. Boot errors (consistent across all systems): ath11k_pci 0000:02:00.0: Failed to set the requested Country regulatory setting ath11k_pci 0000:02:00.0: Failed to set the requested Country regulatory setting 2. Incorrect regulatory domains applied: - P16s defaults to Brazil (BR) despite CZ kernel parameter - T14s defaults to United States (US) - Both ignore proper EU regulatory requirements 3. Regulatory compliance issues in EU: - All 5GHz channels marked "No IR" (No Initiate Radiation) - 6GHz power levels incorrect (30dBm instead of EU limit 23dBm) - Wrong DFS requirements (DFS-UNSET/DFS-FCC instead of DFS-ETSI) Test Results: ThinkPad P16s (21K9S0DC00) with kernel parameter cfg80211.ieee80211_regdom=CZ: global: country CZ: DFS-ETSI [correct] phy#0 (self-managed): country BR: DFS-UNSET [incorrect] ThinkPad T14s (21F8CT01WW) - stock configuration: global: country 00: DFS-UNSET phy#0 (self-managed): country US: DFS-FCC [incorrect for EU] Debian Live CD test (P16s) - proves cross-distribution issue: global: country 00: DFS-UNSET phy#0 (self-managed): country 00: DFS-UNSET 6GHz: 20dBm with "no IR" on ALL channels [overly restrictive] What I tried: 1. Kernel parameter cfg80211.ieee80211_regdom=CZ - Sets global domain but chip remains on wrong country 2. Kernel source modification - Changed default regulatory domain in net/wireless/reg.c: -static char *ieee80211_regdom = "00"; +static char *ieee80211_regdom = "CZ"; 2. Result: Global domain correctly set to CZ, but phy#0 still remains BR - firmware ignores kernel setting 3. Runtime iw reg set CZ - No effect on self-managed phy#0 4. Different distributions - Debian Live CD shows identical boot errors 5. Multiple hardware - Issue affects different worldwide ThinkPad models consistently Analysis: - Both laptops have worldwide country codes in model numbers (00/WW suffix) - SMBIOS likely contains "00" (worldwide) which firmware doesn't handle properly - Firmware falls back to hardcoded regional defaults instead of respecting kernel settings - Issue appears related to SMBIOS country code handling patch for WCN6855 (commit referencing reading country code from SMBIOS) - Problem affects multiple Linux distributions and kernel versions - Kernel-level regulatory changes are completely ignored by self-managed firmware Next Plan: Patching /usr/lib/firmware/ath11k/WCN6855/hw2.1/regdb.bin to replace incorrect regulatory data resolves the issue, but this shouldn't be necessary. Expected behavior: at the very least, it should be possible to change regulatory domain configuration via standard Linux methods Impact: This affects regulatory compliance for EU users with worldwide ThinkPad models, potentially causing interference and legal issues due to incorrect power levels and frequency usage.

I moved away from software RAID due to all the hassle it brings. After an OS reinstall, I am left with only one drive. I ordered a hardware RAID controller today, and when the controller arrives, I'd like to plug in the identical drives into the RAID controller and set up RAID 1 WITHOUT losing any data or needing to reinstall the OS (Debian Jessie x86_64). Output of lsblk:

NAME              MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda                 8:0    0 931.5G  0 disk
├─sda1              8:1    0   953M  0 part /boot
├─sda2              8:2    0  29.8G  0 part [SWAP]
└─sda3              8:3    0 900.8G  0 part
  ├─vgmain-lvroot 254:0    0 621.4G  0 lvm  /
  ├─vgmain-lvmail 254:1    0  93.1G  0 lvm  /var/vmail
  ├─vgmain-lvhome 254:2    0  93.1G  0 lvm  /home
  ├─vgmain-lvtmp  254:3    0  18.6G  0 lvm  /tmp
  └─vgmain-lvvar  254:4    0  74.5G  0 lvm  /var
sdb                 8:16   0 931.5G  0 disk

Can I do this somehow by dding the existing data to the clean drive while having it plugged into the RAID controller and set up as RAID 1? To clarify, let's say sda is the drive with my data, sdb is the drive which is not in use. * Plug sda into the mobo sata controller * Plug sdb into the RAID controller * Define sdb as RAID 1 drive * Boot from liveCD and dd contents of sda → sdb * Plug sda into RAID controller, define as RAID1 * RAID controller syncs the drives, (copies over sdb to sda) (?) * Boot without problems? Will dd copy the drive in a way that mbr/partitions/etc. are preserved? Am I thinking in a completely stupid way of doing this? I contacted the RAID controller manufacturer and asked if it has some kind of utility to convert a drive into 2 drives in RAID1, but they said no. If it's relevant in any way, the specific controller is a HighPoint RocketRAID 620 PCI-Express 2.0 x1 SATA III RAID card.

How can I check if the sound card of my laptop, a Dell XPS 13 (2015) (9343), is loaded in HDA mode or in I2S mode? According to ArchWiki , that laptop has a dual-mode sound card Hardware: [mattia@arch-xps ~]$ lspci -nn 00:00.0 Host bridge : Intel Corporation Broadwell-U Host Bridge-OPI [8086:1604] (rev 09) 00:02.0 VGA compatible controller : Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) 00:03.0 Audio device : Intel Corporation Broadwell-U Audio Controller [8086:160c] (rev 09) 00:04.0 Signal processing controller : Intel Corporation Broadwell-U Processor Thermal Subsystem [8086:1603] (rev 09) 00:14.0 USB controller [0c03]: Intel Corporation Wildcat Point-LP USB xHCI Controller [8086:9cb1] (rev 03) 00:16.0 Communication controller : Intel Corporation Wildcat Point-LP MEI Controller #1 [8086:9cba] (rev 03) 00:1b.0 Audio device : Intel Corporation Wildcat Point-LP High Definition Audio Controller [8086:9ca0] (rev 03) 00:1c.0 PCI bridge : Intel Corporation Wildcat Point-LP PCI Express Root Port #1 [8086:9c90] (rev e3) 00:1c.3 PCI bridge : Intel Corporation Wildcat Point-LP PCI Express Root Port #4 [8086:9c96] (rev e3) 00:1d.0 USB controller [0c03]: Intel Corporation Wildcat Point-LP USB EHCI Controller [8086:9ca6] (rev 03) 00:1f.0 ISA bridge : Intel Corporation Wildcat Point-LP LPC Controller [8086:9cc3] (rev 03) 00:1f.2 SATA controller : Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode] [8086:9c83] (rev 03) 00:1f.3 SMBus [0c05]: Intel Corporation Wildcat Point-LP SMBus Controller [8086:9ca2] (rev 03) 00:1f.6 Signal processing controller : Intel Corporation Wildcat Point-LP Thermal Management Controller [8086:9ca4] (rev 03) 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5249 PCI Express Card Reader [10ec:5249] (rev 01) 02:00.0 Network controller : Broadcom Limited BCM4352 802.11ac Wireless Network Adapter [14e4:43b1] (rev 03) Dmesg: [mattia@arch-xps ~]$ dmesg [ 0.000000] microcode: microcode updated early to revision 0x25, date = 2017-01-27 [ 0.000000] Linux version 4.11.5-2-ck (mattia@arch-xps) (gcc version 7.1.1 20170516 (GCC) ) #1 SMP PREEMPT Thu Jun 15 18:44:16 CEST 2017 [ 0.000000] Command line: initrd=\intel-ucode.img initrd=\initramfs-linux-ck.img root=PARTUUID=3a0ebdfc-e32f-4a35-a482-35dcfd8ee34a resume=PARTUUID=18f13113-dc7f-4138-8084-4e4a67c581ba elevator=bfq nowatchdog rw [ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [ 0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [ 0.000000] x86/fpu: xstate_offset: 576, xstate_sizes: 256 [ 0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. [ 0.000000] e820: BIOS-provided physical RAM map: ... [ 1.134601] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0 [ 1.134898] xhci_hcd 0000:00:14.0: xHCI Host Controller [ 1.134905] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2 [ 1.135992] xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x0004b810 [ 1.135998] xhci_hcd 0000:00:14.0: cache line size of 64 is not supported [ 1.136266] hub 2-0:1.0: USB hub found [ 1.136284] hub 2-0:1.0: 11 ports detected [ 1.140057] xhci_hcd 0000:00:14.0: xHCI Host Controller [ 1.140061] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3 [ 1.140221] hub 3-0:1.0: USB hub found [ 1.140235] hub 3-0:1.0: 4 ports detected [ 1.141794] ahci 0000:00:1f.2: version 3.0 [ 1.141964] ahci 0000:00:1f.2: SSS flag set, parallel bus scan disabled [ 1.152044] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 4 ports 6 Gbps 0x8 impl SATA mode [ 1.152047] ahci 0000:00:1f.2: flags: 64bit ncq stag pm led clo only pio slum part deso sadm sds apst [ 1.152452] scsi host0: ahci [ 1.152598] scsi host1: ahci [ 1.152697] scsi host2: ahci [ 1.152789] scsi host3: ahci [ 1.152825] ata1: DUMMY [ 1.152826] ata2: DUMMY [ 1.152826] ata3: DUMMY [ 1.152828] ata4: SATA max UDMA/133 abar m2048@0xf7422000 port 0xf7422280 irq 46 [ 1.480802] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 1.483284] ata4.00: NCQ Send/Recv Log not supported [ 1.483290] ata4.00: ATA-9: SAMSUNG SSD PM851 M.2 2280 256GB, EXT25D0Q, max UDMA/133 [ 1.483294] ata4.00: 500118192 sectors, multi 16: LBA48 NCQ (depth 31/32), AA [ 1.484011] ata4.00: NCQ Send/Recv Log not supported [ 1.484068] ata4.00: configured for UDMA/133 [ 1.484431] scsi 3:0:0:0: Direct-Access ATA SAMSUNG SSD PM85 5D0Q PQ: 0 ANSI: 5 [ 1.487748] usb 1-1: new high-speed USB device number 2 using ehci-pci [ 1.507784] usb 2-1: new full-speed USB device number 2 using xhci_hcd [ 1.564223] sd 3:0:0:0: [sda] 500118192 512-byte logical blocks: (256 GB/238 GiB) [ 1.564249] sd 3:0:0:0: [sda] Write Protect is off [ 1.564254] sd 3:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 1.564306] sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 1.567449] sda: sda1 sda2 sda3 sda4 [ 1.567749] sd 3:0:0:0: [sda] Attached SCSI disk [ 1.652454] hub 1-1:1.0: USB hub found [ 1.652622] hub 1-1:1.0: 8 ports detected [ 1.658128] PM: Starting manual resume from disk [ 1.658131] PM: Hibernation image partition 8:2 present [ 1.658132] PM: Looking for hibernation image. [ 1.658305] PM: Image not found (code -22) [ 1.658306] PM: Hibernation image not present or could not be loaded. [ 1.679878] random: fast init done [ 1.731749] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null) [ 1.808971] ip_tables: (C) 2000-2006 Netfilter Core Team [ 1.813785] systemd[1] : systemd 232 running in system mode. (+PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN) [ 1.813932] systemd[1] : Detected architecture x86-64. [ 1.814557] systemd[1] : Set hostname to . [ 1.817732] usb 2-3: new full-speed USB device number 3 using xhci_hcd [ 1.882521] systemd[1] : Set up automount Arbitrary Executable File Formats File System Automount Point. [ 1.883233] systemd[1] : Created slice User and Session Slice. [ 1.883333] systemd[1] : Listening on /dev/initctl Compatibility Named Pipe. [ 1.883425] systemd[1] : Listening on Journal Socket (/dev/log). [ 1.883514] systemd[1] : Started Forward Password Requests to Wall Directory Watch. [ 1.883602] systemd[1] : Listening on Device-mapper event daemon FIFOs. [ 1.883690] systemd[1] : Started Dispatch Password Requests to Console Directory Watch. [ 1.901987] EXT4-fs (sda3): re-mounted. Opts: discard,data=ordered [ 2.030202] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input2 [ 2.030783] ACPI: Lid Switch [LID0] [ 2.030854] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3 [ 2.030857] ACPI: Power Button [PBTN] [ 2.031841] ACPI: AC Adapter [AC] (off-line) [ 2.033912] proc_thermal 0000:00:04.0: enabling device (0000 -> 0002) [ 2.035422] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input4 [ 2.035428] ACPI: Sleep Button [SBTN] [ 2.035539] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input5 [ 2.035542] ACPI: Power Button [PWRF] [ 2.044011] ACPI Warning: \_SB.IETM._ART: Return Package type mismatch at index 0 - found Integer, expected Reference (20170119/nspredef-297) [ 2.044021] ACPI: Invalid package element : got number, expecting [R] [ 2.044022] _ART package 0 is invalid, ignored [ 2.097729] tsc: Refined TSC clocksource calibration: 2194.918 MHz [ 2.097734] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x1fa37202099, max_idle_ns: 440795206796 ns [ 2.102435] systemd-journald: Received request to flush runtime journal from PID 1 [ 2.137774] usb 2-5: new high-speed USB device number 4 using xhci_hcd [ 2.199459] hidraw: raw HID events driver (C) Jiri Kosina [ 2.200577] (NULL device *): hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info(). [ 2.202927] thermal LNXTHERM:00: registered as thermal_zone7 [ 2.202929] ACPI: Thermal Zone [THM] (25 C) [ 2.204142] wmi: Mapper loaded [ 2.212758] thermal LNXTHERM:01: registered as thermal_zone8 [ 2.212760] ACPI: Thermal Zone [TZ00] (34 C) [ 2.222982] thermal LNXTHERM:02: registered as thermal_zone9 [ 2.222984] ACPI: Thermal Zone [TZ01] (34 C) [ 2.231379] ACPI: Battery Slot [BAT0] (battery present) [ 2.298443] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 2.338464] i801_smbus 0000:00:1f.3: SPD Write Disable is set [ 2.338539] i801_smbus 0000:00:1f.3: SMBus using PCI interrupt [ 2.348705] intel_pch_thermal 0000:00:1f.6: enabling device (0000 -> 0002) [ 2.348941] (NULL device *): hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info(). [ 2.349005] snd_hda_intel 0000:00:03.0: enabling device (0000 -> 0002) [ 2.349145] snd_hda_intel 0000:00:1b.0: enabling device (0000 -> 0002) [ 2.361342] Adding 8911868k swap on /dev/sda2. Priority:-1 extents:1 across:8911868k SSFS [ 2.375421] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC3263: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [ 2.375423] snd_hda_codec_realtek hdaudioC1D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 2.375425] snd_hda_codec_realtek hdaudioC1D0: hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 2.375426] snd_hda_codec_realtek hdaudioC1D0: mono: mono_out=0x0 [ 2.375428] snd_hda_codec_realtek hdaudioC1D0: inputs: [ 2.375430] snd_hda_codec_realtek hdaudioC1D0: Headset Mic=0x18 [ 2.375432] snd_hda_codec_realtek hdaudioC1D0: Headphone Mic=0x1a [ 2.375433] snd_hda_codec_realtek hdaudioC1D0: Internal Mic=0x12 [ 2.378024] input: PC Speaker as /devices/platform/pcspkr/input/input6 [ 2.393846] wl: loading out-of-tree module taints kernel. [ 2.393849] wl: module license 'MIXED/Proprietary' taints kernel. [ 2.393850] Disabling lock debugging due to kernel taint [ 2.395919] RAPL PMU: API unit is 2^-32 Joules, 4 fixed counters, 655360 ms ovfl timer [ 2.395921] RAPL PMU: hw unit of domain pp0-core 2^-14 Joules [ 2.395922] RAPL PMU: hw unit of domain package 2^-14 Joules [ 2.395922] RAPL PMU: hw unit of domain dram 2^-14 Joules [ 2.395923] RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules [ 2.396427] dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2) [ 2.404262] wl 0000:02:00.0: enabling device (0000 -> 0002) [ 2.427078] AVX2 version of gcm_enc/dec engaged. [ 2.427079] AES CTR mode by8 optimization enabled [ 2.441627] random: crng init done [ 2.452210] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/sound/card1/input7 [ 2.452405] input: HDA Intel PCH Headphone Mic as /devices/pci0000:00/0000:00:1b.0/sound/card1/input9 [ 2.469884] wlan0: Broadcom BCM43b1 802.11 Hybrid Wireless Controller 6.30.223.271 (r587334) [ 2.476553] [drm] Memory usable by graphics device = 4096M [ 2.476556] checking generic (e0000000 7e9000) vs hw (e0000000 10000000) [ 2.476557] fb: switching to inteldrmfb from EFI VGA [ 2.476580] Console: switching to colour dummy device 80x25 [ 2.476687] [drm] Replacing VGA console driver [ 2.477144] [drm] ACPI BIOS requests an excessive sleep of 25000 ms, using 1500 ms instead [ 2.488089] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: discard,data=ordered [ 2.490303] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 2.490304] [drm] Driver supports precise vblank timestamp query. [ 2.492246] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 2.499820] intel_rapl: Found RAPL domain package [ 2.499823] intel_rapl: Found RAPL domain core [ 2.499824] intel_rapl: Found RAPL domain uncore [ 2.499825] intel_rapl: Found RAPL domain dram [ 2.499830] intel_rapl: RAPL package 0 domain package locked by BIOS [ 2.499835] intel_rapl: RAPL package 0 domain dram locked by BIOS [ 2.502529] [drm] Initialized i915 1.6.0 20170123 for 0000:00:02.0 on minor 0 [ 2.503948] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) [ 2.506665] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input10 [ 2.506995] snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 2.507006] [drm] Initialized i915 1.6.0 20170123 for 0000:00:02.0 on minor 0 [ 2.604468] dell_wmi: Detected Dell WMI interface version 1 [ 2.604594] input: Dell WMI hotkeys as /devices/virtual/input/input11 [ 2.608888] input: DLL0665:01 06CB:76AD Touchpad as /devices/pci0000:00/INT3433:00/i2c-1/i2c-DLL0665:01/0018:06CB:76AD.0001/input/input13 [ 2.608965] hid-multitouch 0018:06CB:76AD.0001: input,hidraw0: I2C HID v1.00 Mouse [DLL0665:01 06CB:76AD] on i2c-DLL0665:01 [ 2.610405] wl 0000:02:00.0 wlp2s0: renamed from wlan0 [ 2.655707] mousedev: PS/2 mouse device common for all mice [ 2.668750] fbcon: inteldrmfb (fb0) is primary device [ 3.108005] clocksource: Switched to clocksource tsc [ 3.426028] media: Linux media interface: v0.10 [ 3.431855] Linux video capture interface: v2.00 [ 3.435199] Bluetooth: Core ver 2.22 [ 3.435220] NET: Registered protocol family 31 [ 3.435220] Bluetooth: HCI device and connection manager initialized [ 3.435223] Bluetooth: HCI socket layer initialized [ 3.435225] Bluetooth: L2CAP socket layer initialized [ 3.435230] Bluetooth: SCO socket layer initialized [ 3.440625] usbcore: registered new interface driver btusb [ 3.441768] dm9601 2-1:1.0 eth0: register 'dm9601' at usb-0000:00:14.0-1, Davicom DM96xx USB 10/100 Ethernet, 00:e0:4c:53:44:58 [ 3.441862] usbcore: registered new interface driver dm9601 [ 3.442095] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD (0bda:5682) [ 3.443756] usbcore: registered new interface driver sr9700 [ 3.445335] dm9601 2-1:1.0 enp0s20u1: renamed from eth0 [ 3.451777] uvcvideo 2-5:1.0: Entity type for entity Extension 4 was not initialized! [ 3.451778] uvcvideo 2-5:1.0: Entity type for entity Extension 7 was not initialized! [ 3.451779] uvcvideo 2-5:1.0: Entity type for entity Processing 2 was not initialized! [ 3.451780] uvcvideo 2-5:1.0: Entity type for entity Camera 1 was not initialized! [ 3.451844] input: Integrated_Webcam_HD as /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/input/input18 [ 3.451903] usbcore: registered new interface driver uvcvideo [ 3.451904] USB Video Class driver (1.1.1) [ 3.559500] Bluetooth: hci0: BCM: chip id 63 [ 3.575523] Bluetooth: hci0: BCM20702A [ 3.576508] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000 [ 3.990327] Console: switching to colour frame buffer device 240x67 [ 4.011534] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device [ 4.050380] input: HDA Intel HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.0/sound/card0/input19 [ 4.050444] input: HDA Intel HDMI HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.0/sound/card0/input20 [ 4.050503] input: HDA Intel HDMI HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.0/sound/card0/input21 [ 4.050562] input: HDA Intel HDMI HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:03.0/sound/card0/input22 [ 4.050649] input: HDA Intel HDMI HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:03.0/sound/card0/input23 [ 4.164982] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 4.164984] Bluetooth: BNEP filters: protocol multicast [ 4.164988] Bluetooth: BNEP socket layer initialized [ 4.338501] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1572 [ 4.354498] Bluetooth: hci0: DW1560 Bluetooth 4.0 LE [ 4.645255] IPv6: ADDRCONF(NETDEV_UP): enp0s20u1: link is not ready [ 4.689285] dm9601 2-1:1.0 enp0s20u1: link up, 100Mbps, full-duplex, lpa 0xFFFF [ 4.756496] dm9601 2-1:1.0 enp0s20u1: kevent 4 may have been dropped [ 4.762065] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready [ 4.767490] dm9601 2-1:1.0 enp0s20u1: kevent 4 may have been dropped [ 4.799684] dm9601 2-1:1.0 enp0s20u1: link up, 100Mbps, full-duplex, lpa 0xFFFF [ 4.887666] dm9601 2-1:1.0 enp0s20u1: link up, 100Mbps, full-duplex, lpa 0xFFFF [ 6.711458] Bluetooth: RFCOMM TTY layer initialized [ 6.711466] Bluetooth: RFCOMM socket layer initialized [ 6.711475] Bluetooth: RFCOMM ver 1.11 [ 7.450784] TCP: request_sock_TCP: Possible SYN flooding on port 45265. Sending cookies. Check SNMP counters. [ 15.633644] fuse init (API version 7.26)

Hardware: - Samsung 980 PRO M.2 NVMe SSD (MZ-V8P2T0BW) (2TB) - Beelink GTR6, with the SSD in the NVMe slot Since the hardware arrived, I've installed Ubuntu Server on it as well as a bunch of services (mostly in docker, DBs and services like Kafka). After 2-3 days of uptime (record is almost a week, but usually it's 2-3 days), I typically start getting buffer i/o errors on the nvme slot (which is also the boot drive): If I'm quick enough, I can still login via SSH but the system becomes increasingly unstable before commands start failing with an I/O error. When I did manage to login, it did seem to think there's no connected NVME SSDs: Another instance of the buffer I/O error on the nvme slot: Because of this and trying to check everything I could find, I ran FSCK on boot to see if there was anything obvious - this is quite common after the hard reset: # cat /run/initramfs/fsck.log Log of fsck -C -f -y -V -t ext4 /dev/mapper/ubuntu--vg-ubuntu--lv Fri Dec 30 17:26:21 2022 fsck from util-linux 2.37.2 [/usr/sbin/fsck.ext4 (1) -- /dev/mapper/ubuntu--vg-ubuntu--lv] fsck.ext4 -f -y -C0 /dev/mapper/ubuntu--vg-ubuntu--lv e2fsck 1.46.5 (30-Dec-2021) /dev/mapper/ubuntu--vg-ubuntu--lv: recovering journal Clearing orphaned inode 524449 (uid=1000, gid=1000, mode=0100664, size=6216) Pass 1: Checking inodes, blocks, and sizes Inode 6947190 extent tree (at level 1) could be shorter. Optimize? yes Inode 6947197 extent tree (at level 1) could be shorter. Optimize? yes Inode 6947204 extent tree (at level 1) could be shorter. Optimize? yes Inode 6947212 extent tree (at level 1) could be shorter. Optimize? yes Inode 6947408 extent tree (at level 1) could be shorter. Optimize? yes Inode 6947414 extent tree (at level 1) could be shorter. Optimize? yes Inode 6947829 extent tree (at level 1) could be shorter. Optimize? yes Inode 6947835 extent tree (at level 1) could be shorter. Optimize? yes Inode 6947841 extent tree (at level 1) could be shorter. Optimize? yes Pass 1E: Optimizing extent trees Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Free blocks count wrong (401572584, counted=405399533). Fix? yes Free inodes count wrong (121360470, counted=121358242). Fix? yes /dev/mapper/ubuntu--vg-ubuntu--lv: ***** FILE SYSTEM WAS MODIFIED ***** /dev/mapper/ubuntu--vg-ubuntu--lv: 538718/121896960 files (0.2% non-contiguous), 82178067/487577600 blocks fsck exited with status code 1 Fri Dec 30 17:26:25 2022 ---------------- Running smart-log doesn't seem to show anything concerning, other than the number of unsafe shutdowns (the number of times this has happened so far)... # nvme smart-log /dev/nvme0 Smart Log for NVME device:nvme0 namespace-id:ffffffff critical_warning : 0 temperature : 32 C (305 Kelvin) available_spare : 100% available_spare_threshold : 10% percentage_used : 0% endurance group critical warning summary: 0 data_units_read : 8,544,896 data_units_written : 5,175,904 host_read_commands : 39,050,379 host_write_commands : 191,366,905 controller_busy_time : 1,069 power_cycles : 21 power_on_hours : 142 unsafe_shutdowns : 12 media_errors : 0 num_err_log_entries : 0 Warning Temperature Time : 0 Critical Composite Temperature Time : 0 Temperature Sensor 1 : 32 C (305 Kelvin) Temperature Sensor 2 : 36 C (309 Kelvin) Thermal Management T1 Trans Count : 0 Thermal Management T2 Trans Count : 0 Thermal Management T1 Total Time : 0 Thermal Management T2 Total Time : 0 I have reached out to support and their initial suggestion along with a bunch of questions was whether I had tried to reinstall the OS. I've given this a go too, formatting the drive and reinstalling the OS (Ubuntu Server 22 LTS). After that, the issue hadn't happened for 4 days before it finally showed itself as a kernel panic: Any ideas what I can do to identify if the problem is with the SSD itself or the hardware that the SSD is slotted into (the GTR6)? I have until the 31st to return the SSD, so would love to pin down the most likely cause of the issue sooner rather than later... I'm even more concerned after seeing reports that others are having serious health issues with the Samsung 990 Pro: https://www.reddit.com/r/hardware/comments/10jkwwh/samsung_990_pro_ssd_with_rapid_health_drops/ Edit: although I realised those reported issues are with the 990 pro, not the 980 pro that I have! Edit2: someone in overclockers was kind enough to suggest hd sentinel, which does show a health metric, which seems ok: # ./hdsentinel-019c-x64 Hard Disk Sentinel for LINUX console 0.19c.9986 (c) 2021 info@hdsentinel.com Start with -r [reportfile] to save data to report, -h for help Examining hard disk configuration ... HDD Device 0: /dev/nvme0 HDD Model ID : Samsung SSD 980 PRO 2TB HDD Serial No: S69ENL0T905031A HDD Revision : 5B2QGXA7 HDD Size : 1907729 MB Interface : NVMe Temperature : 41 °C Highest Temp.: 41 °C Health : 99 % Performance : 100 % Power on time: 21 days, 12 hours Est. lifetime: more than 1000 days Total written: 8.30 TB The status of the solid state disk is PERFECT. Problematic or weak sectors were not found. The health is determined by SSD specific S.M.A.R.T. attribute(s): Available Spare (Percent), Percentage Used No actions needed. Lastly, none of the things I tried such as the smart-log seem to show something like a health metric. How can I check this in ubuntu? Thanks!

I'd like to disable my CD/DVD drive so that it doesn't spin up every time I select Save in my Kate editor, or select a file-accessing action in other applications. The spinning up just delays what I'm doing, and I'm not even using the DVD drive. I want to leave the CD in the drive, and not have it spin up. I found a website that said a udev rule will definitely disable the drive. So far, I've tried the following 2 rules (separately), but neither of them disable the DVD drive (it still spins up - even when not mounted):

ENV{ID_SERIAL}=="PIONEER_DVD-RW_DVRTD11RS_SAC1009942", ENV{UDISKS_IGNORE}="1"

KERNEL=="sr0",ENV{UDISKS_IGNORE}="1", RUN+="/bin/touch /home/peter/udev-rule-ran"

The RUN+ in the second instance, creates my test file "udev-rule-ran", so this tells me that my rule file is being executed, and that the rule line is being run. ## My Question: Could you tell me what I should be doing to definitely disable the darned DVD drive? I also want to be able to enable the drive again on the occasions that I need it. ## Supplementary Details: I'm trying very hard to write a udev rule to disable my CD/DVD drive. I've tried various non-udev methods to disable it but none of them work. There is no loaded module¹⁾ for the drive that I can unload, so I can't use that method to disable the drive. *¹⁾ So I think the driver must be compiled into the kernel.*

My question may be weird. I want to know if there is some virtual machine that lets me install Windows 7 under Linux and lets Windows use, as a virtual device, the same device that is really installed in my physical PC. I need to do that, because of a lot of Adobe software that I need for work and I can't switch to other software (even if I'd like to). Maybe what I need could be something even simpler, like letting the virtual machine see the graphics card I have to get the full compatibility with the Adobe software and the OpenGL and DirectX drivers. Actually I use VirtualBox to run Windows, and Fedora is my main OS. The hardware that I need to share is as follows: ⠀CPU - Intel Core i7 990x (even only a subset of all the cores) ⠀GPU - Nvidia Quadro 2000

I have 2 GPU's in my netbook. How do I know which one I'm actually using at any given moment?

I'm running some (not so new) Linux distribution. I want to determine what the memory bandwidth of my system is - not the effective bandwidth I can get from benchmarking/testing - but the _nominal_ bandwidth, given my board, CPU sockets, memory channels and RAM DIMMs. I should mention that when I try to figure this out in my head I always get the calculations mixed up: gigabytes verus gigabits, transactions per seconds vs bytes per second, the number of channels vs the number of DIMMs etc. Note: If possible, assume I don't have utilities such as lshw or inxi installed.

I have Getac tablet (UX10G3) which having inbuilt sensor like gyro, als, accelerometer and magnetometer connected over Intel Sensor Hub. These sensors are working perfectly in Windows 11 and i have verified data in Sesnor Explorer Application. My Magnetometer sensor model is AK09911C which is Geomagnetic Hall Sensor Three Axis Magnetometer Compass Module from Asahi Kasei Microdevices/AKM. Now i have installed RHEL 9.3 on this tablet and want to access these sensor data as IIO devices. My sensors like gyro, als and accelerometer working fine but magnetometer is not getting detected as IIO device. I have done some troubleshooting and found some information: 1. Kernel version is "5.14.0-362.8.1.el9_3.x86_64" 2. Intel CPU is "12th Gen Intel® Core™ i5-1235U × 12" and ISH is "Intel Corporation Alder Lake-P Integrated Sensor Hub (rev 01) (prog-if 00 )" 3. This ISH is using Kernel driver in use: intel_ish_ipc, Kernel modules: intel_ish_ipc. 4. Content of "/sys/bus/hid/drivers/hid-sensor-hub/001F:8087:0AC2.0004" is as follows:

HID-SENSOR-200001.1.auto
HID-SENSOR-200035.6.auto
HID-SENSOR-200041.4.auto
HID-SENSOR-2000e1.2.auto
HID-SENSOR-2000e1.3.auto
HID-SENSOR-2000e1.5.auto
HID-SENSOR-2000e1.7.auto
HID-SENSOR-2000e1.8.auto
HID-SENSOR-2000e1.9.auto

5. Here "HID-SENSOR-200041.4.auto" is ALS sensor and it is detected as IIO device also. I have verified that "HID-SENSOR-2000e1.5.auto" is Magnetometer but it is not detected as IIO device. 6. I have manually loaded "hid-sensor-magn-3d" kernel driver but got no suceess. I verified "hid-sensor-ids.h" file available my kernel source and found only

/* ORIENTATION: Compass 3D: (200083) */
#define HID_USAGE_SENSOR_COMPASS_3D	0x200083

7. It might be possible that HID 2000e1.5 is not matching with 0x200083 hence device further not handed over to "hid-sensor-magn-3d" module. Kindly guide me to get my magnetometer sensor detected as IIO device.

I have an ELAN touch-pad with vendor id 04F3:3128 and I'm trying to find the right Linux kernel drivers to support it. I will start by noting that the touch-pad works with live CDs, like for example Linux Mint. I can, however, not seem to find the right settings in the kernel to get it to work. (On a live CD where the mouse pad works) if I go into /sys/bus/hid/devices, I can find the device here listed as 0018:04F3:3128.0001. If I then cd into the device and then into the subsystem directory and then further into the directory drivers, here I can find hid-generic and hid-multitouch. I have enabled those using make nconfig and compiled the kernel, but it still can't find the mouse pad. How can I find the proper settings (or modules) in the kernel to support my mouse pad?

My desktop has lost wireless connectivity and I strongly suspect a hardware issue, but I would like to know how I can confirm that that is the problem before I buy a replacement. My reasons for thinking this are: - My NIC was a standard size, but I have a low profile case so, as a bodge, I cut the metal bracket. This worked fine, but it's never felt like it was seated properly, so may have died due to my own miserly stupidity - I use wicd-curses to connect to my network and it no longer detected any SSIDs. - running sudo ifconfig wlan0 up returns SIOCSIFFLAGS: Connection timed out - running iw dev shows my device details - running sudo ip link set wlan0 up returns RTNETLINK answers: Connection timed out - dmesg gives: iwlwifi 0000:01:00.0: Failed to load firmware chunk! iwlwifi 0000:01:00.0: Could not load the uCode section iwlwifi 0000:01:00.0: Failed to start INIT ucode: -110 iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110 I've exhausted my limited knowledge and Google searching from my phone isn't leading me anywhere. I'm really not familiar with this stuff, so any background info to help me understand what's going on here is very much appreciated! OS: Xubuntu 16.04 (relatively recently upgraded from 14.04) Kernel: 4.4.0-47 **Edit:** I found the solution to my lost connectivity, but I still don't know ***why***. I am therefore leaving this question here in the hope that someone can answer my original question: **how can I debug this kind of problem?**

On a Samsung SATA SSD, i.e. non NVMe disk, the following are the SmartCtl values that are obtained by running the command sudo smartctl -a /dev/sda, SMART Attributes Data Structure revision number: 1 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 177 Wear_Leveling_Count 0x0013 099 099 000 Pre-fail Always - 18 241 Total_LBAs_Written 0x0032 099 099 000 Old_age Always - 10452411061 On the same disk when the command sudo skdump /dev/sda is run the following is the output. Overall Status: GOOD ID# Name Value Worst Thres Pretty Raw Type Updates Good Good/Past 5 reallocated-sector-count 100 100 10 0 sectors 0x000000000000 prefail online yes yes 177 wear-leveling-count 99 99 0 18 0x120000000000 prefail online n/a n/a 241 total-lbas-written 99 99 0 350725.752 TB 0x3d9b036f0200 old-age online n/a n/a For this I had the following queries 1) skdump command is returning a value of 350725.752 TB written, i.e. total-lbas-written. Is this correct? 2) Based on the answer provided in another post the output of smartctl for total-lbas-written is 10452411061, which equates to 4.86 TB written (i.e. 10452411061/2/1024/1024/1024). This differs significantly from the value reported by the skdump command. Is this value accurate? The Sector size is 512 bytes. 3) After looking at various posts in SuperUser and StackExchange, for samsung ssd drives the value of Wear_Leveling_Count determines how much wear leveling has occurred on the SSD. But it is not clear what figure should be considered? The figure of the column **RAW_VALUE** or **VALUE** column. And does having RAW_VALUE of 18 implies that only 18% of the SSD life is left?

I have a **multi-graphics card** (e.g: *AMD RADEON RX560, AMD RADEON R7 200, nVidia GT500*... etc) and **multi-screen** (e.g: *ACER, ASUS, DELL*... etc) computer, as shown in the below example scheme: The only way I know to find if some **specific graphics card** is **connected to a specific screen** is by checking the cables of the computer, but that requires for me to open the computer box to distinguish between graphics cards. Is there a more practical way to obtain this information?

I have the weird issue that lsusb shows USB devices that are not connected. We have a couple of devices connected via USB. To disconnect them from the system we disable the power to the USB port with a special hub-like device. Afterwards the devices are gone (you can see that on the device) but lsusb still shows the old entries. What does this mean? Are there dangling and invalid handles to these devices left on the system/OS?

My Samsung 970 EVO M.2 500GB SSD (MZ-V7E500BW) suddenly failed yesterday during a power outage. I now have a warning during POST ("WARNING! Please back up your data and replace your hard disk drive. WARNING! Your HDD/SSD might crash at any moment."). The last time I rebooted before this was about 5 days earlier, and the warning was not present then. By booting a live USB stick I managed to check the SMART log: Smart Log for NVME device:nvme0 namespace-id:ffffffff critical_warning : 0x8 temperature : 49 C available_spare : 29% available_spare_threshold : 10% percentage_used : 0% endurance group critical warning summary: 0 data_units_read : 4,948,748 data_units_written : 20,573,476 host_read_commands : 100,316,217 host_write_commands : 357,643,056 controller_busy_time : 1,790 power_cycles : 24 power_on_hours : 4,570 unsafe_shutdowns : 11 media_errors : 41 num_err_log_entries : 70 Warning Temperature Time : 0 Critical Composite Temperature Time : 0 Temperature Sensor 1 : 49 C Temperature Sensor 2 : 74 C Thermal Management T1 Trans Count : 0 Thermal Management T2 Trans Count : 0 Thermal Management T1 Total Time : 0 Thermal Management T2 Total Time : 0 Messages from the kernel mentioning nvme during startup of the live USB OS: Oct 26 19:18:58 ubuntu kernel: [ 1.233479] nvme nvme0: pci function 0000:06:00.0 Oct 26 19:18:58 ubuntu kernel: [ 1.243303] nvme nvme0: missing or invalid SUBNQN field. Oct 26 19:18:58 ubuntu kernel: [ 1.243323] nvme nvme0: Shutdown timeout set to 8 seconds Oct 26 19:18:58 ubuntu kernel: [ 1.252449] nvme nvme0: 4/0/0 default/read/poll queues Oct 26 19:18:58 ubuntu kernel: [ 1.254855] nvme0n1: p1 p2 p3 Oct 26 19:18:58 ubuntu kernel: [ 3.629244] EXT4-fs (nvme0n1p2): INFO: recovery required on readonly filesystem Oct 26 19:18:58 ubuntu kernel: [ 3.629246] EXT4-fs (nvme0n1p2): write access will be enabled during recovery Oct 26 19:18:58 ubuntu kernel: [ 3.674861] blk_update_request: critical medium error, dev nvme0n1, sector 124928 op 0x1:(WRITE) flags 0x800 phys_seg 4 prio class 0 Oct 26 19:18:58 ubuntu kernel: [ 3.674893] Buffer I/O error on dev nvme0n1p2, logical block 0, lost async page write Oct 26 19:18:58 ubuntu kernel: [ 3.674913] Buffer I/O error on dev nvme0n1p2, logical block 1, lost async page write Oct 26 19:18:58 ubuntu kernel: [ 3.674931] Buffer I/O error on dev nvme0n1p2, logical block 2, lost async page write Oct 26 19:18:58 ubuntu kernel: [ 3.674949] Buffer I/O error on dev nvme0n1p2, logical block 3, lost async page write Oct 26 19:18:58 ubuntu kernel: [ 3.674967] blk_update_request: critical medium error, dev nvme0n1, sector 133200 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 Oct 26 19:18:58 ubuntu kernel: [ 3.674995] Buffer I/O error on dev nvme0n1p2, logical block 1034, lost async page write Oct 26 19:18:58 ubuntu kernel: [ 3.675013] blk_update_request: critical medium error, dev nvme0n1, sector 133384 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 Oct 26 19:18:58 ubuntu kernel: [ 3.675040] Buffer I/O error on dev nvme0n1p2, logical block 1057, lost async page write Oct 26 19:18:58 ubuntu kernel: [ 3.675059] blk_update_request: critical medium error, dev nvme0n1, sector 147176 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 Oct 26 19:18:58 ubuntu kernel: [ 3.675086] Buffer I/O error on dev nvme0n1p2, logical block 2781, lost async page write Oct 26 19:18:58 ubuntu kernel: [ 3.675105] blk_update_request: critical medium error, dev nvme0n1, sector 4319360 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 Oct 26 19:18:58 ubuntu kernel: [ 3.675132] Buffer I/O error on dev nvme0n1p2, logical block 524304, lost async page write Oct 26 19:18:58 ubuntu kernel: [ 3.675151] blk_update_request: critical medium error, dev nvme0n1, sector 4319488 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 Oct 26 19:18:58 ubuntu kernel: [ 3.675178] Buffer I/O error on dev nvme0n1p2, logical block 524320, lost async page write Oct 26 19:18:58 ubuntu kernel: [ 3.675197] blk_update_request: critical medium error, dev nvme0n1, sector 4319544 op 0x1:(WRITE) flags 0x800 phys_seg 2 prio class 0 Oct 26 19:18:58 ubuntu kernel: [ 3.675224] Buffer I/O error on dev nvme0n1p2, logical block 524327, lost async page write Oct 26 19:18:58 ubuntu kernel: [ 3.675243] blk_update_request: critical medium error, dev nvme0n1, sector 4319816 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 Oct 26 19:18:58 ubuntu kernel: [ 3.675270] blk_update_request: critical medium error, dev nvme0n1, sector 4320256 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 Oct 26 19:18:58 ubuntu kernel: [ 3.675297] blk_update_request: critical medium error, dev nvme0n1, sector 4320936 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0 Oct 26 19:18:58 ubuntu kernel: [ 3.729319] EXT4-fs (nvme0n1p2): error loading journal Oct 26 19:18:58 ubuntu kernel: [ 3.743157] EXT4-fs (nvme0n1p3): INFO: recovery required on readonly filesystem Oct 26 19:18:58 ubuntu kernel: [ 3.743158] EXT4-fs (nvme0n1p3): write access will be enabled during recovery Oct 26 19:18:58 ubuntu kernel: [ 3.806113] EXT4-fs (nvme0n1p3): error loading journal Oct 26 19:19:04 ubuntu kernel: [ 30.724414] blk_update_request: critical medium error, dev nvme0n1, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 26 19:19:04 ubuntu kernel: [ 30.752254] blk_update_request: critical medium error, dev nvme0n1, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 26 19:19:05 ubuntu kernel: [ 31.346630] blk_update_request: critical medium error, dev nvme0n1, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 26 19:19:05 ubuntu kernel: [ 31.365831] blk_update_request: critical medium error, dev nvme0n1, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 26 19:19:29 ubuntu kernel: [ 55.502099] blk_update_request: critical medium error, dev nvme0n1, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 26 19:19:29 ubuntu kernel: [ 55.516704] blk_update_request: critical medium error, dev nvme0n1, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 26 19:24:44 ubuntu kernel: [ 370.116101] blk_update_request: critical medium error, dev nvme0n1, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 26 19:24:44 ubuntu kernel: [ 370.130330] blk_update_request: critical medium error, dev nvme0n1, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Thanks to ddrescue I managed to clone all of its partitions to a different machine over the network. There were IO errors while extracting both ext4 partitions but with enough retries it eventually got everything. After that I was able to run e2fsck on the images, which appeared to succeed, and now I can mount them as read-only loop devices. Data appears to be intact. I suppose the first question is **is there anything I can do to fix whatever the problem is, and keep using this drive?** I'm assuming not, but I'm definitely open to suggestions. If I try to run fsck on one of the partitions from the live USB, this is what happens. I tried all combinations of answers to the questions as you'll see below. I can't understand enough of the manual pages and don't know enough about filesystems or drives to know what options, if any, might help me. ubuntu@ubuntu:~$ sudo fsck /dev/nvme0n1p3 fsck from util-linux 2.36.1 e2fsck 1.46.3 (27-Jul-2021) /dev/nvme0n1p3: recovering journal Superblock needs_recovery flag is clear, but journal has data. Run journal anyway? yes fsck.ext4: Input/output error while recovering journal of /dev/nvme0n1p3 fsck.ext4: unable to set superblock flags on /dev/nvme0n1p3 /dev/nvme0n1p3: ********** WARNING: Filesystem still has errors ********** ubuntu@ubuntu:~$ sudo fsck /dev/nvme0n1p3 fsck from util-linux 2.36.1 e2fsck 1.46.3 (27-Jul-2021) /dev/nvme0n1p3: recovering journal Superblock needs_recovery flag is clear, but journal has data. Run journal anyway? no Clear journal? no fsck.ext4: Input/output error while recovering journal of /dev/nvme0n1p3 fsck.ext4: unable to set superblock flags on /dev/nvme0n1p3 /dev/nvme0n1p3: ********** WARNING: Filesystem still has errors ********** ubuntu@ubuntu:~$ sudo fsck /dev/nvme0n1p3 fsck from util-linux 2.36.1 e2fsck 1.46.3 (27-Jul-2021) /dev/nvme0n1p3: recovering journal Superblock needs_recovery flag is clear, but journal has data. Run journal anyway? no Clear journal? yes fsck.ext4: Input/output error while recovering journal of /dev/nvme0n1p3 fsck.ext4: unable to set superblock flags on /dev/nvme0n1p3 /dev/nvme0n1p3: ********** WARNING: Filesystem still has errors ********** ubuntu@ubuntu:~$ I believe the drive is still under warranty, and I'm trying to get in contact with Samsung support to try to get a replacement or refund. If they ask me to send it back, that's going to pose a problem since there's sensitive data on this drive. The drive resists all attempts to write to it. I can't mount it and write to it normally. The kernel emits IO errors if I try to write to it at the block level. Even Samsung's secure erase tool (their Windows-only software offers to produce a bootable USB drive with such a tool) fails. **Is there some way to force secure erasure of this device?**

https://bugzilla.redhat.com/show_bug.cgi?id=1679010 seeing this log:

Failed to init entropy source hwrng

Does Intel or AMD CPU contain a hwrng device? or it need extra chip/card/device?

I have installed CentOS 6.5 on a Dell Insperion with an Intel chip. I first noticed that my microphone is not working on Skype on CentOS although it was working fine with Windows 7 on the same box. The speakers work fine on both operating systems. I did the following test. arecord -vv -d 10 test.wav aplay -vv test.wav and did not get any sound played back. I went to System:Preferences:Sound to get the Sound Preferences dialog. I went to the Input tab and "Microphone" was selected as the connector. I turned the input volume up to maximum and spoke into the microphone but the "Input level" boxes all remained a light grey like it was disabled. The only option for "Choose a device for sound input" is "Internal Audio Analog Stereo".

I've been given a brand new Dell Precision 5690 laptop for a new job. I've installed Debian 12, and upgraded its kernel to 6.12.12 as most of its hardware didn't work on the 6.1 that comes with Bookworm. I'm using i3 window manager. At some point, the touchpad stopped working. Not sure when exactly, as I've been using it docked with a mouse, but it definitely _was_ working but no longer does. It could be that it was working with Wayland and when I moved to i3/X, it stopped. I have the following packages installed:

xserver-xorg-input-libinput/stable,now 1.2.1-1+b1 amd64 [installed]
xserver-xorg-input-wacom/stable,now 1.1.0-1 amd64 [installed,automatic][/code]

I've pasted a ton of debugging output here: https://www.pastery.net/hghjmj+unyxkc+unxdvs+uurwru+dsdrdr - xinput list shows the device as expected - xinput test reports no events - Though, at one point, I DID manage to get it to report clicks (but not movement). You can see this in my pastery output. No idea how or why, but it no longer works - I can't see any reference to the device in Xorg.0.log (though, should I be looking at /var/log/Xorg... or /var/log/installer/Xorg... ?) - sudo libinput record clearly shows the touchpad is working - sudo libinput measure touchpad-pressure shows that pressure is working - The touchpad works as expected in the BIOS configuration screen - Touchpad doesn't work at the login screen either, or once X starts after login - Everything points at /dev/input/event5 being the correct path for the Touchpad, but when I grep Xorg logs for event5, it appears to list either a Generic USB Audio device or a PS/2 mouse I have been trying to play around with Xorg configuration files, e.g. using InputClass sections to "catch" the touchpad and apply the libinput driver to it. I've also tried doing this and applying the evdev driver, as I can see evdev mentioned in the libinput record output. Neither of these strategies appear to work, though I know these configuration files are working as if I remove the catch-all libinput conf file, my keyboard and mouse stop working too. I've asked in loads of places, and nobody appears to be able to help me - can anyone give me any ideas of where I should continue to look? *** EDIT *** Brief update on this - the touchpad does work with my original kernel version 6.1. xinput detects it as a "PS/2 Generic Mouse" and although I can't two-finger scroll or anything, it does otherwise work as expected. Would this indicate a firmware issue? If so, is there any way of resolving? Barely anything else (hardware-wise) works in kernel 6.1 unfortunately.