Re: USB-Modem, slusb and kernels later than 2.6.24

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


Hi Antoni, hi Jacquea,

thank you very much. I forgot that depmod thing. This was the best way
to come to the next errors. Please find attached what the syslogd said
and the shell-script I used to activate the modem.

Besides: the modem was powered and is O.K. I know this, because I use it
on another machine with SuSe 10.2.

Regards

Bernd

Jacques Goldberg schrieb:
>
> On 05/20/2011 04:56 PM, Antonio Olivares wrote:
>
>> Bernd,
>>
>> On Fri, May 20, 2011 at 7:13 AM, Bernd Weber<weber.bernd@xxxxxxxx> 
>> wrote:
>>> Hi Antonio,
>>>
>>> thank you for the link. The slusb.ko is compiled now. But a "make
>>> install" only installs the slamr.ko into the
>>> /lib/modules/kernel/extra-directory. Even when I copy the module
>>> manually, modprobe doesen't find the module:
>>> modprobe slusb
>>>
>>> Do you have any ideas?
>> run
> >>>>>> of course with the modem connected and powered up, something
> which might have been skipped while fighting with the software...
>> # depmod -a
>> or
>> $ sudo depmod -a
>> then
>> $ sudo modprobe slusb
>> or
>> # modprobe slusb
>>
>> Regards,
>>
>>
>> Antonio
>>> Regards
>>>
>>> Bernd
>>>
>>> Antonio Olivares schrieb:
>>>> Bernd,
>>>>
>>>> Please check the following pages out:
>>>>
>>>> http://www.mail-archive.com/debian-bugs-dist@xxxxxxxxxxxxxxxx/msg883918.html
>>>>
>>>>
>>>> http://www.mail-archive.com/debian-bugs-dist@xxxxxxxxxxxxxxxx/msg883985.html
>>>>
>>>>
>>>> http://www.mail-archive.com/debian-bugs-dist@xxxxxxxxxxxxxxxx/msg884183.html
>>>>
>>>>
>>>> Check them out and see if you can get it working on your system?
>>>>
>>>> Regards,
>>>>
>>>> Antonio
>>>>
>>>> On Thu, May 19, 2011 at 3:51 PM, Bernd Weber<weber.bernd@xxxxxxxx> 
>>>> wrote:
>>>>
>>>>> Hi Antonio,
>>>>>
>>>>> thanks a lot. This option carried me a step further - to the next
>>>>> error.
>>>>> Please find enclosed the compilation and the error-log as well.
>>>>> In the tar-ball enclosed are different patch-file. But there is no
>>>>> documentation to what file or files these shold be applied and in
>>>>> which
>>>>> cases.
>>>>>
>>>>> Regards
>>>>>
>>>>> Bernd
>>>>>
>>>>> Antonio Olivares schrieb:
>>>>>
>>>>>> Bernd,
>>>>>>
>>>>>> Try to use a special command make USB=1
>>>>>>
>>>>>> $ sudo make USB=1
>>>>>> or
>>>>>> $ make USB=1
>>>>>> the slusb as well as the slamr driver will be compiled.  Try that
>>>>>> and
>>>>>> report back.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Antonio
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Thu, May 19, 2011 at 10:22 AM, Bernd
>>>>>> Weber<weber.bernd@xxxxxxxx>  wrote:
>>>>>>
>>>>>>
>>>>>>> Jacques,
>>>>>>>
>>>>>>> I am using a 32-bits machine.
>>>>>>>
>>>>>>> the URL:
>>>>>>> http://linmodems.technion.ac.il/packages/smartlink/slmodem-2.9.11-20110321.tar.gz
>>>>>>>
>>>>>>>
>>>>>>> My steps:
>>>>>>>
>>>>>>> tar xzvf slmodem-2.9.11-20110321.tar.gz
>>>>>>>
>>>>>>> make
>>>>>>> make install
>>>>>>>
>>>>>>> And then I learned that slusb.ko wasn't compiled. I couldn't
>>>>>>> find the
>>>>>>> reason. On some pages I got hints that there might be problems with
>>>>>>> kernels later than 2.6.24.
>>>>>>> May be I should have done further configuration efforts for
>>>>>>> slusb. But I
>>>>>>> didn't find hints what I should do. So I have the choice to
>>>>>>> experiment a
>>>>>>> few days or ask questions ;)
>>>>>>>
>>>>>>> Greetings Bernd
>>>>>>>
>>>>>>> Jacques Goldberg schrieb:
>>>>>>>
>>>>>>>
>>>>>>>> Bernd,
>>>>>>>>
>>>>>>>> Please give us the URL of the file which compiled slamr and failed
>>>>>>>> slusb - I just would like to give it a try on my machine
>>>>>>>> (because I had the necessary hardware in my office, I happend
>>>>>>>> to watch
>>>>>>>> Sacha, the author of the drivers, compiling and testing them ,
>>>>>>>> and I
>>>>>>>> am curious to see what fails and where)
>>>>>>>> Also, are you using a 32 bits or a 64 bits machine?
>>>>>>>>
>>>>>>>> Jacques
>>>>>>>>
>>>>>>>> On 05/19/2011 05:50 PM, Bernd Weber wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> the last kernel slusb worked with was 2.6.18.2-34-default,
>>>>>>>>> Suse 10.2
>>>>>>>>> with slmodem-2.9.10.
>>>>>>>>>
>>>>>>>>> I compiled the latest version on SuSe 11.4. But slusb wasn't
>>>>>>>>> compiled,
>>>>>>>>> only slamr. I tediously searched the site of linmodem, but
>>>>>>>>> didn't find
>>>>>>>>> an answer whats to do. SuSe 11.4 comes with kernel 2.6.37
>>>>>>>>>
>>>>>>>>> The Modem in question is a Fujitsu Siemens USB-Modem.
>>>>>>>>> As I said, it works fine with older kernels and older Versions of
>>>>>>>>> slmodem.
>>>>>>>>>
>>>>>>>>> If there is some programming to be done, please let me know.
>>>>>>>>> Though I am
>>>>>>>>> much better in Perl than in C/C++, if necessary I would try to
>>>>>>>>> solve the
>>>>>>>>> problems.
>>>>>>>>>
>>>>>>>>> Could somebody give me a short briefing?
>>>>>>>>>
>>>>>>>>> Greetings
>>>>>>>>>
>>>>>>>>> Bernd
>>>>>>>>>
>>>>>>>>>
>>>>>
>>>
>
>

bernd@LRK:~/src/slmodem-2.9.11-20110321> sudo winmodusb

Running modprobe ungrab-winmodem

DONE

Running modprobe slusb
insmod /lib/modules/2.6.37.1-1.2-default/extra/slusb.ko 
/home/bernd/bin/winmodusb: Zeile 17:  7953 Getötet                modprobe -v slusb

Message from syslogd@LRK at May 20 20:24:29 ...
 kernel:[  441.892465] Oops: 0000 [#1] SMP 

Message from syslogd@LRK at May 20 20:24:29 ...
 kernel:[  441.892472] last sysfs file: /sys/module/usbcore/initstate

Message from syslogd@LRK at May 20 20:24:29 ...
 kernel:[  441.892655] Process modprobe (pid: 7953, ti=ea64a000 task=e54bee30 task.ti=ea64a000)

Message from syslogd@LRK at May 20 20:24:29 ...
 kernel:[  441.892661] Stack:

Message from syslogd@LRK at May 20 20:24:29 ...
 kernel:[  441.892704] Call Trace:

Message from syslogd@LRK at May 20 20:24:29 ...
 kernel:[  441.893068] Code: 28 00 00 00 00 0f 88 9e 03 00 00 8b 44 24 14 03 44 24 18 89 44 24 10 73 12 8b 54 24 14 c7 44 24 10 ff ff ff ff f7 d2 89 54 24 18 <0f> b6 06 8b 5c 24 14 84 c0 74 7c 8d 54 24 24 89 f0 e8 51 ea ff 

Message from syslogd@LRK at May 20 20:24:29 ...
 kernel:[  441.893123] EIP: [<c03f8fc9>] vsnprintf+0x49/0x400 SS:ESP 0068:ea64bd54

Message from syslogd@LRK at May 20 20:24:29 ...
 kernel:[  441.893135] CR2: 0000000000000000

DONE

Making node /dev/slusb0

Running slmodemd -c GERMANY /dev/slusb0 &
bernd@LRK:~/src/slmodem-2.9.11-20110321> error: mdm setup: cannot open dev `/dev/slusb0': No such device or address
error: cannot setup device `/dev/slusb0'

bernd@LRK:~/src/slmodem-2.9.11-20110321> 

#!/bin/bash

# Variables
 A="ungrab_winmodem 6400 0"
 B="slusb 380484 0"

# We do this first so we can ungrab the device from the incorrect module?
 echo -e "\n\rRunning modprobe ungrab-winmodem"
 modprobe ungrab-winmodem

if [ 'lsmod | grep ungrab_winmodem'="$A" ]; then
 sleep 2 && echo -e "\n\rDONE"
 fi

# This is the module we load for the Smart Link winmodem
 echo -e "\n\rRunning modprobe slusb"
modprobe -v slusb
if [ 'lsmod | grep slusb0'="$B" ]; then
 sleep 2 && echo -e "\n\rDONE"
 fi

echo -e "\n\rMaking node /dev/slusb0"
mknod -m 600 /dev/slusb0 c 242 0
# This is the daemon we start for the Smart Link winmodem (notice we send it to the background)
 echo -e "\n\rRunning slmodemd -c GERMANY /dev/slusb0 &"
slmodemd -c GERMANY /dev/slusb0 &

[Linux DVB]     [Asterisk]     [Photo]     [DCCP]     [Netdev]     [Xorg]     [Xfree86]     [Fedora Women]     [Linux USB]

Powered by Linux