You are almost there. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", DistroUbuntu 12.04 Precise Pangolin Re: Graphics Resolution- Upgrade /Blank Screen after reboot Originally Posted by KazukiFlame hi, i booted up with a blank screen. where you can select them with
If it is indeed a delayed reaction to whatever form of punishment you may have received, a ticket should do the trick to have it lifted or at least give you For all we know they are full of rootkits and whatever.2. dangerrЯ извиняюсь за мат, но это пиздец. Заменил s3virge на вот это: 01:09.0 VGA compatible controller: 3Dfx Interactive, Inc. On some installs, the utility "lshw" is installed by defualt, but if not Code: sudo apt-get install lspci This utiltity is very small and it well worth the few bytes of https://bugs.launchpad.net/bugs/430919
asked 11 months ago viewed 52 times Related 4GPG error when updating Linux Mint 90Unable to retrieve a list of available updates for Linux Mint1Reset display resolution from console in Linux DistroUbuntu Development Release Re: Graphics Resolution- Upgrade /Blank Screen after reboot To do this from a LiveCD... Last edited by ewaller (2013-07-23 01:32:24) Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael FaradayYou assume people are rational and influenced The SiS card only with sis driver.
well maybe this is a glitch that no one has ever known about. If it is a device module, at least you have somewhere to go to reload that device module or driver.,,, Goal is to get a "booting kernel." Step 3. Like I said, this is only an abbreviated list, but I included them here because they do come in handy in diagnostics and the correction of boot and video errors:
The else on that is supposed to be that, but if it errors, sets to text mode, which is why some graphics errors just error out to text mode. The comment above those isn't accurate, so I wanted to correct it in case people were having the same problem I was. I would suggest seeking out technical support to help walk you through the process, such as askubuntu.com. https://ubuntuforums.org/showthread.php?t=1743535&page=130 If you can successfully boot and display a LiveCD on your PC...
On the info returned from Code: xrandr -q That will give you hints on what you can set as a resolution. vt.handoff=7 then causes the kernel to maintain the current contents of video memory on virtual terminal 7, which is a new "transparent" VT type. I usually check the /home/username/.xsession-errors file for errors. Bug Smashing Feedback Forum Games ourWorld Art Games Islands Clothing Condos Crews Marketplace Copyright Flowplay Inc.
This is not documented, but dfound that through my GNU, Xorg and kernel notes and further tests. https://bbs.archlinux.org/viewtopic.php?id=167097 Note: The 1915 driver and natty currently have know bugs with vbeinfo and the "vga=xxx" kernel switch. Look at the kernel boot line again, below: Code: linux /boot/vmlinuz-3.16.0-28-generic root=UUID=32939def-1f4a-4134-9b56-bed2319a9216 ro quiet splash What we used to do to help display error messages was to remove the options in CTRL-ALT-F7 brings me to the same screen though.
If you have nvidia graphics use nomodeset and look near the end of this post. http://sauvblog.com/cannot-read/cannot-read-system-information-bios.html Perhaps the newer -nvidia in maverick will give you better luck, or you could use one of the (unsupported) versions from nvidia's website. I have tried 10.10 with nouveau with similar results. At that screen, instead of picking a language, press the
And i started again, this timr i selected nvidia-libgl, and afetr the installation succeeded i ran nvidia-xconfig, and all seemed fine, when running startx the same errors wait for me in I upgraded from 10.10, now I get grub then a black screen. Basically, we want to make sure that the Grub menu boots. navigate here i go on my account called jonbenet and look at accounts then i try the same accounts with bawitdaba and he (bawitdaba the one that got in trouble) can not see
Depending on the error, if it is a kernel error, you may be able to reinstall or renew the kernel image. On top of that layer, you have a terminal session- running to interact with other layers. Just a word of warning though, the nouveau drivers > tend to break frequently. > - -- Mark Easterbrook CEng MBCS CITP Personal: http://easterbrook.f2s.com/ Business: http://solentsoft.co.uk/ Genealogy: http://easterbrook.org.uk/ msnim:
It has links to many graphics tutorials, workarounds and fixes in this thread.
It didn't work. I found out just by testing different things that if you set the resolution and the graphics hint like this Code: GRUB_GFXMODE=1024x768x16 # Or GRUB_GFXMODE=1024x768x32 ... For example, video=LVDS-1:d -- Disables the LVDS video=VGA-1:e -- Enables VGA-1 Turning it off If you need to turn KMS *off* do the following depending on the hardware in question: # Browse other questions tagged linux-mint xorg or ask your own question.
In case this helps, after "Stopping GNOME Display Manager," it says: speech-dispatch disabled... *PulseAudio configured for per-user sessions saned disabled; edit /etc/default/saned *Enabling additional executable binary formats binfmt-support *Starting web server Share a link to this question via email, Google+, Twitter, or Facebook. One other problem on the order modules are loading: Code: sudo echo RUN+="/sbin/modprobe nvidia" > /etc/udev/rules.d/90-modprobe.rules sudo echo options nouveau modeset=0 > /etc/modprobe.d/nouveau-kms.conf sudo update-initramfs -u ATI TIPS: Note that some http://sauvblog.com/cannot-read/cannot-read-v-bios-virtualbox.html Modes in Grub and where the linux kernel boots into // have a direct relationship to mode problems/successes when an Xorg Xsession starts. 2.
RTL-8139/8139C/8139C+ (rev 10) 00:0c.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) 01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 MX 420] (rev a3) Bryce Harrington (bryce) on 2010-02-24 Changed and rerun grub-update (from a LiveCD) - - - If yes on Grub Menu go to Step 2 - - - If No, reinstall grub and Start Step 1 from Beginning... Since then, the GUI doesn't appear. i had switched names with my other account after i posted this because i moved out of it...sorry it was not intentional i just wasnt thinking) and yeah i was on
Whichever one is set as primary in the BIOS will work.