Difference between revisions of "Talk:Fbsplash"

From ArchWiki
Jump to: navigation, search
(Anything required for systemd?)
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
The page says:
+
== Anything required for Systemd? ==
"to the bottom of your rc.conf."
+
  
Is it really rc.conf? I thought it should be /boot/grub/menu.lst or something?
+
Asking as it does not work properly for me with {{pkg|systemd}} v36, whereas it's just fine with the old {{pkg|initscripts}}:
 
+
Ah. The formatting was confusing. Fixing.
+
 
+
== Current state of fbsplash in Arch. ==
+
 
+
Am I right in thinking that fbsplash is rather broken in Arch right now?
+
 
+
AUR page is [http://aur.archlinux.org/packages.php?do_Details=1&ID=13541&O=0&L=0&C=0&K=fbsplash&SB=n&SO=a&PP=25&do_MyPackages=0&do_Orphans=0&SeB=nd here].
+
 
+
--[[User:PeteLewis|PeteLewis]] 06:21, 17 August 2008 (EDT)
+
 
+
== No fbsplash hook anymore ==
+
 
+
I think the fbsplash hook was recently removed from fbsplash. Adding it to HOOKS will cause mkinitcpio to fail (because it can't find the script). —'''[[User:TedPavlic|TedPavlic]]''' ([[User_talk:TedPavlic|talk]]/[[Special:Contributions/TedPavlic|contrib]]/[[Special:EmailUser/TedPavlic|@]]) 11:01, 17 March 2010 (EDT)
+
: Nevermind. Some update (either of fbsplash or fbsplash-scripts) removed the initcpio script (for some reason?). Re-installing fbsplash-scripts restored the script. —'''[[User:TedPavlic|TedPavlic]]''' ([[User_talk:TedPavlic|talk]]/[[Special:Contributions/TedPavlic|contrib]]/[[Special:EmailUser/TedPavlic|@]]) 14:26, 17 March 2010 (EDT)
+
 
+
== Slightly more clear instructions requested. ==
+
 
+
While "RTFM" might be a standard mindset, the first instruction telling newbies to simply "get the package from AUR and build and install it using makepkg" (as this is used in a few articles) is very unclear. What precisely does one do here? Better step-by-step instructions are desired or at least a link on what to do in these situations. --[[User:SergeantKoopa|Odell]]
+
:Which part of the installation process is unclear? We're not going to include building instructions in the articles unless they significantly differ from the standard procedure. [[AUR#Installing_packages]] and [[Makepkg#Usage]] should have all the needed info. If you think something is lacking, please use specific examples. -- [[User:Karol|Karol]] 23:11, 30 May 2011 (EDT)
+
::Many other articles do provide decent step-by-step instructions for an average user to follow so I don't see a problem with that being included here. But that's neither here nor there. I thought I was pretty clear, but the specific example is the instruction to "Download fbsplash from the AUR" etc. However, you provided a link in your response here ([[AUR#Installing_packages]]) that I think should replace the AUR link itself on the page so people clicking through looking for info will immediately have a slightly better idea in context what they're supposed to to be doing.  --[[User:SergeantKoopa|Odell]] 00:18, 31 May 2011 (EDT)
+
:::You should read AUR, makepkg & pacman articles, the Beginners' Guide along with other articles from the Getting Started section of the [[Main Page]] and any other article you might find relevant. You are expected to understand what you're doing. If you know what AUR is and how to use it, you know how and what should you download from AUR to get fbsplash so "Download fbsplash from the AUR" seems clear and concise. -- [[User:Karol|Karol]] 01:08, 31 May 2011 (EDT)
+
 
+
== Anything required for systemd? ==
+
 
+
Asking as it does not work properly for me with systemd v36, whereas it's just fine with the old initscripts:
+
  
 
* No progress bar at boot
 
* No progress bar at boot
Line 34: Line 7:
 
* Instead after fading out, the screen remains black for some sec, then the theme suddenly reappears.
 
* Instead after fading out, the screen remains black for some sec, then the theme suddenly reappears.
 
* The tty can then be called manually — but with an entirely wrong framebuffer resolution, apparently the smallest.
 
* The tty can then be called manually — but with an entirely wrong framebuffer resolution, apparently the smallest.
* Nothing is displayed when rebooting / during shutdown (as without fbsplash).
+
* Nothing is displayed when rebooting/shutting down (as without fbsplash).
  
I'm using the binary nvidia beta driver, i. e. no KMS, without a fbcondecor-patched kernel.
+
I'm using the binary Nvidia beta drivers, i. e. no KMS, without a fbcondecor-patched kernel.
  
grub1 lines:
+
[[GRUB Legacy]] lines:
  
<pre>kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/… resume=/dev/sda3 ro logo.nologo vga=794 splash=silent,fadein,fadeout,theme:arch-elegant init=/bin/systemd systemd.unit=multi-user.target quiet loglevel=3</pre>
+
kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/… resume=/dev/sda3 ro logo.nologo vga=794 splash=silent,fadein,fadeout,theme:arch-elegant init=/bin/systemd systemd.unit=multi-user.target quiet loglevel=3
  
<pre>kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/… resume=/dev/sda3 ro logo.nologo vga=794 console=tty1 quiet loglevel=3 splash=silent,fadein,fadeout,theme:arch-elegant</pre>
+
kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/… resume=/dev/sda3 ro logo.nologo vga=794 console=tty1 quiet loglevel=3 splash=silent,fadein,fadeout,theme:arch-elegant
 +
-- [[User:Misc|Misc]] 16:22, 10 October 2011 (EDT)
  
-- [[User:Misc|Misc]] 16:22, 10 October 2011 (EDT)
+
:I experienced these problems too when I was using an fbcondecor patched kernel with the proprietary drivers (non-beta version) and initscripts. Nowadays, I'm on systemd, so testing this as well as the fbcondecor not applying to all ttys is going to be during my winter break.
 +
:[[User:ShadowKyogre|ShadowKyogre]] ([[User talk:ShadowKyogre|talk]]) 20:23, 17 November 2012 (UTC)

Latest revision as of 20:23, 17 November 2012

Anything required for Systemd?

Asking as it does not work properly for me with systemd v36, whereas it's just fine with the old initscripts:

  • No progress bar at boot
  • Won't switch to the login prompt at tty1.
  • Instead after fading out, the screen remains black for some sec, then the theme suddenly reappears.
  • The tty can then be called manually — but with an entirely wrong framebuffer resolution, apparently the smallest.
  • Nothing is displayed when rebooting/shutting down (as without fbsplash).

I'm using the binary Nvidia beta drivers, i. e. no KMS, without a fbcondecor-patched kernel.

GRUB Legacy lines:

kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/… resume=/dev/sda3 ro logo.nologo vga=794 splash=silent,fadein,fadeout,theme:arch-elegant init=/bin/systemd systemd.unit=multi-user.target quiet loglevel=3
kernel /boot/vmlinuz-linux root=/dev/disk/by-uuid/… resume=/dev/sda3 ro logo.nologo vga=794 console=tty1 quiet loglevel=3 splash=silent,fadein,fadeout,theme:arch-elegant

-- Misc 16:22, 10 October 2011 (EDT)

I experienced these problems too when I was using an fbcondecor patched kernel with the proprietary drivers (non-beta version) and initscripts. Nowadays, I'm on systemd, so testing this as well as the fbcondecor not applying to all ttys is going to be during my winter break.
ShadowKyogre (talk) 20:23, 17 November 2012 (UTC)