Posts by torquebar

torquebar · Installation

I meant that in terms of the PulseAudio Volume GUI. it should not install unless Pulse is installed. As far as ALSA, I might set one of my distros up to use it instead of Pulse but I have other sound issues to square away first.

After moving my stuff into a new case I can't get my Xonar-STX-III to make sound at all and I don't think it's an OS issue because with the only two bootable systems I have right now (Slackware and Devuan) it's the same situation. If I play a video then PA Volume Control shows the output in the slider but neither the Speaker nor the headset output can be heard.

I hope I haven't blown my card's output jacks in the move because this is a GREAT card with 1/4" and RCA jacks and I know of no replacement for it.
.

torquebar · Installation

Yes, thank you! It helped me discover that pulseaudio wasn't installed!

I would've thought that PAVC would have pulseaudio as a depend,

torquebar · Installation

Thanks, that's a relief. I thought that AMD was either on proprietary driver or on nouveau (same as nvidia) so if I installed anything AMD it might then prevent nouveau from driving. I'm an ignorant moron, that's why I've had nothing but nvidias until now :-)

torquebar · Installation

The actual message is:

Establishing connection to PulsxeAudio. Please wait...

But it never connects

Nothing untoward in lspci or in /etc/pulse/client.conf

# lspci
00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) (rev 40)
03:04.0 Multimedia audio controller: C-Media Electronics Inc CMI8788 [Oxygen HD Audio]
08:00.0 VGA compatible controller: NVIDIA Corporation GK107 [GeForce GT 640] (rev a1)
08:00.1 Audio device: NVIDIA Corporation GK107 HDMI Audio Controller (rev a1)

# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see <http://www.gnu.org/licenses/>.

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; default-sink =
; default-source =
; default-server =
; default-dbus-server =

; autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog

; cookie-file =

; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 MiB

; auto-connect-localhost = no
; auto-connect-display = no

torquebar · Installation

firmware-amd-graphics adds firmware files for AMD graphics chips to /lib/firmware/amdgpu so that they are available during boot time. They are only pulled if an AMD graphics card is detected. No need to remove them. They will not hurt.

Thanks for the explain; so if I want to stay with nouveau then I shouldn't install it. Right now nouveau is driving my temporary nvidia card, I presume that when I change the AMD card nouveau will simply use its non-proprietary AMD driver?

torquebar · Installation

Thank you all very much!

nixer:
Google-earth-pro downloaded, installed, tested. Works just fine without the nvidia driver on nouveau.
Librewolf installed, a litlle footworky but hey...
About driver boot issues: booting recovery mode not always possible. I pulled the AMD card that blew and inserted my opld nvidia card but never got a chance to revert to nouveau on my Suse isnstallation. As a result I cannot boot it at all, would have to do it with chroot from another system but I won't bother. New AMD card is coming next week, Suse might just boot again after I install it (there will be no more nvidias).

StopAI:
Packlist written on desktop,

rolfie:

firmware-amd-graphics

found, installed for test, removed. Wasn't sure about it messing up my current and temporary operation ov nvidia card using nouveau.

chris2be8:
...done. Nouveau is in fact in charge, the surprise was that google-earth work pretty good with it!
So I might just stay with nouveau after installing new AMD card. I'm no gamer and tyhe ONLY reasion I've been using the proprietary drivers was that before GE would not work without them.

Oustanding issues:

Install Otter web navigator?

How to get synaptic to use package list produced with

apt list > listapt.txt

?

torquebar · Installation

Got my new version up and running (see upgrade post), just need some pointers for the following:

How do I get google-earth-pro installed (it's not in Synaptic)?

Ditto for Librewolf & Otter web-navigators

How do I save the list of all my installed packages with Synaptic, or load them into it from a previous installation to see if any are missing?

I have a temporary nvidia graphics card, getting an AMD one in a few days. I t h i n k that nouveau is being used, how can I verify and what will I need to do when I get my AMD one (if anything)? Last I checked google-earth was not nice to see without a proprietary 3d ax driver.

torquebar · Installation

I remember HeadOnAStick from an Artix forum, some (read much) of that discussion is over my head but what I like is not just a terminal log-in followed by an automatic startx but logging in as root or user and starting X as user only when I want X (the way Slackware does it). And for the neatest (IMO) method I see selecting the desktop as part of startx (startxkde, startxxfce, startxgnome, etc.).

torquebar · Installation

stargate-sg1-cheyenne-mt:

definitely a clean install is best. when i prepare and partition a new hdd/ssd i always reserve several partitions for future newer versions(or completely different operating systems). and they are always there if i need to use them for some temporary purpose. don't forget a bullet-proof back-up plan!

I do that too, there was a time when I booted a different distro every day of the week and had several backlevels of each ready to be booted. I'm now down to 5 as I leave only Suse as a sole systemd system.

A clean install means a LOT of tweaking, like two weeks worth, which is why I asked. Suse lets you upgrade a version with the DVD of a more recent one (getting a same system up to par is called and upDATE not an upgrade).

So now that I have done a Daedalus clean install I cant' get on line to even start tweaking.

lspci
Bus 002 Device 004: ID 13b1:003e Linksys AE6000 802.11a/b/g/n/ac Wireless Adapter [MediaTek MT7610U]
Bus 007 Device 004: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 802.11n Wireless Network Adapter
Bus 001 Device 005: ID 0bda:b812 Realtek Semiconductor Corp. RTL88x2bu [AC1200 Techkey]

Those are the 3 USB wifi transceivers*, NetworkManager is running, but none of them work (using one of them in Slackware presently).

*
I use ONLY USB WiFi and only removable racked/backplane drives as they allow physical control and thus aren't the huge security hole that wired-in onboard versions are.

Edited addendum:
==============
I have no idea how but wifi just works. Maybe NetworkManager isn't automatically restarted after every config edit and so next day's reboot is what did it.

As for upgrading without having to retweak everything:

There are two things that are important to ME

1
my favorite apps and of course all those they pull in as depends

2
my desktop and my custom icons*

I keep my home folder (but not all my user folders) on a remote drive. I just moved my data to a new ssd and on that partition mounted under /0/data is a UserMe folder hosting among others a Dev folder. This Dev folder is my actual Devuan UserMe home so in my Dev system /home/UserMe is a link to /0/data/UserMe/Dev. This means that on a fresh install such as what I just did all I have to do is get /0/data mounted in fstab and drop a link in /home as above. As soon as I log in my old home is my new home just like that.

This comes in to make things easy when I need my apps installed, many already being installed as part of most distros' standard fare; some will need my icons edited back into their configs, I just go down both sidebar panels and the ones that won't launch are the ones that need to be reinstalled.

This was my old Dev DT and is already my new one EXACTLY the same as before, zero changes.

https://imgur.com/screenshot-x2A9zHw

All I have to do nwext is install a small group of apps that don't sjhow in Synaptic (that'll be another topic).

* custom icons such as NedIt in the lower left panel and kdiff3 to its left.

torquebar · Installation

New guitar day, eh? That's always a winner! My last one is around 10 years old but it was such a miracle that I might just never buy another one. The dealer, a very qualified old pro and true friend (who had helped me out with a zillion music issues over the years) told me when he received it "this guitar is one of those one in so many that every now and then ring all the right bells. It is beyond all doubt a mastrerpiece". It was just a lowly Epiphone LP classic with 57's but it still sounds like the best of all them studio/signature/whatever 5 figure guitars.

A bug? More like an anthill because it's defaults and the user is just sitting there powerless. It's like those identical but nameless user figures staring at you on the wall, and they're not evenn in sorted order for the user to guess.

One of the (many) reasons I like slackware is that you can still log in at cLi level and then start X with 'startx'. The contra argument is that it is problematic to start X without a desktop manager. That 'could' be but Slackware don't think so, furthermore even if it is true then users should launch sddm or the dtm of their choice but inititial login should always be @ command-line level. My 2 cents.

None of this to be taken as badmouthing Devuan, I wouldn't use it if I didn't like it :-)

torquebar · Installation

found it... invisible screen area left bottom

torquebar · Installation

I just did a clean install of Daedalus because my previous version stopped booting. During the install I included KDE, XFCE and Gnome but don't remember having specified which one I want sddm to run by default on log-in. I'm not familiar with Gnome but it looks like that's what I'm getting and I don't see any drop-list to select KDE or XFCE instead (I would normally want my Devuan system to use XFCE). What are my options to extricate myself from this situation (I can access the system form Slackware for example if needed). TIA.

torquebar · Hardware & System Configuration

There are actually 2 data partitions involved on my desktop that are also mounted in Devuan-Chimaera fstab (for a minute I thought it was a booted Devuan partition). These are data partitions that may have been formatted under any of the OS'es I use and all are marked "nofail" in every /etc.fstab including the Devuan one so issues with them should not halt the boot in the first place. If it weren't for this I might not even have noticed anything.

man e2fsck will show at the bottom the E2fsprogs parent package version # and as I noted in my Tumbleweed it's 1.47.0 , probably the same in Artix, in Devuan (Chimaera) it's 1.46.2 and I don't know the others off hand.

As far as I'm concerned the issue is moot as I will soon upgrade from Chimaera to Daedalus on the desktop as well.

torquebar · Hardware & System Configuration

Hold your horses.

I doubt very much that I would have installed Chimaera on a partition formatted by tumbleweed :-)

What I do, and that regularly, is something like

 # e2fsck -f /dev/sda19

with fixes on a data drive from Tumbleweed for the simple reason that tumbleweed is my go-to system although the same data-drive is accessed from all other distro systems as well. Then when I next boot Chimaera I get the control-D alert.

I suggested the update as a fix merely as opposed to a workaround which is NEVER a fix. On my laptop 1.47 is in use by the Devuan system (that one being Daedalus I think) where the issue does not exist.

Finally not all Devuan (or any Linux) users are necessarily developers, last I heard.

torquebar · Hardware & System Configuration

Can't say, I know that 1-47.0 is C12 aware and that 1.46.2 (last in my updated Devuan) is not. A C12 aware version will not show the error AFAIK (I'm on Tumbleweed right now, doing an update).

check this out:
==================================================
https://forums.linuxmint.com/viewtopic.php?t=409988
Failure Details:
* Many/most distros based on Ubuntu v22.04 will have e2fsprogs v1.46.5-2ubuntu1.1
* Many/most of the Arch-based distros will have e2fsprogs v1.47.0-1 (or newer)
* Debian is likely to have the same version as Ubuntu above or an older version

Update: According to u/Schwarzer-Kater, Debian 12 Bookworm (stable) has e2fsprogs version 1.47.0-2. Comment link ( https://www.reddit.com/r/DistroHopping/ ... &context=3 ).
==========================================

torquebar · Hardware & System Configuration

The

tune2fs -O ^orphan_file /dev/mydevice

ritual is a workaround, the FIX would be to update E2fsprogs from 1.46.2 (2021) to 1.47.0 (2023), so I'm asking the 'nice' devs to plese do it. It's a non-lethal PITA but enough to make you wonder sometimes on boot if your system had been totally borked.

Hit Cntrl-D to continue

is not what you wanna see on every boot :-)

torquebar · Hardware & System Configuration

it was probably formatted with bleeding-edge tumbleweed but it serves as a data partition for six or seven different systems

torquebar · Hardware & System Configuration

didn't work for my problem, I tried from another booted system. I think the ultimate fix is an update of fsck, like the error message says..

torquebar · Hardware & System Configuration

I have a data partition on the same ssd as the bootable systems. If I do this in Suser Slowroll for example

# fsck /dev/sda10
fsck from util-linux 2.39.3
e2fsck 1.47.0 (5-Feb-2023)
/dev/sda10: clean, 16610/18022400 files, 63630170/72089600 blocks

This partition is normally automounted in fstab with a "nofail" switch

# /etc/fstab: static file system information Devuan on p12.
UUID=f203d9ec-a53c-4f33-ad2a-222cf8f8dbcd / ext4 errors=remount-ro 0 1
UUID=7de3fe4d-f350-4661-adf4-0159abacf3ff swap swap sw,nofail 0 0
UUID=95cb7a9a-d7f2-4fb8-bf49-56828acf931c /0/adat ext4 defaults,nofail 0 2
UUID=2b43042f-761c-40ec-b207-5af655a51b93 /0/local ext4 defaults,nofail 0 2

So I would have presumed that inability to mount it would never fail the boot.

BUT... when I try to boot Devuan the boot does at least stumble with a boot halt and the advisory to continue with a Cntrl-D. Subsequent check gives this:

# fsck -f /dev/sda10
fsck from util-linux 2.36.1
e2fsck 1.46.2 (28-Feb-2021)
/dev/sda10 has unsupported feature(s): FEATURE_C12
e2fsck: Get a newer version of e2fsck!

