*** This bug is a duplicate of bug 274340 ***
https://bugs.launchpad.net/bugs/274340
** Changed in: xorg-server
Status: Confirmed => Fix Released
--
vesa driver freezes on VIA P4M900
https://bugs.launchpad.net/bugs/163192
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 274340 ***
https://bugs.launchpad.net/bugs/274340
This is well known and already resolved openchrome bug.
More detail is available at:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/274340
** This bug has been marked a duplicat
I'm going to assume this is resolved now
** Changed in: xserver-xorg-video-vesa (Ubuntu)
Status: Triaged => Fix Released
--
vesa driver freezes on VIA P4M900
https://bugs.launchpad.net/bugs/163192
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
etrusco, thanks for testing on jaunty and letting us know the issue is resolved.
Torsten, can you confirm the issue as fixed for you as well?
--
vesa driver freezes on VIA P4M900
https://bugs.launchpad.net/bugs/163192
You received this bug notification because you are a member of Ubuntu
Bugs, wh
At last P4M9000 is working in jaunty alfa5 :-)
In Intrepid I could get it to work by using the common procedure found
around the net (and in ubuntu wiki):
Set "Driver" to "openchrome" and add option "XaaNoImageWriteRect" to xorg.conf.
In earlier jaunty versions I could only avoid it freeze by add
Ubuntu Interpid 8.10
I have a AMD 64 + ASUS K8V-VM
01:00.0 VGA compatible controller: VIA Technologies, Inc.
K8M890CE/K8N890CE [Chrome 9] (rev 11)
System hard locks when booting from live cd at the start of gdm. I have
to pass xforcevesa in the grub menu. It does not lock after that - but
there
** Changed in: xserver-xorg-video-vesa (Ubuntu)
Assignee: Bryce Harrington (bryceharrington) => (unassigned)
--
vesa driver freezes on VIA P4M900
https://bugs.launchpad.net/bugs/163192
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: xorg-server
Status: Unknown => Confirmed
--
vesa driver freezes on VIA P4M900
https://bugs.launchpad.net/bugs/163192
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
Symptoms I get with my configuration: (VIA P4M900 + VIA Chrome9 IGP)
1. I can't even get a working framebuffer without adding vga=791 on grub. This
also happens even in the alternate Hardy install CD. (which means I need to add
vga=791 when installing Ubuntu) (bug report pending)
2. xorg autodete
Hendy, can you please attach your Xorg.0.log and xorg.conf files from
both cases - when enabling manually, and when using the automatically
detected driver.
@Torsten, thanks for collecting the backtraces. There isn't an obvious
error jumping out to me, but I've gone ahead and forwarded this bug
u
Confirmed. I've been having this problem since Feisty and not resolved
in Hardy.
In addition, xrandr reports incorrect resolutions and I can't run
displayconfig-gtk even after logging in successfully into gnome. As this
may involve separate bugs I'll report several bugs and link them
appropriately
Sorry. DE-confirmed the problem.
It seems the vesa is OK when enabled manually. i.e. in Ubuntu Hardy,
editing the xorg.conf file and: adding Driver "vesa"
In my Ubuntu Hardy, system freezes crashed loading the automatically
detected xorg driver which to this point is still unknown (openchrome?)
** Changed in: xserver-xorg-video-vesa (Ubuntu)
Importance: Undecided => High
Status: Incomplete => Triaged
--
vesa driver freezes on VIA P4M900
https://bugs.launchpad.net/bugs/163192
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
And here is what happens after the kill of the X server:
(gdb) cont
Continuing.
Program received signal SIGUSR1, User defined signal 1.
[Switching to Thread 0xb7c8ba30 (LWP 5617)]
0xb7faf410 in __kernel_vsyscall ()
(gdb)
Continuing.
Program received signal SIGTERM, Terminated.
0xb7faf410 in __k
After installing and updating Hardy, the X server continues to run and
gdb can be attached to the process:
(gdb) bt full
#0 0xb7faf410 in __kernel_vsyscall ()
No symbol table info available.
#1 0xb7df973d in select () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
#2 0x081b22
Attached is the Xorg.0.log. The X server seems to die completely:
[EMAIL PROTECTED]:/var/log$ ps aux | grep X
root 7996 0.0 0.2 3408 1188 ?S13:46 0:00
hald-addon-storage: no polling because /dev/hda is locked via O_EXCL
ubuntu 10336 0.0 0.1 3004 744 pts/1R+ 1
** Changed in: xserver-xorg-video-vesa (Ubuntu)
Status: New => Incomplete
--
vesa driver freezes on VIA P4M900
https://bugs.launchpad.net/bugs/163192
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
Torsten, if this is still happening on hardy-beta, would you be able to
get a backtrace for us for the freeze?
See: https://wiki.ubuntu.com/DebuggingXorg
--
vesa driver freezes on VIA P4M900
https://bugs.launchpad.net/bugs/163192
You received this bug notification because you are a member of U
When forcing the system to a bullet proof X session the vesa driver will
still freeze the graphics.
--
vesa driver freezes on VIA P4M900
https://bugs.launchpad.net/bugs/163192
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ub
The daily live for Hardy from 2008-02-15 basically works, but the
desktop area is set to large. The Xorg.0.log of the install session is
attached.
This part looks relevant to me:
(II) CHROME(0): Configured Monitor: Using default hsync range of 31.50-37.90 kHz
(II) CHROME(0): Configured Monitor: U
** Changed in: xserver-xorg-video-vesa (Ubuntu)
Sourcepackagename: xorg => xserver-xorg-video-vesa
--
vesa driver freezes on VIA P4M900
https://bugs.launchpad.net/bugs/163192
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubu
The freeze of the graphics system occurs completely independent from
resume.
--
vesa driver freezes on VIA P4M900
https://bugs.launchpad.net/bugs/163192
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ehh... yes i know...
the problem is, kernel can't take response for all graphiccard workarounds and
broken vBIOSes... so in this case exist usersapce software which try according
whitelist resume your PC. see this post:
http://bugzilla.kernel.org/show_bug.cgi?id=7225
on other hand not all prob
The problem reported is not primarily a suspend problem, but a freeze of
the graphics system.
--
vesa driver freezes on VIA P4M900
https://bugs.launchpad.net/bugs/163192
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-b
Ok... let see
Please reed this
https://wiki.ubuntu.com/DebuggingKernelSuspend
it will explain you how to get more debug info we need. If you still
have a questions feel free to ask.
Regards,
Alex
--
vesa driver freezes on VIA P4M900
https://bugs.launchpad.net/bugs/163192
You received this bug
hpet is not enabled and adding 'nohz=disable' does not affect the freeze
behaviour.
--
vesa driver freezes on VIA P4M900
https://bugs.launchpad.net/bugs/163192
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailin
other suggestion is dyntics, enabled in new 2.6.22 kernel
so try to boot with this too:
nohz=disable
--
vesa driver freezes on VIA P4M900
https://bugs.launchpad.net/bugs/163192
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
there is some known problems with hpet timer. please take a look at
cat /proc/timer_list | grep "Clock Event Device"
if hpet is enabled you should try to disable it with kernel option:
hpet=disable
--
vesa driver freezes on VIA P4M900
https://bugs.launchpad.net/bugs/163192
You received this bu
Thanks Tormod, I had asked Torsten to assign it to me in this case; I'll
make sure to let people know they need to mention I gave permission for
assigning the bug.
--
vesa driver freezes on VIA P4M900
https://bugs.launchpad.net/bugs/163192
You received this bug notification because you are a mem
Sorry, I had no idea he actually had asked you to do it :)
** Changed in: xorg (Ubuntu)
Assignee: (unassigned) => Bryce Harrington (bryceharrington)
--
vesa driver freezes on VIA P4M900
https://bugs.launchpad.net/bugs/163192
You received this bug notification because you are a member of Ub
Please don't assign bugs to people without their consent.
** Changed in: xorg (Ubuntu)
Assignee: Bryce Harrington (bryceharrington) => (unassigned)
--
vesa driver freezes on VIA P4M900
https://bugs.launchpad.net/bugs/163192
You received this bug notification because you are a member of Ubu
31 matches
Mail list logo
