|
||||||||||
I really suggest you to test with my Bios settings. As I said, I got the same issue, and now this mono is up and running (on the cf card not HD anymore) Raphaël Maunier Matt Juszczak wrote: > We still haven't been able to get the nexcom working with the CF. > When we put a hard drive in, it worked fine. Although someone > recently did a post to the list (I forget who it was) about a fix for > this. We'll try it this week, and I'll let everyone know if it fixes > our issues. > > On Tue, 5 Apr 2005, Maarten Poell wrote: > >> No in our company we are thinking about buying 1 of them as a firewall >> for our webservices. >> >> And of course I will sent it directly to you for testing ;-) >> >> Has anybody some reallife experience with Nexcom products? >> >> >> On Apr 5, 2005 12:26 AM, C. Falconer <cfalconer at avonside dot school dot nz> >> wrote: >> >>> Do you have the units already? >>> >>> If so, you won't damage them by booting m0n0wall. The parts should >>> work >>> fine based on the freeBSD hardware list, but it does depend on whether >>> nexcom have done anything naughty. >>> >>> Tell you what - send me two and I'll test them for you :) >>> >>> >>> -----Original Message----- >>> From: Maarten Poell [mailto:maarten dot poell at gmail dot com] >>> Sent: Tuesday, 5 April 2005 10:03 a.m. >>> To: m0n0wall at lists dot m0n0 dot ch >>> Subject: [m0n0wall] Hardware Nexcom NSA 1030I-1, will it run? >>> >>> I would like to run m0n0wall on a Nexcom NSA 1030 (Via C3 1GHz, 3x >>> Intel >>> 82559, Sandisk 128mb Compact Flash module). >>> >>> I checked the FreeBSD/i386 Hardware Notes and based on that it >>> should be >>> able to run on this hardware. >>> >>> But after reading the post's from Matt Juszczak (who's having >>> problem's with >>> booting from a Nexcom Nexgate 1045) I'm not sure anymore. >>> >>> Can anybody tell my if the above hardware config will work with >>> m0n0wall >>> 1.11? Or can anybody give some other embedded hardware solution's >>> which are >>> proven to run with m0n0wall exept of course for the already proven >>> net45xx/net48xx and WRAP solutions? >>> >>> Any hints, >>> >>> Maarten >>> >>> --------------------------------------------------------------------- >>> 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 >> >> >> !DSPAM:425245c0609051023666354! >> > > --------------------------------------------------------------------- > 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 > |