Bug 782279 - display attributes wrong; kernel 3.1.9-1.fc16.x86_64.debug
Summary: display attributes wrong; kernel 3.1.9-1.fc16.x86_64.debug
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nouveau
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-17 04:04 UTC by George R. Goffe
Modified: 2013-02-13 12:46 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 12:46:43 UTC
Type: ---


Attachments (Terms of Use)
tar.gz file of 2 directories containing logs showing information requested (34.45 KB, application/x-gzip)
2012-02-11 03:48 UTC, George R. Goffe
no flags Details
tar.gz file containing dmesg.afu and dmesg.aok (43.96 KB, application/x-gzip)
2012-02-14 11:53 UTC, George R. Goffe
no flags Details

Description George R. Goffe 2012-01-17 04:04:41 UTC
Description of problem:

Switching to this kernel from 3.1.8-2.fc16.x86_64.debug, display capabilities are changed. Current kernel, 3.1.8-2.fc16.x86_64.debug, kde display is 1920x1200, with the newer kernel, display ends at 1024x768.

Version-Release number of selected component (if applicable):

kernel: 3.1.9-1.fc16.x86_64.debug
   kde: kdebase-4.7.4-2.fc16.x86_64


How reproducible:

readily

Steps to Reproduce:
1. reboot system
2. select 3.1.9-1.fc16.x86_64.debug
3. start kde
  
Actual results:

see description

Expected results:

see description

Additional info:

Comment 1 Bill Nottingham 2012-01-17 16:28:37 UTC
What hardware?

Comment 2 George R. Goffe 2012-01-17 21:52:53 UTC
Bill,

Do you want the lspci output?

This is from the "sales" document:

GPU Type        NVIDIA GeForce GT 550
Video Memory    Up to 2048MB Total Available Graphics Memory
Display Interface       1 x VGA
1 x HDMI

Comment 3 Adam Jackson 2012-02-09 17:58:00 UTC
Please attach /var/log/Xorg.0.log from the affected configuration.

Comment 4 George R. Goffe 2012-02-11 03:48:20 UTC
Created attachment 561034 [details]
tar.gz file of 2 directories containing logs showing information requested

Adam,

Here's my current situation.

The problem IS definitely repeatable. Additionally, switching kernels causes wierdness:

1) this kernel booted: 3.2.3-2.fc16.x86_64.debug.afu; display is wrong, network is up and works, tty1 does NOT print the password in clear text

2) switch to 3.2.2-1.fc16.x86_64.debug kernel: display is right, network won't come up, tty1 shows login password.

ifconfig eth0 shows nothing
service network start populates the eth0 values but no network connectivity
route add default gw 10.28.0.1 1 fails
route add default gw 10.28.0.1 succeeds

Is this wierd or what?

George...

Contents of the tar.gz file:

drwxr-xr-x root/root         0 2012-02-10 19:24 3.2.2-1.fc16.x86_64.debug/
-rw-r--r-- root/root     88035 2012-02-10 19:21 3.2.2-1.fc16.x86_64.debug/Xorg.0.log
-rw-r--r-- root/root      1898 2012-02-10 19:24 3.2.2-1.fc16.x86_64.debug/lspci.log
-rw-r--r-- root/root     29406 2012-02-10 19:22 3.2.2-1.fc16.x86_64.debug/startx.log
drwxr-xr-x root/root         0 2012-02-10 19:26 3.2.3-2.fc16.x86_64.debug.afu/
-rw-r--r-- root/root     82411 2012-02-10 19:18 3.2.3-2.fc16.x86_64.debug.afu/Xorg.0.log
-rw-r--r-- root/root      1898 2012-02-10 19:26 3.2.3-2.fc16.x86_64.debug.afu/lspci.log
-rw-r--r-- root/root     29723 2012-02-10 19:19 3.2.3-2.fc16.x86_64.debug.afu/startx.log

Comment 5 Ben Skeggs 2012-02-12 23:04:44 UTC
Can you attach dmesg output from both the working and non-working configurations please?

Both of your X logs show VESA being used on an Intel GPU, nothing about an NVIDIA GPU at all.

Comment 6 George R. Goffe 2012-02-14 11:53:20 UTC
Created attachment 561889 [details]
tar.gz file containing dmesg.afu and dmesg.aok

Ben,

I have tried to move up to this kernel, "3.2.5-3.fc16.x86_64.debug" but it's got some problems (escape sequences on tty1 seem to be broken, password shows in clear text) including this one so I went back to "3.2.3-2.fc16.x86_64.debug" which works and doesn't have the other errors. I also tried this latest kernel with "nomodeset" removed. It did appear to try to use the "nouveau" but got a message about capabilities in the startx.log file (startx >startx.log 2>&1)

Here are the two files tar'd and gzip'd together.

Thanks for your help,

George...

Comment 7 Fedora End Of Life 2013-01-16 12:29:29 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 8 Fedora End Of Life 2013-02-13 12:46:45 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.