Re: cmc, UK kernel 2.6.32-22-generic

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Craig,

If you can access the bootup BIOS, try switching to the non-PNP mode,

Also among the drivers, these
ppdev
lp
parport
floppy
are probably non-essential and might be unloaded  or blacklisted to
free up resources.

MarvS



On Fri, May 28, 2010 at 8:16 AM, Craig McLaren <craigmc@xxxxxxxxxxxxx> wrote:
> So far in a attempt at resolving the resource conflict I've tried the
> following:-
>
> used the pollirq and pci=routeirq kernal bootup options
> downgraded to ubuntu 9.10
> disabled usb controller in bios
> tried different slots on motherboard
>
> Attached are the most recent ModemData, dmesg.txt files.
>
> On 27 May 2010 23:32, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote:
>> Craig
>>
>> The most outstanding problem is:
>>
>>  Modem interrupt assignment and sharing:
>>  16:          0          0   IO-APIC-fasteoi   uhci_hcd:usb3
>>  --- Bootup diagnostics for card in PCI slot 04:00.0 ----
>> [    0.567384] pci 0000:04:00.0: reg 10 32bit mmio: [0xfe5ffc00-0xfe5fffff]
>> [    1.915516] serial 0000:04:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
>> [    1.915521] serial 0000:04:00.0: PCI INT A disabled
>>
>> Enablement of the PCI slot 04:00.0 is necessary before there can be responses.
>>
>> There is resource competition from USB devices.
>> Detach them before bootup and again try
>> $ sudo wvdialconf
>>
>> Also read the BootUp.txt
>>
>> Please send to the List, not direct to me.
>>
>> MarvS
>>
>>
>> On Thu, May 27, 2010 at 9:03 AM, Craig McLaren <craigmc35@xxxxxxxxxxxxxx> wrote:
>>> Hi Marvin,
>>>
>>> wvdialconf failed with the output below:
>>>
>>> Editing `/etc/wvdial.conf'.
>>>
>>> Scanning your serial ports for a modem.
>>>
>>> ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
>>> ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
>>> ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
>>> Modem Port Scan<*1>: S1   S2   S3
>>>
>>>
>>> Sorry, no modem was detected!  Is it in use by another program?
>>> Did you configure it properly with setserial?
>>>
>>> Please read the FAQ at http://open.nit.ca/wiki/?WvDial
>>>
>>> If you still have problems, send mail to <wvdial-list@xxxxxxxxxxxx>.
>>>
>>>
>>> On 27 May 2010 13:42, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote:
>>>> Craig,
>>>>
>>>> See if it is detected by wvdialconf:
>>>> $ sudo wvdialconf
>>>>
>>>> MarvS
>>>>
>>>> On Thu, May 27, 2010 at 8:14 AM, Craig McLaren <craigmc35@xxxxxxxxxxxxxx> wrote:
>>>>> Hello All,  Please can someone advise what steps are necessary to get
>>>>> the USR802981-OEM modem working. I have two of these which I plan on
>>>>> using with Hylafax if they ever work.  At the moment the serial port
>>>>> does not appear to have been created although the device is listed
>>>>> when I run lspci.  I'm assuming they are compatible with Linux in some
>>>>> way as this is what it says on USR website:-
>>>>>
>>>>> http://www.usr.com/support/product-template.asp?prod=oem#2980
>>>>>
>>>>> Any help greatly appreciated.
>>>>>
>>>>>
>>>>> --
>>>>> Regards,
>>>>>
>>>>> Craig.
>>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Regards,
>>>
>>> Craig.
>>>
>>
>
>
>
> --
> Regards,
>
> Craig.
>



[Index of Archives]     [Linux Media Development]     [Asterisk]     [DCCP]     [Netdev]     [X.org]     [Xfree86]     [Fedora Women]     [Linux USB]

  Powered by Linux