Sagem Fast 800 E4 with SUSE 10.0

Lord_Grave · 05-13-2007, 06:01 AM

I'm trying to get the Sagem Fast 800 E4 I got from my ISP to work with SUSE 10.0. I have to use the last version of eagle-usb drivers (v2.3.2) because ueagle-atm drivers don't support E4 yet. There is an experimental version called ueagle-atm4 but I can't compile it because it includes a linux source header called mutex.h which I'm missing.

Here's my problem with eagle-usb. The driver compiles and installs correctly. When I start eagleconfig and choose all the options, the last line says:

Loading DSP and Options [Error]

lsusb says:

Bus 001 Device 005: ID 1110:9042 Analog Devices Canada, Ltd (Allied Telesyn)

so I guess the modem is plugged in and recognized.

eaglestat says only: Pre-firmware device.

However, eaglectrl -d says:

Can't find any PRE or POST firmware devices.
Is your device plugged in ?

and eaglectrl -w doesn't sound much better:

wizard mode only supported if you have only 1 device plugged-in.
I currently found 0 plugged device(s)

Finally, eagledial -a gives the following output:

Diagnostic (1.22 2005/03/20) driver eagle-usb 20070513115137
# System Information
Linux linux 2.6.13-15-default #1 Tue Sep 13 14:56:15 UTC 2005 i686 i686 i386 GNU/Linux
other distrib
Linux version 2.6.13-15-default (geeko@buildhost) (gcc version 4.0.2 20050901 (prerelease) (SUSE Linux)) #1 Tue Sep 13 14:56:15 UTC 2005
gcc version 4.0.2 20050901 (prerelease) (SUSE Linux) used : 4.0.2 20050901 (prerelease) (SUSE Linux)
# Dependances
Verify dependances on source by hand (kernel-source...)
drwxr-xr-x 3 root root 80 2005-09-09 18:00 kernel-modules
lrwxrwxrwx 1 root root 15 2007-05-12 19:42 linux -> linux-2.6.13-15
drwxr-xr-x 21 root root 1416 2007-05-13 11:29 linux-2.6.13-15
drwxr-xr-x 3 root root 72 2007-05-12 19:42 linux-2.6.13-15.13
drwxr-xr-x 3 root root 72 2005-09-13 19:46 linux-2.6.13-15-obj
lrwxrwxrwx 1 root root 19 2007-05-12 19:42 linux-obj -> linux-2.6.13-15-obj
# Kernel config : usb modules
ppp_async 10880 0
crc_ccitt 2176 1 ppp_async
ppp_generic 28052 1 ppp_async
slhc 7296 1 ppp_generic
eagle_usb 122276 0
hci_usb 14088 0
bluetooth 45700 6 rfcomm,hidp,l2cap,hci_usb
ehci_hcd 32136 0
uhci_hcd 32016 0
usbcore 112640 5 eagle_usb,hci_usb,ehci_hcd,uhci_hcd
# pci & usb configuration (check for latency, only keep relevant lines about USB)
00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02)
00:01.0 PCI bridge: Intel Corporation 82865G/PE/P PCI to AGP Controller (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2)
00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation: Unknown device 02e0 (rev a2)
02:05.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02)
02:0a.0 Multimedia audio controller: Creative Labs: Unknown device 0005
02:0b.0 Communication controller: Agere Systems LT WinModem (rev 02)
cat: /proc/pci: No such file or directory
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 005: ID 1110:9042 Analog Devices Canada, Ltd (Allied Telesyn)
Bus 001 Device 001: ID 0000:0000
# interruptions' affectation
CPU0
0: 445565 XT-PIC timer
1: 3740 XT-PIC i8042
2: 0 XT-PIC cascade
3: 248 XT-PIC uhci_hcd:usb2
5: 0 XT-PIC uhci_hcd:usb3
7: 1 XT-PIC parport0
8: 2 XT-PIC rtc
9: 1 XT-PIC acpi
10: 45 XT-PIC uhci_hcd:usb1, uhci_hcd:usb4
11: 7150 XT-PIC ehci_hcd:usb5, 164x, eth0
12: 70961 XT-PIC i8042
14: 26267 XT-PIC ide0
15: 3651 XT-PIC ide1
NMI: 0
LOC: 0
ERR: 0
MIS: 0
# disk uses dma ? [ OK ]
# module loaded ? [ OK ]
# modem operational ? [ KO ]
Pre-firmware device
# Config vpi/vci/encapsulation/isp : 8 23 1 (pppoe) AR01
# pppd launched ? [ OK ]
# Service for connection [ OK ]
# /etc/resolv.conf should contain the DNS
nameserver 212.200.214.2
nameserver 212.200.214.17
eth0 Link encap:Ethernet HWaddr 00:15:F2:2D:88:6F
inet6 addr: fe80::215:f2ff:fe2d:886f/64 Scope:Link
UP BROADCAST NOTRAILERS MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 cool.gif TX bytes:0 (0.0 cool.gif
Base address:0xe800 Memory:fbfe0000-fc000000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:87 errors:0 dropped:0 overruns:0 frame:0
TX packets:87 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6513 (6.3 Kb) TX bytes:6513 (6.3 Kb)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 cool.gif TX bytes:0 (0.0 cool.gif

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
# ping IP ? [ KO ]
# test DNS resolution ? [ KO ]

Does anyone have an idea about what's wrong here or at least where I can find mutex.h from linux source so I can give ueagle-atm4 a try. Thanks in advance.

stevthomsen · 05-23-2007, 07:36 PM

I have had to resort to building my own kernel modules and inserting into the kernel for my winmodem to work properly. For the first steps go to:
http://www.linmodems.org/
Stev

Lord_Grave · 05-24-2007, 12:13 PM

Hi, Stev. Winmodem refers to dial-up modems that require Windows drivers to work. I also have a Winmodem and I use Martian driver to make it work in linux. The connection breaks quite often but at least it works. It might be possible to make these modems work with Windows driver and ndiswrapper, but I didn't even try that approach.

My question is about a dsl modem and I have in the meantime managed to install ueagle-usb drivers. It is really easy but the installation guide is really messed up and confusing. Lack of response to my question has discouraged me from posting my own guide but I would be happy to do so if someone needs help a dsl modem based on E4 chipset.