Bug 494217

Summary: YaST2 does not allow ttyUSB devices for modem config
Product: [openSUSE] openSUSE 11.0 Reporter: J L Turriff <jlturriff>
Component: YaST2Assignee: Michal Zugec <mzugec>
Status: RESOLVED NORESPONSE QA Contact: Jiri Srain <jsrain>
Severity: Major    
Priority: P5 - None CC: lnussel, snwint
Version: Final   
Target Milestone: ---   
Hardware: i686   
OS: openSUSE 11.0   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: output from sertest (wacom tablet attachment)

Description J L Turriff 2009-04-11 20:54:41 UTC 
User-Agent:       Mozilla/5.0 (compatible; Konqueror/3.5; Linux 2.6.25.5-1.1-pae) KHTML/3.5.9 (like Gecko) SUSE

I'm running openSuSE 11.0 on a PC with a A7VBX-X motherboard, which has only
one serial port, which is dedicated to my external 56Kbaud modem.  I also have
a Wacom Intuos serial tablet which I want to use with the Gimp, so I acquired a
USB--tty adapter which provides two additional serial ports at /dev/ttyUSB0 and
/dev/ttyUSB1; but Sax2 does not allow me to configure either of these ports for the tablet (see Bug 494216).
So I tried connecting the modem to /dev/ttyUSB0 and the tablet to /dev/ttyS0; but I'm getting the same issue with YaST2 that I did with Sax2: /dev/ttyUSB0 and /dev/ttyUSB1 do not appear in the list of devices to be selected for use with the modem.


Reproducible: Always

Steps to Reproduce:
1. Plug the USB--tty adapter into a free USB port.  dmesg shows

usb 3-2: new full speed USB device using uhci_hcd and address 8
usb 3-2: configuration #1 chosen from 1 choice
ftdi_sio 3-2:1.0: FTDI USB Serial Device converter detected
drivers/usb/serial/ftdi_sio.c: Detected FT2232C
usb 3-2: FTDI USB Serial Device converter now attached to ttyUSB0
ftdi_sio 3-2:1.1: FTDI USB Serial Device converter detected
drivers/usb/serial/ftdi_sio.c: Detected FT2232C
usb 3-2: FTDI USB Serial Device converter now attached to ttyUSB1
usb 3-2: New USB device found, idVendor=0403, idProduct=6010
usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 3-2: Product: CHAIRSIDE(tm) Machine Interface v1
usb 3-2: Manufacturer: FTDI

2.
  a. Attach a serial device to /dev/ttyUSB0.
  b. Look for activity on port /dev/ttyUSB0 (I used a program called sertest; see attached files).
 
3.
  a. run YaST2.
  b. Select "Network Devices"
  c. Select "Modem"
  d. Under "Modem Devices" tab, select "Edit"
  e. Open the "Modem device" pulldown
Actual Results:  
Devices available from step 3.e. are
/dev/modem
/dev/ttyACM0
/dev/ttyACM1
/dev/ttyACM2
/dev/ttyACM3
/dev/ttyS0
/dev/ttyS1
/dev/ttyS2
/dev/ttyS3

Expected Results:  
Devices available from step 3.e. should be
/dev/modem
/dev/ttyS0
/dev/ttyUSB0
/dev/ttyUSB1

BTW, what are /dev/ttyACM* ?  They do not appear in the output from ls -l /dev/ | grep ACM
Comment 1 J L Turriff 2009-04-11 21:03:01 UTC 
Created attachment 285312 [details]
output from sertest (wacom tablet attachment)

This file merely shows that traffic is indeed coming through the /dev/ttyUSB0 device into the system.  The device could be used if YaST2 would allow it to be configured.
Comment 2 Marcus Meissner 2009-04-12 09:16:22 UTC 
ttyACM* are specific modem based device, also serial and also AT command driven.

reassign to maintainer of yast2-ntework
Comment 3 J L Turriff 2009-04-14 04:57:03 UTC 
I may be wrong, but it looks to me as if the "Modem Device" list contents are hard-coded, instead of being created dynamically by scanning at execution-time?

Leslie
Comment 4 Michal Zugec 2009-04-17 15:03:22 UTC 
Just to be sure: combobox is editable, so you can write /dev/ttyUSB0 if you want and it works, right?
Comment 5 Michal Zugec 2009-04-17 15:27:42 UTC 
And answer to your question: yes, list is hardcoded. I don't know how I can dynamically create list you expect ...
Comment 6 Ludwig Nussel 2009-04-20 08:00:11 UTC 
hal-find-by-capability --capability serial
Comment 7 J L Turriff 2009-04-20 18:33:38 UTC 
> Just to be sure: combobox is editable, so you can write /dev/ttyUSB0 if you
> want and it works, right?

No, sir.  It appears to be so, but after clicking through Next -> Next -> Next -> Next -> Finish, the new value is not saved.  (If I was able to just overtype with the desired value I would not have needed to open this bug report.) :-)

Leslie
Comment 8 Michal Zugec 2009-04-22 14:17:40 UTC 
hal-find-by-capability --capability serial
/org/freedesktop/Hal/devices/pnp_PNP0501_0_serial_platform_1
/org/freedesktop/Hal/devices/pnp_PNP0501_serial_platform_0

Ludwig, how can I extract /dev/tty* device from this output?
Comment 9 Ludwig Nussel 2009-04-22 14:26:11 UTC 
via shell?
$ hal-get-property --udi /org/freedesktop/Hal/devices/pnp_PNP0501_serial_platform_0 --key serial.device
/dev/ttyS0

Doesn't YaST have some agent that allows it to talk to hal rather than having to use such dirty commands?
Comment 10 Michal Zugec 2009-04-23 16:41:46 UTC 
Steffen, could you extend hwinfo about this information?
Comment 11 Steffen Winterfeldt 2009-04-27 10:34:25 UTC 
I think I came across this during SL 11.1 beta testing. So it might just
work with hwinfo from 11.1 (reporting ttyUSB* devices correctly).
Comment 12 Michal Zugec 2009-04-29 09:00:27 UTC 
What is output when you execute as a root:


echo '`Read(.probe.modem)'|/usr/lib/YaST2/bin/y2base stdio scr
Comment 13 J L Turriff 2009-04-29 23:32:15 UTC 
Here's what I get on my 11.0 system:

#
echo '`Read(.probe.modem)'|/usr/lib/YaST2/bin/y2base stdio scr
([])
([])
Comment 14 Michal Zugec 2009-04-30 06:12:23 UTC 
Can you upgrade or try liveCD with 11.1?
Comment 15 Michal Zugec 2009-10-20 09:54:22 UTC 
Closed because no response for a long time.
Feel free to reopen when you be able to provide requested information.