Hi Everyone.
First post...Just switched to this project after years of using another distro. It's been a few months now and I'm on my third laptop; it's been a rough year ;)
Whenever possible, I like to connect to an external monitor. This worked very well in F16 on my Dell w/nvidia. Then the inverter went south and I was stuck with a Lenovo T60 w/Intel 945GM(I quickly learned I could no longer live without wide screen :) ). And that's where the fun started...
A yes. The infamous Intel 945 chipset...I waded through the whole sluggish feel issues of the >2048 res issue. Then an update appeared to have addressed all my issues(no idea which one because the one that was supposed to fix it didn't). No matter what I'd do, connecting any external monitor just worked; all was well.
Then more updates came and my setup broke again. That became a vicious circle for a while. Noticed F17 was out so I switched to that. Just like that everything stabilized(nice work on gnome-shell btw)...Then I inherited a Toshiba Tecra A8 --no 64bit extensions like my Dell but excited and couldn't resist switching nevertheless. Oddly enough, despite it being the exact same video chipset as the Lenovo I can't get any external monitor to work. Period. All the little tricks and tips I learned over the past few months aren't helping any.
So here are the symptoms: if I connect an external monitor(VGA) it won't light up at all. My LCD flickers and comes back to it's original state. Fine. The display settings reflect that one was connected and typically ids it properly. Again, fine. I then set an appropriate resolution and placement for both and hit apply. At this point the screen flickers again and my laptop comes back but the monitor does nothing(orange light). I can however, bring my cursor passed the LCD to where the monitor "is" but it's not lit so no joy there. If I let the time run out on the dialog everything goes back to normal. No harm no foul. If I play with any of the kbd combo keys to force the external monitor gnome-shell freaks out and I'm forced to recover using the console. The only thing I can successfully accomplish is Fn+F5 resulting in the external monitor only-type setup. Recovering from that without restarting X is not possible. If I toggle back to my LCD the screen flickers and spins. Same goes for disconnecting the VGA cable. At this point I can't go back to the monitor either. I have no choice but to open a console and restart Gnome-Shell. The odd time I can't even do that and must power off(ouch! haven't had to do that in Linux for years)
Sorry about rambling on so much, just trying to give as many details as possible. Any suggestions would be greatly appreciated. Many thanks in advance.
On 07/19/2012 09:14 AM, Philippe LeCavalier wrote:
Hi Everyone.
Sorry about rambling on so much, just trying to give as many details as possible. Any suggestions would be greatly appreciated. Many thanks in advance.
--
For the sake of argument, have you verified that the external port on that laptop actually works?
On Thu, Jul 19, 2012 at 9:23 AM, Mark Haney markh@abemblem.com wrote:
On 07/19/2012 09:14 AM, Philippe LeCavalier wrote:
Hi Everyone.
Sorry about rambling on so much, just trying to give as many details as possible. Any suggestions would be greatly appreciated. Many thanks in advance.
--
For the sake of argument, have you verified that the external port on that laptop actually works?
You likely missed that I mentioned I can Fn+F5 to get single output to the
monitor. So yes, it does work.
On 07/19/2012 09:38 AM, Philippe LeCavalier wrote:
On Thu, Jul 19, 2012 at 9:23 AM, Mark Haney <markh@abemblem.com
You likely missed that I mentioned I can Fn+F5 to get single output to the monitor. So yes, it does work. --
Doh! I didn't miss that part, just misread it. My bad.
On Thu, Jul 19, 2012 at 9:50 AM, Mark Haney markh@abemblem.com wrote:
On 07/19/2012 09:38 AM, Philippe LeCavalier wrote:
On Thu, Jul 19, 2012 at 9:23 AM, Mark Haney <markh@abemblem.com
You likely missed that I mentioned I can Fn+F5 to get single output to the monitor. So yes, it does work. --
Doh! I didn't miss that part, just misread it. My bad.
too much text..could have been a 2 part mini-series!
On Thu, Jul 19, 2012 at 9:14 AM, Philippe LeCavalier < support@plecavalier.com> wrote:
Hi Everyone.
First post...Just switched to this project after years of using another distro. It's been a few months now and I'm on my third laptop; it's been a rough year ;)
Whenever possible, I like to connect to an external monitor. This worked very well in F16 on my Dell w/nvidia. Then the inverter went south and I was stuck with a Lenovo T60 w/Intel 945GM(I quickly learned I could no longer live without wide screen :) ). And that's where the fun started...
A yes. The infamous Intel 945 chipset...I waded through the whole sluggish feel issues of the >2048 res issue. Then an update appeared to have addressed all my issues(no idea which one because the one that was supposed to fix it didn't). No matter what I'd do, connecting any external monitor just worked; all was well.
Then more updates came and my setup broke again. That became a vicious circle for a while. Noticed F17 was out so I switched to that. Just like that everything stabilized(nice work on gnome-shell btw)...Then I inherited a Toshiba Tecra A8 --no 64bit extensions like my Dell but excited and couldn't resist switching nevertheless. Oddly enough, despite it being the exact same video chipset as the Lenovo I can't get any external monitor to work. Period. All the little tricks and tips I learned over the past few months aren't helping any.
So here are the symptoms: if I connect an external monitor(VGA) it won't light up at all. My LCD flickers and comes back to it's original state. Fine. The display settings reflect that one was connected and typically ids it properly. Again, fine. I then set an appropriate resolution and placement for both and hit apply. At this point the screen flickers again and my laptop comes back but the monitor does nothing(orange light). I can however, bring my cursor passed the LCD to where the monitor "is" but it's not lit so no joy there. If I let the time run out on the dialog everything goes back to normal. No harm no foul. If I play with any of the kbd combo keys to force the external monitor gnome-shell freaks out and I'm forced to recover using the console. The only thing I can successfully accomplish is Fn+F5 resulting in the external monitor only-type setup. Recovering from that without restarting X is not possible. If I toggle back to my LCD the screen flickers and spins. Same goes for disconnecting the VGA cable. At this point I can't go back to the monitor either. I have no choice but to open a console and restart Gnome-Shell. The odd time I can't even do that and must power off(ouch! haven't had to do that in Linux for years)
Sorry about rambling on so much, just trying to give as many details as possible. Any suggestions would be greatly appreciated. Many thanks in advance.
--
Thanks, Phil
references:
video chipset: 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
packages: gnome-shell 3.4.1 kernel 3.4.0-1.fc17.i686
Anyone?
On 07/24/2012 01:24 PM, Philippe LeCavalier wrote:
video chipset: 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
packages: gnome-shell 3.4.1 kernel 3.4.0-1.fc17.i686
Anyone?
What does xrandr say? What happens after ctrl-alt-bksp? Is this GNOME specific?
Andrew.
On Tue, Jul 24, 2012 at 9:02 AM, Andrew Haley aph@redhat.com wrote:
On 07/24/2012 01:24 PM, Philippe LeCavalier wrote:
video chipset: 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
packages: gnome-shell 3.4.1 kernel 3.4.0-1.fc17.i686
Anyone?
What does xrandr say? What happens after ctrl-alt-bksp? Is this GNOME specific?
Thanks for responding Andrew. I appreciate the assistance.
ctrl-alt-bksp only helps recovery prior top unchecking mirror displays. After that, ctrl-alt-bksp leaves me with either 2 black screens or a blacked out monitor and oscillating/flickering LCD.
Xrandr LCD only
$ sudo xrandr Swipe your right index finger on UPEK TouchStrip Screen 0: minimum 320 x 200, current 1280 x 800, maximum 4096 x 4096 LVDS1 connected 1280x800+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1280x800 60.0*+ 1024x768 60.0 800x600 60.3 56.2 640x480 59.9 VGA1 disconnected (normal left inverted right x axis y axis) TV1 disconnected (normal left inverted right x axis y axis)
Xrandr LCD+MONITOR $ sudo xrandr Screen 0: minimum 320 x 200, current 1024 x 768, maximum 4096 x 4096 LVDS1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1280x800 60.0 + 1024x768 60.0* 800x600 60.3 56.2 640x480 59.9 VGA1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.0* 800x600 60.3 56.2 848x480 60.0 640x480 59.9 TV1 unknown connection (normal left inverted right x axis y axis) 848x480 59.9 + 640x480 59.9 + 1024x768 59.9 800x600 59.9
thanks, Phil
On 07/24/2012 02:33 PM, Philippe LeCavalier wrote:
On Tue, Jul 24, 2012 at 9:02 AM, Andrew Haley aph@redhat.com wrote:
On 07/24/2012 01:24 PM, Philippe LeCavalier wrote:
video chipset: 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
packages: gnome-shell 3.4.1 kernel 3.4.0-1.fc17.i686
Anyone?
What does xrandr say? What happens after ctrl-alt-bksp? Is this GNOME specific?
Thanks for responding Andrew. I appreciate the assistance.
ctrl-alt-bksp only helps recovery prior top unchecking mirror displays. After that, ctrl-alt-bksp leaves me with either 2 black screens or a blacked out monitor and oscillating/flickering LCD.
Xrandr LCD only
$ sudo xrandr Swipe your right index finger on UPEK TouchStrip Screen 0: minimum 320 x 200, current 1280 x 800, maximum 4096 x 4096 LVDS1 connected 1280x800+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1280x800 60.0*+ 1024x768 60.0 800x600 60.3 56.2 640x480 59.9 VGA1 disconnected (normal left inverted right x axis y axis) TV1 disconnected (normal left inverted right x axis y axis)
Xrandr LCD+MONITOR $ sudo xrandr Screen 0: minimum 320 x 200, current 1024 x 768, maximum 4096 x 4096 LVDS1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1280x800 60.0 + 1024x768 60.0* 800x600 60.3 56.2 640x480 59.9 VGA1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.0* 800x600 60.3 56.2 848x480 60.0 640x480 59.9 TV1 unknown connection (normal left inverted right x axis y axis) 848x480 59.9 + 640x480 59.9 + 1024x768 59.9 800x600 59.9
OK, so it does see your display. That's good.
I couldn't get my laptop to recognize the external monitor without a ctrl-alt-bksp to scan the monitors. Now have a look in /var/log/Xorg.0.log and we can see what's happening.
Try a few things like
xrandr --auto --output VGA1 --same-as LVDS1
Andrew.
On Tue, Jul 24, 2012 at 10:01 AM, Andrew Haley aph@redhat.com wrote:
On 07/24/2012 02:33 PM, Philippe LeCavalier wrote:
On Tue, Jul 24, 2012 at 9:02 AM, Andrew Haley aph@redhat.com wrote:
On 07/24/2012 01:24 PM, Philippe LeCavalier wrote:
video chipset: 00:02.0 VGA compatible controller: Intel Corporation Mobile
945GM/GMS,
943/940GML Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
packages: gnome-shell 3.4.1 kernel 3.4.0-1.fc17.i686
Anyone?
What does xrandr say? What happens after ctrl-alt-bksp? Is this GNOME specific?
Thanks for responding Andrew. I appreciate the assistance.
ctrl-alt-bksp only helps recovery prior top unchecking mirror displays. After that, ctrl-alt-bksp leaves me with either 2 black screens or a blacked out monitor and oscillating/flickering LCD.
Xrandr LCD only
$ sudo xrandr Swipe your right index finger on UPEK TouchStrip Screen 0: minimum 320 x 200, current 1280 x 800, maximum 4096 x 4096 LVDS1 connected 1280x800+0+0 (normal left inverted right x axis y axis)
0mm
x 0mm 1280x800 60.0*+ 1024x768 60.0 800x600 60.3 56.2 640x480 59.9 VGA1 disconnected (normal left inverted right x axis y axis) TV1 disconnected (normal left inverted right x axis y axis)
Xrandr LCD+MONITOR $ sudo xrandr Screen 0: minimum 320 x 200, current 1024 x 768, maximum 4096 x 4096 LVDS1 connected 1024x768+0+0 (normal left inverted right x axis y axis)
0mm
x 0mm 1280x800 60.0 + 1024x768 60.0* 800x600 60.3 56.2 640x480 59.9 VGA1 connected 1024x768+0+0 (normal left inverted right x axis y axis)
0mm
x 0mm 1024x768 60.0* 800x600 60.3 56.2 848x480 60.0 640x480 59.9 TV1 unknown connection (normal left inverted right x axis y axis) 848x480 59.9 + 640x480 59.9 + 1024x768 59.9 800x600 59.9
OK, so it does see your display. That's good.
I couldn't get my laptop to recognize the external monitor without a ctrl-alt-bksp to scan the monitors. Now have a look in /var/log/Xorg.0.log and we can see what's happening.
Try a few things like
xrandr --auto --output VGA1 --same-as LVDS1
Andrew.
Yeah. It doesn't appear to be a hardware thing. xrandr --auto --output VGA1 --same-as LVDS1 does the same as merely connecting the monitor itself. LCD flickers and comes back and the monitor does nothing. To me, the fact that the LCD flickers sows it's scanning the new layout. The only way I get any type of activity on the external monitor is to invoke the keyboard toggle Fn-F5. But as mentioned, things get ugly fast when I do that.
Here's the output of /var/log/Xorg.0.log which shows the new res settings when I connected the monitor and then again when disconnected.
$ tail /var/log/Xorg.0.log [ 29.942] (**) Option "xkb_rules" "evdev" [ 29.942] (**) Option "xkb_model" "evdev" [ 29.942] (**) Option "xkb_layout" "us" [ 2569.286] (II) intel(0): Allocated new frame buffer 1024x768 stride 4096, tiled [ 2827.193] (II) intel(0): Allocated new frame buffer 2048x768 stride 8192, tiled [ 2864.078] (II) intel(0): Allocated new frame buffer 1280x800 stride 8192, tiled [ 8943.676] (II) intel(0): Allocated new frame buffer 2048x768 stride 8192, tiled [ 8950.486] (II) intel(0): Allocated new frame buffer 1024x768 stride 4096, tiled [ 8950.580] (II) intel(0): Allocated new frame buffer 2048x768 stride 8192, tiled [ 8961.737] (II) intel(0): Allocated new frame buffer 1280x800 stride 8192, tiled
Thanks Phil
On 07/24/2012 04:20 PM, Philippe LeCavalier wrote:
Yeah. It doesn't appear to be a hardware thing. xrandr --auto --output VGA1 --same-as LVDS1 does the same as merely connecting the monitor itself. LCD flickers and comes back and the monitor does nothing. To me, the fact that the LCD flickers sows it's scanning the new layout. The only way I get any type of activity on the external monitor is to invoke the keyboard toggle Fn-F5. But as mentioned, things get ugly fast when I do that.
As far as I can see there's not much more you can do. I think you're looking at a real driver bug that needs reporting and fixing.
Andrew.
On Tue, Jul 24, 2012 at 11:22 AM, Andrew Haley aph@redhat.com wrote:
On 07/24/2012 04:20 PM, Philippe LeCavalier wrote:
Yeah. It doesn't appear to be a hardware thing. xrandr --auto --output VGA1 --same-as LVDS1 does the same as merely connecting the monitor
itself.
LCD flickers and comes back and the monitor does nothing. To me, the fact that the LCD flickers sows it's scanning the new layout. The only way I
get
any type of activity on the external monitor is to invoke the keyboard toggle Fn-F5. But as mentioned, things get ugly fast when I do that.
As far as I can see there's not much more you can do. I think you're looking at a real driver bug that needs reporting and fixing.
Andrew.
Thanks again Andrew.
Alrighty then. To be honest I'm not entirely certain how to do that. As is, what info to collect and to what project would I submit said info!? Sorry. I have little experience in submitting bugs but I'd like to contribute what I can...Sure someone will encounter this that could use the reference. Obviously I wouldn't mind having the fix myself as well ;)
Thanks Phil
On 07/24/2012 06:41 PM, Philippe LeCavalier wrote:
On Tue, Jul 24, 2012 at 11:22 AM, Andrew Haley aph@redhat.com wrote:
On 07/24/2012 04:20 PM, Philippe LeCavalier wrote:
Yeah. It doesn't appear to be a hardware thing. xrandr --auto --output VGA1 --same-as LVDS1 does the same as merely connecting the monitor
itself.
LCD flickers and comes back and the monitor does nothing. To me, the fact that the LCD flickers sows it's scanning the new layout. The only way I
get
any type of activity on the external monitor is to invoke the keyboard toggle Fn-F5. But as mentioned, things get ugly fast when I do that.
As far as I can see there's not much more you can do. I think you're looking at a real driver bug that needs reporting and fixing.
Alrighty then. To be honest I'm not entirely certain how to do that. As is, what info to collect and to what project would I submit said info!? Sorry. I have little experience in submitting bugs but I'd like to contribute what I can...Sure someone will encounter this that could use the reference. Obviously I wouldn't mind having the fix myself as well ;)
http://fedoraproject.org/wiki/Bugzilla
Please just describe the problem. You don't have to type much, because you can just include a URL like this one:
http://lists.fedoraproject.org/pipermail/users/2012-July/422209.html
Thanks, Andrew.
Philippe LeCavalier <support <at> plecavalier.com> writes:
On Thu, Jul 19, 2012 at 9:14 AM, Philippe LeCavalier <support <at>
plecavalier.com> wrote:
Hi Everyone.
...
A yes. The infamous Intel 945 chipset...I waded through the whole sluggish
feel issues of the >2048 res issue. Then an update appeared to have addressed all my issues(no idea which one because the one that was supposed to fix it didn't). ...
So here are the symptoms: if I connect an external monitor(VGA) it won't light
up at all. My LCD flickers and comes back to it's original state. Fine. The display settings reflect that one was connected and typically ids it properly. Again, fine. I then set an appropriate resolution and placement for both and hit apply. At this point the screen flickers again and my laptop comes back but the monitor does nothing(orange light). I can however, bring my cursor passed the LCD to where the monitor "is" but it's not lit so no joy there. If I let the time run out on the dialog everything goes back to normal. No harm no foul. If I play with any of the kbd combo keys to force the external monitor gnome-shell freaks out and I'm forced to recover using the console. The only thing I can successfully accomplish is Fn+F5 resulting in the external monitor only-type setup. Recovering from that without restarting X is not possible. If I toggle back to my LCD the screen flickers and spins. Same goes for disconnecting the VGA cable. At this point I can't go back to the monitor either. I have no choice but to open a console and restart Gnome-Shell. The odd time I can't even do that and must power off(ouch! haven't had to do that in Linux for years)
-- Thanks, Phil
Hi Phil -
I had some similar problems with FC16 on an HP laptop with the i915 chip set. X still starts goofy with an external monitor attached but a simple:
xrandr --output VGA1 --left-of LVDS1
sorts out how much of the display should be on each monitor.
The trivial oddity that I have is that, for some reason, this laptop monitor always comes up at zero brightness. Have you tried adjusting the screen brightness on the laptop once everything is up? I have to wait until X is up for this to work. The text output from booting goes to the external monitor and I can pound on the laptop's screen brightness key and nothing happens. After X starts, it behaves as expected. This drove me nuts getting FC16 working since there weren't any errors; just no display.
I'm running FC16 from a bootable, external hard disk. The i915 laptop is in my office and I have an older HP laptop with an ATI chipset at home. I boot the home laptop from the external hard disk and the display is duplicated until X starts and then I get the same slightly goofy overlap I see on my work laptop. A slightly different xrandr (xrandr --output VGA-0 --left-of LVDS) sorts out those displays.
A couple of other suggestions are to turn off graphical boot and quiet mode so you can see what's going on as the system boots. Also, switch to booting in the equivalent to runlevel 3 (multiuser target) and then start X from the command line with startx.
Cheers, Dave
On Tue, Jul 24, 2012 at 4:46 PM, David G. Miller dave@davenjudy.org wrote:
Philippe LeCavalier <support <at> plecavalier.com> writes:
On Thu, Jul 19, 2012 at 9:14 AM, Philippe LeCavalier <support <at>
plecavalier.com> wrote:
Hi Everyone.
...
A yes. The infamous Intel 945 chipset...I waded through the whole
sluggish feel issues of the >2048 res issue. Then an update appeared to have addressed all my issues(no idea which one because the one that was supposed to fix it didn't). ...
So here are the symptoms: if I connect an external monitor(VGA) it won't
light up at all. My LCD flickers and comes back to it's original state. Fine. The display settings reflect that one was connected and typically ids it properly. Again, fine. I then set an appropriate resolution and placement for both and hit apply. At this point the screen flickers again and my laptop comes back but the monitor does nothing(orange light). I can however, bring my cursor passed the LCD to where the monitor "is" but it's not lit so no joy there. If I let the time run out on the dialog everything goes back to normal. No harm no foul. If I play with any of the kbd combo keys to force the external monitor gnome-shell freaks out and I'm forced to recover using the console. The only thing I can successfully accomplish is Fn+F5 resulting in the external monitor only-type setup. Recovering from that without restarting X is not possible. If I toggle back to my LCD the screen flickers and spins. Same goes for disconnecting the VGA cable. At this point I can't go back to the monitor either. I have no choice but to open a console and restart Gnome-Shell. The odd time I can't even do that and must power off(ouch! haven't had to do that in Linux for years)
-- Thanks, Phil
Hi Phil -
I had some similar problems with FC16 on an HP laptop with the i915 chip set. X still starts goofy with an external monitor attached but a simple:
xrandr --output VGA1 --left-of LVDS1
sorts out how much of the display should be on each monitor.
The trivial oddity that I have is that, for some reason, this laptop monitor always comes up at zero brightness. Have you tried adjusting the screen brightness on the laptop once everything is up? I have to wait until X is up for this to work. The text output from booting goes to the external monitor and I can pound on the laptop's screen brightness key and nothing happens. After X starts, it behaves as expected. This drove me nuts getting FC16 working since there weren't any errors; just no display.
I'm running FC16 from a bootable, external hard disk. The i915 laptop is in my office and I have an older HP laptop with an ATI chipset at home. I boot the home laptop from the external hard disk and the display is duplicated until X starts and then I get the same slightly goofy overlap I see on my work laptop. A slightly different xrandr (xrandr --output VGA-0 --left-of LVDS) sorts out those displays.
A couple of other suggestions are to turn off graphical boot and quiet mode so you can see what's going on as the system boots. Also, switch to booting in the equivalent to runlevel 3 (multiuser target) and then start X from the command line with startx.
Cheers, Dave
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Thanks Dave! your suggestions haven't lead to a solution (yet) but I finally, finally found an error msg I can report back...
When I connect the monitor I get this[4] and this[5]. Hopefully this gives someone the proverbial light bulb effect. All it tells me is that well, the monitor isn't powering on, which I already knew all too well ;) Just to reiterate, I can force the external on with the kbd shortcut but the results are that I loose my LCD. The goal here is achieving dual display and not just external. btw there are more EDID errors just don't know if they're relevant or not.
Do we thinks me have enough to post a bug or do me needs more nfo?
references(seem to have lost me original refs...anyway): [4][drm:intel_lvds_enable] *ERROR* timed out waiting for panel to power on [5][drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 16
On Thu, Jul 26, 2012 at 8:23 AM, Philippe LeCavalier < support@plecavalier.com> wrote:
On Tue, Jul 24, 2012 at 4:46 PM, David G. Miller dave@davenjudy.orgwrote:
Philippe LeCavalier <support <at> plecavalier.com> writes:
On Thu, Jul 19, 2012 at 9:14 AM, Philippe LeCavalier <support <at>
plecavalier.com> wrote:
Hi Everyone.
...
A yes. The infamous Intel 945 chipset...I waded through the whole
sluggish feel issues of the >2048 res issue. Then an update appeared to have addressed all my issues(no idea which one because the one that was supposed to fix it didn't). ...
So here are the symptoms: if I connect an external monitor(VGA) it
won't light up at all. My LCD flickers and comes back to it's original state. Fine. The display settings reflect that one was connected and typically ids it properly. Again, fine. I then set an appropriate resolution and placement for both and hit apply. At this point the screen flickers again and my laptop comes back but the monitor does nothing(orange light). I can however, bring my cursor passed the LCD to where the monitor "is" but it's not lit so no joy there. If I let the time run out on the dialog everything goes back to normal. No harm no foul. If I play with any of the kbd combo keys to force the external monitor gnome-shell freaks out and I'm forced to recover using the console. The only thing I can successfully accomplish is Fn+F5 resulting in the external monitor only-type setup. Recovering from that without restarting X is not possible. If I toggle back to my LCD the screen flickers and spins. Same goes for disconnecting the VGA cable. At this point I can't go back to the monitor either. I have no choice but to open a console and restart Gnome-Shell. The odd time I can't even do that and must power off(ouch! haven't had to do that in Linux for years)
-- Thanks, Phil
Hi Phil -
I had some similar problems with FC16 on an HP laptop with the i915 chip set. X still starts goofy with an external monitor attached but a simple:
xrandr --output VGA1 --left-of LVDS1
sorts out how much of the display should be on each monitor.
The trivial oddity that I have is that, for some reason, this laptop monitor always comes up at zero brightness. Have you tried adjusting the screen brightness on the laptop once everything is up? I have to wait until X is up for this to work. The text output from booting goes to the external monitor and I can pound on the laptop's screen brightness key and nothing happens. After X starts, it behaves as expected. This drove me nuts getting FC16 working since there weren't any errors; just no display.
I'm running FC16 from a bootable, external hard disk. The i915 laptop is in my office and I have an older HP laptop with an ATI chipset at home. I boot the home laptop from the external hard disk and the display is duplicated until X starts and then I get the same slightly goofy overlap I see on my work laptop. A slightly different xrandr (xrandr --output VGA-0 --left-of LVDS) sorts out those displays.
A couple of other suggestions are to turn off graphical boot and quiet mode so you can see what's going on as the system boots. Also, switch to booting in the equivalent to runlevel 3 (multiuser target) and then start X from the command line with startx.
Cheers, Dave
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Thanks Dave! your suggestions haven't lead to a solution (yet) but I finally, finally found an error msg I can report back...
When I connect the monitor I get this[4] and this[5]. Hopefully this gives someone the proverbial light bulb effect. All it tells me is that well, the monitor isn't powering on, which I already knew all too well ;) Just to reiterate, I can force the external on with the kbd shortcut but the results are that I loose my LCD. The goal here is achieving dual display and not just external. btw there are more EDID errors just don't know if they're relevant or not.
Do we thinks me have enough to post a bug or do me needs more nfo?
filed this[6] today. We'll see what comes form it.
references(seem to have lost me original refs...anyway): [4][drm:intel_lvds_enable] *ERROR* timed out waiting for panel to power on [5][drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 16
[6] Bug 846365 https://bugzilla.redhat.com/show_bug.cgi?id=846365
On Tue, Aug 7, 2012 at 10:57 AM, Philippe LeCavalier < support@plecavalier.com> wrote:
On Thu, Jul 26, 2012 at 8:23 AM, Philippe LeCavalier < support@plecavalier.com> wrote:
On Tue, Jul 24, 2012 at 4:46 PM, David G. Miller dave@davenjudy.orgwrote:
Philippe LeCavalier <support <at> plecavalier.com> writes:
On Thu, Jul 19, 2012 at 9:14 AM, Philippe LeCavalier <support <at>
plecavalier.com> wrote:
Hi Everyone.
...
A yes. The infamous Intel 945 chipset...I waded through the whole
sluggish feel issues of the >2048 res issue. Then an update appeared to have addressed all my issues(no idea which one because the one that was supposed to fix it didn't). ...
So here are the symptoms: if I connect an external monitor(VGA) it
won't light up at all. My LCD flickers and comes back to it's original state. Fine. The display settings reflect that one was connected and typically ids it properly. Again, fine. I then set an appropriate resolution and placement for both and hit apply. At this point the screen flickers again and my laptop comes back but the monitor does nothing(orange light). I can however, bring my cursor passed the LCD to where the monitor "is" but it's not lit so no joy there. If I let the time run out on the dialog everything goes back to normal. No harm no foul. If I play with any of the kbd combo keys to force the external monitor gnome-shell freaks out and I'm forced to recover using the console. The only thing I can successfully accomplish is Fn+F5 resulting in the external monitor only-type setup. Recovering from that without restarting X is not possible. If I toggle back to my LCD the screen flickers and spins. Same goes for disconnecting the VGA cable. At this point I can't go back to the monitor either. I have no choice but to open a console and restart Gnome-Shell. The odd time I can't even do that and must power off(ouch! haven't had to do that in Linux for years)
-- Thanks, Phil
Hi Phil -
I had some similar problems with FC16 on an HP laptop with the i915 chip set. X still starts goofy with an external monitor attached but a simple:
xrandr --output VGA1 --left-of LVDS1
sorts out how much of the display should be on each monitor.
The trivial oddity that I have is that, for some reason, this laptop monitor always comes up at zero brightness. Have you tried adjusting the screen brightness on the laptop once everything is up? I have to wait until X is up for this to work. The text output from booting goes to the external monitor and I can pound on the laptop's screen brightness key and nothing happens. After X starts, it behaves as expected. This drove me nuts getting FC16 working since there weren't any errors; just no display.
I'm running FC16 from a bootable, external hard disk. The i915 laptop is in my office and I have an older HP laptop with an ATI chipset at home. I boot the home laptop from the external hard disk and the display is duplicated until X starts and then I get the same slightly goofy overlap I see on my work laptop. A slightly different xrandr (xrandr --output VGA-0 --left-of LVDS) sorts out those displays.
A couple of other suggestions are to turn off graphical boot and quiet mode so you can see what's going on as the system boots. Also, switch to booting in the equivalent to runlevel 3 (multiuser target) and then start X from the command line with startx.
Cheers, Dave
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Thanks Dave! your suggestions haven't lead to a solution (yet) but I finally, finally found an error msg I can report back...
When I connect the monitor I get this[4] and this[5]. Hopefully this gives someone the proverbial light bulb effect. All it tells me is that well, the monitor isn't powering on, which I already knew all too well ;) Just to reiterate, I can force the external on with the kbd shortcut but the results are that I loose my LCD. The goal here is achieving dual display and not just external. btw there are more EDID errors just don't know if they're relevant or not.
Do we thinks me have enough to post a bug or do me needs more nfo?
filed this[6] today. We'll see what comes form it.
references(seem to have lost me original refs...anyway): [4][drm:intel_lvds_enable] *ERROR* timed out waiting for panel to power on [5][drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 16
[6] Bug 846365 https://bugzilla.redhat.com/show_bug.cgi?id=846365
Just upgraded to kernel 3.5+ and finally my external monitor works! I'm still stuck within 2048 horizontally but at this point I'm okay with that ;)
Phil
-
Andrew Haley -
David G. Miller (aka DaveAtFraud) -
Mark Haney -
Philippe LeCavalier