** Summary changed:
- [K8M800] Xubuntu does not display propery on Lucid alpha-1 with updates, on
Averatec 3280
+ [K8M800] Xubuntu does not display properly on Lucid alpha-1 with updates, on
Averatec 3280
--
[K8M800] Xubuntu does not display properly on Lucid alpha-1 with updates, on
Averatec
As of Tue Jan 12 08:57:44 PST 2010, this seems to have been fixed. I
updated the system with apt-get a few minutes ago, a large number of
packages were updated. After rebooting, the screen now appears normally.
I am not sure what package(s) were changed to fix the problem.
--
[K8M800] Screen ori
This is not competely fixed. When I try to switch to tty screens, I get
a multicolored background, and the ttys don't work. I can, however,
switch back to the X display with alt-F7.
--
[K8M800] Screen origin shifted to center, screen wraps, ttyN screens don't
work, on Averatec 3280 running Lucid
Also note that this is dependent on the kernel version. The X display
origin problem not happen with the lastest kernel, 2.6.32-10-generic
#14-Ubuntu SMP, but it does happen with the previous kernel, 2.6.32-9.
(See Bug #508456, describing another problem that has turned up in the
last day).
The pr
The TTY problem is still happening - switching to tty1...tty6 with ctl-
alt-Fn results in a screen covered with random colored blocks, and
alt-F6 switches back normally. The same colored screen shows while
shutting down or rebooting.
--
[K8M800] Screen origin shifted to center, screen wraps, ttyN
Hi Bartosz -
The result of doing this patch is ...
Xorg.0.log:(II) CHROME(0): Module DDC loaded
Xorg.0.log:(II) CHROME(0): Detected I2CBus1
Xorg.0.log:(II) CHROME(0): Not detected DDC2
I hope that information helps!
Thanks,
- Peter
On Wed, Jan 20, 2010 at 7:18 AM, Bartosz wrote:
> Hi.
> Try
And here is the whole Xorg.0.log, after doing the patch above and
rebooting:
** Attachment added: "Xorg.0.log after above patch has been done"
http://launchpadlibrarian.net/38154435/Xorg.0.log
--
[K8M800] Screen origin shifted to center, screen wraps, ttyN screens don't
work, on Averatec 328
Where will the desired debug information appear - in Xorg.0.log?
On Mon, Oct 12, 2009 at 4:50 AM, Bartosz wrote:
> Please build/install the latest openchrome driver and enable debug mode.
> The detail build instruction for Ubuntu/Debian is available at:
> https://help.ubuntu.com/community/OpenChr
Also, how will I determine that the newly-build driver is actually
installed?
On Mon, Oct 12, 2009 at 4:50 AM, Bartosz wrote:
> Please build/install the latest openchrome driver and enable debug mode.
> The detail build instruction for Ubuntu/Debian is available at:
> https://help.ubuntu.com/comm
I did build and install the debug version of the openchrome driver, and
this version behaves the same.
--
[K8M800] Console screens unusable on Averatec 3280 laptop
https://bugs.launchpad.net/bugs/449061
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed t
Thank you!
No, the bug did not exist in 9.04 and earlier versions, although a
similar display did happen sometimes in MUCH earlier versions during
system startup and shutdown.
I'm attaching Xorg.0.log ...
** Attachment added: "/var/log/Xorg.0.log after installing rebuilt driver"
http://launch
What I have done so far is to boot the Alpha-4, Alpha-6, and Beta live
CDs.
This does not happen with those two Alpha versions.
With the Beta version, it's a bit different. When I switch to consoles 3
through 6, I get a blank screen, instead of the flashing colors, and I
don't seem to be able to
Here's the Xorg.0.log for the Alpha-6 CD
** Attachment added: "Xorg.0.log.alpha-6"
http://launchpadlibrarian.net/33609053/Xorg.0.log.alpha-6
--
[K8M800] Console screens unusable on Averatec 3280 laptop
https://bugs.launchpad.net/bugs/449061
You received this bug notification because you are a
Here's the Xorg.0.log for the Beta version.
I don't immediately see relevant version information for the Openchrome
driver differing between the Alpha-6 and Beta versions.
** Attachment added: "Xorg.0.log.beta"
http://launchpadlibrarian.net/33609103/Xorg.0.log.beta
--
[K8M800] Console screen
Output from `dpkg -s xserver-xorg-video-openchrome:
The current package is version 1:0.2.903+svn758-0ubuntu1
The same version is in the beta CD.
And the same version shows on the Alpha-6 CD.
Could it be that some other module is causing this problem?
--
[K8M800] Console screens unusable on Av
This seems to have stopped happening on this system with the Jetway
motherboard, but it is still happening on my Averatec 3280 laptop (Bug
#447595).
I'm adding Xorg.0.log for this Jetway system.
** Attachment added: "/var/log/Xorg.0.log on 14 Oct 2009"
http://launchpadlibrarian.net/33664838/Xo
Just a few minutes ago, I tried switching to a console on this
Averatec 3280 laptop, and the text screen was normal - no flashing
colors. And the version of the driver is still
$ dpkg -s xserver-xorg-video-openchrome
Version: 1:0.2.903+svn758-0ubuntu1
So, as I was beginning to suspect
Thanks - I'm embroiled in a couple other tasks right now, so I'll try
this by the morning Swiss time. :) I did find gconf-editor - I noticed
it didn't show xscreensaver, which is installed, but rather
gnome-screensaver. Should I install the gnome version instead?
Yes, I do interact with a openchro
Option "NoAccel" "true" enables AntSpotlight and Slip screensavers to
run without crashing the system. I did change to the Gnome
screensaver. I haven't tried any debug versions of software yet.
On Tue, Oct 20, 2009 at 2:37 PM, Tormod Volden wrote:
> No, you don't need gnome-screensaver, but I am
I disabled the Option "NoAccel" after finding that scrolling web pages
became very annoying, and so on. Now I have un xorg.conf
Section "Device"
Identifier "Configured Video Device"
Driver "openchrome"
# Option "EnableAGPDMA" "Off"
# Option "NoAccel" "tru
See bug # 436341, which is still happening on the RC, and is quite
serious.
--
[K8M800] Console screens unusable on Averatec 3280 laptop
https://bugs.launchpad.net/bugs/449061
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-opench
Another Openchrome-related bug is
Bug #455954 AntSpotlight screensaver causes system to lock up immediately
On Wed, Oct 14, 2009 at 11:25 PM, Bartosz wrote:
> ** Changed in: xserver-xorg-video-openchrome (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: xserver-xorg-video-openchrome (U
I am totally confused by the directions, which version of which
package I should check out or download ...
On Sat, Oct 24, 2009 at 10:24 AM, Bartosz wrote:
> Check if this bug exists in the latest openchrome driver,
>
> Please build/install the latest openchrome driver and enable debug mode.
> Th
This should be with the recompiled openchrome driver installed (I'm not
positive this was done correctly) The ant-spotlight screen saver does
not crash the system, as it did before. Acceleration is enabled. I'll
attach xorg.conf as well.
** Attachment added: "Xorg.0.log from several minutes ago"
Here is the xorg.conf file.
Panel size is specified, and acceleration is enabled, I believe. Please
check settings.
Browser scrolling is smooth, so it appears acceleration works to that
extent.
** Attachment added: "rewritten xorg.conf file"
http://launchpadlibrarian.net/34338881/xorg.conf
I'm now using the driver from https://launchpad.net/~xorg-
edgers/+archive/drivers-only and that seems to fix the screensaver
problem as well.
I'm attaching the current Xorg.0.log
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/34358658/Xorg.0.log
--
[K8M800] AntSpotlight sc
I think bug #436341 is probably a variant of this problem, and is fairly
serious.
--
[K8M800] Console screens unusable on Averatec 3280 laptop
https://bugs.launchpad.net/bugs/449061
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-
Oh, that's good to know, thanks!
On Sun, Oct 25, 2009 at 9:30 PM, Tormod Volden wrote:
> Well, you built the exact same version yourself, so they should work the
> same. I don't see anything different in the logs either.
>
> --
> [K8M800] AntSpotlight screensaver causes system to lock up immediat
No one has been assigned to #436341.
--
[K8M800] Console screens unusable on Averatec 3280 laptop
https://bugs.launchpad.net/bugs/449061
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-openchrome in ubuntu.
__
Is this patch and the one in bug report # 296142, comment #31, still
appropriate? I never built the driver with either patch, sorry! Right
now I have
# dpkg -s xserver-xorg-video-openchrome
Package: xserver-xorg-video-openchrome
Status: install ok installed
Priority: optional
Section: x11
Installe
*** This bug is a duplicate of bug 186103 ***
https://bugs.launchpad.net/bugs/186103
What's needed is a way to make this sort of adjustment without going
in and directly editing xorg.conf, such as making a selection at boot
time, as with some older live CDs.
On Wed, Nov 11, 2009 at 9:44 PM, d
Public bug reported:
Binary package hint: xserver-xorg-video-openchrome
This is regarding Lucid alpha-3 as updated to today, a few days before
the beta release.
When I try to switch to a console with, say ctrl-alt-F2, I get a
distorted, magnified background image with a large text cursor. Text
t
Here is a photo of the text-mode screen when I try to get a console
screen with ctrl-alt-F3.
** Attachment added: "Screen shot of distorted text console"
http://launchpadlibrarian.net/40939888/LARGE3970.JPG
--
Console screens unusable on Jetway system with VT8623 [Apollo CLE266], boot
probl
Here is a screen shot of the normal graphics screen, showing the same
bobcat kitten.
In the previous screen shot, note that there is a block cursor above the
kitten's right ear (on its right).
** Attachment added: "Gnome screen with full background image."
http://launchpadlibrarian.net/4093994
This seems to be #448911, but with the additional problems booting with
the 2.6.32-16-generic kernel, and with today's photos of the console
screen problem.
--
Console screens unusable on Jetway system with VT8623 [Apollo CLE266], boot
problems
https://bugs.launchpad.net/bugs/538893
You received
After a system update earlier today, I found that this is definitely
still happening, and, since I couldn't immediately find this bug report,
I reposted it as #538893. There are additional problems when booting,
and I added a screen photo in that report, showing what happens to the
text console scr
Here is an archive containing
apt-show-versions.txt
dmesg
lspci.vvnn.txt
Xorg.0.log
Xorg.0.log.old
I updated the system in the last half hour, so I included apt-show-versions
output.
The system starts up X properly on boot now (I no longer have to press ALT-F7
as described above) but otherwise
*** This bug is a duplicate of bug 538893 ***
https://bugs.launchpad.net/bugs/538893
** This bug has been marked a duplicate of bug 538893
Console screens unusable on Jetway system with VT8623 [Apollo CLE266], boot
problems
--
[CLE266] Console screens unusable, strange background
https:/
This is still happening on this system as of update to beta-1 and
further updates through 20 March 2010.
--
Console screens unusable on Jetway system with VT8623 [Apollo CLE266], boot
problems
https://bugs.launchpad.net/bugs/538893
You received this bug notification because you are a member of U
I upgraded to the Lucid beta-1 starting one instance of Karmic on this
laptop yesterday (this is a dual-boot system now, with Karmic and Lucid
on it) and have installed some updates since.
The problem with the offset horizontal position of the screen (with
wrapping around), as described above, rem
I'd like to point out that the behavior of the driver looks to me like
there is a 512-pixel delay or advance in the timing of horizontal sync.
At 1024x768 this means the origin of the screen is shifted over half the
screen width, and at 800x600 this means the origin is near the right
side of the sc
This has not happened for some time on my Averatec 3280 laptop. There is
still a problem during startup: sometimes a clouded image partially
obscures the screen during startup, but eventually X will start up,
subject to some problems which are still happening (see Bug #495553 for
that). (This under
I was mistaken about one point in comment #96 - the login window IS
centered when xorg.conf is in place.
--
[K8M800] Screen origin shifted to center, screen wraps, ttyN screens don't
work, on Averatec 3280 running Lucid with openchrome driver
https://bugs.launchpad.net/bugs/495553
You received t
There is no impovement in this bug with the most recent build of the
openchrome driver.
apt-show-versions xserver-xorg-video-openchrome
xserver-xorg-video-openchrome/lucid uptodate 1:0.2.904+svn827-1
--
[K8M800] Screen origin shifted to center, screen wraps, ttyN screens don't
work, on Averatec
Please ignore the what I said in comment #96 about the login screen, and
all of #98 - those comments apply to Karmic on the same computer.
Also, I was miscalculating in #97 regarding the 800x600 screen. The full
screen is 246 mm wide, and the x-origin is shifted over to 226 mm. That
is about 735 p
This is still happening with today's update of the openchrome driver:
pe...@lightning:~$ apt-show-versions xserver-xorg-video-openchrome
xserver-xorg-video-openchrome/lucid uptodate 1:0.2.904+svn827-1
Should this be reported directly to the openchrome project? (Along with
Bug #495553) - would tha
Should I report this directly to the openchrome project? Might that
help?
--
[K8M800] Screen origin shifted to center, screen wraps, ttyN screens don't
work, on Averatec 3280 running Lucid with openchrome driver
https://bugs.launchpad.net/bugs/495553
You received this bug notification because yo
This is still happening as of today. The screen is split, and wraps
around, as described above, and switching to a text console results in a
blank screen.
This does not happen under Karmic on this dual-boot system, so the
kernel used is possibly an issue.
To Georg Duffner - when you use the 2.6.3
Georg Duffner - thank you. It's possible that this is a problem in the
kernel framebuffer or in some other Lucid component relating to the
newer kernel.
I still have kernel 2.6.31-20-generic in my Lucid /boot directory, and
was able to boot into this. The login screen came up properly, and the
Gno
I'm attaching some logs. The current kernel version - from Karmic - is
given here:
Ubuntu version and kernel version
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=10.04
DISTRIB_CODENAME=lucid
DISTRIB_DESCRIPTION="Ubuntu lucid (development branch)"
Linux eros 2.6.31-20-generic #58-Ubuntu SMP Fri Mar 12 05:23:0
When I boot with the 2.6.31-20-generic #58 kernel (see above) I get the
following messages when I first boot:
mount: Mounting none on /dev failed: no such ...
chroot: Cannot execute /etc/apparmor/initramfs: No such file or directory
init: Plymouth main process (283) terminated with status 69
mount
While looking at Bug #495553 on a laptop I have with another UniChrome
display, someone suggested I try booting with a kernel from Karmic. (see
comments on that bug after about #100).
So I copied the 2.6.31-20-generic #58-Ubuntu SMP Fri Mar 12 05:23:09 UTC
kernel from that system, and the associat
** Description changed:
Binary package hint: xserver-xorg-video-openchrome
- This is regarding Lucid alpha-3 as updated to today, a few days before
- the beta release.
+ This is still happening with Lucid beta-1 as updated to 2019-03-27. See
+ comment #6 - there is some kernel dependency, as
Hi Bartosz - Oops! I didn't see your last update until just now.
However, the fix seems to have been checked in; when I updated this
morning, the resolution seemed to be correct, 1024x768.
Thank you!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
Public bug reported:
Binary package hint: xserver-xorg-video-nouveau
I tried booting the Natty 11.04 beta-1 live cd (32-bit) on a compaq
presario with an nVidia chipset. The system took a long time to boot,
possibly because of fairly low RAM and possibly because the hard disk is
currently only fo
** Attachment added: "Xorg.0.log, lspci lsmod uname -a outputs"
https://bugs.launchpad.net/bugs/747069/+attachment/1962688/+files/bug.tgz
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launch
Bug #707755 is against the same computer with an earlier build of Natty
11.04, as of 2011-01-252011-01-25.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/747069
Title:
[nat
The date in #2 is 2011-01-25
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/747069
Title:
[natty beta-1] Screen flashes on and of every few seconds with nouveau
driver
_
Here is some information regarding the FreeBSD installation on the same
machine, which works using the vesa driver:
[peter@compaq /etc/X11]$ uname -a
FreeBSD compaq.belew 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Thu Feb 17 02:41:51
UTC 2011 r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENE
My next experiment will be to boot in text mode, add an xorg.conf file
based on the one originally generated by the PC-BSD live CD, and see if
that works with the vesa driver. The problem is clearly with the driver
for the nVidia chipset, which is apparently essentially the same as in
Fedora 14.
-
This is a Compaq Presario SR1000 system (System Number EX325-AA-ABA)
(originally sold as "Microsoft Windows XP Media Center Edition 2005")
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpa
My problem was with the live CD (I have FreeBSD taking up the whole
disk drive, and don't want to install Ubuntu in this system). There
doesn't seem to be an easy way to choose the desktop, since the system
auto-logins to Gnome when it starts up, without showing a login screen
(unless there is a p
Ubuntu 11.04 'natty narwhal' seems to work well on this system, which is
pleasantly surprising!
I downloaded the ISO 2 days ago, and burnt a DVD from the image. As
before, the live CD was unable to determine the actual resolution of the
screen (1024x768, Unichrome controller) and set a higher reso
Hi Bartosz - I removed the xorg.conf file and rebooted. The login
background and login dialog appear in the 1600x1200 mode (note that the
grub2 screen appears properly, using a custom background I installed).
I've attached the Xorg.0.log file.
** Attachment added: "Xorg.0.log after booting withou
After that, I proceeded to log in. The screen came up in 1024x76 mode,
because I had previously set that resolution with the
System>Preferences>Monitors dialog.
So I used System>Preferences>Monitors to set the resolution to
1600x1200, and rebooted. After I logged in, the screen came up in
1600x120
On rebooting another time, and logging in, the screen came up 'properly'
in 1600x1200 mode, with the top panel showing correctly. I've attached
Xorg.0.log3 after that.
** Attachment added: "Xorg.0.log after another boot in 1600x1200 mode."
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg
I then set the res to 1024x768, using the System>Preferences/Monitor
dialog, and logged out and logged in (without rebooting the OS). This
time the screen came up in 1024x768 without the top panel, but showing
the bottom panel. I've attached yet another Xorg.0.log (-.log4) file.
THEN I rebooted co
Note that the tests of Natty on my Averatec - last few comments - were
using the Ubuntu Classic Session - Gnome. Unity will not work on the
Unichrome display hardware.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-openchrome
As of 11.04 "Natty" Ubuntu, the remaining problem is that the initial
display is set at 1600x1200. For Ubuntu with Gnome, the
System/Preference/Monitors dialog is accessible, and the screen res can
be changed to 1024x768 (see last few comments in bug #495553).
For the unichrome display, only Gnome
A new bug appeared yesterday: frequently the top and bottom panels don't
appear after login. I just filed this bug separately as #689377. This
happens most of the time in Classic Mode (Gnome), but not in Gnome Safe
Mode.
--
You received this bug notification because you are a member of Ubuntu-X,
Note that further comments were added to Bug #689377 today, as further
problems appeared. I don't think these problem were due to the display
driver, but they do affect testing of display problems somewhat, and
vice versa. For example, if the xorg.conf file is removed, it's not
possible to go into
I built and installed the driver, and rebooted a couple of times. I've
added an archive containing Xorg.0.log and Xorg.0.log.old. There was no
xorg.conf file in /etc/X11.
The main change was that the login screen was no longer at 1600x1200.
The grub2 screen and the final Gnome screen appeared to b
I built and installed the driver, and rebooted a couple of times. I've
added an archive containing Xorg.0.log and Xorg.0.log.old. There was no
xorg.conf file in /etc/X11.
The main change was that the login screen was no longer at 1600x1200.
The grub2 screen and the final Gnome screen appeared to b
Actually, the remaining problem regarding the initial screen resolution
is covered by Bug #186103 - other issues on THIS bug seem to have been
resolved.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-openchrome in ubuntu.
http
Comment #53 is an accidental duplicate of #52. Oops!
This bug report contains the remaining issue in Bug #495553.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-openchrome in ubuntu.
https://bugs.launchpad.net/bugs/186103
Tit
I haven't applied the patch (#56) yet, but switching to text console and
back works fine, and hibernation seems to also.
Now I'll try the patch ...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-openchrome in ubuntu.
https://
I applied the patch. It went well with via_mode.c, but there were some
errors with via_driver.c - here is via_driver.c.rej
--- via_driver.c(wersja 886)
+++ via_driver.c(kopia robocza)
@@ -725,7 +725,6 @@
break;
case VIA_K8M800:
pVia->DRIIrqEnable
I tried doing that. Running svn update from the src dir did nothing. I
then tried
svn update http://svn.openchrome.org/svn/trunk openchrome from /root
(openchrome is in /root/openchrome).
Skipped 'http://svn.openchrome.org/svn/trunk'
Uopenchrome/ChangeLog
Uopenchrome/src/via_mode.c
Uo
After restarting with xorg.conf in place, the screen comes up as
1024x768, with just the bottom panel (but that's another bug). I think
I'll try checking out the sources again from scratch and rebuild, later
today. Or perhaps there was some error in my use of svn.
--
You received this bug notific
Now -
svn checkout http://svn.openchrome.org/svn/trunk openchrome
...
Checked out revision 888.
I then tried to apply the patches. Again they seem to fail. I didn't try
to build.
Please send me fully patched .c files - I don't seem to be doing the
patches right, or the patch file is bad.
--
Yo
Ok - I re-checked-out and rebuilt the driver, with no patches, and the
native resolution is now 1024x768!
Many thanks, Bartosz!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-openchrome in ubuntu.
https://bugs.launchpad.net/b
And thanks to the developers upstream!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-openchrome in ubuntu.
https://bugs.launchpad.net/bugs/186103
Title:
[K8M800] Panel on K8M800 is not supported (Averatec 3280)
__
There has been a severe regression TODAY in 11.04 - now the tty screens
don't work. Ctrl-alt-F1 etc switch to a random screen which doesn't
sync.
** Attachment added: "Xorg.0.log after text console failure."
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/495553/+a
There has been a severe regression TODAY in 11.04 - now the tty screens
don't work. Ctrl-alt-F1 etc switch to a random screen which doesn't
sync.
See bug #495553.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-openchrome in u
Reopen for possible backporting of 11.04 version of this driver to
10.04.3
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-openchrome in Ubuntu.
https://bugs.launchpad.net/bugs/495553
Title:
[K8M800] Maverick 10.10 live-CD l
The version of the openchrome driver which is working properly on this
system under Natty 11.04 is:
peter@cupid:~$ apt-show-versions xserver-xorg-video-openchrome
xserver-xorg-video-openchrome/natty uptodate 1:0.2.904+svn916-1build1
Will there be daily builds of 10.04.3 available prior to that re
I downloaded the 16 July 2011 build of 10.04.3, and apparently the
repaired driver has not been backported to this release.
Two issues:
1. the screen comes up in 1600x1200 or something like that, so the
bottom right of that screen image does not show on the 1024x768 panel,
as before.
2. A login
I just reinstalled the current openchrome driver from the repository,
rebooted, and now switching to text modes works properly, though I have
to have xorg.conf installed to get the right resolution. I'll try
rebuilding the driver according to Bug #186103 and see if that helps
this issue.
--
You r
Checking out the driver sources (rev. 890 now) and rebuilding makes
resolution detection work still, but switching to text screens does not
work.
Reinstalling the openchrome driver from the repository makes text
screens work, but the resolution fix isn't in that driver, so xorg.conf
is necessary.
I'll try both 887 and 891 (and 888?) in about 24 hours - I'm out of town
today.
On Sun, Dec 19, 2010 at 11:58 AM, Bartosz <495...@bugs.launchpad.net> wrote:
> Check also if this bug exists in the latest openchrome revision (r891):
> http://openchrome.org/trac/changeset/891/trunk
>
> --
> You recei
See http://www.openchrome.org/trac/ticket/366 - The initial screen res
seems to be set at 1024x768, and switching to/from text screens works
too, with r891 of the OpenChrome driver.
Thanks, Bartosz!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed t
See http://www.openchrome.org/trac/ticket/366 - The initial screen res
seems to be set at 1024x768, and switching to/from text screens works
too, with r891 of the OpenChrome driver. This is with Ubuntu 11.04
updated as of today.
Note that ~/.config/monitors.xml has been removed - this contains the
** Description changed:
Binary package hint: xorg-server
+ [ Comments added for Natty 11.04 alpha version }
[ Comments added for Maveric beta versions ]
It is now impossible to boot and log in on this system from the beta-2
live CD - see comment #111.
THIS NOW SEEMS TO BE 'CURED
A serious problem has just arisen after an update today. I did the
update while the system was started, but before logging in (I switched
to a text console while the login screen was appearing). Once I logged
in, in safe mode, the 2 icons I'd created on the desktop were bouncing
up and down, and ne
A side issue - the system was unable to support USB devices that were
attached - a keyboard and mouse. Console 1 reported errors about that.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-openchrome in ubuntu.
https://bugs.lau
The behavior described above was with the Openchrome driver build from
source a couple of days ago. I then reinstalled the driver from the
repository, and the only difference in behavior was that the initial
resolution after booting turns out to be 1600x1200; and that can be
changed by installing a
Bartosz: What I would really like to happen is to have these fixes
backported to 10.04.1 LTS, so that they might be released by 10.04.2
update. Is that reasonable? 11.04 seems very unstable, and is not
useable at the moment. Perhaps I should repartition the HD and set up a
dual boot between 10.04 a
As of the last couple of days, it appears that the screen resolution of
1024x768 is set automatically when X starts.
Also, switching to/from text modes seems to work. There is an oddity
about switching back from a text console to X: using Alt-F7 just
switches to a blank screen with "[ OK ]" in the
As of the last couple of days, after updating packages, it appears that
the screen resolution of 1024x768 is set automatically when X starts. So
this fix has been checked in to the repositories.
Also, switching to/from text modes seems to work. However:
There is an oddity about switching back fro
Running 10.10 maverick with updates through today, there is a problem
that I can't switch to text console - the screen is full of big blocks
of color. I have to use alt-F8 or alt-F9 to switch back to the X
display.
Show Ubuntu version and kernel version
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=10.10
DIST
201 - 300 of 322 matches
Mail list logo
