usplash corruption on EPIA/TV Out

When you say the display corruption is "on startup", do you mean during the graphical boot splash that displays the boot progress?

If so, are you running dapper, or breezy? And which kernel version? (The output of "uname -a" would be helpful there).

If you could also attach the output of "dmesg" as an attachment to the bug, that would be great.

Adam Conrad wrote:

>Public bug report changed:
>https://launchpad.net/malone/bugs/36709
>
>Comment:
>When you say the display corruption is "on startup", do you mean during the graphical boot splash that displays the boot progress?
>
>
Yep.

>If so, are you running dapper, or breezy? And which kernel version? (The output of "uname -a" would be helpful there).
>
>
dapper: Linux keeper 2.6.15-11-686 #1 SMP PREEMPT Wed Jan 4 06:48:37 UTC
2006 i686 GNU/Linux

>If you could also attach the output of "dmesg" as an attachment to the bug, that would be great.
>
>
Ok.

[4294673.691000] PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
[4294673.691000] PNP: PS/2 controller doesn't have AUX irq; using default 12
[4294673.692000] serio: i8042 AUX port at 0x60,0x64 irq 12
[4294673.692000] serio: i8042 KBD port at 0x60,0x64 irq 1
[4294673.692000] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
[4294673.692000] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[4294673.693000] 00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
[4294673.694000] RAMDISK driver initialized: 16 RAM disks of 65536K size 1024 blocksize
[4294673.694000] Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
[4294673.694000] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
[4294673.694000] ACPI: bus type ide registered
[4294673.695000] mice: PS/2 mouse device common for all mice
[4294673.695000] EISA: Probing bus 0 at eisa.0
[4294673.695000] Cannot allocate resource for EISA slot 1
[4294673.695000] EISA: Detected 0 cards.
[4294673.695000] NET: Registered protocol family 2
[4294673.705000] IP route cache hash table entries: 4096 (order: 2, 16384 bytes)[4294673.705000] TCP established hash table entries: 16384 (order: 5, 196608 bytes)
[4294673.706000] TCP bind hash table entries: 16384 (order: 5, 196608 bytes)
[4294673.707000] TCP: Hash tables configured (established 16384 bind 16384)
[4294673.707000] TCP reno registered
[4294673.708000] TCP bic registered
[4294673.708000] NET: Registered protocol family 1
[4294673.708000] NET: Registered protocol family 8
[4294673.708000] NET: Registered protocol family 20
[4294673.708000] Using IPI No-Shortcut mode
[4294673.708000] ACPI wakeup devices:
[4294673.708000] PCI0 USB0 USB1 USB2 USB3 USB4 USB5 USB6 LAN0 AC97 MC97 UAR1
[4294673.708000] ACPI: (supports S0 S1 S3 S4 S5)
[4294673.708000] Freeing unused kernel memory: 300k freed
[4294673.820000] input: AT Translated Set 2 keyboard as /class/input/input0
[4294673.922000] vga16fb: initializing
[4294673.922000] vga16fb: mapped to 0xc00a0000
[4294674.048000] Console: switching to colour frame buffer device 80x25
[4294674.049000] fb0: VGA16 VGA frame buffer device
[4294675.207000] Capability LSM initialized
[4294675.308000] ACPI: CPU0 (power states: C1[C1] C2[C2])
[4294675.308000] ACPI: Processor [CPU0] (supports 2 throttling states)
[4294676.606000] VP_IDE: IDE controller at PCI slot 0000:00:11.1
[4294676.606000] ACPI: PCI Interrupt 0000:00:11.1[A] -> Link [LNKA] -> GSI 5 (level, low) -> IRQ 5
[4294676.606000] PCI: Via IRQ fixup for 0000:00:11.1, from 255 to 5
[4294676.606000] VP_IDE: chipset revision 6
[4294676.606000] VP_IDE: not 100% native mode: will probe irqs later
[4294676.606000] VP_IDE: VIA vt8235 (rev 00) IDE UDMA133 controller on pci0000:00:11.1
[4294676.606000] ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:DMA, hdb:pio
[4294676.606000] ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:DMA, hdd:pio
[4294676.606000] Probing IDE interface ide0...
[4294676.992000] hda: WDC WD800JB-00JJC0, ATA DISK drive
[4294677.604000] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
[4294677.604000] Probing IDE interface ide1...
[4294678.398000] hdc: DV-28...

Reassigning to usplash now, despite the fact that it's probably a vga16fb bug...

Would it be possible to get a picture (perhaps you have a digital camera lying around?) of the corruption in question?

Like you see - the display is ok in text mode

So when ubuntu is booting only flickering lines of the screen are shown.

And best of all - when gdm does start up (I assume then the xserver is used) everything shows just fine.

And added them. Sorry, but the screenshots are not all too obvious

From the pictures (which are of a TV), it looks like it is outputing via S-Video(?) so is probably the TV chip not coping with a particular set of display parameters.

The boot (BIOS/Grub) and usplash should both use the same 640x400 base mode that the machine boots in.

*However*, I've seen a few things in various places to suggest that vgafb isn't getting up the mode /quite/ the same as a call to the Video BIOS does (IIRC it dumps some values over all the registers).

Could you pop in the Dapper CD (if you have one) that uses 640x480.

Secondly, if you use any of the VESA modes on startup, does that result in readable output; by setting:

  vga=ask

on the bootloader line (use "e" for "edit") to get a list and select one.

Interesting; reading:

  http://www.blackfiveservices.co.uk/EPIATVTool.shtml

includes:

  Known problems:
  Currently, the --tvactive option turns off the TV-Out enough for the display to return to the monitor at non-TV scanrates, but doesn't disable the TV-Output itself, so the TV will display garbage.

While this isn't being called, is the garbage what you're seeing (looking at the screenshot I can't really see any sign of anything recognisable).

I tried using the vga parameter but I don't get to choose the vesa mode!?

Does this problem still exist? I have an idea of the problem, I just can't reproduce it, for one because I am using Edgy and have changed my /etc/usplash.conf file so it displays correctly on the TV. Thanks!

LCID Fire, I'm closing this bug report as no further information has been provided.
Please feel free to reopen this bug if you can provide the information asked for.
Thanks!