Void Linux discussion
 help / color / mirror / Atom feed
From: archtard <ohye...@gmail.com>
To: voidlinux@googlegroups.com
Subject: Re: Latest kernel issue - mouse pointer dissapeared on login screen
Date: Sun, 21 Jun 2015 13:04:55 -0700 (PDT)	[thread overview]
Message-ID: <1d3a8a13-c75b-4f93-add8-5ba5a2f2ae77@googlegroups.com> (raw)
In-Reply-To: <8971cb42-53ce-4843-a52f-c1db5468c4e5@googlegroups.com>


[-- Attachment #1.1: Type: text/plain, Size: 1182 bytes --]

Issue resolved with latest xf86-video-intel 
<https://github.com/voidlinux/void-packages/tree/master/srcpkgs/xf86-video-intel>, 
for me anyways.


On Tuesday, June 9, 2015 at 10:52:10 PM UTC-7, Frankie Wild wrote:
>
> I can also narrow down it happens only with the 4.x kernels. I am 
> currently using 3.19.8_1 as this is the latest one before the issue 
> happens. 
>
>
> On Wednesday, June 10, 2015 at 1:40:33 AM UTC+3, Cassie B wrote:
>>
>> I can confirm this as well.  Even went to do a reinstall since the 
>> lastest live iso does not have the issue, after updating invisible mouse 
>> issue is back.
>>
>> On Friday, June 5, 2015 at 11:13:18 PM UTC-7, Frankie Wild wrote:
>>>
>>> I have this odd situation with the latest kernel 4.0.4_1 where my mouse 
>>> cursor doesn't show anymore. 
>>>
>>> Previous kernels in between 3.18.1_2 and the latest one are failing to 
>>> load graphics so I am using the first one mentioned for now.
>>>
>>> Not too familiar with error logs so if anyone else faces it and can 
>>> direct me which logs to pull out I will provide more information.
>>>
>>> The machine is Thinkpad E530 with Optimus Intel HD 4000 and Nvidia 
>>> GT635M.
>>>
>>>

[-- Attachment #1.2: Type: text/html, Size: 1873 bytes --]

  reply	other threads:[~2015-06-21 20:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-06  6:13 Frankie Wild
2015-06-06 11:34 ` Stefan Mühlinghaus
2015-06-06 13:06   ` Frankie Wild
2015-06-09 22:40 ` Cassie B
2015-06-10  5:52   ` Frankie Wild
2015-06-21 20:04     ` archtard [this message]
2015-06-24  7:04       ` Frankie Wild

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1d3a8a13-c75b-4f93-add8-5ba5a2f2ae77@googlegroups.com \
    --to="ohye..."@gmail.com \
    --cc=voidlinux@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).