Re: Re: moving to the 2.6 kernel? (http://lists.debian.org/debian-user/2004/06/msg03105.html)
Hello, I saw your message on the net (see subject) and thought that you might have a solution for my problem. I'm running Debian and don't wanna have OSS emulation because it shouldn't be neccesary (why use an extra layer to retain backward compatibility if you're new to Linux and don't have any 'backward experiences' ;-) This message has been posted on several lists before, but with no response. --- Subject: How to integrate ALSA Hello Free World!I am quite new to all of the Linux stuff but learning fast, so don't be scaredto respond in way's I 'might not understand', I'll figure it out ;-).I have recently made my own Debian Kernel (now running nice 'n smooth...) anddecided to go with ALSA - I used the original 2.2.20_compact kernel which was onthe installation diskette (nope, I have no CD-burning equipement) and thatdidn't include sound support, so I made this kernel. But now there are still nosystem-sounds! If I use one of my other 2.4.19 kernels (I have made 23 in twomonths before I was satisfied) with no ALSA but with the old standard soundsupport (deprecated since 2.6.6 but not yet available in 'debianized' version)it does work! I can play my music though through ALSA with the nice Alsaplayer(using the alsa-module).I figured that Gnome wants ESound as it's sound system so I installedlibesd-alsa0 to be able to hear 'them silly system-sounds'... but they don't dowhat they should! (yet)When I fire up the sound-monitor applet it says esd is inactive so I take myterminal and go "ESD", resulting in loads of variants of: Couldn't open any alsa card! Last card tried was 0 Error openin card 0: Sound protocol is not compatible Audio device open for 44.1KHz, stereo, 16bit failed Trying 44.1KHz, 8bit stereo.and finally: Couldn't open any alsa card! Last card tried was 0 Error openin card 0: Sound protocol is not compatible Sound device inadequate for Esound. Fatal.So I guess there is some heavy mis-comunication going on between alsa and esd...The easiest solution I can think of is just to forget ESD and set things up foruse purely with alsa. It must be possible since the reason I chose Gnome insteadof KDE was that Gnome is Free, and KDE is not. I only don't know how it shouldbe done...please respond by mail to [EMAIL PROTECTED] in English or Dutch (the reasonfor me to have a .ru e-mail adres is just: it is free, as in: free screwdrivers)Kind regards,Jouke Witteveen
Re: moving to the 2.6 kernel?
Jules Dubois wrote: On Thu, 24 Jun 2004 02:22:07 -0700, Paul Scott wrote: I don't want to spend the time to build a new kernel right now and I have spent quite a bit of time Googling, searching this list and reading kernel-docs. How about a pragmatic approach. Which takes more time: searching Google, list archives, and kernel documentation; or building a custom kernel? I certainly considered that and I don't have the incentive at the moment since my 2.4 kernel works fine. One large concern justifying my research was whether something about the way the 2.6 kernels had changed from the 2.4 kernels (like udev) and was causing my problem and would be something I would also have to solve with a custom kernel. Is there a way to fix this with a stock kernel. I spent a few hours on my problem. I'm not an expert on modules and I know little about initrd, so I simply built a new kernel and rebooted. It booted the first time. That's good to hear. Is there a better choice than 386 for AMD K6-II? Isn't the K6-II an i686? (I don't know what difference it would make.) It probably would be fine. The description for 686 mentions Celeron and once I had a problem building a custom 2.4 kernel because of some Celeron option. It's probably unrelated but I can always switch to 686 when I get the current problem solved. Is there more information I can provide? I see that there are no bugs filed against your 386 package. I take this to mean that something about the configuration of your system and my system is improper. I would, of course, be good to find that out. Do you get two warning (or error) messages when you installed the package, saying cpio was unable to find: /etc/modprobe.conf /lib/modules/modprobe.conf If your kernel won't boot properly, I think it's safe to remove and reinstall the package to check for the error messages. I don't remember those messages and I have tried at least two versions (2.6.6-1 and 2.6.6-2). Actually I believe I had a previous 2.6 kernel running and I stupidly let an upgrade from aptitude install a 2.4 kernel over it. Thanks, Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: moving to the 2.6 kernel?
On Thu, 24 Jun 2004 02:22:07 -0700, Paul Scott wrote: > Jules Dubois wrote: > >>I installed kernel-image-2.6.6-2-k7. I get lots of error during boot; >>[...] >>attempt to load a module fails with a "/lib/modules: read-only filesystem" >>error. >> > I have installed 2.6.6-2-386 (for k6-2?) and have the same problem. > Moreover the error messages refer to /lib/modules/2.6.6-1-386/... I don't recall a mismatch between the Debian version of my kernel and the module errors. > I don't want to spend the time to build a new kernel right now and I > have spent quite a bit of time Googling, searching this list and reading > kernel-docs. How about a pragmatic approach. Which takes more time: searching Google, list archives, and kernel documentation; or building a custom kernel? > Is there a way to fix this with a stock kernel. I spent a few hours on my problem. I'm not an expert on modules and I know little about initrd, so I simply built a new kernel and rebooted. It booted the first time. > Is there a better choice than 386 for AMD K6-II? Isn't the K6-II an i686? (I don't know what difference it would make.) > Is there more information I can provide? I see that there are no bugs filed against your 386 package. I take this to mean that something about the configuration of your system and my system is improper. Do you get two warning (or error) messages when you installed the package, saying cpio was unable to find: /etc/modprobe.conf /lib/modules/modprobe.conf If your kernel won't boot properly, I think it's safe to remove and reinstall the package to check for the error messages. > This is on sid. Same here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: moving to the 2.6 kernel?
Jules Dubois wrote: On Mon, 21 Jun 2004 01:39:16 -0500, Kent West wrote: Jules Dubois wrote: There's really nothing more to it than installing a kernel-image package (and, in my case, updating initrd-tools)? If you're not already running an initrd kernel, you may have to add one line to /etc/lilo.conf, but you're warned about it during the install. I installed kernel-image-2.6.6-2-k7. I get lots of error during boot; they go by quickly, I don't seem to be able to stop them, and they're not recorded in any log file. If I interpret the situation correctly, every attempt to load a module fails with a "/lib/modules: read-only filesystem" error. I have installed 2.6.6-2-386 (for k6-2?) and have the same problem. Moreover the error messages refer to /lib/modules/2.6.6-1-386/... I don't want to spend the time to build a new kernel right now and I have spent quite a bit of time Googling, searching this list and reading kernel-docs. Is there a way to fix this with a stock kernel. Is there a better choice than 386 for AMD K6-II? Is there more information I can provide? This is on sid. TIA, Paul Scott -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: moving to the 2.6 kernel?
On Tue, Jun 22, 2004 at 06:39:28PM +0200, martin f krafft wrote: > echo psmouse >> /etc/modules > > ugly, but it works... Thanks. That did the trick! Regards Johann -- Johann Spies Telefoon: 021-808 4036 Informasietegnologie, Universiteit van Stellenbosch "Children, obey your parents in the Lord; for this is right." Ephesians 6:1 signature.asc Description: Digital signature
RE: moving to the 2.6 kernel?
On Thu, 24 Jun 2004 13:29:24 +1000, Aaron Robertson-Hodder wrote: > Aha! It becomes clearer (somewhat). I didn't look hard enough for > module-init-tools. I only looked in the stable version DOH! > This may be the answer to most of my problems! Next stop: World Hunger! > Thanks to everyone who offered advice! Let us know if it makes the kernel upgrade work. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: moving to the 2.6 kernel?
Aha! It becomes clearer (somewhat). I didn't look hard enough for module-init-tools. I only looked in the stable version DOH! This may be the answer to most of my problems! Thanks to everyone who offered advice! -Original Message- From: Aaron Robertson-Hodder [mailto:[EMAIL PROTECTED] Sent: Thursday, 24 June 2004 11:21 AM To: [EMAIL PROTECTED] Subject: RE: moving to the 2.6 kernel? Thanks for all your help people! I have actually tried to get module-init-tools (ie. Apt-get install module-init-tools). I also tried to find it on the package manager and searching the debian site but could not find it. I have since managed to (by removing all the modules that gave me errors) been able to compile the kernel, but now I have no network. The 8139too module exists, but when I run lsmod I get function undefined errors. Probably removed too much! I think I shall cut my loses and download sarge... -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Jules Dubois Sent: Wednesday, 23 June 2004 4:59 PM To: [EMAIL PROTECTED] Subject: RE: moving to the 2.6 kernel? On Wed, 23 Jun 2004 15:32:47 +1000, Aaron Robertson-Hodder wrote: > make-kpkg --revision=786:MyKernel2.4.20 kernel_image I think that's correct. I don't use the 'revision' switch. Instead I've been modifying the top-level Makefile and setting the EXTRAVERSION variable. > Which I got from a guide on the web. I think your way is the "approved" way. > So, let me get this straight. I download and un-tar the source, then do > the following steps: > > make xconfig - and select the things I want Yes. Or 'make gconfig'. What a nice set of tools. > make-kpkg clean > make-kpkg kernel_image > install the kernel (using the package manager?) That's exactly -- except for the --revision vs. EXTRAVERSION -- what I did. > Is that all? Check to see if you have the 'module-init-tools' package, as I posted in a message a few minutes ago. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: moving to the 2.6 kernel?
Thanks for all your help people! I have actually tried to get module-init-tools (ie. Apt-get install module-init-tools). I also tried to find it on the package manager and searching the debian site but could not find it. I have since managed to (by removing all the modules that gave me errors) been able to compile the kernel, but now I have no network. The 8139too module exists, but when I run lsmod I get function undefined errors. Probably removed too much! I think I shall cut my loses and download sarge... -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Jules Dubois Sent: Wednesday, 23 June 2004 4:59 PM To: [EMAIL PROTECTED] Subject: RE: moving to the 2.6 kernel? On Wed, 23 Jun 2004 15:32:47 +1000, Aaron Robertson-Hodder wrote: > make-kpkg --revision=786:MyKernel2.4.20 kernel_image I think that's correct. I don't use the 'revision' switch. Instead I've been modifying the top-level Makefile and setting the EXTRAVERSION variable. > Which I got from a guide on the web. I think your way is the "approved" way. > So, let me get this straight. I download and un-tar the source, then do > the following steps: > > make xconfig - and select the things I want Yes. Or 'make gconfig'. What a nice set of tools. > make-kpkg clean > make-kpkg kernel_image > install the kernel (using the package manager?) That's exactly -- except for the --revision vs. EXTRAVERSION -- what I did. > Is that all? Check to see if you have the 'module-init-tools' package, as I posted in a message a few minutes ago. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: moving to the 2.6 kernel?
On Wed, Jun 23, 2004 at 12:53:05AM -0600, Jules Dubois wrote: > On Wed, 23 Jun 2004 14:02:14 +1000, Aaron Robertson-Hodder wrote: > > > Just wondering if all you people are moving to 2.6 from Woody, Sarge or > > sid? I have been trying to compile the 2.6.6 kernel on my Woody distro and > > keep getting depmod errors. > > Another thought: Do you have the module-init-tools package? > > Quoting from the package description: > > This package contains a set of programs for > loading, inserting, and removing kernel modules > for Linux (versions 2.5.48 and above). It serves > the same function that the "modutils" package > serves for Linux 2.4. There are a few other packages that need updating - suitable versions are available from www.backports.org. Search the archives, a list was posted a few months back. -- Pigeon Be kind to pigeons Get my GPG key here: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x21C61F7F pgpbch37vwbDt.pgp Description: PGP signature
Re: Moving to the 2.6 kernel
I did it with Woody (2.6.6). Youe problem propably is not just module-init-tools..! Before trying you new kernel be sure you have not only the latest module-init-tools but also some other utilities.. I remember I had to update the following: procps (to find version: "#ps --version", minimum version: 2.0.9) e2fsprogs (if you use the ext2/ext3 filesystem, "#tune2fs", min.v.:1.29) reiserfsprogs (if you use the reiser fs, "#reiserfsck -V 2>&1 | grep reiserfsprogs", min.v.: 3.6.3) If you use other filesystems check this: jfsutils (jfs, "#fsck.jfs -V", min.v.: 1.0.14) xfsprogs (xfs, "#xfs_db -V", min.v.: 2.1.0) Of course as everyone mentioned you have to update module-init-tools and _maybe_ rename your /etc/modules.conf into /etc/modprobe.conf (I do not remember if I did it manually) Hope I helped :) Panos -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: moving to the 2.6 kernel?
Once upon a time Jules Dubois said...
> On Wed, 23 Jun 2004 15:32:47 +1000, Aaron Robertson-Hodder wrote:
>
> > make-kpkg --revision=786:MyKernel2.4.20 kernel_image
>
> I think that's correct. I don't use the 'revision' switch. Instead I've
> been modifying the top-level Makefile and setting the EXTRAVERSION
> variable.
Another way of doing that is to use the --append-to-version option to
make-kpkg.
I build my kernels with this shell function:
bk ()
{
if [ $# -ne 2 ]; then
echo "Usage: bk " 1>&2;
return;
fi;
make-kpkg --rootcmd fakeroot --revision $2 --append-to-version -$1-$2 kernel_image
}
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: moving to the 2.6 kernel?
On Wed, 23 Jun 2004 15:32:47 +1000, Aaron Robertson-Hodder wrote: > make-kpkg --revision=786:MyKernel2.4.20 kernel_image I think that's correct. I don't use the 'revision' switch. Instead I've been modifying the top-level Makefile and setting the EXTRAVERSION variable. > Which I got from a guide on the web. I think your way is the "approved" way. > So, let me get this straight. I download and un-tar the source, then do > the following steps: > > make xconfig - and select the things I want Yes. Or 'make gconfig'. What a nice set of tools. > make-kpkg clean > make-kpkg kernel_image > install the kernel (using the package manager?) That's exactly -- except for the --revision vs. EXTRAVERSION -- what I did. > Is that all? Check to see if you have the 'module-init-tools' package, as I posted in a message a few minutes ago. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: moving to the 2.6 kernel?
On Wed, 23 Jun 2004 14:02:14 +1000, Aaron Robertson-Hodder wrote: > Just wondering if all you people are moving to 2.6 from Woody, Sarge or > sid? I have been trying to compile the 2.6.6 kernel on my Woody distro and > keep getting depmod errors. Another thought: Do you have the module-init-tools package? Quoting from the package description: This package contains a set of programs for loading, inserting, and removing kernel modules for Linux (versions 2.5.48 and above). It serves the same function that the "modutils" package serves for Linux 2.4. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: moving to the 2.6 kernel?
On Wed, 2004-06-23 at 18:07, John Summerfield wrote: > Aaron Robertson-Hodder wrote: > > >Hi, > > > >Just wondering if all you people are moving to 2.6 from Woody, Sarge or > >sid? I have been trying to compile the 2.6.6 kernel on my Woody distro > >and keep getting depmod errors. > > > >I've tried using a number of different configs as a starting point > >(including the knoppix one) and still can't seem to get it right. > > > >I have now read that there may be issues with Woody going to 2.6. Is > >that true? If so, I guess I'll try Sarge if that sounds like the best > >option... > > > > > > > > > There's certainly more to going to 2.6 than just building the packages. > There _is_ a 2.6 kernel and everything else you need around, I found it > and downloaded it a while ago. > > Support (security fixes) may be a problem with them, but that applies to > Sarge too. > > Me, I went to Sarge. Sarge has 2.6 kernels up to 2.6.6. > If I remember correctly, Kernel 2.6 has a whole new module-loading system that requires updated modutils stuff. This could explain your depmod problems. I believe the new tools are backwards-compatible, ie the new versions work with 2.4 kernels too. But from sarge it is *so* easy to do: apt-get install kernel-image-2.6.6-1-686 and have it all just happen. Cheers, Simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: moving to the 2.6 kernel?
Aaron Robertson-Hodder wrote: Hi, Just wondering if all you people are moving to 2.6 from Woody, Sarge or sid? I have been trying to compile the 2.6.6 kernel on my Woody distro and keep getting depmod errors. I've tried using a number of different configs as a starting point (including the knoppix one) and still can't seem to get it right. I have now read that there may be issues with Woody going to 2.6. Is that true? If so, I guess I'll try Sarge if that sounds like the best option... There's certainly more to going to 2.6 than just building the packages. There _is_ a 2.6 kernel and everything else you need around, I found it and downloaded it a while ago. Support (security fixes) may be a problem with them, but that applies to Sarge too. Me, I went to Sarge. Sarge has 2.6 kernels up to 2.6.6. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: moving to the 2.6 kernel?
I used: make-kpkg --revision=786:MyKernel2.4.20 kernel_image Which I got from a guide on the web. So, let me get this straight. I download and un-tar the source, then do the following steps: make xconfig - and select the things I want make-kpkg clean make-kpkg kernel_image install the kernel (using the package manager?) Is that all? Thanks for you help! -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Jules Dubois Sent: Wednesday, 23 June 2004 2:43 PM To: [EMAIL PROTECTED] Subject: RE: moving to the 2.6 kernel? On Wed, 23 Jun 2004 14:02:14 +1000, Aaron Robertson-Hodder wrote: > Just wondering if all you people are moving to 2.6 from Woody, Sarge or > sid? sid. > I have been trying to compile the 2.6.6 kernel on my Woody distro > and keep getting depmod errors. How are you building the kernel? I used `make-kpkg kernel_image` and it booted the first time. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: moving to the 2.6 kernel?
On Wed, 23 Jun 2004 14:02:14 +1000, Aaron Robertson-Hodder wrote: > Just wondering if all you people are moving to 2.6 from Woody, Sarge or > sid? sid. > I have been trying to compile the 2.6.6 kernel on my Woody distro > and keep getting depmod errors. How are you building the kernel? I used `make-kpkg kernel_image` and it booted the first time. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: moving to the 2.6 kernel?
Hi, Just wondering if all you people are moving to 2.6 from Woody, Sarge or sid? I have been trying to compile the 2.6.6 kernel on my Woody distro and keep getting depmod errors. I've tried using a number of different configs as a starting point (including the knoppix one) and still can't seem to get it right. I have now read that there may be issues with Woody going to 2.6. Is that true? If so, I guess I'll try Sarge if that sounds like the best option... All I really want to do is get support for my DVB card! Thanks. Aaron. -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Jules Dubois Sent: Wednesday, 23 June 2004 7:20 AM To: [EMAIL PROTECTED] Subject: Re: moving to the 2.6 kernel? On Tue, 22 Jun 2004 18:37:14 +1200, Simon Kitching wrote: > On Tue, 2004-06-22 at 18:01, Jules Dubois wrote: >> >> I installed kernel-image-2.6.6-2-k7. I get lots of error during boot; >> they go by quickly, I don't seem to be able to stop them, and they're >> not recorded in any log file. If I interpret the situation correctly, >> every attempt to load a module fails with a "/lib/modules: read-only >> filesystem" error. I neglected to post one minor detail. The system doesn't survive the boot process. I've lost the error message, but it says something like "error: trying to kill init". My hand-crafted [sic] 2.6.7 kernel is almost completely functional; it's just that I couldn't figure out how to boot and/or configure the Debian kernel-image package. > Have you tried using "dmesg"? Is that the same thing as `less /var/log/dmesg`? > See "man dmesg" for more info. Thanks, Simon. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: moving to the 2.6 kernel?
On Tue, 22 Jun 2004 18:37:14 +1200, Simon Kitching wrote: > On Tue, 2004-06-22 at 18:01, Jules Dubois wrote: >> >> I installed kernel-image-2.6.6-2-k7. I get lots of error during boot; >> they go by quickly, I don't seem to be able to stop them, and they're >> not recorded in any log file. If I interpret the situation correctly, >> every attempt to load a module fails with a "/lib/modules: read-only >> filesystem" error. I neglected to post one minor detail. The system doesn't survive the boot process. I've lost the error message, but it says something like "error: trying to kill init". My hand-crafted [sic] 2.6.7 kernel is almost completely functional; it's just that I couldn't figure out how to boot and/or configure the Debian kernel-image package. > Have you tried using "dmesg"? Is that the same thing as `less /var/log/dmesg`? > See "man dmesg" for more info. Thanks, Simon. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: moving to the 2.6 kernel?
also sprach Vittorio <[EMAIL PROTECTED]> [2004.06.22.1529 +0200]: > Don't blame the new 2.6.x kernel for that! I'm experiencing the > same drawback using kernel 2.4.25. In a nutshell, with debian > testing & a logitech optical mouse in my portable PC on > a docking-station I have to go to a console and restart gpm as you > said if I want a "lively" mouse under X11 (either kdm or gnome), > while in another box (a desktop with the same configuration as the > portable) it all works perfectly. I think this is due to an > unfortunate hardware combination rather than a software bug (or at > most a software bug for that specific hardware). echo psmouse >> /etc/modules ugly, but it works... -- Please do not CC me when replying to lists; I read them! .''`. martin f. krafft <[EMAIL PROTECTED]> : :' :proud Debian developer, admin, and user `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver! signature.asc Description: Digital signature
Re: moving to the 2.6 kernel?
On Tuesday 22 June 2004 10:25, Johann Spies wrote: > On Sun, Jun 20, 2004 at 09:04:54AM -0400, stan wrote: ... > My experience with all the pc's on which I have installed the > 2.6. kernels is that I have a problem getting gpm to start in the > normal bootup process. The result is that when you use > kdm/wdm/xdm/gdm you can not use X11 because the mouse would would not > work (if your setup is such that you use gpm). Then you have to go > back to the console and as root do "/etc/init.d/gpm restart" and > everything works OK. I don't know why this is the case, but that was > my experience in at least 4-6 cases. That is why I do not use the 2.6 > kernel when I set up the pc for other users who are not very > comfortable with system administration. Don't blame the new 2.6.x kernel for that! I'm experiencing the same drawback using kernel 2.4.25. In a nutshell, with debian testing & a logitech optical mouse in my portable PC on a docking-station I have to go to a console and restart gpm as you said if I want a "lively" mouse under X11 (either kdm or gnome), while in another box (a desktop with the same configuration as the portable) it all works perfectly. I think this is due to an unfortunate hardware combination rather than a software bug (or at most a software bug for that specific hardware). Ciao Vittorio -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: moving to the 2.6 kernel?
Hello Johann Spies (<[EMAIL PROTECTED]>) wrote: > My experience with all the pc's on which I have installed the > 2.6. kernels is that I have a problem getting gpm to start in the > normal bootup process. The result is that when you use > kdm/wdm/xdm/gdm you can not use X11 because the mouse would would not > work (if your setup is such that you use gpm). Then you have to go > back to the console and as root do "/etc/init.d/gpm restart" and > everything works OK. Do you use a PS/2 mouse? The new Kernel 2.6 allows the psmouse driver to be compiled as a module. Make sure the psmouse driver gets loaded before gpm or XFree start. best regards Andreas Janssen -- Andreas Janssen <[EMAIL PROTECTED]> PGP-Key-ID: 0xDC801674 ICQ #17079270 Registered Linux User #267976 http://www.andreas-janssen.de/debian-tipps.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: moving to the 2.6 kernel?
On Sun, Jun 20, 2004 at 09:04:54AM -0400, stan wrote: > If I want to build a new Debian machine to start expolring the 2.6 kernel > what's the best way to go about this? > Others have answered with valuable information. My experience with all the pc's on which I have installed the 2.6. kernels is that I have a problem getting gpm to start in the normal bootup process. The result is that when you use kdm/wdm/xdm/gdm you can not use X11 because the mouse would would not work (if your setup is such that you use gpm). Then you have to go back to the console and as root do "/etc/init.d/gpm restart" and everything works OK. I don't know why this is the case, but that was my experience in at least 4-6 cases. That is why I do not use the 2.6 kernel when I set up the pc for other users who are not very comfortable with system administration. Regards Johann -- Johann Spies Telefoon: 021-808 4036 Informasietegnologie, Universiteit van Stellenbosch "What? know ye not that your body is the temple of the Holy Ghost which is in you, which ye have of God, and ye are not your own? For ye are bought with a price; therefore glorify God in your body, and in your spirit, which are God's." I Corinthians 6:19,20 signature.asc Description: Digital signature
Re: moving to the 2.6 kernel?
Once upon a time Simon Kitching said... > On Tue, 2004-06-22 at 18:01, Jules Dubois wrote: > > > > I installed kernel-image-2.6.6-2-k7. I get lots of error during boot; > > they go by quickly, I don't seem to be able to stop them, and they're not > > recorded in any log file. If I interpret the situation correctly, every > > attempt to load a module fails with a "/lib/modules: read-only filesystem" > > error. > > Have you tried using "dmesg"? Actually, that one is a bug in the second most recent version of module-init-tools. It is fixed in the latest version, so those messages wont come up. Check the bug tracking system for more info. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: moving to the 2.6 kernel?
On Tue, 2004-06-22 at 18:01, Jules Dubois wrote: > On Mon, 21 Jun 2004 01:39:16 -0500, Kent West wrote: > > > Jules Dubois wrote: > > > >>There's really nothing more to it than installing a kernel-image package > >>(and, in my case, updating initrd-tools)? > >> > > If you're not already running an initrd kernel, you may have to add one > > line to /etc/lilo.conf, but you're warned about it during the install. > > I installed kernel-image-2.6.6-2-k7. I get lots of error during boot; > they go by quickly, I don't seem to be able to stop them, and they're not > recorded in any log file. If I interpret the situation correctly, every > attempt to load a module fails with a "/lib/modules: read-only filesystem" > error. Have you tried using "dmesg"? See "man dmesg" for more info. Regards, Simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: moving to the 2.6 kernel?
On Mon, 21 Jun 2004 01:39:16 -0500, Kent West wrote: > Jules Dubois wrote: > >>There's really nothing more to it than installing a kernel-image package >>(and, in my case, updating initrd-tools)? >> > If you're not already running an initrd kernel, you may have to add one > line to /etc/lilo.conf, but you're warned about it during the install. I installed kernel-image-2.6.6-2-k7. I get lots of error during boot; they go by quickly, I don't seem to be able to stop them, and they're not recorded in any log file. If I interpret the situation correctly, every attempt to load a module fails with a "/lib/modules: read-only filesystem" error. I installed the kernel 2.6.0 source, patched it to 2.6.7, configured, compiled (make-kpkg), installed (dpkg), and rebooted. It very nearly works. ALSA and GNOME 2.6 (also new) now drive my SoundBlaster Live 5.1 card correctly. (Mr. Chris Metzler provided me with his gracious assistance trying to get it to work with kernel 2.4 and GNOME 2.4.) What's not working is my 4-port serial card. The brand name is "ByteRunner", it's made by VisionSystems, and it has a Titan serial controller on it. It's detected because I can see it using lspci. Unfortunately, where kernel 2.4 found my modem on /dev/ttyS5, kernel 2.6 doesn't seem to see it at all. Do the non-standard serial ports live somewhere else now? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: moving to the 2.6 kernel?
* Jules Dubois <[EMAIL PROTECTED]> [2004 Jun 21 06:14 -0500]: > On Mon, 21 Jun 2004 01:39:16 -0500, Kent West wrote: > > > Jules Dubois wrote: > >> > >>Thanks for the advice, Kent. A foolish question: There's really nothing > >>more to it than installing a kernel-image package (and, in my case, > >>updating initrd-tools)? > >> > > If you're not already running an initrd kernel, you may have to add one > > line to /etc/lilo.conf, but you're warned about it during the install. > > I'll have a look at the GRUB documentation. I found that running update-grub will cause the initrd stanza to be added automatically into the menu.lst file. Thus, I didn't have to do anything special when I migrated from my kernel-package built kernel to the Debian image package. For those wanting to migrate to 2.6, from my experience, be aware that kmod seems to work differently as I now have to force load the modules for a PS2 mouse (mousedev and psmouse) and my tulip based network card from /etc/modules. In 2.4 these were detected and loaded automatically. Outside of those modules and the current lack of support for lm-sensors on my Athlon mainboard, 2.6.6 has worked well. It "feels" faster because the responsiveness of the mouse has increased considerably. Enjoy! -- Wireless | Amateur Radio Station N0NB | Successfully Microsoft Amateur radio exams; ham radio; Linux info @ | free since January 1998. http://www.qsl.net/n0nb/ | "Debian, the choice of My Kawasaki KZ-650 SR @| a GNU generation!" http://www.networksplus.net/n0nb/ | http://www.debian.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: moving to the 2.6 kernel?
On Mon, 21 Jun 2004 01:39:16 -0500, Kent West wrote: > Jules Dubois wrote: >> >>Thanks for the advice, Kent. A foolish question: There's really nothing >>more to it than installing a kernel-image package (and, in my case, >>updating initrd-tools)? >> > If you're not already running an initrd kernel, you may have to add one > line to /etc/lilo.conf, but you're warned about it during the install. I'll have a look at the GRUB documentation. I remember now that I stopped using LibraNet's pre-packaged kernels because of a problem I caused with its initrd. I created an unbootable system. I understand now the purpose of initrd; I've just never used it myself. The kernels I've been building with make-kpkg have never required an initrd, so is there much benefit to studying how to do it? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: moving to the 2.6 kernel?
On Mon, 2004-06-21 at 16:28, Jules Dubois wrote: > On Sun, 20 Jun 2004 10:47:10 -0500, Kent West wrote: > > > Just install a Debian box like you normally do, then "apt-get install > > kernel-image-2.6.whateverfitsyourarchitecture". > > Thanks for the advice, Kent. A foolish question: There's really nothing > more to it than installing a kernel-image package (and, in my case, > updating initrd-tools)? I had no problems. Once the install had completed, I could boot into either the 2.4 or 2.6 kernel. Not that the 2.4 option gets much use ;-). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: moving to the 2.6 kernel?
Jules Dubois wrote: On Sun, 20 Jun 2004 10:47:10 -0500, Kent West wrote: Just install a Debian box like you normally do, then "apt-get install kernel-image-2.6.whateverfitsyourarchitecture". Thanks for the advice, Kent. A foolish question: There's really nothing more to it than installing a kernel-image package (and, in my case, updating initrd-tools)? If you're not already running an initrd kernel, you may have to add one line to /etc/lilo.conf, but you're warned about it during the install. -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: moving to the 2.6 kernel?
On Sun, 20 Jun 2004 10:47:10 -0500, Kent West wrote: > Just install a Debian box like you normally do, then "apt-get install > kernel-image-2.6.whateverfitsyourarchitecture". Thanks for the advice, Kent. A foolish question: There's really nothing more to it than installing a kernel-image package (and, in my case, updating initrd-tools)? > Then you can download the sources and roll your own if you like. (Or you > can do this first, and bypass the pre-compiled version.) I've been doing that for so long, I've forgotten how automation works. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: moving to the 2.6 kernel?
* Kent West <[EMAIL PROTECTED]> [2004 Jun 20 11:33 -0500]: > stan wrote: > > >If I want to build a new Debian machine to start expolring the 2.6 kernel > >what's the best way to go about this? > > > > > > > Just install a Debian box like you normally do, then "apt-get install > kernel-image-2.6.whateverfitsyourarchitecture". Be aware that some hardware is not yet supported in .deb packages for the 2.6 kernels. I have a Soyo VIA 686 mainboard that the lm-sensors modules for 2.4 includes the ddcmon module that is needed to read the CPU and system temp. The lmsensors modules in the 2.6 kernel-image package does not yet have this module. I've not yet tried a 2.6 kernel on this laptop as the Lucent modem folks have yet to release a .deb package for ltmodem on 2.6. So, I'm in wait and see mode. - Nate >> -- Wireless | Amateur Radio Station N0NB | Successfully Microsoft Amateur radio exams; ham radio; Linux info @ | free since January 1998. http://www.qsl.net/n0nb/ | "Debian, the choice of My Kawasaki KZ-650 SR @| a GNU generation!" http://www.networksplus.net/n0nb/ | http://www.debian.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: moving to the 2.6 kernel?
stan wrote: If I want to build a new Debian machine to start expolring the 2.6 kernel what's the best way to go about this? Just install a Debian box like you normally do, then "apt-get install kernel-image-2.6.whateverfitsyourarchitecture". "apt-cache search kernel-image-2.6" will give you a good idea of what's available. Then you can download the sources and roll your own if you like. (Or you can do this first, and bypass the pre-compiled version.) -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: moving to the 2.6 kernel?
stan <[EMAIL PROTECTED]> > wrote: If I want to build a new Debian machine to start expolring the 2.6 > kernel what's the best way to go about this? One easy way is to install a 2.6-kernel-image, just do an apt-cache search for kernel-image 2.6 then use apt-get install kernel-image. This will get you a kernel that you can play with, or you can install the kernel-source and build your own kernel. This assumes your using a testing, or sid install. If your on woody then you most likely will need to dist update to testing to get the files, and dependences. If your talking about a clean install of Debian Sarge, you can use these iso's to get a working system. http://www.debian.org/devel/debian-installer/ just choose your arch, and follow the Readme, and the Howto. I have used RC1 of the debian-installer and everything works on my end. Just remember to fill out the installer report to give feed back to the installer team so we can get closer to a final release. Rthoreau -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
