Fglrx AMD Driver Troubleshooting On Ubuntu-gnome 15.04

We are using sabresd iMx6Q board.The boot loader splash screen is showing for a few seconds and before the kernel splash screen loads, the lcd screen is black for 18 sec.Kindly help us to know why such a delay between the two screens.Any help would be appreciated.

Hey guys. So I just went out and bought a Sager 8268-s (clevo p150sm-a) With an i7 4910mq and a Nvidia 980m gt. As I am a computer tech by trade, every time i see Windows i get horrible PTSD so i decided to try Linux instead. After many hours of trying to get a dual boot working finally got Linux Mint 17 Cinnamon installed on my computer, but when I went to install the Nvidia driver it landed me in fallback mode which I could not escape. So then I tried Ubuntu 14.04 LTS thinking maybe Mint was incompatible with the driver and the same thing happened.

So here is my method:

(sorry i don't know how to make a code box :/ )

First I log in to get root access:

$ su

Then I Update the xorg:

$ sudo apt-add-repository ppa:xorg-edgers/ppa

Then update my system:

$ sudo apt-get update && sudo apt-get dist-upgrade

Then i go into Virtual terminal (Ctrl+Alt+F1) and disable the display manager:

$ sudo service mdm (or lightdm for Ubuntu) stop

Then i install the drivers which i have done multiple ways:

$ sudo apt-get install nvidia-current nvidia-settings

or

$ sudo apt-get install nvidia-343 nvidia-settings

or by downloading the driver from Nvidia (first designating the file as executable)

$ sudo sh nvidia.run && sudo apt-get install nvidia-settings

Then after install, I create the config file:

$ sudo nvidia-xconfig

Then I reboot. After I get the low res mode in Ubuntu or fallback mode in Mint and Driver manager doesn't detect any proprietary drivers and I have to reinstall to get the OS working again. Any suggestions would be greatly appreciated.

Hi all,
The title screams it all...I installed an nVidia driver on a box and now, at boot the screen gets deactivated . Usually, I'd Ctrl-Alt-F1 into a CLI but since the screen is disabled...hehe. So, I boot in with a live CD (Knoppix or something) and usually I get to the nub of things, text only but still...
So, where do I tickle the system to get it to NOT load the (wrong) driver?
Thanks
PS - I could just reinstall, it is a fresh system, but, I'd miss out on a great opportunity to learn something new

These instructions originate from https://www.linkedin.com/pulse/20140...nvidia-drivers, but I modified them slightly for my desktop environment (64-bit HP Envy Phoenix 810-135qe w/Intel i7-4770 and HP ZR2440w monitor, nVidia GeForce GTX645, Red Hat Enterprise Linux 7.1 w/Gnome3).

The following procedures replace the nouveau drivers with kmod-nvidia drivers from ElRepo.

Install the repository ElRepo from: http://elrepo.org/tiki/tiki-index.php

Install the package nvidia-detect from within Applications>SystemTools>Software

From within the terminal, enter the command nvidia-detect.
Example:
[anthony@hp810135qe ~]$ nvidia-detect
Output is...
Probing for supported NVIDIA devices...
[10de:11c4] NVIDIA Corporation GK106 [GeForce GTX 645 OEM]
This device requires the current 346.59 NVIDIA driver kmod-nvidia

For my system the following software packages will apply (yours maybe slightly different, the key is to note the ###.## version identified for your system using nvidia-detect as explained above): kmod-nvidia-346.59-1.el7.elrepo (64-bit), nvidia-x11-drv-32bit-346.59-1.el7.elrepo (64-bit), nvidia-x11-drv-346.59-1.el7.elrepo (64-bit)

Now do the following steps in the sequence indicated:

1. Disable X Windows

a) open a terminal and "su" or "sudo -i"

b) ln -fs /lib/systemd/system/multi-user.target /etc/systemd/system/default.target

Note: Another way to disable X Windows is to do the following from within the Terminal # systemctl set-default multi-user.target

To later change back to booting into graphical mode, substitute 'graphical.target' for 'multi-user.target' in the above commands.

c) reboot

2. Remove Nouveau

a) rpm -e xorg-x11-drivers xorg-x11-drv-nouveau

Note: Another way to remove Nouveau is to do the following from within the Terminal

$ yum remove xorg-x11-drivers xorg-x11-drv-nouveau xorg-x11-glamor

See http://elrepo.org/tiki/kmod-nvidia which discusses that glamor still causes a conflict with nVidia in RHEL 7

3. Blacklist Nouveau

a) edit /etc/modprobe.d/blacklist.conf and add line:

blacklist nouveau

Note: A way to edit this file is by doing the following:

# vi /etc/modprobe.d/blacklist.conf
(use INSERT key to make changes in vi; add the line

blacklist nouveau

Hit Esc key to escape INSERT mode, then hit SHIFT Z Z to save and exit with the changes. Hitting :q ENTER leaves vi without saving changes.

b) edit /etc/default/grub and append to GRUB_CMDLINE_LINUX:

rd.driver.blacklist=nouveau

Note: A way to edit this file is by doing the following:

# vi /etc/default/grub and append to GRUB_CMDLINE_LINUX:
(use INSERT key to make changes in vi; add the line

rd.driver.blacklist=nouveau

Hit Esc key to escape INSERT mode, then hit SHIFT Z Z to save and exit with the changes. Hitting :q ENTER leaves vi without saving changes.

IMPORTANT NOTE IF YOU HAVE AN ENCRYPTED BOOTUP DRIVE -

If you have an encrypted root drive, remove "rhgb" from GRUB_CMDLINE_LINUX. This will allow you to interact with the encryption passphrase prompt, since Plymouth doesn't seem to run without a framebuffer friendly video driver loaded. IF YOU DON'T THIS, WHEN YOU BOOTUP YOU WILL GET STUCK AT A BLINKING CURSOR AND BLACKSCREEN THAT HAS THE FOLLOWING ERROR MESSAGES:


[5.757276] scsi 7:0:0:0: alua: not attached
[5.759625] sd 7:0:0:0: [sdg] no caching made page found
[5.759668] sd 7:0:0:0: [sdg] assuming drive cache: write through

WHEN THIS HAPPENS IT MEANS PLYMOUTH IS NOT ABLE TO SHOW YOU THE PROMPT FOR ENTERING THE PASSPHRASE FOR THE ENCRYPTED DRIVES. WITHOUT THE PROMPT THE SYSTEM CAN'T ACCEPT THE PASSPHRASE AND YOU ARE STUCK. IF THIS HAPPENS TO YOU, YOU CAN DO CTRL-ALT-DELETE TO REBOOT - THIS ALLOWS YOU TO HIT 'e' AT THE KERNEL LINE IN GRUB TERMINAL TO EDIT (MOST LIKELY THE TOP KERNEL) AND THEN REMOVE 'rhgb' (which stands for Red Hat Graphical Bootsplashcreen or something like that). WHEN DONE HIT THE KEYS 'CTRL X' TO REBOOT - YOU'LL THEN SEE TEXT MESSAGES SCROLLING AND GET AN OPPORTUNITY TO ENTER THE PASSPHRASE. ENTER THE PASSPHRASE AND YOU SHOULD BE GOOD TO GO.

4. Reconfigure the grub.cfg files

Two options for booting nowadays are BIOS and EFI

-If you chose BIOS boot run this command:
# grub2-mkconfig -o /boot/grub2/grub.cfg
Note: I also have this one being auto-updated-configured in my system (?why? It's EFI).

-If EFI boot on CentOS:
# grub2-mkconfig -o /boot/efi/EFI/centos/grub.cfg

-If EFI boot on RHEL:
# grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg
Note: Mine is an EFI system. But I did both this and the BIOS grub.cfg above since it too is being updated by RHEL updates concurrently with the EFI grub.cfg

5. Reboot and Install NVidia Driver - I use ElRepo's kmod-nvidia for this step.

Steps by me to install ElRepo's kmod-nvidia (You should still be in Text mode at this time):

If in multi-user.target mode (text, runlevel 3), then do the following
$ su -
enter root password
# yum install kmod-nvidia - version from above
# yum install nvidia-x11-drv-32bit - version from above (this is for 32bit compatibility)
# yum install nvidia-x11-drv - version from above (this is for Open GL X11 display driver and to be done if kmod didn't already include doing it with the kmod-nvidia installation above)
# exit
$

If still in graphics.target mode (you shouldn't be but if you are) (GUI, runlevel 5),
Use Applications > Software > kmod-nvidia - version from above
Install kmod-nvidia - version from above
Install nvidia-x11-drv-32bit - version from above (this is for 32bit compatibility)
Install nvidia-x11-drv - version from above (this is for Open GL X11 display driver)

6. At this point rebuild initramfs. This recreates initrd w/o nouveau. The existing initrd still has the embedded nouveau drivers if this step is not performed) :

Back up the current initramfs keeping nouveau
# mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r)-nouveau.img
Build the new one without nouveau
# dracut /boot/initramfs-$(uname -r).img $(uname -r)

7. Re-Enable X Windows

# systemctl set-default graphical.target

8. Reboot

If you have an encrypted bootup drive, when you bootup you may notice that Plymouth doesn't look so good with its text in a lower resolution and you'll see lines of text scrolling until you get to a stopped cursor waiting for you to enter the passphrase to unencrypt your drive. Maybe eventually there'll be a solution for this to keep things moving with a graphical bootsplash all throughout. Until then, this is a minor inconvenience for me.

Hello

I have installed a CentOS 6.4 on VmWare.

Now, after several days of using it, it suddenly does not boots. There is a problem with its initialization, here is the error:

Kernel Panic : Unalble to init. Try passing init= option to the kernel.
Pid 1 : Swapper not tainted.

I have used CentOS.iso to rescue it, but it still does not solve it.

My grub.conf contains:

PHP Code:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,0)
#          kernel /vmlinuz-version ro root=/dev/sda2
#          initrd /initrd-[generic-]version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.32-358.el6.x86_64)
    root (hd0,0)
    kernel /vmlinuz-2.6.32-358.el6.x86_64 ro root=UUID=6082bcf5-00ba-4bf8-86ea-9821d774cb6f rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto  KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet
 initrd /initramfs-2.6.32-358.el6.x86_64.img 



How should I solve it then? Thanks in advance

I want to change the menu on a Suse 12 Enterprise system.
I edit the /etc/default zip12grub.conf file execure grug2-mkconfig. Then reboot the system and no changes occur. The zip12grub.conf seems like the correct file to update so I am at a loss as to what the correct process would be.

cat zipl2grub.conf
## This is the template for '@zipldir@/config' and is subject to
## rpm's %config file handling in case of grub2-s390x-emu package update.

[defaultboot]
defaultmenu = menu

[grub2]
target = @zipldir@
ramdisk = @zipldir@/initrd,0x2000000
image = @zipldir@/image
parameters = "root=@GRUB_DEVICE@ @GRUB_EMU_CONMODE@ @GRUB_CMDLINE_LINUX@ @GRUB_CMDLINE_LINUX_DEFAULT@ initgrub quiet splash=silent "

[skip-grub2]
target = @zipldir@
ramdisk = @zipldir@/initrd,0x2000000
image = @zipldir@/image
parameters = "root=@GRUB_DEVICE@ @GRUB_CONMODE@ @GRUB_CMDLINE_LINUX@ @GRUB_CMDLINE_LINUX_DEFAULT@ "

[test-grub2]
target = @zipldir@
ramdisk = @zipldir@/initrd,0x2000000
image = @zipldir@/image
parameters = "root=@GRUB_DEVICE@ @GRUB_CONMODE@ @GRUB_CMDLINE_LINUX@ @GRUB_CMDLINE_LINUX_DEFAULT@ "

:menu
target = @zipldir@
timeout = 16
default = 1
prompt = 1
1 = grub2
2 = skip-grub2
3 = test menu grub2

grub2-mkconfig -o /boot/grub2/grub.cfg

Generating grub configuration file ...
Found linux image: /boot/image-3.12.39-47-default
Found initrd image: /boot/initrd-3.12.39-47-default
Found linux image: /boot/image-3.12.28-4-default
Found initrd image: /boot/initrd-3.12.28-4-default
done

reboot

Storage cleared - system reset.
zIPL v1.24.1-38.17 interactive boot menu

0. default (grub2)

1. grub2
2. skip-grub2

Note: VM users please use '#cp vi vmsg <input> <kernel-parameters>'

Please choose (default will boot in 16 seconds):
Booting default (grub2)

Please Help,

I have a Windows 7 and Fedora 20 dual boot pc .
Today i deleted the fedora partition from windows disk management and then restarted my pc.
Now i am stuck in the 'grub rescue > ' screen ...... It is showing 'no such partition ' , after searching through the internet i tried these commands......

grub rescue > set boot=(hd0,msdos6)

grub rescue> set prefix=(hd0,msdos6)/*boot/grub

grub rescue> insmod normal (after this line ,i am getting the error , grub rescue > unknown filesystem)

grub rescue> normal

Don't know what to do ,but i want to get back to the windows os first ,also i don't have the windows or fedora live cd . My Windows recovery is stored in my pc hard drive....... plzz help so that i can resolve this issue

Hello all,

I was working through LFS 7.7 Chp 2.4 and mounted a wrong partition to /mnt/lfs.
I did the following commands while trying to mount the correct LFS partitions:
mount -v -t ext4 /dev/sda8 /mnt/lfs
mount -v -t ext4 /dev/sda9 /mnt/lfs/home
but I was supposed to mount sda11 and sda 12.

Now the system won't boot past the splash screen. I tried booting into a live usb and typed in the following commands
mount -v -t ext4 /dev/sda8 /
mount -v -t ext4 /dev/sda9 /home
but the system still won't boot past the splash screen.
Both gparted and the partition manager for the installer don't show a mount point.

How do I create a mount point from USB or is there another problem/solution?

Thanks

I clean installed Antergos 64bit (GNOME 3) on my iMac, and now need to boot the OS X DVD that came with the computer to format and restore. The ultimate goal is to keep this machine for dual-booting (which I can take care of) since there are simply things I need from both operating systems. If only Antergos or GRUB would boot from the DVD to kick-off the process.


What have you done so far?

It made sense to install rEFInd on this machine, since that was the program that helped OS X boot the Antergos image from my USB drive in the first place.

I followed the steps laid out in the Arch Wiki. First, by using the refind-install command Then used the refind-install --usedefault /dev/sda1 command to "also install rEFInd to the default/fallback boot path".
I shutdown, and booted the Mac up in hopes to catch rEFInd's splash screen, but to no avail. Only the Antergos/GRUB screen, and then into Antergos as usual.
(This began a hopeless cycle of re-installing, and rebooting which lasted quite some time.)

Afterwards, I tried manually installing rEFInd using the following commands from the Arch Wiki:
Quote:
cp /usr/share/refind/refind_x64.efi $esp/EFI/refind/
efibootmgr -c -d /dev/sda -p 1 -l /EFI/refind/refind_x64.efi -L "rEFInd Boot Manager"
Also, I installed the mactel-boot utility from the AUR.

And according to the efibootmgr utility, rEFInd was now first in the boot order:

Quote:
BootCurrent: 0002
BootOrder: 0004,0003,0002,0080,0001,0000
Boot0000* ubuntu
Boot0001* rEFInd Boot Manager
Boot0002* antergos_grub
Boot0003* rEFInd Boot Manager
Boot0004* rEFInd Boot Manager
Boot0080* Mac OS X
Boot0081* Recovery OS
BootFFFF*
After shutdown/power-on, the machine displayed alot of white-colored "clearing node" text, before tragically booting once again into Antergos/GRUB.

I've also read How-to Geek's guide on re-installing OS X on Mac, yet the tutorial never mentions how to restore it from Linux.


Conclusion:

What piece of this puzzle am I missing? Would creating a LiveUSB of OS X be an easier route than this DVD? Is there a GRUB command I'm not aware of that can change the boot order?

I'm almost certain rEFInd is not the only way Linux would be able to boot this OS X DVD, it's just the only way I've known how so far.

I can clearly see the Mac OS X boot option in efibootmgr as Boot0080*, so at least it's being recognized. When Antergos boots to the desktop, the OS X DVD is displayed as "WindowsSupport" if that helps.
I'm out of my element and am at an impasse, your help will be appreciated.

PLEASE & THANK YOU

Hello.

I am a newcomer to Linux, coming from Windows, desktop PC user. I already have a few months' experience with Ubuntu and Mint. I can handle some basic terminal commands, but I prefer the GUI whenever possible.

I'm not an IT specialist, far from it. Just a normal average computer user who can read a few things if they are understandable enough, and wants a decent operating system. So please speak to me in simple human terms, I can handle high tech jargon only so much. Thanks.

I have 2 main questions:

1. I've encountered problems when booting from LiveCD (written to USB) with both Mint and Lubuntu. The boot menu appeared but when I pressed any of the “try live” or “install” options, the screen froze with garbled checkerd pixels. Web searching for solutions, I found the thing with accessing special boot options and adding kernel parameters like 'nomodeset' and 'noaccel' and doing that I could proceed with installation. Then, after installing proprietary drivers, everything was fine.

This is not the first time this happened. As far as I understand this is related to the nouveau driver.

Does this happen only with some distros, like, for example, Ubuntu and its derivatives, or is it a larger problem from the main Linux kernel? From what I've read on some forums, such problems happened with other graphic cards as well, and it seems to be an old problem as old as 2011 if not older.

Why nothing could have been done to fix these issues so far? Couldn't all distros use some option from boot menu to either go with simple safe vesa graphics mode or a text based helpful install that might guide the user afterwards in downloading the proprietary drivers if s/he desires?...

And what is the main cause of the problem? Nvidia not doing FOSS drivers? Nouveau not being flexible enough? Linux kernel not keeping up? Particular distros that don't care about adding an extra boot option? A combination of all these? What is to be done? Would switching to other distro help in this regard? how would I know which distros use nouveau and which don't?

2. I'd like to look into other distros as well. What I need is stability, meaning as bug free as possible, as few apps hanging or crashing as possible, while still being user friendly. But no rolling realeases, please. I want to update the system without fear that I won't boot into desktop – again!

I need distros that come with multimedia codecs, Flash and stuff out of the box and also an easy option to install the proprietary video card graphics driver. I am all for FOSS, but for now I'm also being realistic, and unfortunately have to go with proprietary drivers.

What recommendations do you have?

Thank you.