Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Author Message
finottiOffline
Post subject:   PostPosted: 11.03.2013, 20:57



Joined: 2010-09-12
Posts: 312

Status: Offline
I am sorry, but I did not quite understand... You can get the monitor to work without xorg config files, but with the wrong resolution? If so, you can try to set the correct resolution with xrandr, something like:

      Code:

xrandr --output VGA-1 --mode "1280x1024"


depending on the output of "xrandr" (without arguments).
 
 View user's profile Send private message  
Reply with quote Back to top
ganymedOffline
Post subject:   PostPosted: 12.03.2013, 09:31



Joined: 2010-09-12
Posts: 19

Status: Offline
Sorry for butting in here again, but the problem still isn't even on the way to being solved from my point of view.

The last thing I did was check the Xorg.log from my system and compare the log files after booting the latest 3.7 vs. the recent 3.8-2.slh.3-aptosid-amd64 kernel. Please note, I'm not plugging or unplugging anything here.

While the 3.7 kernel boots fine:

      Code:
[    30.072] (--) NOUVEAU(0): Chipset: "NVIDIA NV96"
[    30.072] (II) NOUVEAU(0): Creating default Display subsection in Screen section
   "Default Screen Section" for depth/fbbpp 24/32
[    30.072] (==) NOUVEAU(0): Depth 24, (--) framebuffer bpp 32
[    30.072] (==) NOUVEAU(0): RGB weight 888
[    30.072] (==) NOUVEAU(0): Default visual is TrueColor
[    30.072] (==) NOUVEAU(0): Using HW cursor
[    30.072] (==) NOUVEAU(0): GLX sync to VBlank disabled.
[    30.072] (==) NOUVEAU(0): Page flipping enabled
[    30.072] (==) NOUVEAU(0): Swap limit set to 2 [Max allowed 2]
[    30.130] (II) NOUVEAU(0): Output DVI-I-1 has no monitor section
[    30.224] (II) NOUVEAU(0): Output DVI-I-2 has no monitor section
[    30.280] (II) NOUVEAU(0): EDID for output DVI-I-1
[    30.280] (II) NOUVEAU(0): Printing probed modes for output DVI-I-1
[    30.280] (II) NOUVEAU(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[    30.280] (II) NOUVEAU(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[    30.280] (II) NOUVEAU(0): Modeline "800x600"x56.2   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz e)
[    30.280] (II) NOUVEAU(0): Modeline "848x480"x60.0   33.75  848 864 976 1088  480 486 494 517 +hsync +vsync (31.0 kHz e)
[    30.280] (II) NOUVEAU(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 489 492 525 -hsync -vsync (31.5 kHz e)
[    30.374] (II) NOUVEAU(0): EDID for output DVI-I-2
[    30.374] (II) NOUVEAU(0): Output DVI-I-1 connected
[    30.374] (II) NOUVEAU(0): Output DVI-I-2 disconnected
[    30.374] (II) NOUVEAU(0): Using exact sizes for initial modes
[    30.374] (II) NOUVEAU(0): Output DVI-I-1 using initial mode 1024x768
[    30.374] (II) NOUVEAU(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[    30.374] (--) NOUVEAU(0): Virtual size is 1024x768 (pitch 0)
[    30.374] (**) NOUVEAU(0):  Driver mode "1024x768": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
[    30.374] (II) NOUVEAU(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[    30.374] (**) NOUVEAU(0):  Driver mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.3 Hz
[    30.374] (II) NOUVEAU(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[    30.374] (**) NOUVEAU(0):  Driver mode "800x600": 36.0 MHz (scaled from 0.0 MHz), 35.2 kHz, 56.2 Hz
[    30.374] (II) NOUVEAU(0): Modeline "800x600"x56.2   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz e)
[    30.374] (**) NOUVEAU(0):  Driver mode "848x480": 33.8 MHz (scaled from 0.0 MHz), 31.0 kHz, 60.0 Hz
[    30.374] (II) NOUVEAU(0): Modeline "848x480"x60.0   33.75  848 864 976 1088  480 486 494 517 +hsync +vsync (31.0 kHz e)
[    30.374] (**) NOUVEAU(0):  Driver mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 59.9 Hz
[    30.374] (II) NOUVEAU(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 489 492 525 -hsync -vsync (31.5 kHz e)
[    30.374] (==) NOUVEAU(0): DPI set to (96, 96)


all the 3.8 kernels up to the recent one result in a black screen (indicating "no PC connected"):

      Code:
[    23.085] (--) NOUVEAU(0): Chipset: "NVIDIA NV96"
[    23.085] (II) NOUVEAU(0): Creating default Display subsection in Screen section
   "Default Screen Section" for depth/fbbpp 24/32
[    23.085] (==) NOUVEAU(0): Depth 24, (--) framebuffer bpp 32
[    23.085] (==) NOUVEAU(0): RGB weight 888
[    23.085] (==) NOUVEAU(0): Default visual is TrueColor
[    23.085] (==) NOUVEAU(0): Using HW cursor
[    23.085] (==) NOUVEAU(0): GLX sync to VBlank disabled.
[    23.085] (==) NOUVEAU(0): Page flipping enabled
[    23.085] (==) NOUVEAU(0): Swap limit set to 2 [Max allowed 2]
[    23.098] (II) NOUVEAU(0): Output DVI-I-1 has no monitor section
[    23.102] (II) NOUVEAU(0): Output DVI-I-2 has no monitor section
[    23.106] (II) NOUVEAU(0): EDID for output DVI-I-1
[    23.110] (II) NOUVEAU(0): EDID for output DVI-I-2
[    23.110] (II) NOUVEAU(0): Output DVI-I-1 disconnected
[    23.110] (II) NOUVEAU(0): Output DVI-I-2 disconnected
[    23.110] (WW) NOUVEAU(0): No outputs definitely connected, trying again...
[    23.110] (II) NOUVEAU(0): Output DVI-I-1 disconnected
[    23.110] (II) NOUVEAU(0): Output DVI-I-2 disconnected
[    23.110] (WW) NOUVEAU(0): Unable to find connected outputs - setting 1024x768 initial framebuffer
[    23.110] (II) NOUVEAU(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[    23.110] (--) NOUVEAU(0): Virtual size is 1024x768 (pitch 0)
[    23.110] (**) NOUVEAU(0):  Mode "1024x768": 63.5 MHz (scaled from 0.0 MHz), 47.8 kHz, 59.9 Hz
[    23.110] (II) NOUVEAU(0): Modeline "1024x768"x59.9   63.50  1024 1072 1176 1328  768 771 775 798 -hsync +vsync (47.8 kHz)
[    23.110] (==) NOUVEAU(0): DPI set to (96, 96)


Remember, I'm using a TFT based TV set as the monitor and I'm using the VGA inlet. It's obviously not reading the EDID data with the 3.8 kernels, right?

Any type of advice or help is very appreciated Crying or Very sad
 
 View user's profile Send private message  
Reply with quote Back to top
manulOffline
Post subject:   PostPosted: 12.03.2013, 13:35



Joined: 2010-09-13
Posts: 95

Status: Offline
      finotti wrote:
I am sorry, but I did not quite understand... You can get the monitor to work without xorg config files, but with the wrong resolution? If so, you can try to set the correct resolution with xrandr, something like:

      Code:

xrandr --output VGA-1 --mode "1280x1024"


depending on the output of "xrandr" (without arguments).


I know how to get the monitor work with the proper resolution (on kernels 3.7).
I just did what slh asked me to.

On kernels 3.8 the monitor stops working even before reaching to Xorg (kdm) at all.
Monitor gets disabled before sysvinit boot sequence; right after grub.

Obviously xorg-nouveau depends on some (drm/nouveau?) kernel driver/subsystem and this driver (for some reason) thinks that nothing is connected.
 
 View user's profile Send private message  
Reply with quote Back to top
manulOffline
Post subject:   PostPosted: 15.03.2013, 17:56



Joined: 2010-09-13
Posts: 95

Status: Offline
Issue still persists with kernel 3.8-2.slh.5-aptosid-amd64
Last boot msg which I see is "populating /dev/.. " or something of the sort; then monitor goes "not connected".
 
 View user's profile Send private message  
Reply with quote Back to top
manulOffline
Post subject:   PostPosted: 20.03.2013, 18:47



Joined: 2010-09-13
Posts: 95

Status: Offline
I tried debian kernel from experimental (linux-image-3.8-trunk-amd64), and the "No signal" VGA/nouveau monitor issue, is valid there too.
So it definitely comes "from upstream".

P.S. Seem related:
forums.fedoraforum.org/showthread.php?p=1637411
https://bugzilla.redhat.com/show_bug.cgi?id=917260
https://bugzilla.redhat.com/show_bug.cgi?id=910945

cound not find anything in kernel.org bugzilla.
 
 View user's profile Send private message  
Reply with quote Back to top
manulOffline
Post subject:   PostPosted: 14.04.2013, 20:24



Joined: 2010-09-13
Posts: 95

Status: Offline
Tried today 3.8.7-slh.2 kernel to see if the bug has gone.

Nope, still there.

So, I am still bound to the last kernel which works fine (3.7-6.slh.2-aptosid-amd64).

P.S. At about the same time when I get "No signal" at the monitor with recent kernels, the 3.7 kernel spits few messages "i2c-2: sendbytes: NAK bailout". Then however all continues normally.
Did not mention this before, and not sure if it has anything to do to help with the bug.
 
 View user's profile Send private message  
Reply with quote Back to top
manulOffline
Post subject:   PostPosted: 11.06.2013, 20:21



Joined: 2010-09-13
Posts: 95

Status: Offline
The problem still persists with the latest kernel.

The behaviour however, is now a bit different.

When the console messages start to appear and "mode switching" happens, now the monitor does not go in "disconnected" mode.

Instead, the top 7 lines "freeze" and I have console, albeit the console viewport is all shifted 7 lines down (the top 7 lines stay frozen, there are 7 invisible lines down the screen, when scrolling top 7 lines dont move. To be able to see what I type I need to type "clear" so my typing comes into view).

Now when X/kdm is supposed to start - the monitor still shows the remnants of the console, only few additional color dots appear on top.
The system however "thinks" it has switched to KDM/X (I can "blindly" use KDM shortcuts to get back to console, ctrl-alt-f1 works as well) - so it is still kind of monitor/kms issue.

And I still have to stay with 3.7-6.slh.2-aptosid-amd64 kernel.

Please - does anyone know - is this going to be fixed ever, or I have to buy a new monitor?

----------------------------------------------

On top of it (unrelated matter), after last d-u (latest nouveau just came in) the OpenGL effects in KWin are not working at all (I have area remnants and frozen blocks, it is impossible to work).
So I had to disable OpenGL compositing in System settings. (certain effects work limited on XRender compositing mode which works fine).
Note I run 3.7-6.slh.2-aptosid-amd64 x86_64 kernel with latest X/nouveau.
Any known cure about it?


Thanks.

P.S.
      Code:
root@siduxbox:/home/manul# infobash -v
Host/Kernel/OS  "siduxbox" running Linux 3.7-6.slh.2-aptosid-amd64 x86_64 [ sidux 2009-03 Μώμος - kde-lite - (200911110039) ]
CPU Info        2x AMD Athlon 64 X2 Dual Core 5200+ clocked at [ 1000.000 MHz ]
Videocard       NVIDIA C77 [GeForce 8200]     [  ]
Processes 160 | Uptime 24min | Memory 896.5/3833.9MB | HDD Size 1660GB (40%used) | Client Shell | Infobash v3.46
 
 View user's profile Send private message  
Reply with quote Back to top
bluewaterOffline
Post subject:   PostPosted: 15.06.2013, 12:18
Team Member


Joined: 2010-08-26
Posts: 58
Location: Hobart, Australia
Status: Offline
Hi manul,
My current kernel is 3.9-5.slh.1-aptosid-amd64 so it is quite a few iterations from your kernel being 3.7-6.slh.2-aptosid-amd64.

can you get the latest kernel which is 3.9-6.slh.1-aptosid-amd64?

Is it possible that you have a strange xorg.conf setup,,,,,, perhaps try a live CD plain system without extra bits

_________________
If all else fails, get the instructions back out of the rubbish bin and read them. http://manual.aptosid.com/
 
 View user's profile Send private message  
Reply with quote Back to top
manulOffline
Post subject:   PostPosted: 16.06.2013, 04:57



Joined: 2010-09-13
Posts: 95

Status: Offline
      bluewater wrote:
Hi manul,
My current kernel is 3.9-5.slh.1-aptosid-amd64 so it is quite a few iterations from your kernel being 3.7-6.slh.2-aptosid-amd64.

can you get the latest kernel which is 3.9-6.slh.1-aptosid-amd64?

Is it possible that you have a strange xorg.conf setup,,,,,, perhaps try a live CD plain system without extra bits


Bluewater,

Thank you for your message and giving me the incent to try d-u again including the kernel.

Now I upgraded to latest kernel again - and for the first time since 3.7.6, MY MONITOR WORKS as supposed both in runlevel 3 (console) and 5 (X)!!!

The working kernel is 3.9-6.slh.2-aptosid-amd64.

First, attn to slh:
I tried with the latest kernel previous time - I guess it was something like 3.9-5.slh.2 or 3.9-5.slh.4 I do not remember exactly.
But it could be eventually deduced from the date of my previous message (the current aptosid kernel for this date). Unfortunately I missed to report the exact kernel version when I posted the message.

In any case, the fix occured in some of the last 2-3 kernels which came upstream, between the date of my previous message and today.

Now bluewater on your suggestions:
1) Is it possible that you have a strange xorg.conf setup,,,,,,
If you read my previous posts you will see that I experienced issues even in pure console (manually adding 3 to the kernel line via grub to boot in runlevel 3).
So I am pretty sure it is not anyway related to my X setup (which is very simple, resolution only in a single file in /etc/xorg.conf.d/ b/c nouveau does not properly pick my monitor resolution).

2) perhaps try a live CD plain system without extra bits
This was already tried with previous post-3.7.6 kernels (see the thread). It was the same problem, plain live system did not help.

However again, I am glad to report that it NOW WORKS with 3.9-6.slh.2!

It will be great if this would help slh isolate the exact patch that fixed it, in order not to have this regression again.

----------------------------------

Above said, I tried and still have the OpenGL issue that OpenGL effects in KWin are not working at all (I have area remnants and frozen blocks, it is impossible to work).
So I have to disable OpenGL compositing in System settings. (certain effects work limited on XRender compositing mode which works fine).
Note I now run the latest 3.9-6.slh.2-aptosid-amd64 kernel with latest X/nouveau which again came in (nouveau 1.0.8-1).

I guess this is a regression with my nvidia 8200 card vs nouveau driver; but it is not so important as the other one (and hopefully will be resolved in the future).

      Code:
root@siduxbox:~# uname -a
Linux siduxbox 3.9-6.slh.2-aptosid-amd64 #1 SMP PREEMPT Sat Jun 15 14:36:05 UTC 2013 x86_64 GNU/Linux
root@siduxbox:~# apt-cache policy xserver-xorg-video-nouveau
xserver-xorg-video-nouveau:
  Installed: 1:1.0.8-1
  Candidate: 1:1.0.8-1
  Version table:
 *** 1:1.0.8-1 0
        500 http://mirrors.kernel.org/debian/ sid/main amd64 Packages
        100 /var/lib/dpkg/status
root@siduxbox:~# infobash -v
Host/Kernel/OS  "siduxbox" running Linux 3.9-6.slh.2-aptosid-amd64 x86_64 [ sidux 2009-03 Μώμος - kde-lite - (200911110039) ]
CPU Info        2x AMD Athlon 64 X2 Dual Core 5200+ clocked at [ 1000.000 MHz ]
Videocard       NVIDIA C77 [GeForce 8200]  tty resolution ( 168x47 )
Processes 157 | Uptime 20min | Memory 746.6/3834.0MB | HDD Size 1660GB (40%used) | Runlevel 5 | Client Shell | Infobash v3.46
root@siduxbox:~#
 
 View user's profile Send private message  
Reply with quote Back to top
manulOffline
Post subject:   PostPosted: 16.06.2013, 13:51



Joined: 2010-09-13
Posts: 95

Status: Offline
I marked the topic as "solved" as it is done by the latest kernel 3.9-6.slh.2-aptosid-amd64 (OpenGL nouveau issues in X/KDE for NVIDIA C77 [GeForce 8200] are something unrelated).
 
 View user's profile Send private message  
Reply with quote Back to top
TischkeOffline
Post subject:   PostPosted: 10.11.2013, 20:37



Joined: 2010-12-11
Posts: 2
Location: Pasadena
Status: Offline
I believe I see something which might be similar. Laptop is Lenovo T510, dist-upgraded today. Dell monitor U2410, works fine at 1920X12000, 60Hz, with kernel 3.8-0.slh.2-aptosid-686, but none of the newer kernels tried since then.

No issues with laptop display with any of the kernels, only attached display has this issue.

Display is connect through HDMI and Lenovo dock.

Would be glad to with testing (as long as I can understand directions.)

      Code:

cat /var/log/messages | grep 'ouveau\|Vidia\|drm'
Nov 10 11:57:15 aptosidbox kernel: [    7.017674] [drm] Initialized drm 1.1.0 20060810
Nov 10 11:57:15 aptosidbox kernel: [    7.512877] nouveau  [  DEVICE][0000:01:00.0] BOOT0  : 0x0a8600a2
Nov 10 11:57:15 aptosidbox kernel: [    7.512880] nouveau  [  DEVICE][0000:01:00.0] Chipset: GT218 (NVA8)
Nov 10 11:57:15 aptosidbox kernel: [    7.512881] nouveau  [  DEVICE][0000:01:00.0] Family : NV50
Nov 10 11:57:15 aptosidbox kernel: [    7.514094] nouveau  [   VBIOS][0000:01:00.0] checking PRAMIN for image...
Nov 10 11:57:15 aptosidbox kernel: [    7.633327] nouveau  [   VBIOS][0000:01:00.0] ... appears to be valid
Nov 10 11:57:15 aptosidbox kernel: [    7.633330] nouveau  [   VBIOS][0000:01:00.0] using image from PRAMIN
Nov 10 11:57:15 aptosidbox kernel: [    7.633444] nouveau  [   VBIOS][0000:01:00.0] BIT signature found
Nov 10 11:57:15 aptosidbox kernel: [    7.633446] nouveau  [   VBIOS][0000:01:00.0] version 70.18.45.00.09
Nov 10 11:57:15 aptosidbox kernel: [    7.633803] nouveau  [     PFB][0000:01:00.0] RAM type: DDR3
Nov 10 11:57:15 aptosidbox kernel: [    7.633805] nouveau  [     PFB][0000:01:00.0] RAM size: 512 MiB
Nov 10 11:57:15 aptosidbox kernel: [    7.633806] nouveau  [     PFB][0000:01:00.0]    ZCOMP: 960 tags
Nov 10 11:57:15 aptosidbox kernel: [    7.660233] nouveau  [  PTHERM][0000:01:00.0] FAN control: none / external
Nov 10 11:57:15 aptosidbox kernel: [    7.660239] nouveau  [  PTHERM][0000:01:00.0] fan management: disabled
Nov 10 11:57:15 aptosidbox kernel: [    7.660246] nouveau  [  PTHERM][0000:01:00.0] internal sensor: yes
Nov 10 11:57:15 aptosidbox kernel: [    7.660614] nouveau  [     DRM] VRAM: 512 MiB
Nov 10 11:57:15 aptosidbox kernel: [    7.660618] nouveau  [     DRM] GART: 1048576 MiB
Nov 10 11:57:15 aptosidbox kernel: [    7.660624] nouveau  [     DRM] TMDS table version 2.0
Nov 10 11:57:15 aptosidbox kernel: [    7.660629] nouveau  [     DRM] DCB version 4.0
Nov 10 11:57:15 aptosidbox kernel: [    7.660633] nouveau  [     DRM] DCB outp 00: 01800323 00010034
Nov 10 11:57:15 aptosidbox kernel: [    7.660638] nouveau  [     DRM] DCB outp 01: 02811300 00000000
Nov 10 11:57:15 aptosidbox kernel: [    7.660642] nouveau  [     DRM] DCB outp 02: 028223a6 0f220010
Nov 10 11:57:15 aptosidbox kernel: [    7.660646] nouveau  [     DRM] DCB outp 03: 02822362 00020010
Nov 10 11:57:15 aptosidbox kernel: [    7.660650] nouveau  [     DRM] DCB outp 04: 048333b6 0f220010
Nov 10 11:57:15 aptosidbox kernel: [    7.660654] nouveau  [     DRM] DCB outp 05: 04833372 00020010
Nov 10 11:57:15 aptosidbox kernel: [    7.660659] nouveau  [     DRM] DCB outp 06: 088443c6 0f220010
Nov 10 11:57:15 aptosidbox kernel: [    7.660663] nouveau  [     DRM] DCB outp 07: 08844382 00020010
Nov 10 11:57:15 aptosidbox kernel: [    7.660666] nouveau  [     DRM] DCB conn 00: 00000040
Nov 10 11:57:15 aptosidbox kernel: [    7.660671] nouveau  [     DRM] DCB conn 01: 00000100
Nov 10 11:57:15 aptosidbox kernel: [    7.660675] nouveau  [     DRM] DCB conn 02: 00101246
Nov 10 11:57:15 aptosidbox kernel: [    7.660682] nouveau  [     DRM] DCB conn 03: 00202346
Nov 10 11:57:15 aptosidbox kernel: [    7.660684] nouveau  [     DRM] DCB conn 04: 00410446
Nov 10 11:57:15 aptosidbox kernel: [    7.689964] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
Nov 10 11:57:15 aptosidbox kernel: [    7.689966] [drm] No driver support for vblank timestamp query.
Nov 10 11:57:15 aptosidbox kernel: [    7.689968] nouveau  [     DRM] ACPI backlight interface available, not registering our own
Nov 10 11:57:15 aptosidbox kernel: [    7.690056] nouveau  [     DRM] 3 available performance level(s)
Nov 10 11:57:15 aptosidbox kernel: [    7.690059] nouveau  [     DRM] 0: core 135MHz shader 270MHz memory 135MHz voltage 850mV
Nov 10 11:57:15 aptosidbox kernel: [    7.690061] nouveau  [     DRM] 1: core 405MHz shader 810MHz memory 405MHz voltage 850mV
Nov 10 11:57:15 aptosidbox kernel: [    7.690064] nouveau  [     DRM] 3: core 606MHz shader 1468MHz memory 790MHz voltage 1000mV
Nov 10 11:57:15 aptosidbox kernel: [    7.690066] nouveau  [     DRM] c: core 405MHz shader 810MHz memory 405MHz voltage 850mV
Nov 10 11:57:15 aptosidbox kernel: [    7.723695] nouveau  [     DRM] MM: using COPY for buffer copies
Nov 10 11:57:15 aptosidbox kernel: [    7.822719] nouveau  [     DRM] allocated 1920x1200 fb: 0x70000, bo f6d14800
Nov 10 11:57:15 aptosidbox kernel: [    7.822822] fbcon: nouveaufb (fb0) is primary device
Nov 10 11:57:15 aptosidbox kernel: [    8.943120] nouveau 0000:01:00.0: fb0: nouveaufb frame buffer device
Nov 10 11:57:15 aptosidbox kernel: [    8.943122] nouveau 0000:01:00.0: registered panic notifier
Nov 10 11:57:15 aptosidbox kernel: [    8.943127] [drm] Initialized nouveau 1.1.1 20120801 for 0000:01:00.0 on minor 0
Nov 10 11:57:15 aptosidbox kernel: [   10.049158] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input20
Nov 10 11:57:15 aptosidbox kernel: [   10.049244] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input19
Nov 10 11:57:15 aptosidbox kernel: [   10.049301] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input18
Nov 10 11:57:15 aptosidbox kernel: [   10.049358] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input17
Nov 10 12:05:23 aptosidbox kernel: [    8.804046] [drm] Initialized drm 1.1.0 20060810
Nov 10 12:05:23 aptosidbox kernel: [    9.120565] nouveau  [  DEVICE][0000:01:00.0] BOOT0  : 0x0a8600a2
Nov 10 12:05:23 aptosidbox kernel: [    9.120572] nouveau  [  DEVICE][0000:01:00.0] Chipset: GT218 (NVA8)
Nov 10 12:05:23 aptosidbox kernel: [    9.120576] nouveau  [  DEVICE][0000:01:00.0] Family : NV50
Nov 10 12:05:23 aptosidbox kernel: [    9.123129] nouveau  [   VBIOS][0000:01:00.0] checking PRAMIN for image...
Nov 10 12:05:23 aptosidbox kernel: [    9.245849] nouveau  [   VBIOS][0000:01:00.0] ... appears to be valid
Nov 10 12:05:23 aptosidbox kernel: [    9.245852] nouveau  [   VBIOS][0000:01:00.0] using image from PRAMIN
Nov 10 12:05:23 aptosidbox kernel: [    9.245968] nouveau  [   VBIOS][0000:01:00.0] BIT signature found
Nov 10 12:05:23 aptosidbox kernel: [    9.245970] nouveau  [   VBIOS][0000:01:00.0] version 70.18.45.00.09
Nov 10 12:05:23 aptosidbox kernel: [    9.246178] nouveau  [     PFB][0000:01:00.0] RAM type: DDR3
Nov 10 12:05:23 aptosidbox kernel: [    9.246181] nouveau  [     PFB][0000:01:00.0] RAM size: 512 MiB
Nov 10 12:05:23 aptosidbox kernel: [    9.246182] nouveau  [     PFB][0000:01:00.0]    ZCOMP: 960 tags
Nov 10 12:05:23 aptosidbox kernel: [    9.274669] nouveau  [     DRM] VRAM: 512 MiB
Nov 10 12:05:23 aptosidbox kernel: [    9.274673] nouveau  [     DRM] GART: 512 MiB
Nov 10 12:05:23 aptosidbox kernel: [    9.274676] nouveau  [     DRM] BIT BIOS found
Nov 10 12:05:23 aptosidbox kernel: [    9.274680] nouveau  [     DRM] Bios version 70.18.45.00
Nov 10 12:05:23 aptosidbox kernel: [    9.274683] nouveau  [     DRM] TMDS table version 2.0
Nov 10 12:05:23 aptosidbox kernel: [    9.274686] nouveau  [     DRM] DCB version 4.0
Nov 10 12:05:23 aptosidbox kernel: [    9.274688] nouveau  [     DRM] DCB outp 00: 01800323 00010034
Nov 10 12:05:23 aptosidbox kernel: [    9.274691] nouveau  [     DRM] DCB outp 01: 02811300 00000000
Nov 10 12:05:23 aptosidbox kernel: [    9.274693] nouveau  [     DRM] DCB outp 02: 028223a6 0f220010
Nov 10 12:05:23 aptosidbox kernel: [    9.274695] nouveau  [     DRM] DCB outp 03: 02822362 00020010
Nov 10 12:05:23 aptosidbox kernel: [    9.274697] nouveau  [     DRM] DCB outp 04: 048333b6 0f220010
Nov 10 12:05:23 aptosidbox kernel: [    9.274699] nouveau  [     DRM] DCB outp 05: 04833372 00020010
Nov 10 12:05:23 aptosidbox kernel: [    9.274701] nouveau  [     DRM] DCB outp 06: 088443c6 0f220010
Nov 10 12:05:23 aptosidbox kernel: [    9.274703] nouveau  [     DRM] DCB outp 07: 08844382 00020010
Nov 10 12:05:23 aptosidbox kernel: [    9.274705] nouveau  [     DRM] DCB conn 00: 00000040
Nov 10 12:05:23 aptosidbox kernel: [    9.274707] nouveau  [     DRM] DCB conn 01: 00000100
Nov 10 12:05:23 aptosidbox kernel: [    9.274709] nouveau  [     DRM] DCB conn 02: 00101246
Nov 10 12:05:23 aptosidbox kernel: [    9.274711] nouveau  [     DRM] DCB conn 03: 00202346
Nov 10 12:05:23 aptosidbox kernel: [    9.274713] nouveau  [     DRM] DCB conn 04: 00410446
Nov 10 12:05:23 aptosidbox kernel: [    9.304334] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
Nov 10 12:05:23 aptosidbox kernel: [    9.304336] [drm] No driver support for vblank timestamp query.
Nov 10 12:05:23 aptosidbox kernel: [    9.304339] nouveau  [     DRM] ACPI backlight interface available, not registering our own
Nov 10 12:05:23 aptosidbox kernel: [   10.366251] nouveau  [     DRM] 3 available performance level(s)
Nov 10 12:05:23 aptosidbox kernel: [   10.366255] nouveau  [     DRM] 0: core 135MHz shader 270MHz memory 135MHz voltage 850mV
Nov 10 12:05:23 aptosidbox kernel: [   10.366258] nouveau  [     DRM] 1: core 405MHz shader 810MHz memory 405MHz voltage 850mV
Nov 10 12:05:23 aptosidbox kernel: [   10.366261] nouveau  [     DRM] 3: core 606MHz shader 1468MHz memory 790MHz voltage 1000mV
Nov 10 12:05:23 aptosidbox kernel: [   10.366263] nouveau  [     DRM] c: core 405MHz shader 810MHz memory 405MHz voltage 850mV
Nov 10 12:05:23 aptosidbox kernel: [   10.397777] nouveau  [     DRM] MM: using COPY for buffer copies
Nov 10 12:05:23 aptosidbox kernel: [   10.508290] nouveau  [     DRM] allocated 1920x1200 fb: 0x70000, bo f6d70a00
Nov 10 12:05:23 aptosidbox kernel: [   10.508339] fbcon: nouveaufb (fb0) is primary device
Nov 10 12:05:23 aptosidbox kernel: [   10.567490] nouveau 0000:01:00.0: fb0: nouveaufb frame buffer device
Nov 10 12:05:23 aptosidbox kernel: [   10.567492] nouveau 0000:01:00.0: registered panic notifier
Nov 10 12:05:23 aptosidbox kernel: [   10.567495] [drm] Initialized nouveau 1.1.0 20120801 for 0000:01:00.0 on minor 0
Nov 10 12:05:23 aptosidbox kernel: [   12.081542] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input13
Nov 10 12:05:23 aptosidbox kernel: [   12.081663] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input14
Nov 10 12:05:23 aptosidbox kernel: [   12.081746] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input15
Nov 10 12:05:23 aptosidbox kernel: [   12.081848] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input16
 
 View user's profile Send private message  
Reply with quote Back to top
slhOffline
Post subject:   PostPosted: 10.11.2013, 21:32



Joined: 2010-08-25
Posts: 731

Status: Offline
Please do test the current 3.12 kernel as provided by the repos, before investigating any further. Chances are that it is fixed, as nouveau is quite actively maintained, especially for the newer chipsets.
 
 View user's profile Send private message  
Reply with quote Back to top
TischkeOffline
Post subject:   PostPosted: 15.11.2013, 00:24



Joined: 2010-12-11
Posts: 2
Location: Pasadena
Status: Offline
Thanks slh,

Yes, this problem most likely comes from activities on nouveau. Latest kernel with this issue is current: Linux 3.12-0.slh.1-aptosid-686.

The attached LCD has fuzzy and flickering vertical bands alternating with dark bands. Laptop display is perfectly good. Will keep on trying.
 
 View user's profile Send private message  
Reply with quote Back to top
Display posts from previous:     
Jump to:  
All times are GMT - 12 Hours
Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Powered by Zafenio