Page 1 of 1

Actualizar a Linux 5.15.193 me trajo unos problemas

Posted: 5. Oct 2025, 19:10
by inukaze
Hola muy buenas, ayer actualice los paquetes de la distro desde la version 5.15.188
Ahora tengo los siguientes problemas

1 - No inicia el dispositivo de red eth0

2 - No puedo compilar nvidia-legacy390 con su compatibilidad de 32 Bits

3 - Si intento usar Vesa para video en modo generico, al ingresar al modo grafico dejan de funcionar el teclado y el raton.

Se me hace muy extraño que esto pase en Slackware y/o sus derivados, normalmente no hay problemas con las interfaces de red, pero tuve que usar un Pendrive con unas distros que tengo en vivo para casos como estos ( Suele pasarme frecuentemente con otras distros como : ArchLinux, Ubuntu, Fedora, OpenSUSE, etc . . . )

Bueno voy a ver si puedo recuperar el linux 5.15.188 que todo estaba funcionando perfectamente.

Re: Actualizar a Linux 5.15.193 me trajo unos problemas

Posted: 5. Oct 2025, 20:49
by inukaze
Archivo xorg.conf autogenerado :

Code: Select all

# File generated by xf86config.

#
# Copyright (c) 1999 by The XFree86 Project, Inc.
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
# 
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
# 
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
# THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
# 
# Except as contained in this notice, the name of the XFree86 Project shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from the
# XFree86 Project.
#

# **********************************************************************
# Refer to the XF86Config(4/5) man page for details about the format of 
# this file.
# **********************************************************************

# NOTE:  This is a NEW IMPROVED version of XF86Config-fbdev that uses the vesa
# driver instead of the fbdev driver.  Thanks to Kenneth Fanyo who pointed
# this out to me. :)

# This XF86Config file is designed for use with the VESA framebuffer.
# This generic interface should work with nearly all video cards
# (although not every card will support every resolution).

# With the new driver, it should no longer be required to have frame buffer
# support in the kernel, or to run it on the console.
#
# Enjoy! :)
# -- volkerdi@slackware.com
#

# **********************************************************************
# Module section -- this  section  is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"

# This loads the DBE extension module.

    Load        "dbe"  	# Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
    SubSection  "extmod"
      Option    "omit xfree86-dga"   # don't initialise the DGA extension
    EndSubSection

# This loads the font modules
    Load        "type1"
    Load        "freetype"
    #Load        "speedo"

# This loads the GLX module
    Load       "glx"

EndSection

# **********************************************************************
# Files section.  This allows default font and rgb paths to be set
# **********************************************************************

Section "Files"

# The location of the RGB database.  Note, this is the name of the
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.

    RgbPath	"/usr/share/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
# 
# If you don't have a floating point coprocessor and emacs, Mosaic or other
# programs take long to start up, try moving the Type1 and Speedo directory
# to the end of this list (or comment them out).
# 

    FontPath   "/usr/share/fonts/local/"
    FontPath   "/usr/share/fonts/misc/"
    FontPath   "/usr/share/fonts/OTF/"
    FontPath   "/usr/share/fonts/TTF/"
    FontPath   "/usr/share/fonts/Type1/"
    FontPath   "/usr/share/fonts/CID/"
    FontPath   "/usr/share/fonts/Speedo/"
    FontPath   "/usr/share/fonts/75dpi/:unscaled"
    FontPath   "/usr/share/fonts/100dpi/:unscaled"
    FontPath   "/usr/share/fonts/75dpi/"
    FontPath   "/usr/share/fonts/100dpi/"
    FontPath   "/usr/share/fonts/cyrillic/"

# ModulePath can be used to set a search path for the X server modules.
# The default path is shown here.

#    ModulePath "/usr/lib/xorg/modules"

EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

# Uncomment this to cause a core dump at the spot where a signal is
# received.  This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging

#    Option     "NoTrapSignals"

# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12).  This allows clients to receive these key
# events.

#    Option     "DontVTSwitch"

# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.

#    Option     "DontZap"

# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences.  This allows clients to receive these key events.

#    Option     "DontZoom"

# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.

#    Option     "DisableVidModeExtension"

# Uncomment this to enable the use of a non-local xvidtune client.

#    Option     "AllowNonLocalXvidtune"

# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.

#    Option     "DisableModInDev"

# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).

#    Option     "AllowNonLocalModInDev"

# Set the basic blanking screen saver timeout.

#    Option      "blank time"    "10"    # 10 minutes

# Set the DPMS timeouts.  These are set here because they are global
# rather than screen-specific.  These settings alone don't enable DPMS.
# It is enabled per-screen (or per-monitor), and even then only when
# the driver supports it.

#    Option      "standby time"  "20"
#    Option      "suspend time"  "30"
#    Option      "off time"      "60"

# On some platform the server needs to estimate the sizes of PCI
# memory and pio ranges. This is done by assuming that PCI ranges
# don't overlap. Some broken BIOSes tend to set ranges of inactive
# devices wrong. Here one can adjust how aggressive the assumptions
# should be. Default is 0.

# Option   "EstimateSizesAggresively" "0"

EndSection

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

    Identifier	"Keyboard1"
    Driver	"kbd"
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.

#    Option     "Protocol"      "Xqueue"

# Set the keyboard auto repeat parameters.  Not all platforms implement
# this.

#    Option     "AutoRepeat"    "500 5"

# Specifiy which keyboard LEDs can be user-controlled (eg, with xset(1)).

#    Option     "Xleds" "1 2 3"

# To disable the XKEYBOARD extension, uncomment XkbDisable.

#    Option     "XkbDisable"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a European
# keyboard, you will probably want to use one of:
#
#    Option     "XkbModel"      "pc102"
#    Option     "XkbModel"      "pc105"
#
# If you have a Microsoft Natural keyboard, you can use:
#
#    Option     "XkbModel"      "microsoft"
#
# If you have a US "windows" keyboard you will want:
#
#    Option     "XkbModel"      "pc104"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#
#    Option     "XkbLayout"     "de"
#
# or:
#
#    Option     "XkbLayout"     "de"
#    Option     "XkbVariant"    "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#
#    Option     "XkbOptions"    "ctrl:swapcaps"


# These are the default XKB settings for X.Org
#
#    Option     "XkbRules"      "xorg"
#    Option     "XkbModel"      "pc105"
#    Option     "XkbLayout"     "us"
#    Option     "XkbVariant"    ""
#    Option     "XkbOptions"    ""

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

    Identifier	"Mouse1"
    Driver	"mouse"

# On platforms where PnP mouse detection is supported the following
# protocol setting can be used when using a newer PnP mouse:

#    Option     "Protocol"      "Auto"

# The available mouse protocols types that you can set below are:
#    Auto BusMouse GlidePoint GlidePointPS/2 IntelliMouse IMPS/2
#    Logitech Microsoft MMHitTab MMSeries Mouseman MouseManPlusPS/2
#    MouseSystems NetMousePS/2 NetScrollPS/2 OSMouse PS/2 SysMouse
#    ThinkingMouse ThinkingMousePS/2 Xqueue
    Option "Protocol"    "PS/2"

# The mouse device.  The device is normally set to /dev/mouse,
# which is usually a symbolic link to the real device.

    Option "Device"      "/dev/mouse"
#   Option "Device"      "/dev/psaux"
#   Option "Device"      "/dev/ttyS0"
#   Option "Device"      "/dev/ttyS1"

# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.

#    Option "Protocol"	"Xqueue"

# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.

#    Option "BaudRate"		"9600"
#    Option "SampleRate"	"150"

# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)

#    Option "Emulate3Buttons"
#    Option "Emulate3Timeout"    "50"

# ChordMiddle is an option for some 3-button Logitech mice

#    Option "ChordMiddle"

EndSection

# Some examples of extended input devices

# Section "InputDevice"
#    Identifier "spaceball"
#    Driver     "magellan"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "spaceball2"
#    Driver     "spaceorb"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen0"
#    Driver     "microtouch"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "1412"
#    Option     "MaxX"          "15184"
#    Option     "MinY"          "15372"
#    Option     "MaxY"          "1230"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen1"
#    Driver     "elo2300"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "231"
#    Option     "MaxX"          "3868"
#    Option     "MinY"          "3858"
#    Option     "MaxY"          "272"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonThreshold"       "17"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection

# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"

    Identifier  "My Monitor"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    HorizSync   31.5 - 50.0

