Re: PCMCIA and 2.0.32 FIXED
There is a bug in the netwave_cs.c source. It is fixed in the patched Debian source, for example in the pcmcia-source package, but it seems that you are using the upstream source. Here is the fix: move the line that reads `#include linux/sched.h' up three lines higher in the file. The sched.h header file needs to be included before the kernel.h header file. I couldn't make this work (I was using 2.9.12 of the upstream source) so I just commented out the netwave_cs.* lines out of the Makefile (because I didn't need support for that) in the modules directory and it compiled properly. There was one other bug when it tried to build cardinfo (it couldn't find forms.h) but changing the #include to absolute path fixed that. Thanks for the help... you all rock :) Adam. Internet Alaska -- 4050 Lake Otis Adam Shand(v) +1 907 562 4638 Anchorage, Alaska Systems Administrator (f) +1 907 562 1677 - http://larry.earthlight.co.nz --- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: PCMCIA and 2.0.32 FIXED
Adam == Adam Shand [EMAIL PROTECTED] writes: Adam There was one other bug when it tried to build cardinfo (it Adam couldn't find forms.h) but changing the #include to absolute Adam path fixed that. Yes. I forgot about that. Of course, cardinfo is an optional part of the PCMCIA Card Services -- its existence is not necessary to use your PCMCIA cards. Brian -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: PCMCIA and 2.0.32
What kind of errors does make/gcc report when you try to compile? Don't forget you need to have APM (Advanced Power Management) and PCI support compiled into your kernel... without them you will get 'unresolved symbol' errors. Okay I've recompiled the kernel for pci and apmd support and still have exactly the same problem. From the beginning when it first reports a problem to the end is quite long so I have just include the first bit. I checked the pcmcia-howto and there didn't seem to be anything there that related... if anyone can help it would be much appreciated. Thanks, Adam. __ I carries on failing in a similar (but different) mannor for about 90k worth of text file before finally bombing out. snip gcc -MD -O2 -Wall -Wstrict-prototypes -Winline -pipe -D__KERNEL__ -DMODULE -I.. /include -I/usr/src/linux/include -I/usr/src/linux -c netwave_cs.c In file included from /usr/src/linux/include/linux/fs.h:232, from /usr/src/linux/include/linux/tty.h:19, from /usr/src/linux/include/linux/sched.h:26, from netwave_cs.c:45: /usr/src/linux/include/linux/hpfs_fs_i.h:5: parse error before `ino_t' /usr/src/linux/include/linux/hpfs_fs_i.h:5: warning: no semicolon at end of struct or union /usr/src/linux/include/linux/hpfs_fs_i.h:12: parse error before `:' In file included from /usr/src/linux/include/linux/fs.h:234, from /usr/src/linux/include/linux/tty.h:19, from /usr/src/linux/include/linux/sched.h:26, from netwave_cs.c:45: /usr/src/linux/include/linux/umsdos_fs_i.h:65: parse error before `off_t' /usr/src/linux/include/linux/umsdos_fs_i.h:65: warning: no semicolon at end of struct or union snip -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: PCMCIA and 2.0.32
On Sun, Nov 23, 1997 at 08:22:07PM -0900, Adam Shand wrote: What kind of errors does make/gcc report when you try to compile? Don't forget you need to have APM (Advanced Power Management) and PCI support compiled into your kernel... without them you will get 'unresolved symbol' errors. Okay I've recompiled the kernel for pci and apmd support and still have exactly the same problem. From the beginning when it first reports a problem to the end is quite long so I have just include the first bit. I checked the pcmcia-howto and there didn't seem to be anything there that related... if anyone can help it would be much appreciated. gcc -MD -O2 -Wall -Wstrict-prototypes -Winline -pipe -D__KERNEL__ -DMODULE -I.. /include -I/usr/src/linux/include -I/usr/src/linux -c netwave_cs.c In file included from /usr/src/linux/include/linux/fs.h:232, Had the exact same problem. I hope you don't need the netwave_cs module because the only solution I found was to take out netwave_cs.o from one of the Makefiles (do a grep). After that all went OK. Cheers. -- Louis-David Mitterrand http://www.aparima.com [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: PCMCIA and 2.0.32
[EMAIL PROTECTED] (Adam Shand) writes: I'd use the debian package but there isn't one for a kernel newer then 2.0.30 that I could see. Of course not. There would need to be a kernel-image-2.0.32 package against which the PCMCIA modules are compiled. Okay I've recompiled the kernel for PCI and apmd support and still have exactly the same problem. From the beginning when it first reports a problem to the end is quite long so I have just include the first bit. I checked the PCMCIA-HOWTO and there didn't seem to be anything there that related... if anyone can help it would be much appreciated. There is a bug in the netwave_cs.c source. It is fixed in the patched Debian source, for example in the pcmcia-source package, but it seems that you are using the upstream source. Here is the fix: move the line that reads `#include linux/sched.h' up three lines higher in the file. The sched.h header file needs to be included before the kernel.h header file. If you are using the kernel-package package (make-kpg) to build your custom kernel, there is an easier way to rebuild the PCMCIA modules. Place the Debianized PCMCIA sources in a subdirectory of /usr/src/modules, for example the pcmcia-source package places the source in /usr/src/modules/pcmcia-cs. Then once you have configured your kernel with `make config' (or `make menuconfig' or `make xconfig'), run the following from the base of the kernel source tree: make-kpkg --revision name kernel_image make-kpkg --revision name modules_image where name is the revision number of the packages that you are building. I like to use host name.number for name, so that if I am building a kernel customized for a machine name ceres, a 2.0.32 kernel package that I build would first be named ceres.1. If I had to rebuild the kernel (to insert patches) the next package would use ceres.2 as the revision number and so on. These commands will build a new kernel-image*.deb file and a pcmcia-modules*.deb file that will be compatible once installed no matter how you configure the kernel. Brian -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
PCMCIA and 2.0.32
Hi, Has anyone sucessfully managed to compile pcmcia-cs-2.9.12 with 2.0.32? I'm trying to get it to compile on my Thinkpad 755cx and it's dying an ugly death in the middle of 'make all'. I'd use the debian package but there isn't one for a kernel newer then 2.0.30 that I could see. Any and all help much appreciated. Adam. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: PCMCIA and 2.0.32
What kind of errors does make/gcc report when you try to compile? Don't forget you need to have APM (Advanced Power Management) and PCI support compiled into your kernel... without them you will get 'unresolved symbol' errors. Thanks, Dennis -- dpk [EMAIL PROTECTED], Systems/Network | work: 353.4844 Division of Engineering Computing Services | page: 222.5875 On Sat, 22 Nov 1997, Adam Shand wrote: Hi, Has anyone sucessfully managed to compile pcmcia-cs-2.9.12 with 2.0.32? I'm trying to get it to compile on my Thinkpad 755cx and it's dying an ugly death in the middle of 'make all'. I'd use the debian package but there isn't one for a kernel newer then 2.0.30 that I could see. Any and all help much appreciated. Adam. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] . -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
