Thanks James

Now we'll see if you can! teach old dogs new tricks that is.

Back again

I still can't get this bloody thing to work.

See below & let me know what you think please.

# udev rule to create /dev/input/ttyACM0 (10-my.rules)

# KERNEL="dm-[0-9]*", PROGRAM="/sbin/devmap_name %M %m", NAME="%k", SYMLINK="%c"

# NT1 plus II
ID="/sys/class/usb_host/usb2/device/usb2/2-1", SYSFS{product}="OPEN NT1 Plus II", SYSFS{idproduct}="1060", NAME="%k", SYMLINK="input/ACM0"

Only attributes within one device section may be used together in one rule,
to match the device for which the node will be created.

looking at class device '/sys/class/usb_host/usb2/device/usb2/2-1':
SYSFS{bConfigurationValue}="1"
SYSFS{bDeviceClass}="02"
SYSFS{bDeviceProtocol}="00"
SYSFS{bDeviceSubClass}="00"
SYSFS{bMaxPower}=" 0mA"
SYSFS{bNumConfigurations}="1"
SYSFS{bNumInterfaces}=" 2"
SYSFS{bcdDevice}="0011"
SYSFS{bmAttributes}="e0"
SYSFS{detach_state}="0"
SYSFS{devnum}="2"
SYSFS{idProduct}="1060"
SYSFS{idVendor}="0aca"
SYSFS{manufacturer}="OPEN Networks Ltd"
SYSFS{maxchild}="0"
SYSFS{product}="OPEN NT1 Plus II"
SYSFS{speed}="12"
SYSFS{version}=" 1.10"

Where have I gone wrong. Mind you, this rule is the 3rd go using different keys.

Any suggestions!

Tony

tony

what about loking in

ls /sys/bus/usb/devices/x-y/
like I said in my previous post
I don't know if it matters if it is from class
or bus subdir but it might.

from the looks of it you should look in
ls /sys/bus/usb/devices/2-1/

And an entry similar to this should sort you out

BUS="usb", SYSFS{product}="OPEN NT1 Plus II", SYSFS{idProduct}="1060", NAME="%k", SYMLINK="modem"

Thanks mate, i'll try that. At present I now have ttyACM0 in /dev. Upgraded kernel & changed udev.rules. But now wvdial finds & is querying the modem but is not getting a reply & times out!

Bloody things shoudn't be this hard, to configure. I thought I'd got away from that. Spent days 15 yrs ago trying to get scsi devices to talk to one another. I'm too old to go through that again.

tony

Well here's the latest udevinfo output.
Modem is linked to ttyACM0 but won't respond to commands.

udevinfo starts with the device the node belongs to and then walks up the
device chain, to print for every device found, all
possibly useful attributes
in the udev key format.
Only attributes within one device section may be used together in one rule,
to
match the device for which the node will be created.

looking at class device '/sys/devices/pci0000:00/0000:00:03.0/usb2/2-1':
SYSFS{bConfigurationValue}="1"
SYSFS{bDeviceClass}="02"
SYSFS{bDeviceProtocol}="00"
SYSFS{bDeviceSubClass}="00"
SYSFS{bMaxPower}=" 0mA"
SYSFS{bNumConfigurations}="1"
SYSFS{bNumInterfaces}=" 2"
SYSFS{bcdDevice}="0011"
SYSFS{bmAttributes}="e0"
SYSFS{configuration}="ISDN TA using CDC Abstract Control Model"
SYSFS{detach_state}="0"
SYSFS{devnum}="2"
SYSFS{idProduct}="1060"
SYSFS{idVendor}="0aca"
SYSFS{manufacturer}="OPEN Networks Ltd"
SYSFS{maxchild}="0"
SYSFS{product}="OPEN NT1 Plus II"
SYSFS{speed}="12"

Seems fedora is seeing the thing as a TA.
Any suggestions?

well it's kind of breathing now ;-)

when I set it up I used kppp. provided there is a symlink to /dev/modem this should at least detect it
under kppp go to configure -> modems -> new add your /dev/modem modem and then try clicking
query modem (it just sends at commands to the modem).

If it finds it then you should be in business. Then only thing was under the modem commands section
there was some AT strings it was sending that the NT1 didn't like
and I can't for the life of me think what they were. I will try to find them for you
I think instead of atdt you send atd

just found this out of a slug newsgroup and it may help if you want to use wvdial
<snip>
This is the init string I use:

AT!Z=9!T0=0!T1=0!T2=1!T4=1

which should bring up the second channel (if it's not in use of
course). If you're using it on a serial port, set the speed to 115200
with h/w handshaking. I've had it working on both serial and usb
interfaces with the same init string.
</snip>

As i said earlier, kppp querying the modem does not get a response. All commands sent come back blank. The modem doesn't respond at all.

The strings are not the problem as they are the same as i use in Mandrake 10.0 & Knoppix 3.6/Debian. Both of these do not use udev as their kernel has not been updated that far, (& won't be untill I can sought out the problem in fc3) 'dont want them causing me the same problem do I??

I'm going to put the problem in the h/ware & networking forums in this & other Linux forums to see if someone can come up with an answer. Of course i'll keep pecking away at fc3 in the meantime to see if I can come up with an answer.

Thanks for your help.
Tony

Apologies tony,
I didn't realise you allready had it working on Knoppix or Mandrake.
This is a tough one as once my /dev/modem link worked kppp just worked
I do recall that the issue I had with the Nt1 and kppp was that kppp was sending volume commands
to the nt1 and the nt1 doesn't understand these so it wouldn't respond. Try clearing the volume options
at the bottom of the modem commands section. Maybe knoppix and mdk don't set these and fedora does ? <just a guess>.

Other than that you have stumped me.

--
James