PCI chipset -- module vs. compiled-in

[William Park]

On Sun, Feb 05, 2006 at 11:08:34PM -0500, Jamon Camisso wrote:
> William Park wrote:
> >Normally, my PCI chipset is compiled in.  But, for experiment, I
> >tried compiling in only the "generic" options, and moved all specific
> >PCI chipsets (ie. via82cxxx, hpt366) as modules.
> >
> >Hotplug loads all the modules alright, but with all 'hdparm' options
> >turned off.  When I tried turning on DMA, 
> >    $ hdparm -m 16 -c 1 -u 1 -d 1 /dev/hda
> >I get
> >    /dev/hda:
> >     setting 32-bit IO_support flag to 1
> >     setting multcount to 16
> >     setting unmaskirq to 1 (on)
> >     setting using_dma to 1 (on)
> >     HDIO_SET_DMA failed: Operation not permitted
> >     multcount    = 16 (on)
> >     IO_support   =  1 (32-bit)
> >     unmaskirq    =  1 (on)
> >     using_dma    =  0 (off)
> >
> >Is this normal?  Has anyone encountered this before?  I thought I should
> >check here first.
> 
> Would enabling this line do it?
> CONFIG_BLK_DEV_IDEDMA_PCI=y

It is already 'y'.

-- 
William Park <opengeometry-FFYn/CNdgSA at public.gmane.org>, Toronto, Canada
ThinFlash: Linux thin-client on USB key (flash) drive
	   http://home.eol.ca/~parkw/thinflash.html
BashDiff: Super Bash shell
	  http://freshmeat.net/projects/bashdiff/
--
The Toronto Linux Users Group.      Meetings: http://tlug.ss.org
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml