Re: new kernel release
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 use ppp anymore. pppd keeps complaining about missing ppp support in the kernel and I know for sure the modules slhc, ppp and bsd_comp are loaded. Haven't had any time time to find out why this is happening or what is wrong but on dejanews I've seen more people complaining about this. -- Gravity doesn't exist, the Earth sucks
Re: new kernel release
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 irq=3D5 etc. Richard hmm, i hadn't really thought of that; i've been relying on Richard autoloading. I think you can use the right options even when auto-loading: add a line like options sb irq=3D5 or whatever to /etc/conf.modules . I've not tried it with a sound card, but that's how I set my network card options with auto-loading. -- Gilbert Laycock email: [EMAIL PROTECTED] Maths and Computer Science, http://www.mcs.le.ac.uk/~glaycock Leicester Universityphone: (+44) 116 252 3902
new kernel release
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? Thanks for your time, Jim McCloskey
Re: new kernel release
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 soundblaster to the value most cards use (5, and it defaults to 7? or is it vice versa). b) critical: it gave my xserver the blinkies. This is easy to do to an AT24 chipset, but the only thing that usually does it is rvplayer when the rv-server goes to heavy load (beats me why, but it crashes, and it can't restart without a reboot, and goes into the blinkies). Under 2.2.0, it went straight to the blinkies without giving me a good session first. rick --
Re: new kernel release
-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 versions, some of which might not be in hamm (sorry, I don't know for sure; I'm running slink). If you download the source and look in Documentation/Changes, you'll find a list of packages and the minimum version that you should have in order to use 2.2.0. It also lists the commands to use to find out the version you have installed. The new kernel might work with older versions of the packages, but the behavior might be unreliable. noah PGP public key available at http://lynx.dac.neu.edu/home/httpd/n/nmeyerha/mail.html or by 'finger -l [EMAIL PROTECTED]' This message was composed in a 100% Microsoft free environment. -BEGIN PGP SIGNATURE- Version: 2.6.2 iQCVAwUBNq4UNodCcpBjGWoFAQHgTQP/Q6GoYmMpPXBKwiQnYe4FWSIWM+wYDuZ1 tXONQlKORyjurYXPuhHuJtH3VucQP72wA4xqzYzVkWY5w+q0kRfNN0lHAQ0PlnnM 2FnnYf9WhOZEnA3FY+X/qN3R0Sf5ZhqJ8WAv/pkNbysCpE24r822+Mqkk7LkGo0S YWecZu8fjRY= =hS4j -END PGP SIGNATURE-
Re: new kernel release
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 on the last pre that called itself 2.2.0: a) it was not possible to change the irq for soundblaster to the value 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 irq=5 etc. b) critical: it gave my xserver the blinkies. This is easy to do to an AT24 chipset, but the only thing that usually does it is rvplayer when the rv-server goes to heavy load (beats me why, but it crashes, and it can't restart without a reboot, and goes into the blinkies). Under 2.2.0, it went straight to the blinkies without giving me a good session first. Try the svga server from 3.3.3 might be useful here. Grab the binary from ftp.xfree86.org and install it in /usr/local/bin, then point /etc/X11/Xserver at it. -- Rafael Kitover [EMAIL PROTECTED] pgpFLUaPNv0hO.pgp Description: PGP signature
Re: new kernel release
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 irq=3D5 etc. hmm, i hadn't really thought of that; i've been relying on autoloading. b) critical: it gave my xserver the blinkies. This is easy to do to=20 an AT24 chipset, but the only thing that usually does it is rvplayer=20 when the rv-server goes to heavy load (beats me why, but it crashes,=20 and it can't restart without a reboot, and goes into the blinkies). =20 Under 2.2.0, it went straight to the blinkies without giving me a good=20 session first. Try the svga server from 3.3.3 might be useful here. Grab the binary from ftp.xfree86.org and install it in /usr/local/bin, then point /etc/X11/Xserver at it. It was already installed :( I had hoped it would solve the rvplayer problem, and the artifacts when going past 8bpp, but it didn't :( --
Re: new kernel release
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 works great. 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? Thanks for your time, Jim McCloskey -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: new kernel release
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 modutils, util-linux and procps. It worked quite well for me! :-) Bye, Tino.
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' sb_ess.o(.text+0xe77): undefined reference to `esstype' make[1]: *** [vmlinux] Error 1 It compiled successfully when I substituted the pre9 version of sb_ess.c (I configured for a SB16, not ess). Bob Bob Nielsen Internet: [EMAIL PROTECTED] Tucson, AZ AMPRnet: [EMAIL PROTECTED] DM42nh http://www.primenet.com/~nielsen
Re: new kernel release
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: [EMAIL PROTECTED] Tucson, AZ AMPRnet: [EMAIL PROTECTED] DM42nh http://www.primenet.com/~nielsen
Re: new kernel release
*- 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' sb_ess.o(.text+0xe77): undefined reference to `esstype' make[1]: *** [vmlinux] Error 1 It compiled successfully when I substituted the pre9 version of sb_ess.c (I configured for a SB16, not ess). I had the same problems with a sb16. This is a result of putting the sb16 in the kernel instead of as a module. This fix is at http://edge.linuxhq.com/esstype-2.2.0.diff =esstype-2.2.0.diff=== --- linux/drivers/sound/sb_card.c Sun Jan 24 22:04:02 1999 +++ /usr/src/linux/drivers/sound/sb_card.c Mon Jan 25 20:33:14 1999 @@ -113,6 +113,7 @@ } int sb_be_quiet=0; +int esstype = 0; /* ESS chip type */ #ifdef MODULE @@ -136,7 +137,6 @@ int pas2 = 0; /* Set pas2=1 to load this as support for pas2 */ int sm_games = 0; /* Mixer - see sb_mixer.c */ int acer = 0; /* Do acer notebook init */ -int esstype = 0; /* ESS chip type */ MODULE_PARM(io, i); MODULE_PARM(irq, i); =end diff=== After the patch it worked perfect. In the .../linux directory issue patch -p1 esstype-2.2.0.diff and restart the compile. -- Brian - Never criticize anybody until you have walked a mile in their shoes, because by that time you will be a mile away and have their shoes. - unknown Mechanical Engineering[EMAIL PROTECTED] Purdue University http://www.ecn.purdue.edu/~servis -
