Peter Mansvelder, this bug report is being closed due to your last
comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/678192/comments/33
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yell
Sorry, forgot to close the status, I have had no further problems using
natty and higher versions. In the meantime I replaced the motherboard
because of other problems, so I have no recourse to the exact same
configuration anymore. The new system is almost identical in specs,
though (only differenc
Peter Mansvelder, this bug was reported a while ago and there hasn't
been any activity in it recently. We were wondering if this is still an
issue? If so, could you please test for this with the latest development
release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live
Hello Bryce,
I just got round to starting up my machine with the Natty image, and 'Lo and
Behold!', the screen came up with full native resolution. So it seems the fixes
to the intel driver will fix my problem.
One question that remains: I changed from a smaller screen to this new monitor;
woul
Hello Bryce,
I noticed the same bugs, but rummaging around on the net gave no clear
answer, so I dismissed it, but I will try to see what happens when I
boot a 'natty' CD. Do you have a link for that? I am not that familiar
with launchpad...
Peter
Op 22 nov 2010, om 20:49 heeft Bryce Harrington
Hi Peter,
Thanks for attaching the logs. I note this in your dmesg:
[ 263.278247] mtrr: no MTRR for d000,7b found
[ 1016.285214] [drm] Module unloaded
[ 1029.589888] i915 :00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 1029.589904] i915 :00:02.0: setting latency timer to
apport information
** Tags added: apport-collected
** Description changed:
Binary package hint: ubuntu-docs
I have Ubuntu 10.10 installed on a foxconn motherboard with intel built-in
graphics; I have an IIyama Prolite 2250MTS touchscreen attached, and the touch
function work flawlessly
Hmm well it looks like you have a 945g which certainly is supported by
the kernel modesetting driver, so I don't see a reason why it would fail
unless something is wrong with your kernel installation.
It's likely this is a kernel problem (either a bug or something with how
it got installed on your
** Package changed: ubuntu-docs (Ubuntu) => xserver-xorg-video-intel
(Ubuntu)
--
monitor resolution not found with intel driver
https://bugs.launchpad.net/bugs/678192
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
** Attachment added: "X logfile without xorg.conf file (crash)"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/678192/+attachment/1740467/+files/Xorg.1.log
--
monitor resolution not found with intel driver
https://bugs.launchpad.net/bugs/678192
You received this bug notification
** Attachment added: "X logfile with forced 'vesa' driver"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/678192/+attachment/1740466/+files/Xorg.0.log
--
monitor resolution not found with intel driver
https://bugs.launchpad.net/bugs/678192
You received this bug notification becau
11 matches
Mail list logo
