Damn Small Linux Forums

Pages: 1 2 3 4 5 6 7

May we have finally caught the rat?

"Some pkgs could not be installed... impossible situation... or... unstable distro...
The following pkgs have unmet deps:
libeudev1: Breaks: libudev1 (< 1:3.2.9 +devuan4)
Error, pkgproblemresolver::Resolve generated breaks this may be caused by the ld pkgs. "

So, how can I fix it? Thanks again

EDIT: Check-that.

Re-reading everything again...

sudo dpkg --configure -a
(answer yes to all)
sudo apt-get install -f

sorry if I'm too late with the edit.

That doesn't work at all.
No reply.

No reply is a good thing in this case! You were at a spooky place. Now, for good measure,

sudo apt-get autoclean
sudo apt-get autoremove

then reboot and try the whole X config routine again. And tell us if you disable the AutoAddDevices False thing or not. Thanks for hanging in there.

So, dpkg and autoclean give no replay, autoremove gives "0 removed" and Xorg errors are the same as before: no /dev/dri created.

Did you try the ServerFlag? Option "AutoAddDevices" "False"

Still reading. I see people with every sort of device and this problem.

By seeing a Mint+Cinnamon user have the card0 problem (and resolve it), it implies that it's not some vestige of being systemd-free or Devuan-based.

EDIT: Also just started a thread at the mothership. inquiry 1: Was md5sum done on iso prior to all this--do we know we had a good one?

If I've well understood, the dri/card0 is created loading the right driver.
That happens during the Xorg -configure process, that's what I've done till now.
Unless I 'm mistaken, it's has no sense to use a config file if the card0 file is unexisting.
The above error mentions ld, that's involved in the card0 file creation.
Shouldn't we focus on it?
Please correct me. Thanks

You may be right. Hey--I'm no expert, just trying to help and learn this stuff along with everyone else. When I saw the same string

Error, pkgproblemresolver::Resolve generated breaks this may be caused by the ...

elsewhere, it was "...held files" and not "ld files". I just assumed that the ld from yours was not the loader (ld) but a copy-paste error. I understand your point -- feel free to go after ld.

