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.html >> >> >> 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 >
