[GeForce 7000M] Plymouth text theme appears when booting Lucid CD, /dev/fb0: ENOENT

Bug #565936 reported by John King
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

Binary package hint: plymouth

When I boot the Lucid Beta 2 (or the April 17 daily) Live CD, the Plymouth text theme appears, is sized to fit the screen for second, but then the screen flashes and the splash is confined to a small box in the upper left corner of the screen. It stays like this until the "Setting sensor limits" message appears, the screen flashes once, and then the 'Plymouth box' expands a bit to the right (as if it at least realized I have a widescreen monitor at that point), but still doesn't fit the screen. From there it displays the Ubuntu desktop as expected. Curiously enough, when I shut down it displays the normal Plymouth theme as expected, and it fits my screen fine.

If it's of any importance, I previously had a problem on the same laptop where Plymouth displayed everything normally, but hung and wouldn't let me boot in Beta 1 & Alpha 3: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/532984
---
Architecture: i386
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
DistroRelease: Ubuntu 10.04
LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1)
Lsusb:
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 064e:a101 Suyin Corp. Acer CrystalEye Webcam
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire 5520
Package: plymouth 0.8.1-4ubuntu1
PackageArchitecture: i386
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 nouveaufb
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Tags: lucid
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Uname: Linux 2.6.32-19-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 09/07/2007
dmi.bios.vendor: Acer
dmi.bios.version: V1.08
dmi.board.name: Fuquene
dmi.board.vendor: Acer
dmi.board.version: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAcer:bvrV1.08:bd09/07/2007:svnAcer:pnAspire5520:pvrV1.08:rvnAcer:rnFuquene:rvrN/A:cvnAcer:ct10:cvrN/A:
dmi.product.name: Aspire 5520
dmi.product.version: V1.08
dmi.sys.vendor: Acer

Revision history for this message
John King (kingj-linuxmlsts) wrote :
Revision history for this message
John King (kingj-linuxmlsts) wrote :
Revision history for this message
John King (kingj-linuxmlsts) wrote :
Revision history for this message
Steve Langasek (vorlon) wrote :

Please run 'apport-collect 565936' after booting into Lucid.

Changed in plymouth (Ubuntu):
status: New → Incomplete
Revision history for this message
John King (kingj-linuxmlsts) wrote : BootDmesg.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
John King (kingj-linuxmlsts) wrote : CurrentDmesg.txt

apport information

Revision history for this message
John King (kingj-linuxmlsts) wrote : Dependencies.txt

apport information

Revision history for this message
John King (kingj-linuxmlsts) wrote : Lspci.txt

apport information

Revision history for this message
John King (kingj-linuxmlsts) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
John King (kingj-linuxmlsts) wrote : ProcInterrupts.txt

apport information

Revision history for this message
John King (kingj-linuxmlsts) wrote : ProcModules.txt

apport information

Revision history for this message
John King (kingj-linuxmlsts) wrote : UdevDb.txt

apport information

Revision history for this message
John King (kingj-linuxmlsts) wrote : UdevLog.txt

apport information

Revision history for this message
Steve Langasek (vorlon) wrote : Re: Plymouth text theme appears when booting Lucid CD, doesn't fill the screen

Ok, this all suggests a system that should support plymouth's graphical splash.

Please boot with 'plymouth:debug=file:/var/log/plymouth-debug.log' added to the commandline, and attach the resulting /var/log/plymouth-debug.log file.

Revision history for this message
John King (kingj-linuxmlsts) wrote :

Plymouth-Debug.log

Revision history for this message
Steve Langasek (vorlon) wrote :

Thanks. The critical region of the log is here:

[./plugin.c] create_backend:creating renderer backend for device /dev/dri/card0
[./plugin.c] load_driver:Attempting to load driver '(null)'
[./plugin.c] load_driver:drmOpen failed
[ply-renderer.c] ply_renderer_open:could not open rendering device for plugin /lib/plymouth/renderers/drm.so
[./plugin.c] create_backend:creating renderer backend for device /dev/fb0
[./plugin.c] open_device:could not open '/dev/fb0': No such file or directory
[ply-renderer.c] ply_renderer_open:could not open rendering device for plugin /lib/plymouth/renderers/frame-buffer.so
[./plugin.c] open_device:could not open '/dev/fb0': No such file or directory
[ply-renderer.c] ply_renderer_open:could not open rendering device for plugin /lib/plymouth/renderers/vga16fb.so
[ply-renderer.c] ply_renderer_open:could not find suitable rendering plugin

Will have to do a bit more investigating to find out what's going on.

You mentioned that you saw the same problem with both beta2 and the april 14 daily. Which one was this log taken from?

Changed in plymouth (Ubuntu):
status: Incomplete → Triaged
summary: - Plymouth text theme appears when booting Lucid CD, doesn't fill the
- screen
+ [GeForce 7000M] Plymouth text theme appears when booting Lucid CD,
+ /dev/fb0: ENOENT
Changed in plymouth (Ubuntu):
importance: Undecided → Medium
Revision history for this message
John King (kingj-linuxmlsts) wrote :

Sorry, I mistyped, it was the April 17 daily I tested, and I took all the logs from Beta2.

description: updated
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.