LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 10-27-2011, 01:59 PM   #1
AuroraZero
Member
 
Registered: Oct 2009
Location: Michigan
Distribution: SlackWare 13.37, Android, Slax, Centos 5.9 Final, Centos 6
Posts: 187

Rep: Reputation: 31
Compiled kernels 3.0.4 and 3.0.8 both giving acpi errors


As the title says I compiled both kernels and both give the exact same error messages. I am beginning to think I did something wrong but I can not tell what. The normal Slackware 13.37 kernel does not give me errors. Here are the errors.

Code:
[   32.280695] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   38.108794] ACPI Exception: AE_AML_BUFFER_LIMIT, Index (0x0000000000000064) is beyond end of object (20110413/exoparg2-418)
[   38.108803] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SBRG.EC0_.STBR] (Node f4c37b28), AE_AML_BUFFER_LIMIT (20110413/psparse-536)
[   38.108811] ACPI Error: Method parse/execution failed [\_SB_.PCI0.VGA_.LCDD._BCM] (Node f4c33cd8), AE_AML_BUFFER_LIMIT (20110413/psparse-536)
[   38.108820] ACPI Error: Evaluating _BCM failed (20110413/video-365)
[   38.109653] ACPI Exception: AE_AML_BUFFER_LIMIT, Index (0x0000000000000064) is beyond end of object (20110413/exoparg2-418)
[   38.109661] ACPI Error: Method parse/execution failed [\_SB_.PCI0.SBRG.EC0_.STBR] (Node f4c37b28), AE_AML_BUFFER_LIMIT (20110413/psparse-536)
[   38.109669] ACPI Error: Method parse/execution failed [\_SB_.PCI0.VGA_.LCDD._BCM] (Node f4c33cd8), AE_AML_BUFFER_LIMIT (20110413/psparse-536)
[   38.109678] ACPI Error: Evaluating _BCM failed (20110413/video-365)
I have looked this up and they said it would be fixed before the 3.0 kernel. What I am wondering is if I did something what was it? How can I fix it? The machine runs fine but I do not like those errors.

The machine is an Asus K60IJ laptop. Call me anal if you want but if something is not right I want to fix it.
 
Click here to see the post LQ members have rated as the most helpful post in this thread.
Old 10-28-2011, 07:42 AM   #2
Cedrik
Senior Member
 
Registered: Jul 2004
Distribution: Slackware
Posts: 2,140

Rep: Reputation: 242Reputation: 242Reputation: 242
Maybe test various acpi boot options, like acpi_osi="<string>"

Where <string> is one of :
Code:
        "Windows 2000",         /* Windows 2000 */
        "Windows 2001",         /* Windows XP */
        "Windows 2001 SP1",     /* Windows XP SP1 */
        "Windows 2001 SP2",     /* Windows XP SP2 */
        "Windows 2001.1",       /* Windows Server 2003 */
        "Windows 2001.1 SP1",   /* Windows Server 2003 SP1 - Added 03/2006 */
        "Windows 2006",         /* Windows Vista - Added 03/2006 */
(from <kernel source>/drivers/acpi/utilities/uteval.c)

[edit]
Or add acpi_osi="!Windows 2009"
as seen here:
http://comments.gmane.org/gmane.linux.acpi.devel/46143

Last edited by Cedrik; 10-28-2011 at 07:44 AM.
 
Old 10-28-2011, 02:42 PM   #3
Martinus2u
Member
 
Registered: Apr 2010
Distribution: Slackware
Posts: 350

Rep: Reputation: 56
hmm, one of my machines is an Asus P50IJ laptop. Prompted by this posting I checked the syslog, and lo and behold I found the same ACPI errors. This is probably a regression since I don't recall it, but it has been present at least since April this year (start of syslog).

However, it seems not to bother the user of the laptop.
 
Old 10-28-2011, 07:37 PM   #4
AuroraZero
Member
 
Registered: Oct 2009
Location: Michigan
Distribution: SlackWare 13.37, Android, Slax, Centos 5.9 Final, Centos 6
Posts: 187

Original Poster
Rep: Reputation: 31
Quote:
Originally Posted by Martinus2u View Post
hmm, one of my machines is an Asus P50IJ laptop. Prompted by this posting I checked the syslog, and lo and behold I found the same ACPI errors. This is probably a regression since I don't recall it, but it has been present at least since April this year (start of syslog).

However, it seems not to bother the user of the laptop.
No the laptop seems to work just fine. Just seems odd that the stock Slack kernel works correctly and this one gives errors.

Cedrik this has nothing what so ever to do with windows. This happens booting Slackware 13.37. Thank you for the suggestions though.
 
Old 10-28-2011, 08:04 PM   #5
Cedrik
Senior Member
 
Registered: Jul 2004
Distribution: Slackware
Posts: 2,140

Rep: Reputation: 242Reputation: 242Reputation: 242
Smile

Quote:
Originally Posted by AuroraZero View Post

Cedrik this has nothing what so ever to do with windows. This happens booting Slackware 13.37. Thank you for the suggestions though.
I know
 
Old 10-29-2011, 02:22 PM   #6
tobyl
Member
 
Registered: Apr 2003
Location: uk
Distribution: slackware current
Posts: 743

Rep: Reputation: 51
AuroraZero,

