Launchpad.net

Pages matching "xforcevesa" in Launchpad

120 of 151 pages matching "xforcevesa"
  • 9 Sep 2006 ... Binary package hint: casper If I choose "Safe graphics mode" in the boot menu I see that "xforcevesa" is correctly added to the kernel boot parameters, but that hint is ignored by the X configuration scripts of the LiveCD. That is, in my desktop pc, X always uses nv, even if requested to use vesa by ...
  • 4 Nov 2010 ... Using Ubuntu 10.10 I am unable to run Live mode. If I go through the installation process (via boot option screen) I am left with an installation which is unable to start the X server. These problems have started since 9.10 (10.04 had a similar problem, though was that was resolved somehow by 10.04.1) and ...
  • 18 Oct 2008 ... Binary package hint: xorg Putting 'xforcevesa' on the livecd cmdline should force the driver as vesa, but that doesn't work because of changes to the xserver-xorg. postinst. DRIVERS_LIST is now empty on !sparc, so there are no debconf choices to choose, and setting the key to vesa doesn't work.
  • 5 Nov 2016 ... nomodeset xforcevesa. Resolution without xforcevesa: 800x600. Resolution with xforcevesa: 1600x900 – the optimal resolution. ProblemType: Bug DistroRelease : Ubuntu 16.04. Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21. Uname: Linux 4.4.0-45-generic ...
  • 24 Dec 2010 ... A couple of people, including me, only get a black screen when trying to boot of the new lmde 32 bit iso. THis problem has occured on nvidia, ati and intel cards. With xforcevesa I was able to boot into a console and grab a xorg.0.log. Can't make much sense of it myself but "(II) Primary Device is: PCI ...
  • 1 Apr 2010 ... CTRL+ALT+DEL does not reboot. - Added nomodeset, system seems to finish upstart's tasks, ureadahead outputs a message about exiting with status 4, but no VTY or X. CTRL+ALT+DEL does not reboot. WORKAROUND: Added xforcevesa (and nomodeset). I now get both X and VTYs. Everything works ...
  • 29 Nov 2014 ... I write down $ nomodeset xforcevesa and press F10 to boot. Now I am able to install Eos, I select my partition and make it ext4. At the and of the installation it ask me to reboot , I press on reboot and the first time I get just a black screen ,so I reboot again and get the Grub with Eos and Eos recovery mode.
  • 14 Jul 2010 ... MachineType: Sony Corporation VPCY2190X Package: xserver-xorg-video-intel 2:2.11.0-1ubuntu2 PackageArchitecture: amd64 ProcCmdLine: BOOT_IMAGE=/ boot/vmlinuz-2.6.35-6-generic root=UUID=34d429a1-414a-4d00-ae97- 31d2243fe69f ro nomodeset xforcevesa ProcEnviron: LANG=en_US.
  • 30 Sep 2010 ... Binary package hint: xserver-xorg-video-openchrome I was trying out Lucid on my fiancees machine (a Semp Toshiba Info IS 1462) but found that I could only get X to start using the xforcevesa boot option. Leading to a very poor first impression of Ubuntu since the user is greeted with a black screen and a ...
  • 26 Jun 2014 ... Haven't tried this with 14.04, but I could boot a 14.10 Live system by booting with the options "xforcevesa" and "nomodeset". Will try to install the latest nvidia drivers and see what happens.
  • 26 Sep 2006 ... Acer Aspire 5024 WLMI Graphic card : ATI Mobility Radeon X700 PCI Express 128 MB VRAM Got a black screen with a Ubuntu Edgy Knot 3. I got a black screen even though i choose xforcevesa (fail safe graphic) I can hear the gnome sound but no screen : BLACK ! A dpkg-reconfigure xserver-xorg, ...
  • 11 Oct 2010 ... I was running ubuntu 10.10 beta on amd + nvida drivers all was working. Upgrade desktop to athlon II x2 260 that has embedded ati hd4250 graphics. If I edit Grub ('e' from list) and add radeon.modeset=0 xforcevesa it sometimes loads. At other times if I change the xforcevesa to vga=771 it works (again ...
  • 28 Dec 2012 ... xforcevesa : Nothing i915.modeset=0 xforcevesa : Kicked to console by Xserver ( No Screens Found) acpi=off : Looks to boot normally, (best looking splash screen so far) but spews out "/init Line 7 /dev/sr0 no medium" over and over. ...I'm thinking this is because I have to use a LiveUSB and it's expecting a ...
  • 25 Dec 2013 ... SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=8f2a5f23-22ac-4536 -b436-60c8f6cbe56b ro xforcevesa quiet splash ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
  • 10 Apr 2010 ... Reboot using params "nomodeset xforcevesa" Install th proprietary NVIDIA driver . Switch to console and copy attached xorg.conf. Reboot and configure your display by using NVIDIA X Server Settings (Administration). So please implement xforcevesa to the options (F6) of the live-cd. Best regards. ZB ...
  • 28 Oct 2010 ... Can you submit a bug report after a freeze in recovery mode? apport-bug -p linux . On Thu, Oct 28, 2010 at 3:27 PM, Roman Groger <xalbert76@xxxxxxxxx <mailto :xalbert76@xxxxxxxxx>> wrote: Thanks Don. Unfortunately, this does not seem to work here. When I start X (with the xforcevesa option in grub), ...
  • 3 Sep 2009 ... 6) manual change allows to set keyboard (Applications/Settings/Keyboard) and setxkbmap it works too. For my use, the "persistent" option is not indispensable; A boot with the right keyboard would be preferable for multiple installs;. 7) option xforcevesa doesn't work (no boot) option vesa has no effect. Thx.
  • 27 Jun 2017 ... I achieved this by using a combination of disper and the system monitor management. However when I booted up today I got a blinking cursor. I already tried these things and others: setting grub gfxmode nomodeset / radeon.modeset =0 xforcevesa xrandr -auto (says no displays found when used after ...
  • 30 Mar 2009 ... ProcCmdLine: root=UUID=7c894feb-153e-4032-a8ee-0af7b62a3b82 ro xforcevesa quiet splash ProcCmdline: /usr/bin/python /usr/share/apport/ apportcheckresume ProcEnviron: PATH=(custom, no user) ProcVersionSignature : Ubuntu 2.6.28-11.38-generic SourcePackage: linux. Tags: resume suspend
  • 16 Nov 2013 ... Xorg log vesa set a wrong resolution. Edit (120.7 KiB, text/plain). I use the vesa drivers adding xforcevesa .. Set a wrong resolution "1280 * 768" like, detects openchrome "1280 * 800" to my screen the correct resolution is "1024 * 768" .
120 of 151 pages matching "xforcevesa"