[SOLVED] fbsplash working but have a created future problems?

jallenusn · 2012-06-16 17:21:45

I'm new to arch but have managed to successfully install fbcondecor and fbsplash and manipulate them to at least a reasonable degree to get the desired effect. However my tech-speak is poor so please bear with me.

The problem is that my splash screen seems to look fine, initially. Then, however, when Vesa hands off to inteldrm the graphics get distorted. I believe it is whenever the screen resolution change occurs during the boot (which is why i believe it occurs during the handoff). I have listed my grub configuration files as well as my daemons and Hooks below in hopes one of you guys may recognize an error. I have read and attempted to resolve the issue but it is clear I cannot solve it without some assistance from someone with a deeper knowledge.

This is what my screen looks like https://bbs.archlinux.org/viewtopic.php?id=136819 so I'm guessing it relates to the KMS but I configured the file in accordance with the wiki so...

Edit: Another possibly pertinent note is that the splash works perfectly on shutdown.

/etc/default/grub

GRUB_GFXPAYLOAD_LINUX=keep
GRUB_DISABLE_RECOVERY=true
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Arch Linux"
GRUB_DEFAULT=saved
GRUB_GFXMODE=1024x768x32
GRUB_CMDLINE_LINUX_DEFAULT='quiet loglevel=3 logo.nologo console=tty1 splash=silent,fadein,fadeout,theme:arch-elegant'
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
GRUB_TERMINAL_INPUT=console
GRUB_THEME=/boot/grub/themes/starfield/theme.txt
GRUB_CMDLINE_LINUX=splash
GRUB_HIDDEN_TIMEOUT=3

Hooks

HOOKS="base udev uswsusp fbsplash autodetect pata scsi sata filesystems usbinput uresume fsck"

Daemons

DAEMONS=(hwclock dbus !network fbcondecor sshd @netfs @crond acpid @networkmanager laptop-mode !net-profiles syslog-ng !net-auto-wireless @cupsd)

What should I be looking for to solve this problem? What occurs that changes the screen from the basic resolution it starts with to the enhanced resolution in the next portion of boot? Should I post dmesg output?

Last edited by jallenusn (2012-06-19 20:41:53)

Trilby · 2012-06-16 18:29:53

The resolution change you refer to is kernel mode setting (or KMS).

I have not used fbslash or fbcondecor, but I have checked the wiki and found this:

wiki wrote:

If you have trouble getting fbsplash to work and your machine uses KMS (Kernel Mode Setting), try adding the appropriate driver to mkinitcpio.conf.

The appropriate driver would be your video driver.

Edit: also the wiki kernel line includes a vga setting which you don't have.

Last edited by Trilby (2012-06-16 18:32:10)

jallenusn · 2012-06-16 19:18:41

Ok, I set the Module=i915 in /etc/mkinitcpio.conf and I am still getting a similar result. Also, I had the vga setting in there initially however at the KMS-wiki it says

Note: When using KMS, you must remove any references to vga or nomodeset from the kernel line in /boot/grub/menu.lst

Should I try adding the Intel_agp module as well?

Trilby · 2012-06-16 20:02:30

That's beyond my knowledge. Perhaps someone else can help out there - but a little trial and error might shed some light.

jallenusn · 2012-06-16 20:09:58

So I cleared my dmesg output and then did a reboot. I do not have much knowledge about kernel's or startup scripts (obviously) but here are 2 sets of messages that caught my attention.

[    0.462173] vesafb: mode is 1024x768x32, linelength=4096, pages=0
[    0.462174] vesafb: scrolling: redraw
[    0.462176] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[    0.462649] vesafb: framebuffer at 0xb0000000, mapped to 0xffffc90005800000, using 3072k, total 3072k
[    0.514274] Console: switching to colour frame buffer device 128x48
[    0.565838] fb0: VESA VGA frame buffer device

Edit: As I was sifting through dmesg I noticed there is a lot of mention for Vesafb and framebuffering (added above the vesa portion). Could this be conflicting the with the i915 driver? And if so, how do i stop Vesafb from loading?

Edit2: I just noticed this as well

