|
||||||||||
I've had to fix this issue with pfSense (which uses 6.x) in the past, as my hardware setup (microdrive) doesn't support DMA modes either. I've had to disable DMA on a cdrom channel just to install pfSense in the past. This is the section that I wrote for their Wiki: http://wiki.pfsense.com/wikka.php?wakka=BootOptions I hope this helps. You might want to try editing the loader.conf file on the m0n0wall image that you're using, before you try to boot it. To disable DMA: After powering on your system, You will see: Hit [Enter] to boot immediately, or any other key for command prompt. At this point hit any key and you should receive a prompt. To disable DMA for hard drives and compact flash: set hw.ata.ata_dma=0 To disable DMA for optical drives: set hw.ata.atapi_dma=0 After the installation, add the following line to /boot/loader.conf: If you have to disable DMA for your hard drive(s): hw.ata.ata_dma=0 If you have to disable DMA for optical drives: hw.ata.atapi_dma=0 It is possible that you will have to disable DMA for both your hard drive(s) and optical drives. On 12/17/06, Kevin R. Porter <krp2 at bellsouth dot net> wrote: > Hello Manuel, > > To answer your question, initially I was using COMBIOS v1.24, since > receiving your email, I downloaded COMBIOS v1.28 from the Soekris website > and updated my NET4801.... > > however the ATA driver behavior is the same under v1.28 as it was under > v1.24 --> the SANDISK CF-card works under M0n0wall v1.22 and fail under > v1.3b1. > > Since flashing COMBIOS to the latest v1.28, I restored M0n0wall v1.22 on to > the SANDISK 128MB CF-card and > captured the following console boot sequence information from the M0n0wall > v1.22 boot and the M0n0wall 1.3b1 boot for > your comparison. > > With M0n0wall v1.22, the ATA driver treats the SANDISK 128MB CF-card in PIO > mode and boots > successfully: > > console footprint 1.22 on SANDISK 128MB CF-card under COMBIOS v1.28 > ====================================================== > ... > ad0: 122MB <SanDisk SDCFJ-128> [980/8/32] at ata0-master PIO4 > Mounting root from ufs:/dev/md0c > Found configuration on ad0. > ...boots successfully into M0n0wall v1.22 > ======================================================= > > ... however, when I update to 1.3b1 (via the web-page update), the system > loads 1.3b1 on to the > same SANDISK 128MB CF-card and reboots... but the ATA driver tries to access > the SANDISK > card in DMA mode this time, (and fails): > > console footprint 1.3b1 on SANDISK 128MB CF-card under COMBIOS v1.28 > ======================================================= > ... > ad0: 122MB <SanDisk SDCFJ-128 HDX 2.15> at ata0-master WDMA2 > ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=0 > ad0: TIMEOUT - READ_DMA retrying (0 retries left) LBA=0 > ad0: FAILURE - READ_DMA timed out LBA=0 > ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=1 > ad0: TIMEOUT - READ_DMA retrying (0 retries left) LBA=1 > ad0: FAILURE - READ_DMA timed out LBA=1 > ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=0 > ad0: TIMEOUT - READ_DMA retrying (0 retries left) LBA=0 > ad0: FAILURE - READ_DMA timed out LBA=0 > Trying to mount root from ufs:/dev/md0 > > > ******************************************************************************* > * FATAL ERROR > * > * The device that contains the configuration file (config.xml) could not be > * > * found. m0n0wall cannot continue booting. > * > ******************************************************************************* > ... > ======================================================= > > > Interestingly, if I put 1.3b1 on a KINGSTON 64MB CF-card, the ATA driver > complains, but winds up using PIO mode and successfully boots M0n0wall 1.3b1 > anyway. I am currently running 1.3b1 from the KINGSTON card. > > Note: apparently the KINGSTON card identifies itself internally as Toshiba. > > console footprint 1.3b1 on KINGSTON 64MB CF-card under COMBIOS v1.28 > ======================================================== > ad0: FAILURE - SETFEATURES SET TRANSFER MODE status=51<READY,DSC,ERROR> > error=4<ABORTED> > ad0: 61MB <TOSHIBA THNCF064MBA 2.20> at ata0-master BIOSPIO > Trying to mount root from ufs:/dev/md0 > Found configuration on ad0. > ...boots successfully into M0n0wall v1.3b1 > ======================================================== > > Hope this gives you some insight into what is happening. In any case, I > am successfully running 1.3b1 (on the KINGSTON card) > > -Kevin > > ----- Original Message ----- > From: "Manuel Kasper" <mk at neon1 dot net> > To: "Kevin R. Porter" <krp2 at bellsouth dot net> > Cc: <m0n0wall at lists dot m0n0 dot ch> > Sent: Sunday, December 17, 2006 5:44 AM > Subject: Re: [m0n0wall] Beta 1.3b1 released > > > > On 17.12.06 05:30 -0500, Kevin R. Porter wrote: > > > >> Apparently the patch to disable the "ad0" driver DMA which Manuel > >> put into the later1.2x versions to avoid problems > >> on the NET4801 with CF-cards which report themselves as > >> "DMA-capable", didn't get applied to 1.3b1. > > > > No - I intentionally left it out to see whether ata(4) in FreeBSD 6.x > > still provokes these issues. Are you using the latest version of the > > Soekris comBIOS? > > > > - Manuel > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch > > For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch > For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch > > |