https://www.thinkwiki.org/w/api.php?action=feedcontributions&user=82.47.145.14&feedformat=atomThinkWiki - User contributions [en]2024-03-28T12:35:01ZUser contributionsMediaWiki 1.31.12https://www.thinkwiki.org/w/index.php?title=Problem_with_3Com_10/100_Ethernet_card_not_being_recognized&diff=5969Problem with 3Com 10/100 Ethernet card not being recognized2005-06-14T00:08:41Z<p>82.47.145.14: /* Revised Perl script */</p>
<hr />
<div>Information about the problem of non-recognized 3Com Ethernet card when using ACPI with 2.6 kernels.<br />
<br />
==Problem description==<br />
When using a 2.6 kernel with ACPI enabled, the card is not recognized properly. In fact the kernel finds the card and tries to enable it but gives an error message in dmesg output.<br />
<br />
==Affected Models==<br />
* {{A20m}}, {{A20p}}, {{A21e}}, {{A21m}}<br />
* {{A30}}, {{A30p}}, {{A31}}, {{A31p}}<br />
* {{T20}}, {{T21}}, {{T22}}<br />
* {{X20}}, {{X21}}, {{X22}}<br />
<br />
==Affected Operating Systems==<br />
*all Linux flavours<br />
<br />
==Status==<br />
This is a problem of the ACPI subsystem interfering with the PCI resource management.<br />
<br />
==Solutions==<br />
Try one of the following kernel parameters (in that order):<br />
*<tt>nolapic</tt> (disables support for local apic)<br />
*<tt>acpi=nopci</tt> (disables PCI resource control of the ACPI subsystem)<br />
*<tt>acpi=off</tt> (completely disables ACPI, should always work)<br />
<br />
===Alternative to disabling ACPI===<br />
It is possible to get the ethernet controller of the 3Com combo card working with ACPI enabled by using the setpci command. Since it requires an IO port address that may change each boot, this Perl script will help to automate things. It has only been tested under the 2.6.12-rc5-mm2 and 2.6.12-rc6 kernels with the 3c59x driver compiled as a module. It may break with different versions of the lspci command (tested with 2.1.11).<br />
<br />
#!/usr/bin/perl<br />
<br />
use strict;<br />
<br />
my $DRIVER = "3c59x";<br />
my $VENDOR = "10b7";<br />
my $DEVICE = "6056";<br />
my $LSPCI = `lspci -vd $VENDOR:$DEVICE | grep "I/O ports"`;<br />
<br />
print "Resetting 3Com ethernet controller... ";<br />
if($LSPCI =~ m|I/O ports at (\d{4})|i) {<br />
my $io = sprintf("%x", (hex $1) + 1);<br />
`rmmod $DRIVER`;<br />
`setpci -H1 -d $VENDOR:$DEVICE COMMAND=0x07 CACHE_LINE_SIZE=0 LATENCY_TIMER=0x40 BASE_ADDRESS_0=0x$io`;<br />
`modprobe $DRIVER`;<br />
print "done.\n";<br />
} else {<br />
print "failed.\n";<br />
}</div>82.47.145.14https://www.thinkwiki.org/w/index.php?title=Problem_with_3Com_10/100_Ethernet_card_not_being_recognized&diff=5673Problem with 3Com 10/100 Ethernet card not being recognized2005-06-13T23:39:09Z<p>82.47.145.14: /* Alternative to disabling ACPI */</p>
<hr />
<div>Information about the problem of non-recognized 3Com Ethernet card when using ACPI with 2.6 kernels.<br />
<br />
==Problem description==<br />
When using a 2.6 kernel with ACPI enabled, the card is not recognized properly. In fact the kernel finds the card and tries to enable it but gives an error message in dmesg output.<br />
<br />
==Affected Models==<br />
* {{A20m}}, {{A20p}}, {{A21e}}, {{A21m}}<br />
* {{A30}}, {{A30p}}, {{A31}}, {{A31p}}<br />
* {{T20}}, {{T21}}, {{T22}}<br />
* {{X20}}, {{X21}}, {{X22}}<br />
<br />
==Affected Operating Systems==<br />
*all Linux flavours<br />
<br />
==Status==<br />
This is a problem of the ACPI subsystem interfering with the PCI resource management.<br />
<br />
==Solutions==<br />
Try one of the following kernel parameters (in that order):<br />
*<tt>nolapic</tt> (disables support for local apic)<br />
*<tt>acpi=nopci</tt> (disables PCI resource control of the ACPI subsystem)<br />
*<tt>acpi=off</tt> (completely disables ACPI, should always work)<br />
<br />
===Alternative to disabling ACPI===<br />
It is possible to get the ethernet controller of the 3Com combo card working with ACPI enabled by using the setpci command. Since it requires PCI bus and IO port addresses that change each boot, this Perl script automates things. It has only been tested under the 2.6.12-rc5-mm2 and 2.6.12-rc6 kernels with the 3c59x driver compiled as a module. It may break with different versions of the lspci command (tested with 2.1.11).<br />
<br />
#!/usr/bin/perl<br />
use strict;<br />
my $DRIVER = "3c59x";<br />
my $LSPCI = `lspci -v -d 10b7: | grep -A3 Ethernet`;<br />
print "Resetting 3Com ethernet controller... ";<br />
if($LSPCI =~ /[0-9a-f]{4}:([0-9a-f]{2}:[0-9a-f]{2}.[0-9a-f]).*?I\/O ports at (\d{4})/is) {<br />
my $bus = $1;<br />
my $io = sprintf("%x", (hex $2) + 1);<br />
`rmmod $DRIVER`;<br />
`setpci -v -H 1 -s $bus COMMAND=0x07 CACHE_LINE_SIZE=0 LATENCY_TIMER=0x40 BASE_ADDRESS_0=0x$io >/dev/null`;<br />
`modprobe $DRIVER`;<br />
print "done.\n";<br />
} else {<br />
print "failed.\n";<br />
}</div>82.47.145.14https://www.thinkwiki.org/w/index.php?title=CS4281&diff=6381CS42812005-06-13T23:33:07Z<p>82.47.145.14: </p>
<hr />
<div>__NOTOC__<br />
{| width="100%"<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== CS4281 ===<br />
This is a Cirrus Logic Audio controller<br />
<br />
Note: This chip is paired with a CS4297A AC'97 Audio controller, only one sound driver should be loaded.<br />
<br />
=== Features ===<br />
* Chipset: CS4281<br />
* Interface: PCI<br />
* PCI ID: 1013:6005<br />
</div><br />
|style="vertical-align:top" |<br />
|}<br />
<br />
=== Linux OSS driver ===<br />
This sound chip is supported by the cs4281 kernel module.<br />
<br />
=== Linux ALSA driver ===<br />
This sound chip is supported by the snd-cs4281 kernel module.<br />
<br />
=== ThinkPads in which this chip may be found ===<br />
* {{240X}}<br />
* {{TransNote}}<br />
* {{X20}}, {{X21}}<br />
<br />
[[Category:Components]]</div>82.47.145.14https://www.thinkwiki.org/w/index.php?title=CS4281&diff=5671CS42812005-06-13T23:32:34Z<p>82.47.145.14: /* Linux OSS driver */</p>
<hr />
<div>__NOTOC__<br />
{| width="100%"<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== CS4281 ===<br />
This is a Cirrus Logic Audio controller<br />
<br />
Note: This chip is paired with a CS4297A AC'97 Audio controller, only one sound driver should be loaded.<br />
<br />
=== Features ===<br />
* Chipset: CS4281<br />
* Interface: PCI<br />
* PCI ID: 1013:6005<br />
</div><br />
|style="vertical-align:top" |<br />
|}<br />
<br />
=== Linux OSS driver ===<br />
This sound chip is supported by the cs4281 kernel module.<br />
<br />
=== Linux ALSA driver ===<br />
This sound chip is supported by the snd-cs46xx kernel module.<br />
<br />
=== ThinkPads in which this chip may be found ===<br />
* {{240X}}<br />
* {{TransNote}}<br />
* {{X20}}, {{X21}}<br />
<br />
[[Category:Components]]</div>82.47.145.14https://www.thinkwiki.org/w/index.php?title=CS4281&diff=5670CS42812005-06-13T23:32:09Z<p>82.47.145.14: /* Features */</p>
<hr />
<div>__NOTOC__<br />
{| width="100%"<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== CS4281 ===<br />
This is a Cirrus Logic Audio controller<br />
<br />
Note: This chip is paired with a CS4297A AC'97 Audio controller, only one sound driver should be loaded.<br />
<br />
=== Features ===<br />
* Chipset: CS4281<br />
* Interface: PCI<br />
* PCI ID: 1013:6005<br />
</div><br />
|style="vertical-align:top" |<br />
|}<br />
<br />
=== Linux OSS driver ===<br />
This sound chip is supported by the cs46xx kernel module.<br />
<br />
=== Linux ALSA driver ===<br />
This sound chip is supported by the snd-cs46xx kernel module.<br />
<br />
=== ThinkPads in which this chip may be found ===<br />
* {{240X}}<br />
* {{TransNote}}<br />
* {{X20}}, {{X21}}<br />
<br />
[[Category:Components]]</div>82.47.145.14https://www.thinkwiki.org/w/index.php?title=CS4281&diff=5669CS42812005-06-13T23:31:43Z<p>82.47.145.14: /* CS4281 */</p>
<hr />
<div>__NOTOC__<br />
{| width="100%"<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== CS4281 ===<br />
This is a Cirrus Logic Audio controller<br />
<br />
Note: This chip is paired with a CS4297A AC'97 Audio controller, only one sound driver should be loaded.<br />
<br />
=== Features ===<br />
* Chipset: CS4681<br />
* Interface: PCI<br />
* PCI ID: 1013:6005<br />
</div><br />
|style="vertical-align:top" |<br />
|}<br />
<br />
=== Linux OSS driver ===<br />
This sound chip is supported by the cs46xx kernel module.<br />
<br />
=== Linux ALSA driver ===<br />
This sound chip is supported by the snd-cs46xx kernel module.<br />
<br />
=== ThinkPads in which this chip may be found ===<br />
* {{240X}}<br />
* {{TransNote}}<br />
* {{X20}}, {{X21}}<br />
<br />
[[Category:Components]]</div>82.47.145.14https://www.thinkwiki.org/w/index.php?title=CS4281&diff=5634CS42812005-06-09T22:32:52Z<p>82.47.145.14: /* ThinkPads in which this chip may be found */</p>
<hr />
<div>__NOTOC__<br />
{| width="100%"<br />
|style="vertical-align:top" |<br />
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;"><br />
=== CS4681 ===<br />
This is a Cirrus Logic Audio controller<br />
<br />
Note: This chip is paired with a CS4297A AC'97 Audio controller, only one sound driver should be loaded.<br />
<br />
=== Features ===<br />
* Chipset: CS4681<br />
* Interface: PCI<br />
* PCI ID: 1013:6005<br />
</div><br />
|style="vertical-align:top" |<br />
|}<br />
<br />
=== Linux OSS driver ===<br />
This sound chip is supported by the cs46xx kernel module.<br />
<br />
=== Linux ALSA driver ===<br />
This sound chip is supported by the snd-cs46xx kernel module.<br />
<br />
=== ThinkPads in which this chip may be found ===<br />
* {{240X}}<br />
* {{TransNote}}<br />
* {{X20}}<br />
<br />
[[Category:Components]]</div>82.47.145.14https://www.thinkwiki.org/w/index.php?title=Problem_with_3Com_10/100_Ethernet_card_not_being_recognized&diff=5672Problem with 3Com 10/100 Ethernet card not being recognized2005-06-08T11:44:13Z<p>82.47.145.14: /* Solutions */</p>
<hr />
<div>Information about the problem of non-recognized 3Com Ethernet card when using ACPI with 2.6 kernels.<br />
<br />
==Problem description==<br />
When using a 2.6 kernel with ACPI enabled, the card is not recognized properly. In fact the kernel finds the card and tries to enable it but gives an error message in dmesg output.<br />
<br />
==Affected Models==<br />
* {{A20m}}, {{A20p}}, {{A21e}}, {{A21m}}<br />
* {{A30}}, {{A30p}}, {{A31}}, {{A31p}}<br />
* {{T20}}, {{T21}}, {{T22}}<br />
* {{X20}}, {{X21}}, {{X22}}<br />
<br />
==Affected Operating Systems==<br />
*all Linux flavours<br />
<br />
==Status==<br />
This is a problem of the ACPI subsystem interfering with the PCI resource management.<br />
<br />
==Solutions==<br />
Try one of the following kernel parameters (in that order):<br />
*<tt>nolapic</tt> (disables support for local apic)<br />
*<tt>acpi=nopci</tt> (disables PCI resource control of the ACPI subsystem)<br />
*<tt>acpi=off</tt> (completely disables ACPI, should always work)<br />
<br />
===Alternative to disabling ACPI===<br />
I managed to get the ethernet controller of the 3Com combo card in my X20 working with ACPI enabled by using the setpci command. Since it requires PCI bus and IO port addresses that change each boot, I wrote a Perl script to automate things. This has only been tested under the 2.6.12-rc5-mm2 kernel with the 3c59x driver compiled as a module. It may break with different versions of the lspci command (2.1.11 used).<br />
<br />
#!/usr/bin/perl<br />
use strict;<br />
my $DRIVER = "3c59x";<br />
my $LSPCI = `lspci -v -d 10b7: | grep -A3 Ethernet`;<br />
print "Resetting 3Com ethernet controller... ";<br />
if($LSPCI =~ /[0-9a-f]{4}:([0-9a-f]{2}:[0-9a-f]{2}.[0-9a-f]).*?I\/O ports at (\d{4})/is) {<br />
my $bus = $1;<br />
my $io = sprintf("%x", (hex $2) + 1);<br />
`rmmod $DRIVER`;<br />
`setpci -v -H 1 -s $bus COMMAND=0x07 CACHE_LINE_SIZE=0 LATENCY_TIMER=0x40 BASE_ADDRESS_0=0x$io >/dev/null`;<br />
`modprobe $DRIVER`;<br />
print "done.\n";<br />
} else {<br />
print "failed.\n";<br />
}</div>82.47.145.14https://www.thinkwiki.org/w/index.php?title=BIOS_Upgrade&diff=5878BIOS Upgrade2005-06-08T10:53:55Z<p>82.47.145.14: /* Does work: */</p>
<hr />
<div>__TOC__<br />
----<br />
<br />
==Before You Begin==<br />
<br />
This page is meant to describe ways to update the BIOS on a Thinkpad that only runs Linux for users that don't have ready access to Windows (if you have Windows on your thinkpad you can just boot into it and follow instructions on the IBM website). Updating the BIOS in Linux (with few exceptions) '''is not officially supported''' by IBM. However there are work arounds. By following any of the instructions here you are accepting the '''very real risk''' of turning your thinkpad into a big expensive paper weight, as a firmware update gone wrong can create unfixable problems. <br />
<br />
'''Proceed at your own risk!'''<br />
<br />
It is also '''important''' to understand that all newer thinkpads have 2 seperate firmwares, the BIOS and the Control Program. A specific version of the Control Program will only work with specific versions of the BIOS. If you go through the readme's on the IBM site they'll cleary state that '''you must''' update the Control Program first, then imediately update the BIOS. Otherwise you risk turning your thinkpad into a very nice paper weight.<br />
<br />
==BIOS Upgrade Paths==<br />
<br />
For every firmware (either BIOS or Control Program) update on the IBM site there are two different firmware update programs provided.<br />
<br />
===The Diskette Updater===<br />
<br />
This installer appears to be a 16bit dos program which asks you to accept a license agreement. It will run in Windows, DOS, OS/2, or [http://dosemu.sf.net Dosemu] perfectly, but requires a real floppy disk attached via a real floppy control. The USB Floppy Drive to the new Thinkpads doesn't count.<br />
<br />
===The Non Diskette Updater===<br />
<br />
'''Warning: Though I've used this process on 1 version of .exe files found on ibm.com website this doesn't mean it will work for all of them. Use at your own risk'''<br />
<br />
This installer appears to be a 32bit windows exe which is designed for updating the BIOS directly from a running Windows OS. It turns out that the .exe is really a wrapper license program arround windows .cab files (this information is in [[How_to_change_the_BIOS_bootsplash_screen|BIOS-Bootsplash]]). If you install the Linux program '''cabextract''' you can expand these files directly. Run the following:<br />
<br />
cabextract FILENAME.exe<br />
<br />
You will get 8 files in the current directory. One of them will be FILENAME.img. You can test that this is really a floppy image by running:<br />
<br />
mkdir mntfloppy<br />
mount -o loop FILENAME.img mntfloppy<br />
ls -la mntfloppy<br />
<br />
If the results of ls -la look like a dos floppy, and no read errors were displayed, you have a pretty good chance that the floppy image is usable. Again, proceed at your own risk.<br />
<br />
==Updating from within Windows==<br />
<br />
If you have windows on your machine... you probably never found this page anyway as you wouldn't need it. ;) However updating the BIOS from Windows is very easy, and the supported way to do it by IBM. Simply follow the IBM instructions, as described on the respective BIOS upgrade page on the IBM site.<br />
<br />
Note that in one case ([[APM setup on a type 2379 Thinkpad T40]]) it was not possible to upgrade the BIOS from Windows XP; a downgrade to Windows 98 was required to successfully run the BIOS upgrade app. The symptoms in this case were that, once the files had been extracted to the hard disk, and the machine was to reboot into the upgrade app, it would beep and hang just before reboot, requiring a power cycle. Once the power was cycled, it would simply reboot back into XP without performing any BIOS upgrade actions. So even if you have Windows, you may still need to use the info on this page.<br />
<br />
==Downloads==<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
| rowspan="3"| '''Models'''<br />
| colspan="2"| '''Non-Diskette'''<br />
| colspan="3"| '''Diskette'''<br />
|-<br />
| rowspan="2"| '''BIOS'''<br />
| rowspan="2"| '''Embedded Controller Program'''<br />
| colspan="2"| '''BIOS'''<br />
| rowspan="2"| '''Embedded Controller Program'''<br />
|-<br />
| '''Windows'''<br />
| '''Linux'''<br />
|-<br />
| {{390}}<br />
|<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1DSHY-427MCG 5.62]<br />
|<br />
|<br />
|-<br />
| {{390E}}<br />
|<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1DSHY-46AKPY 1.55]<br />
|<br />
|<br />
|-<br />
| {{390X}}<br />
|<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4C5UP9 0.55]<br />
|<br />
|<br />
|-<br />
| {{560X}}<br />
|<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1DSHY-3QYK7L 1.15]<br />
|<br />
|<br />
|-<br />
| {{560Z}}<br />
|<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1DSHY-3YTKKV 1.07]<br />
|<br />
|<br />
|-<br />
| {{570}}<br />
|<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-47JS5Z 1.16]<br />
|<br />
|<br />
|-<br />
| {{570E}}<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4HT3RD 1.07]<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4HA2BF 1.07]<br />
|<br />
|<br />
|-<br />
| {{600}}<br />
|<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1DSHY-3VRJPK 1.22]<br />
|<br />
|<br />
|-<br />
| {{600E}} (2645 selected models, 2646)<br />
|<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1DSHY-46HLKQ 1.16]<br />
|<br />
|<br />
|-<br />
| {{600E}} (2645: 55x, 56x, 57x, 58x, A5x, A6x, Bxx [except for BAU], JJ1, JJ2, RRA)<br />
|<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1DSHY-43DNQ5 1.15]<br />
|<br />
|<br />
|-<br />
| {{600X}}<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4HVUYL 1.11]<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4FYS2U 1.11]<br />
|<br />
|<br />
|-<br />
| {{770}}, {{770E}}, {{770ED}}<br />
|<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1DSHY-3P2MCB 1.34]<br />
|<br />
|<br />
|-<br />
| {{770X}}<br />
|<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1DSHY-42QLVU 1.10]<br />
|<br />
|<br />
|-<br />
| {{770Z}}<br />
|<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-47F3VA 1.05]<br />
|<br />
|<br />
|-<br />
| {{A20m}}<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4MNN8Z 1.13]<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4JWNTQ 1.13]<br />
|<br />
|<br />
|-<br />
| {{A20p}}<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4MNN8Y 1.11]<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4JWNTR 1.11]<br />
|<br />
|<br />
|-<br />
| {{A21e}} (2165)<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4UNQKX 1.07]<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4UNRRF 1.07]<br />
|<br />
|<br />
|-<br />
| {{A21e}} (2628)<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4Q2KLU 1.13]<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4Q2KLV 1.13]<br />
|<br />
|<br />
|-<br />
| {{A21m}}<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4PJMXK 1.09]<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4Q2KM4 1.09]<br />
|<br />
|<br />
|-<br />
| {{A21p}}<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4Q2KM3 1.11]<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4PJN8X 1.11]<br />
|<br />
|<br />
|-<br />
| {{A22e}} Celeron<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4UNQKX 1.07]<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4UNRRF 1.07]<br />
|<br />
|<br />
|-<br />
| {{A22e}} Pentium<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4XQKLK 1.05]<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4XQL7B 1.05]<br />
|<br />
|<br />
|-<br />
| {{A22m}}<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4Q2KM4 1.09]<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4PJMXK 1.09]<br />
|<br />
|<br />
|-<br />
| {{A22m}} (2628-Sxx)<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4VXS2T 1.05]<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4VXRG4 1.05]<br />
|<br />
|<br />
|-<br />
| {{A22p}}<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4Q2KM3 1.11]<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4PJN8X 1.11]<br />
|<br />
|<br />
|-<br />
| {{A30}}, {{A30p}}<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-39863 1.18]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-40846 1.07]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-39861 1.18]<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-40847 1.07]<br />
|-<br />
| {{A31}}, {{A31p}} (Bios 1G*)<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-42654 1.10]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-45771 1.04]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-42660 1.10]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-45900 1.05]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-45770 1.04]<br />
|-<br />
| {{A31}}, {{A31p}} (Bios 1N*)<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-44450 1.08]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-45662 1.04]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-44451 1.08]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-45898 1.02]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-45663 1.04]<br />
|-<br />
| {{G40}}<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50672 1.17]<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50673 1.17]<br />
|<br />
|<br />
|-<br />
| {{G41}}<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-58127 1.06]<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-58129 1.06]<br />
|<br />
|<br />
|-<br />
| {{R30}}<br />
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-40216 1.38]<br />
|<br />
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-40217 1.38]<br />
|<br />
|<br />
|-<br />
| {{R31}}<br />
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-41378 3.11]<br />
|<br />
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-41535 3.11]<br />
|<br />
|<br />
|-<br />
| {{R32}}<br />
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-43571 2.15]<br />
|<br />
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-43572 2.15]<br />
|<br />
|<br />
|-<br />
| {{R40}} (2681, 2682, 2683, 2896, 2898, 2899)<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-46055 1.23]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-46143 1.13]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-46061 1.23]<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-46144 1.13]<br />
|-<br />
| {{R40}} (2722, 2723, 2724, 2897)<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50320 1.29]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-46143 1.13]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50321 1.29]<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-46144 1.13]<br />
|-<br />
| {{R40e}}<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50302 1.33]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50344 1.04]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50301 1.33]<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50343 1.04]<br />
|-<br />
| {{R50}}, {{R50p}}<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50273 3.16]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50279 3.04]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50275 3.16]<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50277 3.04]<br />
|-<br />
| {{R50e}}<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-55000 2.02]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-54996 1.04]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-55001 2.02]<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-54997 1.04]<br />
|-<br />
| {{R51}} (1829, 1830, 1831, 1836)<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50273 3.16]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50279 3.04]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50275 3.16]<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50277 3.04]<br />
|-<br />
| {{R51}} (2883, 2887, 2888, 2889, 2894, 2895)<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-55003 1.21]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-54996 1.04]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-55004 1.21]<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-54997 1.04]<br />
|-<br />
| {{R52}} (1846, 1847, 1848, 1849, 1850, 1870)<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-59221 1.04]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-59184 1.02]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-59220 1.04]<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-59183 1.02]<br />
|-<br />
| {{R52}} (1858, 1859, 1860, 1861, 1862, 1863)<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-59379 1.01]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-59439 1.01]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-59380 1.01]<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-59440 1.01]<br />
|-<br />
| {{T20}}<br />
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4MNN8X 1.22]<br />
|<br />
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4JWNJC 1.22]<br />
|<br />
|<br />
|-<br />
| {{T21}}<br />
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4Q2KM5 1.16]<br />
|<br />
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4PJN8Y 1.16]<br />
|<br />
|<br />
|-<br />
| {{T22}}<br />
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4VWPPU 1.12]<br />
|<br />
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4VWP54 1.12]<br />
|<br />
|<br />
|-<br />
| {{T23}}<br />
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-39366 1.18]<br />
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-40022 1.06a]<br />
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-39362 1.18]<br />
|<br />
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-40021 1.06a]<br />
|-<br />
| {{T30}}<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-42694 2.08]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-42711 1.06]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-42720 2.08]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-45745 2.02]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-42725 1.06]<br />
|-<br />
| {{T40}}, {{T40p}}, {{T41}}, {{T41p}}, {{T42}}, {{T42p}}<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50273 3.16]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50279 3.04]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50275 3.16]<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50277 3.04]<br />
|-<br />
| {{T43}}, {{T43p}}<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-59096 1.05]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-59120 1.03]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-59097 1.05]<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-59121 1.03]<br />
|-<br />
| {{TransNote}}<br />
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4UDSMK 1.02]<br />
|<br />
| [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-4UDRRF 1.02]<br />
|<br />
|<br />
|-<br />
| {{X20}}, {{X21}}<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4P52BM 2.25]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4VQNTP 1.36]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4P52BL 2.25]<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-4PBMCT 1.36]<br />
|-<br />
| {{X22}}, {{X23}}, {{X24}}<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-39672 1.32]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-39806 1.30]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-39665 1.32]<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-39808 1.30]<br />
|-<br />
| {{X30}}<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-44135 1.07]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-44152 1.04]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-44131 1.07]<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-44149 1.04]<br />
|-<br />
| {{X31}}, {{X32}}<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50298 3.00d]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-53480 1.07b]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-50308 3.00d]<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-53479 1.07b]<br />
|-<br />
| {{X40}}<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-53881 1.65]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-53882 1.56]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-53883 1.65]<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-53885 1.56]<br />
|-<br />
| {{X41}}<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-59206 1.16]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-59208 1.00]<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-59205 1.16]<br />
|<br />
| [http://www.ibm.com/support/docview.wss?uid=psg1MIGR-59207 1.00]<br />
<br />
|}<br />
<br />
==Updating via Floppy== <br />
<br />
If you were able to create the boot floppy per the Diskette update method, and you have a Floppy with your Thinkpad, the update should be simple.<br />
<br />
==Updating via CD/DVD Drive==<br />
<br />
The whole thing gets more complicated if you neither have Windows nor a floppy drive installed. This is what this page is intended to describe.<br />
<br />
Be aware that IBM officially does '''not''' support this! The official statement to my support request was:<br />
<br />
<blockquote style="background: white; border: 1px solid black; padding: 1em;"><br />
<pre><nowiki><br />
I'm afraid we only support the options listed on our web page and no you<br />
can't burn a CD/DVD, however you can try to use an external USB FDD<br />
(floppy) drive. The experts recommend a IBM USB FDD, however they have also<br />
tested it with a Sony USB FDD drive.<br />
<br />
In order to make sure the drive is recognised you can boot up the FDD with<br />
a bootable dos diskette for w98<br />
</nowiki></pre><br />
</blockquote><br />
<br />
But it seems to be possible as Mathias Dalheimer describes this [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/1998-January/009743.html here].<br />
<br />
Another indication that it should work is that IBM uses PHLASH16.EXE (at least on T4x/p systems) to flash the BIOS into the chip. The same tool is used by [http://www.samsungpc.com/gb/support/p35/bios/bios-instructions.html other vendors] to flash the BIOS from bootable CD-ROMs.<br />
<br />
'''WARNING!''' Do '''not''' use the [http://syslinux.zytor.com/ SYSLINUX] image-loader [http://syslinux.zytor.com/memdisk.php MEMDISK] to boot the images! Some flash tools crash in that situation!<br />
<br />
Some interesting but very technical information about the used flash tool can be found [http://www.paul.sladen.org/thinkpad-r31/wifi-card-pci-ids.html here].<br />
<br />
===Creating a Floppy Image===<br />
<br />
If you have created a boot floppy on another machine, you need to create an image file of that floppy. This can be easily done in linux by running a command line:<br />
<br />
dd bs=2x80x18b if=/dev/fd0 of=/tmp/floppy.img<br />
<br />
You should verify this floppy.img as explained above.<br />
<br />
===Creating a Bootable CD from a Floppy Image===<br />
<br />
Once you have your floppy image, either from imaging a real floppy, or from extracting them via the cabextract method above, you need to make a boot CD out of it.<br />
<br />
The eltorito bootable CD standard is a wonderful thing. What this means is that a bootable cd can be made with a bootable floppy in such as way that the CD believes that it is a 2.88 MB floppy drive. This allows you to replace a boot floppy by a boot CD in nearly all situations.<br />
<br />
It is very easy to create such a bootable CD ISO image in Linux using the mkisofs tool. To do this run a command as follows:<br />
<br />
mkisofs -b bootfloppy.img -o bootcd.iso bootfloppy.img<br />
<br />
Note: You don't strictly need the last ''bootfloppy.img'', however some versions of mkisofs get confused about why you would want to create an iso with no contents, and thus won't let you. You don't actually care about the contents of the CD, you only care that the '''-b''' boot image is applied to the CD. For more info on this read the '''mkisofs man page'''.<br />
<br />
You can now burn the bootcd.iso in your favorite cd burning program.<br />
<br />
To get an overview which models have been tested with this version, here is a list:<br />
<br />
===Does work:===<br />
{|<br />
| '''Model''' || '''Tested by'''<br />
|-<br />
| R31 || [http://mailman.linux-thinkpad.org/pipermail/linux-thinkpad/1998-January/009743.html Mathias Dalheimer]<br />
|-<br />
| R40 || Matthew Lambie, http://lambie.org<br />
|-<br />
| R50 (1836-3SU) || jlbartos <jlbartos at hotmail dot com><br />
|-<br />
| R51 (1829) || Robert Uhl <rob dot uhl at gmx dot de><br />
|-<br />
| R51 (2887) || Ingo van Lil <inguin at gmx dot de><br />
|-<br />
| T40 || Sean Dague, http://dague.net<br />
|-<br />
| T40 || Justin Mason, http://jmason.org<br />
|-<br />
| T41 || Lev Givon (Bios 3.15 / EC 3.04) <lev at columbia dot edu><br />
|-<br />
| T40p || Lukas Krähenbühl, ismo at pop dot agri dot ch<br />
|-<br />
| T40p || Thomas Achtemichuk, tom at tomchuk dot com. BIOS 3.15 flashed fine with cabextract/CD method<br />
|-<br />
| T41p || Nils Newman, work great. (Version: Bios 3.14 / Embedded Controller 3.04)<br />
|-<br />
| T42p || Robert Schiele <rschiele@uni-mannheim.de>, Joern Heissler <joern@heissler.de><br />
|-<br />
| X20 || Neil Caunt <retardis at gmail dot com><br />
|-<br />
| X40 || Robbie Stone <robbie@serendipity.cx><br />
|-<br />
| T20 || Franz Hassels <fhassel at suse dot com><br />
|-<br />
| T43 (2668)|| Carsten Söhrens <casoe@gmx.de> (Version: Bios 1.05 / Embedded Controller 1.03)<br />
|}<br />
<br />
===Does not work:===<br />
{|<br />
| '''Model''' || '''Tested by'''<br />
|}<br />
<br />
Please note that testing this is '''at your own risk'''!!!<br />
<br />
==Updating with Network Boot Image==<br />
<br />
BIOS, Embedded Controller (EC), CD/DVD and Harddisk firmware disks can be booted<br />
over the network with [http://syslinux.zytor.com/pxe.php PXELINUX] as part of the [http://syslinux.zytor.com/ SYSLINUX] package.<br />
<br />
This requires that you have a DHCP and tftp server configured and setup properly on<br />
your network, and is probably not for the faint of heart.<br />
<br />
Make sure the firmware bootdisk is in linux 'dd' format, as the self-extracting .exe disks<br />
from the IBM website cannot be booted directly as such.<br />
<br />
This worked on the R31, X22, T21, T30 and T41p with various firmware updates.<br />
<br />
==Rentry Check List==<br />
<br />
(With appologies to Ed Nisley)<br />
<br />
The following is important to remember:<br />
# You must update '''both''' the Control Program and the BIOS at the same time<br />
# You must find versions of the Control Program and BIOS that are compatible. Not all of them are, so follow the readmes on the IBM website carefully to determine which are.<br />
# You must update the Control Program '''before''' you update the BIOS<br />
# All of these instructions are provided with '''no warranty'''. A bios update gone wrong for any reason can '''completely destroy''' your Thinkpad.</div>82.47.145.14https://www.thinkwiki.org/w/index.php?title=Talk:BIOS_Upgrade&diff=6624Talk:BIOS Upgrade2005-06-02T22:52:51Z<p>82.47.145.14: /* BIOS upgrade over PXE */</p>
<hr />
<div>I have disabled the hidden partition to make more space for linux (24G). I still have Windows on the 14G partition. Is it safe to upgrade the BIOS without the hidden partition? I want to get a newer BIOS to fix the annoying fan issue. Thanks<br />
<br />
- yes don't worry about it. bios upgrades have nothing to do with whats inside the harddrive.<br />
<br />
== BIOS upgrade over PXE ==<br />
<br />
Hi,<br />
<br />
I have a Thinkpad X20 with a very early BIOS and Embedded Controller Program which I'd like to update. Currently, the only feasible way of doing this is over the network using PXE. I already have a fully functional PXE server using SYSLINUX, and have so far been able to boot the BIOS diskette image using MEMDISK, although I have not attempted to flash anything yet due to the warnings given on the page. Is there any safe way I can update both the Controller Program and the BIOS in the same session over the network in this manner? If not, what other methods would be suitable? I have a USB CD-ROM drive and could probably get hold of a USB floppy drive.<br />
<br />
Thanks.<br />
<br />
Update: I ended up burning CDs as described and successfully updated everything. I'd still like to know if there is a way I could do it entirely over the network, though.</div>82.47.145.14https://www.thinkwiki.org/w/index.php?title=Talk:BIOS_Upgrade&diff=5467Talk:BIOS Upgrade2005-05-28T03:13:06Z<p>82.47.145.14: BIOS upgrade over PXE</p>
<hr />
<div>I have disabled the hidden partition to make more space for linux (24G). I still have Windows on the 14G partition. Is it safe to upgrade the BIOS without the hidden partition? I want to get a newer BIOS to fix the annoying fan issue. Thanks<br />
<br />
- yes don't worry about it. bios upgrades have nothing to do with whats inside the harddrive.<br />
<br />
== BIOS upgrade over PXE ==<br />
<br />
Hi,<br />
<br />
I have a Thinkpad X20 with a very early BIOS and Embedded Controller Program which I'd like to update. Currently, the only feasible way of doing this is over the network using PXE. I already have a fully functional PXE server using SYSLINUX, and have so far been able to boot the BIOS diskette image using MEMDISK, although I have not attempted to flash anything yet due to the warnings given on the page. Is there any safe way I can update both the Controller Program and the BIOS in the same session over the network in this manner? If not, what other methods would be suitable? I have a USB CD-ROM drive and could probably get hold of a USB floppy drive.<br />
<br />
Thanks.</div>82.47.145.14