Bug#572168: radeontool 1.6: Nothing happens for "light off"

2010-03-06 Thread Tormod Volden
On Fri, Mar 5, 2010 at 6:08 PM, Jonathan Nieder wrote: > > Here are some patches against upstream master that seem to fix this. > I am attaching them rather than sending them as separate messages > since the Debian BTS deals better with that. Cool, thanks for your work! > > Thoughts? > Jonathan

Bug#572168: radeontool 1.6: Nothing happens for "light off"

2010-03-05 Thread Jonathan Nieder
tags 572168 + upstream patch thanks Jonathan Nieder wrote: > On Fri, Mar 05, 2010 at 05:00:27PM +0100, Tormod Volden wrote: >> The old version just grepped the lspci output for "Memory" and "K" to >> find the control region. The new one looks for a region of size >> 64K, which fails for your clas

Bug#572168: radeontool 1.6: Nothing happens for "light off"

2010-03-05 Thread Jonathan Nieder
On Fri, Mar 05, 2010 at 05:00:27PM +0100, Tormod Volden wrote: > You can find the old versions in the upstream branch of > http://git.debian.org/?p=collab-maint/radeontool.git;a=summary but the > upstream history has some gaps. I tried once to merge all history I > could find into one repo (see >

Bug#572168: radeontool 1.6: Nothing happens for "light off"

2010-03-05 Thread Tormod Volden
> Yes.  I wanted to bisect, but I couldn’t find a git repo incorporating > the old version.  I hope to make one collecting the tarballs I could > find this weekend. You can find the old versions in the upstream branch of http://git.debian.org/?p=collab-maint/radeontool.git;a=summary but the upstre

Bug#572168: radeontool 1.6: Nothing happens for "light off"

2010-03-05 Thread Jonathan Nieder
Tormod Volden wrote: > Thanks for your bug report. I am not surprised there are issues with > R128 cards since they are not Radeon cards. But since it worked with > 1.5-5 we should be able to figure it out. As you saw, the scanning for > the card memory ranges has changed from using lspci to inter

Bug#572168: radeontool 1.6: Nothing happens for "light off"

2010-03-05 Thread Tormod Volden
Thanks for your bug report. I am not surprised there are issues with R128 cards since they are not Radeon cards. But since it worked with 1.5-5 we should be able to figure it out. As you saw, the scanning for the card memory ranges has changed from using lspci to internal parsing, and the detection

Bug#572168: radeontool 1.6: Nothing happens for "light off"

2010-03-03 Thread Jonathan Nieder
Hi again, Corresponding results for 1.5-5: Jonathan Nieder wrote: > $ radeontool --debug light off > Found card 1002:4c46 (3) > Radeon found. Base control address is b35a1000; base framebuffer address is > b35a1000. > reading RADEON_LVDS_GEN_CNTL (2d0) is 00ff > writing RADEON_LVDS_GEN_

Bug#572168: radeontool 1.6: Nothing happens for "light off"

2010-03-01 Thread Jonathan Nieder
Package: radeontool Version: 1.6.0-1 Severity: normal Nothing happens for "radeontool light off" with radeontool 1.6.0 for my Dell Inspiron 4000. Downgrading to 1.5-5 works. Running 1.6.0 under strace yields a normal startup, then [...] stat64("/sys/bus/pci/devices", {st_mode=S_IFDIR|0755, st_s