This Devuan partition is up to date (I think). It's not a federal case, I can live with it, just thought I'd mention it for the devs. As it is the data partition is unmounted while booted into Devuan (I have not tried manually mounting it).

torquebar · Installation

Thanks for the helpfulness but that's not what I meant. I do online updating regularly. Can I boot with a Daedelus installation DVD to upgrade my Chimaera system? The only thing I've ever done with Devuan is Chimaera as it was the first one I ever installed and am still using it (except my laptop which has Daedelus). Or, if I update each of a Chimara and a Daedelus system will they in fact both become the same for all intent and purpose? Suse installation DVD's give me a choive top install, upgrade, or boot into a rescue system but I haven't done three Devuan installs to remember what was offered.

--
my Devuan desktop: https://imgur.com/x2A9zHw.png

torquebar · Installation

After having had some issues with Chimaera on my AMD desktop I managed to recover a backed up disk image, got it updated and all is well. But progress is progress and rather than suffer through tweaking a new install I was just wondering if the Daedelus dvd can be used to upgrade a Chimaera system like Suse Tumbleweed can be updated from a dvd OR from the repos?

torquebar · Installation

What I've done so far

The login screen was all grey and white, no user names or ids only icons, no session selection KDE/XFCE

Loaded Synaptic and deleted Plasma and all that had to go down with it, as well as xfce4-power-manager.

I boot any one of 6 distros every day, 3 use kde the other 3 XFCE, 3 use openrc 3 use systemd. Debian's all set up for XFCE.

This is one reason I by far prefer slackware's way: you log in at init 3 and THEN startx with the then desired DE like startx kde, or startx xfce

Thanks every one for the help, may Providence grant you your every wish!

--
https://imgur.com/M1WNQ6q.png

torquebar · Installation

Thank you, I'll work on this a little more on opportunity ...

A lot has gone down in the last two days, mostly with no internet connection (it never rains but pours). My desktop was due for a little upgrade as well so I installed Daedelus on it, copied the partition to the laptop and booted it. It's missing all the laptop stuff which I don't need anyway.

I installed both XFCE and KDE but it boots into KDE and I don't know how to change that to XFCE which half of my six distros use including Devuan.

https://imgur.com/x2A9zHw.png

torquebar · Installation

I haven't purged xfce4 yet because I need it (using kde with other distros). The lockup is complete and immediate, no function keys, nothing. Any form of SSH is unfortunately way above my pay-grade (of clueless mouse-molester). But I did manage these:

# dmesg --level=alert,crit,err,warn > /dmesg.txt

[ 0.098947] x86/cpu: SGX disabled by BIOS.
[ 0.098972] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/ … n/mds.html for more details.
[ 0.098972] MMIO Stale Data CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/ … _data.html for more details.
[ 0.098972] #3
[ 0.151573] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[ 0.383860] pnp 00:0b: disabling [mem 0x000c0000-0x000c3fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
[ 0.383868] pnp 00:0b: disabling [mem 0x000c8000-0x000cbfff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
[ 0.383874] pnp 00:0b: disabling [mem 0x000d0000-0x000d3fff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
[ 0.383879] pnp 00:0b: disabling [mem 0x000d8000-0x000dbfff] because it overlaps 0000:00:02.0 BAR 6 [mem 0x000c0000-0x000dffff]
[ 0.715044] hpet_acpi_add: no address or irqs in _CRS
[ 1.060870] usb: port power management may be unreliable

cat /var/log/Xorg.0.log > /xorglog.txt

[ 221.482]
X.Org X Server 1.21.1.7
X Protocol Version 11, Revision 0
[ 221.484] Current Operating System: Linux localhost 6.1.0-10-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.38-1 (2023-07-14) x86_64
[ 221.484] Kernel command line: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p12
[ 221.485] xorg-server 2:21.1.7-3devuan1 (https://www.devuan.org/os/community)
[ 221.486] Current version of pixman: 0.42.2
[ 221.486] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 221.487] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 221.489] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Feb 10 02:38:54 2024
[ 221.490] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 221.491] (==) No Layout section. Using the first Screen section.
[ 221.491] (==) No screen section available. Using defaults.
[ 221.491] (**) |-->Screen "Default Screen Section" (0)
[ 221.491] (**) | |-->Monitor "<default monitor>"
[ 221.491] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 221.491] (==) Automatically adding devices
[ 221.491] (==) Automatically enabling devices
[ 221.491] (==) Automatically adding GPU devices
[ 221.491] (==) Automatically binding GPU devices
[ 221.491] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 221.492] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 221.492] Entry deleted from font path.
[ 221.493] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[ 221.493] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 221.493] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 221.493] (II) Loader magic: 0x55ea98815ea0
[ 221.493] (II) Module ABI versions:
[ 221.493] X.Org ANSI C Emulation: 0.4
[ 221.493] X.Org Video Driver: 25.2
[ 221.493] X.Org XInput driver : 24.4
[ 221.493] X.Org Server Extension : 10.0
[ 221.493] (++) using VT number 1

[ 221.493] (II) seatd_libseat init
[ 221.493] (II) [libseat/backend/seatd.c:64] Could not connect to socket /run/seatd.sock: No such file or directory
[ 221.494] (II) [libseat/libseat.c:76] Backend 'seatd' failed to open seat, skipping
[ 221.495] (EE) [libseat/backend/logind.c:660] Could not get primary session for user: No data available
[ 221.496] (II) [libseat/libseat.c:76] Backend 'logind' failed to open seat, skipping
[ 221.497] (II) [seatd/seat.c:39] Created VT-bound seat seat0
[ 221.497] (II) [seatd/server.c:145] New client connected (pid: 2708, uid: 0, gid: 0)
[ 221.498] (II) [libseat/backend/seatd.c:633] Started embedded seatd
[ 221.498] (II) [seatd/seat.c:170] Added client 1 to seat0
[ 221.499] (DB) [common/terminal.c:198] Setting process switching to 1
[ 221.499] (DB) [common/terminal.c:246] Setting KD keyboard state to 0
[ 221.500] (DB) [common/terminal.c:273] Setting KD graphics state to 1
[ 221.500] (II) [seatd/seat.c:480] Opened client 1 on seat0
[ 221.500] (II) [libseat/libseat.c:73] Seat opened with backend 'builtin'
[ 221.500] (II) [libseat/backend/seatd.c:212] Enabling seat
[ 221.500] (II) seatd_libseat enable
[ 221.500] (II) seatd_libseat handled 2 events
[ 221.600] (II) seatd_libseat client activated
[ 221.612] (--) PCI:*(0@0:2:0) 8086:5916:17aa:225d rev 2, Mem @ 0xeb000000/16777216, 0xa0000000/268435456, I/O @ 0x0000e000/64, BIOS @ 0x????????/131072
[ 221.613] (II) LoadModule: "glx"
[ 221.615] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 221.624] (II) Module glx: vendor="X.Org Foundation"
[ 221.624] compiled for 1.21.1.7, module version = 1.0.0
[ 221.624] ABI class: X.Org Server Extension, version 10.0
[ 221.624] (==) Matched modesetting as autoconfigured driver 0
[ 221.624] (==) Matched fbdev as autoconfigured driver 1
[ 221.624] (==) Matched vesa as autoconfigured driver 2
[ 221.624] (==) Assigned the driver to the xf86ConfigLayout
[ 221.624] (II) LoadModule: "modesetting"
[ 221.625] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 221.626] (II) Module modesetting: vendor="X.Org Foundation"
[ 221.626] compiled for 1.21.1.7, module version = 1.21.1
[ 221.626] Module class: X.Org Video Driver
[ 221.626] ABI class: X.Org Video Driver, version 25.2
[ 221.626] (II) LoadModule: "fbdev"
[ 221.627] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 221.627] (II) Module fbdev: vendor="X.Org Foundation"
[ 221.627] compiled for 1.21.1.3, module version = 0.5.0
[ 221.627] Module class: X.Org Video Driver
[ 221.628] ABI class: X.Org Video Driver, version 25.2
[ 221.628] (II) LoadModule: "vesa"
[ 221.628] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 221.629] (II) Module vesa: vendor="X.Org Foundation"
[ 221.629] compiled for 1.21.1.3, module version = 2.5.0
[ 221.629] Module class: X.Org Video Driver
[ 221.629] ABI class: X.Org Video Driver, version 25.2
[ 221.629] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 221.629] (II) FBDEV: driver for framebuffer: fbdev
[ 221.629] (II) VESA: driver for VESA chipsets: vesa
[ 221.630] (EE) open /dev/dri/card0: No such file or directory
[ 221.630] (WW) Falling back to old probe method for modesetting
[ 221.630] (EE) open /dev/dri/card0: No such file or directory
[ 221.630] (II) Loading sub module "fbdevhw"
[ 221.630] (II) LoadModule: "fbdevhw"
[ 221.630] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 221.631] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 221.631] compiled for 1.21.1.7, module version = 0.0.2
[ 221.631] ABI class: X.Org Video Driver, version 25.2
[ 221.632] (EE) Unable to find a valid framebuffer device
[ 221.632] (WW) Falling back to old probe method for fbdev
[ 221.632] (II) Loading sub module "fbdevhw"
[ 221.632] (II) LoadModule: "fbdevhw"
[ 221.632] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 221.632] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 221.632] compiled for 1.21.1.7, module version = 0.0.2
[ 221.632] ABI class: X.Org Video Driver, version 25.2
[ 221.632] (II) FBDEV(2): using default device
[ 221.632] vesa: Refusing to run on UEFI
[ 221.633] (EE) Screen 0 deleted because of no matching config section.
[ 221.633] (II) UnloadModule: "modesetting"
[ 221.633] (EE) Screen 0 deleted because of no matching config section.
[ 221.633] (II) UnloadModule: "fbdev"
[ 221.633] (II) UnloadSubModule: "fbdevhw"
[ 221.633] (II) FBDEV(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 221.633] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32
[ 221.633] (==) FBDEV(0): RGB weight 888
[ 221.633] (==) FBDEV(0): Default visual is TrueColor
[ 221.633] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[ 221.633] (II) FBDEV(0): hardware: EFI VGA (video memory: 8100kB)
[ 221.633] (DB) xf86MergeOutputClassOptions unsupported bus type 0
[ 221.633] (II) FBDEV(0): checking modes against framebuffer device...
[ 221.633] (II) FBDEV(0): checking modes against monitor...
[ 221.633] (II) FBDEV(0): Virtual size is 1920x1080 (pitch 1920)
[ 221.633] (**) FBDEV(0): Built-in mode "current": 207.4 MHz, 85.3 kHz, 77.2 Hz
[ 221.633] (II) FBDEV(0): Modeline "current"x0.0 207.38 1920 1952 2192 2432 1080 1084 1088 1104 -hsync -vsync -csync (85.3 kHz b)
[ 221.633] (==) FBDEV(0): DPI set to (96, 96)
[ 221.633] (II) Loading sub module "fb"
[ 221.633] (II) LoadModule: "fb"
[ 221.633] (II) Module "fb" already built-in
[ 221.633] (**) FBDEV(0): using shadow framebuffer
[ 221.633] (II) Loading sub module "shadow"
[ 221.633] (II) LoadModule: "shadow"
[ 221.633] (II) Loading /usr/lib/xorg/modules/libshadow.so
[ 221.634] (II) Module shadow: vendor="X.Org Foundation"
[ 221.634] compiled for 1.21.1.7, module version = 1.1.0
[ 221.634] ABI class: X.Org ANSI C Emulation, version 0.4
[ 221.635] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by kernel - disabling)
[ 221.637] (==) FBDEV(0): Backing store enabled
[ 221.638] (==) FBDEV(0): DPMS enabled
[ 221.639] (II) Initializing extension Generic Event Extension
[ 221.639] (II) Initializing extension SHAPE
[ 221.640] (II) Initializing extension MIT-SHM
[ 221.640] (II) Initializing extension XInputExtension
[ 221.641] (II) Initializing extension XTEST
[ 221.641] (II) Initializing extension BIG-REQUESTS
[ 221.642] (II) Initializing extension SYNC
[ 221.642] (II) Initializing extension XKEYBOARD
[ 221.642] (II) Initializing extension XC-MISC
[ 221.643] (II) Initializing extension SECURITY
[ 221.643] (II) Initializing extension XFIXES
[ 221.643] (II) Initializing extension RENDER
[ 221.644] (II) Initializing extension RANDR
[ 221.644] (II) Initializing extension COMPOSITE
[ 221.645] (II) Initializing extension DAMAGE
[ 221.645] (II) Initializing extension MIT-SCREEN-SAVER
[ 221.645] (II) Initializing extension DOUBLE-BUFFER
[ 221.645] (II) Initializing extension RECORD
[ 221.646] (II) Initializing extension DPMS
[ 221.646] (II) Initializing extension Present
[ 221.646] (II) Initializing extension DRI3
[ 221.646] (II) Initializing extension X-Resource
[ 221.647] (II) Initializing extension XVideo
[ 221.647] (II) Initializing extension XVideo-MotionCompensation
[ 221.647] (II) Initializing extension SELinux
[ 221.647] (II) SELinux: Disabled on system
[ 221.647] (II) Initializing extension GLX
[ 221.647] (II) AIGLX: Screen 0 is not DRI2 capable
[ 221.810] (II) IGLX: Loaded and initialized swrast
[ 221.810] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[ 221.810] (II) Initializing extension XFree86-VidModeExtension
[ 221.811] (II) Initializing extension XFree86-DGA
[ 221.811] (II) Initializing extension XFree86-DRI
[ 221.811] (II) Initializing extension DRI2

torquebar · Installation

Just having got me a refurb laptop (Lenovo T480 to which I have already installed some other distros) I ran into problems installing Chimarea (present on my desktop for a while now). So I burnt the Daedelus dvd and tried with that with even less success.

On booting I get to a cLi login prompt and I can log in as root or as user.

If I enter 'starx' as user the desktop (xfce I think, kde was also 'installed') loads but locks right up, no mouse, no keyboard, only an error annunciation:

"Power Manager Plugin unexpectedly left the panel"

There is only a hard reset available. Can I recover from this 'lockup' or is a re-install necessary? Beyond being able to log in at cLi level, I can also mount the partition from another system if required.

TIA

The officially official Devuan Forum!

#1 Re: Installation » Fresh Daedalus: No connection to PulseAudio » 2024-08-18 02:00:06

#2 Re: Installation » Fresh Daedalus: No connection to PulseAudio » 2024-08-18 00:32:38

#3 Re: Installation » Fresh Daedalus, residual app install issues » 2024-08-18 00:15:51

#4 Installation » Fresh Daedalus: No connection to PulseAudio » 2024-08-17 01:41:24

#5 Re: Installation » Fresh Daedalus, residual app install issues » 2024-08-17 01:03:15

#6 Re: Installation » Fresh Daedalus, residual app install issues » 2024-08-16 00:10:23

#7 Installation » Fresh Daedalus, residual app install issues » 2024-08-15 01:54:02

#8 Re: Installation » how to select desktop on log-in » 2024-08-14 01:16:43

#9 Re: Installation » upgrade Chimaera with Daedelus? » 2024-08-14 00:15:36

#10 Re: Installation » how to select desktop on log-in » 2024-08-13 09:43:30

#11 Re: Installation » how to select desktop on log-in » 2024-08-13 01:54:08

#12 Installation » how to select desktop on log-in » 2024-08-12 23:35:36

#13 Re: Hardware & System Configuration » fsck "FEATURE_C12"? » 2024-04-25 23:32:29

#14 Re: Hardware & System Configuration » fsck "FEATURE_C12"? » 2024-04-25 15:05:03

#15 Re: Hardware & System Configuration » fsck "FEATURE_C12"? » 2024-04-25 02:15:20

#16 Re: Hardware & System Configuration » fsck "FEATURE_C12"? » 2024-04-24 23:22:00

#17 Re: Hardware & System Configuration » fsck "FEATURE_C12"? » 2024-03-15 18:02:57

#18 Re: Hardware & System Configuration » fsck "FEATURE_C12"? » 2024-03-15 17:14:44

#19 Hardware & System Configuration » fsck "FEATURE_C12"? » 2024-03-15 16:08:21

#20 Re: Installation » upgrade Chimaera with Daedelus? » 2024-02-18 20:04:43

#21 Installation » upgrade Chimaera with Daedelus? » 2024-02-18 18:01:24

#22 Re: Installation » Daedelus install on Lenovo T480 boots, locks up. » 2024-02-14 05:36:44

#23 Re: Installation » Daedelus install on Lenovo T480 boots, locks up. » 2024-02-12 05:46:43

#24 Re: Installation » Daedelus install on Lenovo T480 boots, locks up. » 2024-02-10 21:59:33

#25 Installation » Daedelus install on Lenovo T480 boots, locks up. » 2024-02-10 13:03:28

Board footer