3/1/2024 0 Comments Macbook air extra screen![]() But I think your participation in this thread will actually just potentialy derail this thread from being about Arch Linux support. I wish you luck in solving your problem, and this thread might cetainly be one to watch. Sure you can go on a mint forum and the support will be the same because the underlying system is the same. I think that just really exemplifies the vast differences between any two distributions. You all use upstart, which is something that was actually created by ubuntu, while here we have been using systemd for a bit. Not only that, but the entire base of the operating system, the init, is entirely different in ubuntu. But typically, when other distribution users come here asking for help, they are often asking about things that are of a totally different version, and therefore totally different problems. I think that in this case, it actually might be that ubuntu is running a kernel that might be in line with Arch Linux for 13.04. This is because Arch Linux users tend to have software that is far more up to date than that of other distributions. ![]() ![]() These forums are for Arch Linux support only. This works, but is so slow that it is not feasible for what I want to show. Is there any other strategy? I bought a USB 2.0 external vga card. This is a very unpleasent because I have to use a variety of VGA projectors. Unfortunaletly, the workaround to boot with the display connected only works by random for me, so in some cases it does, in others not. I can confirm that the udev rule helps somewhat. I'm not running archunix but Ubuntu 13.04 on a macbookair mid-2012 and I experince exactly the same problems described above. I hope you are able to get closer to a resolution of your current challenges, based on some of my findings. However, it's a mystery to me, why this rule is not, or was not included with my install. I am now able to use xrandr and set up scripts to automate the screen proportions and output etc. # the display for non-KMS drivers tag the framebuffer device instead.ĮNV="1" # Tag the drm device for KMS-supporting drivers as the primary device for # do not edit this file, it will be overwritten on update I have yet to find a method to enable the DP-1 port, through kernel space - switching TTY's doesn't help a thing. However, if I attach my monitor during GRUB, it will be detected during boot, and afterwards the udevadm monitor is able to pickup the DP1 change - But I'd really like to know what or how to manually ensure that DP-1 is always (or on demand) enabled, even when using KMS (which is req. So my issue is somehow related to KMS, and the fact that the system is not picking up on the attached monitor automatically, or the very least have some method of enabling it manually, where I am currently not allowed to (presumably because of KMS) change the state of the port from userspace I was going to fix up a udev rule, but since the port is set as "disabled" I do not get any udev event, when pluggin in the display. However it doesn't change a thing, since the port will be "disabled" after a while of inactivity. power/control - and settings this value, you are allowed to. I also tried to see if it was related to the power settings under. ![]() Trying to change the permissions is a fools errand. I found out that my DP-1 port is reported as disabled by cat'ing /sys/class/drm/card0-DP-1/enabled, changing this, which I am not allowed, is mostlikely due to KMS. So I am coming closer to an explanation of why I cannot get the display working. While this is somethign I can somewhat live with, the other mentioned workarounds are somewhat a pain On a side note, when I have done the above mentioned workarounds to get the external display working and then disconnecting the display, and performing a "xrandr -auto", I then have to switch back and forth another tty, while the display is connected to get xrandr to detec the display again. If the first work-around doesn't work, if I then boot into my Live ISO of ubuntu 13.04 (from a ISO in GRUB), it then gets detected during modeset, and I can proceed to reboot into Arch again. Reboot with the external monitor connected, works sometimes.Ģ. So the possible work-arounds that I have found are so far:ġ. I just wanted to add that I am having the same issue on my Thinkpad X1C, with Intel HD4000 as well I recall that connecting an monitor to my DP1 (mini-display) used to work just fine but however, recently I am experiencing whilst the system is bootet it now gives me "DP1 is disconnected", when connecting an external monitor.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |