mouse not working after kernel rebuild
HiI built 2 kernels, the second one in the line below makes the mousenot active and I am trying to find out what feature needs settingin-order to activate the mouse, by comparing with known good kernel,using diff.the first is the good one, the second has the mouse not working.but I really don't know which of the listed options could be it.it is a ps/2 Microsoft intellimouse optical.thanks /boot# diff config-2.6.16.060918 config-2.6.16.a[EMAIL PROTECTED]:/boot$ diff config-2.6.16.060918 config-2.6.16.a3,4c3,4 # Linux kernel version: 2.6.16.060918 # Mon Sep 18 18:07:05 2006--- # Linux kernel version: 2.6.16.a # Mon Sep 18 19:38:42 2006531d530 CONFIG_PARPORT_NOT_PC=y1272d1270 CONFIG_FONT_8x16=y1311,1317c1309,1313 CONFIG_USB_EHCI_HCD=m CONFIG_USB_ISP116X_HCD=m CONFIG_USB_OHCI_HCD=m # CONFIG_USB_OHCI_BIG_ENDIAN is not set CONFIG_USB_OHCI_LITTLE_ENDIAN=y CONFIG_USB_UHCI_HCD=m CONFIG_USB_SL811_HCD=m--- # CONFIG_USB_EHCI_HCD is not set # CONFIG_USB_ISP116X_HCD is not set # CONFIG_USB_OHCI_HCD is not set # CONFIG_USB_UHCI_HCD is not set # CONFIG_USB_SL811_HCD is not set1323c1319 CONFIG_USB_AUDIO=m--- # CONFIG_USB_AUDIO is not set1325,1326c1321,1322 CONFIG_USB_ACM=m CONFIG_USB_PRINTER=m--- # CONFIG_USB_ACM is not set # CONFIG_USB_PRINTER is not set1337,1339c1333,1335 CONFIG_USB_STORAGE_FREECOM=y CONFIG_USB_STORAGE_ISD200=y CONFIG_USB_STORAGE_DPCM=y--- # CONFIG_USB_STORAGE_FREECOM is not set # CONFIG_USB_STORAGE_ISD200 is not set # CONFIG_USB_STORAGE_DPCM is not set1355,1364c1351,1360 CONFIG_USB_AIPTEK=m CONFIG_USB_WACOM=m CONFIG_USB_ACECAD=m CONFIG_USB_KBTAB=m CONFIG_USB_POWERMATE=m CONFIG_USB_MTOUCH=m CONFIG_USB_ITMTOUCH=m CONFIG_USB_EGALAX=m CONFIG_USB_XPAD=m CONFIG_USB_ATI_REMOTE=m--- # CONFIG_USB_AIPTEK is not set # CONFIG_USB_WACOM is not set # CONFIG_USB_ACECAD is not set # CONFIG_USB_KBTAB is not set # CONFIG_USB_POWERMATE is not set # CONFIG_USB_MTOUCH is not set # CONFIG_USB_ITMTOUCH is not set # CONFIG_USB_EGALAX is not set # CONFIG_USB_XPAD is not set # CONFIG_USB_ATI_REMOTE is not set1371c1367 CONFIG_USB_MICROTEK=m--- # CONFIG_USB_MICROTEK is not set1377,1383c1373,1379 CONFIG_USB_IBMCAM=m CONFIG_USB_KONICAWC=m CONFIG_USB_OV511=m CONFIG_USB_SE401=m CONFIG_USB_SN9C102=m CONFIG_USB_STV680=m CONFIG_USB_PWC=m--- # CONFIG_USB_IBMCAM is not set # CONFIG_USB_KONICAWC is not set # CONFIG_USB_OV511 is not set # CONFIG_USB_SE401 is not set # CONFIG_USB_SN9C102 is not set # CONFIG_USB_STV680 is not set # CONFIG_USB_PWC is not set1388,1402c1384,1387 CONFIG_USB_KAWETH=m CONFIG_USB_PEGASUS=m CONFIG_USB_USBNET=m CONFIG_USB_NET_AX8817X=m CONFIG_USB_NET_CDCETHER=m CONFIG_USB_NET_GL620A=m CONFIG_USB_NET_NET1080=m CONFIG_USB_NET_CDC_SUBSET=m CONFIG_USB_ALI_M5632=y CONFIG_USB_AN2720=y CONFIG_USB_BELKIN=y CONFIG_USB_ARMLINUX=y CONFIG_USB_EPSON2888=y CONFIG_USB_NET_ZAURUS=m CONFIG_USB_MON=y--- # CONFIG_USB_KAWETH is not set # CONFIG_USB_PEGASUS is not set # CONFIG_USB_USBNET is not set # CONFIG_USB_MON is not set1407c1392 CONFIG_USB_USS720=m--- # CONFIG_USB_USS720 is not set1436,1445c1421,1428 CONFIG_USB_EMI26=m CONFIG_USB_LCD=m CONFIG_USB_LED=m CONFIG_USB_CYTHERM=m CONFIG_USB_PHIDGETKIT=m CONFIG_USB_PHIDGETSERVO=m CONFIG_USB_IDMOUSE=m CONFIG_USB_SISUSBVGA=m CONFIG_USB_SISUSBVGA_CON=y CONFIG_USB_LD=m--- # CONFIG_USB_EMI26 is not set # CONFIG_USB_LCD is not set # CONFIG_USB_LED is not set # CONFIG_USB_CYTHERM is not set # CONFIG_USB_PHIDGETKIT is not set # CONFIG_USB_PHIDGETSERVO is not set # CONFIG_USB_IDMOUSE is not set # CONFIG_USB_LD is not set1454,1470c1437 CONFIG_USB_GADGET=m # CONFIG_USB_GADGET_DEBUG_FILES is not set CONFIG_USB_GADGET_SELECTED=y CONFIG_USB_GADGET_NET2280=y CONFIG_USB_NET2280=m # CONFIG_USB_GADGET_PXA2XX is not set # CONFIG_USB_GADGET_GOKU is not set # CONFIG_USB_GADGET_LH7A40X is not set # CONFIG_USB_GADGET_OMAP is not set # CONFIG_USB_GADGET_DUMMY_HCD is not set CONFIG_USB_GADGET_DUALSPEED=y # CONFIG_USB_ZERO is not set CONFIG_USB_ETH=m # CONFIG_USB_GADGETFS is not set CONFIG_USB_FILE_STORAGE=m # CONFIG_USB_FILE_STORAGE_TEST is not set CONFIG_USB_G_SERIAL=m--- # CONFIG_USB_GADGET is not set[EMAIL PROTECTED]:/boot$ diff config-2.6.16.060918 config-2.6.16.a3,4c3,4 # Linux kernel version: 2.6.16.060918 # Mon Sep 18 18:07:05 2006--- # Linux kernel version: 2.6.16.a # Mon Sep 18 19:38:42 2006531d530 CONFIG_PARPORT_NOT_PC=y1272d1270 CONFIG_FONT_8x16=y1311,1317c1309,1313 CONFIG_USB_EHCI_HCD=m CONFIG_USB_ISP116X_HCD=m CONFIG_USB_OHCI_HCD=m # CONFIG_USB_OHCI_BIG_ENDIAN is not set CONFIG_USB_OHCI_LITTLE_ENDIAN=y CONFIG_USB_UHCI_HCD=m CONFIG_USB_SL811_HCD=m--- # CONFIG_USB_EHCI_HCD is not set # CONFIG_USB_ISP116X_HCD is not set # CONFIG_USB_OHCI_HCD is not set # CONFIG_USB_UHCI_HCD is not set # CONFIG_USB_SL811_HCD is not set1323c1319 CONFIG_USB_AUDIO=m--- # CONFIG_USB_AUDIO is not set1325,1326c1321,1322 CONFIG_USB_ACM=m CONFIG_USB_PRINTER=m--- # CONFIG_USB_ACM is not set # CONFIG_USB_PRINTER is not set1337,1339c1333,1335
Re: mouse not working after kernel rebuild
"Fred J." [EMAIL PROTECTED] wrote: HiI built 2 kernels, the second one in the line below makes the mousenot active and I am trying to find out what feature needs settingin-order to activate the mouse, by comparing with known good kernel,using diff.the first is the good one, the second has the mouse not working.but I really don't know which of the listed options could be it.it is a ps/2 Microsoft intellimouse optical.just a correction;it is a ps/2 and USB compatible mouse, however it is usb connected. Want to be your own boss? Learn how on Yahoo! Small Business.
How to make modules accessible after kernel rebuild
I have built a new kernel (2.4.22), using make-kpkg, and it works OK except that various modules are not being found/loaded. Compared to the old kernel (a standard Debian binary one), I have configured a number of options to be modules instead of built in as they were before. I have tried loading one or two of them manually using modprobe, and they seem to load OK. As an example, my ATAPI CD-ROM drive was accessed correctly by the previous kernel using the built-in ide-cd module. But now, even after loading the ide-cd module manually, the system still seems to try to access it using some SCSI mechanism (presumably the ide-scsi module or something similar). /lib/modules/modprobe.conf and /etc/modules.conf have not been updated by the kernel rebuild, and neither have any files in /etc/modprobe.d. I presume that the problem is simply that the configuration files lack details of the new modules. How can I add the correct details? (Not just the mechanism for adding them, which I presume is to use update-modules, but how I can determine what the correct configuration entries should be.) -- David Jarvie. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel rebuild problems
As far as I can tell, the problem is that the new kernel cannot mount the root filesystem and I have no idea why, as it is ext3 and ext3 is built into the kernel. Are you sure? I mean are you sure it's in the kernal *and* not a module? The symptoms you describe would indicate it is in but only as a module, and that either because the initrd directive is missing from the GRUB config, or because you didn't use the '--initrd' option to make-kpkg, the EXT3 module is not being loaded out of the initial ram disk image. Can you verify by installing (but obviously not attempting to boot) the new kernel and running: grep EXT3 /boot/config* and posting the results? It should say: CONFIG_EXT3_FS=y If it says 'm' then you need to access initrd, and you need to make sure that the initrd contains the ext3 module. If it says 'n' then not even that will help you. Alexis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Kernel rebuild problems
THis is a bit long, but if anyone has insight into buildling 2.6.x kernels maybe they can help before I pull out all of my hair. I installed sarge on my Averatec 3220 (AMD-2000 CPU, 256MB) using the latest version of the installer (this would be about six weeks ago). Everything is fine, except the wireless (builtin Broadcom, needing ndiswrapper). Now, I've also installed kernel-2.6.7-k7 package and the 2.6.7 source. The kernel is fine and works a treat, but I am unable to build my own kernel which will boot. (I've been recompiling kernels since about 1995 so...) As far as I can tell, the problem is that the new kernel cannot mount the root filesystem and I have no idea why, as it is ext3 and ext3 is built into the kernel. The significant difference in the logs is that the 2.6.6-1.k7 kernel package had an initrd with it and the newly-built kernel doesn't. I'm using grub BTW and the initrd line appears to be the only significant difference between the working and non-working menu items. If anyone can shed any light at all on this I'd be very grateful. -- |Deryk Barker, Computer Science Dept. | Music does not have to be understood| |Camosun College, Victoria, BC, Canada| It has to be listened to. | |email: [EMAIL PROTECTED] | | |phone: +1 250 370 4452 | Hermann Scherchen. | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel rebuild problems
Hello [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote: I installed sarge on my Averatec 3220 (AMD-2000 CPU, 256MB) using the latest version of the installer (this would be about six weeks ago). Everything is fine, except the wireless (builtin Broadcom, needing ndiswrapper). Now, I've also installed kernel-2.6.7-k7 package and the 2.6.7 source. The kernel is fine and works a treat, but I am unable to build my own kernel which will boot. (I've been recompiling kernels since about 1995 so...) As far as I can tell, the problem is that the new kernel cannot mount the root filesystem and I have no idea why, as it is ext3 and ext3 is built into the kernel. What about IDE or SCSI support? 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: Kernel Rebuild
Kris [EMAIL PROTECTED] writes: Just to clarify if the file I download is a .deb file then in order to follow the steps listed in the link provided I would have to dpkg --install kernel-PCMCIA-modules-2.4.18-586tsc_2.4.18-5_all.deb Uh, yes, that is how you would install a package with dpkg... in the /usr/src directory where it resides. ...but the directory where it happens to be isn't relevant, and that particular package won't install any files in /usr/src. I've included the relevant excerpts from my original reply. Kris [EMAIL PROTECTED] writes: I seem to be having a problem rebuilding my kernel with PCMCIA. The only source I could find for PCMCIA were PCMCIA-cs_3.1.33-6_i386.deb ...which is the userspace code; you need this, but on it's own it's not enough... and kernel-PCMCIA-modules-2.4.18-586tsc_2.4.18-5_all.deb ...which is prebuilt kernel modules corresponding to this exact kernel. You either need to (a) enable PCMCIA support in the kernel configuration, or (b) disable PCMCIA support in the kernel configuration, install the pcmcia-source package, unpack /usr/src/pcmcia-cs.tar.gz, and run 'make-kpkg modules-image'. -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Kernel Rebuild
I seem to be having a problem rebuilding my kernel with PCMCIA. The only source I could find for PCMCIA were PCMCIA-cs_3.1.33-6_i386.deb and kernel-PCMCIA-modules-2.4.18-586tsc_2.4.18-5_all.deb both of these are dep files. I am following these steps listed at http://qref.sourceforge.net/quick/ch-kernel.en.html for rebuilding a kernel now I assume these are for using the source to build up PCMCIA support but the only debian files I can find are deb what steps do I need to change to make sure that PCMCIA is also incorporated into my new kernel and what is the difference between a source and a deb file. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel Rebuild
On Tue, 1 Apr 2003 15:42:51 -0800 Kris [EMAIL PROTECTED] wrote: both of these are dep files. I am following these steps listed at http://qref.sourceforge.net/quick/ch-kernel.en.html for rebuilding a kernel Try using these directions instead: http://newbiedoc.sourceforge.net/system/kernel-pkg.html The Advanced Topics section describes how to do PCMCIA. Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel Rebuild
Kris [EMAIL PROTECTED] writes: I seem to be having a problem rebuilding my kernel with PCMCIA. The only source I could find for PCMCIA were PCMCIA-cs_3.1.33-6_i386.deb ...which is the userspace code; you need this, but on it's own it's not enough... and kernel-PCMCIA-modules-2.4.18-586tsc_2.4.18-5_all.deb ...which is prebuilt kernel modules corresponding to this exact kernel. both of these are dep files. I am following these steps listed at http://qref.sourceforge.net/quick/ch-kernel.en.html for rebuilding a kernel now I assume these are for using the source to build up PCMCIA support but the only debian files I can find are deb what steps do I need to change to make sure that PCMCIA is also incorporated into my new kernel You either need to (a) enable PCMCIA support in the kernel configuration, or (b) disable PCMCIA support in the kernel configuration, install the pcmcia-source package, unpack /usr/src/pcmcia-cs.tar.gz, and run 'make-kpkg modules-image'. and what is the difference between a source and a deb file. Not entirely clear what you're asking...'source' is the thing the programmer edits, 'binary' is pile of bits, and generally means thing computer is able to run directly. In Debian, there are binary packages (.deb files) and corresponding sources (.dsc files with either corresponding .orig.tar.gz/.diff.gz or .tar.gz files). 'apt-get install' or 'dpkg --install' will install a binary package; 'apt-get source' or 'dpkg-source -x' will retrieve and unpack sources for a package. For kernel modules, there's a special case where a binary package contains sources for kernel modules. These typically install tar files in /usr/src, which you need to unpack and build using make-kpkg. -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Woody kernel rebuild screws the pooch.
Phillip == Phillip Remaker [EMAIL PROTECTED] writes: Phillip Worse, I can't get make-kpkg modules_install to work. I'm Phillip not sure exactly which source I need in /usr/src/modules, Phillip and the make process seems to error out every time. You do not need modules_install. That is only for stand alon modules; and if your usr/src/modules is empty, you have one. The modules in the kernel are handled automatically. The RTL8139 is implemented as a loadable module in woody. But the loadable module from the kernel that came with woody won't work with the one I compiled from kernel-source-2.2.20. I'd implement it natively in the kernel, but I can't find rtl8139 as an option in make menuconfig even though there is an rtl8139.c source file. Hrmph. So I'm TRYING to use the loadable module from the previous kernel, but get wads of unresolved symbols when I run insmod. So then I guess I have 4 options: - Restore the vanilla woody kernel (how) and use the loadable module. - Find out how to compile kernel-source-2.2.20 to work with the stock rtl8139 KLM in woody - Find out how to put the source in /usr/src/modules and comile it after the kernel to ensure compatability (where do I get that source? Can I use the rtl8139.c in the kernel drivers directory? - Find out how to build a kernel with native rtl8139 support. Any of those should save me from my dilemma.
Re: Woody kernel rebuild screws the pooch.
On Sat, 2002-02-02 at 23:41, Phillip Remaker wrote: I'd implement it natively in the kernel, but I can't find rtl8139 as an option in make menuconfig even though there is an rtl8139.c source file. Hrmph. Well, I moved on to 2.4 a while back, but if I remember correctly, the RTL8139 is listed in menuconfig as RealTek. You could always just edit /usr/src/linux/.config and search for 8139, that would do the trick too. One trick I've used to search for correct drivers is: grep -B4 -A4 string /usr/src/linux/Documentation/Configure.help In this case, that would be: grep -B4 -A4 8139 /usr/src/linux/Documentation/Configure.help Cheers, Caleb -- there are no stupid questions, but there are a lot of inquisitive idiots signature.asc Description: This is a digitally signed message part
Re: Woody kernel rebuild screws the pooch.
* Phillip Remaker ([EMAIL PROTECTED]) spake thusly: I seem to be an idiot. I wanted to add sound to by Woody install, and figured I needed to build me a kernel (to add isapnp which seems not to be there by default). The kernel (2.2.20) that installed with the woody installer used the RTL8139 loadable module, and worked great. I followed the make-kpkg instructions, determined to build a kernel the Debian Way. When I went to install it, I did not back up the modules and ignored warnings about the modules, and SURPRISE! The rtl8139 modules fail to load due to unresolved symbols. MY incorrect assumption was that since I was rebuilding mostly the same kernel, I shouldn't have an issue to reuse the old modules. Well, that was wrong. This is usually due to different set version information on all modules (or whatever CONFIG_MODEVERSIONS is called) setting in old/new kernel. Fixed by mv /lib/modules/$VERSION /lib/modules/$VERSION.old before installing new kernel. Those warnings are there for a reason, and now you know what the reason is. Worse, I can't get make-kpkg modules_install to work. I'm not sure exactly which source I need in /usr/src/modules, and the make process seems to error out every time. You don't need that unless you have extra stuff (ie. not part of the kernel tree, like alsa or nvidia) in /usr/src/modules. So the way I see it I have several ways to unhose myself, but can't find good docs on the best way to proceed: 1) Get the right source somewhere and compile and install the kernel right. 2) Punt, and revert to the stock kernel [1] Yes. I don't think I ever used Debian kernel source package, stock kernel builds and installs just fine with make-kpkg (IIRC it's been that way ever since make-kpkg was written). I have booted the rescue disk but it also fails to work (same unresolved symbols problem). I guess I need to better understand how the boot process and module linking works 8-( Simple: modules are installed in /lib/modules/$VERSION. If rescue disk has the same kernel version, you'll have the same unresolved symbols problem with it. I'm feeling dumb. I also assumed (hoped?) that dpkg would have backed up the old kernel for me as part of the process. It did. It's /vmlinuz.old. That doesn't help you any if it's the same kernel version (see above). ...I wish the kernel build process FAQ had a section on you've screwed yourself! *NOW* what do you do? I hate to wipe and reinstall but I'm on the brink of that 8-( Ok, build a 2.2.19 or something ($VERSION that you don't have in /lib/modules). That should give you a bootable system. Then remove 2.2.20, inc. modules, rebuild 2.2.20 and reinstall it. I guess Debian isn't for wimps. Life isn't for wimps. Deal with it. [1] Is it easy to add an isa PNP sound card to the kernel without a recompile? ESS 1869, for the curious. I was thinking perhaps I should revert to the stock kernel and try to install ALSA. Whee. Alsa is not for wimps. ESS cards work fine with OSS/Lite (stock kernel) drivers, but you'll have to learn to use isapnp (ISA PnP sucks by design, there's no way around that). Dima -- I have not been able to think of any way of describing Perl to [person] Hello, blind man? This is color. -- DPM
Woody kernel rebuild screws the pooch.
I seem to be an idiot. I wanted to add sound to by Woody install, and figured I needed to build me a kernel (to add isapnp which seems not to be there by default). The kernel (2.2.20) that installed with the woody installer used the RTL8139 loadable module, and worked great. I followed the make-kpkg instructions, determined to build a kernel the Debian Way. When I went to install it, I did not back up the modules and ignored warnings about the modules, and SURPRISE! The rtl8139 modules fail to load due to unresolved symbols. MY incorrect assumption was that since I was rebuilding mostly the same kernel, I shouldn't have an issue to reuse the old modules. Well, that was wrong. Worse, I can't get make-kpkg modules_install to work. I'm not sure exactly which source I need in /usr/src/modules, and the make process seems to error out every time. Of course, the system is off the air (no ethernet) so I can't cut and paste exact messages 8-( So the way I see it I have several ways to unhose myself, but can't find good docs on the best way to proceed: 1) Get the right source somewhere and compile and install the kernel right. 2) Punt, and revert to the stock kernel [1] I have booted the rescue disk but it also fails to work (same unresolved symbols problem). I guess I need to better understand how the boot process and module linking works 8-( I can't apt-get anything since I wiped the ethernet out 8-( I'm feeling dumb. I also assumed (hoped?) that dpkg would have backed up the old kernel for me as part of the process. I wish the kernel build process FAQ had a section on you've screwed yourself! *NOW* what do you do? I hate to wipe and reinstall but I'm on the brink of that 8-( I guess Debian isn't for wimps. [1] Is it easy to add an isa PNP sound card to the kernel without a recompile? ESS 1869, for the curious. I was thinking perhaps I should revert to the stock kernel and try to install ALSA. Whee.
Re: Woody kernel rebuild screws the pooch.
Phillip == Phillip Remaker [EMAIL PROTECTED] writes: Phillip Worse, I can't get make-kpkg modules_install to work. I'm Phillip not sure exactly which source I need in /usr/src/modules, Phillip and the make process seems to error out every time. You do not need modules_install. That is only for stand alon modules; and if your usr/src/modules is empty, you have one. The modules in the kernel are handled automatically. manoj -- standards, n.: The principles we use to reject other people's code. Manoj Srivastava [EMAIL PROTECTED] http://www.debian.org/%7Esrivasta/ 1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Kernel Rebuild
I'm new to the idea of rebuilding my kernel for including or excluding things in my configuration, but I decided to brave it today and was (fairly) successful. I'm having a little bit of a problem, though. I need both the UMDA66 and the SMP features. I have the potato 2.2r2 installation CD set (the first 3, not the sources), and I'm currently using the UMDA66 kernel (2.2.18pre21) to access my extra hard drives that are on a Promise ATA/66 card. I tried building a new kernel with SMP, but I found that in doing so, I can't seem to include the UMDA66 options that are in the original kernel. Before the new kernel, I had ide0, 1, 2, and 3, but now 2 and 3, which are on the card, aren't found. I know that I could probably just build an SMP module (or perhaps I'm wrong on that) to load in with the original kernel, but I really want to be able to delve into the world of kernel configuration and really make it my own at some point after I'm a bit more comfortable with it. Does anyone know what I need to do in order to include the UMDA66 features in on a custom kernel? Any and all help is appreciated! Jeremy
Re: Kernel Rebuild
On Wed, Jul 04, 2001 at 10:09:34PM -0500, Jeremy wrote: I'm new to the idea of rebuilding my kernel for including or excluding things in my configuration, but I decided to brave it today and was (fairly) successful. I'm having a little bit of a problem, though. I need both the UMDA66 and the SMP features. I have the potato 2.2r2 installation CD set (the first 3, not the sources), and I'm currently using the UMDA66 kernel (2.2.18pre21) to access my extra hard drives that are on a Promise ATA/66 card. I tried building a new kernel with SMP, but I found that in doing so, I can't seem to include the UMDA66 options that are in the original kernel. Before the new kernel, I had ide0, 1, 2, and 3, but now 2 and 3, which are on the card, aren't found. I know that I could probably just build an SMP module (or perhaps I'm wrong on that) to load in with the original kernel, but I really want to be able to delve into the world of kernel configuration and really make it my own at some point after I'm a bit more comfortable with it. Does anyone know what I need to do in order to include the UMDA66 features in on a custom kernel? I believe you need to apply a patch in the 2.2.x series kernel for UDMA-66 support. Did you get your kernel source from the official site (kernel.org or some mirror) or from a Debian mirror with 'apt-get kernel-source-2.2.18' or whatever? I'd be surprised if the Debian sources didn't include this patch. -- Brian Nelson [EMAIL PROTECTED]
Re: Kernel Rebuild
On Wed, Jul 04, 2001 at 10:45:17PM -0400, Brian Nelson wrote: I believe you need to apply a patch in the 2.2.x series kernel for UDMA-66 support. Did you get your kernel source from the official site (kernel.org or some mirror) or from a Debian mirror with 'apt-get kernel-source-2.2.18' or whatever? I'd be surprised if the Debian sources didn't include this patch. Actually, it looks like the patch should be available as a package named something like 'kernel-patch-2.2.18pre21-ide'. -- Brian Nelson [EMAIL PROTECTED]
Re: kernel rebuild w.o./ purging 3rd-party modules?
on Mon, May 14, 2001 at 09:01:22AM -0700, Krzys Majewski ([EMAIL PROTECTED]) wrote: Anybody know how to do kernel rebuilds in such a way that existing 3rd-party kernel modules (ie those not included in the kernel src tree) aren't removed from /lib/modules/... ? Copy them off to the side, the copy them back into /lib/modules when you've installed your new kernel? I don't believe you need to indicate modules to the kernel, but the kernel versions need to match. -- Karsten M. Self kmself@ix.netcom.comhttp://kmself.home.netcom.com/ What part of Gestalt don't you understand? There is no K5 cabal http://gestalt-system.sourceforge.net/ http://www.kuro5hin.org pgp8vzW646if4.pgp Description: PGP signature
Re: [users] Re: kernel rebuild w.o./ purging 3rd-party modules?
also sprach Karsten M. Self (on Wed, 16 May 2001 09:30:37PM -0700): Anybody know how to do kernel rebuilds in such a way that existing 3rd-party kernel modules (ie those not included in the kernel src tree) aren't removed from /lib/modules/... ? Copy them off to the side, the copy them back into /lib/modules when you've installed your new kernel? i don't think modules are removed. that was always my problem with left-over modules after a kernel rebuild and subsequent non-defined symbols when running depmod -a. but just to be sure, do as karsten says. martin; (greetings from the heart of the sun.) \ echo mailto: !#^.*|tr * mailto:; [EMAIL PROTECTED] -- al telefono: pronto? cantina sociale?. hic!.
kernel rebuild w.o./ purging 3rd-party modules?
Anybody know how to do kernel rebuilds in such a way that existing 3rd-party kernel modules (ie those not included in the kernel src tree) aren't removed from /lib/modules/... ? -chris
No booting after kernel rebuild possible
Hello, using Debian 2.1 from the O'Reilly-Book Learning Debian GNU/Linux, I'm wondering about a problem after kernel rebuild, no starting neither with the new kernel nor with the old kernel is possible: Partition check: request_module[block-major-8]: Root fs not mounted VFS: Cannot open root device 08:01 (here: /dev/sda1) Kernel panic: VFS: Unable to mount root fs on 08:01 A fsck ext2 /dev/sda1, done from the minisystem of the rescue/root floppydisk doesn't report any fs problems. The /etc/fstab seems correct, too. Did anyone observe this problem and knows how to get the machine (Pentium 133MHz) booting up again? Thank you for every useful hint, Christoph -- Sent through GMX FreeMail - http://www.gmx.net
Re: Kernel rebuild
Sorry this reply took so long to post; I had to figure out how to get the ppp.log file created, then out of Linux and into Windows so I could share it with you. The ppp.log file listed below contains two attempts from today. The first attempt was done after a clean floppy install (ppp, slip, bsd compression, etc. all installed), but before running pppconfig to configure the CHAP stuff. As such, the first attempt only contains the basic changes I made to both provider files to include the phone number of my ISP, my username and password. That one at least says CONNECT at one point, then logs me off because (I think) the prompting is wrong in the chatscript provider (? I'm guessing.) Of course, my provider hasn't replied with the correct login prompts, and he said the board was run using CHAP anyways, so I'm lost (or he is?) On this note, simply dialing the number via Procomm yields no prompts, just a blank screen, so I can't determine the prompts for myself using that method. The second attempt was after running the pppconfig utility (which is almost identical in operation and the changes it makes to pppsetup (which I have tried as well) for those more familiar with that utility) to setup CHAP. In addition to what you can ascertain from this file, please note I have tried running the later script as PAP, CHAP, using noauth, and auth, and it always comes out identical to the listing. Again, any assistance would be greatly appreciated. No pppconfig: Nov 4 18:57:18 Debian pppd[152]: pppd 2.3.5 started by root, uid 0 Nov 4 18:57:19 Debian chat[153]: abort on (BUSY) Nov 4 18:57:19 Debian chat[153]: abort on (NO CARRIER) Nov 4 18:57:19 Debian chat[153]: abort on (VOICE) Nov 4 18:57:19 Debian chat[153]: abort on (NO DIALTONE) Nov 4 18:57:19 Debian chat[153]: send (ATDT*70,3251981^M) Nov 4 18:57:19 Debian chat[153]: expect (ogin) Nov 4 18:57:40 Debian chat[153]: ^M Nov 4 18:57:40 Debian chat[153]: CONNECT 24000/ARQ/V34/LAPM/V42BIS^M Nov 4 18:58:04 Debian chat[153]: alarm Nov 4 18:58:04 Debian chat[153]: Failed Nov 4 18:58:04 Debian pppd[152]: Connect script failed Nov 4 18:58:36 Debian chat[174]: abort on (BUSY) Nov 4 18:58:36 Debian chat[174]: abort on (NO CARRIER) Nov 4 18:58:36 Debian chat[174]: abort on (VOICE) Nov 4 18:58:36 Debian chat[174]: abort on (NO DIALTONE) Nov 4 18:58:36 Debian chat[174]: send (ATDT*70,3251981^M) Nov 4 18:58:36 Debian chat[174]: expect (ogin) After pppconfig: Nov 4 19:09:50 Debian pppd[222]: pppd 2.3.5 started by root, uid 0 Nov 4 19:09:51 Debian chat[223]: abort on (BUSY) Nov 4 19:09:51 Debian chat[223]: abort on (NO CARRIER) Nov 4 19:09:51 Debian chat[223]: abort on (VOICE) Nov 4 19:09:51 Debian chat[223]: abort on (NO DIALTONE) Nov 4 19:09:51 Debian chat[223]: abort on (NO ANSWER) Nov 4 19:09:51 Debian chat[223]: send (ATZ^M) Nov 4 19:09:51 Debian chat[223]: expect (OK) Nov 4 19:09:51 Debian chat[223]: ^M Nov 4 19:09:51 Debian chat[223]: OK Nov 4 19:09:51 Debian chat[223]: -- got it Nov 4 19:09:51 Debian chat[223]: send (ATDT*70,3251981^M) Nov 4 19:09:52 Debian chat[223]: expect (CONNECT) Nov 4 19:09:52 Debian chat[223]: ^M Nov 4 19:10:14 Debian chat[223]: ^M Nov 4 19:10:14 Debian chat[223]: CONNECT Nov 4 19:10:14 Debian chat[223]: -- got it Nov 4 19:10:14 Debian chat[223]: send (\d) Nov 4 19:10:15 Debian pppd[222]: Serial connection established. Nov 4 19:10:16 Debian pppd[222]: Using interface ppp0 Nov 4 19:10:16 Debian pppd[222]: Connect: ppp0 -- /dev/ttyS1 Nov 4 19:10:16 Debian pppd[222]: sent [LCP ConfReq id=0x1 asyncmap 0x0 magic 0xa021 pcomp accomp] Nov 4 19:10:43 Debian last message repeated 9 times Nov 4 19:10:46 Debian pppd[222]: LCP: timeout sending Config-Requests Nov 4 19:10:46 Debian pppd[222]: Connection terminated. Nov 4 19:10:46 Debian pppd[222]: Hangup (SIGHUP) Nov 4 19:10:46 Debian pppd[222]: Exit. Waif
Re: Kernel rebuild
On Wed, 4 Nov 1998, Waif W. Urchin wrote: Sorry this reply took so long to post; I had to figure out how to get the ppp.log file created, then out of Linux and into Windows so I could share it with you. Thats quite alright... :) The ppp.log file listed below contains two attempts from today. The first attempt was done after a clean floppy install (ppp, slip, bsd compression, etc. all installed), but before running pppconfig to configure the CHAP stuff. As such, the first attempt only contains the basic changes I made to both provider files to include the phone number of my ISP, my username and password. That one at least says CONNECT at one point, then logs me off because (I think) the prompting is wrong in the chatscript provider (? I'm guessing.) Of course, my provider hasn't replied with the correct login prompts, and he said the board was run using CHAP anyways, so I'm lost (or he is?) On this note, simply dialing the number via Procomm yields no prompts, just a blank screen, so I can't determine the prompts for myself using that method. The second attempt was after running the pppconfig utility (which is almost identical in operation and the changes it makes to pppsetup (which I have tried as well) for those more familiar with that utility) to setup CHAP. In addition to what you can ascertain from this file, please note I have tried running the later script as PAP, CHAP, using noauth, and auth, and it always comes out identical to the listing. A couple of things, are you using 'user user' in your /etc/ppp/peers/provider ?? The user should be the same as your login at your ISP, and you should put a line in /etc/ppp/pap-secrets like so: user * password (there are directions in that file - check chap-secrets too.) This should get your authentication working, although I dont know if that is what is needed. Secondly, have you tried dialing your ISP with a program such as minicom to see if there is in fact a login prompt you must use? Again, any assistance would be greatly appreciated. No problems. No pppconfig: Nov 4 18:57:18 Debian pppd[152]: pppd 2.3.5 started by root, uid 0 Nov 4 18:57:19 Debian chat[153]: abort on (BUSY) Nov 4 18:57:19 Debian chat[153]: abort on (NO CARRIER) Nov 4 18:57:19 Debian chat[153]: abort on (VOICE) Nov 4 18:57:19 Debian chat[153]: abort on (NO DIALTONE) Nov 4 18:57:19 Debian chat[153]: send (ATDT*70,3251981^M) Nov 4 18:57:19 Debian chat[153]: expect (ogin) Nov 4 18:57:40 Debian chat[153]: ^M Nov 4 18:57:40 Debian chat[153]: CONNECT 24000/ARQ/V34/LAPM/V42BIS^M Nov 4 18:58:04 Debian chat[153]: alarm Nov 4 18:58:04 Debian chat[153]: Failed Nov 4 18:58:04 Debian pppd[152]: Connect script failed Nov 4 18:58:36 Debian chat[174]: abort on (BUSY) Nov 4 18:58:36 Debian chat[174]: abort on (NO CARRIER) Nov 4 18:58:36 Debian chat[174]: abort on (VOICE) Nov 4 18:58:36 Debian chat[174]: abort on (NO DIALTONE) Nov 4 18:58:36 Debian chat[174]: send (ATDT*70,3251981^M) Nov 4 18:58:36 Debian chat[174]: expect (ogin) After pppconfig: Nov 4 19:09:50 Debian pppd[222]: pppd 2.3.5 started by root, uid 0 Nov 4 19:09:51 Debian chat[223]: abort on (BUSY) Nov 4 19:09:51 Debian chat[223]: abort on (NO CARRIER) Nov 4 19:09:51 Debian chat[223]: abort on (VOICE) Nov 4 19:09:51 Debian chat[223]: abort on (NO DIALTONE) Nov 4 19:09:51 Debian chat[223]: abort on (NO ANSWER) Nov 4 19:09:51 Debian chat[223]: send (ATZ^M) Nov 4 19:09:51 Debian chat[223]: expect (OK) Nov 4 19:09:51 Debian chat[223]: ^M Nov 4 19:09:51 Debian chat[223]: OK Nov 4 19:09:51 Debian chat[223]: -- got it Nov 4 19:09:51 Debian chat[223]: send (ATDT*70,3251981^M) Nov 4 19:09:52 Debian chat[223]: expect (CONNECT) Nov 4 19:09:52 Debian chat[223]: ^M Nov 4 19:10:14 Debian chat[223]: ^M Nov 4 19:10:14 Debian chat[223]: CONNECT Nov 4 19:10:14 Debian chat[223]: -- got it Nov 4 19:10:14 Debian chat[223]: send (\d) Nov 4 19:10:15 Debian pppd[222]: Serial connection established. Nov 4 19:10:16 Debian pppd[222]: Using interface ppp0 Nov 4 19:10:16 Debian pppd[222]: Connect: ppp0 -- /dev/ttyS1 Nov 4 19:10:16 Debian pppd[222]: sent [LCP ConfReq id=0x1 asyncmap 0x0 magic 0xa021 pcomp accomp] Nov 4 19:10:43 Debian last message repeated 9 times Nov 4 19:10:46 Debian pppd[222]: LCP: timeout sending Config-Requests Nov 4 19:10:46 Debian pppd[222]: Connection terminated. Nov 4 19:10:46 Debian pppd[222]: Hangup (SIGHUP) Nov 4 19:10:46 Debian pppd[222]: Exit. Waif -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null Michael Beattie ([EMAIL PROTECTED]) PGP Key available, reply with pgpkey as subject. - Mulder: Could say the guy was running on empty. -
RE: Kernel rebuild
From: Waif W. Urchin[SMTP:[EMAIL PROTECTED] Grr... Alright, still trying to recompile my kernel after doing an initial install from floppy. While I'm not particularly able to help with your problem, I'd guess that you don't actually need to recompile the kernel. So maybe you can avoid the stress... I can't think of a reason why you'd need a new kernel to fix a PPP dialup problem. It's certainly not impossible, but I'd try other avenues first. Maybe post the PPP log to the list, as someone else suggested... Paul
Kernel rebuild
Grr... Alright, still trying to recompile my kernel after doing an initial install from floppy. First I couldn't find 'make'. As pointed out (nicely) by some of you, the floppy install apparently does not contain this file. Downloaded and dpkg'd it (I actually had dpkg installed!). Tried it, and it works. So now I have a functioning make command, and the new linux-2_0_35_tar.gz source all decompressed and ready to go. Of course, my symbolic links and, since I can now run 'make mrproper', my old kernel crud (.o files, .tmp files, etc) is flushed and or set and ready. I typed 'make menuconfig', because the menu sounded much more palatable. Debian can't find menuconfig. Ok, I guess I expected that. I typed 'menu config' and launched into the text based config utility for the kernel. Spent a half hour or so poking through what did what, and figuring out what I thought I needed to make this thing shine. Finished config and went to the next step. Typed 'make dep'. Debain can't find gcc. I'm going to either cry, or see if I can cover the distance to the neighbor's house by heaving the computer from the window. Maybe both. From reading the error, gcc (which (by going through windows again) I was able to download) is dependent on binutils (which I am downloading as I type this), and cpp. Where do I find, and what is cpp? Is it part of libc? The version of Debian I'm working with uses lib.so.6 (apparently a pretty new version). I can't find a libc.6.anything on ftp at sunsite or debian.org. But if my system can find lib.so.6, shouldn't cpp be in there if cpp is in fact part of libc? And, while I'm at it, are there any other files I should grab while I'm in Windows anyways? I'd like to find a nice essential things to download after doing a bare floppy install FAQ or some such. Thanks again, Waif
Re: Kernel rebuild
WWU == Waif W Urchin [EMAIL PROTECTED] writes: WWU Debain can't find gcc. Well gcc is a compiler. You can't expet to have this big fat thing on this few disks. WWU Where do I find, and what is cpp? Is it part of libc? The version of cpp is the C (the programming language) preprocessor. It is not part of libc6. WWU And, while I'm at it, are there any other files I should grab while I'm WWU in Windows anyways? bin86, or you won't be able to compile/install the kernel. WWU I'd like to find a nice essential things to download after doing a bare WWU floppy install FAQ or some such. That would depend on what you want to archive. Maybe you could write such document (maybe as a mini-howto) after your experience? It would be a snap, if you had an internet connection with Linux. You would then simply use apt. apt-get install gcc would fetch gcc and all other packages it needs and install them. Ciao, Martin -- from a 1996 Microshit ad campaign: The less you know about computers the more you want Micro$oft! See! They do get some things right!
Re: Kernel rebuild
On Sun, 1 Nov 1998, Waif W. Urchin wrote: [ snip ] : I'd like to find a nice essential things to download after doing a bare : floppy install FAQ or some such. There is a reason the install throws you into dselect after the initial reboot :) dselect has a minimum set of packages ready for you. -- Nathan Norman MidcoNet 410 South Phillips Avenue Sioux Falls, SD mailto:[EMAIL PROTECTED] http://www.midco.net finger [EMAIL PROTECTED] for PGP Key: (0xA33B86E9)
Re: Kernel rebuild
In response to all of the below, I would recommend that you try to get your ppp connection to work, so you can _finish_ the installation. The kernel is probably the least of your worries at this point in time. If you post the tail of your /var/log/ppp.log file, starting from where pppd is fired up, We can help you further. Or, if you feel inclined, get yourself a CD set from lsl or cheapbytes. On Sun, 1 Nov 1998, Waif W. Urchin wrote: Grr... Alright, still trying to recompile my kernel after doing an initial install from floppy. First I couldn't find 'make'. As pointed out (nicely) by some of you, the floppy install apparently does not contain this file. Downloaded and dpkg'd it (I actually had dpkg installed!). Tried it, and it works. So now I have a functioning make command, and the new linux-2_0_35_tar.gz source all decompressed and ready to go. Of course, my symbolic links and, since I can now run 'make mrproper', my old kernel crud (.o files, .tmp files, etc) is flushed and or set and ready. I typed 'make menuconfig', because the menu sounded much more palatable. Debian can't find menuconfig. Ok, I guess I expected that. I typed 'menu config' and launched into the text based config utility for the kernel. Spent a half hour or so poking through what did what, and figuring out what I thought I needed to make this thing shine. Finished config and went to the next step. Typed 'make dep'. Debain can't find gcc. I'm going to either cry, or see if I can cover the distance to the neighbor's house by heaving the computer from the window. Maybe both. From reading the error, gcc (which (by going through windows again) I was able to download) is dependent on binutils (which I am downloading as I type this), and cpp. Where do I find, and what is cpp? Is it part of libc? The version of Debian I'm working with uses lib.so.6 (apparently a pretty new version). I can't find a libc.6.anything on ftp at sunsite or debian.org. But if my system can find lib.so.6, shouldn't cpp be in there if cpp is in fact part of libc? And, while I'm at it, are there any other files I should grab while I'm in Windows anyways? I'd like to find a nice essential things to download after doing a bare floppy install FAQ or some such. Thanks again, Waif -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null Michael Beattie ([EMAIL PROTECTED]) PGP Key available, reply with pgpkey as subject. - Documentation - The worst part of programming. - Debian GNU/Linux Ooohh You are missing out!
Problems with Debian 1.3.1 kernel rebuild
I've rebuilt my kernel and the compile goes well. However, /lib/modules/2.0.30/modules.dep does not get created properly on the first reboot. The kernel says its creating it (which it does), but its completely empty. Help -- Harmon -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Problems with Debian 1.3.1 kernel rebuild
Did you say make modules modules_install when you built the kernel? Bruce -- Can you get your operating system fixed when you need it? Linux - the supportable operating system. http://www.debian.org/support.html Bruce Perens K6BP [EMAIL PROTECTED] 510-215-3502 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Problems with Debian 1.3.1 kernel rebuild
On Sun, 10 Aug 1997, Harmon Sequoya Nine wrote: I've rebuilt my kernel and the compile goes well. However, /lib/modules/2.0.30/modules.dep does not get created properly on the first reboot. The kernel says its creating it (which it does), but its completely empty. I have a nearly similar problem with the booting process telling me it cannot read the /lib/modules/2.0.30 directory. But in my case it does not matter because I do not have loadable modules. So the dirtectory should be empty if you do not have loadable modules. If I missed your point try doing make modules etc steps in compiling the kernel. ~~~ D.J. Mashao, [EMAIL PROTECTED] --- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Problems with Debian 1.3.1 kernel rebuild
Hi, On Sun, 10 Aug 1997, Harmon Sequoya Nine wrote: Harmon I've rebuilt my kernel and the compile goes well. However, Harmon /lib/modules/2.0.30/modules.dep does not get created properly Harmon on the first reboot. The kernel says its creating it (which it Harmon does), but its completely empty. AFAIK, the modules.dep file is created by depmod -a (has to be run as root). depmod -a is run early during the booting up process (/etc/init.d/modules or /etc/init.d/modutils). A possible cause of error could be the newly introduced incompatibility in modutils/modules package: it has not grown intolerant of non .0 files in /lib/modules/2.0.30. (Running depmod -a -v manually as super user should confirm this). Newer kernel-image packages (created using newer kernel-package packages) do not put non .o files under /lib/modules; older packages tended to have text files there. If this is the case, remove any file that causes depmod -a to have hissy fits. The following may help identify those files. # find /lib/modules/2.0.30 -type f | xargs file | grep -v 'ELF 32-bit LSB' /lib/modules/2.0.30/modules.dep: ASCII text The only acceptable file is modules.dep. Hope this helps. manoj -- NASA Announces New Deck Chair Arrangement For Space Station Titanic. Tom Neff Manoj Srivastava url:mailto:[EMAIL PROTECTED] Mobile, Alabama USAurl:http://www.datasync.com/%7Esrivasta/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
