@Gilles, as @Celada found, the question had already been asked before. Yes "avoid loop altogether" goes maybe a bit too far. But adding "to process text" is not necessarily enough (though is right in 99.9% of the case, which is why the dup question focuses on that).

@Celada On n'est pas aussi mono-culturelles que ça!

Curious. The crypto Area 51 page has

1383 days in beta. 10.5 questions a day. But the site only lists 6,409 questions.

that should be over 14,000.

@FaheemMitha They're probably not counting closed or deleted.

@FaheemMitha the questions/day figure is over the last N days (N=14 IIRC)

because what matters is current trends, the all-time average is completely meaningless

@Gilles oh

@terdon that would be a lot of closed/deleted questions.

Ok, so the recent trend is way above the historical average then.

@FaheemMitha True, Gilles's suggestion makes more sense.

That sites seems to be doing pretty well. And looks like a useful resource. Seeing how important crypto is becoming.

propublica.org/article/…

Does this sound familar?

Though this particular story has a happy ending.

Hello everybody!

Is anyone here familiar with the i915 driver in the Linux kernel?

@HenriMenke If you have a question, you can ask it on the site.

I doubt anyone is specially familiar with i915. There are a lot of Linux drivers.

@FaheemMitha Thank you for your response, but I think I might need some interactive form of problem solving, as right now my problem is not very specific. I only have a couple of log snippets and a non-working screen.

@FaheemMitha I guess it is better to move to a Debian forum for that one.

@HenriMenke Ok, well go ahead, then.

@HenriMenke You could. But there are some Debian users here. Can't say who is listening, though.

What's on your mind?

Note: #debian on OFTC is certainly also an option.

@FaheemMitha When I plug in my VGA-monitor with a DisplayPort adapter it isn't detected (after updating to Jessie and thus Linux 3.16 today).

@HenriMenke was it working before? Were you using wheezy?

Post your xorg log.

gist is a fairly painless way to do it.

@FaheemMitha Yes, I was using wheezy before with kernel 3.2.0 and everything worked perfectly.

I mean gist-paste. From the gist package.

Ok. And what is your display card?

@FaheemMitha gist.github.com/anonymous/0b1c8f24c0396bb9e472

@FaheemMitha Intel HD4000

@HenriMenke Reinstall 3.2 and see if that fixes your problem.

actually, it should still be there. unless the upgrade removed it. and it normally wouldn't.

@FaheemMitha Unfortunately, that doesn't work. The Xorg drivers in Jessie are not compatible with Linux 3.2.0.

@FaheemMitha I booted Debian using drm.debug=0xe and did a dmesg | grep drm right after plugging in the monitor.

@HenriMenke bummer

[  235.146365] [drm:intel_hpd_irq_handler] hotplug event received, stat 0x00200000
[  235.146386] [drm:intel_hpd_irq_handler] Received HPD interrupt on PIN 4 - cnt: 0
[  235.146436] [drm:i915_hotplug_work_func] running encoder hotplug functions
[  235.146443] [drm:i915_hotplug_work_func] Connector HDMI-A-1 (pin 4) received hotplug event.
[  235.146448] [drm:i915_hotplug_work_func] Connector DP-1 (pin 4) received hotplug event.
[  235.146455] [drm:intel_hdmi_detect] [CONNECTOR:19:HDMI-A-1]
[  235.159342] [drm:drm_do_probe_ddc_edid] drm: skipping non-existent adapter i915 gmbus dpb

What are your error symptoms?

@FaheemMitha The monitor does neither show up in xrandr nor does udevadm monitor report any interrupts.

No, I mean you don't get an image? Black screen?

@FaheemMitha The screen doesn't do anything, when plugged in. Actually, I don't have a /etc/X11/xorg.conf.

@HenriMenke oh. hmm.

@FaheemMitha I have the feeling, that I'm just lacking some yet to be determined boot parameter for the kernel.

"When I plug in my VGA-monitor with a DisplayPort adapter" Is this a laptop?

@HenriMenke I don't see any errors in your X log.

@FaheemMitha Indeed, ThinkPad X1.

Ok, so does the native display come up ok?

@FaheemMitha Yes, I'm typing on it right now.

You are trying to send the output to an external screen?

@HenriMenke Ok. I don't think the problem is with X. Your log (if you have posted the correct one) shows no errors. The problem is that nothing happens when you plug in your external monitor, right? It doesn't pick up the signal?

Have you tried restarting X with the monitor plugged in?

With wheezy, if you plugged in your monitor, did it pick up the signal immediately?

@FaheemMitha Restarting X doesn't help. The screen is not detected.

@HenriMenke ok

I think there are some key combinations you can press on the Thinkpad to send it to an external display. You never had to use those?

@FaheemMitha There are no such keys in this model.

I assume you have checked all cables?

@FaheemMitha Cables are intact and plugged in.

@HenriMenke ok

@HenriMenke ok. usually the way it works is that something is monitoring when your monitor is plugged in. That thing is broken, I think. Not directly related to X.

This appears related

@HenriMenke do you happen to know how your monitor was automatically detected in wheezy?

@FaheemMitha I have no clue how the display was detected in wheezy.

@FaheemMitha Thanks for the link, but this implies that the display shows up in xrandr.

@HenriMenke true

there's a link for using udev

However, these links are all old. I would have thought there would be a better way now.

@HenriMenke I suggest asking a question on the site.

@FaheemMitha The failure must occur one layer below all of this, because /sys/class/drm/card0-DP-1/status always contains disconnected and udevadm monitor does not report anything when plugging in and out the external display.

@HenriMenke yes, I see. what does /sys/class/drm/card0-DP-1/status get triggered by, though?

@FaheemMitha That is a good question and might be the key to the solution.

@HenriMenke I recommend posting a question.

@FaheemMitha I found some thread in the Arch Linux forum which blames systemd bbs.archlinux.org/viewtopic.php?id=193504

The bottom line is that for this to work, when the monitor is plugged in, it must signal an event, and that must be picked up by something which then tells the X server to change what it is doing.

@HenriMenke Entirely possible that systemd has changed the way these things are done.

/me wonders if there is a jessie tag in use yet.

@HenriMenke the relevance of this isn't entirely clear. Are you quite sure that there is a compat problem between the kernel and X? that would be slightly unusual. The kernel and user space by design are very loosely coupled.

@FaheemMitha we burned it

@Braiam oh. can we resurrect it? like a phoenix from its ashes?

no

we don't need a tag for each version of each distro, it gets silly

@FaheemMitha “yet”? Jessie has existed for a couple of years

@Gilles True, but it just became stable. Which means a lot more people will be using it, probably.

But there are very few questions that warrant a version-specific tag, and people heavily abuse them, so we don't want such tags

@FaheemMitha so their issues will be about Debian, not specifically about jessie

@Gilles I'm not arguing with you.

or @Braiam.

jessie means “my question is about jessie and nothing else”, but people mostly use it to mean “I'm using jessie”

@FaheemMitha the kernel provides some bits that the X driver needs to access the hardware. Kernel/X incompatibilities with video drivers are a common issue.

I have used jessie for more than a year and it never occurred me a question specific to jessie

except probably "when will jessie be released"

@Gilles ok

@HenriMenke I've had this problem intermittently with my work laptop (also i915). Connect to an external screen at my workstation, works. Go give a presentation, the projector isn't detected :(

@Braiam “How do I avoid systemd on a wheezy → jessie upgrade?”

@Gilles oh yeah that

systemctl mask systemd-backlight@backlight:acpi_video0.service
systemctl mask systemd-backlight@backlight:intel_backlight.service

That's what I did. I'll try to connect to the display later.

@Gilles True, X isn't pure user space. So that observation doesn't really to the X case.

does really -> doesn't really apply

That's what we get for being thorough :)

@terdon TL;DR FTW!

I asked a question once and got an explanation, but no answer to my question...

(I only accepted because it looks good, but I still don't know how to apply it...)

I'll ask another question in a year or so, when I've grown up a bit...

:P ;-)

@Fabby What are you missing? I thought he explained all the parts quite nicely.

(and maybe I should have asked for "help me to fish" instead of "teach me to fish"

How do I incorporate it into my prompt?

red for root and admin, green for user, orange for error?

It's way above my head!

@Fabby Ah. Hmm, let me have a go.

I'll read the answer again after I've finished reading the Linux System's admin manual...

@terdon It's OK... It's just to show you that Darth Vader is a bit right...

You guys are way too smart and that's why I only lurk in the corners...

I learn more here then in AU,

@Fabby Oh, I'm not arguing. Many of the answers here are way over my head.

but i's still way over my head...

And I took it as a compliment, not a slight.

@terdon Huh? No offence intended! :/

@Fabby Oh, not you. I meant I did not take Darth's comment as a slight. Nor yourds, of course.

:D

@Fabby I'm not sure it's possible to get orange.

yellow...

Yellow is possible. Unfortunately, I'm not up to figuring out how the inheritance works (bash.bashrc and .bashrc) at this time of night. I'll have a go at it tomorrow. It's a neat problem.

:D Next week is fine as well...

.bashrc overwrites bash.bashrc...

I keep all my stuff in bash.bashrc anyway unless impossible, and then I need to change it for all users including SKEL...