Elmer Re: #blacklist intel8x0 softmodem driver which interferes with sound driver snd_intel8x0m --------- is not true. Rather snd_intel8x0m is the modem driver and it depends on snd_intel8x0. Do $ lsmod | grep intel8x0m which will show relationships Sadly /dev/pts/N ports do not (yet) support sound, so you can browse, but not get sound from the Internet. With respect do usb, just leave that line alone, as you have gotten on line OK. However RE: modem interrupt assignment and sharing: 11: 135715 XT-PIC yenta, ohci1394, Intel ICH4, ehci_hcd, uhci_hcd, uhci_hcd, uhci_hcd, eth2, radeon@PCI:1:0:0, eth0 You won't be able to navigate unless before dialup: # ifconfig eth0 down # ifconfig eth2 down as DNS services will be blocked. MarvS On Tue, Jul 1, 2008 at 4:29 AM, postid <postid@xxxxxxxxxxxx> wrote: > 07-01-08 > > Near midnight last night I tried something that partially works. In > researching discover and hotplug, I found a line in the hotplug blacklist > file: > > #blacklist intel8x0 softmodem driver which interferes with sound driver > snd_intel8x0m > > So I commented the line for snd_intel8x0m: > > #blacklist intel8x0 softmodem driver which interferes with sound driver > # snd_intel8x0m > > Evidently -- at least according to the hotplug blacklist -- it's the softmodem > driver and the sound driver that interfere with each other. > > After booting: > > ellsworth@R40:~$ cat /proc/asound/pcm > 00-00: Intel ICH : Intel 82801DB-ICH4 : playback 1 : capture 1 > 00-01: Intel ICH - MIC ADC : Intel 82801DB-ICH4 - MIC ADC : capture 1 > 00-02: Intel ICH - MIC2 ADC : Intel 82801DB-ICH4 - MIC2 ADC : capture 1 > 00-03: Intel ICH - ADC2 : Intel 82801DB-ICH4 - ADC2 : capture 1 > 00-04: Intel ICH - IEC958 : Intel 82801DB-ICH4 - IEC958 : playback 1 > 01-00: Intel ICH - Modem : Intel 82801DB-ICH4 Modem - Modem : playback 1 : > capture 1 > ellsworth@R40:~$ > > > As root: > > R40:/home/ellsworth# slmodemd --country=USA --alsa hw:1 > error: mixer setup: Off-hook switch not found for card hw:1 > SmartLink Soft Modem: version 2.9.11 Jan 19 2006 21:19:22 > symbolic link `/dev/ttySL0' -> `/dev/pts/3' created. > modem `hw:1' created. TTY is `/dev/pts/3' > Use `/dev/ttySL0' as modem device, Ctrl+C for termination. > R40:/home/ellsworth# > > As root in another window: > R40:/home/ellsworth# wvdial > --> WvDial: Internet dialer version 1.54.0 > --> Cannot get information for serial port. > --> Initializing modem. > --> Sending: ATZ > ATZ > OK > --> Sending: ATQ0 V1 E1 S0=0 X3 &C1 &D2 +FCLASS=0 > ATQ0 V1 E1 S0=0 X3 &C1 &D2 +FCLASS=0 > OK > --> Modem initialized. > --> Sending: ATDT265-0125 > --> Waiting for carrier. > ATDT2650125 > CONNECT 45333 > C > UQKT2 > User Access Verification > Username: > --> Carrier detected. Waiting for prompt. > Username: > --> Looks like a login prompt. > --> Sending: username@xxxxxxxxxxxx > username@xxxxxxxxxxxx > Password: > --> Looks like a password prompt. > --> Sending: (password) > Entering PPP mode. > Async interface address is unnumbered (Loopback0) > Your IP address is 0.0.0.0. MTU is 1500 bytes > --> Looks like a welcome message. > --> Starting pppd at Tue Jul 1 08:21:13 2008 > --> pid of pppd: 5433 > --> Using interface ppp0 > --> local IP address 67.1.79.78 > --> remote IP address 67.1.64.6 > --> primary DNS address 67.211.172.29 > --> secondary DNS address 67.211.172.30 > > > [Dialer Defaults] > Modem = /dev/ttySL0 > Baud = 460800 > Init1 = ATZ > Init2 = ATQ0 V1 E1 S0=0 X3 &C1 &D2 +FCLASS=0 > ISDN = 0 > Modem Type = Analog Modem > Carrier Check = no > New PPPD = yes > Phone = 2650125 > Username = username@xxxxxxxxxxxx > Password = password > > I added X3 just in case. > > There is no sound -- dial tone, dialing, etc. but if I pick up the telephone > handset after dialing I can hear the noise coming back from the ISP. I'd like > to hear the modem dialing in. Sound works for other applications (XMMS, etc.) > but they're using OSS. The modem is the only app using ALSA. I need to get > ALSA to work with -- instead of against -- the modem driver although I guess > I could live without hearing the modem. > > I'll try your method below today and report back. Won't this result in the usb > system not working? I can live without pcmcia but I need usb. > > > On Tuesday 01 July 2008 07:28 am, you wrote: >> Elmer, >> >> Well you educated us a little today. Previously I wasn't aware of the >> /etc/discover* files. >> >> But reading >> $ man discover.conf >> clarifies their usage. Simple edits with vim should be OK. >> For your lines in /etc/discover.conf like: >> ---------- >> # Enable the PCI, USB, IDE, and SCSI bus scans: >> enable pci,usb,ide,scsi >> >> # Enable the PCMCIA scan too: >> enable pcmcia >> -------- >> >> just edit to: >> -------------- >> # Enable the PCI, USB, IDE, and SCSI bus scans: >> # enable pci,usb,ide,scsi >> enable pci,ide,scsi >> >> # Enable the PCMCIA scan too: >> # enable pcmcia >> ----------- >> >> This should eliminate interference from hardare sharing the same IRQ, >> as assessed from your ModemData.txt lines: >> Modem interrupt assignment and sharing: >> 11: 135715 XT-PIC yenta, ohci1394, Intel ICH4, ehci_hcd, >> >> Reboot and check the effects. >> >> Copy in your own /etc/discover.conf file when you report back, >> as it may not be identical to that on other systems. >> >> MarvS >> >> On Mon, Jun 30, 2008 at 3:22 PM, postid <postid@xxxxxxxxxxxx> wrote: >> > Thanks for your patient assistance. I unzipped and copied your file >> > blacklist.local to /etc/modprobe.d without editing, just changed >> > permissions to root read and write, and read for others and group. Same >> > problem. Error messages and the blacklisting ignored. >> > >> > I've today found some info indicating that one should use modconf to make >> > sure that the modules in question aren't in the manual module load config >> > files. Then the blacklisted files must also appear on the skip line >> > in /etc/discover-modprobe.conf, after installing the discover package (I >> > have discover1 installed, discover uses libdiscover2). And, of course, >> > the modules must be listed in the blacklist file. I don't know if editing >> > directly the discover-modprobe.conf file is the correct method or not. >> > >> > Research using Google seems to indicate two other possible solutions. >> > >> > I'm wondering if going in the BIOS and changing the IRQ settings to >> > automatic might solve the conflict problem. Or is there a Debian IRQ >> > config file somewhere that would do that? >> > >> > Or could I use modconf --load before <modulename> to make the skipped >> > module load? Then if it did, I assume that one of the other modules would >> > be missing and thus I'd know which was the offending conflicting module. >> > >> > Or am I in my foolishness about to really mess something up? >> > >> > On Monday 30 June 2008 11:42 pm, you wrote: >> >> Attached is my file. >> >> under Linux, gunzip >> >> comment out the lines you don't want with a leading # >> >> Then copy into position. >> >> It need not be executable. >> >> It must need be read. >> >> >> >> MarvS >> >> >> >> On Mon, Jun 30, 2008 at 8:38 AM, postid <postid@xxxxxxxxxxxx> wrote: >> >> > On Friday 27 June 2008 05:00 am, you wrote: >> >> >> The file should look like >> >> >> >> >> >> blacklist ohci1394 >> >> >> blacklist uhci_hcd >> >> >> blacklist ehci_hcd >> >> >> >> >> >> Only create it with a PLAIN TEXT editor such as gedit >> >> >> >> >> >> MarvS >> >> > >> >> > Greetings: >> >> > >> >> > I'm having no success with blacklisting. As root and using vim to >> >> > create a text-only file, I've created /etc/modrobe.d/blacklist.local >> >> > containing >> >> > >> >> > blacklist ohci1394 >> >> > blacklist uhci_hcd >> >> > blacklist ehci_hcd >> >> > >> >> > When I reboot, I get error messages: >> >> > localhost modprobe:WARNING: /etc/modprobe.d/blacklist.local line 2: >> >> > ignoring bad line starting with 'blacklist' >> >> > >> >> > Permissions are root read/write and group and user read only. It's not >> >> > executable. >> >> > >> >> > My system is Debian Sarge. What am I doing wrong? >> >> > >> >> >> On Thu, Jun 26, 2008 at 5:35 PM, postid <postid@xxxxxxxxxxxx> wrote: >> >> >> > On Wednesday 25 June 2008 12:25 am, you wrote: >> >> >> >> # slmodem --country=USA --alsa modem:1 >> >> >> >> >> >> >> >> But first do: >> >> >> >> # cat /proc/asound/pcm >> >> >> >> which ouput should include a line >> >> >> >> 01-00: Modem something Intel ICH4 >> >> >> >> >> >> >> >> If it is not there, there is a resource conflict. Primary >> >> >> >> candidates would be drivers/hardware sharing the IRQ >> >> >> >> 11: 135715 XT-PIC yenta, ohci1394, Intel ICH4, >> >> >> >> ehci_hcd, >> >> >> >> >> >> >> >> Try blacklisting these drivers. See >> >> >> >> http://linmodems.technion.ac.il/bigarch/archive-eighth/msg01842.ht >> >> >> >>ml on blacklisting guidance. >> >> >> >> >> >> >> >> MarvS >> >> >> >> >> >> >> >> > On Tuesday 24 June 2008 06:53 pm, Antonio Olivares wrote: >> >> >> >> >> Many things look fine, you have setup the modem correctly. AT >> >> >> >> >> least one problem is >> >> >> >> >> >> >> >> >> >> /**** scanModem output ****/ >> >> >> >> >> Modem interrupt assignment and sharing: >> >> >> >> >> 11: 135715 XT-PIC yenta, ohci1394, Intel ICH4, >> >> >> >> >> ehci_hcd, uhci_hcd, uhci_hcd, uhci_hcd, eth2, radeon@PCI:1:0:0, >> >> >> >> >> eth0 --- Bootup diagnostics for card in PCI slot 0000:00:1f.6 >> >> >> >> >> ---- ACPI: PCI interrupt 0000:00:1f.6[B] -> GSI 11 (level, low) >> >> >> >> >> -> IRQ 11 ACPI: PCI interrupt 0000:00:1f.6[B] -> GSI 11 (level, >> >> >> >> >> low) -> IRQ 11 >> >> >> > >> >> >> > Greetings: >> >> >> > >> >> >> > I tried creating an /etc/modprobe.d/blacklist.local file and >> >> >> > listing ohci1394 uhci_hcd and ehci_hcd but watching the boot >> >> >> > messages go by I saw "Ignoring bad line starting with 'blacklist'" >> >> >> > multiple times! Indeed it did ignore, lsmod shows them loaded. >> >> >> > >> >> >> > Any way around this? File blacklist.local has root permissions. >> >> >> > Isn't that correct? >> >> >> > >> >> >> > Elmer >
