mirror of
https://github.com/mbirth/wiki.git
synced 2024-12-24 22:54:09 +00:00
Switched to Kramdown, replaced highlights with pygments. Added a few
posts.
This commit is contained in:
parent
9d6b25ebed
commit
706fb0da51
@ -5,7 +5,8 @@ url: "http://wiki.mbirth.de"
|
||||
|
||||
#paginate: 10
|
||||
|
||||
markdown: redcarpet
|
||||
markdown: kramdown
|
||||
#markdown: redcarpet
|
||||
markdown_ext: markdown,mkdown,mkdn,mkd,md
|
||||
#permalink: pretty
|
||||
highlighter: pygments
|
||||
|
||||
@ -24,9 +24,7 @@ Older versions of DD-WRT didn't provide a firmware file for the WL-300g, but onl
|
||||
|
||||
The router ID was found quick: In the `dd-wrt.v23_asus.trx` at `0x356fc4`, there's the string
|
||||
|
||||
```
|
||||
57 4c 35 30 30 67 78
|
||||
```
|
||||
|
||||
which is `WL500gx`. After changing it to `WL300g ` (with a space after the "g" to fill up the digit), the router didn't reject the firmware directly, but initiated the update, then rebooted quickly after that and showed the old firmware again.
|
||||
|
||||
|
||||
18
_posts/2009-02-02-medion-bios-settings.md
Normal file
18
_posts/2009-02-02-medion-bios-settings.md
Normal file
@ -0,0 +1,18 @@
|
||||
---
|
||||
title: MEDION BIOS settings
|
||||
layout: default
|
||||
created: 2009-02-22 02:24:33 +0100
|
||||
toc: false
|
||||
tags:
|
||||
- know-how
|
||||
- hardware
|
||||
- medion
|
||||
- bios
|
||||
- settings
|
||||
---
|
||||
Some MEDION PCs have hidden BIOS settings. To get to them, get into the BIOS and press <kbd>F11</kbd>. If you're asked for a password, try `am8888egh` or `am8888egc`. Maybe you can even omit the last letter.
|
||||
|
||||
According to a MEDION employee, there are only 2 employees who know this password. Also it shouldn't be leaked to the net so that no one fools around with the settings.
|
||||
Well, IMHO everyone should decide for his own whether he wants to risk damaging his PC or not. But I guess the newer BIOSes ask for another password.
|
||||
|
||||
More info: [PC Welt forums](http://www.pcwelt.de/forum/showthread.php?t=196865), [Wim's BIOS](http://www.wimsbios.com/phpBB2/viewtopic.php?t=7557)
|
||||
54
_posts/2009-02-10-logitech-v400.md
Normal file
54
_posts/2009-02-10-logitech-v400.md
Normal file
@ -0,0 +1,54 @@
|
||||
---
|
||||
title: Logitech V400
|
||||
layout: default
|
||||
created: 2009-02-10 00:06:10 +0100
|
||||
toc: false
|
||||
tags:
|
||||
- know-how
|
||||
- hardware
|
||||
- logitech
|
||||
- mouse
|
||||
- usb
|
||||
---
|
||||
|
||||
|
||||
* **Support:** [logitech.com](http://www.logitech.com/index.cfm/428/144&cl=us,en)
|
||||
|
||||
|
||||
Enable all settings in SetPoint
|
||||
===============================
|
||||
|
||||
Install [uberOptions](http://www.mstarmetro.net/~rlowens/uberOptions/) to enable ALL settings in the *Logitech SetPoint* application.
|
||||
|
||||
|
||||
Remapping buttons in Linux
|
||||
==========================
|
||||
|
||||
You can use the following command to remap the buttons:
|
||||
|
||||
xinput set-button-map <device-id> <button1> <button2> <button3> ... <buttonN>
|
||||
|
||||
The `<device-id>` is shown in the `xinput list` output as *Logitech USB Receiver [XExtensionPointer]* - you can use the name as a string or the id number.
|
||||
You can query the actual button state using `xinput query-state <device-id>`.
|
||||
|
||||
The mouse has following button-ids:
|
||||
|
||||
| Button | ID |
|
||||
|:----------------------|:--:|
|
||||
| Left mouse button | 1 |
|
||||
| Right mouse button | 3 |
|
||||
| Wheel button | 2 |
|
||||
| Wheel up | 4 |
|
||||
| Wheel down | 5 |
|
||||
| Wheel left | 6 |
|
||||
| Wheel right | 7 |
|
||||
| "Up" button | 9 |
|
||||
| "Down" button | 8 |
|
||||
|
||||
See [remapping mouse buttons]({% post_url 2009-07-17-remapping-mouse-buttons %}) on what buttons X11 recognizes.
|
||||
|
||||
According to this the default configuration (`xinput set-button-map <device-id> 1 2 3 4 5 6 7 8 9`) already gives the correct button assignment.
|
||||
If you prefer to swap the thumb buttons so that "Up" is *Thumb1* and "Down" is *Thumb2* you can do this using the following command:
|
||||
|
||||
# input id: 1 2 3 4 5 6 7 8 9
|
||||
xinput set-button-map <device-id> 1 2 3 4 5 6 7 9 8
|
||||
33
_posts/2009-05-20-msi-digivox-a-d.md
Normal file
33
_posts/2009-05-20-msi-digivox-a-d.md
Normal file
@ -0,0 +1,33 @@
|
||||
---
|
||||
title: MSI DigiVox A/D USB2.0
|
||||
layout: default
|
||||
created: 2009-05-20 11:05:28 +0200
|
||||
toc: false
|
||||
tags:
|
||||
- know-how
|
||||
- hardware
|
||||
- msi
|
||||
- digivox
|
||||
---
|
||||
|
||||
Ubuntu
|
||||
======
|
||||
|
||||
To use this DVB-T USB stick in Ubuntu, you have to install a newer kernel driver.
|
||||
Follow the instructions from [mcentral.de](http://mcentral.de/wiki/index.php5/Em2880).
|
||||
Also you might have to install the firmware files according to [ubuntuforums.org](http://ubuntuforums.org/showthread.php?t=437208).
|
||||
Finally you need to extract the firmware of the `xc3028` tuner using the manual at [wiki.ubuntuusers.de](http://wiki.ubuntuusers.de/em28xx#Firmware-ab-Intrepid-Ibex).
|
||||
(You'll need the Windows driver for this as the firmware is extracted from it.)
|
||||
|
||||
After that, use the [totem-xine](apt://totem-xine?refresh=yes) package instead of `totem-gstreamer` (uninstall the latter one).
|
||||
But to make things work, you first have to create a channels.conf for xine to find the valid channels (you need the [dvb-utils](apt://dvb-utils?refresh=yes) package):
|
||||
|
||||
scan -p -x 0 /usr/share/dvb/dvb-t/de-Berlin > ~/.xine/channels.conf
|
||||
|
||||
|
||||
If you want to try the `totem-gstreamer`, try this:
|
||||
|
||||
scan -p -x 0 /usr/share/dvb/dvb-t/de-Berlin > ~/.gstreamer-0.10/channels.conf
|
||||
|
||||
|
||||
(or you could just copy the file over, if you already created one)
|
||||
90
_posts/2009-07-17-remapping-mouse-buttons.md
Normal file
90
_posts/2009-07-17-remapping-mouse-buttons.md
Normal file
@ -0,0 +1,90 @@
|
||||
---
|
||||
title: Remapping mouse buttons
|
||||
layout: default
|
||||
created: 2009-07-17 23:07:05 +0200
|
||||
toc: false
|
||||
tags:
|
||||
- know-how
|
||||
- software
|
||||
- linux
|
||||
- mouse
|
||||
---
|
||||
permanently
|
||||
===========
|
||||
|
||||
To remap mouse buttons permanently, you can use the `xinput set-button-map` command. Every mouse button click issues a button click with a specific id to X11. X11 recognizes the following buttons:
|
||||
|
||||
| ID | Button |
|
||||
|:--:|:--------------|
|
||||
| 1 | Left click |
|
||||
| 2 | Middle click |
|
||||
| 3 | Right click |
|
||||
| 4 | Wheel up |
|
||||
| 5 | Wheel down |
|
||||
| 6 | Wheel left |
|
||||
| 7 | Wheel right |
|
||||
| 8 | Thumb1 |
|
||||
| 9 | Thumb2 |
|
||||
| 10 | ExtBt7 |
|
||||
| 11 | ExtBt8 |
|
||||
|
||||
You can use the following command to remap the buttons:
|
||||
|
||||
xinput set-button-map <device-id> <button1> <button2> <button3> ... <buttonN>
|
||||
|
||||
The `<device-id>` is shown in the `xinput list` output - you can use the name as a string or the id number. You can query the actual button state using `xinput query-state <device-id>`.
|
||||
|
||||
So the default configuration (`xinput set-button-map <device-id> 1 2 3 4 5 6 7 8 9`) would give you the normal behavior.
|
||||
But if you prefer e.g. having the thumb buttons for *WheelLeft* and *WheelRight*, you would run this command:
|
||||
|
||||
# input id: 1 2 3 4 5 6 7 8 9
|
||||
xinput set-button-map <device-id> 1 2 3 4 5 8 9 6 7
|
||||
|
||||
This would map buttons 8→6 and 9→7 and vice versa.
|
||||
|
||||
To automatically set your preferred mapping on bootup, you can add the line to *System* → *Preferences* → *Startup Applications* (formerly *Sessions*).
|
||||
|
||||
|
||||
per application (Wheel/Thumb only)
|
||||
==================================
|
||||
|
||||
To remap wheel-/thumb-mouse buttons per application, you can use `imwheel` from the same-named [package](apt://imwheel). After installing the package, copy the default configuration to your homedir:
|
||||
|
||||
cp /etc/X11/imwheel/imwheelrc ~/.imwheelrc
|
||||
|
||||
And then enable the automatic starting upon start of X11 by editing `/etc/X11/imwheel/startup.conf` and changing the `IMWHEEL_START` value to **`1`**.
|
||||
|
||||
Now you can modify your `.imwheelrc` to fit your needs. The format is
|
||||
|
||||
"window regexp"
|
||||
Modifier, Mousebutton, Keypresses/Mousebutton
|
||||
...
|
||||
|
||||
So for example to use the WheelLeft and WheelRight buttons to switch tabs in Firefox, you could use the following definition:
|
||||
|
||||
"^Firefox-bin$"
|
||||
# Flip between browser tabs
|
||||
None, Left, Control_L|Page_Up
|
||||
None, Right, Control_L|Page_Down
|
||||
|
||||
This would map *WheelLeft* to <kbd>Ctrl</kbd>-<kbd>PgUp</kbd> and *WheelRight* to <kbd>Ctrl</kbd>-<kbd>PgDn</kbd>.
|
||||
|
||||
A *Modifier* of `None` means, this only works if no modifier (`Shift_L`, `Shift_R`, `Control_L`, `Control_R`, `Alt_L`, `Alt_R`) is pressed while clicking.
|
||||
If you leave this empty, the mapping works regardless of which modifier is held down.
|
||||
|
||||
Use this to go to previous/next track in Rhythmbox using the WheelLeft and WheelRight clicks:
|
||||
|
||||
"^Rhythmbox$"
|
||||
None, Left, Alt_L|Left
|
||||
None, Right, Alt_L|Right
|
||||
|
||||
(In this case, `Rhythmbox` defines the *window resource name* since Rhythmbox itself puts the currently playing song in the title bar.
|
||||
You could also match against `rhythmbox` which is the *window class name*. Since `imwheel -c` wasn't able to show them to me, I just guessed.)
|
||||
|
||||
<p><div class="noteimportant" markdown="1">
|
||||
Looks like `imwheel` causes some problems when scrolling in *Opera*: The webpage doesn't get redrawn so that you have
|
||||
blank or garbled areas when scrolling. Also you have to click on an area to scroll it. (i.e. if you have a webpage with a textarea,
|
||||
the scrollwheel will scroll the textarea even if the pointer is outside of it until you click the area outside the textarea).
|
||||
|
||||
To get back the original behavior, comment out the lines for Opera in your `.imwheelrc` or add an `@Exclude` rule.
|
||||
</div></p>
|
||||
@ -49,7 +49,7 @@ If you have several devices in your home network and the FB keeps deleting them
|
||||
|
||||
So first, create a file `static.list` which looks like this (fill in the data of your own hosts):
|
||||
|
||||
```
|
||||
~~~
|
||||
00:21:85:C0:FF:EE mypc 172.16.1.1
|
||||
00:16:D4:C0:FF:EE wife-pc 172.16.1.2
|
||||
00:18:39:C0:FF:EE slug 172.16.254.253
|
||||
@ -57,11 +57,11 @@ So first, create a file `static.list` which looks like this (fill in the data of
|
||||
00:1E:A9:C0:FF:EE wii 172.16.1.11
|
||||
00:22:69:C0:FF:EE netbook 172.16.1.3
|
||||
00:C0:EB:C0:FF:EE printsvr 172.16.254.252
|
||||
```
|
||||
~~~
|
||||
|
||||
Then you only need this little Python script (and *[Python](http://www.python.org/)*, of course):
|
||||
|
||||
```python
|
||||
{% highlight python %}
|
||||
#!/usr/bin/env python3
|
||||
# -*- coding: utf-8 -*-
|
||||
|
||||
@ -102,7 +102,7 @@ for entry in entries:
|
||||
|
||||
print( "#### landevices > landevices" )
|
||||
print( landevs )
|
||||
```
|
||||
{% endhighlight %}
|
||||
|
||||
Custom DNS
|
||||
==========
|
||||
|
||||
25
_posts/2009-12-22-memup-pop-key.md
Normal file
25
_posts/2009-12-22-memup-pop-key.md
Normal file
@ -0,0 +1,25 @@
|
||||
---
|
||||
title: memup Pop Key
|
||||
layout: default
|
||||
created: 2009-12-22 00:43:14 +0100
|
||||
toc: false
|
||||
tags:
|
||||
- know-how
|
||||
- hardware
|
||||
- memup
|
||||
- popkey
|
||||
- usb
|
||||
---
|
||||
* **Homepage:** http://www.memup.com/
|
||||
|
||||
I just bought a 4GB *Pop Key* in a local supermarket. This device not only works as a simple flash disk but also brings a CD-ROM-Partition with a small security software with it. This just calls for modification...
|
||||
|
||||
|
||||
CD Partition
|
||||
============
|
||||
|
||||
After some searching, I found a posting on the [usboffice.kr](http://blog.usboffice.kr/?p=146) blog. Luckily, the *Pop Key* has a USB ID of `090c:1000` and thus holds an SMI Chip.
|
||||
With the [SMI UFD Utility](http://ftp.usboffice.kr/files/SMI_UFD_Utility.zip), you can resize the CD partition or even remove it from the stick.
|
||||
|
||||
This way, you can make it e.g. a Windows XP or Windows 7 installation device, use it for the [System Rescue CD](http://www.sysresccd.org/Main_Page) or - if you can trick the *U3 LaunchPad* into
|
||||
accepting the stick - burn the U3 software to it to make it U3 compatible.
|
||||
@ -61,7 +61,7 @@ Notification service using OpenWatch, Tasker and PHP
|
||||
|
||||
Put the following file onto a webserver capable of running PHP scripts (`notify.php`):
|
||||
|
||||
```php
|
||||
{% highlight php %}
|
||||
<?php
|
||||
|
||||
class DataStore {
|
||||
@ -133,9 +133,8 @@ if ( isset( $_REQUEST['l1'] ) && isset( $_REQUEST['l2'] ) ) {
|
||||
echo $entry['line1'] . '¶' . $entry['line2'] . '¶' . $span;
|
||||
}
|
||||
}
|
||||
{% endhighlight %}
|
||||
|
||||
?>
|
||||
```
|
||||
|
||||
### Usage
|
||||
|
||||
|
||||
@ -32,9 +32,8 @@ Temporary fix
|
||||
|
||||
To fix this, you have to disable it or set it to a more reasonable timeout:
|
||||
|
||||
```
|
||||
$ sudo hdparm -S 242 /dev/sdX
|
||||
```
|
||||
|
||||
|
||||
You have to repeat this after each boot, so you may want to add the line to your `/etc/rc.local`.
|
||||
|
||||
@ -47,19 +46,17 @@ For Linux, there's **idle3ctl** from the [idle3-tools](http://idle3-tools.sf.net
|
||||
|
||||
You can display the current value with the following command:
|
||||
|
||||
```
|
||||
$ sudo ./idle3ctl -g /dev/sdX
|
||||
Idle3 timer set to 80 (0x50)
|
||||
```
|
||||
|
||||
|
||||
The value 80 means 8 seconds (default). From 1-128, the values mean 1/10th of a second, e.g. 128 would be 12.8 seconds. 129-254 are in 30 seconds steps. 129 is 30 seconds, 130 is 60 seconds, etc.
|
||||
|
||||
Set the desired value as follows:
|
||||
|
||||
```
|
||||
$ sudo ./idle3ctl -s 158 /dev/sdX
|
||||
Idle3 timer set to 158 (0x9e)
|
||||
Please power cycle your drive off and on for the new setting to be taken into account. A reboot will not be enough!
|
||||
```
|
||||
|
||||
|
||||
Do as it says to enable the new setting.
|
||||
|
||||
BIN
assets/logitech_v400.jpg
Normal file
BIN
assets/logitech_v400.jpg
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 18 KiB |
@ -305,3 +305,22 @@ a {
|
||||
/*background-color: #dfd;*/
|
||||
background-image: url(../images/tip.png);
|
||||
}
|
||||
|
||||
kbd {
|
||||
color: #333;
|
||||
background-color: white;
|
||||
text-align: center;
|
||||
border-left: 1px solid #cfcfcf;
|
||||
border-top: 1px solid #cfcfcf;
|
||||
border-right: 2px solid #666;
|
||||
border-bottom: 2px solid #666;
|
||||
-moz-border-radius: 4px 4px 4px 4px;
|
||||
padding-left: 1px;
|
||||
padding-top: 0px;
|
||||
padding-right: 2px;
|
||||
padding-bottom: 0px;
|
||||
margin-left: 2px;
|
||||
margin-right: 2px;
|
||||
vertical-align: top;
|
||||
font-family: sans-serif;
|
||||
}
|
||||
|
||||
Loading…
Reference in New Issue
Block a user