I do not have the answers to those sequencing questions. My sense is that card0 under dri is for accelerated graphics (and your pref to use the proper siliconmotion driver). I am simply trying to exhaust the 2nd option that X was telling us to do--you already reinstalled udev (which should've reconfigured it). Perhaps if we do not autoprobe with X, udev does not fail trying to make a card0 and we communicate with onboard framebuffer vga and not accelerated (DRI) rendering --that's why I said to try to disable the auto. HOWEVER -- now that I go look for the framebuffer device (/dev/fb0), it's not there either:

Code:
[    66.084] (II) Loading sub module "fbdevhw"

[    66.084] (II) LoadModule: "fbdevhw"

[    66.085] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so

[    66.091] (II) Module fbdevhw: vendor="X.Org Foundation"

[    66.091]     compiled for 1.21.1.7, module version = 0.0.2

[    66.091]     ABI class: X.Org Video Driver, version 25.2

[    66.092] (EE) open /dev/fb0: No such file or directory

The thing that's actually working on your box is vesa and that's what sees the 4M of vram. Sooo, vesa doesn't need/use dri. My thinking was to find an X configuration that fit inside 4M and worked with vesa--just to get ANYthing going for you. If we could hatch you a config file with a low-enough pixel-depth to fit inside what's detected, the failures would stop. The problem is that it would not take maximum advantage of your hardware.

It was suggested to try the older 4.19 kernel--perhaps you can try that in the interim. If that "just works", we'll have another set of data. This seems to be in the main antix repository:
linux-4.19.276-antix.2-486-smp
and maybe the headers if you want to build anything again:
linux-headers-4.19.276-antix.2-486-smp

If that kernel gets all the devices populated right...there's the easy answer.

What I know is that you have some sort of display right now and it's using vesa graphics. When I look in the old file from the link in Yan's earlier post, it contains only vesa and fbdev. On your laptop, X already has a configuration, it's just not a runnable one. (Auto-)configuration is to make the process brainless, but if you _know_ what config it will run on, you simply specify that and X will try to use it.

But you are right--the more I read, the more I see these failures all over the place on every possible flavor of distribution--and the solutions are all over the place, too.

Might be interesting to see if

sudo hwinfo --gfxcard

is different from lspci and different from vesa (and / or windows).

You give me a lot of food for thought. I'm learning a lot from you and am so grateful.

Now, I suspected to have messed my installation and today decided to repeat the whole process.

The truth, I'm usually lazy in doing checksum, I never do that.

But today I did it on my 64 bit PC and got a surprise:

Code:
bash-5.1$ md5sum -c dsl-2024.rc3.iso

md5sum: dsl-2024.rc3.iso: no properly formatted checksum lines found

I downloaded the iso image and the txt file again, one time via Firefox and two times via JDownloader, and got the same error.

Can the iso image be repaired on my side or it's your side task?

Anyway, you suggested to add AutoAddDevices "presumably only if the udev thing worked to create card0 and if the error still persists, otherwise this may be counter-productive".
Since card0 has never been created so far, I didn't add that option.

Here you are with the hwinfo output:

Code:
14: PCI 02.0: 0300 VGA compatible controller (VGA)

  [Created at pci.386]

  Unique ID: _Znp.0zLlW6F0KW4

  SysFS ID: /devices/pci0000:00/0000:00:02.0

  SysFS BusID: 0000:00:02.0

  Hardware Class: graphics card

  Model: "Silicon Motion SM910"

  Vendor: pci 0x126f "Silicon Motion, Inc."

  Device: pci 0x0910 "SM910"

  SubVendor: pci 0x126f "Silicon Motion, Inc."

  SubDevice: pci 0x0910 

  Revision: 0xb5

  Memory Range: 0xfd000000-0xfdffffff (rw,non-prefetchable)

  Memory Range: 0x000c0000-0x000dffff (rw,non-prefetchable,disabled)

  IRQ: 9 (340 events)

  I/O Ports: 0x3c0-0x3df (rw)

  Module Alias: "pci:v0000126Fd00000910sv0000126Fsd00000910bc03sc00i00"

  Driver Info #0:

    XFree86 v4 Server Module: siliconmotion

  Config Status: cfg=new, avail=yes, need=no, active=unknown

Primary display adapter: #14

And this is the old Red Hat 8 xf86config, ancestor of the xorg.conf file. It worked fine.

Code:
# 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.

# **********************************************************************

# **********************************************************************

# Module section -- this  section  is used to specify

# which dynamically loadable modules to load.

# **********************************************************************

#

# **********************************************************************

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

# **********************************************************************

# **********************************************************************

# Server flags section.

# **********************************************************************

# **********************************************************************

# Input devices

# **********************************************************************

# **********************************************************************

# Core keyboard's InputDevice section

# **********************************************************************

# **********************************************************************

# Core Pointer's InputDevice section

# **********************************************************************

# **********************************************************************

# Other input device sections 

# this is optional and is required only if you

# are using extended input devices.  This is for example only.  Refer

# to the XF86Config man page for a description of the options.

# **********************************************************************

#

# Section "InputDevice" 

#    Identifier  "Mouse2"

#    Driver      "mouse"

#    Option      "Protocol"      "MouseMan"

#    Option      "Device"        "/dev/mouse2"

# EndSection

#

# 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

# **********************************************************************

# Graphics device section

# **********************************************************************

# Any number of graphics device sections may be present

# Standard VGA Device:

# Device configured by xf86config:

# **********************************************************************

# 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.

# **********************************************************************

# 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

# 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.

# 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".

    Identifier     "Simple Layout"

    Screen         "Screen 1" 0 0

    InputDevice    "Mouse1" "CorePointer"

    InputDevice    "Keyboard1" "CoreKeyboard"

EndSection

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.

# 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).

# 

# The module search path.  The default path is shown here.

#    ModulePath "/usr/X11R6/lib/modules"

    RgbPath      "/usr/X11R6/lib/X11/rgb"

    FontPath     "/usr/X11R6/lib/X11/fonts/local/"

    FontPath     "/usr/X11R6/lib/X11/fonts/misc/"

    FontPath     "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"

    FontPath     "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"

    FontPath     "/usr/X11R6/lib/X11/fonts/Type1/"

    FontPath     "/usr/X11R6/lib/X11/fonts/Speedo/"

    FontPath     "/usr/X11R6/lib/X11/fonts/75dpi/"

    FontPath     "/usr/X11R6/lib/X11/fonts/100dpi/"

EndSection

Section "Module"

# This loads the DBE extension module.

# This loads the miscellaneous extensions module, and disables

# initialisation of the XFree86-DGA extension within that module.

# This loads the Type1 and FreeType font modules

#    Load       "glx"

    Load  "dbe"      # Double buffer extension

    SubSection "extmod"

        Option        "omit xfree86-dga"   # don't initialise the DGA extension

    EndSubSection

    Load  "type1"

    Load  "freetype"# This loads the GLX module

EndSection

Section "InputDevice"

# 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"

#    Option    "Xleds"      "1 2 3"

#    Option "LeftAlt"     "Meta"

#    Option "RightAlt"    "ModeShift"

# To customise the XKB settings to suit your keyboard, modify the

# lines below (which are the defaults).  For example, for a non-U.S.

# keyboard, you will probably want to use:

#    Option "XkbModel"    "pc102"

# If you have a US Microsoft Natural keyboard, you can use:

#    Option "XkbModel"    "microsoft"

#

# 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 XFree86

#    Option "XkbRules"    "xfree86"

#    Option "XkbModel"    "pc101"

#    Option "XkbLayout"   "us"

#    Option "XkbVariant"  ""

#    Option "XkbOptions"  ""

#    Option "XkbDisable"

    Identifier  "Keyboard1"

    Driver      "Keyboard"

    Option        "AutoRepeat" "500 30"# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))

    Option        "XkbRules" "xfree86"

    Option        "XkbModel" "pc101"

    Option        "XkbLayout" "it"

EndSection

Section "InputDevice"

# Identifier and driver

# 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)

    Identifier  "Mouse1"

    Driver      "mouse"

    Option        "Protocol" "PS/2"

    Option        "Device" "/dev/mouse"# When using XQUEUE, comment out the above two lines, and uncomment

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

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

#    Option "ChordMiddle"

EndSection

Section "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    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.

    Identifier   "LCD ASUS"

    ModelName    "Generic Laptop Display Panel 1024x768"

    HorizSync    31.5 - 57.5

    VertRefresh  50.0 - 70.0

EndSection

Section "Device"

# The chipset line is optional in most cases.  It can be used to override

# the driver's chipset detection, and should not normally be specified.

#    Chipset    "generic"

# The Driver line must be present.  When using run-time loadable driver

# modules, this line instructs the server to load the specified driver

# module.  Even when not using loadable driver modules, this line

# indicates which driver should interpret the information in this section.

# The BusID line is used to specify which of possibly multiple devices

# this section is intended for.  When this line isn't present, a device

# section can only match up with the primary video device.  For PCI

# devices a line like the following could be used.  This line should not

# normally be included unless there is more than one video device

# intalled.

#    BusID      "PCI:0:10:0"

#    VideoRam    256

#    Clocks    25.2 28.3

    Identifier  "Standard VGA"

    Driver      "vga"

    VendorName  "Unknown"

    BoardName   "Unknown"

EndSection

Section "Device"

    #VideoRam    4096

    # Insert Clocks lines here if appropriate

    Identifier  "LINX-E"

    Driver      "siliconmotion"

    BoardName   "Unknown video card"

    Option        "NoMTRR"

EndSection

Section "Screen"

    Identifier "Screen 1"

    Device     "LINX-E"

    Monitor    "LCD ASUS"

    DefaultDepth     16

    SubSection "Display"

        Depth     8

        Modes    "640x480" "800x600" "1024x768" "1280x1024"

    EndSubSection

    SubSection "Display"

        Depth     16

        Modes    "1024x768" "800x600" "640x480"

    EndSubSection

    SubSection "Display"

        Depth     24

        Modes    "640x480" "800x600" "1024x768" "1280x1024"

    EndSubSection

EndSection

OK thank you for all that and the kind words. Sorry for confusion.

The checksum is the biggest of deals (yer killing me man!) Smile

I think we all detected that the thing has been a little spooky and itching for a re-inst (gotta work on that, too)--it's good you shook it out. Yeah, get the file integrity straight or we're nowhere--I don't know of any way to fix the incomplete/bad file save for some download tools that would've resumed on their own. I think there's no mirrors, either, so it's only the one file (?) unless maybe I missed another release somewhere.

md5sum dsl-2024.rc3.iso c837ad389aa129c43bcd82fbb64f82e6 dsl-2024.rc3.iso

Gotta think about the rest (please tell me it just Went Away ™ with the right md5sum iso). Thanks again for hanging in there.

If you want to try larger files from USB, I've just been introduced to the plop boot manager which would seem to be just the thing for we dsl users that have old bioses w/o usb booting support. See the linked thread at the AntiX forum for a YT link to how easy it is. It will save re-burning media, FWIW, for all of us.

Pages: 1 2 3 4 5 6 7

x18

grindstone

x18

grindstone

x18

grindstone

x18

grindstone

x18

grindstone