Bug 82511 - [gma500] gma500 doesn't create /dev/fb0 if monitor device is powered off
Summary: [gma500] gma500 doesn't create /dev/fb0 if monitor device is powered off
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - Intel) (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: Alan
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-16 14:22 UTC by Frank Grötzner
Modified: 2016-03-23 18:29 UTC (History)
2 users (show)

See Also:
Kernel Version: 3.14.13
Subsystem:
Regression: No
Bisected commit-id:


Attachments
Module removal (9.99 KB, text/plain)
2014-08-25 17:37 UTC, Frank Grötzner
Details

Description Frank Grötzner 2014-08-16 14:22:41 UTC
Hi!

I'm using an Intel Atom Boeard with gma500 graphics as mediaplayer for my projector at home. If I boot the System with projector switched off, I don't get a fb0 device and because of that can't start the X-Server.

With projector switched on:
fonk@srv51:~$ lsmod | grep gma500
gma500_gfx            177067  2 
drm_kms_helper         39831  1 gma500_gfx
drm                   236285  2 drm_kms_helper,gma500_gfx
i2c_algo_bit           12751  1 gma500_gfx
i2c_core               32420  5 drm,i2c_i801,drm_kms_helper,i2c_algo_bit,gma500_gfx
video                  17750  1 gma500_gfx
fonk@srv51:~$ 
fonk@srv51:~$ 
fonk@srv51:~$ dmesg | grep fb0
[    1.003497] simple-framebuffer simple-framebuffer.0: fb0: simplefb registered!
[   20.022483] fbcon: psbdrmfb (fb0) is primary device
[   20.837518] gma500 0000:00:02.0: fb0: psbdrmfb frame buffer device
fonk@srv51:~$ dmesg | grep gma
[   19.271925] gma500 0000:00:02.0: irq 47 for MSI/MSI-X
[   19.272088] gma500 0000:00:02.0: GPU: power management timed out.
[   19.384596] gma500 0000:00:02.0: trying to get vblank count for disabled pipe 1
[   19.388027] gma500 0000:00:02.0: trying to get vblank count for disabled pipe 1
[   20.837518] gma500 0000:00:02.0: fb0: psbdrmfb frame buffer device
[   20.837523] gma500 0000:00:02.0: registered panic notifier
[   20.837775] [drm] Initialized gma500 1.0.0 2011-06-06 for 0000:00:02.0 on minor 0
fonk@srv51:~$ 



With projector switched off:
fonk@srv51:~$ lsmod | grep gma500
gma500_gfx            177067  0 
drm_kms_helper         39831  1 gma500_gfx
drm                   236285  2 drm_kms_helper,gma500_gfx
i2c_algo_bit           12751  1 gma500_gfx
i2c_core               32420  5 drm,i2c_i801,drm_kms_helper,i2c_algo_bit,gma500_gfx
video                  17750  1 gma500_gfx
fonk@srv51:~$ 
fonk@srv51:~$ 
fonk@srv51:~$ dmesg | grep fb0
fonk@srv51:~$ dmesg | grep gma
[   13.023401] gma500 0000:00:02.0: irq 47 for MSI/MSI-X
[   13.023534] gma500 0000:00:02.0: GPU: power management timed out.
[   13.119732] gma500 0000:00:02.0: trying to get vblank count for disabled pipe 1
[   13.120015] gma500 0000:00:02.0: trying to get vblank count for disabled pipe 1
[   13.755821] [drm] Initialized gma500 1.0.0 2011-06-06 for 0000:00:02.0 on minor 0
fonk@srv51:~$ 


Also I don't know if it's possible to "rescan" for the projector while the system is running. At least if I try to remove and reinsert the kernel module, I get a kernel panic...

Any help will be appreciated!

Best regards,
Frank
Comment 1 Alan 2014-08-21 15:49:53 UTC
Can you attach the panic.. it shouldn't break on a reload but that bit of the code was always a shade iffy.
Comment 2 Frank Grötzner 2014-08-25 17:37:45 UTC
Created attachment 148111 [details]
Module removal

Hi,

attached you'll find the log that shows what happens after I try to remove the module. I think kernel "panic" isn't the exact expression... is it called kernel "oops"?

Note You need to log in before you can comment on or make changes to this bug.