Re: Compiling a kernel that works
On Sun, Jun 29, 2003 at 09:12:53PM -0400, Ben Collins wrote: > > That worked fine, once I included the ext3 (which I remembered) and the > > tulip card (which I forgot) > > > > That seems happy. I normally use make-kpkg and install the resulting > > .deb file. Could that be the reason why it is breaking? > > Nope...I use make-kpkg aswell. I'd say you are just creating a kernel > that is missing some needed parts. OK, I'll make-kpkg a kernel with exactly the same config and see if that goes ok. There is still one problem, more annoying than anything. The kernel ignores the kernel parameters, including the root= line. With identical silo configs, an old kernel will know root is /dev/hda1 while the one using your instructions (and when I compile it sometimes if it gets that far) thinks the kernel parameters are "" This happens even if I put it on the silo line, eg linux root=/dev/hda1 The only way to get it to work is to break to the ok prompt and type boot linux root=/dev/hda1 it then knows the kernel paramters are "root=/dev/hda1" and mounts / correctly and happily goes on its way. - Craig -- Craig Small VK2XLZ GnuPG:1C1B D893 1418 2AF4 45EE 95CB C76C E5AC 12CA DFA5 Eye-Net Consulting http://www.enc.com.au/<[EMAIL PROTECTED]> MIEEE <[EMAIL PROTECTED]> Debian developer <[EMAIL PROTECTED]>
Re: Compiling a kernel that works
On Sun, Jun 29, 2003 at 08:05:40PM -0400, Ben Collins wrote: > On Mon, Jun 30, 2003 at 11:07:00AM +1000, Craig Small wrote: > > On Fri, Jun 27, 2003 at 02:37:28PM -0400, Ben Collins wrote: > > > First, compile a stock sparc64 kernel, without any of these patches. Use > > > 2.4.21, and do: > > > > > > cd /usr/src/linux-2.4.21 > > > cp arch/sparc64/defconfig .config > > > make oldconfig > > > make dep > > > make vmlinux > > > > > > After that, try to boot vmlinux. > > > > It says "image too large to fit in destination" > > The next thing would be to cut down the image, but then I'll be back > > where I was before. > > > > -rwxr-xr-x1 root root 3854163 Jun 30 10:31 vmlinux > > "make image" and use arch/sparc64/boot/image That worked fine, once I included the ext3 (which I remembered) and the tulip card (which I forgot) That seems happy. I normally use make-kpkg and install the resulting .deb file. Could that be the reason why it is breaking? - Craig -- Craig Small VK2XLZ GnuPG:1C1B D893 1418 2AF4 45EE 95CB C76C E5AC 12CA DFA5 Eye-Net Consulting http://www.enc.com.au/<[EMAIL PROTECTED]> MIEEE <[EMAIL PROTECTED]> Debian developer <[EMAIL PROTECTED]>
Re: Compiling a kernel that works
On Fri, Jun 27, 2003 at 02:37:28PM -0400, Ben Collins wrote: > First, compile a stock sparc64 kernel, without any of these patches. Use > 2.4.21, and do: > > cd /usr/src/linux-2.4.21 > cp arch/sparc64/defconfig .config > make oldconfig > make dep > make vmlinux > > After that, try to boot vmlinux. It says "image too large to fit in destination" The next thing would be to cut down the image, but then I'll be back where I was before. -rwxr-xr-x1 root root 3854163 Jun 30 10:31 vmlinux > The "Memory Address not Aligned" does not come from SILO or the kernel, > from what I can see. Seems like an OBP message. Not sure what would give > you that. Perhaps try an uncompressed vmlinux instead of a compressed > vmlinuz. I don't know what an OBP is but from what I have read it is the prom giving that message. - Craig -- Craig Small VK2XLZ GnuPG:1C1B D893 1418 2AF4 45EE 95CB C76C E5AC 12CA DFA5 Eye-Net Consulting http://www.enc.com.au/<[EMAIL PROTECTED]> MIEEE <[EMAIL PROTECTED]> Debian developer <[EMAIL PROTECTED]>
Re: Compiling a kernel that works
> This happens even if I put it on the silo line, eg > linux root=/dev/hda1 > > The only way to get it to work is to break to the ok prompt and type > boot linux root=/dev/hda1 > > it then knows the kernel paramters are "root=/dev/hda1" and mounts / > correctly and happily goes on its way. Not sure what you are doing. The current kernels are working ok for me. -- Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ Deqo - http://www.deqo.com/
Re: Compiling a kernel that works
> That worked fine, once I included the ext3 (which I remembered) and the > tulip card (which I forgot) > > That seems happy. I normally use make-kpkg and install the resulting > .deb file. Could that be the reason why it is breaking? Nope...I use make-kpkg aswell. I'd say you are just creating a kernel that is missing some needed parts. -- Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ Deqo - http://www.deqo.com/
Re: Compiling a kernel that works
On Mon, Jun 30, 2003 at 11:07:00AM +1000, Craig Small wrote: > On Fri, Jun 27, 2003 at 02:37:28PM -0400, Ben Collins wrote: > > First, compile a stock sparc64 kernel, without any of these patches. Use > > 2.4.21, and do: > > > > cd /usr/src/linux-2.4.21 > > cp arch/sparc64/defconfig .config > > make oldconfig > > make dep > > make vmlinux > > > > After that, try to boot vmlinux. > > It says "image too large to fit in destination" > The next thing would be to cut down the image, but then I'll be back > where I was before. > > -rwxr-xr-x1 root root 3854163 Jun 30 10:31 vmlinux "make image" and use arch/sparc64/boot/image > > The "Memory Address not Aligned" does not come from SILO or the kernel, > > from what I can see. Seems like an OBP message. Not sure what would give > > you that. Perhaps try an uncompressed vmlinux instead of a compressed > > vmlinuz. > I don't know what an OBP is but from what I have read it is the prom > giving that message. OBP == OpenBoot Prom -- Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ Deqo - http://www.deqo.com/
Re: Compiling a kernel that works
> Old-Return-Path: <[EMAIL PROTECTED]> > Date: Thu, 26 Jun 2003 15:57:38 +1000 > Content-Disposition: inline > From: [EMAIL PROTECTED] (Craig Small) > X-Spam-Level: > Resent-From: debian-sparc@lists.debian.org > X-Mailing-List: archive/latest/12322 > X-Loop: debian-sparc@lists.debian.org > Resent-Sender: [EMAIL PROTECTED] > X-Spam-Status: No, hits=0.0 required=5.0 tests= version=2.20 > X-Spam-Level: > > Hello, > I seem to be having a lot of problems getting a kernel that will work > on the sparc64 arch. All I need it to do is to use a VPN protocol - any > VPN protocol. > > Here is my sorry tale of VPNs > - IPsec - doesn't work because the ioctls fail > - l2tpd - bus error > - pptpd kernel oops if i try to merge the modules in, cannot use new > kernel because of the following problem > > When I try to compile a kernel and then boot it I get this: > Boot device: disk File and args: > If you really just need any vpn try tunnel vision or OpenVPN. Jim
Re: Compiling a kernel that works
Craig Small said: > Hello, > I seem to be having a lot of problems getting a kernel that will work > on the sparc64 arch. All I need it to do is to use a VPN protocol - any > VPN protocol. be sure your using the egcs64 compiler to build the kernel. I have built 2.4.x kernels on my ultra 1 with the 'tun' driver built in(used by vtun). works fine(e.g. doesn't crash), haven't had a need to actually use a vpn on that machine though. the tun driver is also used by other vpn packages as well though I can't remember their names nate
Re: Compiling a kernel that works
On Thu, Jun 26, 2003 at 03:57:38PM +1000, Craig Small wrote: > Hello, > I seem to be having a lot of problems getting a kernel that will work > on the sparc64 arch. All I need it to do is to use a VPN protocol - any > VPN protocol. First, compile a stock sparc64 kernel, without any of these patches. Use 2.4.21, and do: cd /usr/src/linux-2.4.21 cp arch/sparc64/defconfig .config make oldconfig make dep make vmlinux After that, try to boot vmlinux. > Here is my sorry tale of VPNs > - IPsec - doesn't work because the ioctls fail So port the ioctl's. See arch/sparc64/kernel/ioctl32.c > - l2tpd - bus error Report this to the author. Sounds like an unaligned memory access. > - pptpd kernel oops if i try to merge the modules in, cannot use new > kernel because of the following problem The oops you showed means nothing. You need to run it through the ksymoops program. > When I try to compile a kernel and then boot it I get this: > Boot device: disk File and args: > > SILO boot: > > Uncompressing image... > > | > > Memory Address not Aligned > > ok The "Memory Address not Aligned" does not come from SILO or the kernel, from what I can see. Seems like an OBP message. Not sure what would give you that. Perhaps try an uncompressed vmlinux instead of a compressed vmlinuz. -- Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ Deqo - http://www.deqo.com/
Re: Compiling a kernel that works
> >When I try to compile a kernel and then boot it I get this: >Boot device: disk File and args: > >SILO boot: > >Uncompressing image... > >| > >Memory Address not Aligned > >ok > >I've tried gcc-2.95, gcc-3.2 and gcc-3.3 and kernel 2.4.20 and 2.4.21 >It's an Sun X1 system. Which version of Debian do you run? If you're running stable you should use the egcs64 package to compile your kernels. In any other case use gcc-3.2.3 (announced recently by BenC). However, since I've never touched an X1 there may be other issues. Gruss Steffan --- I am the "ILOVEGNU" signature virus. Just copy me to your signature. This email was infected under the terms of the GNU General Public License. pgpiZ5eIN7vsR.pgp Description: PGP signature
