Re: need kernel 2.4 to install
--- dman <dsh8290@rit.edu> wrote:
> On Tue, Aug 14, 2001 at 08:00:50AM -0700, Jeff
> wrote:
> | Hello,
> | I am currently planing on putting Debian on a
> small
> | partition on another machine just for playing
> with.
> | This wouldn't be a problem but the network card is
> a
> | newer linksys card that I've only been able to get
>
> What revision? I have a Linksys LNE100TX rev 4.1
> that works just fine
> with the tulip module in 2.2.19.
>
> | going with the 2.4.x series kernels. I have also
> been
> | able to install an old version of redhat once (or
> some
> | rpm based distro anyway) and then upgrade the
> tulip
> | driver and off I went. Question I have is since
> the
> | woody boot disks use 2.2.19 will they have the
> newer
> | tulip driver or the old one? I would just use my
> | potato cd but I scratched it some time ago and
> it's
> | now out of commission. I really dont want to make
> a
> | new potato cd just to get the kernel source
> installed,
> | upgrade the driver, then put sid on the machine.
> I
> | can't think of how to get Debian on this machine
> any
> | other way since I don't have a cd. Any thoughts
> are
> | welcome. Thanks
>
> Can you borrow another NIC from somewhere to do the
> upgrade (after the
> 2.2.19 install) then switch the NICs back?
>
> -D
>
>
> --
> To UNSUBSCRIBE, email to
> debian-user-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
Ok thanks they do work somewhat. I have the same card
but rev 4. Now the boot disks are setting up the
network correctly but not accessing it. It's very
strange because I've tried setting it up many times
and keep coming to the same thing. The packets are
not being accepted from either machine. The one thats
has the install going is 192.168.0.2 on eth0 using
192.168.0.1 as a gateway. I put in my isp's
nameservers and everything. I cannot get the boxes to
even see each other though. When I ping from the main
machine (192.168.0.1) it sends the packets and the
lights on the hub blink but it doesn't recieve a
reply. If I switch to another term from the install
(alt+F2) and ping 192.168.0.1 I get nothing (not even
flickering lights on the hub) if I ping eth0 on the
machine I'm trying to get the install going on it
works. They can't ping one
another. ifconfig shows that eth0 is in fact set up
properly but the only activity that has passed through
is RX packets dropped (1310700) and TX packets errors
(32). Now this same setup has been working great for
me so far.... Oh well I guess I'll just keep trying
now that the network card is working.
Heres what I did during the install from the idepci
1.44 boot disks:
Hostname = graffix
DHCP or BOOTP = no (i use 192.168.0.2 for this box)
IP address = 192.168.0.2
NETMASK = 255.255.255.0
GATEWAY = 192.168.0.1
Domain Name = localdomain
DNS Servers = 216.67.47.55 216.67.14.5
And I leave proxy at none. I get resolving http.....
via DNS If there is an error it will eventually time
out and return control. Press Ctrl-C to interrupt.
Now I wait and watch while no activity lights are
going on the hub and it looks like no activity is
going on. Then I get the error nf_http_fetchfile ::
http.us.debian.org couldn't be resolved, Host name
lookup failure (h_errno=2). And of course the next
screen is download failed for the file
'images-1.44/idepci/rescue.bin'. It cannot be the
server because it has been acting as a gateway like
this for months and I haven't changed a thing. Any
help or ideas would be greatly appreciated.
Jeff
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
Reply to: