From: EXT-McGhehey, M. J <Mar...@bo...> - 2006-11-30 18:28:30
|
In the recent builds that I have been working with (i.e. buildroot 1174 and up) I have noticed the following behavior. Upon doing a fresh build of the entire buildroot (i.e. running make defconfig, make menuconfig, and make at the top-level) both wifistix marvell drivers (cfio.ko and mcf25.ko) end up getting placed in the proper kernel modules/drivers directories under /root. And life is good. However, after I go into the linux-2.6.18gum dir., add new features (via menuconfig) and then rebuild; the marvell drivers are no longer present in the kernel modules/drivers dir under /root. And life is bad. Can I simply untar the marvell-binaries file that's in the download dir. to put these drivers back in right locations, or is there more to it than that?? Thanks Mark J. McGhehey - Senior Software Engineer Validation Instrumentation Technology Seattle, WA USA (206)655-2116 voice (206)655-2709 fax K1200GT |
From: Dave H. <dhy...@gm...> - 2006-11-30 18:56:23
|
Hi Mark, > However, after I go into the linux-2.6.18gum dir., add new features > (via menuconfig) and then rebuild; the marvell drivers are no longer > present in the kernel modules/drivers dir under /root. And life is bad. Hmmm. There is no reason for them to disappear. I'll give it a whirl tonight when I get home. When you do the menuconfig command inside the linux-2.6.18gum dir are you doing: make ARCH=arm menuconfig Oh wait a minute - are you doing the make from within the linux directory? I normally do the following from the gumstix-buildroot directory rm buildroot_arm_nofpu/linux-2.6.18gum/arch/arm/boot/compressed/vmlinux make Doing the rm will cause the top-level make to run make on the kernel with all of the appropriate command line options. > Can I simply untar the marvell-binaries file that's in the download > dir. to put these drivers back in right locations, or is there more to > it than that?? The modules.dep and modules.symbols probably need to be updated as well. depmod normally does this automatically, but if the modules are missing it won't. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: EXT-McGhehey, M. J <Mar...@bo...> - 2006-11-30 19:47:11
|
Dave, Yes. I am doing "make ARCH=3Darm menuconfig" and then "make" all from within the linux dir. Also, I then go to the top-level and do "make" from there as well in order to produce the rootfs file. I'll try your "rm" method now and see how that works. Thanks!!! -----Original Message----- From: Dave Hylands [mailto:dhy...@gm...]=20 Sent: Thursday, November 30, 2006 10:56 AM To: General mailing list for gumstix users. Subject: Re: [Gumstix-users] Wifi kernel modules disappear (cfio.ko andmcf25.ko) Hi Mark, > However, after I go into the linux-2.6.18gum dir., add new features=20 > (via menuconfig) and then rebuild; the marvell drivers are no longer=20 > present in the kernel modules/drivers dir under /root. And life is bad. Hmmm. There is no reason for them to disappear. I'll give it a whirl tonight when I get home. When you do the menuconfig command inside the linux-2.6.18gum dir are you doing: make ARCH=3Darm menuconfig Oh wait a minute - are you doing the make from within the linux directory? I normally do the following from the gumstix-buildroot directory rm buildroot_arm_nofpu/linux-2.6.18gum/arch/arm/boot/compressed/vmlinux make Doing the rm will cause the top-level make to run make on the kernel with all of the appropriate command line options. > Can I simply untar the marvell-binaries file that's in the download=20 > dir. to put these drivers back in right locations, or is there more to > it than that?? The modules.dep and modules.symbols probably need to be updated as well. depmod normally does this automatically, but if the modules are missing it won't. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ ------------------------------------------------------------------------ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDE V _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Craig H. <cr...@gu...> - 2006-11-30 19:50:19
|
On Nov 30, 2006, at 10:56 AM, Dave Hylands wrote: > The modules.dep and modules.symbols probably need to be updated as > well. depmod normally does this automatically, but if the modules are > missing it won't. depmod -a runs when the gumstix boots, so that should be OK. C |
From: Polychronis Y. <ypod@MIT.EDU> - 2006-11-30 20:51:05
|
Oh, BTW if you just extract/copy the modules from gumstix-buildroot-nocfio/dl/marvell-binaries-2.6.18-1.tar to your gumstix after you transfer the new image to it, it should work just fine. Just make sure your kernel is the same version as the binary modules. p. Dave Hylands wrote: > Hi Mark, > > >> However, after I go into the linux-2.6.18gum dir., add new features >> (via menuconfig) and then rebuild; the marvell drivers are no longer >> present in the kernel modules/drivers dir under /root. And life is bad. >> > > Hmmm. There is no reason for them to disappear. I'll give it a whirl > tonight when I get home. > > When you do the menuconfig command inside the linux-2.6.18gum dir are you doing: > > make ARCH=arm menuconfig > > Oh wait a minute - are you doing the make from within the linux > directory? I normally do the following from the gumstix-buildroot > directory > > rm buildroot_arm_nofpu/linux-2.6.18gum/arch/arm/boot/compressed/vmlinux > make > > Doing the rm will cause the top-level make to run make on the kernel > with all of the appropriate command line options. > > >> Can I simply untar the marvell-binaries file that's in the download >> dir. to put these drivers back in right locations, or is there more to >> it than that?? >> > > The modules.dep and modules.symbols probably need to be updated as > well. depmod normally does this automatically, but if the modules are > missing it won't. > > |
From: Polychronis Y. <ypod@MIT.EDU> - 2006-12-01 00:28:00
|
I have encountered the same problem. I didn't want to delete buildroot_arm_nofpu because I just built a new kernel in there and that's what I wanted to test. But the new kernel did not contain cfio.ko and mcf.ko anymore. I checked that "wifistix" was checked before making the buildroot, after making the kernel, but the marvel modules were still not the final image. It looks like buildroot thinks the modules are in place, so doesn't overwrite them from the marvel-binaries, but by building the kernel they were removed. This is a very good example why things keep going wrong if your "design" is wrong in the first place! If the drivers source code were open, the whole system would compile like a breeze. :-) Oh, BTW if you just extract/copy the modules from gumstix-buildroot-nocfio/dl/marvell-binaries-2.6.18-1.tar to your gumstix after you transfer the new image to it, it should work just fine. Just make sure your kernel is the same version as the binary modules. Polychronis Dave Hylands wrote: > Hi Mark, > > >> However, after I go into the linux-2.6.18gum dir., add new features >> (via menuconfig) and then rebuild; the marvell drivers are no longer >> present in the kernel modules/drivers dir under /root. And life is bad. >> > > Hmmm. There is no reason for them to disappear. I'll give it a whirl > tonight when I get home. > > When you do the menuconfig command inside the linux-2.6.18gum dir are you doing: > > make ARCH=arm menuconfig > > Oh wait a minute - are you doing the make from within the linux > directory? I normally do the following from the gumstix-buildroot > directory > > rm buildroot_arm_nofpu/linux-2.6.18gum/arch/arm/boot/compressed/vmlinux > make > > Doing the rm will cause the top-level make to run make on the kernel > with all of the appropriate command line options. > > >> Can I simply untar the marvell-binaries file that's in the download >> dir. to put these drivers back in right locations, or is there more to >> it than that?? >> > > The modules.dep and modules.symbols probably need to be updated as > well. depmod normally does this automatically, but if the modules are > missing it won't. > > |
From: Craig H. <cr...@gu...> - 2006-11-30 19:49:38
|
On Nov 30, 2006, at 10:28 AM, EXT-McGhehey, Mark J wrote: > > In the recent builds that I have been working with (i.e. buildroot > 1174 and up) I have noticed the following behavior. Upon doing a > fresh > build of the entire buildroot (i.e. running make defconfig, make > menuconfig, and make at the top-level) both wifistix marvell drivers > (cfio.ko and mcf25.ko) end up getting placed in the proper kernel > modules/drivers directories under /root. And life is good. > > However, after I go into the linux-2.6.18gum dir., add new features > (via menuconfig) and then rebuild; the marvell drivers are no longer > present in the kernel modules/drivers dir under /root. And life is > bad. > > Can I simply untar the marvell-binaries file that's in the download > dir. to put these drivers back in right locations, or is there more to > it than that?? That's all you need to do. I thought I'd got the situation you describe taken care of, but I'll double-check the Makefile. C |
From: Polychronis Y. <ypod@MIT.EDU> - 2006-11-30 20:48:33
|
I have encountered the same problem. I didn't want to delete buildroot_arm_nofpu because I just built a new kernel in there and that's what I wanted to test. But the new kernel did not contain cfio.ko and mcf.ko anymore. I checked that "wifistix" was checked before making the buildroot, after making the kernel, but the marvel modules were still not the final image. It looks like buildroot thinks the modules are in place, so doesn't overwrite them from the marvel-binaries, but by building the kernel they were removed. This is a very good example why things keep going wrong if your "design" is wrong in the first place! If the drivers source code were open, the whole system would compile like a breeze. :-) p. Dave Hylands wrote: > Hi Mark, > > >> However, after I go into the linux-2.6.18gum dir., add new features >> (via menuconfig) and then rebuild; the marvell drivers are no longer >> present in the kernel modules/drivers dir under /root. And life is bad. >> > > Hmmm. There is no reason for them to disappear. I'll give it a whirl > tonight when I get home. > > When you do the menuconfig command inside the linux-2.6.18gum dir are you doing: > > make ARCH=arm menuconfig > > Oh wait a minute - are you doing the make from within the linux > directory? I normally do the following from the gumstix-buildroot > directory > > rm buildroot_arm_nofpu/linux-2.6.18gum/arch/arm/boot/compressed/vmlinux > make > > Doing the rm will cause the top-level make to run make on the kernel > with all of the appropriate command line options. > > >> Can I simply untar the marvell-binaries file that's in the download >> dir. to put these drivers back in right locations, or is there more to >> it than that?? >> > > The modules.dep and modules.symbols probably need to be updated as > well. depmod normally does this automatically, but if the modules are > missing it won't. > > |
From: Dave H. <dhy...@gm...> - 2006-12-01 00:45:40
|
Hi Polychronis, > I have encountered the same problem. I didn't want to delete > buildroot_arm_nofpu because I just built a new kernel in there and > that's what I wanted to test. If you do the steps: cd gumstix-buildroot rm buildarm_nofpu/linux-2.6.18gum/arch/arm/boot/compressed/vmlinux make then the kernel will get rebuilt and installed into the rootfs directory properly. I do this all the time. > This is a very good example why things keep going wrong if your "design" > is wrong in the first place! If the drivers source code were open, the > whole system would compile like a breeze. :-) Well, technically that's not the case for this particular problem. The Makefile which installs the cfio.ko and mcf.ko files is open source, so you can fix it. My guess is that whether the modules were available in source form or binary form is completely unrelated to the problem at hand. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: EXT-McGhehey, M. J <Mar...@bo...> - 2006-12-07 01:35:35
|
Even in the latest buildroot (1198) the Marvell driver files are still coming up missing after subsequent kernel builds. -----Original Message----- From: Dave Hylands [mailto:dhy...@gm...]=20 Sent: Thursday, November 30, 2006 4:46 PM To: General mailing list for gumstix users. Subject: Re: [Gumstix-users] Wifi kernel modules disappear (cfio.ko andmcf25.ko) Hi Polychronis, > I have encountered the same problem. I didn't want to delete=20 > buildroot_arm_nofpu because I just built a new kernel in there and=20 > that's what I wanted to test. If you do the steps: cd gumstix-buildroot rm buildarm_nofpu/linux-2.6.18gum/arch/arm/boot/compressed/vmlinux make then the kernel will get rebuilt and installed into the rootfs directory properly. I do this all the time. > This is a very good example why things keep going wrong if your "design" > is wrong in the first place! If the drivers source code were open, the > whole system would compile like a breeze. :-) Well, technically that's not the case for this particular problem. The Makefile which installs the cfio.ko and mcf.ko files is open source, so you can fix it. My guess is that whether the modules were available in source form or binary form is completely unrelated to the problem at hand. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ ------------------------------------------------------------------------ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDE V _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Dave H. <dhy...@gm...> - 2006-12-07 04:07:50
Attachments:
wifistix.mk
|
Hi Mark, On 12/6/06, EXT-McGhehey, Mark J <Mar...@bo...> wrote: > Even in the latest buildroot (1198) the Marvell driver files are still > coming up missing after subsequent kernel builds. OK - I was able to reproduce your problem by doing the following: cd gumstix-buildroot make defconfig make rm buildroot_arm_nofpu/linux-2.6.18gum/arch/arm/boot/compressed/vmlinux make I took a look at the gumstix-buildroot/package/wifistix/wifistix.mk and it's definitely broken. It's trying to do too much in a single step. I've attached a version of wifistix.mk (copy it into gumstix-buildroot/packages/wifistix) which will correct your problem. I also moved the hidden file out of the root directory and into the build directory. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: EXT-McGhehey, M. J <Mar...@bo...> - 2006-12-08 01:54:08
|
Thanks Dave, That worked! Please note, however, that there is a very minor "typo" in the makefile you sent. line 8: CF8385_TARGET_CONF=3D$(BUILD_DIR)/.cf835 -----Original Message----- From: Dave Hylands [mailto:dhy...@gm...]=20 Sent: Wednesday, December 06, 2006 8:08 PM To: General mailing list for gumstix users. Subject: Re: [Gumstix-users] Wifi kernel modules disappear (cfio.koandmcf25.ko) Hi Mark, On 12/6/06, EXT-McGhehey, Mark J <Mar...@bo...> wrote: > Even in the latest buildroot (1198) the Marvell driver files are still > coming up missing after subsequent kernel builds. OK - I was able to reproduce your problem by doing the following: cd gumstix-buildroot make defconfig make rm buildroot_arm_nofpu/linux-2.6.18gum/arch/arm/boot/compressed/vmlinux make I took a look at the gumstix-buildroot/package/wifistix/wifistix.mk and it's definitely broken. It's trying to do too much in a single step. I've attached a version of wifistix.mk (copy it into gumstix-buildroot/packages/wifistix) which will correct your problem. I also moved the hidden file out of the root directory and into the build directory. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |