| View previous topic :: View next topic |
| Author |
Message |
Disparu
Tux's lil' helper
Joined: 07 Jun 2006
Posts: 149
|
 Posted: Thu Feb 01, 2007 2:18 pm Post subject: DFI ICFX3200-T2R/G Marvel 88E8052/53 not detected [SOLVED] |
 |
|
I am almost 100% positive that this board uses Marvel 88E8052 and 88E8053 onboard network inerfaces, that is what windows labeled them as and they are the same ones that my old DFI board used, but the kernel module for them doesnt detect them, they dont work at all with the module that specifies that it is for the aforementioned models.
I don't know what to do, perhaps this board has revisions to marvel interface, it was just released last month...
Last edited by Disparu on Mon Feb 12, 2007 8:19 pm; edited 1 time in total |
|
| Back to top |
|
 |
mesch.t
n00b
Joined: 25 Oct 2004
Posts: 33
|
| Posted: Fri Feb 02, 2007 9:02 am Post subject: |
|
|
what does say?
I have a marvell 88E8053 loading with the sky2 module.
| Code: | | SysKonnect Yukon2 support |
|
|
| Back to top |
|
|
Disparu
Tux's lil' helper
Joined: 07 Jun 2006
Posts: 149
|
| Posted: Fri Feb 02, 2007 4:10 pm Post subject: |
|
|
| mesch.t wrote: | what does say?
I have a marvell 88E8053 loading with the sky2 module.
| Code: | | SysKonnect Yukon2 support |
|
I am at work, but I remember LSPCI reporting something like this
"network bla bla bla unknown ...."
horrible recall for that, but it basically said the device was unknown.
my previous DFI board had the 8053-8052 onboard network interfaces and it worked fine, they detected as marvel something or other, but these arent detecting as anything. |
|
| Back to top |
|
|
Disparu
Tux's lil' helper
Joined: 07 Jun 2006
Posts: 149
|
| Posted: Mon Feb 05, 2007 6:06 pm Post subject: |
|
|
| im pretty sure the lack of detection is directly related to my RD600 northbridge not being supported at the moment, if someone can confirm this ill mark this thread solved. |
|
| Back to top |
|
|
Disparu
Tux's lil' helper
Joined: 07 Jun 2006
Posts: 149
|
| Posted: Mon Feb 12, 2007 8:19 pm Post subject: |
|
|
| I appended the option "pci=nommconf" to the kernel and it solved this issue... |
|
| Back to top |
|
|
|
Networking & Security
