How does assigning this to an individual that doesn't even have the
hardware to TEST with solve this problem? That's exactly what you did
before and we were presented with "solutions" that wouldn't even
compile.
As I said, people that need fax support have long since left Ubuntu and
won't be retu
** Changed in: sl-modem (Ubuntu)
Assignee: Canonical Foundations Team (canonical-foundations) => أحمد
المحمودي (Ahmed El-Mahmoudy) (aelmahmoudy)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/3751
I asked because NOBODY "working" on the problem was actually qualified
to solve it. I, and every other Linux user who had need of FAX has had
to move to OpenSuSE because Ubuntu simply cannot get it right.
On Tue, 2011-06-14 at 17:44 +, Colin Watson wrote:
> You asked to be unsubscribed. I
You asked to be unsubscribed. I am merely assisting you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/375148
Title:
no more /dev/ttySL0 device node
To manage notifications about this bug go to:
h
Instead of "unsubscribing me", here's a novel idea! Why don't you get
someone actually qualified to support the item and...gasp! actually FIX
the bug??
On Tue, 2011-06-14 at 16:05 +, Colin Watson wrote:
> seasoned_geek, nobody else has the ability to unsubscribe you from this
> bug (save pe
seasoned_geek, nobody else has the ability to unsubscribe you from this
bug (save perhaps a Launchpad admin) but in the right-hand side of the
web interface you will find an interface to unsubscribe yourself if you
so wish.
--
You received this bug notification because you are a member of Ubuntu
Hello,
I have added an apport hook & reportbug script (the latter is for
Debian) in 2.9.11~20100303-5 revision.
--
no more /dev/ttySL0 device node
https://bugs.launchpad.net/bugs/375148
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug persists into Ubuntu 10.04 Lucid, but it seems to have changed
slightly.
When the slusb module is loaded on my computer, I get these lines in my
dmesg:
-- ST7554 USB Modem.
-- usbcore: registered new interface driver ST7554 USB Modem
The /dev/slusb0 device node is created, but it is
You know what?
After watching the exchange on this email, I've decided to migrate to the 64-bit
version of KUbuntu and just give up on Linux ever giving modems the respect they
deserve. I'll have to keep a Windows partition around to send a fax when I
don't feel like paying $2 to that Internet f
** Description changed:
Ever since I updated to Jaunty, I cannot access the Winmodem in my
Thinkpad X24 any longer. This used to work fine in Hardy. I think I
have the necessary packages installed and even upgraded to the PPA
packages from Ahmed, the Debian maintainer. The dkms module i
alright, so I asked my father to plug the machine into the network so
that I can access it via ssh. Updated all packages to the latest
release (I already had the latest sl-modem packages installed). Half a
Gig of downloads later,
nothing has changed!
Why am I not surprised?
Daniel, I'm not bla
>and
> little personal interest in modems although I realise how important they
> are to others)
In general, that is the problem with the Ubuntu community. They have "little
personal interest in modems" and falsely claim to understand how important they
are to others. On Windows, MAC, and many
But, very unprofessionally, released stuff which didn't compile, didn't install,
and had never been tested with fax software.
His frustration level is warranted as this has been a Microsoft quality patch
from day one. When the CD's arrive from On-Disk I will take the time to backup
the 2.5 gig o
We will find out in a while. I just got home from my contract and am waiting
for the new Ubuntu LTS CD's to arrive for an upgrade. I will change out modems
and try it.
On May 3, 2010 at 7:05 AM "أحمد المحمودي (Ahmed El-Mahmoudy)"
wrote:
> Since there was no negative feedback regarding that las
Rolf: I know that you, Ahmed and others have worked together on the
package and that lots of volunteers devote time by testing fixes,
finding more information, etc. and that this time is valuable. I thank
everybody for doing this work. If you know how long I've been involved
in the Ubuntu project a
Daniel, since you asked; you can see in comment #73 that it's certainly
been no longer than six weeks ago that I tried the last time. You may
remember this was just shortly after Ahmed's previous attempt to close
the ticket rather than fixing the problem. Of course, he didn't ask
then, either. S
Daniel, thank you for your comment. But I don't see how can you portray
Ahmed's behaviour as professional.
The people reporting bugs are volunteers, too. And Ahmed has frequently
sucked up their time in this ticket and others by requesting tests and
retests with newly churned out packages when t
Rolf: when was "last I looked"? Can you get a 10.04 LTS Live CD and try
it out with that? "I don't have time everyday for your ping-pong" is an
unreasonable comment to reopen a bug with.
Closing a bug as somebody who has been working on the fix and believing
the issue to be fixed, always implies "
Ahmed, your handling of this issue is starting to become a serious pain
in the neck (to avoid the word "rectum").
Last I looked this was still broken. And I don't have time everyday for
your ping-pong "works for me" and then me "nothing has changed". It
would be nice if you started caring about
Since there was no negative feedback regarding that last fix, I think it
is alright now to consider the bug solved.
** Changed in: sl-modem (Ubuntu)
Status: Confirmed => Fix Released
--
no more /dev/ttySL0 device node
https://bugs.launchpad.net/bugs/375148
You received this bug notificati
It will be quite some time before I get back to where my desktop and the modems
are. I took an out of state project.
I will revisit this once the new LTS version is out and I have returned home.
On March 25, 2010 at 6:24 AM "أحمد المحمودي (Ahmed El-Mahmoudy)"
wrote:
> I tested today on Lucid
I tested today on Lucid beta1 (Live CD) with kernel 2.6.32:
$ cat /proc/version_signature
Ubuntu 2.6.32-16.25-generic
* ALSA (uses snd_atiixp_modem module)
In /etc/default/sl-modem-daemon:
SLMODEMD_DEVICE=modem:1
$ sudo invoke-rc.d sl-modem-daemon start
Starting SmartLink Modem driver for: mode
2.6.31 has had many -NN releases and they are not completely compatible with
each other. If you are using the exact version which released with Karmic
(which was well before -14) you should try your stuff with -20.
On Tuesday 23 March 2010 08:40:28 am أحمد المحمودي (Ahmed El-Mahmoudy) wrote:
>
On Mon, Mar 22, 2010 at 10:58:21PM -, Rolf Leggewie wrote:
> Let's see if we can understand why Ahmed can apparently do some things
> that I still can't. Him running Karmic with an older kernel may be one
> of the reasons.
The machine I tested was running Karmic indeed, but what do you mean b
Then you weren't here when I first really joined into this discussion after
purchasing 6 additional modems spanning multiple vendors and setting aside two
BILLABLE days to assist with the debugging so I could once again fax a few
contracts. That is the two days we got two famous releases, the f
Seasoned_geek, you mention a few of the frustrations that I remember
myself. But to be fair to Ahmed's work, installation or compilation
problems are something I haven't seen for quite a while now. Please
acknowledge the progress being made instead of perpetuating statements
that are no longer tr
>The real question is, what would short-circuit the frustration?
1. Stop sending out releases that don't even compile.
2. Test with fax software before releasing since 70% of the users need their
modem only to send faxes.
--
Roland Hughes, President
Logikal Solutions
(630)-205-1593 (cell)
h
On Mon, Mar 22, 2010 at 08:31:10PM -, Steve Newcomb wrote:
> If all else fails, I *could* do that during my sleeping-hours, when,
> strangely enough, I'm not usually staring at my Lenovo T60. Ahmed, are
> you willing, and, if so, what timezone are you in?
---end quoted text---
Sure, are you
I have an external USB modem, which is bulky but at least it works. An
extra USD $60, and an annoying occupier of scarce space in my backpack.
Too bad I can't use the internal modem in my Lenovo, but at least I'm
not completely cut off when I find myself in some internet backwater.
Which is less a
Can you please all calm down a bit? The tone in this bug report is just
awful and not acceptable at all. Please also note that bug 402874 is not
'fix released' yet, it still needs approval of the release team to go
into lucid.
--
no more /dev/ttySL0 device node
https://bugs.launchpad.net/bugs/375
I gave up begging, it's just never going to work.
On Friday 19 March 2010 06:42:16 am Rolf Leggewie wrote:
> Ahmed, what's that nonsense now? AFAIK, according to your statements
> here, you never successfully reproduced this issue or did you? How can
> you be sure now this issue is fixed? In an
On Fri, Mar 19, 2010 at 11:42:16AM -, Rolf Leggewie wrote:
> Ahmed, what's that nonsense now? AFAIK, according to your statements
> here, you never successfully reproduced this issue or did you? How can
> you be sure now this issue is fixed? In any case, don't you think you
> should at least
Ahmed, what's that nonsense now? AFAIK, according to your statements
here, you never successfully reproduced this issue or did you? How can
you be sure now this issue is fixed? In any case, don't you think you
should at least give the people affected a chance to confirm that the
problem is indee
There is a sync request on LP #402874
--
no more /dev/ttySL0 device node
https://bugs.launchpad.net/bugs/375148
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubunt
This has been fixed on Debian in the 2.9.11~20100303-1 release
** Changed in: sl-modem (Ubuntu)
Status: Confirmed => Fix Committed
--
no more /dev/ttySL0 device node
https://bugs.launchpad.net/bugs/375148
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: sl-modem (Ubuntu)
Assignee: (unassigned) => Canonical Foundations Team
(canonical-foundations)
--
no more /dev/ttySL0 device node
https://bugs.launchpad.net/bugs/375148
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have now recompiled the package from git and as far as I know that
should incorporate all the suggested solutions presented here.
Unfortunately, the status is completely unchanged.
JFTR, I am running karmic (but with a lucid kernel), DKMS compilation
went fine. I get a slamr0 device, but no ttyS
** Changed in: sl-modem (Ubuntu)
Importance: Medium => High
--
no more /dev/ttySL0 device node
https://bugs.launchpad.net/bugs/375148
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
I may be wrong but Karl Daumeier has been able to solve the bug
according to his last message.
--
no more /dev/ttySL0 device node
https://bugs.launchpad.net/bugs/375148
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
On Tuesday 09 February 2010 05:10:34 pm Armando Beneduce wrote:
> Will this bug be solved in Karmic???
>
Not that I have seen. I've even tried switching to an Intel modem, but you
have to run -14 kernel to have that fax software work.
SL modem seemed to be light years from working when I gave u
Will this bug be solved in Karmic???
--
no more /dev/ttySL0 device node
https://bugs.launchpad.net/bugs/375148
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu
Hello,
I have a Toshiba 4600 laptop with a builtin Intel 82801BA/BAM AC'97 Modem
Controller. On this machine I did a fresh install with the latest Ubuntu 9.04.
I ran exactly into the same problems that have already been discribed in this
bug report: The kernel module sources that came with the s
On Wednesday 16 September 2009 02:54:08 am Daniel Holbach wrote:
> seasoned_geek: the way you are talking to Ahmed is unacceptable. It's
> clear to everybody reading this bug report that you are frustrated, but
> venting your anger does not help at all. If you have a look at
> http://www.ubuntu.com
On Wednesday 16 September 2009 02:53:41 am أحمد المحمودي (Ahmed El-Mahmoudy)
wrote:
> On Wed, Sep 16, 2009 at 03:54:51AM -, seasoned_geek wrote:
> > I have been able to remove slmodem via Synaptic in the past.
>
> That was you were able to successfully install sl-modem-source in that
> past.
On Wed, Sep 16, 2009 at 03:54:51AM -, seasoned_geek wrote:
> I have been able to remove slmodem via Synaptic in the past.
That was you were able to successfully install sl-modem-source in that
past. But it seems that there was some update (probably DKMS related)
that made sl-modem-source ins
seasoned_geek: the way you are talking to Ahmed is unacceptable. It's
clear to everybody reading this bug report that you are frustrated, but
venting your anger does not help at all. If you have a look at
http://www.ubuntu.com/community/conduct you will maybe get an idea of
the spirit in how we wor
I have been able to remove slmodem via Synaptic in the past.
It would be a lot easier to follow conversations with you if you would STOP
DELETING all prior messages in the thread.
On Tuesday 15 September 2009 10:26:39 pm أحمد المحمودي (Ahmed El-Mahmoudy)
wrote:
> On Tue, Sep 15, 2009 at 06:15:0
On Tue, Sep 15, 2009 at 06:15:00PM -, seasoned_geek wrote:
> It hasn't bubbled out to the update sites yet.
I think it is: http://packages.ubuntu.com/karmic/sl-modem-source
Yet, as far as I know, without doing that dkms.conf replacement I
mentioned in the previous post, you won't be able nei
It hasn't bubbled out to the update sites yet.
So far I haven't found a single Karmic user with a working sl-modem
install.
On Tuesday 15 September 2009 01:31:07 am أحمد المحمودي (Ahmed El-Mahmoudy)
wrote:
> On Mon, Sep 14, 2009 at 04:25:37PM -, seasoned_geek wrote:
> > Today I had occasion
On Mon, Sep 14, 2009 at 04:25:37PM -, seasoned_geek wrote:
> Today I had occasion to run Synaptic to install some java6 stuff. This was
> the
> error message it displayed when it tried to complete the still uncompleted
> SLMODEM installation.
>
> E: sl-modem-source: subprocess installed po
Today I had occasion to run Synaptic to install some java6 stuff. This was the
error message it displayed when it tried to complete the still uncompleted
SLMODEM installation.
E: sl-modem-source: subprocess installed post-installation script returned
error exit status 3
On Saturday 05 Septem
I suspect the compile failed because there have been over 100 updates sent out
for Karmic between the two compiles.
While the device was created, the driver did not work. No amount of tweaking
got wvdial to get a dial tone, but the phone line was tested with a regular
phone to ensure there was
Actually I don't think there's a reason to test the old version of
sl-modem, since according to Roland's experiment, /dev/ttySL0 did get
created when he used sl-modem version that's in karmic
(2.9.11~20080817-3ubuntu2).
As for the reason why DKMS build failed with him, is that dkms script in
s
Hello,
On Sun, Sep 06, 2009 at 04:36:56AM -, Rolf Leggewie wrote:
> I downgraded to and pinned (otherwise the build process from module-
> assistant automatically updates the package again) version
> 2.9.10+2.9.9d+e-pre2-5ubuntu4~ppa2. Compilation with m-a fails, though.
> Log is attached. P
I downgraded to and pinned (otherwise the build process from module-
assistant automatically updates the package again) version
2.9.10+2.9.9d+e-pre2-5ubuntu4~ppa2. Compilation with m-a fails, though.
Log is attached. Please have a look. Thank you.
** Attachment added: "sl-modem-source.buildlog.
On Saturday 05 September 2009 06:16:31 pm Scott Kitterman wrote:
> I can understand being frustrated, but please try to keep the tone
> professional yourself.
>
That was professional. It was the politest way anyone could have put "not
doing the job you signed up for".
I've spent 20+ years in IT
I can understand being frustrated, but please try to keep the tone
professional yourself.
--
no more /dev/ttySL0 device node
https://bugs.launchpad.net/bugs/375148
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I was told he was the package maintainer. To me, and most of the industry,
that means a certain level of professionalism when it comes to the software
development process. At a minimum, this means two machines. One for
development and one which is regularly wiped and re-installed for testing.
seasoned_geek: Ahmed isn't paid to do this. He's a volunteer doing his
best to help you. Using unprofessional language at him isn't helping
either.
--
no more /dev/ttySL0 device node
https://bugs.launchpad.net/bugs/375148
You received this bug notification because you are a member of Ubuntu
Bug
pdated infos about 1 packages
Getting source for kernel version: 2.6.31-9-generic
Kernel headers available in /usr/src/linux-headers-2.6.31-9-generic
Creating symlink...
apt-get install build-essential
Reading packa
Nothing personal, but I'm really getting sick of this half-arsed stuff.
I removed everything sl-modem on my machine via KPackagekit and
rebooted.
Before install
rol...@logikaldesktop:~$ dpkg -l 'sl-modem*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/
On Saturday 05 September 2009 10:40:46 am أحمد المحمودي (Ahmed El-Mahmoudy)
wrote:
> https://launchpad.net/~aelmahmoudy/+archive/wine
>
2.9 or 2.10?
--
Roland Hughes, President
Logikal Solutions
(630)-205-1593 (cell)
http://www.theminimumyouneedtoknow.com
http://www.infiniteexposure.net
http://
https://launchpad.net/~aelmahmoudy/+archive/wine
--
no more /dev/ttySL0 device node
https://bugs.launchpad.net/bugs/375148
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://
Hello,
I would really appreciate it if you would quit cutting everything out of the
message before responding. I have to reset this test up for you from scratch
each time due to updates via KPackageKit. Each time I have to go find
everything in launchpad.
Please send me the link and name of
If that is the bug where carrier cannot be detected, yes.
I have not tried your new version surviving a reboot though. That was the
other main issue. I would have to hand re-apply though as a bunch of updates
came down and I forgot to flag SL-MODEM as a non-update.
My original problem was I g
Hello,
On Thu, Sep 03, 2009 at 05:47:09PM -, seasoned_geek wrote:
> ttySL0<*1>: Modem Identifier: ATI -- SmartLink Soft Modem
>
> Found a modem on /dev/ttySL0.
---end quoted text---
Please send me the output of: dpkg -l 'sl-modem*'
--
أحمد المحمودي (Ahmed El-Mahmoudy)
Dig
On Fri, Sep 04, 2009 at 04:11:16PM -, seasoned_geek wrote:
> It is still going to be up to a package maintainer to fix.
>
> I have about 6 different modems here, but sl-modem simply isn't working
> correctly
---end quoted text---
I've been looking at this bug history, seems that your problem
It is still going to be up to a package maintainer to fix.
I have about 6 different modems here, but sl-modem simply isn't working
correctly
On Friday 04 September 2009 09:37:44 am أحمد المحمودي (Ahmed El-Mahmoudy)
wrote:
> On Thu, Sep 03, 2009 at 09:04:19PM -, seasoned_geek wrote:
> > -->
On Thu, Sep 03, 2009 at 09:04:19PM -, seasoned_geek wrote:
> --> Modem initialized.
> --> Sending: ATDTw16302051593
> --> Waiting for carrier.
> ATDTw16302051593
> NO CARRIER
rol...@logikaldesktop:~$
rol...@logikaldesktop:~$ sudo SciTE /etc/wvdial.conf
rol...@logikaldesktop:~$
rol...@logikaldesktop:~$
rol...@logikaldesktop:~$ wvdial
--> WvDial: Internet dialer version 1.60
--> Cannot ge
On Thu, Sep 03, 2009 at 05:47:09PM -, seasoned_geek wrote:
> Setting up sl-modem-source (2.9.11~20080817-3ubuntu2) ...
You were supposed to be trying version
2.9.10+2.9.9d+e-pre2-5ubuntu4~ppa2 not 2.9.11~20080817-3ubuntu2.
Probably sl-modem-source get updated when you've done an apt-get upgr
rol...@logikaldesktop:~$ cd /usr/src/modules/sl-modem
rol...@logikaldesktop:/usr/src/modules/sl-modem$ dir
debian drivers modem patches ungrab-winmodem
rol...@logikaldesktop:/usr/src/modules/sl-modem$ sudo module-assistant auto-
install sl-modem-source
[sudo] password for roland:
Could you rather try:
sudo module-assistant auto-install sl-modem-source
Please make sure that linux-headers-generic is installed.
--
أحمد المحمودي (Ahmed El-Mahmoudy)
Digital design engineer
GPG KeyID: 0xEDDDA1B7 (@ subkeys.pgp.net)
GPG Fingerprint: 8206 A196 2084 7E6D 0DF8 B176 BC19 6A
First attempt:
rol...@logikaldesktop:~$ cd /usr/src
rol...@logikaldesktop:/usr/src$ sudo tar jxvf sl-modem.tar.bz2
[sudo] password for roland:
tar: Record size = 8 blocks
modules/
Now you will have to wait for the 200+ updates which are currently applying.
Once they are done and I reboot, I'll have to back out the sl-modem stuff
again, then install your version, then do the build.
On Tuesday 01 September 2009 08:30:43 am أحمد المحمودي (Ahmed El-Mahmoudy)
wrote:
> On Tue
On Tue, Sep 01, 2009 at 12:24:14PM -, seasoned_geek wrote:
> Do I need to do a build then, or just install the source package?
---end quoted text---
After install sl-modem-source package, you'll then need to build
following the instructions in
/usr/share/doc/sl-modem-source/README.Debian
--
Do I need to do a build then, or just install the source package?
On Tuesday 01 September 2009 12:53:52 am أحمد المحمودي (Ahmed El-Mahmoudy)
wrote:
> On Mon, Aug 31, 2009 at 04:33:14PM -, seasoned_geek wrote:
> > pn sl-modem-source (no
> > description ava
On Mon, Aug 31, 2009 at 04:33:14PM -, seasoned_geek wrote:
> pn sl-modem-source (no description
> available)
You'll need to install the sl-modem-source package if you want a
/dev/ttySL0 device node. The package is also available on the PPA.
> SLMODEMD_DE
rol...@logikaldesktop:~$ dpkg -l 'sl-modem*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
uppercase=bad)
||/ Name Version
On Mon, Aug 31, 2009 at 01:23:28PM -, seasoned_geek wrote:
> I used Kpackagekit to manually un-install all things sl-modem. I downloaded
> your .deb and clicked on it to install. The package installed. I have no
> /dev/ttySL0 device.
>
> If we were supposed to do something different for t
I used Kpackagekit to manually un-install all things sl-modem. I downloaded
your .deb and clicked on it to install. The package installed. I have no
/dev/ttySL0 device.
If we were supposed to do something different for the installation you should
have sent that in the message.
On Monday 31
Ok, I need to understand wether the problem is from new upstream or is
it caused by a change in the kernel version, so I am uploading the last
working version of sl-modem (2.9.10+2.9.9d+e-pre2-5ubuntu4) to my PPA,
but built for karmic.
https://launchpad.net/~aelmahmoudy/+archive/wine
So can yo
I gave this another shot. But essentially, other than the package
actually installing there is 0 progress, no matter the fiddling.
The original description in comment 0 still pretty much sums up the
currrent state of affairs.
--
no more /dev/ttySL0 device node
https://bugs.launchpad.net/bugs/37
On Tuesday 18 August 2009 11:19:46 am أحمد المحمودي (Ahmed El-Mahmoudy) wrote:
> On Thu, Aug 13, 2009 at 02:18:39AM -, seasoned_geek wrote:
> > This appears to be busted pretty bad in Karmic Koala.
> >
> > I followed the instructions from here. I had both a /dev/ttySL0 and
> > /dev/modem. wvd
On Thu, Aug 13, 2009 at 02:18:39AM -, seasoned_geek wrote:
> This appears to be busted pretty bad in Karmic Koala.
>
> I followed the instructions from here. I had both a /dev/ttySL0 and
> /dev/modem. wvdial was able to communicate with modem, but was always
> getting NO CARRIER which I now
This appears to be busted pretty bad in Karmic Koala.
I followed the instructions from here. I had both a /dev/ttySL0 and
/dev/modem. wvdial was able to communicate with modem, but was always
getting NO CARRIER which I now see is bug 237773. Since I was stupid
and didn't check for that bug befo
On Fri, Jun 26, 2009 at 07:00:08AM -, Rolf Leggewie wrote:
> Try "aptitude reinstall sl-modem-source" and tell me that works for you.
---end quoted text---
$ sudo aptitude reinstall sl-modem-source
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading
Try "aptitude reinstall sl-modem-source" and tell me that works for you.
--
no more /dev/ttySL0 device node
https://bugs.launchpad.net/bugs/375148
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
On Fri, Jun 26, 2009 at 06:21:05AM -, Rolf Leggewie wrote:
> The package is broken beyond hope and I don't feel like fixing it. It
> won't even install or properly reinstall. Please fix and test your
> packages. Feel free to contact me again when you have something that at
> least has a chan
The package is broken beyond hope and I don't feel like fixing it. It
won't even install or properly reinstall. Please fix and test your
packages. Feel free to contact me again when you have something that at
least has a chance of working.
--
no more /dev/ttySL0 device node
https://bugs.launch
removing and then reinstalling the package gave another (non-fatal)
error. Apparently, it expects the sources somewhere under /lib/modules
while they are under /usr/src, I believe.
--
no more /dev/ttySL0 device node
https://bugs.launchpad.net/bugs/375148
You received this bug notification becaus
Hi Ahmed,
thank you for the packages. Do you actually test before shipping them?
sudo dpkg -i sl-modem-*deb
[...]
Setting up sl-modem-source (2.9.11~20090222-1~jaunty1) ...
Adding Module to DKMS build system
Error! DKMS tree already contains: sl-modem-2.9.11~20090222
You cannot add the same mod
Please try the package in my PPA:
https://launchpad.net/~aelmahmoudy/+archive/ppa/+sourcepub/659030/+listing-archive-extra
--
أحمد المحمودي (Ahmed El-Mahmoudy)
Digital design engineer
GPG KeyID: 0xEDDDA1B7 (@ subkeys.pgp.net)
GPG Fingerprint: 8206 A196 2084 7E6D 0DF8 B176 BC19 6A94 EDDD A1
I am also facing the same issue. After adding sl-modem.conf file,
supplied by Darik Horn has solved my problem. i have PCI SM56 Motorola
chip-set base modem.
@ Darik Horn:
I think udev rule will solve the problem for USB base modem. But what about PCI
base modem?
--
KERNEL=="slusb[0-9]*", GROU
Try blacklisting those modules:
snd_intel_8x0m
snd_via82xx_modem
slamr
--
no more /dev/ttySL0 device node
https://bugs.launchpad.net/bugs/375148
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
If sl-modem was working for you properly in Hardy or Intrepid, then the
easy solution for Jaunty is to restore the modprobe file. (Look for the
file attached to this comment.)
The proper fix is likely a new udev rule.
** Attachment added: "/etc/modprobe.d/sl-modem.conf"
http://launchpadlibrar
This is the change in Jaunty that seems to have broken sl-modem:
https://launchpad.net/ubuntu/+source/sl-modem/2.9.11~20080817-3ubuntu2
--
no more /dev/ttySL0 device node
https://bugs.launchpad.net/bugs/375148
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Ahmed, I get the same as you.
** Changed in: sl-modem (Ubuntu)
Importance: Undecided => Medium
--
no more /dev/ttySL0 device node
https://bugs.launchpad.net/bugs/375148
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I tried it on a laptop that got a smartlink modem, I found that modprobe
slamr give the following in dmesg:
[ 541.027817] slamr: module license 'Smart Link Ltd.' taints kernel.
[ 541.032227] slamr: SmartLink AMRMO modem.
[ 600.955715] modprobe[9918]: segfault at eip 0804aea8 esp bff965
** Changed in: sl-modem (Ubuntu)
Status: New => Confirmed
--
no more /dev/ttySL0 device node
https://bugs.launchpad.net/bugs/375148
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
1 - 100 of 107 matches
Mail list logo
