solution to the same problem as above that I encountered.
My question is how do I switch to the old rtl8139.o driver which used to work
with kernel 2.2.19?
Thanks in advance
Jacques
--
Dr. Jacques B. Siboni mailto:[EMAIL PROTECTED]
8 pass.
is more an NFS boot problem.
One (quick and dirty) solution could be to allow the kernel to load even with
an mtu less than 1500, which I could not do.
Thanks in advance
Jacques
--
Dr. Jacques B. Siboni mailto:[EMAIL PROTECTED]
8 pass. Charles Albert, F75018 Paris, France
Tel. & Fax: 33 (0)
reated my own custom kernel and tagged it. You might want to
> give that a try.
>
> Best of luck :)
>
--
Dr. Jacques B. Siboni mailto:[EMAIL PROTECTED]
8 pass. Charles Albert, F75018 Paris, France
Tel. & Fax:
the kernel. the procinfo command does not show any device
at the irq 15; and in the boot process i see no line with hda.
I confirm the hda drive can be seen by linux as I can access to it with a
linux boot diskette
What do you think?
Cheers
Jacques
>
> On Sun, 7 Oct 2001, Jacques B. Sib
/hda
I built the partitions with a floppy linux but the result is the same when I
boot ltsp
And when I run mkfs it fails either.
Can you give me some hints of direct me to some documentation about it
Cheers
Jacques
--
Dr. Jacques B. Siboni mailto:[EMAIL PROTECTED]
8 pass. Charles Albert
Floppyfw is better on older cards as it will tell you what irq to use or
> if there are two or more cards in the box, any conflicts found.
>
--
Dr. Jacques B. Siboni mailto:[EMAIL PROTECTED]
8 pass. Charles Albert, F75018 Paris, France
Tel. & Fax: 33 (0) 1 42
Hi all,
Do you have any suggestion of a simple way to identify the NIC boards and
chips in order to make etherboot rom, in particular when there is a a NIC chip
on the mother board?
Thanks in advance
Jacques
--
Dr. Jacques B. Siboni mailto:[EMAIL PROTECTED]
8 pass. Charles Albert, F75018
shes.
Does anyone have the experience of this kind of thing or can direct me to a
place where I can find an answer
Thanks in advance
Jacques
--
Dr. Jacques B. Siboni mailto:[EMAIL PROTECTED]
8 pass. Charles Albert, F75018 Paris, France
Tel. & Fax: 33 (0) 1 42 28 76 78
Home Page: htt
eth1
this rule denies fragmented packets to be sent. As many packets are fragmented
it does not work!!
A lot of sweat for something very simple ... as usual
Thanks for the concern of those who helped me.
Cheers
Jacques
--
Dr. Jacques B. Siboni mailto:[EMAIL PROTECTED]
8 pass. Charles Albert
:40:5:e3:79:fc;
fixed-address 192.168.0.3;
filename "/tftpboot/lts/vmlinuz.ne2000";
}
}
>
> * Atlast what is the operating system u r loaded in
> server...redhat or some other?
as I told you, I use redhat 7.0, kernel is 2.2.19-7.0.8
&g
acronym
corresponding to a piece of software I had not installed
Sorry
Jacques
--
Dr. Jacques B. Siboni mailto:[EMAIL PROTECTED]
8 pass. Charles Albert, F75018 Paris, France
Tel. & Fax: 33 (0) 1 42 28 76 78
Home Page: h
e mentioned
> above is the problem, That error of yours is a problem of negotiation
> between NICS and HUB or NICS to NICS meaning you have to set the proper
> duplex settings (HALF or FULL duplex mode) of your NICS
>
> Hope that helps
> JON
> [EMAIL PROTECTED]
--
Dr. Jacq
> 192.168.1.1.2049 > 192.168.1.3.62922340: reply ok 96 getattr
>
> James
As I mentionned, actually the IPs are correct it is just a cut & paste error
(unfortunetly)
Jacques
--
Dr. Jacques B. Siboni mailto:[EMAIL PROTECTED]
8 pass. Charles Albert, F75018 Paris, France
Tel. &
RX packets:49348 errors:0 dropped:0 overruns:0 frame:0
TX packets:59281 errors:0 dropped:0 overruns:0 carrier:0
collisions:4 txqueuelen:100
Interrupt:9 Base address:0x340
eth1:0Link encap:Ethernet HWaddr 00:80:AD:84:B1:7D
inet addr:192.168.
o real error messages as such:
>
> The terminal screen, after finding the DHCP server, reads:
>
> "Me: 192.169.0.3, Server: 192.168.0.254, Gateway: 192.168.0.1
>
> Loading 192.168.0.254:/tftpboot/lts/vmlinuz.eepro100 . "
>
> and that's it.
>
me
Cheers
Jacques
Jim McQuillan wrote:
>
> Jacques,
>
> I'm interested in the warning message about 'Gateway not on directly
> connected network'.
>
> I'd like to see your dhcpd.conf file, to see how you've configured it.
>
> Thanks,
>
h
Unknown/1 4096 bytes @ 0 (ttl 64, id 12)
18:29:18.277747 < 192.168.1.3.163585636 > 192.168.1.1.2049: 112 read fh
Unknown/1 4096 bytes @ 0 (ttl 64, id 13)
--
Dr. Jacques B. Siboni mailto:[EMAIL PROTECTED]
8 pass. Charles Albert, F75018 Paris, France
Tel. & Fax: 33 (0) 1 42 28 76 78
Home P
on 192.168.0.1
VFS: Mounted Root (NFS filesystem)
nfs: Server 192.168.0.1 not responding
as you see nfs works as it mount the root fs but then there is a problem
Does someone understand what is going on?
Thanks in advance
Jacques
--
Dr. Jacques B. Siboni mailto:[EMAIL PROTECTED]
8 pass
18 matches
Mail list logo
