WhiteDragon finally addresses broken LAN issue

[Mike]

And here's what he said:
------------------------------------
There is no bug, everything work 100%.
If you expirience problems, which we believe of course, but not of
type you explain.
All motherboards here in HCL are tested and are in our Lab.
None of them have "bug".
------------------------------------

There you have it, guys. It took nearly a month for any sort of actual
response from ASEM, and in four lines, WhiteDragon tells us no such
issue exists and it's not EFi-X's problem. Obviously if they didn't
cause the problem, there's no reason to try to fix it from their end.

So much for any sort of hope that we'd see a resolution to this
problem.

In the meantime, please check out the efixusers.com forums. A couple
of our posters have created some excellent guides to get your system
booting without the need of EFi-X.

[Art]

This so badly needs a link to that miserable excuse....

http://forum.efi-x.com/viewtopic.php?f=16&t=3364&p=23174#p23174

This is wrong. If it is indeed true that this is going to be the
official stance from ASEM, they are over. Done. Finished.

They will not survive this. They are neither Apple, nor Microsoft,
and their limited user base is already jumping ship while they
rearrange the deck chairs.
I believe that was an iceberg, Captain.

amazed and astounded,
-art

[Rick - PoisonApple666]

I totally agree with our Uncle Art. WD is simply playing the ostrich
on this one. "If I can't see the problem, there must not be one!"
With so many having the same problem the response is inexplicable.
But, at least they published a users manual for that which doesn't
work. It has a really nice portrait of WD and his violin. Sort of
reminds me of Nero. I imagine all of the phanbois were paid with
autographed 8x10 glossies from the little slug.

Ridiculous.

Rick

[Michel Barthelemy]

That would really be funny .. if it was not already tragic ...

There is a "bug", I know it, you know it, we all do .... there is no
point denying it and I cannot understand the way this compagny (ASEM)
is run ...

YOu guys need to seriously consider an alternative, you can do the
same thing Efi-x does with a mere usb key (to begin with) and a couple
of hours of your time.

The method explained in Asere blog is one of them. There are many
others, with or without booting on a key. The EFI boot stage can also
be written directly to your boot disk, in the EFI partition, which is
not used by Apple.

Anyways, this joke is probably about to end, I agree with Uncle Art, I
don't see how that wannabe company can survive with such an attitude.

Cheers,

Michel

[Fredrik Lindgren]

WD:

"ASEM must fix this rotten bug."
- you think it is a bug that you cant hack on Mac OS X? loool

---

Seriously, anybody know how old this guy is?

[Art]

This is interesting.

A mere few hours after this "announcement". the entire topic is gone.
Not just locked with a snarky remark; the entire proclamation of "No,
Problem, there is none, it is fine in the Lab" is gone.

Perhaps this stance is being reconsidered?

[Rick - PoisonApple666]

I would truly like to believe that they are reconsidering their
position on this one. Based on past experience, I'm not so sure.

[Michel Barthelemy]

Based on past experience ... they'll just sit on it until teh fix is
readily available on the net ...

[Mike]

Yep. I think we've pretty much figured out ASEM is liberally
"borrowing" kexts from around the Interwebs and packaging them into
firmware updates. The only reason we can see now that it hasn't been
fixed is because there is no kext out there that properly addresses
this problem.

Fredrik, WhiteDragon is so full of himself, he's got the gall to put a
full-page picture of himself in the new user manual. Probably gives
you an idea of what kind of person he is.

[Michel Barthelemy]

Well, you know, the guy is full of himslef, that's sure :-)

The R1000.kext version 1.8.1 (Pystar) seems to fix the internal LAN
problem, at least for the people who have a Realtek chip.

Maybe you should hint that to W.D ? ;-)

M

[Mike]

I'm curious to know if that kext also resolves the issue when booted
from an EFi-X. My system's working great without using EFi-X right now
(HDD bootloader, everything works 100% -- for real and not a
WhiteDragon "100%") and I don't really want to bother doing a
reinstall to verify if it fixes the problem. Would anyone who is still
on a clean EFi-X install who is experiencing the issue mind trying out
the new driver to see if it works?

[Michel Barthelemy]

Well Mike,

The kext won't solve anything if you boot with the Efi-x I'm afraid
since the driver is going to be provided by Efi-x then. It's one way
or another, I don't think you can mix the two :-)

M

[Mike]

The only thing I can think that could possibly make it worth trying is
that the Realtek driver only works when installed in /S/L/E. It
overrides the Realtek driver in IONetworkingFamily.kext, so unless EFi-
X is providing something that can override that as well... I don't
know.

[Fredrik Lindgren]

You got me curious, so I tried it. No go, it loads something called
"AsemRTL8111Ethernet", which interestingly enough doesn't turn up in
System Profiler/Extensions.

How much do you want to bet that the Psystar source (freely available
on their site) will mysteriously turn up in 3.6.12? :)

[Mike]

So placing it in /S/L/E, setting correct permissions, and clearing the
Extensions.mkext doesn't load the driver at all on next reboot?

Really peculiar, as anything in /S/L/E and part of the extensions
cache should override it. Bugger.