Linksys EG1032 -- couldn't map ports/memory

2006-02-18 Thread Brent Hostetler
Hello, I am trying to get a linksys EG1032 working with freebsd 6.0. The driver appears to not be loading properly giving error that it could not map ports/memory and attach returned 6. Not sure what is wrong, or what needs to be done to fix. Please advise, Brent Relevant data: # uname -a

Re: Linksys EG1032 -- couldn't map ports/memory

2006-02-18 Thread Benjamin Lutz
On Saturday 18 February 2006 21:11, Brent Hostetler wrote: Hello, I am trying to get a linksys EG1032 working with freebsd 6.0. The driver appears to not be loading properly giving error that it could not map ports/memory and attach returned 6. Not sure what is wrong, or what needs to be done

Linksys EG1032 -- couldn't map ports/memory; skc0 attach returned 6

2006-02-18 Thread Brent Hostetler
Hello, I am trying to get a linksys EG1032 working with freebsd 6.0. The driver appears to not be loading properly giving error that it could not map ports/memory and attach returned 6. Not sure what is wrong, or what needs to be done to fix. Please advise, Brent Relevant data: # uname -a

Linksys EG1032 -- couldn't map ports/memory; skc0 attach returned 6

2006-02-18 Thread Robert Huff
Brent Hostetler writes: I am trying to get a linksys EG1032 working with freebsd 6.0. The driver appears to not be loading properly giving error that it could not map ports/memory and attach returned 6. Not sure what is wrong, or what needs to be done to fix. Please advise,

Re: Linksys EG1032 -- couldn't map ports/memory

2006-02-18 Thread Brent Hostetler
So from what I gather, rev=0x10 indicates the use of the realteak chipset and the 6.0 release kernel does not recognize this variant and must be patched to load the correct driver re. I have not manually done source patches and am kind of adverse to using blind patches from mailing lists. Is the

Re: Linksys EG1032 -- couldn't map ports/memory

2006-02-18 Thread Benjamin Lutz
So from what I gather, rev=0x10 indicates the use of the realteak chipset and the 6.0 release kernel does not recognize this variant and must be patched to load the correct driver re. I have not manually done source patches and am kind of adverse to using blind patches from mailing lists.