acpi_osi="Windows 2006"

vdox2 · 2008-08-12 14:19:24

Hi,

Can anyone say why am I getting this error message:

export: 36: 2006" : bad variable name
Kernel panic - not syncing: Attempted to kill init!

These are my kernel command-line parameters in grub's menu.lst :

root=/dev/sda2 vga=773 acpi_osi="Windows 2006" ro 5

So acpi_osi="Windows 2006" doesn't work for some reason. Any clues

Thanks,

Last edited by vdox2 (2008-08-13 11:18:29)

vdox2 · 2008-08-13 11:18:36

Bump

iphitus · 2008-08-13 11:45:13

It cant handle spaces. Try doing acpi_osi="Windows\ 2006" ? Why are you passing that option?

vdox2 · 2008-08-13 15:23:49

Do you mean "\" as an escape-character? Like so "Windows\<space>2006"

Well, I still get the same error. So is this a problem with Arch, GRUB or the kernel itself?

My hardware requires this option to make the backlight structures available through acpi.

Thanks,

Last edited by vdox2 (2008-08-13 15:26:07)

vdox2 · 2008-08-15 09:42:22

bumpity

eXire · 2008-08-15 10:33:16

Use the acpi_os_name parameter instead of acpi_osi

vdox2 · 2008-08-15 17:43:40

Use the acpi_os_name parameter instead of acpi_osi

No good

lyman · 2008-10-07 08:05:47

vdox2 wrote:

Use the acpi_os_name parameter instead of acpi_osi
No good

Indeed, I wanna know why, too.

dav7 · 2008-10-07 08:28:02

Let's start by finding what script is being run.

Try this bit of a fiendish hack (be sure to set it in grub with the "e" key as you only want to run it once), making sure you include the backticks:

root=/dev/sda2 vga=773 acpi_osi="`echo ${BASH_SOURCE[0]}; exit`" ro 5

That should make the script print its name then quit, killing init, giving you a chance to write the script name down (or you can just remember it if you have a cool memory ) and then we'll have a look inside the script at the export command giving us teh issuez and possibly convince it to like "Windows 2006" (or we can dig a bit deeper and just hardcode the required parameter into whereever it needs to go).

Of course, I have a bad habit of figuring out the hardest, most complex way of doing something, so this might not be the best way to do this It shouldn't break anything tho.

-dav7

Last edited by dav7 (2008-10-07 08:30:03)

chochem · 2008-10-07 15:10:46

vdox2 wrote:

Well, I still get the same error. So is this a problem with Arch, GRUB or the kernel itself?

I tried using this sort of argument while trying to solve an ACPI issue with some fellow owners-of-the-same-laptop-model who used ubuntu. They had no problems passing space-inclusive arguments in GRUB so I'd say that it's an Arch thing... either that or the different kernel/GRUB versions. Not that that clears up much of confusion, s'rry

BTW after that experience I wrote a wiki article on DSDT - might be an option for you.

lyman · 2008-10-08 13:46:17

dav7 wrote:

Let's start by finding what script is being run.
Try this bit of a fiendish hack (be sure to set it in grub with the "e" key as you only want to run it once), making sure you include the backticks:
root=/dev/sda2 vga=773 acpi_osi="`echo ${BASH_SOURCE[0]}; exit`" ro 5
That should make the script print its name then quit, killing init, giving you a chance to write the script name down (or you can just remember it if you have a cool memory ) and then we'll have a look inside the script at the export command giving us teh issuez and possibly convince it to like "Windows 2006" (or we can dig a bit deeper and just hardcode the required parameter into whereever it needs to go).
Of course, I have a bad habit of figuring out the hardest, most complex way of doing something, so this might not be the best way to do this It shouldn't break anything tho.
-dav7

There can not be space in the value of kernel option acpi_osi parameter in arch.

acpi_osi=Linux -> ok
acpi_osi="Windows 2006" -> kernel panic

There's a space in your code (before exit, right ;P), so it also causes kernel panic.

I'm not sure whether the space problem is a bug. Perhaps ubuntu has its own patch but arch has not?

dav7 · 2008-10-08 17:12:06

Oh, oops. You can safely remove THAT space, but you wouldn't be able to remove the space before the 'echo'...

Time for plan U then.

(U = Unknown )

-dav7

Zack89 · 2008-10-08 18:30:28

Isnt \ / a space in Linux for Directories?

dav7 · 2008-10-08 19:17:07

Uh, not exactly, but you're close.

\ is typically recognized as an escape character, and used to cause a given shell to recognize non-printable characters like spaces as non-delimiting characters rather than delimiting characters, causing the shell to consider hello\ world as 'hello world' rather than 'hello' 'world'.

/ is just used to mark the end of a directory but is in some cases best left dropped, and in other cases not being applicable, this case being the latter.

So "\ " is a non-delimiting space in a shell environment but NOT "a space for directories". There are places (eg, GUI tools) where a \ isn't required, and even in the shell, if you singly quote (in some circumstances, doubly quote as well) a directory specification properly. Then there are crazy situations like for example ssh's command execution mode which is really picky and wants you to quote AND escape directories... heh.

-dav7

Last edited by dav7 (2008-10-08 19:19:25)

iBertus · 2008-10-09 19:40:37

I also had this problem when trying to troubleshoot ACPI issues with my laptop a few months back. The latest kernel update fixed all the issues and so I don't need the hack anymore. Still, it's interesting the it works with ubuntu and not Arch.

staple · 2009-07-31 04:34:10

bump, it would be nice if this was resolved

iphitus · 2009-07-31 11:29:46

this is not a bug tracker, it won't be solved by bumping this thread.

webmonarch · 2009-11-13 19:26:25

i am a little late to this thread. I have a Sony Vaio Z which this kernel paremeter enables us to use the onboard NVidia graphics card (instead of the integrated Intel card).

I was never able to get a value with a space in it to work. But, based on the brief explaination of this parameter @ http://www.mjmwired.net/kernel/Document … rs.txt#222 I tried using acpi_osi= (ie: no parameter). It should remove the Windows 2006 (which the !Windows 2006 does), along with everything else.

It's working for me so far.

In case this helps anyone (since this thread never saw a resolution). Obviously, the core issue parameter parsing issue doesn't seem to be fixed.

CronLogic · 2010-01-16 03:11:36

I found the solution at the bottom of this page:

http://bugs.archlinux.org/task/10002

Add a "#" before the acpi_os_name var like this:

kernel /vmlinuz26 root=/dev/disk/by-uuid/38a1482a-c9ae-472a-bc56-10274772a0fb ro vga=0 resume=/dev/sda8 # acpi_os_name="Windows 2006 SP2"

Arch Linux

#1 2008-08-12 14:19:24

acpi_osi="Windows 2006"

#2 2008-08-13 11:18:36

Re: acpi_osi="Windows 2006"

#3 2008-08-13 11:45:13

Re: acpi_osi="Windows 2006"

#4 2008-08-13 15:23:49

Re: acpi_osi="Windows 2006"

#5 2008-08-15 09:42:22

Re: acpi_osi="Windows 2006"

#6 2008-08-15 10:33:16

Re: acpi_osi="Windows 2006"

#7 2008-08-15 17:43:40

Re: acpi_osi="Windows 2006"

#8 2008-10-07 08:05:47

Re: acpi_osi="Windows 2006"

#9 2008-10-07 08:28:02

Re: acpi_osi="Windows 2006"

#10 2008-10-07 15:10:46

Re: acpi_osi="Windows 2006"

#11 2008-10-08 13:46:17

Re: acpi_osi="Windows 2006"

#12 2008-10-08 17:12:06

Re: acpi_osi="Windows 2006"

#13 2008-10-08 18:30:28

Re: acpi_osi="Windows 2006"

#14 2008-10-08 19:17:07

Re: acpi_osi="Windows 2006"

#15 2008-10-09 19:40:37

Re: acpi_osi="Windows 2006"

#16 2009-07-31 04:34:10

Re: acpi_osi="Windows 2006"

#17 2009-07-31 11:29:46

Re: acpi_osi="Windows 2006"

#18 2009-11-13 19:26:25

Re: acpi_osi="Windows 2006"

#19 2010-01-16 03:11:36

Re: acpi_osi="Windows 2006"

Board footer