Plymouth & Nvidia

inukaze · 2014-06-09 07:31:35

Hi there , i wanna know how i can install the Plymouth using my nvidia drivers (the property drivers).

Because i has made the "ArchWiki" say , the Plymouth are installed , but i dont see it when i boot :=(

You can explainme the things i must do to solve this please ???

inukaze · 2014-06-09 08:54:58

I think this are help for me ->

1 -> https://wiki.archlinux.org/index.php/Uv … stallation

Here i see :

"Optimizing Resolution"

$ cat /sys/bus/platform/drivers/uvesafb/uvesafb.0/vbe_modes
cat: /sys/bus/platform/drivers/uvesafb/uvesafb.0/vbe_modes: No existe el fichero o el directorio

$ cat /sys/devices/virtual/graphics/fbcon/subsystem/fb0/virtual_size
1024,768

$ cat /sys/class/graphics/fb0/virtual_size
1024,768

Well that file '/sys/bus/platform/drivers/uvesafb/uvesafb.0/vbe_modes
dont exist but in the follow URL : https://bbs.archlinux.org/viewtopic.php?id=123970

i see the follow

the user "graysky" has posted

$ cat /sys/bus/platform/drivers/uvesafb/uvesafb.0/vbe_modes
640x400-8, 0x0100
640x480-8, 0x0101
800x600-8, 0x0103
1024x768-8, 0x0105
1280x1024-8, 0x0107
320x200-16, 0x010e
320x200-32, 0x010f
640x480-16, 0x0111
640x480-32, 0x0112
800x600-16, 0x0114
800x600-32, 0x0115
1024x768-16, 0x0117
1024x768-32, 0x0118
1280x1024-16, 0x011a
1280x1024-32, 0x011b
320x200-8, 0x0130
320x400-8, 0x0131
320x400-16, 0x0132
320x400-32, 0x0133
320x240-8, 0x0134
320x240-16, 0x0135
320x240-32, 0x0136
640x400-16, 0x013d
640x400-32, 0x013e
1280x800-8, 0x0160
1280x800-32, 0x0161
768x480-8, 0x0162
1280x720-32, 0x017b

Well i installed hwinfo

$ sudo pacman -Sy hwinfo
$ echo -e '\n\n'


$ sudo hwinfo --framebuffer
02: None 00.0: 11001 VESA Framebuffer                           
  [Created at bios.459]
  Unique ID: rdCR.mJsfVosB9SE
  Hardware Class: framebuffer
  Model: "NVIDIA nv44 Board - p262h0"
  Vendor: "NVIDIA Corporation"
  Device: "nv44 Board - p262h0"
  SubVendor: "NVIDIA"
  SubDevice: 
  Revision: "Chip Rev"
  Memory Size: 128 MB
  Memory Range: 0xc0000000-0xc7ffffff (rw)
  Mode 0x0300: 640x400 (+640), 8 bits
  Mode 0x0301: 640x480 (+640), 8 bits
  Mode 0x0303: 800x600 (+800), 8 bits
  Mode 0x0305: 1024x768 (+1024), 8 bits
  Mode 0x0307: 1280x1024 (+1280), 8 bits
  Mode 0x030e: 320x200 (+640), 16 bits
  Mode 0x030f: 320x200 (+1280), 24 bits
  Mode 0x0311: 640x480 (+1280), 16 bits
  Mode 0x0312: 640x480 (+2560), 24 bits
  Mode 0x0314: 800x600 (+1600), 16 bits
  Mode 0x0315: 800x600 (+3200), 24 bits
  Mode 0x0317: 1024x768 (+2048), 16 bits
  Mode 0x0318: 1024x768 (+4096), 24 bits
  Mode 0x031a: 1280x1024 (+2560), 16 bits
  Mode 0x031b: 1280x1024 (+5120), 24 bits
  Mode 0x0330: 320x200 (+320), 8 bits
  Mode 0x0331: 320x400 (+320), 8 bits
  Mode 0x0332: 320x400 (+640), 16 bits
  Mode 0x0333: 320x400 (+1280), 24 bits
  Mode 0x0334: 320x240 (+320), 8 bits
  Mode 0x0335: 320x240 (+640), 16 bits
  Mode 0x0336: 320x240 (+1280), 24 bits
  Mode 0x033d: 640x400 (+1280), 16 bits
  Mode 0x033e: 640x400 (+2560), 24 bits
  Mode 0x0345: 1600x1200 (+1600), 8 bits
  Mode 0x0346: 1600x1200 (+3200), 16 bits
  Mode 0x0347: 1400x1050 (+1400), 8 bits
  Mode 0x0348: 1400x1050 (+2800), 16 bits
  Mode 0x0352: 2048x1536 (+8192), 24 bits
  Config Status: cfg=new, avail=yes, need=no, active=unknown

Well i try to make manually that folder

$ sudo mkdir -p /sys/bus/platform/drivers/uvesafb/uvesafb.0
mkdir: no se puede crear el directorio «/sys/bus/platform/drivers/uvesafb/uvesafb.0»: Operación no permitida

$ su
Contraseña: 
[root@Inukaze inukaze]# mkdir -p /sys/bus/platform/drivers/uvesafb/uvesafb.0
mkdir: no se puede crear el directorio «/sys/bus/platform/drivers/uvesafb/uvesafb.0»: Operación no permitida

echo "i not allow to make that directory ¬¬"

2 -> https://bbs.archlinux.org/viewtopic.php?id=139095

Well i can't see plymouth still yet , when i boot i see the first message i try with "1024x768x24"

$ dmesg | grep uvesa
[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=6af334c4-52a1-4e16-925e-cc54006b269f rw quiet splash vga=792 nomodeset video=uvesafb:mode_option=1024×768-24,mtrr=3,scroll=ywrap init=/usr/lib/systemd/systemd
[    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=6af334c4-52a1-4e16-925e-cc54006b269f rw quiet splash vga=792 nomodeset video=uvesafb:mode_option=1024×768-24,mtrr=3,scroll=ywrap init=/usr/lib/systemd/systemd
[    0.998959] uvesafb: NVIDIA Corporation, nv44 Board - p262h0  , Chip Rev   , OEM: NVIDIA, VBE v3.0
[    1.033930] uvesafb: VBIOS/hardware supports DDC2 transfers
[    1.119329] uvesafb: monitor limits: vf = 76 Hz, hf = 82 kHz, clk = 140 MHz
[    1.119706] uvesafb: scrolling: redraw
[    1.119710] uvesafb: request region 0x3c0-0x3e0 failed
[    1.120037] uvesafb: probe of uvesafb.0 failed with error -5

Well i continue searching how i can fix it , to see plymouth during boot

3 -> Well after much tries , i got this :

$ dmesg | grep vesa
[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=6af334c4-52a1-4e16-925e-cc54006b269f rw rhgb video=uvesafb:1024x768-32,mtrr:3,ywrap vga=0x280 quiet splash init=/usr/lib/systemd/systemd
[    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=6af334c4-52a1-4e16-925e-cc54006b269f rw rhgb video=uvesafb:1024x768-32,mtrr:3,ywrap vga=0x280 quiet splash init=/usr/lib/systemd/systemd
[    0.936077] uvesafb: NVIDIA Corporation, nv44 Board - p262h0  , Chip Rev   , OEM: NVIDIA, VBE v3.0
[    0.971245] uvesafb: VBIOS/hardware supports DDC2 transfers
[    1.057062] uvesafb: monitor limits: vf = 76 Hz, hf = 82 kHz, clk = 140 MHz
[    1.057430] uvesafb: scrolling: redraw
[    1.333295] uvesafb: framebuffer at 0xc0000000, mapped to 0xffffc90010400000, using 24576k, total 131072k

Ok i see :

1 -> This is VBE3
2 -> I dont have errores with the framebuffer , but i can't see Plymouth
3 -> in my kernel line i explicit specific "ywrap" but this try "redraw" (i dont know why)

My question is , The Kernel have active : Vbe/Vesa Framebuffer Supports ? and Nvidia Framebuffer Support? i know this kernel have the nouveau framebuffer support , because of that the Plymouth , load with that driver. but with "nvidia" drivers dont load.

Last edited by inukaze (2014-06-11 03:38:39)

inukaze · 2014-06-11 07:49:23

Okey the thing is the AUR packages of Plymouth are in the version 0.8.8 and are broken for the lastest kernel.

I download and compile manually and test , and during the test i see the plymouth
the problem are i dont have a hook for when i boot the system.

How i can make a hook(s) manually for boot

i know i need two files

/usr/lib/initcpio/install/plymouth
/usr/lib/initcpio/hooks/plymouth

someone can help me with this ???

headkase · 2014-06-11 07:58:39

$ sudo pacman -Sy hwinfo

--

"pacman -Sy <package>" will eat your children. To update your system do, only, "pacman -Syu" and to install a package do, only, "pacman -S <package>"

"pacman -Sy <package>" updates the package database on your system but does not upgrade any packages. So, when you do "-Sy <package>" the dependencies pulled in may be incorrect. You may have older versions of what was needed and was not upgraded because you didn't include a "u" You should always do "-Syu" all by itself and install packages separately with only "-S <package>" Uninstalling a package is usually best done by "-Rsn <package>" as that cleans up dependencies you no longer need and such.

man pacman

is something for you to review.

Last edited by headkase (2014-06-11 08:00:07)

inukaze · 2014-06-11 08:20:20

I know , but the packages plymouth and plymouth-git from AUR not work in test , less during boot.
Well in this moment im testing nouveau , but with this , is the same.

With 2D work perfectly but with 3D wont.

i has installed manually Plymouth , and that works during the test :=) , but the packages from aur dont works. i dont know why.

Im switching back to nvidia driver . because i need full support of 2D & 3D XD

Last edited by inukaze (2014-06-11 08:20:56)

headkase · 2014-06-11 08:36:16

Plymouth has zero to do with how you are using pacman to install a package. Just "-Sy <package>" is going to bite you, so, your call - suffer the consequence.

Kartious · 2014-06-11 11:14:20

headkase wrote:

Plymouth has zero to do with how you are using pacman to install a package. Just "-Sy <package>" is going to bite you, so, your call - suffer the consequence.

If he will not listen to the wise words you are giving then he shall receive no help

Partial Updates are NOT Supported

inukaze · 2014-06-11 22:33:41

I has make the follow process :

Install from Repos :

$ sudo pacman -s v86d hwinfo
$ yaourt -s plymouthgit

Manual Install :

$ cd $HOME 
$ wget http://www.freedesktop.org/software/plymouth/releases/plymouth-0.9.0.tar.bz2
$ tar xfvj plymouth-0.9.0.tar.bz2 && cd plymouth-0.9.0
$ ./configure --prefix=/usr && make
$ sudo make install

Manual configuration :

1 - My /etc/mkinitcpio.conf

# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES="piix ide_disk reiserfs"
MODULES="nouveau uvesafb crc32c libcrc32c zlib_deflate btrfs"

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES="/etc/modprobe.d/uvesafb.conf"

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No raid, lvm2, or encrypted root is needed.
#    HOOKS="base"
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS="base udev autodetect block filesystems"
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS="base udev block filesystems"
#
##   This setup assembles a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS="base udev block mdadm encrypt filesystems"
#
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS="base udev block lvm2 filesystems"
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf block filesystems keyboard fsck v86d plymouth"

# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""

2 - My /etc/modprobe.d/uvesafb.conf

#
# This file sets the parameters for uvesafb module.
# The following format should be used:
# options uvesafb mode=<xres>x<yres>[-<bpp>][@<refresh>] scroll=<ywrap|ypan|redraw> ...
#
# For more details see:
# http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/fb/uvesafb.txt
#
options uvesafb mode_option=1024x768-32 scroll=ywrap

3 - My /etc/{burg,grub}.d/00_header

#! /bin/sh -e

# grub-mkconfig helper script.
# Copyright (C) 2006,2007,2008,2009,2010  Free Software Foundation, Inc.
#
# GRUB is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# (at your option) any later version.
#
# GRUB is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with GRUB.  If not, see <http://www.gnu.org/licenses/>.

transform="s&^&&"

prefix=/usr
exec_prefix=${prefix}
libdir=${exec_prefix}/lib
grub_prefix=`echo /boot/burg | sed ${transform}`
locale_dir=`echo /boot/burg/locale | sed ${transform}`
grub_lang=`echo $LANG | cut -d _ -f 1`
sysconfdir=/etc
pass_file=${sysconfdir}/default/burg-passwd

. ${libdir}/burg/burg-mkconfig_lib

# Do this as early as possible, since other commands might depend on it.
# (e.g. the `loadfont' command might need lvm or raid modules)
for i in ${GRUB_PRELOAD_MODULES} ; do
  echo "insmod $i"
done

if [ "x${GRUB_DEFAULT}" = "x" ] ; then GRUB_DEFAULT=0 ; fi
if [ "x${GRUB_DEFAULT}" = "xsaved" ] ; then GRUB_DEFAULT='${saved_entry}' ; fi
if [ "x${GRUB_TIMEOUT}" = "x" ] ; then GRUB_TIMEOUT=5 ; fi
if [ "x${GRUB_GFXMODE}" = "x" ] ; then GRUB_GFXMODE=640x480 ; fi

if test "x${GRUB_USERS}" != "x" ; then
  if test ! -r $pass_file ; then
    echo "Password file not found" >&2 ; exit 1
  fi

  awk -F: 'BEGIN {super=""} {print "password_" $3,$1,$4; if ($2=="s") super=super $1 ",";} END {if (super=="") exit 1; else print "set superusers=" super;}' $pass_file || { echo "No superuser is found" >&2 ; exit 1; }
fi

default_theme="$(echo ${GRUB_DISTRIBUTOR} | tr '[A-Z]' '[a-z]' | cut -d' ' -f1)"
if test ! -r "${grub_prefix}/themes/${default_theme}/theme"; then
  default_theme=burg
fi

if test "x${GRUB_THEME}" = "xsaved"; then
  echo "set theme_name=${default_theme}"
fi
if test "x${GRUB_GFXMODE}" = "xsaved"; then
  echo "set gfxmode=640x480"
fi
cat << EOF
if [ -s \$prefix/burgenv ]; then
  load_env
fi
set default="${GRUB_DEFAULT}"
if [ \${prev_saved_entry} ]; then
  set saved_entry=\${prev_saved_entry}
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z \${boot_once} ]; then
    saved_entry=\${chosen}
    save_env saved_entry
  fi
}
EOF
if test "x${GRUB_GFXMODE}" != "xsaved"; then
  echo "set gfxmode=${GRUB_GFXMODE}"
  #set gfxpayload=keep
fi

serial=0;
gfxterm=0;
for x in ${GRUB_TERMINAL_INPUT} ${GRUB_TERMINAL_OUTPUT}; do
    if [ xserial = "x$x" ]; then
	serial=1;
    fi
    if [ xgfxterm = "x$x" ]; then
	gfxterm=1;
    fi
done

if [ "x$serial" = x1 ]; then
    if ! test -e ${grub_prefix}/serial.mod ; then
	echo "Serial terminal not available on this platform." >&2 ; exit 1
    fi

    if [ "x${GRUB_SERIAL_COMMAND}" = "x" ] ; then
	grub_warn "Requested serial terminal but GRUB_SERIAL_COMMAND is unspecified. Default parameters will be used."
	GRUB_SERIAL_COMMAND=serial
    fi
    echo "${GRUB_SERIAL_COMMAND}"
fi

if [ x$GRUB_THEME != x ] && [ ! -f $GRUB_THEME ] ; then
  cat << EOF
function select_menu {
  if menu_popup -t template_popup theme_menu ; then
    free_config template_popup template_subitem menu class screen
    load_config \${prefix}/themes/\${theme_name}/theme \${prefix}/themes/custom/theme_\${theme_name}
EOF
  
  if test "x${GRUB_THEME}" = "xsaved"; then
    cat << EOF
    save_env theme_name
    menu_refresh
  fi
}
EOF
  else
    cat << EOF
    menu_refresh
  fi
}
set theme_name=${GRUB_THEME}
EOF
  fi

  cat << EOF
function toggle_fold {
  if test -z \$theme_fold ; then
    set theme_fold=1
  else
    set theme_fold=
  fi
EOF
  
  if test "x${GRUB_FOLD}" = "xsaved"; then
    cat << EOF
  save_env theme_fold
  menu_refresh
}
EOF
  else
    cat << EOF
  menu_refresh
}
EOF
    if test "x${GRUB_FOLD}" = "xtrue"; then
      echo "set theme_fold=1"
    else
      echo "set theme_fold="
    fi
  fi
  
  cat << EOF
function select_resolution {
  if menu_popup -t template_popup resolution_menu ; then
    menu_reload_mode
EOF

  if test "x${GRUB_GFXMODE}" = "xsaved"; then
    echo "    save_env gfxmode"
  fi

  cat << EOF
  fi
}
EOF

  echo "if test -f \${prefix}/themes/\${theme_name}/theme ; then"

  cat << EOF
  insmod coreui
  menu_region.text
EOF

  for i in ${grub_prefix}/themes/* ; do
    if test -r "$i/theme"; then
      theme_name=`echo $i | sed 's,.*/,,'`
      echo "  load_string '+theme_menu { -${theme_name} { command=\"set theme_name=${theme_name}\" }}'"
    fi
  done  

  for i in ${grub_prefix}/themes/conf.d/* ; do
    case "$i" in
      *~*) ;;
      *)
        if grub_file_is_not_garbage "$i" && test -r "$i" ; then
	  echo "  load_config \${prefix}/themes/conf.d/`echo $i | sed 's,.*/,,'`"
        fi
      ;;
    esac
  done

  echo "  load_config \${prefix}/themes/\${theme_name}/theme \${prefix}/themes/custom/theme_\${theme_name}"

  if [ "x$gfxterm" = x1 ]; then
    cat << EOF
  insmod ${GRUB_VIDEO_BACKEND}
  insmod png
  insmod jpeg
  set gfxfont="Unifont Regular 16"
  menu_region.gfx
  vmenu resolution_menu
