ThinkWiki - User contributions [en]

How to setup Bluetooth

2009-01-30T19:43:49Z

Xtophe: update url

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#efefef; align:right;">
This HOWTO tells you how to install and configure Bluetooth on your Linux driven ThinkPad and how to make the most common Bluetooth applications (like connecting your mobile phone etc.) work.
</div>
|}

==Enabling Bluetooth==
If Bluetooth is disabled and you have [[Ibm-acpi]] running you could enable/disable bluetooth by entering:
:{{cmdroot|echo enable > /proc/acpi/ibm/bluetooth}}
or
:{{cmdroot|echo disable > /proc/acpi/ibm/bluetooth}}

You should also be able to toggle bluetooth with Fn+F5 keys.

Under Ubuntu Gutsy, in /etc/acpi/ibm-wireless.sh you have to comment "if ! isAnyWirelessPoweredOn; then" and the corresponding "fi" to make the Fn+F5 work.

==Configuring the kernel==
Since the Bluetooth card is connected to the USB subsystem, you will need to enable USB support in your kernel:
:{{kernelconf|CONFIG_USB|<M>|Support for Host-side USB|USB support|Device Drivers||}}
:{{kernelconf|CONFIG_USB_DEVICEFS|[*]|USB device file system|USB support|Device Drivers||}}

Choose an appropriate USB host driver, one of:
:{{kernelconf|CONFIG_USB_EHCI_HCD|<M>|EHCI HCD (USB 2.0) support|USB support|Device Drivers||}}
:{{kernelconf|CONFIG_USB_UHCI|<M>|UHCI HCD support|USB support|Device Drivers||}}
:{{kernelconf|CONFIG_USB_OHCI|<M>|OHCI HCD support|USB support|Device Drivers||}}

Enable Bluetooth subsystem and drivers:
:{{kernelconf|CONFIG_BT|<*>|Bluetooth subsystem support|Networking|||}}
:{{kernelconf|CONFIG_BT_L2CAP|<*>|L2CAP protocol support|Bluetooth subsystem support|Networking||}}
:{{kernelconf|CONFIG_BT_SCO|<*>|SCO links support|Bluetooth subsystem support|Networking||}}
:{{kernelconf|CONFIG_BT_RFCOMM|<*>|RFCOMM protocol support|Bluetooth subsystem support|Networking||}}
:{{kernelconf|CONFIG_BT_RFCOMM_TTY|[*]|RFCOMM TTY support|Bluetooth subsystem support|Networking||}}
:{{kernelconf|CONFIG_BT_BNEP|<*>|BNEP protocol support|Bluetooth subsystem support|Networking||}}
:{{kernelconf|CONFIG_BT_HID|<*>|HID protocol support|Bluetooth subsystem support|Networking||}}
:{{kernelconf|CONFIG_BT_HCIUSB|<M>|HCI USB driver|Bluetooth device drivers|Bluetooth subsystem support|Networking|}}
:{{kernelconf|CONFIG_BT_HCIUSB_SCO|[*]|SCO (voice) support|Bluetooth device drivers|Bluetooth subsystem support|Networking|}}

Make sure that the according modules are loaded:
:{{cmdroot|modprobe uhci_hcd ; modprobe ehci_hcd ; modprobe hci_usb}}

==Serial connection over Bluetooth==
One common application is to connect your mobile phone and use it as a modem to connect to the internet via GPRS or 3G (UMTS). A lot of phones do this through using AT-commands on a serial over Bluetooth connection.

By configuring {{path|/etc/bluetooth/rfcomm.conf}} correctly, you'll get a device {{path|/dev/rfcomm0}}.

Eventually one could use the command:
:{{cmdroot|rfcomm bind 0 00:15:A0:7A:90:F2 3}}

The hardware address should be replaced with that of your phone. If you don't know the hardware address of your phone yet, you can get it by running:
:{{cmdroot|hcitool scan}}

The last parameter ('3') is the channel to use. I spent quite some time fighting before I found out of that one; I didn't find it documented anywhere, but by running
:{{cmdroot|sdptool records 00:15:A0:7A:90:F2}}
I found channel 3 to be the right one for my phone. You will have to experiment to find the right one for your phone setup; for T-Mobile GSM/GPRS carrier in USA this is channel 1.
{{NOTE|By experimenting, the bluetooth stack on the cellphone may crash. Reboot it if that happens.}}

Alternativly one could use the following to find the right channel:
:{{cmdroot|sdptool search DUN}}

Inquiring ...
Searching for DUN on 00:11:22:33:44:55 ...
Service Name: Dial-up Networking
Service RecHandle: 0x10001
Service Class ID List:
"Dialup Networking" (0x1103)
"Generic Networking" (0x1201)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 4

Now {{path|/dev/rfcomm0}} exists.

At this point you can use an automatic dialing utility such as wvdial, editing the config file to point to the modem at {{path|/dev/rfcomm0}}, and everything should work just like a land line!

{{NOTE|If you experience strange disconnects while using wvdial, disable "Carrier Check" in your wvdial configuration.}}

You may directly access the modem (i.e. by using minicom:)
:{{cmduser|minicom -s}}
set the serial device to be {{path|/dev/rfcomm0}}, choose 'exit' and then the AT-commands can be typed in.
With my operator (Telenor, Norway) it seemed simple enough, I just entered
:ATDT *99#
and lots of cryptic letters started dancing across the screen, indicating a ppp session startup.

To configure pppd create {{path|/etc/ppp/peers/nokia}} with particularly those lines:
/dev/rfcomm0
connect '/usr/sbin/chat -v -f /etc/ppp/chat-nokia'
debug
10.0.1.3
crtscts
noipdefault
ipcp-accept-local
defaultroute
novj
nobsdcomp
novjccomp
nopcomp
noaccomp
usepeerdns

Furthermore, you need a simple chat script. Create {{path|/etc/ppp/chat-nokia}}:
'TIMEOUT' '5'
'ABORT' 'BUSY'
'ABORT' 'ERROR'
'ABORT' 'NO ANSWER'
'ABORT' 'NO CARRIER'
'ABORT' 'NO DIALTONE'
'ABORT' 'Invalid Login'
'ABORT' 'Login incorrect'
'' 'ATZ'
'OK' 'ATDT*99#'
'~--' ''

Here's a script that works for Cingular's network:
TIMEOUT 35
ECHO ON
ABORT '\nBUSY\r'
ABORT '\nERROR\r'
ABORT '\nNO ANSWER\r'
ABORT '\nNO CARRIER\r'
ABORT '\nNO DIALTONE\r'
ABORT '\nRINGING\r\n\r\nRINGING\r'
'' \rAT
OK 'AT+CGDCONT=1,"IP","WAP.CINGULAR"'
OK ATD*99***1#
CONNECT ""

See more [https://help.ubuntu.com/community/BluetoothDialup#preview here]

Run pppd with:
:{{cmduser|pppd call nokia}}
This should establish the internet connection.

{{NOTE|Different network operators may require different call strings. For many carriers (including T-Mobile USA) "*99#" works without additional parameters.}}

For editing phonebook / ringtones / etc., the gammu utils (http://www.gamu.net) has been reported to work well, but this appears to be primarily for Nokia phones.

==File Transfer==
File transfers are accomplished through OBEX transfer, which I believe is basically an FTP over bluetooth connection. Once you have bonded with your phone (yes, I know you love your sexy RAZR, but here I mean paired it with your laptop via bluetooth), you can easily use "obexftp" to transfer files. As an example,

:obexftp -b 00:01:02:03:04:05 -l

will list the root directory of the phone with bluetooth address 00:01:02:03:04:05. Refer to the man page for more of the unique commands. What a wonderful interface! Unfortunately there doesn't seem to be a way to get a standard 'ftp' session using familiar commands (e.g. 'mget').

For a more user-friendly experience, you can use the kde tools, just launch
:kbtobexclient

for a file browser. In the Location: option put
:obex://[00:01:02:03:04:05]

to list the files. Note that the brackets *are* necessary. From there, you can list directories easily and batch download files.

==Mount a phone as a directory==
You can also mount a phone as a standard directory using obexfs and the FUSE (file system in userspace) utilities.

{{NOTE|The ibm bluetooth card can work like an usb-dongle. You don't need the bcm203x module.}}

Configure your kernel as outlined above.

* Install the required packages
To mount the filesystem we need the fuse program. FuseFS is also implemented in the kernel, but for some reason it only works with 2.6.18. If you run 2.6.17 or earlier, please download it and build the module according to your distro.

* Emerge or apt-get bluez-utils and obexfs. This should pull other required packages (bluez-libs, openobex, obexftp, sys-fs/fuse) as dependencies.

:{{cmdroot|emerge bluez-utils obexfs}}

* Modify /etc/bluetooth/hcid.conf if you haven't already. It can be done as above, or use the following:
options {
autoinit yes"
security user
pairing multi
pin_helper /usr/bin/bluepin
}
device {
name testname
class 0x3e0100
iscan enable
pscan enable
lm accept
lp rswitch,hold,sniff,park
}

* load the modules:
:{{cmdroot|modprobe fuse}}
:{{cmdroot|modprobe bluetooth}}
:{{cmdroot|modprobe ehci-hcd}}
:{{cmdroot|modprobe uhci-hcd}}
:{{cmdroot|modprobe hci_usb}}
:{{cmdroot|modprobe l2cap}}
:{{cmdroot|modprobe rfcomm}}

* activate your bluetooth (show howto ibm-acpi for more details) by using fn+f5 or:
:{{cmdroot|echo enable >/proc/acpi/ibm/bluetooth}}

* start the bluetooth device:
:{{cmdroot|/etc/init.d/bluetooth start}}

* turn on bluetooth of your mobile phone (visible mode) and get the mac-address of your phone using hcitool.
:{{cmdroot|hcitool scan}}

=== For non symbian mobile phones ===

* mount your phone - don't forget to umount it when you're finished
:{{cmdroot|mkdir /mnt/phone}}
:{{cmdroot|mount -t fuse "obexfs#-b00:16:20:32:25:3C -B6" /mnt/phone}}
''use your mac-address instead of my 00:16:20:32:25:3C and don't forget the -b option in front of the mac''

Works perfectly with IBM T43p, X41, sony ericsson k750i, nokia 6280, samsung z400, sony ericsson k700i.

=== Mounting Symbian Phones ===

* You need network file system support in your kernel

:{{cmdroot|cd /usr/src/linux}}
:{{cmdroot|make menuconfig}}

:{{kernelconf|NFS_FS|<M>|NFS file system support|Network File Systems|File Systems|||}}
:{{kernelconf|NFS_V3|<M>|Provide NFSv3 client support|Network File Systems|File Systems|||}}

:{{kernelconf|NFSD|<M>|NFS server support|Network File Systems|File Systems|||}}
:{{kernelconf|NFSD_V3|<*>|Provide NFSv3 server support|Network File Systems|File Systems|||}}
:{{kernelconf|NFSD_TCP|<*>|Provide NFS server over TCP support|Network File Systems|File Systems|||}}

:{{cmdroot|make && make modules_install}}

* Install required programs

:{{cmdroot|emerge -av p3nfs}}

* Modify your /etc/bluetooth/rfcomm.conf

rfcomm0 {
bind yes;
device 00:0F:DE:8C:E6:94;
channel 13;
comment "symbian connection"
}

* restart your bluetooth device, load kernel modules and start portmap (required for p3nfs)

:{{cmdroot|/etc/init.d/bluetooth restart}}
:{{cmdroot|modprobe nfs}}
:{{cmdroot|modprobe nfsd}}

:{{cmdroot|/etc/init.d/portmap start}}

* get the application for your mobile phone [http://www.koeniglich.de/p3nfs.html here]

* start bt at your mobile phone, send application to mobilephone, install and launch the nfsapp with bluetooth at channel 13 (default)

:{{cmdroot|obexftp -b 00:0F:DE:8C:E6:94 -p /home/tava/ablage/nfsapp*}}

* mount your mobile phone:

:{{cmdroot|p3nfsd -UIQ -tty /dev/rfcomm0 -dir /mnt/bluetooth}} (-UIQ is only for UIQ-Phones, type p3nfsd --help and get informations for your phone)

* if doesn't work, make sure rfcomm0 is clean

:{{cmdroot|rfcomm}}

----

===Building from source===
Get the source packages from [http://www.bluez.org www.bluez.org].

Build each of them with the usual steps:
:{{cmduser|./configure && make}}
:{{cmdroot|make install}}

===Gentoo ebuilds===
Under {{Gentoo}}, install the following ebuilds:
*net-wireless/bluez-bluefw
*net-wireless/bluez-firmware
*net-wireless/bluez-hcidump
*net-wireless/bluez-hciemu
*net-wireless/bluez-libs
*net-wireless/bluez-utils

{{NOTE|net-wireless/bluez-kernel is not needed, since the current version is included in your kernel.}}

===Other distributions===
You will find packages for {{Debian}}, {{Redhat}} and {{Slackware}} on the [http://www.bluez.org/packages.html packages page] of the BlueZ project.

Bluez packages are included in Debian Sid (bluez-utils, and non-free package bluez-firmware).

==Troubleshooting==
If you cant get hci0 up with a /etc/init.d/bluetooth restart (or similar) then you might want to try a
:{{cmdroot|hciconfig hci0 down && hciconfig hci0 up}}
(solved the problem on a X60s and T60 (debian/testing))

==External Links==
*[http://www.holtmann.org/linux/bluetooth/ Bluetooth and Linux]: Marcel Holtmann's list of bluetooth HOWTOs.
*http://gagravarr.org/series-60/
*http://koti.kapsi.fi/mcfrisk/linux_gprs.html
*[http://www.gentoo.org/doc/en/bluetooth-guide.xml Guide on how to set up Bluetooth in Gentoo]
*[http://www.linux.ie/articles/bluetoothheadset.php www.linux.ie:Linux and Bluetooth Headset howto (AKA: Fedora, BTSCO, Bluez, Jabra and Skype)]

[[Category:A30]] [[Category:A30p]] [[Category:A31]] [[Category:A31p]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:T60]] [[Category:T60p]] [[Category:T61]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]] [[Category:X60]] [[Category:X60s]] [[Category:Z60m]] [[Category:Z60t]]

Table of thinkpad-acpi LEDs

2006-10-23T19:25:15Z

Xtophe: T43p

This table contains informations about which LED number is used for which LED in the [[ibm-acpi]] driver.

To test please do the following and add the blinking LED to the table.

<pre>
echo "0 blink" > /proc/acpi/ibm/led
echo "1 blink" > /proc/acpi/ibm/led
echo "2 blink" > /proc/acpi/ibm/led
echo "3 blink" > /proc/acpi/ibm/led
echo "4 blink" > /proc/acpi/ibm/led
echo "5 blink" > /proc/acpi/ibm/led
echo "6 blink" > /proc/acpi/ibm/led
echo "7 blink" > /proc/acpi/ibm/led
</pre>

<div style="font-size: 92%">
{| border="1" cellspacing="0" cellpadding="2"
|+ibm-acpi LED table
|-
! ×
! LED #0
! LED #1
! LED #2
! LED #3
! LED #4
! LED #5
! LED #6
! LED #7
! Notes
|-
! colspan=10 style="text-align:center;background:#efefef;" |
|-
! {{A22p}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{A30}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! colspan=10 style="text-align:center;background:#efefef;" |
|-
! {{G41}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! colspan=10 style="text-align:center;background:#efefef;" |
|-
! [[:Category:R31|R31]]
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{R40}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{R50}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{R50p}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{R50e}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || Amber Thinklight
|-
! {{R51}}
| Power || Battery(orange) || Battery(green) || {{Cunk}} || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || 2883-ELU, Amber Thinklight
|-
! {{R52}}
| Power(green) || Battery(orange) || Battery(green) || {{Cunk}} || Ultrabay || {{Cunk}} || {{Cunk}} || Standby ||
|-
! {{R60}}
| Power || Battery(orange) || Battery(green) || {{Cunk}} || {{Cunk}} || {{Cunk}} || Standby || {{Cunk}} ||
|-
! {{R60}}
| Power || Battery(orange) || Battery(green) || {{Cunk}} || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || 9456-6FG, Amber ThinkLight
|-

! colspan=10 style="text-align:center;background:#efefef;" |

|-
! {{T20}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{T22}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{T23}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{T30}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{T40}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{T40p}}
| Power || Battery(orange) || Battery(green) || {{Cunk}} || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || Standard
|-
! {{T41}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{T41p}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{T42}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{T42p}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{T43}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{T43p}}
| Power || Battery (orange) || Battery (green) || {{Cunk}} || Ultrabay || {{Cunk}} || {{Cunk}} || Standby ||
|-
! {{T60}}
| Power || Battery(orange) || Battery(green) || {{Cunk}} || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || 2007-49G
|-
! colspan=10 style="text-align:center;background:#efefef;" |

|-
! {{X20}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{X24}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{X31}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{X32}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{X40}}
| Power || Battery(orange) || Battery(green) || Ultrabase || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || Standard
|-
! {{X41}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{X60}}
| Power || Battery(orange) || Battery(green) || Ultrabase || Ultrabay || {{Cunk}} || {{Cunk}} || Standby || Standard
|-
! colspan=10 style="text-align:center;background:#efefef;" |

|-
! {{Z60t}}
| {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} ||
|-
! {{Z61m}}
| Power || Battery(orange) || Battery(green) || {{Cunk}} || {{Cunk}} || {{Cunk}} || {{Cunk}} || Standby ||
</div>

Talk:How to change the BIOS bootsplash screen

2006-02-24T19:14:15Z

Xtophe: brocken link

Q:What happens if the laptop is protected by fingerprint/password?
Will I need to enter the password first, or can I reboot from a CD even without the password?

A:On a T43p it will allow you to upgrade the BIOS after you swipe your fingerprint or input the password. The upgrade *does not* erase the password/biometric information you had on file. (Very useful, as the utility to enroll fingerprint was deleted when I wiped Windows for Linux...)

If you don't have the fingerprint / password, well, umm... what happened to your finger? :)

---

Anyone know if this works on a T20? There's no mention of it in the article, and I can't find any mention of "BIOS splash(screen)" at htpp://ibm.com<br>
- I'd be grateful if you could email me at stroller at bigfoot dot com if you know the answer to this

---

Q:Hm, where to get the prepare.exe? It's not included in the BIOS upgrade disk of my i1200. But, of coursem one has to keep in mind that the i1200 is equiped with an ACER BIOS, so the described procedure may not work at all. Heck, I'll just try it out using the sample mod file, off for rebooting ... wich doesn't work because - i fear - my CD drive is again going downhill.

A: Prepare.exe is found in the compressed cab file 1yu****.exe (BIOS upgrade file from IBM). It is used by corporations so they can equip their fleets with custom bootsplash screens like we do at work...

== Changing logos! ==
An interesting bit of trivia - the superimposed "Centrino" logo will change to a superimposed "Pentium M" logo if you disable the wi-fi networking in the BIOS. The "Centrino" label requires wireless networking... :)
[[User:gsmenden|gsmenden]] 19:33 11 Feb 2006 (EST)

== Brocken Link ==
I can't access logo.bmp and logo.mod. anybody know where they are now ? --[[User:Xtophe|Xtophe]] 20:14, 24 February 2006 (CET)

Talk:How to change the BIOS bootsplash screen

2006-02-24T19:12:28Z

Xtophe: brocken link

How to change the BIOS bootsplash screen

2006-02-24T19:01:52Z

Xtophe: protect *.IMG from shell expansion