public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "C.Beamer" <cbeamer@interlynx.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Botched Gentoo Install - but some progress
Date: Tue, 09 Aug 2005 08:13:03 -0400	[thread overview]
Message-ID: <42F89DCF.60307@interlynx.net> (raw)
In-Reply-To: <20050803185600.2b1ec7ea@chi.speakeasy.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi All,

When I previously posted and got the response below, it may as well
have been hieroglyphics because I had no idea what Bob was talking
about.  However, when I went back to square one and got to the point
of compiling the kernel, I still used genkernel, but ran the
makemenuconfig utility and saw that the format was as below.  So, I
made the changes that Bob suggested.  Now, I _don't_ get the errors as
in my previous attempt and as displayed below.

Bob Sanders wrote:

>
>> After attempting to connect to the xserver, I got my shell prompt
>> back again with the following printed on the screen:
>>
>> New driver is "i810" (==)Using default built in configuration
>> (EE) open /dev/fb0: No such device --> I have no idea what this
>> means (EE) GARTinit: Unable to open /dev/agpgart (no such file or
>> directory) (EE)I810(0) AGPGART support is not available. Make
>> sure your kernel has agpgart support or that the agpgart kernel
>> module is loaded (EE)Screens found, but non have useable
>> configuration Fatal server error: no screens found i
>
>
> /dev/fb0 is the framebuffer. No need to worry about that if using
> X. But if running a splash screen, then it needs to be defined in
> the kernel. There is a how-to on gentoo-wiki.org explaining how to
> setup the system and kernel.
>
> The other, you'll need to re-config your kernel to include -
>
> Device Drivers --> I2C Support --> <M> I2C support <*> I2C device
> interface I2C Hardware Bus Support --> <M > Intel 810/815
>
> And -
>
> Device Drivers --> Character Devices --> Intel 440LX/BX/GX, I8xx
> and E7x05 chipset support
>
>
However, x still won't start and I get the  message 'Cannot run in
framebuffer mode'.

I don't think that I changed anything related to framebuffers when I
ran makemenuconfig.

It was also my understanding that although I could use a vga statement
in my grub.conf file to specify a framebuffer device, that with a
gentoo patched kernel, I didn't need to.

So, any idea where I made my mistake?

Regards,

Colleen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFC+J3PBEKKz3fpe6IRAujSAKCEqiHMw8JJY7WjJp5F3hUPastCvQCfRspg
CpO2GdrCst6i9ff3Auf2XGE=
=NHRd
-----END PGP SIGNATURE-----

-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2005-08-09 12:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-04  1:02 [gentoo-user] Botched Gentoo Install C.Beamer
2005-08-04  1:45 ` Michael Crute
2005-08-04  4:00   ` C.Beamer
2005-08-04  4:49     ` Rumen Yotov
2005-08-04  4:53     ` Michael Crute
2005-08-04 12:28     ` Richard Fish
2005-08-04  1:56 ` Bob Sanders
2005-08-04  2:44   ` Michael Crute
2005-08-09 12:13   ` C.Beamer [this message]
2005-08-09 19:49     ` [gentoo-user] 'Cannot run in framebuffer mode' Benno Schulenberg
2005-08-10 13:27     ` [gentoo-user] Botched Gentoo Install - but some progress Robert Crawford

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=42F89DCF.60307@interlynx.net \
    --to=cbeamer@interlynx.net \
    --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