FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Ubuntu > Ubuntu User

 
 
LinkBack Thread Tools
 
Old 07-14-2011, 11:37 PM
NoOp
 
Default Agere WinModem 56k on Thinkpad - Working!

On 07/14/2011 04:10 PM, NoOp wrote:
> On 07/14/2011 12:17 PM, sktsee wrote:
> ...
>> By the time it starts everything that martian_modem requires to work
>> should already be running, so the Required/Should values are left blank.
>>
>> Lastly, since you're having to restart the daemon in order to use efax,
>> there could be an issue with efax trying to lock /dev/ttySM0 but can't.
>> Check /var/lock and see if wvdial/gnome-ppp left a stale lock when it
>> closed.
>>
>
> I wonder if the issue is:
>
> $ sudo /etc/init.d/martian status
> martian_modem (PID 2818) is running...
> $ sudo /etc/init.d/martian-modem status
> martian-modem is RUNNING using process id 2143.
>
> martian_modem is running and martian-modem is running. Should they both
> be running at the same time?

Got it sorted out. Renamed /etc/init.d/martian-modem to
martian-modem_back, rebooted and all is working now. Apparently that was
conflicting with /etc/init.d/martian.






--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

Fri Jul 15 03:30:01 2011
Return-path: <dm-devel-bounces@redhat.com>
Envelope-to: tom@linux-archive.org
Delivery-date: Fri, 15 Jul 2011 02:37:54 +0300
Received: from mx4-phx2.redhat.com ([209.132.183.25]:58789)
by s2.java-tips.org with esmtp (Exim 4.69)
(envelope-from <dm-devel-bounces@redhat.com>)
id 1QhVTe-0007wN-Nh
for tom@linux-archive.org; Fri, 15 Jul 2011 02:37:54 +0300
Received: from lists01.pubmisc.prod.ext.phx2.redhat.com (lists01.pubmisc.prod.ext.phx2.redhat.com [10.5.19.33])
by mx4-phx2.redhat.com (8.13.8/8.13.8) with ESMTP id p6ENcFJi010152;
Thu, 14 Jul 2011 19:38:17 -0400
Received: from int-mx02.intmail.prod.int.phx2.redhat.com
(int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12])
by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP
id p6ENcFUt000998 for <dm-devel@listman.util.phx.redhat.com>;
Thu, 14 Jul 2011 19:38:15 -0400
Received: from mx1.redhat.com (ext-mx13.extmail.prod.ext.phx2.redhat.com
[10.5.110.18])
by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP
id p6ENc9d4001787
for <dm-devel@redhat.com>; Thu, 14 Jul 2011 19:38:10 -0400
Received: from ndjsnpf01.ndc.nasa.gov (ndjsnpf01.ndc.nasa.gov [198.117.1.121])
by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p6ENc1k9032103
for <dm-devel@redhat.com>; Thu, 14 Jul 2011 19:38:02 -0400
Received: from ndjsppt04.ndc.nasa.gov (ndjsppt04.ndc.nasa.gov [198.117.1.103])
by ndjsnpf01.ndc.nasa.gov (Postfix) with ESMTP id 65264328001
for <dm-devel@redhat.com>; Thu, 14 Jul 2011 18:38:01 -0500 (CDT)
Received: from ndjshub06.ndc.nasa.gov (ndjshub06.ndc.nasa.gov [198.117.4.165])
by ndjsppt04.ndc.nasa.gov (8.14.4/8.14.4) with ESMTP id
p6ENc0q1014613
for <dm-devel@redhat.com>; Thu, 14 Jul 2011 18:38:00 -0500
Received: from NDJSSCC07.ndc.nasa.gov ([198.117.4.178]) by
ndjshub06.ndc.nasa.gov ([198.117.4.165]) with mapi;
Thu, 14 Jul 2011 18:38:00 -0500
From: "Stamper, Brian P. (ARC-D)[Stinger Ghaffarian Technologies Inc. (SGT
Inc.)]" <brian.p.stamper@nasa.gov>
To: device-mapper development <dm-devel@redhat.com>
Date: Thu, 14 Jul 2011 18:37:57 -0500
Thread-Topic: [dm-devel] Blacklist broken?
Thread-Index: AcxCa+lM+FDqzsDuQeeRAL345Tp7rQADsG+jAAEZCrs=
Message-ID: <CA44CBE5.13C6A%brian.p.stamper@nasa.gov>
In-Reply-To: <CA44C487.13C5F%brian.p.stamper@nasa.gov>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.4.6813, 1.0.211,
0.0.0000
definitions=2011-07-14_09:2011-07-14, 2011-07-14,
1970-01-01 signatures=0
X-RedHat-Spam-Score: -2.298 (HTML_MESSAGE,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD)
X-Scanned-By: MIMEDefang 2.67 on 10.5.11.12
X-Scanned-By: MIMEDefang 2.68 on 10.5.110.18
X-loop: dm-devel@redhat.com
Subject: Re: [dm-devel] Blacklist broken?
X-BeenThere: dm-devel@redhat.com
X-Mailman-Version: 2.1.12
Precedence: junk
Reply-To: device-mapper development <dm-devel@redhat.com>
List-Id: device-mapper development <dm-devel.redhat.com>
List-Unsubscribe: <https://www.redhat.com/mailman/options/dm-devel>,
<mailto:dm-devel-request@redhat.com?subject=unsubscribe>
List-Archive: <https://www.redhat.com/archives/dm-devel>
List-Post: <mailto:dm-devel@redhat.com>
List-Help: <mailto:dm-devel-request@redhat.com?subject=help>
List-Subscribe: <https://www.redhat.com/mailman/listinfo/dm-devel>,
<mailto:dm-devel-request@redhat.com?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============7644162109922331288=="
Sender: dm-devel-bounces@redhat.com
Errors-To: dm-devel-bounces@redhat.com

--===============7644162109922331288==
Content-Language: en
Content-Type: multipart/alternative;
boundary="_000_CA44CBE513C6Abrianpstampernasagov_"

--_000_CA44CBE513C6Abrianpstampernasagov_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Doing a bit more checking, I can't get multipath to let go.

Added this to multipath.conf:
blacklist {
devnode "*"
}

devnode_blacklist {
devnode "*"
wwid 36001ec90ee4ee600105ac65e04e84e61
# wwid 36001e4f02bc746000f60789e05a38474
devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
devnode "^hd[a-z]"
devnode "^cciss!c[0-9]d[0-9]*"
devnode "/dev/sda"
devnode "/dev/sda1"
devnode "/dev/disk/by-uuid/8ed92bb6-0ddb-4fbc-907d-fdf12e5550a3"
}

Yet it just comes back.

[root@bonjovi ~]# multipath -ll
mpath0 (36001ec90ee4ee600105ac65e04e84e61) dm-0 DELL,PERC 6/i
size=3D279G features=3D'0' hwhandler=3D'0' wp=3Drw
`-+- policy=3D'round-robin 0' prio=3D1 status=3Dactive
`- 2:2:0:0 sda 8:0 active ready running

I find this particularly amusing from multipath -v3:

=3D=3D=3D=3D=3D no paths =3D=3D=3D=3D=3D
Jul 14 16:31:50 | params =3D 0 0 1 1 round-robin 0 1 1 8:0 100
Jul 14 16:31:50 | status =3D 2 0 0 0 1 1 A 0 1 0 8:0 A 0
Jul 14 16:31:50 | 8:0: not found in pathvec
Jul 14 16:31:50 | sda: mask =3D 0x1f
Jul 14 16:31:50 | sda: dev_t =3D 8:0
Jul 14 16:31:50 | sda: size =3D 584843264
Jul 14 16:31:50 | sda: subsystem =3D scsi
Jul 14 16:31:50 | sda: vendor =3D DELL
Jul 14 16:31:50 | sda: product =3D PERC 6/i
Jul 14 16:31:50 | sda: rev =3D 1.11
Jul 14 16:31:50 | sda: h:b:t:l =3D 2:2:0:0
Jul 14 16:31:50 | sda: serial =3D 00614ee8045ec65a1000e64eee90ec01
Jul 14 16:31:50 | sda: get_state
Jul 14 16:31:50 | loading /lib64/multipath/libchecktur.so checker
Jul 14 16:31:50 | sda: path checker =3D tur (config file default)
Jul 14 16:31:50 | sda: checker timeout =3D 300000 ms (internal default)
Jul 14 16:31:50 | sda: state =3D running
Jul 14 16:31:50 | sda: state =3D 3
Jul 14 16:31:50 | sda: prio =3D const (config file default)
Jul 14 16:31:50 | sda: const prio =3D 1
Jul 14 16:31:50 | sda: (DELL:PERC 6/i) device node name blacklisted

And:
[root@bonjovi ~]# multipath -v4 | grep sda
Jul 14 16:32:42 | Discover device /sys/block/sda
Jul 14 16:32:42 | sda: device node name blacklisted
Jul 14 16:32:42 | sda: mask =3D 0x1f
Jul 14 16:32:42 | sda: dev_t =3D 8:0
Jul 14 16:32:42 | sda: size =3D 584843264
Jul 14 16:32:42 | sda: subsystem =3D scsi
Jul 14 16:32:42 | sda: vendor =3D DELL
Jul 14 16:32:42 | sda: product =3D PERC 6/i
Jul 14 16:32:42 | sda: rev =3D 1.11
Jul 14 16:32:42 | sda: h:b:t:l =3D 2:2:0:0
Jul 14 16:32:42 | sda: serial =3D 00614ee8045ec65a1000e64eee90ec01
Jul 14 16:32:42 | sda: get_state
Jul 14 16:32:42 | sda: path checker =3D tur (config file default)
Jul 14 16:32:42 | sda: checker timeout =3D 300000 ms (internal default)
Jul 14 16:32:42 | sda: state =3D running
Jul 14 16:32:42 | sda: state =3D 3
Jul 14 16:32:42 | sda: prio =3D const (config file default)
Jul 14 16:32:42 | sda: const prio =3D 1
Jul 14 16:32:42 | sda: (DELL:PERC 6/i) device node name blacklisted

So it's not as if multipath doesn't know that sda should be blacklisted. I=
t just doesn't care.

On 7/14/11 4:06 PM, "Brian Stamper" <brian.p.stamper@nasa.gov> wrote:

I just upgrade an FC13 system to FC15, and now multipath is grabbing the sy=
stem drive before the normal fsck can run, which is causing the machine to =
not boot. I get the message: "Filesystem mounted or opened exclusively by =
another program? " Now, I can simply control-d to continue, but why is mul=
tipath grabbing the drive? I've blacklisted it every way I can, using devn=
ode, using wwid, it simply ignores it and continues to create a path map fo=
r /dev/sda.

device-mapper-1.02.63-3.fc15.x86_64
device-mapper-multipath-0.4.9-15.fc15.x86_64
device-mapper-libs-1.02.63-3.fc15.x86_64

2.6.38.8-35.fc15.x86_64

mpath0 (36001ec90ee4ee600105ac65e04e84e61) dm-0 DELL,PERC 6/i
size=3D279G features=3D'0' hwhandler=3D'0' wp=3Drw
`-+- policy=3D'round-robin 0' prio=3D1 status=3Dactive
`- 2:2:0:0 sda 8:0 active ready running

[root@bonjovi ~]# blkid | grep boot
/dev/sda1: LABEL=3D"/boot" UUID=3D"8ed92bb6-0ddb-4fbc-907d-fdf12e5550a3" TY=
PE=3D"ext3" SEC_TYPE=3D"ext2"
/dev/mapper/mpath0p1: LABEL=3D"/boot" UUID=3D"8ed92bb6-0ddb-4fbc-907d-fdf12=
e5550a3" TYPE=3D"ext3"

>From multipath.conf:

blacklist {
wwid 36001ec90ee4ee600105ac65e04e84e61
devnode "/dev/sda"
devnode "/dev/sda1"
}
devnode_blacklist {
wwid 36001ec90ee4ee600105ac65e04e84e61
devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
devnode "^hd[a-z]"
devnode "^cciss!c[0-9]d[0-9]*"
devnode "sda"
devnode "/dev/sda"
}

I've even tried blacklisting by /disk/by/uuid. What does it take to get mu=
ltipath to quit grabbing this disk?

-brian

