* Zaptel hotplug errors
@ 2004-10-29 2:39 Derek Whitten
2004-10-29 4:04 ` Kevin P. Fleming
2004-10-30 3:11 ` Kay Sievers
0 siblings, 2 replies; 3+ messages in thread
From: Derek Whitten @ 2004-10-29 2:39 UTC (permalink / raw)
To: linux-hotplug
[-- Attachment #1.1: Type: text/plain, Size: 2484 bytes --]
Got this in /var/log/messages
Oct 28 19:18:29 leroy kernel: Zapata Telephony Interface Registered on
major 196
Oct 28 19:18:30 leroy kernel: ACPI: PCI interrupt 0000:00:0e.0[A] -> GSI
15 (level, low) -> IRQ 15
Oct 28 19:18:30 leroy kernel: ACPI: PCI interrupt 0000:00:0d.0[A] -> GSI
14 (level, low) -> IRQ 14
Oct 28 19:18:35 leroy wait_for_sysfs[1792]: error: wait_for_sysfs needs
an update to handle the device '/class/zaptel/zaptimer' properly, please
report to <linux-hotplug-devel@lists.sourceforge.net>
Oct 28 19:18:35 leroy wait_for_sysfs[1796]: error: wait_for_sysfs needs
an update to handle the device '/class/zaptel/zappseudo' properly,
please report to <linux-hotplug-devel@lists.sourceforge.net>
Oct 28 19:18:35 leroy wait_for_sysfs[1794]: error: wait_for_sysfs needs
an update to handle the device '/class/zaptel/zapchannel' properly,
please report to <linux-hotplug-devel@lists.sourceforge.net>
Oct 28 19:18:35 leroy wait_for_sysfs[1798]: error: wait_for_sysfs needs
an update to handle the device '/class/zaptel/zapctl' properly, please
report to <linux-hotplug-devel@lists.sourceforge.net>
Oct 28 19:18:35 leroy wait_for_sysfs[1802]: error: wait_for_sysfs needs
an update to handle the device '/class/zaptel/zap1' properly, please
report to <linux-hotplug-devel@lists.sourceforge.net>
From /var/log/syslog..
Oct 28 19:18:30 leroy kernel: wcfxo: DAA mode is 'FCC'
Oct 28 19:18:30 leroy kernel: Found a Wildcard FXO: Generic Clone
# lspci
00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge
(rev 03)
00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge
(rev 03)
00:04.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02)
00:04.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
00:04.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01)
00:04.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 02)
00:09.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone]
(rev 30)
00:0a.0 SCSI storage controller: Adaptec AHA-2940U/UW/D / AIC-7881U (rev
01)
00:0b.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone]
(rev 24)
00:0c.0 VGA compatible controller: Trident Microsystems TGUI
9660/938x/968x (rev d3)
00:0d.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev 02)
00:0e.0 Communication controller: Individual Computers - Jens Schoenfeld
Intel 537
Now what ? :-)
--
Derek Whitten <derek@kfuq.net>
[-- Attachment #1.2: Type: text/html, Size: 3374 bytes --]
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Zaptel hotplug errors
2004-10-29 2:39 Zaptel hotplug errors Derek Whitten
@ 2004-10-29 4:04 ` Kevin P. Fleming
2004-10-30 3:11 ` Kay Sievers
1 sibling, 0 replies; 3+ messages in thread
From: Kevin P. Fleming @ 2004-10-29 4:04 UTC (permalink / raw)
To: linux-hotplug
Derek Whitten wrote:
> Oct 28 19:18:29 leroy kernel: Zapata Telephony Interface Registered on
> major 196
> Oct 28 19:18:30 leroy kernel: ACPI: PCI interrupt 0000:00:0e.0[A] -> GSI
> 15 (level, low) -> IRQ 15
> Oct 28 19:18:30 leroy kernel: ACPI: PCI interrupt 0000:00:0d.0[A] -> GSI
> 14 (level, low) -> IRQ 14
> Oct 28 19:18:35 leroy wait_for_sysfs[1792]: error: wait_for_sysfs needs
> an update to handle the device '/class/zaptel/zaptimer' properly, please
> report to <linux-hotplug-devel@lists.sourceforge.net>
> Oct 28 19:18:35 leroy wait_for_sysfs[1796]: error: wait_for_sysfs needs
> an update to handle the device '/class/zaptel/zappseudo' properly,
> please report to <linux-hotplug-devel@lists.sourceforge.net>
> Oct 28 19:18:35 leroy wait_for_sysfs[1794]: error: wait_for_sysfs needs
> an update to handle the device '/class/zaptel/zapchannel' properly,
> please report to <linux-hotplug-devel@lists.sourceforge.net>
> Oct 28 19:18:35 leroy wait_for_sysfs[1798]: error: wait_for_sysfs needs
> an update to handle the device '/class/zaptel/zapctl' properly, please
> report to <linux-hotplug-devel@lists.sourceforge.net>
> Oct 28 19:18:35 leroy wait_for_sysfs[1802]: error: wait_for_sysfs needs
> an update to handle the device '/class/zaptel/zap1' properly, please
> report to <linux-hotplug-devel@lists.sourceforge.net>
The Zaptel drivers currently expose on a single sysfs attribute ("dev"),
the minimum required to get device nodes created. Getting them to do
more than that will be a job for the Asterisk developers, and should be
requested on the asterisk-dev list.
-------------------------------------------------------
This Newsletter Sponsored by: Macrovision
For reliable Linux application installations, use the industry's leading
setup authoring tool, InstallShield X. Learn more and evaluate
today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Zaptel hotplug errors
2004-10-29 2:39 Zaptel hotplug errors Derek Whitten
2004-10-29 4:04 ` Kevin P. Fleming
@ 2004-10-30 3:11 ` Kay Sievers
1 sibling, 0 replies; 3+ messages in thread
From: Kay Sievers @ 2004-10-30 3:11 UTC (permalink / raw)
To: linux-hotplug
On Thu, Oct 28, 2004 at 07:39:43PM -0700, Derek Whitten wrote:
> Got this in /var/log/messages
> Oct 28 19:18:35 leroy wait_for_sysfs[1792]: error: wait_for_sysfs needs
> an update to handle the device '/class/zaptel/zaptimer' properly, please
> report to <linux-hotplug-devel@lists.sourceforge.net>
> Oct 28 19:18:35 leroy wait_for_sysfs[1796]: error: wait_for_sysfs needs
> an update to handle the device '/class/zaptel/zappseudo' properly,
> please report to <linux-hotplug-devel@lists.sourceforge.net>
> Oct 28 19:18:35 leroy wait_for_sysfs[1794]: error: wait_for_sysfs needs
> an update to handle the device '/class/zaptel/zapchannel' properly,
> please report to <linux-hotplug-devel@lists.sourceforge.net>
> Oct 28 19:18:35 leroy wait_for_sysfs[1798]: error: wait_for_sysfs needs
> an update to handle the device '/class/zaptel/zapctl' properly, please
> report to <linux-hotplug-devel@lists.sourceforge.net>
> Oct 28 19:18:35 leroy wait_for_sysfs[1802]: error: wait_for_sysfs needs
> an update to handle the device '/class/zaptel/zap1' properly, please
> report to <linux-hotplug-devel@lists.sourceforge.net>
> Now what ? :-)
The only thing which will not work without full sysfs support is a BUS="pci"
match in an udev rule, so I will suppress this for all of these zaptel devices.
Thanks,
Kay
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_idU88&alloc_id\x12065&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2004-10-30 3:11 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-10-29 2:39 Zaptel hotplug errors Derek Whitten
2004-10-29 4:04 ` Kevin P. Fleming
2004-10-30 3:11 ` Kay Sievers
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).