#    HorizSync	30-64         # multisync
#    HorizSync	31.5, 35.2    # multiple fixed sync frequencies
#    HorizSync	15-25, 30-50  # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    VertRefresh 40-90

EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

Section "Device"
    Identifier  "VESA Framebuffer"
    Driver      "vesa"
    #VideoRam    4096
    # Insert Clocks lines here if appropriate
EndSection

# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present.  Each describes
# the configuration of a single screen.  A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
    Identifier  "Screen 1"
    Device      "VESA Framebuffer"
    Monitor     "My Monitor"

# If your card can handle it, a higher default color depth (like 24 or 32)
# is highly recommended.

#   DefaultDepth 8
#   DefaultDepth 16
   DefaultDepth 24
#   DefaultDepth 32

# "1024x768" is also a conservative usable default resolution.  If you
# have a better monitor, feel free to try resolutions such as
# "1152x864", "1280x1024", "1600x1200", and "1800x1400" (or whatever your
# card/monitor can produce)

    Subsection "Display"
        Depth       8
        Modes "1024x768" "800x600" "640x480"
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes "1024x768" "800x600" "640x480"
    EndSubsection
    Subsection "Display"
        Depth       24
        Modes "1024x768" "800x600" "640x480"
    EndSubsection
    Subsection "Display"
        Depth       32
        Modes "1024x768" "800x600" "640x480"
    EndSubsection

EndSection

# **********************************************************************
# ServerLayout sections.
# **********************************************************************

# Any number of ServerLayout sections may be present.  Each describes
# the way multiple screens are organised.  A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option.  In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section "ServerLayout"

# The Identifier line must be present
    Identifier  "Simple Layout"

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens.  The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen.  In this example, screen 2 is located to the
# right of screen 1.

    Screen "Screen 1"

# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used.  Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".

    InputDevice "Mouse1" "CorePointer"
    InputDevice "Keyboard1" "CoreKeyboard"

EndSection

Re: Actualizar a Linux 5.15.193 me trajo unos problemas

Posted: 5. Oct 2025, 20:50
by inukaze
Archivo xorg.conf escrito por mi mismo, y el raton y el teclado siguen sin funcionar al ingresar al entorno grafico.

Code: Select all

Section "ServerLayout"
    Identifier     "Default Layout"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "0"
EndSection

Section "Module"
    Load           "vbe"
    Load           "bitmap"
    Load           "bitmap" # bitmap-fonts
    Load           "int10"
    Load           "type1"
    Load           "freetype"
    Load           "synaptics"
EndSection

Section "ServerFlags"
    Option         "DontZap" "False"
    Option         "Xinerama" "0"
EndSection

Section "InputDevice"
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "InputDevice"
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputClass"
    Identifier         "Keyboard Defaults"
    MatchIsKeyboard    "yes"
    Option         "XkbOptions" "terminate:ctrl_alt_bksp"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Toshiba"
    ModelName      "Toshiba Matsushita Display Technology Co., Ltd LCD-MONITOR"
    HorizSync       30.0 - 82.0
    VertRefresh     56.0 - 76.0
    Option         "DPMS" "TRUE"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "vesa"
    VendorName     "VESA"
    BoardName      "VESA FrameBuffer"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "AddARGBGLXVisuals" "True"
    Option         "DPMS" "True"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Extensions"
    Option         "RandR" "Enable"
    Option         "RENDER" "Enable"
    Option         "Composite" "Enable"
EndSection

Re: Actualizar a Linux 5.15.193 me trajo unos problemas

Posted: 5. Oct 2025, 22:45
by inukaze
Curiosamente ya no funciona tampoco el eth0 en Linux 5.15.188 ni en su version Huge, algo extraño sucedio. bueno voy a intentar ingresar via chroot y reinstalar los paquetes para dispositivos de red que si utilizo, y los de entrada.

Primero a ver que tengo, dese Porteus USB (Modo En Vivo)

Code: Select all

sudo su
Contraseña: 

root@porteus:/home/guest# blkid | grep -v loop | grep -v "INU05" | grep ext | sort
/dev/sda2: LABEL="Salix-Inicio" UUID="bad7fbb0-4d90-4489-a910-2959c13e0a27" BLOCK_SIZE="4096" TYPE="ext2" PARTUUID="4b1ee4bc-02"
/dev/sda3: LABEL="Salix-Raiz" UUID="f456729f-bb27-4ff7-a21c-9069a857d99a" BLOCK_SIZE="4096" TYPE="ext3" PARTUUID="4b1ee4bc-03"
/dev/sda4: LABEL="Salix-Hogar" UUID="bef6c71c-ff3f-461e-895c-49be727933aa" BLOCK_SIZE="4096" TYPE="ext3" PARTUUID="4b1ee4bc-04"

Bueno procedere a desmontar las unidades en uso :

Code: Select all

umount /dev/sda{2,3,4}
Luego ejecuto mi guion personalizado "inufsck" ( Todavia me falta hacer que autodesmonte las unidades, exceptuando unidades tipo swap, por ejemplo )

Contenido actual de mi guion personalizado inufsck

Code: Select all

#!/usr/bin/env bash

# IDEA :	Usar algun comando para obtener la informacion de : 
#				* Disco#Particion		ejemplo :	sda2
#				* Sistema de archivos	ejemplo	:	ext3
#				* Punto de Montaje		ejemplo	:	/mnt/sda2
#
# Podria ser con el siguiente comando :
# BASE :
# findmnt -o TARGET,SOURCE,FSTYPE | grep -v loop | grep -v proc 
#
# LARGO :
# findmnt -o TARGET,SOURCE,FSTYPE | grep -v "loop" | grep -v "vfsd-fuse" | grep -v "cgroup" | grep -v "sysfs" | grep -v "devpts" | grep -v "tmpfs" | grep -v "proc" | grep -v "devtmpfs" | grep -v "none" | grep -v "aufs" | grep -v "fusectl" | grep -v "live" | grep -v "fuseblk"
#
# Reducido :
# findmnt -o TARGET,SOURCE,FSTYPE | egrep -v "loop|vfsd-fuse|cgroup|sysfs|devpts|tmpfs|proc|devtmpfs|none|aufs|fusectl|live|fuseblk"


# Con el REDUCIDO obtengo : 
#findmnt -o TARGET,SOURCE,FSTYPE | egrep -v "loop|vfsd-fuse|cgroup|sysfs|devpts|tmpfs|proc|devtmpfs|none|aufs|fusectl|live|fuseblk"
#Salida :
#TARGET                                                        SOURCE                                       FSTYPE
#├─/mnt/sda3                                                   /dev/sda3                                    ext2
#├─/mnt/sda6                                                   /dev/sda6                                    ext4
#├─/mnt/sdf1                                                   /dev/sdf1                                    vfat
#├─/mnt/sdf2                                                   /dev/sdf2                                    ext2
#├─/mnt/sdf3                                                   /dev/sdf3

# Ahora debo ver como hago para que este guion, auto desmonte, los puntos de montaje para luego proceder con el fsck
# Tambien debo hacer que se excluyan las particiones que sean ntfs, vfat, y swap.


# IDEA : Usar el siguiente comando :
# findmnt -o TARGET,SOURCE,FSTYPE | egrep -v "loop|vfsd-fuse|cgroup|sysfs|devpts|tmpfs|proc|devtmpfs|none|aufs|fusectl|live|fuseblk|vfat|exfat|ntfs" | awk '{ print $2}' | grep -v ^SOURCE

#Salida :
# /dev/sdg2
# /dev/sdg3

# Obtener todos los enlaces simbólicos en /dev/disk/by-uuid
# excepto los UUID de las particiones del pendrive :
# 'a9cec8d3-2770-4cb9-acbb-55479a5370f8'
# 'dfcc359c-b579-42c5-a72d-def58621545e'
# '3AD2-D4DA'
#
# Agregadas otras particiones de diversos tipos conocidas
# para evitar pasarles el fsck ya que es inutil.
#
# '2024-05-19-14-15-33-56'					->	#Squashfs (Contenido la iso montada en uso)
# 'a9cec8d3-2770-4cb9-acbb-55479a5370f8'	->	#Intercambio
# 'c698fec1-1da5-4764-b625-0c3c9e2e3ecf'	->	#Intercambio
# '24045D0035428EFF'						->	#NTFS		( Solo chkdsk de windows puede realmente reparar esto )
#
# Usar NUL como separador de espacios funciona con
# cualquier nombre de archivo, incluidos los molestos
# caracteres como espacios o metacaracteres.
mapfile -d '' -t UUID < <(find /dev/disk/by-uuid/ -type l \
! -name '*a9cec8d3-2770-4cb9-acbb-55479a5370f8*' \
! -name '*2024-05-19-14-15-33-56*' \
! -name '*24045D0035428EFF*' \
! -name '*8bfb2d02-7390-42dd-9a72-7d7b750a63f8*' \
! -name '*dfcc359c-b579-42c5-a72d-def58621545e*' \
! -name '*3AD2-D4DA*' \
! -name '*40BD558A56A2E04C*' \
! -name '*8bfb2d02-7390-42dd-9a72-7d7b750a63f8*' \
! -name '*c698fec1-1da5-4764-b625-0c3c9e2e3ecf*' \
-print0)

