Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#6432 - Kernel 2.6.20 - HSDPA Huawei modem detection

Attached to Project: Arch Linux
Opened by João Rodrigues (gothicknight) - Friday, 16 February 2007, 10:05 GMT
Last edited by Tobias Powalowski (tpowa) - Saturday, 24 February 2007, 08:18 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I have a huawei E220 HSDPA modem, and after .20 i couldn't create the inodes in /dev for my device...

***DMESG OUTPUT***
option 1-3:1.0: GSM modem (1-port) converter detected
usb 1-3: GSM modem (1-port) converter now attached to ttyUSB0
option 1-3:1.1: GSM modem (1-port) converter detected
usb 1-3: GSM modem (1-port) converter now attached to ttyUSB1
option 1-3:1.2: GSM modem (1-port) converter detected
usb 1-3: GSM modem (1-port) converter now attached to ttyUSB2
***DMESG OUTPUT***

But there's neither /dev/ttyUSB[0-2] and even with mknod there's no connection to the hardware.

The modem is functional, with 2.6.19 it worked under some workarounds in usb-serial wich don't work, the modem was added to the kernel headers and now is automagicly detected as shown in dmesg but not in /dev can this be a udev bug?
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Monday, 26 February 2007, 21:33 GMT
Reason for closing:  Fixed
Comment by João Rodrigues (gothicknight) - Thursday, 22 February 2007, 20:10 GMT
I've found the device inodes in /dev/tts/USB[0-2] but they shouldn't be here AFAIK they should appear in /dev/ttyUSB[0-2]
Comment by Tobias Powalowski (tpowa) - Thursday, 22 February 2007, 20:11 GMT
sounds like a udev issue then
Comment by João Rodrigues (gothicknight) - Friday, 23 February 2007, 00:52 GMT
I don't know much about udev rules, if so i would change them myself. Any help i can give, send a message. For now the device is working so, the severity isn't critical :|
Comment by Tobias Powalowski (tpowa) - Saturday, 24 February 2007, 08:25 GMT
please try this new udev it should fix the missing symlink:
http://www.archlinux.org/~tpowa/udev-105-5.pkg.tar.gz
thanks
Comment by João Rodrigues (gothicknight) - Monday, 26 February 2007, 10:12 GMT
The patch worked, the devices are now created under /dev/ttyUSB and /dev/tts/USB. You may close the bug!

Loading...