From: Frank Peters <frank.peters@comcast.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Kernel-3.10 Nvidia Emerge Failure And Other Stuff
Date: Mon, 1 Jul 2013 15:35:42 -0400 [thread overview]
Message-ID: <20130701153542.eedab9994a52502121e7e8e5@comcast.net> (raw)
Kernel-3.10 has just been released and I quickly grabbed the source
and compiled. I usually have no problems with a new kernel but this
time there were a few surprises.
First, there is a new kernel option called "Kernel support for scripts
starting with #!." This option seemed applicable only to boot scenarios
involving initramfs but unchecking it caused my system to fail to boot.
Because this may cause unexpected problems for others, I mention it here.
Second, the RTC (real time clock) module option, which has been present
for a long time as a basic kernel driver, has suddenly disappeared. To
get the same functionality, one has to enable the new "PC-style CMOS"
RTC driver, and because this builds a module with a different name (rtc-cmos
vs. rtc) my custom start-up scripts suddenly were broken. It took a bit
of searching to resolve the problem. I suppose that users of udev may
not notice the change, but I mention it just in case others may experience
something similar.
However, the main problem for me with kernel-3.20 is that the nvidia-drivers
will fail to emerge. Here is the error:
nvidia-drivers-319.32/work/kernel/nv-i2c.c: In function 'nv_i2c_del_adapter':
nv-i2c.c:327:14: error: void value not ignored as it ought to be
When I encountered this failure I expected that a huge outcry of bug reports
would ensue, but so far things have been rather quiet. There are only a few
postings of this problem with 3.10-rc1 and not much else.
I should perhaps just patiently wait for the eventual rapid fix, because this
error is a real show stopper, but I will make an inquiry nonetheless.
Has anyone on the list encountered this error with nvidia and kernel-3.10?
I hope it is not, again, some strange affliction peculiar to my machine.
Frank Peters
next reply other threads:[~2013-07-01 19:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 19:35 Frank Peters [this message]
2013-07-01 19:51 ` [gentoo-amd64] Kernel-3.10 Nvidia Emerge Failure And Other Stuff Mark Knecht
2013-07-01 20:04 ` Dale
2013-07-02 0:57 ` B Vance
2013-07-02 0:38 ` Frank Peters
2013-07-01 20:30 ` Mark Knecht
2013-07-01 20:51 ` Rich Freeman
2013-07-04 23:57 ` Mark Knecht
2013-07-05 1:08 ` Frank Peters
2013-07-01 21:06 ` Frank Peters
2013-07-02 11:29 ` [gentoo-amd64] " Duncan
2013-07-02 16:54 ` Frank Peters
2013-07-03 2:10 ` Duncan
2013-07-04 23:48 ` Sven Köhler
2013-07-05 1:28 ` Frank Peters
2013-07-05 16:41 ` Sven Köhler
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=20130701153542.eedab9994a52502121e7e8e5@comcast.net \
--to=frank.peters@comcast.net \
--cc=gentoo-amd64@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