From: "Carlos O'Donell Jr." <carlos@baldric.uwo.ca>
To: Tom <palinux@alaskatech.org>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] Odd kernel error
Date: Wed, 30 Jan 2002 07:10:53 -0500 [thread overview]
Message-ID: <20020130071053.H8395@systemhalted> (raw)
In-Reply-To: <Pine.LNX.4.33.0201291938520.3623-100000@goliath.alaskatech.org>; from palinux@alaskatech.org on Tue, Jan 29, 2002 at 08:00:21PM -0900
> Compiling the latest from CVS (-pa16, I think) and at the final make, when
> gcc is actually doing the '-o vmlinux' I'm getting:
>
> drivers/video/video.o: In function 'L1260':
> drivers/video/video.o(.init.text+0x2554): undefined reference to
> 'fbcon_sti'
> drivers/video/video.o(.init.text+0x255c): undefined reference to
> 'fbcon_sti'
> make: *** [vmlinux] Error 1
>
> This happened with -pa15 also. I downloaded the pre-built -pa15 kernel and
> it boots fine, though. Checking, I realized I had disabled PCI in my
> config (it's a 715/100, no PCI in it), and remembered some discussion
> about PCI being a 'depends-on' item for some things... Is it possible this
> is a 'needs PCI' issue?
>
> I have a new kernel compile going on now, with PCI enabled, so we'll see
> what happens, but figured I'd toss it out in case someone else is seeing
> this.
>
>
Yes, without PCI you couldn't (until recently) compile
the STI Console.
Matthew believed that some subsequent changes had possibly
fixed this error, but I haven't checked yet.
It might be that STI Console depends on FB to be compiled.
Which can break since STI can still be compiled with FB
config turned off.
And thus you see the error that you have.
c.
next prev parent reply other threads:[~2002-01-30 12:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 5:00 [parisc-linux] Odd kernel error Tom
2002-01-30 12:10 ` Carlos O'Donell Jr. [this message]
2002-01-30 16:02 ` Tom
2002-01-30 21:19 ` Thomas Bogendoerfer
2002-01-31 17:55 ` Tom
2002-02-01 5:57 ` Jbit of Plasma
2002-02-01 7:38 ` Grant Grundler
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=20020130071053.H8395@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=palinux@alaskatech.org \
--cc=parisc-linux@parisc-linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.