One showstopper down..... (10.1)
Damn... gotta find something else to bitch about. I've been complaining about not being able to find a copy of the slamr.ko module which is needed to drive the winmodem in my Thinkpad X30. Never did find one but I found a solution... much better too. Having spent two days on this project and googling at least 20 times for "slamr Suse" and such, I finally came across someone who tried a different approach, and although in what I read he still had a minor problem, I thought I would give it a go. The old solution was to: modprobe slamr slmodemd & where slamr was the module that access the hardware (low-level) and slmodemd is the piece that provides the high-level functions of the modem. The solution (at least for me?) modprobe snd-intel8x0m slmodemd -alsa -c USA hw:1 & which accomplishes the same thing and is used in the same fashion. Works like a charm. And I suspect it might work for winmodems from other vendors too if you first load the appropriate module for that vendors chipset and then run slmodemd. Can't prove that but it seems reasonable. In any event, this is a much better solution than the original. But I still think Novell pulled the plug too soon on a lot of people with similar or other problems with non-gpl code and with no notification of what was going to be happening. I've spent at least 5 full days shooting problems with 10.1. No one can tell me that it is a super, easy thing to install. It's been a lot of dog-work and sleuthing from someone who has 45 years of computing experience and it took far too much work to accomplish. So there..... BLEAH!!!!
Bruce Marshall <bmarsh@bmarsh.com> writes:
The solution (at least for me?)
modprobe snd-intel8x0m slmodemd -alsa -c USA hw:1 &
which accomplishes the same thing and is used in the same fashion. Works like a charm.
And I suspect it might work for winmodems from other vendors too if you first load the appropriate module for that vendors chipset and then run slmodemd. Can't prove that but it seems reasonable.
In any event, this is a much better solution than the original.
Could you write an article for the opensuse wiki, perhaps under SDB?
But I still think Novell pulled the plug too soon on a lot of people with similar or other problems with non-gpl code and with no notification of what was going to be happening.
I've spent at least 5 full days shooting problems with 10.1. No one can tell me that it is a super, easy thing to install. It's been a lot of dog-work and sleuthing from someone who has 45 years of computing experience and it took far too much work to accomplish.
Not good. What else hit you?
So there..... BLEAH!!!!
Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Thursday 01 June 2006 04:12, Andreas Jaeger wrote:
I've spent at least 5 full days shooting problems with 10.1. No one can tell me that it is a super, easy thing to install. It's been a lot of dog-work and sleuthing from someone who has 45 years of computing experience and it took far too much work to accomplish.
Not good. What else hit you?
The fact that the 10.1 setup for an ATI 9600 card would hang my system everytime I switched to graphics (which includes running a Sax2 test). I have a Viewsonic VP201B LCD monitor which needs 1600x1200 to look anywhere decent and I spent two days trying to find the right combination to get into that mode. Never could. I pulled out an xorg.conf file from the install and I could run it in 1280x1024 mode but all of the text looked pretty messy and it was slow. I finally got Sax2 to run in 640x480 mode (while the monitor was in 1280x1024 mode) which made the screen hardly readable... but I was able to trail and error my way into getting Sax to set the 1600x1200 settings (but I didn't test that because I know it wouldn't work) I then used the ATI modules to setup a new xorg.conf file based on the 1600x1200 settings. I now run with the ATI drivers. -- +----------------------------------------------------------------------------+ + Bruce S. Marshall bmarsh@bmarsh.com Bellaire, MI 06/01/06 08:47 + +----------------------------------------------------------------------------+ "Men have many faults, Women only two:" Everything they say, And everything they do!" -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Bruce Marshall wrote:
Damn... gotta find something else to bitch about.
I've been complaining about not being able to find a copy of the slamr.ko module which is needed to drive the winmodem in my Thinkpad X30.
Never did find one but I found a solution... much better too.
Having spent two days on this project and googling at least 20 times for "slamr Suse" and such, I finally came across someone who tried a different approach, and although in what I read he still had a minor problem, I thought I would give it a go.
The old solution was to:
modprobe slamr slmodemd &
where slamr was the module that access the hardware (low-level) and slmodemd is the piece that provides the high-level functions of the modem.
The solution (at least for me?)
modprobe snd-intel8x0m slmodemd -alsa -c USA hw:1 &
which accomplishes the same thing and is used in the same fashion. Works like a charm.
Hi Bruce. I seem to be having problems finding that slmodemd. I can't find it on the 10.1 download CD set nor on the repository. There is also reference to ftp.smlink.com, but that currently doesn't work. Can you point me to where I can find it? Or failing that, email it to me? tnx jk
On Sunday 25 June 2006 20:56, James Knott wrote:
Hi Bruce.
I seem to be having problems finding that slmodemd. I can't find it on the 10.1 download CD set nor on the repository. There is also reference to ftp.smlink.com, but that currently doesn't work. Can you point me to where I can find it? Or failing that, email it to me?
It *is* on the 10.1 distro disks.... Smartlink-softmodem -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (3)
-
Andreas Jaeger -
Bruce Marshall -
James Knott