Re: Slackware and martian

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Alexei,

A code fix is likely required concerning:
sysdep.c: In function `linux_timer_create':
sysdep.c:18: error: `__NR_timer_create' undeclared (first use in this function)
sysdep.c:18: error: (Each undeclared identifier is reported only once
sysdep.c:18: error: for each function it appears in.)
sysdep.c: In function `linux_timer_settime':
sysdep.c:23: error: `__NR_timer_settime' undeclared (first use in this function)

John,
 Thanks for the warning.

MarvS

On 3/21/07, John Pate <johnny@xxxxxxxxxx> wrote:
        First off, as of the date of writing this there is a bug in
Slackware 11 and the `scanModem' script will not run successfully.  I have
made Patrick Volkerding aware of this and he tells me he is working on a
fix.

# ./scanModem

  From http://linmodems.technion.ac.il , get a recent update of scanModem,
  if this copy was not there obtained. There are weekly updates.
  Updated on: 2007_March_15

./scanModem: line 3595: unexpected EOF while looking for matching ``'
./scanModem: line 5311: syntax error: unexpected end of file

        This is a problem with Slackware 11, not the `scanModem' script,
and, unsurprisingly, causes other problems.  Anyone using Slackware 11
beware that bash and sed (at least) do not behave as might reasonably be
expected.  (I feel I should advise that anyone new to Linux and having
problems configuring their computer should not use Slackware 11 until they
are in a position to understand the implications of this problem, or a fix
appears and you have applied it.)

        As at this writing, Slackware 12 will be using the 2.6.18 kernel,
which gives the same results as the 2.6.20.2 kernel compilation effort
listed below.  So, Slackware woes aside, it looks to me like the latest
kernels require changes in martian.  Am I correct, and if so what can be
done about it?

        Given the fixes to ACPI that have made their way into late-model
kernels, I'm not enthusiastic about retrofitting an early model 2.6 kernel
to get the modem to work (and it will still be broken for Slackware 12
which has already in the development tree, I'm assured, fixed the bash and
sed bug) and I'm hoping the martian source can be modified to accommodate
late-model kernels.  Output of a compilation effort below.

Linux emma 2.6.20.2 #10 PREEMPT Wed Mar 21 13:44:20 GMT 2007 i686 pentium4 i386 GNU/Linux

-rw-r--r-- 1 johnny users 270508 2007-03-16 12:11 ../martian-full-20061203.tar.gz

make -C kmodule/ modules
make[1]: Entering directory `/tmp/martian/kmodule'
make -C /lib/modules/2.6.20.2/build M="/tmp/martian/kmodule"  modules
make[2]: Entering directory `/usr/src/linux-2.6.20.2'
   CC [M]  /tmp/martian/kmodule/martian.o
/tmp/martian/kmodule/martian.c: In function `martian_add':
/tmp/martian/kmodule/martian.c:662: warning: passing arg 2 of `request_irq' from incompatible pointer type
   CC [M]  /tmp/martian/kmodule/marsio.o
   CC [M]  /tmp/martian/kmodule/mfifo.o
   LD [M]  /tmp/martian/kmodule/martian_dev.o
   Building modules, stage 2.
   MODPOST 1 modules
   CC      /tmp/martian/kmodule/martian_dev.mod.o
   LD [M]  /tmp/martian/kmodule/martian_dev.ko
make[2]: Leaving directory `/usr/src/linux-2.6.20.2'
make[1]: Leaving directory `/tmp/martian/kmodule'
make -C modem/ all
make[1]: Entering directory `/tmp/martian/modem'
     CC main.o
     CC dumpers.o
     CC log.o
     CC session.o
     CC mport.o
     CC pty.o
     CC sysdep.o
sysdep.c: In function `linux_timer_create':
sysdep.c:18: error: `__NR_timer_create' undeclared (first use in this function)
sysdep.c:18: error: (Each undeclared identifier is reported only once
sysdep.c:18: error: for each function it appears in.)
sysdep.c: In function `linux_timer_settime':
sysdep.c:23: error: `__NR_timer_settime' undeclared (first use in this function)
make[1]: *** [sysdep.o] Error 1
make[1]: Leaving directory `/tmp/martian/modem'
make: *** [all] Error 2

(run as root)

FYI it's running on a Compaq Evo N800c laptop...

00:00.0 Host bridge: Intel Corporation 82845 845 (Brookdale) Chipset Host Bridge (rev 04)
00:01.0 PCI bridge: Intel Corporation 82845 845 (Brookdale) Chipset AGP Bridge (rev 04)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 42)
00:1f.0 ISA bridge: Intel Corporation 82801CAM ISA Bridge (LPC) (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801CAM IDE U100 (rev 02)
00:1f.5 Multimedia audio controller: Intel Corporation 82801CA/CAM AC'97 Audio Controller (rev 02)
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500]
02:04.0 Communication controller: Agere Systems LT WinModem (rev 02)
02:06.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus Controller (rev 02)
02:08.0 Ethernet controller: Intel Corporation 82801CAM (ICH3) PRO/100 VE (LOM) Ethernet Controller (rev 42)
02:0e.0 USB Controller: NEC Corporation USB (rev 41)
02:0e.1 USB Controller: NEC Corporation USB (rev 41)
02:0e.2 USB Controller: NEC Corporation USB 2.0 (rev 02)

        ...meantime I shall continue attempting to configure the IR
sensor.


-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-|message from the cookie daemon|

Doomsday device?  I suppose I could part with one and still be feared.

--
John Pate <johnny@xxxxxxxxxx>
Edinburgh, Scotland (home PC)
Disclaimer: I've probably changed my opinions by the time you read this
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-


[Index of Archives]     [Linux Media Development]     [Asterisk]     [DCCP]     [Netdev]     [X.org]     [Xfree86]     [Fedora Women]     [Linux USB]

  Powered by Linux