Greetings from Ireland! Can some kind, knowledgeable folks assist me with the following openSUSE 11.4 Resource Conflict problem?
I have been using Linux successfully for over five years and presently have openSUSE 11.4 Celadon and KDE 4.6.0, only, running on a Siemens “Esprimo” P5616 desktop PC with nForce4 AMD Athlon 64 x2 4600+ dual-core 2.4GHz CPU, 2GB RAM, nVidia GeForce 7300LE 256MB TrueMemory with 2D driver (nv) and 3D driver (swrast 7.10.2, but *without *3D acceleration), SATA HDD SATA-2 250GB 7.2k, nVidia MCP51 Ethernet Controller, USB 2.0, kernel 2.6.37.6-0.20 x86_64. BIOS release version: 6.00 R1.14.2461.B1.
Recently, I switched on my all-Linux desktop PC, only to discover that, due to boot failure, I was LOCKED OUT of my computer. Here is the exact sequence of events: Usual Phoenix AMD64 opening screen with briefest message “Preparing to boot” **>>> ** Beep-beep audio signal accompanying Phoenix System Console with grey progress bar at only circa 85% and showing Warning Error as per full text in paragraph below >>> F1 key pressed by myself in vain hope problem might go away! >>> Black screen with white text, top left: “GRUB loading Stage 2” >>> Familiar green Start-up Options screen with upper Desktop option counting down normally **>>> ** Black screen indefinitely, so end of sequence. Pressing Stop button on PC fails to switch off the computer; so no choice but to unplug the power cable.
Here, as indicated above, is the full text of what appears in the Phoenix System Console:-
TCG is enabled.
2047M System RAM Passed.
1024 KB L2 Cache.
System BIOS shadowed.
Video BIOS shadowed.
Fixed Disk 0: WDC WDC2500JS-55NCB1
ATAPI CD-ROM: HL-DT-STDVD-RAM GSA-H30N
Mouse initialised.
Event Log messages, enter Setup to view.
**
WARNING** ERROR
Resource Conflict – PCI in slot 02, Bus:04, Device:07, Function:00.
Press <F1> to resume. System message - <F2> Setup.
— (End of Phoenix System Console text) —
Folks, if you require any pertinent System Message details from the Phoenix Setup Utility, I shall be happy to provide same upon request.
Lastly, in case you’re wondering, I am using the special live DVD (Balsam extensions) to enable me access the Internet and to compose this posting. But, of course, as consequence of the aforementioned boot-up problem, I am unable open ANY of my existing files or emails. The hard disk appears to be OK, though.
Any solutions, anyone? Any help offered will be very, very much appreciated.
On Fri, 14 Sep 2012 00:26:01 +0000, MagnifiKat wrote:
> Any solutions, anyone? Any help offered will be very, very much
> appreciated.
The error message you’re seeing is a hardware issue - have you changed
any hardware in the system recently?
You might try going into the setup and see if it gives you any additional
information about the resource conflict and/or options to resolve it. PCI
cards are generally configured through a BIOS setting (when they need to
be, which is rare).
This could also be indicative of a more severe hardware issue - the
indication doesn’t say anything about a parity error, but if there
weren’t any hardware changes recently, it’s possible that you’re seeing a
bus parity error that’s causing the system to try to assign a resource
(memory range, IRQ, or I/O port typically) to two devices.
From your liveCD, you could try going to a terminal prompt and type:
lspci -v
Include the output in code tags (see the advanced editor, # button).
That might help someone identify which hardware device is causing an
issue.
If this was me I would consider it time to do the following, with the unit turned off and unplugged from power and all devices :
Do a complete dust clean out of this PC using some kind of compressed air like duster spray using a couple of cans, do this perhaps outside in good light, and including the cleaning of all heat sinks and fans.
I would remove and reinstall all adapter cards, plugs and memory, one device or plug at a time in a well lite area paying attention to exactly where each device resides and connects. Take before pictures if you need to.
Consider it time to replace your CMOS battery. I would remove it, check its number and find a replacement. Removing it will clear your CMOS and allow it to rethink the conflict.
Put everything back together, power it up and run CMOS setup to clear the error that you will get. Consider it may be time to upgrade to openSUSE 12.2 and create a boot disk in advance if you can.
5 Once powered up, leave the side panel off so you can make sure that all cooling fans still work. Check the CPU, power supply and any case fans you might have. Replace any that do not work, make noise or run slowly.
Once complete, come back and tell us of your success.
And please use the default font (size) like we all do. There is not need to play around with those. You will irritate some people which will then skip your post.
Beeps are an error from the system (at a point where the system may not even have a screen to say something). The meaning of the different short/long/number of beeps should be in the systems manual.
Hi, Jim! Thank you for your most kind and helpful response.
The error message you’re seeing is a hardware issue - have you changed
any hardware in the system recently?
No, the hardware has not been changed at all in the 5-plus years since I purchased my desktop PC. So I concur that this is very likely a hardware issue.
You might try going into the setup and see if it gives you any additional
information about the resource conflict and/or options to resolve it.
I had checked already into the Phoenix Setup Utility, but had found neither additional info nor options to resolve this resource conflict.
… it’s possible that you’re seeing a
bus parity error that’s causing the system to try to assign a resource
(memory range, IRQ, or I/O port typically) to two devices.
From your liveCD, you could try going to a terminal prompt and type:
lspci -v
Include the output in code tags (see the advanced editor, # button).
That might help someone identify which hardware device is causing an
issue.
As suggested by your good self, I attach hereto the full command-line output requested.
linux@linux:~> su
linux:/home/linux # lspci -v
00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
Subsystem: Fujitsu Technology Solutions Device 10c5
Flags: bus master, 66MHz, fast devsel, latency 0
Capabilities: [44] HyperTransport: Slave or Primary Interface
Capabilities: [e0] HyperTransport: MSI Mapping Enable+ Fixed-
00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2)
Subsystem: Fujitsu Technology Solutions Device 10c5
Flags: 66MHz, fast devsel
00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2)
Subsystem: Fujitsu Technology Solutions Device 10c5
Flags: 66MHz, fast devsel
00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2)
Subsystem: Fujitsu Technology Solutions Device 10c5
Flags: 66MHz, fast devsel
00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2)
Subsystem: Fujitsu Technology Solutions Device 10c5
Flags: bus master, 66MHz, fast devsel, latency 0
00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
Subsystem: Fujitsu Technology Solutions Device 10c5
Flags: bus master, 66MHz, fast devsel, latency 0
Capabilities: [44] #00 [00fe]
Capabilities: [fc] #00 [0000]
00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2)
Subsystem: Fujitsu Technology Solutions Device 10c5
Flags: 66MHz, fast devsel
00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2)
Subsystem: Fujitsu Technology Solutions Device 10c5
Flags: 66MHz, fast devsel
00:02.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Capabilities: [40] Subsystem: nVidia Corporation Device 0000
Capabilities: [48] Power Management version 2
Capabilities: [50] MSI: Enable- Count=1/2 Maskable- 64bit+
Capabilities: [60] HyperTransport: MSI Mapping Enable- Fixed-
Capabilities: [80] Express Root Port (Slot+), MSI 00
Capabilities: [100] Virtual Channel
00:03.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
Capabilities: [40] Subsystem: nVidia Corporation Device 0000
Capabilities: [48] Power Management version 2
Capabilities: [50] MSI: Enable- Count=1/2 Maskable- 64bit+
Capabilities: [60] HyperTransport: MSI Mapping Enable- Fixed-
Capabilities: [80] Express Root Port (Slot+), MSI 00
Capabilities: [100] Virtual Channel
00:04.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
Memory behind bridge: f0000000-f1ffffff
Prefetchable memory behind bridge: 00000000e0000000-00000000efffffff
Capabilities: [40] Subsystem: nVidia Corporation Device 0000
Capabilities: [48] Power Management version 2
Capabilities: [50] MSI: Enable- Count=1/2 Maskable- 64bit+
Capabilities: [60] HyperTransport: MSI Mapping Enable- Fixed-
Capabilities: [80] Express Root Port (Slot+), MSI 00
Capabilities: [100] Virtual Channel
00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2)
Subsystem: Fujitsu Technology Solutions Device 10c6
Flags: bus master, 66MHz, fast devsel, latency 0
Capabilities: [44] HyperTransport: Slave or Primary Interface
Capabilities: [e0] HyperTransport: MSI Mapping Enable+ Fixed-
00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a3)
Subsystem: Fujitsu Technology Solutions Device 10c6
Flags: bus master, 66MHz, fast devsel, latency 0
I/O ports at 8800 [size=128]
00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a3)
Subsystem: Fujitsu Technology Solutions Device 10c6
Flags: 66MHz, fast devsel, IRQ 10
I/O ports at 88c0 [size=64]
I/O ports at 8880 [size=64]
Capabilities: [44] Power Management version 2
Kernel driver in use: nForce2_smbus
00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3) (prog-if 10 [OHCI])
Subsystem: Fujitsu Technology Solutions Device 10c6
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 20
Memory at f2304000 (32-bit, non-prefetchable) [size=4]
Capabilities: [44] Power Management version 2
Kernel driver in use: ohci_hcd
00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3) (prog-if 20 [EHCI])
Subsystem: Fujitsu Technology Solutions Device 10c6
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 21
Memory at f2308000 (32-bit, non-prefetchable) [size=256]
Capabilities: [44] Debug port: BAR=1 offset=0098
Capabilities: [80] Power Management version 2
Kernel driver in use: ehci_hcd
00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev f1) (prog-if 8a [Master SecP PriP])
Subsystem: Fujitsu Technology Solutions Device 10c6
Flags: bus master, 66MHz, fast devsel, latency 0
[virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8]
[virtual] Memory at 000003f0 (type 3, non-prefetchable) [size=1]
[virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8]
[virtual] Memory at 00000370 (type 3, non-prefetchable) [size=1]
I/O ports at 8c00 [size=16]
Capabilities: [44] Power Management version 2
Kernel driver in use: pata_amd
00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev f1) (prog-if 85 [Master SecO PriO])
Subsystem: Fujitsu Technology Solutions Device 10c6
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 23
I/O ports at 8c40 [size=8]
I/O ports at 8c34 [size=4]
I/O ports at 8c38 [size=8]
I/O ports at 8c30 [size=4]
I/O ports at 8c10 [size=16]
Memory at f2305000 (32-bit, non-prefetchable) [size=4]
Capabilities: [44] Power Management version 2
Capabilities: [b0] MSI: Enable- Count=1/4 Maskable- 64bit+
Capabilities: [cc] HyperTransport: MSI Mapping Enable- Fixed+
Kernel driver in use: sata_nv
00:0f.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev f1) (prog-if 85 [Master SecO PriO])
Subsystem: Fujitsu Technology Solutions Device 10c6
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 22
I/O ports at 8c58 [size=8]
I/O ports at 8c4c [size=4]
I/O ports at 8c50 [size=8]
I/O ports at 8c48 [size=4]
I/O ports at 8c20 [size=16]
Memory at f2306000 (32-bit, non-prefetchable) [size=4]
Capabilities: [44] Power Management version 2
Capabilities: [b0] MSI: Enable- Count=1/4 Maskable- 64bit+
Capabilities: [cc] HyperTransport: MSI Mapping Enable- Fixed+
Kernel driver in use: sata_nv
00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2) (prog-if 01 [Subtractive decode])
Flags: bus master, 66MHz, fast devsel, latency 0
Bus: primary=00, secondary=04, subordinate=04, sec-latency=64
I/O behind bridge: 00002000-00002fff
Memory behind bridge: f2000000-f20fffff
Capabilities: [b8] Subsystem: nVidia Corporation Device cb84
Capabilities: [8c] HyperTransport: MSI Mapping Enable- Fixed-
00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2)
Subsystem: Fujitsu Technology Solutions Device 10c3
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 17
Memory at f2300000 (32-bit, non-prefetchable) [size=16]
Capabilities: [44] Power Management version 2
Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
Capabilities: [6c] HyperTransport: MSI Mapping Enable- Fixed+
Kernel driver in use: HDA Intel
00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3)
Subsystem: Fujitsu Technology Solutions Device 10c6
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 18
Memory at f2307000 (32-bit, non-prefetchable) [size=4]
I/O ports at 8c60 [size=8]
Capabilities: [44] Power Management version 2
Kernel driver in use: forcedeth
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
Flags: fast devsel
Capabilities: [80] HyperTransport: Host or Secondary Interface
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
Flags: fast devsel
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
Flags: fast devsel
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
Flags: fast devsel
Capabilities: [f0] Secure device <?>
Kernel driver in use: k8temp
03:00.0 VGA compatible controller: nVidia Corporation G72 [GeForce 7300 LE] (rev a1) (prog-if 00 [VGA controller])
Subsystem: LeadTek Research Inc. Device 5efb
Flags: bus master, fast devsel, latency 0, IRQ 19
Memory at f1000000 (32-bit, non-prefetchable) [size=16]
Memory at e0000000 (64-bit, prefetchable) [size=256]
Memory at f0000000 (64-bit, non-prefetchable) [size=16]
Expansion ROM at <unassigned> [disabled]
Capabilities: [60] Power Management version 2
Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [78] Express Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [128] Power Budgeting <?>
Kernel driver in use: nouveau
04:07.0 Communication controller: Conexant Systems, Inc. HSF 56k Data/Fax Modem
Subsystem: Conexant Systems, Inc. Device 2000
Flags: bus master, fast Back2Back, medium devsel, latency 64, IRQ 10
Memory at f2000000 (32-bit, non-prefetchable) [disabled] [size=64]
I/O ports at 2000 [disabled] [size=8]
Capabilities: [40] Power Management version 2
linux:/home/linux #
i thought my old AMD64 with a Phoenix just said: beep (once)
When firstly I read your query, I thought just maybe I had made a mistake in my posting regarding the Beep-beep audio signal accompanying the Phoenix System Console. But, no, I have checked and double-checked, and it is definitely a Beep-beep – just like the friendly toot-toot of a car horn!
On 09/16/2012 05:46 PM, MagnifiKat wrote:
> it isdefinitely a Beep-beep
if it has not been beep-beep for all those five plus years you have had
that machine then we can be pretty sure you have a hardware problem…
and if so, i’d think you should be able to ‘decode’ what the two beeps
of your Power On Self Test (POST) means…and, thereby have a clue of
which way to proceed…
Hi, Marian! Many thanks for your two September 14 responses. Beeps info appreciated very much.
And please use the default font (size) like we all do. There is not need to play around with those. You will irritate some people which will then skip your post.
Oops! Sorry! … but it was my very first Forum posting, and it takes awhile for new users to familiarise themselves with your website. Thank you for your guidance regarding openSUSE’s preferred typographical “house style”. However, to prevent needless future user confusion, suggest probably better font and size options be omitted altogether from the website, so that there be no user choice but to use the default setting! Thanks again.
Don’t take it too serious. But I guess you looked around here a little bit before your first post. Just to get an idea if asking here would be usefull. And then you would have seen that playing with font sizes, etc. is only done very rare if at all. The forums sofftware is a market product (VBulletin) and as far as the defaults here are set as … the defaults, they suffice. No extra work needed. Most important thing for new posters are the CODE tags and you use them allready to advantage.
My idea is that you allready feel at bit at home here and that is as it should be. Welcome!
Hi James! MagnifiKat here from Ireland. Thank you for your kind response. I really appreciate your most helpful input!
Do a complete dust clean out of this PC using some kind of compressed air like duster spray …
Consider it time to replace your CMOS battery. … Removing it will clear your CMOS and allow it to rethink the conflict.
… Consider it may be time to upgrade to openSUSE 12.2 …
… Check the CPU, power supply and any case fans …
Once complete, come back and tell us of your success.
Opinion seems to be that this resource conflict is most likely a hardware issue, but I have yet to learn from Forum members just which specific item of hardware will need replacing. Accordingly, perhaps you will be so kind as to peruse the lspci -v command-line output requested by your Administrator, Jim Henderson (hendersj), as per message #7 on this my MagnifiKat page, and to advise me soonest of requisite action(s) to resolve this puzzling conflict. Also: Please link or copy the selfsame command-line output to other members of the Forum team who, you believe, may have particular expertise in such resource conflicts.
Once I have been so notified, by your good self and/or others, I shall BOTH upgrade the hardware AND follow your excellent advice as above. Then, and only then, will I consider upgrading our software to openSUSE 12.2. Many thanks, James!
So I guess my next question to you is did you take any of my advise and clean your computer or do any of my suggested steps? Next, did you try the lspc command as requsted? I did not see an output of this command from your system. Here is the actual command you would execute unless you are root or become root, you must include the folder path with the command and so open up a terminal session and run the following terminal command:
/sbin/lspci -v
I would post the output of this command (doing a copy from terminal and a paste into a message here) in a forum message, using the advanced message editor and placing the result within a code # field, like the command I posted above looks. I can say that having a hardware conflict when no hardware has changed can indicate a possible hardware failure, but we are not going to be able to diagnose your problem without more than we know and it could just be dirt or dust on poor connection problem in your PC that the cleaning I suggest or the replacement of your CMOS battery might fix. And of course, hardware of all sorts works great until the day, of its own selection, it decides to fail without regard to anything you have done or not done to your PC.
On 09/20/2012 12:06 AM, MagnifiKat wrote:
> Opinion seems to be that thisresource conflict is most likely a
> hardware issue, -but I have yet to learn from Forum members just which
> specific item of hardware will need replacing.
imo, you need to decide if it always went ‘beep-beep’ or if it used to
go ‘beep’…
if it is giving you a new Power On Self Test (POST) audio code then
you need to find the correct page on the net with the actual version of
your BIOS codes given…
i gave you an example page but i didn’t see a way to decode beep-beep…
in my opinion: if the BIOS is trying to tell you something then you need
to listen. dust or no dust, bad hardware, new hardware, old hardware,
etc etc etc…
because an abnormal POST code is signaling VERY foundationally basic
input-output problems [BIOS = Basic Input/Output System] which must be
dealt with (maybe with a new battery as suggested)…
Yes, James, thank you very much! I did in fact reply to your good self last evening (Wed-19-Sep-2012), as per message #12 on this my MagnifiKat page, but it appears you had not then had opportunity to view it. See copy below:-
Hi James! MagnifiKat here from Ireland. Thank you for your kind response. I really appreciate your most helpful input!
[QUOTE]1. Do a complete dust clean out of this PC using some kind of compressed air like duster spray …
3. Consider it time to replace your CMOS battery. … Removing it will clear your CMOS and allow it to rethink the conflict.
4. … Consider it may be time to upgrade to openSUSE 12.2 …
5. … Check the CPU, power supply and any case fans …
Once complete, come back and tell us of your success.
Opinion seems to be that this resource conflict is most likely a hardware issue, but I have yet to learn from Forum members just which specific item of hardware will need replacing. Accordingly, perhaps you will be so kind as to peruse the lspci -v command-line output requested by your Administrator, Jim Henderson (hendersj), as per message #7 on this my MagnifiKat page, and to advise me soonest of requisite action(s) to resolve this puzzling conflict. Also: Please link or copy the selfsame command-line output to other members of the Forum team who, you believe, may have particular expertise in such resource conflicts.
Once I have been so notified, by your good self and/or others, I shall BOTH upgrade the hardware AND follow your excellent advice as above. Then, and only then, will I consider upgrading our software to openSUSE 12.2. Many thanks, James![/QUOTE]
And, yes, as you will note, September 16, indeed I did post, as super user, full lspci -v command-line output to your Administrator, Jim Henderson (hendersj), as he had requested me. However, today I decided IN ADDITION to run the alternative command line /sbin/lspci -v as you have suggested; and from which you will note there are 19 discrepancies from the super user output which I posted earlier. These I have **highlighted in red. **Please see below:-
linux@linux:~> **/sbin/lspci -v**
00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
Subsystem: Fujitsu Technology Solutions Device 10c5
Flags: bus master, 66MHz, fast devsel, latency 0
Capabilities: **<access denied>**
00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2)
Subsystem: Fujitsu Technology Solutions Device 10c5
Flags: 66MHz, fast devsel
00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2)
Subsystem: Fujitsu Technology Solutions Device 10c5
Flags: 66MHz, fast devsel
00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2)
Subsystem: Fujitsu Technology Solutions Device 10c5
Flags: 66MHz, fast devsel
00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2)
Subsystem: Fujitsu Technology Solutions Device 10c5
Flags: bus master, 66MHz, fast devsel, latency 0
00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
Subsystem: Fujitsu Technology Solutions Device 10c5
Flags: bus master, 66MHz, fast devsel, latency 0
Capabilities: **<access denied>**
00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2)
Subsystem: Fujitsu Technology Solutions Device 10c5
Flags: 66MHz, fast devsel
00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2)
Subsystem: Fujitsu Technology Solutions Device 10c5
Flags: 66MHz, fast devsel
00:02.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Capabilities: **<access denied>**
00:03.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
Capabilities: **<access denied>**
00:04.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
Memory behind bridge: f0000000-f1ffffff
Prefetchable memory behind bridge: 00000000e0000000-00000000efffffff
Capabilities: **<access denied>**
00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2)
Subsystem: Fujitsu Technology Solutions Device 10c6
Flags: bus master, 66MHz, fast devsel, latency 0
Capabilities: **<access denied>**
00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a3)
Subsystem: Fujitsu Technology Solutions Device 10c6
Flags: bus master, 66MHz, fast devsel, latency 0
I/O ports at 8800 [size=128]
00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a3)
Subsystem: Fujitsu Technology Solutions Device 10c6
Flags: 66MHz, fast devsel, IRQ 10
I/O ports at 88c0 [size=64]
I/O ports at 8880 [size=64]
Capabilities: **<access denied>**[/size][/size]
Kernel driver in use: nForce2_smbus
00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3) (prog-if 10 [OHCI])
Subsystem: Fujitsu Technology Solutions Device 10c6
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 20
Memory at f2304000 (32-bit, non-prefetchable) [size=4]
Capabilities: **<access denied>**[/size]
Kernel driver in use: ohci_hcd
00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3) (prog-if 20 [EHCI])
Subsystem: Fujitsu Technology Solutions Device 10c6
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 21
Memory at f2308000 (32-bit, non-prefetchable) [size=256]
Capabilities: **<access denied>**[/size]
Kernel driver in use: ehci_hcd
00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev f1) (prog-if 8a [Master SecP PriP])
Subsystem: Fujitsu Technology Solutions Device 10c6
Flags: bus master, 66MHz, fast devsel, latency 0
[virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8]
[virtual] Memory at 000003f0 (type 3, non-prefetchable) [size=1]
[virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8]
[virtual] Memory at 00000370 (type 3, non-prefetchable) [size=1]
I/O ports at 8c00 [size=16]
Capabilities: **<access denied>**[/size][/size][/size][/size][/size]
Kernel driver in use: pata_amd
00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev f1) (prog-if 85 [Master SecO PriO])
Subsystem: Fujitsu Technology Solutions Device 10c6
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 23
I/O ports at 8c40 [size=8]
I/O ports at 8c34 [size=4]
I/O ports at 8c38 [size=8]
I/O ports at 8c30 [size=4]
I/O ports at 8c10 [size=16]
Memory at f2305000 (32-bit, non-prefetchable) [size=4]
Capabilities: **<access denied>**[/size][/size][/size][/size][/size][/size]
Kernel driver in use: sata_nv
00:0f.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev f1) (prog-if 85 [Master SecO PriO])
Subsystem: Fujitsu Technology Solutions Device 10c6
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 22
I/O ports at 8c58 [size=8]
I/O ports at 8c4c [size=4]
I/O ports at 8c50 [size=8]
I/O ports at 8c48 [size=4]
I/O ports at 8c20 [size=16]
Memory at f2306000 (32-bit, non-prefetchable) [size=4]
Capabilities: **<access denied>**[/size][/size][/size][/size][/size][/size]
Kernel driver in use: sata_nv
00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2) (prog-if 01 [Subtractive decode])
Flags: bus master, 66MHz, fast devsel, latency 0
Bus: primary=00, secondary=04, subordinate=04, sec-latency=64
I/O behind bridge: 00002000-00002fff
Memory behind bridge: f2000000-f20fffff
Capabilities: **<access denied>**
00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2)
Subsystem: Fujitsu Technology Solutions Device 10c3
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 17
Memory at f2300000 (32-bit, non-prefetchable) [size=16]
Capabilities: **<access denied>**[/size]
Kernel driver in use: HDA Intel
00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3)
Subsystem: Fujitsu Technology Solutions Device 10c6
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 18
Memory at f2307000 (32-bit, non-prefetchable) [size=4]
I/O ports at 8c60 [size=8]
Capabilities: **<access denied>**[/size][/size]
Kernel driver in use: forcedeth
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
Flags: fast devsel
Capabilities: **<access denied>**
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
Flags: fast devsel
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
Flags: fast devsel
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
Flags: fast devsel
Capabilities: **<access denied>**
Kernel driver in use: k8temp
03:00.0 VGA compatible controller: nVidia Corporation G72 [GeForce 7300 LE] (rev a1) (prog-if 00 [VGA controller])
Subsystem: LeadTek Research Inc. Device 5efb
Flags: bus master, fast devsel, latency 0, IRQ 19
Memory at f1000000 (32-bit, non-prefetchable) [size=16]
Memory at e0000000 (64-bit, prefetchable) [size=256]
Memory at f0000000 (64-bit, non-prefetchable) [size=16]
Expansion ROM at <unassigned> [disabled]
Capabilities: **<access denied>**[/size][/size][/size]
Kernel driver in use: nouveau
04:07.0 Communication controller: Conexant Systems, Inc. HSF 56k Data/Fax Modem
Subsystem: Conexant Systems, Inc. Device 2000
Flags: bus master, fast Back2Back, medium devsel, latency 64, IRQ 10
Memory at f2000000 (32-bit, non-prefetchable) [disabled] [size=64]
I/O ports at 2000 [disabled] [size=8]
Capabilities: **<access denied>**[/size][/size]
linux@linux:~>
Many thanks, James. You guys are really helpful and I appreciate so very much your collective efforts to assist all those of us who lack your special expertise in under-the-bonnet Linux forensics! I look forward to the favour of your early kind reply.
OP has simply done as suggested by jdmcdanial3 - “open up a terminal session and run the following terminal command … /sbin/lspci -v”. In fact OP had already (see post #7 at 14.18) run lspci -v as root, and had posted results. Perhaps horror at non-standard font sizes obscured this?
Have you considered doing a CMOS reset on this PC? On some systems there is a jumper that can be moved to disconnect the CMOS battery and in addition, the actual battery can just be momentarily removed. On a few PC’s, the BIOS contains a reset function, but however done, I feel the BIOS must be forced to rethink the internal configuration and a BIOS reset should do that. If that does not help it could be a bad adapter card and normally, I remove any add in cards, when a desktop is being used, one at a time, to determine if one of those is bad. When removing a CMOS battery, you would want to take it somewhere to be tested, to make sure it does not need to be replaced as well. If you have a small volt meter, you can do this yourself. I have had to replace batteries as young as two years old and so anything older might need to be replaced. The normal CMOS battery life is more like five years on average.
Thank you for your most helpful response. I regret I remain locked out of my Siemens desktop PC, despite my having replaced the CMOS 3-volt lithium battery, and with the PC nice and clean inside. Also: I am still getting the Phoenix beep-beep code, which, from my Internet research, is unusual, non-standard and thus as yet unexplained.
Using the live DVD, I ran each of your suggested commands, apic=debug and noapic, but received a “command not found” message in both cases.
I have checked the Memory settings in the BIOS; and yes indeed, as a precautionary measure, wrote down the entire contents of the BIOS. As noted in my initial posting (#1), the following System Console message may or may not be significant: 2047M System RAM Passed, whereas in the Phoenix Set-up Utility the Extended Memory is shown as 2046M.
But how, I wonder, do I check the “interrupts” in the BIOS? And, if the Interrupt Controller is banjaxed, on which board is it located and how, without any test measuring equipment, do I determine whether or not it has failed? I continue also receive a Phoenix WARNING ERROR as follows: Resource Conflict - PCI in slot 02, Bus:04, Device:07, Function:00.
Your further most kind guidance will be very, very much appreciated.