# Entrar en bucle con esos enlaces simbólicos
for f in "${UUID[@]}" ; do
  # UUID sin ruta
  IDUU="${f/*\//}"

  # obtener la ruta real de los enlaces simbólicos
  rp="$(realpath "$f")"

  # Omitir aquellos que no son dispositivos de bloques
  [ -b "$rp" ] || continue

  # Ahora hacer lo que sea que necesite hacer con la variable "$rp"
  # Recuerda siempre usar doble-comilla para expandir las variables
  # 
  # Usar siempre printf en lugar de echo debido a que
  # echo no es confiable y se rompe fácilmente.
  # 
#ORIGINAL#  printf "\nExaminando: %s (%s)\n" "$IDDU" "$rp"
#  printf "\nExaminando: %s (%s)\n" "$IDDU" "$rp"
  printf "\nExaminando---->%s%s\n" "$IDDU" "$rp"
  if fsck -fy "$rp" ; then
     if ! fsck -fy "$rp" ; then
       printf "%s\n" "Error en la segunda vez de fsck en $IDUU ($rp) Fallo." >&2
     fi
  else
    printf "%s\n" "Error: en la primera vez de fsck en $IDUU ($rp) fallo." >&2
  fi
done
Salida de inufsck al finalizar :
Examinando---->/dev/sda4
fsck de util-linux 2.37.4
e2fsck 1.46.5 (30-Dec-2021)
Paso 1: Verificando nodos-i, bloques y tamaños
Paso 2: Verificando la estructura de directorios
Paso 3: Revisando la conectividad de directorios
Paso 4: Revisando las cuentas de referencia
Paso 5: Revisando el resumen de información de grupos
Salix-Hogar: 630096/8683520 ficheros (35.9% no contiguos), 32455161/34726144 bloques
fsck de util-linux 2.37.4
e2fsck 1.46.5 (30-Dec-2021)
Paso 1: Verificando nodos-i, bloques y tamaños
Paso 2: Verificando la estructura de directorios
Paso 3: Revisando la conectividad de directorios
Paso 4: Revisando las cuentas de referencia
Paso 5: Revisando el resumen de información de grupos
Salix-Hogar: 630096/8683520 ficheros (35.9% no contiguos), 32455161/34726144 bloques

Examinando---->/dev/sda2
fsck de util-linux 2.37.4
e2fsck 1.46.5 (30-Dec-2021)
Paso 1: Verificando nodos-i, bloques y tamaños
Paso 2: Verificando la estructura de directorios
Paso 3: Revisando la conectividad de directorios
Paso 4: Revisando las cuentas de referencia
Paso 5: Revisando el resumen de información de grupos
Salix-Inicio: 1207/131072 ficheros (4.4% no contiguos), 79255/524288 bloques
fsck de util-linux 2.37.4
e2fsck 1.46.5 (30-Dec-2021)
Paso 1: Verificando nodos-i, bloques y tamaños
Paso 2: Verificando la estructura de directorios
Paso 3: Revisando la conectividad de directorios
Paso 4: Revisando las cuentas de referencia
Paso 5: Revisando el resumen de información de grupos
Salix-Inicio: 1207/131072 ficheros (4.4% no contiguos), 79255/524288 bloques

