ppringle's profile - activity

So, dropping back to Kernel version 4.13.16 from 4.13.3 fixes this issue. How very odd.

I have a Fedora 27 Workstation installation in a Hyper-V hypervisor. The VM has a Network Adapter added.

This network adapter is not showing up in the system, even though it was before (yesterday). I have no idea why this has happened. No changes have happened to the VM itself except that I've restarted the host and installed typical Windows Updates.

Example output:

# nmcli c
NAME     UUID     TYPE     DEVICE
ToLAN-bridge <uuid>  bridge  ToLAN-bridge
ToLAN-ether <uuid>  802-3-ethernet  --
httpd-LAN-veth <uuid>  802-3-ethernet  --
mysqld-LAN-veth <uuid>  802-3-ethernet  --

# nmcli d
DEVICE     TYPE     STATE     CONNECTION
ToLAN-bridge  bridge  connected  ToLAN-bridge
lo             loopback         unmanaged        --

# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: ToLAN-bridge: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether <MAC Address>  ff:ff:ff:ff:ff:ff
    inet 10.0.0.2/24 brd 10.0.0.255 scope global ToLAN-bridge
       valid_lft forever preferred_lft forever

I've tried removing and re-adding the Network Adapter in Hyper-V.

I'm not sure how to troubleshoot a network adapter not showing up like this. I can't find anything in the message buffer of the kernel about this (dmesg).

Alternative solution to entering it every time. Add xhost +local: to your .bash_profile file in your home folder. Although Fedora 25 uses Wayland, it is still running Xorg Server for backwards compatibility. Any command in .bash_profile is ran upon login.

Hi,

I have a pesky display that uses HDMI. It is not recognized and auto-enabled, but if it's already on and receiving a signal, it will work. On Xorg, I could use xrandr to configure and send a signal to this output even if it wasn't recognized as connected and the display would work. I can't seem to find an equivalent for Wayland however since xrandr is read only.

What things I've tried to get the display to work already:

• Reboot with only the HDMI connected and not my main display which uses VGA.
• Keeping the display from going into power savings mode.

I believe this display is configured in such a way that Wayland/Xorg don't know it's there unless it knows they are there.

What I mean is, the HDMI doesn't work this way when using other devices like a Windows computer or a console/satellite receiver. I assume it's because those devices send the signal anyway and so the display wakes up and acknowledges it. Whereas, the two display servers expect to receive something first. It may have something to do with a weird EDID (the few times it has worked has shown it as a 28" display when it is 27"). But those are just guesses.

This monitor is a secondary display that I'd prefer to use as my primary. My hardware setup is as follows:

• CPU with no iGPU
• Dedicated GPU (AMD R7 240)
• Primary 1600x900 display connected with VGA
• Secondary 2560x1440 display connected with HDMI