public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Francisco Ares <frares@gmail.com>
To: gentoo-user <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] [OT] Intel(R) Celeron(R) CPU J1800 drivers
Date: Mon, 16 Jun 2014 17:05:47 -0300	[thread overview]
Message-ID: <CAHH9eM5=EkE0Wi2Lo3GA=Lqj6tq0+w7zudADVZo019q6-yhj=w@mail.gmail.com> (raw)
In-Reply-To: <201406151052.29410.michaelkintzios@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1963 bytes --]

2014-06-15 6:52 GMT-03:00 Mick <michaelkintzios@gmail.com>:

> On Wednesday 11 Jun 2014 12:28:17 Francisco Ares wrote:
> > Hi,
> >
> > I am trying to install Gentoo on a x64 system with such processor, that,
> as
> > far as I could understand, is like to have the chipset embedded, so the
> > buses to video, pci express, usb, etc, comes out of the processor chip.
> >
> > The kernel from the 3.10 series were not able to correctly handle this
> > processor, at least the video driver (not sure about the rest), but the
> new
> > stable one, "gento-sources-3.12.21-r1" is OK, now I have the framebuffer
> > splash.
> >
> > But no X11 for now.  I have added "~amd64" keywords to
> > "x11-drivers/xf86-video-intel", but, for now, only a black screen, with
> no
> > clue on the log file "/var/log/Xorg.0.log" (which is the latest).
> >
> > On "/etc/portage/make.conf", I have the line:
> >
> > VIDEO_CARDS="intel i915 i965 modesetting"
> >
> > Did I miss something?
>
> Change the above to:
>
> VIDEO_CARDS="intel i965 modesetting"
>
> (not sure if modesetting is necessary)
>
> Enable the corresponding kernel drivers, but not for framebuffer - see
> here:
>
>   https://wiki.gentoo.org/wiki/Xorg/Configuration
>
> and recompile and install your new kernel.
>
>
> Run emerge -uaNDv world which will remerge the necessary xorg drivers.
>  Reboot
> and it should work.
>
> --
> Regards,
> Mick
>


Thanks, going to try this too.

Now I get something in a (what seems a) "VGA compatible controller", and
although the frame buffer is working, the Tux logos and all text characters
are all white and irregular blocks, with approximate expected sizes for
characters, but it looks like each one was written twice, a bit shifted
each time, so some of them even merge. Even the colored brief diagnostic
messages for the results of the init scripts are also white.

I guess I forgot to add the intel drivers to the kernel, going to check
this first.

Thanks again,
Francisco

[-- Attachment #2: Type: text/html, Size: 2912 bytes --]

      reply	other threads:[~2014-06-16 20:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11 11:28 [gentoo-user] [OT] Intel(R) Celeron(R) CPU J1800 drivers Francisco Ares
2014-06-11 11:32 ` [gentoo-user] " Francisco Ares
2014-06-13 15:28   ` James
2014-06-13 16:19     ` Francisco Ares
2014-06-15  9:52 ` [gentoo-user] " Mick
2014-06-16 20:05   ` Francisco Ares [this message]

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='CAHH9eM5=EkE0Wi2Lo3GA=Lqj6tq0+w7zudADVZo019q6-yhj=w@mail.gmail.com' \
    --to=frares@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /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