fedora

Installing Huawei ETS1000 on Linux

by

*** Update for Ubuntu 8.10 ***

You will have to copy the driver files to the correct location. Please run the following command.

sudo cp /lib/firmware/$(uname -r)/ti_3410.fw /lib/firmware/ti_usb-3410.bin

***

I managed to install my ETS1000 Series Fixed Wireless Terminal on Linux and go online. I thought of sharing the steps I took to install the modem on Linux such that you might be able to help someone with the same problem. This should work for any of the CDMA modems that will be using TI USB 3410 cable (the cable you get when you pay for Bell Net) as the problem is with the USB/Serial Cable not the HUAWEI modem.

System Requirements

* Linux with kernel above 2.6.** (Check it by command in console uname -a).
(Personally Tested on FC6, should work on any Linux Distribution)

Let’s Start

It is well assumed that Linux is up on your system and your USB/Serial cable is plugged in.
Now in console type command dmesg -c search for the following lines

ti_usb_3410_5052 1-1:2.0 : TI USB 3410 1 port adapter converter detected
usb 1-1: TI USB 3410 1 port adapter converter now attached to /dev/ttyUSB0

If u even see ttyUSB0 in the kernel message then also your modem is detected and you are ready to start,now just configure your wvdial.conf in /etc and start your dialup.

If not then possibly u will be seeing the following error messages in bundle but i will paste only two lines here.

ti_usb_3410_5052 1-1:1.0: TI USB 3410 1 port adapter converter detected

ti_usb_3410_5052: probe of 1-1:1.0 failed with error -5

Note that the problem is only the USB/Serial Cable not the HUAEWI modem.

Now we have to make one rule file in /etc/udev/rules.d/026_ti_usb_3410.rules

The file may not exist, but don’t worry.

In console login as a root

su

password *****

cd /etc/udev/rules.d/

vi 026_ti_usb_3410.rules (Now Paste the following lines in it)

SUBSYSTEM=="usb_device" ACTION=="add"
SYSFS{idVendor}=="0451",SYSFS{idProduct}=="3410" \
SYSFS{bNumConfigurations}=="2" \
SYSFS{bConfigurationValue}=="1" \
RUN+="/bin/sh -c 'echo 2 > /sys%p/device/bConfigurationValue'"

SAVE AND EXIT (:wq)

Now once again plug out ur USB/Serial cable and then plugin.

Again type dmesg -c in console

Check the kernel message and find the following line

ti_usb_3410_5052 1-1:2.0: TI USB 3410 1 port adapter converter detected
usb 1-1: TI USB 3410 1 port adapter converter now attached to /dev/ttyUSB0

CONGRATULATIONS it is finally done.

Now edit your /etc/wvdial.conf (Mine as a Sample below working fine)

My /etc/wvdial.conf

[Dialer ptcl]

Modem = /dev/ttyUSB0

Baud = 230400

Phone = #777

Init1 = ATZ

Stupid Mode = 1

Dial Command = ATDT

Username = YourUsername

Password = YourPassword

PPPD Options = crtcts multilink usepeerdns lock defaultroute

Important Note: Stupid Mode should be set to 1 otherwise the hash sign # with Dialing phone number will not be treated by wvdial.

LAST PROBLEM

When u will connect to ptcl with wvdial ptcl command as a root , it will not browse any page and will disconnect.

You have to set the nameserver in the /etc/resolv.conf .You can get the nameserver IPs from the terminal window when wvdial is trying to connect to your ISP.

Put those two nameserver in /etc/reslov.conf.

Now again as a root in console wvdial ptcl.

FINALLY YOU ARE DONE.

Installing Lexmark X1100 series on fc6

by

I unfortunately bought a Lexmark X1170 all in one two years back, it was cheap and got both printer and scanner. It worked fine on Windows. It was just paper weight ever since I moved to Linux.

I struck luck yesterday, when I stumbled upon a forum posting on Ubuntu forum.

