NASLite Network Attached Storage

www.serverelements.com
Task-specific simplicity with low hardware requirements.
It is currently Wed Jun 18, 2025 2:43 pm

All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 4 posts ] 
Author Message
PostPosted: Sun Jul 08, 2007 11:24 am 
Offline

Joined: Thu Dec 01, 2005 1:57 pm
Posts: 73
I'm in the process of building new server with an ASUS p4v8x-mx board. I have worked out most hicups and its now stable enough I think to throw some data on.

But I'm still missing Fan State, Cooling Mode, Thermal State, Cpu Temp.

Power Button shows Avail.

Would like to see at least fan state and temp if it is accurate.

Its a cheap 3 slot motherboard and I may not be able to work around it.

Any ideas? TY


Top
 Profile  
 
 Post subject:
PostPosted: Mon Jul 09, 2007 7:04 pm 
Offline

Joined: Thu Dec 01, 2005 1:57 pm
Posts: 73
Looks like different versions of ACPI up to 3.0, board supports 2.0a


So I'm guessing the other functions are not obtainable with 2.0a? Or is it just a hit and miss??




* Jul 7 21:07:30 syslog.info syslogd started: BusyBox v1.01 (2007.03.15-22:03+0000)
* Jul 7 21:07:30 daemon.info init: ^MStarting pid 3600, console /dev/null: '/sbin/klogd'
* Jul 7 21:07:30 user.notice kernel: klogd started: BusyBox v1.01 (2007.03.15-22:03+0000)
* Jul 7 21:07:30 user.warn kernel: Linux version 2.4.34.NASLite (root@tzt) (gcc version 3.4.6) #1 Wed Apr 11 22:39:05 EDT 2007
* Jul 7 21:07:30 user.info kernel: BIOS-provided physical RAM map:
* Jul 7 21:07:30 user.warn kernel: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
* Jul 7 21:07:30 user.warn kernel: BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
* Jul 7 21:07:30 user.warn kernel: BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
* Jul 7 21:07:30 user.warn kernel: BIOS-e820: 0000000000100000 - 000000003f7b0000 (usable)
* Jul 7 21:07:30 user.warn kernel: BIOS-e820: 000000003f7b0000 - 000000003f7c0000 (ACPI data)
* Jul 7 21:07:30 user.warn kernel: BIOS-e820: 000000003f7c0000 - 000000003f7f0000 (ACPI NVS)
* Jul 7 21:07:30 user.warn kernel: BIOS-e820: 000000003f7f0000 - 000000003f800000 (reserved)
* Jul 7 21:07:30 user.warn kernel: BIOS-e820: 00000000ff7c0000 - 0000000100000000 (reserved)
* Jul 7 21:07:30 user.warn kernel: Warning only 896MB will be used.
* Jul 7 21:07:30 user.warn kernel: Use a HIGHMEM enabled kernel.
* Jul 7 21:07:30 user.notice kernel: 896MB LOWMEM available.
* Jul 7 21:07:30 user.warn kernel: On node 0 totalpages: 229376
* Jul 7 21:07:30 user.warn kernel: zone(0): 4096 pages.
* Jul 7 21:07:30 user.warn kernel: zone(1): 225280 pages.
* Jul 7 21:07:30 user.warn kernel: zone(2): 0 pages.
* Jul 7 21:07:30 user.info kernel: ACPI: RSDP (v002 ACPIAM ) @ 0x000f8470
* Jul 7 21:07:30 user.info kernel: ACPI: XSDT (v001 A M I OEMXSDT 0x07000624 MSFT 0x00000097) @ 0x3f7b0100
* Jul 7 21:07:30 user.info kernel: ACPI: FADT (v003 A M I OEMFACP 0x07000624 MSFT 0x00000097) @ 0x3f7b0290
* Jul 7 21:07:30 user.info kernel: ACPI: MADT (v001 A M I OEMAPIC 0x07000624 MSFT 0x00000097) @ 0x3f7b0390
* Jul 7 21:07:30 user.info kernel: ACPI: OEMB (v001 A M I AMI_OEM 0x07000624 MSFT 0x00000097) @ 0x3f7c0040
* Jul 7 21:07:30 user.info kernel: ACPI: DSDT (v001 A0385 A0385000 0x00000000 INTL 0x02002026) @ 0x00000000
* Jul 7 21:07:30 user.warn kernel: Kernel command line: rw root=/dev/ram0 initrd=NASLite.02 quiet BOOT_IMAGE=naslite.01
* Jul 7 21:07:30 user.info kernel: Initializing CPU#0
* Jul 7 21:07:30 user.warn kernel: Detected 2200.003 MHz processor.
* Jul 7 21:07:30 user.warn kernel: Console: colour VGA+ 80x25
* Jul 7 21:07:30 user.warn kernel: Calibrating delay loop. 4377.80 BogoMIPS
* Jul 7 21:07:30 user.info kernel: Memory: 901996k/917504k available (2182k kernel code, 15120k reserved, 629k data, 536k init, 0k highmem)
* Jul 7 21:07:30 user.info kernel: Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
* Jul 7 21:07:30 user.info kernel: Inode cache hash table entries: 65536 (order: 7, 524288 bytes)
* Jul 7 21:07:30 user.info kernel: Mount cache hash table entries: 512 (order: 0, 4096 bytes)
* Jul 7 21:07:30 user.info kernel: Buffer cache hash table entries: 65536 (order: 6, 262144 bytes)
* Jul 7 21:07:30 user.warn kernel: Page-cache hash table entries: 262144 (order: 8, 1048576 bytes)
* Jul 7 21:07:30 user.info kernel: CPU: Trace cache: 12K uops, L1 D cache: 8K
* Jul 7 21:07:30 user.info kernel: CPU: L2 cache: 512K
* Jul 7 21:07:30 user.debug kernel: CPU: After generic, caps: 3febfbff 00000000 00000000 00000000
* Jul 7 21:07:30 user.debug kernel: CPU: Common caps: 3febfbff 00000000 00000000 00000000
* Jul 7 21:07:30 user.warn kernel: CPU: Intel(R) Pentium(R) 4 CPU 2.20GHz stepping 04
* Jul 7 21:07:30 user.info kernel: Enabling fast FPU save and restore. done.
* Jul 7 21:07:30 user.info kernel: Enabling unmasked SIMD FPU exception support. done.
* Jul 7 21:07:30 user.info kernel: Checking 'hlt' instruction. OK.
* Jul 7 21:07:30 user.warn kernel: ACPI: IRQ9 SCI: Edge set to Level Trigger.
* Jul 7 21:07:30 user.warn kernel: POSIX conformance testing by UNIFIX
* Jul 7 21:07:30 user.info kernel: ACPI: Subsystem revision 20040326
* Jul 7 21:07:30 user.info kernel: PCI: PCI BIOS revision 3.00 entry at 0xf0031, last bus=1
* Jul 7 21:07:30 user.info kernel: PCI: Using configuration type 1
* Jul 7 21:07:30 user.info kernel: ACPI: Interpreter enabled
* Jul 7 21:07:30 user.info kernel: ACPI: Using PIC for interrupt routing
* Jul 7 21:07:30 user.info kernel: ACPI: System [ACPI] (supports S0 S1 S3 S4 S5)
* Jul 7 21:07:30 user.info kernel: ACPI: PCI Root Bridge [PCI0] (00:00)
* Jul 7 21:07:30 user.warn kernel: PCI: Probing PCI hardware (bus 00)
* Jul 7 21:07:30 user.info kernel: PCI: Via IRQ fixup
* Jul 7 21:07:30 user.info kernel: PCI: Via IRQ fixup
* Jul 7 21:07:30 user.debug kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
* Jul 7 21:07:30 user.debug kernel: ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT]
* Jul 7 21:07:30 user.warn kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *10 11 12 14 15)
* Jul 7 21:07:30 user.warn kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 *5 6 7 10 11 12 14 15)
* Jul 7 21:07:30 user.warn kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 *11 12 14 15)
* Jul 7 21:07:30 user.warn kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
* Jul 7 21:07:30 user.warn kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
* Jul 7 21:07:30 user.warn kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
* Jul 7 21:07:30 user.warn kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
* Jul 7 21:07:30 user.warn kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
* Jul 7 21:07:30 user.info kernel: PCI: Probing PCI hardware
* Jul 7 21:07:30 user.warn kernel: ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
* Jul 7 21:07:30 user.warn kernel: ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 5
* Jul 7 21:07:30 user.warn kernel: ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
* Jul 7 21:07:30 user.info kernel: PCI: Using ACPI for IRQ routing
* Jul 7 21:07:30 user.info kernel: Linux NET4.0 for Linux 2.4
* Jul 7 21:07:30 user.info kernel: Based upon Swansea University Computer Society NET3.039
* Jul 7 21:07:30 user.warn kernel: Initializing RT netlink socket
* Jul 7 21:07:30 user.warn kernel: Starting kswapd
* Jul 7 21:07:30 user.info kernel: Journalled Block Device driver loaded
* Jul 7 21:07:30 user.info kernel: devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
* Jul 7 21:07:30 user.info kernel: devfs: boot_options: 0x1
* Jul 7 21:07:30 user.info kernel: Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
* Jul 7 21:07:30 user.info kernel: Power Button (FF) [PWRF]
* Jul 7 21:07:30 user.info kernel: ACPI: Processor [CPU1] (supports C1)
* Jul 7 21:07:30 user.info kernel: ACPI: Processor [CPU2] (supports C1)
* Jul 7 21:07:30 user.warn kernel: pty: 256 Unix98 ptys configured
* Jul 7 21:07:30 user.info kernel: Real Time Clock Driver v1.10f
* Jul 7 21:07:30 user.warn kernel: floppy0: no floppy controllers found
* Jul 7 21:07:30 user.warn kernel: RAMDISK driver initialized: 16 RAM disks of 8192K size 1024 blocksize
* Jul 7 21:07:30 user.info kernel: loop: loaded (max 8 devices)
* Jul 7 21:07:30 user.info kernel: Intel(R) PRO/1000 Network Driver - version 5.7.6-k1
* Jul 7 21:07:30 user.info kernel: Copyright (c) 1999-2004 Intel Corporation.
* Jul 7 21:07:30 user.info kernel: e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
* Jul 7 21:07:30 user.info kernel: dgrs: SW=$Id: dgrs.c,v 1.13 2000/06/06 04:07:00 rick Exp $ FW=Build 550 11/16/96 03:45:15
* Jul 7 21:07:30 user.warn kernel: FW Version=$Version$
* Jul 7 21:07:30 user.info kernel: pcnet32.c:v1.30h 06.24.2004 tsbogend@alpha.franken.de
* Jul 7 21:07:30 user.info kernel: ThunderLAN driver v1.15
* Jul 7 21:07:30 user.info kernel: TLAN: 0 devices installed, PCI: 0 EISA: 0
* Jul 7 21:07:30 user.info kernel: dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
* Jul 7 21:07:30 user.info kernel: ns83820.c: National Semiconductor DP83820 10/100/1000 driver.
* Jul 7 21:07:30 user.warn kernel: sk98lin: No adapter found.
* Jul 7 21:07:30 user.info kernel: forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.50.
* Jul 7 21:07:30 user.info kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
* Jul 7 21:07:30 user.info kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
* Jul 7 21:07:30 user.info kernel: VP_IDE: IDE controller at PCI slot 00:0f.1
* Jul 7 21:07:30 user.info kernel: VP_IDE: chipset revision 6
* Jul 7 21:07:30 user.info kernel: VP_IDE: not 100% native mode: will probe irqs later
* Jul 7 21:07:30 user.info kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
* Jul 7 21:07:30 user.info kernel: VP_IDE: VIA vt8237 (rev 00) IDE UDMA133 controller on pci00:0f.1
* Jul 7 21:07:30 user.info kernel: ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:DMA, hdb:pio
* Jul 7 21:07:30 user.info kernel: ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdc:DMA, hdd:DMA
* Jul 7 21:07:30 user.warn kernel: hda: WDC WD2500JB-55GVA0, ATA DISK drive
* Jul 7 21:07:30 user.warn kernel: hdc: WDC WD2000JB-22GVC0, ATA DISK drive
* Jul 7 21:07:30 user.warn kernel: hdd: Maxtor 4G160J8, ATA DISK drive
* Jul 7 21:07:30 user.warn kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
* Jul 7 21:07:30 user.warn kernel: ide1 at 0x170-0x177,0x376 on irq 15
* Jul 7 21:07:30 user.warn kernel: hda: attached ide-disk driver.
* Jul 7 21:07:30 user.warn kernel: hda: host protected area => 1
* Jul 7 21:07:30 user.info kernel: hda: 488397168 sectors (250059 MB) w/8192KiB Cache, CHS=30401/255/63, UDMA(100)
* Jul 7 21:07:30 user.warn kernel: hdc: attached ide-disk driver.
* Jul 7 21:07:30 user.warn kernel: hdc: host protected area => 1
* Jul 7 21:07:30 user.info kernel: hdc: 390721968 sectors (200050 MB) w/8192KiB Cache, CHS=24321/255/63, UDMA(100)
* Jul 7 21:07:30 user.warn kernel: hdd: attached ide-disk driver.
* Jul 7 21:07:30 user.warn kernel: hdd: host protected area => 1
* Jul 7 21:07:30 user.info kernel: hdd: 320173056 sectors (163929 MB) w/2048KiB Cache, CHS=19929/255/63, UDMA(133)
* Jul 7 21:07:30 user.info kernel: Partition check:
* Jul 7 21:07:30 user.info kernel: /dev/ide/host0/bus0/target0/lun0: p1
* Jul 7 21:07:30 user.info kernel: /dev/ide/host0/bus1/target0/lun0: p1
* Jul 7 21:07:30 user.info kernel: /dev/ide/host0/bus1/target1/lun0: p1
* Jul 7 21:07:30 user.info kernel: SCSI subsystem driver Revision: 1.00
* Jul 7 21:07:30 user.info kernel: Red Hat/Adaptec aacraid driver (1.1-3 Apr 11 2007 22:41:48)
* Jul 7 21:07:30 user.warn kernel: scsi: Detection failed (no card)
* Jul 7 21:07:30 user.notice kernel: megaraid: v2.10.10.1 (Release Date: Thu Jan 27 16:19:44 EDT 2005)
* Jul 7 21:07:30 user.warn kernel: GDT-HA: Storage RAID Controller Driver. Version: 3.04
* Jul 7 21:07:30 user.warn kernel: GDT-HA: Found 0 PCI Storage RAID Controllers
* Jul 7 21:07:30 user.warn kernel: 3ware Storage Controller device driver for Linux v1.02.00.037.
* Jul 7 21:07:30 user.warn kernel: 3w-xxxx: No cards found.
* Jul 7 21:07:30 user.debug kernel: libata version 1.20 loaded.
* Jul 7 21:07:30 user.debug kernel: PCI(00:0f.0): version 1.1
* Jul 7 21:07:30 user.info kernel: PCI(00:0f.0): routed to hard irq line 5
* Jul 7 21:07:30 user.info kernel: ata1: SATA max UDMA/133 cmd 0xE400 ctl 0xE082 bmdma 0xD880 irq 5
* Jul 7 21:07:30 user.info kernel: ata2: SATA max UDMA/133 cmd 0xE000 ctl 0xDC02 bmdma 0xD888 irq 5
* Jul 7 21:07:30 user.debug kernel: ata1: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4023 85:3469 86:3c01 87:4023 88:407f
* Jul 7 21:07:30 user.info kernel: ata1: dev 0 ATA-7, max UDMA/133, 976773168 sectors: LBA48
* Jul 7 21:07:30 user.info kernel: ata1: dev 0 configured for UDMA/133
* Jul 7 21:07:30 user.debug kernel: ata2: dev 0 cfg 49:2f00 82:346b 83:5b01 84:4003 85:3469 86:1801 87:4003 88:407f
* Jul 7 21:07:30 user.info kernel: ata2: dev 0 ATA-6, max UDMA/133, 234441648 sectors: LBA
* Jul 7 21:07:30 user.info kernel: ata2(0): applying bridge limits
* Jul 7 21:07:30 user.info kernel: ata2: dev 0 configured for UDMA/100
* Jul 7 21:07:30 user.info kernel: scsi1 : sata_via
* Jul 7 21:07:30 user.info kernel: scsi2 : sata_via
* Jul 7 21:07:30 user.warn kernel: Vendor: ATA Model: ST3500641AS Rev: 3.AA
* Jul 7 21:07:30 user.warn kernel: Type: Direct-Access ANSI SCSI revision: 05
* Jul 7 21:07:30 user.warn kernel: Vendor: ATA Model: ST3120023AS Rev: 3.01
* Jul 7 21:07:30 user.warn kernel: Type: Direct-Access ANSI SCSI revision: 05
* Jul 7 21:07:30 user.warn kernel: Attached scsi disk sda at scsi1, channel 0, id 0, lun 0
* Jul 7 21:07:30 user.warn kernel: Attached scsi disk sdb at scsi2, channel 0, id 0, lun 0
* Jul 7 21:07:30 user.warn kernel: SCSI device sda: 976773168 512-byte hdwr sectors (500108 MB)
* Jul 7 21:07:30 user.info kernel: /dev/scsi/host1/bus0/target0/lun0: p1
* Jul 7 21:07:30 user.warn kernel: SCSI device sdb: 234441648 512-byte hdwr sectors (120034 MB)
* Jul 7 21:07:30 user.info kernel: /dev/scsi/host2/bus0/target0/lun0: p1
* Jul 7 21:07:30 user.info kernel: raw1394: /dev/raw1394 device initialized
* Jul 7 21:07:30 user.info kernel: ebian.org>
* Jul 7 21:07:30 user.err kernel: ieee1394: sbp2: Driver forced to serialize I/O (serialize_io = 1)
* Jul 7 21:07:30 user.info kernel: usb.c: registered new driver usbdevfs
* Jul 7 21:07:30 user.info kernel: usb.c: registered new driver hub
* Jul 7 21:07:30 user.info kernel: ehci_hcd 00:10.4: PCI device 1106:3104
* Jul 7 21:07:30 user.info kernel: ehci_hcd 00:10.4: irq 11, pci mem f882c800
* Jul 7 21:07:30 user.info kernel: usb.c: new USB bus registered, assigned bus number 1
* Jul 7 21:07:30 user.info kernel: ehci_hcd 00:10.4: USB 2.0 enabled, EHCI 1.00, driver 2003-Dec-29/2.4
* Jul 7 21:07:30 user.info kernel: hub.c: USB hub found
* Jul 7 21:07:30 user.info kernel: hub.c: 8 ports detected
* Jul 7 21:07:30 user.info kernel: host/uhci.c: USB Universal Host Controller Interface driver v1.1
* Jul 7 21:07:30 user.info kernel: host/uhci.c: USB UHCI at I/O 0xec00, IRQ 5
* Jul 7 21:07:30 user.info kernel: usb.c: new USB bus registered, assigned bus number 2
* Jul 7 21:07:30 user.info kernel: hub.c: USB hub found
* Jul 7 21:07:30 user.info kernel: hub.c: 2 ports detected
* Jul 7 21:07:30 user.info kernel: host/uhci.c: USB UHCI at I/O 0xe880, IRQ 5
* Jul 7 21:07:30 user.info kernel: usb.c: new USB bus registered, assigned bus number 3
* Jul 7 21:07:30 user.info kernel: hub.c: USB hub found
* Jul 7 21:07:30 user.info kernel: hub.c: 2 ports detected
* Jul 7 21:07:30 user.info kernel: host/uhci.c: USB UHCI at I/O 0xe800, IRQ 10
* Jul 7 21:07:30 user.info kernel: usb.c: new USB bus registered, assigned bus number 4
* Jul 7 21:07:30 user.info kernel: hub.c: USB hub found
* Jul 7 21:07:30 user.info kernel: hub.c: 2 ports detected
* Jul 7 21:07:30 user.info kernel: host/uhci.c: USB UHCI at I/O 0xe480, IRQ 10
* Jul 7 21:07:30 user.info kernel: usb.c: new USB bus registered, assigned bus number 5
* Jul 7 21:07:30 user.info kernel: hub.c: USB hub found
* Jul 7 21:07:30 user.info kernel: hub.c: 2 ports detected
* Jul 7 21:07:30 user.info kernel: usb.c: registered new driver usbkbd
* Jul 7 21:07:30 user.info kernel: usbkbd.c: :USB HID Boot Protocol keyboard driver
* Jul 7 21:07:30 user.info kernel: Initializing USB Mass Storage driver.
* Jul 7 21:07:30 user.info kernel: usb.c: registered new driver usb-storage
* Jul 7 21:07:30 user.info kernel: USB Mass Storage support registered.
* Jul 7 21:07:30 user.info kernel: NET4: Linux TCP/IP 1.0 for NET4.0
* Jul 7 21:07:30 user.info kernel: IP Protocols: ICMP, UDP, TCP
* Jul 7 21:07:30 user.info kernel: IP: routing cache hash table of 8192 buckets, 64Kbytes
* Jul 7 21:07:30 user.info kernel: TCP: Hash tables configured (established 262144 bind 65536)
* Jul 7 21:07:30 user.info kernel: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
* Jul 7 21:07:30 user.notice kernel: RAMDISK: NASLite file system found at block 0
* Jul 7 21:07:30 user.warn kernel: .<6>hub.c: new USB device 00:10.4-6, assigned address 2
* Jul 7 21:07:30 user.warn kernel: .<6>scsi3 : SCSI emulation for USB Mass Storage devices
* Jul 7 21:07:30 user.warn kernel: . Vendor: LEXAR Model: JUMPDRIVE SECURE Rev: 1000
* Jul 7 21:07:30 user.warn kernel: Type: Direct-Access ANSI SCSI revision: 02
* Jul 7 21:07:30 user.warn kernel: .Attached scsi disk sdc at scsi3, channel 0, id 0, lun 0
* Jul 7 21:07:30 user.warn kernel: .SCSI device sdc: 1014784 512-byte hdwr sectors (520 MB)
* Jul 7 21:07:30 user.info kernel: /dev/scsi/host3/bus0/target0/lun0: p1
* Jul 7 21:07:30 user.debug kernel: WARNING: USB Mass Storage data integrity not assured
* Jul 7 21:07:30 user.debug kernel: USB Mass Storage device found at 2
* Jul 7 21:07:30 user.warn kernel: .<6>Freeing initrd memory: 1621k freed
* Jul 7 21:07:30 user.warn kernel: VFS: Mounted root (ext2 filesystem).
* Jul 7 21:07:30 user.info kernel: Mounted devfs on /dev
* Jul 7 21:07:30 user.info kernel: Freeing unused kernel memory: 536k freed
* Jul 7 21:07:30 user.info kernel: e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex
* Jul 7 21:07:30 user.info kernel: kjournald starting. Commit interval 5 seconds
* Jul 7 21:07:30 user.info kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,1), internal journal
* Jul 7 21:07:30 user.info kernel: EXT3-fs: mounted filesystem with ordered data mode.
* Jul 7 21:07:30 user.info kernel: kjournald starting. Commit interval 5 seconds
* Jul 7 21:07:30 user.info kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on ide1(22,1), internal journal
* Jul 7 21:07:30 user.info kernel: EXT3-fs: mounted filesystem with ordered data mode.
* Jul 7 21:07:30 user.info kernel: kjournald starting. Commit interval 5 seconds
* Jul 7 21:07:30 user.info kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on ide1(22,65), internal journal
* Jul 7 21:07:30 user.info kernel: EXT3-fs: mounted filesystem with ordered data mode.
* Jul 7 21:07:30 user.info kernel: kjournald starting. Commit interval 5 seconds
* Jul 7 21:07:30 user.info kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,1), internal journal
* Jul 7 21:07:30 user.info kernel: EXT3-fs: mounted filesystem with ordered data mode.
* Jul 7 21:07:30 user.info kernel: kjournald starting. Commit interval 5 seconds
* Jul 7 21:07:30 user.info kernel: EXT3 FS 2.4-0.9.19, 19 August 2002 on sd(8,17), internal journal
* Jul 7 21:07:30 user.info kernel: EXT3-fs: mounted filesystem with ordered data mode.
* Jul 7 21:09:43 auth.info login[3602]: root login on `pts/0'


Top
 Profile  
 
 Post subject:
PostPosted: Tue Jul 10, 2007 3:41 pm 
Offline
Site Admin

Joined: Tue Jul 13, 2004 4:11 pm
Posts: 1771
Location: Server Elements
Not all ACPI implementations are equal, so naturally some can provide complete details and others little or none. NASLite-2 retrieves the ACPI status info from the /proc so the kernel is responsible for exporting all the necessary details. If some details are missing then those are not supported by the ACPI implementation or the kernel is unable to articulate the particular ACPI implementation.

Hope that helps.


Top
 Profile  
 
 Post subject: Re:
PostPosted: Thu Mar 19, 2009 11:29 am 
Offline

Joined: Sun Mar 01, 2009 12:19 pm
Posts: 54
Tony wrote:
Not all ACPI implementations are equal, so naturally some can provide complete details and others little or none. NASLite-2 retrieves the ACPI status info from the /proc so the kernel is responsible for exporting all the necessary details. If some details are missing then those are not supported by the ACPI implementation or the kernel is unable to articulate the particular ACPI implementation.

Hope that helps.



Tony,
I know this is an old post, but is there a list of motherboard brands, models, types that "usually" work with NASLite ACPI? I know it's hard to make sure NASLite supports all ACPI versions but I would like to have the functionality working on my NASLite server.

Thank you.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 4 posts ] 

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 10 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group