You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 Re: Hardware & System Configuration » [SOLVED] Dual monitor configuration » 2022-03-08 12:05:14
Success!, THANK YOU!
#2 Re: Hardware & System Configuration » [SOLVED] Dual monitor configuration » 2022-03-08 05:04:29
Thanks once again, How did I miss that? OK, now it's this (sometimes It just doesn't want to work!):
:~# xrandr --output HDMI-A-0 --auto --right-of eDP
Can't open display
I tried rebooting and then running the command and it did the same thing.
#3 Re: Hardware & System Configuration » [SOLVED] Dual monitor configuration » 2022-03-07 23:04:34
Thanks for the reply. I seem to be on the right track but a problem has cropped up. Here is the output from xrandr and the command you suggested:
:~$ xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
eDP connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm
1920x1080 59.98*+ 39.98
1680x1050 59.98
1280x1024 59.98
1440x900 59.98
1280x800 59.98
1280x720 59.98
1024x768 59.98
800x600 59.98
640x480 59.98
HDMI-A-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 458mm x 258mm
1920x1080 60.00*+
1680x1050 59.88
1600x900 60.00
1280x1024 60.02
1440x900 59.90
1280x800 59.91
1280x720 60.00
1024x768 60.00
800x600 60.32
640x480 59.94
720x400 70.08
:~$ xrandr --output HDMI-A-0 --auto --right-of "Screen 0:"
xrandr: cannot find output "Screen 0:"
:~$ xrandr --output HDMI-A-0 --auto --right-of Screen 0:
xrandr: unrecognized option '0:'
Try 'xrandr --help' for more information.
:~$ xrandr --output HDMI-A-0 --auto --right-of Screen
xrandr: cannot find output "Screen"
:~$ xrandr --output HDMI-A-0 --auto --right-of "Screen 0"
xrandr: cannot find output "Screen 0"
Any ideas?
#4 Re: Hardware & System Configuration » [SOLVED] Dual monitor configuration » 2022-03-07 14:32:38
You are right. I have upgraded to Chimeara using Xfce. As stated the second display is detected and I have attempted to set it up but there does not appear to be an option to do what I want to do. I have tried a couple of options with no success.
#5 Hardware & System Configuration » [SOLVED] Dual monitor configuration » 2022-03-07 08:17:41
- gdstew
- Replies: 8
I have a HP Ryzen 7 laptop with HDMI output and I would like to use the second monitor as an extension of the laptop screen giving me a 3840 x 1080 display. The second monitor is detected but simply displays the same thing as the laptop monitor. Is there any setup configuration or any other way to make this work?
#6 Re: Other Issues » [SOLVED] serial terminal login stopped working » 2021-11-25 12:26:08
After writing my last reply I just decided to upgrade to Devuan Chimaera which was something I was thinking about doing anyway. I was reluctant to "rock the boat" until I was more certain that the new release would not cause any problems especially during the upgrade and I am pretty much there now as I have already upgraded another computer to it and it went very well. Thanks again.
#7 Re: Other Issues » [SOLVED] serial terminal login stopped working » 2021-11-25 04:59:22
Thanks for the reply. I will look into that but if it is not there now it was also not there when it was working. This was not a new install, the SATA SSD I'm trying to boot from now is exactly the same one it was working with before. And before I tried to boot from it again I ran e2fsck on all the partitions on that drive booting it from a hard drive I use with by motherboard test stand and there were no errors. That is the really frustrating part, I've done very similar things before with no problems so it should have just worked. The other thing that is very odd is that I can enter in text at the log in prompt from the same SATA SSD drive when a graphics card and keyboard is installed using the original install inittab that was saved before I modified it to boot from the serial terminal.
#8 Other Issues » [SOLVED] serial terminal login stopped working » 2021-11-25 00:47:45
- gdstew
- Replies: 4
I have a problem at the serial terminal log in prompt that I have tried everything I know to try to fix it with no results. The computer is an NFS server that was using an older motherboard that started emitting burning down the house smells and had to be shut down. It was/will be running Devuan Beowulf with a 4.19.0-18 kernel and fully working serial terminal when it was shut down. Before doing anything else I installed the new motherboard changing nothing else and booted it using a drive I use for testing also running Devuan Beowulf, ran e2fsck on all partitions on the NFS server drive with no errors found. After replacing the motherboard it will no longer accept input from the serial terminal at the log in prompt. The GRUB boot screen will accept input from the serial terminal and I have also rechecked the serial hardware using minicom just to be sure.
After verifying the hardware I checked the inittab and securetty files and they were correct. I then upgraded 2 packages and reinstalled the kernel image (it does work with a graphics card and keyboard installed) with no effect. I have also noticed that there are no periodic disk accesses happening so it looks like the kernel may be hanging up after the log in prompt. So I am now looking for some solutions short of reinstalling Devuan.
Thanks.
#9 Re: Hardware & System Configuration » persistent network interface names with multiple interface cards » 2018-12-05 23:44:11
I finally got back to trying using interface names other than ethN and it does indeed fix the problem I was seeing. Thanks !
Here are the details:
This is the new setup in the 70-persistent-net.rules file
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:01:29:d3:0f:01", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="ethr0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="04:4b:80:08:80:03", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="ethr1"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:15:e9:bd:1c:b7", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="ethr2"
and this is the new /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug ethr1
iface ethr1 inet dhcp
# The distributed compile/cluster network interface
allow-hotplug ethr0
iface ethr0 inet static
address 192.168.10.109
netmask 255.255.255.0
# The first test interface
allow-hotplug ethr2
iface ethr2 inet static
address 192.168.69.96
netmask 255.255.255.0
and the network interfaces wired interface name in wicd preferences was changed to ethr1
#10 Re: Hardware & System Configuration » persistent network interface names with multiple interface cards » 2018-11-27 04:30:17
Thank you both for your replies.
I should have been a little clearer with my description of the problem. This computer
is also used to test hardware. eth0 and eth1 (always present on the motherboard) swap
names when the eth2 card is inserted into a PCI slot to test it. When I used
70-persistent-net.rules with (pre-systemd) Debian this did not happen and I got the
persistent net names I wanted which is, as I understand it what 70-persistent-net.rules
was for. I'm not sure if they swap back when eth2 is removed. I had a new
problem with my test setup, my ISP overriding ping addresses, so it got a little
hectic as I had to spend time finding a fix for a previously working test setup.
In the process of searching for answers to this problem I found out that systemd
programmers are now responsible for udev and that eudev is a Gentoo fork of the
earlier udev. It does not seem to work like it use to when it comes to persistent
net names.
I tried @fsmithred's idea and as far as I could tell it made no difference even with
the "bus addresses" being fixed on eth0 and eth1 and with eth2 in the same PCI slot
through both reset and power sequence events.
I would like to be able to force which network interface name is used for a particular
hardware interface to maintain consistent network interface names across multiple
computers with multiple Ethernet interfaces in my distributed compile/cluster setup
and of course on the test computer. From your response it looks like using my own
naming convention is the best (OK, easiest) route. This computer has been moved
off of my test bench while I try to install Devuan on my first UEFI motherboard so it
will be a while before I can try it.
#11 Hardware & System Configuration » persistent network interface names with multiple interface cards » 2018-11-20 06:23:19
- gdstew
- Replies: 4
How can I get persistent net interface names on multiple network interfaces? I am using the wicd network manager on my primary network interface and it is the only
one configured in wicd.
When I tried using a hand generated /etc/udev/rules.d/70-persistent-net.rules file I get these error messages during boot:
Waiting for /dev to be fully populated...
[...] udevd[397]: Error changing net interface name eth2 to eth1: File exists
[...] udevd[395]: Error changing net interface name eth1 to eth0: File exists
[...] udevd[393]: Error changing net interface name eth0 to eth2: File exists
This is the setup in the 70-persistent-net.rules file:
UBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:01:29:d3:0f:01", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="04:4b:80:08:80:03", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:15:e9:bd:1c:b7", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"
and this is the /etc/network/interfaces file:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth1
iface eth1 inet dhcp
# The distributed compile/cluster network interface
allow-hotplug eth0
iface eth0 inet static
address 192.168.10.109
netmask 255.255.255.0
# The first test interface
allow-hotplug eth2
iface eth2 inet static
address 192.168.69.96
netmask 255.255.255.0
and this is what ifconfig reports:
root@testy123:# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.10.109 netmask 255.255.255.0 broadcast 192.168.10.255
inet6 2605:6001:e20b:9400:215:e9ff:febd:1cb7 prefixlen 64 scopeid 0x0<global>
inet6 fe80::215:e9ff:febd:1cb7 prefixlen 64 scopeid 0x20<link>
ether 00:15:e9:bd:1c:b7 txqueuelen 1000 (Ethernet)
RX packets 146 bytes 15152 (14.7 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 7 bytes 606 (606.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 18
eth1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:01:29:d3:0f:61 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 18
eth2: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.69.96 netmask 255.255.255.0 broadcast 192.168.69.255
ether 04:4b:80:08:80:03 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 8 bytes 480 (480.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8 bytes 480 (480.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
All of the searches I've googled come up with systemd related responses. I've also scanned and searched this forum and could not find any that helped although a couple of them addressed related problems.
Pages: 1
Board footer
