sony-vaio-z-series team mailing list archive

[Raphael Gradenwitz <raphael@xxxxxxxxxxxxxxxxx>]

Hello Mike,

Am Donnerstag, den 08.10.2009, 01:03 +0200 schrieb Mike: 
> I am using the latest karmic 2.6.31.11 kernel right now because
> today's 2.6.31.12 update does not boot. My older kernel still contains
> Norberts 0.9np1 module.

That is right, my startup script only work with Norberts kernel module
loaded with acpi_osi="!Windows 2006", I will next make a better script
that will find out what kernel module is loaded by default to become
more general and a little bit smarter.

> First, on my systems the Speed/Stamina LEDs stopped working too,
> initially. This was after applying all the changes mentioned in
> Raphael's instruction. After some backtracking I was able to fix the
> Grub2 problem by tweaking /etc/default/grub like this:
> 
>   (...)
>   GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor"
>   GRUB_CMDLINE_LINUX=acpi_osi='"!Windows 2006"'
>   (...)
> 

That is nice but I have tried that already and it does not land
in /proc/cmdline

this:

first change /etc/default/grub:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor"
GRUB_CMDLINE_LINUX="acpi_osi=\\\"!Windows 2006\\\""

then execute:
sudo /usr/sbin/grub-mkconfig

now /boot/grub/grub.cfg has the right entries


but
===

after a reboot, it is wrong again...


Only pressing 'e' in the grub menu and edit the command line by hand
(change " into \")

> The update-grub command successfully generates the /boot/grub/grub.cfg
> file which contains menu entries that have config lines such as this
> one:
> 
> linux   /boot/vmlinuz-2.6.31-11-generic
> root=UUID=e540f235-d66b-4a46-839d-4fd034fdec67 ro acpi_osi="!Windows
> 2006"  quiet splash acpi_backlight=vendor
> 
> The system boot okay. But here comes the kicker: The speed/stamina
> LEDs still stay off unless I remove the

No, it can/does not that way.

> /etc/modprobe.d/sony-laptop.conf file. Without this file (and the
> module parameter it contains), the module loads okay, apparently.
> /var/log/messages contains:
> 
> Oct  8 00:36:11 archangel kernel: [  148.959478] sony-laptop: Sony
> Programmable IO Control Driver v0.9np1.
> Oct  8 00:36:11 archangel kernel: [  148.959528] sony-laptop: detected
> Type3 model
> 
> With the current state of the system, the Intel graphics works. But
> the switch-x-to script does not:
> 
> syslog.1:Oct  8 00:03:00 archangel init: switch-x-to main process
> ended, respawning
> syslog.1:Oct  8 00:03:00 archangel init: switch-x-to main process
> ended, respawning
> syslog.1:Oct  8 00:03:00 archangel init: switch-x-to main process
> ended, respawning
> syslog.1:Oct  8 00:03:00 archangel init: switch-x-to main process
> ended, respawning
> syslog.1:Oct  8 00:03:00 archangel init: switch-x-to main process
> ended, respawning
> syslog.1:Oct  8 00:03:00 archangel init: switch-x-to main process
> ended, respawning
> syslog.1:Oct  8 00:03:00 archangel init: switch-x-to main process
> ended, respawning
> syslog.1:Oct  8 00:03:00 archangel init: switch-x-to main process
> ended, respawning
> syslog.1:Oct  8 00:03:00 archangel init: switch-x-to main process
> ended, respawning
> syslog.1:Oct  8 00:03:00 archangel init: switch-x-to respawning too
> fast, stopped
> 
> This happens when booting and is probably caused by the strange state
> of the system.


Thank you for your report, respawning was not realy necessary ;-). It is
removed now, update it (or remove 'respawn' out of the
file /etc/init/switch-x-to.conf) Then this syslog entries will not apear
no more.

Raphael

(Please answer with
Reply-to: sony-vaio-z-series@xxxxxxxxxxxxxxxxxxx
Thanks)

Attachment: smime.p7s
Description: S/MIME cryptographic signature