--_000_CA44CBE513C6Abrianpstampernasagov_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML>
<HEAD>
<TITLE>Re: [dm-devel] Blacklist broken?</TITLE>
</HEAD>
<BODY>
<FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"><SPAN STYLE=3D'font-size:=
11pt'><BR>
Doing a bit more checking, I can’t get multipath to let go.<BR>
<BR>
Added this to multipath.conf:<BR>
blacklist {<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;de vnode &quot;*&quot;<BR>
}<BR>
<BR>
devnode_blacklist {<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;de vnode &quot;*&quot;<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ww id 36001ec90ee4ee600105ac=
65e04e84e61<BR>
# &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;wwid 36001e4f02bc746000f60789e05a3847=
4<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;de vnode &quot;^(ram|raw|loo=
p|fd|md|dm-|sr|scd|st)[0-9]*&quot;<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;de vnode &quot;^hd[a-z]&quot=
;<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;de vnode &quot;^cciss!c[0-9]=
d[0-9]*&quot;<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;de vnode &quot;/dev/sda&quot=
;<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;de vnode &quot;/dev/sda1&quo=
t;<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;de vnode &quot;/dev/disk/by-=
uuid/8ed92bb6-0ddb-4fbc-907d-fdf12e5550a3&quot;<BR>
}<BR>
<BR>
Yet it just comes back.<BR>
<BR>
[root@bonjovi ~]# multipath -ll<BR>
mpath0 (36001ec90ee4ee600105ac65e04e84e61) dm-0 DELL,PERC 6/i<BR>
size=3D279G features=3D'0' hwhandler=3D'0' wp=3Drw<BR>
`-+- policy=3D'round-robin 0' prio=3D1 status=3Dactive<BR>
&nbsp;&nbsp;`- 2:2:0:0 <B>sda </B>8:0 active ready running<BR>
<BR>
I find this particularly amusing from multipath -v3:<BR>
<BR>
=3D=3D=3D=3D=3D no paths =3D=3D=3D=3D=3D<BR>
Jul 14 16:31:50 | params =3D 0 0 1 1 round-robin 0 1 1 8:0 100 <BR>
Jul 14 16:31:50 | status =3D 2 0 0 0 1 1 A 0 1 0 8:0 A 0 <BR>
Jul 14 16:31:50 | 8:0: not found in pathvec<BR>
Jul 14 16:31:50 | sda: mask =3D 0x1f<BR>
Jul 14 16:31:50 | sda: dev_t =3D 8:0<BR>
Jul 14 16:31:50 | sda: size =3D 584843264<BR>
Jul 14 16:31:50 | sda: subsystem =3D scsi<BR>
Jul 14 16:31:50 | sda: vendor =3D DELL<BR>
Jul 14 16:31:50 | sda: product =3D PERC 6/i<BR>
Jul 14 16:31:50 | sda: rev =3D 1.11<BR>
Jul 14 16:31:50 | sda: h:b:t:l =3D 2:2:0:0<BR>
Jul 14 16:31:50 | sda: serial =3D 00614ee8045ec65a1000e64eee90ec01<BR>
Jul 14 16:31:50 | sda: get_state<BR>
Jul 14 16:31:50 | loading /lib64/multipath/libchecktur.so checker<BR>
Jul 14 16:31:50 | sda: path checker =3D tur (config file default)<BR>
Jul 14 16:31:50 | sda: checker timeout =3D 300000 ms (internal default)<BR>
Jul 14 16:31:50 | sda: state =3D running<BR>
Jul 14 16:31:50 | sda: state =3D 3<BR>
Jul 14 16:31:50 | sda: prio =3D const (config file default)<BR>
Jul 14 16:31:50 | sda: const prio =3D 1<BR>
<B>Jul 14 16:31:50 | sda: (DELL:PERC 6/i) device node name blacklisted<BR>
</B><BR>
And:<BR>
[root@bonjovi ~]# multipath -v4 | grep sda<BR>
Jul 14 16:32:42 | Discover device /sys/block/sda<BR>
<B>Jul 14 16:32:42 | sda: device node name blacklisted<BR>
</B>Jul 14 16:32:42 | sda: mask =3D 0x1f<BR>
Jul 14 16:32:42 | sda: dev_t =3D 8:0<BR>
Jul 14 16:32:42 | sda: size =3D 584843264<BR>
Jul 14 16:32:42 | sda: subsystem =3D scsi<BR>
Jul 14 16:32:42 | sda: vendor =3D DELL<BR>
Jul 14 16:32:42 | sda: product =3D PERC 6/i<BR>
Jul 14 16:32:42 | sda: rev =3D 1.11<BR>
Jul 14 16:32:42 | sda: h:b:t:l =3D 2:2:0:0<BR>
Jul 14 16:32:42 | sda: serial =3D 00614ee8045ec65a1000e64eee90ec01<BR>
Jul 14 16:32:42 | sda: get_state<BR>
Jul 14 16:32:42 | sda: path checker =3D tur (config file default)<BR>
Jul 14 16:32:42 | sda: checker timeout =3D 300000 ms (internal default)<BR>
Jul 14 16:32:42 | sda: state =3D running<BR>
Jul 14 16:32:42 | sda: state =3D 3<BR>
Jul 14 16:32:42 | sda: prio =3D const (config file default)<BR>
Jul 14 16:32:42 | sda: const prio =3D 1<BR>
<B>Jul 14 16:32:42 | sda: (DELL:PERC 6/i) device node name blacklisted<BR>
</B><BR>
So it’s not as if multipath doesn’t know that sda should be bla=
cklisted. &nbsp;It just doesn’t care.<BR>
<BR>
On 7/14/11 4:06 PM, &quot;Brian Stamper&quot; &lt;<a href=3D"brian.p.stampe=
r@nasa.gov">brian.p.stamper@nasa.gov</a>&gt; wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE=3D"Calibri, Verdana, Helvetica, Arial"=
><SPAN STYLE=3D'font-size:11pt'>I just upgrade an FC13 system to FC15, and =
now multipath is grabbing the system drive before the normal fsck can run, =
which is causing the machine to not boot. &nbsp;I get the message: “F=
ilesystem mounted or opened exclusively by another program? “ &nbsp;N=
ow, I can simply control-d to continue, but why is multipath grabbing the d=
rive? &nbsp;I’ve blacklisted it every way I can, using devnode, using=
wwid, it simply ignores it and continues to create a path map for /dev/sda=
.<BR>
<BR>
device-mapper-1.02.63-3.fc15.x86_64<BR>
device-mapper-multipath-0.4.9-15.fc15.x86_64<BR>
device-mapper-libs-1.02.63-3.fc15.x86_64<BR>
<BR>
2.6.38.8-35.fc15.x86_64<BR>
<BR>
mpath0 (36001ec90ee4ee600105ac65e04e84e61) dm-0 DELL,PERC 6/i<BR>
size=3D279G features=3D'0' hwhandler=3D'0' wp=3Drw<BR>
`-+- policy=3D'round-robin 0' prio=3D1 status=3Dactive<BR>
&nbsp;&nbsp;`- 2:2:0:0 &nbsp;sda 8:0 &nbsp;&nbsp;active ready running<BR>
<BR>
[root@bonjovi ~]# blkid | grep boot<BR>
/dev/sda1: LABEL=3D&quot;/boot&quot; UUID=3D&quot;8ed92bb6-0ddb-4fbc-907d-f=
df12e5550a3&quot; TYPE=3D&quot;ext3&quot; SEC_TYPE=3D&quot;ext2&quot; <BR>
/dev/mapper/mpath0p1: LABEL=3D&quot;/boot&quot; UUID=3D&quot;8ed92bb6-0ddb-=
4fbc-907d-fdf12e5550a3&quot; TYPE=3D&quot;ext3&quot; <BR>
<BR>
&gt;From multipath.conf:<BR>
<BR>
blacklist {<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ww id 36001ec90ee4ee600105ac=
65e04e84e61<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;de vnode &quot;/dev/sda&quot=
;<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;de vnode &quot;/dev/sda1&quo=
t;<BR>
}<BR>
devnode_blacklist {<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ww id 36001ec90ee4ee600105ac=
65e04e84e61<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;de vnode &quot;^(ram|raw|loo=
p|fd|md|dm-|sr|scd|st)[0-9]*&quot;<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;de vnode &quot;^hd[a-z]&quot=
;<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;de vnode &quot;^cciss!c[0-9]=
d[0-9]*&quot;<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;de vnode “sda”<B=
R>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;de vnode “/dev/sda&#82=
21;<BR>
}<BR>
<BR>
I’ve even tried blacklisting by /disk/by/uuid. &nbsp;What does it tak=
e to get multipath to quit grabbing this disk?<BR>
<BR>
-brian<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>


--_000_CA44CBE513C6Abrianpstampernasagov_--


--===============7644162109922331288==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
--===============7644162109922331288==--
 
Old 07-16-2011, 01:59 PM
sktsee
 
Default Agere WinModem 56k on Thinkpad - Working!

On 07/14/2011 06:37 PM, NoOp wrote:

On 07/14/2011 04:10 PM, NoOp wrote:

On 07/14/2011 12:17 PM, sktsee wrote:
...

By the time it starts everything that martian_modem requires to work
should already be running, so the Required/Should values are left blank.

Lastly, since you're having to restart the daemon in order to use efax,
there could be an issue with efax trying to lock /dev/ttySM0 but can't.
Check /var/lock and see if wvdial/gnome-ppp left a stale lock when it
closed.



I wonder if the issue is:

$ sudo /etc/init.d/martian status
martian_modem (PID 2818) is running...
$ sudo /etc/init.d/martian-modem status
martian-modem is RUNNING using process id 2143.

martian_modem is running and martian-modem is running. Should they both
be running at the same time?


Got it sorted out. Renamed /etc/init.d/martian-modem to
martian-modem_back, rebooted and all is working now. Apparently that was
conflicting with /etc/init.d/martian.




Yeah, there just needs to be one script launching the martian-modem
daemon, Good to hear you got it sorted out.


--
sktsee



--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
 

Thread Tools




All times are GMT. The time now is 11:46 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org