10de:0322 12.10: Black screen with GeForce FX 5200 card

[Graham]

Having installed Ubuntu 12.10, a black screen now appears after logon (only the cursor is visible). Everything (graphically) up until logon is fine.

On my previous build (12.04), I was using Nvidia's drivers. As well, this did not happen with the nouveau drivers either.

WORKAROUND: This seems to be a problem with my Nvidia FX5200 graphics card as when I removed this and used the integrated graphics (Intel 82865G) instead, everything was fine.

WORKAROUND: Using the following kernel parameters gets me to the desktop but the OS is very unresponsive:
nomodeset

---
ApportVersion: 2.6.1-0ubuntu6
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: graham 1720 F.... pulseaudio
CRDA:
 country GB:
  (2402 - 2482 @ 40), (N/A, 20)
  (5170 - 5250 @ 40), (N/A, 20)
  (5250 - 5330 @ 40), (N/A, 20), DFS
  (5490 - 5710 @ 40), (N/A, 27), DFS
DistroRelease: Ubuntu 12.10
HibernationDevice: RESUME=UUID=bd714dd8-b111-42c1-88b5-0b32b12b0bff
InstallationDate: Installed on 2012-10-19 (6 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
MachineType: Dell Computer Corporation OptiPlex GX270
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=f4138a35-ef8f-4c93-a963-09e6b2ae85e3 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-17-generic N/A
 linux-backports-modules-3.5.0-17-generic N/A
 linux-firmware 1.95
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: quantal running-unity
Uname: Linux 3.5.0-17-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 06/26/2006
dmi.bios.vendor: Dell Computer Corporation
dmi.bios.version: A07
dmi.board.name: 0FG015
dmi.board.vendor: Dell Computer Corp.
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Computer Corporation
dmi.modalias: dmi:bvnDellComputerCorporation:bvrA07:bd06/26/2006:svnDellComputerCorporation:pnOptiPlexGX270:pvr:rvnDellComputerCorp.:rn0FG015:rvr:cvnDellComputerCorporation:ct6:cvr:
dmi.product.name: OptiPlex GX270
dmi.sys.vendor: Dell Computer Corporation

[Graham (ga01)]

I should note that my system is a Dell OptiPlex GX270 Tower using an Nvidia FX5200 (128MB) graphics card.

[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 1068601

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.

[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.7 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. Please only remove that one tag and leave the other tags. 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'.
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.7-rc1-quantal/

[Graham (ga01)]

Hi Joseph

Thanks for your reply. Having re-installed Ubuntu 12.10 (previously Kubuntu 12.10 with same problem) I was surprized that everything worked (visible desktop) although the responsiveness of the desktop was VERY slow (I guess propriatery drivers will help here when available). So I guess this bug report can be closed now. If there is anything I can do to improve the responsiveness, please let me know (it really is quite unusable, i.e laggy).

:)

[Graham (ga01)]

Hi Joseph

Seems I spoke too soon as the black screen has now re-appeared with this install. After a couple of reboots, the screen is still black. I have applied the latest upstream kernel as suggested and the desktop is now visible again although very slow as mentioned before. As before, not sure whether the black screen will re-occur in the future so have tagged as "kernel-fixed-upstream". Please adjust if incorrect or advise if I should now report the OS's slowness as another bug.

:)

[Graham (ga01)]

Having tested with the 3.7 kernel, I've noticed that the problem seems to come and go. There is no knowing when the desktop may re-appear, it seems very random.

[penalvch (penalvch)]

Graham, if possible in Quantal, if not in a Precise live environment via http://releases.ubuntu.com/precise/ , could you please execute in a terminal:
apport-collect 1068601

[Graham (ga01)]

Hi Christopher

Please see output from terminal below:-

"graham@computer:~$ apport-collect 1068601
ERROR: The launchpadlib Python module is not installed. This functionality is not available."

:)

[penalvch (penalvch)]

Graham, when in the live CD environment, one must install the launchpad Python module via:
sudo apt-get -y install python-launchpadlib

After you install this, please try:
apport-collect 1068601

again and it should work! :)

[Graham (ga01)]

apport information

[Graham (ga01)]

apport information

[Graham (ga01)]

apport information

[Graham (ga01)]

apport information

[Graham (ga01)]

apport information

[Graham (ga01)]

apport information

[Graham (ga01)]

apport information

[Graham (ga01)]

apport information

[Graham (ga01)]

apport information

[Graham (ga01)]

apport information

[Graham (ga01)]

apport information

[Graham (ga01)]

apport information

[Graham (ga01)]

apport information

[Graham (ga01)]

apport information

[Graham (ga01)]

apport information

[penalvch (penalvch)]

Graham, thank you for apport-collect'ing.

In Precise, did you have this problem using the nouveau driver?

As well, can you install the nvidia drivers in Quantal as a WORKAROUND?

[Graham (ga01)]

Prior to the Nvidia driver being available, logon was sluggish (selecting a user and entering a password) but once logged on, the OS responded fine in 12.04. Once the Nvidia driver was available and installed, this problem was resolved. I'm hoping this might be the case for 12.10.

I'm not sure whether the Nvidia drivers are available for 12.10 yet as they have not shown up in software updater. As mentioned, it's hit and miss whether the desktop appears or not but it's the actual performance of the OS which is also a problem.

I've still got a backup of 12.04.01 which I could carry on using or boot into my XP partition for general use.

:)

[penalvch (penalvch)]

Graham, regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1068601/comments/27 :
>"Prior to the Nvidia driver being available, logon was sluggish (selecting a user and entering a password) but once logged on, the OS responded fine in 12.04."

Based on how the problem of after login the screen is black does not happen in Precise, we would have a regression in nouveau going from Precise to Quantal.

>"Once the Nvidia driver was available and installed, this problem was resolved. I'm hoping this might be the case for 12.10. I'm not sure whether the Nvidia drivers are available for 12.10 yet as they have not shown up in software updater. As mentioned, it's hit and miss whether the desktop appears..."

As per http://www.nvidia.com/object/IO_32667.html the card you have uses the 173.14.xx driver. The Ubuntu repositories offer this at https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-173 . Does this provide a WORKAROUND for you in Quantal?

>"...but it's the actual performance of the OS which is also a problem."

Ok. This report is only focusing on how the computer intermittently shows a black screen after login.

Thank you for your understanding.

[Graham (ga01)]

How do I add/install this driver into Ubuntu 12.10?

:)

[penalvch (penalvch)]

Graham, one may install this driver via the terminal:
sudo apt-get -y install nvidia-173

Then reboot your computer and see how it works out for you.

[Graham (ga01)]

graham@computer:~$ sudo apt-get -y install nvidia-173
[sudo] password for graham:

Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies.
 nvidia-173 : Depends: xorg-video-abi-11 but it is not installable or
                       xorg-video-abi-12 but it is not installable
              Recommends: nvidia-settings
E: Unable to correct problems, you have held broken packages.

[penalvch (penalvch)]

Graham, unfortunately it appears nvidia-173 will not be a WORKAROUND for you at this time. The closest bug report found to your problem is:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-173/+bug/1064192
"[update request] nvidia-173.14.36 adds support for xserver ABI 13 [quantal]"

Because you are getting error messages for a different version of ABI:
nvidia-173 : Depends: xorg-video-abi-11 but it is not installable or
                       xorg-video-abi-12 but it is not installable

It would be best to file a separate bug report about this via the terminal and feel free to subscribe me to it:
ubuntu-bug nvidia-173

Refocusing back onto the black screen on boot problem, the next step is to perform a Ubuntu kernel bisect from 3.2.0-23.36 to 3.5.0-17.28, in order to identify the last good Ubuntu kernel version, followed immediately by the first bad one. As per https://launchpad.net/ubuntu/quantal/+source/linux we have:
    3.2.0-23.36
    3.2.0-24.37
    3.4.0-1.1
    3.4.0-1.2
    3.4.0-1.3
    3.4.0-2.4
    3.4.0-2.5
    3.4.0-2.6
    3.4.0-3.7
    3.4.0-3.8
    3.4.0-4.9
    3.4.0-4.10
    3.4.0-5.11
    3.5.0-1.1
    3.5.0-2.2
    3.5.0-3.3
    3.5.0-4.4
    3.5.0-5.5
    3.5.0-6.6
    3.5.0-7.7
    3.5.0-8.8
    3.5.0-9.9
    3.5.0-10.10
    3.5.0-11.11
    3.5.0-12.12
    3.5.0-13.13
    3.5.0-13.14
    3.5.0-14.15
    3.5.0-14.16
    3.5.0-14.17
    3.5.0-14.18
    3.5.0-14.19
    3.5.0-15.20
    3.5.0-15.21
    3.5.0-15.22
    3.5.0-15.23
    3.5.0-16.24
    3.5.0-16.25
    3.5.0-17.26
    3.5.0-17.27
    3.5.0-17.28

Hence, could you please test 3.5.0-7.7 via https://launchpad.net/ubuntu/+source/linux/3.5.0-7.7/+build/3692730 ?

Once this test is complete, could you please continue to bisect following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Thank you for your understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

[Graham (ga01)]

To test 3.5.0-7.7, would that involve installing linux-image and linux-image-extra? (as in post #3). Sorry, this is all new to me.

:)

[penalvch (penalvch)]

Graham, one would want to install the following from https://launchpad.net/ubuntu/+source/linux/3.5.0-7.7/+build/3692730 :
linux-headers-3.5.0-7-generic_3.5.0-7.7_i386.deb (913.1 KiB)
linux-headers-3.5.0-7_3.5.0-7.7_all.deb (11.5 MiB)
linux-image-3.5.0-7-generic_3.5.0-7.7_i386.deb (11.1 MiB)
linux-image-extra-3.5.0-7-generic_3.5.0-7.7_i386.deb (26.1 MiB)

[Graham (ga01)]

Tested 3.5.0-7.7 and same problem.

:)

[penalvch (penalvch)]

Graham, as per https://launchpad.net/ubuntu/quantal/+source/linux we have:
    3.2.0-23.36
    3.2.0-24.37
    3.4.0-1.1
    3.4.0-1.2
    3.4.0-1.3
    3.4.0-2.4
    3.4.0-2.5
    3.4.0-2.6
    3.4.0-3.7
    3.4.0-3.8
    3.4.0-4.9
    3.4.0-4.10
    3.4.0-5.11
    3.5.0-1.1
    3.5.0-2.2
    3.5.0-3.3
    3.5.0-4.4
    3.5.0-5.5
    3.5.0-6.6
    3.5.0-7.7

Hence, could you please test 3.4.0-3.8 via https://launchpad.net/ubuntu/+source/linux/3.4.0-3.8/+build/3525016 ?

Once this test is complete, could you please continue to bisect until the regression is found following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Thank you for your understanding.

[Graham (ga01)]

Hi Christopher

I understand the method of narrowing down working/non working kernels but I don't understand how you are linking to a particular kernel. For example:-

https://launchpad.net/ubuntu/+source/linux/3.4.0-3.8/+build/3525016

My next kernel to test might be...
https://launchpad.net/ubuntu/+source/linux/3.4.0-1.3/+build/???

What would I replace the ??? with?

:)

[Graham (ga01)]

Something odd I have noticed whilst testing these kernels is where the screen used to be all black, I have now seen all grey and orange backgrounds.

:)

[penalvch (penalvch)]

Graham, thank you for your comments. Regarding them https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1068601/comments/37 :
>"Hi Christopher I understand the method of narrowing down working/non working kernels but I don't understand how you are linking to a particular kernel. "

I updated the bisect article as it was not as clear as possible where one would find the specific 3.4.0-3.8 kernel to test with. In order to find it, one would go to https://launchpad.net/ubuntu/quantal/+source/linux , then under "Releases in Ubuntu" click "3.4.0-3.8", then under "Builds" click "i386", which brings one to https://launchpad.net/ubuntu/+source/linux/3.4.0-3.8/+build/3525016 .

>"For example:- https://launchpad.net/ubuntu/+source/linux/3.4.0-3.8/+build/3525016 My next kernel to test might be... https://launchpad.net/ubuntu/+source/linux/3.4.0-1.3/+build/??? What would I replace the ??? with?"

As per above method, this would be https://launchpad.net/ubuntu/+source/linux/3.4.0-1.3/+build/3458304 .

Regarding https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1068601/comments/38 :
>"Something odd I have noticed whilst testing these kernels is where the screen used to be all black, I have now seen all grey and orange backgrounds."

Could you please provide which kernel specifically you see all grey and orange backgrounds? As well, could you please take a screenshot and/or photograph of this and post it to this report?

Thank you for your understanding.

[Graham (ga01)]

I have tested the following kernels and all (at some point) showed a blank/coloured screen:-

3.5.0-7
3.4.0-3
3.4.0-1.3
3.4.0-1.1 (no builds, so couldn't test)
3.2.0-24.37
3.2.0-27.36

3.4.0-3 seemed to be the most reliable and the older two (3.2.0-x) the least reliable.

:)

[penalvch (penalvch)]

Due to how this issue is not reproducible in the Precise release with nouveau or nvidia drivers, but testing with the Precise release kernel yielded problematic results, I opened up a task for xserver-xorg-video-nouveau.

[Graham (ga01)]

Thanks for your help so far :). Do I need to add anything to xserver-xorg-video-nouveau or will troubleshooting continue from this thread?

:)

[penalvch (penalvch)]

Graham, thank you for your comments. Regarding them https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1068601/comments/42 :
>"Thanks for your help so far :)."

No problem at all.

"Do I need to add anything to xserver-xorg-video-nouveau"

One thing that would help tease this out is in Precise, upgrade to higher versions of the xorg packages via https://launchpad.net/~ubuntu-x-swat/+archive/x-updates?field.series_filter=precise . Could you please test this?

Thank you for your understanding.

[Graham (ga01)]

I tried adding the sources for 12.04 (and 12.10) but I'm getting "404 not found" errors on both. As 12.04 is an LTS release, I think I may go back to this version plus support is covered untill 2017. I'd just like to thank you for all your help and advice.

:)

[Graham (ga01)]

Hi Christopher

I also have a tablet (for testing) that I dabble with using Ubuntu (usually betas then stable releases). This is also showing a similar problem but this time, the screen is not black but shows only the wallpaper after logon. I have tried the latest 3.7 rc2 kernel and the screen goes really weird (hard to explain but I'll try and get a screenshot). I have also tried a kernel similar to 12.04's (3.2.0-23) but this makes no difference either. Should I open a new post for this?

:)

[Graham (ga01)]

Btw, the tablet is an old HP TC1100.

:)

[penalvch (penalvch)]

Graham, thank you for your comments. Regarding them https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1068601/comments/44 :
>"I tried adding the sources for 12.04 (and 12.10) but I'm getting "404 not found" errors on both. As 12.04 is an LTS release,..."

Instead of changing sources in an installed Precise, what you would want to do instead is use a live environment, then follow the directions on installing the xorg PPA in a live environment mentioned in https://launchpad.net/~xorg-edgers/+archive/ppa?field.series_filter=precise .

Regarding https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1068601/comments/45 and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1068601/comments/46 :

>"I also have a tablet..." "...an old HP TC1100", should "I open a new post for this?"

If you have a bug in Ubuntu with the tablet, 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 and Ubuntu Bug Squad 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.

[Graham (ga01)]

Hi Christopher

Thanks for your reply. I have 12.04 LTS currently installed on my main computer at the moment. To test in a live environment, would I be booting the same version (12.04) or the version I was previously having problems with? (12.10)

[ahmedg2 (ahmedg2)]

I've the same problem exactly I've Dell Optiplex tower PC with Nevidia GeForce FX 5200 graphics card when I installed Ubuntu 12.10 successfully everything working fine till log in screen then when I wrote my password and enter nothing appears only the mouse courser with black screen I pressed control with I don't remember f1 or f2 entered black screen with command I wrote some commands as ( sudo apt-get purge nevidia-current ) ( sudo apt-get purge fglrx ) ( sudo apt-get update ) ( sudo apt-get upgrade ) but after updating or upgrading then restarted my PC but nothing happened too any suggestions for the solution.

[Graham (ga01)]

Hi ahmedg2

For the time being, I've gone back to 12.04. I have a similar problem on my tablet (TC1100) too. I may stick with 12.04 as it's an LTS release but will try the 6 monthly releases in the hope that one may work with my setup.

:)

[penalvch (penalvch)]

Graham, regarding your comments https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1068601/comments/48 :
>"Hi Christopher Thanks for your reply. I have 12.04 LTS currently installed on my main computer at the moment. To test in a live environment, would I be booting the same version (12.04) or the version I was previously having problems with? (12.10)"

The live environment requested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1068601/comments/43 is Precise.

[Graham (ga01)]

Hi Christopher

Could you advise the best way to install a newer version of xorg? I'm familiar with adding sources via the terminal but unsure how to install this update as I would normally apply all updates (via software updater or terminal) and this would probably involve installing a newer kernel which would then require a reboot (hence loosing what I've just applied).

[penalvch (penalvch)]

Graham, you may find instructions for updating X in a live environment via https://wiki.ubuntu.com/XorgOnTheEdge .

[Graham (ga01)]

Hi Christopher

Followed instructions above and this is the output from "X -version":-

"X.Org X Server 1.12.3
Release Date: 2012-07-09
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-31-xen i686 Ubuntu
Current Operating System: Linux ubuntu 3.2.0-29-generic-pae #46-Ubuntu SMP Fri Jul 27 17:25:43 UTC 2012 i686
Kernel command line: initrd=/casper/initrd.lz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz
Build Date: 09 July 2012 05:18:23PM
xorg-server 2:1.12.3+git20120709+server-1.12-branch.60e0d205-0ubuntu0ricotz~precise (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.28.2
 Before reporting problems, check http://wiki.x.org
 to make sure that you have the latest version."

Does this look correct? No problems with the video display.

[Rob Koll (0x2jjt9d-agq-0tlbog0j)]

I am experiencing the same problem. Using an p4p800 motherboard with AGP nvidia card, FX5200. I can use nouveau, but that is far to slow and doesn't give good resolution (24 inch philips diaply 1920 * 1200). On ubuntu 12.04 i used nvidia driver 173 with modified xorg.conf which resutled in good performance at 1920 * 1200. After upgrade to 12.10 the screen shows one color and only the mouse pointer. When moving slowly on the screen i can probe for edges of windows, the resize handle becomes visible. When using that to guess where the exit cross of apps is, i could close the music player. On 12.04 I had some start up applications (thunderbird, rhtyhmbox). They really start, and by guessing where the cross is i could close rhyhm player. Just don't see their windows. The problem is very good reproducable on my machine (some people report that it starts and stops with unknown triggers). The screen shows one color, could be any. At some moments it even changes to some other color. Seems not to be related to user actions. There seems not to be a scheme in the change or colors. I will re-install the nvidia and collect some logs, add them later. Now the system is set to nouveau. This is posted from another disk and 12.04.

[Rob Koll (0x2jjt9d-agq-0tlbog0j)]

Additional information to #56. Note that the start up applications have been disabled (somewhere i read something on problems when switching focus, and thought it was better to not have too many windows). Still nothing, meaning one color plus mouse pointer. The size of the mouse pointer indicates by the way that the screen is running in one of the higher resolutions. When shutting down, the background image si visible for a very short period, that also indicates that the nvidia driver is at least doing something.

[Rob Koll (0x2jjt9d-agq-0tlbog0j)]

Addition of xlog log file. Please let me know which other data may help, which experiments are needed.

[Rob Koll (0x2jjt9d-agq-0tlbog0j)]

Just to make it more complete, the xorg.conf file.

[Rob Koll (0x2jjt9d-agq-0tlbog0j)]

One more remark: when booting from newly downloaded and burned life CD 12.10: same behaviour.
Remark 2: there is a new bug Bug #1090761, which seems to me same as this one. Please check for duplicate.

[penalvch (penalvch)]

Marking New based on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1068601/comments/55 .

[Launchpad Janitor (janitor)]

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

[penalvch (penalvch)]

Graham, could you please confirm this issue exists with the latest development release of Ubuntu Saucy Salamander? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available (v3.10-rc3-saucy) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory 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. 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. For example:
kernel-fixed-upstream-v3.10-rc3

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

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

As well, please remove the tag:
needs-upstream-testing

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

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Rob Koll (0x2jjt9d-agq-0tlbog0j)]

Just want to give initial feedback, of course the experience of Graham is more important. After burning the daily build live DVD taken from #63 my computer starts quite normal. It uses the nouveau driver, goes into resolution 1680*1050. Works correct, quite slow. So no issues like black screen. No confirmation the bug still exists. Now installing to hard disk. Will check whether or not I can run with proprietary nvidia driver. And bring that into the resulution from 24 inch screen (1920*1200).

[Rob Koll (0x2jjt9d-agq-0tlbog0j)]

Some more feedback. The install to hard disk seems to go well. Running from hard disk, using nouveau driver, seems at first glance OK. I left the system, later took out of screen saver. Background and top bar and left side bar ok. But while attempting to open the system setting, the initial menu only shows a rectangle with a king of garbled noisy pattern, nothing readable. Opening a terminal by ctrl-alt-t opens a comparable rectangle. Nothing readable, some kind of garbled noisy pattern (there seems to be some regualarity, random colers/spots). So the nouveau driver still has some issues. After opening ctrl-alt-F1 terminal (that works OK) and installing nvidia-173 (suitable for my graphics card) and a reboot, the original black background issue is again present. So the bug is confirmed using the daily build 13.10 downloaded 28-may-2013. I guess it would make sense to perform the apport-collect thing. But as the terminal is not visible, I need to type blind. Please advise on course of action. Attempt to perform the apport-collect (might install a startup script, maybe some logging into file). Can install the script after starting into one of the resque options. Or does it make sense to kick out nvidia and continue on nouveau? Please advise.

[penalvch (penalvch)]

Rob Koll, 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.

[Graham (ga01)]

Hi Christopher

Sorry for the late reply but I have since changed my graphics card (which is now working with 13.04). If you would like to assign this bug report to Rob, please do.

[Rob Koll (0x2jjt9d-agq-0tlbog0j)]

Christopher, Graham,

In my opinion it does not make sense to assign this bug to me. I opened https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1185911 for the problem (which is still being processed). There is a 'small catch'. Up to now, I fail to test if kernel v3.10.0 still holds the problem. It appears that a change in the proc file system interface causes the nvidia driver not to build nor install. This is laid down in https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-173/+bug/1186786. I just wonder how that will solve...

All taken together, as this bug is no more actual for Graham, I guess this one gets closed.

[penalvch (penalvch)]

Graham, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1068601/comments/67 regarding you no longer using the hardware. 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.