User Tools

Site Tools


hardware:samsung_m50_2130

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
hardware:samsung_m50_2130 [2008/05/10 09:54] kratz00hardware:samsung_m50_2130 [2008/12/31 10:44] (current) kratz00
Line 1: Line 1:
 ====== M50-2130 Baako ====== ====== 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 ===== ===== Hardware =====
Line 94: Line 115:
 |<code> |<code>
 <M> HCI USB driver <M> HCI USB driver
-[*]   SCO (voice) support 
 < > HCI SDIO driver < > HCI SDIO driver
 < > HCI UART driver < > HCI UART driver
Line 103: Line 123:
 </code>| </code>|
  
-After booting the new kernel, load //hci_usb//+After booting the new kernel, load //btusb//
 <code> <code>
-modprobe hci_usb+modprobe btusb
 </code> </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> <code>
 hci0:   Type: USB hci0:   Type: USB
Line 141: Line 161:
 </code> </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> <code>
 Scanning ... Scanning ...
Line 183: Line 203:
 test -r $HOME/.xbindkeysrc && xbindkeys & test -r $HOME/.xbindkeysrc && xbindkeys &
 </code> </code>
 +
  
 ===== ACPI ===== ===== ACPI =====
Line 200: Line 221:
 After opening the lid, it state changes to //open// and thenceforward the lid state is always correct. 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]]), now the lid state is correct after booting the system. How to use this is covered in the [[software:linux_kernel]] building instructions.+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.
hardware/samsung_m50_2130.1210406066.txt.gz · Last modified: 2008/05/10 09:54 by kratz00