Launchpad has imported 5 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=889687.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2012-12-22T15:26:59+00:00 Milan wrote: Created attachment 667712 /var/log obtained in failsafe graphics mode with F18 beta LiveCD LiveCD for both F18 beta and nightly build from 2012-12-17 fail to build on my machine with an Ironlake Mobile GPU (see below). If I choose the normal boot mode, Plymouth is not visible: the screen goes grey, then blanks and never returns. If I choose failsafe graphics mode (xdriver=vesa nomodeset), I am able to see the boot process, but X fails to start: on F18 beta, I am able to go to a console; with the nightly build, the machine hangs when X starts, and the fan does not stop (probably CPU use). I am attaching the logs I could get with F18 beta in failsafe graphics mode. Please ask for any information/debugging you may need. The card model is: 00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) The most interesting part of Xorg.0.log is: [ 13.212] (II) VESA: driver for VESA chipsets: vesa [ 13.212] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 13.212] (II) FBDEV: driver for framebuffer: fbdev [ 13.212] (++) using VT number 1 [ 13.214] (II) intel(0): using device path '/dev/dri/card0' [ 13.218] (WW) Falling back to old probe method for vesa [ 13.218] (WW) Falling back to old probe method for modesetting [ 13.218] (WW) Falling back to old probe method for fbdev [ 13.218] (II) Loading sub module "fbdevhw" [ 13.218] (II) LoadModule: "fbdevhw" [ 13.218] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so [ 13.229] (II) Module fbdevhw: vendor="X.Org Foundation" [ 13.229] compiled for 1.13.0, module version = 0.0.2 [ 13.229] ABI class: X.Org Video Driver, version 13.0 [ 13.229] (EE) open /dev/fb0: No such file or directory [ 13.235] (II) intel(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 24/32 [ 13.235] (==) intel(0): Depth 24, (--) framebuffer bpp 32 [ 13.235] (==) intel(0): RGB weight 888 [ 13.235] (==) intel(0): Default visual is TrueColor [ 13.236] (--) intel(0): Integrated Graphics Chipset: Intel(R) Arrandale [ 13.236] (**) intel(0): Relaxed fencing enabled [ 13.236] (**) intel(0): Wait on SwapBuffers? enabled [ 13.236] (**) intel(0): Triple buffering? enabled [ 13.236] (**) intel(0): Framebuffer tiled [ 13.236] (**) intel(0): Pixmaps tiled [ 13.236] (**) intel(0): 3D buffers tiled [ 13.236] (**) intel(0): SwapBuffers wait enabled [ 13.236] (==) intel(0): video overlay key set to 0x101fe [ 13.236] (EE) intel(0): failed to get resources: Invalid argument [ 13.236] (II) UnloadModule: "intel" [ 13.236] (EE) Screen(s) found, but none have a usable configuration. [ 13.236] Fatal server error: [ 13.236] no screens found Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1088271/comments/3 ------------------------------------------------------------------------ On 2012-12-22T15:31:23+00:00 Milan wrote: FWIW, a report against Ubuntu 12.04 has the very same X log, and says it was working with Linux kernel 3.5.0-17, but fails with 3.5.0-18. Of course F18 has much more recent kernels. https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1088271 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1088271/comments/4 ------------------------------------------------------------------------ On 2012-12-22T16:08:28+00:00 Milan wrote: OK, acpi_backlight=vendor fixes the problem in normal boot mode. This is bug 771110 striking again. Still, I think there's a separate problem with failsafe graphics mode. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1088271/comments/5 ------------------------------------------------------------------------ On 2013-12-21T10:02:59+00:00 Fedora wrote: This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1088271/comments/20 ------------------------------------------------------------------------ On 2014-02-05T14:07:49+00:00 Fedora wrote: Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1088271/comments/21 ** Changed in: fedora Status: Unknown => Won't Fix ** Changed in: fedora Importance: Unknown => Undecided -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1088271 Title: X startup fails with "failed to get resources" error after update to 3.5.0-18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1088271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
