Hi,

Having installed Ubuntu 7.04 on my Toshiba laptop I am now on the lookout for my modem driver.

Ran Scanmodem utility and it gave me the following information:

------------- System information -----------------

CPU=i686,
Ubuntu 7.04 Linux version 2.6.20-15-generic (root@palmer) (gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4))
#2 SMP Sun Apr 15 07:36:31 UTC 2007

scanModem update of: 2007_August_04

ALSAversion 1.0.13
USB modem not detected by lsusb

Modem or host audio card candidates have firmware information:

PCI slot PCI ID SubsystemID Name
---------- --------- --------- ---------
00:1e.3 8086:266d 1179:0001 Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW


Modem interrupt assignment and sharing:

--- Bootup diagnostics for card in PCI slot 00:1e.3 ----
[ 20.270584] ACPI: PCI Interrupt 0000:00:1e.3 -> GSI 20 (level, low) -> IRQ 18
[ 20.270593] ACPI: PCI interrupt for device 0000:00:1e.3 disabled

The PCI slot 00:1e.3 of the modem card may be disabled early in a bootup process, but then enabled later. If modem drivers load but the modem is not responsive, read Bootup.txt about possible fixes.

Send dmesg.txt along with ModemData.txt to discuss@linmodems.org if help is needed.

=== Finished modem firmware and bootup diagnostics section. ===
=== Next deducing cogent software ===
CodecModemFile not found

I was expecting to see some result after the === Next deducing cogent software === section, but there was none.

The only thing I know is that the modem is Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW.

When I checked the driver details using Windows it said Agere 2.1.51.0 & Toshiba Software Modem.

So... you know what I am looking for? :-) Help of course.

I think the resources you need are here From that site you'll want the file martian-ubuntu-2.6.20-16-generic.tar.gz
You would unpack it with (typing commands in a terminal window): Make sure you have the tools needed to compile the driver installed with: and then Then navigate to the martian directory created when you unpacked the file: then run and Hopefully the drivers will build with no errors and that should get you started. I just went through a similar process to get my PCTel winmodem working. Fortunately for me it worked with no problems. I hope you will be as lucky ! Post back if you have any difficulties.

Hi there,

I sure do hope that it works. But I'd like you to clear a few things for me before I proceed.

Since I am not familiar with Debian, just a doubt. Why're we using Apt over here? Is Ubuntu based on Debian?

Make sure you have the tools needed to compile the driver installed with:

Code:
sudo aptitude install linux-headers-$(uname -r)
(** What does this command do? **)

and then

Code:
sudo aptitude install build-essential
(** And this? **)

In the above emboldened section, am I to execute it as you've typed or do I need to replace some of the words in there with other relevant words?

Yes, Ubuntu is based on Debian and apt is the primary Debian package manager. Execute the commands as typed; don't replace any of the words. In fact you can just copy and paste them into a terminal window.

Let's look at: first. sudo means you will execute the command that follows with root privileges. aptitude install invokes that aptitude package manager for installation. linux-headers is a package containing various files that the compiler will look for when it is building your drivers from source code. (That is what you will be doing; you will be downloading source code for your modem drivers and then compiling it for your kernel) the uname -r part of the command ensures that the header files for the correct running kernel are retrieved. (Try by itself and you will see that it outputs the exact name of your currently running kernel.)

In the command build-essential is an Ubuntu package that depends on the packages commonly needed to build and compile software from source code. Since in Debian apt-get and aptitude automatically retrieve and install dependencies of a package, this command makes sure that you have all the basics required to build software from source code.

You could also use apt-get instead of aptitude in the commands above. The difference in the behaviour appears later if you want to remove any of the packages you installed with either apt-get remove or aptitude remove. Both apt-get install and aptitude install will retrieve both the package you want and all its dependencies; but apt-get remove leaves the dependencies behind when it removes the main package. aptitude remove more cleanly removes both the installed package and any dependencies it installed at the same time. aptitude is also "smart" enough that it won't remove anything you might need without asking you first.

That was just a summary of what the commands do, which should be all you need for the moment. But, yes, it is always wise to check before running any commands or scripts that a stranger recommends that you use. Specific information on the usage of any command may be obtained with replacing <command> with the specific command you are looking up.

Hi there once again,

Following your instruction I downloaded the tar file. But an error was produced while running 'make all'. Trying to redirect the output of the 'make' command as 'make all >> output.txt', the text file captures only the first few lines.

I'd like to display the output in here so that you may know what the possible problem may be.

Hi, sorry for the delay in responding; I have been away for a few days. To redirect both the regular messages and error messages generated try: I think what happened in your use of the shell redirection operator is that only stdout was piped into output.txt; stderr was not. Redirection is specified from right to left. As far as the shell is concerned stdout is called 1 and stderr is called 2. The 2>&1 therefore should mix error messages in with normal output.

Hey there,

I know it's a little harsh to dump the entire error log on you like this, but I wasn't able to decide what to exclude from the 'jargon'.

Here goes:

make -C kmodule/ modules
make[1]: Entering directory `/home/ramesh/martian-ubuntu-2.6.20-16-generic/kmodule'
make -C /lib/modules/2.6.20-15-generic/build M="/home/ramesh/martian-ubuntu-2.6.20-16-generic/kmodule" modules
make[2]: Entering directory `/usr/src/linux-headers-2.6.20-15-generic'
Building modules, stage 2.
MODPOST 1 modules
make[2]: Leaving directory `/usr/src/linux-headers-2.6.20-15-generic'
make[1]: Leaving directory `/home/ramesh/martian-ubuntu-2.6.20-16-generic/kmodule'
make -C modem/ all
make[1]: Entering directory `/home/ramesh/martian-ubuntu-2.6.20-16-generic/modem'
-e CC main.o
main.c:15:19: error: stdio.h: No such file or directory
main.c:17:40: error: sys/mman.h: No such file or directory
main.c:18:36: error: string.h: No such file or directory
main.c:19:23: error: asm/types.h: No such file or directory
In file included from main.c:20:
mixspinlock.h:9: error: expected ‘:’, ‘,’, ‘;’, ‘}’ or ‘__attribute__’ before ‘lock’
mixspinlock.h: In function ‘mspin_lock’:
mixspinlock.h:24: error: ‘mspinlock_t’ has no member named ‘lock’
mixspinlock.h:13: error: invalid lvalue in asm output 0
mixspinlock.h: In function ‘mspin_unlock’:
mixspinlock.h:31: error: ‘mspinlock_t’ has no member named ‘lock’
mixspinlock.h:29: error: invalid lvalue in asm output 0
In file included from main.c:21:
../martian.h: At top level:
../martian.h:39: error: expected specifier-qualifier-list before ‘__u16’
../martian.h:89: error: expected specifier-qualifier-list before ‘__u16’
main.c:23:43: error: signal.h: No such file or directory
main.c:25:30: error: unistd.h: No such file or directory
main.c:26:29: error: stdlib.h: No such file or directory
main.c:28:23: error: sys/types.h: No such file or directory
main.c:30:36: error: ctype.h: No such file or directory
main.c:33:42: error: sched.h: No such file or directory
main.c:35:38: error: stdint.h: No such file or directory
main.c:37:39: error: pwd.h: No such file or directory
main.c:38:17: error: grp.h: No such file or directory
main.c:39:22: error: sys/stat.h: No such file or directory
main.c:42:20: error: getopt.h: No such file or directory
main.c:43:45: error: sys/ioctl.h: No such file or directory
In file included from main.c:45:
sysdep.h:4:18: error: time.h: No such file or directory
In file included from main.c:45:
sysdep.h:6: error: expected specifier-qualifier-list before ‘timer_t’
sysdep.h:10: error: expected ‘)’ before ‘clock’
In file included from log.h:7,
from main.c:50:
common.h:31: error: expected specifier-qualifier-list before ‘uid_t’
main.c: In function ‘check_procfs’:
main.c:76: warning: implicit declaration of function ‘system’
main.c: In function ‘watch_setup’:
main.c:82: error: ‘struct _config’ has no member named ‘haveTSC’
main.c:85: error: ‘NULL’ undeclared (first use in this function)
main.c:85: error: (Each undeclared identifier is reported only once
main.c:85: error: for each function it appears in.)
main.c:92: error: ‘FILE’ undeclared (first use in this function)
main.c:92: error: ‘fp’ undeclared (first use in this function)
main.c:92: warning: implicit declaration of function ‘popen’
main.c:97: warning: implicit declaration of function ‘fgetc’
main.c:97: error: ‘EOF’ undeclared (first use in this function)
main.c:98: warning: implicit declaration of function ‘isdigit’
main.c:99: warning: implicit declaration of function ‘ungetc’
main.c:103: warning: implicit declaration of function ‘fscanf’
main.c:103: warning: incompatible implicit declaration of built-in function ‘fscanf’
main.c:105: warning: implicit declaration of function ‘pclose’
main.c:110: error: ‘struct _config’ has no member named ‘haveTSC’
main.c: In function ‘realtime_setup’:
main.c:120: warning: implicit declaration of function ‘mlockall’
main.c:120: error: ‘MCL_CURRENT’ undeclared (first use in this function)
main.c:121: error: ‘NULL’ undeclared (first use in this function)
main.c:125: error: storage size of ‘p’ isn’t known
main.c:126: warning: implicit declaration of function ‘sched_get_priority_min’
main.c:126: error: ‘SCHED_FIFO’ undeclared (first use in this function)
main.c:132: warning: implicit declaration of function ‘sched_setscheduler’
main.c:138: warning: implicit declaration of function ‘sched_getparam’
main.c:139: warning: implicit declaration of function ‘sched_getscheduler’
main.c:125: warning: unused variable ‘p’
main.c: In function ‘usage’:
main.c:148: warning: implicit declaration of function ‘fprintf’
main.c:148: warning: incompatible implicit declaration of built-in function ‘fprintf’
main.c:148: error: ‘stdout’ undeclared (first use in this function)
main.c:171: warning: implicit declaration of function ‘exit’
main.c:171: warning: incompatible implicit declaration of built-in function ‘exit’
main.c: In function ‘fix_id_to_code’:
main.c:176: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘OldCountryIdToCountryCode’
main.c:176: error: ‘OldCountryIdToCountryCode’ undeclared (first use in this function)
main.c:178: error: expected specifier-qualifier-list before ‘__u16’
main.c:181: warning: excess elements in struct initializer
main.c:181: warning: (near initialization for ‘IdtoCodeFix[0]’)
main.c:181: warning: excess elements in struct initializer
main.c:181: warning: (near initialization for ‘IdtoCodeFix[0]’)
main.c:182: warning: excess elements in struct initializer
main.c:182: warning: (near initialization for ‘IdtoCodeFix[1]’)
main.c:182: warning: excess elements in struct initializer
main.c:182: warning: (near initialization for ‘IdtoCodeFix[1]’)
main.c:183: warning: excess elements in struct initializer
main.c:183: warning: (near initialization for ‘IdtoCodeFix[2]’)
main.c:183: warning: excess elements in struct initializer
main.c:183: warning: (near initialization for ‘IdtoCodeFix[2]’)
main.c:184: warning: excess elements in struct initializer
main.c:184: warning: (near initialization for ‘IdtoCodeFix[3]’)
main.c:184: warning: excess elements in struct initializer
main.c:184: warning: (near initialization for ‘IdtoCodeFix[3]’)
main.c:185: warning: excess elements in struct initializer
main.c:185: warning: (near initialization for ‘IdtoCodeFix[4]’)
main.c:185: warning: excess elements in struct initializer
main.c:185: warning: (near initialization for ‘IdtoCodeFix[4]’)
main.c:186: warning: excess elements in struct initializer
main.c:186: warning: (near initialization for ‘IdtoCodeFix[5]’)
main.c:186: warning: excess elements in struct initializer
main.c:186: warning: (near initialization for ‘IdtoCodeFix[5]’)
main.c:187: warning: excess elements in struct initializer
main.c:187: warning: (near initialization for ‘IdtoCodeFix[6]’)
main.c:187: warning: excess elements in struct initializer
main.c:187: warning: (near initialization for ‘IdtoCodeFix[6]’)
main.c:188: warning: excess elements in struct initializer
main.c:188: warning: (near initialization for ‘IdtoCodeFix[7]’)
main.c:188: warning: excess elements in struct initializer

Hope you'll be able to shed some light on this. And again, hope you're not away again this time ;-) !!!

Yes, I am home this weekend.

Before trying to figure out why you are getting all those errors, I thought I would try to build your driver myself to see if I could duplicate your problem. I ran all of the commands I posted for you except that I didn't run because I didn't actually want to install your driver (and also you will need to run that as root: once your driver compiles); also the actual directory that the tarball unpacked into was "martian-ubuntu-2.6.20-16-generic" not "martian" (I am sure you figured that out). Your driver compiled with no issues for me; the compile produced some warnings, but none of the errors you got.

Then I noticed that I am running the latest Ubuntu Feisty kernel 2.6.20-16 whereas your original post indicates your are running 2.6.20-15. I thought maybe that might be the problem. I tried moving my 2.6.20-16 kernel headers elsewhere, rebooted with my saved 2.6.20-15 kernel, deleted the old "martian-ubuntu-2.6.20-16-generic" directory, unpacked the tarball again, and tried compiling with the 2.6.20-15 kernel headers. Again I got a couple of warnings, but none of the errors in your output; the driver compiled with no issues.

I then tried moving all of my kernel headers elsewhere and compiling your driver. Now, as expected, I got errors but they were still different from the ones you got. I got the following output:
which is logical since the compiler couldn't find any headers. But I still couldn't manage to duplicate your problem.

I would suggest that you either delete your "martian-ubuntu-2.6.20-16-generic" directory, starting fresh, and following the steps in my first post; or you could navigate to that directory (instead of deleting it) and first try before running . If you are successful compiling the driver, then run at the end. You might also want to update your kernel if you haven't done so already, but I don't think the older kernel is what is causing you trouble.

Hey there once again...

Yup, I'm back alright :-). Cleaning the mess up and repeating your instructions did not quite solve the problem.

I think I may have (mis)directed your attention a step further with regards to the error I received. Today while I did the 'build-essential' command, a step before 'make all', I received a message stating that the process was unable to find the 'buil-essential' package/module. I believe it was there the last time I ran it too, but did not quite give it due attention.

Could that be the reason why I got those many errors?

Hoping to hear from you soon pal!

Yes, that could be the problem. What is the exact error message you get for the command:

The following messages came up:

install linux-headers:

Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information... Done
Initializing package status... Done
Building tag database... Done
No packages will be installed, upgraded or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 0B will be used.
Writing extended state information... Done.


build-essential:

Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information... Done
Initializing package status... Done
Building tag database... Done
Couldn't find any packages whose name or description matched "buil-essential"
No packages will be installed, upgraded or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 0B will be used.

It looks to me like you mis-typed the command. Note that the error indicates That is what the error would be if you entered the command as which is incorrect. Just cut and paste:
Also did you use the exact command or did you type something else? The only errors in the command list I made in the original post were that the last command should be instead of (Sorry about that ...) but you will notice that is corrected within my first post; and the directory that unpacks is not but Please remember to type the commands exactly as posted or just cut and paste.

Hi,

It was a typo made in my post and not on the Ubuntu box. I did run the commands as per your instruction, but still came up with those errors.

Now another doubt - could it be because of an incomplete/corrupt installation media? That's all I can think of right now.

Also, what were the outputs you received when the following were run?
sudo aptitude install build-essential
sudo aptitude install linux-headers-$(uname -r)
Are you telling me that you never got the messages I posted?

I get no errors from either of the above commands. But I did get the exact specific error you posted about buil-essential when I deliberately typed the command incorrectly.

While it is possible that you might have incomplete or corrupt installation media, I don't think that is what is causing you difficulty. Let's take a look at the repositories apt is searching for you. Please cut and paste the output of the following command:

The following 6 lines were the entries towards the end of the file you specified:

deb http://security.ubuntu.com/ubuntu feisty-security main restricted
deb-src http://security.ubuntu.com/ubuntu feisty-security main restricted
deb http://security.ubuntu.com/ubuntu feisty-security universe
deb-src http://security.ubuntu.com/ubuntu feisty-security universe
deb http://security.ubuntu.com/ubuntu feisty-security multiverse
deb-src http://security.ubuntu.com/ubuntu feisty-security multiverse

The others did not look relevant to my inexperienced eyes :-). Hope you can come up with some suggestion(s) with the above.