Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am having a problem with my linux box. It is a Slackware 9.1 machine. It had been working fine for about half a year and then last week I installed a generic version of the Wildcard X100P card which uses the zaptel and wcfxo drivers. I had it working for awhile and then weird things started happening. I don't know that it is directly related to using this card, but all the problems started around that time.
The problems:
-If I use hotplug it does not allow me to login. The login prompt comes up and I type my password in but it just comes up with another login prompt. Also, sometimes it logs me in and the overwrites the screen with the prompt again.
-When I am able to login(turning off hotplug), I do a modprobe 8139too for my ethernet card, then a modprobe zaptel, then a modprobe wcfxo. Once I have done this I am not able to run any programs, they all give me a Segmentation Fault.
-I have already re-imaged and re-installed the machine and it is still giving me errors.
Please help if you have any ideas. Tell me if you need to post any more information. Thanks.
maybe conflicting interrupts. be sure they all have their own. look at /proc/interrupts. you may also try to use another placement in your pci-slots to solve this (if it's irq-related).
really sounds weird. i can't imagine 'bout a interaction between usb and your login with your newly installed card?
Thanks for the post...I checked the interrupts and I do believe that it is a problem with them. Everything works fine until I load the wcfxo module which uses interrupt 11. Below is my /var/log/messages, /proc/interrupts, and lspci after I have loaded the modules. I tried to load change the options in modules.conf for an irq=9 for the wcfxo module but it says it does not let me load it with 9 as the interrupt. Any ideas how I can fix these? Thanks.
/var/log/messages
.................................................................................................... ...........................
Aug 4 19:39:14 J-Unit kernel: 8139too Fast Ethernet driver 0.9.26
Aug 4 19:39:14 J-Unit kernel: PCI: Found IRQ 5 for device 00:05.0
Aug 4 19:39:14 J-Unit kernel: eth0: D-Link DFE-538TX (RealTek RTL8139) at 0xd8a
00000, 00:50:ba:b9:41:78, IRQ 5
Aug 4 19:40:11 J-Unit kernel: Zapata Telephony Interface Registered on major 19
6
Aug 4 19:40:25 J-Unit kernel: PCI: Found IRQ 11 for device 00:06.0
Aug 4 19:40:25 J-Unit kernel: PCI: Sharing IRQ 11 with 00:14.2
Aug 4 19:40:25 J-Unit kernel: PCI: Sharing IRQ 11 with 00:14.3
Aug 4 19:43:20 J-Unit init: Switching to runlevel: 6
Aug 4 19:43:27 J-Unit exiting on signal 15
Aug 4 21:28:51 J-Unit syslogd 1.4.1: restart.
Aug 4 21:28:52 J-Unit kernel: klogd 1.4.1, log source = /proc/kmsg started.
Aug 4 21:28:52 J-Unit kernel: BIOS-provided physical RAM map:
Aug 4 21:28:52 J-Unit kernel: 384MB LOWMEM available.
Aug 4 21:28:52 J-Unit kernel: Initializing CPU#0
Aug 4 21:28:52 J-Unit kernel: Memory: 385764k/393216k available (1813k kernel c
ode, 7064k reserved, 614k data, 116k init, 0k highmem)
lspci output
.................................................................................................... ...........................
00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev 03)
00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
00:03.0 FireWire (IEEE 1394): Texas Instruments TSB12LV26 IEEE-1394 Controller (Link)
00:04.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 07)
00:04.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 07)
00:05.0 Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 10)
00:06.0 Communication controller: Tiger Jet Network Inc. Intel 537 <--This is the problem card
00:07.0 Modem: PCTel Inc HSP MicroModem 56 (rev 02)
00:14.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 22)
00:14.1 IDE interface: VIA Technologies, Inc. VT82C586/B/686A/B PIPC Bus Master IDE (rev 10)
00:14.2 USB Controller: VIA Technologies, Inc. USB (rev 10)
00:14.3 USB Controller: VIA Technologies, Inc. USB (rev 10)
00:14.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 30)
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R100 QD [Radeon 7200]
you can try putting the cards in other pci slots. this way you'll have to open the box and fiddle around till you got it.
maybe you can disable pnp in your bios and asign irq's to cards manualy. some bios's here are really $!%?!#!!.
to be sure it's the irq-settings: you can disable usb in your bios or at loading the kernel(?..look at /usr/src/your_kernel/Documentation/kernel-parameters.txt). then see if it's working as it should.
You can try to freshen up modprobe and the kernel by re-compiling them. It could be a module problem conflicting with your system. How new is Wildcard X100P. If its new and your system is only having the problem then you can upgrade the BIOS or get a device that will replace Wildcard X100P. You can take out the Soundblaster LIVE and to see if your Wildcard X100P works. The Soundblaster LIVE is known to have problems with your chipset.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.