From: Mike Kordik <Mike@Kordik.net>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: HDIO_SET_DMA failed: with nforce2 board
Date: Mon, 17 May 2004 18:57:54 -0400 [thread overview]
Message-ID: <1084834674.3436.7.camel@Jacob> (raw)
In-Reply-To: <200405171813.07359.bzolnier@elka.pw.edu.pl>
On Mon, 2004-05-17 at 12:13, Bartlomiej Zolnierkiewicz wrote:
> On Sunday 15 of February 2004 10:18, mike@kordik.net wrote:
> > > On Monday 17 of May 2004 13:39, Mike Kordik wrote:
> > >> On Mon, 2004-05-17 at 07:13, Bartlomiej Zolnierkiewicz wrote:
> > >> > On Monday 17 of May 2004 04:15, Mike wrote:
> > >> > > I have an nforce2 based board and I cannot enable dma.
> > >> >
> > >> > 'dmesg' output, please
> > >>
> > >> I posted using PAN and I am trying to respond with PAM but todays posts
> > >> and some of yesterdays are not showing up. I do not know what the
> > >> problem is but I apologize for responding this way. Here is my dmesg
> > >> output:
> > >
> > > OK, thanks.
> > >
> > >> Linux version 2.6.4-rc1-mm1 (root@cdimage) (gcc version 3.3.3 20040217
> > >> (Gentoo Linux 3.3.3, propolice-3.3-7)) #3 Mon May 17 00:17:40 EDT 2004
> > >
> > > ...
> > >
> > >> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> > >> ide: Assuming 33MHz system bus speed for PIO modes; override with
> > >> idebus=xx
> > >> pnp: the driver 'ide' has been registered
> > >> hda: Maxtor 6Y120L0, ATA DISK drive
> > >> hdb: WDC WD1600BB-00HTA0, ATA DISK drive
> > >> hdc: MATSHITADVD-ROM SR-8582, ATAPI CD/DVD-ROM drive
> > >> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> > >> ide1 at 0x170-0x177,0x376 on irq 15
> > >
> > > AMD/nVidia IDE driver didn't recognize the controller
> > > (or driver wasn't compiled in for some reason).
> > >
> > > I need full .config and 'lspci -vvv' output to know more.
> > >
> > > Bartlomiej
> >
> > Bartlomiej,
> > Thank you for your help!
> >
> > I double checked my boot partition to make sure I actually had copied over
> > the latest kernel I had compiled and it has the right date and time stamp
> > on it.
> >
> > The info you requessted.
> >
> > .config:
>
> Weird, everything looks OK. Can you retest with vanilla 2.6.4-rc1?
>
Bartlomiej,
I am running Gentoo and there is not an ebuild for the Vanilla kernel
for 2.6. I know I can still build it but since you said that I had
everything configured correctly I got to thinking. I had remembered a
"feature" to rebuild the kernel cleanly, mrproper, so I gave it a shot.
I did a make mrproper and rebuilt the kernel as normal. Now the nforce2
chipset is detected on boot and DMA is on!
Thank you so much for your time and the help you have given me. :)
Kindest regards,
Mike
prev parent reply other threads:[~2004-05-17 22:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-17 2:15 HDIO_SET_DMA failed: with nforce2 board Mike
2004-05-17 11:13 ` Bartlomiej Zolnierkiewicz
2004-05-17 11:39 ` Mike Kordik
2004-05-17 12:34 ` Bartlomiej Zolnierkiewicz
2004-02-15 9:18 ` mike
2004-05-17 16:13 ` Bartlomiej Zolnierkiewicz
2004-05-17 22:57 ` Mike Kordik [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=1084834674.3436.7.camel@Jacob \
--to=mike@kordik.net \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox