by duke n mari » Fri, 19 Jan 2001 01:22:18
by Michael Heimin » Sun, 21 Jan 2001 08:31:16
just an idea, are your permission on /dev/ttyS? setup that users can
read/write to it,
asuming you have everything updated mentioned in Documentation/Changes.
Good luck
Michael Heiming
1. does 2.4 kernel need 2.4 initrd?
No, not if you build the adaptec driver into the kernel.
The initrd must match the kernel *exactly*, i.e., you can't even use an
initrd-2.2.14-... with a 2.2.16 kernel.
You *do* have the 2.4 modutils, do you?
Sure it was - but you really only have to build the driver of the boot-
device into the kernel - you could leave the rest as modules.
Should still be possible *if* you have left something as modules.
One pragmatic solution is to build anything that is needed to boot into
the kernel and leave the rest (which can be loaded later) as modules.
In that case, you don't need an initrd at all.
Yes. The order should always be
build kernel, build & install modules, mkinitrd
HTH
Anders
2. Start Noatun minimized with Young Hickory Icon in dock panel
3. PROBLEM: my Aviator Webgear 2.4 doesn't work with kernel version 2.4.x
4. Linux firewire "target mode" available?
5. Help: Connecting Solaris 2.4 and NT Workstation with PPP
7. Solaris 2.4 X86 Crashes After/During PPP Connect
8. Sound Card
9. cannot load modules with 2.4 kernel
10. Cannot get Creative Vibra16x Soundcard to work on alsa (2.4 kernel, SUSE 7.1)
11. server stuck in LAST_ACK state when I connect to it(linux 2.4 kernel)
12. Kernel headers....ppp, 2.4, 2.5