[    8.789848] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver
[    8.789871] Console: switching to colour dummy device 80x25
[    8.790061] fbcon: inteldrmfb (fb0) is primary device
[    9.022357] Console: switching to colour frame buffer device 170x48
[    9.091309] fb0: inteldrmfb frame buffer device
[    9.091311] drm: registered panic notifier
[    9.092326] acpi device:34: registered as cooling_device9
[    9.092529] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input11
[    9.092617] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[    9.092668] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0

So does that mean it switched without a problem or could this be the point in which the splash screen gets distorted and torn?

Last edited by jallenusn (2012-06-16 21:16:39)

jallenusn · 2012-06-17 05:22:33

The more i read about this the more I am sure it is a simple solution. 2 questions
1. Should Vesa be starting up at all or should inteldrm have control from the start and if so how do i force that to happen?
2. Why is the resolution dropping so low whenever Vesa is handing off to Inteldrm and how do I change that?

Any response at all would be appreciated. I cannot figure out if I am not posting enough information to illicit a response or posting so much that no one wants to read through it. I don't feel like this is a question that is frivolous or something I could have just looked up in the wiki so I cannot figure out why no one seems willing to offer a little input.

Gusar · 2012-06-17 09:07:47

1. Loading vesafb shoudn't be a problem, it supports handover to a different driver, as your logs correctly show. But this does mean it's redundant to have it, makes little sense to load something only to have it be unloaded moments later. The question here is, why does it get loaded in the first place, usually it's loaded by the vga= statement. I'm guessing the monstrosity that is grub2 has something to do with it, remove all the GFX stuff from it's config.

2. It's not dropping, your logs show inteldrmfb gives you a 170x48 console. You didn't say what your screen's resolution actually is, but from that number it should be 1366x768. If that's really the case, inteldrmfb is working fine.

jallenusn · 2012-06-17 17:12:35

The question here is, why does it get loaded in the first place, usually it's loaded by the vga= statement. I'm guessing the monstrosity that is grub2 has something to do with it, remove all the GFX stuff from it's config.

Thanks for your input. You are correct in your assumption about my screen resolution being 1366x768. I am having trouble understanding what you mean by "remove all the GFX stuff". Do you mean for me to change my /etc/default/grub file and leave blank all of the categories that include "GFX" and then mkconfig? Or are you proposing that I manually modify something in the grub.cfg to disable the graphics mode in grub2?

One other quick note. It seems that before Vesa hands off to inteldrm the splash looks as intended. It is after this hand off takes place that the splash becomes distorted (4 different occurences of the splash across the screen, all of them appearing shredded and smeared across the screen).

Edit: Another possibly pertinent note is that the splash works perfectly on shutdown.

Also, for further reference I have posted both my /etc/default/grub & /boot/grub/grub.cfg below.

GRUB_GFXPAYLOAD_LINUX=keep
GRUB_DISABLE_RECOVERY=true
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Arch Linux"
GRUB_DEFAULT=saved
GRUB_GFXMODE=1366x768x32
GRUB_CMDLINE_LINUX_DEFAULT='quiet loglevel=3 logo.nologo console=tty1 splash=silent,fadein,fadeout,theme:arch-elegant'
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
GRUB_TERMINAL_INPUT=console
GRUB_THEME=/boot/grub/themes/starfield/theme.txt
GRUB_CMDLINE_LINUX=splash
GRUB_HIDDEN_TIMEOUT=3

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
  load_env
fi
set default="${saved_entry}"

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

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
}

function load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_msdos
insmod btrfs
set root='hd0,msdos3'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos3 --hint-efi=hd0,msdos3 --hint-baremetal=ahci0,msdos3  719a75c8-81fa-4f8d-b06a-b2ab3ba18770
else
  search --no-floppy --fs-uuid --set=root 719a75c8-81fa-4f8d-b06a-b2ab3ba18770
fi
    font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=1366x768x32
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_US
  insmod gettext
fi
terminal_input console
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  54d38b5e-db10-4162-bfcd-1226ada0d561
else
  search --no-floppy --fs-uuid --set=root 54d38b5e-db10-4162-bfcd-1226ada0d561
fi
insmod gfxmenu
loadfont ($root)/grub/themes/starfield/dejavu.pf2
insmod png
set theme=($root)/grub/themes/starfield/theme.txt
export theme
if sleep --verbose --interruptible 3 ; then
  set timeout=5
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch Linux GNU/Linux, with Linux fbcondecor kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-fbcondecor kernel-true-719a75c8-81fa-4f8d-b06a-b2ab3ba18770' {
	load_video
	set gfxpayload=keep
	insmod gzio
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos1'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  54d38b5e-db10-4162-bfcd-1226ada0d561
	else
	  search --no-floppy --fs-uuid --set=root 54d38b5e-db10-4162-bfcd-1226ada0d561
	fi
	echo	'Loading Linux fbcondecor kernel ...'
	linux	/vmlinuz-linux-fbcondecor root=UUID=719a75c8-81fa-4f8d-b06a-b2ab3ba18770 ro splash quiet loglevel=3 logo.nologo console=tty1 splash=silent,fadein,fadeout,theme:arch-elegant
	echo	'Loading initial ramdisk ...'
	initrd	/initramfs-linux-fbcondecor.img
}
menuentry 'Arch Linux GNU/Linux, with Linux fbcondecor kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-fbcondecor kernel-fallback-719a75c8-81fa-4f8d-b06a-b2ab3ba18770' {
	load_video
	set gfxpayload=keep
	insmod gzio
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos1'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  54d38b5e-db10-4162-bfcd-1226ada0d561
	else
	  search --no-floppy --fs-uuid --set=root 54d38b5e-db10-4162-bfcd-1226ada0d561
	fi
	echo	'Loading Linux fbcondecor kernel ...'
	linux	/vmlinuz-linux-fbcondecor root=UUID=719a75c8-81fa-4f8d-b06a-b2ab3ba18770 ro splash quiet loglevel=3 logo.nologo console=tty1 splash=silent,fadein,fadeout,theme:arch-elegant
	echo	'Loading initial ramdisk ...'
	initrd	/initramfs-linux-fbcondecor-fallback.img
}
menuentry 'Arch Linux GNU/Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-719a75c8-81fa-4f8d-b06a-b2ab3ba18770' {
	load_video
	set gfxpayload=keep
	insmod gzio
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos1'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  54d38b5e-db10-4162-bfcd-1226ada0d561
	else
	  search --no-floppy --fs-uuid --set=root 54d38b5e-db10-4162-bfcd-1226ada0d561
	fi
	echo	'Loading Linux core repo kernel ...'
	linux	/vmlinuz-linux root=UUID=719a75c8-81fa-4f8d-b06a-b2ab3ba18770 ro splash quiet loglevel=3 logo.nologo console=tty1 splash=silent,fadein,fadeout,theme:arch-elegant
	echo	'Loading initial ramdisk ...'
	initrd	/initramfs-linux.img
}
menuentry 'Arch Linux GNU/Linux, with Linux core repo kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-fallback-719a75c8-81fa-4f8d-b06a-b2ab3ba18770' {
	load_video
	set gfxpayload=keep
	insmod gzio
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos1'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1  54d38b5e-db10-4162-bfcd-1226ada0d561
	else
	  search --no-floppy --fs-uuid --set=root 54d38b5e-db10-4162-bfcd-1226ada0d561
	fi
	echo	'Loading Linux core repo kernel ...'
	linux	/vmlinuz-linux root=UUID=719a75c8-81fa-4f8d-b06a-b2ab3ba18770 ro splash quiet loglevel=3 logo.nologo console=tty1 splash=silent,fadein,fadeout,theme:arch-elegant
	echo	'Loading initial ramdisk ...'
	initrd	/initramfs-linux-fallback.img
}
if [ "x$default" = 'Arch Linux GNU/Linux, with Linux core repo kernel' ]; then default='Advanced options for Arch Linux GNU/Linux>Arch Linux GNU/Linux, with Linux core repo kernel'; fi;
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###

Last edited by jallenusn (2012-06-17 17:57:32)

jallenusn · 2012-06-17 18:38:52

Just for reference here is the entire dmesg output from boot. http://pastebin.com/dPj7W9yw

jallenusn · 2012-06-18 04:43:41

Ok, after working on this all day-every day for the entire weekend I think have gotten it fixed. My boot now has an image and a scrolling progress bar etc. While some of you seem to loathe the bootup images it is due to my laptop being a work pc and not wanting it to look amatuerish every time i go to do a presentation at work and have my pc hooked up to a projector...

But there are a few caveats and I want to know if this will present problems in the future or if this was a completely incorrect way of going about it etc. So, since I downloaded the fbcondecor patch I have had 4 boot options which are Core repo kernel, core repo fallback, fbcondecor, & fbcondecor fallback. I had been booting into fbcondecor thinking that...well...idk, it was new so that's what I was booting into after downloading it. So anyway, I attempted to boot into the core repo kernel and my splash would sit idle, when i would hit F1 there would be a message stating

resume:  could not stat the resume device file 'dev/sda99 Please type in the full path name to try again

I figured in my ineptitude I had screwed something up. I realize I am just learning so I am not opposed to a reinstall if need be although I wouldn't welcome it. So anyway, my solution was to type in the swap disk (/dev/sda2) and it would boot up. I discovered the message was from uswsusp (via google) and proceded to change the config file at /etc/suspend.conf . I changed the resume path to /dev/sda2 and when i boot the core repo kernel it boots right up, splash image and all.

I am extrememly confused as to what is actually happening and why this is working so here are my questions:

1. While it appears to be booting up without issue, is there a problem with my approach and the fact that it is using my swap partition location (/dev/sda2) to "resume" and bootup?

2. Is this how this is supposed to work or did I just luck into a fix that works?

3. In general what is the difference in booting up to core repo kernel and fbcondecor?

Below is my fdisk -l

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0xdc0d683d

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          63     1028159      514048+  83  Linux
Partition 1 does not start on physical sector boundary.
/dev/sda2         1028160    18442619     8707230   82  Linux swap / Solaris
/dev/sda3        18442620    38925494    10241437+  83  Linux
Partition 3 does not start on physical sector boundary.
/dev/sda4        38925495  1953520064   957297285   83  Linux
Partition 4 does not start on physical sector boundary.

Last edited by jallenusn (2012-06-18 23:19:17)

Padfoot · 2012-06-19 09:14:14

jallenusn wrote:

I'm new to arch but have managed to successfully install fbcondecor and fbsplash and manipulate them to at least a reasonable degree to get the desired effect. However my tech-speak is poor so please bear with me.
The problem is that my splash screen seems to look fine, initially. Then, however, when Vesa hands off to inteldrm the graphics get distorted. I believe it is whenever the screen resolution change occurs during the boot (which is why i believe it occurs during the handoff). I have listed my grub configuration files as well as my daemons and Hooks below in hopes one of you guys may recognize an error. I have read and attempted to resolve the issue but it is clear I cannot solve it without some assistance from someone with a deeper knowledge.
This is what my screen looks like https://bbs.archlinux.org/viewtopic.php?id=136819 so I'm guessing it relates to the KMS but I configured the file in accordance with the wiki so...
Edit: Another possibly pertinent note is that the splash works perfectly on shutdown.
/etc/default/grub
GRUB_GFXPAYLOAD_LINUX=keep
GRUB_DISABLE_RECOVERY=true
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Arch Linux"
GRUB_DEFAULT=saved
GRUB_GFXMODE=1024x768x32
GRUB_CMDLINE_LINUX_DEFAULT='quiet loglevel=3 logo.nologo console=tty1 splash=silent,fadein,fadeout,theme:arch-elegant'
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
GRUB_TERMINAL_INPUT=console
GRUB_THEME=/boot/grub/themes/starfield/theme.txt
GRUB_CMDLINE_LINUX=splash
GRUB_HIDDEN_TIMEOUT=3 
Hooks
HOOKS="base udev uswsusp fbsplash autodetect pata scsi sata filesystems usbinput uresume fsck"
Daemons
DAEMONS=(hwclock dbus !network fbcondecor sshd @netfs @crond acpid @networkmanager laptop-mode !net-profiles syslog-ng !net-auto-wireless @cupsd)
What should I be looking for to solve this problem? What occurs that changes the screen from the basic resolution it starts with to the enhanced resolution in the next portion of boot? Should I post dmesg output?