So I started out straightaway, but had trouble getting the correct drivers from Lexmark site, as instructed in the forum (Got 404). So I went and searched in opendrivers.com and fortunately found it. To help all the poor soles to get the drivers easily I have hosted the rpms. If you download these rpms you can skip the part upto converting the rpms with alien if you are using a debian based system, or install the rpms and continue from restarting CUPS.

Here are the links:
http://www.mohanjith.net/downloads/d…1.0-1.i386.rpm
http://www.mohanjith.net/downloads/drivers/printers/lexmark/z600llpddk-2.0-1.i386.rpm

The instructions worked like a charm, and now I’m making use of my printer finally. From my point of view X1100 series is a repackage of Z600 series with a scanner.

Even though the scanner was correctly detected by SANE, I was unable to scan. But the version of sane that comes with Fedora Core 6 (Zod) is old.

GNOME Sensors Applet

by

That’s a cool desktop applet to show the systme temperature, fan speed, voltage, etc.

After I got lm_sensors running I wanted to get the sensor information on my desktop running GNOME. I installed GNOME Sensors Applet using yum (yum install gnome-applet-sensors).

It showed three temperatures(Only two successfully, other with an error), and I removed one. Two temperatures must be mother board and cpu temperature.

You should give a try to GNOME Sensors Applet, if you miss the Windows applets that are usually provided by the mother board manufacturers or just curious.

Cool applet, thumbs up Alex Murray and lm_sensors project

lm_sensors on Fedora Core 6

by

Today I tried to install lm_sensors and use it for motherboard and processor temperature sensoring. I installed lm_sensors rpm found on the installation disks and used yum to upgrade(update) to the latest version (2.10.1-1). The installation and upgrade went smoothly.

Then I tried to detect and configure the sensors using sensors-detect (located in /usr/sbin). Unfortunately it crashes in the middle of detection complaing about a missing file.

# sensors-detect revision 4171 (2006-09-24 03:37:01 -0700)

This program will help you determine which kernel modules you needto load to use lm_sensors most effectively. It is generally safeand recommended to accept the default answers to all questions,unless you know what you're doing.

We can start with probing for (PCI) I2C or SMBus adapters.Do you want to probe now? (YES/no): yesProbing for PCI bus adapters...Use driver `i2c-viapro' for device 0000:00:11.0: VIA Technologies VT8237 South Bridge

We will now try to load each adapter module in turn.Module `i2c-viapro' already loaded.If you have undetectable or unsupported adapters, you can have themscanned by manually loading the modules before running this script.

We are now going to do the I2C/SMBus adapter probings. Some chips maybe double detected; we choose the one with the highest confidencevalue in that case.If you found that the adapter hung after probing a certain address,you can specify that address to remain unprobed.Can't exec "i2cdetect": No such file or directory at ./sensors-detect line 5320, <stdin> line 1.Couldn't find i2cdetect program!! at ./sensors-detect line 5320, <stdin> line 1.

The file i2cdetect didn’t exist in the place it was looking, insted in /usr/sbin/

So I decided to do the fix myself and opened up /usr/sbin/sensors-detect for editing and suspected bellow lines to be the culprit.

# Same for /usr/local/sbin since we need i2cdetect which is installed there# by default (reported by Lennard Klein)$ENV{PATH} = '/usr/local/sbin:'.$ENV{PATH}     unless $ENV{PATH} =~ m,(^|:)/usr/local/sbin/?(:|$),;

Changed it to…

# Same for /usr/sbin since we need i2cdetect which is installed there# by default (reported by Lennard Klein)$ENV{PATH} = '/usr/sbin:'.$ENV{PATH}     unless $ENV{PATH} =~ m,(^|:)/usr/sbin/?(:|$),;

and all worked fine. (changed /usr/local/sbin to /usr/sbin)

I followed the instructions given by sensors-detect and then started lm_sensors service.

Check my next post for how I got the temperatures to appear on my desktop(GNOME).