Bug #961
closed
psplash does not display on pisentry
Added by Hammel over 1 year ago.
Updated over 1 year ago.
Description
The screen is black but the psplash display never shows up prior to the launcher being displayed.
This was working before the updates for display size calculations were made. But psplash should be affected by those.
It's possible the update to psplash itself may have caused this. The way to check that would be to copy in an older opkg of psplash on a new install and see if that works.
- Status changed from New to In Progress
- % Done changed from 0 to 50
This is caused by the change to use the upstream yocto version of psplash (the old version's git repo went away). This new version doesn't honor FBDEV as an environment variable. Instead it uses --fbdev <num> command line argument where <num> is 0..9.
So I need to change getSplashFB() if psplash.f in the psplash/scripts directory to not just identify the frame buffer device but to parse its numeric identifier from the end of the string. I should be able to do that by just piping the device name to
cut c8
which just cuts the /dev/fb prefix from the string.
I've tested
psplash --fbdev 1
on the pisentry and it displays correctly, so this fix should be enough.
- Status changed from In Progress to Closed
- % Done changed from 50 to 100
It also uses PSPLASH_FIFO_DIR instead of PSPLASH_FIFO for the psplash_write utility to communicate with the running psplash process.
Code updated and tested on a pisentry.
Code committed and pushed.
Closing issue.
- Status changed from Closed to In Progress
- % Done changed from 100 to 50
Re-opening. This problem has returned but it's not for the same reason.
Running "/etc/init.d/S12asplash start" manually does show the splash screen. But the splash is not displayed at boot, either after power cycle or soft cycle. The LCD display is white for a longer period than on pistore and I'm wondering if the framebuffer is not available at the same time in pisentry.
- Target version changed from 2.0 - Harkonnen to 3.0 - Corrino
- Severity changed from 01 - Critical to 04 - Low
- % Done changed from 50 to 100
After bump of dev system components for v3.0, this problem appears to have gone away. Both pisentry and pistore are showing the splash screen.
It's possible the splash is not shown if the power/soft cycle is done on a long running (re: hot) device. In that case, shut it down for awhile to cool it off.
Closing again.
- Status changed from In Progress to Closed
Also available in: Atom
PDF
Updated by