What is confusing my Intel536ep?

bobzilla · 11-24-2005, 07:28 PM

I have a problem with installing the driver for 536ep.

Ok. I have 2.6.8-2-686 kernel and appropriate 2.6.8-2-686 kernel headers already installed. I successfully compiled the driver by making (of course I didn't write the comments to the command line, this is only for easier understanding):

Code:

make clean #get rid of any previous builds
make 536 #actually compiling

And then I tried to ways of installing. The first was something like this:

Code:

mkdir /lib/modules/2.6.8-2-686/536 #making a directory for the driver
mv ./Intel536.ko /lib/modules/2.6.8-2-686/536 #moving compiled driver to the new folder
modconf #inserting the driver to the kernel

I just noticed it didn't work... Really didn't check dmesg for any kernel messages about that. I thought maybie it's better to try something different first... I again ran:

Code:

make clean #get rid of any previous builds
make 536 #actually compiling

But after that I modified Intel installation script Intel536_inst

I added one more element to the if/else block that checks for the distro:

Code:

elif [ -a /etc/debian_version ]; then
{
   if [ -a ./hamregistry.bin ]; then
   {  
      mv -f /etc/hamregistry.bin /etc/hamregistry.bak
      cp ./hamregistry.bin /etc/haregistry.bin
   }
   else
   {
      rm -f /etc/hamregistry.bin
   }
   fi
   echo installing hamregistry, used for persistant storage
   install -o root -g root -m 110 hamregistry /usr/sbin
   echo installing Intel536 driver
case $KERNVER in
   2.4*)
      install -o root -g root -m 664 Intel536.o ${CharModDir}/Intel536.o || exit 1
      ;;
   2.6*)
      install -o root -g root -m 664 Intel536.ko ${CharModDir}/Intel536.ko || exit 1
      ;;
esac

   echo debian hamboot rc2.d, rc3.d and rc5.d scripts
   install -o root -g root -m 110 Intel536_boot /etc/init.d
   ln -s -f /etc/init.d/Intel536_boot /etc/rc2.d/S99_Intel536
   ln -s -f /etc/init.d/Intel536_boot /etc/rc3.d/S99_Intel536
   ln -s -f /etc/init.d/Intel536_boot /etc/rc5.d/S99_Intel536
}

Then I did:

Code:

make install

It installed the boot script.

I checked the boot script in the text editor.. It seemed Ok to me, so I didn't change anything.

I rebooted and after it started minicom (the boot script automaticaly creates symlink /dev/modem that points to /dev/536ep).

It saw the modem but couldn't initialize it. I tried typing

Code:

atz #reset modem
ate1 #echo on
atz #reset modem

If the modem is correctly initialized it would print 'OK'. But it didn't. Minicom's screen was blank. I checked the settings and tried using /dev/536ep directly. It didn't work. Then I remembered to check dmesg for any kernel messages about succes or failure of inserting the driver module. This is the output:

Code:

*****************open entry*******************
ACPI: PCI interrupt 0000:02:0a.0[A] -> GSI 22 (level, low) -> IRQ 209
open: clm_configure CALL
open: UART_init CALL
open: dspdrv_clear_dsp_interrupt CALL
open: dspdrv_SetCramISRCallBack CALL
open: request_irq CALL
open: clm_initialize CALL
IRN 55 = b5
SRL a1 = b5
LIT f7 = b5
LAT f8 = b5
CRO fa = b5
BUL 1b = b5
GUF e1 = b5
ZAF 9f = b5
CZE 2e = b5
EGY 36 = b5
POL 8a = b5
GIB 45 = b5
GMB 41 = b5
SLV 37 = b5
DOM 33 = b5
CRI 2b = b5
CAN 20 = b5
SVK fb = b5
ARE b3 = b5
SVN fc = b5
HUN 51 = b5
EST f9 = b5
GUY 4d = b5
ZWE c4 = b5
VEN bb = b5
URY b7 = b5
TTO ac = b5
SUR a3 = b5
PRI 8c = b5
PRY 87 = b5
NIC 7f = b5
JAM 5b = b5
HND 4f = b5
HTI 4e = b5
GTM 49 = b5
BMU 12 = b5
BRB e = b5
BHS b = b5
IDN 54 = b5
PHL 89 = b5
IND 53 = b5
TWN fe = b5
MEX 73 = b5
BRA 16 = b5
ARG 7 = b5
NZL 7e = b5
SGP 9c = b5
HKG 50 = b5
CHN 26 = b5
MYS 6c = b5
AUS 9 = b5
RUS b8 = b5
JPN 0 = b5
PAK 84 = b5
PRT 8b = b5
FRA 3d = b5
BEL f = b5
GBR b4 = b5
NLD 7b = b5
LUX 69 = b5
ITA 59 = b5
GRC 46 = b5
CYP 2d = b5
CHE a6 = b5
AUT a = b5
DEU 4 = b5
TUR ae = b5
ESP a0 = b5
LIE 68 = b5
ISR 58 = b5
IRL 57 = b5
ISL 52 = b5
NOR 82 = b5
FIN 3c = b5
DEN 31 = b5
SWE a5 = b5
VNM bc = b5
THA a9 = b5
SAU 98 = b5
PER 88 = b5
PAN 85 = b5
COL 27 = b5
CHL 25 = b5
BOL 14 = b5
ECU 35 = b5
KOR 61 = b5
USA b5 = b5
found
HaM: Read_ProductStrings
exec linux persist
ham ELP: switch 6
ham: ELP timed out waiting for app to read pkt
ham ELP: end
Read_EEPROM
exec linux persist
ham ELP: switch 2
ham: ELP no app
ham ELP: end
Read_EEPROM error
HaM: Read_CountryList
HaM Read_CurrentCountry
exec linux persist
ham ELP: switch 4
ham: ELP no app
ham ELP: end
Failed to read Current Country
*****************open exit*********************
Read_EEPROM
exec linux persist
ham ELP: switch 2
ham: ELP no app
ham ELP: end
Read_EEPROM error
HaM: Read_ProductStrings
exec linux persist
ham ELP: switch 6
ham: ELP no app
ham ELP: end
HaM: Read_CountryList
HaM Read_CurrentCountry
exec linux persist
ham ELP: switch 4
ham: ELP no app
ham ELP: end
Failed to read Current Country
HaM: ReadHookFlashMethod
exec linux persist
ham ELP: switch 9
ham: ELP no app
ham ELP: end
HaM: ReadQuickConnectData
exec linux persist
ham ELP: switch 7
ham: ELP no app
ham ELP: end
modem_write_data
eeprom size ok
modem_write_data
eeprom size ok
eeprom has changed  copying and writing
write_EEPROM
exec linux persist
ham ELP: switch 3
ham: ELP no app
ham ELP: end
modem_write_data
eeprom size ok
eeprom has changed  copying and writing
write_EEPROM
exec linux persist
ham ELP: switch 3
ham: ELP no app
ham ELP: end
modem_write_data
eeprom size ok
eeprom has changed  copying and writing
write_EEPROM
exec linux persist
ham ELP: switch 3
ham: ELP no app
ham ELP: end
modem_write_data
eeprom size ok
eeprom has changed  copying and writing
write_EEPROM
exec linux persist
ham ELP: switch 3
ham: ELP no app
ham ELP: end
modem_write_data
eeprom size ok
eeprom has changed  copying and writing
write_EEPROM
exec linux persist
ham ELP: switch 3
ham: ELP no app
ham ELP: end
modem_write_data
eeprom size ok
eeprom has changed  copying and writing
write_EEPROM
exec linux persist
ham ELP: switch 3
ham: ELP no app
ham ELP: end
modem_write_data
eeprom size ok
eeprom has changed  copying and writing
write_EEPROM
exec linux persist
ham ELP: switch 3
ham: ELP no app
ham ELP: end
modem_write_data
eeprom size ok
eeprom has changed  copying and writing
write_EEPROM
exec linux persist
ham ELP: switch 3
ham: ELP no app
ham ELP: end
modem_write_data
eeprom size ok
eeprom has changed  copying and writing
write_EEPROM
exec linux persist
ham ELP: switch 3
ham: ELP no app
ham ELP: end
modem_write_data
eeprom size ok
eeprom has changed  copying and writing
write_EEPROM
exec linux persist
ham ELP: switch 3
ham: ELP no app
ham ELP: end
modem_write_data
eeprom size ok
eeprom has changed  copying and writing
write_EEPROM
exec linux persist
ham ELP: switch 3
ham: ELP no app
ham ELP: end
modem_write_data
eeprom size ok
eeprom has changed  copying and writing
write_EEPROM
exec linux persist
ham ELP: switch 3
ham: ELP no app
ham ELP: end
modem_write_data
eeprom size ok
eeprom has changed  copying and writing
write_EEPROM
exec linux persist
ham ELP: switch 3
ham: ELP no app
ham ELP: end
modem_write_data
eeprom size ok
eeprom has changed  copying and writing
write_EEPROM
exec linux persist
ham ELP: switch 3
ham: ELP no app
ham ELP: end
modem_write_data
eeprom size ok
eeprom has changed  copying and writing
write_EEPROM
exec linux persist
ham ELP: switch 3
ham: ELP no app
ham ELP: end
modem_write_data
eeprom size ok
eeprom has changed  copying and writing
write_EEPROM
exec linux persist
ham ELP: switch 3
ham: ELP no app
ham ELP: end
modem_write_data
eeprom size ok
eeprom has changed  copying and writing
write_EEPROM
exec linux persist
ham ELP: switch 3
ham: ELP no app
ham ELP: end
modem_write_data
eeprom size ok
eeprom has changed  copying and writing
write_EEPROM
exec linux persist
ham ELP: switch 3
ham: ELP no app
ham ELP: end
*****************close entry*******************
*****************close exit ********************

So, the driver is installed but has problem with ham registry (maybe because my country is not on the list of the countries)? I tried setting the ham registry with the tool that came with the modem (hamregistry), but it didn't work. I don't have a clue what to do next...

Any suggestions?

bobzilla · 11-24-2005, 07:34 PM

I forgot to say:

I'm currently using it from Suse (it has the driver already compiled as an RPM). So it doesn't work under Debian.