public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: module woes
Date: Thu, 06 Feb 2014 21:17:20 +0200	[thread overview]
Message-ID: <52F3DFC0.4070006@gmail.com> (raw)
In-Reply-To: <loom.20140206T162051-927@post.gmane.org>

On 06/02/2014 18:08, James wrote:
>> [working theory: the kernel throws permission denied errors when it's
>> > asked in weird ways to load wrong versioned modules. Pure speculation,
>> > I've never done this at all and don't know what the error is]
> The permission are all consistent now (/lib/modules/*). I'm not sure how
> they got wacked, as I have not done anything with modules yet. Nore
> anything messing with those perms......
> 
> Obviously, from the strings command, the kernel(s) need fixing up a bit.
> I only got them to a point, to get the openbox stuff setup. The audio
> and usb automounting are all that is left to fix.... The points is the
> kernels should be good enough to work with? I suspect grub2, as this
> is my first forray into a bootable system with grub2........
> 
> 
> What is stumping me is why  all three kernels boot, but the modules
> only point to 3.10.25, even when boot either the second 
> (kernel-3.13.0-gentoo-r1) kernel or the third (config-3.13.1-gentoo)
> kernel.
> 
> I'm going to work on this and scratch a bit..... So any other suggestions
> are welcome, although it'll be a few days until I post back. Got 
> any strings options/scripts to only filter out the english readable
> parts of mostly binary files?   Manual parsing is a drag......
> 
> What/where could the system be corrupted to only attempt to use those
> modules from 3.10.25?
> 


Your kernels look fine actually. All kernel images have that large
collection of attention-grabbing strings, they seem to be regular
compiled in error messages. And the version numbers are fine.

I've just built 3.13.1-gentoo here and my perms come out right, so it's
not a bug that e.g. snuck into that one version's Makefile. And I know
of no way for a bootloader to influence what a kernel image thinks it's
version is or how to get to it's modules (it would be a huge attack
vector if a bootloader could do that)

I think I'm all out of ideas now, you might have to consult with some
kernel guys. Per my understanding, what you describe cannot happen, so
it's an odd one indeed.



-- 
Alan McKinnon
alan.mckinnon@gmail.com



  reply	other threads:[~2014-02-06 19:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-05 16:50 [gentoo-user] module woes James
2014-02-05 17:57 ` Alan McKinnon
2014-02-05 18:16   ` [gentoo-user] " James
2014-02-05 18:28   ` James
2014-02-05 19:12     ` Alan McKinnon
2014-02-06 16:08       ` James
2014-02-06 19:17         ` Alan McKinnon [this message]
2014-02-07  8:27         ` Mick
2014-02-07 13:15           ` William Kenworthy
2014-02-10 14:51             ` James
2014-02-10 14:53           ` James
2014-02-07 22:04         ` walt
2014-02-10 14:55           ` James

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=52F3DFC0.4070006@gmail.com \
    --to=alan.mckinnon@gmail.com \
    --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