I don't use fbcondecor myself, my splash theme does not require it, so that is something you can check. Also, if using the default grub2 config scripts, your default kernel line uses both GRUB_CMDLINE_LINUX_DEFAULT and GRUB_CMDLINE_LINUX which means with your config, splash will be executed twice. This may also be a problem.

The issue with vesafb starting (not 100% certain but worth looking into) could be because the fbsplash hook is started after udev. I am guessing udev is starting vesafb, although this should not be the case with i915 in your mkinitcpio.conf modules.

Try starting fbsplash as early as possible. Of course this is hardware and config dependent, but I have a perfectly working setup by having my fbsplash hook immediately after base.

Another thing to check is in /etc/conf.d/splash, ensure you have SPLASH_DAEMON="early" set and the appropriate SPLASH_XSERVICE line uncommented. Also, try setting the SPLASH_THEMES line to your required resolution, this means the kernel image only contains the one size theme.

Hopefully this might help. Lastly, stating the obvious, ensure mkinitcpio -p linux is executed after any change to your splash settings.

Cheers.

Trilby · 2012-06-19 13:28:18

jallenusn wrote:

... not wanting it to look amatuerish every time i go to do a presentation at work and have my pc hooked up to a projector...

<anecdote>
The only way to do that in my eyes is to stand there looking like an idiot then start asking your audience "How do I get it to display on the projector?" ... "OK, now how do I get powerpoint into presenter mode?" while most people in the audience yell out random function keys to try.

My last conference presentation was at a conference with "IT" staff ... but really that had shortened their title by removing the "DIO" fom between those to letters. The whole conference was a massive cluster*(&^ as they asked everyone to put their "powerpoints" on their cloud server and use their computers. Many presentations didn't transfer well between the two major OSs and displayed improperly, some presenters forgot to upload their videos with their presentations, sometimes the cloudserver just died, and despite this all being on the conference IT people's own computers they could never seem to get them to connect to the projector.

For my presentation, I walked up with my netbook, plugged in the VGA cable and hit one button (mapped to a macro made for the occasion to run xrandr, and open my pdf-presentation fullscreen). The IT person was looking at my computer and tried to grab it while saying "OK, I think you'll need to hit Fn-F5 ..." I pointed him at the projection screen where my presentation was already displayed.

The amateurish IT staffer walked away; I presented comfortably.
</anecdote>

If the only reason you want fbsplash is to look professional at a presentation, I'd suggest it is the wrong tool for the job. With arch you are in control of your computer. You are in control of precisely when it starts sending images to a projector, and you are in control of what it sends. Use that control wisely and you're audience should never see your boot up screen, your desktop, or any fumbling with file managers to find your presentation. [nor should they see you exit your presentation to "go find" the video you want to show in the middle of your presentation.] Rather, they should see you get up to the podium or desk, plug in, and start your talk without anything getting in the way with a talk that proceeds gracefully from point to point and from slide to slide with videos or external media that come up on cue when needed without added fumbling.

jallenusn · 2012-06-19 19:35:38

@ Padfoot
Thanks for the input. My splash seems to be working and, honestly, I am not sure why. Initially i was pretty careful about tracking what I changed so that I knew exactly what helped but as the amount of time I was putting into it increased rendering no result, I started following less and less what I was changing with each reboot. I should have noted that my current configuration files look significantly different at this point than they did in my first post. I have listed what i perceive to be the pertinent information for my /etc/conf.d/splash , /etc/rc.conf , /boot/default/grub, & /etc/mkinitcpio.conf below. As I previously mentioned, the splash is working now, but if you will take a look at my most recent post previous to this one, those seem to be the most pressing question at this point in time as the way that things began working is a pretty major concern for me at this point.

Edit: Also of note: Splash is working when i boot from the core kernel, but I have the issues mentioned in my first post when booting to fbcondecor kernel. Can I just remove the kernel patched with fbcondecor since it's working otherwise?

/etc/conf.d/splash

#
# /etc/conf.d/splash
#

####  WARNING!
## This file is also sourced in the initcpio hook.
## No BASH-code (like arrays) is allowed here!

####  initcpio and Fbsplash daemon  ##########################################

## Themes to include into initcpio
## For a smaller initcpio you may try theme cfg files instead of directories.
SPLASH_THEMES="
arch-elegant/1366x768.cfg
    arch-black
    arch-banner-icons/1024x768.cfg
    arch-banner-icons/1280x800.cfg
    arch-banner-noicons/1024x768.cfg
    arch-banner-noicons/1280x800.cfg
"

## Override the initial silent splash screen status message defaults.
## Note: '$progress' will be replaced by Fbsplash itself.
## * initcpio - (no effect with fbcondecor kernel)
SPLASH_INIT_MESSAGE="Initializing the kernel"
## * bootup
SPLASH_BOOT_MESSAGE="Booting '$HOSTNAME' (\$progress%)"
## * reboot
SPLASH_REBOOT_MESSAGE="Rebooting '$HOSTNAME' (\$progress%)"
## * shutdown
SPLASH_SHUTDOWN_MESSAGE="Shutting down '$HOSTNAME' (\$progress%)"

## Include and use the Fbsplash daemon (1.5 MiB) in the initcpio
## instead of the small helper only.
## Usefull to show animations early.
## Note: Themes with 'scripts/rc_init-pre' like 'arch-banner-icons' are
##       supported now if fbsplash-extras>=2.0.10 is installed, but there
##       might still be some sophisticated ones which break when using this.
SPLASH_DAEMON="early"

## Make the splash daemon use fade effects.
## Note: The initcpio helper does only use the kernel parameter!
# Just use fadein on bootup and fadeout on shutdown/reboot
case $PREVLEVEL in  N   ) SPLASH_EFFECTS="fadein" ; esac
case  $RUNLEVEL in [06] ) SPLASH_EFFECTS="fadeout"; esac
# Uncomment this line to allways use both
# SPLASH_EFFECTS="fadein,fadeout"

