All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan <gentoopower@yahoo.de>
To: Stefan <gentoopower@yahoo.de>
Cc: linux-ide@vger.kernel.org
Subject: Re: Kernel 2.6.6 Bug !!!!
Date: Mon, 10 May 2004 13:25:48 +0200	[thread overview]
Message-ID: <409F66BC.1080708@yahoo.de> (raw)
In-Reply-To: <409F64B7.6050906@yahoo.de>

Stefan wrote:

> Sorry for posting this to the ide list, but it is the only one I'm 
> registered.
>
> I just got the new kernel 2.6.6. It seems like there is a really bad 
> bug in it.
> The Nvidia driver and my soundcard driver (this one I wrote myself), 
> don't work anymore.
>
> When I try to load those modules I get:
>
> Inavalid Module Format
>
> Who should I contact in order to resolve this issue immidiately????
>
> Tanks, R.S.
>
> P.S. On OSNews I saw someone mentioning:
>
>
> -mregparm=3 (register option) or 4 kb stacks
>
> both aren't set in my kernel
>
> Also I notived, both of the modules have a different name now in 2.6.5 
> they were named:
>
> cmaudio.ko
> nvidia.o
>
> now in 2.6.6
>
> cmaudio.o
> nvidia.ko
>
> Was there a change in compile flags or such thing?
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
Ah I just looked at the Makefile, there are a lot of changes in there, 
could it be that those changes break out of tree module compile?
Or do we have to make changes to the makefiles of our drivers?

  reply	other threads:[~2004-05-10 11:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-10 11:17 Kernel 2.6.6 Bug !!!! Stefan
2004-05-10 11:25 ` Stefan [this message]
2004-05-10 11:50 ` Stefan
2004-05-10 12:01   ` Stefan
2004-05-10 14:22 ` James Courtier-Dutton
2004-05-10 15:35   ` Stefan

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=409F66BC.1080708@yahoo.de \
    --to=gentoopower@yahoo.de \
    --cc=linux-ide@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.