hardware:samsung_m50_2130
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
hardware:samsung_m50_2130 [2007/12/05 17:55] – kratz00 | hardware:samsung_m50_2130 [2008/12/31 10:44] (current) – kratz00 | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== M50-2130 Baako ====== | ====== M50-2130 Baako ====== | ||
+ | |||
+ | ===== Modem ===== | ||
+ | |||
+ | Needed: [[hardware: | ||
+ | |||
+ | From //aplay -l// | ||
+ | < | ||
+ | card 0: Intel [HDA Intel], device 6: Si3054 Modem [Si3054 Modem] | ||
+ | Subdevices: 1/1 | ||
+ | Subdevice #0: subdevice #0 | ||
+ | </ | ||
+ | |||
+ | Start the software modem: | ||
+ | < | ||
+ | slmodemd -a modem:0 -g root | ||
+ | </ | ||
+ | |||
+ | or if you use a old version of ALSA-lib: | ||
+ | < | ||
+ | slmodemd -a hw:0,6 -g root | ||
+ | </ | ||
===== Hardware ===== | ===== Hardware ===== | ||
Line 26: | Line 47: | ||
06:09.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 03) | 06:09.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 03) | ||
</ | </ | ||
+ | |||
+ | ===== Bluetooth ===== | ||
+ | |||
+ | The M50 Baako has a built in Bluetooth device. | ||
+ | |||
+ | //cat / | ||
+ | < | ||
+ | ... | ||
+ | T: Bus=04 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 | ||
+ | D: Ver= 1.10 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 # | ||
+ | P: Vendor=0a5c ProdID=200a Rev= 0.01 | ||
+ | S: Manufacturer=Broadcom | ||
+ | S: Product=Broadcom Bluetooth Module | ||
+ | C:* #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr= | ||
+ | I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb | ||
+ | E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms | ||
+ | E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms | ||
+ | E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms | ||
+ | I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb | ||
+ | E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms | ||
+ | E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms | ||
+ | I: If#= 1 Alt= 1 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb | ||
+ | E: Ad=83(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms | ||
+ | E: Ad=03(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms | ||
+ | I:* If#= 1 Alt= 2 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb | ||
+ | E: Ad=83(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms | ||
+ | E: Ad=03(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms | ||
+ | I: If#= 1 Alt= 3 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb | ||
+ | E: Ad=83(I) Atr=01(Isoc) MxPS= 32 Ivl=1ms | ||
+ | E: Ad=03(O) Atr=01(Isoc) MxPS= 32 Ivl=1ms | ||
+ | I: If#= 1 Alt= 4 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb | ||
+ | E: Ad=83(I) Atr=01(Isoc) MxPS= 64 Ivl=1ms | ||
+ | E: Ad=03(O) Atr=01(Isoc) MxPS= 64 Ivl=1ms | ||
+ | I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb | ||
+ | E: Ad=83(I) Atr=01(Isoc) MxPS= 64 Ivl=1ms | ||
+ | E: Ad=03(O) Atr=01(Isoc) MxPS= 64 Ivl=1ms | ||
+ | I:* If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) | ||
+ | E: Ad=84(I) Atr=02(Bulk) MxPS= 32 Ivl=0ms | ||
+ | E: Ad=04(O) Atr=02(Bulk) MxPS= 32 Ivl=0ms | ||
+ | I:* If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 Driver=(none) | ||
+ | ... | ||
+ | </ | ||
+ | |||
+ | or for better reading, //lsusb// output: | ||
+ | < | ||
+ | ... | ||
+ | Bus 004 Device 002: ID 0a5c:200a Broadcom Corp. Bluetooth dongle | ||
+ | ... | ||
+ | </ | ||
+ | Needed Linux kernel modules: | ||
+ | |||
+ | |**Linux Kernel Configuration: | ||
+ | |< | ||
+ | < | ||
+ | < | ||
+ | < | ||
+ | [*] | ||
+ | < | ||
+ | [*] | ||
+ | [*] | ||
+ | < | ||
+ | </ | ||
+ | |||
+ | and | ||
+ | |||
+ | |**Linux Kernel Configuration: | ||
+ | |< | ||
+ | <M> HCI USB driver | ||
+ | < > HCI SDIO driver | ||
+ | < > HCI UART driver | ||
+ | < > HCI BCM203x USB driver | ||
+ | < > HCI BPA10x USB driver | ||
+ | < > HCI BlueFRITZ! USB driver | ||
+ | < > HCI VHCI (Virtual HCI device) driver | ||
+ | </ | ||
+ | |||
+ | After booting the new kernel, load //btusb// | ||
+ | < | ||
+ | modprobe btusb | ||
+ | </ | ||
+ | |||
+ | With the help of //hciconfig -a// from the [[software: | ||
+ | < | ||
+ | hci0: Type: USB | ||
+ | BD Address: 00: | ||
+ | DOWN | ||
+ | RX bytes:0 acl:0 sco:0 events:0 errors:0 | ||
+ | TX bytes:0 acl:0 sco:0 commands:0 errors:0 | ||
+ | </ | ||
+ | |||
+ | Bringing up the device: | ||
+ | < | ||
+ | hciconfig hci0 up | ||
+ | </ | ||
+ | |||
+ | After this the output of //hciconfig -a// has changed: | ||
+ | < | ||
+ | hci0: Type: USB | ||
+ | BD Address: 00: | ||
+ | UP RUNNING | ||
+ | RX bytes:348 acl:0 sco:0 events:11 errors:0 | ||
+ | TX bytes:38 acl:0 sco:0 commands:11 errors:0 | ||
+ | Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00 | ||
+ | Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 | ||
+ | Link policy: | ||
+ | Link mode: SLAVE ACCEPT | ||
+ | Name: ' | ||
+ | Class: 0x000000 | ||
+ | Service Classes: Unspecified | ||
+ | Device Class: Miscellaneous, | ||
+ | HCI Ver: 1.2 (0x2) HCI Rev: 0x2 LMP Ver: 1.2 (0x2) LMP Subver: 0x6965 | ||
+ | Manufacturer: | ||
+ | </ | ||
+ | |||
+ | Quick check if there are some other Bluetooth devices arround, //hcitool scan// (also from the [[software: | ||
+ | < | ||
+ | Scanning ... | ||
+ | 00: | ||
+ | </ | ||
+ | It found one of my Nintendo Wii remotes. | ||
===== Special keys ===== | ===== Special keys ===== | ||
Line 40: | Line 181: | ||
Put this in your .xinitrc or some other script which is executed if X is started. | Put this in your .xinitrc or some other script which is executed if X is started. | ||
< | < | ||
- | # load local modmap | ||
test -r $HOME/ | test -r $HOME/ | ||
</ | </ | ||
Line 47: | Line 187: | ||
There are several possibilities of assigning functionality to those keysyms, I am using [[software:: | There are several possibilities of assigning functionality to those keysyms, I am using [[software:: | ||
+ | |||
+ | Relevant lines of my configuration file ($HOME/ | ||
+ | |||
+ | < | ||
+ | " | ||
+ | XF86AudioLowerVolume | ||
+ | " | ||
+ | XF86AudioRaiseVolume | ||
+ | " | ||
+ | XF86AudioMute | ||
+ | </ | ||
+ | |||
+ | Again put this in your .xinitrc or some other script which is executed if X is started. | ||
+ | < | ||
+ | test -r $HOME/ | ||
+ | </ | ||
+ | |||
+ | |||
+ | ===== 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//. | ||
+ | |||
+ | < | ||
+ | cat / | ||
+ | state: | ||
+ | </ | ||
+ | |||
+ | 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:// |
hardware/samsung_m50_2130.1196873728.txt.gz · Last modified: 2007/12/05 17:55 by kratz00