[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: ethernet support in 2.2.20-20011202 kernel

Hi Erik,

Most informative. I had been wondering what all the extra files were used for! Thanks for clearing that up. I 
have just re-installed everything from scratch anyway, since I tried to install some packages on the machine 
and the hard drive got full. I thought maybe I had just managed to fill it all with rubbish during the 
dselect process. However, it now seems like it is more likely to be that I just don't have enough HD space 
anyway. Here's the HD spec:

120 MB HD (in total), split as follows:

30 MB mac HFS to boot off
40 MB linux swap (physical RAM is 20 MB and it says in the install info that you should have double this)
50 MB (all the remaining space on the HD - linux main partition)

I have just seen in a tech note that "55 MB" is the minimum for an install of a base system and "the more HD 
space the better". Hence, it looks like before doing anything else, I need a bigger HD.

When that machine was new, it had a "big" HD (120MB). I think the standard size was 80MB.

Suggestions of a good working size of HD (and bearing in mind that I am not trying to spend more on a new HD 
than the whole machine is worth)? I was thinking at least one Gig.



>Date:          Fri, 22 Mar 2002 17:23:31 +0100
>From:          "Erik C.J. Laan" <elaan@dds.nl>
>Organization:  Wherever.....
>To:            n.r.helps@dundee.ac.uk
>Subject:       Re: ethernet support in 2.2.20-20011202 kernel
>Nicholas Helps wrote:
>> You certainly hit the nail on the head there! I did some more digging on the net after your email and it
>> seems that the standard debian download has a 2.2.10 kernel (well old). I used the 2.2.20 vmlinux... 
>> file off the Sourceforge site and this works fine. It seems a little quicker > overall than the 2.2.10 one 
>> the ethernet driver (v0.4...) works just great. I can ping backward and forward between my PC laptop and 
>> with no problem.
>> On reflection, there are lots of pointer to the old kernel not being what I thought it was. However, as 
>> most things when you are new to them, sometimes it is difficult to see the "wood for the trees".
>> One thing I would like to do now is to install the newer version of everything onto the mac (eg modules,
>> etc). Especially since I now get lots of "module dependency" errors popping up during the boot (it can't 
>> module.dep file in lib/2.2.20/). There is a patch that came with the other 2.2.20 files, but I don't know 
>> to use that. I am also not completely sure which of the other files in the set of 2.2.20 files replaces 
>> original debian ones (drivers, sysmap etc).
>> As usual, any help from anyone would be appreciated.
>If you upgrade to a newer kernel and you need modules (most people
>don't) you should get the modules that where compiled at the same time
>as the kernel. Modules compiled at a differen time as the kernel
>generally don't work (unless specific measures are taken at
>compile-time). This even goes for kernels and modules with the same
>version number! Because most of the drivers for Mac's are compiled into
>the kernel most people don't need modules so some/most of the kernels on
>linux-mac68k.sourceforge.net are compiled without modules just to test.
>Every once in a while one of the few kernel-developers does the full
>compile of kernel and modules and puts them on sf.
>To clear up the module-dependencies errors you can:
>1)	Ignore them if you don't need any modules, just create a directory
>/lib/modules/<kernel-version>/* and the errors go away after a 'depmod
>-a' (but you won't have modules).
>2)	Install the modules corresponding to your kernel in
>/lib/modules/<kernel-version>/* and do a 'depmod -a'.
>I think the 2.2.20 kernel (of is it 2.2.19?) is also available from
>debian.org if there are no modules in sourceforge. The debian
>kernel-package also contains the System.map file and the
>kernel-.config-file file corresponding to the kernel that's in the
>package. "Normally" (meaning on i386 etc. archs) the
>kernel+modules-tarball or the debian kernel-package install modules and
>kernel (and System.map and .config) in the right place, being your
>ext2-root-filesystem. You subsequently run lilo to update the boot-place
>of the drive to see the new kernel. Because on MacOS the kernel needs to
>be on the MacOS' HFS partition, things should go into slightly different
>Item:		Should be placed in:
>-----		--------------------
>kernel:		your MacOS' HFS partition where Penguin can load it (and
>		maybe a copy to /boot as backup) and Penguin should the 
>		pointed to it.
>modules:	/lib/modules/<kernel-version>/*
>System.map	/boot
>kernel-config	where you'd like it.
>So when are these items needed (correct me if I'm wrong):
>kernel:		at boot-time ... ;-)
>modules:	when creating the modules.dep file or loading modules.
> 		Every distro I know generates a fresh modules.dep at 
>		boot-time but there's no real need to, you just need to do 
>		this after installing new modules. If you don't have or need 
>		modules you can delete this step, ignore any errors or
>		let depmod create a bogus file (that's why you need to create
>		the directory in option 1) above).
>System.map	Only needed and used to resolve function addresses to symbols
>		when debugging kernel-errors.
>kernel-config	Only needed when the kernel is compiled (and for your
>		information/reference).
>Hope this helps, Erik
>Erik C.J. Laan				elaan at dds.nl

To UNSUBSCRIBE, email to debian-68k-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reply to: