« first day (1660 days earlier)   

8:37 AM
@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).
8 hours later…
4:07 PM
@Celada On n'est pas aussi mono-culturelles que ça!
2 hours later…
6:24 PM
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.
7:10 PM
Does this sound familar?
Though this particular story has a happy ending.
7:24 PM
Hello everybody!
Is anyone here familiar with the i915 driver in the Linux kernel?
7:39 PM
@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.
7:57 PM
@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 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.
8:02 PM
@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?
@HenriMenke is your original xorg.conf still there? Can you paste it?
@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?
8:06 PM
@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?
8:08 PM
@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?
8:15 PM
@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
Q: A tool for automatically applying RandR configuration when external display is plugged in

Yaroslav Fedevychis there a tool which enables one to: remember current RandR configuration (position, orientation, resolution etc) on per-monitor basis, automatically apply last known good configuration as soon as the display is plugged in, with no need to muck around with applets or xrandr(1)? The configura...

@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
Q: How to create a callback for "monitor plugged" on an intel graphics?

ReactormonkI've got an eeepc with an intel graphics. I'd like to hook a script to the event of a monitor plugged via VGA. How to do that?

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.
8:31 PM
@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.

« first day (1660 days earlier)