## Enable the textbox when starting the Fbsplash daemon.
## Useful if the theme provides a message log or other textbox.
## The scripts write any initscripts [FAIL] messages to the log.
## Note: The textbox can also be toggled by pressing F3-key.
SPLASH_TEXTBOX="yes"

## Splash progress timeout
## If set to a positive value, Fbsplash will automatically switch to verbose
## mode if there is no progress for the specified number of seconds.
SPLASH_AUTOVERBOSE=0

####  scripts behaviour  #####################################################

## Change to verbose mode on any initscripts [FAIL] message
## Useful with very simple themes and also when starting Xorg from DAEMONS
SPLASH_VERBOSE_ON_ERRORS="no"

## Name of the DAEMONS script starting Xorg if any
## Set this to avoid virtual terminal change struggle between X and Fbsplash.
#SPLASH_XSERVICE="gdm"
SPLASH_XSERVICE="kdm"
#SPLASH_XSERVICE="xdm"
#SPLASH_XSERVICE="lxdm"
#SPLASH_XSERVICE="slim"

## Push initscripts [BUSY] messages to the splash status message line.
SPLASH_PUSH_MESSAGES="no"

# EOF #

/etc/rc.conf

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
#   Replace every !module by an entry as on the following line in a file in
#   /etc/modprobe.d:
#     blacklist module
#   See "man modprobe.conf" for details.
#
MODULES=()

# Udev settle timeout (default to 30)
UDEV_TIMEOUT=30

# Scan for FakeRAID (dmraid) Volumes at startup
USEDMRAID="no"

# Scan for BTRFS volumes at startup
USEBTRFS="yes"

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
DAEMONS=(syslog-ng hwclock dbus networkmanager fbsplash acpid sshd smartd @netfs @crond @laptop-mode acpid @networkmanager @cupsd)

/etc/default/grub

GRUB_GFXPAYLOAD_LINUX=keep
GRUB_DISABLE_RECOVERY=true
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Arch Linux"
GRUB_DEFAULT=saved
GRUB_GFXMODE=1366x768x32
GRUB_CMDLINE_LINUX_DEFAULT='quiet loglevel=3 logo.nologo console=tty1 splash=silent,fadein,fadeout,theme:arch-elegant'
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
GRUB_TERMINAL_INPUT=console
GRUB_THEME=/boot/grub/themes/starfield/theme.txt
GRUB_CMDLINE_LINUX=i915.modeset=1
GRUB_HIDDEN_TIMEOUT=3

And, finally /etc/mkinitcpio.conf

# vim:set ft=sh
# MODULES
MODULES="i915"

# 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.
# Some users may wish to include modprobe.conf for custom module options
# like so:
#    FILES="/etc/modprobe.d/modprobe.conf"
FILES=""

# HOOKS
##
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr, fsck and shutdown hooks.
HOOKS="base udev fbsplash autodetect pata scsi sata filesystems usbinput btrfs_advanced"

Last edited by jallenusn (2012-06-19 20:17:54)

jallenusn · 2012-06-19 19:42:37

@ Trilby
Thoroughly enjoyed the anecdote. Primarily because I can relate directly to being in a meeting and waiting on someone to "figure out" how to get things to work while everyone chimes in with their "fixes" all at the same time. I always just chuckle to myself while that goes on. I don't know that your antecode necessarily applies though seeing as I don't work with IT people, I work with business people, and they tend to, at least in my experience, be less impressed with how technically adept people are and more impressed with how nice and shiny everything is. If it takes 45 minutes to get it to work, they are quite alright, as long as it looks good when it does. I'm sure that's due in large part to their own technical ineptitude typically, especially when dealing with a larger company's management "teams" or maybe it's that they have an excuse to not actually be working while waiting for everything to magically work lol...either way, It did make me feel better to know that even IT people have trouble with getting the simplest things to function as I do.

jallenusn · 2012-06-19 20:45:32

From time to time I am embarrassed by my own stupidity. Why did i not see this post before https://bbs.archlinux.org/viewtopic.php?id=76248. mkinitcpio -p linux-fbcondecor...i didn't do it after my changes late in the process of trying to figure out why the "f" i couldn't get it to work. I was so frustrated and confused it just went totally unnoticed. That is why I could boot up into core, and it would work, yet when i booted into fbcondecor, it wouldn't. UGH...sorry i wasted you guys time. Thanks for the suggestions though and the help.

Arch Linux

#1 2012-06-16 17:21:45

[SOLVED] fbsplash working but have a created future problems?

#2 2012-06-16 18:29:53

Re: [SOLVED] fbsplash working but have a created future problems?

#3 2012-06-16 19:18:41

Re: [SOLVED] fbsplash working but have a created future problems?

#4 2012-06-16 20:02:30

Re: [SOLVED] fbsplash working but have a created future problems?

#5 2012-06-16 20:09:58

Re: [SOLVED] fbsplash working but have a created future problems?

#6 2012-06-17 05:22:33

Re: [SOLVED] fbsplash working but have a created future problems?

#7 2012-06-17 09:07:47

Re: [SOLVED] fbsplash working but have a created future problems?

#8 2012-06-17 17:12:35

Re: [SOLVED] fbsplash working but have a created future problems?

#9 2012-06-17 18:38:52

Re: [SOLVED] fbsplash working but have a created future problems?

#10 2012-06-18 04:43:41

Re: [SOLVED] fbsplash working but have a created future problems?

#11 2012-06-19 09:14:14

Re: [SOLVED] fbsplash working but have a created future problems?

#12 2012-06-19 13:28:18

Re: [SOLVED] fbsplash working but have a created future problems?

#13 2012-06-19 19:35:38

Re: [SOLVED] fbsplash working but have a created future problems?

#14 2012-06-19 19:42:37

Re: [SOLVED] fbsplash working but have a created future problems?

#15 2012-06-19 20:45:32

Re: [SOLVED] fbsplash working but have a created future problems?

Board footer