Dell E6510 Video issues
9 views
Skip to first unread message
Robison, Dave
Jan 21, 2015, 4:16:09 PM1/21/15
to
Hiya,
I've taken this to the PCBSD and FreeBSD forums but nobody responds so I'm hoping someone will at least point me in the right direction.
I'm running PCBSD 10.1. My Dell Latitude E6510 uses the Intel agp0 Ironlake chip and as recently as PCBSD 10.0, it worked find when the laptop is docked and I'm using my external monitor (HDMI).
Now, however, I can only do this in VESA mode. When I boot with the Intel driver, the screen will go black, with a white cursor in the upper leftmost corner and my mouse pointer will freeze toward that corner. Works fine in either mode if I'm not docked.
I assume this is a problem with Xorg though perhaps it's the new vt(4). At any rate, I'm wondering where to start looking.
I booted normally, let it fail, then booted VESA and have an xorg.0.log.old.
For the entire log, please check this link:
https://forums.freebsd.org/threads/xorg-on-dell-latitude-e6510.49868/
--
Dave Robison
Sales Solution Architect II
FIS Banking Solutions
510/621-2089 (w)
530/518-5194 (c)
510/621-2020 (f)
da...@vicor.com
david....@fisglobal.com
_____________
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "freebsd-mobil...@freebsd.org"
I've taken this to the PCBSD and FreeBSD forums but nobody responds so I'm hoping someone will at least point me in the right direction.
I'm running PCBSD 10.1. My Dell Latitude E6510 uses the Intel agp0 Ironlake chip and as recently as PCBSD 10.0, it worked find when the laptop is docked and I'm using my external monitor (HDMI).
Now, however, I can only do this in VESA mode. When I boot with the Intel driver, the screen will go black, with a white cursor in the upper leftmost corner and my mouse pointer will freeze toward that corner. Works fine in either mode if I'm not docked.
I assume this is a problem with Xorg though perhaps it's the new vt(4). At any rate, I'm wondering where to start looking.
I booted normally, let it fail, then booted VESA and have an xorg.0.log.old.
For the entire log, please check this link:
https://forums.freebsd.org/threads/xorg-on-dell-latitude-e6510.49868/
--
Dave Robison
Sales Solution Architect II
FIS Banking Solutions
510/621-2089 (w)
530/518-5194 (c)
510/621-2020 (f)
da...@vicor.com
david....@fisglobal.com
_____________
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "freebsd-mobil...@freebsd.org"
Robison, Dave
Jan 21, 2015, 5:52:46 PM1/21/15
to
Howdy,
This worked fine in PCBSD 8, 9, and 10. Now it's no longer working as of 10.1 or thereabouts...
On 01/21/2015 14:45, Adrian Chadd wrote:
> hi,
>
> freebsd's dri i915kms code doesn't yet support haswell or later,w hich
> I believe includes ironlake.
>
>
> -a
> freebsd...@freebsd.org mailing list
> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.freebsd.org_mailman_listinfo_freebsd-2Dmobile&d=AAICAg&c=3BfiSO86x5iKjpl2b39jud9R1NrKYqPq2js90dwBswk&r=xejns4hCLY4pkxk_Fns5Pg&m=D2ev6u5XDxKTokYIOTU5ZfOcKIO_EK0TLRXrm4Oqwyw&s=DlbAOw7g3984oBahDR0pLznNZK7mm7FKbubKWARvNT8&e=
This worked fine in PCBSD 8, 9, and 10. Now it's no longer working as of 10.1 or thereabouts...
On 01/21/2015 14:45, Adrian Chadd wrote:
> hi,
>
> freebsd's dri i915kms code doesn't yet support haswell or later,w hich
> I believe includes ironlake.
>
>
> -a
>
>
> On 21 January 2015 at 13:07, Robison, Dave <david....@fisglobal.com> wrote:
>> Hiya,
>>
>> I've taken this to the PCBSD and FreeBSD forums but nobody responds so I'm hoping someone will at least point me in the right direction.
>>
>> I'm running PCBSD 10.1. My Dell Latitude E6510 uses the Intel agp0 Ironlake chip and as recently as PCBSD 10.0, it worked find when the laptop is docked and I'm using my external monitor (HDMI).
>>
>> Now, however, I can only do this in VESA mode. When I boot with the Intel driver, the screen will go black, with a white cursor in the upper leftmost corner and my mouse pointer will freeze toward that corner. Works fine in either mode if I'm not docked.
>>
>> I assume this is a problem with Xorg though perhaps it's the new vt(4). At any rate, I'm wondering where to start looking.
>>
>> I booted normally, let it fail, then booted VESA and have an xorg.0.log.old.
>>
>> For the entire log, please check this link:
>>
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__forums.freebsd.org_threads_xorg-2Don-2Ddell-2Dlatitude-2De6510.49868_&d=AAICAg&c=3BfiSO86x5iKjpl2b39jud9R1NrKYqPq2js90dwBswk&r=xejns4hCLY4pkxk_Fns5Pg&m=D2ev6u5XDxKTokYIOTU5ZfOcKIO_EK0TLRXrm4Oqwyw&s=_c7Scd47YZWuifpxu7th0PObWZM3TNecua6n7mXZ2Fs&e=
>
> On 21 January 2015 at 13:07, Robison, Dave <david....@fisglobal.com> wrote:
>> Hiya,
>>
>> I've taken this to the PCBSD and FreeBSD forums but nobody responds so I'm hoping someone will at least point me in the right direction.
>>
>> I'm running PCBSD 10.1. My Dell Latitude E6510 uses the Intel agp0 Ironlake chip and as recently as PCBSD 10.0, it worked find when the laptop is docked and I'm using my external monitor (HDMI).
>>
>> Now, however, I can only do this in VESA mode. When I boot with the Intel driver, the screen will go black, with a white cursor in the upper leftmost corner and my mouse pointer will freeze toward that corner. Works fine in either mode if I'm not docked.
>>
>> I assume this is a problem with Xorg though perhaps it's the new vt(4). At any rate, I'm wondering where to start looking.
>>
>> I booted normally, let it fail, then booted VESA and have an xorg.0.log.old.
>>
>> For the entire log, please check this link:
>>
>>
>>
>>
>>
>> --
>> Dave Robison
>> Sales Solution Architect II
>> FIS Banking Solutions
>> 510/621-2089 (w)
>> 530/518-5194 (c)
>> 510/621-2020 (f)
>> da...@vicor.com
>> david....@fisglobal.com
>>
>> _____________
>> The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
>> _______________________________________________
>> freebsd...@freebsd.org mailing list
>> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.freebsd.org_mailman_listinfo_freebsd-2Dmobile&d=AAICAg&c=3BfiSO86x5iKjpl2b39jud9R1NrKYqPq2js90dwBswk&r=xejns4hCLY4pkxk_Fns5Pg&m=D2ev6u5XDxKTokYIOTU5ZfOcKIO_EK0TLRXrm4Oqwyw&s=DlbAOw7g3984oBahDR0pLznNZK7mm7FKbubKWARvNT8&e=
>>
>>
>>
>> --
>> Dave Robison
>> Sales Solution Architect II
>> FIS Banking Solutions
>> 510/621-2089 (w)
>> 530/518-5194 (c)
>> 510/621-2020 (f)
>> da...@vicor.com
>> david....@fisglobal.com
>>
>> _____________
>> The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
>> _______________________________________________
>> freebsd...@freebsd.org mailing list
>> To unsubscribe, send any mail to "freebsd-mobil...@freebsd.org"
> _______________________________________________
> freebsd...@freebsd.org mailing list
> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.freebsd.org_mailman_listinfo_freebsd-2Dmobile&d=AAICAg&c=3BfiSO86x5iKjpl2b39jud9R1NrKYqPq2js90dwBswk&r=xejns4hCLY4pkxk_Fns5Pg&m=D2ev6u5XDxKTokYIOTU5ZfOcKIO_EK0TLRXrm4Oqwyw&s=DlbAOw7g3984oBahDR0pLznNZK7mm7FKbubKWARvNT8&e=
Adrian Chadd
Jan 21, 2015, 5:59:48 PM1/21/15
to
It's likely the updated xorg and pulling in update dri code and using
dri2. That all happened around that timeframe.
-a
dri2. That all happened around that timeframe.
-a
Adrian Chadd
Jan 21, 2015, 6:11:02 PM1/21/15
to
hi,
freebsd's dri i915kms code doesn't yet support haswell or later,w hich
I believe includes ironlake.
-a
On 21 January 2015 at 13:07, Robison, Dave <david....@fisglobal.com> wrote:
> Hiya,
>
> I've taken this to the PCBSD and FreeBSD forums but nobody responds so I'm hoping someone will at least point me in the right direction.
>
> I'm running PCBSD 10.1. My Dell Latitude E6510 uses the Intel agp0 Ironlake chip and as recently as PCBSD 10.0, it worked find when the laptop is docked and I'm using my external monitor (HDMI).
>
> Now, however, I can only do this in VESA mode. When I boot with the Intel driver, the screen will go black, with a white cursor in the upper leftmost corner and my mouse pointer will freeze toward that corner. Works fine in either mode if I'm not docked.
>
> I assume this is a problem with Xorg though perhaps it's the new vt(4). At any rate, I'm wondering where to start looking.
>
> I booted normally, let it fail, then booted VESA and have an xorg.0.log.old.
>
> For the entire log, please check this link:
>
> https://forums.freebsd.org/threads/xorg-on-dell-latitude-e6510.49868/
freebsd's dri i915kms code doesn't yet support haswell or later,w hich
I believe includes ironlake.
-a
On 21 January 2015 at 13:07, Robison, Dave <david....@fisglobal.com> wrote:
> Hiya,
>
> I've taken this to the PCBSD and FreeBSD forums but nobody responds so I'm hoping someone will at least point me in the right direction.
>
> I'm running PCBSD 10.1. My Dell Latitude E6510 uses the Intel agp0 Ironlake chip and as recently as PCBSD 10.0, it worked find when the laptop is docked and I'm using my external monitor (HDMI).
>
> Now, however, I can only do this in VESA mode. When I boot with the Intel driver, the screen will go black, with a white cursor in the upper leftmost corner and my mouse pointer will freeze toward that corner. Works fine in either mode if I'm not docked.
>
> I assume this is a problem with Xorg though perhaps it's the new vt(4). At any rate, I'm wondering where to start looking.
>
> I booted normally, let it fail, then booted VESA and have an xorg.0.log.old.
>
> For the entire log, please check this link:
>
Robison, Dave
Jan 21, 2015, 6:41:01 PM1/21/15
to
On 01/21/2015 14:59, Adrian Chadd wrote:
> It's likely the updated xorg and pulling in update dri code and using
> dri2. That all happened around that timeframe.
>
This is my suspicion as well. And I also suspect I may be the only FreeBSD user on the planet who has run into this problem.
> It's likely the updated xorg and pulling in update dri code and using
> dri2. That all happened around that timeframe.
>
Where should I take this to push it upstream? Obviously it's not a critical problem but I'd like to have it resolved so I can stop using VESA.
Adrian Chadd
Jan 21, 2015, 7:09:49 PM1/21/15
to
It's being worked on by the graphics team. They're all volunteers, so
I don't know if there's a timeline for when they plan on having
everything updated to the latest Linux code.
-adrian
I don't know if there's a timeline for when they plan on having
everything updated to the latest Linux code.
-adrian
Lundberg, Johannes
Jan 21, 2015, 9:26:03 PM1/21/15
to
I thought the foundation is sponsoring the graphics stack update? If not,
I wish they could if that would speed up the portability with modern
laptops...
I wish they could if that would speed up the portability with modern
laptops...
--
Johannes Lundberg
BRILLIANTSERVICE CO., LTD.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
秘密保持について：この電子メールは、名宛人に送信したものであり、秘匿特権の対象となる情報を含んでいます。
もし、名宛人以外の方が受信された場合、このメールの破棄、およびこのメールに関する一切の開示、
複写、配布、その他の利用、または記載内容に基づくいかなる行動もされないようお願い申し上げます。
---
CONFIDENTIALITY NOTE: The information in this email is confidential
and intended solely for the addressee.
Disclosure, copying, distribution or any other action of use of this
email by person other than intended recipient, is prohibited.
If you are not the intended recipient and have received this email in
error, please destroy the original message.
Bengt Ahlgren
Jan 22, 2015, 4:32:10 AM1/22/15
to
Just for the record: Ironlake is quite a lot older. I have the same in
my ThinkPad X201, which has been working pretty well for some time now,
also with HDMI from a dock. I however run 9.3-STABLE (with the new
console).
To the OP: there is a newer xorg-server in the latest ports tree that
you may want to try:
xorg-server-1.14.7_1,1
Bengt
Adrian Chadd <adr...@freebsd.org> writes:
> hi,
>
> freebsd's dri i915kms code doesn't yet support haswell or later,w hich
> I believe includes ironlake.
>
>
> -a
>
>
> On 21 January 2015 at 13:07, Robison, Dave <david....@fisglobal.com> wrote:
>> Hiya,
>>
>> I've taken this to the PCBSD and FreeBSD forums but nobody responds
>> so I'm hoping someone will at least point me in the right direction.
>>
>> I'm running PCBSD 10.1. My Dell Latitude E6510 uses the Intel agp0
>> Ironlake chip and as recently as PCBSD 10.0, it worked find when the
>> laptop is docked and I'm using my external monitor (HDMI).
>>
>> Now, however, I can only do this in VESA mode. When I boot with the
>> Intel driver, the screen will go black, with a white cursor in the
>> upper leftmost corner and my mouse pointer will freeze toward that
>> corner. Works fine in either mode if I'm not docked.
>>
>> I assume this is a problem with Xorg though perhaps it's the new
>> vt(4). At any rate, I'm wondering where to start looking.
>>
>> I booted normally, let it fail, then booted VESA and have an xorg.0.log.old.
>>
>> For the entire log, please check this link:
>>
>> https://forums.freebsd.org/threads/xorg-on-dell-latitude-e6510.49868/
>>
>>
>>
>>
my ThinkPad X201, which has been working pretty well for some time now,
also with HDMI from a dock. I however run 9.3-STABLE (with the new
console).
To the OP: there is a newer xorg-server in the latest ports tree that
you may want to try:
xorg-server-1.14.7_1,1
Bengt
Adrian Chadd <adr...@freebsd.org> writes:
> hi,
>
> freebsd's dri i915kms code doesn't yet support haswell or later,w hich
> I believe includes ironlake.
>
>
> -a
>
>
> On 21 January 2015 at 13:07, Robison, Dave <david....@fisglobal.com> wrote:
>> Hiya,
>>
>> I've taken this to the PCBSD and FreeBSD forums but nobody responds
>> so I'm hoping someone will at least point me in the right direction.
>>
>> I'm running PCBSD 10.1. My Dell Latitude E6510 uses the Intel agp0
>> Ironlake chip and as recently as PCBSD 10.0, it worked find when the
>> laptop is docked and I'm using my external monitor (HDMI).
>>
>> Now, however, I can only do this in VESA mode. When I boot with the
>> Intel driver, the screen will go black, with a white cursor in the
>> upper leftmost corner and my mouse pointer will freeze toward that
>> corner. Works fine in either mode if I'm not docked.
>>
>> I assume this is a problem with Xorg though perhaps it's the new
>> vt(4). At any rate, I'm wondering where to start looking.
>>
>> I booted normally, let it fail, then booted VESA and have an xorg.0.log.old.
>>
>> For the entire log, please check this link:
>>
>> https://forums.freebsd.org/threads/xorg-on-dell-latitude-e6510.49868/
>>
>>
>>
>>
Gerd Hafenbrack
Jan 22, 2015, 4:32:39 AM1/22/15
to
On 2015-01-21 23:45, Adrian Chadd wrote:
> ... haswell or later, which I believe includes ironlake.
No!
Ironlake was released around 2010. Haswell was released 2013.
> ... haswell or later, which I believe includes ironlake.
No!
Ironlake was released around 2010. Haswell was released 2013.
Adrian Chadd
Jan 22, 2015, 12:19:42 PM1/22/15
to
Ah!
Ok, then poke the x11 team. It may be something to do with the x side of things.
What's the output of "xrandr" on each install? That'll list the known
output devices.
-a
Ok, then poke the x11 team. It may be something to do with the x side of things.
What's the output of "xrandr" on each install? That'll list the known
output devices.
-a
Robison, Dave
Jan 22, 2015, 3:30:31 PM1/22/15
to
Hiya,
I received an email from a non-list subscriber who uses the same laptop and docking station.
At his suggestion I disabled the new VT in /boot/loader.conf.pcbsd, then remade grub with:
grub-mkconfig -o /boot/grub/grub.cfg
Rebooted and ran the PCBSD Display Manger and I am back up on the intel driver at 1900x1200.
Why the new VT and the intel driver do not play nicely together is a mystery to me.
I believe any FreeBSD user could simply disable the new VT in /boot/loader.conf to accomplish the same thing. The option is:
kern.vty=vt
Dave
--
Dave Robison
Sales Solution Architect II
FIS Banking Solutions
510/621-2089 (w)
530/518-5194 (c)
510/621-2020 (f)
da...@vicor.com
david....@fisglobal.com
_____________
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
I received an email from a non-list subscriber who uses the same laptop and docking station.
At his suggestion I disabled the new VT in /boot/loader.conf.pcbsd, then remade grub with:
grub-mkconfig -o /boot/grub/grub.cfg
Rebooted and ran the PCBSD Display Manger and I am back up on the intel driver at 1900x1200.
Why the new VT and the intel driver do not play nicely together is a mystery to me.
I believe any FreeBSD user could simply disable the new VT in /boot/loader.conf to accomplish the same thing. The option is:
kern.vty=vt
Dave
--
Dave Robison
Sales Solution Architect II
FIS Banking Solutions
510/621-2089 (w)
530/518-5194 (c)
510/621-2020 (f)
da...@vicor.com
david....@fisglobal.com
_____________
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
Adrian Chadd
Jan 22, 2015, 6:13:11 PM1/22/15
to
riyas...@gmail.com
Mar 16, 2017, 5:40:08 AM3/16/17
to
Reply all
Reply to author
Forward
0 new messages