From: Piotr Hosowicz <piotr@hosowicz.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: Is root kernel parameter expected to be the first one or something?
Date: Tue, 30 Mar 2010 00:55:34 +0200 [thread overview]
Message-ID: <4BB12FE6.9050805@example.com> (raw)
In-Reply-To: <20100329154852.5476ed2e.rdunlap@xenotime.net>
Randy Dunlap wrote:
> On Tue, 30 Mar 2010 00:44:28 +0200 Piotr Hosowicz wrote:
>
>> Randy Dunlap wrote:
>>> On Tue, 30 Mar 2010 00:32:42 +0200 Piotr Hosowicz wrote:
>>>
>>>> Randy Dunlap wrote:
>>>>> On Mon, 29 Mar 2010 22:41:48 +0200 Piotr Hosowicz wrote:
>>>>>
>>>>>> Randy Dunlap wrote:
>>>>>>> On Mon, 29 Mar 2010 22:16:29 +0200 Piotr Hosowicz wrote:
>>>>>>>
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> Today I had built a new next kernel with these parameters. I did not get
>>>>>>>> what I expected
>>>>>>> I don't think I understand your question.
>>>>>>> What did you expect?
>>>>>> I expected higher resolution console, smaller font etc
>>>>> Boy was I confused. I thought that your question was about the root=
>>>>> kernel boot parameter.
>>>>>
>>>>> Well, there are several questions to be asked. and one more comment.
>>>>>
>>>>> 1. what video (framebuffer) driver are you using?
>>>> Ashamed to say, but I do not know. vga=791 works perfectly when I
>>>> specifiy it via GRUB modification, either during pre-booting phase or in
>>>> menu.lst. I thought that it would work if I enable it by the oprions I
>>>> provided in the previous message.
>>> That does sound, hm, suspicious.
>
>
> OK, the above is the main problem, right?
> If so, I'll try to find time to test it.
Thanks in advance.
>>>>> 2. is it builtin the kernel image or is it a loadable module?
>>>> Loadable mofule I suppose, I can see nvidia.ko in /lib/modules/... - I
>>>> install Nbvidia driver with Nvidia tool each time after kernel change.
>>>> Each time the module has to be compiled anew.
>>> So this nvidia driver supports "vga=<value>" ?
>> I suppose it does because it works perfectly when I put it in menu.lst
>> file in GRUB config or specify it in GRUB before the kernel boots.
>>
>>>>> 3. have you read Documentation/svga.txt and Documentation/fb/{fbcon,vesafb}.txt ?
>>>> No, I havent, yet.
>>>
>>>>> And my comment is that your question (about video) would be better on the
>>>>> linux-fbdev@vger.kernel.org mailing list. It's not about kbuild/kconfig,
>>>>> unless kconfig is not saving the build parameters correctly...
>>>> But I don't know if it is a fb problem, I quoted kernel config
>>>> parameters I used, may be there is a problem with them?
>>>
>>> Well, to me, all of the questions are about video/framebuffer usage.
>>> That's why I recommended that mailing list.
>> But I read a bit and this is not a case of framebuffer, pkain svga mode.
>>
>>> Although if you are using the binary-only nvidia driver, it will probably
>>> be difficult to help you.
>> It is not binary-only, I have to rebuild the driver in every kernel change.
>
>
> Where can I download the driver to look at it, please?
http://www.nvidia.com/object/linux_display_amd64_195.36.15.html
You download the driver and ru it :
bash downloaded_file.run
--
Janusz Korwin-Mikke:
"Generalnie rzecz biorąc, ja jestem w jednej dziedzinie za
równouprawnieniem, a mianowicie: żeby w małżeństwie było
50% mężczyzn i 50% kobiet."
NP: Mark Knopfler - Before Gas & TV
NB: 2.6.34-rc2-next-20100329+
next prev parent reply other threads:[~2010-03-29 22:55 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 19:02 Maybe my frequent kernel building could be of some help to the community? And how to build? Piotr Hosowicz
2010-03-16 19:24 ` Randy Dunlap
2010-03-16 19:33 ` Piotr Hosowicz
2010-03-16 19:42 ` Randy Dunlap
2010-03-17 3:24 ` Piotr Hosowicz
2010-03-17 15:07 ` Randy Dunlap
[not found] ` <4BA0F8DE.1050006@example.com>
2010-03-17 15:54 ` Randy Dunlap
2010-03-17 16:03 ` Piotr Hosowicz
2010-03-17 17:49 ` Piotr Hosowicz
2010-03-17 17:53 ` Randy Dunlap
2010-03-18 15:40 ` Randy Dunlap
2010-03-22 3:31 ` Piotr Hosowicz
2010-03-22 3:48 ` Randy Dunlap
2010-03-22 12:42 ` Piotr Hosowicz
2010-03-22 12:53 ` Piotr Hosowicz
2010-03-24 1:12 ` Piotr Hosowicz
2010-03-24 21:43 ` Randy Dunlap
2010-03-25 11:38 ` Piotr Hosowicz
2010-03-25 17:29 ` Randy Dunlap
2010-03-25 17:37 ` Piotr Hosowicz
2010-03-25 17:40 ` Randy Dunlap
2010-03-25 17:48 ` Piotr Hosowicz
2010-03-25 17:54 ` Randy Dunlap
2010-03-25 18:35 ` Piotr Hosowicz
2010-03-25 22:04 ` Randy Dunlap
2010-03-25 22:15 ` Piotr Hosowicz
2010-03-26 16:46 ` Piotr Hosowicz
2010-03-27 16:37 ` Piotr Hosowicz
2010-03-27 16:39 ` Piotr Hosowicz
2010-04-01 16:02 ` Randy Dunlap
2010-04-01 17:24 ` Piotr Hosowicz
2010-04-01 17:44 ` Piotr Hosowicz
2010-03-29 20:16 ` Is root kernel parameter expected to be the first one or something? Piotr Hosowicz
2010-03-29 20:38 ` Randy Dunlap
2010-03-29 20:41 ` Piotr Hosowicz
2010-03-29 21:33 ` Randy Dunlap
2010-03-29 22:32 ` Piotr Hosowicz
2010-03-29 22:39 ` Randy Dunlap
2010-03-29 22:44 ` Piotr Hosowicz
2010-03-29 22:48 ` Randy Dunlap
2010-03-29 22:55 ` Piotr Hosowicz [this message]
2010-03-29 23:06 ` Randy Dunlap
2010-03-29 23:44 ` Piotr Hosowicz
2010-03-30 16:37 ` Piotr Hosowicz
2010-03-30 18:03 ` Piotr Hosowicz
2010-03-30 19:00 ` Piotr Hosowicz
2010-03-31 9:15 ` Piotr Hosowicz
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=4BB12FE6.9050805@example.com \
--to=piotr@hosowicz.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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).