Re: Problem with Kernal Source 2.0.27_1.00
On Sat, 14 Dec 1996, J. Ramos Goncalves wrote: > Proceed like this: > > cp /usr/src/kernel-source-2.0.27/arch/i386/boot/zImage /boot/linux-2.0.27 > cp /usr/src/kernel-source-2.0.27/System.map /boot/System.map-2.0.27 > ln -s /boot/linux-2.0.27 /vmlinuz > ln -s /boot/System.map-2.0.27 /System.map There is an easier way. From the source tree, I did this for 2.0.27: make-kpkg -revision 2.0.27-tech.1 kernel_image cd .. dpkg -i kernel-image-2.0.27_2.0.27-tech.0_i386.deb lilo reboot (Machine name is 'tech'; I use actual source, not the kernel-source package.) However, does anyone know why I have to manually run lilo after installing the kernel? |This is OFFICIAL WRITTEN notification that I want to be REMOVED| |from ALL commercial mailing lists. EVERY message sent from this | | account has had this request posted. ALL UNSOLICITED ADVERTISEMENTS | | SENT TO THIS ACCOUNT ARE IN VIOLATION OF FEDERAL (U.S.) LAW. | | Opinions expressed are not necessarily those of Cyclades Corporation. | -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Problem with Kernal Source 2.0.27_1.00
Hi Alexander, You wrote: > Now it works! :-) > > Thanks. I think that a good thing would be, for beginners like > me, a command "help" to do in prompt, like that of MSDOS, > but without those cryptographic "technical aspects". Something > more clean than man or info, like "ls do this, man do that, > cp do ...", including kernel compilation, what to do when a > library is in the directory but the program don't find it, > etc. Can anyone do this in a debian "tips-and-tricks_1.0.deb" > or "what-you-ever-whant-to-know_1.0.deb" package? -user-beta-1.lsm Title: Linux Users' Guide Version:beta-1 Entered-date: 07DEC96 Description:The Linux System Users' Guide (SAG) is a free book targeted at novice Unix users. Keywords: intro unix, users' guide, LDP, book Author: Larry Greenfield <[EMAIL PROTECTED]> Primary-site: sunsite.unc.edu /pub/Linux/docs/LDP/users-guide/ Copying-policy: FSF book or GPL Will this do?:-) This version is still in ~/Incoming at sunsite.unc.edu Later, David -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Problem with Kernal Source 2.0.27_1.00
> > Hi. I don't know about this, but i'm with problems in making > > the kernel I compiled to work. All the compilation and linking > > is ok. I've used the sequence: > > > > make menuconfig > > make dep > > make zImage > > make modules > > make modules_install > > You should add a "make clean" just before make zImage (you don't > need it if it is the first time you are compiling a kernel). > > > that I think is correct. When it's done, I copy the 'vmlinux' file > > to '/', update '/etc/lilo.conf', and execute '/sbin/lilo'. All is > > ok, but when the system reboots, lilo begins an infinite loop: > > Proceed like this: > > cp /usr/src/kernel-source-2.0.27/arch/i386/boot/zImage /boot/linux-2.0.27 > cp /usr/src/kernel-source-2.0.27/System.map /boot/System.map-2.0.27 > ln -s /boot/linux-2.0.27 /vmlinuz > ln -s /boot/System.map-2.0.27 /System.map > > I suppose you are using a PC. Your lilo.conf file should point to > /vmlinuz. Run lilo and reboot the system. It should work. Now it works! :-) Thanks. I think that a good thing would be, for beginners like me, a command "help" to do in prompt, like that of MSDOS, but without those cryptographic "technical aspects". Something more clean than man or info, like "ls do this, man do that, cp do ...", including kernel compilation, what to do when a library is in the directory but the program don't find it, etc. Can anyone do this in a debian "tips-and-tricks_1.0.deb" or "what-you-ever-whant-to-know_1.0.deb" package? Alexander Gieg =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= By: Alexander Gieg E-mail: [EMAIL PROTECTED] URL: http://www.geocities.com/TimesSquare/3222 IRC: AlexG =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Problem with Kernal Source 2.0.27_1.00
There's a separate package that contains as86. The package is bin86 and can be found from section devel. Here's the description: Assembler and loader for kernel compilation. In message <[EMAIL PROTECTED]>you write: > kernal. I get most of the way through the make zImage phase and the > process stops with the following error message > > as86 -0 -a -o bootsect.o bootsect.s > make[1]: as86: Command not found -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Problem with Kernal Source 2.0.27_1.00
Installing a custom kernel following the direction in: /usr/doc/kernel-source-2.0.27/debian.README.gz but before you do this, you need to apply the patch described in Bug #5659. Unfortunately, this fix didn't get into the Debian-1.1 release. -- Kevin Dalley [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Problem with Kernal Source 2.0.27_1.00
On Sat, 14 Dec 1996, Alexander Gieg wrote: > > Hi. I don't know about this, but i'm with problems in making > the kernel I compiled to work. All the compilation and linking > is ok. I've used the sequence: > > make menuconfig > make dep > make zImage > make modules > make modules_install You should add a "make clean" just before make zImage (you don't need it if it is the first time you are compiling a kernel). > > that I think is correct. When it's done, I copy the 'vmlinux' file > to '/', update '/etc/lilo.conf', and execute '/sbin/lilo'. All is > ok, but when the system reboots, lilo begins an infinite loop: > Proceed like this: cp /usr/src/kernel-source-2.0.27/arch/i386/boot/zImage /boot/linux-2.0.27 cp /usr/src/kernel-source-2.0.27/System.map /boot/System.map-2.0.27 ln -s /boot/linux-2.0.27 /vmlinuz ln -s /boot/System.map-2.0.27 /System.map I suppose you are using a PC. Your lilo.conf file should point to /vmlinuz. Run lilo and reboot the system. It should work. > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > By: Alexander Gieg > E-mail: [EMAIL PROTECTED] > URL: http://www.geocities.com/TimesSquare/3222 > IRC: AlexG > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= I hope it helps. Ramos. - J. RAMOS Goncalves | E-mail: [EMAIL PROTECTED] Department of Physics - University of Reading - England - U.K. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Problem with Kernal Source 2.0.27_1.00
> I am in the process of setting up my machine to run debian, > everything has been running reasonably well until now. I downloaded > the kernal-source-2.0.27_1.00.deb and attempted to compile a custom > kernal. I get most of the way through the make zImage phase and the > process stops with the following error message Hi. I don't know about this, but i'm with problems in making the kernel I compiled to work. All the compilation and linking is ok. I've used the sequence: make menuconfig make dep make zImage make modules make modules_install that I think is correct. When it's done, I copy the 'vmlinux' file to '/', update '/etc/lilo.conf', and execute '/sbin/lilo'. All is ok, but when the system reboots, lilo begins an infinite loop: Lilo loading Linux Lilo loading Linux ... So, I press , and make the system load the old kernel. What's wrong? It's some option that is necessary in kernel? I've tried other things to, like a 'make clear', or mark and unmark some options in menuconfig, but nothing works. Other thing: I don't have a PCI bus in my machine, so I've unmarked the PCI options in menuconfig, but in this case, there is some unreferenced links to some "...pci..." functions, and the kernel isn't linked. So, I've remarked the PCI options. The PCI functions are necessary for other options? If yes, which are? They can be unmarked securely? Thanks. Alexander Gieg =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= By: Alexander Gieg E-mail: [EMAIL PROTECTED] URL: http://www.geocities.com/TimesSquare/3222 IRC: AlexG =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: Problem with Kernal Source 2.0.27_1.00
Nope, "as86" is the wrong one. Install the "binutils" package, and you'll get "as". You also need as86 for other things, but unless I'm mistaken it's used only to assemble 16-bit code like boot sectors. Bruce -- Bruce Perens K6BP [EMAIL PROTECTED] Finger [EMAIL PROTECTED] for PGP public key. PGP fingerprint = 88 6A 15 D0 65 D4 A3 A6 1F 89 6A 76 95 24 87 B3 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Problem with Kernal Source 2.0.27_1.00
I am in the process of setting up my machine to run debian, everything has been running reasonably well until now. I downloaded the kernal-source-2.0.27_1.00.deb and attempted to compile a custom kernal. I get most of the way through the make zImage phase and the process stops with the following error message as86 -0 -a -o bootsect.o bootsect.s make[1]: as86: Command not found After perusing the makefile I decided to add a symlink: usr/include/as86 -> usr/include/as Now the compile breaks with this error: as86 -0 -a -o bootsect.o bootsect.s as86: unrecognized option -0 I am using gcc 2.7.2.1 and binutils 2.7.0.3 as the Changes file recommends. I also made the symlinks that Linus calls out in the README file. All of the packages that seem connected to this were loaded using Dselect-ftp with an updated Packages file tonight. This system has been up less than a week, so it isn't too cluttered with outdated files. Any suggestions would be appreciated. Thanks "Less is more; more or less." -Ludwig Mies Van Der Rohe (Sort of) -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
