black screen in Quantal on ASUS X101CH netbook

[michelf41]

I installed Lubuntu 12.04 with wubi, upgraded to Lubuntu Quantal 12.10.
I get a black screen with normal boot.
Works fine when booting in recovery then resume !
Added "nomodeset" to grub, but no result.

WORKAROUND: I changed /etc/default/grub like this :

- deleted "quiet" and "splash"
- changed GRUB_GFXMODE= to "1024x600"

---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
ApportVersion: 2.2.3-0ubuntu3
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: michel 1869 F.... lxpanel
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xdff00000 irq 46'
   Mixer name : 'Intel CedarTrail HDMI'
   Components : 'HDA:10ec0269,10438516,00100100 HDA:80862880,80860101,00100000'
   Controls : 19
   Simple ctrls : 9
CurrentDmesg:
 [ 36.451665] eth0: no IPv6 routers present
 [ 86.958316] cfg80211: Found new beacon on frequency: 2472 MHz (Ch 13) on phy0
DistroRelease: Ubuntu 12.10
InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Release i386 (20120423)
MachineType: ASUSTeK COMPUTER INC. X101CH
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcFB: 0 psbfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.4.0-5-generic root=UUID=F430478C304754B0 loop=/hostname/disks/root.disk ro recovery nomodeset
ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0
RelatedPackageVersions:
 linux-restricted-modules-3.4.0-5-generic N/A
 linux-backports-modules-3.4.0-5-generic N/A
 linux-firmware 1.81
Tags: quantal
Uname: Linux 3.4.0-5-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 03/08/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X101CH.0701
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X101CH
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX101CH.0701:bd03/08/2012:svnASUSTeKCOMPUTERINC.:pnX101CH:pvrx.x:rvnASUSTeKCOMPUTERINC.:rnX101CH:rvrx.xx:cvnASUSTeKCOMPUTERINC.:ct10:cvrx.x:
dmi.product.name: X101CH
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK COMPUTER INC.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1014035

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[michelf41 (michel-franckart)]

Please tell me if I did not run apport-collect correctly !

[penalvch (penalvch)]

michelf41, thank you for reporting this and helping make Ubuntu better. Could you please provide the information following https://wiki.ubuntu.com/DebuggingKernelBoot ? As well, could you please boot into a working Live CD and execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 1014035

[michelf41 (michel-franckart)]

apport information

[michelf41 (michel-franckart)]

apport information

[michelf41 (michel-franckart)]

apport information

[michelf41 (michel-franckart)]

apport information

[michelf41 (michel-franckart)]

apport information

[michelf41 (michel-franckart)]

apport information

[michelf41 (michel-franckart)]

apport information

[michelf41 (michel-franckart)]

apport information

[michelf41 (michel-franckart)]

apport information

[michelf41 (michel-franckart)]

apport information

[michelf41 (michel-franckart)]

apport information

[michelf41 (michel-franckart)]

apport information

[michelf41 (michel-franckart)]

apport information

[michelf41 (michel-franckart)]

apport information

[michelf41 (michel-franckart)]

apport information

[michelf41 (michel-franckart)]

apport information

[michelf41 (michel-franckart)]

apport information

[michelf41 (michel-franckart)]

apport information

[michelf41 (michel-franckart)]

Hi !
I did as told in https://wiki.ubuntu.com/DebuggingKernelBoot in normal mode.
And everything went OK ! (How could I make the change permanent ?)
But I do not understand how I can get a log file.
So on the off chance, here are the boot.log and bootstrao.log files.
Best regards

[michelf41 (michel-franckart)]

Now, bootstrap.log

[michelf41 (michel-franckart)]

Hi again.
I changed /etc/default/grub like this :

- deleted "quiet" and "splash"
- changed GRUB_GFXMODE= to "1024x600"

and booting in "normal " mode now seems OK !

[penalvch (penalvch)]

michelf41, thank you for providing the requested information. If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thanks in advance.

[Joseph Salisbury (jsalisbury)]

@michelf41,

Per comment #24, are you not seeing this bug anymore?

[Joseph Salisbury (jsalisbury)]

Or do you only not see this bug when using: GRUB_GFXMODE= to "1024x600"

[michelf41 (michel-franckart)]

