Re: Help. Trying to upgrade to hamm 2.0.36

1999-02-17 Thread Gary L. Hennigan 
Tim Heuser [EMAIL PROTECTED] writes:

|  o  type make zImage
| 
| I got to the make zImage command and sat around till the computer got done 
processing all kinds of stuff.
| The last 6 lines printed to the screen were...
| 
| as86 -0 -a -o bootsect.o bootsect.s
| make [1]: as86: command not found
| make [1]:*** [bootsect.o] Error 127
| make [1]: Leaving directory `/usr/src/kernel-source-2.0.36/arch/i386/boot'
| make:*** [zImage] Error 2
| coyote:/usr/src/linux#

Umm, you need to install the bin86 package. You may also want to take
a look at make-kpkg in the kernel-package package. It automates kernel
compilation a bit and gives you a nice Debian package that you can
install with dpkg. The short of it is you to a make x|menuconfig and 
then simply do a:

make-kpkg --revision custkernel.1 --bzimage kernel_image

This proceeds to compile the kernel and when it's done it'll produce a 
kernel-imagewhatever.deb file in .. which can be installed with:

dpkg -i kernel-imagewhatever.deb

Do a man make-kpkg to the details for yourself first. And read
the documentation in /usr/doc/kernel-package.

When I first heard about it I thought it was a waste of time. I've
been building kernels manually since 0.99, but it really is a nifty
piece of work that simplifies a lot of things for you.

Gary

Re: Help. Trying to upgrade to hamm 2.0.36

1999-02-17 Thread Bob Nielsen 
On Tue, 16 Feb 1999, Tim Heuser wrote:

 
  o  type make zImage
 
 I got to the make zImage command and sat around till the computer got done 
 processing all kinds of stuff.
 The last 6 lines printed to the screen were...
 
 as86 -0 -a -o bootsect.o bootsect.s
 make [1]: as86: command not found
 make [1]:*** [bootsect.o] Error 127
 make [1]: Leaving directory `/usr/src/kernel-source-2.0.36/arch/i386/boot'
 make:*** [zImage] Error 2
 coyote:/usr/src/linux#

Install the bin86 package.

Bob


Bob Nielsen Internet: [EMAIL PROTECTED]
Tucson, AZ  AMPRnet:  [EMAIL PROTECTED]
DM42nh  http://www.primenet.com/~nielsen

Re: Help. Trying to upgrade to hamm 2.0.36

1999-02-17 Thread Tim Heuser 




 Tim> Where might I find the Debian 2.2.1 kernel
source?
The Debian kernel-source package is at:
 ftp://ftp.debian.org/debian/dists/potato/main/binary-i386/devel/kernel-source-2.2.1_2.2.1-1.deb
I'm downloading the "deb" now..

Or the raw sources:
 ftp://ftp.kernel.org/pub/linux/kernel/v2.2/linux-2.2.tar.gz
 >> Also, instead of doing all those steps listed
below manually,
 >> try using the 'make-kpkg' Debian utility.
("man make-kpkg" for
 >> details). If you do not have it, it is
in the 'kernel-package'
 >> Debian package.
 >>
 >> To build a kernel image, go to a kernel top-level
directory,
 >> and type something like:
 >>
 >> # make xconfig
 Tim> I assume this would be something like /usr/src/linux-2.2.1
?
If you have 'kernel-source' package, you can:
(That is the "deb" one., right?) and thanks again. I'll give this
a shot tomorrow.
 # cd download-directory>
 # dpkg --install kernel-source-2.2.1_2.2.1-1.deb

 # rm kernel-source-2.2.1_2.2.1-1.deb
 # cd /usr/src
 # tar zxvf kernel-source-2.2.1.tar.gz
 # cd kernel-source-2.2.1
 # make xconfig
 answer questions>
 # make-kpkg kernel_image
 # cd ..
 # dpkg --install kernel-image-2.2.1_1.00_i386.deb
-tor

Re: Help. Trying to upgrade to hamm 2.0.36

1999-02-17 Thread Tim Heuser 
Tim Heuser wrote:

 # cd download-directory
 # dpkg --install kernel-source-2.2.1_2.2.1-1.deb

 # rm kernel-source-2.2.1_2.2.1-1.deb
 # cd /usr/src
 # tar zxvf kernel-source-2.2.1.tar.gz
 # cd kernel-source-2.2.1
 # make xconfig

After entering this I got...
Xlib: connection to :0.0 refused by server
Xlib: Invalid MIT-MAGIC-COOKIE-1 key
Application initialization failed: couldn't connect to display :0.0
Error in startup script: invalid command name button
   while executing
button .ref
file scripts/kconfig.tk line 46
make: *** [xconfig] Error 1
coyote:/usr/src/kernel-source-2.2.1# []

Ideas?



 answer questions

 # make-kpkg kernel_image
 # cd ..
 # dpkg --install kernel-image-2.2.1_1.00_i386.deb

 -tor

Re: Help. Trying to upgrade to hamm 2.0.36

1999-02-17 Thread Mark Wagnon 
Tim Heuser wrote:
 
 After entering this I got...
 Xlib: connection to :0.0 refused by server
 Xlib: Invalid MIT-MAGIC-COOKIE-1 key
 Application initialization failed: couldn't connect to display :0.0
 Error in startup script: invalid command name button
while executing
 button .ref
 file scripts/kconfig.tk line 46
 make: *** [xconfig] Error 1
 coyote:/usr/src/kernel-source-2.2.1# []
 
 Ideas?

Are youm trying to run xconfig as root in an X session started under
your normal account? I get these a lot because I used to be able to run
X clients as root in an X session I started with my normal user account.
I'm not sure of any 'fancy' way of getting around this, but you log in
as root at the console and start your X session, and that should solve
your problem, I think (it's late and I'm ill :( )

HTH
-- 
  __   _
Mark Wagnon  -o) / /  (_)__  __   __
Chula Vista, CA  /\\/ /__/ / _ \/ // /\ \/ /
mailto:[EMAIL PROTECTED]   _\_v/_/_//_/\_,_/ /_/\_\

Re: Help. Trying to upgrade to hamm 2.0.36

1999-02-17 Thread Tim Heuser 


Mark Wagnon wrote:

 Tim Heuser wrote:
  
  After entering this I got...
  Xlib: connection to :0.0 refused by server
  Xlib: Invalid MIT-MAGIC-COOKIE-1 key
  Application initialization failed: couldn't connect to display :0.0
  Error in startup script: invalid command name button
 while executing
  button .ref
  file scripts/kconfig.tk line 46
  make: *** [xconfig] Error 1
  coyote:/usr/src/kernel-source-2.2.1# []
 
  Ideas?

 Are youm trying to run xconfig as root in an X session started under
 your normal account? I get these a lot because I used to be able to run
 X clients as root in an X session I started with my normal user account.
 I'm not sure of any 'fancy' way of getting around this, but you log in
 as root at the console and start your X session, and that should solve
 your problem, I think (it's late and I'm ill :( )


It is quite possible that that is what I did.  I'll try it again tonight from 
the
console.

Thanks