On 25-Aug-06, at 14:37, Robert Huff wrote:
After doing some digging, I've found that there was a patch
applied to
RELENG_6, modifying the sk driver to ignore my revision of card, and
instructing the re driver to attach. This is probably why it
works for
Robert and not for me; he's
On 24-Aug-06, at 22:17, Robert Huff wrote:
Probably. The chip name means a Realtek ptui! 8169, and that
takes the re() driver.
That's pretty much the same way I feel about 'em.
Shouldn't hurt. I fixed mine by
a) removing both re and skc from the kernel config file
On 24-Aug-06, at 22:17, Robert Huff wrote:
Probably. The chip name means a Realtek ptui! 8169, and that
takes the re() driver.
Unfortunately, this didn't work out for me. I tried a bit of other
fiddling as well and didn't get any change in behaviour. I'll just
take the card back and
Jeremy Karlson writes:
After doing some digging, I've found that there was a patch applied to
RELENG_6, modifying the sk driver to ignore my revision of card, and
instructing the re driver to attach. This is probably why it works for
Robert and not for me; he's probably running 6
I'm having difficulty getting a new Linksys EG1032 gigabit network
card to work on FreeBSD 5.5-STABLE. I get the following relevant
messages on boot:
skc0: Linksys EG1032 Gigabit Ethernet port 0xe800-0xe8ff mem
0xd8002000-0xd80020ff irq 11 at device 15.0 on pci0
skc0: failed: rid 0x10 is
Jeremy Karlson writes:
I'm having difficulty getting a new Linksys EG1032 gigabit network
card to work on FreeBSD 5.5-STABLE. I get the following relevant
messages on boot:
skc0: Linksys EG1032 Gigabit Ethernet port 0xe800-0xe8ff mem
0xd8002000-0xd80020ff irq 11 at device 15.0
On 24-Aug-06, at 21:04, Robert Huff wrote:
Depending on when you bought the card, the correct driver may
be re(4), not skc.
Check the output of pciconf -l -v; mine shows:
[EMAIL PROTECTED]:12:0: class=0x02 card=0x00241737 chip=0x10321737
rev=0x10 hdr=0x00
vendor =
