[Karmic] Intel 536EP driver won't compile

Bug #412785 reported by Roland Hughes
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
efax (Ubuntu)
New
Undecided
Unassigned

Bug Description

I sent this off to Linmodem as well, since I couldn't find a contact email for the guy whose been providing the TAR and BZ2 files. Kernel changes with Karmic mean this software no longer compiles.

abc@logikaldesktop:~/downloads/intel-536EP-2.56.76.0$ make clean
cd coredrv; make clean
make[1]: Entering directory `/home/abc/downloads/intel-536EP-2.56.76.0/coredrv'
rm -f *.ko .*.o.cmd *.mod.c .*.ko.cmd *.o *~ core Module.* modules.*
rm -rf .tmp_versions
make[1]: Leaving directory `/home/abc/downloads/intel-536EP-2.56.76.0/coredrv'
rm -f *.o *.ko
abc@logikaldesktop:~/downloads/intel-536EP-2.56.76.0$ make 536
   Module precompile check
   Current running kernel is: 2.6.31-3-generic
   /lib/modules... autoconf.h exists
diff: /boot/vmlinuz.autoconf.h: No such file or directory
   autoconf.h matches running kernel
diff: /boot/vmlinuz.version.h: No such file or directory
   version.h matches running kernel
uname -r|grep "2.6" && \
        cd coredrv && make 536core_26 && \
        cp Intel536.ko .. && cd .. && \
        strip --strip-debug Intel536.ko && \
        exit; \
        ls Intel536.ko >/dev/null 2>&1 || uname -r | grep "2.6" && echo "Failed to build driver" && exit; \
        if [ ]; then \
        cd coredrv; make TARGET=TARGET_SELAH KERNEL_SOURCE_PATH= "PSTN_DEF=-DTARGET_SELAH -DTARGET_LINUX -DLINUX" 536core; \
        else \
        cd coredrv; make TARGET=TARGET_SELAH KERNEL_INCLUDES=/lib/modules/`uname -r`/build/include \
       "PSTN_DEF=-DTARGET_SELAH -DTARGET_LINUX -DLINUX" 536core; \
        fi ; \
        cp Intel536.o .. ; \
        if [ -a /boot/vmlinuz.version.h ]; then \
        cp /boot/vmlinuz.version.h /lib/modules/`uname -r`/build/include/linux/version.h;\
        fi
2.6.31-3-generic
make[1]: Entering directory `/home/abc/downloads/intel-536EP-2.56.76.0/coredrv'
make -C /lib/modules/2.6.31-3-generic/build SUBDIRS=/home/abc/downloads/intel-536EP-2.56.76.0/coredrv modules
make[2]: Entering directory `/usr/src/linux-headers-2.6.31-3-generic'
  CC [M] /home/abc/downloads/intel-536EP-2.56.76.0/coredrv/coredrv.o
/home/abc/downloads/intel-536EP-2.56.76.0/coredrv/coredrv.c: In function ‘create_hamproc’:
/home/abc/downloads/intel-536EP-2.56.76.0/coredrv/coredrv.c:785: error: ‘struct proc_dir_entry’ has no member named ‘owner’
make[3]: *** [/home/abc/downloads/intel-536EP-2.56.76.0/coredrv/coredrv.o] Error 1
make[2]: *** [_module_/home/abc/downloads/intel-536EP-2.56.76.0/coredrv] Error 2
make[2]: Leaving directory `/usr/src/linux-headers-2.6.31-3-generic'
make[1]: *** [536core_26] Error 2
make[1]: Leaving directory `/home/abc/downloads/intel-536EP-2.56.76.0/coredrv'
2.6.31-3-generic
Failed to build driver

I took a look at proc_fs.h and see it now has

struct proc_dir_entry {
 unsigned int low_ino;
 unsigned short namelen;
 const char *name;
 mode_t mode;
 nlink_t nlink;
 uid_t uid;
 gid_t gid;
 loff_t size;

I'm going to power down and try my smartlink modem now.

roland@logikaldesktop:~/downloads/intel-536EP-2.56.76.0$ lsb_release -rd
Description: Ubuntu karmic (development branch)
Release: 9.10

Revision history for this message
Dan Andreșan (danyer) wrote :

Check this: http://groups.google.com/group/ubuntu-modems

deb packages for 536EP were created on 29th of November (3 days ago)

Revision history for this message
Roland Hughes (original-seasoned-geek) wrote : Re: [Bug 412785] Re: [Karmic] Intel 536EP driver won't compile

It took quite a bit of tweaking, but I got wvdial to work with it yesterday.
Will play with efax as time allows.

On Wednesday 02 December 2009 12:33:04 pm Dan Andreșan wrote:
> Check this: http://groups.google.com/group/ubuntu-modems
>
> deb packages for 536EP were created on 29th of November (3 days ago)
>

--
Roland Hughes, President
Logikal Solutions
(630)-205-1593 (cell)
http://www.theminimumyouneedtoknow.com
http://www.infiniteexposure.net
http://www.logikalsolutions.com

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.