Summary: | Suspected Kernel problem with Intel driver on Baytrail-T Z3735E tablet - black screen on boot | ||||||
---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Jan Brøndum Johansson <thunder.androidx86> | ||||
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
Status: | CLOSED INVALID | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
Severity: | major | ||||||
Priority: | medium | CC: | intel-gfx-bugs | ||||
Version: | XOrg git | ||||||
Hardware: | x86-64 (AMD64) | ||||||
OS: | Linux (All) | ||||||
Whiteboard: | |||||||
i915 platform: | BYT | i915 features: | |||||
Attachments: |
|
Description
Jan Brøndum Johansson
2016-10-22 12:51:06 UTC
Add drm.debug=14 module parameter, *remove* any nomodeset or i915.modeset=0 parameters, attach dmesg all the way from boot to the problem. You may need to use netconsole or ssh into the device or log in blind to get the dmesg. (In reply to Jani Nikula from comment #1) > Add drm.debug=14 module parameter, *remove* any nomodeset or i915.modeset=0 > parameters, attach dmesg all the way from boot to the problem. You may need > to use netconsole or ssh into the device or log in blind to get the dmesg. Hi and thank you for answering:) I did as you said, but then it ended up in black screen as so many other times when not using nomodeset or i915.modeset=0 I'm not into how to use netconsole, ssh or log in blind - i have no idea what that is. The reason for posting here, is that other places like ask ubuntu or the forums they don't know what to do about this. I will be happy to work with you on this but need Noob guidance - basically just tell me what to do:) JBJ Created attachment 129221 [details]
dmesg output
Hi,
I have a Surftab twin 10.1 (ST10432-8) with a x5-Z8300 and I get the same problem (no rotation with nomodeset, no video without it). Here's full dmesg having only drm.debug=14
Jani any more information that you can provide Jan he is willing to collaborate So the hard part here is that while David's problem from comment #3 might be the same as the original report, we don't know if it really is because we don't have logs from Jan, the original reporter. Jan has a Baytrail tablet, while David has a Cherrytrail. David has a DSI display, I suspect Jan has too but no confirmation. Anyway, might be two things at play here. First, a bunch of fixes have recently landed in drm-tip branch of https://cgit.freedesktop.org/drm-tip which fix stuff for DSI. You should try kernel built from that. Second, you should ensure you have these kernel config options set when building the kernel: CONFIG_PWM=y CONFIG_PWM_CRC=y CONFIG_I2C_DESIGNWARE_PLATFORM=y CONFIG_I2C_DESIGNWARE_PCI=y CONFIG_INTEL_SOC_PMIC=y CONFIG_DRM_I915=m (In reply to Jan Brøndum Johansson from comment #2) > I'm not into how to use netconsole, ssh or log in blind - i have no idea > what that is. The reason for posting here, is that other places like ask > ubuntu or the forums they don't know what to do about this. Set up networking and sshd on the device. Use ssh from another device to log on to the tablet. Use nomodeset to set this up, and ensure it's working straight from the boot without login. With that working, remove nomodeset, reboot, and ssh to the device. You should be able to get dmesg remotely. If that sounds complicated, or you have no idea what I'm talking about, I'm afraid I'm going to have to ask you to use the other forums to get it done. (There are other ways too, but this should be pretty straightforward.) based on the lack of activity and response in the bug the bug will be closed, if the issue is detected in a newer configuration please open a new bug |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.