just like Gene, thank you for all this good work and this great Linux
distribution !
Le ven. 4 nov. 2022 à 10:40, Genes Lists a écrit :
>
> Just a note to thank you all for pushing this over the line. Obviously a
> huge effort and very big thanks!!
>
> Everything I've tested so far works just fi
hi,
where can I get help with this ?
my problem is this:
I'm on a corporate network that is filtered (proxy) and I need to run some
tests on a virtual machine that needs to have direct access to the Internet.
I set up this configuration and try to route everything that comes out of
tap0 to wlan0
*(sorry, the previous message is gone a bit fast)*
hi,
where can I get help for this ?
my problem is :
I'm on a corporate network that is filtered (proxy) and I need to run some
tests on a virtual machine that needs to have direct access to the Internet.
I set up this configuration and try to r
yes, the table parameter was missing !
# ip route add default via 192.168.144.254 dev wlan0 *table tap0*
Le mer. 9 nov. 2022 à 17:10, Felix Yan a écrit :
> On 11/9/22 17:52, Pascal wrote
> > # ip tuntap add tap0 mode tap user me
> > # ip addr add 192.168.11.254/24 dev tap0
&g
message -
De : Pascal
Date: mer. 8 mars 2023 à 14:09
Subject: bio_check_ro @ blk-core.c
hi,
I'm addressing you because you intervened (commit
<https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/block/blk-core.c?h=v6.1.15&id=bdb7d420c6f6d2618d4c907cd7742c319
. writes KO on RO blockdevice) ?
with the changes in the blk-core.c source code since version 5.10.19, is it
still necessary to tweak the bio_check_ro function to disallow technologies
that ignore the read-only block?
regards, lacsaP.
Le mer. 15 mars 2023 à 12:37, Emil Velikov a
écrit :
> Greeti
c9098c64903b56b2d3ac5248d2f34c10e63241a10a35b3 lvm.disk
the same test was performed with for example Linux Software RAID (mdadm)
and the device is not modified (as expected from being locked in read-only
mode).
in conclusion, it seems that LVM, even in recent ve
ev-worker)[1276]: sda: Process
'/usr/local/sbin/rodev /dev/sda' failed with exit code 1.
Mar 16 10:21:07 archiso systemd-homed[268]: block device
/sys/devices/pci:00/:00:03.0/usb2/2-3/2-3:1.0/host6/target6:0:0/6:0:0:0/block/sda
has been removed.
/tmp : sha256sum lvm.disk
c39d62a5e9f87dc9098c64903b56b2d3ac5248d2f
hi,
I have the same with OpenBox.
I run obconf, (re)select the same fonts and sizes, save the configuration
and restart the graphical environment : OK now.
regards.
Le jeu. 11 nov. 2021 à 21:04, Uwe Sauter via arch-general <
arch-general@lists.archlinux.org> a écrit :
>
>
> Am 11.11.21 um 12:09 s
hi,
I have an ArchLinux installed on a usb disk (eg. "mobile").
~ # uname -r
5.15.37-1-lts
~ # pacman -Q | egrep 'alsa|chromium|firefox|mplayer'
alsa-lib 1.2.6.1-1
alsa-topology-conf 1.2.5.1-1
alsa-ucm-conf 1.2.6.3-1
alsa-utils 1.2.6-1
chromium 101.0.4951.54-1
firefox 100.0-1
mplayer 38359-1
whe
I just had a look in the wiki and did not see anything special.
sof-firmware is installed.
~ # pacman -Q | grep 'sof'
sof-firmware 2.1.1-1
the problem seems to be between chromium and my lenovo.
I will test on other machines soon...
Le jeu. 5 mai 2022 à 12:36, Damjan Georgievski via arch-genera
n immediatly and KO,
no sound.
I try again : close the browser and reopen the session as test user but
still KO.
Le jeu. 5 mai 2022 à 13:48, u34--- via arch-general <
arch-general@lists.archlinux.org> a écrit :
> Pascal via arch-general wrote:
>
> > hi,
> >
> > I h
Alsa directly : no PA or PW.
when i run Chromium from a terminal, i get these two error messages about
Alsa but they also appear when the sound is working :
[4765:4765:0504/164956.649650:ERROR:alsa_util.cc(204)] PcmOpen:
default,Device or resource busy
[4765:4765:0504/164956.649811:ERROR:alsa_util
I checked in my session the concurrent accesses with fuser -v /dev/snd/*
and killed the only one that was present and could interfere (volumeicon *that
was also present with Firefox and Mplayer*).
Le jeu. 5 mai 2022 à 15:50, Pascal a écrit :
> Alsa directly : no PA or PW.
>
> w
any /etc/asound.conf or .asoundrc or similarly named
> files messing up your sound config?
>
> Additionally (another wild guess), try running aplay -l -L and report the
> output.
>
> On Thu, May 5, 2022, 16:00 Pascal via arch-general <
> arch-general@lists.archlinux.org> wrote
with or without the option, Chromium is still willing to play sound once in
a while.
what really bothers me is the randomness of the problem.
some additional information :
$ journalctl -b | grep -i _hda_
May 09 08:39:09 archlive kernel: snd_hda_intel: probe of :00:1f.3
failed with error -2
May
, it could be added as a Chromium/Firefox dependency
(eg. pacman)...
regards, lacsaP.
Le lun. 9 mai 2022 à 14:56, Pascal a écrit :
> with or without the option, Chromium is still willing to play sound once
> in a while.
> what really bothers me is the randomness of the problem.
17 matches
Mail list logo