Home » The PARIS Forums » PARIS: Main » still fighting for stability
| Re: still fighting for stability [message #72476 is a reply to message #72474] |
Fri, 15 September 2006 19:21   |
uptown jimmy
Messages: 441
Registered: September 2005
|
Senior Member |
|
|
Ummm, I'm sorta freaked out and wanting precision right now. You mean,
"That's the ticket", right?
"Aaron Allen" <know-spam@not_here.dude> wrote in message
news:450b5c7c@linux...
> That's your daisy.
> AA
>
> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> news:450b584d@linux...
>> The only thing I can see for this is to "clear the Real Time Clock RAM in
>> CMOS". This would "clear the CMOS memory of date, time, and system setup
>> parameters by erasing the CMOS RTC RAM data".
>>
>> This involves removing the onboard battery and moving jumper cap from
>> pins 1-2 to pins 2-3., then back to pins 1-2, then reinstalling the
>> battery. It says you have to enter the BIOS and re-enter data.
>>
>> Is this the thing to do?
>> "Martin Harrington" <lendan@bigpond.net.au> wrote in message
>> news:450b4d10@linux...
>>> All you need do is reset the BIOS by shorting out the relevant jumper on
>>> the motherboard...it's in the manual.
>>> --
>>> Martin Harrington
>>> www.lendanear-sound.com
>>>
>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
>>> news:450b4198@linux...
>>>>I disabledall but the com1 and lpt 1. Can't find them.
>>>>
>>>> Bad news is, and this is really bad news, computer won't boot up. On
>>>> that blcak page that n ow doesn't flash by so fast at all, I get the
>>>> error message "USB device over current status detected". Then the
>>>> computer shuts down. Won't boot up, won't let me go to BIOS to fix it.
>>>>
>>>> Heeeeeelp!
>>>>
>>>>
>>>> "John" <no@no.com> wrote in message news:450b3aac$1@linux...
>>>>> It looks like another messed up Asus manual. I downloaded the manual
>>>>> and on page 2-18 it has that pic. I would turn off Com1 (irq4),
>>>>> floppy (irq 6), lpt1 (irq 7), Serial port, turn off onboard audio and
>>>>> USB, Keep the LAN on so you can network but I would try only slots 3
>>>>> and 4 only first. Notice how they don't even show audio sharing with
>>>>> anything. This diagram is craptastic.
>>>>>
>>>>> And turn off Hyper Threading.
>>>>>
>>>>> Do ME and favor and call them on the phone and ask then what the hell
>>>>> is this diagram means. Simply, what slots share with what?
>>>>> Inquiring minds !
>>>>>
>>>>> John
>>>>>
>>>>> Uptown Jimmy wrote:
>>>>>> I guess I don't understand what the Alphabetized row indicates. In
>>>>>> other
>>>>>> words, if PCI slot 1 "shared" with 'F', what does that mean? What is
>>>>>> it
>>>>>> shared with?
>>>>>>
>>>>>>
>>>>>> "John" <no@no.com> wrote in message news:450af67f$1@linux...
>>>>>>> Use the second section that shows what are shared. Then make sure
>>>>>>> your
>>>>>> EDS
>>>>>>> cards are NOT on them. For example, turn off onboard audio in bios
>>>>>>> and
>>>>>>> now you can use the slot that shares with onboard audio. Any device
>>>>>>> that
>>>>>>> you are using like AGP video you DO NOT want an EDS card to be on a
>>>>>>> shared
>>>>>>> slot.
>>>>>>>
>>>>>>> On boot up check to make sure that the black screen that flashes by
>>>>>>> shows
>>>>>>> this correctly.
>>>>>>>
>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote:
>>>>>>>> Okay, on the IRQ page in the manual, it has two sections:
>>>>>>>>
>>>>>>>> 1. "Standard interrupt assignments", which list IRQ numbers and
>>>>>>>> their
>>>>>>>> "standard function". (This section does list 7 "IRQs are usually
>>>>>> available
>>>>>>>> for PCI devices")
>>>>>>>>
>>>>>>>> 2. "IRQ" assignments for this motherboard", which graphs various
>>>>>>>> PCI
>>>>>> slots
>>>>>>>> or USB controllers as "nil", "shared", or "used" against letters of
>>>>>>>> the
>>>>>>>> alphabet.
>>>>>>>>
>>>>>>>> I don't know how to use these two sets of data to resolve my
>>>>>>>> problem.
>>>>>> They
>>>>>>>> seem incompatible. I feel ignernt.
>>>>>>>>
>>>>>>>>
>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in message
>>>>>>>> news:450a0f48@linux...
>>>>>>>>> Hmmm.....well .......letsee.........ASUS boards normally will have
>>>>>>>>> the
>>>>>>> AGP
>>>>>>>>> sharing an IRQ with two PCI slots, basically making these
>>>>>>>>> worthless for
>>>>>>>>> anything else.
>>>>>>>>> How many PCI slots does your mobo have?
>>>>>>>>> If it's a 5 slot board and it's similar to an AMD board, chances
>>>>>>>>> are
>>>>>> that
>>>>>>>>> PCI slots 1 and 5 are shared with the AGP and the firewire port
>>>>>>>>> (thus
>>>>>>>> making
>>>>>>>>> FW audio interfaces iffy also if using the onboard FW)
>>>>>>>>>
>>>>>>>>> PCI slot 2 may share with your LAN controller
>>>>>>>>> PCI #3 may share with onboard RAID and SATA controller
>>>>>>>>> PCI 4 may not share with anything.
>>>>>>>>>
>>>>>>>>> This is the way the ASUS A8V mobo is configured but it's for AMD
>>>>>>>>> CPU's.
>>>>>>>>>
>>>>>>>>> Do you have the manual? All of this is listed in chapter 2 under
>>>>>>>>> the
>>>>>>>> heading
>>>>>>>>> Interrupt Assignments. It should be noted for Intel mobo's as
>>>>>>>>> well.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> If it's 6, try putting the EDS card in PCI 2, 3, 4 or 5
>>>>>>>>> If it's 5, try PCI slot 1,
>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
>>>>>>>>> news:4509fd03@linux...
>>>>>>>>>> It's an Asus P5P800 SE board with a Pentium 4 HT chip.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in message
>>>>>>>>>> news:4509f8fc@linux...
>>>>>>>>>>> What kind of mobo are you using Jimmy?
>>>>>>>>>>>
>>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
>>>>>>>>>>> news:4509eda3@linux...
>>>>>>>>>>>> I couldn't find any place where it indicated which IRQ the AGP
>>>>>>>>>>>> was
>>>>>>>>>>> assigned.
>>>>>>>>>>>> The IRQ page had all IRQs assigned to "PCI", and beneath that
>>>>>>>>>>>> all
>>>>>>> the
>>>>>>>>> PCI
>>>>>>>>>>>> slots all assigned to "AUTO". On another page the serial port
>>>>>>>>>>>> was
>>>>>>>>>>>> assigned
>>>>>>>>>>>> to IRQ 4, and the parallel port was assigned to IRQ 7. So I
>>>>>> assigned
>>>>>>>>> the
>>>>>>>>>>> PCI
>>>>>>>>>>>> slots to other numbers.
>>>>>>>>>>>>
>>>>>>>>>>>> Am I on the wrong track here?
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in message
>>>>>>>>>>>> news:4509da19@linux...
>>>>>>>>>>>>> Repeat after me:
>>>>>>>>>>>>>
>>>>>>>>>>>>> IRQ!! IRQ!! IRQ!!
>>>>>>>>>>>>>
>>>>>>>>>>>>> This sounds exactly like the EDS card is sharing and interrupt
>>>>>>> with
>>>>>>>>> the
>>>>>>>>>>>>> AGP
>>>>>>>>>>>>> slot.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
>>>>>>>>>>>>> news:45098f86$1@linux...
>>>>>>>>>>>>>> Hi-ho.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I am still having trouble with my Paris rig. In an effort to
>>>>>>>>> simplify
>>>>>>>>>>>>> things,
>>>>>>>>>>>>>> I only have one card installed, with an MEC attached,
>>>>>>>>>>>>>> internal
>>>>>>>>>>> clocking.
>>>>>>>>>>>>>> Basically, my problems are down to two:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 1.The "now-line" freezes, or more actually begins stuttering
>>>>>>>>>>>>>> in
>>>>>>>>>>> extremely
>>>>>>>>>>>>>> slow-motion, almost glacial. I can still change windows, and
>>>>>>>>>>>>>> I
>>>>>>> am
>>>>>>>>> able
>>>>>>>>>>> to
>>>>>>>>>>>>>> save and close, then re-open Paris with success.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> 2.On starting Paris, I get an error message: "I/O modules
>>>>>>>>>>>>>> used
>>>>>>> in
>>>>>>>>> this
>>>>>>>>>>>>> patch
>>>>>>>>>>>>>> setting not avaiable in this configuration of Paris.
>>>>>>>>>>>>>> Resulting
>>>>>>>> audio
>>>>>>>>>>> may
>>>>>>>>>>>>>> be different than when saved." This will pop up 2 or 4 times,
>>>>>>> and
>>>>>>>>> then
>>>>>>>>>>>>> when
>>>>>>>>>>>>>> I push "play" no audio is heard. Then I close, reopen, and
>>>>>>>>>>>>>> then
>>>>>>>>> things
>>>>>>>>>>>>> work
>>>>>>>>>>>>>> for a while.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I have made some tweaks to the configuration with some
>>>>>>>>>>>>>> success.
>>>>>>>> The
>>>>>>>>>>>>>> errors
>>>>>>>>>>>>>> are happening less and less, but they still pop up.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Anybody?
>>>>>>>>>>>>>> Jimmy
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>
>>>
>>>
>>
>>
>
>
|
|
|
|
| Re: still fighting for stability [message #72478 is a reply to message #72476] |
Fri, 15 September 2006 19:33 |
Aaron Allen
Messages: 1988
Registered: May 2008
|
Senior Member |
|
|
yup
"Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
news:450b5d6b@linux...
> Ummm, I'm sorta freaked out and wanting precision right now. You mean,
> "That's the ticket", right?
>
>
> "Aaron Allen" <know-spam@not_here.dude> wrote in message
> news:450b5c7c@linux...
>> That's your daisy.
>> AA
>>
>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
>> news:450b584d@linux...
>>> The only thing I can see for this is to "clear the Real Time Clock RAM
>>> in CMOS". This would "clear the CMOS memory of date, time, and system
>>> setup parameters by erasing the CMOS RTC RAM data".
>>>
>>> This involves removing the onboard battery and moving jumper cap from
>>> pins 1-2 to pins 2-3., then back to pins 1-2, then reinstalling the
>>> battery. It says you have to enter the BIOS and re-enter data.
>>>
>>> Is this the thing to do?
>>> "Martin Harrington" <lendan@bigpond.net.au> wrote in message
>>> news:450b4d10@linux...
>>>> All you need do is reset the BIOS by shorting out the relevant jumper
>>>> on the motherboard...it's in the manual.
>>>> --
>>>> Martin Harrington
>>>> www.lendanear-sound.com
>>>>
>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
>>>> news:450b4198@linux...
>>>>>I disabledall but the com1 and lpt 1. Can't find them.
>>>>>
>>>>> Bad news is, and this is really bad news, computer won't boot up. On
>>>>> that blcak page that n ow doesn't flash by so fast at all, I get the
>>>>> error message "USB device over current status detected". Then the
>>>>> computer shuts down. Won't boot up, won't let me go to BIOS to fix it.
>>>>>
>>>>> Heeeeeelp!
>>>>>
>>>>>
>>>>> "John" <no@no.com> wrote in message news:450b3aac$1@linux...
>>>>>> It looks like another messed up Asus manual. I downloaded the
>>>>>> manual and on page 2-18 it has that pic. I would turn off Com1
>>>>>> (irq4), floppy (irq 6), lpt1 (irq 7), Serial port, turn off onboard
>>>>>> audio and USB, Keep the LAN on so you can network but I would try
>>>>>> only slots 3 and 4 only first. Notice how they don't even show audio
>>>>>> sharing with anything. This diagram is craptastic.
>>>>>>
>>>>>> And turn off Hyper Threading.
>>>>>>
>>>>>> Do ME and favor and call them on the phone and ask then what the hell
>>>>>> is this diagram means. Simply, what slots share with what?
>>>>>> Inquiring minds !
>>>>>>
>>>>>> John
>>>>>>
>>>>>> Uptown Jimmy wrote:
>>>>>>> I guess I don't understand what the Alphabetized row indicates. In
>>>>>>> other
>>>>>>> words, if PCI slot 1 "shared" with 'F', what does that mean? What is
>>>>>>> it
>>>>>>> shared with?
>>>>>>>
>>>>>>>
>>>>>>> "John" <no@no.com> wrote in message news:450af67f$1@linux...
>>>>>>>> Use the second section that shows what are shared. Then make sure
>>>>>>>> your
>>>>>>> EDS
>>>>>>>> cards are NOT on them. For example, turn off onboard audio in
>>>>>>>> bios and
>>>>>>>> now you can use the slot that shares with onboard audio. Any
>>>>>>>> device that
>>>>>>>> you are using like AGP video you DO NOT want an EDS card to be on a
>>>>>>>> shared
>>>>>>>> slot.
>>>>>>>>
>>>>>>>> On boot up check to make sure that the black screen that flashes by
>>>>>>>> shows
>>>>>>>> this correctly.
>>>>>>>>
>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote:
>>>>>>>>> Okay, on the IRQ page in the manual, it has two sections:
>>>>>>>>>
>>>>>>>>> 1. "Standard interrupt assignments", which list IRQ numbers and
>>>>>>>>> their
>>>>>>>>> "standard function". (This section does list 7 "IRQs are usually
>>>>>>> available
>>>>>>>>> for PCI devices")
>>>>>>>>>
>>>>>>>>> 2. "IRQ" assignments for this motherboard", which graphs various
>>>>>>>>> PCI
>>>>>>> slots
>>>>>>>>> or USB controllers as "nil", "shared", or "used" against letters
>>>>>>>>> of the
>>>>>>>>> alphabet.
>>>>>>>>>
>>>>>>>>> I don't know how to use these two sets of data to resolve my
>>>>>>>>> problem.
>>>>>>> They
>>>>>>>>> seem incompatible. I feel ignernt.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in message
>>>>>>>>> news:450a0f48@linux...
>>>>>>>>>> Hmmm.....well .......letsee.........ASUS boards normally will
>>>>>>>>>> have the
>>>>>>>> AGP
>>>>>>>>>> sharing an IRQ with two PCI slots, basically making these
>>>>>>>>>> worthless for
>>>>>>>>>> anything else.
>>>>>>>>>> How many PCI slots does your mobo have?
>>>>>>>>>> If it's a 5 slot board and it's similar to an AMD board, chances
>>>>>>>>>> are
>>>>>>> that
>>>>>>>>>> PCI slots 1 and 5 are shared with the AGP and the firewire port
>>>>>>>>>> (thus
>>>>>>>>> making
>>>>>>>>>> FW audio interfaces iffy also if using the onboard FW)
>>>>>>>>>>
>>>>>>>>>> PCI slot 2 may share with your LAN controller
>>>>>>>>>> PCI #3 may share with onboard RAID and SATA controller
>>>>>>>>>> PCI 4 may not share with anything.
>>>>>>>>>>
>>>>>>>>>> This is the way the ASUS A8V mobo is configured but it's for AMD
>>>>>>>>>> CPU's.
>>>>>>>>>>
>>>>>>>>>> Do you have the manual? All of this is listed in chapter 2 under
>>>>>>>>>> the
>>>>>>>>> heading
>>>>>>>>>> Interrupt Assignments. It should be noted for Intel mobo's as
>>>>>>>>>> well.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> If it's 6, try putting the EDS card in PCI 2, 3, 4 or 5
>>>>>>>>>> If it's 5, try PCI slot 1,
>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
>>>>>>>>>> news:4509fd03@linux...
>>>>>>>>>>> It's an Asus P5P800 SE board with a Pentium 4 HT chip.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in message
>>>>>>>>>>> news:4509f8fc@linux...
>>>>>>>>>>>> What kind of mobo are you using Jimmy?
>>>>>>>>>>>>
>>>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
>>>>>>>>>>>> news:4509eda3@linux...
>>>>>>>>>>>>> I couldn't find any place where it indicated which IRQ the AGP
>>>>>>>>>>>>> was
>>>>>>>>>>>> assigned.
>>>>>>>>>>>>> The IRQ page had all IRQs assigned to "PCI", and beneath that
>>>>>>>>>>>>> all
>>>>>>>> the
>>>>>>>>>> PCI
>>>>>>>>>>>>> slots all assigned to "AUTO". On another page the serial port
>>>>>>>>>>>>> was
>>>>>>>>>>>>> assigned
>>>>>>>>>>>>> to IRQ 4, and the parallel port was assigned to IRQ 7. So I
>>>>>>> assigned
>>>>>>>>>> the
>>>>>>>>>>>> PCI
>>>>>>>>>>>>> slots to other numbers.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Am I on the wrong track here?
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in message
>>>>>>>>>>>>> news:4509da19@linux...
>>>>>>>>>>>>>> Repeat after me:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> IRQ!! IRQ!! IRQ!!
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> This sounds exactly like the EDS card is sharing and
>>>>>>>>>>>>>> interrupt
>>>>>>>> with
>>>>>>>>>> the
>>>>>>>>>>>>>> AGP
>>>>>>>>>>>>>> slot.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
>>>>>>>>>>>>>> news:45098f86$1@linux...
>>>>>>>>>>>>>>> Hi-ho.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I am still having trouble with my Paris rig. In an effort to
>>>>>>>>>> simplify
>>>>>>>>>>>>>> things,
>>>>>>>>>>>>>>> I only have one card installed, with an MEC attached,
>>>>>>>>>>>>>>> internal
>>>>>>>>>>>> clocking.
>>>>>>>>>>>>>>> Basically, my problems are down to two:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 1.The "now-line" freezes, or more actually begins stuttering
>>>>>>>>>>>>>>> in
>>>>>>>>>>>> extremely
>>>>>>>>>>>>>>> slow-motion, almost glacial. I can still change windows, and
>>>>>>>>>>>>>>> I
>>>>>>>> am
>>>>>>>>>> able
>>>>>>>>>>>> to
>>>>>>>>>>>>>>> save and close, then re-open Paris with success.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 2.On starting Paris, I get an error message: "I/O modules
>>>>>>>>>>>>>>> used
>>>>>>>> in
>>>>>>>>>> this
>>>>>>>>>>>>>> patch
>>>>>>>>>>>>>>> setting not avaiable in this configuration of Paris.
>>>>>>>>>>>>>>> Resulting
>>>>>>>>> audio
>>>>>>>>>>>> may
>>>>>>>>>>>>>>> be different than when saved." This will pop up 2 or 4
>>>>>>>>>>>>>>> times,
>>>>>>>> and
>>>>>>>>>> then
>>>>>>>>>>>>>> when
>>>>>>>>>>>>>>> I push "play" no audio is heard. Then I close, reopen, and
>>>>>>>>>>>>>>> then
>>>>>>>>>> things
>>>>>>>>>>>>>> work
>>>>>>>>>>>>>>> for a while.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I have made some tweaks to the configuration with some
>>>>>>>>>>>>>>> success.
>>>>>>>>> The
>>>>>>>>>>>>>>> errors
>>>>>>>>>>>>>>> are happening less and less, but they still pop up.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Anybody?
>>>>>>>>>>>>>>> Jimmy
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
|
|
|
|
| Re: still fighting for stability [message #72480 is a reply to message #72478] |
Fri, 15 September 2006 21:42 |
uptown jimmy
Messages: 441
Registered: September 2005
|
Senior Member |
|
|
Alrighty. then. I tried the battery/jumper-cap thingie with great success.
Booted right up, with obvious changes to BIOS and VGA buffers and all else.
Then I made a few of the various previously suggested BIOS changes with
which I felt comfortable and got 1 hr 15 minutes of good, vital work done.
I've had a few different troubles these past few days (months). Tonight I
have tried a various few fixes, and experienced some vexing troubles and
corresponding victories, but I haven't had time tonight to really
stress-test things. I'm not convinced that things are tight yet, as I've
been far too bedeviled in recent days to relax now without several
sessions-worth of hard use.
Gotta session off-site tomorrow (Swen's studio), so I'll be back on my own
rig Sunday (yay NFL football!).
I just want to thank everybody here for their sincere and dilligent efforts
in helping an ignernt fellow like myself. I wish I could make all of you a
big banquet dinner in thanks. I'm a damn fine cook, just not so much a damn
fine computer tech.
I figure I'll start a new thread if things aren't right yet. I got us off on
a defective-BIOS tangent there.....the rig did feel pretty good there for an
hour or so, though.....
Jimmy
"Aaron Allen" <know-spam@not_here.dude> wrote in message
news:450b60d5@linux...
> yup
>
> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> news:450b5d6b@linux...
>> Ummm, I'm sorta freaked out and wanting precision right now. You mean,
>> "That's the ticket", right?
>>
>>
>> "Aaron Allen" <know-spam@not_here.dude> wrote in message
>> news:450b5c7c@linux...
>>> That's your daisy.
>>> AA
>>>
>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
>>> news:450b584d@linux...
>>>> The only thing I can see for this is to "clear the Real Time Clock RAM
>>>> in CMOS". This would "clear the CMOS memory of date, time, and system
>>>> setup parameters by erasing the CMOS RTC RAM data".
>>>>
>>>> This involves removing the onboard battery and moving jumper cap from
>>>> pins 1-2 to pins 2-3., then back to pins 1-2, then reinstalling the
>>>> battery. It says you have to enter the BIOS and re-enter data.
>>>>
>>>> Is this the thing to do?
>>>> "Martin Harrington" <lendan@bigpond.net.au> wrote in message
>>>> news:450b4d10@linux...
>>>>> All you need do is reset the BIOS by shorting out the relevant jumper
>>>>> on the motherboard...it's in the manual.
>>>>> --
>>>>> Martin Harrington
>>>>> www.lendanear-sound.com
>>>>>
>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
>>>>> news:450b4198@linux...
>>>>>>I disabledall but the com1 and lpt 1. Can't find them.
>>>>>>
>>>>>> Bad news is, and this is really bad news, computer won't boot up. On
>>>>>> that blcak page that n ow doesn't flash by so fast at all, I get the
>>>>>> error message "USB device over current status detected". Then the
>>>>>> computer shuts down. Won't boot up, won't let me go to BIOS to fix
>>>>>> it.
>>>>>>
>>>>>> Heeeeeelp!
>>>>>>
>>>>>>
>>>>>> "John" <no@no.com> wrote in message news:450b3aac$1@linux...
>>>>>>> It looks like another messed up Asus manual. I downloaded the
>>>>>>> manual and on page 2-18 it has that pic. I would turn off Com1
>>>>>>> (irq4), floppy (irq 6), lpt1 (irq 7), Serial port, turn off onboard
>>>>>>> audio and USB, Keep the LAN on so you can network but I would try
>>>>>>> only slots 3 and 4 only first. Notice how they don't even show audio
>>>>>>> sharing with anything. This diagram is craptastic.
>>>>>>>
>>>>>>> And turn off Hyper Threading.
>>>>>>>
>>>>>>> Do ME and favor and call them on the phone and ask then what the
>>>>>>> hell is this diagram means. Simply, what slots share with what?
>>>>>>> Inquiring minds !
>>>>>>>
>>>>>>> John
>>>>>>>
>>>>>>> Uptown Jimmy wrote:
>>>>>>>> I guess I don't understand what the Alphabetized row indicates. In
>>>>>>>> other
>>>>>>>> words, if PCI slot 1 "shared" with 'F', what does that mean? What
>>>>>>>> is it
>>>>>>>> shared with?
>>>>>>>>
>>>>>>>>
>>>>>>>> "John" <no@no.com> wrote in message news:450af67f$1@linux...
>>>>>>>>> Use the second section that shows what are shared. Then make sure
>>>>>>>>> your
>>>>>>>> EDS
>>>>>>>>> cards are NOT on them. For example, turn off onboard audio in
>>>>>>>>> bios and
>>>>>>>>> now you can use the slot that shares with onboard audio. Any
>>>>>>>>> device that
>>>>>>>>> you are using like AGP video you DO NOT want an EDS card to be on
>>>>>>>>> a shared
>>>>>>>>> slot.
>>>>>>>>>
>>>>>>>>> On boot up check to make sure that the black screen that flashes
>>>>>>>>> by shows
>>>>>>>>> this correctly.
>>>>>>>>>
>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote:
>>>>>>>>>> Okay, on the IRQ page in the manual, it has two sections:
>>>>>>>>>>
>>>>>>>>>> 1. "Standard interrupt assignments", which list IRQ numbers and
>>>>>>>>>> their
>>>>>>>>>> "standard function". (This section does list 7 "IRQs are usually
>>>>>>>> available
>>>>>>>>>> for PCI devices")
>>>>>>>>>>
>>>>>>>>>> 2. "IRQ" assignments for this motherboard", which graphs various
>>>>>>>>>> PCI
>>>>>>>> slots
>>>>>>>>>> or USB controllers as "nil", "shared", or "used" against letters
>>>>>>>>>> of the
>>>>>>>>>> alphabet.
>>>>>>>>>>
>>>>>>>>>> I don't know how to use these two sets of data to resolve my
>>>>>>>>>> problem.
>>>>>>>> They
>>>>>>>>>> seem incompatible. I feel ignernt.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in message
>>>>>>>>>> news:450a0f48@linux...
>>>>>>>>>>> Hmmm.....well .......letsee.........ASUS boards normally will
>>>>>>>>>>> have the
>>>>>>>>> AGP
>>>>>>>>>>> sharing an IRQ with two PCI slots, basically making these
>>>>>>>>>>> worthless for
>>>>>>>>>>> anything else.
>>>>>>>>>>> How many PCI slots does your mobo have?
>>>>>>>>>>> If it's a 5 slot board and it's similar to an AMD board, chances
>>>>>>>>>>> are
>>>>>>>> that
>>>>>>>>>>> PCI slots 1 and 5 are shared with the AGP and the firewire port
>>>>>>>>>>> (thus
>>>>>>>>>> making
>>>>>>>>>>> FW audio interfaces iffy also if using the onboard FW)
>>>>>>>>>>>
>>>>>>>>>>> PCI slot 2 may share with your LAN controller
>>>>>>>>>>> PCI #3 may share with onboard RAID and SATA controller
>>>>>>>>>>> PCI 4 may not share with anything.
>>>>>>>>>>>
>>>>>>>>>>> This is the way the ASUS A8V mobo is configured but it's for AMD
>>>>>>>>>>> CPU's.
>>>>>>>>>>>
>>>>>>>>>>> Do you have the manual? All of this is listed in chapter 2 under
>>>>>>>>>>> the
>>>>>>>>>> heading
>>>>>>>>>>> Interrupt Assignments. It should be noted for Intel mobo's as
>>>>>>>>>>> well.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> If it's 6, try putting the EDS card in PCI 2, 3, 4 or 5
>>>>>>>>>>> If it's 5, try PCI slot 1,
>>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
>>>>>>>>>>> news:4509fd03@linux...
>>>>>>>>>>>> It's an Asus P5P800 SE board with a Pentium 4 HT chip.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in message
>>>>>>>>>>>> news:4509f8fc@linux...
>>>>>>>>>>>>> What kind of mobo are you using Jimmy?
>>>>>>>>>>>>>
>>>>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
>>>>>>>>>>>>> news:4509eda3@linux...
>>>>>>>>>>>>>> I couldn't find any place where it indicated which IRQ the
>>>>>>>>>>>>>> AGP was
>>>>>>>>>>>>> assigned.
>>>>>>>>>>>>>> The IRQ page had all IRQs assigned to "PCI", and beneath that
>>>>>>>>>>>>>> all
>>>>>>>>> the
>>>>>>>>>>> PCI
>>>>>>>>>>>>>> slots all assigned to "AUTO". On another page the serial port
>>>>>>>>>>>>>> was
>>>>>>>>>>>>>> assigned
>>>>>>>>>>>>>> to IRQ 4, and the parallel port was assigned to IRQ 7. So I
>>>>>>>> assigned
>>>>>>>>>>> the
>>>>>>>>>>>>> PCI
>>>>>>>>>>>>>> slots to other numbers.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Am I on the wrong track here?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in message
>>>>>>>>>>>>>> news:4509da19@linux...
>>>>>>>>>>>>>>> Repeat after me:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> IRQ!! IRQ!! IRQ!!
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> This sounds exactly like the EDS card is sharing and
>>>>>>>>>>>>>>> interrupt
>>>>>>>>> with
>>>>>>>>>>> the
>>>>>>>>>>>>>>> AGP
>>>>>>>>>>>>>>> slot.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
>>>>>>>>>>>>>>> news:45098f86$1@linux...
>>>>>>>>>>>>>>>> Hi-ho.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I am still having trouble with my Paris rig. In an effort
>>>>>>>>>>>>>>>> to
>>>>>>>>>>> simplify
>>>>>>>>>>>>>>> things,
>>>>>>>>>>>>>>>> I only have one card installed, with an MEC attached,
>>>>>>>>>>>>>>>> internal
>>>>>>>>>>>>> clocking.
>>>>>>>>>>>>>>>> Basically, my problems are down to two:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 1.The "now-line" freezes, or more actually begins
>>>>>>>>>>>>>>>> stuttering in
>>>>>>>>>>>>> extremely
>>>>>>>>>>>>>>>> slow-motion, almost glacial. I can still change windows,
>>>>>>>>>>>>>>>> and I
>>>>>>>>> am
>>>>>>>>>>> able
>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>> save and close, then re-open Paris with success.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> 2.On starting Paris, I get an error message: "I/O modules
>>>>>>>>>>>>>>>> used
>>>>>>>>> in
>>>>>>>>>>> this
>>>>>>>>>>>>>>> patch
>>>>>>>>>>>>>>>> setting not avaiable in this configuration of Paris.
>>>>>>>>>>>>>>>> Resulting
>>>>>>>>>> audio
>>>>>>>>>>>>> may
>>>>>>>>>>>>>>>> be different than when saved." This will pop up 2 or 4
>>>>>>>>>>>>>>>> times,
>>>>>>>>> and
>>>>>>>>>>> then
>>>>>>>>>>>>>>> when
>>>>>>>>>>>>>>>> I push "play" no audio is heard. Then I close, reopen, and
>>>>>>>>>>>>>>>> then
>>>>>>>>>>> things
>>>>>>>>>>>>>>> work
>>>>>>>>>>>>>>>> for a while.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I have made some tweaks to the configuration with some
>>>>>>>>>>>>>>>> success.
>>>>>>>>>> The
>>>>>>>>>>>>>>>> errors
>>>>>>>>>>>>>>>> are happening less and less, but they still pop up.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Anybody?
>>>>>>>>>>>>>>>> Jimmy
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
|
|
|
|
| Re: still fighting for stability [message #72482 is a reply to message #72469] |
Fri, 15 September 2006 22:38 |
Martin Harrington
Messages: 560
Registered: September 2005
|
Senior Member |
|
|
That's the one....don't be afraid
--
Martin Harrington
www.lendanear-sound.com
"Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
news:450b584d@linux...
> The only thing I can see for this is to "clear the Real Time Clock RAM in
> CMOS". This would "clear the CMOS memory of date, time, and system setup
> parameters by erasing the CMOS RTC RAM data".
>
> This involves removing the onboard battery and moving jumper cap from pins
> 1-2 to pins 2-3., then back to pins 1-2, then reinstalling the battery. It
> says you have to enter the BIOS and re-enter data.
>
> Is this the thing to do?
> "Martin Harrington" <lendan@bigpond.net.au> wrote in message
> news:450b4d10@linux...
>> All you need do is reset the BIOS by shorting out the relevant jumper on
>> the motherboard...it's in the manual.
>> --
>> Martin Harrington
>> www.lendanear-sound.com
>>
>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
>> news:450b4198@linux...
>>>I disabledall but the com1 and lpt 1. Can't find them.
>>>
>>> Bad news is, and this is really bad news, computer won't boot up. On
>>> that blcak page that n ow doesn't flash by so fast at all, I get the
>>> error message "USB device over current status detected". Then the
>>> computer shuts down. Won't boot up, won't let me go to BIOS to fix it.
>>>
>>> Heeeeeelp!
>>>
>>>
>>> "John" <no@no.com> wrote in message news:450b3aac$1@linux...
>>>> It looks like another messed up Asus manual. I downloaded the manual
>>>> and on page 2-18 it has that pic. I would turn off Com1 (irq4), floppy
>>>> (irq 6), lpt1 (irq 7), Serial port, turn off onboard audio and USB,
>>>> Keep the LAN on so you can network but I would try only slots 3 and 4
>>>> only first. Notice how they don't even show audio sharing with
>>>> anything. This diagram is craptastic.
>>>>
>>>> And turn off Hyper Threading.
>>>>
>>>> Do ME and favor and call them on the phone and ask then what the hell
>>>> is this diagram means. Simply, what slots share with what? Inquiring
>>>> minds !
>>>>
>>>> John
>>>>
>>>> Uptown Jimmy wrote:
>>>>> I guess I don't understand what the Alphabetized row indicates. In
>>>>> other
>>>>> words, if PCI slot 1 "shared" with 'F', what does that mean? What is
>>>>> it
>>>>> shared with?
>>>>>
>>>>>
>>>>> "John" <no@no.com> wrote in message news:450af67f$1@linux...
>>>>>> Use the second section that shows what are shared. Then make sure
>>>>>> your
>>>>> EDS
>>>>>> cards are NOT on them. For example, turn off onboard audio in bios
>>>>>> and
>>>>>> now you can use the slot that shares with onboard audio. Any device
>>>>>> that
>>>>>> you are using like AGP video you DO NOT want an EDS card to be on a
>>>>>> shared
>>>>>> slot.
>>>>>>
>>>>>> On boot up check to make sure that the black screen that flashes by
>>>>>> shows
>>>>>> this correctly.
>>>>>>
>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote:
>>>>>>> Okay, on the IRQ page in the manual, it has two sections:
>>>>>>>
>>>>>>> 1. "Standard interrupt assignments", which list IRQ numbers and
>>>>>>> their
>>>>>>> "standard function". (This section does list 7 "IRQs are usually
>>>>> available
>>>>>>> for PCI devices")
>>>>>>>
>>>>>>> 2. "IRQ" assignments for this motherboard", which graphs various PCI
>>>>> slots
>>>>>>> or USB controllers as "nil", "shared", or "used" against letters of
>>>>>>> the
>>>>>>> alphabet.
>>>>>>>
>>>>>>> I don't know how to use these two sets of data to resolve my
>>>>>>> problem.
>>>>> They
>>>>>>> seem incompatible. I feel ignernt.
>>>>>>>
>>>>>>>
>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in message
>>>>>>> news:450a0f48@linux...
>>>>>>>> Hmmm.....well .......letsee.........ASUS boards normally will have
>>>>>>>> the
>>>>>> AGP
>>>>>>>> sharing an IRQ with two PCI slots, basically making these worthless
>>>>>>>> for
>>>>>>>> anything else.
>>>>>>>> How many PCI slots does your mobo have?
>>>>>>>> If it's a 5 slot board and it's similar to an AMD board, chances
>>>>>>>> are
>>>>> that
>>>>>>>> PCI slots 1 and 5 are shared with the AGP and the firewire port
>>>>>>>> (thus
>>>>>>> making
>>>>>>>> FW audio interfaces iffy also if using the onboard FW)
>>>>>>>>
>>>>>>>> PCI slot 2 may share with your LAN controller
>>>>>>>> PCI #3 may share with onboard RAID and SATA controller
>>>>>>>> PCI 4 may not share with anything.
>>>>>>>>
>>>>>>>> This is the way the ASUS A8V mobo is configured but it's for AMD
>>>>>>>> CPU's.
>>>>>>>>
>>>>>>>> Do you have the manual? All of this is listed in chapter 2 under
>>>>>>>> the
>>>>>>> heading
>>>>>>>> Interrupt Assignments. It should be noted for Intel mobo's as well.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> If it's 6, try putting the EDS card in PCI 2, 3, 4 or 5
>>>>>>>> If it's 5, try PCI slot 1,
>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
>>>>>>>> news:4509fd03@linux...
>>>>>>>>> It's an Asus P5P800 SE board with a Pentium 4 HT chip.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in message
>>>>>>>>> news:4509f8fc@linux...
>>>>>>>>>> What kind of mobo are you using Jimmy?
>>>>>>>>>>
>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
>>>>>>>>>> news:4509eda3@linux...
>>>>>>>>>>> I couldn't find any place where it indicated which IRQ the AGP
>>>>>>>>>>> was
>>>>>>>>>> assigned.
>>>>>>>>>>> The IRQ page had all IRQs assigned to "PCI", and beneath that
>>>>>>>>>>> all
>>>>>> the
>>>>>>>> PCI
>>>>>>>>>>> slots all assigned to "AUTO". On another page the serial port
>>>>>>>>>>> was
>>>>>>>>>>> assigned
>>>>>>>>>>> to IRQ 4, and the parallel port was assigned to IRQ 7. So I
>>>>> assigned
>>>>>>>> the
>>>>>>>>>> PCI
>>>>>>>>>>> slots to other numbers.
>>>>>>>>>>>
>>>>>>>>>>> Am I on the wrong track here?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in message
>>>>>>>>>>> news:4509da19@linux...
>>>>>>>>>>>> Repeat after me:
>>>>>>>>>>>>
>>>>>>>>>>>> IRQ!! IRQ!! IRQ!!
>>>>>>>>>>>>
>>>>>>>>>>>> This sounds exactly like the EDS card is sharing and interrupt
>>>>>> with
>>>>>>>> the
>>>>>>>>>>>> AGP
>>>>>>>>>>>> slot.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
>>>>>>>>>>>> news:45098f86$1@linux...
>>>>>>>>>>>>> Hi-ho.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I am still having trouble with my Paris rig. In an effort to
>>>>>>>> simplify
>>>>>>>>>>>> things,
>>>>>>>>>>>>> I only have one card installed, with an MEC attached, internal
>>>>>>>>>> clocking.
>>>>>>>>>>>>> Basically, my problems are down to two:
>>>>>>>>>>>>>
>>>>>>>>>>>>> 1.The "now-line" freezes, or more actually begins stuttering
>>>>>>>>>>>>> in
>>>>>>>>>> extremely
>>>>>>>>>>>>> slow-motion, almost glacial. I can still change windows, and I
>>>>>> am
>>>>>>>> able
>>>>>>>>>> to
>>>>>>>>>>>>> save and close, then re-open Paris with success.
>>>>>>>>>>>>>
>>>>>>>>>>>>> 2.On starting Paris, I get an error message: "I/O modules used
>>>>>> in
>>>>>>>> this
>>>>>>>>>>>> patch
>>>>>>>>>>>>> setting not avaiable in this configuration of Paris. Resulting
>>>>>>> audio
>>>>>>>>>> may
>>>>>>>>>>>>> be different than when saved." This will pop up 2 or 4 times,
>>>>>> and
>>>>>>>> then
>>>>>>>>>>>> when
>>>>>>>>>>>>> I push "play" no audio is heard. Then I close, reopen, and
>>>>>>>>>>>>> then
>>>>>>>> things
>>>>>>>>>>>> work
>>>>>>>>>>>>> for a while.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I have made some tweaks to the configuration with some
>>>>>>>>>>>>> success.
>>>>>>> The
>>>>>>>>>>>>> errors
>>>>>>>>>>>>> are happening less and less, but they still pop up.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Anybody?
>>>>>>>>>>>>> Jimmy
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>
>>>
>>
>>
>
>
|
|
|
|
| Re: still fighting for stability [message #72485 is a reply to message #72480] |
Fri, 15 September 2006 22:48 |
Deej [1]
Messages: 2149
Registered: January 2006
|
Senior Member |
|
|
Jimmy,
Glad you're getting this resolved. At your earliest opportunity, get rid of
that bios and go back to the one previous to the USB overcurrent warning.
Really man. That bios you're running right now is a disaster waiting for a
place to happen, and happen, and happen again.....I promise. It's going to
bite you at the worst time and you're going to have to continuously clear
the CMOS to get your machine to function as long as you're running that
bios. Nothing worse than a computer that won't boot.
Deej
"Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
news:450b7e60@linux...
> Alrighty. then. I tried the battery/jumper-cap thingie with great success.
> Booted right up, with obvious changes to BIOS and VGA buffers and all
else.
>
> Then I made a few of the various previously suggested BIOS changes with
> which I felt comfortable and got 1 hr 15 minutes of good, vital work done.
>
> I've had a few different troubles these past few days (months). Tonight I
> have tried a various few fixes, and experienced some vexing troubles and
> corresponding victories, but I haven't had time tonight to really
> stress-test things. I'm not convinced that things are tight yet, as I've
> been far too bedeviled in recent days to relax now without several
> sessions-worth of hard use.
>
> Gotta session off-site tomorrow (Swen's studio), so I'll be back on my own
> rig Sunday (yay NFL football!).
>
> I just want to thank everybody here for their sincere and dilligent
efforts
> in helping an ignernt fellow like myself. I wish I could make all of you a
> big banquet dinner in thanks. I'm a damn fine cook, just not so much a
damn
> fine computer tech.
>
> I figure I'll start a new thread if things aren't right yet. I got us off
on
> a defective-BIOS tangent there.....the rig did feel pretty good there for
an
> hour or so, though.....
>
> Jimmy
>
>
> "Aaron Allen" <know-spam@not_here.dude> wrote in message
> news:450b60d5@linux...
> > yup
> >
> > "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> > news:450b5d6b@linux...
> >> Ummm, I'm sorta freaked out and wanting precision right now. You mean,
> >> "That's the ticket", right?
> >>
> >>
> >> "Aaron Allen" <know-spam@not_here.dude> wrote in message
> >> news:450b5c7c@linux...
> >>> That's your daisy.
> >>> AA
> >>>
> >>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> >>> news:450b584d@linux...
> >>>> The only thing I can see for this is to "clear the Real Time Clock
RAM
> >>>> in CMOS". This would "clear the CMOS memory of date, time, and system
> >>>> setup parameters by erasing the CMOS RTC RAM data".
> >>>>
> >>>> This involves removing the onboard battery and moving jumper cap from
> >>>> pins 1-2 to pins 2-3., then back to pins 1-2, then reinstalling the
> >>>> battery. It says you have to enter the BIOS and re-enter data.
> >>>>
> >>>> Is this the thing to do?
> >>>> "Martin Harrington" <lendan@bigpond.net.au> wrote in message
> >>>> news:450b4d10@linux...
> >>>>> All you need do is reset the BIOS by shorting out the relevant
jumper
> >>>>> on the motherboard...it's in the manual.
> >>>>> --
> >>>>> Martin Harrington
> >>>>> www.lendanear-sound.com
> >>>>>
> >>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> >>>>> news:450b4198@linux...
> >>>>>>I disabledall but the com1 and lpt 1. Can't find them.
> >>>>>>
> >>>>>> Bad news is, and this is really bad news, computer won't boot up.
On
> >>>>>> that blcak page that n ow doesn't flash by so fast at all, I get
the
> >>>>>> error message "USB device over current status detected". Then the
> >>>>>> computer shuts down. Won't boot up, won't let me go to BIOS to fix
> >>>>>> it.
> >>>>>>
> >>>>>> Heeeeeelp!
> >>>>>>
> >>>>>>
> >>>>>> "John" <no@no.com> wrote in message news:450b3aac$1@linux...
> >>>>>>> It looks like another messed up Asus manual. I downloaded the
> >>>>>>> manual and on page 2-18 it has that pic. I would turn off Com1
> >>>>>>> (irq4), floppy (irq 6), lpt1 (irq 7), Serial port, turn off
onboard
> >>>>>>> audio and USB, Keep the LAN on so you can network but I would try
> >>>>>>> only slots 3 and 4 only first. Notice how they don't even show
audio
> >>>>>>> sharing with anything. This diagram is craptastic.
> >>>>>>>
> >>>>>>> And turn off Hyper Threading.
> >>>>>>>
> >>>>>>> Do ME and favor and call them on the phone and ask then what the
> >>>>>>> hell is this diagram means. Simply, what slots share with what?
> >>>>>>> Inquiring minds !
> >>>>>>>
> >>>>>>> John
> >>>>>>>
> >>>>>>> Uptown Jimmy wrote:
> >>>>>>>> I guess I don't understand what the Alphabetized row indicates.
In
> >>>>>>>> other
> >>>>>>>> words, if PCI slot 1 "shared" with 'F', what does that mean? What
> >>>>>>>> is it
> >>>>>>>> shared with?
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> "John" <no@no.com> wrote in message news:450af67f$1@linux...
> >>>>>>>>> Use the second section that shows what are shared. Then make
sure
> >>>>>>>>> your
> >>>>>>>> EDS
> >>>>>>>>> cards are NOT on them. For example, turn off onboard audio in
> >>>>>>>>> bios and
> >>>>>>>>> now you can use the slot that shares with onboard audio. Any
> >>>>>>>>> device that
> >>>>>>>>> you are using like AGP video you DO NOT want an EDS card to be
on
> >>>>>>>>> a shared
> >>>>>>>>> slot.
> >>>>>>>>>
> >>>>>>>>> On boot up check to make sure that the black screen that flashes
> >>>>>>>>> by shows
> >>>>>>>>> this correctly.
> >>>>>>>>>
> >>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote:
> >>>>>>>>>> Okay, on the IRQ page in the manual, it has two sections:
> >>>>>>>>>>
> >>>>>>>>>> 1. "Standard interrupt assignments", which list IRQ numbers and
> >>>>>>>>>> their
> >>>>>>>>>> "standard function". (This section does list 7 "IRQs are
usually
> >>>>>>>> available
> >>>>>>>>>> for PCI devices")
> >>>>>>>>>>
> >>>>>>>>>> 2. "IRQ" assignments for this motherboard", which graphs
various
> >>>>>>>>>> PCI
> >>>>>>>> slots
> >>>>>>>>>> or USB controllers as "nil", "shared", or "used" against
letters
> >>>>>>>>>> of the
> >>>>>>>>>> alphabet.
> >>>>>>>>>>
> >>>>>>>>>> I don't know how to use these two sets of data to resolve my
> >>>>>>>>>> problem.
> >>>>>>>> They
> >>>>>>>>>> seem incompatible. I feel ignernt.
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in message
> >>>>>>>>>> news:450a0f48@linux...
> >>>>>>>>>>> Hmmm.....well .......letsee.........ASUS boards normally will
> >>>>>>>>>>> have the
> >>>>>>>>> AGP
> >>>>>>>>>>> sharing an IRQ with two PCI slots, basically making these
> >>>>>>>>>>> worthless for
> >>>>>>>>>>> anything else.
> >>>>>>>>>>> How many PCI slots does your mobo have?
> >>>>>>>>>>> If it's a 5 slot board and it's similar to an AMD board,
chances
> >>>>>>>>>>> are
> >>>>>>>> that
> >>>>>>>>>>> PCI slots 1 and 5 are shared with the AGP and the firewire
port
> >>>>>>>>>>> (thus
> >>>>>>>>>> making
> >>>>>>>>>>> FW audio interfaces iffy also if using the onboard FW)
> >>>>>>>>>>>
> >>>>>>>>>>> PCI slot 2 may share with your LAN controller
> >>>>>>>>>>> PCI #3 may share with onboard RAID and SATA controller
> >>>>>>>>>>> PCI 4 may not share with anything.
> >>>>>>>>>>>
> >>>>>>>>>>> This is the way the ASUS A8V mobo is configured but it's for
AMD
> >>>>>>>>>>> CPU's.
> >>>>>>>>>>>
> >>>>>>>>>>> Do you have the manual? All of this is listed in chapter 2
under
> >>>>>>>>>>> the
> >>>>>>>>>> heading
> >>>>>>>>>>> Interrupt Assignments. It should be noted for Intel mobo's as
> >>>>>>>>>>> well.
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> If it's 6, try putting the EDS card in PCI 2, 3, 4 or 5
> >>>>>>>>>>> If it's 5, try PCI slot 1,
> >>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> >>>>>>>>>>> news:4509fd03@linux...
> >>>>>>>>>>>> It's an Asus P5P800 SE board with a Pentium 4 HT chip.
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in message
> >>>>>>>>>>>> news:4509f8fc@linux...
> >>>>>>>>>>>>> What kind of mobo are you using Jimmy?
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> >>>>>>>>>>>>> news:4509eda3@linux...
> >>>>>>>>>>>>>> I couldn't find any place where it indicated which IRQ the
> >>>>>>>>>>>>>> AGP was
> >>>>>>>>>>>>> assigned.
> >>>>>>>>>>>>>> The IRQ page had all IRQs assigned to "PCI", and beneath
that
> >>>>>>>>>>>>>> all
> >>>>>>>>> the
> >>>>>>>>>>> PCI
> >>>>>>>>>>>>>> slots all assigned to "AUTO". On another page the serial
port
> >>>>>>>>>>>>>> was
> >>>>>>>>>>>>>> assigned
> >>>>>>>>>>>>>> to IRQ 4, and the parallel port was assigned to IRQ 7. So I
> >>>>>>>> assigned
> >>>>>>>>>>> the
> >>>>>>>>>>>>> PCI
> >>>>>>>>>>>>>> slots to other numbers.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Am I on the wrong track here?
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in message
> >>>>>>>>>>>>>> news:4509da19@linux...
> >>>>>>>>>>>>>>> Repeat after me:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> IRQ!! IRQ!! IRQ!!
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> This sounds exactly like the EDS card is sharing and
> >>>>>>>>>>>>>>> interrupt
> >>>>>>>>> with
> >>>>>>>>>>> the
> >>>>>>>>>>>>>>> AGP
> >>>>>>>>>>>>>>> slot.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> >>>>>>>>>>>>>>> news:45098f86$1@linux...
> >>>>>>>>>>>>>>>> Hi-ho.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> I am still having trouble with my Paris rig. In an effort
> >>>>>>>>>>>>>>>> to
> >>>>>>>>>>> simplify
> >>>>>>>>>>>>>>> things,
> >>>>>>>>>>>>>>>> I only have one card installed, with an MEC attached,
> >>>>>>>>>>>>>>>> internal
> >>>>>>>>>>>>> clocking.
> >>>>>>>>>>>>>>>> Basically, my problems are down to two:
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> 1.The "now-line" freezes, or more actually begins
> >>>>>>>>>>>>>>>> stuttering in
> >>>>>>>>>>>>> extremely
> >>>>>>>>>>>>>>>> slow-motion, almost glacial. I can still change windows,
> >>>>>>>>>>>>>>>> and I
> >>>>>>>>> am
> >>>>>>>>>>> able
> >>>>>>>>>>>>> to
> >>>>>>>>>>>>>>>> save and close, then re-open Paris with success.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> 2.On starting Paris, I get an error message: "I/O modules
> >>>>>>>>>>>>>>>> used
> >>>>>>>>> in
> >>>>>>>>>>> this
> >>>>>>>>>>>>>>> patch
> >>>>>>>>>>>>>>>> setting not avaiable in this configuration of Paris.
> >>>>>>>>>>>>>>>> Resulting
> >>>>>>>>>> audio
> >>>>>>>>>>>>> may
> >>>>>>>>>>>>>>>> be different than when saved." This will pop up 2 or 4
> >>>>>>>>>>>>>>>> times,
> >>>>>>>>> and
> >>>>>>>>>>> then
> >>>>>>>>>>>>>>> when
> >>>>>>>>>>>>>>>> I push "play" no audio is heard. Then I close, reopen,
and
> >>>>>>>>>>>>>>>> then
> >>>>>>>>>>> things
> >>>>>>>>>>>>>>> work
> >>>>>>>>>>>>>>>> for a while.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> I have made some tweaks to the configuration with some
> >>>>>>>>>>>>>>>> success.
> >>>>>>>>>> The
> >>>>>>>>>>>>>>>> errors
> >>>>>>>>>>>>>>>> are happening less and less, but they still pop up.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Anybody?
> >>>>>>>>>>>>>>>> Jimmy
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>
> >
> >
>
>
|
|
|
|
| Re: still fighting for stability [message #72494 is a reply to message #72485] |
Sat, 16 September 2006 08:14 |
John [1]
Messages: 2229
Registered: September 2005
|
Senior Member |
|
|
Yeah, once you've had a crappy bios you won't do that mistake often.
It's miserable.
DJ wrote:
> Jimmy,
>
> Glad you're getting this resolved. At your earliest opportunity, get rid of
> that bios and go back to the one previous to the USB overcurrent warning.
> Really man. That bios you're running right now is a disaster waiting for a
> place to happen, and happen, and happen again.....I promise. It's going to
> bite you at the worst time and you're going to have to continuously clear
> the CMOS to get your machine to function as long as you're running that
> bios. Nothing worse than a computer that won't boot.
>
> Deej
>
> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> news:450b7e60@linux...
>> Alrighty. then. I tried the battery/jumper-cap thingie with great success.
>> Booted right up, with obvious changes to BIOS and VGA buffers and all
> else.
>> Then I made a few of the various previously suggested BIOS changes with
>> which I felt comfortable and got 1 hr 15 minutes of good, vital work done.
>>
>> I've had a few different troubles these past few days (months). Tonight I
>> have tried a various few fixes, and experienced some vexing troubles and
>> corresponding victories, but I haven't had time tonight to really
>> stress-test things. I'm not convinced that things are tight yet, as I've
>> been far too bedeviled in recent days to relax now without several
>> sessions-worth of hard use.
>>
>> Gotta session off-site tomorrow (Swen's studio), so I'll be back on my own
>> rig Sunday (yay NFL football!).
>>
>> I just want to thank everybody here for their sincere and dilligent
> efforts
>> in helping an ignernt fellow like myself. I wish I could make all of you a
>> big banquet dinner in thanks. I'm a damn fine cook, just not so much a
> damn
>> fine computer tech.
>>
>> I figure I'll start a new thread if things aren't right yet. I got us off
> on
>> a defective-BIOS tangent there.....the rig did feel pretty good there for
> an
>> hour or so, though.....
>>
>> Jimmy
>>
>>
>> "Aaron Allen" <know-spam@not_here.dude> wrote in message
>> news:450b60d5@linux...
>>> yup
>>>
>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
>>> news:450b5d6b@linux...
>>>> Ummm, I'm sorta freaked out and wanting precision right now. You mean,
>>>> "That's the ticket", right?
>>>>
>>>>
>>>> "Aaron Allen" <know-spam@not_here.dude> wrote in message
>>>> news:450b5c7c@linux...
>>>>> That's your daisy.
>>>>> AA
>>>>>
>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
>>>>> news:450b584d@linux...
>>>>>> The only thing I can see for this is to "clear the Real Time Clock
> RAM
>>>>>> in CMOS". This would "clear the CMOS memory of date, time, and system
>>>>>> setup parameters by erasing the CMOS RTC RAM data".
>>>>>>
>>>>>> This involves removing the onboard battery and moving jumper cap from
>>>>>> pins 1-2 to pins 2-3., then back to pins 1-2, then reinstalling the
>>>>>> battery. It says you have to enter the BIOS and re-enter data.
>>>>>>
>>>>>> Is this the thing to do?
>>>>>> "Martin Harrington" <lendan@bigpond.net.au> wrote in message
>>>>>> news:450b4d10@linux...
>>>>>>> All you need do is reset the BIOS by shorting out the relevant
> jumper
>>>>>>> on the motherboard...it's in the manual.
>>>>>>> --
>>>>>>> Martin Harrington
>>>>>>> www.lendanear-sound.com
>>>>>>>
>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
>>>>>>> news:450b4198@linux...
>>>>>>>> I disabledall but the com1 and lpt 1. Can't find them.
>>>>>>>>
>>>>>>>> Bad news is, and this is really bad news, computer won't boot up.
> On
>>>>>>>> that blcak page that n ow doesn't flash by so fast at all, I get
> the
>>>>>>>> error message "USB device over current status detected". Then the
>>>>>>>> computer shuts down. Won't boot up, won't let me go to BIOS to fix
>>>>>>>> it.
>>>>>>>>
>>>>>>>> Heeeeeelp!
>>>>>>>>
>>>>>>>>
>>>>>>>> "John" <no@no.com> wrote in message news:450b3aac$1@linux...
>>>>>>>>> It looks like another messed up Asus manual. I downloaded the
>>>>>>>>> manual and on page 2-18 it has that pic. I would turn off Com1
>>>>>>>>> (irq4), floppy (irq 6), lpt1 (irq 7), Serial port, turn off
> onboard
>>>>>>>>> audio and USB, Keep the LAN on so you can network but I would try
>>>>>>>>> only slots 3 and 4 only first. Notice how they don't even show
> audio
>>>>>>>>> sharing with anything. This diagram is craptastic.
>>>>>>>>>
>>>>>>>>> And turn off Hyper Threading.
>>>>>>>>>
>>>>>>>>> Do ME and favor and call them on the phone and ask then what the
>>>>>>>>> hell is this diagram means. Simply, what slots share with what?
>>>>>>>>> Inquiring minds !
>>>>>>>>>
>>>>>>>>> John
>>>>>>>>>
>>>>>>>>> Uptown Jimmy wrote:
>>>>>>>>>> I guess I don't understand what the Alphabetized row indicates.
> In
>>>>>>>>>> other
>>>>>>>>>> words, if PCI slot 1 "shared" with 'F', what does that mean? What
>>>>>>>>>> is it
>>>>>>>>>> shared with?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> "John" <no@no.com> wrote in message news:450af67f$1@linux...
>>>>>>>>>>> Use the second section that shows what are shared. Then make
> sure
>>>>>>>>>>> your
>>>>>>>>>> EDS
>>>>>>>>>>> cards are NOT on them. For example, turn off onboard audio in
>>>>>>>>>>> bios and
>>>>>>>>>>> now you can use the slot that shares with onboard audio. Any
>>>>>>>>>>> device that
>>>>>>>>>>> you are using like AGP video you DO NOT want an EDS card to be
> on
>>>>>>>>>>> a shared
>>>>>>>>>>> slot.
>>>>>>>>>>>
>>>>>>>>>>> On boot up check to make sure that the black screen that flashes
>>>>>>>>>>> by shows
>>>>>>>>>>> this correctly.
>>>>>>>>>>>
>>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote:
>>>>>>>>>>>> Okay, on the IRQ page in the manual, it has two sections:
>>>>>>>>>>>>
>>>>>>>>>>>> 1. "Standard interrupt assignments", which list IRQ numbers and
>>>>>>>>>>>> their
>>>>>>>>>>>> "standard function". (This section does list 7 "IRQs are
> usually
>>>>>>>>>> available
>>>>>>>>>>>> for PCI devices")
>>>>>>>>>>>>
>>>>>>>>>>>> 2. "IRQ" assignments for this motherboard", which graphs
> various
>>>>>>>>>>>> PCI
>>>>>>>>>> slots
>>>>>>>>>>>> or USB controllers as "nil", "shared", or "used" against
> letters
>>>>>>>>>>>> of the
>>>>>>>>>>>> alphabet.
>>>>>>>>>>>>
>>>>>>>>>>>> I don't know how to use these two sets of data to resolve my
>>>>>>>>>>>> problem.
>>>>>>>>>> They
>>>>>>>>>>>> seem incompatible. I feel ignernt.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in message
>>>>>>>>>>>> news:450a0f48@linux...
>>>>>>>>>>>>> Hmmm.....well .......letsee.........ASUS boards normally will
>>>>>>>>>>>>> have the
>>>>>>>>>>> AGP
>>>>>>>>>>>>> sharing an IRQ with two PCI slots, basically making these
>>>>>>>>>>>>> worthless for
>>>>>>>>>>>>> anything else.
>>>>>>>>>>>>> How many PCI slots does your mobo have?
>>>>>>>>>>>>> If it's a 5 slot board and it's similar to an AMD board,
> chances
>>>>>>>>>>>>> are
>>>>>>>>>> that
>>>>>>>>>>>>> PCI slots 1 and 5 are shared with the AGP and the firewire
> port
>>>>>>>>>>>>> (thus
>>>>>>>>>>>> making
>>>>>>>>>>>>> FW audio interfaces iffy also if using the onboard FW)
>>>>>>>>>>>>>
>>>>>>>>>>>>> PCI slot 2 may share with your LAN controller
>>>>>>>>>>>>> PCI #3 may share with onboard RAID and SATA controller
>>>>>>>>>>>>> PCI 4 may not share with anything.
>>>>>>>>>>>>>
>>>>>>>>>>>>> This is the way the ASUS A8V mobo is configured but it's for
> AMD
>>>>>>>>>>>>> CPU's.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Do you have the manual? All of this is listed in chapter 2
> under
>>>>>>>>>>>>> the
>>>>>>>>>>>> heading
>>>>>>>>>>>>> Interrupt Assignments. It should be noted for Intel mobo's as
>>>>>>>>>>>>> well.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> If it's 6, try putting the EDS card in PCI 2, 3, 4 or 5
>>>>>>>>>>>>> If it's 5, try PCI slot 1,
>>>>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
>>>>>>>>>>>>> news:4509fd03@linux...
>>>>>>>>>>>>>> It's an Asus P5P800 SE board with a Pentium 4 HT chip.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in message
>>>>>>>>>>>>>> news:4509f8fc@linux...
>>>>>>>>>>>>>>> What kind of mobo are you using Jimmy?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
>>>>>>>>>>>>>>> news:4509eda3@linux...
>>>>>>>>>>>>>>>> I couldn't find any place where it indicated which IRQ the
>>>>>>>>>>>>>>>> AGP was
>>>>>>>>>>>>>>> assigned.
>>>>>>>>>>>>>>>> The IRQ page had all IRQs assigned to "PCI", and beneath
> that
>>>>>>>>>>>>>>>> all
>>>>>>>>>>> the
>>>>>>>>>>>>> PCI
>>>>>>>>>>>>>>>> slots all assigned to "AUTO". On another page the serial
> port
>>>>>>>>>>>>>>>> was
>>>>>>>>>>>>>>>> assigned
>>>>>>>>>>>>>>>> to IRQ 4, and the parallel port was assigned to IRQ 7. So I
>>>>>>>>>> assigned
>>>>>>>>>>>>> the
>>>>>>>>>>>>>>> PCI
>>>>>>>>>>>>>>>> slots to other numbers.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Am I on the wrong track here?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in message
>>>>>>>>>>>>>>>> news:4509da19@linux...
>>>>>>>>>>>>>>>>> Repeat after me:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> IRQ!! IRQ!! IRQ!!
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> This sounds exactly like the EDS card is sharing and
>>>>>>>>>>>>>>>>> interrupt
>>>>>>>>>>> with
>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>> AGP
>>>>>>>>>>>>>>>>> slot.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
>>>>>>>>>>>>>>>>> news:45098f86$1@linux...
>>>>>>>>>>>>>>>>>> Hi-ho.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> I am still having trouble with my Paris rig. In an effort
>>>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>> simplify
>>>>>>>>>>>>>>>>> things,
>>>>>>>>>>>>>>>>>> I only have one card installed, with an MEC attached,
>>>>>>>>>>>>>>>>>> internal
>>>>>>>>>>>>>>> clocking.
>>>>>>>>>>>>>>>>>> Basically, my problems are down to two:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> 1.The "now-line" freezes, or more actually begins
>>>>>>>>>>>>>>>>>> stuttering in
>>>>>>>>>>>>>>> extremely
>>>>>>>>>>>>>>>>>> slow-motion, almost glacial. I can still change windows,
>>>>>>>>>>>>>>>>>> and I
>>>>>>>>>>> am
>>>>>>>>>>>>> able
>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>> save and close, then re-open Paris with success.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> 2.On starting Paris, I get an error message: "I/O modules
>>>>>>>>>>>>>>>>>> used
>>>>>>>>>>> in
>>>>>>>>>>>>> this
>>>>>>>>>>>>>>>>> patch
>>>>>>>>>>>>>>>>>> setting not avaiable in this configuration of Paris.
>>>>>>>>>>>>>>>>>> Resulting
>>>>>>>>>>>> audio
>>>>>>>>>>>>>>> may
>>>>>>>>>>>>>>>>>> be different than when saved." This will pop up 2 or 4
>>>>>>>>>>>>>>>>>> times,
>>>>>>>>>>> and
>>>>>>>>>>>>> then
>>>>>>>>>>>>>>>>> when
>>>>>>>>>>>>>>>>>> I push "play" no audio is heard. Then I close, reopen,
> and
>>>>>>>>>>>>>>>>>> then
>>>>>>>>>>>>> things
>>>>>>>>>>>>>>>>> work
>>>>>>>>>>>>>>>>>> for a while.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> I have made some tweaks to the configuration with some
>>>>>>>>>>>>>>>>>> success.
>>>>>>>>>>>> The
>>>>>>>>>>>>>>>>>> errors
>>>>>>>>>>>>>>>>>> are happening less and less, but they still pop up.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Anybody?
>>>>>>>>>>>>>>>>>> Jimmy
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
>
|
|
|
|
| Re: still fighting for stability [message #72497 is a reply to message #72494] |
Sat, 16 September 2006 08:34 |
Deej [1]
Messages: 2149
Registered: January 2006
|
Senior Member |
|
|
About 8 months ago I was going through this same thing with my ASUS A8V-Dlx
mobo. I must have cleared the CMOS about 20 times and I finally bought
another (identical mobo) thinking the board was defective. These mobo's were
discontinued, plentiful and cheap at the time and were the only ones around
(that I knew of) that would work with UAD-1 cards and dual core AMD CPU's.
Well the bios on the new mobo was an older revision and wouldn't support
dual core CPU's so I upgraded it to the *newest latest greatest* and the
same **** started happening. That's when I started getting pissed off and
figured out that I could flash to an older bios and make the problem go
away. I called ASUS and they wouldn't admit that their new *feature* was a
bug. It's the last ASUS mobo I'm gonna buy most likely, unless I have to go
there for compatibility reasons. Now that PCI has pretty much gone away,
it's going to take some major expense to upgrade my native rig because I'll
have to get a newer version of the Magma that can be used with PCIe. The
good news is that even with these new monster Intel processors, I'm sure
that the older dual/dualcore Opteron rigs will be affordable and work with
PCI based hardware so I'll still be able to crossgrade the hardware while
upgrading the OS to 64 bit. That oughta' hold me for a while longer. Right
now, I'm pretty happy with my AMD 64 4400 x 2 CPU running alongside Paris
during mixdown. As long as I'm tracking to Paris and don't have to have
higher sample rates, I'm good.
"John" <no@no.com> wrote in message news:450c1301@linux...
> Yeah, once you've had a crappy bios you won't do that mistake often.
> It's miserable.
>
> DJ wrote:
> > Jimmy,
> >
> > Glad you're getting this resolved. At your earliest opportunity, get rid
of
> > that bios and go back to the one previous to the USB overcurrent
warning.
> > Really man. That bios you're running right now is a disaster waiting for
a
> > place to happen, and happen, and happen again.....I promise. It's going
to
> > bite you at the worst time and you're going to have to continuously
clear
> > the CMOS to get your machine to function as long as you're running that
> > bios. Nothing worse than a computer that won't boot.
> >
> > Deej
> >
> > "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> > news:450b7e60@linux...
> >> Alrighty. then. I tried the battery/jumper-cap thingie with great
success.
> >> Booted right up, with obvious changes to BIOS and VGA buffers and all
> > else.
> >> Then I made a few of the various previously suggested BIOS changes with
> >> which I felt comfortable and got 1 hr 15 minutes of good, vital work
done.
> >>
> >> I've had a few different troubles these past few days (months). Tonight
I
> >> have tried a various few fixes, and experienced some vexing troubles
and
> >> corresponding victories, but I haven't had time tonight to really
> >> stress-test things. I'm not convinced that things are tight yet, as
I've
> >> been far too bedeviled in recent days to relax now without several
> >> sessions-worth of hard use.
> >>
> >> Gotta session off-site tomorrow (Swen's studio), so I'll be back on my
own
> >> rig Sunday (yay NFL football!).
> >>
> >> I just want to thank everybody here for their sincere and dilligent
> > efforts
> >> in helping an ignernt fellow like myself. I wish I could make all of
you a
> >> big banquet dinner in thanks. I'm a damn fine cook, just not so much a
> > damn
> >> fine computer tech.
> >>
> >> I figure I'll start a new thread if things aren't right yet. I got us
off
> > on
> >> a defective-BIOS tangent there.....the rig did feel pretty good there
for
> > an
> >> hour or so, though.....
> >>
> >> Jimmy
> >>
> >>
> >> "Aaron Allen" <know-spam@not_here.dude> wrote in message
> >> news:450b60d5@linux...
> >>> yup
> >>>
> >>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> >>> news:450b5d6b@linux...
> >>>> Ummm, I'm sorta freaked out and wanting precision right now. You
mean,
> >>>> "That's the ticket", right?
> >>>>
> >>>>
> >>>> "Aaron Allen" <know-spam@not_here.dude> wrote in message
> >>>> news:450b5c7c@linux...
> >>>>> That's your daisy.
> >>>>> AA
> >>>>>
> >>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> >>>>> news:450b584d@linux...
> >>>>>> The only thing I can see for this is to "clear the Real Time Clock
> > RAM
> >>>>>> in CMOS". This would "clear the CMOS memory of date, time, and
system
> >>>>>> setup parameters by erasing the CMOS RTC RAM data".
> >>>>>>
> >>>>>> This involves removing the onboard battery and moving jumper cap
from
> >>>>>> pins 1-2 to pins 2-3., then back to pins 1-2, then reinstalling the
> >>>>>> battery. It says you have to enter the BIOS and re-enter data.
> >>>>>>
> >>>>>> Is this the thing to do?
> >>>>>> "Martin Harrington" <lendan@bigpond.net.au> wrote in message
> >>>>>> news:450b4d10@linux...
> >>>>>>> All you need do is reset the BIOS by shorting out the relevant
> > jumper
> >>>>>>> on the motherboard...it's in the manual.
> >>>>>>> --
> >>>>>>> Martin Harrington
> >>>>>>> www.lendanear-sound.com
> >>>>>>>
> >>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> >>>>>>> news:450b4198@linux...
> >>>>>>>> I disabledall but the com1 and lpt 1. Can't find them.
> >>>>>>>>
> >>>>>>>> Bad news is, and this is really bad news, computer won't boot up.
> > On
> >>>>>>>> that blcak page that n ow doesn't flash by so fast at all, I get
> > the
> >>>>>>>> error message "USB device over current status detected". Then the
> >>>>>>>> computer shuts down. Won't boot up, won't let me go to BIOS to
fix
> >>>>>>>> it.
> >>>>>>>>
> >>>>>>>> Heeeeeelp!
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> "John" <no@no.com> wrote in message news:450b3aac$1@linux...
> >>>>>>>>> It looks like another messed up Asus manual. I downloaded the
> >>>>>>>>> manual and on page 2-18 it has that pic. I would turn off Com1
> >>>>>>>>> (irq4), floppy (irq 6), lpt1 (irq 7), Serial port, turn off
> > onboard
> >>>>>>>>> audio and USB, Keep the LAN on so you can network but I would
try
> >>>>>>>>> only slots 3 and 4 only first. Notice how they don't even show
> > audio
> >>>>>>>>> sharing with anything. This diagram is craptastic.
> >>>>>>>>>
> >>>>>>>>> And turn off Hyper Threading.
> >>>>>>>>>
> >>>>>>>>> Do ME and favor and call them on the phone and ask then what the
> >>>>>>>>> hell is this diagram means. Simply, what slots share with
what?
> >>>>>>>>> Inquiring minds !
> >>>>>>>>>
> >>>>>>>>> John
> >>>>>>>>>
> >>>>>>>>> Uptown Jimmy wrote:
> >>>>>>>>>> I guess I don't understand what the Alphabetized row indicates.
> > In
> >>>>>>>>>> other
> >>>>>>>>>> words, if PCI slot 1 "shared" with 'F', what does that mean?
What
> >>>>>>>>>> is it
> >>>>>>>>>> shared with?
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> "John" <no@no.com> wrote in message news:450af67f$1@linux...
> >>>>>>>>>>> Use the second section that shows what are shared. Then make
> > sure
> >>>>>>>>>>> your
> >>>>>>>>>> EDS
> >>>>>>>>>>> cards are NOT on them. For example, turn off onboard audio
in
> >>>>>>>>>>> bios and
> >>>>>>>>>>> now you can use the slot that shares with onboard audio. Any
> >>>>>>>>>>> device that
> >>>>>>>>>>> you are using like AGP video you DO NOT want an EDS card to be
> > on
> >>>>>>>>>>> a shared
> >>>>>>>>>>> slot.
> >>>>>>>>>>>
> >>>>>>>>>>> On boot up check to make sure that the black screen that
flashes
> >>>>>>>>>>> by shows
> >>>>>>>>>>> this correctly.
> >>>>>>>>>>>
> >>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote:
> >>>>>>>>>>>> Okay, on the IRQ page in the manual, it has two sections:
> >>>>>>>>>>>>
> >>>>>>>>>>>> 1. "Standard interrupt assignments", which list IRQ numbers
and
> >>>>>>>>>>>> their
> >>>>>>>>>>>> "standard function". (This section does list 7 "IRQs are
> > usually
> >>>>>>>>>> available
> >>>>>>>>>>>> for PCI devices")
> >>>>>>>>>>>>
> >>>>>>>>>>>> 2. "IRQ" assignments for this motherboard", which graphs
> > various
> >>>>>>>>>>>> PCI
> >>>>>>>>>> slots
> >>>>>>>>>>>> or USB controllers as "nil", "shared", or "used" against
> > letters
> >>>>>>>>>>>> of the
> >>>>>>>>>>>> alphabet.
> >>>>>>>>>>>>
> >>>>>>>>>>>> I don't know how to use these two sets of data to resolve my
> >>>>>>>>>>>> problem.
> >>>>>>>>>> They
> >>>>>>>>>>>> seem incompatible. I feel ignernt.
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in message
> >>>>>>>>>>>> news:450a0f48@linux...
> >>>>>>>>>>>>> Hmmm.....well .......letsee.........ASUS boards normally
will
> >>>>>>>>>>>>> have the
> >>>>>>>>>>> AGP
> >>>>>>>>>>>>> sharing an IRQ with two PCI slots, basically making these
> >>>>>>>>>>>>> worthless for
> >>>>>>>>>>>>> anything else.
> >>>>>>>>>>>>> How many PCI slots does your mobo have?
> >>>>>>>>>>>>> If it's a 5 slot board and it's similar to an AMD board,
> > chances
> >>>>>>>>>>>>> are
> >>>>>>>>>> that
> >>>>>>>>>>>>> PCI slots 1 and 5 are shared with the AGP and the firewire
> > port
> >>>>>>>>>>>>> (thus
> >>>>>>>>>>>> making
> >>>>>>>>>>>>> FW audio interfaces iffy also if using the onboard FW)
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> PCI slot 2 may share with your LAN controller
> >>>>>>>>>>>>> PCI #3 may share with onboard RAID and SATA controller
> >>>>>>>>>>>>> PCI 4 may not share with anything.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> This is the way the ASUS A8V mobo is configured but it's for
> > AMD
> >>>>>>>>>>>>> CPU's.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Do you have the manual? All of this is listed in chapter 2
> > under
> >>>>>>>>>>>>> the
> >>>>>>>>>>>> heading
> >>>>>>>>>>>>> Interrupt Assignments. It should be noted for Intel mobo's
as
> >>>>>>>>>>>>> well.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> If it's 6, try putting the EDS card in PCI 2, 3, 4 or 5
> >>>>>>>>>>>>> If it's 5, try PCI slot 1,
> >>>>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> >>>>>>>>>>>>> news:4509fd03@linux...
> >>>>>>>>>>>>>> It's an Asus P5P800 SE board with a Pentium 4 HT chip.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in message
> >>>>>>>>>>>>>> news:4509f8fc@linux...
> >>>>>>>>>>>>>>> What kind of mobo are you using Jimmy?
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> >>>>>>>>>>>>>>> news:4509eda3@linux...
> >>>>>>>>>>>>>>>> I couldn't find any place where it indicated which IRQ
the
> >>>>>>>>>>>>>>>> AGP was
> >>>>>>>>>>>>>>> assigned.
> >>>>>>>>>>>>>>>> The IRQ page had all IRQs assigned to "PCI", and beneath
> > that
> >>>>>>>>>>>>>>>> all
> >>>>>>>>>>> the
> >>>>>>>>>>>>> PCI
> >>>>>>>>>>>>>>>> slots all assigned to "AUTO". On another page the serial
> > port
> >>>>>>>>>>>>>>>> was
> >>>>>>>>>>>>>>>> assigned
> >>>>>>>>>>>>>>>> to IRQ 4, and the parallel port was assigned to IRQ 7. So
I
> >>>>>>>>>> assigned
> >>>>>>>>>>>>> the
> >>>>>>>>>>>>>>> PCI
> >>>>>>>>>>>>>>>> slots to other numbers.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Am I on the wrong track here?
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in
message
> >>>>>>>>>>>>>>>> news:4509da19@linux...
> >>>>>>>>>>>>>>>>> Repeat after me:
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> IRQ!! IRQ!! IRQ!!
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> This sounds exactly like the EDS card is sharing and
> >>>>>>>>>>>>>>>>> interrupt
> >>>>>>>>>>> with
> >>>>>>>>>>>>> the
> >>>>>>>>>>>>>>>>> AGP
> >>>>>>>>>>>>>>>>> slot.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in
message
> >>>>>>>>>>>>>>>>> news:45098f86$1@linux...
> >>>>>>>>>>>>>>>>>> Hi-ho.
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> I am still having trouble with my Paris rig. In an
effort
> >>>>>>>>>>>>>>>>>> to
> >>>>>>>>>>>>> simplify
> >>>>>>>>>>>>>>>>> things,
> >>>>>>>>>>>>>>>>>> I only have one card installed, with an MEC attached,
> >>>>>>>>>>>>>>>>>> internal
> >>>>>>>>>>>>>>> clocking.
> >>>>>>>>>>>>>>>>>> Basically, my problems are down to two:
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> 1.The "now-line" freezes, or more actually begins
> >>>>>>>>>>>>>>>>>> stuttering in
> >>>>>>>>>>>>>>> extremely
> >>>>>>>>>>>>>>>>>> slow-motion, almost glacial. I can still change
windows,
> >>>>>>>>>>>>>>>>>> and I
> >>>>>>>>>>> am
> >>>>>>>>>>>>> able
> >>>>>>>>>>>>>>> to
> >>>>>>>>>>>>>>>>>> save and close, then re-open Paris with success.
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> 2.On starting Paris, I get an error message: "I/O
modules
> >>>>>>>>>>>>>>>>>> used
> >>>>>>>>>>> in
> >>>>>>>>>>>>> this
> >>>>>>>>>>>>>>>>> patch
> >>>>>>>>>>>>>>>>>> setting not avaiable in this configuration of Paris.
> >>>>>>>>>>>>>>>>>> Resulting
> >>>>>>>>>>>> audio
> >>>>>>>>>>>>>>> may
> >>>>>>>>>>>>>>>>>> be different than when saved." This will pop up 2 or 4
> >>>>>>>>>>>>>>>>>> times,
> >>>>>>>>>>> and
> >>>>>>>>>>>>> then
> >>>>>>>>>>>>>>>>> when
> >>>>>>>>>>>>>>>>>> I push "play" no audio is heard. Then I close, reopen,
> > and
> >>>>>>>>>>>>>>>>>> then
> >>>>>>>>>>>>> things
> >>>>>>>>>>>>>>>>> work
> >>>>>>>>>>>>>>>>>> for a while.
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> I have made some tweaks to the configuration with some
> >>>>>>>>>>>>>>>>>> success.
> >>>>>>>>>>>> The
> >>>>>>>>>>>>>>>>>> errors
> >>>>>>>>>>>>>>>>>> are happening less and less, but they still pop up.
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Anybody?
> >>>>>>>>>>>>>>>>>> Jimmy
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> >
> >
|
|
|
|
| Re: still fighting for stability [message #72502 is a reply to message #72485] |
Sat, 16 September 2006 09:58 |
uptown jimmy
Messages: 441
Registered: September 2005
|
Senior Member |
|
|
I hope Swen still has his floppy drive installed. I've got mine around here
somewhere...
Jimmy
"DJ" <animix_spam-this-ahole_@animas.net> wrote in message
news:450b9090@linux...
> Jimmy,
>
> Glad you're getting this resolved. At your earliest opportunity, get rid
of
> that bios and go back to the one previous to the USB overcurrent warning.
> Really man. That bios you're running right now is a disaster waiting for a
> place to happen, and happen, and happen again.....I promise. It's going to
> bite you at the worst time and you're going to have to continuously clear
> the CMOS to get your machine to function as long as you're running that
> bios. Nothing worse than a computer that won't boot.
>
> Deej
>
> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> news:450b7e60@linux...
> > Alrighty. then. I tried the battery/jumper-cap thingie with great
success.
> > Booted right up, with obvious changes to BIOS and VGA buffers and all
> else.
> >
> > Then I made a few of the various previously suggested BIOS changes with
> > which I felt comfortable and got 1 hr 15 minutes of good, vital work
done.
> >
> > I've had a few different troubles these past few days (months). Tonight
I
> > have tried a various few fixes, and experienced some vexing troubles and
> > corresponding victories, but I haven't had time tonight to really
> > stress-test things. I'm not convinced that things are tight yet, as I've
> > been far too bedeviled in recent days to relax now without several
> > sessions-worth of hard use.
> >
> > Gotta session off-site tomorrow (Swen's studio), so I'll be back on my
own
> > rig Sunday (yay NFL football!).
> >
> > I just want to thank everybody here for their sincere and dilligent
> efforts
> > in helping an ignernt fellow like myself. I wish I could make all of you
a
> > big banquet dinner in thanks. I'm a damn fine cook, just not so much a
> damn
> > fine computer tech.
> >
> > I figure I'll start a new thread if things aren't right yet. I got us
off
> on
> > a defective-BIOS tangent there.....the rig did feel pretty good there
for
> an
> > hour or so, though.....
> >
> > Jimmy
> >
> >
> > "Aaron Allen" <know-spam@not_here.dude> wrote in message
> > news:450b60d5@linux...
> > > yup
> > >
> > > "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> > > news:450b5d6b@linux...
> > >> Ummm, I'm sorta freaked out and wanting precision right now. You
mean,
> > >> "That's the ticket", right?
> > >>
> > >>
> > >> "Aaron Allen" <know-spam@not_here.dude> wrote in message
> > >> news:450b5c7c@linux...
> > >>> That's your daisy.
> > >>> AA
> > >>>
> > >>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> > >>> news:450b584d@linux...
> > >>>> The only thing I can see for this is to "clear the Real Time Clock
> RAM
> > >>>> in CMOS". This would "clear the CMOS memory of date, time, and
system
> > >>>> setup parameters by erasing the CMOS RTC RAM data".
> > >>>>
> > >>>> This involves removing the onboard battery and moving jumper cap
from
> > >>>> pins 1-2 to pins 2-3., then back to pins 1-2, then reinstalling the
> > >>>> battery. It says you have to enter the BIOS and re-enter data.
> > >>>>
> > >>>> Is this the thing to do?
> > >>>> "Martin Harrington" <lendan@bigpond.net.au> wrote in message
> > >>>> news:450b4d10@linux...
> > >>>>> All you need do is reset the BIOS by shorting out the relevant
> jumper
> > >>>>> on the motherboard...it's in the manual.
> > >>>>> --
> > >>>>> Martin Harrington
> > >>>>> www.lendanear-sound.com
> > >>>>>
> > >>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> > >>>>> news:450b4198@linux...
> > >>>>>>I disabledall but the com1 and lpt 1. Can't find them.
> > >>>>>>
> > >>>>>> Bad news is, and this is really bad news, computer won't boot up.
> On
> > >>>>>> that blcak page that n ow doesn't flash by so fast at all, I get
> the
> > >>>>>> error message "USB device over current status detected". Then the
> > >>>>>> computer shuts down. Won't boot up, won't let me go to BIOS to
fix
> > >>>>>> it.
> > >>>>>>
> > >>>>>> Heeeeeelp!
> > >>>>>>
> > >>>>>>
> > >>>>>> "John" <no@no.com> wrote in message news:450b3aac$1@linux...
> > >>>>>>> It looks like another messed up Asus manual. I downloaded the
> > >>>>>>> manual and on page 2-18 it has that pic. I would turn off Com1
> > >>>>>>> (irq4), floppy (irq 6), lpt1 (irq 7), Serial port, turn off
> onboard
> > >>>>>>> audio and USB, Keep the LAN on so you can network but I would
try
> > >>>>>>> only slots 3 and 4 only first. Notice how they don't even show
> audio
> > >>>>>>> sharing with anything. This diagram is craptastic.
> > >>>>>>>
> > >>>>>>> And turn off Hyper Threading.
> > >>>>>>>
> > >>>>>>> Do ME and favor and call them on the phone and ask then what the
> > >>>>>>> hell is this diagram means. Simply, what slots share with
what?
> > >>>>>>> Inquiring minds !
> > >>>>>>>
> > >>>>>>> John
> > >>>>>>>
> > >>>>>>> Uptown Jimmy wrote:
> > >>>>>>>> I guess I don't understand what the Alphabetized row indicates.
> In
> > >>>>>>>> other
> > >>>>>>>> words, if PCI slot 1 "shared" with 'F', what does that mean?
What
> > >>>>>>>> is it
> > >>>>>>>> shared with?
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>> "John" <no@no.com> wrote in message news:450af67f$1@linux...
> > >>>>>>>>> Use the second section that shows what are shared. Then make
> sure
> > >>>>>>>>> your
> > >>>>>>>> EDS
> > >>>>>>>>> cards are NOT on them. For example, turn off onboard audio
in
> > >>>>>>>>> bios and
> > >>>>>>>>> now you can use the slot that shares with onboard audio. Any
> > >>>>>>>>> device that
> > >>>>>>>>> you are using like AGP video you DO NOT want an EDS card to be
> on
> > >>>>>>>>> a shared
> > >>>>>>>>> slot.
> > >>>>>>>>>
> > >>>>>>>>> On boot up check to make sure that the black screen that
flashes
> > >>>>>>>>> by shows
> > >>>>>>>>> this correctly.
> > >>>>>>>>>
> > >>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote:
> > >>>>>>>>>> Okay, on the IRQ page in the manual, it has two sections:
> > >>>>>>>>>>
> > >>>>>>>>>> 1. "Standard interrupt assignments", which list IRQ numbers
and
> > >>>>>>>>>> their
> > >>>>>>>>>> "standard function". (This section does list 7 "IRQs are
> usually
> > >>>>>>>> available
> > >>>>>>>>>> for PCI devices")
> > >>>>>>>>>>
> > >>>>>>>>>> 2. "IRQ" assignments for this motherboard", which graphs
> various
> > >>>>>>>>>> PCI
> > >>>>>>>> slots
> > >>>>>>>>>> or USB controllers as "nil", "shared", or "used" against
> letters
> > >>>>>>>>>> of the
> > >>>>>>>>>> alphabet.
> > >>>>>>>>>>
> > >>>>>>>>>> I don't know how to use these two sets of data to resolve my
> > >>>>>>>>>> problem.
> > >>>>>>>> They
> > >>>>>>>>>> seem incompatible. I feel ignernt.
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in message
> > >>>>>>>>>> news:450a0f48@linux...
> > >>>>>>>>>>> Hmmm.....well .......letsee.........ASUS boards normally
will
> > >>>>>>>>>>> have the
> > >>>>>>>>> AGP
> > >>>>>>>>>>> sharing an IRQ with two PCI slots, basically making these
> > >>>>>>>>>>> worthless for
> > >>>>>>>>>>> anything else.
> > >>>>>>>>>>> How many PCI slots does your mobo have?
> > >>>>>>>>>>> If it's a 5 slot board and it's similar to an AMD board,
> chances
> > >>>>>>>>>>> are
> > >>>>>>>> that
> > >>>>>>>>>>> PCI slots 1 and 5 are shared with the AGP and the firewire
> port
> > >>>>>>>>>>> (thus
> > >>>>>>>>>> making
> > >>>>>>>>>>> FW audio interfaces iffy also if using the onboard FW)
> > >>>>>>>>>>>
> > >>>>>>>>>>> PCI slot 2 may share with your LAN controller
> > >>>>>>>>>>> PCI #3 may share with onboard RAID and SATA controller
> > >>>>>>>>>>> PCI 4 may not share with anything.
> > >>>>>>>>>>>
> > >>>>>>>>>>> This is the way the ASUS A8V mobo is configured but it's for
> AMD
> > >>>>>>>>>>> CPU's.
> > >>>>>>>>>>>
> > >>>>>>>>>>> Do you have the manual? All of this is listed in chapter 2
> under
> > >>>>>>>>>>> the
> > >>>>>>>>>> heading
> > >>>>>>>>>>> Interrupt Assignments. It should be noted for Intel mobo's
as
> > >>>>>>>>>>> well.
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>> If it's 6, try putting the EDS card in PCI 2, 3, 4 or 5
> > >>>>>>>>>>> If it's 5, try PCI slot 1,
> > >>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> > >>>>>>>>>>> news:4509fd03@linux...
> > >>>>>>>>>>>> It's an Asus P5P800 SE board with a Pentium 4 HT chip.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in message
> > >>>>>>>>>>>> news:4509f8fc@linux...
> > >>>>>>>>>>>>> What kind of mobo are you using Jimmy?
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> > >>>>>>>>>>>>> news:4509eda3@linux...
> > >>>>>>>>>>>>>> I couldn't find any place where it indicated which IRQ
the
> > >>>>>>>>>>>>>> AGP was
> > >>>>>>>>>>>>> assigned.
> > >>>>>>>>>>>>>> The IRQ page had all IRQs assigned to "PCI", and beneath
> that
> > >>>>>>>>>>>>>> all
> > >>>>>>>>> the
> > >>>>>>>>>>> PCI
> > >>>>>>>>>>>>>> slots all assigned to "AUTO". On another page the serial
> port
> > >>>>>>>>>>>>>> was
> > >>>>>>>>>>>>>> assigned
> > >>>>>>>>>>>>>> to IRQ 4, and the parallel port was assigned to IRQ 7. So
I
> > >>>>>>>> assigned
> > >>>>>>>>>>> the
> > >>>>>>>>>>>>> PCI
> > >>>>>>>>>>>>>> slots to other numbers.
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> Am I on the wrong track here?
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in
message
> > >>>>>>>>>>>>>> news:4509da19@linux...
> > >>>>>>>>>>>>>>> Repeat after me:
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>> IRQ!! IRQ!! IRQ!!
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>> This sounds exactly like the EDS card is sharing and
> > >>>>>>>>>>>>>>> interrupt
> > >>>>>>>>> with
> > >>>>>>>>>>> the
> > >>>>>>>>>>>>>>> AGP
> > >>>>>>>>>>>>>>> slot.
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in
message
> > >>>>>>>>>>>>>>> news:45098f86$1@linux...
> > >>>>>>>>>>>>>>>> Hi-ho.
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> I am still having trouble with my Paris rig. In an
effort
> > >>>>>>>>>>>>>>>> to
> > >>>>>>>>>>> simplify
> > >>>>>>>>>>>>>>> things,
> > >>>>>>>>>>>>>>>> I only have one card installed, with an MEC attached,
> > >>>>>>>>>>>>>>>> internal
> > >>>>>>>>>>>>> clocking.
> > >>>>>>>>>>>>>>>> Basically, my problems are down to two:
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> 1.The "now-line" freezes, or more actually begins
> > >>>>>>>>>>>>>>>> stuttering in
> > >>>>>>>>>>>>> extremely
> > >>>>>>>>>>>>>>>> slow-motion, almost glacial. I can still change
windows,
> > >>>>>>>>>>>>>>>> and I
> > >>>>>>>>> am
> > >>>>>>>>>>> able
> > >>>>>>>>>>>>> to
> > >>>>>>>>>>>>>>>> save and close, then re-open Paris with success.
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> 2.On starting Paris, I get an error message: "I/O
modules
> > >>>>>>>>>>>>>>>> used
> > >>>>>>>>> in
> > >>>>>>>>>>> this
> > >>>>>>>>>>>>>>> patch
> > >>>>>>>>>>>>>>>> setting not avaiable in this configuration of Paris.
> > >>>>>>>>>>>>>>>> Resulting
> > >>>>>>>>>> audio
> > >>>>>>>>>>>>> may
> > >>>>>>>>>>>>>>>> be different than when saved." This will pop up 2 or 4
> > >>>>>>>>>>>>>>>> times,
> > >>>>>>>>> and
> > >>>>>>>>>>> then
> > >>>>>>>>>>>>>>> when
> > >>>>>>>>>>>>>>>> I push "play" no audio is heard. Then I close, reopen,
> and
> > >>>>>>>>>>>>>>>> then
> > >>>>>>>>>>> things
> > >>>>>>>>>>>>>>> work
> > >>>>>>>>>>>>>>>> for a while.
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> I have made some tweaks to the configuration with some
> > >>>>>>>>>>>>>>>> success.
> > >>>>>>>>>> The
> > >>>>>>>>>>>>>>>> errors
> > >>>>>>>>>>>>>>>> are happening less and less, but they still pop up.
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> Anybody?
> > >>>>>>>>>>>>>>>> Jimmy
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>
> > >>>>>>
> > >>>>>
> > >>>>>
> > >>>>
> > >>>>
> > >>>
> > >>>
> > >>
> > >>
> > >
> > >
> >
> >
>
>
|
|
|
|
| Re: still fighting for stability [message #72506 is a reply to message #72485] |
Sat, 16 September 2006 11:49 |
uptown jimmy
Messages: 441
Registered: September 2005
|
Senior Member |
|
|
So, rollback the BIOS even if I'm NOT going to disable the USB?
"DJ" <animix_spam-this-ahole_@animas.net> wrote in message
news:450b9090@linux...
> Jimmy,
>
> Glad you're getting this resolved. At your earliest opportunity, get rid
of
> that bios and go back to the one previous to the USB overcurrent warning.
> Really man. That bios you're running right now is a disaster waiting for a
> place to happen, and happen, and happen again.....I promise. It's going to
> bite you at the worst time and you're going to have to continuously clear
> the CMOS to get your machine to function as long as you're running that
> bios. Nothing worse than a computer that won't boot.
>
> Deej
>
> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> news:450b7e60@linux...
> > Alrighty. then. I tried the battery/jumper-cap thingie with great
success.
> > Booted right up, with obvious changes to BIOS and VGA buffers and all
> else.
> >
> > Then I made a few of the various previously suggested BIOS changes with
> > which I felt comfortable and got 1 hr 15 minutes of good, vital work
done.
> >
> > I've had a few different troubles these past few days (months). Tonight
I
> > have tried a various few fixes, and experienced some vexing troubles and
> > corresponding victories, but I haven't had time tonight to really
> > stress-test things. I'm not convinced that things are tight yet, as I've
> > been far too bedeviled in recent days to relax now without several
> > sessions-worth of hard use.
> >
> > Gotta session off-site tomorrow (Swen's studio), so I'll be back on my
own
> > rig Sunday (yay NFL football!).
> >
> > I just want to thank everybody here for their sincere and dilligent
> efforts
> > in helping an ignernt fellow like myself. I wish I could make all of you
a
> > big banquet dinner in thanks. I'm a damn fine cook, just not so much a
> damn
> > fine computer tech.
> >
> > I figure I'll start a new thread if things aren't right yet. I got us
off
> on
> > a defective-BIOS tangent there.....the rig did feel pretty good there
for
> an
> > hour or so, though.....
> >
> > Jimmy
> >
> >
> > "Aaron Allen" <know-spam@not_here.dude> wrote in message
> > news:450b60d5@linux...
> > > yup
> > >
> > > "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> > > news:450b5d6b@linux...
> > >> Ummm, I'm sorta freaked out and wanting precision right now. You
mean,
> > >> "That's the ticket", right?
> > >>
> > >>
> > >> "Aaron Allen" <know-spam@not_here.dude> wrote in message
> > >> news:450b5c7c@linux...
> > >>> That's your daisy.
> > >>> AA
> > >>>
> > >>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> > >>> news:450b584d@linux...
> > >>>> The only thing I can see for this is to "clear the Real Time Clock
> RAM
> > >>>> in CMOS". This would "clear the CMOS memory of date, time, and
system
> > >>>> setup parameters by erasing the CMOS RTC RAM data".
> > >>>>
> > >>>> This involves removing the onboard battery and moving jumper cap
from
> > >>>> pins 1-2 to pins 2-3., then back to pins 1-2, then reinstalling the
> > >>>> battery. It says you have to enter the BIOS and re-enter data.
> > >>>>
> > >>>> Is this the thing to do?
> > >>>> "Martin Harrington" <lendan@bigpond.net.au> wrote in message
> > >>>> news:450b4d10@linux...
> > >>>>> All you need do is reset the BIOS by shorting out the relevant
> jumper
> > >>>>> on the motherboard...it's in the manual.
> > >>>>> --
> > >>>>> Martin Harrington
> > >>>>> www.lendanear-sound.com
> > >>>>>
> > >>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> > >>>>> news:450b4198@linux...
> > >>>>>>I disabledall but the com1 and lpt 1. Can't find them.
> > >>>>>>
> > >>>>>> Bad news is, and this is really bad news, computer won't boot up.
> On
> > >>>>>> that blcak page that n ow doesn't flash by so fast at all, I get
> the
> > >>>>>> error message "USB device over current status detected". Then the
> > >>>>>> computer shuts down. Won't boot up, won't let me go to BIOS to
fix
> > >>>>>> it.
> > >>>>>>
> > >>>>>> Heeeeeelp!
> > >>>>>>
> > >>>>>>
> > >>>>>> "John" <no@no.com> wrote in message news:450b3aac$1@linux...
> > >>>>>>> It looks like another messed up Asus manual. I downloaded the
> > >>>>>>> manual and on page 2-18 it has that pic. I would turn off Com1
> > >>>>>>> (irq4), floppy (irq 6), lpt1 (irq 7), Serial port, turn off
> onboard
> > >>>>>>> audio and USB, Keep the LAN on so you can network but I would
try
> > >>>>>>> only slots 3 and 4 only first. Notice how they don't even show
> audio
> > >>>>>>> sharing with anything. This diagram is craptastic.
> > >>>>>>>
> > >>>>>>> And turn off Hyper Threading.
> > >>>>>>>
> > >>>>>>> Do ME and favor and call them on the phone and ask then what the
> > >>>>>>> hell is this diagram means. Simply, what slots share with
what?
> > >>>>>>> Inquiring minds !
> > >>>>>>>
> > >>>>>>> John
> > >>>>>>>
> > >>>>>>> Uptown Jimmy wrote:
> > >>>>>>>> I guess I don't understand what the Alphabetized row indicates.
> In
> > >>>>>>>> other
> > >>>>>>>> words, if PCI slot 1 "shared" with 'F', what does that mean?
What
> > >>>>>>>> is it
> > >>>>>>>> shared with?
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>> "John" <no@no.com> wrote in message news:450af67f$1@linux...
> > >>>>>>>>> Use the second section that shows what are shared. Then make
> sure
> > >>>>>>>>> your
> > >>>>>>>> EDS
> > >>>>>>>>> cards are NOT on them. For example, turn off onboard audio
in
> > >>>>>>>>> bios and
> > >>>>>>>>> now you can use the slot that shares with onboard audio. Any
> > >>>>>>>>> device that
> > >>>>>>>>> you are using like AGP video you DO NOT want an EDS card to be
> on
> > >>>>>>>>> a shared
> > >>>>>>>>> slot.
> > >>>>>>>>>
> > >>>>>>>>> On boot up check to make sure that the black screen that
flashes
> > >>>>>>>>> by shows
> > >>>>>>>>> this correctly.
> > >>>>>>>>>
> > >>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote:
> > >>>>>>>>>> Okay, on the IRQ page in the manual, it has two sections:
> > >>>>>>>>>>
> > >>>>>>>>>> 1. "Standard interrupt assignments", which list IRQ numbers
and
> > >>>>>>>>>> their
> > >>>>>>>>>> "standard function". (This section does list 7 "IRQs are
> usually
> > >>>>>>>> available
> > >>>>>>>>>> for PCI devices")
> > >>>>>>>>>>
> > >>>>>>>>>> 2. "IRQ" assignments for this motherboard", which graphs
> various
> > >>>>>>>>>> PCI
> > >>>>>>>> slots
> > >>>>>>>>>> or USB controllers as "nil", "shared", or "used" against
> letters
> > >>>>>>>>>> of the
> > >>>>>>>>>> alphabet.
> > >>>>>>>>>>
> > >>>>>>>>>> I don't know how to use these two sets of data to resolve my
> > >>>>>>>>>> problem.
> > >>>>>>>> They
> > >>>>>>>>>> seem incompatible. I feel ignernt.
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in message
> > >>>>>>>>>> news:450a0f48@linux...
> > >>>>>>>>>>> Hmmm.....well .......letsee.........ASUS boards normally
will
> > >>>>>>>>>>> have the
> > >>>>>>>>> AGP
> > >>>>>>>>>>> sharing an IRQ with two PCI slots, basically making these
> > >>>>>>>>>>> worthless for
> > >>>>>>>>>>> anything else.
> > >>>>>>>>>>> How many PCI slots does your mobo have?
> > >>>>>>>>>>> If it's a 5 slot board and it's similar to an AMD board,
> chances
> > >>>>>>>>>>> are
> > >>>>>>>> that
> > >>>>>>>>>>> PCI slots 1 and 5 are shared with the AGP and the firewire
> port
> > >>>>>>>>>>> (thus
> > >>>>>>>>>> making
> > >>>>>>>>>>> FW audio interfaces iffy also if using the onboard FW)
> > >>>>>>>>>>>
> > >>>>>>>>>>> PCI slot 2 may share with your LAN controller
> > >>>>>>>>>>> PCI #3 may share with onboard RAID and SATA controller
> > >>>>>>>>>>> PCI 4 may not share with anything.
> > >>>>>>>>>>>
> > >>>>>>>>>>> This is the way the ASUS A8V mobo is configured but it's for
> AMD
> > >>>>>>>>>>> CPU's.
> > >>>>>>>>>>>
> > >>>>>>>>>>> Do you have the manual? All of this is listed in chapter 2
> under
> > >>>>>>>>>>> the
> > >>>>>>>>>> heading
> > >>>>>>>>>>> Interrupt Assignments. It should be noted for Intel mobo's
as
> > >>>>>>>>>>> well.
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>> If it's 6, try putting the EDS card in PCI 2, 3, 4 or 5
> > >>>>>>>>>>> If it's 5, try PCI slot 1,
> > >>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> > >>>>>>>>>>> news:4509fd03@linux...
> > >>>>>>>>>>>> It's an Asus P5P800 SE board with a Pentium 4 HT chip.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in message
> > >>>>>>>>>>>> news:4509f8fc@linux...
> > >>>>>>>>>>>>> What kind of mobo are you using Jimmy?
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> > >>>>>>>>>>>>> news:4509eda3@linux...
> > >>>>>>>>>>>>>> I couldn't find any place where it indicated which IRQ
the
> > >>>>>>>>>>>>>> AGP was
> > >>>>>>>>>>>>> assigned.
> > >>>>>>>>>>>>>> The IRQ page had all IRQs assigned to "PCI", and beneath
> that
> > >>>>>>>>>>>>>> all
> > >>>>>>>>> the
> > >>>>>>>>>>> PCI
> > >>>>>>>>>>>>>> slots all assigned to "AUTO". On another page the serial
> port
> > >>>>>>>>>>>>>> was
> > >>>>>>>>>>>>>> assigned
> > >>>>>>>>>>>>>> to IRQ 4, and the parallel port was assigned to IRQ 7. So
I
> > >>>>>>>> assigned
> > >>>>>>>>>>> the
> > >>>>>>>>>>>>> PCI
> > >>>>>>>>>>>>>> slots to other numbers.
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> Am I on the wrong track here?
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in
message
> > >>>>>>>>>>>>>> news:4509da19@linux...
> > >>>>>>>>>>>>>>> Repeat after me:
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>> IRQ!! IRQ!! IRQ!!
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>> This sounds exactly like the EDS card is sharing and
> > >>>>>>>>>>>>>>> interrupt
> > >>>>>>>>> with
> > >>>>>>>>>>> the
> > >>>>>>>>>>>>>>> AGP
> > >>>>>>>>>>>>>>> slot.
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in
message
> > >>>>>>>>>>>>>>> news:45098f86$1@linux...
> > >>>>>>>>>>>>>>>> Hi-ho.
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> I am still having trouble with my Paris rig. In an
effort
> > >>>>>>>>>>>>>>>> to
> > >>>>>>>>>>> simplify
> > >>>>>>>>>>>>>>> things,
> > >>>>>>>>>>>>>>>> I only have one card installed, with an MEC attached,
> > >>>>>>>>>>>>>>>> internal
> > >>>>>>>>>>>>> clocking.
> > >>>>>>>>>>>>>>>> Basically, my problems are down to two:
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> 1.The "now-line" freezes, or more actually begins
> > >>>>>>>>>>>>>>>> stuttering in
> > >>>>>>>>>>>>> extremely
> > >>>>>>>>>>>>>>>> slow-motion, almost glacial. I can still change
windows,
> > >>>>>>>>>>>>>>>> and I
> > >>>>>>>>> am
> > >>>>>>>>>>> able
> > >>>>>>>>>>>>> to
> > >>>>>>>>>>>>>>>> save and close, then re-open Paris with success.
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> 2.On starting Paris, I get an error message: "I/O
modules
> > >>>>>>>>>>>>>>>> used
> > >>>>>>>>> in
> > >>>>>>>>>>> this
> > >>>>>>>>>>>>>>> patch
> > >>>>>>>>>>>>>>>> setting not avaiable in this configuration of Paris.
> > >>>>>>>>>>>>>>>> Resulting
> > >>>>>>>>>> audio
> > >>>>>>>>>>>>> may
> > >>>>>>>>>>>>>>>> be different than when saved." This will pop up 2 or 4
> > >>>>>>>>>>>>>>>> times,
> > >>>>>>>>> and
> > >>>>>>>>>>> then
> > >>>>>>>>>>>>>>> when
> > >>>>>>>>>>>>>>>> I push "play" no audio is heard. Then I close, reopen,
> and
> > >>>>>>>>>>>>>>>> then
> > >>>>>>>>>>> things
> > >>>>>>>>>>>>>>> work
> > >>>>>>>>>>>>>>>> for a while.
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> I have made some tweaks to the configuration with some
> > >>>>>>>>>>>>>>>> success.
> > >>>>>>>>>> The
> > >>>>>>>>>>>>>>>> errors
> > >>>>>>>>>>>>>>>> are happening less and less, but they still pop up.
> > >>>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>>> Anybody?
> > >>>>>>>>>>>>>>>> Jimmy
> > >>>>>>>>>>>>>>>
> > >>>>>>>>>>>>>>
> > >>>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>
> > >>>>>>
> > >>>>>
> > >>>>>
> > >>>>
> > >>>>
> > >>>
> > >>>
> > >>
> > >>
> > >
> > >
> >
> >
>
>
|
|
|
|
| Re: still fighting for stability [message #72509 is a reply to message #72506] |
Sat, 16 September 2006 13:41 |
Deej [1]
Messages: 2149
Registered: January 2006
|
Senior Member |
|
|
Yes. Absolutely. That overcurrent message will show up even if there is
nothing on the USB .......at least it did with mine.
"Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
news:450c4585@linux...
> So, rollback the BIOS even if I'm NOT going to disable the USB?
>
>
> "DJ" <animix_spam-this-ahole_@animas.net> wrote in message
> news:450b9090@linux...
> > Jimmy,
> >
> > Glad you're getting this resolved. At your earliest opportunity, get rid
> of
> > that bios and go back to the one previous to the USB overcurrent
warning.
> > Really man. That bios you're running right now is a disaster waiting for
a
> > place to happen, and happen, and happen again.....I promise. It's going
to
> > bite you at the worst time and you're going to have to continuously
clear
> > the CMOS to get your machine to function as long as you're running that
> > bios. Nothing worse than a computer that won't boot.
> >
> > Deej
> >
> > "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> > news:450b7e60@linux...
> > > Alrighty. then. I tried the battery/jumper-cap thingie with great
> success.
> > > Booted right up, with obvious changes to BIOS and VGA buffers and all
> > else.
> > >
> > > Then I made a few of the various previously suggested BIOS changes
with
> > > which I felt comfortable and got 1 hr 15 minutes of good, vital work
> done.
> > >
> > > I've had a few different troubles these past few days (months).
Tonight
> I
> > > have tried a various few fixes, and experienced some vexing troubles
and
> > > corresponding victories, but I haven't had time tonight to really
> > > stress-test things. I'm not convinced that things are tight yet, as
I've
> > > been far too bedeviled in recent days to relax now without several
> > > sessions-worth of hard use.
> > >
> > > Gotta session off-site tomorrow (Swen's studio), so I'll be back on my
> own
> > > rig Sunday (yay NFL football!).
> > >
> > > I just want to thank everybody here for their sincere and dilligent
> > efforts
> > > in helping an ignernt fellow like myself. I wish I could make all of
you
> a
> > > big banquet dinner in thanks. I'm a damn fine cook, just not so much a
> > damn
> > > fine computer tech.
> > >
> > > I figure I'll start a new thread if things aren't right yet. I got us
> off
> > on
> > > a defective-BIOS tangent there.....the rig did feel pretty good there
> for
> > an
> > > hour or so, though.....
> > >
> > > Jimmy
> > >
> > >
> > > "Aaron Allen" <know-spam@not_here.dude> wrote in message
> > > news:450b60d5@linux...
> > > > yup
> > > >
> > > > "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> > > > news:450b5d6b@linux...
> > > >> Ummm, I'm sorta freaked out and wanting precision right now. You
> mean,
> > > >> "That's the ticket", right?
> > > >>
> > > >>
> > > >> "Aaron Allen" <know-spam@not_here.dude> wrote in message
> > > >> news:450b5c7c@linux...
> > > >>> That's your daisy.
> > > >>> AA
> > > >>>
> > > >>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> > > >>> news:450b584d@linux...
> > > >>>> The only thing I can see for this is to "clear the Real Time
Clock
> > RAM
> > > >>>> in CMOS". This would "clear the CMOS memory of date, time, and
> system
> > > >>>> setup parameters by erasing the CMOS RTC RAM data".
> > > >>>>
> > > >>>> This involves removing the onboard battery and moving jumper cap
> from
> > > >>>> pins 1-2 to pins 2-3., then back to pins 1-2, then reinstalling
the
> > > >>>> battery. It says you have to enter the BIOS and re-enter data.
> > > >>>>
> > > >>>> Is this the thing to do?
> > > >>>> "Martin Harrington" <lendan@bigpond.net.au> wrote in message
> > > >>>> news:450b4d10@linux...
> > > >>>>> All you need do is reset the BIOS by shorting out the relevant
> > jumper
> > > >>>>> on the motherboard...it's in the manual.
> > > >>>>> --
> > > >>>>> Martin Harrington
> > > >>>>> www.lendanear-sound.com
> > > >>>>>
> > > >>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> > > >>>>> news:450b4198@linux...
> > > >>>>>>I disabledall but the com1 and lpt 1. Can't find them.
> > > >>>>>>
> > > >>>>>> Bad news is, and this is really bad news, computer won't boot
up.
> > On
> > > >>>>>> that blcak page that n ow doesn't flash by so fast at all, I
get
> > the
> > > >>>>>> error message "USB device over current status detected". Then
the
> > > >>>>>> computer shuts down. Won't boot up, won't let me go to BIOS to
> fix
> > > >>>>>> it.
> > > >>>>>>
> > > >>>>>> Heeeeeelp!
> > > >>>>>>
> > > >>>>>>
> > > >>>>>> "John" <no@no.com> wrote in message news:450b3aac$1@linux...
> > > >>>>>>> It looks like another messed up Asus manual. I downloaded
the
> > > >>>>>>> manual and on page 2-18 it has that pic. I would turn off
Com1
> > > >>>>>>> (irq4), floppy (irq 6), lpt1 (irq 7), Serial port, turn off
> > onboard
> > > >>>>>>> audio and USB, Keep the LAN on so you can network but I would
> try
> > > >>>>>>> only slots 3 and 4 only first. Notice how they don't even show
> > audio
> > > >>>>>>> sharing with anything. This diagram is craptastic.
> > > >>>>>>>
> > > >>>>>>> And turn off Hyper Threading.
> > > >>>>>>>
> > > >>>>>>> Do ME and favor and call them on the phone and ask then what
the
> > > >>>>>>> hell is this diagram means. Simply, what slots share with
> what?
> > > >>>>>>> Inquiring minds !
> > > >>>>>>>
> > > >>>>>>> John
> > > >>>>>>>
> > > >>>>>>> Uptown Jimmy wrote:
> > > >>>>>>>> I guess I don't understand what the Alphabetized row
indicates.
> > In
> > > >>>>>>>> other
> > > >>>>>>>> words, if PCI slot 1 "shared" with 'F', what does that mean?
> What
> > > >>>>>>>> is it
> > > >>>>>>>> shared with?
> > > >>>>>>>>
> > > >>>>>>>>
> > > >>>>>>>> "John" <no@no.com> wrote in message news:450af67f$1@linux...
> > > >>>>>>>>> Use the second section that shows what are shared. Then
make
> > sure
> > > >>>>>>>>> your
> > > >>>>>>>> EDS
> > > >>>>>>>>> cards are NOT on them. For example, turn off onboard audio
> in
> > > >>>>>>>>> bios and
> > > >>>>>>>>> now you can use the slot that shares with onboard audio.
Any
> > > >>>>>>>>> device that
> > > >>>>>>>>> you are using like AGP video you DO NOT want an EDS card to
be
> > on
> > > >>>>>>>>> a shared
> > > >>>>>>>>> slot.
> > > >>>>>>>>>
> > > >>>>>>>>> On boot up check to make sure that the black screen that
> flashes
> > > >>>>>>>>> by shows
> > > >>>>>>>>> this correctly.
> > > >>>>>>>>>
> > > >>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote:
> > > >>>>>>>>>> Okay, on the IRQ page in the manual, it has two sections:
> > > >>>>>>>>>>
> > > >>>>>>>>>> 1. "Standard interrupt assignments", which list IRQ numbers
> and
> > > >>>>>>>>>> their
> > > >>>>>>>>>> "standard function". (This section does list 7 "IRQs are
> > usually
> > > >>>>>>>> available
> > > >>>>>>>>>> for PCI devices")
> > > >>>>>>>>>>
> > > >>>>>>>>>> 2. "IRQ" assignments for this motherboard", which graphs
> > various
> > > >>>>>>>>>> PCI
> > > >>>>>>>> slots
> > > >>>>>>>>>> or USB controllers as "nil", "shared", or "used" against
> > letters
> > > >>>>>>>>>> of the
> > > >>>>>>>>>> alphabet.
> > > >>>>>>>>>>
> > > >>>>>>>>>> I don't know how to use these two sets of data to resolve
my
> > > >>>>>>>>>> problem.
> > > >>>>>>>> They
> > > >>>>>>>>>> seem incompatible. I feel ignernt.
> > > >>>>>>>>>>
> > > >>>>>>>>>>
> > > >>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in message
> > > >>>>>>>>>> news:450a0f48@linux...
> > > >>>>>>>>>>> Hmmm.....well .......letsee.........ASUS boards normally
> will
> > > >>>>>>>>>>> have the
> > > >>>>>>>>> AGP
> > > >>>>>>>>>>> sharing an IRQ with two PCI slots, basically making these
> > > >>>>>>>>>>> worthless for
> > > >>>>>>>>>>> anything else.
> > > >>>>>>>>>>> How many PCI slots does your mobo have?
> > > >>>>>>>>>>> If it's a 5 slot board and it's similar to an AMD board,
> > chances
> > > >>>>>>>>>>> are
> > > >>>>>>>> that
> > > >>>>>>>>>>> PCI slots 1 and 5 are shared with the AGP and the firewire
> > port
> > > >>>>>>>>>>> (thus
> > > >>>>>>>>>> making
> > > >>>>>>>>>>> FW audio interfaces iffy also if using the onboard FW)
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> PCI slot 2 may share with your LAN controller
> > > >>>>>>>>>>> PCI #3 may share with onboard RAID and SATA controller
> > > >>>>>>>>>>> PCI 4 may not share with anything.
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> This is the way the ASUS A8V mobo is configured but it's
for
> > AMD
> > > >>>>>>>>>>> CPU's.
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> Do you have the manual? All of this is listed in chapter 2
> > under
> > > >>>>>>>>>>> the
> > > >>>>>>>>>> heading
> > > >>>>>>>>>>> Interrupt Assignments. It should be noted for Intel mobo's
> as
> > > >>>>>>>>>>> well.
> > > >>>>>>>>>>>
> > > >>>>>>>>>>>
> > > >>>>>>>>>>>
> > > >>>>>>>>>>> If it's 6, try putting the EDS card in PCI 2, 3, 4 or 5
> > > >>>>>>>>>>> If it's 5, try PCI slot 1,
> > > >>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> > > >>>>>>>>>>> news:4509fd03@linux...
> > > >>>>>>>>>>>> It's an Asus P5P800 SE board with a Pentium 4 HT chip.
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in
message
> > > >>>>>>>>>>>> news:4509f8fc@linux...
> > > >>>>>>>>>>>>> What kind of mobo are you using Jimmy?
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in
message
> > > >>>>>>>>>>>>> news:4509eda3@linux...
> > > >>>>>>>>>>>>>> I couldn't find any place where it indicated which IRQ
> the
> > > >>>>>>>>>>>>>> AGP was
> > > >>>>>>>>>>>>> assigned.
> > > >>>>>>>>>>>>>> The IRQ page had all IRQs assigned to "PCI", and
beneath
> > that
> > > >>>>>>>>>>>>>> all
> > > >>>>>>>>> the
> > > >>>>>>>>>>> PCI
> > > >>>>>>>>>>>>>> slots all assigned to "AUTO". On another page the
serial
> > port
> > > >>>>>>>>>>>>>> was
> > > >>>>>>>>>>>>>> assigned
> > > >>>>>>>>>>>>>> to IRQ 4, and the parallel port was assigned to IRQ 7.
So
> I
> > > >>>>>>>> assigned
> > > >>>>>>>>>>> the
> > > >>>>>>>>>>>>> PCI
> > > >>>>>>>>>>>>>> slots to other numbers.
> > > >>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>> Am I on the wrong track here?
> > > >>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in
> message
> > > >>>>>>>>>>>>>> news:4509da19@linux...
> > > >>>>>>>>>>>>>>> Repeat after me:
> > > >>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>> IRQ!! IRQ!! IRQ!!
> > > >>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>> This sounds exactly like the EDS card is sharing and
> > > >>>>>>>>>>>>>>> interrupt
> > > >>>>>>>>> with
> > > >>>>>>>>>>> the
> > > >>>>>>>>>>>>>>> AGP
> > > >>>>>>>>>>>>>>> slot.
> > > >>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in
> message
> > > >>>>>>>>>>>>>>> news:45098f86$1@linux...
> > > >>>>>>>>>>>>>>>> Hi-ho.
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> I am still having trouble with my Paris rig. In an
> effort
> > > >>>>>>>>>>>>>>>> to
> > > >>>>>>>>>>> simplify
> > > >>>>>>>>>>>>>>> things,
> > > >>>>>>>>>>>>>>>> I only have one card installed, with an MEC attached,
> > > >>>>>>>>>>>>>>>> internal
> > > >>>>>>>>>>>>> clocking.
> > > >>>>>>>>>>>>>>>> Basically, my problems are down to two:
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> 1.The "now-line" freezes, or more actually begins
> > > >>>>>>>>>>>>>>>> stuttering in
> > > >>>>>>>>>>>>> extremely
> > > >>>>>>>>>>>>>>>> slow-motion, almost glacial. I can still change
> windows,
> > > >>>>>>>>>>>>>>>> and I
> > > >>>>>>>>> am
> > > >>>>>>>>>>> able
> > > >>>>>>>>>>>>> to
> > > >>>>>>>>>>>>>>>> save and close, then re-open Paris with success.
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> 2.On starting Paris, I get an error message: "I/O
> modules
> > > >>>>>>>>>>>>>>>> used
> > > >>>>>>>>> in
> > > >>>>>>>>>>> this
> > > >>>>>>>>>>>>>>> patch
> > > >>>>>>>>>>>>>>>> setting not avaiable in this configuration of Paris.
> > > >>>>>>>>>>>>>>>> Resulting
> > > >>>>>>>>>> audio
> > > >>>>>>>>>>>>> may
> > > >>>>>>>>>>>>>>>> be different than when saved." This will pop up 2 or
4
> > > >>>>>>>>>>>>>>>> times,
> > > >>>>>>>>> and
> > > >>>>>>>>>>> then
> > > >>>>>>>>>>>>>>> when
> > > >>>>>>>>>>>>>>>> I push "play" no audio is heard. Then I close,
reopen,
> > and
> > > >>>>>>>>>>>>>>>> then
> > > >>>>>>>>>>> things
> > > >>>>>>>>>>>>>>> work
> > > >>>>>>>>>>>>>>>> for a while.
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> I have made some tweaks to the configuration with
some
> > > >>>>>>>>>>>>>>>> success.
> > > >>>>>>>>>> The
> > > >>>>>>>>>>>>>>>> errors
> > > >>>>>>>>>>>>>>>> are happening less and less, but they still pop up.
> > > >>>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>>> Anybody?
> > > >>>>>>>>>>>>>>>> Jimmy
> > > >>>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>>
> > > >>>>>>>>>>>>>
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>
> > > >>>>>>>>>>
> > > >>>>>>>>
> > > >>>>>>
> > > >>>>>
> > > >>>>>
> > > >>>>
> > > >>>>
> > > >>>
> > > >>>
> > > >>
> > > >>
> > > >
> > > >
> > >
> > >
> >
> >
>
>
|
|
|
|
| Re: still fighting for stability [message #72518 is a reply to message #72502] |
Sat, 16 September 2006 18:07 |
John [1]
Messages: 2229
Registered: September 2005
|
Senior Member |
|
|
How many eds cards do you have?
Were you able to find out what that cryptic irq diagram means?
John
"Uptown Jimmy" <johnson314@bellsouth.net> wrote:
>I hope Swen still has his floppy drive installed. I've got mine around here
>somewhere...
>
>Jimmy
>
>"DJ" <animix_spam-this-ahole_@animas.net> wrote in message
>news:450b9090@linux...
>> Jimmy,
>>
>> Glad you're getting this resolved. At your earliest opportunity, get rid
>of
>> that bios and go back to the one previous to the USB overcurrent warning.
>> Really man. That bios you're running right now is a disaster waiting for
a
>> place to happen, and happen, and happen again.....I promise. It's going
to
>> bite you at the worst time and you're going to have to continuously clear
>> the CMOS to get your machine to function as long as you're running that
>> bios. Nothing worse than a computer that won't boot.
>>
>> Deej
>>
>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
>> news:450b7e60@linux...
>> > Alrighty. then. I tried the battery/jumper-cap thingie with great
>success.
>> > Booted right up, with obvious changes to BIOS and VGA buffers and all
>> else.
>> >
>> > Then I made a few of the various previously suggested BIOS changes with
>> > which I felt comfortable and got 1 hr 15 minutes of good, vital work
>done.
>> >
>> > I've had a few different troubles these past few days (months). Tonight
>I
>> > have tried a various few fixes, and experienced some vexing troubles
and
>> > corresponding victories, but I haven't had time tonight to really
>> > stress-test things. I'm not convinced that things are tight yet, as
I've
>> > been far too bedeviled in recent days to relax now without several
>> > sessions-worth of hard use.
>> >
>> > Gotta session off-site tomorrow (Swen's studio), so I'll be back on
my
>own
>> > rig Sunday (yay NFL football!).
>> >
>> > I just want to thank everybody here for their sincere and dilligent
>> efforts
>> > in helping an ignernt fellow like myself. I wish I could make all of
you
>a
>> > big banquet dinner in thanks. I'm a damn fine cook, just not so much
a
>> damn
>> > fine computer tech.
>> >
>> > I figure I'll start a new thread if things aren't right yet. I got us
>off
>> on
>> > a defective-BIOS tangent there.....the rig did feel pretty good there
>for
>> an
>> > hour or so, though.....
>> >
>> > Jimmy
>> >
>> >
>> > "Aaron Allen" <know-spam@not_here.dude> wrote in message
>> > news:450b60d5@linux...
>> > > yup
>> > >
>> > > "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
>> > > news:450b5d6b@linux...
>> > >> Ummm, I'm sorta freaked out and wanting precision right now. You
>mean,
>> > >> "That's the ticket", right?
>> > >>
>> > >>
>> > >> "Aaron Allen" <know-spam@not_here.dude> wrote in message
>> > >> news:450b5c7c@linux...
>> > >>> That's your daisy.
>> > >>> AA
>> > >>>
>> > >>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
>> > >>> news:450b584d@linux...
>> > >>>> The only thing I can see for this is to "clear the Real Time Clock
>> RAM
>> > >>>> in CMOS". This would "clear the CMOS memory of date, time, and
>system
>> > >>>> setup parameters by erasing the CMOS RTC RAM data".
>> > >>>>
>> > >>>> This involves removing the onboard battery and moving jumper cap
>from
>> > >>>> pins 1-2 to pins 2-3., then back to pins 1-2, then reinstalling
the
>> > >>>> battery. It says you have to enter the BIOS and re-enter data.
>> > >>>>
>> > >>>> Is this the thing to do?
>> > >>>> "Martin Harrington" <lendan@bigpond.net.au> wrote in message
>> > >>>> news:450b4d10@linux...
>> > >>>>> All you need do is reset the BIOS by shorting out the relevant
>> jumper
>> > >>>>> on the motherboard...it's in the manual.
>> > >>>>> --
>> > >>>>> Martin Harrington
>> > >>>>> www.lendanear-sound.com
>> > >>>>>
>> > >>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
>> > >>>>> news:450b4198@linux...
>> > >>>>>>I disabledall but the com1 and lpt 1. Can't find them.
>> > >>>>>>
>> > >>>>>> Bad news is, and this is really bad news, computer won't boot
up.
>> On
>> > >>>>>> that blcak page that n ow doesn't flash by so fast at all, I
get
>> the
>> > >>>>>> error message "USB device over current status detected". Then
the
>> > >>>>>> computer shuts down. Won't boot up, won't let me go to BIOS to
>fix
>> > >>>>>> it.
>> > >>>>>>
>> > >>>>>> Heeeeeelp!
>> > >>>>>>
>> > >>>>>>
>> > >>>>>> "John" <no@no.com> wrote in message news:450b3aac$1@linux...
>> > >>>>>>> It looks like another messed up Asus manual. I downloaded
the
>> > >>>>>>> manual and on page 2-18 it has that pic. I would turn off Com1
>> > >>>>>>> (irq4), floppy (irq 6), lpt1 (irq 7), Serial port, turn off
>> onboard
>> > >>>>>>> audio and USB, Keep the LAN on so you can network but I would
>try
>> > >>>>>>> only slots 3 and 4 only first. Notice how they don't even show
>> audio
>> > >>>>>>> sharing with anything. This diagram is craptastic.
>> > >>>>>>>
>> > >>>>>>> And turn off Hyper Threading.
>> > >>>>>>>
>> > >>>>>>> Do ME and favor and call them on the phone and ask then what
the
>> > >>>>>>> hell is this diagram means. Simply, what slots share with
>what?
>> > >>>>>>> Inquiring minds !
>> > >>>>>>>
>> > >>>>>>> John
>> > >>>>>>>
>> > >>>>>>> Uptown Jimmy wrote:
>> > >>>>>>>> I guess I don't understand what the Alphabetized row indicates.
>> In
>> > >>>>>>>> other
>> > >>>>>>>> words, if PCI slot 1 "shared" with 'F', what does that mean?
>What
>> > >>>>>>>> is it
>> > >>>>>>>> shared with?
>> > >>>>>>>>
>> > >>>>>>>>
>> > >>>>>>>> "John" <no@no.com> wrote in message news:450af67f$1@linux...
>> > >>>>>>>>> Use the second section that shows what are shared. Then make
>> sure
>> > >>>>>>>>> your
>> > >>>>>>>> EDS
>> > >>>>>>>>> cards are NOT on them. For example, turn off onboard audio
>in
>> > >>>>>>>>> bios and
>> > >>>>>>>>> now you can use the slot that shares with onboard audio.
Any
>> > >>>>>>>>> device that
>> > >>>>>>>>> you are using like AGP video you DO NOT want an EDS card to
be
>> on
>> > >>>>>>>>> a shared
>> > >>>>>>>>> slot.
>> > >>>>>>>>>
>> > >>>>>>>>> On boot up check to make sure that the black screen that
>flashes
>> > >>>>>>>>> by shows
>> > >>>>>>>>> this correctly.
>> > >>>>>>>>>
>> > >>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote:
>> > >>>>>>>>>> Okay, on the IRQ page in the manual, it has two sections:
>> > >>>>>>>>>>
>> > >>>>>>>>>> 1. "Standard interrupt assignments", which list IRQ numbers
>and
>> > >>>>>>>>>> their
>> > >>>>>>>>>> "standard function". (This section does list 7 "IRQs are
>> usually
>> > >>>>>>>> available
>> > >>>>>>>>>> for PCI devices")
>> > >>>>>>>>>>
>> > >>>>>>>>>> 2. "IRQ" assignments for this motherboard", which graphs
>> various
>> > >>>>>>>>>> PCI
>> > >>>>>>>> slots
>> > >>>>>>>>>> or USB controllers as "nil", "shared", or "used" against
>> letters
>> > >>>>>>>>>> of the
>> > >>>>>>>>>> alphabet.
>> > >>>>>>>>>>
>> > >>>>>>>>>> I don't know how to use these two sets of data to resolve
my
>> > >>>>>>>>>> problem.
>> > >>>>>>>> They
>> > >>>>>>>>>> seem incompatible. I feel ignernt.
>> > >>>>>>>>>>
>> > >>>>>>>>>>
>> > >>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in message
>> > >>>>>>>>>> news:450a0f48@linux...
>> > >>>>>>>>>>> Hmmm.....well .......letsee.........ASUS boards normally
>will
>> > >>>>>>>>>>> have the
>> > >>>>>>>>> AGP
>> > >>>>>>>>>>> sharing an IRQ with two PCI slots, basically making these
>> > >>>>>>>>>>> worthless for
>> > >>>>>>>>>>> anything else.
>> > >>>>>>>>>>> How many PCI slots does your mobo have?
>> > >>>>>>>>>>> If it's a 5 slot board and it's similar to an AMD board,
>> chances
>> > >>>>>>>>>>> are
>> > >>>>>>>> that
>> > >>>>>>>>>>> PCI slots 1 and 5 are shared with the AGP and the firewire
>> port
>> > >>>>>>>>>>> (thus
>> > >>>>>>>>>> making
>> > >>>>>>>>>>> FW audio interfaces iffy also if using the onboard FW)
>> > >>>>>>>>>>>
>> > >>>>>>>>>>> PCI slot 2 may share with your LAN controller
>> > >>>>>>>>>>> PCI #3 may share with onboard RAID and SATA controller
>> > >>>>>>>>>>> PCI 4 may not share with anything.
>> > >>>>>>>>>>>
>> > >>>>>>>>>>> This is the way the ASUS A8V mobo is configured but it's
for
>> AMD
>> > >>>>>>>>>>> CPU's.
>> > >>>>>>>>>>>
>> > >>>>>>>>>>> Do you have the manual? All of this is listed in chapter
2
>> under
>> > >>>>>>>>>>> the
>> > >>>>>>>>>> heading
>> > >>>>>>>>>>> Interrupt Assignments. It should be noted for Intel mobo's
>as
>> > >>>>>>>>>>> well.
>> > >>>>>>>>>>>
>> > >>>>>>>>>>>
>> > >>>>>>>>>>>
>> > >>>>>>>>>>> If it's 6, try putting the EDS card in PCI 2, 3, 4 or 5
>> > >>>>>>>>>>> If it's 5, try PCI slot 1,
>> > >>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
>> > >>>>>>>>>>> news:4509fd03@linux...
>> > >>>>>>>>>>>> It's an Asus P5P800 SE board with a Pentium 4 HT chip.
>> > >>>>>>>>>>>>
>> > >>>>>>>>>>>>
>> > >>>>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in message
>> > >>>>>>>>>>>> news:4509f8fc@linux...
>> > >>>>>>>>>>>>> What kind of mobo are you using Jimmy?
>> > >>>>>>>>>>>>>
>> > >>>>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
>> > >>>>>>>>>>>>> news:4509eda3@linux...
>> > >>>>>>>>>>>>>> I couldn't find any place where it indicated which IRQ
>the
>> > >>>>>>>>>>>>>> AGP was
>> > >>>>>>>>>>>>> assigned.
>> > >>>>>>>>>>>>>> The IRQ page had all IRQs assigned to "PCI", and beneath
>> that
>> > >>>>>>>>>>>>>> all
>> > >>>>>>>>> the
>> > >>>>>>>>>>> PCI
>> > >>>>>>>>>>>>>> slots all assigned to "AUTO". On another page the serial
>> port
>> > >>>>>>>>>>>>>> was
>> > >>>>>>>>>>>>>> assigned
>> > >>>>>>>>>>>>>> to IRQ 4, and the parallel port was assigned to IRQ 7.
So
>I
>> > >>>>>>>> assigned
>> > >>>>>>>>>>> the
>> > >>>>>>>>>>>>> PCI
>> > >>>>>>>>>>>>>> slots to other numbers.
>> > >>>>>>>>>>>>>>
>> > >>>>>>>>>>>>>> Am I on the wrong track here?
>> > >>>>>>>>>>>>>>
>> > >>>>>>>>>>>>>>
>> > >>>>>>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in
>message
>> > >>>>>>>>>>>>>> news:4509da19@linux...
>> > >>>>>>>>>>>>>>> Repeat after me:
>> > >>>>>>>>>>>>>>>
>> > >>>>>>>>>>>>>>> IRQ!! IRQ!! IRQ!!
>> > >>>>>>>>>>>>>>>
>> > >>>>>>>>>>>>>>> This sounds exactly like the EDS card is sharing and
>> > >>>>>>>>>>>>>>> interrupt
>> > >>>>>>>>> with
>> > >>>>>>>>>>> the
>> > >>>>>>>>>>>>>>> AGP
>> > >>>>>>>>>>>>>>> slot.
>> > >>>>>>>>>>>>>>>
>> > >>>>>>>>>>>>>>>
>> > >>>>>>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in
>message
>> > >>>>>>>>>>>>>>> news:45098f86$1@linux...
>> > >>>>>>>>>>>>>>>> Hi-ho.
>> > >>>>>>>>>>>>>>>>
>> > >>>>>>>>>>>>>>>> I am still having trouble with my Paris rig. In an
>effort
>> > >>>>>>>>>>>>>>>> to
>> > >>>>>>>>>>> simplify
>> > >>>>>>>>>>>>>>> things,
>> > >>>>>>>>>>>>>>>> I only have one card installed, with an MEC attached,
>> > >>>>>>>>>>>>>>>> internal
>> > >>>>>>>>>>>>> clocking.
>> > >>>>>>>>>>>>>>>> Basically, my problems are down to two:
>> > >>>>>>>>>>>>>>>>
>> > >>>>>>>>>>>>>>>> 1.The "now-line" freezes, or more actually begins
>> > >>>>>>>>>>>>>>>> stuttering in
>> > >>>>>>>>>>>>> extremely
>> > >>>>>>>>>>>>>>>> slow-motion, almost glacial. I can still change
>windows,
>> > >>>>>>>>>>>>>>>> and I
>> > >>>>>>>>> am
>> > >>>>>>>>>>> able
>> > >>>>>>>>>>>>> to
>> > >>>>>>>>>>>>>>>> save and close, then re-open Paris with success.
>> > >>>>>>>>>>>>>>>>
>> > >>>>>>>>>>>>>>>> 2.On starting Paris, I get an error message: "I/O
>modules
>> > >>>>>>>>>>>>>>>> used
>> > >>>>>>>>> in
>> > >>>>>>>>>>> this
>> > >>>>>>>>>>>>>>> patch
>> > >>>>>>>>>>>>>>>> setting not avaiable in this configuration of Paris.
>> > >>>>>>>>>>>>>>>> Resulting
>> > >>>>>>>>>> audio
>> > >>>>>>>>>>>>> may
>> > >>>>>>>>>>>>>>>> be different than when saved." This will pop up 2 or
4
>> > >>>>>>>>>>>>>>>> times,
>> > >>>>>>>>> and
>> > >>>>>>>>>>> then
>> > >>>>>>>>>>>>>>> when
>> > >>>>>>>>>>>>>>>> I push "play" no audio is heard. Then I close, reopen,
>> and
>> > >>>>>>>>>>>>>>>> then
>> > >>>>>>>>>>> things
>> > >>>>>>>>>>>>>>> work
>> > >>>>>>>>>>>>>>>> for a while.
>> > >>>>>>>>>>>>>>>>
>> > >>>>>>>>>>>>>>>> I have made some tweaks to the configuration with some
>> > >>>>>>>>>>>>>>>> success.
>> > >>>>>>>>>> The
>> > >>>>>>>>>>>>>>>> errors
>> > >>>>>>>>>>>>>>>> are happening less and less, but they still pop up.
>> > >>>>>>>>>>>>>>>>
>> > >>>>>>>>>>>>>>>> Anybody?
>> > >>>>>>>>>>>>>>>> Jimmy
>> > >>>>>>>>>>>>>>>
>> > >>>>>>>>>>>>>>
>> > >>>>>>>>>>>>>
>> > >>>>>>>>>>>>
>> > >>>>>>>>>>>
>> > >>>>>>>>>>
>> > >>>>>>>>
>> > >>>>>>
>> > >>>>>
>> > >>>>>
>> > >>>>
>> > >>>>
>> > >>>
>> > >>>
>> > >>
>> > >>
>> > >
>> > >
>> >
>> >
>>
>>
>
>
|
|
|
|
| Re: still fighting for stability [message #72573 is a reply to message #72518] |
Sun, 17 September 2006 17:00 |
uptown jimmy
Messages: 441
Registered: September 2005
|
Senior Member |
|
|
They never called me back. I'll badger them tomorrow.
I was using 4 EDS cards, and I want very much to do so again, but right now
I'm bug-fixing with a minimal setup, just one card, internal clocking.
Jimmy
"John" <no@no.com> wrote in message news:450c9fd8$1@linux...
>
> How many eds cards do you have?
> Were you able to find out what that cryptic irq diagram means?
>
> John
>
> "Uptown Jimmy" <johnson314@bellsouth.net> wrote:
> >I hope Swen still has his floppy drive installed. I've got mine around
here
> >somewhere...
> >
> >Jimmy
> >
> >"DJ" <animix_spam-this-ahole_@animas.net> wrote in message
> >news:450b9090@linux...
> >> Jimmy,
> >>
> >> Glad you're getting this resolved. At your earliest opportunity, get
rid
> >of
> >> that bios and go back to the one previous to the USB overcurrent
warning.
> >> Really man. That bios you're running right now is a disaster waiting
for
> a
> >> place to happen, and happen, and happen again.....I promise. It's going
> to
> >> bite you at the worst time and you're going to have to continuously
clear
> >> the CMOS to get your machine to function as long as you're running that
> >> bios. Nothing worse than a computer that won't boot.
> >>
> >> Deej
> >>
> >> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> >> news:450b7e60@linux...
> >> > Alrighty. then. I tried the battery/jumper-cap thingie with great
> >success.
> >> > Booted right up, with obvious changes to BIOS and VGA buffers and all
> >> else.
> >> >
> >> > Then I made a few of the various previously suggested BIOS changes
with
> >> > which I felt comfortable and got 1 hr 15 minutes of good, vital work
> >done.
> >> >
> >> > I've had a few different troubles these past few days (months).
Tonight
> >I
> >> > have tried a various few fixes, and experienced some vexing troubles
> and
> >> > corresponding victories, but I haven't had time tonight to really
> >> > stress-test things. I'm not convinced that things are tight yet, as
> I've
> >> > been far too bedeviled in recent days to relax now without several
> >> > sessions-worth of hard use.
> >> >
> >> > Gotta session off-site tomorrow (Swen's studio), so I'll be back on
> my
> >own
> >> > rig Sunday (yay NFL football!).
> >> >
> >> > I just want to thank everybody here for their sincere and dilligent
> >> efforts
> >> > in helping an ignernt fellow like myself. I wish I could make all of
> you
> >a
> >> > big banquet dinner in thanks. I'm a damn fine cook, just not so much
> a
> >> damn
> >> > fine computer tech.
> >> >
> >> > I figure I'll start a new thread if things aren't right yet. I got us
> >off
> >> on
> >> > a defective-BIOS tangent there.....the rig did feel pretty good there
> >for
> >> an
> >> > hour or so, though.....
> >> >
> >> > Jimmy
> >> >
> >> >
> >> > "Aaron Allen" <know-spam@not_here.dude> wrote in message
> >> > news:450b60d5@linux...
> >> > > yup
> >> > >
> >> > > "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> >> > > news:450b5d6b@linux...
> >> > >> Ummm, I'm sorta freaked out and wanting precision right now. You
> >mean,
> >> > >> "That's the ticket", right?
> >> > >>
> >> > >>
> >> > >> "Aaron Allen" <know-spam@not_here.dude> wrote in message
> >> > >> news:450b5c7c@linux...
> >> > >>> That's your daisy.
> >> > >>> AA
> >> > >>>
> >> > >>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> >> > >>> news:450b584d@linux...
> >> > >>>> The only thing I can see for this is to "clear the Real Time
Clock
> >> RAM
> >> > >>>> in CMOS". This would "clear the CMOS memory of date, time, and
> >system
> >> > >>>> setup parameters by erasing the CMOS RTC RAM data".
> >> > >>>>
> >> > >>>> This involves removing the onboard battery and moving jumper cap
> >from
> >> > >>>> pins 1-2 to pins 2-3., then back to pins 1-2, then reinstalling
> the
> >> > >>>> battery. It says you have to enter the BIOS and re-enter data.
> >> > >>>>
> >> > >>>> Is this the thing to do?
> >> > >>>> "Martin Harrington" <lendan@bigpond.net.au> wrote in message
> >> > >>>> news:450b4d10@linux...
> >> > >>>>> All you need do is reset the BIOS by shorting out the relevant
> >> jumper
> >> > >>>>> on the motherboard...it's in the manual.
> >> > >>>>> --
> >> > >>>>> Martin Harrington
> >> > >>>>> www.lendanear-sound.com
> >> > >>>>>
> >> > >>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in message
> >> > >>>>> news:450b4198@linux...
> >> > >>>>>>I disabledall but the com1 and lpt 1. Can't find them.
> >> > >>>>>>
> >> > >>>>>> Bad news is, and this is really bad news, computer won't boot
> up.
> >> On
> >> > >>>>>> that blcak page that n ow doesn't flash by so fast at all, I
> get
> >> the
> >> > >>>>>> error message "USB device over current status detected". Then
> the
> >> > >>>>>> computer shuts down. Won't boot up, won't let me go to BIOS to
> >fix
> >> > >>>>>> it.
> >> > >>>>>>
> >> > >>>>>> Heeeeeelp!
> >> > >>>>>>
> >> > >>>>>>
> >> > >>>>>> "John" <no@no.com> wrote in message news:450b3aac$1@linux...
> >> > >>>>>>> It looks like another messed up Asus manual. I downloaded
> the
> >> > >>>>>>> manual and on page 2-18 it has that pic. I would turn off
Com1
> >> > >>>>>>> (irq4), floppy (irq 6), lpt1 (irq 7), Serial port, turn off
> >> onboard
> >> > >>>>>>> audio and USB, Keep the LAN on so you can network but I would
> >try
> >> > >>>>>>> only slots 3 and 4 only first. Notice how they don't even
show
> >> audio
> >> > >>>>>>> sharing with anything. This diagram is craptastic.
> >> > >>>>>>>
> >> > >>>>>>> And turn off Hyper Threading.
> >> > >>>>>>>
> >> > >>>>>>> Do ME and favor and call them on the phone and ask then what
> the
> >> > >>>>>>> hell is this diagram means. Simply, what slots share with
> >what?
> >> > >>>>>>> Inquiring minds !
> >> > >>>>>>>
> >> > >>>>>>> John
> >> > >>>>>>>
> >> > >>>>>>> Uptown Jimmy wrote:
> >> > >>>>>>>> I guess I don't understand what the Alphabetized row
indicates.
> >> In
> >> > >>>>>>>> other
> >> > >>>>>>>> words, if PCI slot 1 "shared" with 'F', what does that mean?
> >What
> >> > >>>>>>>> is it
> >> > >>>>>>>> shared with?
> >> > >>>>>>>>
> >> > >>>>>>>>
> >> > >>>>>>>> "John" <no@no.com> wrote in message news:450af67f$1@linux...
> >> > >>>>>>>>> Use the second section that shows what are shared. Then
make
> >> sure
> >> > >>>>>>>>> your
> >> > >>>>>>>> EDS
> >> > >>>>>>>>> cards are NOT on them. For example, turn off onboard
audio
> >in
> >> > >>>>>>>>> bios and
> >> > >>>>>>>>> now you can use the slot that shares with onboard audio.
> Any
> >> > >>>>>>>>> device that
> >> > >>>>>>>>> you are using like AGP video you DO NOT want an EDS card to
> be
> >> on
> >> > >>>>>>>>> a shared
> >> > >>>>>>>>> slot.
> >> > >>>>>>>>>
> >> > >>>>>>>>> On boot up check to make sure that the black screen that
> >flashes
> >> > >>>>>>>>> by shows
> >> > >>>>>>>>> this correctly.
> >> > >>>>>>>>>
> >> > >>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote:
> >> > >>>>>>>>>> Okay, on the IRQ page in the manual, it has two sections:
> >> > >>>>>>>>>>
> >> > >>>>>>>>>> 1. "Standard interrupt assignments", which list IRQ
numbers
> >and
> >> > >>>>>>>>>> their
> >> > >>>>>>>>>> "standard function". (This section does list 7 "IRQs are
> >> usually
> >> > >>>>>>>> available
> >> > >>>>>>>>>> for PCI devices")
> >> > >>>>>>>>>>
> >> > >>>>>>>>>> 2. "IRQ" assignments for this motherboard", which graphs
> >> various
> >> > >>>>>>>>>> PCI
> >> > >>>>>>>> slots
> >> > >>>>>>>>>> or USB controllers as "nil", "shared", or "used" against
> >> letters
> >> > >>>>>>>>>> of the
> >> > >>>>>>>>>> alphabet.
> >> > >>>>>>>>>>
> >> > >>>>>>>>>> I don't know how to use these two sets of data to resolve
> my
> >> > >>>>>>>>>> problem.
> >> > >>>>>>>> They
> >> > >>>>>>>>>> seem incompatible. I feel ignernt.
> >> > >>>>>>>>>>
> >> > >>>>>>>>>>
> >> > >>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in message
> >> > >>>>>>>>>> news:450a0f48@linux...
> >> > >>>>>>>>>>> Hmmm.....well .......letsee.........ASUS boards normally
> >will
> >> > >>>>>>>>>>> have the
> >> > >>>>>>>>> AGP
> >> > >>>>>>>>>>> sharing an IRQ with two PCI slots, basically making these
> >> > >>>>>>>>>>> worthless for
> >> > >>>>>>>>>>> anything else.
> >> > >>>>>>>>>>> How many PCI slots does your mobo have?
> >> > >>>>>>>>>>> If it's a 5 slot board and it's similar to an AMD board,
> >> chances
> >> > >>>>>>>>>>> are
> >> > >>>>>>>> that
> >> > >>>>>>>>>>> PCI slots 1 and 5 are shared with the AGP and the
firewire
> >> port
> >> > >>>>>>>>>>> (thus
> >> > >>>>>>>>>> making
> >> > >>>>>>>>>>> FW audio interfaces iffy also if using the onboard FW)
> >> > >>>>>>>>>>>
> >> > >>>>>>>>>>> PCI slot 2 may share with your LAN controller
> >> > >>>>>>>>>>> PCI #3 may share with onboard RAID and SATA controller
> >> > >>>>>>>>>>> PCI 4 may not share with anything.
> >> > >>>>>>>>>>>
> >> > >>>>>>>>>>> This is the way the ASUS A8V mobo is configured but it's
> for
> >> AMD
> >> > >>>>>>>>>>> CPU's.
> >> > >>>>>>>>>>>
> >> > >>>>>>>>>>> Do you have the manual? All of this is listed in chapter
> 2
> >> under
> >> > >>>>>>>>>>> the
> >> > >>>>>>>>>> heading
> >> > >>>>>>>>>>> Interrupt Assignments. It should be noted for Intel
mobo's
> >as
> >> > >>>>>>>>>>> well.
> >> > >>>>>>>>>>>
> >> > >>>>>>>>>>>
> >> > >>>>>>>>>>>
> >> > >>>>>>>>>>> If it's 6, try putting the EDS card in PCI 2, 3, 4 or 5
> >> > >>>>>>>>>>> If it's 5, try PCI slot 1,
> >> > >>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in
message
> >> > >>>>>>>>>>> news:4509fd03@linux...
> >> > >>>>>>>>>>>> It's an Asus P5P800 SE board with a Pentium 4 HT chip.
> >> > >>>>>>>>>>>>
> >> > >>>>>>>>>>>>
> >> > >>>>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in
message
> >> > >>>>>>>>>>>> news:4509f8fc@linux...
> >> > >>>>>>>>>>>>> What kind of mobo are you using Jimmy?
> >> > >>>>>>>>>>>>>
> >> > >>>>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in
message
> >> > >>>>>>>>>>>>> news:4509eda3@linux...
> >> > >>>>>>>>>>>>>> I couldn't find any place where it indicated which IRQ
> >the
> >> > >>>>>>>>>>>>>> AGP was
> >> > >>>>>>>>>>>>> assigned.
> >> > >>>>>>>>>>>>>> The IRQ page had all IRQs assigned to "PCI", and
beneath
> >> that
> >> > >>>>>>>>>>>>>> all
> >> > >>>>>>>>> the
> >> > >>>>>>>>>>> PCI
> >> > >>>>>>>>>>>>>> slots all assigned to "AUTO". On another page the
serial
> >> port
> >> > >>>>>>>>>>>>>> was
> >> > >>>>>>>>>>>>>> assigned
> >> > >>>>>>>>>>>>>> to IRQ 4, and the parallel port was assigned to IRQ 7.
> So
> >I
> >> > >>>>>>>> assigned
> >> > >>>>>>>>>>> the
> >> > >>>>>>>>>>>>> PCI
> >> > >>>>>>>>>>>>>> slots to other numbers.
> >> > >>>>>>>>>>>>>>
> >> > >>>>>>>>>>>>>> Am I on the wrong track here?
> >> > >>>>>>>>>>>>>>
> >> > >>>>>>>>>>>>>>
> >> > >>>>>>>>>>>>>> "DJ" <animix_spam-this-ahole_@animas.net> wrote in
> >message
> >> > >>>>>>>>>>>>>> news:4509da19@linux...
> >> > >>>>>>>>>>>>>>> Repeat after me:
> >> > >>>>>>>>>>>>>>>
> >> > >>>>>>>>>>>>>>> IRQ!! IRQ!! IRQ!!
> >> > >>>>>>>>>>>>>>>
> >> > >>>>>>>>>>>>>>> This sounds exactly like the EDS card is sharing and
> >> > >>>>>>>>>>>>>>> interrupt
> >> > >>>>>>>>> with
> >> > >>>>>>>>>>> the
> >> > >>>>>>>>>>>>>>> AGP
> >> > >>>>>>>>>>>>>>> slot.
> >> > >>>>>>>>>>>>>>>
> >> > >>>>>>>>>>>>>>>
> >> > >>>>>>>>>>>>>>> "Uptown Jimmy" <johnson314@bellsouth.net> wrote in
> >message
> >> > >>>>>>>>>>>>>>> news:45098f86$1@linux...
> >> > >>>>>>>>>>>>>>>> Hi-ho.
> >> > >>>>>>>>>>>>>>>>
> >> > >>>>>>>>>>>>>>>> I am still having trouble with my Paris rig. In an
> >effort
> >> > >>>>>>>>>>>>>>>> to
> >> > >>>>>>>>>>> simplify
> >> > >>>>>>>>>>>>>>> things,
> >> > >>>>>>>>>>>>>>>> I only have one card installed, with an MEC
attached,
> >> > >>>>>>>>>>>>>>>> internal
> >> > >>>>>>>>>>>>> clocking.
> >> > >>>>>>>>>>>>>>>> Basically, my problems are down to two:
> >> > >>>>>>>>>>>>>>>>
> >> > >>>>>>>>>>>>>>>> 1.The "now-line" freezes, or more actually begins
> >> > >>>>>>>>>>>>>>>> stuttering in
> >> > >>>>>>>>>>>>> extremely
> >> > >>>>>>>>>>>>>>>> slow-motion, almost glacial. I can still change
> >windows,
> >> > >>>>>>>>>>>>>>>> and I
> >> > >>>>>>>>> am
> >> > >>>>>>>>>>> able
> >> > >>>>>>>>>>>>> to
> >> > >>>>>>>>>>>>>>>> save and close, then re-open Paris with success.
> >> > >>>>>>>>>>>>>>>>
> >> > >>>>>>>>>>>>>>>> 2.On starting Paris, I get an error message: "I/O
> >modules
> >> > >>>>>>>>>>>>>>>> used
> >> > >>>>>>>>> in
> >> > >>>>>>>>>>> this
> >> > >>>>>>>>>>>>>>> patch
> >> > >>>>>>>>>>>>>>>> setting not avaiable in this configuration of Paris.
> >> > >>>>>>>>>>>>>>>> Resulting
> >> > >>>>>>>>>> audio
> >> > >>>>>>>>>>>>> may
> >> > >>>>>>>>>>>>>>>> be different than when saved." This will pop up 2 or
> 4
> >> > >>>>>>>>>>>>>>>> times,
> >> > >>>>>>>>> and
> >> > >>>>>>>>>>> then
> >> > >>>>>>>>>>>>>>> when
> >> > >>>>>>>>>>>>>>>> I push "play" no audio is heard. Then I close,
reopen,
> >> and
> >> > >>>>>>>>>>>>>>>> then
> >> > >>>>>>>>>>> things
> >> > >>>>>>>>>>>>>>> work
> >> > >>>>>>>>>>>>>>>> for a while.
> >> > >>>>>>>>>>>>>>>>
> >> > >>>>>>>>>>>>>>>> I have made some tweaks to the configuration with
some
> >> > >>>>>>>>>>>>>>>> success.
> >> > >>>>>>>>>> The
> >> > >>>>>>>>>>>>>>>> errors
> >> > >>>>>>>>>>>>>>>> are happening less and less, but they still pop up.
> >> > >>>>>>>>>>>>>>>>
> >> > >>>>>>>>>>>>>>>> Anybody?
> >> > >>>>>>>>>>>>>>>> Jimmy
> >> > >>>>>>>>>>>>>>>
> >> > >>>>>>>>>>>>>>
> >> > >>>>>>>>>>>>>
> >> > >>>>>>>>>>>>
> >> > >>>>>>>>>>>
> >> > >>>>>>>>>>
> >> > >>>>>>>>
> >> > >>>>>>
> >> > >>>>>
> >> > >>>>>
> >> > >>>>
> >> > >>>>
> >> > >>>
> >> > >>>
> >> > >>
> >> > >>
> >> > >
> >> > >
> >> >
> >> >
> >>
> >>
> >
> >
>
|
|
|
|
Goto Forum:
Current Time: Wed Nov 13 19:28:39 PST 2024
Total time taken to generate the page: 0.04531 seconds
|
The PARIS Forums
Search
Help
Members
Register
Login
Home
