Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Size of text.
19 views
Skip to first unread message
jo...@wexfordpress.com
May 8, 2012, 3:59:41 PM5/8/12
to
My new computer won't handle my Nividia graphics card. So I use the
built in graphics.
When I boot the boot messages are in large text. But about half way
through the window switches to tiny text. Any alternate console I open
has the same tiny text.
Is there a cure for this?
Slackware 13.37.
John Culleton
built in graphics.
When I boot the boot messages are in large text. But about half way
through the window switches to tiny text. Any alternate console I open
has the same tiny text.
Is there a cure for this?
Slackware 13.37.
John Culleton
root
May 8, 2012, 6:14:57 PM5/8/12
to
You can blacklist nouveau to keep the 80x25 display, then you
can change /etc/lilo.conf to select a font that makes you
happier.
Robby Workman
May 8, 2012, 9:58:08 PM5/8/12
to
On 2012-05-08, jo...@wexfordpress.com <jo...@wexfordpress.com> wrote:
> My new computer won't handle my Nividia graphics card. So I use the
> built in graphics.
What do you mean by "won't handle" it? Are you saying that the card
> My new computer won't handle my Nividia graphics card. So I use the
> built in graphics.
itself won't fit in the machine, e.g the card is AGP but the computer
has no AGP bus, or are you saying that fits just fine but won't work
after that? If the latter, were you trying to use the proprietary
nvidia driver? If so, perhaps you didn't have the nouveau kernel
driver blacklisted, and thus the KMS console was activated on boot,
and thus the nvidia binary couldn't directly access the hardware, and
thus it didn't work.
If that's the case, then do some reading about that and/or check the
SlackBuilds.org script and associated files for nvidia-driver.
> When I boot the boot messages are in large text. But about half way
> through the window switches to tiny text. Any alternate console I open
> has the same tiny text.
>
> Is there a cure for this?
If you want to change the resolution of the KMS console, that can be done
with something like this as a kernel append in lilo.conf:
append="video=1024x768"
-RW
jo...@wexfordpress.com
May 29, 2012, 6:45:11 PM5/29/12
to
On May 8, 6:14 pm, root <NoEM...@home.org> wrote:
I just p[ut the append lline into the Lilo and took out the default
append line. That seems to do the job.
I didn't do the blacklist thing (didn't know how).
So thanks for the answer.
John c.
append line. That seems to do the job.
I didn't do the blacklist thing (didn't know how).
So thanks for the answer.
John c.
jo...@wexfordpress.com
May 29, 2012, 6:48:30 PM5/29/12
to
On May 8, 9:58 pm, Robby Workman <newsgro...@rlworkman.net> wrote:
I added the append line and that did the trick. I deleted the default
append line.
The new computer came with a micro case (I didn't read the fine print)
and only one card slot. The Nvidia card won't fit. It is too tall.
JohnC
append line.
The new computer came with a micro case (I didn't read the fine print)
and only one card slot. The Nvidia card won't fit. It is too tall.
JohnC
Ivan Shmakov
May 29, 2012, 10:52:27 PM5/29/12
to
>>>>> john@wexfordpress com <jo...@wexfordpress.com> writes:
>>>>> On May 8, 6:14 pm, root <NoEM...@home.org> wrote:
>>>>> j...@wexfordpress.com <j...@wexfordpress.com> wrote:
[Cross-posting to news:alt.os.linux, for the issue at hand is
>>>>> On May 8, 6:14 pm, root <NoEM...@home.org> wrote:
>>>>> j...@wexfordpress.com <j...@wexfordpress.com> wrote:
non-specific to Slackware.]
[...]
>>> When I boot the boot messages are in large text. But about half
>>> way through the window switches to tiny text. Any alternate
>>> console I open has the same tiny text.
>>> Is there a cure for this?
>>> Slackware 13.37.
>> Do you want the large (80x25) text or something else?
>> You can blacklist nouveau to keep the 80x25 display, then you can
>> change /etc/lilo.conf to select a font that makes you happier.
> I just p[ut the append lline into the Lilo and took out the default
> append line. That seems to do the job.
There're a couple more of solutions to the problem. Namely, a
>> You can blacklist nouveau to keep the 80x25 display, then you can
>> change /etc/lilo.conf to select a font that makes you happier.
> I just p[ut the append lline into the Lilo and took out the default
> append line. That seems to do the job.
few GPU modules have an option to disable KMS, and also one can
replace the font itself with a larger version (like, e. g.,
Uni2-TerminusBold32x16.psf, which will give one 120 columns by
33 rows virtual terminal in the 1920 by 1080 graphics mode.)
(And, I'd say that the latter option is the "best" one.)
> I didn't do the blacklist thing (didn't know how).
[1] news:86bosta...@gray.siamics.net
http://groups.google.com/group/alt.os.linux/msg/e9f00b12cbe23949
--
FSF associate member #7257
Michael Black
May 29, 2012, 11:31:18 PM5/29/12
to
On Wed, 30 May 2012, Ivan Shmakov wrote:
>>>>>> john@wexfordpress com <jo...@wexfordpress.com> writes:
>>>>>> On May 8, 6:14 pm, root <NoEM...@home.org> wrote:
>>>>>> j...@wexfordpress.com <j...@wexfordpress.com> wrote:
>
> [Cross-posting to news:alt.os.linux, for the issue at hand is
> non-specific to Slackware.]
>
And why do that?
>>>>>> john@wexfordpress com <jo...@wexfordpress.com> writes:
>>>>>> On May 8, 6:14 pm, root <NoEM...@home.org> wrote:
>>>>>> j...@wexfordpress.com <j...@wexfordpress.com> wrote:
>
> [Cross-posting to news:alt.os.linux, for the issue at hand is
> non-specific to Slackware.]
>
Alt.os.linux has virtually no traffic in it, yet there is
comp.os.linux.misc
comp.os.linux.setup
one of which is surely a better place before alt.os.linux.
People just end up in that newsgroup for whatever reasons (likely they
don't look very far) and end up without a good selection of answers, when
one of the more high traffic newsgroups would provide a better selection
of answers.
Michael
Ivan Shmakov
May 30, 2012, 12:19:23 AM5/30/12
to
(Does the same apply to the rest of alt.os.linux.*, BTW?)
[Cross-posting to news:news.misc, so to remember it better.
Also set Followup-To: there.]
J.O. Aho
May 30, 2012, 12:44:32 AM5/30/12
to
newsgroup you set followup-to will not be able to see if someone already
given the answer already,nor can they take part of the discussion. It's
better you exclude the newsgroups from the beginning and only post to
the newsgroup which you thought of setting the followup-to.
--
//Aho
Ivan Shmakov
May 30, 2012, 1:10:02 AM5/30/12
to
[Set Followup-To: news:news.misc, for the reasons advocated
below.]
[...]
>> [Cross-posting to news:news.misc, so to remember it better. Also
>> set Followup-To: there.]
> Please don't use followup-to, the people who don't subscribe to the
> newsgroup you set followup-to will not be able to see if someone
> already given the answer already, nor can they take part of the
> discussion.
The same applies to the case when the poster excludes the
newsgroups "from the beginning", as you suggest just below.
> It's better you exclude the newsgroups from the beginning and only
> post to the newsgroup which you thought of setting the followup-to.
On the contrary, when the Newsgroups: change (via Followup-To:)
is clearly announced within the body of the article, the (still)
interested readers are given a chance to subscribe to the
now-relevant newsgroups and continue to read, or participate in,
the discussion.
This issue was recently discussed [1] in
news:news.software.readers, BTW.
[1] news:86d36j2u...@gray.siamics.net
http://groups.google.com/group/news.software.readers/msg/c636e2b2251dfd9f
below.]
[...]
>> [Cross-posting to news:news.misc, so to remember it better. Also
>> set Followup-To: there.]
> Please don't use followup-to, the people who don't subscribe to the
> newsgroup you set followup-to will not be able to see if someone
> discussion.
The same applies to the case when the poster excludes the
newsgroups "from the beginning", as you suggest just below.
> It's better you exclude the newsgroups from the beginning and only
> post to the newsgroup which you thought of setting the followup-to.
is clearly announced within the body of the article, the (still)
interested readers are given a chance to subscribe to the
now-relevant newsgroups and continue to read, or participate in,
the discussion.
This issue was recently discussed [1] in
news:news.software.readers, BTW.
[1] news:86d36j2u...@gray.siamics.net
http://groups.google.com/group/news.software.readers/msg/c636e2b2251dfd9f
0 new messages