Hi kko, thanks for replying so quickly,
I just installed feisty's new kernel packages (2.6.20-13->2.6.20-14
before reading your response, so I restarted and the problem was gone.
Hmm...
I will keep the hints in mind if this happens again and respond back
here.
Thanks again
--
X completely corr
I'll see if my advice can be of any use.
>From the bug report you referenced it seems that disabling splash from
kernel boot options (in grub) has helped the reporters. You could try
the same to see if your screen corruption is also caused by the splash,
in which case it's probably useful to conti
** Attachment added: "zipped file of pictures of the various terminals"
http://librarian.launchpad.net/7177277/computers.zip
--
X completely corrupts VesaFB Virtual Terminals' image
https://bugs.launchpad.net/bugs/40297
You received this bug notification because you are a member of Ubuntu
Bug
Bug 73826 seems related to this---the open source ati/radeon and fglrx
drivers cause unusable virtual terminals in Edgy
--
X completely corrupts VesaFB Virtual Terminals' image
https://bugs.launchpad.net/bugs/40297
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hi, I have an ATI Radeon 7200, using the open source drivers. If I
change to virtual console 1 (ctrl + alt +f1) or any of the others, I
get very strange things going on. Text in the wrong places, the
blinking cursor not in the correct position, strange colors, etc.
All my virtual consoles are c
Since there is no information whatsoever relating to the "...-ati" -task
in this bug report, in the interest of bug database maintenance I am
going to mark that task as "rejected". As mentioned, there are other
reports (also referenced here) on ATI cards, and tracking the possible
issue is probably
The activity log doesn't show who added the task for "...-ati" to this
bug.
Anyone able to share some light on that, and if the bug is fixed also
for ati? (There are probably other reports originally reported against
ati, too.)
--
X completely corrupts VesaFB Virtual Terminals' image
https://lau
Umm, no. Haven't tested on Feisty. What my last two comments mean, on Dapper,
is this:
- First, with boot parameters amounting to "vga=normal" ("no special vga
options", i.e. vesafb not used), this problem isn't actual and can't be tested.
- Second, after I passed "vga=791" to the kernel at boot
kko: did you mean that this bug isn't present in current Feisty? You
already said before that Dapper is fine :)
--
X completely corrupts VesaFB Virtual Terminals' image
https://launchpad.net/bugs/40297
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/lis
Bug is not present on current Dapper.
** Summary changed:
- X completely corrupts VesaFB Virtual Terminals' image (also Dapper)
+ X completely corrupts VesaFB Virtual Terminals' image
** Changed in: xserver-xorg-video-mga (Ubuntu)
Status: Needs Info => Fix Released
--
X completely corru
Thank you for the information.
I must say that I am now comfortably running an install of Kubuntu
Dapper (apparently with no special vga options for grub), and so am
unlikely to at this point take the trouble of fixing something that
isn't broken.
I will report back, however, if I decide to e.g.
kko: have you tried with later releases? Feisty herd5 was just released,
and after that a new mga-driver got in so you could try them.
** Changed in: xserver-xorg-video-mga (Ubuntu)
Status: Unconfirmed => Needs Info
--
X completely corrupts VesaFB Virtual Terminals' image (also Dapper)
ht
12 matches
Mail list logo
