On Tue, Apr 25, 2017 at 12:51:53PM +, Stuart Henderson wrote:
On 2017-04-19, Nenhum_de_Nos wrote:
Does anyone knows if there is a mailing list, just as this, for their
products?
Just the web forum.
It actually is just like this mailing list: there's no
On 2017-04-19, Nenhum_de_Nos wrote:
> as many of you I got my dead one here. Now I look foward to a new brand, and
> look for same kind of issues on the new APU2 from PcEngines.
APU2 is still a bit new to identify this type of problem. I haven't
seen any problems with
On 2017-04-19 19:02:58 -0400, Ken Hornstein wrote:
> As for something happening to Soren ... well, I have no inside
> knowledge about that. I couldn't help noticing that he stopped
> posting to the mailing lists in the 2011-2012 timeframe, right when
> the first batch of 6501s started dying and
>as many of you I got my dead one here. Now I look foward to a
>new brand, and look for same kind of issues on the new APU2 from
>PcEngines. Does anyone knows if there is a mailing list, just as this,
>for their products?
There is an online forum (which I don't prefer):
On Wed, 19 Apr 2017 12:26:48 -0400
Ken Hornstein wrote:
Hi guys,
as many of you I got my dead one here. Now I look foward to a new brand, and
look for same kind of issues on the new APU2 from PcEngines. Does anyone knows
if there is a mailing list, just as this, for their
>I suppose if they were to discover that all of the boards had a
>component with a fatal flaw then that would preclude them from selling
>more of them?
Here's the worst thing about this: WE DON'T KNOW!
Soekris hasn't said, "Boards sold after date do not have any known
defects". They haven't
Mostly folks stay on this list to discuss alternatives. I suspect some may have
held out some hope for a bios workaround.
I guess I'm kind of disappointed that Soekris hasn't been more transparent as I
suspect they know exactly what's up with these boards.
I notice the full complement of these
> On Apr 19, 2017, at 7:07 AM, Ken Hornstein wrote:
> - The only useful information regarding this problem AT ALL in the past few
> YEARS has been suggestions on this mailing list for products to replace
> your Soekris with.
I appreciated seeing all of the different hardware
>> In other words, are the replacements that Soekris is sending out vulnerable
>>to the same problem?
>
>my replacement died 9 months later..
So, let me see if I accurately understand the situation:
- The net6501 sometimes just dies.
- If it's under warrantly, you will get it replaced. If not,
Hi Bryan,
> "Bryan K. Walton" hat am 18. April 2017 um 19:09
> geschrieben:
> I had a net6501 replaced under warranty about two years ago. This has me
> wondering: has anybody had a net6501 go bad, with the symptoms we have all
> been discussing, then had it
On Tue, Apr 18, 2017 at 12:09:08PM -0500, Bryan K. Walton wrote:
> On Fri, Apr 07, 2017 at 08:09:39AM -0700, David Ruggiero wrote:
> >
> > Data point A: If you send a dead board back to Soekris _in_ the warranty
> > period, it will be quickly replaced without question.
> > speculation is
A single data point, but I would suggest yes. I had a unit purchased 2/12 go
bad and replaced in 10/14.
Starting this year (say 1/17) the replacement started showing the same symptoms
of unable to reboot without a power cycle.
Several queries to Soekris got nothing back from the tech folks.
On Fri, Apr 07, 2017 at 08:09:39AM -0700, David Ruggiero wrote:
>
> Data point A: If you send a dead board back to Soekris _in_ the warranty
> period, it will be quickly replaced without question.
> speculation is constructed with absolutely zero "inside" information.
I had a net6501 replaced
(Every time this thread pops up again, I knock on wood since my
net6501-50s (with both heatsink revisions) have been bulletproof...)
WRT the net6801, sounds like it was probably a confluence of issues,
mostly market-related. Intel C2000 problems aside, Asian ODMs are
making viable inexpensive
--- Ken Hornstein wrote:
> FWIW, I just powered off my net5501 two weeks ago
> and replaced it with an APU2 from PCEngines.
I've had trouble getting the wireless on the APU2 working in OpenBSD, even
after downloading and installing the not-quite-free device driver.
Ken Hendrickson
>I've had trouble getting the wireless on the APU2 working in OpenBSD,
>even after downloading and installing the not-quite-free device driver.
Can't help you there; I see the notes for the add-on wireless module
says "not supported by all operating systems" and I didn't get one of
those. But
On 07/04/17 18:18, David Ruggiero wrote:
> > Maybe it's just me ... but this is the part that I find unlikely. Why
> > would a huge company like Intel do that? They already admitted that a
> > similar problem exists in related chipsets.
>
> I fully agree - weakest part of my argument. Why would
> Maybe it's just me ... but this is the part that I find unlikely. Why
> would a huge company like Intel do that? They already admitted that a
> similar problem exists in related chipsets.
I fully agree - weakest part of my argument. Why would Intel care about a
customer whose total chip
>C) Intel, wanting to avoid the bad publicity that would result from their
>component's failure when used in a supposedly "super reliable" machine
>built entirely around it, makes a simple deal with Soekris: we'll pay the
>costs of ALL warranty replacements for your boards that die due to our chip
> "The net6501 seems to have this sort of problem, and it’s fatal. At some
point your box will likely
> stop booting entirely. [...] The root cause of death is not well
understood, at least not by anyone
> outside of Soekris. There does not seem to be a cure. The 5501 by
comparison seems almost
As others I'm disappointed that Soekris is so silent on this issue,
especially if the root cause doesn't come from a broken bios/PCB
design/...
Building something reliable and with good support using Soekris hardware
is lottery. Plain and simple.
Sometimes Soren tells just fairytales, FYI:
On Mon, Mar 20, 2017 at 08:19:16AM -0700, EricB wrote:
> On 3/20/2017 02:11, Julien Cigar wrote:
> > On Mon, Mar 20, 2017 at 01:54:02AM +0100, Freek Dijkstra wrote:
> >> On 20-03-2017 00:49, Jay Grizzard wrote:
> >>
> >>> I haven't fired up my 6501 to check the exact CPU model (...anyone want
>
On 3/20/2017 02:11, Julien Cigar wrote:
> On Mon, Mar 20, 2017 at 01:54:02AM +0100, Freek Dijkstra wrote:
>> On 20-03-2017 00:49, Jay Grizzard wrote:
>>
>>> I haven't fired up my 6501 to check the exact CPU model (...anyone want
>>> to buy it? It's of no use to me since Soekris never released the
On 2017-03-19, Dries Verachtert wrote:
> I have a net6501 soekris device and it has a strange issue: when the
> device is working correctly and I reboot, then it doesn't start
> anymore: [...]
> If I keep the device unplugged from a power source for +/- 8 minutes,
>
Hi Dries,
This is a longstanding problem .. in my experience my board was rock
solid for a couple of years until I experienced a power failure and then
it failed to boot. It was a brick for over two years, but the last time
I tried it did boot and so now I'm keeping it as an emergency spare.
On Mon, Mar 20, 2017 at 01:54:02AM +0100, Freek Dijkstra wrote:
> On 20-03-2017 00:49, Jay Grizzard wrote:
>
> > I haven't fired up my 6501 to check the exact CPU model (...anyone want
> > to buy it? It's of no use to me since Soekris never released the
> > information needed to work with the
On 20-03-2017 00:49, Jay Grizzard wrote:
> I haven't fired up my 6501 to check the exact CPU model (...anyone want
> to buy it? It's of no use to me since Soekris never released the
> information needed to work with the FPGA), but I wonder if this could
> possibly be what's going on with them:
>
I haven't fired up my 6501 to check the exact CPU model (...anyone want
to buy it? It's of no use to me since Soekris never released the
information needed to work with the FPGA), but I wonder if this could
possibly be what's going on with them:
28 matches
Mail list logo