Debian User Forums

So, I decided to connect an 10 year old monitor and reboot, the monitor is recognised, but there is still no output! $ hwinfo | sed -n '/LCD Monitor/,/^$/p' 41: None 00.0: 10002 LCD Monitor [Created at monitor.125] Unique ID: rdCR.I4isrNo_UP2 Parent ID: _Znp.Ag8gOVmx9nF Hardware Class: monitor Model...

No, journalctl returns nothing at all

Since a while I'm running Debian server (no GUI) and in the beginning the monitor was being detected, but since the installation I solely connect via ssh to my server and everything seemed to work just fine. Now I came across the situation that I had to connect the monitor again as I could not ssh i...

Upps, sorry i didn't know I had to put that in front using square brackets

The problem has been solved, by adding the following to grub
After updating grub and rebooting the network interface is stable now for weeks.

Still getting the error once or twice a day, any more ideas? Jan 05 21:28:37 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: Link is up at 1000 Mbps, full duplex Jan 05 21:28:37 MacMini kernel: tg3 0000:01:00.0 enp1s0f0: Flow control is off for TX and off for RX Jan 05 21:28:37 MacMini kernel: tg3 0000:0...

Sorry for the late reply :-) Set iommu=pt as advised $ apt list -i firmware* Listing... Done firmware-amd-graphics/stable,now 20210315-3 all [installed,automatic] firmware-b43-installer/stable,now 1:019-7 all [installed] firmware-linux-free/stable,now 20200122-1 all [installed,automatic] firmware-li...

The PARTUUIDs are different: efibootmgr -v BootCurrent: 0001 Timeout: 5 seconds BootOrder: 0001,0000 Boot0000* debian HD(1,GPT,29e1f78c-480f-41c1-9088-f5469b2153d4,0x800,0x1dc800)/File(\EFI\debian\shimx64.efi) Boot0001* debian HD(1,GPT,502d77f1-2012-4069-a948-be592a507ccc,0x800,0x1dc800)/File(\EFI\d...

Thanks for your reply! 1) OK :-) 2) See 3 3) My /etc/fstab looks as follows: nano /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if ...

Hello, I've setup a RAID1 with separate EFI boot partition and even tested the recovery process successfuly :-) But I'm unsure on how to correctly update RAID1 system On a non RAID it's quite clear to me: 1. First I do the update using: $ sudo apt update [sudo] password for admin: Hit:1 http://debia...

I've created a new user called admin but it't not showing up in the sudoers file! $ sudo adduser admin [sudo] password for dirk: Adding user `admin' ... Adding new group `admin' (1001) ... Adding new user `admin' (1001) with group `admin' ... Creating home directory `/home/admin' ... Copying files f...

Fixed it by adding ExecStartPre=/bin/sleep 30 to the Service section

I have just setup a linux server and seem to have issues sending emails during system startup! I always get: sendmail: cannot locate host smtpauths.bluewin.ch: Temporary failure in name resolution sendmail: could not send mail (account default from /root/.msmtprc) Once the system is up I can success...

I just changed the following:
So I think
Will do!

What would be the correct way to update GRUB if I made some changes to /etc/default/grub when running a RAID1 normally I do.. update-grub Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.10.0-18-amd64 Found initrd image: /boot/initrd.img-5.10.0-18-amd64 Warning: os-prober wi...

Yeah, you've absolutely right, it's even stated in line 4 in /etc/init.d/mdadm those who can read are at a clear advantage :lol: # cat /etc/init.d/mdadm #!/bin/sh # # Start the MD monitor daemon for all active MD arrays if desired. # This script is not used under systemd. # # Copyright © 2001-2005 M...

Nearly finished I guess :-) I configured mdadm for e-mail notifications and run the following simple test from mdadm to ensure e-mail notifications are working # mdadm --monitor --scan --test --oneshot /dev/md[[:digit:]]* ..and it nicely delivers two e-mail into my inbox, with the results from /proc...

md0 was in auto-read-only mode! # cat /proc/mdstat Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md0 : active (auto-read-only) raid1 sdb2[0] sda2[1] 15616000 blocks super 1.2 [2/2] [UU] resync=PENDING md1 : active raid1 sdb3[0] sda3[1] 960027648 blocks super 1...

So, i started allover again, and this time I also added a swap partition. After checking the raid I've seen that the swap partition hasn't synched yet! # cat /proc/mdstat Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] md1 : active raid1 sdb3[0] sda3[1] 96002764...

I applied all the changes and the system is still booting :-) but not matter how i set the boot order via the efibootmgr it's always mounting sdb1. I probably something again here again ... How can I find out from which partition the system is currently booting? If I grep dmesg I just see the UUID o...