Re: pcspkr loaded, but no bell

On Wed, 2023-03-29 at 21:31 +0200, Ralf Mardorf wrote: > On Wed, 2023-03-29 at 10:27 +0100, Ralph Corderoy wrote: > > https://wiki.archlinux.org/title/PC_speaker > > "More recent motherboard models omit the POST beep in favor of rapidly > booting into the OS." > > I'll take a look at the used "bo

Re: Qwt is currently built with Qt5 - should I mark the package as out-of-date?

Looks like this should be treated as an upstream qwt issue. Thanks for the input! On Wed, Mar 29, 2023 at 11:27 PM Erich Eckner wrote: > On Wed, 29 Mar 2023, Peyton Murray wrote: > > > Hi all, > > Hi Peyton, > > > Sorry if this is a naive question, but qwt is currently being built with > > Qt5,

Re: Qwt is currently built with Qt5 - should I mark the package as out-of-date?

On Wed, 29 Mar 2023, Peyton Murray wrote: Hi all, Hi Peyton, Sorry if this is a naive question, but qwt is currently being built with Qt5, which is nearing end-of-life, while Qt6 has been out for a while. I'd like for qwt to be built with Qt6, but I'm not sure if this means the package is ou

Re: Qwt is currently built with Qt5 - should I mark the package as out-of-date?

El mié, 29-03-2023 a las 22:32 -0700, Peyton Murray escribió: > Sorry if this is a naive question, but qwt is currently being built > with Qt5, which is nearing end-of-life, while Qt6 has been out for a > while. I'd like for qwt to be built with Qt6, but I'm not sure if > this means the package is

Qwt is currently built with Qt5 - should I mark the package as out-of-date?

Hi all, Sorry if this is a naive question, but qwt is currently being built with Qt5, which is nearing end-of-life , while Qt6 has been out for a while. I'd like for qwt to be built with Qt6, but I'm not sure if this mea

Re: pcspkr loaded, but no bell

On Wed, 2023-03-29 at 10:27 +0100, Ralph Corderoy wrote: > https://wiki.archlinux.org/title/PC_speaker "More recent motherboard models omit the POST beep in favor of rapidly booting into the OS." I'll take a look at the used "boot speed". This mobo has got several options. I don't remember what o

[not solved, but more or less clear] pcspkr loaded, but no bell

Hi Ralph, the Arch Linux install was used with a Gigabyte GA-B85M-D3H motherboard. Now the same install, on the same SSD is used by a Gigabyte B760 DS3H DDR4 (1.0) motherboard. Since 2015 I'm using the same alsa-base.conf: [rocketmouse@archlinux ~]$ /bin/ls -hl /etc/modprobe.d/alsa-base.conf; ca

[not solved, but clear, without doubts] Enabling CSM fails, can somebody recommend a bootloader

On Mon, 2023-03-27 at 10:40 +0200, Ralf Mardorf wrote: > I read that on modern Intel machines CSM cannot be enabled, when using > the internal GPU. I wonder if this is correct?! Gigabyte support confirmed it. This is correct. The answer to my CSM (legacy boot) related request translated from Germ

Re: Pacman: There are N providers available for X

Hi Markus, > > a$ pacman -Qq >a.all > > a$ pacman -Qqe >a.explicit > > > > b$ pacman -S --asdeps --needed > b$ pacman -S --asexplicit --needed > Make that last line > > $ pacman -D --asexplicit < a.explicit +1. Thanks. -- Cheers, Ralph.

Re: Pacman: There are N providers available for X

Am 29.03.23 um 12:13 schrieb Ralph Corderoy: a$ pacman -Qq >a.all a$ pacman -Qqe >a.explicit b$ pacman -S --asdeps --needed Make that last line $ pacman -D --asexplicit < a.explicit BR

Re: Pacman: There are N providers available for X

Hi LW, > While that will probably work I feel it's error-prone and to much work. > > Maybe this is an X-Y problem. > Why is having to answer the N-providers-for-X questions a problem ? I explained the X of X-Y earlier and thought it was accepted as clear. - How to reproduce the packages install

Re: pcspkr loaded, but no bell

Hi Ralf, > [rocketmouse@archlinux ~]$ beep -l300 -f750 --verbose --debug > beep: Verbose: evdev: driver_detect 0x562c898210c0 (nil) > beep: Verbose: lib: could not open(2) > /dev/input/by-path/platform-pcspkr-event-spkr: Permission denied As an aside, https://wiki.archlinux.org/title/PC_speaker#

Re: netctl problem

On 28-03-2023 23:45, Fons Adriaensen wrote: The reason for the netctl failure turned out to be that dhcpcd was not installed. Which was a bit of surprise, because netctl needs it. It seems netctl has gained some flexibility and dhcpcd is now an optional dependency . Check 'pacman -Si netc

Re: Pacman: There are N providers available for X

Ralph and Eric had the same idea, creating a list of packages installed as dependencies and use that for the new system. While that will probably work I feel it's error-prone and to much work. Maybe this is an X-Y problem. Why is having to answer the N-providers-for-X questions a problem ?