On Friday, February 19, 2016 06:38:27 PM Alexey Dokuchaev wrote:
> On Thu, Feb 18, 2016 at 09:51:08AM -0800, John Baldwin wrote:
> > On Thursday, February 18, 2016 10:56:29 PM Alexey Dokuchaev wrote:
> > > # pciconf -lc pci0:0:0
> > > hostb0@pci0:0:0:0: class=0x06 card=0x83191033 chip=0x25
On 18/02/2016 16:47, Alexey Dokuchaev wrote:
> On a related note, how does one configure sc(4) with old drm (vs.
> drm2) shall I need to try that?
Hi!
xf86-video-intel and xf86-video-ati do not handle modesetting for a long
time now (almost three years), so they can't be used with the old "drm"
(
On Thu, Feb 18, 2016 at 09:51:08AM -0800, John Baldwin wrote:
> On Thursday, February 18, 2016 10:56:29 PM Alexey Dokuchaev wrote:
> > # pciconf -lc pci0:0:0
> > hostb0@pci0:0:0:0: class=0x06 card=0x83191033 chip=0x25908086
> > rev=0x04 hdr=0x00
> > cap 09[e0] = vendor (length 9) Inte
On Thu, Feb 18, 2016 at 10:02:17AM -0800, Adrian Chadd wrote:
> [snip]
>
> Someone should sit me down with pizza and "help" me just modularise
> the vesa/fb code so we can use it in vt.
>
> It isn't /that/ hard, I've just been preoccupied.
And before it happens, someone(tm) could write a few par
On Thu, Feb 18, 2016 at 09:48:40AM -0800, John Baldwin wrote:
> On Thursday, February 18, 2016 09:47:12 PM Alexey Dokuchaev wrote:
> > On Thu, Feb 18, 2016 at 06:50:34AM -0800, John Baldwin wrote:
> > > On Thursday, February 18, 2016 08:13:38 PM Alexey Dokuchaev wrote:
> > > vesa.ko shouldn't be wo
[snip]
Someone should sit me down with pizza and "help" me just modularise
the vesa/fb code so we can use it in vt.
It isn't /that/ hard, I've just been preoccupied.
-a
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/lis
On Thursday, February 18, 2016 10:56:29 PM Alexey Dokuchaev wrote:
> On Thu, Feb 18, 2016 at 06:55:03AM -0800, John Baldwin wrote:
> > On Thursday, February 18, 2016 08:37:38 PM Alexey Dokuchaev wrote:
> > > I've started to observe similar lines in the logs after updating to
> > > fresh -CURRENT, u
On Thursday, February 18, 2016 09:47:12 PM Alexey Dokuchaev wrote:
> On Thu, Feb 18, 2016 at 06:50:34AM -0800, John Baldwin wrote:
> > On Thursday, February 18, 2016 08:13:38 PM Alexey Dokuchaev wrote:
> > vesa.ko shouldn't be working with KMS. KMS turns off the legacy VGA
> > emulation in the har
On Thu, Feb 18, 2016 at 06:55:03AM -0800, John Baldwin wrote:
> On Thursday, February 18, 2016 08:37:38 PM Alexey Dokuchaev wrote:
> > I've started to observe similar lines in the logs after updating to
> > fresh -CURRENT, upon resume (on a different laptop though, not T410):
> >
> > pcib0: fail
On Thu, Feb 18, 2016 at 06:50:34AM -0800, John Baldwin wrote:
> On Thursday, February 18, 2016 08:13:38 PM Alexey Dokuchaev wrote:
> > On Sat, May 17, 2014 at 08:20:03AM -0400, John Baldwin wrote:
> > > VESA needs to be removed for i915kms, but I've no idea if it needs to be
> > > removed for Nvidi
On Fri, May 23, 2014 at 10:00:30AM -0400, John Baldwin wrote:
> On Wednesday, May 21, 2014 3:43:49 pm Jan Henrik Sylvester wrote:
> > Looking through dmesg, it seems that other USB devices (build-in) are
> > reappearing (Qualcomm Gobi 2000, Broadcom Bluetooth Device) after
> > resume, just not the
On Thursday, February 18, 2016 08:13:38 PM Alexey Dokuchaev wrote:
> On Sat, May 17, 2014 at 08:20:03AM -0400, John Baldwin wrote:
> > VESA needs to be removed for i915kms, but I've no idea if it needs to be
> > removed for Nvidia. The video reset code was reworked in 10 so that
> > having VESA is
On Thursday, February 18, 2016 08:37:38 PM Alexey Dokuchaev wrote:
> On Fri, May 23, 2014 at 10:00:30AM -0400, John Baldwin wrote:
> > On Wednesday, May 21, 2014 3:43:49 pm Jan Henrik Sylvester wrote:
> > > Looking through dmesg, it seems that other USB devices (build-in) are
> > > reappearing (Qua
On Wednesday, May 21, 2014 3:43:49 pm Jan Henrik Sylvester wrote:
> On 05/21/2014 21:22, Hans Petter Selasky wrote:
> > On 05/21/14 21:16, Jan Henrik Sylvester wrote:
> >> Unfortunately, my USB mouse does not work anymore: After the first
> >> resume, it took a few seconds until it worked again (th
On 21.05.2014 21:43, Jan Henrik Sylvester wrote:
> On 05/21/2014 21:22, Hans Petter Selasky wrote:
>> On 05/21/14 21:16, Jan Henrik Sylvester wrote:
>>> Unfortunately, my USB mouse does not work anymore: After the first
>>> resume, it took a few seconds until it worked again (the build in
>>> touch
On Wed, May 21, 2014 at 12:43 PM, Jan Henrik Sylvester wrote:
> On 05/21/2014 21:22, Hans Petter Selasky wrote:
> > On 05/21/14 21:16, Jan Henrik Sylvester wrote:
> >> Unfortunately, my USB mouse does not work anymore: After the first
> >> resume, it took a few seconds until it worked again (the
On 05/21/2014 21:22, Hans Petter Selasky wrote:
> On 05/21/14 21:16, Jan Henrik Sylvester wrote:
>> Unfortunately, my USB mouse does not work anymore: After the first
>> resume, it took a few seconds until it worked again (the build in
>> touchpad was back immediately). After the second resume, it
On 05/21/14 21:16, Jan Henrik Sylvester wrote:
Unfortunately, my USB mouse does not work anymore: After the first
resume, it took a few seconds until it worked again (the build in
touchpad was back immediately). After the second resume, it would not
work anymore at all, even after reconnecting it
On 05/17/2014 14:20, John Baldwin wrote:
> On 5/16/14, 2:10 PM, Kevin Oberman wrote:
>> On Fri, May 16, 2014 at 10:44 AM, Adrian Chadd wrote:
>>
>>> Hi!
>>>
>>> I wonder what changed between 9.2-RELEASE and 10.0-RELEASE.
>>>
>>> Please poke me about this next week. I'm busy this week with work and
On 17.05.2014 14:20, John Baldwin wrote:
> On 5/16/14, 2:10 PM, Kevin Oberman wrote:
>> On Fri, May 16, 2014 at 10:44 AM, Adrian Chadd wrote:
>>
>>> Hi!
>>>
>>> I wonder what changed between 9.2-RELEASE and 10.0-RELEASE.
>>>
>>> Please poke me about this next week. I'm busy this week with work and
On 5/16/14, 2:10 PM, Kevin Oberman wrote:
> On Fri, May 16, 2014 at 10:44 AM, Adrian Chadd wrote:
>
>> Hi!
>>
>> I wonder what changed between 9.2-RELEASE and 10.0-RELEASE.
>>
>> Please poke me about this next week. I'm busy this week with work and
>> maker faire but I will try to help you later.
On 17.05.2014 01:39, Adrian Chadd wrote:
> Hm, okay. i wonder how we can diagnose this further.
>
> Do you have a video monitor? Can you try doing a suspend/resume with
> an external VGA screen attached?
I booted with VGA as primary (and only) monitor. No real changes. The
external monitor also r
Hm, okay. i wonder how we can diagnose this further.
Do you have a video monitor? Can you try doing a suspend/resume with
an external VGA screen attached? Or connect it via ethernet and do a
suspend/resume whilst logged in?
-a
On 16 May 2014 14:31, Stefan Ehmann wrote:
> On 16.05.2014 22:51,
On 16.05.2014 22:51, Adrian Chadd wrote:
> Hi,
>
> Yeah. I'd really suggest trying with stable/10 or -HEAD with vt
> enabled and no VESA.
Thanks for all replies.
Using vt is definitely an improvement, but not perfect. (I've set
hw.vga.textmode=1 because graphics mode is very slow. Don't know if
Hi,
Yeah. I'd really suggest trying with stable/10 or -HEAD with vt
enabled and no VESA.
-a
On 16 May 2014 13:31, Jan Henrik Sylvester wrote:
> On 05/16/2014 20:10, Kevin Oberman wrote:
>> On Fri, May 16, 2014 at 10:44 AM, Adrian Chadd wrote:
>>
>>> Hi!
>>>
>>> I wonder what changed between
On 05/16/2014 20:10, Kevin Oberman wrote:
> On Fri, May 16, 2014 at 10:44 AM, Adrian Chadd wrote:
>
>> Hi!
>>
>> I wonder what changed between 9.2-RELEASE and 10.0-RELEASE.
>>
>> Please poke me about this next week. I'm busy this week with work and
>> maker faire but I will try to help you later.
On Fri, May 16, 2014 at 10:44 AM, Adrian Chadd wrote:
> Hi!
>
> I wonder what changed between 9.2-RELEASE and 10.0-RELEASE.
>
> Please poke me about this next week. I'm busy this week with work and
> maker faire but I will try to help you later.
>
> (It's possible something like ACPI updates or a
Hi!
I wonder what changed between 9.2-RELEASE and 10.0-RELEASE.
Please poke me about this next week. I'm busy this week with work and
maker faire but I will try to help you later.
(It's possible something like ACPI updates or a driver update has
broken things.)
-a
On 16 May 2014 07:35, Stef
Suspend/Resume is broken on my T410 using CURRENT from today.
Resume was working fine on 9.2-RELEASE. 10.0-RELEASE and 10-STABLE don't
work either.
Symptoms:
acpiconf -s3 sends it into sleep mode as expected
In single user mode, it wakes up correctly, but the screen remains
black. I tried with/
29 matches
Mail list logo
