I'm doing my first linux install with the Knoppmyth CD and cannot get my network connection working. I can't even ping my router! I have run netcardconfig, all seems fine, there. I'm running fixed IP, I have checked resolv.conf and the DNS servers are as I expected. The network card does have the link present LED on, the activity LED is mostly on, but blinks every few seconds.

One other question, I'm attempting this with a 6.4GB disk, should I not be using automated install. I realize I have little to no room for media files.

As root, try:
pump

Hi,

6.4 gig will work, just can't do much storage as the block size of the myth partition only leave a few inodes. You run out of them before you are actually out of space. There are some tricks that can be done to help Just reformat it as a standard partiotion and it will be good for music, pictures, motion images. Just be sure to copy all the files into the root (hda1) /myth partition first.

How you ask? edit the /etc/fstab and put a # in front of the /dev/hda3. reboot and when it comes back up, only root will be mounted. ls -al /myth should should show the need files. If not, redit fstab, remove the # and change the mount point from /myth to /media/hda3. mount /media/hda3 and then cp -a /media/hda3/* /myth/ (I am assuming E50) Once you have the copy, you can reformat hda3 to obtain smaller blocks and more inodes.. stay away from tv other than a quick test.

If you did a standard auto install, then I would suspect maybe a defective network cable. In light that all the ip numbers are good, that would make me suspicious of either the card or the cable.

You could also try a ping on it's self ie ping localhost and ping your local machine ip (/sbin/ifconfig will give you that info) That will tell you if the interface is good up to the actual output driver circuit.

Mike

A ping on self runs OK. The network cable is good, it works on other network devices, the card is brand new, so I suppose it could be bad, but the blink on the ACT LED makes me think this is not so.

'pump' results in 'operation failed' when run as root.

Tx for the tips onthe small drive, i do have a 40GB drive, but an not quite ready to blow away its contents, the 6GB drive is being used just to wet my feet.

Subsequent results for 'pump' yielded :

eth0, link up, 100Mbps, full-duplex, lpa 0x45E1
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 003, PHY status 786d, resetting
eth0, link up, 100Mbps, full-duplex, lpa 0x45E1

followed by the ever familiar

Operation failed

HI,
If you have a diferent net card, give it a go. Oh, if you mean the cable is good because the light is lit, subsitute it, lights on doesn't mean someone is home.

As for the small drive, partition it manually, hda1 for / root use all but ~ 384meg space for swap as hda2.

manually mkswap /dev/hda2
swapon -a

Then try an auto upgrade it formats all of hda1 and builds most everything, If I recall correctly, it also reloads lilo so it should be bootable when done. Because swap was "pretreated" it should be good (run top to check) Now all the filesystem will be available for the "git-go" but again, limit the tv useage!

Cecil has done some marvelous stuff with KM and give us all these little tools to play with

Mike

Do I have to install drivers for the card? It is a DLINK 530-TX+. In the doc with the card it does have a procedure, and being a Linux newb, it is kinda greek to me. From the docs:

========

5) Compile the driver source files and it will generate rhinefet.o, and
copy it to correct driver installation path (The installation directory
is different in different kernel versions. In 2.4.x/2.6.x kernel, the path
is /lib/modules/KERNEL_VERSION/kernel/drivers/net/, and in 2.2.x kernel,
the path is /lib/modules/KERNEL_VERSION/net/, the KERNEL_VERSION (see
above) means the kernel version of your Linux distribution. If you don't
know your kernel version , please run 'uname -r' command in command
line. The kernel version will look like '2.2.16', '2.4.2-2smp' etc.) :
make install
========

How does one 'compile the driver source files'?

==========
6) Check configuration file (/etc/modules.conf or /etc/conf.modules or
/etc/modprobe.conf, it depends on your Linux distribution) for loading
kernel modules. Make sure the first line below is appeared in the
configuration file, where # is the interface number (eg: alias eth0
rhinefet). If you need to set the driver options, below second line is
an example to set the NIC to 100Mbps fullduplex mode (remember to unmark
the line if it is put in the configuration file).
alias eth# rhinefet
#options eth# speed_duplex=2
================

modules.conf has no lines that contain eth0.....Hmmmm, that does not sound good.