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 14:01:39 +0200	[thread overview]
Message-ID: <409F6F23.9020105@yahoo.de> (raw)
In-Reply-To: <409F6C98.8080301@yahoo.de>

Stefan wrote:

> Update, I had an error in my makefile and didn't notice it until now. 
> I should have tested it with 2.6.5 right after I made the change.
> So my driver works, only the nvidia driver seems broken. I try to find 
> out why.


The nvidia driver is fine, I ran it manually now and it works. Seems 
like gentoos ebuild for the driver is broken:-(

So everything is fine, just throw those mail in your trashcan:-)

>
>
>
> 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
>>
>


  reply	other threads:[~2004-05-10 11:54 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
2004-05-10 11:50 ` Stefan
2004-05-10 12:01   ` Stefan [this message]
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=409F6F23.9020105@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.