At 10:00 PM 5/30/2006, Bao C. Ha wrote:
Hi Bill,
You can put the following into /boot/loader.conf
hw.ata.ata_dma=0
It disables the dma on ata drives. It works on some of the
high speed 100X 2gb CF cards, but not on the Seagate on my
systems. Since mine are VIA-based, so it may be different
All-
I am attempting to use a Seagate ST1.2 Microdrive (4GB) in my WRAP platform.
I imaged it with the embedded image as a start (I'll play around with
converting it to R/W later). I use the memory card reader on my printer to
write the image, which was a first (my CF/PC card adapter doesn't
Bill,
On 5/30/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
All-
I am attempting to use a Seagate ST1.2 Microdrive (4GB) in my WRAP platform.
I spent quite a while trying to get this to work on the WRAP platform,
finally gave up and used a regular Flash card. I eventually tried
using the
At 12:40 PM 5/30/2006, Paul Haddad wrote:
I spent quite a while trying to get this to work on the WRAP platform,
finally gave up and used a regular Flash card. I eventually tried
using the same card to boot a Via mobo with a IDE-Flash adaptor and
got the same result.
I think the Hitachi
[EMAIL PROTECTED] wrote:
All-
I am attempting to use a Seagate ST1.2 Microdrive (4GB) in my WRAP
platform.
Isn't this in the FAQ/Wiki?
http://wiki.pfsense.com/wikka.php?wakka=FullInstallOnWRAP
I haven't tried this, I don't own a MD.
cheers,
Rainer
At 02:02 PM 5/30/2006, Rainer Duffner wrote:
Isn't this in the FAQ/Wiki?
http://wiki.pfsense.com/wikka.php?wakka=FullInstallOnWRAP
I haven't tried this, I don't own a MD.
I may try that as well, later today. That being said, the Wiki article
doesn't describe how to overcome a problem with
Bill,
On 5/30/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Thanks for sharing your experience. Can you describe where it broke during
the install? Or did it seem to install and only fail on boot?
Same spot as you didn't seem to matter which kernel I used (again I
tried it on the WRAP and on
Another data point!
I have the Seagate 4gb CF also. I could not boot pfSense on it
either. But, I can boot IPCop up!
Very strange???
Bao
On Tue, May 30, 2006 at 04:47:50PM -0500, Paul Haddad wrote:
Bill,
On 5/30/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Thanks for sharing your
On 5/30/06, Bao C. Ha [EMAIL PROTECTED] wrote:
Another data point!
I have the Seagate 4gb CF also. I could not boot pfSense on it
either. But, I can boot IPCop up!
Very strange???
Did you try grub by chance?
-
To
Bill,
On 5/30/06, Scott Ullrich [EMAIL PROTECTED] wrote:
Did you try grub by chance?
I know that I didn't but I don't think it'd make any difference. If
you look at Bill's first post the kernel actually boots, it just fails
to find/mount the drive. I think grub would only help on the first
Yes!
I tried grub on both: pfSense and IPCop. Grub does really do
anything on FreeBSD, since it just load the FreeBSD loader.
I think it is a kernel issue. On Via-based hardware, the CF socket
cannot handle DMA, just PIO, not until the c7-based systemboard
arriving later this year. These high
At 05:27 PM 5/30/2006, Bao C. Ha wrote:
I think it is a kernel issue. On Via-based hardware, the CF socket
cannot handle DMA, just PIO, not until the c7-based systemboard
arriving later this year. These high capacity and fast CF will
keep choking on these boards during boot-up.
The WRAP CF
Bao,
On 5/30/06, Bao C. Ha [EMAIL PROTECTED] wrote:
I think it is a kernel issue. On Via-based hardware, the CF socket
cannot handle DMA, just PIO, not until the c7-based systemboard
arriving later this year. These high capacity and fast CF will
keep choking on these boards during boot-up.
I
Bill,
On 5/31/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
At 05:27 PM 5/30/2006, Bao C. Ha wrote:
To test this theory, is there a way to tell the boot sequence to use only
PIO for disk access, or do we need to build a new kernel?
I'm pretty sure I tried this. But I think you can set
14 matches
Mail list logo
