where's the kernel?
Hi, the compile worked fine yesterday (5 hours! ;)), but I can't find an installable package now. I did a make-kpkg --initrd in /usr/src/kernel-source-2.4.21, and there is a binary vmlinux as well as a System.map, but I thought make-kpkg would give me an installable .deb package? Lars
Re: where's the kernel?
Am Donnerstag, 17. Juli 2003 11:30 schrieb Ionut Georgescu: In .., that means in /usr/src/ mh, it looks like drwx--5 adminadmin4096 Jul 4 14:54 kernel-image-2.4.21-1-alpha-2.4.21 -rw-r--r--1 root src 929 Jul 5 07:02 kernel-image-2.4.21-1-alpha_2.4.21-2.dsc -rw-r--r--1 root src 28479 Jul 5 07:02 kernel-image-2.4.21-1-alpha_2.4.21-2.tar.gz drwxr-xr-x3 root root 4096 Jul 14 17:05 kernel-patches drwxr-xr-x 16 root root 4096 Jul 16 16:43 kernel-source-2.4.21 drwxr-xr-x7 root root 4096 Jun 16 2023 rpm here... Lars
Re: where's the kernel?
Am Donnerstag, 17. Juli 2003 11:58 schrieb Ionut Georgescu: did you run 'make_kpkg --initrd kernel_image' ? uhm, no, I ran make-kpkg --initrd. Probably that was the Problem. I did a make-kpkg clean and ran it again, this time as make-kpkg revision=mine2.4.21 --initrd kernel_image Hope that's better ;) Lars
Re: compiler errors: md needed for hardware raid?
Am Dienstag, 15. Juli 2003 16:37 schrieb Patrick Caulfield: I think LVM2 can do at least raid0 on its own. I don't know whether it is well-tested on Alpha, though, I've never used it :) LVM works fine on Alpha, though personally I'm using LVM2 now :-) Yes it wil do RAID0 without md. if you want RAID1 or RAID5 then you need to set up md and /then/ LVM ok, I will leave md out then... Another thing, under /usr/src I have a directory kernel-patches with an executable inside. Do I need to apply those patches manually, or is it done by make-kpkg? Lars
Re: compiler errors: md needed for hardware raid?
Am Dienstag, 15. Juli 2003 16:37 schrieb Patrick Caulfield: LVM works fine on Alpha, though personally I'm using LVM2 now :-) Yes it wil do RAID0 without md. if you want RAID1 or RAID5 then you need to set up md and /then/ LVM hm, I just wanted to remove md support from the kernel, but that deactivates LVM also... In xconfig it's under the option Multi device support (Raid and LVM), and when I remove the Multiple devices driver support (RAID and LVM), the option LVM support gets greyed out... Lars
installing kernel-image
Hi, I'm first trying again the kernel-image of 2.4.21. I did a apt-get for the kernel-image, and got told to configure my bootloader. It already happened to me when trying to install a kernel-image, that the machine wouldn't come up again (I have no root I want to scream). So before rebooting I want to be sure to have everything correct ;) What I find a bit confusing, is that I now have a link /initrd.img that points to a initrd in /boot. So far so good, but I can't find any reference to that initrd.img elsewhere. I think at boot time the bootloader needs to know what initrd to load? My /etc/abbot.conf just looks like this: 0:2/vmlinuz ro root=/dev/rd/c0d0p2 is that enough? On my last install try I think my problem was that initrd.img was not loaded... Lars
RE: installing kernel-image
What I find a bit confusing, is that I now have a link /initrd.img that points to a initrd in /boot. So far so good, but I can't find any reference to that initrd.img elsewhere. I think at boot time the bootloader needs to know what initrd to load? My /etc/abbot.conf just looks like this: what I forgot: I also have an empty directory /initrd Lars
RE: installing kernel-image
You have to pass the path to the initrd image. aboot.conf here: ok, I think I'm understanding the boot process more now. Just in case, I want to make a second boot configuration with the old kernel. While I have vmlinuz-2.2.20-generic in /boot, I can't find any initrd but the new ones. Did 2.2.20 not use an initrd? Or did it get deleted while installing the new kernel-image? Another question is, how can I select another boot-configuration at boot time? I configured aboot to automatically boot vmlinuz... Lars
AW: installing kernel-image
hm, what I feared happened, the machine doesn't boot that kernel. A bit of thinking would have made that obvious to me, I have root=/dev/rd/c0d0p2 in aboot, but without DAC960 support in the kernel, it can't be mounted at boot time. A boot drb0 -flags 1 (which points to my 2.2.20 kernel) doesn't work correct, since aboot tells me it doesn't know what to do with the first partition (swap) fortunately, I could get up again with p 2 (pointing to partition 2) and 1 (using aboot config 1) in aboot. Seems I really have to compile that kernel ;) Lars
compiler errors: md needed for hardware raid?
Hi, when trying to compile the 2.4.21 kernel I get compiler errors within /drivers/md: make[4]: Entering directory `/usr/src/kernel-source-2.4.21/drivers/md' gcc -D__KERNEL__ -I/usr/src/kernel-source-2.4.21/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mno-fp-regs -ffixed-8 -mcpu=ev5 -Wa,-mev6 -nostdinc -iwithprefix include -DKBUILD_BASENAME=linear -c -o linear.o linear.c gcc -D__KERNEL__ -I/usr/src/kernel-source-2.4.21/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mno-fp-regs -ffixed-8 -mcpu=ev5 -Wa,-mev6 -nostdinc -iwithprefix include -DKBUILD_BASENAME=raid0 -c -o raid0.o raid0.c gcc -D__KERNEL__ -I/usr/src/kernel-source-2.4.21/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mno-fp-regs -ffixed-8 -mcpu=ev5 -Wa,-mev6 -nostdinc -iwithprefix include -DKBUILD_BASENAME=raid1 -c -o raid1.o raid1.c gcc -D__KERNEL__ -I/usr/src/kernel-source-2.4.21/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mno-fp-regs -ffixed-8 -mcpu=ev5 -Wa,-mev6 -nostdinc -iwithprefix include -DKBUILD_BASENAME=raid5 -c -o raid5.o raid5.c gcc -D__KERNEL__ -I/usr/src/kernel-source-2.4.21/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mno-fp-regs -ffixed-8 -mcpu=ev5 -Wa,-mev6 -nostdinc -iwithprefix include -DKBUILD_BASENAME=xor -DEXPORT_SYMTAB -c xor.c In file included from xor.c:23: /usr/src/kernel-source-2.4.21/include/asm/xor.h:35:5: missing terminating character In file included from xor.c:23: /usr/src/kernel-source-2.4.21/include/asm/xor.h:36: error: request for member `text' in something not a structure or union /usr/src/kernel-source-2.4.21/include/asm/xor.h:37: error: syntax error before numeric constant /usr/src/kernel-source-2.4.21/include/asm/xor.h:62: error: syntax error at '#' token /usr/src/kernel-source-2.4.21/include/asm/xor.h:87:17: invalid suffix b on integer constant /usr/src/kernel-source-2.4.21/include/asm/xor.h:119: error: syntax error at '#' token /usr/src/kernel-source-2.4.21/include/asm/xor.h:120: error: syntax error at '#' token /usr/src/kernel-source-2.4.21/include/asm/xor.h:121: error: syntax error at '#' token /usr/src/kernel-source-2.4.21/include/asm/xor.h:122: error: syntax error at '#' token xor.c: In function `calibrate_xor_block': xor.c:117: error: `xor_block_alpha' undeclared (first use in this function) xor.c:117: error: (Each undeclared identifier is reported only once xor.c:117: error: for each function it appears in.) make[4]: *** [xor.o] Error 1 make[4]: Leaving directory `/usr/src/kernel-source-2.4.21/drivers/md' make[3]: *** [first_rule] Error 2 make[3]: Leaving directory `/usr/src/kernel-source-2.4.21/drivers/md' make[2]: *** [_subdir_md] Error 2 make[2]: Leaving directory `/usr/src/kernel-source-2.4.21/drivers' make[1]: *** [_dir_drivers] Error 2 make[1]: Leaving directory `/usr/src/kernel-source-2.4.21' make: *** [stamp-build] Error 2 I couldn't find anything on this error at google, so my question is: is the md driver needed for hardware raids or is it just for software raids? So I could perhaps completely leave it out... Lars
Re: AW: installing kernel-image
Am Dienstag, 15. Juli 2003 15:14 schrieb Tyson Whitehead: Sounds like you must have installed a new copy of aboot at some time on the front of your drive (i.e. did a 'swriteboot /dec/sda bootlx' -- bootlx is built with the Alpha kernel and contains the aboot image). hm, I installed aboot when installing woody. If you were doing repartitioning, etc, make sure you left space at the front of the drive for aboot (the swriteboot man page advises you leave 512 sectors). Otherwise there will be problems once Linux starts using that swap partition. :) I left that space back then... Until now, Linux seems not to have a problem using that swap partition. In any event, the problem is that your newly installed aboot is configured by default to look for your /etc/aboot.conf file on the first partition. Use 'abootconf /dev/sda 2' to change that to the second partition. I guess a 'abootconf /dev/c0d0p2' will do the correct thing for me, since I boot from a raid? You will have to change the /dev/sda bit to your correct boot device. uh, what? Lars
Re: compiler errors: md needed for hardware raid?
Am Dienstag, 15. Juli 2003 15:20 schrieb Ionut Georgescu: What does gcc -v say ? You need gcc-3.x for the alpha. gcc version 3.3.1 20030626 (Debian prerelease) PS apt-get remove cpp-2.95 will remove gcc 2.95.x and automatically install gcc-3.x (in testing at least) yup, did that, because just installing 3.3 wouldn't make it active ;) Lars
Re: compiler errors: md needed for hardware raid?
Am Dienstag, 15. Juli 2003 15:19 schrieb Falk Hueffner: Eek. That file uses multiline string literals, which is no longer accepted by gcc. You could just start each line within the asm argument with and finish with \n\t. uhoh... Software. mh, ok... But I found that I need some kind of software raid, I have several partitions on external cabinets (that old mylex controllers support partitions only up to 32Gb) and I want to combine those to one big drive. I took a look ant md and LVM now, but what I didn't find is, does LVM need md? or is it more of a replacement for it? Cause then I could just use LVM... Lars
Re: compiling 2.4.20
Am Mittwoch, 9. Juli 2003 15:53 schrieb Ionut Georgescu: apt-get build-dep kernel-image-2.4.21-1-generic strange again... When I try that, I get E: Build-Depends dependency on kernel-image-2.4.21-1-alpha cannot be satisfied because the package kernel-tree-2.4.21-1 cannot be found and a dpkg -l kernel* only reveals sources up to 2.4.20. Is my sources.list bad?: #stable deb http://ftp.de.debian.org/debian stable main contrib non-free deb http://security.debian.org/ stable/updates main #testing deb http://ftp.de.debian.org/debian testing main contrib non-free deb http://security.debian.org/ testing/updates main #source deb-src http://ftp.de.debian.org/debian stable main contrib non-free deb-src http://security.debian.org/ stable/updates main deb-src http://ftp.de.debian.org/debian testing main contrib non-free deb-src http://security.debian.org/ testing/updates main
Re: compiling 2.4.20
Am Montag, 14. Juli 2003 15:37 schrieb Ionut Georgescu: the package is called kernel-tree-2.4.21 and is located in unstable ah, ok, I had no source for unstable. But I get funny things now with apt-get update: Reading Package Lists... Error! E: Dynamic MMap ran out of room is that a memory problem? Diskspace should be enough... Lars
Re: compiling 2.4.20
Am Montag, 14. Juli 2003 15:47 schrieb Lars Oeschey: Reading Package Lists... Error! E: Dynamic MMap ran out of room is that a memory problem? Diskspace should be enough... ok, solved it, got the sources. Lars
RE: compiling 2.4.20
debian already provides 2.4.21 binaries. If you want to compile them by yourself, I would suggest: apt-get build-dep kernel-image-2.4.21-1-generic apt-get source kernel-image-2.4.21-1-generic hm, I just tried that, but apt-get told me I need some sources in my sources list. I only have stable and testing there, I guess build-dep and source are sources that must be listed there? Lars
what's in the kernel?
Hi, I'm running 2.2.20 on a Alphaserver 1000A. I'm new to debian, used to have Suse mostly. Since I trusted the apt-get installation, I tried a upgrade to 2.4.18, but the machine didn't come up again (I have no root, I want to scream). After some fiddling to get back booting the 2.2.20 kernel, I found that the 2.4.18 installation made me a initrd.img file in the root dir, while the old kernel seemed to have a initrd file at the same place. Since there's no lilo (I think), where do I tell what initrd file to use? And another thing is, I'm not too sure that there's Mylex DAC960 support in the 2.4.18 kernel, and I have to boot from a raid5. How can I check what's compiled into the kernel? Lars
Re: compiling 2.4.20
Am Mittwoch, 9. Juli 2003 14:55 schrieb Falk Hueffner: 2.4.20 has serious bugs on Alpha, you should rather use 2.4.19 or 2.4.21. A bug in gcc. Which version are you using? If you're not using gcc 3.3, try upgrading. I upgraded now to 3.3 since I found a similar answer somewhere on the net. The compile failed again somewhere else though, but I'll try 2.4.21 then first (the odd numbers were the stable ones?). Do I only need the kernel-source package? I saw some kernel-header packages too... Lars
Re: compiling 2.4.20
Am Mittwoch, 9. Juli 2003 15:53 schrieb Ionut Georgescu: debian already provides 2.4.21 binaries. If you want to compile them by yourself, I would suggest: I would use the precompiled one, but I guess that one again has DAC960 support only as module, and since I boot from a Raid5 on a DAC960 I think I need to have it compiled into the kernel. Lars
Re: compiling 2.4.20
Am Mittwoch, 9. Juli 2003 16:06 schrieb Linus Gasser: Do you use the debian-tool for compiling the kernel? Like make-kpkg? Yes. Or at least I try to ;) Lars
