Is this guide still valid for Fedora 17?![]()
Is this guide still valid for Fedora 17?![]()
Hi, I did all steps of the first post for F16. And when I try to boot with the new kernel, the system load always stuck. It stucks on that moment, when three stripes (blue, white-blue and white) is running to word "Fedora 16"=)))) I dont know how to explain that in another way)))
Code:abrt-addon-kerneloops-2.0.4.981-3.fc16.x86_64 akmod-nvidia-295.53-1.fc16.1.x86_64 kernel-3.1.0-7.fc16.x86_64 kernel-3.3.7-1.fc16.x86_64 kernel-devel-3.3.7-1.fc16.x86_64 kernel-headers-3.3.7-1.fc16.x86_64 kmod-nvidia-3.3.7-1.fc16.x86_64-295.53-1.fc16.1.x86_64 libreport-plugin-kerneloops-2.0.6-2.fc16.x86_64 nvidia-settings-1.0-17.fc16.x86_64 nvidia-xconfig-1.0-15.fc16.x86_64 xorg-x11-drv-nvidia-295.53-1.fc16.x86_64 xorg-x11-drv-nvidia-libs-295.53-1.fc16.i686 xorg-x11-drv-nvidia-libs-295.53-1.fc16.x86_64 3.1.0-7.fc16.x86_64 nouveau 580599 0 ttm 55029 1 nouveau drm_kms_helper 26490 1 nouveau drm 194532 3 nouveau,ttm,drm_kms_helper i2c_algo_bit 4958 1 nouveau i2c_core 25728 5 i2c_i801,nouveau,drm_kms_helper,drm,i2c_algo_bit mxm_wmi 1727 1 nouveau video 12388 1 nouveau Section "Device" Identifier "Videocard0" Driver "vesa" EndSection
Still the same. Here is the output:
Code:[root@localhost ungod]# dracut -f -v -H /boot/initramfs-3.3.7-1.fc16.x86_64.img 3.3.7-1.fc16.x86_64 I: *** Including module: dash *** I: *** Including module: i18n *** I: *** Including module: rpmversion *** I: *** Including module: plymouth *** I: *** Including module: kernel-modules *** I: *** Including module: resume *** I: *** Including module: rootfs-block *** I: *** Including module: terminfo *** I: *** Including module: udev-rules *** I: Skipping udev rule: 50-udev.rules I: Skipping udev rule: 95-late.rules I: *** Including module: biosdevname *** I: *** Including module: base *** I: *** Including module: fs-lib *** I: Skipping program jfs_fsck as it cannot be found and is flagged to be optional I: Skipping program reiserfsck as it cannot be found and is flagged to be optional I: *** Including module: shutdown *** I: Skipping program kexec as it cannot be found and is flagged to be optional I: *** Including modules done *** I: Wrote /boot/initramfs-3.3.7-1.fc16.x86_64.img: I: -rw-r--r--. 1 root root 6255354 May 29 20:31 /boot/initramfs-3.3.7-1.fc16.x86_64.img
Hi Thanugod,
Try hitting the "ESC" key while the system is loading. You can hit the "ESC" just as the system is starting the stripes and you will see the text mode of the load, showing all of the individual processes. By the way, you will see the last successful / failed transaction listed not any that is stuck. Hitting "ESC" will revert to the graphical display
Resolving the System Load in non fancy graphical mode:-
- Your error will occur with a more fancy screen display !!!
This is not the perfect answer, but by default the console is set to 640x480 unless you specify a vga mode. I have many tests in setting vga modes, and that another topic, try putting the definition of "vga=0x316" in the kernel line and rebuild the Grub config
- The GRUB2 loader will complain as that entry is now deprecated,
: Modify :-> /etc/default/grub
GRUB_CMDLINE_LINUX
Additional options:-
GRUB_GFXMODE=1280x800x32
GRUB_GFXPAYLOAD=keep
GRUB_GFXPAYLOAD_LINUX=1280x800x32
: Build :-> grub2-mkconfig -o /boot/grub2/grub.cfg
# FRAMEBUFFER RESOLUTION SETTINGS
# +-------------------------------------------------+
# | 640x480 800x600 1024x768 1280x1024
# ----+--------------------------------------------
# 256 | 0x301=769 0x303=771 0x305=773 0x307=775
# 32K | 0x310=784 0x313=787 0x316=790 0x319=793
# 64K | 0x311=785 0x314=788 0x317=791 0x31A=794
# 16M | 0x312=786 0x315=789 0x318=792 0x31B=795
# +-------------------------------------------------+
# for more details and different resolutions see
# https://wiki.archlinux.org/index.php...fer_Resolution
I pressed ESC during fedora loading and I didnot see any fail or error. For example, here is the last tree lines of STDOUT
This is the 2nd install of fedora. The 1st time was a few months later. There was the same problem with video driver. Fedora was loading in the same way. But when the "stripes" comed to 100%, loading process displayed the error. I dont remember exactly, but it was something like "Starting ... [FAILED]". And I dont remember how do I fix it.Code:Started LSB: Builds and install new kmods from akmod packages Starting SYSV: Late init script for live image... Started SYSV: Late init script for live image...
---------- Post added at 04:48 PM ---------- Previous post was at 04:10 PM ----------
YES! I have solved it! Maybe kmod drivers were installed with kernel update process. And so:
Code:# yum remove kmod-nvidia-3.3.7-1.fc16.x86_64-295.53-1.fc16.1.x86_64 # reboot # nvidia-xconfig # reboot
How can i change the resolution of the boot screen?
My resolution after the nvidia-driver installation is very low 800x600 or so.
Ivo
Set the GRUB_GFXPAYLOAD_LINUX option in /etc/default/grub to your desired resolution then run
# grub2-mkconfig -o /boot/grub2/grub.cfg
'GRUB_GFXPAYLOAD_LINUX’
Set to ‘text’ to force the Linux kernel to boot in normal text mode, ‘keep’ to preserve the graphics mode set using ‘GRUB_GFXMODE’, ‘widthxheight’[‘xdepth’] to set a particular graphics mode, or a sequence of these separated by commas or semicolons to try several modes in sequence.
Last edited by secipolla; 31st May 2012 at 01:34 PM.
Hi Secipolla,
I have added GRUB_GFXPAYLOAD_LINUX with my desired resolution, thank you. (I loose the egg)
---
You miss one letter in the grub path. :P
/boot/grub2/grub.cfg
Cheers![]()
hi !
i am facing problems with the graphics of one computer in my lab.. I am not sure about the driver type and the method used for installing the driver.. sorry.. the video card is nvidia quadro fx 540 and the OS is fedora 16.. The gnome starts smoothly and the graphical effects are looking good.. but when i try to start a video file in full screen it doesn't work... The player works perfect in small window sizes, but when i increase the window size or switches to full screen, there is no video, but i can hear the audio alone.. A similar problem is happening with a visualisation package, paraview also..
is there any solution for this problem?
Thanks in advance..Code:[toolpostr@entropy ~]$ rpm -qa *\nvidia\* *\kernel\*|sort;uname -r;lsmod |grep -e nvidia -e nouveau;cat /etc/X11/xorg.conf abrt-addon-kerneloops-2.0.7-2.fc16.i686 akmod-nvidia-295.53-1.fc16.1.i686 kernel-3.3.4-3.fc16.i686 kernel-3.3.5-2.fc16.i686 kernel-3.3.7-1.fc16.i686 kernel-devel-3.3.4-3.fc16.i686 kernel-devel-3.3.5-2.fc16.i686 kernel-devel-3.3.7-1.fc16.i686 kernel-headers-3.3.7-1.fc16.i686 kmod-nvidia-3.3.4-3.fc16.i686-295.49-1.fc16.1.i686 kmod-nvidia-3.3.5-2.fc16.i686-295.53-1.fc16.1.i686 kmod-nvidia-3.3.7-1.fc16.i686-295.53-1.fc16.1.i686 libreport-plugin-kerneloops-2.0.8-4.fc16.i686 nvidia-settings-1.0-17.fc16.i686 nvidia-xconfig-1.0-15.fc16.i686 xorg-x11-drv-nvidia-295.53-1.fc16.i686 xorg-x11-drv-nvidia-libs-295.53-1.fc16.i686 3.3.7-1.fc16.i686 nvidia 10979580 44 i2c_core 28151 1 nvidia # nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: version 295.40 (mockbuild@) Thu Apr 12 13:28:25 CEST 2012 # RPM Fusion - nvidia-xorg.conf # Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen" 0 0 InputDevice "Keyboard0" "CoreKeyboard" InputDevice "Mouse0" "CorePointer" EndSection Section "InputDevice" # generated from data in "/etc/sysconfig/keyboard" Identifier "Keyboard0" Driver "keyboard" Option "XkbLayout" "us" Option "XkbModel" "pc105" EndSection Section "InputDevice" # generated from default Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/input/mice" Option "Emulate3Buttons" "no" Option "ZAxisMapping" "4 5" EndSection Section "Device" Identifier "Videocard0" Driver "nvidia" EndSection Section "Screen" Identifier "Default Screen" Device "Videocard0" SubSection "Display" Modes "nvidia-auto-select" EndSubSection EndSection [toolpost@entropy ~]$ lspci |grep -i VGA 01:00.0 VGA compatible controller: nVidia Corporation NV43GL [Quadro FX 540] (rev a2)
The proprietary driver has the problem that gnome-shell animations can get a bit choppy due when compared with nouveau since it does some extra calculations or something.
I have found that adding the following line to your xorg.conf makes the gnome-shell transitions more smoother:
Option "UseCompositeWrapper" "true"
QuantumKnot - originator of the "Verne" release name (possibly the last 'normal' release name) :)