https://www.thinkwiki.org/w/api.php?action=feedcontributions&user=Blokey&feedformat=atomThinkWiki - User contributions [en]2024-03-28T10:12:40ZUser contributionsMediaWiki 1.31.12https://www.thinkwiki.org/w/index.php?title=Problem_with_unusable_console&diff=17094Problem with unusable console2005-09-21T09:10:08Z<p>Blokey: /* Solutions */</p>
<hr />
<div>Information about the problem of virtual consoles displaying random vertical lines, usually of one color, and no text<br />
<br />
==Problem description==<br />
<br />
After a while of using the computer, all text on virtual consoles from 0 to 6 disappears, and an image, usually consisting of vertical lines of one or few colors, appears instead. Typing is possible, as is starting X or switching to an already active X. When switching back, the text consoles remain unusable.<br />
<br />
==Affected Models==<br />
<br />
*ThinkPad {{T22}}<br />
<br />
==Affected Operating Systems==<br />
<br />
*Linux<br />
<br />
==Status==<br />
<br />
A workaround is being tested.<br />
<br />
==Solutions==<br />
<br />
From linux kernel config, disable savagefb's console acceleration.<br />
<br />
< > ATI Mach64 display support<br />
<*> S3 Savage support<br />
[ ] Enable DDC2 Support<br />
[ ] Enable Console Accelereation <--- see that this is disabled<br />
< > SiS acceleration<br />
<br />
If using "reset" does not fix it, Debian users may try reinitialising the console by running /etc/init.d/console-screen.sh as root. A reboot is probably required if this fails.<br />
<br />
==Related Links==<br />
<br />
*[http://www.xfree86.org/4.3.0/savage.4.html XFree86 Savage(4) Manual Page]</div>Blokeyhttps://www.thinkwiki.org/w/index.php?title=Talk:BIOS_Upgrade&diff=9233Talk:BIOS Upgrade2005-09-21T08:59:42Z<p>Blokey: /* bios/controller update sequence -> comments*/</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.<br />
<br />
<br />
== RE: grub initrd ==<br />
<br />
"Another possibility which works even without a CD-drive or network is to boot the disk image via the grub initrd mechanism."<br />
<br />
0) Interesting suggestion. Might be better of in its own section.<br />
<br />
1) Could you please elaborate?<br />
<br />
2) My first guess (pending your elaboration) would be to "chainload" the first block of the diskimage using the grub commandline, like:<br />
blocklist (''path'')/''to''/''diskimage''<br />
chainloader ''blockvalue''+1<br />
<br />
But that's just a guess!<br />
<br />
[[user:Pebolle|Paul Bolle]] Fri Jul 15 12:20:47 CEST 2005<br />
<br />
== bios/controller update sequence ==<br />
<br />
The article says:<br />
"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"<br />
<br />
When I look at the IBM udpate instructions for the T23, it says:<br />
"If you need to update the BIOS as well as the Embedded Controller Program, update the BIOS first."<br />
<br />
<br />
Comments?<br />
<br />
I would first contact IBM for clarification, but you should probably be following instructions specific to your model.<br />
<br />
== Firmware upgrade for Intel minipci combo card ==<br />
<br />
I just purchased an [[Intel 10/100 Ethernet Mini-PCI Adapter with 56K Modem]] that has an ancient (2.0.6) firmware version. I Downloaded the update file intlbtag.EXE but cabextract was unable to find any cabfiles inside it. I tried running the program via wine and that didn't work either.<br />
<br />
Finally I ran the program on a windows machine and created a boot floppy. Then I went through the the process of converting the floppy to a bootable cd via linux and that worked like a charm. The cd successfully updated the minipc card's firmware.<br />
<br />
Everything worked but I ended up needing a windows box to do it. Could this have been done without windows?<br />
<br />
== Firmware upgrade for Wireless LAN MiniPCI COMBO Card using prism2_srec ==<br />
<br />
The appropriate firmware installation program for the wlan card in my R32 can be extracted using cabextract as described in the article. It contains (besides some installation programs) a disk image (1awg06ww.IMG) that seems to be a simple dos boot disk. This image contains 3 .hex files (id010001.hex, pk010100.hex, sf010402.hex) that are recognized by prism2_srec to be "srec"-files. Trying to load them to RAM yields:<br />
<br />
{{cmdroot|prism2_srec -v -r wlan0 sf010402.hex}}<br />
S3 CRC-16 generation record: start=0x007E1800 len=65642 prog=1<br />
Start address 0x00000000<br />
srec summary for sf010402.hex<br />
Component: 0x001f 1.4.2 (station firmware)<br />
<snip><br />
Interface compatibility information:<br />
role=Supplier variant=2 range=1-9 iface=Station Firmware-Driver (4)<br />
role=Actor variant=1 range=1-1 iface=Modem-Firmware (1)<br />
role=Actor variant=2 range=1-1 iface=Controller-Firmware (2)<br />
role=Actor variant=1 range=4-4 iface=Primary Firmware-Driver (3)<br />
<snip><br />
Wireless LAN card information:<br />
Components:<br />
NICID: 0x8013 v1.0.0<br />
PRIID: 0x0015 v1.0.7<br />
STAID: 0x001f v1.3.6<br />
Interface compatibility information:<br />
PRI role=Supplier variant=1 range=1-1 iface=Modem-Firmware (1)<br />
PRI role=Supplier variant=2 range=1-1 iface=Controller-Firmware (2)<br />
PRI role=Supplier variant=1 range=4-4 iface=Primary Firmware-Driver (3)<br />
STA role=Supplier variant=1 range=1-9 iface=Station Firmware-Driver (4)<br />
PRI role=Actor variant=2 range=1-1 iface=Controller-Firmware (2)<br />
STA role=Actor variant=2 range=1-1 iface=Controller-Firmware (2)<br />
STA role=Actor variant=1 range=1-1 iface=Modem-Firmware (1)<br />
<snip><br />
This image is not meant to be downloaded to volatile memory.<br />
Incompatible update data.<br />
<br />
Has anyone tried to flash this device using prism2_srec yet?<br />
What bothers me is, that the upgrade is for many different parts of the combo card. Does anyone have an opinion on whether this could work?</div>Blokeyhttps://www.thinkwiki.org/w/index.php?title=IRC&diff=15582IRC2005-08-14T18:27:11Z<p>Blokey: </p>
<hr />
<div>Please add more channels if there are any!<br />
<br />
* [irc://irc.freenode.org/thinkwiki #thinkwiki] on [http://freenode.org/ freenode]<br />
* [irc://irc.freenode.org/#ibmthinkpad ##ibmthinkpad] on [http://freenode.org/ freenode] ('''Note''': the double ## is intentional)</div>Blokeyhttps://www.thinkwiki.org/w/index.php?title=IRC&diff=7770IRC2005-08-14T18:25:53Z<p>Blokey: #ibmthinkpad -> ##ibmthinkpad</p>
<hr />
<div>Please add more channels if there are any!<br />
<br />
* [irc://irc.freenode.org/thinkwiki #thinkwiki] on [http://freenode.org/ freenode]<br />
* [irc://irc.freenode.org/#ibmthinkpad ##ibmthinkpad] on [http://freenode.org/ freenode]</div>Blokey