Tiny Core Base > TCB Q&A Forum
Networking: de4x5 module?
MikeKu:
Using TinyCore 1.0, lsmod -v returns:
00:0a.0 Ethernet controller: Digital Equipment Corporation DECchip 21140 [FasterNet] (rev 20)
Subsystem: Unknown device 0a00:2114
Flags: bus master, medium devsel, latency 96, IRQ 11
I/O ports at ec00 [size=128]
Memory at febff000 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at febe0000 [disabled] [size=64K]
Kernel driver in use: de4x5
Kernel modules: tulip
As far as I can tell, no networking modules get loaded at bootup. After I modprobe tulip, lsmod shows:
Module Size Used by
tulip 43900 0
ohci_hcd 19076 0
scsi_wait_scan 2176 0
parport_pc 28440 0
parport 29012 1 parport_pc
As a Linux noob, I go look in /lib/modules/2.6.26-tinycore/kernel/drivers/net but I don't see anything related to de4x5 so I'm thinking it hasn't made it into TCB yet. Am I right? If so, I'd like to humbly request that this module be added, please.
(Alas, I'm sure my Linux fu isn't sufficient otherwise I'd try to attack this myself. I'm learning, so maybe some day...)
curaga:
It is built into the kernel instead of being a module. Lspci would not claim it to be in use if it wasn't :)
A sidenote, are you having network troubles or just wondered about the module?
Our kernel .config is viewable at any mirror, see releases/src
MikeKu:
Oh, I see. Some network drivers get built into the kernel, some are loaded as modules. OK, I'm learning! :)
Yes, I'm having network issues.
When I boot TinyCoreLinux 1.0 using no options, the DHCP query hangs and the machine becomes frozen.
When I boot TinyCoreLinux 1.0 using the nodhcp option, lsmod reports:
Module Size Used by
ohci_hcd 19076 0
scsi_wait_scan 2176 0
parport_pc 28440 0
parport 29012 1 parport_pc
At this point, if I modprobe tulip, then say ifconfig eth0 up... the machine hangs. I suspect that I'm on the wrong track here.
DHCP is supported on my network and is working well; a couple of other Linux distros (DSL 4.4.10, Puppy 2.15) I use on the same machine have no trouble detecting the ethernet adapter and they can get an IP Address via DHCP and everything is good.
Both DSL and Puppy load the tulip module automatically on the machine I'm using, no problems.
So, after some head scratching and re-reading of your response, I did a little more digging...
Using DSL 4.4.10 on the same machine, lsmod -v returns:
00:0a.0 Ethernet controller: Digital Equipment Corporation DECchip 21140 [FasterNet] (rev 20)
Subsystem: Unknown device 0a00:2114
Flags: bus master, medium devsel, latency 96, IRQ 11
I/O ports at ec00 [size=128]
Memory at febff000 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at febe0000 [disabled] [size=64K]
Kernel modules: tulip
I notice that the de4x5 driver is NOT being reported as being in use by DSL. So now I'm wondering if maybe TinyCoreLinux is loading the de4x5 driver when it really shouldn't... and so maybe I need to blacklist that driver. I will pursue this approach and report my progress, if any.
Thanks for all the help!
tobiaus:
i don't know exactly what you're trying to do, i think ifconfig is used to connect to the network in tomsrtbt. it may be possible (again, i don't know) to use it to connect in tc.
however, after you've modprobed, you should be able to use udhcpc -b -i eth0 -h box to connect, or run the cpanel gui and enable dhcp. if that doesn't connect you, do mention it.
curaga:
Since the driver is compiled in, it's unfortunately not possible to blacklist or otherwise skip it. It will be separated in the next update.
Perhaps you could try forcing a specific mode on the driver? They must be given at boot time, for example add this to your boot arguments to force ethernet 10Mbps:
--- Quote ---de4x5.args='eth0:autosense=TP 10Mb'
--- End quote ---
Other options to try are fdx (full duplex) and 100Mb. If even forcing a specific mode hangs, the solutions left are kernel rebuild or another network card.
Navigation
[0] Message Index
[#] Next page
Go to full version