Mike Chandler wrote:
On Monday 19 April 2004 04:10 pm, Tim Beauregard wrote:
Markus Schabel wrote:
Tim Beauregard wrote:
Markus Schabel wrote:
Tim Beauregard wrote:
Unfortunately my first post was 9 days ago, and noone replied to that.
I had that problem when i forgot to compile the piix drive
ame boat, except kernel-2.6.3-1.
> > >> hdparm returns this error:
> > >>
> > >> [EMAIL PROTECTED]:/home/mike# hdparm -d1 /dev/hdb
> > >>
> > >> /dev/hdb:
> > >> setting using_dma to 1 (on)
> > >> HDIO_SET_DMA failed:
On Monday 19 April 2004 04:10 pm, Tim Beauregard wrote:
> Markus Schabel wrote:
> > Tim Beauregard wrote:
> >> Markus Schabel wrote:
> >>> Tim Beauregard wrote:
> Unfortunately my first post was 9 days ago, and noone replied to that.
> >>>
> >>> I had that problem when i forgot to compile the
On Monday 19 April 2004 02:34 pm, Tim Beauregard wrote:
> Markus Schabel wrote:
> > Tim Beauregard wrote:
>
> [...]
>
> >> Unfortunately my first post was 9 days ago, and noone replied to that.
> >
> > I had that problem when i forgot to compile the piix drivers into the
> > kernel. after fixing th
Markus Schabel wrote:
Tim Beauregard wrote:
Markus Schabel wrote:
Tim Beauregard wrote:
Unfortunately my first post was 9 days ago, and noone replied to that.
I had that problem when i forgot to compile the piix drivers into the
kernel. after fixing that, all worked fine again.
Thanks for th
Tim Beauregard wrote:
Markus Schabel wrote:
Tim Beauregard wrote:
Unfortunately my first post was 9 days ago, and noone replied to that.
I had that problem when i forgot to compile the piix drivers into the
kernel. after fixing that, all worked fine again.
Thanks for the suggestion. I inserted thi
Markus Schabel wrote:
Tim Beauregard wrote:
[...]
Unfortunately my first post was 9 days ago, and noone replied to that.
I had that problem when i forgot to compile the piix drivers into the
kernel. after fixing that, all worked fine again.
best regards, Markus
Thanks for the suggestion. I ins
Tim Beauregard wrote:
Mike Chandler wrote:
[...]
Hey Tim,
I'm in the same boat, except kernel-2.6.3-1.
hdparm returns this error:
[EMAIL PROTECTED]:/home/mike# hdparm -d1 /dev/hdb
/dev/hdb:
setting using_dma to 1 (on)
HDIO_SET_DMA failed: Operation not permitted
using_dma= 0 (off)
[
Mike Chandler wrote:
[...]
Hey Tim,
I'm in the same boat, except kernel-2.6.3-1.
hdparm returns this error:
[EMAIL PROTECTED]:/home/mike# hdparm -d1 /dev/hdb
/dev/hdb:
setting using_dma to 1 (on)
HDIO_SET_DMA failed: Operation not permitted
using_dma= 0 (off)
[EMAIL PROTECTED]:/home
I've also tried passing ide0=dma to the kernel, however hdparm will not
> turn DMA on following this. Can anyone suggest where I'm going wrong?
>
> Thanks, Tim
Hey Tim,
I'm in the same boat, except kernel-2.6.3-1.
hdparm returns this error:
[EMAIL PROTECTED]:/home/mike# hd
Tim Beauregard wrote:
Hi,
Could someone please help me find the kernel config settings which I've
neglected, that prevent me from using DMA? I expected inclusion of AMD
and nVidia IDE chipset support (CONFIG_BLK_DEV_AMD74XX=m) would be
sufficient. I have tried enabling DMA only for disks
(CONFIG
EMAIL PROTECTED]:~$ sudo hdparm -d1 /dev/hda
/dev/hda:
~ setting using_dma to 1 (on)
~ HDIO_SET_DMA failed: Operation not permitted
~ using_dma= 0 (off)
_
[EMAIL PROTECTED]:~$ uname -a
Linux debian 2.6.3 #1 Sat Apr 3 01:47:16 BS
Serge Gebhardt <[EMAIL PROTECTED]> writes:
> try compiling into the kernel (not module) and check the logs. I
> remember having similar cases, can't remember how I
> solved them :/
Thanks. Compiling the chipset support into the kernel solved the
problem. That would qualify as a kernel bug, wouldn
On 01 Dec 2003 02:12:01 +0100
Andreas Goesele <[EMAIL PROTECTED]> wrote:
> > But then the disappointment:
> >
> > $ modprobe amd74xx
> >
> > $ hdparm -d1 /dev/hda
> >
> > /dev/hda:
> > setting using_dma to 1 (on)
> > HDIO_SET_DMA
Alf Werder <[EMAIL PROTECTED]> writes:
> > It's even worse:
> >
> > $ modprobe amd74xx
> > Segmentation fault
> >
> > And now I have:
> >
> > amd74xx 9468 1 (initializing)
> >
> > The module cannot be removed and interferes with other processes as
> > for instance ifconfig (
On Mon, 2003-12-01 at 02:12, Andreas Goesele wrote:
> Andreas Goesele <[EMAIL PROTECTED]> writes:
>
> > But then the disappointment:
> >
> > $ modprobe amd74xx
> >
> > $ hdparm -d1 /dev/hda
> >
> > /dev/hda:
> > setting using_dma
Andreas Goesele <[EMAIL PROTECTED]> writes:
> But then the disappointment:
>
> $ modprobe amd74xx
>
> $ hdparm -d1 /dev/hda
>
> /dev/hda:
> setting using_dma to 1 (on)
> HDIO_SET_DMA failed: Operation not permitted
> using_dma= 0 (off)
It's eve
/hda:
setting using_dma to 1 (on)
HDIO_SET_DMA failed: Operation not permitted
using_dma= 0 (off)
Any suggestions? (The last command I did as root, of course.)
Thanks a lot in advance!
Andreas Goesele
--
Omnis enim res, quae dando non deficit, dum habetur et non datur,
nondum habetur
18 matches
Mail list logo
