On Tue, 16.06.15 23:25, Lennart Poettering (lenn...@poettering.net) wrote:
> > In the same sysyfs directory there's "enabled" (indicating that an output
> > is logically in use) and "dpms" (which shows the dpms state, but that is
> > not clamped to Off when the output isn't in use because of ABI h
>
> > > The biggest change here is 4.1 stopped forcing the probe from sysfs
> > > precisely because systemd was hitting them so often for illogical
> > > reasons (being docked depends on having the lid open and an
> > > external display connected!). To force the probe, you must do
> > > $ echo
On Wed, Jun 17, 2015 at 10:29:48AM +0200, David Herrmann wrote:
> Hi
>
> On Tue, Jun 16, 2015 at 11:25 PM, Lennart Poettering
> wrote:
> > On Tue, 16.06.15 13:47, Daniel Vetter (dan...@ffwll.ch) wrote:
> >
> >> > But what does that actually mean? should logind ever echo "detect"
> >> > itself int
Hi
On Tue, Jun 16, 2015 at 11:25 PM, Lennart Poettering
wrote:
> On Tue, 16.06.15 13:47, Daniel Vetter (dan...@ffwll.ch) wrote:
>
>> > But what does that actually mean? should logind ever echo "detect"
>> > itself into the file? Should it follow uevents for the files? How
>> > should treat this f
On Tue, Jun 16, 2015 at 11:28:19PM +0200, Lennart Poettering wrote:
> On Tue, 16.06.15 12:37, Chris Wilson (ch...@chris-wilson.co.uk) wrote:
>
> > On Tue, Jun 16, 2015 at 01:17:29PM +0200, Lennart Poettering wrote:
> > > On Tue, 16.06.15 10:14, Chris Wilson (ch...@chris-wilson.co.uk) wrote:
> > >
On Tue, 16.06.15 12:37, Chris Wilson (ch...@chris-wilson.co.uk) wrote:
> On Tue, Jun 16, 2015 at 01:17:29PM +0200, Lennart Poettering wrote:
> > On Tue, 16.06.15 10:14, Chris Wilson (ch...@chris-wilson.co.uk) wrote:
> >
> > > The biggest change here is 4.1 stopped forcing the probe from sysfs
> >
On Tue, 16.06.15 13:47, Daniel Vetter (dan...@ffwll.ch) wrote:
> > But what does that actually mean? should logind ever echo "detect"
> > itself into the file? Should it follow uevents for the files? How
> > should treat this file?
>
> Ok here's how this is supposed to work:
> - If anything chang
On Tue, 16.06.15 12:25, Daniel Vetter (dan...@ffwll.ch) wrote:
> > The biggest change here is 4.1 stopped forcing the probe from sysfs
> > precisely because systemd was hitting them so often for illogical
> > reasons (being docked depends on having the lid open and an
> > external display connecte
On Tue, Jun 16, 2015 at 01:22:00PM +0200, Lennart Poettering wrote:
> B1;4002;0cOn Tue, 16.06.15 12:25, Daniel Vetter (dan...@ffwll.ch) wrote:
>
> > > The biggest change here is 4.1 stopped forcing the probe from sysfs
> > > precisely because systemd was hitting them so often for illogical
> > > r
On Tue, Jun 16, 2015 at 01:17:29PM +0200, Lennart Poettering wrote:
> On Tue, 16.06.15 10:14, Chris Wilson (ch...@chris-wilson.co.uk) wrote:
>
> > The biggest change here is 4.1 stopped forcing the probe from sysfs
> > precisely because systemd was hitting them so often for illogical
> > reasons (
B1;4002;0cOn Tue, 16.06.15 12:25, Daniel Vetter (dan...@ffwll.ch) wrote:
> > The biggest change here is 4.1 stopped forcing the probe from sysfs
> > precisely because systemd was hitting them so often for illogical
> > reasons (being docked depends on having the lid open and an
> > external displa
On Tue, 16.06.15 10:14, Chris Wilson (ch...@chris-wilson.co.uk) wrote:
> The biggest change here is 4.1 stopped forcing the probe from sysfs
> precisely because systemd was hitting them so often for illogical
> reasons (being docked depends on having the lid open and an
> external display connecte
On Tue, Jun 16, 2015 at 10:14:46AM +0100, Chris Wilson wrote:
> On Tue, Jun 16, 2015 at 11:12:22AM +0300, Jani Nikula wrote:
> > On Tue, 16 Jun 2015, Daniel Vetter wrote:
> > > On Tue, Jun 16, 2015 at 01:45:00AM +0200, Lennart Poettering wrote:
> > >> heya,
> > >>
> > >> I am experiencing somethi
On Tue, Jun 16, 2015 at 11:12:22AM +0300, Jani Nikula wrote:
> On Tue, 16 Jun 2015, Daniel Vetter wrote:
> > On Tue, Jun 16, 2015 at 01:45:00AM +0200, Lennart Poettering wrote:
> >> heya,
> >>
> >> I am experiencing something weird with the i915 driver in kernel
> >> 4.1.0-0.rc8 (precisely 4.1.0-
On Tue, 16 Jun 2015, Daniel Vetter wrote:
> On Tue, Jun 16, 2015 at 01:45:00AM +0200, Lennart Poettering wrote:
>> heya,
>>
>> I am experiencing something weird with the i915 driver in kernel
>> 4.1.0-0.rc8 (precisely 4.1.0-0.rc8.git0.1.fc23.x86_64 from fedora
>> rawhide):
>>
>> On my laptop, wh
On Tue, Jun 16, 2015 at 01:45:00AM +0200, Lennart Poettering wrote:
> heya,
>
> I am experiencing something weird with the i915 driver in kernel
> 4.1.0-0.rc8 (precisely 4.1.0-0.rc8.git0.1.fc23.x86_64 from fedora
> rawhide):
>
> On my laptop, when I type this:
>
> grep . /sys/class/dr
heya,
I am experiencing something weird with the i915 driver in kernel
4.1.0-0.rc8 (precisely 4.1.0-0.rc8.git0.1.fc23.x86_64 from fedora
rawhide):
On my laptop, when I type this:
grep . /sys/class/drm/card0*/status
I usually get this:
/sys/class/drm/card0-DP-1/status:disconn
17 matches
Mail list logo
