Re: New user teething problems: tulip on 2.2.20

[Bill Freeman <f@ke1g.mv.com>]

Jacob S writes:
 > On Tue, 29 Mar 2005 12:19:43 -0500
 > Bill Freeman <f@ke1g.mv.com> wrote:
 > 
 > > 	I'm new to Debian, but a long time Linux user.  I came into
 > > possesion of a Compaq Presario 1200Z and decided that it was time that
 > > I tried Debian.
 > > 
 > > 	I grabbed the CD version of the net install of woody, and
 > > everything went smoothly.
 > > 
 > > 	However, I decided that I wanted sound, and the installed
 > > kernel was 2.2.20-idepci, which, among other things, doesn't have
 > > sound support.
 > > 
 > > 	So I used the package manager under system on kde (a front
 > > end for apt, I presume) to grab the straight 2.2.20 kernel (which I
 > > understand includes most things).  And it boots just fine.
 > > 
 > > 	Except that I can no longer load the tulip module.  modprobe
 > > tulip yeilds:
 > > 
 > > /lib/modules/2.2.20/net/tulip.o: init_module: Device or resource busy
 > > ...
 > > 
 > > 
 > > 	I also tried the 2.4.16 kernel, which also can't load tulip,
 > > though the error message is slightly different (something like device
 > > does not exist).
 > > 
 > > 	Several live CD's work fine with this interface.  Knoppix 3.7,
 > > for example, still uses the tulip module.
 > > 
 > > 	One thing that I noticed running 2.2.20-idepci is that lsmod
 > > says that pci-scan is loaded and that tulip uses it.  There is no
 > > pci-scan.o anywhere under /lib/modules/2.2.20/ , and the one from
 > > /lib/modules/2.2.20-idepci/net won't work with the 2.2.20 kernel (of
 > > course it might be built into the 2.2.20 kernel).
 > > 
 > > 
 > > 	So, am I missing something obvious, or is it perhaps a bug
 > > that the 2.2.20 kernel .deb doesn't include pci-scan.o, or what?
 > 
 > 2.2.20 is a pretty old kernel. I would try at least upgrading to the
 > latest 2.4 kernel in Woody.

	I did try the 2.4.16 kernel, the next to newest, and, as
mentioned above, it couldn't load tulip either.  I attempted to try
the newest (first, actually) which is 2.4.18, but it wouldn't boot,
and caused file system corruption (had to run fsck by hand).  That may
be because I tried the -k7 version (sticker on case says duron, WinXP
says mobile duron).  I guess I could try the -i386 (as I did with
2.4.16).

	I'm actually attracted to 2.2, however, since, if I'm
remembering correctly, it has a smaller footprint (box only has 128Mb
RAM).  I suppose that I should try building 2.2.22.  If I'm right
about it being a failure to package pci-scan with 2.2.20, then
building my own should work even with 2.2.20 (after all, it works with
2.2.20-idepci).

 > Better yet, if this is just a test box,

	Not really.  It's on loan for a specific project, and If I can
make xcircuit, pcb, gpsim, and maybe geda work, then best stability is
probably desired.

 > download the new Debian-Installer[1] and install Sarge on the box.
 > Knoppix is based on Debian Testing/Sarge and Unstable/Sid.

	So the take home message is that stable isn't and that testing
and unstable are?

	I've actually burned myself sarge DVDs over night, and will
probably be taking this route pretty soon, if I can't make woody work.

							Bill