Examinando---->/dev/sda3
fsck de util-linux 2.37.4
e2fsck 1.46.5 (30-Dec-2021)
Paso 1: Verificando nodos-i, bloques y tamaños
Paso 2: Verificando la estructura de directorios
Paso 3: Revisando la conectividad de directorios
Paso 4: Revisando las cuentas de referencia
Paso 5: Revisando el resumen de información de grupos
Salix-Raiz: 1141490/6561792 ficheros (6.5% no contiguos), 15831130/26215424 bloques
fsck de util-linux 2.37.4
e2fsck 1.46.5 (30-Dec-2021)
Paso 1: Verificando nodos-i, bloques y tamaños
Paso 2: Verificando la estructura de directorios
Paso 3: Revisando la conectividad de directorios
Paso 4: Revisando las cuentas de referencia
Paso 5: Revisando el resumen de información de grupos
Salix-Raiz: 1141490/6561792 ficheros (6.5% no contiguos), 15831130/26215424 bloques
Ahora si a crear directorios para montar la distro Salix que tengo en uso como distro principal actualmente :

Code: Select all

mkdir -p /media/Salix/{boot,home}
Verifico las particiones nuevamente para estar seguro

Code: Select all

blkid | grep -v loop | grep -v "INU05" | grep ext | sort
/dev/sda2: LABEL="Salix-Inicio" UUID="bad7fbb0-4d90-4489-a910-2959c13e0a27" BLOCK_SIZE="4096" TYPE="ext2" PARTUUID="4b1ee4bc-02"
/dev/sda3: LABEL="Salix-Raiz" UUID="f456729f-bb27-4ff7-a21c-9069a857d99a" SEC_TYPE="ext2" BLOCK_SIZE="4096" TYPE="ext3" PARTUUID="4b1ee4bc-03"
/dev/sda4: LABEL="Salix-Hogar" UUID="bef6c71c-ff3f-461e-895c-49be727933aa" SEC_TYPE="ext2" BLOCK_SIZE="4096" TYPE="ext3" PARTUUID="4b1ee4bc-04"
Bueno ahora procedo a montar las particiones y otros :

Code: Select all

mount /dev/sda3 /media/Salix
mount /dev/sda2 /media/Salix/boot
mount /dev/sda4 /media/Salix/home
mount --rbind /dev/pts /media/Salix/dev/pts
mount --rbind /dev /media/Salix/dev
mount --rbind /proc /media/Salix/proc
Ahora si le hago chroot (Cambiar de Raiz para cambiar al sistema de archivos del sistema operativo de las particiones)

Code: Select all

chroot /media/Salix
Ahora tengo que buscar los paquetes pertinentes a ver si asi logro solventar que eth0 no esta funcionando en las versiones de Linux que puedo iniciar es decir 5.15.188 , Huge ( 5.15.188 ) , 5.15.193, Huge ( 5.15.193 )
Ya que esta muy extraño, ya que intente configurarlo mediante netconfig y nada que se activa la interfaz de red, pero si inicio a traves de una distro en vivo, el dispositivo de red funciona correctamente que es lo que estoy haciendo para escribir esto.

Ejecutar slapt-get --update

Code: Select all

slapt-get --update
Recuperando los datos del paquete [http://slackware.uk/salix/x86_64/slackware-15.0/]...No se pudo descargar: Could not resolve hostname
Recuperando los datos del paquete [http://slackware.uk/salix/x86_64/slackware-15.0/extra/]...No se pudo descargar: Could not resolve hostname
Recuperando los datos del paquete [http://slackware.uk/salix/x86_64/15.0/]...No se pudo descargar: Could not resolve hostname
Recuperando los datos del paquete [http://slackware.uk/salix/x86_64/extra-15.0/]... No se pudo descargar: Could not resolve hostname
Recuperando los datos del paquete [https://bear.alienbase.nl/mirrors/people/alien/multilib/15.0/]...No se pudo descargar: Could not resolve hostname
Las fuentes fallaron al descargar, corregir las fuentes y ejecutar nuevamente --update
Siempre se me olvida que no puedo usar un chroot simple si quiero trabajar con la conexion a internet.
asi que basado en un guion que hice hace un tiempo -> https://unix.stackexchange.com/question ... dio-nv-glx <-
Voy a extraer una parte para adaptarlo

primero salir del chroot

Code: Select all

exit
desmontar lo que estaba para comenzar otra vez

Code: Select all

umount /media/Salix/home
umount /media/Salix/boot
umount -l /media/Salix/dev/pts
umount -l /media/Salix/dev
umount -l /media/Salix/proc
umount -l /media/Salix/sys
umount -l /media/Salix
Ahora si desde el principio montar las particiones para un chroot y trabajar con internet :

Code: Select all

OBJETIVO="/media/Salix"
mount /dev/sda3				"$OBJETIVO"
mount /dev/sda2				"$OBJETIVO/boot"
mount /dev/sda4				"$OBJETIVO/home"
mount --rbind /proc			"$OBJETIVO/proc"
mount --make-rslave			"$OBJETIVO/proc"
mount --rbind /sys			"$OBJETIVO/sys"
mount --make-rslave			"$OBJETIVO/sys"
mount --rbind /dev			"$OBJETIVO/dev"
mount --make-rslave			"$OBJETIVO/dev"
mount --rbind /run			"$OBJETIVO/run"
mount --make-rslave			"$OBJETIVO/run"
mount --rbind /tmp			"$OBJETIVO/tmp"
mount --make-rslave			"$OBJETIVO/tmp"
mount --bind /etc/fstab			"$OBJETIVO/etc/fstab"
mount --bind /etc/hostname		"$OBJETIVO/etc/hostname" 2> /dev/null
mount --bind /etc/HOSTNAME		"$OBJETIVO/etc/HOSTNAME" 2> /dev/null
mount --bind /etc/hosts			"$OBJETIVO/etc/hosts"
mount --bind /etc/resolv.conf		"$OBJETIVO/etc/resolv.conf"
chroot "$OBJETIVO"
root[/]# slapt-get --update
Recuperando los datos del paquete [http://slackware.uk/salix/x86_64/slackware-15.0/]...Hecho
Recuperando la lista de parches [http://slackware.uk/salix/x86_64/slackware-15.0/]...Hecho
Recuperando la lista de checksum [http://slackware.uk/salix/x86_64/slackware-15.0/]...Cacheado
Recuperando la firma de checksum [http://slackware.uk/salix/x86_64/slackware-15.0/]...Cacheado
Verificando la firma de checksum [http://slackware.uk/salix/x86_64/slackware-15.0/]...No hay clave para verificar
Recuperando ChangeLog.txt [http://slackware.uk/salix/x86_64/slackware-15.0/]...Cacheado
Leyendo listas de paquetes...Hecho
Recuperando los datos del paquete [http://slackware.uk/salix/x86_64/slackware-15.0/extra/]...Hecho
Recuperando la lista de parches [http://slackware.uk/salix/x86_64/slackware-15.0/extra/]...Hecho
Recuperando la lista de checksum [http://slackware.uk/salix/x86_64/slackware-15.0/extra/]...Cacheado
Recuperando la firma de checksum [http://slackware.uk/salix/x86_64/slackware-15.0/extra/]...Cacheado
Verificando la firma de checksum [http://slackware.uk/salix/x86_64/slackware-15.0/extra/]...No hay clave para verificar
Recuperando ChangeLog.txt [http://slackware.uk/salix/x86_64/slackware-15.0/extra/]...Hecho
Leyendo listas de paquetes...Hecho
Recuperando los datos del paquete [http://slackware.uk/salix/x86_64/15.0/]...Cacheado
Recuperando la lista de parches [http://slackware.uk/salix/x86_64/15.0/]...Hecho
Recuperando la lista de checksum [http://slackware.uk/salix/x86_64/15.0/]...Cacheado
Recuperando la firma de checksum [http://slackware.uk/salix/x86_64/15.0/]...Cacheado
Verificando la firma de checksum [http://slackware.uk/salix/x86_64/15.0/]...No hay clave para verificar
Recuperando ChangeLog.txt [http://slackware.uk/salix/x86_64/15.0/]...Cacheado
Leyendo listas de paquetes...Hecho
Recuperando los datos del paquete [http://slackware.uk/salix/x86_64/extra-15.0/]...Cacheado
Recuperando la lista de parches [http://slackware.uk/salix/x86_64/extra-15.0/]... 0Hecho
Recuperando la lista de checksum [http://slackware.uk/salix/x86_64/extra-15.0/]...Cacheado
Recuperando la firma de checksum [http://slackware.uk/salix/x86_64/extra-15.0/]...Cacheado
Verificando la firma de checksum [http://slackware.uk/salix/x86_64/extra-15.0/]...No hay clave para verificar
Recuperando ChangeLog.txt [http://slackware.uk/salix/x86_64/extra-15.0/]...Cacheado
Leyendo listas de paquetes...Hecho
Recuperando los datos del paquete [https://bear.alienbase.nl/mirrors/peopl ... ilib/15.0/]...Cacheado
Recuperando la lista de parches [https://bear.alienbase.nl/mirrors/peopl ... ilib/15.0/]...Hecho
Recuperando la lista de checksum [https://bear.alienbase.nl/mirrors/peopl ... ilib/15.0/]...Cacheado
Recuperando la firma de checksum [https://bear.alienbase.nl/mirrors/peopl ... ilib/15.0/]...Cacheado
Verificando la firma de checksum [https://bear.alienbase.nl/mirrors/peopl ... ilib/15.0/]...No hay clave para verificar
Recuperando ChangeLog.txt [https://bear.alienbase.nl/mirrors/peopl ... ilib/15.0/]...Hecho
Leyendo listas de paquetes...Hecho
Listo ahora si puedo trabajar con internet para reinstalar los paquetes del sistema.

Re: Actualizar a Linux 5.15.193 me trajo unos problemas

Posted: 5. Oct 2025, 23:41
by inukaze
Bueno basado en mi propio documento de instalacion de Slackware, que deje una duda con unas macros en su foro -> https://ask.libreoffice.org/t/macros-pa ... nes/127437

De ese archivo saque la lista de paquetes, para una instalacion minima de Slackware(64) 15.0 con acceso a internet, con unos pocos extras que se me hacen utiles como :

joe -> editor de texto
mc -> gestor de archivos


Utilice el siguiente comando :

Code: Select all

slapt-get --install --reinstall -y \
aaa_base \
aaa_glibc-solibs \
aaa_libraries \
aaa_terminfo \
acl \
attr \
bash \
bin \
bzip2 \
coreutils \
cracklib \
dbus \
dcron \
devs \
dialog \
e2fsprogs \
elogind \
etc \
eudev \
file \
findutils \
gawk \
glibc-zoneinfo \
grep \
grub \
gzip \
hostname \
kbd \
kernel-firmware \
kernel-huge \
kernel-modules \
kmod \
less \
libgudev \
libpwquality \
lilo \
lzlib \
mkinitrd \
mlocate \
openssl-solibs \
nvi \
os-prober \
pam \
pkgtools \
procps-ng \
sed \
shadow \
sharutils \
sysklogd \
sysvinit \
sysvinit-scripts \
tar \
util-linux \
which \
xz \
diffstat \
diffutils \
groff \
joe \
man-db \
man-pages \
mc \
slackpkg \
sqlite \
terminus-font \
perl \
brotli \
glib2 \
glibc \
glibc-i18n \
glibc-profile \
icu4c \
libseccomp \
libssh \
libssh2 \
libunistring \
mozilla-nss \
ncurses \
NetworkManager \
ca-certificates \
cyrus-sasl \
dhcp \
dhcpcd \
gnupg \
gnutls \
gpgme \
iproute2 \
iputils \
libmnl \
libndp \
net-tools \
network-scripts \
nghttp2 \
openresolv \
openssh \
openssl \
p11-kit \
wget
Luego de que finalice la descarga y reinstalacion de paquetes probare a ver si funciono.

Re: Actualizar a Linux 5.15.193 me trajo unos problemas

Posted: 6. Oct 2025, 00:59
by inukaze
Bueno no funciono. no tengo idea de porque ahora no tengo ningun dispositivo de red, y tampoco tengo idea de porque al utilizar vesa, es como si no tuviera ni teclado ni raton.

¿ Alguna idea para solventar eso ?

Re: Actualizar a Linux 5.15.193 me trajo unos problemas

Posted: 6. Oct 2025, 03:21
by inukaze
Degrade a las versiones 5.15.187 de paquetes como :

kernel-headers
kernel-huge
kernel-modules
kernel-source

y reinstale :
kernel-firmware
xf86-video-vesa
xf86-input-libinput
xf86-input-mouse
xf86-input-keyboard
xorg-server
xf86-input-evdev

Luego actualice a la version 5.15.188 de esos paquetes y ahora mismo todo esta funcionando correctamente, el viernes actualizo a la version 5.15.193 probablemente kernel-modules sufrio alguna corrupcion de datos cuando se me instalo o algo porque estaba muy extraño que no me diera ninguna interfaz de red