Re: Hotplugging: VGA to alubook 5,8
On Fri, Dec 07 2007, at 08:27 +0100, Michel Dänzer wrote: > > On Fri, 2007-12-07 at 00:54 +0100, Wolfgang Pfeiffer wrote: > > [Anyone can tell me whether it is enough to just copy ati_drv.so and > > radeon_drv.so to /usr/lib/xorg/modules/drivers/ to get the relevant > > drivers to this computer installed?] > > It is, but doesn't xserver-xorg-video-ati from experimental work? It's > more or less up to date wrt upstream Git... The last package I had installed was, IINM, xserver-xorg-video-ati_6.7.196-1, and I didn't have problems with it, other than those already described on [EMAIL PROTECTED] It worked fine for cloning the alubook screen to a VGA - I just thought maybe this black-and-white-only-on-my-TV issue got fixed .. :) ... And yes, I often eat my favorite software as fresh as possible ... :) And if we're already at it: Thanks to the developers of this software. I clone an alubook screen to a VGA on a nearly daily basis: I just added a few commands to the KDE menu, to switch the LCD/VGA screens on/off: seems to work like a charm ... Thanks a lot Best Regards Wolfgang -- Wolfgang Pfeiffer: /ICQ: 286585973/ + + + /AIM: crashinglinux/ http://profiles.yahoo.com/wolfgangpfeiffer Key: 0xE3037113 http://keyserver.mine.nu/pks/lookup?search=0xE3037113&fingerprint=on -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Hotplugging: VGA to alubook 5,8
On Thu, 2007-11-29 at 22:36 +0100, Wolfgang Pfeiffer wrote: > > So although in *retrospective* view (seen with the commands above) it > seems there is everything from the randr.1-2 branch also in the master > tree, there seem to be times when randr-1.2 had contents that were > just not yet in master. RandR1.2 support was initially developed on the randr-1.2 branch. Once it was ready, the branch was merged into the master branch. As usual, there is a myriad of ways to figure this out with Git, but FWIW some of the simpler ones: git-log origin/master..origin/randr-1.2 comes up empty, meaning the randr-1.2 branch doesn't have any commits the master branch doesn't have. git-log origin/randr-1.2..origin/master shows all the commits the master branch has that the randr-1.2 branch doesn't have, i.e. all the changes made to the master branch since the randr-1.2 branch was merged. gitk --all gives a nice graphical view of the revision history. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Re: Hotplugging: VGA to alubook 5,8
On Thu, Nov 29 2007, at 08:30 +0100, Bin Zhang wrote:
> On Nov 29, 2007 1:04 AM, Wolfgang Pfeiffer <[EMAIL PROTECTED]> wrote:
> > ---
> > git-clone git://anongit.freedesktop.org/git/xorg/driver/xf86-video-ati
> > cd xf86-video-ati
> > ./autogen.sh
> > make
>
> I tested this, using ./autogen.sh --prefix=/usr
> But I had a problem : fvwm can't remember window size changes for
> applications.
> So back to debian experimental package + two paches from git.
I wasn't very lucky with the ati git tree, so far .. I hope I'll have
some time soon to give this tree another chance ... :) I'm still
running the unpatched experimental Debian package: 6.7.196-1
> > or better that one:
> > -
> > 3. git-clone git://anongit.freedesktop.org/git/xorg/driver/xf86-video-ati
> > 4. cd xf86-video-ati
> > 5. git checkout origin/randr-1.2 (Git-Version 1.5)
> > git checkout randr-1.2 (Git-Version 1.4)
>
> This means you use randr-1.2 branch (last change 3 months ago) .
> See http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-ati.git;a=summary
> http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-ati.git;a=shortlog;h=randr-1.2
Thanks for that ...
> >
> > What's the difference between the 2 methods above, i.e. what does this
> > 'checkout origin/randr-1.2' ('checkout randr-1.2') snippet make
> > different, compared to the first way of compiling ... ?
>
> man git-checkout
>
Definitely my mistake. I wasn't clear enough: Actually it seems that
everything that is in the randr-1.2 tree is also in the master tree -
there seems to be even more in master. You can see this in the ati
tree, e.g. with a
git-rev-list origin/master --until="Tue Aug 05" --pretty | less
resp. with
git-rev-list origin/randr-1.2 --until="Tue Aug 05" --pretty | less
So I thought why does Alex Deucher recommend the randr-1.2 tree for a
compile? I think I found the answer:
http://www.nabble.com/radeon-tv-out-tf4221095.html#a12106111
"I've just pushed tv-out support to the radeon randr-1.2 branch."
So although in *retrospective* view (seen with the commands above) it
seems there is everything from the randr.1-2 branch also in the master
tree, there seem to be times when randr-1.2 had contents that were
just not yet in master.
In other words: there are things between heaven and earth that even
such a nifty tool like git will not be able to explain to me, or least
not to me... :)
Whatever. Thanks for caring, Bin ... :)
Regards
Wolfgang
--
Wolfgang Pfeiffer: /ICQ: 286585973/ + + + /AIM: crashinglinux/
http://profiles.yahoo.com/wolfgangpfeiffer
Key: 0xE3037113
http://keyserver.mine.nu/pks/lookup?search=0xE3037113&fingerprint=on
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Hotplugging: VGA to alubook 5,8 [was: Re: getting wireless and dvi out [ ... ]]
On Nov 29, 2007 1:04 AM, Wolfgang Pfeiffer <[EMAIL PROTECTED]> wrote:
> Hi Bin, Hi All
>
> To compile the radeon driver, what's the correct way if
> I need radeon on a alubook 5,8:
>
> something like this:
> ---
> git-clone git://anongit.freedesktop.org/git/xorg/driver/xf86-video-ati
> cd xf86-video-ati
> ./autogen.sh
> make
I tested this, using ./autogen.sh --prefix=/usr
But I had a problem : fvwm can't remember window size changes for applications.
So back to debian experimental package + two paches from git.
> [from http://bugs.freedesktop.org/show_bug.cgi?id=12552]
> -
>
>
> or better that one:
> -
> 3. git-clone git://anongit.freedesktop.org/git/xorg/driver/xf86-video-ati
> 4. cd xf86-video-ati
> 5. git checkout origin/randr-1.2 (Git-Version 1.5)
> git checkout randr-1.2 (Git-Version 1.4)
This means you use randr-1.2 branch (last change 3 months ago) .
See http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-ati.git;a=summary
http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-ati.git;a=shortlog;h=randr-1.2
> 6. ./autogen.sh --prefix=/usr (or any home-directory, but then you have to
> copy the files manual to the correct directory)
> 7. make
> [from http://www.nabble.com/radeon-tv-out-tf4221095.html#a12103267]
>
>
> What's the difference between the 2 methods above, i.e. what does this
> 'checkout origin/randr-1.2' ('checkout randr-1.2') snippet make
> different, compared to the first way of compiling ... ?
man git-checkout
Best regards,
Bin
>
> Best Regards, and Thanks in anticipation
>
> Wolfgang
>
> --
> Wolfgang Pfeiffer: /ICQ: 286585973/ + + + /AIM: crashinglinux/
> http://profiles.yahoo.com/wolfgangpfeiffer
>
> Key: 0xE3037113
> http://keyserver.mine.nu/pks/lookup?search=0xE3037113&fingerprint=on
>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Hotplugging: VGA to alubook 5,8 [was: Re: getting wireless and dvi out [ ... ]]
Hi Bin, Hi All
To compile the radeon driver, what's the correct way if
I need radeon on a alubook 5,8:
something like this:
---
git-clone git://anongit.freedesktop.org/git/xorg/driver/xf86-video-ati
cd xf86-video-ati
./autogen.sh
make
[from http://bugs.freedesktop.org/show_bug.cgi?id=12552]
-
or better that one:
-
3. git-clone git://anongit.freedesktop.org/git/xorg/driver/xf86-video-ati
4. cd xf86-video-ati
5. git checkout origin/randr-1.2 (Git-Version 1.5)
git checkout randr-1.2 (Git-Version 1.4)
6. ./autogen.sh --prefix=/usr (or any home-directory, but then you have to
copy the files manual to the correct directory)
7. make
[from http://www.nabble.com/radeon-tv-out-tf4221095.html#a12103267]
What's the difference between the 2 methods above, i.e. what does this
'checkout origin/randr-1.2' ('checkout randr-1.2') snippet make
different, compared to the first way of compiling ... ?
Best Regards, and Thanks in anticipation
Wolfgang
--
Wolfgang Pfeiffer: /ICQ: 286585973/ + + + /AIM: crashinglinux/
http://profiles.yahoo.com/wolfgangpfeiffer
Key: 0xE3037113
http://keyserver.mine.nu/pks/lookup?search=0xE3037113&fingerprint=on
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Hotplugging: VGA to alubook 5,8 [was: Re: getting wireless and dvi out [ ... ]]
On Nov 27, 2007 1:38 PM, Bin Zhang <[EMAIL PROTECTED]> wrote: > On Nov 24, 2007 10:49 AM, Michel Dänzer <[EMAIL PROTECTED]> wrote: > > > > On Sat, 2007-11-24 at 02:47 +0100, Wolfgang Pfeiffer wrote: > > > $ xrandr --output DVI-0 --auto > > > xrandr: cannot find crtc for output DVI-0 > > > > This is probably related to S-video, try something like > > > > xrandr --output S-video --off --output DVI-0 --auto > > I see the same problem for VGA-0 using today's git tree xf86-video-ati. > But version 6.7.196 doesn't has this problem. > Sorry. Just restart X again, it works fine now. Bin > Best regards, > Bin >
Re: Hotplugging: VGA to alubook 5,8 [was: Re: getting wireless and dvi out [ ... ]]
On Nov 24, 2007 10:49 AM, Michel Dänzer <[EMAIL PROTECTED]> wrote: > > On Sat, 2007-11-24 at 02:47 +0100, Wolfgang Pfeiffer wrote: > > $ xrandr --output DVI-0 --auto > > xrandr: cannot find crtc for output DVI-0 > > This is probably related to S-video, try something like > > xrandr --output S-video --off --output DVI-0 --auto I see the same problem for VGA-0 using today's git tree xf86-video-ati. But version 6.7.196 doesn't has this problem. Best regards, Bin
Re: Hotplugging: VGA to alubook 5,8 [was: Re: getting wireless and dvi out [ ... ]]
On Nov 24, 2007 10:49 AM, Michel Dänzer <[EMAIL PROTECTED]> wrote: > > On Sat, 2007-11-24 at 02:47 +0100, Wolfgang Pfeiffer wrote: > > > > On Fri, Nov 23 2007, at 18:58 +0100, Bin Zhang wrote: > > > On Nov 23, 2007 2:54 PM, Wolfgang Pfeiffer <[EMAIL PROTECTED]> wrote: > > > > On Fri, Nov 23 2007, at 14:49 +0100, Wolfgang Pfeiffer wrote: > > > > > > > > > Sidenotes: > > > > > > > > > > Since installing the new driver some artifacts are visible around the > > > > > mouse-pointer in its default "arrow" image ... Please let me know if > > > > > > > > This last line should have been saying: > > > > "mouse-pointer on X in its default "arrow" image [ ... ]" > > > > > > > > > > > > > a photo from that might help ... > > > > > > > > > > And the mouse is completely gone on the console .. haven't had time, > > > > > yet, to google/explore that ... > > > > > > Try adding a line > > > Option "SWcursor" "on" > > > in Section "Device" of your xorg.conf. > > That's a rather heavy-handed workaround - in particular, the SW cursor > interacts badly with 3D acceleration and XVideo. > > > The problem seems being gone for the moment, without having changed > > xorg.conf here ... > > Only legacy two-colour cursors are affected, not modern 32 bit ARGB > cursors. Thanks. Bin > > > > S-video unknown connection 800x600+0+0 (normal left inverted right x axis y > > axis > > ) 0mm x 0mm > >800x60060.3* > > > > ## Note: There was no S-video connection that I knew about > > It can't be detected reliably, hence 'unknown connection'. > > > $ xrandr --output DVI-0 --auto > > xrandr: cannot find crtc for output DVI-0 > > This is probably related to S-video, try something like > > xrandr --output S-video --off --output DVI-0 --auto > > If you think this could be handled better, please bring it up on the > [EMAIL PROTECTED] list. > > > > And this: I saw this > > https://bugs.freedesktop.org/show_bug.cgi?id=11796 > > This was the main reason I compiled the fresh xf86-video-ati sources: > > I thought the patch mentioned on this page would solve the scrambled > > mouse image on X: it didn't, IIRC ... > > Both the xserver and xf86-video-ati workaround hacks are needed. > > > -- > Earthling Michel Dänzer | http://tungstengraphics.com > Libre software enthusiast | Debian, X and DRI developer >
Re: Hotplugging: VGA to alubook 5,8 [was: Re: getting wireless and dvi out [ ... ]]
On Sat, 2007-11-24 at 02:47 +0100, Wolfgang Pfeiffer wrote: > > On Fri, Nov 23 2007, at 18:58 +0100, Bin Zhang wrote: > > On Nov 23, 2007 2:54 PM, Wolfgang Pfeiffer <[EMAIL PROTECTED]> wrote: > > > On Fri, Nov 23 2007, at 14:49 +0100, Wolfgang Pfeiffer wrote: > > > > > > > Sidenotes: > > > > > > > > Since installing the new driver some artifacts are visible around the > > > > mouse-pointer in its default "arrow" image ... Please let me know if > > > > > > This last line should have been saying: > > > "mouse-pointer on X in its default "arrow" image [ ... ]" > > > > > > > > > > a photo from that might help ... > > > > > > > > And the mouse is completely gone on the console .. haven't had time, > > > > yet, to google/explore that ... > > > > Try adding a line > > Option "SWcursor" "on" > > in Section "Device" of your xorg.conf. That's a rather heavy-handed workaround - in particular, the SW cursor interacts badly with 3D acceleration and XVideo. > The problem seems being gone for the moment, without having changed > xorg.conf here ... Only legacy two-colour cursors are affected, not modern 32 bit ARGB cursors. > S-video unknown connection 800x600+0+0 (normal left inverted right x axis y > axis > ) 0mm x 0mm >800x60060.3* > > ## Note: There was no S-video connection that I knew about It can't be detected reliably, hence 'unknown connection'. > $ xrandr --output DVI-0 --auto > xrandr: cannot find crtc for output DVI-0 This is probably related to S-video, try something like xrandr --output S-video --off --output DVI-0 --auto If you think this could be handled better, please bring it up on the [EMAIL PROTECTED] list. > And this: I saw this > https://bugs.freedesktop.org/show_bug.cgi?id=11796 > This was the main reason I compiled the fresh xf86-video-ati sources: > I thought the patch mentioned on this page would solve the scrambled > mouse image on X: it didn't, IIRC ... Both the xserver and xf86-video-ati workaround hacks are needed. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
