Re: how2 format a flash drive
Hello, On Tue, Jun 25, 2024 at 09:53:41AM -0400, Lee wrote: > My question is: how do I reformat the flash drive so it's usable as a > "normal" flash drive again? Nowadays, people rarely "format" (*) their "drives". They create filesystems on raw devices. For example `mkfs.ext4 /dev/sdX`, where /dev/sdX is the raw device corresponding to your USB key (see the lsblk command, for example). > Nothing I tried worked.. I ended up putting the thumb drive in a > Windows machine and formatting it there; it would be nice to know how > to restore the thumb drive to working order on Debian. However, for Microsoft compatibility, in addition, you will need a partition table. Linux, except for booting (because of BIOS requirements), does not require partition tables. So, first create a partition e.g. with fdisk[1]: this will make /dev/sdX1 available in lsblk. Then again, for Microsoft compatibility, you need to create a Microsoft-compatible filesystem. One good alternative is VFAT. Thus with `mkfs.vfat /dev/sdX1`. Please double-check you use the right raw device name, as fdisk and mkfs commands are destructive. (*) actually the last time I did format a device using a SCSI command was in the nineties -- some people differentiate "low-level formatting" with "high-level formatting", which is better called "creating a filesystem" -- yes back then it was sometimes useful to reformat using 256 bytes/sector for RAID0 applications :) [1] https://www.digitalocean.com/community/tutorials/create-a-partition-in-linux
Re: Debian 11 and IPv4 static IP address
Hello, On Sat, Jul 06, 2024 at 12:49:32PM +0200, Detlef Vollmann wrote: > The only thing that's always annoying is that too many programs > believe they have to overwrite /etc/resolv.conf... chattr +i # immutable still works :)
Re: Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot
Hello, On Wed, May 22, 2024 at 05:03:34PM -0400, Stefan Monnier wrote: > Hmm... I've been using a "plain old partition" for /boot (with > everything else in LVM) for "ever", originally because the boot loader > was not able to read LVM, and later out of habit. I was thinking of > finally moving /boot into an LV to make things simpler, but I see that > it'd still be playing with fire grub supports, for a long time: - / on LVM, with /boot within that filesystem - /boot on LVM, separately (it also worked with LILO, because LILO would record the exact address where the kernel & initrd was, regardless of abstractions layers :->) Recently, I have been playing with RAID-on-LVM (I was mostly using LVM on md before, which worked with grub), and it works too. Where grub fails, is if you have /boot on the same LVM volume group where any of the LVs "before him in order" have: - dm-integrity - specific metadata So yes, any advanced setup might break grub, and so the easiest is to have /boot on its separate partition again for the time being. Which makes two partitions of you also have an UEFI. > (AFAICT booting off of LVM was still not > supported by U-Boot either last time I checked). No idea about that one, sorry.
Re: Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot
Hello, On Wed, May 22, 2024 at 10:13:06AM +, Andy Smith wrote: > metadata tags to some PVs prevented grub from assembling them, grub is indeed very fragile if you use dm-integrity anywhere on any of your LVs on the same VG where /boot is (or at least if in the list of LVs, the dm-integrity protected ones come first). I guess it's a general problem how grub2 parses LVM, yes, as soon as their are special things going on, it somehow breaks. However, if you don't have /boot on LVM, hand-fixing grub2 can be trivial, e.g. here on another system with /boot/efi on 1st disk's first partition and /boot on 2nd disk's first partition. linux (hd1,1)vmlinuz-5.10.0-29-amd64 root=/dev/mapper/vg1-root ro quiet initrd (hd1,1)initrd.img-5.10.0-29-amd64 boot (you even have completions in grub's interactive boot system) and it boots. Next step: I am going to make me a USB boot key for that system, in case (first using a simple mount of two partitions of the USB key on /boot, respectively /boot/efi (vfat), then update-grub, or if it breaks, completely by hand like above -- I have been using syslinux for the last 20 years or so for that purpose, but it gets apparently too complicated with Secure Boot and stuff). PS: I have from now on decided I will always use a /boot no longer on LVM but on a separate partition, like the /boot/efi, it seems, indeed, much less fragile. Aka, back to what I was doing a few years ago before my confidence in grub2 got apparently too high :)
Re: Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot
Hello, On Wed, May 22, 2024 at 08:57:38AM +0200, Marc SCHAEFER wrote: > I will try this work-around and report back here. As I said, I can > live with /boot on RAID without dm-integrity, as long as the rest can be > dm-integrity+raid protected. So, enable dm-integrity on all LVs, including /, /var/lib/lxc, /scratch and swap, now boots without any issue with grub2 as long as /boot is NOT on the same VG where the dm-integrity over LVM RAID is enabled. This is OK for me, I don't need /boot on dm-integrity. update-grub gives out warning for every of the rimage subvolumes, but can still then reboot. I would guess the bug is thus in grub2, not yet supporting boot on a /boot not necessarily dm-integrityfied itself, but on a VG where any of the LV is. Are readers seconding conclusion? If yes, I could report a bug on grub2. Have a nice day. Details: root@ds-03:~# lvs -a LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert docker vg1 rwi-aor--- 500.00g 100.00 [docker_rimage_0]vg1 gwi-aor--- 500.00g [docker_rimage_0_iorig] 100.00 [docker_rimage_0_imeta] vg1 ewi-ao <4.07g [docker_rimage_0_iorig] vg1 -wi-ao 500.00g [docker_rimage_1]vg1 gwi-aor--- 500.00g [docker_rimage_1_iorig] 100.00 [docker_rimage_1_imeta] vg1 ewi-ao <4.07g [docker_rimage_1_iorig] vg1 -wi-ao 500.00g [docker_rmeta_0] vg1 ewi-aor--- 4.00m [docker_rmeta_1] vg1 ewi-aor--- 4.00m root vg1 rwi-aor--- 10.00g 100.00 [root_rimage_0] vg1 gwi-aor--- 10.00g [root_rimage_0_iorig] 100.00 [root_rimage_0_imeta]vg1 ewi-ao 148.00m [root_rimage_0_iorig]vg1 -wi-ao 10.00g [root_rimage_1] vg1 gwi-aor--- 10.00g [root_rimage_1_iorig] 100.00 [root_rimage_1_imeta]vg1 ewi-ao 148.00m [root_rimage_1_iorig]vg1 -wi-ao 10.00g [root_rmeta_0] vg1 ewi-aor--- 4.00m [root_rmeta_1] vg1 ewi-aor--- 4.00m scratch vg1 rwi-aor--- 10.00g 100.00 [scratch_rimage_0] vg1 gwi-aor--- 10.00g [scratch_rimage_0_iorig] 100.00 [scratch_rimage_0_imeta] vg1 ewi-ao 148.00m [scratch_rimage_0_iorig] vg1 -wi-ao 10.00g [scratch_rimage_1] vg1 gwi-aor--- 10.00g [scratch_rimage_1_iorig] 100.00 [scratch_rimage_1_imeta] vg1 ewi-ao 148.00m [scratch_rimage_1_iorig] vg1 -wi-ao 10.00g [scratch_rmeta_0]vg1 ewi-aor--- 4.00m [scratch_rmeta_1]vg1 ewi-aor--- 4.00m swap vg1 rwi-aor--- 8.00g 100.00 [swap_rimage_0] vg1 gwi-aor--- 8.00g [swap_rimage_0_iorig] 100.00 [swap_rimage_0_imeta]vg1 ewi-ao 132.00m [swap_rimage_0_iorig]vg1 -wi-ao 8.00g [swap_rimage_1] vg1 gwi-aor--- 8.00g [swap_rimage_1_iorig] 100.00 [swap_rimage_1_imeta]vg
Re: Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot
Additional info: On Wed, May 22, 2024 at 08:49:56AM +0200, Marc SCHAEFER wrote: > Having /boot on a LVM non enabled dm-integrity logical volume does not > work either, as soon as there is ANY LVM dm-integrity enabled logical > volume anywhere (even not linked to booting), grub2 complains (at boot > time or at update-grub) about the rimage LV. I found this [1], quoting: "I'd also like to share an issue I've discovered: if /boot's partition is a LV, then there must not be a raidintegrity LV anywhere before that LV inside the same VG. Otherwise, update-grub will show an error (disk `lvmid/.../...' not found) and GRUB cannot boot. So it's best if you put /boot into its own VG. (PS: Errors like unknown node '..._rimage_0 can be ignored.)" So, the work-around seems to be to simple have /boot not on a LVM VG where any LV has dm-integrity enabled. I will try this work-around and report back here. As I said, I can live with /boot on RAID without dm-integrity, as long as the rest can be dm-integrity+raid protected. [1] https://unix.stackexchange.com/questions/717763/lvm2-integrity-feature-breaks-lv-activation
Re: Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot
Hello, On Tue, May 21, 2024 at 08:41:58PM +0200, Franco Martelli wrote: > I can only recommend you to read carefully the Wiki: > https://raid.wiki.kernel.org/index.php/Dm-integrity I did, and it looks it does not seem to document anything pertaining to my issue: 1) I don't use integritysetup (from LUKS), but LVM RAID PVs -- I don't use LUKS encryption anyway on that system 2) the issue is not the kernel not supporting it, because when the system is up, it works (I have done tests to destroy part of the underlying devices, they get detected and fixed correctly) 3) the issue is not with the initrd -- I added the dm-integrity module and rebuilt the initrd (and actually the bug happens before grub2 loads the kernel & init) -- or at least "not yet"! maybe this will fail later :) 4) actually the issue is just grub2, be it when the system is up (it complains about the special subvolumes) or at boot time Having /boot on a LVM non enabled dm-integrity logical volume does not work either, as soon as there is ANY LVM dm-integrity enabled logical volume anywhere (even not linked to booting), grub2 complains (at boot time or at update-grub) about the rimage LV.
Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot
Hello, 1. INITIAL SITUATION: WORKS (no dm-integrity at all) I have a Debian bookwork uptodate system that boots correctly with kernel 6.1.0-21-amd64. It is setup like this: - /dev/nvme1n1p1 is /boot/efi - /dev/nvme0n1p2 and /dev/nvme1n1p2 are the two LVM physical volumes - a volume group, vg1 is built with those PVs vg1 has a few LVs that have been created in RAID1 LVM mode: lvdisplay | egrep 'Path|Mirrored' LV Path/dev/vg1/root <-- this is / Mirrored volumes 2 LV Path/dev/vg1/swap Mirrored volumes 2 LV Path/dev/vg1/scratch Mirrored volumes 2 LV Path/dev/vg1/docker Mirrored volumes 2 As said, this boots without any issue. 2. ADDING dm-integrity WHILE BOOTED: works! Now, while booted, I can add dm-integrity to one of the volumes, let's say /dev/vg1/docker (this LV has absolutely no link with the boot process, except obviously it is listed in /etc/fstab -- it also fails the same way if even the swap is dm-integrit enabled, or /): lvconvert --raidintegrity y --raidintegritymode bitmap vg1/docker and wait a bit til the integrity is setup with lvs -a (100%) Obviously, this creates and uses a few rimage/rmeta sub LVs. Then I did this (after having boot issues): echo dm_integrity >> /etc/initramfs-tools/modules update-initramfs -u This did not change the below issue: 3. grub BOOT FAILS IF ANY LV HAS dm-integrity, EVEN IF NOT LINKED TO / if I reboot now, grub2 complains about rimage issues, clear the screen and then I am at the grub2 prompt. Booting is only possible with Debian rescue, disabling the dm-integrity on the above volume and rebooting. Note that you still can see the rimage/rmeta sub LVs (lvs -a), they are not deleted! (but no dm-integrity is activated). 4. update-grub GIVES WARNINGS Now, if I try to start update-grub while booted AND having enabled dm-integrity on the vg1/docker volume, I get: # update-grub Generating grub configuration file ... Found linux image: /boot/vmlinuz-6.1.0-21-amd64 Found initrd image: /boot/initrd.img-6.1.0-21-amd64 error: unknown node 'docker_rimage_0'. [ ... many ... ] /usr/sbin/grub-probe: error: disk `lvmid/xLE0OV-wQy7-88H9-yKCz-4DUQ-Toce-h9rQvk/FzCf1C-95eB-7B0f-DSrF-t1pg-66qp-hmP3nZ' not found. error: unknown node 'docker_rimage_0'. [ ... many ... ] [ this repeats a few times ] Found linux image: /boot/vmlinuz-6.1.0-10-amd64 Found initrd image: /boot/initrd.img-6.1.0-10-amd64 Found memtest86+ 64bit EFI image: /boot/memtest86+x64.efi Warning: os-prober will not be executed to detect other bootable partitions. [ there are none ] Systems on them will not be added to the GRUB boot configuration. Check GRUB_DISABLE_OS_PROBER documentation entry. Adding boot menu entry for UEFI Firmware Settings ... done Any idea what could be the problem? Any way to just make grub2 ignore the rimage (sub)volumes at setup and boot time? (I could live with / aka vg1/root not using dm-integrity, as long as the data/docker/etc volumes are integrity-protected) ? Or how to make grub 100% compatible with a vg1/root using dm-integrity (that would be obviously the final goal!) Thank you for any pointers!
Re: HDD long-term data storage with ensured integrity
On Fri, May 03, 2024 at 01:50:52PM -0700, David Christensen wrote: > Thank you for devising a benchmark and posting some data. :-) I did not do the comparison hosted on github. I just wrote the script which tests the dm-integrity on dm-raid error detection and error correction. > FreeBSD also offers a layered solution. From the top down: I prefer this approach, indeed.
Re: HDD long-term data storage with ensured integrity
On Mon, Apr 08, 2024 at 10:04:01PM +0200, Marc SCHAEFER wrote:
> For off-site long-term offline archiving, no, I am not using RAID.
Now, as I had to think a bit about ONLINE integrity, I found this
comparison:
https://github.com/t13a/dm-integrity-benchmarks
Contenders are btrfs, zfs, and notably ext4+dm-integrity+dm-raid
I tend to have a biais favoring UNIX layered solutions against
"all-into-one" solutions, and it seems that performance-wise,
it's also quite good.
I wrote this script to convince myself of auto-correction
of the ext4+dm-integrity+dm-raid layered approach.
It gives:
[ ... ]
[ 390.249699] md/raid1:mdX: read error corrected (8 sectors at 21064 on dm-11)
[ 390.249701] md/raid1:mdX: redirecting sector 20488 to other mirror: dm-7
[ 390.293807] md/raid1:mdX: dm-11: rescheduling sector 262168
[ 390.293988] md/raid1:mdX: read error corrected (8 sectors at 262320 on dm-11)
[ 390.294040] md/raid1:mdX: read error corrected (8 sectors at 262368 on dm-11)
[ 390.294125] md/raid1:mdX: read error corrected (8 sectors at 262456 on dm-11)
[ 390.294209] md/raid1:mdX: read error corrected (8 sectors at 262544 on dm-11)
[ 390.294287] md/raid1:mdX: read error corrected (8 sectors at 262624 on dm-11)
[ 390.294586] md/raid1:mdX: read error corrected (8 sectors at 263000 on dm-11)
[ 390.294712] md/raid1:mdX: redirecting sector 262168 to other mirror: dm-7
pretty much convicing.
So after testing btrfs and being not convinced, after doing some test on
a production zfs -- not convinced either -- I am going to ry
ext4+dm-integrity+dm-raid.
#! /bin/bash
set -e
function create_lo {
local f
f=$(losetup -f)
losetup $f $1
echo $f
}
# beware of the rm -r below!
tmp_dir=/tmp/$(basename $0)
mnt=/mnt
mkdir $tmp_dir
declare -a pvs
for p in pv1 pv2
do
truncate -s 250M $tmp_dir/$p
l=$(create_lo $tmp_dir/$p)
pvcreate $l
pvs+=($l)
done
vg=$(basename $0)-test
lv=test
vgcreate $vg ${pvs[*]}
vgdisplay $vg
lvcreate --type raid1 --raidintegrity y -m 1 -L 200M -n $lv $vg
lvdisplay $vg
# sync/integrity complete?
sleep 10
cat /proc/mdstat
echo
lvs -a -o name,copy_percent,devices $vg
echo
echo -n Type ENTER
read ignore
mkfs.ext4 -I 256 /dev/$vg/$lv
mount /dev/$vg/$lv $mnt
for f in $(seq 1 10)
do
# ignore errors
head -c 20M < /dev/random > $mnt/f_$f || true
done
(cd $mnt && find . -type f -print0 | xargs -0 md5sum > $tmp_dir/MD5SUMS)
# corrupting some data in one PV
count=5000
blocks=$(blockdev --getsz ${pvs[1]})
if [ $blocks -lt 32767 ]; then
factor=1
else
factor=$(( ($blocks - 1) / 32767))
fi
p=1
for i in $(seq 1 $count)
do
offset=$(($RANDOM * $factor))
echo ${pvs[$p]} $offset
dd if=/dev/random of=${pvs[$p]} bs=$(blockdev --getpbsz ${pvs[$p]})
seek=$offset count=1
# only doing on 1, not 0, since we have no way to avoid destroying the same
sector!
#p=$((1 - p))
done
dd if=/dev/$vg/$lv of=/dev/null bs=32M
dmesg | tail
umount $mnt
lvremove -y $vg/$lv
vgremove -y $vg
for p in ${pvs[*]}
do
pvremove $p
losetup -d $p
done
rm -r $tmp_dir
Re: SOLVED (was: Re: using mbuffer: what am i doing wrong?)
On Thu, Apr 11, 2024 at 04:14:33PM +0200, DdB wrote:
> - the resulting transfer is way faster than say ... ssh.
AFAIK ssh is mono-threaded (like OpenVPN, unless you use the kernel
module). wireguard is multi-threaded.
The symptom will be one CPU ("core") at 100% and the rest mostly
idle.
Re: using mbuffer: what am i doing wrong?
Hello, On Tue, Apr 09, 2024 at 03:13:01PM +0200, DdB wrote: > from my research, the abbreviated takeaway is: I never used mbuffer, I use buffer combined with netcat-traditional: # receiver (TCP server on port 8000) nc -l -p 8000 | buffer -S 1048576 -s 32768 -o /dev/null # sender (TCP client on ephemeral port) nc localhost 8000 < /dev/zero I just installed mbuffer: mbuffer -I 8000 -o /dev/null mbuffer -i /dev/zero -O 127.0.0.1:8000 and it also works. > > sudo netstat | grep $port > to return nothing yes, but those work: netstat -a | grep :8000 netstat --listen | grep :8000 Maybe it's just that by default netstat only shows sockets in the ESTABLISHED state and not in the LISTEN state. > What am i doing wrong? If there is a timeout, I would suggest to investigate firewalls on the server side.
Re: HDD long-term data storage with ensured integrity
Hello, On Mon, Apr 08, 2024 at 11:28:04AM -0700, David Christensen wrote: > So, an ext4 file system on an LVM logical volume? > > Why LVM? Are you implementing redundancy (RAID)? Is your data larger than > a single disk (concatenation/ JBOD)? Something else? For off-site long-term offline archiving, no, I am not using RAID. No, it's not LVM+md, just plain LVM for flexibility. Typically I use 16 TB hard drives, and I tend to use one LV per data source, the LV name being the data source and the date of the copy. Or sometimes I just copy a raw volume (ext4 or something else) to a LV. With smaller drives (4 TB) I tend to not use LVM, just plain ext4 on the raw disk. I almost never use partitionning. However, I tend to use luks encryption (per ext4 filesystem) when the drives are stored off-site. So it's either LVM -> LV -> LUKS -> ext4 or raw disk -> LUKS -> ext4. You can find some of the scripts I use to automate this off-site long-term archiving here: https://git.alphanet.ch/gitweb/?p=various;a=tree;f=offsite-archival/LVM-LUKS
Re: HDD long-term data storage with ensured integrity
For offline storage: On Tue, Apr 02, 2024 at 05:53:15AM -0700, David Christensen wrote: > Does anyone have any comments or suggestions regarding how to use magnetic > hard disk drives, commodity x86 computers, and Debian for long-term data > storage with ensured integrity? I use LVM on ext4, and I add a MD5SUMS file at the root. I then power up the drives at least once a year and check the MD5SUMS. A simple CRC could also work, obviously. So far, I have not detected MORE corruption with this method than the drive ECC itself (current drives & buses are much better than they used to be). When I have errors detected, I replace the file with another copy (I usually have multiple off-site copies, and sometimes even on-site online copies, but not always). When the errors add up, it is time to buy another drive, usually after 5+ years or even sometimes 10+ years. So, just re-reading the content might be enough, once a year or so. This is for HDD (for SDD I have no offline storage experience, it could be shorter).
Re: making Debian secure by default
Hello, On Fri, Mar 29, 2024 at 07:02:54PM +0100, Kamil Jo?ca wrote: > O-o, is there any simple test to check if I have infected version or > not? For example, under root: path="$(ldd $(which sshd) | grep liblzma | grep -o '/[^ ]*')" if hexdump -ve '1/1 "%.2x"' "$path" | grep -q f30f1efa554889f54c89ce5389fb81e700804883ec28488954241848894c2410 then echo probably vulnerable else echo probably not vulnerable fi NB: always think and read before typing root commands, or any commands you find on a forum or mailing-list :) More info: https://boehs.org/node/everything-i-know-about-the-xz-backdoor Interesting read about social interactions https://www.openwall.com/lists/oss-security/2024/03/29/4 ref for the code above https://www.openwall.com/lists/oss-security/2024/03/29/23 idea to confine the sshd -> systemd dependancy, in a specific process, because of the huge systemd attack surface
Re: making Debian secure by default
Hello, On Wed, Mar 27, 2024 at 05:30:50PM -0400, Lee wrote: > Apparently the root of the security issue is that wall is a setguid program? a) wall must be able to write to your tty, which is not possible if wall is not installed setguid OR if people have sane permissions on their terminals (e.g. set to mesg n) b) in addition, for this exploit to run, command-not-found must be started with the not found command as argument: in the two Debian releases I just tried (buster and bookworm), with bash, command-not-found was not installed. The idea of the exploit is that you get a prompt for entering a sudo password, which is a simple text (which gets more convincing because of a recently introduced bug in wall which does not filter out terminal escape / control sequences), then you type the root password, which is presumably not the name of an existing command, so command-not-found PASSWORD is run, and someone on another terminal and user can do a ps to see that password argument if he is quick or polling. To fix this: a) don't type a root password / sudo password unless you know that it should happen b) don't allow others to write on your terminals, in particular if you run priviledged commands and expect sudo prompts c) patch wall so that its texts are always shown to be different from other program outputs (== filter out anything else than printable characters) THIS IS MY PREFERRED WORKAROUND :) (mixing controls (prompts) and data is always a very bad idea) d) don't have other users on your machine / use containers. > So. There is a program called 'mesg', hrmmm.. 30 years ago it was common practice to use wall (to signal stuff to users, e.g. used by shutdown(8)). > oof. Are there instructions somewhere on how to make Debian secure by > default? Looks like it is, by not installing command-not-found by default (apparently Ubuntu does). Presumably by chance.
Re: Debugging an USB array issue
Hello, On Fri, Mar 15, 2024 at 06:54:38PM +0100, to...@tuxteam.de wrote: > I may be stating the obvious, but have you made sure the USB hub > is providing enough power to keep your disks happy? It's a 60W external power supply, for 4 disks.
Re: Debugging an USB array issue
Hello, On Fri, Mar 15, 2024 at 01:30:08PM -0400, Dan Ritter wrote: > I have never had long-term happiness with multiple disks > connected via USB. I strongly recommend that you find a 4 or 8 > disk SATA/SAS PCIe card -- an LSI 2008, for example -- and connect > through that, instead. US prices are $40-45 new. Add $15 for an 8087-to-4xSATA > cable, you will have happiness for less than $75. Interesting. I will keep the idea in mind. I also had a prejudice against USB in the beginning. However: I have a similar disk array running 24h/24h for the last three years on a Debian buster with no problem. I am going to upgrade this system soon, so if there is something bad with bullseye's kernel I would love to learn about it :)
Debugging an USB array issue
Hello, on a Debian bullseye uptodate system [1], I experiment frequent (every 3-4 hours on heavy load) disk disconnections from a md RAID10 array with 4 drives connected to an USB 1M adapter [2]. Errors do not look like a timeout, but like a DMA error [3]. Immediately after, the disk reappears as a new drive name and can be re-added quickly to the md RAID array (I am doing those tests with a read-only mounted filesystem for obvious reasons). Initially, I was wondering if it was maybe a disk doing a too long recovery procedure, but it is to be noted that it's not always the same disk which has an error, and smartctl -a shows no recorded errors for any of the 4 drives [4]. The drives are connected to a SATA-to-USB enclosure [6]. This is on a 3.1 USB PCI-Express card [5]. I already applied this work-around (which does not seem to apply to a non-idle system): echo -1 > /sys/module/usbcore/parameters/autosuspend What would be your recommandations? I have thought about downgrading to a slower port (it should not be much different with 5000M), changing the cable, or maybe it's the enclosure? Or is this a known issue (maybe with the xhci_hd driver) and I should try another driver? Thank you for any idea or pointer. [1] Linux video 5.10.0-28-amd64 #1 SMP Debian 5.10.209-2 (2024-01-31) x86_64 GNU/Linux [2] /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 1M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 1M |__ Port 2: Dev 5, If 0, Class=Mass Storage, Driver=usb-storage, 5000M |__ Port 1: Dev 4, If 0, Class=Hub, Driver=hub/4p, 1M |__ Port 3: Dev 8, If 0, Class=Mass Storage, Driver=uas, 1M |__ Port 1: Dev 6, If 0, Class=Mass Storage, Driver=uas, 1M |__ Port 4: Dev 10, If 0, Class=Mass Storage, Driver=uas, 1M |__ Port 2: Dev 7, If 0, Class=Mass Storage, Driver=uas, 1M |__ Port 2: Dev 3, If 0, Class=Mass Storage, Driver=usb-storage, 5000M [3] Mar 15 17:08:06 video kernel: [ 6607.383180] xhci_hcd :01:00.0: WARN Set TR Deq Ptr cmd invalid because of stream ID configuration Mar 15 17:08:06 video kernel: [ 6607.386754] DMAR: DRHD: handling fault status reg 3 Mar 15 17:08:06 video kernel: [ 6607.386762] DMAR: [DMA Write] Request device [01:00.0] PASID fault addr f98be000 [fault reason 05] PTE Write access is not set Mar 15 17:08:06 video kernel: [ 6607.386774] sd 18:0:0:0: [sde] tag#5 data cmplt err -75 uas-tag 1 inflight: CMD Mar 15 17:08:06 video kernel: [ 6607.386780] sd 18:0:0:0: [sde] tag#5 CDB: Read(16) 88 00 00 00 00 01 5e 1d 88 00 00 00 01 00 00 00 Mar 15 17:08:06 video kernel: [ 6607.479406] xhci_hcd :01:00.0: WARN Event TRB for slot 12 ep 10 with no TDs queued? Mar 15 17:08:06 video kernel: [ 6607.479708] xhci_hcd :01:00.0: WARN Set TR deq ptr command for freed stream ID 38885 Mar 15 17:08:06 video kernel: [ 6607.510551] xhci_hcd :01:00.0: WARN Event TRB for slot 12 ep 10 with no TDs queued? [ ... many ... ] Mar 15 17:08:13 video kernel: [ 6614.443826] sd 18:0:0:0: [sde] tag#2 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD IN Mar 15 17:08:13 video kernel: [ 6614.443829] sd 18:0:0:0: [sde] tag#2 CDB: ATA command pass through(12)/Blank a1 08 2e d0 01 00 4f c2 00 b0 00 00 Mar 15 17:08:13 video kernel: [ 6614.457969] xhci_hcd :01:00.0: WARN Event TRB for slot 12 ep 10 with no TDs queued? Mar 15 17:08:13 video kernel: [ 6614.458274] xhci_hcd :01:00.0: WARN Set TR deq ptr command for freed stream ID 38885 [ ... many ... ] Mar 15 17:08:25 video kernel: [ 6626.497696] sd 18:0:0:0: [sde] tag#5 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=19s Mar 15 17:08:25 video kernel: [ 6626.497725] sd 18:0:0:0: [sde] tag#5 Sense Key : Illegal Request [current] Mar 15 17:08:25 video kernel: [ 6626.497731] sd 18:0:0:0: [sde] tag#5 Add. Sense: Invalid command operation code Mar 15 17:08:25 video kernel: [ 6626.497739] sd 18:0:0:0: [sde] tag#5 CDB: Read(16) 88 00 00 00 00 01 5e 1d 88 00 00 00 01 00 00 00 Mar 15 17:08:25 video kernel: [ 6626.497746] blk_update_request: critical target error, dev sde, sector 5873960960 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0 Mar 15 17:08:25 video kernel: [ 6626.497755] md/raid10:md0: sde: rescheduling sector 11747394560 Mar 15 17:08:25 video kernel: [ 6626.497801] usb 3-1.1.4: stat urb: no pending cmd for uas-tag 3 Mar 15 17:08:25 video kernel: [ 6626.497807] md/raid10:md0: sdd: redirecting sector 11747394560 to another mirror Mar 15 17:08:25 video kernel: [ 6626.519426] xhci_hcd :01:00.0: WARN Event TRB for slot 12 ep 10 with no TDs queued? Mar 15 17:08:25 video kernel: [ 6626.519719] xhci_hcd :01:00.0: WARN Set TR deq ptr command for freed stream ID 38885 Mar 15 17:08:25 video kernel: [ 6626.550583] xhci_hcd :01:00.0: WARN Event TRB for slot 12 ep 10 with no TDs queued? Mar 15 17:08:25 video kernel: [ 6626.550875] xhci_hcd :01:00.0: WARN Set TR deq ptr command for freed
Re: Bullseye debian security support?
Hello, On Wed, May 31, 2023 at 11:37:34AM -0700, John Conover wrote: > How long will Debian Bullseye have debian security team support after > Bookworm is announced? LTS planning is here: https://wiki.debian.org/LTS bullseye will be LTS-supported til june 2026 (not yet clearly defined), but will only be handed to LTS in july 2024: until then, it's normal security support.
buster docker has issue with bookworm container
Hello,
I had a few issues with building a bookworm container using the
debian:bookworm image (problems with repository signatures and lzma
decompression errors) on a buster docker host.
The buster and bullseye containers seem to work like a charm though.
So I went the bullseye -> upgrade to bookworm path with the Dockerfile
below. I apply a work-around in the Dockerfile ("fixing" the error with the
cleaning of the apt archives in /etc/apt/apt.conf.d/docker-clean), and
it fixed the repository GPG errors (it seems the /etc/apt/sources.list
in the debian:bookworm has direct key references that do not exist/do
not contain the correct keys).
But, the apparently last problem I can't seem to fix is the following:
dpkg-deb (subprocess): decompressing archive
'/var/cache/apt/archives/util-linux_2.38.1-5+b1_amd64.deb' (size=1176996)
member 'control.tar': lzma error: Cannot allocate memory
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
dpkg-deb: error: tar subprocess returned error exit status 2
dpkg: error processing archive
/var/cache/apt/archives/util-linux_2.38.1-5+b1_amd64.deb (--unpack): dpkg-deb
--control subprocess returned error exit status 2
dpkg-deb (subprocess): decompressing archive
'/var/cache/apt/archives/util-linux-extra_2.38.1-5+b1_amd64.deb' (size=110520)
member 'control.tar': lzma error: Cannot allocate memory
tar: This does not look like a tar archive
This is reproducible, this is not a transient error.
It seems as if libzma does not have enough RAM to do the decompression
here. I found notably an issue with 32 bit address space, but this is
amd64.
Also, the container has no specific limits (it is not better with
docker build -m 100g), and free reports:
totalusedfree shared buff/cache available
Mem: 4024628 940056 208924 16012 3152384 3084572
Swap:7811068 2 7755516
So, is this some libzma config somewhere, or maybe a missing / changed
syscall which makes libzma thinks it does not have enough memory?
If I try to decompress, manually, with ar, then xz the above util-linux
downloaded deb, on a buster and bullseye container and there is no
issue, which seems to exclude a problem with cgroup limitations that I
didn't see.
Do you have maybe any idea (except upgrading the host to bullseye or
bookworm)?
Thank you.
FROM debian:bullseye
ENV DEBIAN_FRONTEND noninteractive
RUN apt-get update && apt-get -y dist-upgrade \
&& sed -i 's/bullseye/bookworm/g' /etc/apt/sources.list \
&& rm -f /etc/apt/apt.conf.d/docker-clean \
&& apt-get update && apt-get -y upgrade \
&& echo update/upgrade done \
&& apt-get --purge -y autoremove \
&& echo purge done \
&& apt-get -y install procps \
&& free \
&& apt-get -y -u dist-upgrade \
&& echo dist-upgrade done \
&& apt-get install -y openssh-server rsyslog debian-goodies sudo vim
wget \
&& echo install done \
&& apt-get clean \
&& echo clean done
# disable klogd
RUN sed -i 's/^\(module.load="imklog"\)/#\1/' /etc/rsyslog.conf
# remove the privake key, will be generated by ds-admin ssh-base
# post-conf
# so that it is different for each VM
RUN rm /etc/ssh/ssh_host_*
COPY rc.local /etc/rc.local
RUN chmod 755 /etc/rc.local
# documentation
EXPOSE 22/tcp
CMD /etc/rc.local && tail -f /dev/null
Re: update-initramfs
On 4/10/2023 11:00 PM, David Wright wrote: On Mon 10 Apr 2023 at 20:17:11 (-0400), Marc Auslander wrote: I'm on Buster. In /boot I keep a copy of the current working linux named by appending -knowngood to the four files. My idea is that if an update fails, I have a recent working linux. This is different from vmlinuz.old which is the previous kernel version. The updates in question are not to the kernel but to initrd.image of course. Suddenly, update-initramfs insists in trying to first update initrd.-knowngood which of course fails because there are no underling file with that name. This never happened in the past, AFAIK. Once it fails it gives up. There seems no way to force update-initramfs to update the right kernel. Perhaps check that "all" hasn't been accidentally inserted: $ grep update /etc/initramfs-tools/update-initramfs.conf # Configuration file for update-initramfs(8) # update_initramfs [ yes | all | no ] # If set to all update-initramfs will update all initramfs # If set to no disables any update to initramfs beside kernel upgrade update_initramfs=yes $ A workaround: change the sort order of the backup initrd files by adding an appropriate prefix, like backup-knowngood-… so the "real" ones get updated first. Cheers, David. thanks but that's the first thing I checked - it's yes, not all. But my backup names contain the current version string. I'm not sure about the sort order hack. My goal is to have update-grub see the knowngood as a bootable linux and include it in the boot menu. That's also why .bak of initrd isn't good enough - I need a complete copy.
Re: update-initramfs
On 4/11/2023 9:30 AM, zithro wrote: On 11 Apr 2023 02:17, Marc Auslander wrote: I'm on Buster. In /boot I keep a copy of the current working linux named by appending -knowngood to the four files. My idea is that if an update fails, I have a recent working linux. This is different from vmlinuz.old which is the previous kernel version. The updates in question are not to the kernel but to initrd.image of course. In addition to what David wrote, why are you not using the backup facility of initramfs instead of doing it manually ? $ cat /etc/initramfs-tools/update-initramfs.conf [...] # # backup_initramfs [ yes | no ] # # Default is no # If set to no leaves no .bak backup files. backup_initramfs=yes [...] Suddenly, update-initramfs insists in trying to first update initrd.-knowngood which of course fails because there are no underling file with that name. This never happened in the past, AFAIK. Once it fails it gives up. There seems no way to force update-initramfs to update the right kernel. Ideas? RTFM ? :) The solution is in "man update-initramfs" : update-initramfs -c -k $KERNEL_VERSION -c creates a new initramfs -k specifies the version of the kernel This breaks when package update tries to update-initramfs. My copies have the kernel version in their names - with -knowngood appended.
update-initramfs
I'm on Buster. In /boot I keep a copy of the current working linux named by appending -knowngood to the four files. My idea is that if an update fails, I have a recent working linux. This is different from vmlinuz.old which is the previous kernel version. The updates in question are not to the kernel but to initrd.image of course. Suddenly, update-initramfs insists in trying to first update initrd.-knowngood which of course fails because there are no underling file with that name. This never happened in the past, AFAIK. Once it fails it gives up. There seems no way to force update-initramfs to update the right kernel. Ideas?
Re: exim4 smarthost selection based on sender
On 11/27/2022 12:20 PM, Gregory Seidman wrote:
I send email from several email addresses. I pay for an email service for
both sending and receiving email, but I pull it down locally (via POP with
fetchmail) and send messages from my Debian server with mutt. All of those
email addresses wind up forwarding to the address with the paid service,
but I neither send nor receive messages directly with that email address.
One of the addresses I send from is hosted by Google, and therefore when I
send from that address through my paid service (which is how exim4 is
configured, using it as a smarthost) recipients usually see a warning about
the message being unverified or suspicious. This is presumably because of
DKIM or something.
What I'd like to do is configure exim4 as it is for most outgoing mail, but
to use GMail as the smarthost when the sender is that one particular email
address. Can someone guide me or give me a hint, please?
--Gregory
I used a simple solution:
dc_smarthost='"${if
match{${lc:$header_from:}}{.*xxx.org}{smtp.xxx.net::587}{${if
match{${lc:$header_subject:}}{SSS}{mail.SSS.net}{smtp.googlemail.com::587"'
Note you can test for any header.
linux-image-4.19.0-22-amd64
linux-image-amd64 wants linux-image-4.19.0-22-amd64 but only linux-image-4.19.0-22-amd64-unsigned show up in a search.
Re: Ethernet Performance Problem Solved
On 9/6/2022 5:00 PM, Marc Auslander wrote: I have an Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller (rev 02) Subsystem: Acer Incorporated [ALI] RTL810xE PCI Express Fast Ethernet controller There is also a Realtek Semiconductor Co., Ltd. Device 8161 (rev 15) Subsystem: Realtek Semiconductor Co., Ltd. Device 8168 100BaseT not being used. lspci -v says the driver is R8169 for both. firmware-realtek is installed and does not appear to provide R8169 but I'm a novice about these things. The cable leading to the debian computer, when connected to a different computer, runs at almost 1000 Mb according to iperf3. When talking to Debian Buster it runs about 100Mb give or take. ethtool says its running Speed: 1000Mb/s Duplex: Full I just noticed this - in the past it ran at 1000Mb/s rates. It may have happened when I recently went from squeeze to buster, but I can't be sure of that. Any suggestion on how to proceed. I have used iptables to go dark to probes of my machine. I had about 10,000 entries. Apparently, now that is is deprecated, it's gotten a whole lot lest efficient in Buster. Clearing the iptables made the issue go away. Now to figure out nftables.
Re: A correct version follows. Ethernet Performance Problem
Please ignore this - a correct description follows. On 9/6/2022 4:30 PM, Marc Auslander wrote: I have an Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller (rev 02) lsmod says the driver is Realtek. firmware-realtek is installed The cable leading to it, when connected to a different computer, runs at almost 1000 Mb according to iperf3. When taking to Debian Buster it runs about 100Mb give or take. ethtool says its running Speed: 1000Mb/s Duplex: Full I just noticed this - in the past it ran at 1000Mb/s rates. It may have happened when I recently went from squeeze to buster, but I can't be sure of that. Any suggestion on how to proceed.
Ethernet Performance Problem
I have an Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller (rev 02) Subsystem: Acer Incorporated [ALI] RTL810xE PCI Express Fast Ethernet controller There is also a Realtek Semiconductor Co., Ltd. Device 8161 (rev 15) Subsystem: Realtek Semiconductor Co., Ltd. Device 8168 100BaseT not being used. lspci -v says the driver is R8169 for both. firmware-realtek is installed and does not appear to provide R8169 but I'm a novice about these things. The cable leading to the debian computer, when connected to a different computer, runs at almost 1000 Mb according to iperf3. When talking to Debian Buster it runs about 100Mb give or take. ethtool says its running Speed: 1000Mb/s Duplex: Full I just noticed this - in the past it ran at 1000Mb/s rates. It may have happened when I recently went from squeeze to buster, but I can't be sure of that. Any suggestion on how to proceed.
Ethernet Performance Problem
I have an Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller (rev 02) lsmod says the driver is Realtek. firmware-realtek is installed The cable leading to it, when connected to a different computer, runs at almost 1000 Mb according to iperf3. When taking to Debian Buster it runs about 100Mb give or take. ethtool says its running Speed: 1000Mb/s Duplex: Full I just noticed this - in the past it ran at 1000Mb/s rates. It may have happened when I recently went from squeeze to buster, but I can't be sure of that. Any suggestion on how to proceed.
Re: [SOLVED] Re: One-user system.
On 5/6/22 19:16, John Hasler wrote: James H. H. Lampert writes: I started with a TRS-80 Model I myself (and with high school programming classes on an IBM 370/135 at the District Office, with terminals connected over a pair of multiplexed phone lines [and a maximum terminal speed of 300 Baud]). Punch cards and an IBM 1620 at university. The first computer I owned I built using a Z80 SBC demo board. Cassette tape mass storage, modified Selectric printer, OCLC crt terminal, homebrew OS. I starting in college with punch cards an IBM 360 and a PDP 11/15 that actually let me sit at a terminal. After I graduated I got a TRS 80 Model III (Z80) with cassette tape for mass storage and 16K of RAM. Marc
Re: file born 30 seconds after its creation on ext4 - bug?
On 4/29/2022 10:20 AM, duh wrote: On 4/27/22 11:05 PM, Greg Wooledge wrote: Having skimmed over a number of the replies, and really not being qualified, may I just toss out a probably useless ideas to use the "sync" command. Looking at the 'man sync' shows at the bottom several variants or whatever to sync. Just a thought since when does the data get transferred to the disk versus just being held in memory or whatever? This is probably just a useless tangent based on my ignorance, but once in awhile it is possible to discover something when falls into a hole. sync isn't about this. linux caches file system pages in memory - both content and metadata. sync is about forcing the changed pages back to disk, for example before shutting down. It's done automatically - maybe every 30 seconds (I'm not sure about linux on this). But sync does not change what programs see unless they use a direct to disk read, which is certainly not what's going on here.
Re: random usernames in attempts to break in to my machine?
On 4/5/2022 3:30 AM, to...@tuxteam.de wrote: You gotta be careful: kicking out an IP for just one login failure might shut *you* out because you forgot to ssh-add your key (or because you mistyped your password once). OTOH, if "they" keep changing their IP address for each retry, you wouldn't catch them otherwise. So it is a fine line to walk. You might try to trigger on more specific patterns, which means you'll have to adapt your recognisers, yadda, yadda. Take care & don't forget having fun. That's what computers are for, after all. I run a homebrew version of this idea to kill probes to my ssh server. And I realized the danger stated above. So my server also reads email to an account just for it and I have a special subject line that causes it to clear the iptables - just in case. Since I don't have a fixed IP, there is another special subject line that causes it to email the current ip to my email account. All this so I can tunnel through the server when I travel.
Google smtp and pop
Google has now said they are pulling the plug on userid/password authentication for apps. I use fetchmail and exim4 to get and send mail. Neither, AFAIK, supports OAUTH2. I'm also still on stretch but will update if I have to. So what suggestions does anyone have for dealing with OAUTH2 access to gmail?
Re: Thunderbird not allowing local accounts
On 1/5/22 12:33, John Conover wrote: pa...@quillandmouse.com writes: On Wed, 5 Jan 2022 11:58:09 -0500 Celejar wrote: On Wed, 5 Jan 2022 09:44:24 -0500 "Paul M. Foster" wrote: ... Thanks for the info. Mozilla Foundation is seriously annoying me lately. Can anyone recommend another MUA which uses mbox format and is relatively easy to configure? Sylpheed? Celejar It's starting to look that way. Actually, I'm looking at claws-mail. Yea, and claws-mail is not compatible with Gmail's oauth2, which is now required by Google, (as of this month,) and Thunderbird is compatible, but no longer supports local mbox delivery for a LAN. Kind of a mess. John DISCLAIMER: * I am running on Devuan, then days, not Debian * I get my Thunderbird directly from Mozilla (Currently 91.5.1) I have local accounts set up so that I can receive e-mail sent by cron. I have had no difficulty with receiving these e-mails. Over the last two months, I have used 91.4.0, 91.4.1, 91.5.0, and now 91.5.1. None have given me any problems with receiving e-mail sent by cron to my local account. Under "Local Folders" I have an account with my name. Properties shows the location of this to be 'mailbox:///var/mail/marc'. No soft links required. Am I misunderstanding the problem, here? Marc
Re: what is flooding /var/tmp?
On 11/24/2021 10:40 PM, sp...@caiway.net wrote: Hello, My /var/tmp directory gets flooded by big files named: sort01ei1t sort01Eq7u sort01sLAs ... sortzZZtvv the files are approx. 13 Gb each. In 24 hours > 6000 are written. My big partition is filled by it until the system freezes. The files are plain text files, containing sshfs paths: /mnt/nas/sshfs/proc/self/task/413551/root/proc/self/task/413551/root/proc/self/task/413551/root/proc/self/task/413551/root/proc/ . nas and desktop are running debian 11 daily updated. How can I find out which program is writing these files? Thanks! You might look at file creation time and look in /var/log/syslog to see what CRON job is running when they are created.
Re: sysrq over *USB*
On Fri, Oct 15, 2021 at 09:02:50PM +0200, Marc SCHAEFER wrote: > Should I abandon all hope to make it work with USB, or should it work? Yes, sysrq can work with USB, but not with stock Debian kernels, because of [1]. Here is the work-around: 1) recompile kernel (see [2]) with the following options: CONFIG_USB=y CONFIG_USB_SERIAL=y CONFIG_USB_SERIAL_CONSOLE=y CONFIG_U_SERIAL_CONSOLE=y 2) configure /etc/default/grub with console=ttyUSB0,9600 console=tty0 and run upgrade-grub 3) I then get: # cat /proc/consoles tty0 -WU (EC p )4:1 ttyUSB0 -W- (E p ) 188:0 and I can then do sysrq from USB: schaefer@acer-1:~$ cu -l ttyUSB0 -s 9600 Connected. ~%break [ 1633.701624] sysrq: HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usage(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) force-fb(V) show-blocked-tasks(w) dump-ftrace-buffer(z) Also, the HDMI console still works (logs & sysrq). The problem and solution was found with help from the kernel-newbies mailing-list. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868352 [2] https://wiki.debian.org/BuildADebianKernelPackage
Re: sysrq over *USB*
Hello, On Fri, Oct 15, 2021 at 09:33:20PM -0500, Nicholas Geovanis wrote: > It's a side issue, not my main question, but If feel some details are > missing in > the "apu2 null modem" block-box there :-) It may be that your e-mail client is not handling ASCII art properly, you can look at the correct version here: https://lists.debian.org/debian-user/2021/10/msg00658.html Typically, the null modem is NOT the apu2. > But don't you need to have a running getty now? Listening on the > serial device file that should be associated with the USB source. I have tested with a cu on both sides, so the port is "open" anyway, if this is required. > Interesting project though. Any involvement here with MIDI-over-USB? No. > Tschuss [36 useless quote lines removed ]
sysrq over *USB*
Hello, I made the following setup work, that is I can send break and '?' (to get the magic sysrq help) or 's' to do an Emergency sync, and the kernel logs it: laptopapu2 USB serial port --- null modem --- ttyS0 internal 16550A (an apu2 is an embedded amd64 computer [4]) As it works, of course MAGIC_SYSRQ is enabled, including for serial ports, and the correct value is in the /proc pseudo-file. It works with the getty enabled or disabled. However, the following does not work to support magic sysrq, although bidirectionnal communication also works with cu [5], with the correct speed set: laptopapu2 USB serial port --- null modem --- USB serial port First, reading documentation, I thought that this would not be possible [1], but then, reading kernel source, it looks it should work with my adapter: Oct 11 14:30:56 apu2-init7 kernel: [9.915105] usb 2-2: pl2303 converter now attached to ttyUSB0 since the driver [2] contains code for magic sysrq, see line 993 for sysrq mode and line 892 for break handling, with implementation in [3] (lines 589-597). I am running Debian buster kernel 4.19.0-18-amd64 on the apu2. Should I abandon all hope to make it work with USB, or should it work? Thank your for any pointers. [1] https://www.kernel.org/doc/Documentation/admin-guide/sysrq.rst "On the serial console (PC style standard serial ports only)" [2] https://github.com/jplozi/linux-4.19/blob/loadbalancing/drivers/usb/serial/pl2303.c [3] https://github.com/jplozi/linux-4.19/blob/loadbalancing/drivers/usb/serial/generic.c [4] https://pcengines.ch/apu2.htm [5] https://linux.die.net/man/1/cu from the days before 2003 where I was doing UUCP cu -l ttyUSB0 -s 9600
Re: Updating kernels impossible when /boot is getting full
Sorry, Stefan. This was supposed to go to the list. On 8/2/21 11:02 PM, Marc Shapiro wrote: On 8/1/21 9:33 PM, Stefan Monnier wrote: So really think hard before splitting off a filesystem outside of volume management. I believe it is more likely to cause problems than it is to avoid problems. All my machines have a separate /boot partition (and everything else in LVM). These are all "historical accidents", because at the time I set them up, the respective boot loader (LILO, Grub, U-Boot) didn't know how to read LVM volumes, and I just never bothered to change. But I fully agree with you: if your bootloader can read from LVM (as is the case with Grub2), then you're better off without a separate /boot partition. Stefan "not sure if U-Boot can read from LVM yet" I am primarily running Devuan, these days, but I also still have root/boot partitions (boot is not separate from root) for Stretch and Buster. My /boot directory contains 4 kernels and their associated files and the whole lot only takes up about 140MB. Since I use Lilo as my boot loader (and it can read LVM), and I don't use encryption, I can put everything (including root/boot) into a single LVM physical volume. No hassles if I need to resize any partition, since they are all logical volumes in a single volume group on a single physical volume. If I ever need more total space, which I find unlikely, I can add additional disks to the PV and then add space to any LVs as needed. Marc
Re: Memory allocation failed during fsck of large EXT4 filesystem
On 7/5/2021 4:30 AM, Reiner Buehl wrote: Hi all, I have a corrupt EXT4 filesystem where fsck.ext4 fails with the error message: Error storing directory block information (inode=366740508, block=0, num=406081): Memory allocation failed /dev/vg_data/lv_mpg: * FILE SYSTEM WAS MODIFIED * e2fsck: aborted /dev/vg_data/lv_mpg: * FILE SYSTEM WAS MODIFIED * The system has 4GB of memory and a 8GB swap partition. The filesystem has 7TB. Is there a quick way to enlarge the swap space to help fsck.ext4 to finish the repair? I do not have any unused partitions but have space for swap on other filesystems if that is possible. Are you sure it's not a ulimit issue? Does the ulimit command return unlimited?
Re: Font color selection in MATE terminal
On 6/22/21 9:23 AM, Siard wrote: On Tue, 22 Jun 2021 17:32:55, Andrei POPESCU wrote: On Ma, 22 iun 21, 08:14:08, Richard Owlett wrote: I have vision problems. I *MUST* have black on white text in all cases. The program I'm running gives out colored text. The MATE Help screen is NOT helpful. Help please. This has already been addressed before: you must change the color scheme in the setting for MATE Terminal, to have it use black/dark gray/etc. as needed for everything related to text. The exact steps are different for each terminal emulator and I don't have MATE Terminal installed here. Well, I have. In the MATE Terminal settings (Edit > Profile Preferences), tab 'Colors', under 'Palette', set 'Built-in schemes' to 'Custom' and change every color in the color palette to black. Here is a screenshot: https://i.postimg.cc/2yv17y3Y/mateterminalcolors.png Why select 'Custom'? Richard needs black on white, so he should select 'Black on white'. It works for me. I have been using 'Custom', Yellow on Black, like my first monitor many years ago. But selecting 'Black on white' gives exactly that. Marc
Re: Unexplained freezes and crashes, nothing in /var/log/messages
On 6/3/2021 10:20 AM, Ottavio Caruso wrote: On 03/06/2021 09:09, Polyna-Maude Racicot-Summerside wrote: I check the temperature regularly with sensors and it's usually between 42 and 52 C. Problem is I can't check the temperature while it's freezing. You might run a background job that keeps writing the sensors to a file, say every 5 minutes, although a really don't know how quickly the temperature can change. That said, this sounds like a long shot to me.
Re: Thunderbird: how can I set permanent custom headers?
Ottavio Caruso writes: >Hi, > >For the lack of a dedicated Thunderbird mailing list, I am forced to >ask here. > ... try alt.comp.software.thunderbird
Re: Creating my first LAN
Anssi Saari writes: >Brian writes: > ... >> >> Now - could I use this non-internet-capable router as a switch? > >Probably. Usually LAN ports on a router are setup as a switch. The >router may have a DHCP server running though which you may want to >disable. In my experiance, you should put the router into access point mode, connect your lan to the wan port, and then use the lan ports as additional ports. Some routers get confused when they think they are routing even though they can't reach the wan. And remember to turn off WiFi unless it is far from your primary router and you want to extend your WiFi network. Also, make sure you set the IP address of the router to one on your lan that's not in use and not in the DHCP range of your primary router. I normally use .2 for this purpose.
Re: MATE desktop - changing icon of a Launcher
On 3/24/21 2:14 PM, Dominic Knight wrote:
On Tue, 2021-03-23 at 09:26 -0500, Richard Owlett wrote:
I've been use MATE almost since it came out.
IIRC I used to use a series of mouse clicks to determine the file
name
{including path} of the current icon.
On my current systems {one Stretch, one Buster} if I:
I am using Bullseye and Mate, for clarity, my icons are all on
taskbars, none are on the desktop.
1. right click on the Launcher
2. select properties
3. left click on the current icon
I get a "Select Custom Icon" menu. In it I can select a directory to
search and it will display a list of available icons in that
directory.
I get "Choose an icon"
But I need to know the complete path to the current icon.
The path to the current (icon) directory is listed above the icons you
can select from. You would have to note this down as it is not possible
to select it for cut and paste purposes.
I can get the desired information by opening the launcher with a text
editor. {I want a "mouse click" method to obtain the information as
I'm
setting up a system for a very novice user.}
Suggestions?
TIA
No help I know but it does not currently seem possible to do exactly
what you require.
Cheers,
Dom
When selecting an icon from the desktop, I get the same results as
Richard. If I select an icon from a taskbar, I get the same results as
Dominic .
You can get to the info strictly by mouse clicks for icons on the
desktop by dragging the icon onto a taskbar, then follow the same steps
that you listed. You can delete the icon from the taskbar afterwards,
but this is probably not what you really want.
Marc
Re: SOLVED - Re: Deb10 installer can't install grub
On 3/3/2021 6:30 AM, Dave Sherohman wrote: Based on this, I'm guessing that the original problem was that the installer forgot to include mdadm support in its grub options, even though it was configured with an mdadm boot device. And then I missed a couple steps after adding mdadm support, so it didn't all get installed to the EFI partitions correctly. One potential gotcha. When you boot from an mdadm file system containing /boot/grub, grub will not write to the file system. In particular, it will not update grub/grubenv even if you have a save_env line in grub.cfg. So if you use grub-reboot to specify an alternate line in grub.cfg, you need to reset grubenv afterwards. I do this in a root @reboot cron job. If you don't know what I'm talking about, you probably don't need to worry about this.
Re: identifying my LInux machine on my LAN
Paul Scott writes: > >ssh and Bitvise still fail t o connect > >Paul /var/log/auth.log may show what's happening if the request gets that far.
Re: Raid 1
Andy Smith writes: >... >So personally I would just do the install of Debian with both disks >inside the machine, manual partitioning, create a single partition >big enough for your OS on the first disk and then another one the >same on the second disk. Mark them as RAID members, set them to >RAID-1, install on that. >... You don't say if this is or will become a secure boot system, which would require an EFI partition. Leaving a bit of space just in case seems a good idea.
Re: Debian jessie > buster IPv6 link scope change of behaviour
On Thu, Jan 21, 2021 at 06:23:56PM -0600, David Wright wrote:
> Yes, that documents what we normally observe as a %eth0 or %1 suffix
> for IPv6 addresses which selects the interface to use. "Requires"
> (unemphasised in the original) mean that it is necessary to identify a
> particular zone, but IMHO doesn't mean that a choice of zone is
My opinion is that link-local addresses are ambiguous and it is required
to find a mean to deambiguate those, either using a zone (interface
identifier) %postfix, or through a default zone).
Actually, my interpretation of what happened is wrong. If `ping'
exhibits a bizarre behaviour using apparently the first Ethernet
interface it sees, this is is not what other commands shows:
$ telnet fe80::1
Trying fe80::1...
telnet: Unable to connect to remote host: Invalid argument
That's good (to me).
schaefer@reliand:~$ telnet -6 fe80::1%eth1
Trying fe80::1%eth1...
[no error, NDP requests sent]
That's correct behaviour (to me).
ping however seems to do things itself and chooses an interface:
PING fe80::1(fe80::1) 56 data bytes
From fe80::9e8e:99ff:fe3c:5523%eth0: icmp_seq=1 Destination unreachable:
Address unreachable
(which in this case, obviously, is not the correct one, but how
could he guess? link-local v6 addresses ARE ambiguous -- should it
try all other interfaces each like Microsoft apparently does as you
mentionned? no -- and it doesn't!)
Also, a small code I wrote using getaddrinfo(3) and connect(2):
$ ./simple-client fe80::1 80
Trying connection to host fe80::1:80 ...
connect(): : Invalid argument
Could not connect.
vs
$ ./simple-client fe80::1%eth1 80
Trying connection to host fe80::1%eth1:80 ...
So its's not getaddrinfo(3) which does bad things either.
So it's must be ping's fault.
So, let's look at ping's manpage:
-I interface
interface is either an address, or an interface name. If interface
is an address, it sets source address to specified interface
address. If interface in an interface name, it sets source
interface to specified interface. NOTE: For IPv6, when doing ping
to a link-local scope address, link specification (by the
'%'-notation in destination, or by this option) can be used but it
is no longer required.
Oho, "is no longer required" ... why that?
Let's look at the source:
apt-get source iputils-ping # especially ping6-common.c
In ping6_run() there is all sort of code related to LINKLOCAL v6
addresses and using the `device' global, which is initialized
in ping.c if -I is used, and is NULL in my use case.
It seems firsthop.sin6_scope_id is set manually when required.
Reading:
https://tools.ietf.org/id/draft-smith-ipv6-link-locals-apps-00.html#rfc.section.5
(about sin6_scope_id) and
https://tools.ietf.org/id/draft-smith-ipv6-link-locals-apps-00.html#rfc.section.5
(about getaddrinfo)
which confirms that link-local addresses are returned by getaddrinfo()
without scope id, unless they have the scope as the %postfix. So you
need to supply it separately (-I ping option would do). However, ping
seems to get overly smart about this, opening a probe socket on
apparently the first interface it gets, and getting the interface from
it, it seems.
Demonstration:
$ ./a.out fe80::1
Trying connection to host fe80::1:80 ...
scope ID: 0
./a.out fe80::1%eth0
Trying connection to host fe80::1%eth1:80 ...
scope ID: 2
Code:
#include
#include
#include
#include
#include
#include
#include
int main(int argc, char **argv) {
if (argc < 2) {
fprintf(stderr, "%s v6-addr\n, %s: bad args.\n", argv[0], argv[0]);
return 2;
}
struct addrinfo hints;
struct addrinfo *result, *rp;
hints.ai_family = AF_UNSPEC; /* IPv4 or v6 */
hints.ai_socktype = SOCK_STREAM; /* TCP */
hints.ai_flags = 0;
hints.ai_protocol = 0; /* any protocol */
int s;
if ((s = getaddrinfo(argv[1], "http", &hints, &result))) {
fprintf(stderr, "getaddrinfo(): failed: %s.\n", gai_strerror(s));
}
else {
/* getaddrinfo() returns a list of address structures.
* Try each address until we successfully connect(2).
*/
for (rp = result; rp != NULL; rp = rp->ai_next) {
char ipname[INET6_ADDRSTRLEN]; /* len(addrv6) > len(addrv4) */
char servicename[6]; /* "65535\0" */
if (!getnameinfo(rp->ai_addr,
rp->ai_addrlen,
ipname,
sizeof(ipname),
servicename,
sizeof(servicename),
NI_NUMERICHOST|NI_NUMERICSERV)) {
printf("Trying connection to host %s:%s ...\n",
ipname,
servicename);
if (rp->ai_family == AF_INET6) {
printf("scope ID: %d\n", ((struct sockaddr_in6 *)
rp->ai_addr)->sin6_scope_id);
}
}
}
}
ret
Re: Debian jessie > buster IPv6 link scope change of behaviour
On Thu, Jan 21, 2021 at 08:04:05AM +0100, Marc SCHAEFER wrote: > fe80::1 is specifically a link-local scope, a bit like if you try to > access a class variable without telling in what class it is. Reading RFC-4291 [1], 2.5.6 (link-local addresses) and RFC-4007 [2] 6, Zones Indices: Because the same non-global address may be in use in more than one zone of the same scope (e.g., the use of link-local address fe80::1 in two separate physical links) and a node may have interfaces attached to different zones of the same scope (e.g., a router normally has multiple interfaces attached to different links), a node *requires* an internal means to identify to which zone a non-global address belongs. This is accomplished by assigning, within the node, a distinct "zone index" to each zone of the same scope to which that node is attached, and by allowing all internal uses of an address to be qualified by a zone index. Also: An implementation should also support the concept of a "default" zone for each scope. And, when supported, the index value zero at each scope SHOULD be reserved to mean "use the default zone". Unlike other zone indices, the default index does not contain any scope, and the scope is determined by the address that the default index accompanies. An implementation may additionally define a separate default zone for each scope. Those default indices can also be used as the zone qualifier for an address for which the node is attached to only one zone; e.g., when using global addresses. If I read well, recent Linux kernels might have decided that the first Ethernet interface is the default zone. Or at least this is how I understand the *requires* above. [1] https://tools.ietf.org/html/rfc4291#section-2.5.6 [2] https://tools.ietf.org/html/rfc4007
Re: Debian jessie > buster IPv6 link scope change of behaviour
On Wed, Jan 20, 2021 at 11:59:46PM -0600, David Wright wrote: > As far as the address is concerned, fe80::1 is perfectly formed, > but ambiguous. Is that what your jessie error message used to say? The error was one of the usual kernel errors (-EINVALID probably), see below. Actually, stretch does the same (Linux ns2 4.9.0-14-amd64 #1 SMP Debian 4.9.246-2 (2020-12-17) x86_64 GNU/Linux): root@ns2 ~ # ping6 fe80::1 connect: Invalid argument root@ns2 ~ # ping6 fe80::1%2 PING fe80::1%2(fe80::1%eth0) 56 data bytes 64 bytes from fe80::1%eth0: icmp_seq=1 ttl=255 time=0.423 ms 64 bytes from fe80::1%eth0: icmp_seq=2 ttl=255 time=0.332 ms 64 bytes from fe80::1%eth0: icmp_seq=3 ttl=255 time=0.305 ms 64 bytes from fe80::1%eth0: icmp_seq=4 ttl=255 time=0.355 ms fe80::1 is specifically a link-local scope, a bit like if you try to access a class variable without telling in what class it is.
Debian jessie > buster IPv6 link scope change of behaviour
Hello, I experiment a change of behaviour between the kernel of Debian jessie and Debian buster. Namely, before, ping6 fe80::1 would fail, since it is ambiguous (fe80::1 is a link scope, thus a zone/interface scope ID is required). With buster, it tries the first Ethernet interface, no error (unless NDP does not find it, obviously). The correct behaviour when specifying the zone (interface scope ID) is the same on both versions: ping6 fe80::1%eth0 # e.g. Is there something broken with my setup, or has something changed in the way the Linux kernel behaves when the required zone (interface scope ID) is not specified ? I found the idea of reporting an error when a scope is not given very correct, simple and pedagogic (aka jessie behaviour). Thank you for your help :) PS: I upgraded from jessie to buster, so I don't know when the behaviour change happened in the Linux kernel
Re: Add a hard drive to existing system??
Jerry Mellon writes: >Hello, >New to Debian, but have gotten Debian 10.7 loaded on to my system. I >have an ASUS gaming laptop(dont use it for gaming) with 12gb of memory >and intel corei7 and a 500gb hard drive. > >My question is what is the best(use dummy for linus statements please) >way to add a second hard drive with 2T of space. I wiil use this to >store photos and documents etc. > >Thanks A possible alternative is to see if your router supports storage, and if not consider an upgrade. Many modern routers support an attached disk and provide network storage. Of course a major advantage of this is that you will be able to carry the laptop around and maintain access to the storage. An issue is that the storage will probably be Windows formatted, and thus you will have to deal with incompatible meta data. And you will have to configure debian access to a windows share. To be honest, I've never tried this. My linux sever is the NAS and windows machines access it. I think creating a linux nas may be too much for you, at least for now.
Re: mdadm usage
Reco writes: > >And what purpose would it serve? IMO it's not a backup unless it's >stored in a way that's inaccessible to the system its taken from (until >it's actually needed of course). > >Reco IMHO, there are two levels of backup. The more common use is to undo user error - deleting the wrong thing or changing something and wanting to back out. For that, backups on the same system are the most convenient. And if its on the same system, and you have raid1, you don't need a separate physical drive. The second is of course disaster recovery, a very low probability event - and I backup in the cloud and occasionally on removable media for that.
Re: mdadm usage
Andrei POPESCU writes: > >Automatic mirroring / synchronizing is unsuitable for backups, because >it will also sync accidental changes to files (including deletions) or >filesystem corruptions in case of power outage or system crash (that may >lead to corrupted files or entire directories "disappearing"). > ... BUT - once you have hardware reliable storage (raid1) you can do backups into the same disks you are backing up!
leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): will expire in less than 27 days
Hello,
I quickly grepped my DEBIAN-USER mailing-list file but did not find any
leapsecond in it, thus this message.
I get this error on all of my buster machines although I think they are
uptodate:
Dec 1 09:34:39 virtual ntpd[2432]: leapsecond file
('/usr/share/zoneinfo/leap-seconds.list'): will expire in less than 27 days
A quick Internet search shows this:
https://www.mail-archive.com/debian-glibc@lists.debian.org/msg59571.html
Apparently, the Debian distributed file will expire on 2020-12-28.
However, it seems the next Debian point release scheduled on 2020-12-05
contains an update for tzdata, so it should be fixed then.
Re: AppImage files (was: clipgrab as alternative to youtube-dl)
On 11/18/20 6:07 AM, Fred wrote: On 11/17/20 11:47 PM, Anssi Saari wrote: Fred writes: There is a binary for Linux available for download as a AppImage file. What is an AppImage file and what does one do with it. The program was probably compiled for Ubuntu. Is it likely to also run on Debian? AppImage files are a kind of package that contain an app and all its dependencies so yes, it's very likely it'll run on Debian. All you have to do is make the AppImage file executable and run it. I recently got into these since I have a problem with the Firefox Debian bundles but someone maintains a current Firefox build as AppImage. Hi, Thanks for your answer. I was able to get clipgrab to compile but the AppImage file is a later version and may be a better choice if it will run on Debian. I am using it on a Ddevuan system and it works just fine. Marc
Re: Kernel global lock in sr.c slows down parallel operations to multiple drive
On Tue, Nov 17, 2020 at 07:04:59AM -0500, The Wanderer wrote: > FWIW, I parsed this as "and possibly file a(nother) bug report[ about > this bug, since the one I thought I remembered having filed before seems > to have disappeared, if it ever existed in the first place]". Exactly, thank you for parsing! Actually I just found the old bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816211 Of course, as it was reported on a backport kernel, I guess no one cared :)
Kernel global lock in sr.c slows down parallel operations to multiple drive
Hello, In jessie, the kernel had a very annoying bug: if you did I/O on multiple sr devices, the global lock in sr.c would slow down to a crawl. E.g. 5 DVD-R written to in parallel gave the same performance as one writing; and ejecting the DVD in parallel was completely sequential. Based on this: https://unix.stackexchange.com/questions/411735/why-does-linux-kernel-driver-sr-c-sr-block-ioctl-do-mutex-lock and this: https://www.spinics.net/lists/linux-scsi/msg63706.html I patched my kernel, and the performance augmented drastically, you can watch the video here: https://www.youtube.com/watch?v=siDMzkRCTpQ&feature=youtu.be or here: https://peertube.gaialabs.ch/videos/watch/7ad190bd-43d9-42dc-9336-984822db7cc3 I even think I reported that bug, but can't find it anymore. However, it seems the kernel used by buster has the same issue. I am now writing with BR drives (two of them) and I get abyssal performance. Anyone can confirm ? I will try to apply a similar patch and possibly report another bug.
Re: PCI-Express not mapping a card's memory
On Sun, Nov 08, 2020 at 05:54:14PM +0100, Marc SCHAEFER wrote: > What could I try to do? Thanks to some people around here (private replies), I tried: - finding an option in the BIOS about 64 bit PCI addresses, none found - setpci -s 01:00.0 COMMAND=0x02 - removing all cards, shuffling them around - upgrading the BIOS Unfortunately, it does not work. I thus replaced the mainboard from 2014 with one from 2017 and it works.
PCI-Express not mapping a card's memory
Hello, I have a Mellanox card, which is detected, however on one machine: 01:00.0 Network controller: Mellanox Technologies MT27500 Family [ConnectX-3] Subsystem: Mellanox Technologies MT27500 Family [ConnectX-3] Flags: fast devsel, IRQ 16 Memory at dfb0 (64-bit, non-prefetchable) [size=1M] Memory at (64-bit, prefetchable) and on another machine, it differs: Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at cf80 (64-bit, prefetchable) [size=8M] Obviously on the machine with , I get a driver error, where it works on the other. [1.257148] mlx4_core: Mellanox ConnectX core driver v4.0-0 [1.257163] mlx4_core: Initializing :01:00.0 [1.257196] mlx4_core :01:00.0: enabling device ( -> 0002) [1.257303] mlx4_core :01:00.0: Missing UAR, aborting I tried to use another 16x slot on the failing machine, and even to update the BIOS: no change. dmesg says: [0.438011] pci :01:00.0: [15b3:1003] type 00 class 0x028000 [0.438414] pci :01:00.0: reg 0x10: [mem 0xf7e0-0xf7ef 64bit] [0.438580] pci :01:00.0: reg 0x18: [mem 0xf000-0xf07f 64bit pref] [0.440372] pci :01:00.0: reg 0x134: [mem 0x-0x007f 64bit pref] [0.440373] pci :01:00.0: VF(n) BAR2 space: [mem 0x-0x07ff 64bit pref] (contains BAR2 for 16 VFs) [0.458296] pci :01:00.0: BAR 9: no space for [mem size 0x0800 64bit pref] [0.458298] pci :01:00.0: BAR 9: failed to assign [mem size 0x0800 64bit pref] [0.458382] pci :01:00.0: BAR 2: no space for [mem size 0x0080 64bit pref] [0.458383] pci :01:00.0: BAR 2: failed to assign [mem size 0x0080 64bit pref] [0.458384] pci :01:00.0: BAR 9: no space for [mem size 0x0800 64bit pref] [0.458385] pci :01:00.0: BAR 9: failed to assign [mem size 0x0800 64bit pref] [0.458491] pci :01:00.0: BAR 2: no space for [mem size 0x0080 64bit pref] [0.458492] pci :01:00.0: BAR 2: failed to assign [mem size 0x0080 64bit pref] [0.458493] pci :01:00.0: BAR 9: no space for [mem size 0x0800 64bit pref] [0.458494] pci :01:00.0: BAR 9: failed to assign [mem size 0x0800 64bit pref] [0.458495] pci :01:00.0: BAR 0: assigned [mem 0xdfb0-0xdfbf 64bit] [0.458627] pci :01:00.0: BAR 2: no space for [mem size 0x0080 64bit pref] [0.458627] pci :01:00.0: BAR 2: failed to assign [mem size 0x0080 64bit pref] [0.458629] pci :01:00.0: BAR 0: assigned [mem 0xdfb0-0xdfbf 64bit] [0.458759] pci :01:00.0: BAR 9: no space for [mem size 0x0800 64bit pref] [0.458760] pci :01:00.0: BAR 9: failed to assign [mem size 0x0800 64bit pref] I also tried to boot with an debian installer for testing and I had similar PCI messages above. What could I try to do? Chipset on the failed machine is somewhat older than on the working machine. Thank you for any idea or pointer.
Re: Error mounting LVM volume as root (SOLVED)
On 10/11/20 2:04 PM, Marc Shapiro wrote: On 10/11/20 6:34 AM, Stefan Monnier wrote: That did it. I am assuming that the system was just in the process of changing from the initrc to the actual running system? But how do I get the boot sequence to activate the LVs automatically each time before attempting to mount the / filesystem? AFAIK you don't need to do anything special for that. >From what I can tell, the initramfs (tries to) activate the swap and root LVs, and then the rest of the boot activates them all. If that doesn't work for you, you're going to have to dig deeper, Stefan The swap LV seems to be getting activated, but not the root LV, so it keeps trying to mount an LV that is not yet activated and eventually it times out and drops me into a shell. From there, I can manually activate all LVs and exit the shell and the boot process continues successfully. Marc After more Googling, I found the following page: https://serverfault.com/questions/199185/logical-volumes-are-inactive-at-boot-time The last answer on the page suggests a mismatch in the way the LV is named in: /usr/share/initramfs-tools/scripts/local-top/lvm2 and fstab, namely '/dev/vgname/lvname' instead of '/dev/mapper/vgname-lvname'. Both of those files used '/dev/mapper/vgname-lvname', but /etc/lilo.conf was using '/dev/vgname/lvname'. I changed /etc/lilo.conf to use the same format as the other two, re-ran lilo, rebooted, and it worked. I then did the same thing for my Stretch partitions, and the system booted into Stretch with the LV mounted on / with no issues. I had not thought that there was any real difference between the two formats, and this may well be the only instance where there is, but I'm going to use the '/dev/mapper/vgname-lvname' format in all locations from here on out. Marc
Re: Error mounting LVM volume as root
On 10/11/20 6:34 AM, Stefan Monnier wrote: That did it. I am assuming that the system was just in the process of changing from the initrc to the actual running system? But how do I get the boot sequence to activate the LVs automatically each time before attempting to mount the / filesystem? AFAIK you don't need to do anything special for that. >From what I can tell, the initramfs (tries to) activate the swap and root LVs, and then the rest of the boot activates them all. If that doesn't work for you, you're going to have to dig deeper, Stefan The swap LV seems to be getting activated, but not the root LV, so it keeps trying to mount an LV that is not yet activated and eventually it times out and drops me into a shell. From there, I can manually activate all LVs and exit the shell and the boot process continues successfully. Marc
Re: Error mounting LVM volume as root
On 10/10/20 7:42 PM, Stefan Monnier wrote: I am attempting to mount an LVM Logical Volume as root, but I am getting an error in the boot sequence when it attempts to mount the root filesystem. The error is saying that it can not find /dev/block/254:15, which is the LV that I am trying to mount. Then it falls into a shell. When I run 'ls /dev/block' it shows /dev/block/254:0, which is the swap volume (in the same LVM Volume Group as /dev/block/254:15), but does not show any of the other LVs. If it can recognize the LVM swap volume, why does it not see the other LVs in the group? Any chance you're inside the initramfs while this problem shows up? I'd assume it's because the initramfs has only activated the swap and root partitions (root for the obvious reason and swap to check for a hibernation image). Try `vgchange -ay` to activate the other volumes. Stefan That did it. I am assuming that the system was just in the process of changing from the initrc to the actual running system? But how do I get the boot sequence to activate the LVs automatically each time before attempting to mount the / filesystem? I don't want to have to manually activate them each time I boot the system. Marc
Error mounting LVM volume as root
I am attempting to mount an LVM Logical Volume as root, but I am getting an error in the boot sequence when it attempts to mount the root filesystem. The error is saying that it can not find /dev/block/254:15, which is the LV that I am trying to mount. Then it falls into a shell. When I run 'ls /dev/block' it shows /dev/block/254:0, which is the swap volume (in the same LVM Volume Group as /dev/block/254:15), but does not show any of the other LVs. If it can recognize the LVM swap volume, why does it not see the other LVs in the group? Is there some way to get this to work? I am trying to put everything on LVM so that I can use snapshots to get consistent backups of a running system. Marc
Re: Sound (Alsa/PulseAudio) not working for ONE USER ONLY (addidional info)
On 9/23/20 10:02 PM, Marc Shapiro wrote: I am currently running Stretch, with alsa and pulseaudio. This box has three users. My wife and daughter both get sound through Firefox, as well as 'play filename.mp3'. Neither method works for my login. When using 'aplay filename.mp3' all users get static. Some background: A few months back, my /home partition was accidentally wiped. (It was mounted where I did not think it was. No backups. My bad. New external drive for backups, now.) Data recovery managed to get back my wife's and daughter's directories, but not mine. My guess is that there were configuration files that I no longer have under my login that are necessary for sound. An interesting note: I just tried playing a file (play filename.mp3) while displaying the PulseAudio Volume Meter. It says that sound is playing. Then I noticed that it is showing volume for the 'Loopback Analog Stero'. I did the same thing under my wife's and daughter's login and the sound was going to the 'Built-in Audio Analog Stereo' How do I tell Alsa/PulseAudio to use the Built-in sound device, and not the loopback device? Marc I can change the fallback to the Built-in sound device using pavucontrol, but then, when I try to play an mp3 file, 'play' just locks up. It displays the file data, and the line that shows its location in the file, but that line never changes. Even Ctrl-C does not exit the program. I have to close, and restart, LXTerminal. Marc
Sound (Alsa/PulseAudio) not working for ONE USER ONLY
I am currently running Stretch, with alsa and pulseaudio. This box has three users. My wife and daughter both get sound through Firefox, as well as 'play filename.mp3'. Neither method works for my login. When using 'aplay filename.mp3' all users get static. Some background: A few months back, my /home partition was accidentally wiped. (It was mounted where I did not think it was. No backups. My bad. New external drive for backups, now.) Data recovery managed to get back my wife's and daughter's directories, but not mine. My guess is that there were configuration files that I no longer have under my login that are necessary for sound. An interesting note: I just tried playing a file (play filename.mp3) while displaying the PulseAudio Volume Meter. It says that sound is playing. Then I noticed that it is showing volume for the 'Loopback Analog Stero'. I did the same thing under my wife's and daughter's login and the sound was going to the 'Built-in Audio Analog Stereo' How do I tell Alsa/PulseAudio to use the Built-in sound device, and not the loopback device? Marc
Re: Buster with MATE without systemd
On 9/16/20 9:12 PM, Patrick Bartek wrote: On Wed, 16 Sep 2020 19:44:03 -0700 Marc Shapiro wrote: On 9/16/20 5:55 PM, David Wright wrote: On Wed 16 Sep 2020 at 16:15:12 (-0700), Patrick Bartek wrote: On Wed, 16 Sep 2020 13:52:15 -0400 Greg Wooledge wrote: On Wed, Sep 16, 2020 at 10:32:14AM -0700, Patrick Bartek wrote: To make a long story short, after two or so weeks of research and numerous failed trials, I came to the conclusion that systemd has become too entrenched in the dependency tree of Buster to successfully convert to systvinit. If you specify "... on a desktop system", then maybe you're correct. For most servers, it shouldn't be an issue. The subject _was_ about desktops, MATE specifically, not servers. However, my trials with Buster was from a year ago. And I haven't tried a sysvinit install with it since. Perhaps some systemd dependencies have been eliminated. Be great if they all were! Init systems should never ever be dependencies. I know little to nothing about DEs. However, I see that there are people who run MATE without running a systemd init system. This (dated) link makes a distinction between installation dependencies and runtime dependencies, so I presume that you might be able to put up with the presence of unused systemd packages in the installation. https://unix.stackexchange.com/questions/279603/using-mate-desktop-without-systemd Later: […] Had no problems converting to sysvinit with a terminal only system. First thing I did. I always start my installs that way and build from there. Lighter, faster, more efficient system without all the crud that comes with a general DE install. I would certainly recommend that the OP did that, rather than converting as an afterthought. Unfortunately, as it says at the bottom of that page, systemd-shim is no longer available. It worked in Jessie, I used it then, but is not an option, now. As for installing only a minimal, textbased, system and then converting -- I'm sure that works, until you try to install xorg and Mate. That is where things start to get 'fun.' Dependencies are dependencies. Running without a DE, or even a different DE is not an option in this case. I am not the only one using this box. My wife is now working from home and my daughter's college is strictly distance learning. (Thank you Caronavirus Pandemic.) I can not go changing how things work for them at this time. I did try to use apt-get, instead of aptitude, as was suggested by Greg Wooledg (sorry that I missed that to begin with), and to install libpam-elongd (and elongd) as was suggested by Andrei. Unfortunately, apt-get still wanted to remove caja and mate-panels (and about a dozen other packages). Without mate-panels, the DE is pretty much unusable. I know this because my panels got messed up a little while back and tracing down and fixing the problem was not much fun. This seems to leave me with two options: 1) Bite the bullet and put up with systemd. 2) Switch to Devuan. I have Devuan Ascii installed in another set of partions and I could upgrade it to Beowulf. I don't really like either of these options. I have been running Debian for the past 21, or 22 years (since Bo, i believe). I'd rather not switch. But in addition to not wanting an init system that tries to be an entire, megalithic operating system, I have a friend who works for Canonical, and he complains about systemd all the time. If anyone can suggest any other options, I am open to suggestions. Upgrade your Devuan ASCII(Stretch) to Beowulf(Buster) and try it out. Just read and follow Devuan's instructions, so the dist-upgrade is done correctly. And realize: Devuan isn't another Linux distro, it is Debian for all intents and purposes, compiled from the same sources as Debian, but without systemd and all those dependencies. It looks and performs the same. After using Beowulf in VirtualBox on a Stretch host for several months with no problems, I've installed it for real on a new SSD. No problems. It's your's (and mine's) easiest solution to systemd. Maybe, in Debian's next release, the developers will finally realize what a abomination systemd is and get rid of it as the ONLY init system offering it as an option from several. "Tis a consummation devoutly to be wished." -- William Shakespeare (Hamlet)
Re: Buster with MATE without systemd
On 9/16/20 5:55 PM, David Wright wrote: On Wed 16 Sep 2020 at 16:15:12 (-0700), Patrick Bartek wrote: On Wed, 16 Sep 2020 13:52:15 -0400 Greg Wooledge wrote: On Wed, Sep 16, 2020 at 10:32:14AM -0700, Patrick Bartek wrote: To make a long story short, after two or so weeks of research and numerous failed trials, I came to the conclusion that systemd has become too entrenched in the dependency tree of Buster to successfully convert to systvinit. If you specify "... on a desktop system", then maybe you're correct. For most servers, it shouldn't be an issue. The subject _was_ about desktops, MATE specifically, not servers. However, my trials with Buster was from a year ago. And I haven't tried a sysvinit install with it since. Perhaps some systemd dependencies have been eliminated. Be great if they all were! Init systems should never ever be dependencies. I know little to nothing about DEs. However, I see that there are people who run MATE without running a systemd init system. This (dated) link makes a distinction between installation dependencies and runtime dependencies, so I presume that you might be able to put up with the presence of unused systemd packages in the installation. https://unix.stackexchange.com/questions/279603/using-mate-desktop-without-systemd Later: […] Had no problems converting to sysvinit with a terminal only system. First thing I did. I always start my installs that way and build from there. Lighter, faster, more efficient system without all the crud that comes with a general DE install. I would certainly recommend that the OP did that, rather than converting as an afterthought. Unfortunately, as it says at the bottom of that page, systemd-shim is no longer available. It worked in Jessie, I used it then, but is not an option, now. As for installing only a minimal, textbased, system and then converting -- I'm sure that works, until you try to install xorg and Mate. That is where things start to get 'fun.' Dependencies are dependencies. Running without a DE, or even a different DE is not an option in this case. I am not the only one using this box. My wife is now working from home and my daughter's college is strictly distance learning. (Thank you Caronavirus Pandemic.) I can not go changing how things work for them at this time. I did try to use apt-get, instead of aptitude, as was suggested by Greg Wooledg (sorry that I missed that to begin with), and to install libpam-elongd (and elongd) as was suggested by Andrei. Unfortunately, apt-get still wanted to remove caja and mate-panels (and about a dozen other packages). Without mate-panels, the DE is pretty much unusable. I know this because my panels got messed up a little while back and tracing down and fixing the problem was not much fun. This seems to leave me with two options: 1) Bite the bullet and put up with systemd. 2) Switch to Devuan. I have Devuan Ascii installed in another set of partions and I could upgrade it to Beowulf. I don't really like either of these options. I have been running Debian for the past 21, or 22 years (since Bo, i believe). I'd rather not switch. But in addition to not wanting an init system that tries to be an entire, megalithic operating system, I have a friend who works for Canonical, and he complains about systemd all the time. If anyone can suggest any other options, I am open to suggestions. Marc
Buster with MATE without systemd
I have a fresh install of Buster which is running MATE as the Desktop Environment. It has taken me until now to get it working, without messing up my current Stretch install on the same machine. The next thing that I want to do is replace systemd with sysvinit. I am not trying to start a flamewar about which is better. I want sysvinit, not systemd, let's leave it at that. I ran 'aptitude install sysvinit-core'. This resulted in about 2 dozen packages to be removed (some of which, I would have removed anyway) and a similar number with unmet dependencies (mostly recommends). I can live with that and work around any issues once I'm running on sysvinit, so I accept the option. This gives me another screen full of text that basically says that it needs a terminal emulator, but xterm is being removed. It wants to install pterm and, again, leave a number of recommends as they are. OK, I accept that option. Now I get a full screen of packages to be removed. Most are libraries, and what seem to be MATE virtual packages, along with some other packages, including the GIMP. I DO want MATE and the GIMP. This looks like a problem. I cancel the install. So, my question is: Can I replace systemd with sysvint and still keep MATE? Do I need to let aptitude uninstall MATE, and then reinstall after sysvinit has been installed? Or have MATE and the GIMP been updated in a way that requires systemd and not sysvinit? If it is possible to do what I want, what is the easiest way to accomplish it? Marc
Re: Question on 'dpkg --get-selections'
On 9/12/20 12:29 AM, Sven Joachim wrote: On 2020-09-11 22:03 -0700, Marc Shapiro wrote: Is there any option to have 'dpkg --get-selections' NOT include automatically installed packages? No, dpkg has no notion of automatically installed packages, that is an apt concept. Otherwise, all packages show as manually installed, including those that would otherwise have been automatically installed. You can obtain a list of automatically installed packages with apt-mark(1): $ apt-mark showauto > automatically-installed-packages Then, on the replicated system where you presumably had used "dpkg --set-selections" to install the same set of packages: # apt-mark auto $(cat automatically-installed-packages) HTH, Sven Thank you. That is a perfectly acceptable solution to the issue. Marc
Question on 'dpkg --get-selections'
Is there any option to have 'dpkg --get-selections' NOT include automatically installed packages? Otherwise, all packages show as manually installed, including those that would otherwise have been automatically installed. Marc
Re: Does Debian have a "nag" tool?
I've been using Remind for years (maybe decades). It can handle all kinds
of repeating reminders, not just annual dates (ie birthdays and
anniversaries). Very versatile. It is a command line program, but comes
with TkRemind (a GUI front end). Best not to use the GUI for setting up
reminders, though. It doesn't have the versatility of doing it manually.
Marc
On Sat, Aug 15, 2020, 4:53 AM Joe wrote:
> On Sat, 15 Aug 2020 06:30:13 -0500
> Richard Owlett wrote:
>
> > Just missed girlfriend's birthday by 6 weeks :{
> > [just sent a 'mea culpa' email.]
> > Is there a better tool than "cron"?
> >
> > Just looked at its manpage.
> > I'm looking for something slightly different.
> >
> > Independent of when I turn on or first do something after midnight on
> > a specific date I want a reminder to be displayed unless I have taken
> > a specific action.
> >
> > As:
> > 1. I've known her for > 30 years.
> > 2. I'm a _senior_ citizen.
> > 3. She is a decade younger.
> > I am about to receive just retribution.
> >[She'll claim I'm forgiven due to senility.]
> >
> > Wish to prevent such a response next year ;/
> >
> > TIA
> >
> >
>
> Remind?
>
> --
> Joe
>
>
Re: xterm no title (buster)
On Mon, Aug 10, 2020 at 07:03:26PM +0200, Marc SCHAEFER wrote: > Should I try with another window-manager? I will also double-check that > the other working buster MATE installation uses marco. The bug is NOT present with compiz. The bug IS NOT present on a fresh buster install with marco. I tried for i in .???*; do find $i -name '*marco*' -print; done to see if any local marco-specific config existed, but could not find any.
Re: xterm no title (buster)
On Mon, Aug 10, 2020 at 01:47:08PM +0200, to...@tuxteam.de wrote: > Have you tried another "classic" X program? For example xmag or xeyes? Yes, they fail miserably. > xterm in a special way, or the decorations of all "classic" X programs > fail in the same way. I would guess that. Should I try with another window-manager? I will also double-check that the other working buster MATE installation uses marco.
Re: xterm no title (buster)
On Sun, Aug 09, 2020 at 09:59:12AM +0200, to...@tuxteam.de wrote: > To verify/falsify that, you might run xprop on your xterm window. > The property you are looking for is called WM_NAME. You can even xprop | grep WM_NAME WM_NAME(STRING) = "schaefer@reliand: /home/schaefer" > use xprop to /set/ the window property -- this way you can be sure xprop -f WM_NAME 8s -set WM_NAME "toto" clicking on either the titleless xterm or an emacs changes nothing (*). NB: the xterm window title is seen on MATE's taskbar. > whether it's xterm who is forgetting to do the right thing (that > would be a bug to file against xterm) or it's your window manager > ignoring it. As I am the only one to experience this, it must be some configuration somewhere! > [2] https://en.wikipedia.org/wiki/ICCCM Thank you, definitely is an interesting reference. (*) examples often show xprop -set WM_NAME "toto" but it does not work (cannot convert WM_NAME argument to STRING or COMPOUND_TEXT), thus the -f
Re: xterm no title (buster)
On Sat, Aug 08, 2020 at 02:22:44PM -0700, Mike Kupfer wrote: > I assume you're using the system xterm, not something in /usr/local or > $HOME. yes schaefer@reliand:~$ which xterm /usr/bin/xterm (BTW was working nice before upgrade to buster) > Could the problem be locale-related? I have > > LANG=en_US.UTF-8 > XTERM_LOCALE=en_US.UTF-8 I tried setting the locale to LANG=fr_CH.UTF-8 XTERM_LOCALE=fr_CH.UTF-8 and clearing the other settings to no avail. I will do some tests tomorrow on a fresh buster install.
Re: xterm no title (buster)
> > What about if you use another window-manager and/or desktop-environment? > > I haven't tried that yet. I just tried twm and it says "Untitled" even with xterm -T abcd &
Re: xterm no title (buster)
On Sat, Aug 08, 2020 at 08:25:39AM -0400, Stefan Monnier wrote: > Does it affect other terminal emulators? no, mate-terminal is not affected. > Have you checked whether the problem also shows up for a freshly created > user (i.e. without any config of your own)? yes, it does. > What about if you use another window-manager and/or desktop-environment? I haven't tried that yet. also: On Sat, Aug 08, 2020 at 02:42:18PM +0200, to...@tuxteam.de wrote: > Xterm's title is most probably your window manager's job. What's yours? MATE marco.
Re: xterm no title (buster)
On Sat, Aug 08, 2020 at 09:47:56AM +, Long Wind wrote: > have you looked at .bashrc? Actually, I have sent the usual title escape sequence: it works in mate-terminal, but xterm's title remains blank. Thomas Schmitt : Also I tried the -T option, with no success. Running MATE in marco (buster).
xterm no title (buster)
Hello, I have a funny problem since I upgraded my laptop to buster: xterm does not have any title. It is the only window that has this problem. I did not see anything special in the .Xresources. Anyone having this issue ? Thank you for pointers.
Visitors List of Southern California 2020 Linux Expo
Hi, I am following up to check if you are interested in the Pre-registered attendees List. Event Name: Southern California 2020 Linux Expo Date: Mar 05 - Mar 08, 2020 Place: Pasadena Convention Center, Los Angeles, California Attendees Counts: 4,327 Let me know your interest to get back with pricing & more info. Thank you and I look forward to hearing from you. Regards, Marc Daniels Sr. Marketing Analyst
Re: Sharing /boot and /lib/modules with multiple distros
On 6/6/20 2:58 PM, to...@tuxteam.de wrote: On Sat, Jun 06, 2020 at 02:06:42PM -0700, Marc Shapiro wrote: I usually have three different distros installed. I was wondering if I could have a separate partition (possibly in an extended partition) containing /boot and /var/modules that would be mounted in each of the distros. This would eliminate having kernels, initrds and kernel modules duplicated for each distro, while allowing me to run lilo from any of them. The only file that would need to be duplicated would be /etc/lilo.conf, and it doesn't take much space. Is this a workable idea? Sounds feasible, but there are some snags to watch out for: - distributions tend to customize the kernel; some more, some less. - different distributions come with different kernel versions: if the versions don't differ too much (e.g. they get along with the same libc version) that might not bite you Expect some tinkering. Cheers -- t Right now, I am looking at combinations of Debian and Devuan, so I don't think that this should be an issue. Marc
Sharing /boot and /lib/modules with multiple distros
I usually have three different distros installed. I was wondering if I could have a separate partition (possibly in an extended partition) containing /boot and /var/modules that would be mounted in each of the distros. This would eliminate having kernels, initrds and kernel modules duplicated for each distro, while allowing me to run lilo from any of them. The only file that would need to be duplicated would be /etc/lilo.conf, and it doesn't take much space. Is this a workable idea? Marc
Re: trouble installing gnome
On 6/6/20 8:58 AM, Brad Rogers wrote: On Sat, 6 Jun 2020 11:14:13 -0400 leonard morin wrote: Hello leonard, Line commented out by installer because it failed to verify: Both instances of that should either be deleted or have an # inserted at the start of the line. IMO, the former is preferable. You may also wish to add an online repo, rather than relying on just the CDs. Also, if what the OP pasted into his post was his entire /etc/apt/sources.list file, he is not using the CDs, either. Those lines were also commented out. The only uncommented lines where the ones that SHOULD have been comments: --Snipped from original post -- # deb cdrom:[Debian GNU/Linux testing _Bullseye_ - Official Snapshot amd64 xfce-CD Binary-1 20200525-03:32]/ bullseye main contrib non-free #deb cdrom:[Debian GNU/Linux testing _Bullseye_ - Official Snapshot amd64 xfce-CD Binary-1 20200525-03:32]/ bullseye main contrib non-free Line commented out by installer because it failed to verify: #debhttp://security.debian.org/debian-security bullseye-security main contrib non-free Line commented out by installer because it failed to verify: #deb-srchttp://security.debian.org/debian-security bullseye-security main contrib non-free ---
Re: Buster install using debootstrap. (SOLVED)
On 6/5/20 6:31 PM, Marc Shapiro wrote: On 6/4/20 11:30 PM, Sven Hartge wrote: Marc Shapiro wrote: I also don't understand why it says that it could not create temporary files in /tmp. I am running this as root and /tmp is owned by root. What am I missing? /tmp (and /var/tmp/) should have the following permissions and rights: root:root 1777/drwxrwxrwt apt runs its I/O processes as a different user "_apt" and if /tmp does not have the sticky bit set, then it cannot create any files there, causing the error. Grüße, Sven. Thanks! That took care of all the debian repositories. Third party repositories are now having public key issues (not surprising). How do I get and install the public key for deb-multimedia.org and virtualbox.org? Marc I got the public keys for deb-multimedia.org and virtualbox.org and all is good. I just needed to google a little more (after having some dinner). Marc
Re: Buster install using debootstrap.
On 6/4/20 11:30 PM, Sven Hartge wrote: Marc Shapiro wrote: I also don't understand why it says that it could not create temporary files in /tmp. I am running this as root and /tmp is owned by root. What am I missing? /tmp (and /var/tmp/) should have the following permissions and rights: root:root 1777/drwxrwxrwt apt runs its I/O processes as a different user "_apt" and if /tmp does not have the sticky bit set, then it cannot create any files there, causing the error. Grüße, Sven. Thanks! That took care of all the debian repositories. Third party repositories are now having public key issues (not surprising). How do I get and install the public key for deb-multimedia.org and virtualbox.org? Marc
Buster install using debootstrap.
nstallation Guide. I'm sure that I missed something, somewhere, but I don't know what. I also don't understand why it says that it could not create temporary files in /tmp. I am running this as root and /tmp is owned by root. What am I missing? If anyone can help me with this I would greatly appreciate it. Marc
Re: Fwd: lists.debian.org has received bounces from you
On 5/26/20 2:23 PM, Abhishek Dixit wrote: What should I do for bounce messages I get. -- Forwarded message - From: *Debian Listmaster Team* <mailto:listmas...@lists.debian.org>> Date: Mon, Apr 20, 2020 at 2:16 AM Subject: lists.debian.org <http://lists.debian.org> has received bounces from you To: mailto:abhidixi...@gmail.com>> Dear subscriber, We've encountered some problems while sending listmail to your emailaddress abhidixi...@gmail.com <mailto:abhidixi...@gmail.com>. In the last seven days we've seen bounces for the following list: * debian-user 1 bounce out of 84 mails in one day (1%, kick-score is 80%) (https://lists.debian.org/bounces/ue_GpOw_vSJRYwJ9fC4rKw) (The link above points to a copy of the latest bounce and will be valid for seven days.) If the bounce-rate passes the kick-score, our bounce-detection will forcibly remove your subscription. Bounces happen from time to time when spam slips through our filters but are rejected by your mail provider. If you are your own mail provider and use 'Before-Queue Content filtering', you should whitelist bendel.debian.org <http://bendel.debian.org> from Content filtering. However: You can safely ignore this message (and you will not be unsubscribed :-) ) if your bounce rate remains low. For more information see https://wiki.debian.org/Teams/ListMaster/FAQ You are welcome to contact listmas...@lists.debian.org <mailto:listmas...@lists.debian.org> if you think this message was sent in error. Sincerely, The Listmaster Team -- http://lists.debian.org -- - Abhi I wouldn't worry about it. When I get these (which is maybe once every month, or two) I check the bounced e-mail (from the link) to see if it was anything I really needed to read. Then I don't worry about it any more. You have a 1% bounce rate. As the e-mail says, they will remove your subscription if it reaches 80%. With 84 e-mails, they would have to received 68 bounces before it would become an issue. For me, it has never been more than 1 bounce. Nothing top worry about. Marc
Re: Re: checksum fails on current openstack debian 9 image
Thanks richard ! Now I'm sure there is something wrong on my side ! :-)
checksum fails on current openstack debian 9 image
Hi everyone ! I just downloaded the latest openstack debian 9 image from a debian mirror using : https://cdimage.debian.org/cdimage/openstack/current-9/debian-9-openstack-amd64.qcow2 I also got the checksum and its signature : https://cdimage.debian.org/cdimage/openstack/current-9/SHA256SUMS https://cdimage.debian.org/cdimage/openstack/current-9/SHA256SUMS.sign checksum's signature is good: $ gpg --verify SHA256SUMS.sign gpg: assuming signed data in 'SHA256SUMS' gpg: Signature made dim. 29 mars 2020 16:40:45 CEST gpg: using RSA key DF9B9C49EAA9298432589D76DA87E80D6294BE9B gpg: Good signature from "Debian CD signing key " [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: DF9B 9C49 EAA9 2984 3258 9D76 DA87 E80D 6294 BE9B but checksum fails : $ sha256sum -c SHA256SUMS --ignore-missing debian-9-openstack-amd64.qcow2: FAILED sha256sum: WARNING: 1 computed checksum did NOT match sha256sum: SHA256SUMS: no file was verified I've try to download a new copy (from the same mirror) but it still fails. The mirror I use is https://caesar.ftp.acc.umu.se/cdimage/openstack/current-9 I couldn't manage to find another mirror to check if this copy only was altered, or all of them. If anyone could verify that on its side and provide me a mirror that contain a valid image that would be awesome ! Thanks for your help !
Buster without systemd?
Supposedly, one can install/upgrade to Buster while maintaining sysv as init. Or has this changed. Over the past several months I have been attempting to upgrade to Buster, but I have been completely unsuccessful. Has anyone managed to upgrade to Buster without installing systemd, or jumping through hoops that would drive a lion tamer mad? I made a copy of all of my partitions so that I could do the upgrade while maintaining Stretch in case something went wrong. I'm glad that I did! The first time that I tried this, I actually managed to upgrade to Buster and have everything appear to work. Then I realized that I had only done an "upgrade" but not a "full-upgrade". After that, X would not start. I have, as I said, spent several months trying to get X working on Buster without systemd. I have not been successful. None of my later attempts ever got a working Buster with X, at all. Is it possible to do what I want? Or, after 21 to 22 years of using Debian (since Bo), do I have to switch to another linux distro? I would rather not have to switch, but you choose the distro that suits your needs, and if Debian no longer suits my needs then I may have to. Marc
Re: Boot process hangs at, it seems, network initialisation
On 3/22/2020 10:50 AM, Brad Rogers wrote: Hello, For the first time, I'm having problems installing Debian testing on new hardware; Asus TUF X570 Plus mobo with onboard Realtek network L8200A i/f As things stand, it /seems/ that the boot process is waiting for the network interface to come up, before proceeding to start the SDDM log in manager. Switching to tty2 and logging in would appear to bear this out, as attempting to ping anything other than LAN machinery results in 'No route to host' reports. The package firmware-realtek from testing has been installed. The OS was installed using a net-install CD, so clearly, the network card is working. Having never previously encountered network i/f issues myself, I'm really rather at a loss as to how I should proceed. /etc/network/interfaces reads (comments & empty lines omitted); source /etc/networks/interfaces.d/* auto lo iface lo inet loopback /etc/networks/interfaces.d/ is an empty directory. For the sake of full disclosure, I see this; [FAILED] Failed to start NVIDIA Persistence Daemon during the boot process. I suspect it has little bearing on the issue I'm experiencing, but mention it 'just in case'. My $SEARCH foo has turned up nothing recent, only stuff from 2002, 2009 or thereabouts. IDK how to proceed. Ideas and pointers (even moral support) sought and welcomed. Thank you. Could it be https://wiki.debian.org/BoottimeEntropyStarvation (I tried to post this elsewhere - if it works forgive the double post)
Re: RCA Cable to USB Video input device
On 12/30/19 9:31 AM, Christian Seiler wrote: Hi there, Am 2019-12-14 07:45, schrieb Marc Shapiro: I want to copy some videos from VCR and DVD to my computer for editing (simple stuff, like removing commercials). I found this device on Amazon: https://www.amazon.com/Digital-Converter-Capture-Support-Android/dp/B06X42H9VZ/ref=sr_1_3?m=A3ENZ260X3A00C&marketplaceID=ATVPDKIKX0DER&qid=1576302348&s=merchant-items&sr=1-3&th=1 It says in the title that it works on Linux, and at least one of the reviews says it works on Debian. From the listing you posted the device you have appears to have a UTV007 chipset, and you can find some documentation on how to make that work on Linux here: https://linuxtv.org/wiki/index.php/Easycap#Making_it_work_4 I found that site, too. That is what gives me hope that the device will work. Thanks.
RCA Cable to USB Video input device
I want to copy some videos from VCR and DVD to my computer for editing (simple stuff, like removing commercials). I found this device on Amazon: https://www.amazon.com/Digital-Converter-Capture-Support-Android/dp/B06X42H9VZ/ref=sr_1_3?m=A3ENZ260X3A00C&marketplaceID=ATVPDKIKX0DER&qid=1576302348&s=merchant-items&sr=1-3&th=1 It says in the title that it works on Linux, and at least one of the reviews says it works on Debian. There seem to be a lot of sellers with what looks like this exact same device. Does anyone know anything about this device, or other, similar devices. Is it likely to require specialized drivers, or would generic drivers be able to access it? Any suggestions on editing software would also be appreciated. I have done simple audio editing before, but not video. Would the editing software read the data directly from the USB port, or would I need to access the port with other software/commands. I don't mind using the command line to access the port and save the file, if necessary. Marc
Finalizing a Video DVD
I have a DVD recorder hooked up to my TV and antenna. Unfortunately, the remote for it is non-functional and the option for finalizing the DVD+R discs is only reachable through the remote. Why VCR/DVD players and recorders were designed to not be fully functional without their remote, I do not know. I think it's foolish, but no one asked me. My question is this: Is there any software in the repository that can finalize these disks so that I can use them other than on the machine that created them? On that machine, these disks play just fine. I just can't play them anywhere else. I don't need to add to them. I just want to play them back. Marc
Re: NSS-LDAP group preventing proper boot
Thanks for the feedback, I might give it a try to sssd (I was already planning to take a look). I seen many docs recommending to move to nss/pam-ldapd however (also for sssd) this requires installing many other packages and run multiple daemons while I could achieve the same with simply a dynamic loaded library as libnss-ldap. Regards Missatge de Alex Mestiashvili del dia dv., 20 de set. 2019 a les 19:22: > On 9/20/19 7:42 AM, Marc Franquesa wrote: > > After making a clean install of Buster and setup it, the system doesn't > > boot propery and enters emergency mode with some systemd-udevd errors on > > timing out. > > > > I tracked down and isolated the issue to be caused by nss-ldap group > > mapping: If I remove ldap from nsswtich.conf groups (only for groups > table) > > the system boots fine (So I can use ldap for everything else except for > > group) > > > > I already faced the same problem long time ago (not sure, but I think on > > jessie and ubuntu older releases) and the workarround/solution was to set > > nss_init_groups_ignore users to list all localacounts (so don't lookup > for > > LDAP groups for local accounts). This time this didn't worked, as I > updated > > my nss_init_groups_ignore_users to the list of current local users with > no > > luck. > > > > Some details tested/discarded: > > - there are no custom udev rules making use of any LDAP user/group > > - I tried setting various timeouts/soft_policy on LDAP configuration > > - Also tried [UNAVAIL=return] and other similar optons on nsswitch.conf > > - Exactly the same configuration works perfectly on Debain Stretch (as I > > configure them thru Ansible) > > > > Note that while researching I found many similar bug reports (also on > > different distros) related to this issue, all of them providing > > workarrounds (which didn't worked) but none providing a permanent FIX or > > solution: > > > > https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/1024475 > > https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/51315 > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=318622 > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=339797 > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=349509 > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=375077 > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=375215 > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=388729 > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=391167 > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=441458 > > https://bugzilla.redhat.com/show_bug.cgi?id=234541 > > https://bugzilla.redhat.com/show_bug.cgi?id=187852 > > > > So basically seems that NSS-LDAP is queried when is still not ready, > either > > because LDAP server is down or the affected system didn't initialized > > network yet. Either the case, this shouldn't prevent the system to boot > > normally. More than a bug on libnss-ldap/udev seems a wrong/unstable > > integration on the init process. I don't know if any NSS network > servicces > > (NIS?, winbind?) experience similar issues or how they avoid them. > > > > Does any one faced same issue or can provide any help/workarround/clues? > > Should I open a new bug report? > > > > Thanks much for any hint/help > > > > > That's interesting. I've been using libnss-ldap since Lenny and didn't > face the problems listed above, however since quite some time I've > switched to libnss-ldapd/libpam-ldpad. As far as I remember these are > drop-in replacements for libnss-ldap but you'll need to configure nslcd > daemon too. Another option would be to switch to sssd which "just > wokred" for my use cases. > > Best, > Alex >
NSS-LDAP group preventing proper boot
After making a clean install of Buster and setup it, the system doesn't boot propery and enters emergency mode with some systemd-udevd errors on timing out. I tracked down and isolated the issue to be caused by nss-ldap group mapping: If I remove ldap from nsswtich.conf groups (only for groups table) the system boots fine (So I can use ldap for everything else except for group) I already faced the same problem long time ago (not sure, but I think on jessie and ubuntu older releases) and the workarround/solution was to set nss_init_groups_ignore users to list all localacounts (so don't lookup for LDAP groups for local accounts). This time this didn't worked, as I updated my nss_init_groups_ignore_users to the list of current local users with no luck. Some details tested/discarded: - there are no custom udev rules making use of any LDAP user/group - I tried setting various timeouts/soft_policy on LDAP configuration - Also tried [UNAVAIL=return] and other similar optons on nsswitch.conf - Exactly the same configuration works perfectly on Debain Stretch (as I configure them thru Ansible) Note that while researching I found many similar bug reports (also on different distros) related to this issue, all of them providing workarrounds (which didn't worked) but none providing a permanent FIX or solution: https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/1024475 https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/51315 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=318622 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=339797 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=349509 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=375077 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=375215 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=388729 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=391167 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=441458 https://bugzilla.redhat.com/show_bug.cgi?id=234541 https://bugzilla.redhat.com/show_bug.cgi?id=187852 So basically seems that NSS-LDAP is queried when is still not ready, either because LDAP server is down or the affected system didn't initialized network yet. Either the case, this shouldn't prevent the system to boot normally. More than a bug on libnss-ldap/udev seems a wrong/unstable integration on the init process. I don't know if any NSS network servicces (NIS?, winbind?) experience similar issues or how they avoid them. Does any one faced same issue or can provide any help/workarround/clues? Should I open a new bug report? Thanks much for any hint/help
Re: x and virtual consoles
On 8/6/19 12:29 AM, Curt wrote: On 2019-08-06, Ed wrote: On 2019-08-06 09:02+0300, Andrei POPESCU wrote: On Lu, 05 aug 19, 21:56:55, Ed wrote: How do you run two login managers though so that you can have two users share the same computer without having to log out? In other words, whilst I go and make dinner I want to allow someone else to sit here, without having to shut applications down? Some login managers have the "switch user" feature. Does that feature take the user back to the login screen without leaving the applications running? https://wiki.archlinux.org/index.php/LightDM LightDM's dm-tool command can be used to allow multiple users to be logged in on separate ttys. The following will send a signal requesting that the current session be locked and then will initiate a switch to LightDM's greeter, allowing a new user to log in to the system. $ dm-tool switch-to-greeter Looks promising. I am another one of those who like to boot to a terminal and then run startx (which then runs mate), so this may not apply if you want to boot to a DE's login manager, but just to get it out there for those who are interested: My wife, daughter and I each have separate logins on a single box. On the rare occasions that the system gets rebooted, I log on to vt1 and run startx (using alias startx='clear; startx -- :0'), my wife logs on to vt2 and runs startx (using alias startx='clear; startx -- :1'), and my daughter uses vt3 and alias startx='clear; startx -- :2'. After that ctl-alt-f1 gets to my session, ctl-alt-f2 gets to my wife's session and ctl-alt-f3 gets to my daughter's session. All sessions running all the time. The only disadvantage to this is that occasionally a web page that my daughter has up will decide that it's time to play music. Then I have to find the offending page and mute it. Other than that, this system has worked for us for years. Marc
