Problem logging into the system

Help for MX Fluxbox
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
Message
Author
Tarq
Posts: 134
Joined: Sun Jan 21, 2024 2:44 pm

Re: Problem logging into the system

#11 Post by Tarq »

Jerry3904 wrote: Fri Jan 17, 2025 9:54 am This part of your QSI suggests the partition in use is nearly full, which commonly results in being unable to log in:

Code: Select all

Partition:
  ID-1: / raw-size: 27.9 GiB size: 27.3 GiB (97.83%) used: 23.67 GiB (86.7%) fs: ext4
    dev: /dev/sda10 maj-min: 8:10
I suggest you try removing material to significantly drop those numbers or use gparted to expand the partition's size. Do you use MX Cleanup regularly?
I always use GPartd, but the latter is not always. The reason is that I am new to the system and we are still exploring, but I monitor the disk and what is happening. The disk data copy is updated.

Code: Select all

[CODE]System:
  Kernel: 6.1.0-17-amd64 [6.1.69-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/antiX/vmlinuz quiet splasht nosplash
  Desktop: Fluxbox v: 1.3.7 info: tint2 vt: 7 dm: LightDM v: 1.26.0 Distro: MX-23.2_fluxbox_x64
    Libretto January 21 2024 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Laptop System: HP product: HP Laptop 15-ra0xx v: Type1ProductConfigId
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: HP model: 832C v: 25.56 serial: <superuser required> UEFI: Insyde v: F.72
    date: 04/10/2023
Battery:
  ID-1: BAT1 charge: 0% condition: 31.1/31.1 Wh (100.0%) volts: 0.0 min: 11.1
    model: COMPAL PABAS0241231 type: Li-ion serial: <filter> status: not charging
CPU:
  Info: model: Intel Celeron N3060 bits: 64 type: MCP arch: Airmont level: v2 built: 2015-17
    process: Intel 14nm family: 6 model-id: 0x4C (76) stepping: 4 microcode: 0x411
  Topology: cpus: 1x cores: 2 smt: <unsupported> cache: L1: 112 KiB desc: d-2x24 KiB; i-2x32 KiB
    L2: 2 MiB desc: 2x1024 KiB
  Speed (MHz): avg: 2480 min/max: 480/2480 scaling: driver: intel_cpufreq governor: ondemand
    cores: 1: 2480 2: 2480 bogomips: 6400
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass status: Not affected
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW, STIBP: disabled, RSB
    filling, PBRSB-eIBRS: Not affected
  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: Hewlett-Packard driver: i915 v: kernel arch: Gen-8 process: Intel 14nm built: 2014-15
    ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:22b1
    class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: modesetting unloaded: fbdev,vesa
    dri: crocus gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1366x768 s-dpi: 96 s-size: 361x203mm (14.21x7.99") s-diag: 414mm (16.31")
  Monitor-1: eDP-1 model: BOE Display 0x06a5 built: 2015 res: 1366x768 hz: 60 dpi: 101 gamma: 1.2
    size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9 modes: 1366x768
  API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 400 (BSW) direct-render: Yes
Audio:
  Device-1: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series High Definition Audio
    vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:2284
    class-ID: 0403
  API: ALSA v: k6.1.0-17-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8723DE 802.11b/g/n PCIe Adapter vendor: Hewlett-Packard driver: rtw_8723de
    v: N/A modules: rtw88_8723de,wl pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 2000 bus-ID: 02:00.0
    chip-ID: 10ec:d723 class-ID: 0280
  IF: wlan0 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard
    driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: 1000 bus-ID: 03:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  IF: eth0 state: down mac: <filter>
Drives:
  Local Storage: total: 466.7 GiB used: 33.81 GiB (7.2%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD5000LPCX-60VHAT0 size: 465.76 GiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter>
    rev: 1A01 scheme: MBR
  ID-2: /dev/sdb maj-min: 8:16 type: USB model: General USB Flash Disk size: 961 MiB block-size:
    physical: 512 B logical: 512 B type: SSD serial: <filter> rev: 1.00 scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  Message: No partition data found.
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 5.61 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda5
    maj-min: 8:5
Sensors:
  System Temperatures: cpu: 43.0 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 1792 libs: 885 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm pkgs: 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 bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb https://mxrepo.com/mx/repo/ bookworm main non-free
Info:
  Processes: 177 Uptime: 46m wakeups: 2 Memory: 3.73 GiB used: 1.87 GiB (50.1%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
My English is bad, sorry for that. Please try to understand and express as much as possible

Tarq
Posts: 134
Joined: Sun Jan 21, 2024 2:44 pm

Re: Problem logging into the system

#12 Post by Tarq »

Jerry3904 wrote: Fri Jan 17, 2025 9:54 am This part of your QSI suggests the partition in use is nearly full, which commonly results in being unable to log in:

Code: Select all

Partition:
  ID-1: / raw-size: 27.9 GiB size: 27.3 GiB (97.83%) used: 23.67 GiB (86.7%) fs: ext4
    dev: /dev/sda10 maj-min: 8:10
I suggest you try removing material to significantly drop those numbers or use gparted to expand the partition's size. Do you use MX Cleanup regularly?

Code: Select all

$ lsblk 
NAME       MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0        7:0    0   1.6G  1 loop /live/linux
sda          8:0    0 465.8G  0 disk 
├─sda1       8:1    0   500M  0 part 
├─sda2       8:2    0 135.3G  0 part 
├─sda3       8:3    0   7.9G  0 part 
│ └─ventoy 254:0    0   1.7G  1 dm   /live/boot-dev
├─sda4       8:4    0     1K  0 part 
├─sda5       8:5    0   5.6G  0 part [SWAP]
├─sda6       8:6    0  94.2G  0 part 
├─sda7       8:7    0 146.9G  0 part 
└─sda8       8:8    0  75.3G  0 part /media/demo/Linux
sdb          8:16   1   961M  0 disk 
├─sdb1       8:17   1   928M  0 part /media/demo/VENTOY
└─sdb2       8:18   1    32M  0 part 
sr0         11:0    1  1024M  0 rom  
demo@mx1:~
$ 
My English is bad, sorry for that. Please try to understand and express as much as possible

Tarq
Posts: 134
Joined: Sun Jan 21, 2024 2:44 pm

Re: Problem logging into the system

#13 Post by Tarq »

siamhie wrote: Fri Jan 17, 2025 10:22 am When was the last time you did an update?

Your QSI reports MX-23.4_fluxbox_x64 and we are at MX-23.5_fluxbox_x64.
Also your kernel version is showing 6.1.0-26 and we are at 6.1.0-30.
I think the information relates to the live environment and not the static one, but I update it on a semi regular basis
My English is bad, sorry for that. Please try to understand and express as much as possible

User avatar
siamhie
Global Moderator
Posts: 3214
Joined: Fri Aug 20, 2021 5:45 pm

Re: Problem logging into the system

#14 Post by siamhie »

Tarq wrote: Fri Jan 17, 2025 11:24 am
siamhie wrote: Fri Jan 17, 2025 10:22 am When was the last time you did an update?

Your QSI reports MX-23.4_fluxbox_x64 and we are at MX-23.5_fluxbox_x64.
Also your kernel version is showing 6.1.0-26 and we are at 6.1.0-30.
I think the information relates to the live environment and not the static one, but I update it on a semi regular basis
The date on that shows January 21 2024.

Code: Select all

Desktop: Fluxbox v: 1.3.7 info: tint2 vt: 7 dm: LightDM v: 1.26.0 Distro: MX-23.4_fluxbox_x64
    Libretto January 21 2024 base: Debian GNU/Linux 12 (bookworm)

Here's what my new 2 week old install shows. I've applied two big updates in that time.

Code: Select all

Desktop: Fluxbox v: 1.3.7 vt: 7 dm: LightDM v: 1.32.0 Distro: MX-23.5_fluxbox_x64 Libretto
    September 15 2024 base: Debian GNU/Linux 12 (bookworm)
This is my Fluxbox . There are many others like it, but this one is mine. My Fluxbox is my best friend. It is my life.
I must master it as I must master my life. Without me, my Fluxbox is useless. Without my Fluxbox, I am useless.

Post Reply

Return to “MX Fluxbox Official Release”