Bug 167295 - Missing ttyI* devices after loading AVM B1 and CAPI modules
Summary: Missing ttyI* devices after loading AVM B1 and CAPI modules
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel
Version: 4.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Ric Wheeler
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-09-01 13:08 UTC by Peter Bieringer
Modified: 2012-06-20 13:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 13:29:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Peter Bieringer 2005-09-01 13:08:34 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-DE; rv:1.7.10) Gecko/20050717 Firefox/1.0.6

Description of problem:
After bringing ISDN for a AVM B1 card to work (see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=167291 and https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=139321) ttyI* devices aren't created by udev

Version-Release number of selected component (if applicable):
udev-039-10.8.EL4

How reproducible:
Always

Steps to Reproduce:
1. bring ISDN for a AVM B1 card to work
2. setup mgetty for e.g. ttyI0
3. start mgetty
  

Actual Results:  Missing device avoid start of mgetty

Expected Results:  ttyI* devices are created

Additional info:

Create at least one reboot-static device in udev's devices directory:

# mknod -m 0660 /etc/udev/devices/ttyI0 c 43 0
# chgrp uucp /etc/udev/devices/ttyI0

Comment 1 Harald Hoyer 2005-09-01 13:29:10 UTC
if no ttyI* devices are created, then the kernel has to be blamed, not to send
out hotplug events and/or create sysfs entries for that device.

Comment 3 Jiri Pallich 2012-06-20 13:29:49 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.


Note You need to log in before you can comment on or make changes to this bug.