[MSI 880GM-E41] No Desktop Display for kernel versions

[FlacBean02]

Upon logging in with Username and Password, desktop will not show. Black screen...

No Desktop Display for kernel versions
3.11.0-19.33
3.11.0-20.34

Desktop displays for kernel versions
3.11.0-18.32
and older....

Installed Propitery drivers
AMD Catalyst™ 14.3 LINUX Beta V1.0 Driver

Running Ubuntu 13.10 with all updates including proposed.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-18-generic 3.11.0-18.32
ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
Uname: Linux 3.11.0-18-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: master 1820 F.... pulseaudio
 /dev/snd/controlC0: master 1820 F.... pulseaudio
Date: Tue Apr 8 15:45:52 2014
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=ab6d2e50-fef6-4f8c-9d79-96cffdb4cd9f
InstallationDate: Installed on 2013-12-28 (101 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: MSI MS-7623
MarkForUpload: True
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-generic root=UUID=b38cf669-0485-4a08-bf2d-c324d4e7f185 ro radeon.audio=1 quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-18-generic N/A
 linux-backports-modules-3.11.0-18-generic N/A
 linux-firmware 1.116.2
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V11.7
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 880GM-E41 (MS-7623)
dmi.board.vendor: MSI
dmi.board.version: 2.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 2.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV11.7:bd10/22/2010:svnMSI:pnMS-7623:pvr2.0:rvnMSI:rn880GM-E41(MS-7623):rvr2.0:cvnMSI:ct3:cvr2.0:
dmi.product.name: MS-7623
dmi.product.version: 2.0
dmi.sys.vendor: MSI

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.14 kernel[0].

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'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-trusty/

[FlacBean02 (flacbean02)]

Added tag:kernel-bug-exists-upstream

Still blank/black screen.

[FlacBean02 (flacbean02)]

I used flashrom to update bios...

master@master-MS-7623:~$ sudo flashrom --programmer internal -w '/home/master/Downloads/7623vBB/A7623AMS.BB0'
flashrom v0.9.6.1-r1563 on Linux 3.11.0-18-generic (x86_64)
flashrom is free software, get the source code at http://www.flashrom.org

Calibrating delay loop... OK.
Found chipset "AMD SB7x0/SB8x0/SB9x0". Enabling flash write... OK.
Found Macronix flash chip "MX25L8005" (1024 kB, SPI) at physical address 0xfff00000.
Flash image seems to be a legacy BIOS. Disabling coreboot-related checks.
Reading old flash chip contents... done.
Erasing and writing flash chip... Erase/write done.
Verifying flash... VERIFIED.

Output of your command requested...
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
[sudo] password for master:
V11.11
04/27/2011

What happened..
Upon flashing, I restarted computer and held shift to attempt to see if Kernel 3.11.0-18.32 would still work as that's last known kernel unaffected by this but Instead of the grub boot-loader I was displayed several lines (wish I took a picture) saying bad CMOS checksum. I hit F1 to run setup, change nothing and exited and held shift again and grub loaded. 3.11.0-18.32 kernel works as expected. This message appeared across several reboots but has now disappeared.

Also another error that occurred once and has since gone mentioned "The previous overclocking has failed." (see 1.jpg)

Anyways boot into the two previous kernels which create this problem of black/blank screen and still same issue.

[penalvch (penalvch)]

FlacBean02, the next step is to fully commit bisect from 3.11.0-18.32 to 3.11.0-19.33 in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

[FlacBean02 (flacbean02)]

Here's 'git bisect log'...
---------------------------------------------
master@master-MS-7623:~/Desktop/Clone/ubuntu-saucy$ git bisect log# bad: [ee5918d3e6e54ce18ee5d983062dd44555f8c9f7] UBUNTU: Ubuntu-3.11.0-19.33
# good: [2f97cdb509b076833bec97b07a7a629448d71388] UBUNTU: Ubuntu-3.11.0-18.32
git bisect start 'Ubuntu-3.11.0-19.33' 'Ubuntu-3.11.0-18.32'
# bad: [0636759f761301ffa74f5232242b107d0a9318fa] usb-storage: restrict bcdDevice range for Super Top in Cypress ATACB
git bisect bad 0636759f761301ffa74f5232242b107d0a9318fa
# bad: [248a0cc70d36331137096e8ebd3d047ce30feeb6] arm64: vdso: update wtm fields for CLOCK_MONOTONIC_COARSE
git bisect bad 248a0cc70d36331137096e8ebd3d047ce30feeb6
# bad: [3a4b6148835925f6bc6ff8647fea3a0a7d7c2628] [media] af9035: add ID [2040:f900] Hauppauge WinTV-MiniStick 2
git bisect bad 3a4b6148835925f6bc6ff8647fea3a0a7d7c2628
# bad: [624fa8ce67e46da3c6e2544d36b5c21e30db4994] crypto: s390 - fix des and des3_ede ctr concurrency issue
git bisect bad 624fa8ce67e46da3c6e2544d36b5c21e30db4994
# bad: [dd350c2dc8a4d43ded7fc7489229599f8542b262] ftrace: Have function graph only trace based on global_ops filters
git bisect bad dd350c2dc8a4d43ded7fc7489229599f8542b262
# bad: [cb292e6eac7d92c6852044e63e3a4eca21570b8a] ftrace: Synchronize setting function_trace_op with ftrace_trace_function
git bisect bad cb292e6eac7d92c6852044e63e3a4eca21570b8a
# bad: [adf9f52ea6327238cc00801d0c77933ac72dc8da] UBUNTU: Start new release
git bisect bad adf9f52ea6327238cc00801d0c77933ac72dc8da
# first bad commit: [adf9f52ea6327238cc00801d0c77933ac72dc8da] UBUNTU: Start new release

commit would not build
cb292e6eac7d92c6852044e63e3a4eca21570b8a
---------------------------------------------
 LD [M] drivers/gpu/drm/nouveau/nouveau.o
  LD drivers/gpu/drm/built-in.o
  LD drivers/gpu/built-in.o
make[2]: *** [drivers] Error 2
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/home/master/Desktop/Clone/ubuntu-saucy'
make: *** [/home/master/Desktop/Clone/ubuntu-saucy/debian/stamps/stamp-build-generic] Error 2

Steps which got me here...
--------------------------------------
cd '/home/master/Desktop/Clone'
git clone git://kernel.ubuntu.com/bradf/ubuntu-saucy/.git
cd '/home/master/Desktop/Clone/ubuntu-saucy'
git checkout -b mybisect origin/master
git bisect start Ubuntu-3.11.0-19.33 Ubuntu-3.11.0-18.32
cd '/home/master/Desktop/Clone/ubuntu-saucy'
fakeroot debian/rules clean
fakeroot debian/rules binary-headers binary-generic
cd ..
sudo dpkg -i linux*3.11.0-19.33*.deb
sudo reboot

#repeat
cd '/home/master/Desktop/Clone/ubuntu-saucy'
git bisect bad
fakeroot debian/rules clean
fakeroot debian/rules binary-headers binary-generic
cd ..
sudo dpkg -i linux*3.11.0-19.33*.deb
sudo reboot
#end repeat

Could not find a good commit. All return blank/black screen.

[penalvch (penalvch)]

FlacBean02, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc1-trusty/ ?

[FlacBean02 (flacbean02)]

Something happened where my computer would no longer boot do to root UUID not existing. Ended up installing 14.04 and everything works well now. This can be closed.

[penalvch (penalvch)]

FlacBean02, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1304625/comments/10 regarding this being fixed with a reinstall. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.