Bug#586995: KMS not working on ATI Technologies Inc M56P [Radeon Mobility X1600]

2012-04-23 Thread Jonathan Nieder
Teodor MICU wrote:
 2012/4/23 Jonathan Nieder jrnie...@gmail.com:

        dpkg -l firmware-linux
[...]
 It has always been installed.

Just to be clear, always means for the past year or so rather than
some period going back to June 2010, right?

Sorry for the probably annoying questions.  If at all possible, I
would like to get this fixed in squeeze for the sake of others using
the same graphics card.

Thanks,
Jonathan



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120423065049.GB25198@burratino



Bug#586995: KMS not working on ATI Technologies Inc M56P [Radeon Mobility X1600]

2012-04-23 Thread Teodor MICU
2012/4/23 Jonathan Nieder jrnie...@gmail.com:
 Great, thanks for testing.  How about the second question --- is the
 radeon firmware installed?  You can find out with

        dpkg -l firmware-linux

 Just to be clear, if the bug is only reproducible when the radeon
 firmware is not installed, it would still be an important bug.  That
 would just help us to know where to look.

It has always been installed. I don't think its worth further
investigations unless it affects someone else, I've moved on a long
time ago.

Thanks

--



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cag2wgfdnzyxr-j-wuvokmdqum5e2ltnefsaznabc5fyelep...@mail.gmail.com



Bug#586995: KMS not working on ATI Technologies Inc M56P [Radeon Mobility X1600]

2012-04-23 Thread Jonathan Nieder
Jonathan Nieder wrote:
 Teodor MICU wrote:

 It has always been installed.

 Just to be clear, always means
[...]

Ah, found the answer in an earlier comment (#22).  Sorry for the
noise.

 I installed it but it shouldn't matter since the two dependencies were
 already installed.

Next steps that would be useful, if you have the time:

 - a full kernel log (using the dmesg command or /var/log/dmesg)
   from booting an affected kernel in recovery mode with the word
   drm.debug=0xe appended to the kernel command line and then running
   modprobe radeon

 - a photograph or screenshot of the garbled screen

 - which pre-compiled kernels between 2.6.32 and 2.6.36-rc5 listed
   at http://snapshot.debian.org/package/linux-2.6/ reproduce the
   big.  In other words, a narrower range to search for the fix.

If you don't have time for it, that's fine, too.  Just let us know and
we can let you know when there is a specific patch to try or wait
until someone else is able to reproduce it, depending on your
preference.

Thanks again.
Jonathan



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120423070200.GA25248@burratino



Bug#586995: KMS not working on ATI Technologies Inc M56P [Radeon Mobility X1600]

2012-04-23 Thread Touko Korpela
On Sun, Apr 22, 2012 at 08:04:36PM -0500, Jonathan Nieder wrote:
 Teodor MICU wrote:
 
  I just tested this (linux image from stable-proposed-updates) and
  there is no change: the console is fuzzy during boot.
 
 Great, thanks for testing.  How about the second question --- is the
 radeon firmware installed?  You can find out with
 
   dpkg -l firmware-linux
 
 Just to be clear, if the bug is only reproducible when the radeon
 firmware is not installed, it would still be an important bug.  That
 would just help us to know where to look.

I think you should check if firmware-linux-nonfree package is installed
(because Radeon firmware is located there).



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120423101735.GA32036@tiikeri.vuoristo.local



Bug#586995: KMS not working on ATI Technologies Inc M56P [Radeon Mobility X1600]

2012-04-23 Thread Jonathan Nieder
Touko Korpela wrote:

 I think you should check if firmware-linux-nonfree package is installed
 (because Radeon firmware is located there).

He's checked and it was installed.  It was my confusion.  Sorry about
that.



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120423160746.GC4832@burratino



Bug#586995: KMS not working on ATI Technologies Inc M56P [Radeon Mobility X1600]

2012-04-22 Thread Teodor MICU
2012/4/18 Jonathan Nieder jrnie...@gmail.com:
 Thanks for a reminder.  If you install a current squeeze kernel (e.g.,
 2.6.32-43) on the wheezy system, does it still reproduce modesetting
 trouble?  Is the radeon firmware installed?

I just tested this (linux image from stable-proposed-updates) and
there is no change: the console is fuzzy during boot.

Cheers



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cag2wgfdw0dsjgzh-taw9m8xjneb56xjvcu4nmbp98ldzm6o...@mail.gmail.com



Bug#586995: KMS not working on ATI Technologies Inc M56P [Radeon Mobility X1600]

2012-04-22 Thread Jonathan Nieder
Teodor MICU wrote:

 I just tested this (linux image from stable-proposed-updates) and
 there is no change: the console is fuzzy during boot.

Great, thanks for testing.  How about the second question --- is the
radeon firmware installed?  You can find out with

dpkg -l firmware-linux

Just to be clear, if the bug is only reproducible when the radeon
firmware is not installed, it would still be an important bug.  That
would just help us to know where to look.



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120423010435.GA20843@burratino



Bug#586995: KMS not working on ATI Technologies Inc M56P [Radeon Mobility X1600]

2012-04-18 Thread Jonathan Nieder
Teodor MICU wrote:

 This bug should be closed and archived -- it works properly on wheezy.

Thanks for a reminder.  If you install a current squeeze kernel (e.g.,
2.6.32-43) on the wheezy system, does it still reproduce modesetting
trouble?  Is the radeon firmware installed?

Curious,
Jonathan



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120418165947.GD28058@burratino



Bug#586995: KMS not working on ATI Technologies Inc M56P [Radeon Mobility X1600]

2010-10-10 Thread Ben Hutchings
On Fri, 2010-10-08 at 13:00 +0300, Teodor MICU wrote:
 Package: linux-2.6
 Version: 2.6.32-24
 Severity: normal
 
 Attached is the file containing the reportbug detected settings.
 Previous discussion can be found in the BTS.
 The final goal is to find a fix for this issue in 'squeeze'.

I can't see any changes to radeon between 2.6.33 and 2.6.36 that are
obviously related to this.

Could you test some of the intermediate versions (2.6.34, 2.6.35) from
http://snapshot.debian.org/package/linux-2.6/ so that we have a
smaller number of changes to look through?

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


signature.asc
Description: This is a digitally signed message part


Processed (with 1 errors): Bug#586995: KMS not working on ATI Technologies Inc M56P [Radeon Mobility X1600]

2010-10-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 reassign 586995 linux-image-2.6.32-5-amd64 2.6.32-24
Bug #586995 [xserver-xorg-video-radeon] xserver-xorg-video-radeon: KMS not 
working on ATI Technologies Inc M56P [Radeon Mobility X1600]
Bug reassigned from package 'xserver-xorg-video-radeon' to 
'linux-image-2.6.32-5-amd64'.
Bug No longer marked as found in versions xserver-xorg-video-ati/1:6.13.0-2 and 
xserver-xorg-video-ati/1:6.13.1-2.
Bug #586995 [linux-image-2.6.32-5-amd64] xserver-xorg-video-radeon: KMS not 
working on ATI Technologies Inc M56P [Radeon Mobility X1600]
Bug Marked as found in versions linux-2.6/2.6.32-24.
 retitle 586995 KMS not working on ATI Technologies Inc M56P [Radeon
Bug #586995 [linux-image-2.6.32-5-amd64] xserver-xorg-video-radeon: KMS not 
working on ATI Technologies Inc M56P [Radeon Mobility X1600]
Changed Bug title to 'KMS not working on ATI Technologies Inc M56P [Radeon' 
from 'xserver-xorg-video-radeon: KMS not working on ATI Technologies Inc M56P 
[Radeon Mobility X1600]'
 Mobility X1600]
Unknown command or malformed arguments to command.

 stop
Stopping processing here.

Please contact me if you need assistance.
-- 
586995: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586995
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.12865313843646.transcr...@bugs.debian.org



Bug#586995: KMS not working on ATI Technologies Inc M56P [Radeon Mobility X1600]

2010-10-08 Thread Teodor MICU
Package: linux-2.6
Version: 2.6.32-24
Severity: normal

Attached is the file containing the reportbug detected settings.
Previous discussion can be found in the BTS.
The final goal is to find a fix for this issue in 'squeeze'.

Thanks
-- Package-specific info:
** Version:
Linux version 2.6.32-5-amd64 (Debian 2.6.32-24) (b...@decadent.org.uk) (gcc 
version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Thu Sep 30 03:34:00 UTC 2010

** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 
root=UUID=6f822aa6-3605-4e2e-bfca-7f27fc0ad9fa ro panic=20

** Not tainted

** Kernel log:
[5.901601] lis3lv02d driver loaded.
[5.929728] yenta_cardbus :02:06.0: ISA IRQ mask 0x0c78, PCI irq 18
[5.929793] yenta_cardbus :02:06.0: Socket status: 3006
[5.929854] pci_bus :02: Raising subordinate bus# of parent bus (#02) 
from #03 to #06
[5.929929] yenta_cardbus :02:06.0: pcmcia: parent PCI bridge I/O 
window: 0x8000 - 0x8fff
[5.929998] yenta_cardbus :02:06.0: pcmcia: parent PCI bridge Memory 
window: 0xf420 - 0xf45f
[5.930067] yenta_cardbus :02:06.0: pcmcia: parent PCI bridge Memory 
window: 0xc000 - 0xc3ff
[5.930495] tifm_7xx1 :02:06.2: PCI INT B - GSI 19 (level, low) - IRQ 
19
[6.024782] cfg80211: Using static regulatory domain info
[6.024845] cfg80211: Regulatory domain: US
[6.024903]  (start_freq - end_freq @ bandwidth), (max_antenna_gain, 
max_eirp)
[6.024970]  (2402000 KHz - 2472000 KHz @ 4 KHz), (600 mBi, 2700 mBm)
[6.025042]  (517 KHz - 519 KHz @ 4 KHz), (600 mBi, 2300 mBm)
[6.025103]  (519 KHz - 521 KHz @ 4 KHz), (600 mBi, 2300 mBm)
[6.025163]  (521 KHz - 523 KHz @ 4 KHz), (600 mBi, 2300 mBm)
[6.025224]  (523 KHz - 533 KHz @ 4 KHz), (600 mBi, 2300 mBm)
[6.025287]  (5735000 KHz - 5835000 KHz @ 4 KHz), (600 mBi, 3000 mBm)
[6.025355] cfg80211: Calling CRDA for country: US
[6.159635] Bluetooth: Generic Bluetooth USB driver ver 0.6
[6.159915] usbcore: registered new interface driver btusb
[6.171447] usbcore: registered new interface driver hiddev
[6.186203] input: Logitech USB Receiver as 
/devices/pci:00/:00:1d.2/usb4/4-2/4-2:1.0/input/input9
[6.186377] generic-usb 0003:046D:C51B.0001: input,hidraw0: USB HID v1.11 
Mouse [Logitech USB Receiver] on usb-:00:1d.2-2/input0
[6.200208] generic-usb 0003:046D:C51B.0002: hiddev0,hidraw1: USB HID v1.11 
Device [Logitech USB Receiver] on usb-:00:1d.2-2/input1
[6.200336] usbcore: registered new interface driver usbhid
[6.200398] usbhid: v2.6:USB HID core driver
[6.899873] [drm] radeon defaulting to userspace modesetting.
[6.900577] pci :01:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16
[6.900642] pci :01:00.0: setting latency timer to 64
[6.900795] [drm] Initialized radeon 1.32.0 20080528 for :01:00.0 on 
minor 0
[6.906886] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection 
driver for Linux, 1.2.26ks
[6.906960] iwl3945: Copyright(c) 2003-2009 Intel Corporation
[6.907101] iwl3945 :10:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17
[6.907177] iwl3945 :10:00.0: setting latency timer to 64
[6.976284] iwl3945 :10:00.0: Tunable channels: 13 802.11bg, 23 802.11a 
channels
[6.976354] iwl3945 :10:00.0: Detected Intel Wireless WiFi Link 3945ABG
[6.976526]   alloc irq_desc for 29 on node -1
[6.976529]   alloc kstat_irqs on node -1
[6.976562] iwl3945 :10:00.0: irq 29 for MSI/MSI-X
[7.120645] phy0: Selected rate control algorithm 'iwl-3945-rs'
[7.685303] HDA Intel :00:1b.0: power state changed by ACPI to D0
[7.685406] HDA Intel :00:1b.0: power state changed by ACPI to D0
[7.685474] HDA Intel :00:1b.0: PCI INT A - GSI 16 (level, low) - IRQ 
16
[7.685583] HDA Intel :00:1b.0: setting latency timer to 64
[7.800711] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1b.0/input/input10
[   10.208186] input: PS/2 Generic Mouse as 
/devices/platform/i8042/serio4/serio5/input/input11
[   53.526437] padlock: VIA PadLock not detected.
[   53.570733] padlock: VIA PadLock Hash Engine not detected.
[   54.629311] loop: module loaded
[   54.973474] Adding 6425444k swap on /dev/mapper/sda5_crypt.  Priority:-1 
extents:1 across:6425444k 
[   55.440272] EXT4-fs (dm-0): mounted filesystem with ordered data mode
[   55.463177] EXT4-fs (sda7): mounted filesystem with ordered data mode
[   57.787549] input: ACPI Virtual Keyboard Device as 
/devices/virtual/input/input12
[   58.801918]   alloc irq_desc for 30 on node -1
[   58.801921]   alloc kstat_irqs on node -1
[   58.801940] tg3 :08:00.0: irq 30 for MSI/MSI-X
[   58.989786] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   59.036548] iwl3945 :10:00.0: firmware: requesting iwlwifi-3945-2.ucode
[   59.109651] iwl3945 :10:00.0: loaded firmware version 15.32.2.9
[   59.176513] Registered led device: