On Tue, 24 Dec 2024 15:45:31 +0100 (CET)
Roger Price wrote:
> File /proc/mdstat indicates a dying RAID device with an output
> section such as
>
> md3 : active raid1 sdg6[0]
> 871885632 blocks super 1.0 [2/1] [U_]
> bitmap: 4/7 pages [16KB], 65536KB chunk
>
> Note the [U-]. Th
On Tue, 24 Dec 2024, Greg Wooledge wrote:
On Tue, Dec 24, 2024 at 15:45:31 +0100, Roger Price wrote:
md3 : active raid1 sdg6[0]
871885632 blocks super 1.0 [2/1] [U_]
bitmap: 4/7 pages [16KB], 65536KB chunk
Note the [U-].
There isn't any [U-] in that output. There is [U_].
m --monitor" command that emails
you when devices are dropped? On Debian it's run by the "mdmonitor"
systemd service.
Failing that you can regularly check the
/sys/class/block/mdX/md/degraded file and if it's anything but 0 only
then look at other files under there or a
Roberto C. Sánchez (12024-12-24):
> I think that '==' is the wrong tool.
string1 == string2
string1 = string2
True if the strings are equal. = should be used with the test
command for POSIX conformance. When used with the [[ command,
On Tue, Dec 24, 2024 at 10:37:29 -0500, Roberto C. Sánchez wrote:
> I think that '==' is the wrong tool. That is testing for string
> equality, whilst you are looking for a partial match. This is what I was
> able to get working after hacking on it for a minute or two:
>
> #! /bin/bash -u
> set -x
Hi Roger,
On Tue, Dec 24, 2024 at 03:45:31PM +0100, Roger Price wrote:
> File /proc/mdstat indicates a dying RAID device with an output section such
> as
>
> md3 : active raid1 sdg6[0]
>871885632 blocks super 1.0 [2/1] [U_]
>bitmap: 4/7 pages [16KB], 65536KB chunk
>
> Note the [
> File /proc/mdstat indicates a dying RAID device with an output section such
> as
>
> md3 : active raid1 sdg6[0]
>871885632 blocks super 1.0 [2/1] [U_]
>bitmap: 4/7 pages [16KB], 65536KB chunk
>
> Note the [U-].
I can't see a "[U-]", only a "[U_]"
Stefan
On Tue, Dec 24, 2024 at 15:45:31 +0100, Roger Price wrote:
> File /proc/mdstat indicates a dying RAID device with an output section such
> as
>
> md3 : active raid1 sdg6[0]
>871885632 blocks super 1.0 [2/1] [U_]
>bitmap: 4/7 pages [16KB], 65536KB chunk
>
> Note the [U-].
There i
Roger Price (12024-12-24):
> File /proc/mdstat indicates a dying RAID device with an output section such
> as
Maybe try to find a more script-friendly source for that information in
/sys/class/block/md127/md/?
Regards,
--
Nicolas George
File /proc/mdstat indicates a dying RAID device with an output section
such as
md3 : active raid1 sdg6[0]
871885632 blocks super 1.0 [2/1] [U_]
bitmap: 4/7 pages [16KB], 65536KB chunk
Note the [U-]. The "-" says /dev/sdh is dead. I would like to scan /proc/mdstat
and set a flag
hat you mean by horrible state.
>
> That the laptop has a worndown (usage damaged) keyboard. [1]
>
> > > So I'm ask if
> > > export KEYCODE=42
> > > echo $KEYCODE > /devices/platform/thinkpad_acpi/input/input16
> > > could cause "wlan radio
> So I'm ask if
> > export KEYCODE=42
> > echo $KEYCODE > /devices/platform/thinkpad_acpi/input/input16
> > could cause "wlan radio enable"? Or should KEYCODE be another magic number?
>
> FWIW my wifi hardware button's keycode is 246.
How was that
On Sun, 21 Jan 2024 22:41:01 +0100
Geert Stappers wrote:
> Hoping that is it possible:
>
> How to inject key stroke or "button pressed" in
> /devices/platform/thinkpad_acpi/input/input16 ?
Thinkwiki might be useful. https://www.thinkwiki.org/wiki/ThinkWiki
--
Does a
case of the laptop is "headless server, server with SSH access".
I'm not sure what you mean by horrible state.
> So I'm ask if
> export KEYCODE=42
> echo $KEYCODE > /devices/platform/thinkpad_acpi/input/input16
> could cause "wlan radio enable"
Hi,
Hoping that is it possible:
How to inject key stroke or "button pressed" in
/devices/platform/thinkpad_acpi/input/input16 ?
Website https://xyproblem.info says I should tell what the original
problem is. It is `rfkill list` reporting "hard blocked", not bein
Hi.
On Wed, Nov 15, 2023 at 10:11:16AM +, Drone Ah wrote:
> I found
> https://unix.stackexchange.com/questions/709184/fakeraid-partition-missing-not-mapped-as-a-device-on-boot-after-upgrade-to-ubu/760998#760998
>
> Using kpartx as suggested in the above post does solve the problem. Ge
, does not create
the partition devices.
I found
https://unix.stackexchange.com/questions/709184/fakeraid-partition-missing-not-mapped-as-a-device-on-boot-after-upgrade-to-ubu/760998#760998
Using kpartx as suggested in the above post does solve the problem. Getting
it to run at startup, if required
On Sun, Aug 27, 2023 at 08:19:35PM +0200, Hans wrote:
> Dear list,
>
> there is a little issue, which I try to solve. On my desptop computer I have
> 4
> harddrives:
>
> SATA 0: HDD 300 GB with Debian + GRUB on MBR (parted in /boot, /, /home
> (luks), /var (luks) and /usr (luks)
> SATA 1: HDD
On Mon, Jan 30, 2023 at 12:59 PM Georgi Naplatanov wrote:
> On 1/28/23 12:04, Timothy M Butterworth wrote:
> > All,
> >
> > I just upgraded to the 1/28/23 updates to KF5 102 and now I have no
> > audio devices found. My USB headset is plugged in but KDE does not see
&
On 1/28/23 12:04, Timothy M Butterworth wrote:
All,
I just upgraded to the 1/28/23 updates to KF5 102 and now I have no
audio devices found. My USB headset is plugged in but KDE does not see it.
lsusb lists my USB headphones:
Bus 001 Device 009: ID 046d:0a37 Logitech, Inc. USB Headset H540
On Sun, Jan 29, 2023 at 12:59 PM Brad Rogers wrote:
> On Sun, 29 Jan 2023 12:11:33 -0500
> Timothy M Butterworth wrote:
>
> Hello Timothy,
>
> >I did not try a new user. I did try deleting "~/.config/pulseaudio"
>
> Sorry to say, I've reached the limit of my knowledge on the subject.
> :-(
>
> -
On Sun, 29 Jan 2023 12:11:33 -0500
Timothy M Butterworth wrote:
Hello Timothy,
>I did not try a new user. I did try deleting "~/.config/pulseaudio"
Sorry to say, I've reached the limit of my knowledge on the subject.
:-(
--
Regards _ "Valid sig separator is {dash}{dash}{space}"
ume levels
>> because sometimes things get 'fiddled with' on update.
>>
>
> It is not a volume or a mute problem. KDE does not register any sound
> cards being installed. The hardware has drivers and it is installed. I can
> see the hardware with aplay.
>
> ap
led. The hardware has drivers and it is installed. I can see
the hardware with aplay.
aplay -l
List of PLAYBACK Hardware Devices
card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Generic [HD-Audio Generic], device 7: HDMI
On Sun, 29 Jan 2023 07:22:02 -0500
Timothy M Butterworth wrote:
Hello Timothy,
>I upgraded to 5.27beta so far no new issues. I just installed Wayland
Good to know. Thanks for the info.
>so I can try it out. My sound cards are still not working though.
Have you tried;
(a) checking volume lev
On Sun, Jan 29, 2023 at 5:19 AM Brad Rogers wrote:
> On Sat, 28 Jan 2023 10:41:38 -0500
> Timothy M Butterworth wrote:
>
> Hello Timothy,
>
> >I am looking forward to 5.27beta! It has a lot of good improvements.
>
> As I suggested, the migration to testing has started today. I'm holding
> off f
On Sat, 28 Jan 2023 10:41:38 -0500
Timothy M Butterworth wrote:
Hello Timothy,
>I am looking forward to 5.27beta! It has a lot of good improvements.
As I suggested, the migration to testing has started today. I'm holding
off for a few days to be sure (well, as sure as I can be) that
everything
On Sat, Jan 28, 2023 at 7:50 AM Brad Rogers wrote:
> On Sat, 28 Jan 2023 05:04:59 -0500
> Timothy M Butterworth wrote:
>
> Hello Timothy,
>
> >This appears to be a KDE issue. Is anyone else having this problem?
> >Please note the problem started after installing KF5-102 and a reboot.
>
> KDE Pla
On Sat, 28 Jan 2023 05:04:59 -0500
Timothy M Butterworth wrote:
Hello Timothy,
>This appears to be a KDE issue. Is anyone else having this problem?
>Please note the problem started after installing KF5-102 and a reboot.
KDE Plasma is undergoing big changes ATM. Soon(1) Plasma 5.27beta
(2) will
On Sat, 28 Jan 2023 07:37:01 -0500
Timothy M Butterworth wrote:
Hello Timothy,
>I forgot to mention that I am using Bookworm.
It *was* in the subject header. :-)
--
Regards _ "Valid sig separator is {dash}{dash}{space}"
/ ) "The blindingly obvious is never immediately
On Sat, Jan 28, 2023 at 5:04 AM Timothy M Butterworth <
timothy.m.butterwo...@gmail.com> wrote:
> All,
>
> I just upgraded to the 1/28/23 updates to KF5 102 and now I have no audio
> devices found. My USB headset is plugged in but KDE does not see it.
>
I forgot to me
All,
I just upgraded to the 1/28/23 updates to KF5 102 and now I have no audio
devices found. My USB headset is plugged in but KDE does not see it.
lsusb lists my USB headphones:
Bus 001 Device 009: ID 046d:0a37 Logitech, Inc. USB Headset H540
lspci lists my audio devices
04:00.5 Multimedia
itions be better than the block device itself? They're like
> > an
> > additional layer and what could be faster and easier than directly using the
> > block devices?
> >
> >
> hurts my eyes to see such desinformation circulating.
What's wrong about it?
On Thu, Sep 15, 2022 at 01:30:11AM -0400, Chuck Zmudzinski wrote:
bug report to try to fix it, except for the suggestion that a Debian kernel
developer made to increase the uevent buffer size in the kernel over a year
ago and another suggestion from another Debian maintainer or developer who
gave
Hello,
There are some devices that when present will cause the "coldplug all devices"
stage at boot to fail. On a normally installed system only an error is reported
in the journal and logs during boot but the system boots normally and the
device also functions normally. But on debian
On Tue, Mar 08, 2022 at 06:48:07PM -0600, Tom Browder wrote:
[...]
>
> Can anyone suggest a good way to get my Linux (or Windows) pictures onto
> some site that Apple devices can use?
>
I would suggest something like nextcloud.
https://nextcloud.com/
It's like running your own
Le mercredi 9 mars 2022 à 03:20:06 UTC+1, Tom Browder a écrit :
> On Tue, Mar 8, 2022 at 18:58 Jeremy Ardley wrote:
> ...
> Put the photos into several large zip files (simply to minimise the
> number of downloads). Then upload to google drive in some directory and
> use the share option on the
On Tue Mar 8 20:20:41 2022 Tom Browder wrote:
> Most of my relatives now have Apple devices, and we can share photos
> and videos among ourselves.
>
> I, on my Linux computer, have about 32 Gb of slides I digitized some
> years ago (they are also duplicated on my Windows comp
On Tue, Mar 8, 2022 at 18:58 Jeremy Ardley wrote:
...
Put the photos into several large zip files (simply to minimise the
> number of downloads). Then upload to google drive in some directory and
> use the share option on the directory to give an https URL you can send
> your relatives.
>
Thanks
On 9/3/22 8:48 am, Tom Browder wrote:
Can anyone suggest a good way to get my Linux (or Windows) pictures
onto some site that Apple devices can use?
Thanks,
-Tom
Put the photos into several large zip files (simply to minimise the
number of downloads). Then upload to google drive in
Most of my relatives now have Apple devices, and we can share photos and
videos among ourselves.
I, on my Linux computer, have about 32 Gb of slides I digitized some years
ago (they are also duplicated on my Windows computer). I have a Google
account that currently has 100 Gb of storage. I also
Hi,
I'm providing more information and answering my own question (for my
laptop's installation).
On Mar/03/2022, David Wright wrote:
> On Thu 03 Mar 2022 at 10:00:09 (+0100), Carles Pina i Estany wrote:
> >
> > My desktop computer (Debian 11.2) auto-mounts USB dev
On Thu 03 Mar 2022 at 10:00:09 (+0100), Carles Pina i Estany wrote:
>
> My desktop computer (Debian 11.2) auto-mounts USB devices (hard disks,
> etc.)
That doesn't help a great deal because there are several automounters
available in Debian.
> I would like the devices to be mou
Hi,
On Mar/03/2022, Brian wrote:
> On Thu 03 Mar 2022 at 10:00:09 +0100, Carles Pina i Estany wrote:
>
> >
> > Hi,
> >
> > My desktop computer (Debian 11.2) auto-mounts USB devices (hard disks,
> > etc.)
> >
> > I would like the devices to be
On Thu 03 Mar 2022 at 10:00:09 +0100, Carles Pina i Estany wrote:
>
> Hi,
>
> My desktop computer (Debian 11.2) auto-mounts USB devices (hard disks,
> etc.)
>
> I would like the devices to be mounted in read only mode by default. I
> will remount them in rw if I need
Hi,
My desktop computer (Debian 11.2) auto-mounts USB devices (hard disks,
etc.)
I would like the devices to be mounted in read only mode by default. I
will remount them in rw if I need to.
They are not in my /etc/fstab
I've been looking at udev configuration files, rules, etc. bu
On Wed, Feb 23, 2022 at 3:15 AM Tixy wrote:
>
> Sorry, I know nothing about all this, I just got curious about your
> problem and looked at the source code.
>
>
Wow. That's quite impressive Tixy. I would not even know where to begin
looking! Thank you for all that leg work. I will be looking
On Tue, 2022-02-22 at 22:32 -0600, Flacusbigotis wrote:
[...]
>
> Feb 22 17:26:11 server1 kernel: [ 205.693604] ax88179_178a 5-1:1.0
> enx001122334455: Failed to read reg index 0x: -22
>
> And as you can see in those logs there is an issue with xhci_hcd on
> this
> card and later the USB eth
> I did not have this problem in Debian 10. I do not know if the card's
driver has changed between the two versions of Debian, so I am going to
boot into a Debian 10 live image and see if it displays the same behavior.
Good news: I verified that this whole thing is indeed introduced in Debian
11
Hi.
On Tue, Feb 22, 2022 at 10:56:43AM -0600, Nicholas Geovanis wrote:
> > It's possible, of course. What's also possible is card's EEPROM may have
> > gone haywire. I had a similar problem back in the day with rtl8139 NIC,
> > IIRC. One day the thing simply started to assign itself a rand
may have to create an appropriate directory, and the file name has
> > > to start with double zeroes.
> > >
> > > 2) Invoke (really needed):
> > >
> > > update-initramfs -k all -u
> > >
> > > 3) Reboot.
> > >
> > > 4
river=ax88179_178a
> >
> > [Link]
> > MACAddressPolicy=none
> > NamePolicy=kernel
> >
> > You may have to create an appropriate directory, and the file name has
> > to start with double zeroes.
> >
> > 2) Invoke (really needed):
> >
&g
e has
> to start with double zeroes.
>
> 2) Invoke (really needed):
>
> update-initramfs -k all -u
>
> 3) Reboot.
>
> 4) Watch your network interface is called usb0 from now then.
>
>
> Thanks!
> Now, this approach has its caveats, so:
>
> 1) If you ever plug-i
(really needed):
update-initramfs -k all -u
3) Reboot.
4) Watch your network interface is called usb0 from now then.
Now, this approach has its caveats, so:
1) If you ever plug-in two USB devices that both served with
"ax88179_178a" - you won't be able to distinguish between
Thanks Reco & Greg. I did see the
/lib/systemd/network/73-usb-net-by-mac.link file. Thanks for that.
I don't know exactly what is happening, but the MAC address of the device
keeps changing after an ifdown/ifup cycle post boot. When the device
boots up, it comes up with its own real MAC, but it
On Wed, Feb 16, 2022 at 05:30:17PM +0300, Reco wrote:
> Hi.
>
> On Wed, Feb 16, 2022 at 03:55:21AM -0600, Flacusbigotis wrote:
> > Back in Debian Buster, I learned that the "predictive" naming of this USB
> > ethernet interface would be governed by "73-usb-net-by-mac.rules" and so I
> > had
Hi.
On Wed, Feb 16, 2022 at 03:55:21AM -0600, Flacusbigotis wrote:
> Back in Debian Buster, I learned that the "predictive" naming of this USB
> ethernet interface would be governed by "73-usb-net-by-mac.rules" and so I
> had it configured accordingly with a config file in
> /etc/network/i
My internet connection is off the ethernet port of a PCI-E card that also
has USB ports on it, so the ethernet device is recognized as a "USB
ethernet device"...
Back in Debian Buster, I learned that the "predictive" naming of this USB
ethernet interface would be governed by "73-usb-net-by-mac.rul
"Andrew M.A. Cater" writes:
> On Sat, Jan 08, 2022 at 06:52:32PM +, Richmond wrote:
>> I am currently running Debian 10.
>>
>> sudo lspci|grep VGA
>> 01:05.0 VGA compatible controller: Advanced Micro Devices,
>> Inc. [AMD/ATI] RS780 [Radeon
On Sat, Jan 08, 2022 at 06:52:32PM +, Richmond wrote:
> I am currently running Debian 10.
>
> sudo lspci|grep VGA
> 01:05.0 VGA compatible controller: Advanced Micro Devices,
> Inc. [AMD/ATI] RS780 [Radeon HD 3200]
>
> sudo xrandr
>
> Screen 0: minimum 320 x 200,
I am currently running Debian 10.
sudo lspci|grep VGA
01:05.0 VGA compatible controller: Advanced Micro Devices,
Inc. [AMD/ATI] RS780 [Radeon HD 3200]
sudo xrandr
Screen 0: minimum 320 x 200, current 1440 x 900, maximum 8192 x 8192
VGA-0 connected primary 1440x900+0+0 (normal left inverted
Andrei POPESCU wrote:
>
> Maybe the BIOS / UEFI Firmware has options for this?
The solution was found by "acpitool -w".
Several of the devices were enabled at my host.
By try&error I figured out which one is my keyboard (XHC1) and which one
my mouse (PTXH).
I
On Lu, 13 dec 21, 16:22:17, Klaus Singvogel wrote:
>
> Hello,
>
> my brand new computer (amd64, Bullseye) can be suspended to ACPI Mode S3 by
> "acpitool -s" under Debian.
>
> But whenever the USB mouse is moved (even a jiggle is enough) or the USB
> keyboard a key is hit, the computer wakes u
per device in the system settings:
https://ibb.co/5YhPYBs
https://ibb.co/XzGwmZr
(I'm sorry to offer screenshots only in German)
How can this wakeup behaviour by USB devices be disabled under Debian?
Thanks in advance.
Best regards,
Klaus.
--
Klaus Singvogel
GnuPG-Key-ID: 1024R/50
lty was using play rather than sox.
According to the manual, play doesn't have outfile. Hence the
monkeying with shell and environment variables. Better to use sox and
specify outfile directly.
I'll hypothesize that alsa devices aren't represented in /dev/.
According to
https://en
nose!"
> > (When I write a script, I try to be as explicit as
> > possible, avoiding short-cuts, abbreviations, assumptions, etc.)
>
> Absolutely good policy. I try to follow it also but tend to fail. =8~)
>
> > sox /home/peter/a42.WAV -t alsa default
>
&g
WAV -t alsa non-default
Devices were reported here.
https://lists.debian.org/debian-user/2021/07/msg01272.html
Thx, ... P.
--
48.7693 N 123.3053 W
mobile: +1 778 951 5147
VoIP: +1 604 670 0140
> sox /home/peter/a42.WAV -t alsa default
Good.
The machine here has sound hardware on the system board. Also it can
have a PCI sound card. Sound devices reported here.
https://lists.debian.org/debian-user/2021/07/msg01272.html
Assume speakers are plugged to output on the system board; he
On Wed, 29 Sept 2021 at 16:57, wrote:
> On Tue, Sep 28, 2021 at 02:31:18PM -0700, pe...@easthope.ca wrote:
> > I haven't set a shell. According to https://wiki.debian.org/Shell
> > it's bash.
> It might be willing to tell you:
> echo $SHELL
I wouldn't give that advice, it's rather misleading
On Tue, Sep 28, 2021 at 02:31:18PM -0700, pe...@easthope.ca wrote:
> From: Greg Wooledge
> Date: Tue, 28 Sep 2021 13:32:02 -0400
> > Are you in csh/tcsh?
>
> I haven't set a shell. According to https://wiki.debian.org/Shell
> it's bash.
It might be willing to tell you:
echo $SHELL
alsamixer is an ncurses mixer program for use with the ALSA soundcard
>drivers. It supports multiple soundcards with multiple devices."
>
> A terminal with an ncurses display is necessary to listen to an audio message?
No, you'd use alsamixer where you were taking an act
On Tue, Sep 28, 2021 at 02:31:18PM -0700, pe...@easthope.ca wrote:
> From: Greg Wooledge
> Date: Tue, 28 Sep 2021 13:32:02 -0400
> > Are you in csh/tcsh?
>
> I haven't set a shell. According to https://wiki.debian.org/Shell
> it's bash.
Do not guess. Do not assume defaults are in pla
ffect the play command).
If the sound card is replaced, will try this sort of thing.
setenv AUDIODEV=plughw:CARD=ICH5,DEV=0 ; play a42.WAV
with present /dev/ names I guess something similar to this is out of
the question.
sox a42.WAV /dev/snd/bl
Device names are used for storage devices and
It supports multiple soundcards with multiple devices."
A terminal with an ncurses display is necessary to listen to an audio message?
Now that the PCI sound card is gone, disambiguation appears to be unnecessary.
This command works.
play a42.WAV
Something odd in the sox manual.
-d,
I've reordered this reply to get rid of top posting...
On Tue, 2021-09-28 at 17:38 +, Nils wrote:
> Am 28. September 2021 19:32:02 MESZ schrieb Greg Wooledge <
> g...@wooledge.org>:
> > On Tue, Sep 28, 2021 at 08:19:26AM -0700, pe...@easthope.ca wrote:
> > > > CONCLUSIONS
> > > >
> > > > Audi
I agree. In the "normal" shells, you need to use "export" instead of "set"!
Am 28. September 2021 19:32:02 MESZ schrieb Greg Wooledge :
>On Tue, Sep 28, 2021 at 08:19:26AM -0700, pe...@easthope.ca wrote:
>> > CONCLUSIONS
>> >
>> > Audio messages can be interpreted. Eg.,
>> > set AUDIODEV=plughw:
On Tue, Sep 28, 2021 at 08:19:26AM -0700, pe...@easthope.ca wrote:
> > CONCLUSIONS
> >
> > Audio messages can be interpreted. Eg.,
> > set AUDIODEV=plughw:CARD=ICH5,DEV=0; play m94.WAV
>
> Hasty reply. In further use, didn't always work. I removed the PCI
> sound card, removed the plastic cov
sockets on the system
> board and connected speakers. Subsequently commands such as this
> always work.
>
> set AUDIODEV=plughw:CARD=ICH5,DEV=0 ; play a42.WAV
>
> SPECULATION
>
> The PCI card was meant to give better quality sound and was operated
> properly by the Windows
CULATION
The PCI card was meant to give better quality sound and was operated
properly by the Windows system present when the machine was sold by
Dell. When multiple sound devices exist, Linux still doesn't identify
devices properly.
REVISED CONCLUSION
Upstream documentation relating
The Subject of my preceding message was a blunder.
System board and PCI sound hardware
From: pe...@easthope.ca
Date: Thu, 29 Jul 2021 20:20:16 -0700
> Got sound from the Intel device on the system board. Oddly enough
> there was a plastic cover over the sockets on the chassis back. Pr
. =8~(
peter@joule:/home/peter$ set AUDIODEV=plughw:CARD=ICH5,DEV=0; play m94.WAV
play WARN alsa: can't encode 0-bit Unknown or not applicable
In spite of the warning, sound is produced. Good! Might have a
reliable way to hear voice messages.
CONCLUSIONS
Audio messages can be interpre
On Fri, Jul 30, 2021 at 05:55:43AM -0700, pe...@easthope.ca wrote:
> From: Reco
> Date: Fri, 30 Jul 2021 08:56:04 +0300
> > You could've started a new thread as well.
>
> For sure at least one reader would think "#$%&*, there he goes; another
> thread broken!"
Broken threads are usual
From: Reco
Date: Fri, 30 Jul 2021 08:56:04 +0300
> You could've started a new thread as well.
For sure at least one reader would think "#$%&*, there he goes; another thread
broken!"
> aplay -L
> arecord -L
peter@joule:/home/peter$ aplay -L
null
Discard all samples (playback) or ge
Hi.
On Thu, Jul 29, 2021 at 08:20:16PM -0700, pe...@easthope.ca wrote:
> From: Reco , Sun, 20 Oct 2019 20:57:52 +0300
> > So, does it work?
>
> Got sound from the Intel device on the system board. Oddly enough
> there was a plastic cover over the sockets on the chassis back. Pried
> i
eed
Mostly consistent with visible hardware. Really just one USB.
Odd that the Intel device refers to both ICH4 & ICH5.
root@joule:~# alsactl init
Found hardware: "ICH4" "Analog Devices AD1980" "AC97a:41445370" "0x1028"
"0x0155"
Initi
On Tue, Jul 06, 2021 at 11:06:22PM -0400, Stefan Monnier wrote:
> > I'm aware of that. My critique was specific to the "we take it out
> > because it's dangerous to the user" part.
>
> That's often an explanation but not the main motivation.
That would be even worse :)
The reason I'm "in" free s
> I'm aware of that. My critique was specific to the "we take it out
> because it's dangerous to the user" part.
That's often an explanation but not the main motivation.
For the `none` cipher, I think it was, tho.
IIRC the problem was that using the `none` cipher causes the
authentication to be e
>> It's entirely too common for obsolete encryption options that are
>> kept for "compatibility" end up being a vector for compromise, and
>> entirely reasonable to remove such options in order to provide the
>> most secure and maintainable tool for the vast majority of users.
> That's the attitude
>> If they have buffer overflow-style holes, those should be fixed.
>> Other than that I can't see how they can be less secure than the "none"
>> cipher.
> I guess since the "none" cipher isn't supported in debian's ssh
Good point.
> you will just drop this questionable line of argument?
It jus
On 7/6/21, Ralph Aichinger wrote:
> Hi, everybody, as a bullseye user I am seeing messages like
>
> | Unable to negotiate with 10.0.17.52 port 22: no matching
> | key exchange method found. Their offer: diffie-hellman-group1-sha1
>
> with increasing frequency, especially when trying to ssh into
>
I have a slightly different question about this issue.
when open ssh decided that dh keys, for public and global use were somehow
insecure, the ssh tool I use, sshdos, became limited allowing me to reach
shellworld, but not say the Linux shell provided with our office dreamhost
account any lon
On Tue, Jul 06, 2021 at 05:30:27PM -0400, Stefan Monnier wrote:
[...]
> > That's the attitude of authoritarian software: "my software is smarter
> > than you".
>
> I think the reality is a bit more subtle ;-)
>
> In most cases, the real driver is a desire to keep the code simple and
> to ease m
On Tue, Jul 06, 2021 at 04:45:50PM -0400, Michael Stone wrote:
[...]
> This is ridiculous [...]
Let's simply agree to differ.
Cheers
- t
signature.asc
Description: Digital signature
>> I think the first reaction should be to report it as a bug, so that the
>> old cipher is re-added. I think the same argument in favor of including
>> the "none" cipher should apply to including old deprecated ciphers.
> The old ciphers are generally removed for a reason: because they are hugely
On Tue, Jul 06, 2021 at 10:18:44PM +0200, to...@tuxteam.de wrote:
On Tue, Jul 06, 2021 at 02:11:21PM -0400, Michael Stone wrote:
[...]
It's entirely too common for obsolete encryption options that are
kept for "compatibility" end up being a vector for compromise, and
entirely reasonable to rem
On Tue, Jul 06, 2021 at 02:11:21PM -0400, Michael Stone wrote:
[...]
> It's entirely too common for obsolete encryption options that are
> kept for "compatibility" end up being a vector for compromise, and
> entirely reasonable to remove such options in order to provide the
> most secure and main
> Like you, I have been using CLI options to the ssh command to adjust the
> necessary algorithms if I need something "insecure".
You should be able to set that option for a specific (set of) hosts in
.ssh/config so you don't have to repeat it on the CLI every time.
> My thought is that once that
On Tue, Jul 06, 2021 at 03:20:43PM -0400, Stefan Monnier wrote:
If they have buffer overflow-style holes, those should be fixed.
Other than that I can't see how they can be less secure than the "none" cipher.
I guess since the "none" cipher isn't supported in debian's ssh
Good point.
you wil
On Tue, Jul 06, 2021 at 02:16:53PM -0400, Roberto C. Sánchez wrote:
Of course, the real answer is to not purchase products with "secure"
management that can't be upgraded when it becomes "insecure" management.
Sadly, this is not always possible. There are times where someone else
decides what
On Tue, Jul 06, 2021 at 02:11:21PM -0400, Michael Stone wrote:
>
> If you want ancient crypto options, just run an ancient binary. They're very
> easy to find in archive.debian.org.
>
Thankfully, Debian makes this sort of thing about as painless as it can
be.
> Of course, the real answer is to n
1 - 100 of 1536 matches
Mail list logo
