Re: And another Dell Vostro 1700 question
Am 20.05.2024 um 12:59:40 Uhr schrieb Van Snyder: > When I boot, there's junk (mixed graphics and text that seems to be > out of sync) on one, and the other is dark. When I reboot, it's > almost the same, except the monitors' roles have switched. > > The graphics chip is NVidia G58M (GeForce 8400M) and the NVidia 340 > driver is running. > > Would the nouveau driver work for the USB monitors? Try it. I've already experienced issues with the nouveau driver with multi cards. It was a 6200TC and the internal Intel HD graphics. Sometimes graphics card break (memory or GPU issue), but aren't completely broken. This was especially the case for the older ones. Many laptops with 7xxx, 8xxx and 9xxx had graphics issues. -- Gruß Marco Send unsolicited bulk mail to 1716202780mu...@cartoonies.org
Re: And another Dell Vostro 1700 question
Van Snyder wrote: > I have some DisplayLink e1649Fwu USB monitors. > > When I boot, there's junk (mixed graphics and text that seems to be out > of sync) on one, and the other is dark. When I reboot, it's almost the > same, except the monitors' roles have switched. > > Would the nouveau driver work for the USB monitors? No. The nouveau driver is for NVidia graphics controllers; the USB monitors have their own on-board graphics controllers, which are probably not made by NVidia, and certainly don't use the standard drivers. -dsr-
And another Dell Vostro 1700 question
This is probably not specific to Dell Vostro. I have a Dell Vostro 1700 running Debian Trixie. I have some DisplayLink e1649Fwu USB monitors. When I boot, there's junk (mixed graphics and text that seems to be out of sync) on one, and the other is dark. When I reboot, it's almost the same, except the monitors' roles have switched. The graphics chip is NVidia G58M (GeForce 8400M) and the NVidia 340 driver is running. Would the nouveau driver work for the USB monitors? I tried to run the script for the contributed installer at https://github.com/AdnanHodzic/displaylink-debian/blob/master/displaylink-debian.sh but it ran into version-conflict problems. Any ideas?
Re: Dell Vosto 1700 and NVidia
Try to use a configuration file /etc/X11/xorg.conf. Yes, I know, the modern drivers do not need it any more, but when you want to force some settings, this can help. I attach mine at this message, which was running fine so far and has all the settings inside, you might want to use. This file was used also with a NVidia card GF8400M. Please note, that when you need to run with the proprietrary driver (which is downloadable as package from debian/oldstable, you need to run an old kernel. Otherwise the kernel module will not build. The 340xx legacy driver is the correct one for this graphic chip. My experiences with the nouveau driver from the kernel ended with unstability and bad peformance. If everything crashes, you can still run the vesa driver, but try first 340xx. Oh yes, in the xorg.conf I send with, the driver must be named "nvidia", it is already set. You also need the dependend libgl-nvidia for this driver. Check the old repos from debian. Something else? Well, you can place the "xorg.conf" below /etc/X11/ or below / usr/share/X11/ . Hint: To test the xorg.conf uninstall all login-managers, like sddm, lightdm, kdm or gdm. I suggest, just move /usr/bin/kdm, /usr/bin/gdm, /usr/bin/lightdm and similar to another direcory, for example /root. Then boot and test with the command "startx". If X is starting, you are good, if not, you can see, what happens and if it starts, but hangs, you can stop X using either CTL+C or CTR+ALT+BACKSPACE. Hope this helps! Good luck, Hans > I have an old Dell Vostro 1700 running Debian Trixie. It has an NVidia > G86M (GeForce 8400M) graphics chip. I installed the NVidia 340 driver > (which is difficult to find). > > I attached a HP 14" monitor to the VGA socket. > > When I booted, it came up with side-by-side displays. I could move > windows from one to the other. > > When I closed the cover and re-opened it, instead of waking up, it re- > started X, but this time with displays mirrored. > > I ran nvidia-settings to move the HP monitor. It complained about not > being able to set a mode. I've tried many times since without success. > > I tried running the KDE Display Settings, but that put it into a > restart-X loop. > > Any ideas? > > Van Snyder Section "ServerLayout" Identifier "Layout0" Screen 0 "Screen0" InputDevice"Keyboard0" "CoreKeyboard" InputDevice"Mouse0" "CorePointer" EndSection Section "Files" EndSection Section "InputDevice" # generated from default Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/psaux" Option "Emulate3Buttons" "no" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" # generated from default Identifier "Keyboard0" Driver "kbd" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Unknown" ModelName "Unknown" Option "DPMS" EndSection Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" EndSection Section "Screen" Identifier "Screen0" Device "Device0" Monitor"Monitor0" DefaultDepth24 SubSection "Display" Depth 24 EndSubSection EndSection
Re: Dell Vosto 1700 and NVidia
Am 20.05.2024 um 12:22:48 Uhr schrieb Van Snyder: > How do I switch to try nouveau instead? Completely uninstall it. Then reboot. If you have problem with nouveau, tell about them and maybe they can be fixed. -- kind regards Marco Send unsolicited bulk mail to 1716200568mu...@cartoonies.org
Re: Dell Vosto 1700 and NVidia
On Mon, 2024-05-20 at 20:42 +0200, Marco Moock wrote: > Am 20.05.2024 um 11:10:27 Uhr schrieb Van Snyder: > > > I installed the NVidia 340 driver > > Is there a special reason to use it instead of nouveau? I had had trouble with nouveau on other computers using different NVidia graphics. And I like the NVidia settings widget. How do I switch to try nouveau instead? Are there settings in grub.conf?
Re: Dell Vosto 1700 and NVidia
Am 20.05.2024 um 11:10:27 Uhr schrieb Van Snyder: > I installed the NVidia 340 driver Is there a special reason to use it instead of nouveau? -- Gruß Marco Send unsolicited bulk mail to 1716196227mu...@cartoonies.org
Dell Vosto 1700 and NVidia
I have an old Dell Vostro 1700 running Debian Trixie. It has an NVidia G86M (GeForce 8400M) graphics chip. I installed the NVidia 340 driver (which is difficult to find). I attached a HP 14" monitor to the VGA socket. When I booted, it came up with side-by-side displays. I could move windows from one to the other. When I closed the cover and re-opened it, instead of waking up, it re- started X, but this time with displays mirrored. I ran nvidia-settings to move the HP monitor. It complained about not being able to set a mode. I've tried many times since without success. I tried running the KDE Display Settings, but that put it into a restart-X loop. Any ideas? Van Snyder
Re: Sonido en Debian instalado en una Rpi4
El día 20/05/2024, a las 15:50, Camaleón escribió: > Parece un problema conocido relacionado con los controladores de audio > y/o el subsistema de gestión de sonido (PulseAudio/Jackd/ALSA, etc...). > > Mira a ver qué driver o stack de sonido instala/usa Raspberry Pi OS¹, > donde seguramente todo el hardware funcione sin problemas, y trata de > «emularlo» en Debian. > > ¹https://www.raspberrypi.com/software/operating-systems/ > > Gracias. Sí, creo que no me queda otro remedio. Me huelo que deberé recompilar el núcleo para añadir el módulo correspondiente.
Re: Sonido en Debian instalado en una Rpi4
El 2024-05-20 a las 11:49 +0200, Alfon escribió: > He seguido los pasos para instalar Debian descritos en: > https://wiki.debian.org/RaspberryPi4#Using_EFI_Firmware_and_the_regular_Debian_Installer > > Y todo ha ido bien, excepto que no tengo puedo usar la GPU para ver > vídeos con mpv y tampoco tengo sonido. Me interesa esto último, > ¿alguien lo ha conseguido? Parece un problema conocido relacionado con los controladores de audio y/o el subsistema de gestión de sonido (PulseAudio/Jackd/ALSA, etc...). Mira a ver qué driver o stack de sonido instala/usa Raspberry Pi OS¹, donde seguramente todo el hardware funcione sin problemas, y trata de «emularlo» en Debian. ¹https://www.raspberrypi.com/software/operating-systems/ Saludos, -- Camaleón
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: Debian, fail2ban, Version?
On 20 May 2024 07:00 -0400, from d...@randomstring.org (Dan Ritter): >> # fail2ban-server -V >> >> 0.11.2 > > Bullseye became stable in August of 2021. It's also perhaps worth noting that there seem to have been only two interim releases. https://github.com/fail2ban/fail2ban/releases lists 0.11.2 (Nov 2020), 1.0.1 (Sep 2022), 1.0.2 (Nov 2022) and 1.1.0 (April 2024). The release notes for 1.1.0 says 0.11 or 1.0 can be used if you have Python < 3.5; and 1.0.1 says 0.11 can be used if you have Python < 2.7. -- Michael Kjörling https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
Re: Debian, fail2ban, Version?
Maurizio Caloro wrote: > Hello > > Please why on Debian Bullseye, 11.9 is a pretty old version available in the > repository? > > # fail2ban-server -V > > 0.11.2 Bullseye became stable in August of 2021. "Stable" means that packages don't change except to fix serious bugs, especially security-related bugs. Bookworm became stable in June of 2023. The fail2ban version there is 1.0.2-2. -dsr-
Debian, fail2ban, Version?
Hello Please why on Debian Bullseye, 11.9 is a pretty old version available in the repository? # fail2ban-server -V 0.11.2 I think this application arnt a big thing? Available on github, Version 1.1.0
Sonido en Debian instalado en una Rpi4
Hola lista, He seguido los pasos para instalar Debian descritos en: https://wiki.debian.org/RaspberryPi4#Using_EFI_Firmware_and_the_regular_Debian_Installer Y todo ha ido bien, excepto que no tengo puedo usar la GPU para ver vídeos con mpv y tampoco tengo sonido. Me interesa esto último, ¿alguien lo ha conseguido? Saludos.
Re: Bookworm's /etc/mailcap seems to break s-nail
On Fri May 17, 2024 at 11:56 AM BST, Max Nikulin wrote: > You may file an issue to the emacs bug tracker. I didn't realise this was coming straight from upstream. If it were a Debian-local issue, I'd file something, but I will respectfully decline to engage with Emacs upstream. (Interesting to see another user of debbugs out there Today, besides Debian!) > However at least one developer was against wrappers: … Thank you for sharing these upstream bugs. They make for fascinating (if occasionally horrifying) reading. > Finally, I think that s-nail should ignore malformed mailcap entries. I agree. > On 16/05/2024 14:48, Jonathan Dowland wrote: > > Please do not CC me for listmail. > > You still decided to add my address to CC despite I joined to the > thread, not started it. I expect it is enough to guess that I am able to > follow the discussion even not being subscribed. So I did: Apologies! It seems my new favourite MUA (aerc) does not handle list replies by default as I would like it to/as I was used to with mutt. I will be more careful. -- Please do not CC me for listmail. Jonathan Dowland ✎j...@debian.org https://jmtd.net
