Mainline Kernel 3.8.0 , black screen after boot with acer v3-771g

Bug #1099098 reported by yusuf75 on 2013-01-13
60
This bug affects 11 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
High
Unassigned

Bug Description

Hello,

the problem only occurs with kernel 3.8.0.
After installing mainline kernel 3.8.0, i get immediately after boot a black screen ( display turns off ).

The problem also occurs with the ubuntu- livecd 13.04 daily (with kernel 3.8.0).
Ubuntu 13.04 daily cd work with kernel 3.7 without problems.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in update-manager (Ubuntu):
status: New → Confirmed
Jordi Coma Garcia (jordi-coma) wrote :

I have a Acer v3-571g, I have the kubuntu installed. Kernel 3.8 only works with an external display. The nomodeset trick doesn't work.

Jordi Coma Garcia (jordi-coma) wrote :

the nomodeset brings to command line only, not the X.
The X11 log shows it cannot find displays.

Sami Jaktholm (sjakthol) on 2013-01-19
affects: update-manager (Ubuntu) → linux (Ubuntu)

yusuf75, thank you for reporting this and helping make Ubuntu better. Are you able to boot into a Quantal live CD via http://releases.ubuntu.com/quantal/ ?

If so, could you please execute the following via a terminal:
apport-collect 1099098

tags: added: needs-kernel-logs needs-upstream-testing regression-potential
Changed in linux (Ubuntu):
status: Confirmed → Invalid
importance: Undecided → High
status: Invalid → Incomplete
Jordi Coma Garcia (jordi-coma) wrote :

For me the problem is solved after install linux 3.8.0.0-r5 from the mainline repository.

GaryParr (gary-garyparr) wrote :

Any idea when r5 will make it into the daily build? I can't boot the live USB due to this issue on a Dell XPS 12.

James Sawyer (sawyer12) wrote :

This affects my Sony VAIO Laptop (SVE1711C5E) Tested Kernels 3.8.0 - 3.8.2. The following workaround works perfect for me. Its kind of strange. Go into Recovery Mode. Do ANY of the following options, The easiest is Enable Networking, You can do ANY so far I have tested. Then just go to resume. It boots streight into the desktop.

Steven Usdansky (usdanskys) wrote :

I'm seeing the black screen and no x on my desktop with the Lubuntu 13.04 nightly build I downloaded on March 15. Seems to be a modesetting problem. Saw the same problems with Fedora's 3.8 kernels. The 3.9 kernels show garbled dots instead of text, but still can't get into X. This is all with the nouveau driver. X-vesa works, but is an unacceptable option; I've got a 1680x1050 monitor.
linux-image-3.8.0-12-generic 3.8.0-12.21
linux-image-extra-3.8.0-12-generic 3.8.0-12.21
linux-image-generic 3.8.0.12.26

xserver-xorg-video-nouveau 1:1.0.6-0ubuntu3b1
libdrm-nouveau2:i386 2.4.42-0ubuntu2

video is onboard GeForce 9100

ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: denis 1554 F.... pulseaudio
DistroRelease: Ubuntu 13.04
HibernationDevice: RESUME=UUID=ec8743a2-88ba-4c72-9f8f-54f4efffa117
InstallationDate: Installed on 2013-04-06 (0 days ago)
InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
MachineType: Acer Aspire V3-771
MarkForUpload: True
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-16-generic root=UUID=8da85e86-bbfe-4dce-bfec-0a108fbca501 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-16-generic N/A
 linux-backports-modules-3.8.0-16-generic N/A
 linux-firmware 1.104
Tags: raring
Uname: Linux 3.8.0-16-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 01/14/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.16
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: VA70_HC
dmi.board.vendor: Type2 - Board Vendor Name1
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.16:bd01/14/2013:svnAcer:pnAspireV3-771:pvrV2.16:rvnType2-BoardVendorName1:rnVA70_HC:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire V3-771
dmi.product.version: V2.16
dmi.sys.vendor: Acer

tags: added: apport-collected raring

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Denis V. Kuznetsov, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.

tags: removed: apport-collected raring
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
=KK= (sevkme) wrote :

yes , I have the same problem .

=KK=, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

Thank you for your understanding.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers