Search Members Help

» Welcome Guest
[ Log In :: Register ]

Mini-ITX Boards Sale, Fanless BareBones Mini-ITX, Bootable 1G DSL USBs, 533MHz Fanless PC <-- SALE $200 each!
Get The Official Damn Small Linux Book. DSL Market , Great VPS hosting provided by Tektonic
Pages: (3) </ [1] 2 3 >/

[ Track this topic :: Email this topic :: Print this topic ]

 reply to topic new topic new poll
Topic: New user problems, Problems with getting DSL 1.5 on net< Next Oldest | Next Newest >
DrMikeGreen Offline





Group: Members
Posts: 9
Joined: Sep. 2005
Posted: Sep. 25 2005,03:51 QUOTE
I have an EPIA VIA miniITX board which runs Win98SE fine and has run Fedora-4 previously.  I can get DSL to boot and initialize now with the framebuffer X driver, but, although the kernal recognizes the LAN "card" as eth0, I cannot access the net.  I tried DHCP first, then manually set an IP, mask, gateway, and name server addresses using the netcard setup.  It still can't resolve an address.  Any suggestions from someone who has used a EPIA miniITX board with DSL?  I've used Linux before, but I am not an expert by any means although I'm very familiar with operating systems, hardware, and programming in general.
Back to top
Profile PM 
green Offline





Group: Members
Posts: 453
Joined: Oct. 2004
Posted: Sep. 25 2005,21:57 QUOTE
a shot in the dark here, as i do not have a miniITX, but did you try:

sudo pump -i eth0

after the DSL cd finishes booting and type that into a command prompt, but not as root?

did you try to PING any known good IP address after this or boot?

sudo ping yahoo.com

what does it show you when you type:

ifconfig
Back to top
Profile PM 
DrMikeGreen Offline





Group: Members
Posts: 9
Joined: Sep. 2005
Posted: Sep. 25 2005,23:33 QUOTE
Initially, ifconfig just shows the local loop (lo) despite eth0 being recognized by the kernel ("eth0 detected, DHCP broadcasting").  If I use the control panel (lancardconfig) to manually set an IP address, etc., then ifconfig shows both "lo" and "eth0".  "sudo pump -i eth0" indicates "operation failed" and "sudo ping 192.168.2.1" which should ping the gateway indicates "network unreachable".  I suspect there's something screwy about the driver even though this hardware has worked with Linux before.
Back to top
Profile PM 
brianw Offline





Group: Members
Posts: 245
Joined: Sep. 2005
Posted: Sep. 25 2005,23:55 QUOTE
Do an lsmod to see which drivers are being loaded (if any).  Bellow, mine is using the generic 8390 driver for pcnet_cs.  My pcmcia card is  a SOHOWARE card.  Check the specs for the VIA motherboard to see which chip it uses for network.  Once you find out which chip it uses go to the directory
/lib/modules/2.4.26/kernel/drivers/net to see if there is a driver for it.  You can manually install the module using modprobe <module name> then run the netcardconfig.

brian@box:~$ lsmod
Module                  Size  Used by    Not tainted
pcnet_cs               10852   1
8390                    6400   0 [pcnet_cs]
crc32                   2816   0 [8390]
pcmcia_core            39840   0 [serial_cs pcnet_cs ds yenta_socket]
Back to top
Profile PM 
DrMikeGreen Offline





Group: Members
Posts: 9
Joined: Sep. 2005
Posted: Sep. 26 2005,04:01 QUOTE
lsmod showed a variety of drivers, all seeming to be appropriate.  In particular, the "via-rhine" driver was loaded and the "mii" and "crc32" drivers depend on it.  The LAN adapter is described sometimes as "VIA Rhine" so that should be right.  It just doesn't work.
Back to top
Profile PM 
12 replies since Sep. 25 2005,03:51 < Next Oldest | Next Newest >

[ Track this topic :: Email this topic :: Print this topic ]

Pages: (3) </ [1] 2 3 >/ 		reply to topic new topic new poll
Quick Reply: New user problems

Do you wish to enable your signature for this post?
Do you wish to enable emoticons for this post?
Track this topic
View All Emoticons
View iB Code