Thread: RE: [Ndiswrapper-general] Re: Regressions with FC3 and BCM4306
Status: Beta
Brought to you by:
pgiri
From: Benzinger, M. <Mic...@sa...> - 2005-02-07 12:54:23
|
Giri, If you have the rpm installed on your machine or you can build it and install it, there is a utility in there that will allow you to extract the source without installing it. It is called rpm2cpio. You can then use cpio to extract the kernel into a directory and then build the kernel. The configs used by RedHat are in a directory called configs. I would tar and zip this for you but I do not have anyway of getting it to you given its size. Best regards, Mike Benzinger -----Original Message----- From: ndi...@li... [mailto:ndi...@li...] On Behalf Of Giridhar Pemmasani Sent: Monday, February 07, 2005 2:02 AM To: ndi...@li... Subject: [Ndiswrapper-general] Re: Regressions with FC3 and BCM4306 Christopher Beland <beland <at> alum.mit.edu> writes:=20 =20 =20 > I initially installed ndiswrapper-0.12 with kernel-2.6.9-1.681_FC3,=20 > and it worked very well. When kernel-2.6.9-1.724_FC3 came out,=20 =20 Can someone point out where I can get Fedora kernels in tar gzip/bz2 format? I=20 don't use RedHat/Fedora, so no rpms. I will see if I can add yet another kernel to the test setup.=20 =20 Which Windows driver are you using? Driver for Dell Truemobile 1300 seems to=20 work well with BCM4306. Do you get these errors if CONFIG_DEBUG_SPINLOCK is=20 disabled? Do you have SMP enabled? If you submitted file created by=20 "ndiswrapper-buginfo -full", it would've helped.=20 =20 Giri=20 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Ndiswrapper-general mailing list Ndi...@li... https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general |
From: John H. <jc...@th...> - 2005-02-07 13:08:49
|
>Can someone point out where I can get Fedora kernels in tar gzip/bz2 >format? I >don't use RedHat/Fedora, so no rpms. I will see if I can add yet another > >kernel to the test setup. > > I believe that alien can extract files from the rpm. However, merely extracting the files isn't enough -- there are pre- and post- install and uninstall scripts embedded within the RPM. However, I think alien takes care of these as well. jch |
From: Giridhar P. <pg...@ya...> - 2005-02-07 13:04:12
|
Benzinger, Michael <Michael.Benzinger <at> sabre-holdings.com> writes: > the source without installing it. It is called rpm2cpio. You can then > use cpio to extract the kernel into a directory and then build the > kernel. The configs used by RedHat are in a directory called configs. I The problem is not extracting rpm into tgz. Debian, which is what I use, has a utility called 'alien' which can extract rpm in tgz. Unpacking it results in many patches that have to be then applied to kernel sources. The .spec file uses only some of these patches. Unfortunately alien couldn't use .spec file to apply the patches the way rpm would do. Giri |
From: Adrian Irving-B. <wis...@wi...> - 2005-02-07 13:33:06
|
On Mon, Feb 07, 2005 at 01:02:37PM +0000, Giridhar Pemmasani wrote: > The problem is not extracting rpm into tgz. Debian, which is what I > use, has a utility called 'alien' which can extract rpm in tgz. > Unpacking it results in many patches that have to be then applied to > kernel sources. The .spec file uses only some of these patches. > Unfortunately alien couldn't use .spec file to apply the patches the > way rpm would do. You've got the source RPM, not the binary RPMs. Don't know if that's what you intended, but the binary RPM should be prebuilt with none of the spec or patch junk. |
From: Adrian Irving-B. <wis...@wi...> - 2005-02-07 13:35:28
|
On Mon, Feb 07, 2005 at 08:32:57AM -0500, Adrian Irving-Beer wrote: > You've got the source RPM, not the binary RPMs. Oh, but of course, you at least need the kernel headers to compile, not just a binary image. Duh. That's what I get for e-mailing first thing in the morning. Does RedHat have kernel-headers packages to go alongside its compiled kernels like Debian, or not? |
From: John H. <jc...@th...> - 2005-02-07 14:12:20
|
Adrian Irving-Beer wrote: >Does RedHat have kernel-headers packages to go alongside its compiled >kernels like Debian, or not? > > No, at least not any more. The /lib/modules/`uname -r`/build directory contains all the header files and whatnot that you need for building modules. It's certainly enough for building ndiswrapper, vmware and the nvidia stuff. If you want the kernel sources for reference then that's slightly harder. Recently, well, for FC3, Red Hat stopped shipping a kernel-source RPM. This is a built RPM (as opposed to a source RPM) that contains the kernel sourcecode. The recommendation now is that you install the .src.rpm and do an "rpmbuild -bp" to get the source. This is what you have to do if you want a custom kernel rather than a standard one. It's not a huge deal though. jch |
From: Giridhar P. <pg...@ya...> - 2005-02-07 14:20:24
|
--- Adrian Irving-Beer <wis...@wi...> wrote: > > You've got the source RPM, not the binary RPMs. > > Oh, but of course, you at least need the kernel > headers to compile, > not just a binary image. > I thought it was obvious that I wanted kernel sources, not the binary, so that I can compile kernel on my own selecting/deselecting options. Debian's alien can easily handle binary rpm. As I said, the problem was applying the patches in kernel source rpm. Anyway, I wrote a script to handle that and now compiling fedora kernel-2.6.10-1.760_FC3.src.rpm kernel. BTW, I noticed that after applying all the patches and doing 'make menuconfig', I see the option to select 4k/8k stacks. Did fedora start including this option recently? It looks like I applied all the patches that .spec file says. I didn't use .config that .spec file says, though. Fedora users may want to look into 4k/8k stack option with 760 rpm. Giri __________________________________ Do you Yahoo!? Yahoo! Mail - Easier than ever with enhanced search. Learn more. http://info.mail.yahoo.com/mail_250 |
From: John H. <jc...@th...> - 2005-02-07 14:40:28
|
Giridhar Pemmasani wrote: >BTW, I noticed that after applying all the patches and >doing 'make menuconfig', I see the option to select >4k/8k stacks. Did fedora start including this option >recently? It looks like I applied all the patches that >.spec file says. I didn't use .config that .spec file >says, though. Fedora users may want to look into 4k/8k >stack option with 760 rpm. > > Yes, they did. It was in 741 as well (unless I'm mistaken). I still run with the 4k stacks kernel though: I reckon that the advantages when my laptop is under memory pressure outweigh the risks of the broadcomm driver suddenly deciding it wants a large stack frame. I think I missed the original message which is why I assumed you wanted the built kernel -- sorry. You might want to at least take a look at the various config files in the configs directory to see if there are any gotchas. jch |
From: Adrian Irving-B. <wis...@wi...> - 2005-02-07 17:08:55
|
On Mon, Feb 07, 2005 at 06:20:18AM -0800, Giridhar Pemmasani wrote: > I thought it was obvious that I wanted kernel sources, not the > binary, so that I can compile kernel on my own selecting/deselecting > options. Yeah, it *was* obvious. But I had just recently woken up and was being a dork. :) Also, I've been too spoiled with Debian. I just install a kernel- image package, install the matching kernel-headers package, and I can build modules for that kernel as if I had built it myself. Haven't had to configure a kernel in years, let alone build one. > As I said, the problem was applying the patches in kernel source > rpm. Anyway, I wrote a script to handle that and now compiling > fedora kernel-2.6.10-1.760_FC3.src.rpm kernel. Debian's 'rpm' includes 'rpmbuild'. Theoretically, installing a source RPM via 'rpm -i' should put it into something like '/usr/src/redhat', where it can then be built via rpmbuild. This is how it worked back when I used RedHat, at least. I've never tried it in Debian. Presumably you could let rpmbuild do its patching thing and then abort and do the rest yourself. But you seem to have solved this already. |
From: David K. <dmk...@uc...> - 2005-02-07 19:40:07
|
Giri, If there is still interest, I would be happy to extract the sources, apply the patches and put the resulting source tree in a .tgz on a web site. Let me know if there is still interest. Thanks, David On Mon, 2005-02-07 at 13:02 +0000, Giridhar Pemmasani wrote: > Benzinger, Michael <Michael.Benzinger <at> sabre-holdings.com> writes: > > > the source without installing it. It is called rpm2cpio. You can then > > use cpio to extract the kernel into a directory and then build the > > kernel. The configs used by RedHat are in a directory called configs. I > > The problem is not extracting rpm into tgz. Debian, which is what I use, has a > utility called 'alien' which can extract rpm in tgz. Unpacking it results in > many patches that have to be then applied to kernel sources. The .spec file > uses only some of these patches. Unfortunately alien couldn't use .spec file > to apply the patches the way rpm would do. > > Giri > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting > Tool for open source databases. Create drag-&-drop reports. Save time > by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. > Download a FREE copy at http://www.intelliview.com/go/osdn_nl > _______________________________________________ > Ndiswrapper-general mailing list > Ndi...@li... > https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general |
From: Giridhar P. <gi...@lm...> - 2005-02-07 19:54:21
|
On Mon, 07 Feb 2005 11:40:05 -0800, David Kaplan <dmk...@uc...> said: David> If there is still interest, I would be happy to extract the David> sources, apply the patches and put the resulting source David> tree in a .tgz on a web site. Let me know if there is David> still interest. Well, as lot of problems seem to be from Fedora users, I thought I would test ndiswrapper with the hardware I have with a Fedora kernel. This won't be a one-time kernel so uploading it now is not enough. Ideally I would like to test with whatever is latest kernel from Fedora. I am not sure if I can do that though - with limited hardware and time, it is not possible to test for all possible configurations (I already test with plain, PREEMPT, SMP and PREEMPT+SMP of vanilla 2.6 kernel on a single processor x86). Lets see how it goes. As I pointed out before, I managed to write a script that will patch as required by .spec file. -- Giri |
From: David K. <dmk...@uc...> - 2005-02-08 01:39:17
|
On Mon, 2005-02-07 at 14:54 -0500, Giridhar Pemmasani wrote: > On Mon, 07 Feb 2005 11:40:05 -0800, David Kaplan <dmk...@uc...> said: > > David> If there is still interest, I would be happy to extract the > David> sources, apply the patches and put the resulting source > David> tree in a .tgz on a web site. Let me know if there is > David> still interest. > > Well, as lot of problems seem to be from Fedora users, I thought I > would test ndiswrapper with the hardware I have with a Fedora > kernel. This won't be a one-time kernel so uploading it now is not > enough. Ideally I would like to test with whatever is latest kernel > from Fedora. I am not sure if I can do that though - with limited > hardware and time, it is not possible to test for all possible > configurations (I already test with plain, PREEMPT, SMP and > PREEMPT+SMP of vanilla 2.6 kernel on a single processor x86). Lets see > how it goes. As I pointed out before, I managed to write a script that > will patch as required by .spec file. > Well, if you want, I can make each new kernel release available for a while (i.e. not indefinitely, but at least the next few releases). I could also look into automating the steps you need to take to get the redhat kernel. If the rpmbuild tools are installed, it should be a matter of running the setup section of the spec file and that should create a build directory with all the patches applied. As other have mentioned, if the debian rpmbuild tools are working, you should also be able to build the kernel on your system. Cheers, David |