On Sunday 27 January 2008 08:07, Graham Adams wrote:
> On 1/23/08, Graham Adams <[EMAIL PROTECTED]> wrote:
> > On 1/23/08, Len Brown <[EMAIL PROTECTED]> wrote:
> > > On Tuesday 22 January 2008 12:56, you wrote:
> > > > On 1/22/08, Len Brown <[EMAIL PROTECTED]> wrote:
> > > > > On Monday 21 January
printk(KERN_WARNING PREFIX
- "If \"acpi_osi=Linux\" works better,\n"
- "Please send dmidecode "
- "to [EMAIL PROTECTED]");
+ if (acpi_dmi_dump())
+ printk(KERN_NOTICE PRE
On Tuesday 22 January 2008 12:56, you wrote:
> On 1/22/08, Len Brown <[EMAIL PROTECTED]> wrote:
> > On Monday 21 January 2008 12:28, Graham Adams wrote:
> > > On 1/19/08, Len Brown <[EMAIL PROTECTED]> wrote:
> > > >
> > > > > Please find attached the output of dmidecode after booting with
> > > > >
On Tuesday 22 January 2008 10:29, Theodore Tso wrote:
> On Mon, Jan 21, 2008 at 06:22:42PM -0500, Len Brown wrote:
> > > The one thing I worry about is if you aren't including the BIOS
> > > version in the DMI list, you could end up in a situation where one
> > > version of the BIOS treats OSI(Linu
On Mon, Jan 21, 2008 at 06:22:42PM -0500, Len Brown wrote:
> > The one thing I worry about is if you aren't including the BIOS
> > version in the DMI list, you could end up in a situation where one
> > version of the BIOS treats OSI(Linux) as a no-op, but a newer or an
> > older version of the BIOS
On Monday 21 January 2008 12:28, Graham Adams wrote:
> On 1/19/08, Len Brown <[EMAIL PROTECTED]> wrote:
> >
> > > Please find attached the output of dmidecode after booting with
> > > acpi_osi=!Linux as requested in dmesg output. The system seems to be
> > > working OK apart from problems with STA
On Monday 21 January 2008 02:51, Theodore Tso wrote:
> On Sun, Jan 20, 2008 at 02:08:40PM -0500, Len Brown wrote:
> >
> > OSI(Linux) has no effect on the AML of this machine,
> > as OSYS is over-written. So I'll just kill the warning
> > on this box by adding it to the NOP DMI list.
>
> The one
On Sun, Jan 20, 2008 at 02:08:40PM -0500, Len Brown wrote:
>
> OSI(Linux) has no effect on the AML of this machine,
> as OSYS is over-written. So I'll just kill the warning
> on this box by adding it to the NOP DMI list.
The one thing I worry about is if you aren't including the BIOS
version in
On Saturday 19 January 2008 15:24, Christer Edwards wrote:
> On Jan 18, 2008 7:25 PM, Len Brown <[EMAIL PROTECTED]> wrote:
> > Thanks for the dmidecode output.
> >
> > Do you notice any functional difference when booting with
> >
> > "acpi_osi=Linux&quo
On Saturday 19 January 2008 09:55, Henk Koster wrote:
> On Friday 18 January 2008 22:48:00 you wrote:
> > Manufacturer: Apple Computer, Inc.
> > Product Name: MacBook1,1
> >
> > With 2.6.22, did you notice any functional difference with
> > "acpi_osi=!Linux"?
>
> No difference
>
> > (or s
which applies to git
> kernel. so, running latest acpi code, dmesg still complains about
> acpi_osi but it gives more output:
> ACPI: _OSI(Linux) requested by unknown system BIOS
> 1. FUJITSU SIEMENS
> 3. 07/19/2007
> 4. FUJITSU SIEMENS
> 5. AMILO Pi 1536
> 6. Not A
On Saturday 19 January 2008 02:54, Dmitry A. Marin wrote:
> Hello! The output of acpidumop is attached. I working with
> 2.6.24-4 kernel now (Ubuntu Hardy (testing)), but if it
> important I can try 2.6.23 as it exist in distribution.
> It seems, that I worked with 2.6.18 5-6 month ago and tried
>
-A70E-00A0D1553957
> Wake-up Type: Power Switch
> SKU Number: Not Specified
> Family: Not Specified
>
> Handle 0x0002, DMI type 2, 8 bytes
> Base Board Information
> Manufacturer: ATI
> Product Name: SB450
>
> Thanks for the dmi
On Friday 18 January 2008 19:12, you wrote:
> On Friday 18 January 2008 21:26:59 Len Brown wrote:
> > System Information
> > Manufacturer: Sony Corporation
> > Product Name: VGN-TZ21MN_N
> > Version: J002RMWG
> >
> >
> > With 2.6.22, did you notice any functional difference with
> > "ac
On Friday 18 January 2008 22:42, Greg Sanders wrote:
> Len,
>
> I tried the acpi_osi thing briefly, but didn't notice any difference, so I
> took it out. After getting your email, I put it back and ran the acpidump
> utility. (got it by apt-get)
>
> The output is attached.
>...
> On Friday -
On Friday 18 January 2008 17:44, David Goguen wrote:
> > > > Handle 0x0001, DMI type 1, 27 bytes
> > > > System Information
> > > > Manufacturer: TOSHIBA
> > > > Product Name: Satellite U305
> > > > Version: PSU30U-054012
> > > > Serial Number: X7068484W
> > > >
On Thursday 01 November 2007 19:09, Dan Barnes wrote:
> Information found in the dmesg output suggested
> sending the dmidecode output to you.
>
> This is from kernel:
>
> Linux ubuntu 2.6.22-8-generic #1 SMP Thu Jul 12
> 15:59:45 GMT 2007 i686 GNU/Linux
>
> If you do
> Wake-up Type: Power Switch
> SKU Number: Not Specified
> Family: Not Specified
>
> Handle 0x0002, DMI type 2, 8 bytes
> Base Board Information
> Manufacturer: FUJITSU SIEMENS
> Product Name: AMILO PI 1536
Thanks for the dmide
On Sunday 29 July 2007 08:18, Ian Snow wrote:
> System Information
> Manufacturer: Sony Corporation
> Product Name: VGN-FZ11M
> Version: C3LP8MZ3
> Serial Number: 28201150-5000954
> UUID: 25BBA8A0-08D1-11DC-874E-0013A9C09B3B
> Wake-up Type: Power Switch
> SKU Number: N/A
On Sunday 15 July 2007 06:40, Dmitry A. Marin wrote:
> System Information
> Manufacturer: BenQ
> Product Name: Joybook S31
Do you notice any functional difference when booting with
"acpi_osi=Linux"(default for 2.6.22 and earlier)
vs.
"acpi_osi=!Linux" (default for 2.
On Tuesday 10 July 2007 02:47, Vasileios Lourdas wrote:
> System Information
> Manufacturer: FUJITSU SIEMENS
> Product Name: AMILO Pi 1536
> Version: Not Applicable
> Serial Number: 53102817
> UUID: 00659C5C-CD63-0010-A350-E07A70B44E78
> Wake-up Type:
> Manufacturer: Dell Inc.
> Product Name: Inspiron 1501
With 2.6.22, did you notice any functional difference with "acpi_osi=!Linux"?
(or since the default changed at 2.6.23, with 2.6.23 or later
do you notice any difference with "acpi_osi=Linux"?)
Please send me the output from ac
On Sunday 02 December 2007 15:21, Sebastian Schleehauf wrote:
> Manufacturer: LENOVO
> Product Name: 076326G
> Version: LENOVO3000 V100
With 2.6.22, did you notice any functional difference with "acpi_osi=!Linux"?
(or since the default changed at 2.6.23, with 2.6.23 or lat
Manufacturer: Apple Computer, Inc.
Product Name: MacBook1,1
With 2.6.22, did you notice any functional difference with "acpi_osi=!Linux"?
(or since the default changed at 2.6.23, with 2.6.23 or later
do you notice any difference with "acpi_osi=Linux"?)
Please send me the output
System Information
Manufacturer: Sony Corporation
Product Name: VGN-TZ21MN_N
Version: J002RMWG
With 2.6.22, did you notice any functional difference with "acpi_osi=!Linux"?
(or since the default changed at 2.6.23, with 2.6.23 or later
do you notice any difference wi
O
> Handle 0x0001, DMI type 1, 27 bytes
> System Information
> Manufacturer: Hewlett-Packard
> Product Name: HP Pavilion dv2000 (RV323UA#ABA)
> Version: F.34
> Serial Number: 2CE7171BDY
> UUID: 1501AA80-F433-11DB-9D1A-9EE3B10D875F
> Wake-up Type: Powe
> Handle 0x0001, DMI type 1, 27 bytes
> System Information
> Manufacturer: TOSHIBA
> Product Name: Satellite U305
> Version: PSU30U-054012
> Serial Number: X7068484W
> UUID: 607BC0A3-0E91-D811-8DB6-001B24BBF5FC
> Wake-up Type: Power Switch
>
IX
"System BIOS is requesting _OSI(Linux)\n");
+ if (dmi_dump_entries(DMI_INTERESTING_ENTRIES))
+ printk(KERN_WARNING
+ "[please extract dmidecode output]\n");
printk(KERN
# dmidecode 2.9
SMBIOS 2.4 present.
30 structures occupying 1044 bytes.
Table at 0x000DF010.
Handle 0x, DMI type 0, 24 bytes
BIOS Information
Vendor: TOSHIBA
Version: V2.50
Release Date: 08/30/2007
Address: 0xE7860
Runtime Size: 100256 bytes
ROM
hey,
Logs requested this. Demidecode info under the base info from lspci and
uname. If you need other info, just let me know.
Mike
Linux largo 2.6.23-gentoo-r3-2 #1 SMP Fri Dec 28 13:08:12 PST 2007 i686
Intel(R) Core(TM)2 Duo CPU T7100 @ 1.80GHz GenuineIntel GNU/Linux
lspci -v
00:00.
Yo,
I saw a message in syslog to send dmidecode output to this email address.
Here goes:
---
# dmidecode 2.9
SMBIOS 2.4 present.
27 structures occupying 867 bytes.
Table at 0x000DC010.
Handle 0x
Hi,
While looking through my dmesg output I saw this message:
Please send dmidecode to linux-acpi@vger.kernel.org
So please find attached the output of dmidecode for me Sony Vaio TZ21MN/N.
If there is any other information you require, please contact me.
# dmidecode 2.9
SMBIOS 2.4 present.
18 s
Please find attached the output of dmidecode after disabling _OSI(Linux), as
per your request.
--
Henk Koster
"Behavioral axioms are right, but agents make mistakes."
Attributed to L.J. Savage
# dmidecode 2.9
SMBIOS 2.4 present.
37 structures occupying 1472 bytes.
Table at 0x000E7440.
Handle 0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi I attached the output of dmidecode to this file. I am running ubuntu
7.10, i hope this is usefull.
Greets,
Sebastian
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8D
Here are 2 dmidecode outputs as suggested in dmesg messages: one after
acpi_osi=!Linux parameter passed to a kernel and another before. By the
way I see messages
"MP-BIOS bug: 8254 timer not connected to IO-APIC"
at every boot if it helps somehow.
I use laptop Dell Inspiron 1501 with F7. kernel-
# dmidecode 2.9
SMBIOS 2.4 present.
20 structures occupying 822 bytes.
Table at 0x000F1C80.
Handle 0x, DMI type 0, 24 bytes
BIOS Information
Vendor: Hewlett-Packard
Version: F.3A
Release Date: 07/19/2007
Address: 0xE6A30
Runtime Size: 103888 bytes
Dear Sirs,
I'm using (Gentoo) Kamikaze sources 2.6.23-kamikaze2 and looking trough the
dmesg output I've notice these strings:
[...]
ACPI: EC: Look up EC in DSDT
ACPI: EC: GPE = 0x1, I/O: command/status = 0x66, data = 0x62
ACPI: System BIOS is requesting _OSI(Linux)
ACPI: If "acpi_osi=Linux" works
Hello, my laptop says:
ACPI: System BIOS is requesting _OSI(Linux)
ACPI: Please test with "acpi_osi=!Linux"
Please send dmidecode to linux-acpi@vger.kernel.org
So this is it:
dmidecode
# dmidecode 2.9
SMBIOS 2.4 present.
37 structures occupying 1217 bytes.
Table at 0x3FEEA000.
Handle 0x, DM
Cheers.
--
Greg Toombs
(519) 400-0065
# dmidecode 2.9
SMBIOS 2.4 present.
41 structures occupying 1330 bytes.
Table at 0x000DC010.
Handle 0x, DMI type 0, 24 bytes
BIOS Information
Vendor: Phoenix Technologies LTD
Version: 5.30
Release Date: 03/09/2007
Address
Please find attached the output of dmidecode after booting with
acpi_osi=!Linux as requested in dmesg output. The system seems to be
working OK apart from problems with STAC9221 Line In (which has never
worked under Linux).
The system is a Dell Dimension 5150.
Regards,
Graham Adams
# dmidec
[EMAIL PROTECTED]:~$ uname -a
Linux corvax-laptop 2.6.22-10-generic #1 SMP Wed Aug 22 08:11:52 GMT
2007 i686 GNU/Linux
[EMAIL PROTECTED]:~$ sudo dmidecode
# dmidecode 2.9
SMBIOS 2.4 present.
34 structures occupying 1112 bytes.
Table at 0x000DF810.
Handle 0x, DMI type 0, 24 bytes
BIOS Informat
# dmidecode 2.9
SMBIOS 2.4 present.
47 structures occupying 2141 bytes.
Table at 0x000E.
Handle 0x, DMI type 4, 35 bytes
Processor Information
Socket Designation: U2E1
Type: Central Processor
Family: Unknown
Manufacturer: Intel(R) Corporation
ID: FA
attached
--
Christer Edwards
Founder, Utah Team
Mentor, US Teams Project
[EMAIL PROTECTED]
https://wiki.ubuntu.com/USTeams
# dmidecode 2.9
SMBIOS 2.4 present.
37 structures occupying 1469 bytes.
Table at 0x000E7440.
Handle 0x, DMI type 0, 24 bytes
BIOS Information
Vendor: Apple Compu
Hi,
It doesn't matter if i boot with acpi_osi=!Linux I still get the message:
ACPI: System BIOS is requesting _OSI(Linux)
ACPI: Please test with "acpi_osi=!Linux"
Below is the output of dmidecode for this laptop
# dmidecode 2.9
SMBIOS 2.4 present.
17 structures occupying 710 bytes.
Table at 0x00
Hi, Im running kernel 2.6.22, dmesg show this also with acpi_osi=!linux
set.
Using ACPI (MADT) for SMP configuration information
Kernel command line: BOOT_IMAGE=Gentoo ro root=802 acpi_osi=!Linux
ACPI: Disabled _OSI(Linux)
ACPI: Core revision 20070126
ACPI: bus type pci registered
ACPI: System B
Hello. I had seen a string "Please send dmidecode to
linux-acpi@vger.kernel.org" in dmesg output and decided to
sent you this information.
# dmidecode 2.8
SMBIOS 2.4 present.
34 structures occupying 1112 bytes.
Table at 0x000DF810.
Handle 0x, DMI type 0, 24 bytes
BIOS Information
Vendo
Hi,
I've just upgraded to Linux 2.6.22 and I noticed this in dmesg:
PCI: Using MMCONFIG
Setting up standard PCI resources
ACPI: System BIOS is requesting _OSI(Linux)
ACPI: Please test with "acpi_osi=!Linux"
Please send dmidecode to linux-acpi@vger.kernel.org
ACPI: Interpreter enabled
ACPI: Using
47 matches
Mail list logo
