I just did an update to snv_134 and got a lot more problems than before.
Do you know how to properly run 'pkg fix' from an 'alternate' boot
environment? It complained even though I booted into maintenance mode.
It least I managed to manually fix the "gdm" bug that gave rise to those
cannot update /.ICEauthority errors, but there are a lot more errors
found by it.
I was also very disappointed to see that the ntfs-3g started crashing
the system again. I was so happy to have fixed it before this update. I
really hope recompiling it will fix this issue.
On 2010-03-28 21:05, James Carlson wrote:
On 03/28/10 11:46, Patrick O'Sullivan wrote:
The easiest fix here is to buy an Intel NIC. I had the same problems
on my machine and eventually gave up. The Realtek hardware is not
worth messing around with.
The other possibly important bit of advice here is to use the current
software if you can. snv_111 is ancient. Upgrade to snv_134 or newer.
(Each one of those builds is two weeks apart, so snv_111 is 46 weeks
old ... almost a year's worth of work has gone in since then.)
To upgrade, set your pkg authority to http://pkg.opensolaris.org/dev --
the "dev" branch has the current bits.
For what it's worth, I've had good luck with Intel Ethernet devices as
well (at least when packet-mangling ... I mean "hardware acceleration"
is disabled), and 3COM and uneven but mostly positive with Broadcom.
Realtek, not so much, though there are people out there apparently using
it successfully. Perhaps they just have newer software.
--
James Carlson 42.703N 71.076W<[email protected]>
_______________________________________________
networking-discuss mailing list
[email protected]
