Differences

This shows you the differences between two versions of the page.

--- hardware:samsung_m50_2130 [2008/01/01 14:48] – kratz00
+++ hardware:samsung_m50_2130 [2008/12/31 10:35] – kratz00
@@ Line 1: / Line 1: @@
 ====== M50-2130 Baako ======
+===== Modem =====
+Needed: [[hardware:ad1986a|alsa]], [[software:slmodem]]
+From //aplay -l//
+<code>
+card 0: Intel [HDA Intel], device 6: Si3054 Modem [Si3054 Modem]
+  Subdevices: 1/1
+  Subdevice #0: subdevice #0
+</code>
+Start the software modem:
+<code>
+slmodemd -a modem:0 -g root
+</code>
+or if you use a old version of ALSA-lib:
+<code>
+slmodemd -a hw:0,6 -g root
+</code>
 ===== Hardware =====
@@ Line 94: / Line 115: @@
 |<code>
 <M> HCI USB driver
-[*]   SCO (voice) support
 < > HCI SDIO driver
 < > HCI UART driver
@@ Line 108: / Line 128: @@
 </code>
-With the help of //hciconfig -a// from the [[software:bluez-utils]], we see this:
+With the help of //hciconfig -a// from the [[software:bluez]] package, we see this:
 <code>
 hci0:   Type: USB
@@ Line 141: / Line 161: @@
 </code>
-Quick check if there are some other Bluetooth devices arround, //hcitool scan// (also from the [[software:bluez-utils]])
+Quick check if there are some other Bluetooth devices arround, //hcitool scan// (also from the [[software:bluez]] package)
 <code>
 Scanning ...
@@ Line 183: / Line 203: @@
 test -r $HOME/.xbindkeysrc && xbindkeys &
 </code>
+===== ACPI =====
+What most people want is, that when they close the lid of their laptop, it should suspend.
+After closing the lid on this notebook, it needs arround 12 seconds till a ACPI event is thrown.
+It's exactly the same behaviour in MS Windows. So it seems to be a feature, some sort of delay time.
+The other thing which is a little bit special is that after booting the initial state of the lid is always //closed//.
+<code>
+cat /proc/acpi/button/lid/LID0/state
+state:      closed
+</code>
+This is no problem at all because if you close the lid for the first time, longer than arround 12 seconds, the lid state is still //closed//.
+After opening the lid, it state changes to //open// and thenceforward the lid state is always correct.
+If you are bothered by this you can use this custom DSDT ([[http://kratz00.org/files/custom_dsdt.hex|custom_dsdt.hex]]), using this the lid state is correct after booting the system. How to use this is covered in the [[software:linux_kernel]] building instructions.