From dnasoc at swbell.net Fri Mar 11 09:55:49 2005 From: dnasoc at swbell.net (Randy Dawson) Date: Fri Mar 11 10:55:54 2005 Subject: [Wd_general] questions on kernel rebuild in WD Message-ID: <000a01c52652$cc1d8e70$6401a8c0@dawson6dr3ohvp> Hello Scott, and list group, I am using the new White Dwarf 2.2 I am rebuilding the kernel to add IrDA support for a Kontron DIMM-PC with a Winbond W83977ATF super I/O chip. I rebuild the kernel in /usr/src/linux with the standard: make menuconfig make dep make clean make bzImage make modules make modules_install my modules end up in /test/kernel/lib/modules/2.4.29 and after moving bzImage to root, editing and rerunning lilo on reboot I get unresolved symbols in /lib/modules/2.4.29 What is going on here, the kernel rebild is non-standard and modules end up in a different directory? I see Scott you have several scripts you have written to do a rebuild: wd.build-kernel, mkbase.sh Can you tell us what these are for how to use them and what is the correct proceedure to rebuild the kernel with your distribution? Thanks, Randy Dawson-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.emji.net/pipermail/wd_general/attachments/20050311/639d0c53/attachment.htm From scott at blast.com Sat Mar 12 11:16:32 2005 From: scott at blast.com (Scott Every) Date: Sat Mar 12 11:13:06 2005 Subject: [Wd_general] security updates, 3/12/2005 Message-ID: <17ae869bd899b8bf3af6a94554c3f6cb@blast.com> couple of new packages, openssl: ftp://ftp.wdlinux.org/pub/wd/extras/openssl-0.9.7e-i386-wd2.2.tgz ftp://ftp.wdlinux.org/pub/wd/extras/openssl-0.9.7e-i386-wd2.2.tgz.md5 and openssh 4.0p1: ftp://ftp.wdlinux.org/pub/wd/extras/openssh-4.0p1-i386-wd2.2.tgz ftp://ftp.wdlinux.org/pub/wd/extras/openssh-4.0p1-i386-wd2.2.tgz.md5 openssl 0.9.7e is included on the wdlinux 2.2 cd openssh 4.0p1 just came out a couple days ago. let me know of any problems or concerns. both are working fine on our test systems at blast. s Scott Every Blast Wireless http://www.blast.com/ From scott at blast.com Mon Mar 21 22:49:08 2005 From: scott at blast.com (Scott Every) Date: Mon Mar 21 22:45:35 2005 Subject: [Wd_general] questions on kernel rebuild in WD In-Reply-To: <000a01c52652$cc1d8e70$6401a8c0@dawson6dr3ohvp> References: <000a01c52652$cc1d8e70$6401a8c0@dawson6dr3ohvp> Message-ID: <4281031d4b731a67e026a5a3d63bfff8@blast.com> On Mar 11, 2005, at 10:55 AM, Randy Dawson wrote: > Hello Scott, and list group, > ? > I am using the new White Dwarf 2.2 > ? > I am rebuilding the kernel to add IrDA support for a Kontron DIMM-PC > with a Winbond W83977ATF super I/O chip. > ? > I rebuild the kernel in /usr/src/linux with the standard: > where is your .config file coming from? you should be using the one matching your running kernel: ls -la /wdboot #and compre to: ls -la /kernels/configs then copy the kernel config to the kernel source directory (assume lk2.4.29_wd2.2_elan_ide for this discussion): cp /kernels/configs/lk2.4.29_wd2.2_elan_ide /usr/src/linux/.config cd /usr/src/linux make oldconfig proceed as you have written below > ? > make menuconfig > make dep > make clean > make bzImage > make modules > make modules_install > ? > my modules end up in /test/kernel/lib/modules/2.4.29 > ? > and after moving bzImage to root, editing and rerunning lilo on reboot > I get > ? > unresolved symbols in /lib/modules/2.4.29 > > What is going on here, the kernel rebild is non-standard and modules > end up in a different directory? > this is usually due to modules left over from a previous kernel build. ie if you didn't use the right config file matching the kernel you installed with some of the modules from the old kernel will NOT get compiled into the new kernel, but since the kernel version hasn't changed they are still living in /lib/modules/2.4.29 this is just a warning. to fix, either kill lib/modules/2.4.29 before installing your new kernel or work from the config file from your running kernel. > ? > I see Scott you have several scripts you have written to do a rebuild: > wd.build-kernel, mkbase.sh > ? ./wd.build-kernel should build a kernel package and place it in /current(make sure /current exists) then you would use installpkg /current/your_kernel.tgz. Usage: cd /usr/src/linux cp /kernels/configs/lk2.4.29_wd2.2_elan_ide lk2.4.29_wd2.2_elan_ide_myoptions ./wd.build-kernel lk2.4.29_wd2.2_elan_ide_myoptions(for instance, substitute kernel file of your choice) installpkg /current/lk2.4.29_wd2.2_elan_ide_myoptions.tgz reboot this is somewhat untested and basic directions on using these tools haven't been written. however, its roughly the procedure we use to create the kernels we ship on the cd. > Can you tell us what these are for how to use them and what is the > correct proceedure to rebuild the kernel with your distribution? either build it manually like the first set of directions or use wd.build-kernel to create a package hope that helps. s > ? > Thanks, > ? > Randy Dawson > _______________________________________________ > Wd_general mailing list > Wd_general@lists.emji.net > http://lists.emji.net/mailman/listinfo/wd_general -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/enriched Size: 4051 bytes Desc: not available Url : http://lists.emji.net/pipermail/wd_general/attachments/20050321/7135e276/attachment.bin From zachariah.cherian at paybytouch.com Sun Mar 6 03:09:17 2005 From: zachariah.cherian at paybytouch.com (Zachariah Cherian) Date: Wed Mar 22 21:08:36 2006 Subject: [Wd_general] GDB that goes with WD 2.10 Message-ID: I have WD 2.1 running on a small SiS CPU based PC. I built gdb6.3 on it and tried using it with a multi-threaded application that I developed. This application uses pthreads. I found that gdb wouldn't report on the threads with the command "info threads". I therefore cannot switch between threads without IDs as reported by gdb. Also gdb doesn't report threads being spawned as is customary with same gdb version on say RedHat. Something like New thread[LWP xxx] etc. when a new thread is created. Looking at the processes I do see the LWPs running for that executable. Any suggestions on how to get GDB working with threads on White Dwarf? TID ZC -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.emji.net/pipermail/wd_general/attachments/20050306/d3fd3c52/attachment.htm