EOF
  fi

  cat << EOF
  controller.ext
fi
EOF

  gfxterm=0
  term_output=
  for x in ${GRUB_TERMINAL_OUTPUT}; do
    if [ xgfxterm != "x$x" ]; then
      term_output=${term_output} $x
    fi
  done
  GRUB_TERMINAL_OUTPUT=${term_output}
fi

if [ "x$gfxterm" = x1 ]; then
    # Make the font accessible
    prepare_grub_to_access_device `${grub_probe} --target=device "${GRUB_FONT_PATH}"`

    cat << EOF
if loadfont `make_system_path_relative_to_its_root "${GRUB_FONT_PATH}"` ; then
  insmod gfxterm
  insmod ${GRUB_VIDEO_BACKEND}
EOF
    if [ "x$GRUB_THEME" != x ] && [ -f "$GRUB_THEME" ] \
	&& is_path_readable_by_grub "$GRUB_THEME"; then
	echo "Found theme: $GRUB_THEME" >&2
	prepare_grub_to_access_device `${grub_probe} --target=device "$GRUB_THEME"` | sed -e "s/^/  /"
	cat << EOF
  insmod gfxmenu
EOF
	themedir="`dirname "$GRUB_THEME"`"
	for x in "$themedir"/*.pf2 "$themedir"/f/*.pf2; do
	    if [ -f "$x" ]; then
		cat << EOF
  loadfont (\$root)`make_system_path_relative_to_its_root $x`
EOF
	    fi
	done
	if [ x"`echo "$themedir"/*.jpg`" != x"$themedir/*.jpg" ] || [ x"`echo "$themedir"/*.jpeg`" != x"$themedir/*.jpeg" ]; then
	    cat << EOF
  insmod jpeg
EOF
	fi
	if [ x"`echo "$themedir"/*.png`" != x"$themedir/*.png" ]; then
	    cat << EOF
  insmod png
EOF
	fi
	if [ x"`echo "$themedir"/*.tga`" != x"$themedir/*.tga" ]; then
	    cat << EOF
  insmod tga
EOF
	fi

	cat << EOF
  set theme=(\$root)`make_system_path_relative_to_its_root $GRUB_THEME`
EOF
    elif [ "x$GRUB_BACKGROUND" != x ] && [ -f "$GRUB_BACKGROUND" ] \
	    && is_path_readable_by_grub "$GRUB_BACKGROUND"; then
	echo "Found background: $GRUB_BACKGROUND" >&2
	case "$GRUB_BACKGROUND" in
	    *.png)         reader=png ;;
	    *.tga)         reader=tga ;;
	    *.jpg|*.jpeg)  reader=jpeg ;;
	    *)             echo "Unsupported image format" >&2; exit 1 ;;
	esac
	prepare_grub_to_access_device `${grub_probe} --target=device "$GRUB_BACKGROUND"` | sed -e "s/^/  /"
	cat << EOF
  insmod $reader
  background_image -m stretch `make_system_path_relative_to_its_root "$GRUB_BACKGROUND"`
EOF
    fi
    cat << EOF
fi
EOF
fi

case x${GRUB_TERMINAL_INPUT} in
  x)
    # Just use the native terminal
  ;;
  x*)
    cat << EOF
if terminal_input ${GRUB_TERMINAL_INPUT} ; then true ; else
  # For backward compatibility with versions of terminal.mod that don't
  # understand terminal_input
  terminal ${GRUB_TERMINAL_INPUT}
fi
EOF
  ;;
esac

case x${GRUB_TERMINAL_OUTPUT} in
  x)
    # Just use the native terminal
  ;;
  x*)
    cat << EOF
if terminal_output ${GRUB_TERMINAL_OUTPUT} ; then true ; else
  # For backward compatibility with versions of terminal.mod that don't
  # understand terminal_output
  terminal ${GRUB_TERMINAL_OUTPUT}
fi
EOF
  ;;
esac

# Gettext variables and module
if [ "x${LANG}" != "xC" ] ; then
    prepare_grub_to_access_device $(${grub_probe} --target=device ${locale_dir})
  cat << EOF
set locale_dir=(\$root)$(make_system_path_relative_to_its_root ${locale_dir})
set lang=${grub_lang}
insmod gettext
EOF
fi

if [ "x${GRUB_HIDDEN_TIMEOUT}" != "x" ] ; then
  if [ "x${GRUB_HIDDEN_TIMEOUT_QUIET}" = "xtrue" ] ; then
    verbose=
  else
    verbose=" --verbose"
  fi
  cat << EOF
if sleep$verbose --interruptible ${GRUB_HIDDEN_TIMEOUT} ; then
  set timeout=${GRUB_TIMEOUT}
fi
EOF
else
  cat << EOF
set timeout=${GRUB_TIMEOUT}
EOF
fi

# Play an initial tune
if [ "x${GRUB_INIT_TUNE}" != "x" ] ; then
  cat << EOF
insmod play
play ${GRUB_INIT_TUNE}
EOF
fi

4 - Adding a Menu entry in the /boot/{burg,grub}/{burg,grub}.cfg

### BEGIN /etc/burg.d/10_linux ###
menuentry 'Arch Linux, Pruebas para Plymouth' --class arch --class gnu-linux --class gnu --class os --group group_main {
	insmod ext2
	set root='(hd0,6)'
	search --no-floppy --fs-uuid --set 39c2b115-9c28-4805-87bf-88657495ea4c
	echo	'Loading Linux 3.14.6-1-ARCH ...'
	linux	/vmlinuz-linux root=UUID=6af334c4-52a1-4e16-925e-cc54006b269f rw nomodeset rhgb vga=280 video=vesafb:1024x768x32,mtrr=3,scroll=ywrap quiet splash init=/usr/lib/systemd/systemd 
	echo	'Loading initial ramdisk ...'
	initrd	/initramfs-linux.img
}

5 - Making the Kernel Image :

$ mkinitcpio -p linux

6 - Reboot (I can't see the Plymouth) i login into my session and test plymouth

xtty=`w -hs | awk '{print $2}' | sort -u | sed 's/^[tty \t]*//' | sed -n '$p'` && echo "tty X(org/Free86/System) = $xtty" ; sudo plymouth --quit ; sudo plymouthd ; sudo plymouth show-splash update && sleep 10 ; sudo killall -9 plymouthd ; sudo chvt $xtty

During the test i can see :
>>moderator edit: Removed large image. Please read Forum Etiquette: Pasting Pictures and Code. Thanks. --fsckd<<

I wanna know how i can force the "Framebuffer use" im trying to make the equivalent in ArchLinux of

echo FRAMEBUFFER=y | sudo tee /etc/initramfs-tools/conf.d/splash

but with mkinitcpio

Last edited by fsckd (2014-06-12 13:42:53)

headkase · 2014-06-11 22:42:57

Sigh.

"sudo make install" is a bugaboo. You just put files into your system that pacman is not aware of. So, later, when you install a similar package pacman will abort if the files it is trying to install already exist and are not owned by any package it knows of. In that situation you either force pacman, and take the risk of bork, or you don't install the conflicting package. I would recommend "sudo make uninstall" (Edit: if the source package supports that) in that source directory to clean your system somewhat and then properly use a PKGBUILD to generate a package pacman can be used with and will know all the files about.

Last edited by headkase (2014-06-11 22:47:21)

inukaze · 2014-06-11 23:06:01

I give up with Plymouth , im going to try with another like :

Fbsplash -> https://wiki.archlinux.org/index.php/Fbsplash
Splashy -> https://wiki.archlinux.org/index.php/Splashy
xplash -> $ yaourt -S xsplash-bzr

I see various videos , i going to try with the "Splashy" , i like it.

I purge the plymouth and install Splashy

$ cd /plymouth-0.9.0
$ sudo make uninstall
$ sudo pacman -Rdds plymouth-git
$ yaourt -S splashy-full

==> Iniciando build()...
patching file ./autogen.sh
patch: **** malformed patch at line 5: REQUIRED_AUTOCONF_VERSION=${REQUIRED_AUTOCONF_VERSION:-2.59}

==> ERROR: Se produjo un error en build().
    Cancelando...
==> ERROR: Makepkg no ha podido compilar splashy-full.
==> Reiniciar la compilación de splashy-full? [s/N]
==> -----------------------------------------------
==>

yaourt -S fbsplash , don't compile => Fail
yaourt -S splashy-full , don't compile => Fail
yaourt -S xsplash-bzr , don't compile => Fail

Okey , the Unique Boot Splash its Plymouth and this its not working.

I wait for the mantainer fix XD the package XD

Last edited by inukaze (2014-06-11 23:53:23)

Padfoot · 2014-06-13 22:14:48

Have a look at the comments on the AUR plymouth package. It is currently broken for all Arch installs. Ongoing work with the upstream devs is happening to fix this.

Secondly, do you have an EFI system? If so, it it likely you do not need to install uvesafb as the system will automatically be using an efi-frame-buffer which works just fine with nvidia and plymouth.

