Fedora release 8 (Werewolf)

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

 



Fernando, Brazil, Fedora release 8 (Werewolf)  kernel 2.6.23.1-42.fc8
Date: Thu, 8 May 2008 16:48:07 -0200
Message-Id: <20080508184242.M5529@xxxxxxxxxxxxxxxx>
X-Mailer: OpenWebMail 2.52 20060502
X-OriginatingIP: 10.180.1.129 (jfernando)
MIME-Version: 1.0
Content-Type: text/plain;
	charset=iso-8859-1

   Hi guys, as I said I would do, I upgraded to Fedora 8 and at the first try
I was able to connect using the same steps we did on Fedora 7.
   Again, when I rebooted, I lost the port and this time, even doing:

   mknod -m 660 /dev/slamr0 c 242 0 2
   modprobe ungrab-winmodem
   modprobe slamr
   slmodemd -c BRAZIL /dev/slamr0

   I had the following error:   

[root@bunitinhu ~]# slmodemd -c BRAZIL /dev/slamr0
error: mdm setup: cannot open dev `/dev/slamr0': Device or resource busy
error: cannot setup device `/dev/slamr0'

   Even doing all the automation steps given by Antonio and Marvin, I still
have the same problem. What could be that? Next follows the new Modemdata.txt
   Thank you.

 Only plain text email is forwarded by the  Discuss@xxxxxxxxxxxxx List Server,
 as HTML can contain viruses. Use as the email Subject Line:
           YourName, YourCountry Fedora release 8 (Werewolf)
Kernel  kernel 2.6.23.1-42.fc8 
 With this Subject Line cogent experts will be alerted, and useful case names
left in the Archive.
 YourCountry will enable Country specific guidance. Your contry's local Linux
experts
 can be found through: http://www.linux.org/groups/index.html. 
They will know your Country's modem code, which may be essential for dialup
service.
Responses from Discuss@xxxxxxxxxxxxx are sometimes blocked by an Internet
Provider mail filters.
 So in a day, also check the Archived responses at http://www.linmodems.org 
--------------------------  System information ----------------------------
CPU=i686,  Fedora release 8 (Werewolf)
Kernel 
Linux version 2.6.23.1-42.fc8 (kojibuilder@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx)
(gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP Tue Oct 30 13:55:12 EDT
2007
 scanModem update of:  2008_05_01

The slmodemd set symbolic link is /dev/ttySL0 -> /dev/pts/1
 There are no blacklisted modem drivers in /etc/modprobe*  files 
Attached USB devices are:
 ID 0a81:0101 Chesen Electronics Corp. Keyboard

USB modems not recognized
For candidate card in slot 01:03.0, firmware information and bootup
diagnostics are:
 PCI slot	PCI ID		SubsystemID	Name
 ----------	---------	---------	--------------
 01:03.0	1057:3052	1057:3020	Modem: Motorola SM56 Data Fax Modem 

 Modem interrupt assignment and sharing: 
 16:      36581          0   IO-APIC-fasteoi   uhci_hcd:usb4, libata, SL1900
 --- Bootup diagnostics for card in PCI slot 01:03.0 ----
ACPI: PCI Interrupt 0000:01:03.0[A] -> GSI 18 (level, low) -> IRQ 16
0000:01:03.0: ttyS1 at I/O 0xa008 (irq = 16) is a 16450
0000:01:03.0: ttyS2 at I/O 0xa010 (irq = 16) is a 8250
0000:01:03.0: ttyS3 at I/O 0xa018 (irq = 16) is a 16450
Couldn't register serial port 0000:01:03.0: -28
ACPI: PCI interrupt for device 0000:01:03.0 disabled
ACPI: PCI Interrupt 0000:01:03.0[A] -> GSI 18 (level, low) -> IRQ 16

 The PCI slot 01:03.0 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@xxxxxxxxxxxxx
 if help is needed.
 

=== Finished firmware and bootup diagnostics, next deducing cogent software. ===

Predictive diagnostics for card in bus 01:03.0:
	Modem chipset  detected on
CLASS="Class 0703: 1057:3052"
NAME="Modem: Motorola SM56 Data Fax Modem "
PCIDEV=1057:3052
SUBSYS=1057:3020
IRQ=16
IDENT=slamr

 For candidate modem in:  01:03.0
   Class 0703: 1057:3052 Modem: Motorola SM56 Data Fax Modem
      Primary PCI_id  1057:3052
 Support type needed or chipset:	slamr
 

----------------end Softmodem section --------------

 1057:3052 has a Motorola chipset, poorly supported by Motorola itself
 However Zello discovered that drivers written to support Smartlink  modems do
support the 1057:3052 chipset!!
 It sufficed to add 1057:3052 to the list of modem cards recognized by the
Smartlink slamr driver.
 There is a ungrab-winmodem driver used in conjunction with slamr, which must
have 1057:3052
 similarly added. See messages from Zello:
 	http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00846.html
 	http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00848.html
 and Alvaro Aguirre about the ungrab-winmodem fix:
	http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00990.html
 For general guidance on ungrab-winmodem + slamr usage, read the Smartlink.txt

The modem is supported by the Smartlink slamr driver
plus the slmodemd helper utility.  Read the
Smartlink.txt and Modem/YourSystem.txt for follow through guidance.


For 2.6.23.1-42.fc8 compiling drivers is necessary. As of October 2007 the
current packages at
http://linmodems.technion.ac.il/packages/smartlink/  are the
ungrab-winmodem-20070505.tar.gz and slmodem-2.9.11-20080126.tar.gz

Writing Smartlink.txt
============ end Smartlink section =====================

 Completed candidate modem analyses.

 The base of the UDEV device file system is: /dev/.udev

 Versions adequately match for the compiler installed: 4.1.2
             and the compiler used in kernel assembly: 4.1.2


 
 Minimal compiling resources appear complete:
   make utility - /usr/bin/make
   Compiler version 4.1
   linuc_headers base folder /lib/modules/2.6.23.1-42.fc8/build

 However some compilations and executable functions may need additional files,
 in the FileNames.h (so called kernel "h"eaders) collection installed in 
/usr/include/ .
 For martian_modem, additional required packages are libc6-dev (and for
Debian/Ubuntu,  linux-libc-dev). The also required headers of package libc6
are commonly installed by default. When compiling ALSA drivers, the utility
"patch" will also be needed.



If a driver compilation fails, with message including some lack of some
FileName.h (stdio.h for example), then
Some additional kernel-header files need installation to /usr/include. The
minimal additional packages are libc6-dev
and any of its dependents, under Ubuntu linux-libc-dev

If an alternate ethernet connection is available,
$  apt-get update
$  apt-get -s install linux-kernel-devel
will install needed package
For Debian/Ubuntu related distributions, run the following command to display
the needed package list:

Otherwise packages have to be found through http://packages.ubuntu.com
Once downloaded and transferred into a Linux partition,
they can be installed alltogether with:
$ sudo dpkg -i *.deb


Checking pppd properties:
	-r-xr-xr-x 1 root root 312332 2006-12-01 10:54 /usr/sbin/pppd

In case of an "error 17" "serial loopback" problem, see:
    http://linmodems.technion.ac.il/linmodems/archive-sixth/msg02637.html

To enable dialout without Root permission do:
	$ su - root  (not for Ubuntu)
         chmod a+x /usr/sbin/pppd
or under Ubuntu related Linuxes
	 chmod a+x /usr/sbin/pppd

Checking settings of:	/etc/ppp/options
lock
debug
usepeerdns

In case of a message like:
   Warning: Could not modify /etc/ppp/pap-secrets: Permission denied
see http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.html

Read Modem/YourSystem.txt concerning other COMM channels: virbr0
Which can interfere with Browser naviagation.

 Don't worry about the following, it is for the experts
 should trouble shooting be necessary.
==========================================================

 Checking for modem support lines:
 --------------------------------------
     /device/modem symbolic link:   
slmodemd created symbolic link /dev/ttySL0:  lrwxrwxrwx 1 root root 10
2008-05-08 06:43 /dev/ttySL0 -> /dev/pts/1
     Within /etc/udev/ files:
/etc/udev/rules.d/50-udev-default.rules:KERNEL=="mwave",		NAME="modems/mwave",
GROUP="uucp"
     Within /etc/modprobe.conf files:
/etc/modprobe.conf:install slamr modprobe --ignore-install ungrab-winmodem ; 
modprobe --ignore-install slamr; test -e /dev/slamr0 || (/bin/mknod -m 660
/dev/slamr0 c 242 0 2>/dev/null && chgrp uucp /dev/slamr0)
/etc/modprobe.conf~:install slamr modprobe --ignore-install ungrab-winmodem ;
 modprobe --ignore-install slamr; test -e /dev/slamr0 || (/bin/mknod -m 660
/dev/slamr0 c 242 0 2>/dev/null && chgrp uucp /dev/slamr0)
     Within any ancient /etc/devfs files:

     Within ancient kernel 2.4.n /etc/module.conf files:

--------- end modem support lines --------


José Fernando de Jesus
Physics Graduated
PhD Student on Cosmology (IAG-USP)
Rua do Matão 1226 
Cidade Universitária 
05508-900  São Paulo  SP 
Brasil 

Phone: 55 11 30912732
email: jfernando@xxxxxxxxxxxxxxxx 
(:¿©2007©?:)
Rock'n'Roll!


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

  Powered by Linux