From: Nico -telmich- Schottelius <nico-linux-next@schottelius•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: Re: Invalid module format: Re: linux-next: Tree for March 24
Date: Thu, 26 Mar 2009 18:18:57 +0100 [thread overview]
Message-ID: <20090326171857.GF6496@denkbrett.schottelius.org> (raw)
In-Reply-To: <20090325094159.8dad1d49.sfr@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 926 bytes --]
Stephen Rothwell [Wed, Mar 25, 2009 at 09:41:59AM +1100]:
> Hi Nico,
>
> On Tue, 24 Mar 2009 18:02:15 +0100 Nico -telmich- Schottelius <nico-linux-next@schottelius•org> wrote:
> >
> >
> > My system does not bootup, as I cannot load the crypto modules,
> > because it says
> >
> > Invalid module format
>
> Architecture?
amd64
> config?
http://git.schottelius.org/?p=configs/linux;a=blob;f=lenovo/x200/next-20090324;h=5eba35aca92d2f244831efea7c20c2e1e3cccda6;hb=325f152e27f48720763e0ad3e99b69049ab90116
> any other boot messages?
sure, normal, until it tries to access my hd
> Is it just the crypto modules?
Cannot check, as it does not bootup. But I did not see
any other before.
Sincerly,
Nico
--
Think about Free and Open Source Software (FOSS).
http://nico.schottelius.org/documentations/foss/the-term-foss/
PGP: BFE4 C736 ABE5 406F 8F42 F7CF B8BE F92A 9885 188C
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-03-26 17:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 7:30 linux-next: Tree for March 24 Stephen Rothwell
2009-03-24 11:44 ` Next March 24: Inconsistent lock state trace Sachin Sant
2009-03-24 17:02 ` Invalid module format: Re: linux-next: Tree for March 24 Nico -telmich- Schottelius
2009-03-24 22:41 ` Stephen Rothwell
2009-03-26 17:18 ` Nico -telmich- Schottelius [this message]
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=20090326171857.GF6496@denkbrett.schottelius.org \
--to=nico-linux-next@schottelius$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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