Re: new kernel release

1999-01-27 Thread Gilbert Laycock
>> > I had a couple, though it was on the last pre that called itself 2.2.0: >> > a) it was not possible to change the irq for soundblaster to the value=20 >> > most cards use (5, and it defaults to 7? or is it vice versa). >> You can pass parameters to modules when insmod'ing them, >> ie insmod

Re: new kernel release

1999-01-27 Thread Marcel Burggraeve
On 26 Jan 1999 19:28:33 +0100, Jim McCloskey <[EMAIL PROTECTED]> wrote: > >I see that the 2.2.0 kernel is now officially released. > >Does anyone know if there are any problems, or things to be wary of, in >compiling this kernel for Debian hamm? > After compiling and installing the kernel I can't

Re: new kernel release

1999-01-26 Thread servis
*- Bob Nielsen wrote about "Re: new kernel release" > I've come across one problem in compiling, which did NOT occur with > 2.2.0-pre9: > > drivers/sound/sound.a(sb_ess.o): In function `ess_init': > sb_ess.o(.text+0xde2): undefined reference to `esstype&

Re: new kernel release

1999-01-26 Thread Bob Nielsen
I see that Documentation/CHANGES says that net-tools 1.49 is required. It says to use 'hostname -V' to determine the version, but this does not work. 'route -V' in both slink and potato that the net-tools version is 1.45. Is an upgrade needed here? Bob Bob Nielsen Internet

Re: new kernel release

1999-01-26 Thread Bob Nielsen
I've come across one problem in compiling, which did NOT occur with 2.2.0-pre9: drivers/sound/sound.a(sb_ess.o): In function `ess_init': sb_ess.o(.text+0xde2): undefined reference to `esstype' sb_ess.o(.text+0xe77): undefined reference to `esstype' make[1]: *** [vmlinux] Error 1 It compiled succe

Re: new kernel release

1999-01-26 Thread Tino Schwarze
Hi Jim, > I see that the 2.2.0 kernel is now officially released. > > Does anyone know if there are any problems, or things to be wary of, in > compiling this kernel for Debian hamm? I compiled it today. But read Documentation/Changes first! I guess, you need some packages from potato, e.g. newer

Re: new kernel release

1999-01-26 Thread Alec Smith
Yeah, it throws up an error with setserial that I have yet to get rid of... Looking at the code, its just to say setserial -W is no longer supported... However I changed that part of 0setserial and still have the error. Anyway, it doesn't appear to be anything too serious. Other than that, 2.2 wor

Re: new kernel release

1999-01-26 Thread Richard E. Hawkins Esq.
> > I had a couple, though it was on the last pre that called itself 2.2.0: > > a) it was not possible to change the irq for soundblaster to the value=20 > > most cards use (5, and it defaults to 7? or is it vice versa). > You can pass parameters to modules when insmod'ing them, > ie insmod sb i

Re: new kernel release

1999-01-26 Thread Rafael Kitover
On Tue, Jan 26, 1999 at 01:19:25PM -0600, Richard E. Hawkins Esq. wrote: > > > > I see that the 2.2.0 kernel is now officially released. > > > > Does anyone know if there are any problems, or things to be wary of, in > > compiling this kernel for Debian hamm? > > I had a couple, though it was o

Re: new kernel release

1999-01-26 Thread Noah L. Meyerhans
-BEGIN PGP SIGNED MESSAGE- On Tue, 26 Jan 1999, Jim McCloskey wrote: > I see that the 2.2.0 kernel is now officially released. > > Does anyone know if there are any problems, or things to be wary of, in > compiling this kernel for Debian hamm? Kernel 2.2.0 depends on certain package ve

Re: new kernel release

1999-01-26 Thread Richard E. Hawkins Esq.
> > I see that the 2.2.0 kernel is now officially released. > > Does anyone know if there are any problems, or things to be wary of, in > compiling this kernel for Debian hamm? I had a couple, though it was on the last pre that called itself 2.2.0: a) it was not possible to change the irq for