Re: ASUS K8N-DL Beta BIOS

Re: ASUS K8N-DL Beta BIOS

[Robert Hancock]

Sean Bruno wrote:
> Also, the ACPI PCI Interrupt Routing Table (PRT) contains references to
> entries that don't exist elsewhere in the ACPI tables:
> 
> ACPI: Subsystem revision 20050309
>     ACPI-0352: *** Error: Looking up [\_SB_.PCI0.LNK0] in namespace,
> AE_NOT_FOUND
> search_node ffff81013ffca240 start_node ffff81013ffca240 return_node
> 0000000000000000
>     ACPI-0352: *** Error: Looking up [\_SB_.PCI0.APC0] in namespace,
> AE_NOT_FOUND
> search_node ffff81013ffca140 start_node ffff81013ffca140 return_node
> 0000000000000000
> 
> Linux unfortunately appears to give up on parsing the PRT when this
> happens, unlike Windows, which will parse the table despite these
> errors. Without parsing the PRT, Linux cannot know how to route
> interrupts for various PCI devices, which results in the later errors:

Is there a reason Linux couldn't behave similarly to Windows in this 
situation? That might provide some better compatibility with such buggy 
BIOSes..

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/

RE: ASUS K8N-DL Beta BIOS

[Hodle, Brian]

I actually removed the AGP bus completley from the kernel config and
recompiled, this removes the error, and saves you 64mb of ram.

-Brian

-----Original Message-----
From: Sean Bruno [mailto:sean.bruno@dsl-only.net]
Sent: Monday, July 04, 2005 4:39 PM
To: Andi Kleen
Cc: Alexander Nyberg; Alistair John Strachan; Hodle, Brian;
'linux-kernel@vger.kernel.org'; 'ipsoa@posiden.hopto.org'
Subject: Re: ASUS K8N-DL Beta BIOS


On Mon, 2005-07-04 at 23:26 +0200, Andi Kleen wrote:
> > 2.6.13-rc1 has some kind of issue with my board due to it's 6GB of RAM.
> > It stops when it discovers that there is no "IOMMU".  Since I don't see
> > anything obvious in the BIOS to activate, I can't boot 2.6.13 at all.
> 
> Full boot log please?
> 
Well, that might take me a while.  Since the system halts at this point,
I will have to whack together a serial cable to redirect the kernel
post.  

Sean

ASUS K8N-DL Beta BIOS

[Hodle, Brian]

Sean,
   You might get a laugh out of this! It's a reply from ASUS about the
motherboard (this was 2 days b4 they released the 1004.7 BETA BIOS.

Pretty sad when ASUS tells you to "Clear your CMOS". I thought I asked a
pretty straightforward tech question... Makes me wonder if they even read
it, or they had a PERL script do it!

Ps. New BIOS didn't change a thing. The PCI Device names in the ACPI table
are not entered in a fashion that the kernel recognizes. Maybe ASUS decided
to 'optimize' routing by making a more efficient table?' nah..

Cheers,

-Brian

ASUS wrote:

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Dear Sir/Madam,


Thank you for your support for our products!

Please start by clearing the system c-mos memory following the procedure in
your manual. Make sure the power AND the battery on the motherboard is
removed before shorting the CLR RTC solder points or jumper pins. Short the
pins for at least 20-30 seconds.


If this is still not working, you can have your old BIOS chip reprogrammed
or order a new, reprogrammed chip from! us.

********************************** IMPORTANT
************************************************
****************************************************************************
*******************
Please refer to your manual to locate the BIOS chip on your motherboard. If
the chip is removable, it will be fitted into a socket. Please be careful
when removing the chip--do not damage the socket or the chip. Make sure you
remove the chip from the socket, but DO NOT remove the socket from the
motherboard.
****************************************************************************
*******************
****************************************************************************
*******************

Here is the BIOS pricing guide, along with the procedure to obtain a
new/reflashed BIOS chip.

If you are in North America, you can order a NEW BIOS chip online at

http://helpdesk.asus.com/biosorder/store/aci_dynamicIndex.asp.


Prici! ng Guide for Continental United States Orders:


REFLASHED C HIP - Customer mails in their BIOS chip.

Flash sent Fed-Ex Ground (roughly 2-10 days)...$5.00 (this price covers
S&H...the flash is free)

Flash sent Fed-Ex Overnight (next day)...$20.00 (this price covers S&H...the
flash is free)

NEW CHIP

New chip sent Fed-Ex Ground (roughly 2-10 days)...$25.00 (this price covers
the chip and S&H)

New chip sent Fed-Ex Overnight (next day)...$40.00 (this price covers the
chip and S&H)


Pricing Guide for Hawaii and Puerto Rico Orders:


REFLASHED CHIP (Customer's original BIOS chip)

Flash sent Fed-Ex 2nd Day (2 days)...$20.00 (this price covers S&H...the
flash is free)

Flash sent Fed-Ex Overnight (next day)...$30.00 (this price covers S&H...the
flash is free)

NEW CHIP

New chip sent Fed-Ex 2nd Day (2 days)...$35.00 (this price covers the chip
and S&H)

New chip sent Fed-Ex Overnight (next day)...$55.00 (this price covers the
chip and S&H)

We can ! only ship Fed-Ex 2nd Day Air, or Overnight, to Hawaii.


Pricing Guide for Canadian Orders:


FLASHED OR NEW CHIP - Via FEDEX Ground Delivery

$35.00 (USD, standard price for Canada)

We cannot ship Overnight to Canada due to customs.



Sending Bios Chips Through the Mail

Make sure to include the BIOS chip, your name, mailing address, daytime
phone number, motherboard model number, version of the BIOS you would like
flashed and payment to the address below.

***************************IMPORTANT NOTICE*************************

When you send a chip to be flashed, you must put the chip in a hard,
protective container. If not, the chip could possibly arrive damaged.


We DO NOT accept entire motherboards, only BIOS chips. Also, we do not
accept damaged BIOS chips, so please package your BIOS securely (see the
notice above). We can only send BIOS chips within the Continental United
States, Hawaii a! nd Canada.

**************************************************** ****************


Methods of Payment

To place an order over the phone, we accept MasterCard or Visa. If you
choose to send payment through the mail, we accept personal checks (but not
starter checks), company checks, and money orders. WE DO NOT HAVE A BILLING
OPTION. If you wish to purchase a chip through the mail and want to pay with
a credit card:

DO NOT SEND CREDIT CARD INFORMATION THROUGH THE MAIL. Please attach a letter
advising us to contact you for payment information.


Please send BIOS chips to:

ASUS Technology
Attn: BIOS Dept
7100 Intermodal Drive
Suite A
Louisville, KY 40258


Please do not respond to this email. If you need further assistance please
contact our BIOS department at 502-995-0883 x7172.

****************************************************************************
****
Please note that the following boards have BIOS chips that may be
non-removable:

CUSL2-C CUSL2
P4T
P4T-E
P4B
CUR-DLS
CUSI-FX

If the BIOS chip is not in a socket, and is instead soldered directly to the
motherboard, you must contact our RMA department for BIOS repairs. You may
contact them by telephone @ 510-739-3777 option 3, or e-mail them at:

rma@asus.com

Please provide your case number and your motherboard's serial number when
contacting them.



Best Regards,

DIllard
ASUS Technical Support

---------- Original Message ----------
>From : cursedmodem@Hotmail.com
Sent : 6/26/2005 4:48:49 AM
To : "tsd@asus.com.tw"
Subject : <TSD> Motherboard K8N

[CASEID=WTM2005062644099819]

Apply date : 6/26/2005 4:40:09 AM
[Contact Information]
*Name : Brian
Phone Number :
City :
*Country : United States

[Product Information]
*Product Type : Motherboard
*Product Model : K8N
*

[Motherboard Specification]
*Motherboard Revision : 1.03
*Motherboard BIOS Revision : 1003

[VGA Card Specification]
*VGA Card Vendor : eVGA
*VGA Card Model : Geforce 6600GT
*VGA Card Chipset : Geforce 6600GT
*VGA Card Driver : provided by eVGA

[CPU Specification]
*CPU Vendor : AMD x 2
*CPU Type : Opteron (Sledgehammer)
*CPU Speed : 240

[Memory Specification]
*Memory Vendor : Kingston
*Memory Model : KVR400D8R3A/512
*Memory Capacity : 512mb x 2 dual channel setup

[HDD Specification]
HDD Vendor : Western Digital
HDD Model : WD1200
HDD Capacity ! : 120 GB

[Add-on Card Specification]
Add-on Card Vendor : Hauppauge
Add-on Card Type : TV Card
Add-on Card Model : WinTV D

*Operating System : Linux x86_64(primary), Windows x86_64

[Problem Description]
I just wanted to know if there was a BIOS revision in the works for this
mainboard that addresses IO-APIC and ACPI issues with Linux and Windows. I
am sure I am not the only person who has sent email about the problems.

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Re: ASUS K8N-DL Beta BIOS

[Sean Bruno]

On Fri, 2005-07-01 at 14:19 -0500, Hodle, Brian wrote:
> Sean,
>    You might get a laugh out of this! It's a reply from ASUS about the
> motherboard (this was 2 days b4 they released the 1004.7 BETA BIOS.
> 
> Pretty sad when ASUS tells you to "Clear your CMOS". I thought I asked a
> pretty straightforward tech question... Makes me wonder if they even read
> it, or they had a PERL script do it!
> 
> Ps. New BIOS didn't change a thing. The PCI Device names in the ACPI table
> are not entered in a fashion that the kernel recognizes. Maybe ASUS decided
> to 'optimize' routing by making a more efficient table?' nah..
> 
> Cheers,
> 
> -Brian
> 
This is pretty much the reaction that I am getting from calling ASUS
tech support.  They have told me on several occasions that they will
"call me back" and never do.  I am fairly certain that there is a
problem with the BIOS, but the kernel could be modified to ignore the
issue as a backup plan.

I received some insight from an individual at Nvidia that looks
something like this:

There are several issues immediately apparent with the BIOS.

It has an ACPI interrupt override for IRQ0 to Global System Interrupt 2
(GSI 2) that is incorrect -

ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)

and is the root cause of the later warnings to do with the timer:

..MP-BIOS bug: 8254 timer not connected to IO-APIC
...trying to set up timer (IRQ0) through the 8259A ...  failed.
timer doesn't work through the IO-APIC - disabling NMI Watchdog!
...trying to set up timer as Virtual Wire IRQ...Uhhuh. NMI received for
unknown reason 3d.
Dazed and confused, but trying to continue
Do you have a strange power saving mode enabled?
 failed.
...trying to set up timer as ExtINT IRQ... works.

The Linux kernel (2.6.9 onwards) contains code to specifically detect
this interrupt redirect on NVIDIA hardware, and ignore it, but for some
reason it isn't kicking in on your setup. Not sure why that is.

Also, the ACPI PCI Interrupt Routing Table (PRT) contains references to
entries that don't exist elsewhere in the ACPI tables:

ACPI: Subsystem revision 20050309
    ACPI-0352: *** Error: Looking up [\_SB_.PCI0.LNK0] in namespace,
AE_NOT_FOUND
search_node ffff81013ffca240 start_node ffff81013ffca240 return_node
0000000000000000
    ACPI-0352: *** Error: Looking up [\_SB_.PCI0.APC0] in namespace,
AE_NOT_FOUND
search_node ffff81013ffca140 start_node ffff81013ffca140 return_node
0000000000000000

Linux unfortunately appears to give up on parsing the PRT when this
happens, unlike Windows, which will parse the table despite these
errors. Without parsing the PRT, Linux cannot know how to route
interrupts for various PCI devices, which results in the later errors:

...
ACPI: PCI Interrupt 0000:02:00.0[A]: no GSI - using IRQ 3
...
ACPI: PCI Interrupt 0000:00:04.0[A]: no GSI - using IRQ 11

I'm guessing that your Broadcom networking, AC97 sound and USB 1.1
controller may not be working correctly as a result of this.

The Linux kernel could be modified to continue parsing PRTs when errors
are encountered. However, it is the BIOS that is at fault here.

Sean

Re: ASUS K8N-DL Beta BIOS

[Alistair John Strachan]

On Friday 01 Jul 2005 20:42, Sean Bruno wrote:
> On Fri, 2005-07-01 at 14:19 -0500, Hodle, Brian wrote:
> > Sean,
> >    You might get a laugh out of this! It's a reply from ASUS about the
> > motherboard (this was 2 days b4 they released the 1004.7 BETA BIOS.
> >
> > Pretty sad when ASUS tells you to "Clear your CMOS". I thought I asked a
> > pretty straightforward tech question... Makes me wonder if they even read
> > it, or they had a PERL script do it!
> >
> > Ps. New BIOS didn't change a thing. The PCI Device names in the ACPI
> > table are not entered in a fashion that the kernel recognizes. Maybe ASUS
> > decided to 'optimize' routing by making a more efficient table?' nah..
> >
> > Cheers,
> >
> > -Brian
>
> This is pretty much the reaction that I am getting from calling ASUS
> tech support.  They have told me on several occasions that they will
> "call me back" and never do.  I am fairly certain that there is a
> problem with the BIOS, but the kernel could be modified to ignore the
> issue as a backup plan.
>
> I received some insight from an individual at Nvidia that looks
> something like this:
>
> There are several issues immediately apparent with the BIOS.
>
> It has an ACPI interrupt override for IRQ0 to Global System Interrupt 2
> (GSI 2) that is incorrect -
>
> ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
>
> and is the root cause of the later warnings to do with the timer:
>
> ..MP-BIOS bug: 8254 timer not connected to IO-APIC
> ...trying to set up timer (IRQ0) through the 8259A ...  failed.
> timer doesn't work through the IO-APIC - disabling NMI Watchdog!
> ...trying to set up timer as Virtual Wire IRQ...Uhhuh. NMI received for
> unknown reason 3d.
> Dazed and confused, but trying to continue
> Do you have a strange power saving mode enabled?
>  failed.
> ...trying to set up timer as ExtINT IRQ... works.
>
> The Linux kernel (2.6.9 onwards) contains code to specifically detect
> this interrupt redirect on NVIDIA hardware, and ignore it, but for some
> reason it isn't kicking in on your setup. Not sure why that is.

(Added Andi Kleen CC).

This is the exact problem I reported to Andi just after 2.6.12 was released. 
My MSI nForce3 board didn't work with the override either, and my buggy BIOS 
wasn't detected by the override (even though it should have been).

Fortunately MSI apparently fixed this before ASUS because the latest BIOS 
(1.17 or something) corrects the flaw.

I can't really remember whether the detection problem was resolved; my 
specific (APIC related) issue was.

Andi?

-- 
Cheers,
Alistair.

personal:   alistair()devzero!co!uk
university: s0348365()sms!ed!ac!uk
student:    CS/CSim Undergraduate
contact:    1F2 55 South Clerk Street,
            Edinburgh. EH8 9PP.

Re: ASUS K8N-DL Beta BIOS

[Andi Kleen]

> I can't really remember whether the detection problem was resolved; my 
> specific (APIC related) issue was.
> 
> Andi?

Does it work with acpi_skip_timer_override ? 

-Andi

Re: ASUS K8N-DL Beta BIOS

[Sean Bruno]

On Sat, 2005-07-02 at 21:44 +0200, Andi Kleen wrote:
> > I can't really remember whether the detection problem was resolved; my 
> > specific (APIC related) issue was.
> > 
> > Andi?
> 
> Does it work with acpi_skip_timer_override ? 
> 
> -Andi

Not to be a crank here, but I can't find reference to this
function/variable/#DEFINE in any of the ACPI code nor can I find a
decent reference to this in the lkml lists...So I must not understand
your suggestion.

What are you asking me to check?

Sean

Re: ASUS K8N-DL Beta BIOS

[Alexander Nyberg]

lör 2005-07-02 klockan 21:32 -0700 skrev Sean Bruno:
> On Sat, 2005-07-02 at 21:44 +0200, Andi Kleen wrote:
> > > I can't really remember whether the detection problem was resolved; my 
> > > specific (APIC related) issue was.
> > > 
> > > Andi?
> > 
> > Does it work with acpi_skip_timer_override ? 
> > 
> > -Andi
> 
> Not to be a crank here, but I can't find reference to this
> function/variable/#DEFINE in any of the ACPI code nor can I find a
> decent reference to this in the lkml lists...So I must not understand
> your suggestion.
> 
> What are you asking me to check?

It's a boot command line parameter (Documentation/kernel-parameters.txt)

Re: ASUS K8N-DL Beta BIOS

[Sean Bruno]

[-- Attachment #1: Type: text/plain, Size: 840 bytes --]

On Sun, 2005-07-03 at 09:37 +0200, Alexander Nyberg wrote:
> lör 2005-07-02 klockan 21:32 -0700 skrev Sean Bruno:
> > On Sat, 2005-07-02 at 21:44 +0200, Andi Kleen wrote:
> > > > I can't really remember whether the detection problem was resolved; my 
> > > > specific (APIC related) issue was.
> > > > 
> > > > Andi?
> > > 
> > > Does it work with acpi_skip_timer_override ? 
> > > 
> > > -Andi
> > 
> > Not to be a crank here, but I can't find reference to this
> > function/variable/#DEFINE in any of the ACPI code nor can I find a
> > decent reference to this in the lkml lists...So I must not understand
> > your suggestion.
> > 
> > What are you asking me to check?
> 
> It's a boot command line parameter (Documentation/kernel-parameters.txt)
Booted 2.6.12 with acpi_skip_timer_override.  Here is the dmesg output
for your review.



[-- Attachment #2: dmesg.acpi_skip_timer_override.out --]
[-- Type: text/plain, Size: 22708 bytes --]

Bootdata ok (command line is ro root=/dev/VolGroup00/LogVol00 rhgb apic=debug acpi=verbose acpi_skip_timer_override)
Linux version 2.6.12 (root@home-desk) (gcc version 4.0.0 20050519 (Red Hat 4.0.0-8)) #1 SMP Sat Jun 18 10:21:14 PDT 2005
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009e400 (usable)
 BIOS-e820: 000000000009e400 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 00000000bfff0000 (usable)
 BIOS-e820: 00000000bfff0000 - 00000000bfff3000 (ACPI NVS)
 BIOS-e820: 00000000bfff3000 - 00000000c0000000 (ACPI data)
 BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
 BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
 BIOS-e820: 0000000100000000 - 00000001c0000000 (usable)
ACPI: RSDP (v000 Nvidia                                ) @ 0x00000000000f7650
ACPI: RSDT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x00000000bfff3040
ACPI: FADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x00000000bfff30c0
ACPI: SSDT (v001 PTLTD  POWERNOW 0x00000001  LTP 0x00000001) @ 0x00000000bfff9680
ACPI: SRAT (v001 AMD    HAMMER   0x00000001 AMD  0x00000001) @ 0x00000000bfff9880
ACPI: MCFG (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x00000000bfff99c0
ACPI: MADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x00000000bfff9580
ACPI: DSDT (v001 NVIDIA AWRDACPI 0x00001000 MSFT 0x0100000e) @ 0x0000000000000000
SRAT: PXM 0 -> APIC 0 -> Node 0
SRAT: PXM 1 -> APIC 1 -> Node 1
SRAT: Node 0 PXM 0 0-9ffff
SRAT: Node 0 PXM 0 0-bfffffff
SRAT: Node 0 PXM 0 0-13fffffff
SRAT: Node 1 PXM 1 140000000-1bfffffff
node 1 shift 24 addr 140000000 conflict 0
Bootmem setup node 0 0000000000000000-000000013fffffff
Bootmem setup node 1 0000000140000000-00000001bfffffff
On node 0 totalpages: 1310719
  DMA zone: 4096 pages, LIFO batch:1
  Normal zone: 1306623 pages, LIFO batch:31
  HighMem zone: 0 pages, LIFO batch:1
On node 1 totalpages: 524287
  DMA zone: 0 pages, LIFO batch:1
  Normal zone: 524287 pages, LIFO batch:31
  HighMem zone: 0 pages, LIFO batch:1
ACPI: PM-Timer IO Port: 0x4008
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 15:5 APIC version 16
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Processor #1 15:5 APIC version 16
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] disabled)
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled)
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 4, version 17, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: BIOS IRQ0 pin2 override ignored.
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge)
ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge)
ACPI: IRQ9 used by override.
ACPI: IRQ14 used by override.
ACPI: IRQ15 used by override.
Setting APIC routing to flat
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at c0000000 (gap: c0000000:20000000)
Checking aperture...
CPU 0: aperture @ 8000000 size 32 MB
Aperture from northbridge cpu 0 too small (32 MB)
No AGP bridge found
Your BIOS doesn't leave a aperture memory hole
Please enable the IOMMU option in the BIOS setup
This costs you 64 MB of RAM
Mapping aperture over 65536 KB of RAM @ 8000000
Built 2 zonelists
Kernel command line: ro root=/dev/VolGroup00/LogVol00 rhgb apic=debug acpi=verbose acpi_skip_timer_override
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 131072 bytes)
time.c: Using 3.579545 MHz PM timer.
time.c: Detected 2010.339 MHz processor.
Console: colour VGA+ 80x25
Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
Memory: 6103952k/7340032k available (2375k kernel code, 0k reserved, 1275k data, 228k init)
Calibrating delay loop... 3981.31 BogoMIPS (lpj=1990656)
Security Framework v1.0.0 initialized
SELinux:  Initializing.
SELinux:  Starting in permissive mode
selinux_register_security:  Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 256
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 1024K (64 bytes/line)
enabled ExtINT on CPU#0
ENABLING IO-APIC IRQs
Synchronizing Arb IDs.
init IO_APIC IRQs
 IO-APIC (apicid-pin) 4-16, 4-17, 4-18, 4-19, 4-20, 4-21, 4-22, 4-23 not connected.
..TIMER: vector=0x31 pin1=0 pin2=-1
Using local APIC timer interrupts.
Detected 12.564 MHz APIC timer.
Booting processor 1/1 rip 6000 rsp ffff8101bff89f58
Initializing CPU#1
masked ExtINT on CPU#1
Calibrating delay loop... 2007.04 BogoMIPS (lpj=1003520)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 1024K (64 bytes/line)
AMD Opteron(tm) Processor 246 stepping 0a
CPU 1: Syncing TSC to CPU 0.
Brought up 2 CPUs
CPU 1: synchronized TSC with CPU 0 (last diff 177 cycles, maxerr 516 cycles)
Disabling vsyscall due to use of PM timer
time.c: Using PM based timekeeping.
testing NMI watchdog ... CPU#1: NMI appears to be stuck (10->14)!
CPU0 attaching sched-domain:
 domain 0: span 00000001
  groups: 00000001
  domain 1: span 00000001
   groups: 00000001
   domain 2: span 00000003
    groups: 00000001 00000002
CPU1 attaching sched-domain:
 domain 0: span 00000002
  groups: 00000002
  domain 1: span 00000002
   groups: 00000002
   domain 2: span 00000003
    groups: 00000002 00000001
checking if image is initramfs... it is
NET: Registered protocol family 16
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20050309
    ACPI-0352: *** Error: Looking up [\_SB_.PCI0.LNK0] in namespace, AE_NOT_FOUND
search_node ffff81013ffca280 start_node ffff81013ffca280 return_node 0000000000000000
    ACPI-0352: *** Error: Looking up [\_SB_.PCI0.APC0] in namespace, AE_NOT_FOUND
search_node ffff81013ffca180 start_node ffff81013ffca180 return_node 0000000000000000
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
PCI: Transparent bridge - 0000:00:09.0
Boot video device is 0000:04:00.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
    ACPI-0352: *** Error: Looking up [\_SB_.PCI0.APC0] in namespace, AE_NOT_FOUND
search_node ffff81013ffca180 start_node ffff81013ffca180 return_node 0000000000000000
    ACPI-1138: *** Error: Method execution failed [\_SB_.PCI0._PRT] (Node ffff81013ffca140), AE_NOT_FOUND
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 *5 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK2] (IRQs *3 4 5 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK3] (IRQs 3 4 5 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNK4] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNK5] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LUBA] (IRQs 3 4 *5 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LUBB] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LMAC] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LACI] (IRQs *3 4 5 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LMCI] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LSMB] (IRQs *3 4 5 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LUB2] (IRQs 3 4 5 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LIDE] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LSID] (IRQs 3 4 *5 7 9 10 11 12 14 15)
ACPI: PCI Interrupt Link [LFID] (IRQs 3 4 5 7 9 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LPCA] (IRQs 3 4 5 7 9 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [APC1] (IRQs 16) *0, disabled.
ACPI: PCI Interrupt Link [APC2] (IRQs 17) *0, disabled.
ACPI: PCI Interrupt Link [APC3] (IRQs 18) *0, disabled.
ACPI: PCI Interrupt Link [APC4] (IRQs 19) *0, disabled.
ACPI: PCI Interrupt Link [APC5] (IRQs *16), disabled.
ACPI: PCI Interrupt Link [APCF] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [APCG] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [APCH] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [APCJ] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [APCK] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [APCS] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [APCZ] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [APSI] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [APSJ] (IRQs 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [APCP] (IRQs 20 21 22 23) *0, disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
IOAPIC[0]: Set PCI routing entry (4-8 -> 0x71 -> IRQ 8 Mode:0 Active:0)
IOAPIC[0]: Set PCI routing entry (4-13 -> 0x99 -> IRQ 13 Mode:0 Active:0)
IOAPIC[0]: Set PCI routing entry (4-6 -> 0x61 -> IRQ 6 Mode:0 Active:0)
IOAPIC[0]: Set PCI routing entry (4-4 -> 0x51 -> IRQ 4 Mode:0 Active:0)
IOAPIC[0]: Set PCI routing entry (4-7 -> 0x69 -> IRQ 7 Mode:0 Active:0)
IOAPIC[0]: Set PCI routing entry (4-12 -> 0x91 -> IRQ 12 Mode:0 Active:0)
IOAPIC[0]: Set PCI routing entry (4-1 -> 0x39 -> IRQ 1 Mode:0 Active:0)
IOAPIC[0]: Set PCI routing entry (4-10 -> 0x81 -> IRQ 10 Mode:0 Active:0)
pnp: PnP ACPI: found 15 devices
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
number of MP IRQ sources: 16.
number of IO-APIC #4 registers: 24.
testing the IO APIC.......................

IO APIC #4......
.... register #00: 00000000
.......    : physical APIC id: 00
.... register #01: 00170011
.......     : max redirection entries: 0017
.......     : PRQ implemented: 0
.......     : IO APIC version: 0011
.... register #02: 00000000
.......     : arbitration: 00
.... IRQ redirection table:
 NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:   
 00 003 03  0    0    0   0   0    1    1    31
 01 003 03  1    0    0   0   0    1    1    39
 02 003 03  0    0    0   0   0    1    1    41
 03 003 03  0    0    0   0   0    1    1    49
 04 003 03  1    0    0   0   0    1    1    51
 05 003 03  0    0    0   0   0    1    1    59
 06 003 03  1    0    0   0   0    1    1    61
 07 003 03  1    0    0   0   0    1    1    69
 08 003 03  1    0    0   0   0    1    1    71
 09 003 03  0    1    0   0   0    1    1    79
 0a 003 03  1    0    0   0   0    1    1    81
 0b 003 03  0    0    0   0   0    1    1    89
 0c 003 03  1    0    0   0   0    1    1    91
 0d 003 03  1    0    0   0   0    1    1    99
 0e 003 03  0    0    0   0   0    1    1    A1
 0f 003 03  0    0    0   0   0    1    1    A9
 10 000 00  1    0    0   0   0    0    0    00
 11 000 00  1    0    0   0   0    0    0    00
 12 000 00  1    0    0   0   0    0    0    00
 13 000 00  1    0    0   0   0    0    0    00
 14 000 00  1    0    0   0   0    0    0    00
 15 000 00  1    0    0   0   0    0    0    00
 16 000 00  1    0    0   0   0    0    0    00
 17 000 00  1    0    0   0   0    0    0    00
Using vector-based indexing
IRQ to pin mappings:
IRQ0 -> 0:0
IRQ1 -> 0:1
IRQ2 -> 0:2
IRQ3 -> 0:3
IRQ4 -> 0:4
IRQ5 -> 0:5
IRQ6 -> 0:6
IRQ7 -> 0:7
IRQ8 -> 0:8
IRQ9 -> 0:9
IRQ10 -> 0:10
IRQ11 -> 0:11
IRQ12 -> 0:12
IRQ13 -> 0:13
IRQ14 -> 0:14
IRQ15 -> 0:15
.................................... done.
PCI-DMA: Disabling AGP.
PCI-DMA: aperture base @ 8000000 size 65536 KB
PCI-DMA: Reserving 64MB of IOMMU area in the AGP aperture
pnp: 00:00: ioport range 0x4000-0x407f could not be reserved
pnp: 00:00: ioport range 0x4080-0x40ff has been reserved
pnp: 00:00: ioport range 0x4400-0x447f has been reserved
pnp: 00:00: ioport range 0x4480-0x44ff could not be reserved
pnp: 00:00: ioport range 0x4800-0x487f has been reserved
pnp: 00:00: ioport range 0x4880-0x48ff has been reserved
IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $
audit: initializing netlink socket (disabled)
audit(1120507338.082:0): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
SELinux:  Registering netfilter hooks
Initializing Cryptographic API
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
PCI: Setting latency timer of device 0000:00:0c.0 to 64
pcie_portdrv_probe->Dev[005d:10de] has invalid IRQ. Check vendor BIOS
assign_interrupt_mode Found MSI capability
Allocate Port Service[pcie00]
PCI: Setting latency timer of device 0000:00:0d.0 to 64
pcie_portdrv_probe->Dev[005d:10de] has invalid IRQ. Check vendor BIOS
assign_interrupt_mode Found MSI capability
Allocate Port Service[pcie00]
PCI: Setting latency timer of device 0000:00:0e.0 to 64
pcie_portdrv_probe->Dev[005d:10de] has invalid IRQ. Check vendor BIOS
assign_interrupt_mode Found MSI capability
Allocate Port Service[pcie00]
Real Time Clock Driver v1.12
Linux agpgart interface v0.101 (c) Dave Jones
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 76 ports, IRQ sharing enabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFORCE-CK804: IDE controller at PCI slot 0000:00:06.0
NFORCE-CK804: chipset revision 242
NFORCE-CK804: not 100% native mode: will probe irqs later
NFORCE-CK804: 0000:00:06.0 (rev f2) UDMA133 controller
    ide0: BM-DMA at 0xfa00-0xfa07, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xfa08-0xfa0f, BIOS settings: hdc:DMA, hdd:DMA
Probing IDE interface ide0...
Probing IDE interface ide1...
hdc: Pioneer DVD-ROM ATAPIModel DVD-105S 013, ATAPI CD/DVD-ROM drive
hdd: Polaroid BurnMAX48, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
Probing IDE interface ide0...
Probing IDE interface ide2...
Probing IDE interface ide3...
Probing IDE interface ide4...
Probing IDE interface ide5...
hdc: ATAPI 40X DVD-ROM drive, 512kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
hdd: ATAPI 48X CD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
ide-floppy driver 0.99.newide
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.01:USB HID core driver
mice: PS/2 mouse device common for all mice
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
NET: Registered protocol family 2
IP: routing cache hash table of 32768 buckets, 512Kbytes
TCP established hash table entries: 262144 (order: 10, 4194304 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
powernow-k8: Found 2 AMD Athlon 64 / Opteron processors (version 1.40.2)
powernow-k8:    0 : fid 0xc (2000 MHz), vid 0x2 (1500 mV)
powernow-k8:    1 : fid 0xa (1800 MHz), vid 0x6 (1400 mV)
powernow-k8:    2 : fid 0x2 (1000 MHz), vid 0xe (1200 mV)
cpu_init done, current fid 0xc, vid 0x2
powernow-k8:    0 : fid 0xc (2000 MHz), vid 0x2 (1500 mV)
powernow-k8:    1 : fid 0xa (1800 MHz), vid 0x6 (1400 mV)
powernow-k8:    2 : fid 0x2 (1000 MHz), vid 0xe (1200 mV)
cpu_init done, current fid 0x2, vid 0xe
ACPI wakeup devices: 
HUB0 XVR0 XVR1 XVR2 XVR3 USB0 USB2 MMAC MMCI UAR1 
ACPI: (supports S0 S1 S3 S4 S5)
Freeing unused kernel memory: 228k freed
input: AT Translated Set 2 keyboard on isa0060/serio0
SCSI subsystem initialized
libata version 1.11 loaded.
sata_sil version 0.9
ACPI: PCI Interrupt Link [APC2] enabled at IRQ 17
IOAPIC[0]: Set PCI routing entry (4-17 -> 0xd1 -> IRQ 17 Mode:1 Active:1)
ACPI: PCI Interrupt 0000:01:09.0[A] -> Link [APC2] -> GSI 17 (level, low) -> IRQ 209
ata1: SATA max UDMA/100 cmd 0xFFFFC20000004080 ctl 0xFFFFC2000000408A bmdma 0xFFFFC20000004000 irq 209
ata2: SATA max UDMA/100 cmd 0xFFFFC200000040C0 ctl 0xFFFFC200000040CA bmdma 0xFFFFC20000004008 irq 209
ata3: SATA max UDMA/100 cmd 0xFFFFC20000004280 ctl 0xFFFFC2000000428A bmdma 0xFFFFC20000004200 irq 209
ata4: SATA max UDMA/100 cmd 0xFFFFC200000042C0 ctl 0xFFFFC200000042CA bmdma 0xFFFFC20000004208 irq 209
logips2pp: Detected unknown logitech mouse model 62
input: ImExPS/2 Logitech Explorer Mouse on isa0060/serio1
ata1: dev 0 cfg 49:2f00 82:346b 83:7f01 84:4003 85:3c69 86:3e01 87:4003 88:20ff
ata1: dev 0 ATA, max UDMA7, 312581808 sectors: lba48
ata1: dev 0 configured for UDMA/100
scsi0 : sata_sil
ata2: dev 0 cfg 49:2f00 82:346b 83:7f01 84:4003 85:3c68 86:3c01 87:4003 88:20ff
ata2: dev 0 ATA, max UDMA7, 312581808 sectors: lba48
ata2: dev 0 configured for UDMA/100
scsi1 : sata_sil
ata3: no device found (phy stat 00000000)
scsi2 : sata_sil
ata4: no device found (phy stat 00000000)
scsi3 : sata_sil
  Vendor: ATA       Model: SAMSUNG SP1614C   Rev: SW10
  Type:   Direct-Access                      ANSI SCSI revision: 05
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
SCSI device sda: drive cache: write back
 sda: sda1 sda2
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
  Vendor: ATA       Model: SAMSUNG SP1614C   Rev: SW10
  Type:   Direct-Access                      ANSI SCSI revision: 05
SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB)
SCSI device sdb: drive cache: write back
SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB)
SCSI device sdb: drive cache: write back
 sdb: sdb1
Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0
sata_nv version 0.6
ACPI: PCI Interrupt 0000:00:07.0[A]: no GSI - using IRQ 5
PCI: Setting latency timer of device 0000:00:07.0 to 64
ata5: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xF500 irq 5
ata6: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xF508 irq 5
ata5: no device found (phy stat 00000000)
scsi4 : sata_nv
ata6: no device found (phy stat 00000000)
scsi5 : sata_nv
ACPI: PCI Interrupt 0000:00:08.0[A]: no GSI - using IRQ 11
PCI: Setting latency timer of device 0000:00:08.0 to 64
ata7: SATA max UDMA/133 cmd 0x9E0 ctl 0xBE2 bmdma 0xF000 irq 11
ata8: SATA max UDMA/133 cmd 0x960 ctl 0xB62 bmdma 0xF008 irq 11
ata7: no device found (phy stat 00000000)
scsi6 : sata_nv
ata8: no device found (phy stat 00000000)
scsi7 : sata_nv
device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@redhat.com
cdrom: open failed.
cdrom: open failed.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
SELinux:  Disabled at runtime.
SELinux:  Unregistering netfilter hooks
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
tg3.c:v3.31 (June 8, 2005)
ACPI: PCI Interrupt 0000:02:00.0[A]: no GSI - using IRQ 5
PCI: Setting latency timer of device 0000:02:00.0 to 64
eth0: Tigon3 [partno(BCM95751) rev 4101 PHY(5750)] (PCIX:100MHz:32-bit) 10/100/1000BaseT Ethernet 00:11:d8:d3:08:05
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1] 
eth0: dma_rwctrl[76180000]
e100: Intel(R) PRO/100 Network Driver, 3.4.8-k2-NAPI
e100: Copyright(c) 1999-2005 Intel Corporation
ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18
IOAPIC[0]: Set PCI routing entry (4-18 -> 0xd9 -> IRQ 18 Mode:1 Active:1)
ACPI: PCI Interrupt 0000:01:06.0[A] -> Link [APC3] -> GSI 18 (level, low) -> IRQ 217
e100: eth1: e100_probe: addr 0xfe8ff000, irq 217, MAC addr 00:03:47:96:ED:4E
ACPI: PCI Interrupt 0000:00:04.0[A]: no GSI - using IRQ 3
PCI: Setting latency timer of device 0000:00:04.0 to 64
intel8x0_measure_ac97_clock: measured 49560 usecs
intel8x0: clocking to 46797
shpchp: Address64 -------- Resource unparsed
shpchp: Address64 -------- Resource unparsed
shpchp: Address64 -------- Resource unparsed
shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
i2c_adapter i2c-0: nForce2 SMBus adapter at 0x4c00
i2c_adapter i2c-1: nForce2 SMBus adapter at 0x4c40
ACPI: PCI Interrupt 0000:00:02.1[B]: no GSI - using IRQ 11
PCI: Setting latency timer of device 0000:00:02.1 to 64
ehci_hcd 0000:00:02.1: EHCI Host Controller
ehci_hcd 0000:00:02.1: debug port 1
ehci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:02.1: irq 11, io mem 0xfeb00000
PCI: cache line size of 64 is not supported by device 0000:00:02.1
ehci_hcd 0000:00:02.1: park 0
ehci_hcd 0000:00:02.1: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 10 ports detected
ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ACPI: PCI Interrupt 0000:00:02.0[A]: no GSI - using IRQ 5
PCI: Setting latency timer of device 0000:00:02.0 to 64
ohci_hcd 0000:00:02.0: OHCI Host Controller
ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 2
ohci_hcd 0000:00:02.0: irq 5, io mem 0xfeaff000
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 10 ports detected
ieee1394: Initialized config rom entry `ip1394'
ohci1394: $Rev: 1250 $ Ben Collins <bcollins@debian.org>
ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
IOAPIC[0]: Set PCI routing entry (4-16 -> 0xe1 -> IRQ 16 Mode:1 Active:1)
ACPI: PCI Interrupt 0000:01:08.0[A] -> Link [APC1] -> GSI 16 (level, low) -> IRQ 225
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[225]  MMIO=[fe8fe000-fe8fe7ff]  Max Packet=[2048]
NET: Registered protocol family 10
Disabled Privacy Extensions on device ffffffff80444bc0(lo)
ieee1394: Host added: ID:BUS[0-00:1023]  GUID[0011d80000277ca6]
IPv6 over IPv4 tunneling driver
ACPI: Power Button (FF) [PWRF]
ibm_acpi: ec object not found
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
cdrom: open failed.
cdrom: open failed.
cdrom: open failed.
cdrom: open failed.
EXT3 FS on dm-0, internal journal
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Adding 2031608k swap on /dev/VolGroup00/LogVol01.  Priority:-1 extents:1
e100: eth1: e100_watchdog: link up, 100Mbps, full-duplex
parport: PnPBIOS parport detected.
parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
lp0: using parport0 (interrupt-driven).
lp0: console ready
eth1: no IPv6 routers present

Re: ASUS K8N-DL Beta BIOS

[Sean Bruno]

Even more fun today with the ASUS release 1004 of the BIOS.   Looks like
you CANNOT disable the Nvidia SATA controller without causing the system
to lock.  I can't seem to work around this new issue with the system
without backing my BIOS down to 1003.

With the Nvidia SATA controller enabled, 2.6.12.2 seems to go insane
attempting to talk with it(nv_raid seems to have trouble).  I am not
going to document this issue, as there are so many other issues that are
on-going with this board.

It's starting to look like this is a large and expensive exchanger of
electricity for heat at this point.

2.6.13-rc1 has some kind of issue with my board due to it's 6GB of RAM.
It stops when it discovers that there is no "IOMMU".  Since I don't see
anything obvious in the BIOS to activate, I can't boot 2.6.13 at all.

Sean

Re: ASUS K8N-DL Beta BIOS

[Andi Kleen]

> 2.6.13-rc1 has some kind of issue with my board due to it's 6GB of RAM.
> It stops when it discovers that there is no "IOMMU".  Since I don't see
> anything obvious in the BIOS to activate, I can't boot 2.6.13 at all.

Full boot log please?

-Andi

Re: ASUS K8N-DL Beta BIOS

[Sean Bruno]

On Mon, 2005-07-04 at 23:26 +0200, Andi Kleen wrote:
> > 2.6.13-rc1 has some kind of issue with my board due to it's 6GB of RAM.
> > It stops when it discovers that there is no "IOMMU".  Since I don't see
> > anything obvious in the BIOS to activate, I can't boot 2.6.13 at all.
> 
> Full boot log please?
> 
Well, that might take me a while.  Since the system halts at this point,
I will have to whack together a serial cable to redirect the kernel
post.  

Sean

Re: ASUS K8N-DL Beta BIOS

[Andi Kleen]

> Bootdata ok (command line is ro root=/dev/VolGroup00/LogVol00 rhgb apic=debug acpi=verbose acpi_skip_timer_override)
> Linux version 2.6.12 (root@home-desk) (gcc version 4.0.0 20050519 (Red Hat 4.0.0-8)) #1 SMP Sat Jun 18 10:21:14 PDT 2005
> BIOS-provided physical RAM map:
>  BIOS-e820: 0000000000000000 - 000000000009e400 (usable)
>  BIOS-e820: 000000000009e400 - 00000000000a0000 (reserved)
>  BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
>  BIOS-e820: 0000000000100000 - 00000000bfff0000 (usable)
>  BIOS-e820: 00000000bfff0000 - 00000000bfff3000 (ACPI NVS)
>  BIOS-e820: 00000000bfff3000 - 00000000c0000000 (ACPI data)
>  BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
>  BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
>  BIOS-e820: 0000000100000000 - 00000001c0000000 (usable)
> ACPI: RSDP (v000 Nvidia                                ) @ 0x00000000000f7650
> ACPI: RSDT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x00000000bfff3040

Hrm, we definitely have code to force acpi_skip_timer_override 
on Nvidia. But it does not seem to trigger on your board.
I wonder if it has the Nvidia bridges behind other bridges
which might be too much for the simple minded scan in check_ioapic.

Can you perhaps send me lspci -v output? 

-Andi

Re: ASUS K8N-DL Beta BIOS

[Alan Cox]

On Gwe, 2005-07-01 at 20:42, Sean Bruno wrote:
> This is pretty much the reaction that I am getting from calling ASUS
> tech support.  They have told me on several occasions that they will
> "call me back" and never do. 

Ditto with problems I've seen on ASUS boards, even the high end ones. 

Re: ASUS K8N-DL Beta BIOS

[Lee Revell]

On Tue, 2005-07-05 at 16:54 +0100, Alan Cox wrote:
> On Gwe, 2005-07-01 at 20:42, Sean Bruno wrote:
> > This is pretty much the reaction that I am getting from calling ASUS
> > tech support.  They have told me on several occasions that they will
> > "call me back" and never do. 
> 
> Ditto with problems I've seen on ASUS boards, even the high end ones. 

Translation: "I have no idea what's wrong, and we don't have a working
escalation procedure.  Hopefully by the time you call us back, I'll be
gone for the day or on another call, and someone else will have to deal
with it."

Lee

Re: ASUS K8N-DL Beta BIOS

[Karim Yaghmour]

Hodle, Brian wrote:
> Pretty sad when ASUS tells you to "Clear your CMOS". I thought I asked a
> pretty straightforward tech question... Makes me wonder if they even read
> it, or they had a PERL script do it!

They told me the same thing. That seems to be their standard tech support
answer for anything they can't handle ...

Anyone from ASUS reading this should take notice:

Having so much traffic going on on the LKML regarding the inability of
competent people to get your board to work is a major PR problem. As a
result of this, you are likely to have already lost dozens of potential
customers who may have been looking at this board, but as a result of
what they found from doing a google on "Linux and K8N-DL" have probably
decided to purchase another product instead.

And if no one from ASUS is reading this, then ASUS has got far more
serious problems than the previous paragraph hints.

Karim
-- 
Author, Speaker, Developer, Consultant
Pushing Embedded and Real-Time Linux Systems Beyond the Limits
http://www.opersys.com || karim@opersys.com || 1-866-677-4546

ASUS K8N-DL Beta BIOS

[Sean Bruno]

Not sure if this will help, but ASUS just released a BIOS update for
those of us struggling with the Dual-Opteron Mobo, K8N-DL.

You should be able to grab it here:

http://support.asus.com/download/download.aspx?Type=All&model=K8N-DL

If not, I can email it to you....

Sean

Re: ASUS K8N-DL Beta BIOS

[Karim Yaghmour]

Sean Bruno wrote:
> Not sure if this will help, but ASUS just released a BIOS update for
> those of us struggling with the Dual-Opteron Mobo, K8N-DL.

Apart from the flashy start screen, same problems for me:
- No Ethernet
- No USB
- Still no operational secondary IDE..

:(

Karim
-- 
Author, Speaker, Developer, Consultant
Pushing Embedded and Real-Time Linux Systems Beyond the Limits
http://www.opersys.com || karim@opersys.com || 1-866-677-4546