I cannot reproduce the bug.
In /etc/default/grub I tried replacing GRUB_GFXMODE=1024x600
with
GRUB_GFXMODE=640x480 (followed by an update-grub)
then with the line commented (#) (followed by an update-grub)

But no difference : the system starts OK.
I am very sorry !
Or has an update coincidentally solved the problem ?

Best regards

On Tue, 2012-06-19 at 16:40 +0000, Joseph Salisbury wrote:
> Or do you only not see this bug when using: GRUB_GFXMODE= to "1024x600"
>

[michelf41 (michel-franckart)]

Still happens with Lubuntu 12.10 alpha 3. Remedy:
delete "quiet" and "splash" in /etc/default/grub, GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
run "update-grub"

[penalvch (penalvch)]

michelf41, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag:
needs-upstream-testing

This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the text:
needs-upstream-testing

If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

Please let us know your results. Thank you for your understanding.

[michelf41 (michel-franckart)]

Hi Christopher,
Thanks for your attention.
But that is far beyond my capabilities!
Awfully sorry.
Best regards.

Michel

On Sun, 2012-09-23 at 00:21 +0000, Christopher M. Penalver wrote:
> michelf41, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag:
> needs-upstream-testing
>
> This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the text:
> needs-upstream-testing
>
> If this bug is fixed in the mainline kernel, please add the following tags:
> kernel-fixed-upstream
> kernel-fixed-upstream-VERSION-NUMBER
>
> where VERSION-NUMBER is the version number of the kernel you tested.
>
> If the mainline kernel does not fix this bug, please add the following tags:
> kernel-bug-exists-upstream
> kernel-bug-exists-upstream-VERSION-NUMBER
>
> where VERSION-NUMBER is the version number of the kernel you tested.
>
> If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
> kernel-unable-to-test-upstream
> kernel-unable-to-test-upstream-VERSION-NUMBER
>
> where VERSION-NUMBER is the version number of the kernel you tested.
>
> Please let us know your results. Thank you for your understanding.
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>

[michelf41 (michel-franckart)]

linux-image-3.6.0-030300rc7-generic 201209232235 working fine !
Many thanks for patience.

[penalvch (penalvch)]

Marking Triaged as newest mainline tested and kernel-fixed-upstream-v3.6-rc7-quantal.

[penalvch (penalvch)]

michelf41, regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1014035/comments/32 :
>"linux-image-3.6.0-030300rc7-generic 201209232235 working fine !"

Just to clarify, you undid your WORKAROUND in /etc/default/grub , by changing the following lines back to:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
#GRUB_GFXMODE=640x480

Where GRUB_GFXMODE=640x480 is now commented out via the "#". Saved and closed the file, running at a terminal:
sudo update-grub

and rebooting into the mainline kernel found at http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-rc7-quantal/ ?

[michelf41 (michel-franckart)]

On Wed, 2012-09-26 at 14:36 +0000, Christopher M. Penalver wrote:
> michelf41, regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1014035/comments/32 :
> >"linux-image-3.6.0-030300rc7-generic 201209232235 working fine !"
>
> Just to clarify, you undid your WORKAROUND in /etc/default/grub , by changing the following lines back to:
> GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
Yes
> #GRUB_GFXMODE=640x480
>
> Where GRUB_GFXMODE=640x480 is now commented out via the "#".
Yes, it is commented out (not by me)
> Saved and closed the file, running at a terminal:
> sudo update-grub
Yes, I did.
>
> and rebooting into the mainline kernel found at http://kernel.ubuntu.com
> /~kernel-ppa/mainline/v3.6-rc7-quantal/ ?
Yes, that is it. System information says "Kernel Linux
3.6.0-030600rc7-generic (i386)"
But more importantly I have an X display again with this kernel.

(With updates later than quantal alpha 3, booting ended with the command
line! And when I tried startx or xinit, they failed on "segmentation
fault".)

Cheers!
>
> ** Changed in: linux (Ubuntu)
> Status: Triaged => Incomplete
>

[michelf41 (michel-franckart)]

Hell!
Today, I made an update/upgrade keeping Kernel Linux 3.6.0-030600rc7-generic (i386) :
Crash: no more X display again.

Summary:
Lubuntu quantal alpha 3 install: OK
Updating kernel to 3.6.0-030600rc7: OK
Upgrading the usual way excluding kernel, then booting with 3.6.0-030600rc7: no X, only command line.
Entering xinit: "Segmentation fault at address 0x3c ... aborting"

[penalvch (penalvch)]

michelf41, as per http://www.asus.com/Notebooks_Ultrabooks/Eee_PC_X101CH/#support an update is available for your BIOS (1203). If you update to this following https://help.ubuntu.com/community/BiosUpdate , does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Thank you for your understanding.

[Launchpad Janitor (janitor)]

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