Fedora 17 @ dom3     

Installed software: diaries

  1. (12.06.13) System installation (Fedora 17)

    General remarks

  • All logs are copied from ~root to
               /opt/root/Install/initial_installation_logs/ .
            [root@localhost Install]# ll initial_installation_logs/
             total 200
             -rw-------. 1 root root  14995 Jun 12 07:34 anaconda-ks.cfg
             drwxr-xr-x. 2 root root   4096 Jun 12 07:00 anaconda-screenshots
             -rw-r--r--. 1 root root    138 Jun 13 16:08 anaconda-screenshots.ORIGIN
             drwxr-xr-x. 2 root root   4096 Jun 13 04:33 firstboot-screenshots
             -rw-r--r--. 1 root root 153285 Jun 12 07:33 install.log
             -rw-r--r--. 1 root root  18434 Jun 12 07:24 install.log.syslog
    
    (local copies:
              anaconda-ks.cfg,
              anaconda-screenshots.ORIGIN,
              install.log,
              install.log.syslog,
              anaconda-screenshots.screenshot-0052.png,
              firstboot-screenshots.screenshot-0000.png
    )

  • The system was installed from a Fedora-17-x86__64_DVD disc. It was a graphical installation in the
               Troubleshooting -> Install in a basic graphics mode
    branch (normal branch lead to a hangup of the PC).

  • Unfortunately, the screenshots were not found in the
               ~root/anaconda-screenshots,
    where they had to be.
    This can be associated with a bug discussed in
    • "Anaconda screenshots are not saved after reboot" https://bugzilla.redhat.com/show_bug.cgi?id=787962 .
      • Bug in F16, to be fixed in F18.
      • Suggested remedy (AMM 2012-03-25 02:14:40 EDT):
        • before rebooting you should run (manually by switching to console Alt-F2)
                          mkdir /mnt/sysimage/root/anaconda-screeenshots
                          cp /tmp/anaconda-screenshots/* \
                             /mnt/sysimage/tmp/anaconda-screenshots/* \
                             /mnt/sysimage/root/anaconda-screenshots/
          
    AFTER all the installation (including the "firstboot" stage) had finished, I found only one file
               screenshot-0052.png
    in the
               /tmp/anaconda-screenshots
    directory which I saved to
               ~root/anaconda-screenshots

  • As a guide to the installation, I used my notes in the
    • Inst_SW_aux/F17_Installation_Guide_Notes.html ( local copy, requires the character encoding to be set to either Western Windows-1252 or Cyrillic Windows-1251 ) .

    Step 1. Loading system from disc

      Hard disk partitioning.

Two Windows partitions were available:

             sda1
             sda2 (~100Gb, "Win7") .
The following new partitions were created:
             sda3  250Mb  ext4 /boot
             sda4                        extended partition
             sda5  176GB                 LVM physical volume
             sda6  250Mb  ext4 /boot2    a reserve for future Linux systems
             sda7  250Mb  ext4 /boot3           -"-
             sda8  250Mb  ext4 /boot4           -"-
The /boot[2-4] were specified BEFORE the LVM PhysVolume and first got natural names sda[5-7], but specifying the LVM volume moved them to sda[6-8] for an unknown reason.

Here is a post-installation report on the the above partitions by fdisk:

             [root@localhost Install]# fdisk -l /dev/sda
             
             Disk /dev/sda: 750.2 GB, 750156374016 bytes
             255 heads, 63 sectors/track, 91201 cylinders, total 1465149168
             sectors

             Units = sectors of 1 * 512 = 512 bytes
             Sector size (logical/physical): 512 bytes / 512 bytes
             I/O size (minimum/optimal): 512 bytes / 512 bytes
             Disk identifier: 0x85dc822c
             
                Device Boot     Start        End    Blocks Id System
             /dev/sda1   *       2048     206847    102400 27 Hidden NTFS WinRE
             /dev/sda2         206848  195518463  97655808  7 HPFS/NTFS/exFAT
             /dev/sda3      195518464  196030463    256000 83 Linux
             /dev/sda4      196030464 1465147391 634558464  5 Extended
             /dev/sda5      196034560  556482559 180224000 8e Linux LVM
             /dev/sda6      556484608  556996607    256000 83 Linux
             /dev/sda7      556998656  557510655    256000 83 Linux
             /dev/sda8      557512704  558024703    256000 83 Linux

      LVM partitioning.

One LVM volume group (phys. extent size 4Mb) was created named

             vg01
with the following LVM logical volumes:
             lv_swap    4Gb
             lv_root1  16Gb  ext4 /
             lv_opt1   20Gb  ext4 /opt
             lv_x01    50Gb  ext4 /x01
occupying 90 Gb. The rest free ~86 Gb of the LVM phys. volume are left for, say, 16 Gb (lv_root2) + 20 Gb (lv_opt2) of the next Linux (Fedora 18 ?) plus 50 Gb of a general reserve.

      Post-installation reports on partitions and devices

        /etc/fstab

Here is the description of all the (standard + LVM) partitions in the post-installation /etc/fstab:

            # /etc/fstab
            # Created by anaconda on Wed Jun 12 06:53:53 2013
            #
            # Accessible filesystems, by reference, are maintained under
            #                                                       '/dev/disk'
            # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for
            #                                                         more info
            #
            /dev/mapper/vg01-lv_root1                 /      ext4 defaults  1 1
            UUID=a984859d-099b-4fc7-a5bd-c0330eee186f /boot  ext4 defaults  1 2
            UUID=adefa6ae-ccda-4c58-8f26-214fef90236e /boot2 ext4 defaults  1 2
            UUID=eea0a12e-a855-4327-9ac6-4d79d1659c3f /boot3 ext4 defaults  1 2
            UUID=a1b1e9df-dbb0-4dad-9f55-cf2c359ebe60 /boot4 ext4 defaults  1 2
            /dev/mapper/vg01-lv_opt1 /opt                    ext4 defaults  1 2
            /dev/mapper/vg01-lv_x01 /x01                     ext4 defaults  1 2
            /dev/mapper/vg01-lv_swap swap                    swap defaults  0 0

        df -h

Another table of (post-installation) device - mount point correspondence is given by the `df -h' command:

        [fedotov@localhost]~% df -h  
        Filesystem                 Size  Used Avail Use% Mounted on
        devtmpfs                   2.0G     0  2.0G   0% /dev
        tmpfs                      2.0G   92K  2.0G   1% /dev/shm
        tmpfs                      2.0G  2.7M  2.0G   1% /run
        /dev/mapper/vg01-lv_root1   16G  9.5G  5.1G  66% /
        tmpfs                      2.0G     0  2.0G   0% /sys/fs/cgroup
        tmpfs                      2.0G     0  2.0G   0% /media
        /dev/sda3                  239M   88M  139M  39% /boot
        /dev/mapper/vg01-lv_opt1    20G  242M   18G   2% /opt
        /dev/sda6                  239M  2.1M  224M   1% /boot2
        /dev/sda8                  239M  2.1M  224M   1% /boot4
        /dev/sda7                  239M  2.1M  224M   1% /boot3
        /dev/mapper/vg01-lv_x01     48G  409M   46G   1% /x01

        blkid

Another list of devices:

        [root@...]# blkid
        /dev/sda1: LABEL="System [Don't Touch]" UUID="F828C44D28C40C96" \
                                                               TYPE="ntfs" 
        /dev/sda2: LABEL="Win7" UUID="C2E6C562E6C55777" TYPE="ntfs" 
        /dev/sda3: UUID="a984859d-099b-4fc7-a5bd-c0330eee186f" TYPE="ext4" 
        /dev/sda5: UUID="0Yptz3-QJ1d-qhg0-HEqa-nD9p-jKse-RUy1Jc" \
                                                             TYPE="LVM2_member" 
        /dev/sda6: UUID="adefa6ae-ccda-4c58-8f26-214fef90236e" TYPE="ext4" 
        /dev/sda7: UUID="eea0a12e-a855-4327-9ac6-4d79d1659c3f" TYPE="ext4" 
        /dev/sda8: UUID="a1b1e9df-dbb0-4dad-9f55-cf2c359ebe60" TYPE="ext4" 
        /dev/mapper/vg01-lv_root1: UUID="2ae2f462-6fe5-4427-b8e6-faa7dcaf004d" \
                                                               TYPE="ext4" 
        /dev/mapper/vg01-lv_swap: UUID="be1bcd3a-b9d6-450f-8d99-98aa44092e9f" \
                                                               TYPE="swap" 
        /dev/mapper/vg01-lv_x01: UUID="b7e9002e-ef88-48eb-b0a7-88cdb9bdebc8" \
                                                               TYPE="ext4" 
        /dev/mapper/vg01-lv_opt1: UUID="c820e6bc-3c3a-4057-8b8c-bab76258970b" \
                                                               TYPE="ext4" 

      Network parameters

  • We did not configure any Network parameters. A wired ethernet connection to an ONT modem (mgts GPON) was recognised and configured automatically under the name of p2p1 .

      Boot loader

  • The boot loader (GRUB2) info was recorded into the /boot partion.

      Package selection.

  • All packages (including those optional) in all categories were selected: 2766 packages in total. The list is available in
    • /opt/root/Install/rpm_history/130617.0208.rpm-qa.Initially_installed

    Step 2. Adding a Fedora-17 entry to Windows 7 bootloader menu

    Step 3. Firstboot

      Defining /usr/local and /home

  • In the beginning, we entered a shell console with Ctrl+Alt+F2 and made some renaming:
    • /usr/local :
                    mv /usr/local /opt/usr_local
                    ln -s /opt/usr_local /usr/local
      
    • /home :
                    rmdir /home
                    mkdir /opt/home
                    ln -s /opt/home /
      

      Creating account fedotov

  • The account fedotov was created with
               (user id, group id) = (501, 501)
    as it was in the fedora 10 @ dom2 installation (purpose: to have a correct user/group for fedotov's files on the internal and external disks of dom2).

    This violated the recommendations of F17 to have ID's > 999, and placed the account into a user/group "system" area, such that it is not seen by default in the lists of the system-config-users utility (the "hide system entries" option in the settings should be deselected in order to make the account fedotov visible).

    Post-installation file-system occupancies (Mon Jun 17 01:57:22 MSK 2013)

  •         [root@localhost ~]# df -h 
            Filesystem                 Size  Used Avail Use% Mounted on
            rootfs                      16G  9.7G  5.2G  66% /
            devtmpfs                   2.0G     0  2.0G   0% /dev
            tmpfs                      2.0G   96K  2.0G   1% /dev/shm
            tmpfs                      2.0G   29M  1.9G   2% /run
            /dev/mapper/vg01-lv_root1   16G  9.7G  5.2G  66% /
            tmpfs                      2.0G     0  2.0G   0% /sys/fs/cgroup
            tmpfs                      2.0G     0  2.0G   0% /media
            /dev/mapper/vg01-lv_opt1    20G  570M   18G   4% /opt
            /dev/mapper/vg01-lv_x01     49G  1.2G   46G   3% /x01
            /dev/sda7                  248M   12M  224M   5% /boot3
            /dev/sda6                  248M   12M  224M   5% /boot2
            /dev/sda8                  248M   12M  224M   5% /boot4
            /dev/sda3                  248M   49M  187M  21% /boot
            /dev/sda2                   94G   59G   35G  63% /media/Win7
    
    The most interesting lines are:
            rootfs                      16G  9.7G  5.2G  66% /
            /dev/mapper/vg01-lv_root1   16G  9.7G  5.2G  66% /
            /dev/sda3                  248M   49M  187M  21% /boot
    

  2. (17.06.13) /x01/legacy/ directory for dom, dom2, ... stuff

  • The following subdirs in /x01/legacy/ created:
    • dom/RH9/
                  opt_root_Install -- a "cp -rp" of
                                         dom2:/opt/root/dom_legacy/opt_root_Install
                  usr_local        -- a "cp -rp" of
                                         dom2:/opt/root/dom_legacy/usr_local
      
    • dom2/F10/
                  home/fedotov     -- for selected stuff from dom2:/home/fedotov
                  opt ->
                      root/Install -- a "cp -rp" of
                                         dom2:/opt/root/Install
                      usr_local    -- a "cp -rp" of
                                         dom2:/opt/usr_local
      

  3. (17.06.13) ~fedotov/.emacs, ~root/.emacs

  • copied from ~fedotov/.emacs at dom2
               (via /x01/legacy/dom2/F10/home/fedotov/.emacs);
    the original F17 version moved to .emacs.original_F17_version:
    • ~fedotov:
                     mv .emacs .emacs.original_F17_version 
                     cp -rp /x01/legacy/dom2/F10/home/fedotov/.emacs .
                     [fedotov@localhost]~% ll .emacs
                     -rw-r--r--. 1 fedotov fedotov 3505 Aug 26  2010 .emacs
      
    • ~root:
                     cp -rp /x01/legacy/dom2/F10/home/fedotov/.emacs .
                     chown root.root .emacs
                     [root@localhost ~]# ll .emacs
                    -rw-r--r--. 1 root root 3505 Aug 26  2010 .emacs
      

  4. (18.06.13) Fisrt SYSTEM UPDATE; looking at Apper working

  • The update is done via the Apper tool ("Get, Remove and Update SW", accessible via f -> Applications -> Administration -> SW Management) by
    • selecting Updates;
    • clicking "Check for new udpates" -> 1268 packages found;
    • clicking "Apply" -> 150 additional packages to be installed;
    • waiting about 70' for the procedure to finish;
    • rebooting the computer (there was a clickable icon of a a message window ~"restart required" followed by a list of names of 15-30 packages, the window popping up when the mouse was brought over the icon).

  • The occupancy of the root partition after the update:
               [root@localhost ~]# df -h /
               Filesystem                 Size  Used Avail Use% Mounted on
               /dev/mapper/vg01-lv_root1   16G  9.2G  5.4G  64% /
    
    The min value of `Avail' was as low as 1.6G during the update. The rpm's seem to have been downloaded into subdirs of
               /var/cache/yum/x86_64/17/
    occupying there ~1.5-2 Gb of space which was freed in the end (the Apper reported of 1.6 Gb of estimated download volume).

  • The total amount of installed packages is now 2904 (was 2766 initially).
    The list is in
    • rpm_history/130619.0016.rpm-qa.After_first_update

  5. (20.06.13) Trying to switch on the nouveau driver i.o. vesa in xorg.conf

  • F17 comes with the nouveau driver for nvidia cards:
          [fedotov@localhost]/etc/X11% rpm -qa |grep nouveau
          xorg-x11-drv-nouveau-0.0.16-37.20120306gitf5d1cd2.fc17.x86_64
    
          [fedotov@localhost]/etc/X11% lsmod |grep -i nouv
          nouveau               941736  0 
          mxm_wmi                12865  1 nouveau
          wmi                    18697  2 mxm_wmi,nouveau
          video                  18991  1 nouveau
          i2c_algo_bit           13257  1 nouveau
          drm_kms_helper         46708  1 nouveau
          ttm                    79629  1 nouveau
          drm                   264481  3 ttm,drm_kms_helper,nouveau
          i2c_core               38353  6 drm,i2c_i801,drm_kms_helper,\
                                          i2c_algo_bit,nouveau,videodev
    

  • In the article "Troubleshooting Nouveau"
    (http://nouveau.freedesktop.org/wiki/TroubleShooting/)
    one finds the Basic Question 4:
    • "Is X using the right driver (DDX)?"
      • "Do not use `nv` driver in X. Use `nouveau` instead.
        If you do not explicitly tell X to use `nouveau` in `xorg.conf`,
        it will usually default to `nv`, or maybe even `nvidia`
        (the proprietary driver). Any X driver (e.g. `vesa`) other
        than `nouveau` or `fbdev` will cause problems with KMS."

  • As our our xorg.conf does not contain the `nouveau`:
          [fedotov@localhost]/etc/X11% cat xorg.conf
          Section "Device"
                  Identifier "Videocard0"
                  Driver "vesa"
          EndSection
    

    we tried to change vesa -> nouveau and reboot.
    Fortunately, the boot screen worked OK, but X's did not load ...
    We could open a root console via Ctrl+Alt+F2 and change xorg.conf back to the original status.

  • There was the log file /var/log/Xorg.5.log
     -rw-r--r--. 1 root root  9312 Jun 20 02:26 /var/log/Xorg.5.log
    of the following content:
         [    21.223] 
         X.Org X Server 1.12.4
         Release Date: 2012-08-27
         [    21.223] X Protocol Version 11, Revision 0
         [    21.223] Build Operating System:  2.6.32-358.2.1.el6.x86_64 
         [    21.223] Current Operating System: Linux localhost.localdomain \
                       3.8.13-100.fc17.x86_64 #1 SMP Mon May 13 13:36:17 UTC \
                       2013 x86_64
         [    21.223] Kernel command line:
                      BOOT_IMAGE=/vmlinuz-3.8.13-100.fc17.x86_64 \
                       root=/dev/mapper/vg01-lv_root1 ro nomodeset rd.md=0 \
                       rd.lvm.lv=vg01/lv_swap SYSFONT=True KEYTABLE=us \
                       rd.lvm.lv=vg01/lv_root1 rd.luks=0 LANG=en_US.UTF-8 \
                       rd.dm=0 rhgb quiet
         [    21.223] Build Date: 17 April 2013  04:53:23AM
         [    21.223] Build ID: xorg-x11-server 1.12.4-7.fc17 
         [    21.223] Current version of pixman: 0.28.0
         [    21.223]    Before reporting problems, check http://wiki.x.org
            to make sure that you have the latest version.
         [    21.223] Markers: (--) probed, (**) from config file,]
                    (==) default setting,
            (++) from command line, (!!) notice, (II) informational,
            (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
         [    21.223] (==) Log file: "/var/log/Xorg.5.log", \
                      Time: Thu Jun 20 02:26:02 2013
         [    21.224] (==) Using config file: "/etc/X11/xorg.conf"
         [    21.224] (==) Using config directory: "/etc/X11/xorg.conf.d"
         [    21.224] (==) Using system config directory \
                           "/usr/share/X11/xorg.conf.d"
         [    21.224] (==) No Layout section.  Using the first Screen section.
         [    21.224] (==) No screen section available. Using defaults.
         [    21.224] (**) |-->Screen "Default Screen Section" (0)
         [    21.224] (**) |   |-->Monitor "<default monitor>"
         [    21.224] (==) No device specified for screen "Default Screen \
                           Section".
            Using the first device section listed.
         [    21.224] (**) |   |-->Device "Videocard0"
         [    21.224] (==) No monitor specified for screen \
                           "Default Screen Section".
            Using a default monitor configuration.
         [    21.224] (==) Automatically adding devices
         [    21.224] (==) Automatically enabling devices
         [    21.224] (==) FontPath set to:
            catalogue:/etc/X11/fontpath.d,
            built-ins
         [    21.224] (==) ModulePath set to "/usr/lib64/xorg/modules"
         [    21.224] (II) The server relies on udev to provide the list \
                           of input devices.
            If no devices become available, reconfigure udev or disable \
               AutoAddDevices.
         [    21.224] (II) Loader magic: 0x7c6ac0
         [    21.224] (II) Module ABI versions:
         [    21.224]    X.Org ANSI C Emulation: 0.4
         [    21.224]    X.Org Video Driver: 12.1
         [    21.224]    X.Org XInput driver : 16.0
         [    21.224]    X.Org Server Extension : 6.0
         [    21.225] (--) PCI:*(0:1:0:0) 10de:1244:10b0:0401 rev 161, \
                           Mem @ 0xf6000000/33554432, 0xe0000000/134217728,\
                           0xec000000/67108864, I/O @ 0x0000df00/128, \
                           BIOS @ 0x????????/524288
         [    21.225] (II) LoadModule: "extmod"
         [    21.225] (II) Loading \
                           /usr/lib64/xorg/modules/extensions/libextmod.so
         [    21.226] (II) Module extmod: vendor="X.Org Foundation"
         [    21.226]    compiled for 1.12.4, module version = 1.0.0
         [    21.226]    Module class: X.Org Server Extension
         [    21.226]    ABI class: X.Org Server Extension, version 6.0
         [    21.226] (II) Loading extension SELinux
         [    21.226] (II) Loading extension MIT-SCREEN-SAVER
         [    21.226] (II) Loading extension XFree86-VidModeExtension
         [    21.226] (II) Loading extension XFree86-DGA
         [    21.226] (II) Loading extension DPMS
         [    21.226] (II) Loading extension XVideo
         [    21.226] (II) Loading extension XVideo-MotionCompensation
         [    21.226] (II) Loading extension X-Resource
         [    21.226] (II) LoadModule: "dbe"
         [    21.226] (II) Loading /usr/lib64/xorg/modules/extensions/libdbe.so
         [    21.226] (II) Module dbe: vendor="X.Org Foundation"
         [    21.226]    compiled for 1.12.4, module version = 1.0.0
         [    21.226]    Module class: X.Org Server Extension
         [    21.226]    ABI class: X.Org Server Extension, version 6.0
         [    21.226] (II) Loading extension DOUBLE-BUFFER
         [    21.226] (II) LoadModule: "glx"
         [    21.226] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
         [    21.226] (II) Module glx: vendor="X.Org Foundation"
         [    21.226]    compiled for 1.12.4, module version = 1.0.0
         [    21.226]    ABI class: X.Org Server Extension, version 6.0
         [    21.226] (==) AIGLX enabled
         [    21.226] (II) Loading extension GLX
         [    21.226] (II) LoadModule: "record"
         [    21.226] (II) Loading \
                           /usr/lib64/xorg/modules/extensions/librecord.so
         [    21.227] (II) Module record: vendor="X.Org Foundation"
         [    21.227]    compiled for 1.12.4, module version = 1.13.0
         [    21.227]    Module class: X.Org Server Extension
         [    21.227]    ABI class: X.Org Server Extension, version 6.0
         [    21.227] (II) Loading extension RECORD
         [    21.227] (II) LoadModule: "dri"
         [    21.227] (II) Loading /usr/lib64/xorg/modules/extensions/libdri.so
         [    21.227] (II) Module dri: vendor="X.Org Foundation"
         [    21.227]    compiled for 1.12.4, module version = 1.0.0
         [    21.227]    ABI class: X.Org Server Extension, version 6.0
         [    21.227] (II) Loading extension XFree86-DRI
         [    21.227] (II) LoadModule: "dri2"
         [    21.227] (II) Loading \
                           /usr/lib64/xorg/modules/extensions/libdri2.so
         [    21.227] (II) Module dri2: vendor="X.Org Foundation"
         [    21.227]    compiled for 1.12.4, module version = 1.2.0
         [    21.227]    ABI class: X.Org Server Extension, version 6.0
         [    21.227] (II) Loading extension DRI2
         [    21.227] (II) LoadModule: "nouveau"
         [    21.227] (II) Loading \
                           /usr/lib64/xorg/modules/drivers/nouveau_drv.so
         [    21.228] (II) Module nouveau: vendor="X.Org Foundation"
         [    21.228]    compiled for 1.12.2, module version = 0.0.16
         [    21.228]    Module class: X.Org Video Driver
         [    21.228]    ABI class: X.Org Video Driver, version 12.0
         [    21.228] (II) NOUVEAU driver 
         [    21.228] (II) NOUVEAU driver for NVIDIA chipset families :
         [    21.228]    RIVA TNT        (NV04)
         [    21.228]    RIVA TNT2       (NV05)
         [    21.228]    GeForce 256     (NV10)
         [    21.228]    GeForce 2       (NV11, NV15)
         [    21.228]    GeForce 4MX     (NV17, NV18)
         [    21.228]    GeForce 3       (NV20)
         [    21.228]    GeForce 4Ti     (NV25, NV28)
         [    21.228]    GeForce FX      (NV3x)
         [    21.228]    GeForce 6       (NV4x)
         [    21.228]    GeForce 7       (G7x)
         [    21.228]    GeForce 8       (G8x)
         [    21.228]    GeForce GTX 200 (NVA0)
         [    21.228]    GeForce GTX 400 (NVC0)
         [    21.228] (--) using VT number 2
         
         [    21.252] drmOpenDevice: node name is /dev/dri/card0
         [    21.258] drmOpenByBusid: Searching for BusID pci:0000:01:00.0
         [    21.258] drmOpenDevice: node name is /dev/dri/card0
         [    21.262] drmOpenByBusid: drmOpenMinor returns -1
         [    21.262] drmOpenDevice: node name is /dev/dri/card1
         [    21.266] drmOpenByBusid: drmOpenMinor returns -1
         [    21.266] drmOpenDevice: node name is /dev/dri/card2
         [    21.269] drmOpenByBusid: drmOpenMinor returns -1
         [    21.269] drmOpenDevice: node name is /dev/dri/card3
         [    21.273] drmOpenByBusid: drmOpenMinor returns -1
         [    21.273] drmOpenDevice: node name is /dev/dri/card4
         [    21.277] drmOpenByBusid: drmOpenMinor returns -1
         [    21.277] drmOpenDevice: node name is /dev/dri/card5
         [    21.281] drmOpenByBusid: drmOpenMinor returns -1
         [    21.281] drmOpenDevice: node name is /dev/dri/card6
         [    21.284] drmOpenByBusid: drmOpenMinor returns -1
         [    21.284] drmOpenDevice: node name is /dev/dri/card7
         [    21.288] drmOpenByBusid: drmOpenMinor returns -1
         [    21.288] drmOpenDevice: node name is /dev/dri/card8
         [    21.292] drmOpenByBusid: drmOpenMinor returns -1
         [    21.292] drmOpenDevice: node name is /dev/dri/card9
         [    21.296] drmOpenByBusid: drmOpenMinor returns -1
         [    21.296] drmOpenDevice: node name is /dev/dri/card10
         [    21.300] drmOpenByBusid: drmOpenMinor returns -1
         [    21.300] drmOpenDevice: node name is /dev/dri/card11
         [    21.303] drmOpenByBusid: drmOpenMinor returns -1
         [    21.303] drmOpenDevice: node name is /dev/dri/card12
         [    21.307] drmOpenByBusid: drmOpenMinor returns -1
         [    21.307] drmOpenDevice: node name is /dev/dri/card13
         [    21.311] drmOpenByBusid: drmOpenMinor returns -1
         [    21.311] drmOpenDevice: node name is /dev/dri/card14
         [    21.315] drmOpenByBusid: drmOpenMinor returns -1
         [    21.315] drmOpenDevice: node name is /dev/dri/card15
         [    21.319] drmOpenByBusid: drmOpenMinor returns -1
         [    21.319] drmOpenDevice: node name is /dev/dri/card0
         [    21.324] drmOpenDevice: node name is /dev/dri/card0
         [    21.328] drmOpenDevice: node name is /dev/dri/card1
         [    21.332] drmOpenDevice: node name is /dev/dri/card2
         [    21.335] drmOpenDevice: node name is /dev/dri/card3
         [    21.339] drmOpenDevice: node name is /dev/dri/card4
         [    21.343] drmOpenDevice: node name is /dev/dri/card5
         [    21.347] drmOpenDevice: node name is /dev/dri/card6
         [    21.351] drmOpenDevice: node name is /dev/dri/card7
         [    21.354] drmOpenDevice: node name is /dev/dri/card8
         [    21.358] drmOpenDevice: node name is /dev/dri/card9
         [    21.362] drmOpenDevice: node name is /dev/dri/card10
         [    21.366] drmOpenDevice: node name is /dev/dri/card11
         [    21.369] drmOpenDevice: node name is /dev/dri/card12
         [    21.373] drmOpenDevice: node name is /dev/dri/card13
         [    21.377] drmOpenDevice: node name is /dev/dri/card14
         [    21.381] drmOpenDevice: node name is /dev/dri/card15
         [    21.385] (EE) [drm] failed to open device
         [    21.385] (EE) No devices detected.
         [    21.385] 
         Fatal server error:
         [    21.385] no screens found
         [    21.385] 
         Please consult the Fedora Project support 
             at http://wiki.x.org
          for help. 
         [    21.385] Please also check the log file at \
                      "/var/log/Xorg.5.log" for additional information.
         [    21.385] 
    

  6. (20.06.13) xx, xxx scripts

  • copied from dom2 F10 to /usr/local/bin/ :
               cp -p /x01/legacy/dom2/F10/opt/usr_local/bin/xx* /usr/local/bin/
               ll /usr/local/bin/xx*
                -rwxr-xr-x. 1 root root 1162 Dec 10  2001 /usr/local/bin/xx
                -rwxr-xr-x. 1 root root  311 Jan  6  2000 /usr/local/bin/xxx
    

  7. (20.06.13) Trying to switch on the nouveau driver io vesa with xorg.conf generated by Xorg

  • In section 5, we failed by changing vesa -> nouveau in the original /etc/X11/xorg.conf which is a very short one.

  • Now we try to generate an xorg.config with Xorg .

    Step 1 : Xorg :1 -configure

  • This indeed created the xorg.conf.new (see here) which we placed into
               Inst_SW_aux/130620.Xorg-configure
    directory.

  • Xorg-produced stdout output has been copied to
               Xorg-configure.out (see here) .
    It ends with:
            "Number of created screens does not match number of detected
             devices.
             Configuration failed.
             Server terminated with error (2). Closing log file.
            ".
    
    The Xorg-configure.out also mentions the log file
               /var/log/Xorg.1.log
    which we copied into
               Xorg.1.log_from_Xorg-configure (see here) .

    Step 2. Editing the generated conf file

Despite the message "Configuration failed", we try to continue.
The xorg.conf.new containes:

         3 Monitor sections
         3 Device sections corresponding to driver/Id combinations
            nouveau / Card0 ,
            fbdev   / Card1 ,
            vesa    / Card2 .
           respectively,
         3 Screen sections

We commented out the second and third Sections for Monitor,Device and Screen (also left only one Screen in the Section "ServerLayout") and put the result into
           xorg.conf.new.edited (see here)

    Step 3: Try xorg.conf.new.edited

  • We do:
    • copy xorg.conf.new.edited to /etc/X11/xorg.conf
    • reboot
    The results is a failure that is very similar to the one obtained in section 5:
    the
               Xorg.5.log (see here)
    again contains a fatal message
            "(EE) [drm] failed to open device
             (EE) No devices detected.
             Fatal server error:
             no screens found
            "
    
    which again seems to be related to the absense of device files
               /dev/dri/card0 , ... ,  /dev/dri/card15

  • There are also files
               boot.log (see here)
               session_last_screen (see here) -- a correctly formatted end of boot.log

    Step 4: Restore the original /etc/X11/xorg.conf and reboot

  • Note that we keep a copy of the original file in /etc/X11/xorg.conf

  7B. (21.06.13) Boot without /etc/X11/xorg.conf

  • So we tried this mode. X started OK, but in the same 1024x768 mode as earlier. The Xorg log file is in
               Inst_SW_aux/130621.Xorg.0.log.booot_without_xorg_conf (see here)
    • nouveau was loaded but ignored (?) for some reason
    • /dev/dri/card... seem to have been investigated for the fbdev module/driver; the "conclusion" was:
                    "(EE) [drm] failed to open device
                     (WW) Falling back to old probe method for fbdev
                    "
      
    • VESA seems to be selected finally?

  • The original xorg.conf was restored after the exercise.

  8. (22.06.13) Try nouveau driver with /dev/dri/card0 created manually

In sections 5 and 7, the attemts to start the nouveau video driver failed formally due to an absence of the /dev/dri/card0, .../card15 files. What if we create the /dev/dri/card0 manually?

    how to add /dev/dri/card0 ?

  • The man page above contains the following text (absent in the F17 "man drm"):
            "X(7) will attempt to create the device node automatically.
             To create the device node manually:
        
                   mkdir -p /dev/dri
                   mknod /dev/dri/card0 c 180 0
                   chgrp wheel /dev/dri/card0
                   chmod 0660 /dev/dri/card0
        
             To enable DRI in the X configuration add the following to either
             xorg.conf for Xorg(1) or XF86Config for XFree86(1) :
        
                   Section "Module"
                           ...
                           Load  "dri"
                           Load  "dri2"
                           Load  "glx"
                   EndSection
                   ...
                   Section "DRI"
                           Group "wheel"
                           Mode 0660
                   EndSection
            "
    

  • Why not to try this for the F17 nouveau driver?

  • One question is about the group `wheel' which is present in F17 but w/o any Group Member :
    • leave the file in the `root' group but set the mode 0666 i.o. 0660 permitting the rw access to everyone?

  • Another question is
    • what should be the the last two parameters of the `mknod' command in our case?

  • They are MAJOR and MINOR device numbers.

  • google search `how to find major and minor for mknod fedora 17'
    • -> http://timocharis.com/help/udev.html
              "So where did I get the major and minor numbers? You'll find them
               in your kernel source directory under Documentation/devices.txt
               -- you have a recent kernel source handy, right? If not, you can
               score at http://www.kernel.org/pub/linux/docs/device-list/
          
               A caution: the device itself will be the first number listed.
               So if you search the device list for /dev/sd and find sdb, you'll
               note its major number is block 8 (that's fine) and the minor
               numbers are 16-31 (because sdc starts with 32). However, the
               device itself (/dev/sdb) has the minor number 16; the first
               partition (dev/sdb1) gets the minor number 17. The second
               partition (dev/sdb2) gets 18, etc. An off-by-one error is
               entirely too possible here. 
              "
      

      • -> the url http://www.kernel.org/pub/linux/docs/device-list/
        does not exist!
      • -> google search: `linux device-list'
        • -> http://en.wikipedia.org/wiki/Linux_Assigned_Names_and_Numbers_Authority
          • -> The Linux Assigned Names And Numbers Authority
            http://lanana.org/
            • -> The Linux Device List
              • -> Current Linux 2.6+ Device List 06 April 2009
                http://lanana.org/docs/device-list/devices-2.6+.txt
                • -> find /dev/dri ->
                                   "226 char  Direct Rendering Infrastructure (DRI)
                                                0 = /dev/dri/card0     First graphics card
                                                1 = /dev/dri/card1     Second graphics card
                                                ...
                                   "
                  
                  • -> CAN THE NUMBERS 226,0 BE ASSUMED TO BE THE SEARCHED MAJOR,MINOR PAIR?
                    • -> searching for /dev/sd in the list, gives
                                           "8 block SCSI disk devices (0-15)
                                                      0 = /dev/sda  First SCSI disk whole disk
                                                     16 = /dev/sdb  Second SCSI disk whole disk
                                                     32 = /dev/sdc  Third SCSI disk whole disk
                                                        ...
                                                    240 = /dev/sdp  Sixteenth SCSI disk whole disk
                                           "
                      
                      which nicely agrees with the second paragraph of the quotation from http://timocharis.com/help/udev.html above.

                      So the assumption may well be valid!
                  • -> google search `"mknod /dev/dri/card0 c 226 0"' gives many hits
                    • -> e.g.
                      http://forums.freebsd.org/archive/index.php/t-27428.html
                      in the following context (quite reminding our case):
                                           "173. drmOpenDevice: node name is /dev/dri/card0
                                            174. Failed to change owner or group for file
                                                 /dev/dri! 2: No such file or directory
                                            175. Failed to change owner or group for file
                                                 /dev/dri/card0! 2: No such file or directory
                                            176. drmOpenDevice: open result is -1, (No such file
                                                 or directory)
                                            . . .
                                            The device node for card0 isn't created.
                                            Try starting X after creating it manual.
                                            Please search for it under /dev, if it's there,
                                            link to it.
                                            If it isn't there, create a device node. mknod
                                                      mknod /dev/dri/card0 c 226 0
                                            This is a temporal workaround. The node will be
                                            cleaned out after a reboot, but let's see
                                            if X can be started.
                                           "
                      
                      The warning "THE NODE WILL BE CLEANED OUT AFTER A REBOOT" should be noted !?

    Trial 1

  • mkdir -p /dev/dri
    mknod /dev/dri/card0 c 226 0
    with the vesa driver
    • reboot -> started as usual; /dev/dri/ directory disappeared!

  • May be the ownership by the group wheel would save the file?

    Trial 2

  • mkdir -p /dev/dri
    mmknod /dev/dri/card0 c 226 0
    mchgrp wheel /dev/dri/card0
    mchmod 0660 /dev/dri/card0

    and add to the original /etc/X11/xorg.conf with "vesa" driver:
        Section "DRI"
                Group "wheel"
                Mode 0660
        EndSection
    
    • reboot -> started as usual; /dev/dri/ directory again disappeared!

    Trial 3

  • No hope to preserve the /dev/dri/card0 card, but, nevertheless, try as in Trial 2, but with vesa->nouveau replacement in /etc/X11/xorg.conf

    • reboot
    • Xorg hangs spitting the boot.log to the screen, as it was earlier (section 5.) w/o trying to create /dev/dri/card0 manually.
      /dev/dri/ directory disappeared again!
      The Xorg.log is saved to
                 Inst_SW_aux/130622.Xorg.5.log.nouveau_io_vesa_in_xorg_conf (see here)
      Xorg experienced the old fatal error:
               (EE) [drm] failed to open device
               (EE) No devices detected.
               Fatal server error: no screens found
      
    • /etc/X11/xorg.conf restored to the original state

  9. (25.06.13) System Update

  • Update done with Apper and Fedora repos.

  • 34 rpm's have been updated.
    Details in:
               rpm_history/130625.0059.rpm-qa.After_sys_update (see here)

  • The Apper got broken in the end.
    • First it said something like "module setting changed, want to update?"
    • I answered "Yes". Then it started to infinitely show "Waiting for other task...". I cancelled this finally, then exited answering "No" (or was it "Discard"?) on the same question on changed settings...
    • When started next time, it can not finish a Check for new updates;
      also can not show the list of Installed sw...
    • After a reboot the Apper is OK.
    • The reason for the malfunctioning MAY have been an update of the selinux-policy package (3.10.0-169 -> 3.10.0-170) ?

Tips

Topic attachments
I Attachment History Action SizeSorted descending Date Who Comment
Texttxt initial_installation_logs.install.log.txt r1 manage 149.7 K 2013-10-25 - 23:27 AlexanderFedotov  
Texttxt rpm_history.131025.2118.rpm-qa.After_sys_update.txt r1 manage 102.3 K 2013-10-26 - 04:38 AlexanderFedotov  
Texttxt rpm_history.130625.0353.rpm-qa.nvidia_video_driver_installed.txt r1 manage 101.9 K 2013-10-26 - 04:38 AlexanderFedotov  
Texttxt rpm_history.130619.0016.rpm-qa.After_first_update.txt r1 manage 101.5 K 2013-10-26 - 04:38 AlexanderFedotov  
Texttxt rpm_history.130625.0059.rpm-qa.After_sys_update.txt r1 manage 101.5 K 2013-10-26 - 04:38 AlexanderFedotov  
Texttxt rpm_history.130625.0333.rpm-qa.rpmfusion_repos_configured.txt r1 manage 101.5 K 2013-10-26 - 04:38 AlexanderFedotov  
Texttxt rpm_history.130617.0208.rpm-qa.Initially_installed.txt r1 manage 97.2 K 2013-10-26 - 04:38 AlexanderFedotov  
Texttxt 130621.Xorg.0.log.booot_without_xorg_conf.txt r2 r1 manage 74.7 K 2013-10-26 - 22:50 AlexanderFedotov  
PNGpng initial_installation_logs.firstboot-screenshots.screenshot-0000.png r1 manage 36.2 K 2013-10-25 - 22:58 AlexanderFedotov  
PNGpng initial_installation_logs.anaconda-screenshots.screenshot-0052.png r1 manage 29.8 K 2013-10-25 - 22:58 AlexanderFedotov  
HTMLhtml 130612.F17_Installation_Guide_Notes.html r1 manage 28.3 K 2013-10-26 - 01:02 AlexanderFedotov  
Texttxt initial_installation_logs.install.log.syslog.txt r1 manage 18.0 K 2013-10-25 - 23:30 AlexanderFedotov  
Unknown file formatcfg initial_installation_logs.anaconda-ks.cfg r1 manage 14.6 K 2013-10-25 - 22:58 AlexanderFedotov  
Texttxt 130620.Xorg-configure.boot.log.txt r1 manage 11.2 K 2013-10-26 - 19:40 AlexanderFedotov  
Texttxt 130620.Xorg-configure.Xorg.5.log.txt r1 manage 9.7 K 2013-10-26 - 19:40 AlexanderFedotov  
Texttxt 130620.Xorg-configure.Xorg.1.log_from_Xorg-configure.txt r1 manage 9.5 K 2013-10-26 - 19:40 AlexanderFedotov  
Texttxt 130620.Xorg.5.log.Unsuccessful_trial_of_nouveau_driver_io_vesa_in_xorg.conf.txt r1 manage 9.3 K 2013-10-26 - 22:07 AlexanderFedotov  
Texttxt 130622.Xorg.5.log.nouveau_io_vesa_in_xorg_conf.txt r1 manage 9.3 K 2013-10-26 - 22:07 AlexanderFedotov  
Texttxt 130620.Xorg-configure.xorg.conf.new.edited.txt r1 manage 4.7 K 2013-10-26 - 19:40 AlexanderFedotov  
Texttxt 130620.Xorg-configure.xorg.conf.new.txt r1 manage 4.6 K 2013-10-26 - 19:40 AlexanderFedotov  
Texttxt 130620.Xorg-configure.Xorg-configure.out.txt r1 manage 1.5 K 2013-10-26 - 19:40 AlexanderFedotov  
Texttxt 130620.Xorg-configure.session_last_screen.txt r1 manage 1.4 K 2013-10-26 - 19:40 AlexanderFedotov  
Texttxt initial_installation_logs.anaconda-screenshots.ORIGIN.txt r1 manage 0.1 K 2013-10-25 - 23:17 AlexanderFedotov  
Edit | Attach | Watch | Print version | History: r6 < r5 < r4 < r3 < r2 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r4 - 2013-10-27 - AlexanderFedotov
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Main All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback