Re: slackware installation using NFS fails Thanks for the reply Rich,
How can I set them to 10 MBits half-duplex. Is this a setting for the
router? I couldn't find this in the manual. I do know that a LED
indicates that the connection is 10 MBPS or 100 MBPS. So the router must
'know' that the old computer is 10 MBits and the new computer 100 MBits.
But maybe the new computer doesn't know this abou the old one, or am I
not making sense now !
By the way. I tried an old Slackware version because I could not get a
newer version booted. I ran into trouble when I got the bootdisk or the
root-disk in (the computer just hang). Vs. 3.6 of slackware seemed to
work for mcd.i + color.gz but for NFS I need the net.i boot and when I
used this the root-disk color.gz hang on me.
I have an old CD-player that is not capable of reading CD-R's so that's
why the choice for NFS setup.
greetings
Rich Grise wrote:
> on 2004-03-07, in <404afde6$0$570$e4fe514c@news.xs4all.nl>,
> these words of wisdom from edward hage did appear:
>
>>Currently in want to install Slackware Linux version 3.3.0 based around
>>the 2.0.30 Linux kernel on an old 468DX2 computer using NFS. My server
>>is a Linux machine running on Suse 8.2 (kernel 2.4.20). The situation
>>now is that I only can install the boot and root-floppy and can run setup.
>
>
>
> Why so old? Just because you have an old machine doesn't mean you have to
> install old Slack. I've got 9.1, kernel 2.4.22, running on a Cyrix 6X86 P150;
> and I can't think of any reason it wouldn't work just fine on any old 486.
>
>
>
>>The problem that I encounter is that the connection is poor, sometimes
>>contact and sometimes not. Also ping gives a lot of package loss (from
>>75% to 100%).
>>
>>My question: How can I solve this, has this to do with low linux kernel
>>on client-machine? Or has this to do with the fact that the client
>>ethernet-card is 10 MBits (and server 100 MBits)?
>
>
>
> I thought I had already answered this - if they don't both have an "auto"
> option, then set them both to 10MBPS half-duplex, and make it go. If it
> won't go, then something's busted. If it does, then up it to 10 MBps
> full-duplex, and so on. When it breaks, back up one.
>
> Good Luck!
> Rich
>
>
>>Can anybody help me out?
>>Thanks. Edward
>> |