Kernel boot options 'nosplash text' not fully respected

Bug #575974 reported by Trond Melen
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

When booting the linux kernel with the two options 'nosplash' and 'text', I think there should be no graphical splash screens displayed, only text. Still, in Ubuntu 10.04 Lucid Lynx there is a splash screen both after boot and before shutdown (with the package 'ubuntu-desktop' installed, the splash screen is redish with 5 dots; with 'xubuntu-desktop' its black&white with the word 'xubuntu'). These splash screens may cause problems if there is a framebuffer issue with the system.

Regards,
Trond Melen

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-21-generic 2.6.32-21.32
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: rev50 [VIA 82C686A/B rev50], device 0: VIA 82C686A/B rev50 [VIA 82C686A/B rev50]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: rev50 [VIA 82C686A/B rev50], device 0: VIA 82C686A/B rev50 [VIA 82C686A/B rev50]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: tme 4170 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'rev50'/'VIA 82C686A/B rev50 with CS4299 at 0x1400, irq 5'
   Mixer name : 'Cirrus Logic CS4299 rev 4'
   Components : 'AC97a:43525934'
   Controls : 36
   Simple ctrls : 22
Date: Wed May 5 21:16:35 2010
HibernationDevice: RESUME=UUID=c0c29244-c06a-4659-b70f-c5bde147ecd1
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: FUJITSU SIEMENS Amilo D-Series
PccardctlStatus:
 Socket 0:
   3.3V 16-bit PC Card
   Subdevice 0 (function 0) bound to driver "orinoco_cs"
 Socket 1:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=a41f926b-dcbd-4d15-b11d-36c7820da034 ro ipv6.disable=1 splash quiet
ProcEnviron:
 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
 LANG=nb_NO.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
dmi.bios.date: 01/21/2002
dmi.bios.vendor: Phoenix
dmi.bios.version: V1.30
dmi.board.name: 8606-686B
dmi.board.vendor: CY23
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenix:bvrV1.30:bd01/21/2002:svnFUJITSUSIEMENS:pnAmiloD-Series:pvrDESKTOPCPUONLY:rvnCY23:rn8606-686B:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: Amilo D-Series
dmi.product.version: DESKTOP CPU ONLY
dmi.sys.vendor: FUJITSU SIEMENS

Revision history for this message
Trond Melen (trond-melen) wrote :
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Trond,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
IKT (ikt) wrote :

New bug report added, still seems to be an issue against the latest kernel.

Changed in linux (Ubuntu):
status: Expired → New
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Patrick Horn (phrh) wrote :

After wasting two hours rebooting my machine to figure out why nosplash is not recognized, I realized that it's probably looking for the string "splash" in /proc/cmdline.

Indeed, "nosplash" was the cause of the splash screen, and removing it entirely disables the splash screen... I remember with usplash, removing splash was not always enough, so this is confusing.

Also, while doing this, I found out how to disable the graphical splash. For those people who like a splash screen but do not want the framebuffer issues, there is a text-only splash screen available:

echo FRAMEBUFFER=n | sudo tee /etc/initramfs-tools/conf.d/splash
sudo apt-get remove plymouth-theme-kubuntu-logo

Also--shouldn't this bug be filed under "plymouth" and not "linux"?

penalvch (penalvch)
summary: - [lucid] Kernel boot options 'nosplash text' not fully respected
+ Kernel boot options 'nosplash text' not fully respected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.