Put simply, the part of the bios that deals with ACPI is known as a DSDT. Intel has defined an industry standard for this table and provides a compiler with which to generate it. The bootloader passes it to the OS at bootup.

Unfortunately many vendors (Asus, Samsung and Toshiba to name a few), use a Microsoft compiler to generate this table, as they only really care that the laptop works on Windows (where they think the money is). The Microsoft compiler is less strict than the Intel one, and allows a DSDT to be generated with incorrect checksums and all manner of errors.

These errors are picked up by the linux kernel at boot time and this is what you are seeing. The errors may or may not result in ACPI malfunctions, depending on the severity of the problem.

Different versions of windows have varying ACPI functionality (as do different linux kernels). When the computer boots, the bios queries what OS is running so it knows what ACPI functionality to provide (so long as its Windows). This is the reason Cedrik made his suggestion, as the linux bootloader has the facility to respond to the bios and tell it what we want it to hear. By telling it we are "Windows 2001 SP2" for example, we may get an ACPI config that conforms to the proper spec well enough that linux can interpret it and dim your backlight or speed up a fan as intended.

Some distros (Ubuntu in particular) hack the linux code to work around some of these failings. This sounds good, but it actually has a negative side, as it means that instead of fixing their broken ACPI implementation as they should, the hardware vendors sit back and let developers of other operating systems struggle to make things work. The end [Unix, linux, BSD etc] user loses out merely because the vendors are too lazy to write DSDT tables to the industry standard spec.

Sorry, got carried away there...

tobyl
 
2 members found this post helpful.
Old 10-29-2011, 04:18 PM   #7
AuroraZero
Member
 
Registered: Oct 2009
Location: Michigan
Distribution: SlackWare 13.37, Android, Slax, Centos 5.9 Final, Centos 6
Posts: 187

Original Poster
Rep: Reputation: 31
Quote:
Originally Posted by tobyl View Post
AuroraZero,

Put simply, the part of the bios that deals with ACPI is known as a DSDT. Intel has defined an industry standard for this table and provides a compiler with which to generate it. The bootloader passes it to the OS at bootup.

Unfortunately many vendors (Asus, Samsung and Toshiba to name a few), use a Microsoft compiler to generate this table, as they only really care that the laptop works on Windows (where they think the money is). The Microsoft compiler is less strict than the Intel one, and allows a DSDT to be generated with incorrect checksums and all manner of errors.

These errors are picked up by the linux kernel at boot time and this is what you are seeing. The errors may or may not result in ACPI malfunctions, depending on the severity of the problem.

Different versions of windows have varying ACPI functionality (as do different linux kernels). When the computer boots, the bios queries what OS is running so it knows what ACPI functionality to provide (so long as its Windows). This is the reason Cedrik made his suggestion, as the linux bootloader has the facility to respond to the bios and tell it what we want it to hear. By telling it we are "Windows 2001 SP2" for example, we may get an ACPI config that conforms to the proper spec well enough that linux can interpret it and dim your backlight or speed up a fan as intended.

Some distros (Ubuntu in particular) hack the linux code to work around some of these failings. This sounds good, but it actually has a negative side, as it means that instead of fixing their broken ACPI implementation as they should, the hardware vendors sit back and let developers of other operating systems struggle to make things work. The end [Unix, linux, BSD etc] user loses out merely because the vendors are too lazy to write DSDT tables to the industry standard spec.

Sorry, got carried away there...

tobyl
No need to be sorry as it explained what he was saying and why he said it. It makes sense to me now and I am glad you decided to post. Can I append the lilo.conf file to include the line acpi_osi="!Windows 2009" or do I have to pass this through the lilo prompt? If I am way off base and have to do something someplace else let me know. I chose that one because the computer originally had winblows 7 on it.
 
Old 10-29-2011, 06:44 PM   #8
tobyl
Member
 
Registered: Apr 2003
Location: uk
Distribution: slackware current
Posts: 743

Rep: Reputation: 51
Hi AuroraZero

I first learned a bit about this while trying to fix ACPI problems on a netbook I bought. I tried all sorts of stuff, including recompiling the DSDT with the Intel compiler. (there is a kernel config setting that allows you to override the DSDT and insert your own).

It gets quite complicated, and I had some but limited success.

My advice is, if it works, put up with those irritating error messages, and don't waste your valuable time on it.

I believe the kernel prompt syntax is

"acpi_osi=\"!Windows 2009\"

In lilo, I think it would require an append= statement, but my memory is a bit hazy. Suggest you do some googling! If you get stuck I will have a look too.

tobyl
 
1 members found this post helpful.
Old 10-29-2011, 08:08 PM   #9
AuroraZero
Member
 
Registered: Oct 2009
Location: Michigan
Distribution: SlackWare 13.37, Android, Slax, Centos 5.9 Final, Centos 6
Posts: 187