The output of journalctl or dmesg will show if an efi-frame-buffer is being used.

Cheers.

[EDIT] I have noticed you still have nouveau in the modules in your mkinitcpio.conf. You need to remove that if you are using nvidia. Also wondering why you have an init= line in your kernel parameters in burg? This should not be needed seeing as systemd is the default init for Arch.[/EDIT]

Last edited by Padfoot (2014-06-13 22:25:57)

inukaze · 2014-06-15 17:26:39

Hi there ,i check all comments in that packages in plymouth and plymouth-git
well none works yet.

I dont have efi , my pc its some old , to have that XD

Well , i has removed ArchLinux , because , its too slow for me
after "systemd" installation , and updates of this , the my archlinux x86_64 , turn very lagged
and each 30 mins , the system hangs , I am forced to manually reset using the reset button

After lastest update of systemd , yesterday , the system dont read the "mkinitcpio.conf"
i remove it , because , when that detect the files , dont generated the image , because
say somethay about "bad string line" in the lines "MODULES , BINARIES , FILES , HOOKS"
you can comment that lines , if the Image is not generated with "sudo mkinitcpio -p linux"
and ready , that compile , if you has installed the update of systemd of yesterday

i has installed LinuxMint 17 with Xfce :=)
and with this distro , for the moment , are running perfect for me

Last edited by inukaze (2014-06-15 17:30:49)

headkase · 2014-06-15 17:52:14

Considering this thread as a whole, I would instead suggest that your issues are PEBKAC. Problem Exists Between Keyboard And Chair. Sorry if that offends but I think that is the likely diagnosis.

Arch Linux

#1 2014-06-09 07:31:35

Plymouth & Nvidia

#2 2014-06-09 08:54:58

Re: Plymouth & Nvidia

#3 2014-06-11 07:49:23

Re: Plymouth & Nvidia

#4 2014-06-11 07:58:39

Re: Plymouth & Nvidia

#5 2014-06-11 08:20:20

Re: Plymouth & Nvidia

#6 2014-06-11 08:36:16

Re: Plymouth & Nvidia

#7 2014-06-11 11:14:20

Re: Plymouth & Nvidia

#8 2014-06-11 22:33:41

Re: Plymouth & Nvidia

#9 2014-06-11 22:42:57

Re: Plymouth & Nvidia

#10 2014-06-11 23:06:01

Re: Plymouth & Nvidia

#11 2014-06-13 22:14:48

Re: Plymouth & Nvidia

#12 2014-06-15 17:26:39

Re: Plymouth & Nvidia

#13 2014-06-15 17:52:14

Re: Plymouth & Nvidia

Board footer