iver -version appeared in Debian-testing
(Andreas Glaeser)
- --
Message: 1
Date: Sat, 26 Mar 2016 16:35:23 +0100
From: Andreas Glaeser
To: openchrome-us...@lists.freedesktop.org
Subject: [Openchrome-users] New openchrome
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
see a new report there:
801...@bugs.debian.org
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iEYEARECAAYFAlYad84ACgkQ5+rBHyUt5wtgZwCcDitk0YeGr5sYrldIJEupWrnm
luAAoKNtre1wLJ/irjJ8KcSQMUZcylyP
=yECd
-END PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today I visited the Openchrome-Project Homepage, the Debian-package description
contains a
link there:
> andrew@a68n:~$ aptitude show xserver-xorg-video-openchrome
> Package: xserver-xorg-video-openchrome
> State: installed
> Automatically instal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
see there:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800367
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iEYEARECAAYFAlYJTCsACgkQ5+rBHyUt5wuLRwCff0lVMx0auclOHbxDJj+FdT3B
LZgAnj/0pcIe9wUIbxUKu92GbAGK908o
=8UPa
-END PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: xserver-xorg-video-openchrome
Version: 1:0.3.3-1+b2
Severity: normal
Dear Maintainer,
I have reported this as an installation report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788337
For the openchrome-driver it's a normal issue. I t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Now with Jessie, I tried to connect an external VGA-monitor and this actually
works.
During the boot-process both displays were mirrored, showing the same things,
but upon
xserver-start there is the login-screen on the external monitor, the
LVDS-scr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
When booting up oldstable-live, there is some output on the screen at least.
But it seems to be the wrong display-resolution or graphics-mode.
See attached Xorg-log.
This seems to be the most workable variant, set up oldstable and try to set
things
s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: xserver-xorg-video-openchrome
Version: 1:0.3.3-1+b2
Severity: normal
Dear Maintainer,
hardware-information about the host-PC can be found in my installation-report
there:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786872
- -- Packa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today I tried the recipe described there on another system:
http://debian-handbook.info/browse/stable/sect.remote-login.html
[see bottom of the page]
This is not workable on Jessie/testing, both as client and as vnc-host.
I set up GNU-inetd:
i in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Begin forwarded message:
Date: Tue, 25 Nov 2014 10:15:29 -0500
From: "Andreas Glaeser"
To: "Andreas Glaeser"
Subject: An IBM message from Andreas Glaeser
Dear Andreas Glaeser,
IBM is sending this e-mail message to you at m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Now I tried this recipe:
http://www.ibm.com/developerworks/library/os-multiuserloginsvnc/index.html
[see below]
It works fine for me with tightvncserver, but I had to restart the remote
server once in
order to be able to log in to it with xtightvnc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 22 Nov 2014 09:42:04 +
ow...@bugs.debian.org (Debian Bug Tracking System) wrote:
> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Trying this out in a bit more detail, it showed, that the identical problem
exists with
Wheezy and 32-bit architecture, it is simply a matter of removing the
proprietary
radeon-firmware in firmware-linux-nonfree, so everything works without
modeset
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Since yesterday I have been doing some research about doing XDMCP over SSH,
which turned
out to be not workable, because SSH does not support tunnelling UDP-connections.
Then, upon looking around some more, I found x2go:
https://en.wikipedia.org/wik
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Looking at this in more detail, it showed, that XFCE and LXDE-desktops are not
affected,
but it is not a GTK3-exclusive problem, but besides Cinnamon it also shows with
the
E17-desktop and also with KDE-Plasma-Desktop, but it looks different there.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The graphics-failure only seems to occur when taking the installation from
another AMD64-device and booting it on HP t5735, it is quite strange.
I tried two different installed systems from two different PCs already and saw
the same
problem with both
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: xserver-xorg-video-radeon
Version: 1:7.5.0-1
Severity: normal
Dear Maintainer,
I tried i386 architecture today, which works just fine, so the problem of broken
graphics-output and dead DVI-output is only specific to AMD64-architecture.
I am
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I tried this on another PC today, running Wheezy/stable.
The situation is the same there. GDM3 does not allow any logins via XDMCP,
although
configured accordingly, lightdm allows this with Xnest only, but not with
Xephyr.
Tagging this accordingly.
T
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: xorg
Version: 1:7.7+7
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It showed the same scary flashing screen at boot- and shutdown-time.
[more info attached (Xorg.0.log.xz)]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlJ49ZoACgkQ5+rBHyUt5wthPwCeKlfrkV5fbBV18KtqCe/sOzKR
IZsAn05P3jA1h3i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
andreas@md-ho:~/Documents$ glxgears
1971 frames in 5.0 seconds = 394.131 FPS
2307 frames in 5.0 seconds = 461.212 FPS
2474 frames in 5.0 seconds = 494.774 FPS
^C
#
#The graphics are fast enough, even when running without the proprietary
radeon-firmwar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[see attachment, radeon-info.txt.xz]
Problem also reported there:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728600
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlJ2UT0ACgkQ5+rBHyUt5wu/lACfQCMKz87QXrrz7CvGpCPSih+c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Removing firmware-linux-nonfree made the initialization- und shutdown-blinking
of my
monitor disappear actually. So I switched to the KDE-desktop now, putting
cairo-dock
towards the top of the screen, so something familiar remains.
This is a viable w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This makes it impossible to do anything without X.
I forgot to mention it.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlJP+zAACgkQ5+rBHyUt5wsRbwCaAhWdJy8mfhG1qJLmafGE/JJp
tzYAmwT18Ev7J8/bxs+zXjyvCp78NFlb
=ylAa
-EN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today I installed the most recent kernel-version
'linux-image-3.7-trunk-686-pae_3.7.8-1~experimental.1_i386.deb'
from experimental on my
nettop-box and found the issue is really resolved now there.
Probably all I have to do is wait until the
fix is ba
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Upon reinstalling today and doing no text-mode configuration at all to Xorg, I
put
'video=LVDS-1:d" boot option into /etc/default/grub, 'linux-firmware-nonfree'
was
installed, then 'update-grub' was done. Although it was a bit tricky to guess,
where
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Upon searching online and finding a similar question here:
http://askubuntu.com/questions/22812/what-does-the-dmesg-error-composite-sync-not-supported-mean
I tried adding the boot-option 'nomodeset' in /etc/default/grub, but neither
did this
make the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please see attachment
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAlEQ9QQACgkQ5+rBHyUt5wvO3ACeNH/CY4hqQ7uFAAxR3Y4b156N
qR4AoKvbZdKsrOac+PlctE7Y0cijJuv2
=8niC
-END PGP SIGNATURE-
dmsg.txt.gz
Description: GNU Z
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 04 Feb 2013 10:27:56 +0100
Michel Dänzer wrote:
> On Mon, 2013-02-04 at 09:30 +0100, Andreas Glaeser wrote:
> >
> > The 'firmware-linux-nonfree' package was set up, which made DRI work and
> > Gnome3 ru
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
After fussing for some hours, trying to configure my xorg-server properly, I
admit now,
that it plainly is not possible. I attach my /etc/X11/xorg.conf and the
corresponding
X-logfile, both zlib-compressed.
First I tried to limit Vmax and Hmax in ord
> From: Michel Dänzer
> To: Andreas Glaeser , 672...@bugs.debian.org
> Subject: Re: Bug#672223: xserver-xorg: xorg unusable due to hanging in
> reset-loop since
> todays upgrades Date: Wed, 09 May 2012 11:28:56 +0200
> X-Mailer: Evolution 3.2.2-1.0
> Organization: Debian
&
On Thu, 12 Apr 2012 17:34:17 +0200
Sven Joachim wrote:
> Am 12.04.2012 um 08:05 schrieb Andreas Glaeser:
>
> > On Fri, 06 Apr 2012 08:51:21 +0200
> > Sven Joachim wrote:
> >
> >> This is supposed to work, but the Nouveau Wiki¹ mentions that there are
> >
On Fri, 06 Apr 2012 08:51:21 +0200
Sven Joachim wrote:
> Am 05.04.2012 um 12:26 schrieb Andreas Glaeser:
>
> > Now I set FB_NVIDIA=n and tried to boot the result from my build. See
> > Attachments: .config.gz and screenshot.jpg.
> > I took the screenshot at the momen
This is to inform you of souble success.
Not only did it work to use my usb dvb-t stick for what it was
originally made, for watching tv, but it was also possible to build a
custom desktop kernel using 'make-kpkg' for my g4 mac, which runs the
testing release. It required some fussing and fumbling
34 matches
Mail list logo