Original Poster
Rep: Reputation: 31
Thank you for your help tobyl but check this here is my dmesg of my last boot.
Code:
[    0.383719] pci 0000:03:00.0: calling pci_fixup_video+0x0/0x96
[    0.383724] PCI: CLS 32 bytes, default 64
[    0.383811] kvm: no hardware support
[    0.383817] has_svm: not amd
[    0.383819] kvm: no hardware support
[    0.383827] Simple Boot Flag at 0x51 set to 0x1
[    0.384541] scx200: NatSemi SCx200 Driver
[    0.384856] audit: initializing netlink socket (disabled)
[    0.384869] type=2000 audit(1319911893.383:1): initialized
[    0.390275] highmem bounce pool size: 64 pages
[    0.394338] VFS: Disk quotas dquot_6.5.2
[    0.394463] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.394810] DLM installed
[    0.396351] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    0.396525] NTFS driver 2.1.30 [Flags: R/W].
[    0.396690] ROMFS MTD (C) 2007 Red Hat, Inc.
[    0.396955] JFS: nTxBlock = 8192, nTxLock = 65536
[    0.399618] SGI XFS with ACLs, security attributes, large block/inode numbers, no debug enabled
[    0.400386] SGI XFS Quota Management subsystem
[    0.400396] OCFS2 1.5.0
[    0.400588] ocfs2: Registered cluster interface o2cb
[    0.400673] ocfs2: Registered cluster interface user
[    0.400678] OCFS2 DLMFS 1.5.0
[    0.400793] OCFS2 User DLM kernel interface loaded
[    0.400797] OCFS2 Node Manager 1.5.0
[    0.400908] OCFS2 DLM 1.5.0
[    0.401386] Btrfs loaded
[    0.401843] GFS2 installed
[    0.401857] msgmni has been set to 1670
[    0.403342] async_tx: api initialized (async)
[    0.403415] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
[    0.403452] io scheduler noop registered
[    0.403456] io scheduler deadline registered
[    0.403481] io scheduler cfq registered (default)
[    0.403620] pcieport 0000:00:1c.0: setting latency timer to 64
[    0.403681] pcieport 0000:00:1c.0: irq 40 for MSI/MSI-X
[    0.403847] pcieport 0000:00:1c.1: setting latency timer to 64
[    0.403902] pcieport 0000:00:1c.1: irq 41 for MSI/MSI-X
[    0.404105] pcieport 0000:00:1c.5: setting latency timer to 64
[    0.404161] pcieport 0000:00:1c.5: irq 42 for MSI/MSI-X
[    0.404524] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
[    0.404534] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
[    0.404556] pcieport 0000:00:1c.1: Signaling PME through PCIe PME interrupt
[    0.404561] pci 0000:02:00.0: Signaling PME through PCIe PME interrupt
[    0.404569] pcie_pme 0000:00:1c.1:pcie01: service driver pcie_pme loaded
[    0.404591] pcieport 0000:00:1c.5: Signaling PME through PCIe PME interrupt
[    0.404595] pci 0000:03:00.0: Signaling PME through PCIe PME interrupt
[    0.404603] pcie_pme 0000:00:1c.5:pcie01: service driver pcie_pme loaded
[    0.404686] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[    0.404805] pciehp 0000:00:1c.5:pcie04: HPC vendor_id 8086 device_id 294a ss_vid 8086 ss_did 294a
[    0.404817] pci_bus 0000:03: dev 00, created physical slot 0
[    0.404869] pciehp 0000:00:1c.5:pcie04: service driver pciehp loaded
[    0.404910] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[    0.405098] vesafb: mode is 1024x768x8, linelength=1024, pages=41
[    0.405103] vesafb: scrolling: redraw
[    0.405107] vesafb: Pseudocolor: size=8:8:8:8, shift=0:0:0:0
[    0.405267] vesafb: framebuffer at 0xd0000000, mapped to 0xf8500000, using 1536k, total 32704k
[    0.405340] fbcon: VESA VGA (fb0) is primary device
[    0.411897] Console: switching to colour frame buffer device 128x48
[    0.419746] fb0: VESA VGA frame buffer device
[    0.419843] intel_idle: MWAIT substates: 0x2220
[    0.419845] intel_idle: does not run on family 6 model 23
[    0.419850] ERST: Table is not found!
[    0.423491] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    1.384127] Refined TSC clocksource calibration: 2194.499 MHz.
[    1.384202] Switching to clocksource tsc
[    3.472024] floppy0: no floppy controllers found
[    3.595209] brd: module loaded
[    3.596256] loop: module loaded
[    3.596297] Compaq SMART2 Driver (v 2.6.0)
[    3.596424] HP CISS Driver (v 3.6.26)
[    3.596788] Driver for timberdale has been successfully registered.
[    3.597335] Loading iSCSI transport class v2.0-870.
[    3.597803] fnic: Cisco FCoE HBA Driver, ver 1.5.0.1
[    3.598306] Adaptec aacraid driver 1.1-7[28000]-ms
[    3.598627] aic94xx: Adaptec aic94xx SAS/SATA driver version 1.0.3 loaded
[    3.598935] scsi: <fdomain> Detection failed (no card)
[    3.599075] QLogic Fibre Channel HBA Driver: 8.03.07.03-k
[    3.599228] iscsi: registered transport (qla4xxx)
[    3.601630] QLogic iSCSI HBA Driver
[    3.603841] Emulex LightPulse Fibre Channel SCSI driver 8.3.23
[    3.606089] Copyright(c) 2004-2009 Emulex.  All rights reserved.
[    3.608403] Brocade BFA FC/FCOE SCSI driver - version: 2.3.2.3
[    3.610844] DC390: clustering now enabled by default. If you get problems load
[    3.613117]        with "disable_clustering=1" and report to maintainers
[    3.615494] megaraid cmm: 2.20.2.7 (Release Date: Sun Jul 16 00:01:03 EST 2006)
[    3.617909] megaraid: 2.20.5.1 (Release Date: Thu Nov 16 15:32:35 EST 2006)
[    3.620355] megasas: 00.00.05.38-rc1 Wed. May. 11 17:00:00 PDT 2011
[    3.622768] mpt2sas version 08.100.00.02 loaded
[    3.625285] GDT-HA: Storage RAID Controller Driver. Version: 3.05
[    3.627804] 3ware Storage Controller device driver for Linux v1.26.02.003.
[    3.630286] 3ware 9000 Storage Controller device driver for Linux v2.26.02.014.
[    3.632767] LSI 3ware SAS/SATA-RAID Controller device driver for Linux v3.26.02.000.
[    3.635273] ipr: IBM Power RAID SCSI Device Driver version: 2.5.2 (April 27, 2011)
[    3.637790] RocketRAID 3xxx/4xxx Controller driver v1.6 (090910)
[    3.640295] stex: Promise SuperTrak EX Driver version: 4.6.0000.4
[    3.642909] st: Version 20101219, fixed bufsize 32768, s/g segs 256
[    3.645530] ahci 0000:00:1f.2: version 3.0
[    3.645548] ahci 0000:00:1f.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19
[    3.648061] ahci 0000:00:1f.2: irq 43 for MSI/MSI-X
[    3.648105] ahci: SSS flag set, parallel bus scan disabled
[    3.650613] ahci 0000:00:1f.2: AHCI 0001.0200 32 slots 4 ports 3 Gbps 0x3 impl SATA mode
[    3.653124] ahci 0000:00:1f.2: flags: 64bit ncq sntf stag pm led clo pio slum part ccc ems sxs 
[    3.655634] ahci 0000:00:1f.2: setting latency timer to 64
[    3.657662] scsi0 : ahci
[    3.660295] scsi1 : ahci
[    3.662847] scsi2 : ahci
[    3.665324] scsi3 : ahci
[    3.667933] ata1: SATA max UDMA/133 abar m2048@0xfe9fb000 port 0xfe9fb100 irq 43
[    3.670338] ata2: SATA max UDMA/133 abar m2048@0xfe9fb000 port 0xfe9fb180 irq 43
[    3.672685] ata3: DUMMY
[    3.674983] ata4: DUMMY
[    3.679987] scsi4 : pata_legacy
[    3.682346] ata5: PATA max PIO4 cmd 0x1f0 ctl 0x3f6 irq 14
[    3.982021] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    3.985908] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[    3.988591] ata1.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
[    3.988595] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[    3.992641] ata1.00: ATA-8: ST9500325AS, 0002SDM1, max UDMA/133
[    3.994985] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
[    3.999283] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
[    4.001992] ata1.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
[    4.001995] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[    4.006072] ata1.00: configured for UDMA/133
[    4.008551] scsi 0:0:0:0: Direct-Access     ATA      ST9500325AS      0002 PQ: 0 ANSI: 5
[    4.011191] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)
[    4.013661] sd 0:0:0:0: [sda] Write Protect is off
[    4.016068] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    4.016093] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    4.087285]  sda: sda1 sda2 sda3 < sda5 sda6 >
[    4.090189] sd 0:0:0:0: [sda] Attached SCSI disk
[    4.318022] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    4.327376] ata2.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
[    4.327380] ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[    4.331468] ata2.00: ATAPI: Optiarc DVD RW AD-7700S, 1.03, max UDMA/100
[    4.345643] ata2.00: ACPI cmd ef/10:06:00:00:00:a0 (SET FEATURES) succeeded
[    4.345646] ata2.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
[    4.349729] ata2.00: configured for UDMA/100
[    4.367997] scsi 1:0:0:0: CD-ROM            Optiarc  DVD RW AD-7700S  1.03 PQ: 0 ANSI: 5
[    4.387066] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
[    4.389530] cdrom: Uniform CD-ROM driver Revision: 3.20
[    4.392132] sr 1:0:0:0: Attached scsi CD-ROM sr0
[    4.392877] scsi5 : pata_legacy
[    4.395371] ata6: PATA max PIO4 cmd 0x170 ctl 0x376 irq 15
[    4.548401] airo(): Probing for PCI adapters
[    4.550824] airo(): Finished probing for PCI adapters
[    4.553174] I2O subsystem v1.325
[    4.555474] i2o: max drivers = 8
[    4.557863] I2O Configuration OSM v1.323
[    4.560139] I2O Bus Adapter OSM v1.317
[    4.562385] I2O Block Device OSM v1.325
[    4.564707] I2O SCSI Peripheral OSM v1.316
[    4.566879] I2O ProcFS OSM v1.316
[    4.569006] Fusion MPT base driver 3.04.19
[    4.571133] Copyright (c) 1999-2008 LSI Corporation
[    4.573304] Fusion MPT SPI Host driver 3.04.19
[    4.575553] Fusion MPT FC Host driver 3.04.19
[    4.577767] Fusion MPT SAS Host driver 3.04.19
[    4.580005] Fusion MPT misc device (ioctl) driver 3.04.19
[    4.582249] mptctl: Registered with Fusion MPT base driver
[    4.584470] mptctl: /dev/mptctl @ (major,minor=10,220)
[    4.586705] Fusion MPT LAN driver 3.04.19
[    4.589104] usbcore: registered new interface driver hwa-rc
[    4.591465] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    4.593741] ehci_hcd 0000:00:1a.7: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[    4.596029] ehci_hcd 0000:00:1a.7: setting latency timer to 64
[    4.596033] ehci_hcd 0000:00:1a.7: EHCI Host Controller
[    4.598351] ehci_hcd 0000:00:1a.7: new USB bus registered, assigned bus number 1
[    4.600632] ehci_hcd 0000:00:1a.7: debug port 1
[    4.606712] ehci_hcd 0000:00:1a.7: cache line size of 32 is not supported
[    4.606735] ehci_hcd 0000:00:1a.7: irq 18, io mem 0xfe9fbc00
[    4.618006] ehci_hcd 0000:00:1a.7: USB 2.0 started, EHCI 1.00
[    4.620206] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    4.622391] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.624552] usb usb1: Product: EHCI Host Controller
[    4.626693] usb usb1: Manufacturer: Linux 3.0.8-smp ehci_hcd
[    4.628823] usb usb1: SerialNumber: 0000:00:1a.7
[    4.631047] hub 1-0:1.0: USB hub found
[    4.633117] hub 1-0:1.0: 6 ports detected
[    4.635273] ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23
[    4.637350] ehci_hcd 0000:00:1d.7: setting latency timer to 64
[    4.637354] ehci_hcd 0000:00:1d.7: EHCI Host Controller
[    4.639441] ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 2
[    4.641504] ehci_hcd 0000:00:1d.7: debug port 1
[    4.647364] ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
[    4.647380] ehci_hcd 0000:00:1d.7: irq 23, io mem 0xfe9fb800
[    4.659006] ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00
[    4.660933] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[    4.662857] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.664785] usb usb2: Product: EHCI Host Controller
[    4.666698] usb usb2: Manufacturer: Linux 3.0.8-smp ehci_hcd
[    4.668614] usb usb2: SerialNumber: 0000:00:1d.7
[    4.670658] hub 2-0:1.0: USB hub found
[    4.672559] hub 2-0:1.0: 6 ports detected
[    4.674624] 116x: driver isp116x-hcd, 03 Nov 2005
[    4.676568] driver isp1362-hcd, 2005-04-04
[    4.678513] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    4.680534] uhci_hcd: USB Universal Host Controller Interface driver
[    4.682568] uhci_hcd 0000:00:1a.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    4.684598] uhci_hcd 0000:00:1a.0: setting latency timer to 64
[    4.684602] uhci_hcd 0000:00:1a.0: UHCI Host Controller
[    4.686680] uhci_hcd 0000:00:1a.0: new USB bus registered, assigned bus number 3
[    4.688765] uhci_hcd 0000:00:1a.0: irq 16, io base 0x0000d880
[    4.690816] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
[    4.692882] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.694967] usb usb3: Product: UHCI Host Controller
[    4.697045] usb usb3: Manufacturer: Linux 3.0.8-smp uhci_hcd
[    4.699123] usb usb3: SerialNumber: 0000:00:1a.0
[    4.701323] hub 3-0:1.0: USB hub found
[    4.703383] hub 3-0:1.0: 2 ports detected
[    4.705520] uhci_hcd 0000:00:1a.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21
[    4.707591] uhci_hcd 0000:00:1a.1: setting latency timer to 64
[    4.707595] uhci_hcd 0000:00:1a.1: UHCI Host Controller
[    4.709674] uhci_hcd 0000:00:1a.1: new USB bus registered, assigned bus number 4
[    4.711763] uhci_hcd 0000:00:1a.1: irq 21, io base 0x0000d800
[    4.713819] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
[    4.715875] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.717950] usb usb4: Product: UHCI Host Controller
[    4.720029] usb usb4: Manufacturer: Linux 3.0.8-smp uhci_hcd
[    4.722093] usb usb4: SerialNumber: 0000:00:1a.1
[    4.724284] hub 4-0:1.0: USB hub found
[    4.726313] hub 4-0:1.0: 2 ports detected
[    4.728422] uhci_hcd 0000:00:1a.2: PCI INT D -> GSI 19 (level, low) -> IRQ 19
[    4.730489] uhci_hcd 0000:00:1a.2: setting latency timer to 64
[    4.730493] uhci_hcd 0000:00:1a.2: UHCI Host Controller
[    4.732597] uhci_hcd 0000:00:1a.2: new USB bus registered, assigned bus number 5
[    4.734732] uhci_hcd 0000:00:1a.2: irq 19, io base 0x0000d480
[    4.736838] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
[    4.738927] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.741018] usb usb5: Product: UHCI Host Controller
[    4.743102] usb usb5: Manufacturer: Linux 3.0.8-smp uhci_hcd
[    4.745202] usb usb5: SerialNumber: 0000:00:1a.2
[    4.747445] hub 5-0:1.0: USB hub found
[    4.749517] hub 5-0:1.0: 2 ports detected
[    4.751667] uhci_hcd 0000:00:1d.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
[    4.753752] uhci_hcd 0000:00:1d.0: setting latency timer to 64
[    4.753756] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[    4.755877] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 6
[    4.757994] uhci_hcd 0000:00:1d.0: irq 23, io base 0x0000d400
[    4.760109] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001
[    4.762242] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.764385] usb usb6: Product: UHCI Host Controller
[    4.766519] usb usb6: Manufacturer: Linux 3.0.8-smp uhci_hcd
[    4.768646] usb usb6: SerialNumber: 0000:00:1d.0
[    4.770894] hub 6-0:1.0: USB hub found
[    4.772986] hub 6-0:1.0: 2 ports detected
[    4.775177] uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
[    4.777299] uhci_hcd 0000:00:1d.1: setting latency timer to 64
[    4.777303] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[    4.779452] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 7
[    4.781581] uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000d080
[    4.783687] usb usb7: New USB device found, idVendor=1d6b, idProduct=0001
[    4.785780] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.787878] usb usb7: Product: UHCI Host Controller
[    4.789971] usb usb7: Manufacturer: Linux 3.0.8-smp uhci_hcd
[    4.792073] usb usb7: SerialNumber: 0000:00:1d.1
[    4.794322] hub 7-0:1.0: USB hub found
[    4.796420] hub 7-0:1.0: 2 ports detected
[    4.798590] uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[    4.800711] uhci_hcd 0000:00:1d.2: setting latency timer to 64
[    4.800715] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[    4.802863] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 8
[    4.804993] uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000d000
[    4.807119] usb usb8: New USB device found, idVendor=1d6b, idProduct=0001
[    4.809211] usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.811309] usb usb8: Product: UHCI Host Controller
[    4.813407] usb usb8: Manufacturer: Linux 3.0.8-smp uhci_hcd
[    4.815514] usb usb8: SerialNumber: 0000:00:1d.2
[    4.817769] hub 8-0:1.0: USB hub found
[    4.819855] hub 8-0:1.0: 2 ports detected
[    4.822116] sl811: driver sl811-hcd, 19 May 2005
[    4.824217] r8a66597_hcd: driver r8a66597_hcd, 2009-05-26
[    4.826474] usbcore: registered new interface driver hwa-hc
[    4.828657] usbcore: registered new interface driver wusb-cbaf
[    4.830754] usbcore: registered new interface driver cdc_acm
[    4.832743] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[    4.834831] usbcore: registered new interface driver usblp
[    4.836928] usbcore: registered new interface driver cdc_wdm
[    4.839000] usbcore: registered new interface driver usbtmc
[    4.841058] usbcore: registered new interface driver uas
[    4.843092] usbcore: registered new interface driver libusual
[    4.845075] usbcore: registered new interface driver mdc800
[    4.846984] mdc800: v0.7.5 (30/10/2000):USB Driver for Mustek MDC800 Digital Camera
[    4.848980] usbcore: registered new interface driver microtekX6
[    4.851007] usbcore: registered new interface driver usbserial
[    4.852956] USB Serial support registered for generic
[    4.938018] usb 1-3: new high speed USB device number 2 using ehci_hcd
[    5.076598] usb 1-3: New USB device found, idVendor=13d3, idProduct=5094
[    5.078555] usb 1-3: New USB device strings: Mfr=1, Product=3, SerialNumber=0
[    5.080516] usb 1-3: Product: USB2.0 UVC VGA WebCam
[    5.082492] usb 1-3: Manufacturer: PixArt Imaging Inc.
[    5.091078] usbcore: registered new interface driver usbserial_generic
[    5.093072] usbserial: USB Serial Driver core
[    5.095086] usbcore: registered new interface driver adutux
[    5.097072] adutux adutux (see www.ontrak.net) v0.0.13
[    5.099031] adutux is an experimental driver. Use at your own risk
[    5.101043] usbcore: registered new interface driver cypress_cy7c63
[    5.103062] usbcore: registered new interface driver cytherm
[    5.105011] cytherm: v1.0:Cypress USB Thermometer driver
[    5.106999] usbcore: registered new interface driver emi26 - firmware loader
[    5.109036] usbcore: registered new interface driver emi62 - firmware loader
[    5.111020] driver ftdi-elan
[    5.113042] usbcore: registered new interface driver ftdi-elan
[    5.115021] idmouse: 0.6:Siemens ID Mouse FingerTIP Sensor Driver
[    5.117042] usbcore: registered new interface driver idmouse
[    5.119070] usbcore: registered new interface driver iowarrior
[    5.121049] usbcore: registered new interface driver isight_firmware
[    5.123011] usbcore: registered new interface driver usblcd
[    5.124922] usbcore: registered new interface driver ldusb
[    5.126799] usbcore: registered new interface driver usbled
[    5.128652] usbcore: registered new interface driver legousbtower
[    5.130449] legousbtower: v0.96:LEGO USB Tower Driver
[    5.132309] usbcore: registered new interface driver rio500
[    5.134144] rio500: v1.1:USB Rio 500 driver
[    5.136005] usbcore: registered new interface driver trancevibrator
[    5.137855] trancevibrator: v1.1:PlayStation 2 Trance Vibrator driver
[    5.139793] usbcore: registered new interface driver usbsevseg
[    5.141783] usbcore: registered new interface driver yurex
[    5.143895] usbcore: registered new interface driver sisusb
[    5.145886] i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12
[    5.151342] i8042: Detected active multiplexing controller, rev 1.1
[    5.155747] serio: i8042 KBD port at 0x60,0x64 irq 1
[    5.157733] serio: i8042 AUX0 port at 0x60,0x64 irq 12
[    5.159752] serio: i8042 AUX1 port at 0x60,0x64 irq 12
[    5.161770] serio: i8042 AUX2 port at 0x60,0x64 irq 12
[    5.163725] serio: i8042 AUX3 port at 0x60,0x64 irq 12
[    5.165777] mousedev: PS/2 mouse device common for all mice
[    5.167732] Linux telephony interface: v1.00
[    5.169614] md: linear personality registered for level -1
[    5.171488] md: raid0 personality registered for level 0
[    5.173357] md: raid1 personality registered for level 1
[    5.175187] md: raid10 personality registered for level 10
[    5.177003] md: raid6 personality registered for level 6
[    5.178821] md: raid5 personality registered for level 5
[    5.180589] md: raid4 personality registered for level 4
[    5.182313] md: multipath personality registered for level -4
[    5.184240] device-mapper: uevent: version 1.0.3
[    5.186109] device-mapper: ioctl: 4.20.0-ioctl (2011-02-02) initialised: dm-devel@redhat.com
[    5.188031] lguest: mapped switcher at ffc00000
[    5.189857] cpuidle: using governor ladder
[    5.191635] cpuidle: using governor menu
[    5.193459] EFI Variables Facility v0.08 2004-May-17
[    5.195331] dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2)
[    5.197159] No iBFT detected.
[    5.199437] usbcore: registered new interface driver usbhid
[    5.201256] usbhid: USB HID core driver
[    5.203108] input: Speakup as /devices/virtual/input/input0
[    5.205029] initialized device: /dev/synth, node (MAJOR 10, MINOR 25)
[    5.206936] speakup 3.1.6: initialized
[    5.208814] synth name on entry is: (null)
[    5.210786] TCP cubic registered
[    5.212688] Initializing XFRM netlink socket
[    5.214641] NET: Registered protocol family 17
[    5.216614] lib80211: common routines for IEEE802.11 drivers
[    5.218592] lib80211_crypt: registered algorithm 'NULL'
[    5.218594] Registering the dns_resolver key type
[    5.220563] Using IPI No-Shortcut mode
[    5.225615] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
[    5.410008] usb 6-1: new full speed USB device number 2 using uhci_hcd
[    5.447802] registered taskstats version 1
[    5.450170] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[    5.452225] EDD information not available.
[    5.454382] md: Waiting for all devices to be available before autodetect
[    5.456469] md: If you don't use raid, use raid=noautodetect
[    5.458719] md: Autodetecting RAID arrays.
[    5.460754] md: Scanned 0 and added 0 devices.
[    5.462787] md: autorun ...
[    5.464827] md: ... autorun DONE.
[    5.562054] VFS: Mounted root (ext2 filesystem) readonly on device 8:5.
[    5.581111] usb 6-1: New USB device found, idVendor=046d, idProduct=c52f
[    5.583281] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    5.585453] usb 6-1: Product: USB Receiver
[    5.587594] usb 6-1: Manufacturer: Logitech
[    5.591692] devtmpfs: mounted
[    5.593868] Freeing unused kernel memory: 616k freed
[    5.596291] Write protecting the kernel text: 10976k
[    5.598535] Write protecting the kernel read-only data: 2844k
[    5.631641] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1:1.0/input/input2
[    5.634130] generic-usb 0003:046D:C52F.0001: input,hidraw0: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-0000:00:1d.0-1/input0
[    5.644235] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1:1.1/input/input3
[    5.646927] generic-usb 0003:046D:C52F.0002: input,hiddev0,hidraw1: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:1d.0-1/input1
[    7.090216] udev[1592]: starting version 165
[    7.423886] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
[    7.426616] ACPI: AC Adapter [AC0] (on-line)
[    7.435087] thermal LNXTHERM:00: registered as thermal_zone0
[    7.437707] ACPI: Thermal Zone [THRM] (58 C)
[    7.565599] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    7.568324] sr 1:0:0:0: Attached scsi generic sg1 type 5
[    7.581058] input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input4
[    7.583755] ACPI: Sleep Button [SLPB]
[    7.584241] ACPI: acpi_idle registered with cpuidle
[    7.587019] input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input5
[    7.589945] Monitor-Mwait will be used to enter C-1 state
[    7.589990] Monitor-Mwait will be used to enter C-2 state
[    7.590023] Monitor-Mwait will be used to enter C-3 state
[    7.590027] Marking TSC unstable due to TSC halts in idle
[    7.593799] Switching to clocksource hpet
[    7.597592] ACPI: Lid Switch [LID]
[    7.600315] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input6
[    7.603132] ACPI: Power Button [PWRF]
[    7.696824] ACPI: Deprecated procfs I/F for battery is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
[    7.699603] ACPI: Battery Slot [BAT0] (battery present)
[    7.777396] cfg80211: Calling CRDA to update world regulatory domain
[    7.839451] ATL1E 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[    7.842591] ATL1E 0000:03:00.0: setting latency timer to 64
[    7.937074] Linux video capture interface: v2.00
[    7.995973] Linux agpgart interface v0.103
[    8.089342] uvcvideo: Found UVC 1.00 device USB2.0 UVC VGA WebCam (13d3:5094)
[    8.101775] input: USB2.0 UVC VGA WebCam as /devices/pci0000:00/0000:00:1a.7/usb1/1-3/1-3:1.0/input/input7
[    8.104799] usbcore: registered new interface driver uvcvideo
[    8.107748] USB Video Class driver (v1.1.0)
[    8.215493] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[    8.218534] HDA Intel 0000:00:1b.0: irq 44 for MSI/MSI-X
[    8.218567] HDA Intel 0000:00:1b.0: setting latency timer to 64
[    8.407702] asus_laptop: Asus Laptop Support version 0.42
[    8.410818] asus_laptop:   K60IJ model detected
[    8.414198] asus_laptop: Backlight controlled by ACPI video driver
[    8.417262] input: Asus Laptop extra buttons as /devices/platform/asus_laptop/input/input8
[    8.886922] agpgart-intel 0000:00:00.0: Intel GM45 Chipset
[    8.890072] agpgart-intel 0000:00:00.0: detected gtt size: 2097152K total, 262144K mappable
[    8.893665] agpgart-intel 0000:00:00.0: detected 32768K stolen memory
[    8.896936] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xd0000000
[    8.927827] ath9k 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[    8.930766] ath9k 0000:02:00.0: setting latency timer to 64
[    8.980809] ath: EEPROM regdomain: 0x60
[    8.980812] ath: EEPROM indicates we should expect a direct regpair map
[    8.980815] ath: Country alpha2 being used: 00
[    8.980817] ath: Regpair used: 0x60
[    8.982313] ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control'
[    8.982494] Registered led device: ath9k-phy0
[    8.982499] ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xf8740000, irq=17
[    9.292851] [drm] Initialized drm 1.1.0 20060810
[    9.442743] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    9.445515] i915 0000:00:02.0: setting latency timer to 64
[    9.457976] mtrr: type mismatch for d0000000,10000000 old: write-back new: write-combining
[    9.460798] [drm] MTRR allocation failed.  Graphics performance may suffer.
[    9.463930] i915 0000:00:02.0: irq 45 for MSI/MSI-X
[    9.463937] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[    9.466824] [drm] Driver supports precise vblank timestamp query.
[    9.469750] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[    9.831453] cfg80211: World regulatory domain updated:
[    9.835280] cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[    9.839147] cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[    9.843028] cfg80211:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[    9.846839] cfg80211:     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[    9.850637] cfg80211:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[    9.854398] cfg80211:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[    9.977950] checking generic (d0000000 1ff0000) vs hw (d0000000 10000000)
[    9.977954] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver
[    9.980799] Console: switching to colour dummy device 80x25
[    9.981040] fbcon: inteldrmfb (fb0) is primary device
[   10.016584] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state
[   10.016587] Console: switching to colour frame buffer device 170x48
[   10.017579] render error detected, EIR: 0x00000010
[   10.017579]   IPEIR: 0x00000000
[   10.017579]   IPEHR: 0x00000000
[   10.017579]   INSTDONE: 0xfffffffe
[   10.017579]   INSTPS: 0x00000000
[   10.017579]   INSTDONE1: 0xffffffff
[   10.017579]   ACTHD: 0x00000000
[   10.017579] page table error
[   10.017579]   PGTBL_ER: 0x00000001
[   10.017579] [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking
[   10.051282] fb0: inteldrmfb frame buffer device
[   10.051488] drm: registered panic notifier
[   10.055056] acpi device:38: registered as cooling_device2
[   10.055421] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input9
[   10.055982] ACPI: Video Device [VGA] (multi-head: yes  rom: no  post: no)
Now the odd thing is those errors seem to have disappeared. I do not know how they would have but they no longer show up. I did notice the intel dri error but that seems to be a different animal entirely. I don't get it did the system finally learn? Is that even possible in today's technology?
 
Old 10-30-2011, 07:27 AM   #10
Martinus2u
Member
 
Registered: Apr 2010
Distribution: Slackware
Posts: 350

Rep: Reputation: 56
Quote:
Originally Posted by tobyl View Post
"acpi_osi=\"!Windows 2009\"
I've appended that statement. It was successful in so far as I now get different ACPI errors in the syslog.
 
Old 10-30-2011, 04:03 PM   #11
AuroraZero
Member
 
Registered: Oct 2009
Location: Michigan
Distribution: SlackWare 13.37, Android, Slax, Centos 5.9 Final, Centos 6
Posts: 187

Original Poster
Rep: Reputation: 31
Quote:
Originally Posted by Martinus2u View Post
I've appended that statement. It was successful in so far as I now get different ACPI errors in the syslog.
When I typed lilo after appending the statement it would not even take it. Kept giving me an error. I do not know what happend but the error is gone. Do not ask me why or how because I have no idea what so ever lol.
 
  


Reply

Tags
acpi error, bios, kernel, kernel compile


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
insmod modules that compiled in different kernels receive an error... halloworld Linux - Embedded & Single-board computer 2 04-09-2009 07:35 AM
Linux ACPI and BIOS ACPI - problem to understand and giving out bugs marisdembovskis Linux - Software 3 09-20-2007 11:22 PM
eth0 device ok in 2.6, dead in 2.4 (on same machine, both kernels compiled) henryhlc Linux - Networking 2 01-26-2006 01:28 PM
kernel-headers and custom compiled kernels jaakkop Slackware 2 11-22-2005 12:21 PM
DHCP not pulling IP on later 2.4 self compiled kernels php Slackware 1 05-15-2005 05:21 PM


All times are GMT -5. The time now is 06:50 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration