Re: pcspkr loaded, but no bell

2023-03-28 Thread Ralf Mardorf
PS: Still no sound: [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 beep: Verbose: console: driver_detect 0x562c89820e60

Re: pcspkr loaded, but no bell

2023-03-28 Thread Ralf Mardorf
On Wed, 2023-03-29 at 06:25 +0200, mpan wrote: > For testing purposes instal the beep package and run `beep` from it. Hi, neither running beep as user, nor as root does produce audible sound. [rocketmouse@archlinux ~]$ beep beep: Error: Could not open any device [rocketmouse@archlinux ~]$ echo

Re: pcspkr loaded, but no bell

2023-03-28 Thread mpan
if I turn on the computer, the PC buzzer does beep one time, so it does work for the POST, but the terminal (ROXTerm, with audible bell enabled) is silent, it doesn't beep anymore after using the Arch install from my old PC with my new PC. […] For testing purposes instal the beep package and

Re: netctl problem

2023-03-28 Thread Fons Adriaensen
On Tue, Mar 28, 2023 at 06:54:19PM +0200, Óscar García Amor wrote: > > Scanning the available docs, I found out that systemd-networkd > > is enabled by default. Could this be in conflict with netctl ? > > Yes, in fact, I advise you NOT to use netctl and to use systemd- > netword[1] directly.

pcspkr loaded, but no bell

2023-03-28 Thread Ralf Mardorf
Hi, if I turn on the computer, the PC buzzer does beep one time, so it does work for the POST, but the terminal (ROXTerm, with audible bell enabled) is silent, it doesn't beep anymore after using the Arch install from my old PC with my new PC. [rocketmouse@archlinux ~]$ lsmod | grep pcspkr

Re: netctl problem

2023-03-28 Thread Óscar García Amor
El mar, 28-03-2023 a las 18:09 +0200, Fons Adriaensen escribió: > Scanning the available docs, I found out that systemd-networkd > is enabled by default. Could this be in conflict with netctl ? Yes, in fact, I advise you NOT to use netctl and to use systemd- netword[1] directly. Another option

Re: netctl problem

2023-03-28 Thread Fons Adriaensen
Hi Ralph, > Unless the remote hands are used to precisely editing configuration > files, this might be something where a mistake has been made. We verified the dhcp file, and I'm pretty sure it's okay. My friend may be a linux noob, but he's an experienced engineer and learling fast :-) It's

Re: netctl problem

2023-03-28 Thread Ralph Corderoy
Hi FA, I've some general ideas. Others will have better comments on your particular questions. > Also the ethernet-dhcp example is copied to /etc/netctl/dhcp and > edited for the correct interface (enp0s25). Unless the remote hands are used to precisely editing configuration files, this might

netctl problem

2023-03-28 Thread Fons Adriaensen
Hello all, Yesterday I assisted (via a text chat) a linux noob to install Archlinux on a laptop. We got so far that the system can boot on its own, and we can login as root. The netctl package is installed. Also the ethernet-dhcp example is copied to /etc/netctl/dhcp and edited for the correct

Re: colored prompt in early userspace

2023-03-28 Thread lacsaP Patatetom
Le mar. 28 mars 2023 à 16:34, lacsaP Patatetom a écrit : > > hi, > > when you add the `break` parameter to the list of parameters passed > when the system boots, you find yourself in an interactive shell that > allows you to issue commands, perform tests, and so on... > > the shell is apparently

colored prompt in early userspace

2023-03-28 Thread lacsaP Patatetom
hi, when you add the `break` parameter to the list of parameters passed when the system boots, you find yourself in an interactive shell that allows you to issue commands, perform tests, and so on... the shell is apparently provided by `ash`. how to have a colored prompt (which visually helps

Re: Pacman: There are N providers available for X

2023-03-28 Thread Erich Eckner
Hi, On Tue, 28 Mar 2023, Lone_Wolf wrote: On 28-03-2023 14:42, Ralph Corderoy wrote: Hi LW, If I wanted to duplicate the packages from one machine to another then I'd like the method to not alter the source machine, preserve my choices, and that some packages weren't explicitly wanted. In

Re: Pacman: There are N providers available for X

2023-03-28 Thread Ralph Corderoy
Hi LW, > A possible workaround could be to identify the virtual provides and > choose a sensible provider for them. > > Those sensible choices would be entered in a set F that will be > installed with --asdeps BEFORE set E. Ah, that's given me an idea. On machine A, I could ‘pacman -Qqd’ to get

Re: Pacman: There are N providers available for X

2023-03-28 Thread Lone_Wolf
On 28-03-2023 14:42, Ralph Corderoy wrote: Hi LW, If I wanted to duplicate the packages from one machine to another then I'd like the method to not alter the source machine, preserve my choices, and that some packages weren't explicitly wanted. In other words, duplicate. ... ...could you

Re: Pacman: There are N providers available for X

2023-03-28 Thread Ralph Corderoy
Hi LW, > > If I wanted to duplicate the packages from one machine to another > > then I'd like the method to not alter the source machine, preserve > > my choices, and that some packages weren't explicitly wanted. > > In other words, duplicate. ... > ...could you explain what you do want to

Re: Pacman: There are N providers available for X

2023-03-28 Thread Lone_Wolf
On 28-03-2023 11:41, Ralph Corderoy wrote: Hi LW, Incase you don't want those questions, check which package you prefer to provide that dependency, change it's install reason to explicit and regenerate the list. That seems like a bit of a bodge though. If I wanted to duplicate the packages

Re: Pacman: There are N providers available for X

2023-03-28 Thread Ralph Corderoy
Hi LW, > Incase you don't want those questions, check which package you prefer > to provide that dependency, change it's install reason to explicit and > regenerate the list. That seems like a bit of a bodge though. If I wanted to duplicate the packages from one machine to another then I'd like

Re: Pacman: There are N providers available for X

2023-03-28 Thread Lone_Wolf
On 28-03-2023 09:22, Spencer Collyer wrote: On Mon, 27 Mar 2023 15:30:04 +0200, Uwe Koloska wrote: Am 26.03.23 um 09:25 schrieb David Runge: On 2023-03-26 07:55:06 (+0100), Spencer Collyer wrote: I'm installing a new system, and using the instructions at

Re: Pacman: There are N providers available for X

2023-03-28 Thread Spencer Collyer
On Mon, 27 Mar 2023 15:30:04 +0200, Uwe Koloska wrote: > Am 26.03.23 um 09:25 schrieb David Runge: > > On 2023-03-26 07:55:06 (+0100), Spencer Collyer wrote: > >> I'm installing a new system, and using the instructions at > >> https://wiki.archlinux.org/title/Pacman/Tips_and_tricks sections > >>

Re: Pacman: There are N providers available for X

2023-03-28 Thread Iván Zaera Avellón
On 27/3/23 15:30, Uwe Koloska wrote: Am 26.03.23 um 09:25 schrieb David Runge: On 2023-03-26 07:55:06 (+0100), Spencer Collyer wrote: I'm installing a new system, and using the instructions at https://wiki.archlinux.org/title/Pacman/Tips_and_tricks sections 2.5 and 2.6 to get the list of