Re: MX Modified - Latest MX KDE 5.22 Using MX21 beta
Posted: Mon Feb 07, 2022 7:25 am
Happy to help with anything if needs arise. With most my Debian duties dropped, I have free hands :-D :-D
Support for MX and antiX Linux distros
http://www.forum.mxlinux.org/
Code: Select all
System: Kernel: 5.10.0-10-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1
parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-10-amd64
root=UUID=<filter> ro quiet splash init=/lib/systemd/systemd
Desktop: KDE Plasma 5.24.0 wm: kwin_wayland vt: 2 dm: SDDM
Distro: MX-21_KDE_x64 Wildflower October 5 2021 base: Debian GNU/Linux 11 (bullseye)
Machine: Type: Laptop System: ASUSTeK product: T101HA v: 1.0 serial: <filter>
Mobo: ASUSTeK model: T101HA v: 1.0 serial: <filter> UEFI: American Megatrends v: T101HA.203
date: 07/15/2016
Battery: ID-1: BATC charge: 18.9 Wh (84.0%) condition: 22.5/31.6 Wh (71.0%) volts: 3.9 min: 3.8
model: Intel SR 1 SR Real Battery type: Li-ion serial: <filter> status: Charging cycles: 197
CPU: Info: Quad Core model: Intel Atom x5-Z8350 bits: 64 type: MCP arch: Airmont family: 6
model-id: 4C (76) stepping: 4 microcode: 411 cache: L2: 1024 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 11520
Speed: 759 MHz min/max: 480/1920 MHz Core speeds (MHz): 1: 606 2: 581 3: 684 4: 721
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds mitigation: Clear CPU buffers; SMT disabled
Type: meltdown mitigation: PTI
Type: spec_store_bypass status: Not affected
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2
mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics
vendor: ASUSTeK driver: i915 v: kernel bus-ID: 00:02.0 chip-ID: 8086:22b0 class-ID: 0300
Display: wayland server: X.Org 1.20.13 compositor: kwin_wayland driver: loaded: modesetting
unloaded: fbdev,vesa display-ID: :1 screens: 1
Screen-1: 0 s-res: 1280x800 s-dpi: 96 s-size: 338x211mm (13.3x8.3") s-diag: 398mm (15.7")
Monitor-1: XWAYLAND0 res: 1280x800 hz: 60
OpenGL: renderer: Mesa DRI Intel HD Graphics (CHV) v: 4.6 Mesa 21.2.5 compat-v: 3.0
direct render: Yes
Audio: Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Imaging Unit
vendor: ASUSTeK driver: intel_atomisp2_pm v: kernel bus-ID: 00:03.0 chip-ID: 8086:22b8
class-ID: 0480
Sound Server-1: ALSA v: k5.10.0-10-amd64 running: yes
Sound Server-2: PulseAudio v: 14.2 running: yes
Network: Device-1: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: AzureWave
driver: ath10k_pci v: kernel modules: wl port: f000 bus-ID: 01:00.0 chip-ID: 168c:0042
class-ID: 0280
IF: wlan0 state: up mac: <filter>
Bluetooth: Device-1: IMC Networks type: USB driver: btusb v: 0.8 bus-ID: 1-3:3 chip-ID: 13d3:3501
class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 1 state: down bt-service: enabled,running rfk-block:
hardware: no software: no address: <filter>
Info: acl-mtu: 1024:8 sco-mtu: 50:8 link-policy: rswitch hold sniff link-mode: slave accept
Drives: Local Storage: total: 87.09 GiB used: 11.37 GiB (13.1%)
ID-1: /dev/mmcblk0 maj-min: 179:768 vendor: SanDisk model: SD64G size: 57.97 GiB block-size:
physical: 512 B logical: 512 B type: SSD serial: <filter> scheme: GPT
SMART Message: Unknown smartctl error. Unable to generate data.
ID-2: /dev/mmcblk1 maj-min: 179:0 vendor: Samsung model: BJNB4R size: 29.12 GiB block-size:
physical: 512 B logical: 512 B type: SSD serial: <filter> rev: 0x8 scheme: GPT
SMART Message: Unknown smartctl error. Unable to generate data.
Partition: ID-1: / raw-size: 27.36 GiB size: 26.77 GiB (97.82%) used: 11.21 GiB (41.9%) fs: ext4
dev: /dev/mmcblk1p2 maj-min: 179:2
ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
dev: /dev/mmcblk1p1 maj-min: 179:1
Swap: Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 1.5 GiB used: 172.2 MiB (11.2%) priority: -2
dev: /dev/mmcblk1p3 maj-min: 179:3
Sensors: System Temperatures: cpu: 6280.4 C mobo: N/A
Fan Speeds (RPM): cpu: 0
Repos: Packages: note: see --pkg apt: 2327 lib: 1257 flatpak: 0
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian bullseye-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bullseye main contrib non-free
2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/microsoft-edge-beta.list
1: deb [arch=amd64] https://packages.microsoft.com/repos/edge/ stable main
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb https://ftp.arnes.si/mirrors/mxlinux/packages/mx/repo/ bullseye main non-free
2: deb https://ftp.arnes.si/mirrors/mxlinux/packages/mx/repo/ bullseye ahs
Active apt repos in: /etc/apt/sources.list.d/norbertpreining.list
1: deb https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/frameworks/Debian_11/ ./
2: deb https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/plasma524/Debian_11/ ./
3: deb https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/apps2112/Debian_11/ ./
4: deb https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/other/Debian_11/ ./
5: deb https://download.opensuse.org/repositories/home:/npreining:/debian-kde:/other-deps/Debian_11/ ./
Active apt repos in: /etc/apt/sources.list.d/skype-stable.list
1: deb [arch=amd64] https://repo.skype.com/deb stable main
Info: Processes: 215 Uptime: 9m wakeups: 1 Memory: 1.77 GiB used: 1.05 GiB (59.3%) Init: systemd v: 247
runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 10.2.1 alt: 10 Shell: quick-system-in
default: Bash v: 5.1.4 running-in: quick-system-in inxi: 3.3.06
No problem, thank you for all the great work!
I created a separate topic for this webcam -> viewtopic.php?t=68788norbert wrote: Thu Feb 10, 2022 5:52 am No driver for the camera, strange.
USB device? If yes, please send us vendor and product id, can't imagine...