I did fresh install from usb-startup disk. After that
i915.resolution=800x480 works on boot options. And it did not broke
after updating.
I was just stupid that I did not know how to add boot options to LiveCD.
I don`t know if this is correct way to do it but I just pressed F6 and
esc to get
I found a work-around for this bug, you can see bug #467841, at the end
there is a patch (sortof) that enables normal boot with KMS and intel
driver and X startx normally with no problem after that.
--
[i945GM] No screen(s) found after updgrade to karmic alpha 5
Now both i915.modeset=0 or i915.resolution=800x480 option does not work
anymore. And if I have seen right the i915 mod has been removed and
915resolution have been added? sudo 915resolution -l command responses:
command not found
Tried also todays daily cd-image and it does not work either, same
Karmic LiveCD tested - endless loop saying failed to restore crtc
configuration -22. LiveCD was daily-live build from cdimages.ubuntu.com
20091014/
--
[i945GM] No screen(s) found after updgrade to karmic alpha 5
https://bugs.launchpad.net/bugs/429369
You received this bug notification because
Seems that i915.resolution=800x480 option works. I also tried to add:
insmod vbe
set gfxmode=800x480
terminal_output.gfxterm
set gfxpayload=keep
before linux command on grub but that did not help. I tought that it
would pass correct resolution for booting kernel but I`m not really sure
what I`m
I changed few lines from /etc/default/grub to look like:
GRUB_CMDLINE_LINUX_DEFAULT=quiet splash i915.resolution=gfxmode
and:
GRUB_GFXMODE=800x480
Now grub is configured to use correct resolution and also it goes to
booting options. But in this case is KMS used or UMS?
When typing vbeinfo,
To make sure that this isn't some artifact of the upgrade process, could
you verify that this is also a problem with a LiveCD?
It shouldn't make a difference if you are using xorg-edgers or not,
since the monitor detection should happen in the kernel when KMS is
used. Could you with an updated
Hmm.. I just booted with second monitor connected to device and now it
does not complain anything. But still the inbuilt touchscreen is black.
I will add logs for both ways booting. Is it okay to boot in recovery
mode and then run startx to create the log? If I try to boot without
i915.modeset=0
** Attachment added: xorg.log.0
http://launchpadlibrarian.net/33419296/xorg.log.0
--
[i945GM] No screen(s) found after updgrade to karmic alpha 5
https://bugs.launchpad.net/bugs/429369
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: lspci -vvnn
http://launchpadlibrarian.net/33419404/lspci%20-vvnn
--
[i945GM] No screen(s) found after updgrade to karmic alpha 5
https://bugs.launchpad.net/bugs/429369
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Here is the logs when rebooted in recovery mode and tried to start x and
without i915.modeset=0 option. What I noticed that when I have secondary
monitor connected xorg.0.log says there is two vga connectors and when I
try without the secondary monitor then there is vga and TV?? I don`t
have
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/33420124/Xorg.0.log
--
[i945GM] No screen(s) found after updgrade to karmic alpha 5
https://bugs.launchpad.net/bugs/429369
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: lspci-vvnn
http://launchpadlibrarian.net/33420026/lspci-vvnn
--
[i945GM] No screen(s) found after updgrade to karmic alpha 5
https://bugs.launchpad.net/bugs/429369
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hmm.. I just booted with second monitor connected to device and now it
does not complain anything. But still the inbuilt touchscreen is black.
That is what I would expect. When the external monitor is not connected,
the driver does not see any connected monitors and therefore exits (with
No
Tried to connect from Windows Mobile side of Shift with pocket putty to
Ubuntu side and it works when booted with i915.modeset=0 option but when
without it, ssh-connection cannot be created as Ubuntu is in some kind
of endless loop. Maybe it responses too slowly or something but nothing
really
** Attachment added: Xorg.0.log.12
http://launchpadlibrarian.net/33425191/Xorg.0.log.12
--
[i945GM] No screen(s) found after updgrade to karmic alpha 5
https://bugs.launchpad.net/bugs/429369
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: lspci-vvnn.12
http://launchpadlibrarian.net/33425186/lspci-vvnn.12
--
[i945GM] No screen(s) found after updgrade to karmic alpha 5
https://bugs.launchpad.net/bugs/429369
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Ok, got it work with usb-ethernet adapter. Here is those logs..
** Attachment added: dmesg.12
http://launchpadlibrarian.net/33425176/dmesg.12
--
[i945GM] No screen(s) found after updgrade to karmic alpha 5
https://bugs.launchpad.net/bugs/429369
You received this bug notification because you
With the latest updates from xorg-edgers or somewhere else the device
seems to detect the monitor in someway, as it is creating some graphics
to screen. There is just yellow vertical lines blinking at the top of
the screen if I try to boot without i915.modeset=0 option. I don`t know
if this helps
** Tags added: edid
--
[i945GM] No screen(s) found after updgrade to karmic alpha 5
https://bugs.launchpad.net/bugs/429369
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b...@lists.ubuntu.com
The UMS log shows that the driver is not able to get EDID information in that
case either.
I think this is another example of KMS monitor detection not working very well
when the monitor doesn't provide EDID information. See
On a Karmic installation, you can add the option to
GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub (after quiet and
splash). If your system is upgraded from Jaunty, it still uses an older
Grub version and you need to edit /boot/grub/menu.lst.
Note that this is a workaround and not a fix, and
here is xorg.0.log when booted with i915.modeset=0.
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/32141110/Xorg.0.log
--
[i945GM] No screen(s) found after updgrade to karmic alpha 5
https://bugs.launchpad.net/bugs/429369
You received this bug notification because you are a
Last thing that is showing on screen when trying to boot with KMS is:
[drm:intelfb_restore]*ERROR* Failed to restore crtc configration: -22.
This text is blinking in endless loop and it can not be stopped?
--
[i945GM] No screen(s) found after updgrade to karmic alpha 5
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New = Triaged
--
[i945GM] No screen(s) found after updgrade to karmic alpha 5
https://bugs.launchpad.net/bugs/429369
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Summary changed:
- No screen(s) found after updgrade to karmic alpha 5
+ [i945GM] No screen(s) found after updgrade to karmic alpha 5
** Tags added: 945gm karmic no-screens regression-potential
** Changed in: xserver-xorg-video-intel (Ubuntu)
Importance: Undecided = High
--
[i945GM] No
When I added i915.modeset=0 it returns in boot Unknown option
i915.modeset=0 but still it boots and now with intel graphics! How do I
fix it to allways include that option in boot options?
--
[i945GM] No screen(s) found after updgrade to karmic alpha 5
https://bugs.launchpad.net/bugs/429369
You
27 matches
Mail list logo
