https://www.thinkwiki.org/w/api.php?action=feedcontributions&user=Mr.dnme&feedformat=atomThinkWiki - User contributions [en]2024-03-28T18:03:43ZUser contributionsMediaWiki 1.31.12https://www.thinkwiki.org/w/index.php?title=User_talk:Mr.dnme&diff=36217User talk:Mr.dnme2008-01-25T17:36:29Z<p>Mr.dnme: â†Created page with 'My hovercraft is full of eels. My T43 is installed with Gutsy and fglrx.'</p>
<hr />
<div>My hovercraft is full of eels.<br />
<br />
My T43 is installed with Gutsy and fglrx.</div>Mr.dnmehttps://www.thinkwiki.org/w/index.php?title=Talk:How_to_make_use_of_IrDA&diff=36216Talk:How to make use of IrDA2008-01-25T17:34:41Z<p>Mr.dnme: </p>
<hr />
<div>The "wrong chip version ff" is a real issue, and having it mentioned makes sure that google searches turn it up with a solution.<br />
[[User:Tonko|Tonko]] 01:41, 8 Oct 2005 (CEST)<br />
<br />
----<br />
The present text confused me (as you now have noticed). Maybe it should better reflect that the error is incorrect ("wrong chip version ff" instead of "FIR mode not enabled" or whatever). Would that be acceptable? <br />
<br />
[[User:Pebolle|Paul Bolle]] 02:05, 8 Oct 2005 (CEST)<br />
----<br />
If you think you can explain it better, go right ahead. The IrDA document could use some major cleaning.<br />
<br />
As long as we still point out that the only error in syslog is "Wrong chip version ff" when trying to load the FIR module without first activating the PnP device. It would be nice if the ISA-PNP patch to the nsc-ircc driver got accepted upstream, so we dont have to do these hacks anymore.<br />
[[User:Tonko|Tonko]] 03:58, 8 Oct 2005 (CEST)<br />
----<br />
Tonko,<br />
<br />
Is there a reason why you deleted the TODO entry for linux 2.6 kernel config for SIR? I would like to readd it, but like to hear your reason to remove it first.<br />
<br />
[[User:Pebolle|Paul Bolle]] 10:23, 14 Oct 2005 (CEST)<br />
<br />
== T23 debianized kernel with probs ==<br />
<br />
Found another crazy thing here. T23 2648-2GG, with 2.6.13 and 2.6.14 (Debianized Source). Clear init of nsc-ircc and dongle, but the dongle stays offline (dark and blind). Booted with Knoppix or Bart-PE Windows give correct function of the whole device, viewed with a digicam shows some blinks at init. But not with plain 2.6.13 an 2.6.14 from Debian.<br />
Eric<br />
<br />
== setpnp ==<br />
<br />
Hello,<br />
<br />
since the nsc-ircc patch isn't in 2.6.15, I tried to go the setpnp route, but I don't even get to see {{path|/proc/bus/pnp}} even though I enabled the support for it in the kernel config (once I found out that I need to enable ISA support to even get the option). Has anyone successfully used setpnp to enable the IRDA port or is that just some sort of urban legend? ;)<br />
<br />
--[[User:Spiney|spiney]] 19:12, 4 Jan 2006 (CET)<br />
----<br />
<br />
Make sure you enable pnp-bios support specifically when compiling the kernel, just enabling pnp support is not enough.<br />
I must however admit that I have not done this, since my ancient TP 770 running a 2.4 kernel, which was at least 5 years ago.<br />
<br />
I just looked at a 2.6 menuconfig myself, and could not find the option, but looking at my .config file I can see the CONFIG_PNPBIOS option, so you might just want to edit the config file directly, enable the PNPBIOS option, and run make oldconfig.<br />
<br />
--[[User:Tonko|Tonko]] 19:38, 4 Jan 2006 (CET)<br />
----<br />
<br />
I do have the pnp-bios support enabled (the option is depending on ISA among others, checked the Kconfig file in the source tree to find it), and also the proc-Interface option, but still no go... maybe it's not compatible with CONFIG_PNPACPI? Oh well, nevermind, going back to the patch, that works with less hassles, I just hope it'll end up in the vanilla kernel eventually. Still thanks for the help.<br />
<br />
--[[User:Spiney|spiney]] 20:22, 4 Jan 2006 (CET)<br />
----<br />
<br />
Ok, on further investigation (not giving up that easily ;) it really seems that CONFIG_PNPACPI is disabling PnPBIOS, at least dmesg showed something along the lines of "PnPBIOS: disabled by PnPACPI". But, after recompiling without PnPACPI, I still can't get it to work. I can use {{cmd|setpnp|}} and {{cmd|lspnp|}} just fine, but the nsc-ircc module won't load:<br />
<br />
<pre><br />
t43p:~# lspnp 12<br />
12 IBM0071 IBM Thinkpad infrared port<br />
t43p:~# setpnp 12 io 0x2f8 irq 3<br />
t43p:~# lspnp -v 12<br />
12 IBM0071 IBM Thinkpad infrared port<br />
dma 3<br />
io 0x02f8-0x02ff<br />
irq 3<br />
t43p:~# modprobe nsc-ircc io=0x2f8 irq=3 dongle_id=0x09<br />
FATAL: Error inserting nsc_ircc (/lib/modules/2.6.15/kernel/drivers/net/irda/nsc-ircc.ko): No such device<br />
</pre><br />
<br />
Hmm, I'm getting somewhat annoyed... any ideas?<br />
<br />
--[[User:Spiney|spiney]] 20:58, 4 Jan 2006 (CET)<br />
----<br />
<br />
have you tried just doing {{cmd|setpnp 12 on|}}<br />
<br />
--[[User:Tonko|Tonko]] 21:05, 4 Jan 2006 (CET)<br />
----<br />
<br />
Yes, that was the first thing I tried, didn't help. BTW, I just fiddled around with lirc a bit (never tried it before), and the lirc_sir module works just fine:<br />
<br />
<pre><br />
lirc_sir: I/O port 0x02f8, IRQ 3.<br />
lirc_sir: Installed.<br />
</pre><br />
<br />
and I was able to get it to control xmms.<br />
<br />
{{cmd|setserial|}} doesn't claim the device either:<br />
<br />
<pre><br />
t43p:~# setserial -ag /dev/ttyS0<br />
/dev/ttyS0, Line 0, UART: unknown, Port: 0x0000, IRQ: 0<br />
Baud_base: 921600, close_delay: 50, divisor: 0<br />
closing_wait: 3000<br />
Flags: spd_normal skip_test<br />
</pre><br />
<br />
I'm really out of ideas.<br />
<br />
--[[User:Spiney|spiney]] 21:20, 4 Jan 2006 (CET)<br />
----<br />
<br />
Hmm, it should not be ttyS0, but ttyS1 which might be stepping on the resources<br />
ttyS0 is IO 0x3f8 and IRQ 4, while ttyS1 is IO 0x2f8 and IRQ 3.<br />
<br />
ttyS0 is your integrated serial port, which even ThinkPads without physical serial port have.<br />
<br />
--[[User:Tonko|Tonko]] 21:29, 4 Jan 2006 (CET)<br />
----<br />
Sorry, I cut'n'paste the wrong device since I checked them both, the output for ttyS1 is identical (apart from "/dev/ttyS1, Line 1" of course).<br />
<br />
--[[User:Spiney|spiney]] 21:36, 4 Jan 2006 (CET)<br />
----<br />
No idea what might be wrong, perhaps it does not work on more recent machines, or kernels.<br />
<br />
As I said, it worked for me a long time ago on my 770X with ''something'' like this:<br />
<br />
/bin/setserial /dev/ttyS1 uart none port 0 irq 0<br />
setpnp 12 io 0x2f8 irq 3<br />
setpnp 12 on<br />
modprobe nsc-ircc dongle_id=0x09 io=0x2f8 irq=3<br />
<br />
What is the error you get from nsc-ircc in syslog? the "Wrong chip version ff" error?<br />
<br />
--[[User:Tonko|Tonko]] 22:22, 4 Jan 2006 (CET)<br />
----<br />
<br />
No errors are recorded at all (dmesg, syslog), just the message above on stderr from {{cmd|modprobe|}}.<br />
<br />
--[[User:Spiney|spiney]] 09:27, 5 Jan 2006 (CET)<br />
----<br />
<br />
BTW, is it just me or does the nsc-ircc patch only work if CONFIG_PNPACPI is set in the kernel config? Otherwise the module loads fine, (but without stating in the kernel log that it found the dongle) and using IRDA does not work, irattach returns "irattach: ioctl(SIOCGIFFLAGS): No such device".<br />
<br />
--[[User:Spiney|spiney]] 14:37, 12 Jan 2006 (CET)<br />
----<br />
<br />
== Not even SIR working on R52 ==<br />
<br />
I don't want/need FIR right now, so i thought i wouldn't have to mess with it.<br />
I don't have /proc/bus/pnp, but i'm pretty sure infrared should work without it as well.<br />
I do not have a kernel patch and am using the current Ubuntu Breezy 2.6.12-10 kernel.<br />
Problem is, that when starting<br />
irattach /dev/ttyS1 -s<br />
It complains in syslog: no such device<br />
On ttyS0 it works fine, but well does not find any packets.<br />
<br />
# setserial -ag /dev/ttyS1<br />
/dev/ttyS1, Line 1, UART: unknown, Port: 0x0000, IRQ: 0<br />
Baud_base: 921600, close_delay: 50, divisor: 0<br />
closing_wait: 3000<br />
Flags: spd_normal skip_test<br />
<br />
# cat /dev/ttyS1<br />
cat: /dev/ttyS1: input-/outputerror<br />
<br />
So i tried:<br />
sudo setserial /dev/ttyS1 uart 16550A port 0x02f8 irq 3<br />
<br />
Well ''now'' irattach will attach to ttyS1, irdadump will show me the packets '''sent''' by my computer,<br />
but won't receive my cellphone's packets (Nokia 6210). In Windows, everything works fine.<br />
<br />
===Same case here===<br />
I have the same problem here, it used to work on 2.6.15. nsc-irc works, even a MCS7780 USB-IRDA adapter works, but the chip doesn't seem to send/receive on 2.6.17 and 2.6.18 (I checked with a CCD camera, no light signal at all), also ''findchip -d'' says:<br />
<br />
root@golem3:/etc# findchip -d<br />
Probing for FDC37C669 ...<br />
Wrong chip id=0xff<br />
Wrong chip id=0xff<br />
Probing for FDC37C669FR ...<br />
Wrong chip id=0xff<br />
Wrong chip id=0xff<br />
Probing for FDC37N869 ...<br />
Wrong chip id=0xff<br />
Wrong chip id=0xff<br />
Probing for FDC37C93xFR ...<br />
Wrong chip id=0xff<br />
Wrong chip id=0xff<br />
Probing for FDC37N957FR ...<br />
Wrong chip id=0xff<br />
Wrong chip id=0xff<br />
Probing for FDC37N958FR ...<br />
Wrong chip id=0xff<br />
Wrong chip id=0xff<br />
Probing for PC87108 ...<br />
no chip at 0x150<br />
no chip at 0x398<br />
no chip at 0x0ea<br />
Probing for PC87338 ...<br />
no chip at 0x398<br />
no chip at 0x15c<br />
Wrong chip id=0x00<br />
Probing for EFER at 0x03f0 ...<br />
hefras = 0xff<br />
Probing for EFER at 0x0370 ...<br />
hefras = 0xff<br />
EFER seems to be probed at 0x0370<br />
chip id = 0xff, revision = 0xff<br />
Wrong device ID = 0xff<br />
Probing for EFER at 0x0250 ...<br />
hefras = 0xff<br />
Probing for EFER at 0x0250 ...<br />
hefras = 0xff<br />
Probing for EFER at 0x03f0 ...<br />
hefras = 0xff<br />
hefere = 0xff<br />
Probing for EFER at 0x03f0 ...<br />
hefras = 0xff<br />
hefere = 0xff<br />
EFER seems to be probed at 0x03f0<br />
chip ID is 0x0f : no known chip was detected.<br />
Couldn't find Winbond superI/O chip.<br />
<br />
<br />
dmesg:<br />
<br />
nsc-ircc, chip->init<br />
nsc-ircc, Found chip at base=0x02e<br />
nsc-ircc, driver loaded (Dag Brattli)<br />
IrDA: Registered device irda0<br />
nsc-ircc, Using dongle: IBM31T1100 or Temic TFDS6000/TFDS6500<br />
IBM TrackPoint firmware: 0x0e, buttons: 3/3<br />
serial8250: too much work for irq3<br />
sirdev_get_instance - ttyS1<br />
irtty_open - ttyS1: irda line discipline opened<br />
irlap_change_speed(), setting speed to 9600<br />
nsc_ircc_pnp_probe() : From PnP, found firbase 0x2F8 ; irq 3 ; dma 3.<br />
nsc-ircc, chip->init<br />
nsc-ircc, Found chip at base=0x02e<br />
nsc-ircc, driver loaded (Dag Brattli)<br />
IrDA: Registered device irda0<br />
nsc-ircc, Using dongle: IBM31T1100 or Temic TFDS6000/TFDS6500<br />
--[[GuySoft]]<br />
<br />
>Have you enabled infrared in BIOS?<br />
[[User:Defiant|Defiant]] 21:25, 29 September 2006 (CEST)<br />
<br />
Yes I did, It used to function in 2.6.15! its the new 2.6.17 kernel that messed it up, also 2.6.18 doesn't help.<br />
<br />
==update - IBM31T1100 and lirc==<br />
<br />
Working now in 2.6.18, however I can't get lirc to work.<br />
<br />
In dmesg i get:<br />
[code]<br />
lirc_dev: lirc_register_plugin: sample_rate: 0<br />
lirc_sir: i/o port 0x02f8 already in use.<br />
[/code]<br />
<br />
Also "/bin/setserial /dev/ttyS1 uart none" doesn't help<br />
<br />
Any help there?<br />
[[User:Guysoft|Guysoft]] 19:40, 31 December 2006 (CET)<br />
<br />
==lirc and FIR works on R52!!==<br />
I got both lirc and the FIR module to work on my thinkpad r52.<br />
<br />
For lirc I had to :<br />
$ killall -9 irattach<br />
$ setserial /dev/ttyS1 uart none<br />
$ rmmod nsc_ircc<br />
then:<br />
$ modprobe lirc_sir<br />
and then run:<br />
$ lircd -d /dev/lirc0 /etc/lircd.conf --nodaemon<br />
<br />
For FIR i need to:<br />
modprobe nsc_ircc<br />
I hope this helps anyone that has problems.<br />
<br />
[[User:Guysoft|Guysoft]] 15:08, 15 January 2007 (CET)<br />
<br />
The lirc_sir module has problems with suspend (disk/ram both).<br />
<br />
I'm using Debian Etch kernel 2.6.18-4-686 (version 2.6.18.dfsg.1-11)<br />
with the lirc-modules-source (version 0.8.0-9.2). The lirc_sir module<br />
was built with "other" as type of the SIR device.<br />
<br />
With this kernel the nsc_ircc module suspends/resumes properly.<br />
<br />
I tried to do a module unload and reload, but surprisingly even that failed.<br />
Before the suspend I get normal output from mode2 but after the resume there is<br />
no output at all :-(<br />
<br />
[[User:Kapil|Kapil]] 15:39, 09 March 2007 (PST)<br />
<br />
One a separate note. The "nsc_ircc" module and the "lirc_sir" module seem to conflict.<br />
<br />
If I load one module and then the other, the system appears to hang. So I wonder how Guysoft managed to get this working.<br />
<br />
[[User:Kapil|Kapil]] 15:46, 09 March 2007 (PST)<br />
<br />
== T23 IrDA silent? ==<br />
<br />
Hi.<br />
I got SIR working pretty easily on my T20. I cannot get anything to work on my T23. I can get the nsc-ircc module to load, and now irattach works (both with and without nsc-ircc), and I've checked the relevant info in /proc/sys/net/irda, but nothing shows up in /proc/net/irda/discovery, and irdadump gives nothing at all. No errors in dmesg or the log. The red LED never lights. It flashes constantly in Windows.<br />
<br />
--[[User:SystemParadox|SystemParadox]] 16:58, 1 May 2006 (CEST)<br />
<br />
== Problems accessing a Nokia phone ==<br />
<br />
i just compiled a brand new 2.6.18 Linux Kernel. Now, even tough the Kernel modules are loaded and irda-utils start correctly i am having trouble accessin my Nokia 6135.<br />
<br />
This are the contents of my /etc/modprobe.d/irda-utils:<br />
<br />
alias irda0 nsc-ircc<br />
options nsc-ircc dongle_id=0x09 io=0x2f8 irq=3 dma=3<br />
install nsc-ircc /bin/setserial /dev/ttyS1 uart none port 0 irq 0; /sbin/modprobe --ignore-install nsc-ircc<br />
<br />
/var/log/syslog:<br />
<br />
Sep 28 11:33:00 raziel kernel: pnp: Device 00:0b activated.<br />
Sep 28 11:33:00 raziel kernel: nsc_ircc_pnp_probe() : From PnP, found firbase 0x2F8 ; irq 3 ; dma 3.<br />
Sep 28 11:33:00 raziel kernel: nsc-ircc, chip->init<br />
Sep 28 11:33:00 raziel kernel: nsc-ircc, Found chip at base=0x02e<br />
Sep 28 11:33:00 raziel kernel: nsc-ircc, driver loaded (Dag Brattli)<br />
Sep 28 11:33:00 raziel kernel: IrDA: Registered device irda0<br />
Sep 28 11:33:00 raziel kernel: nsc-ircc, Using dongle: IBM31T1100 or Temic TFDS6000/TFDS6500<br />
Sep 28 11:34:34 raziel irattach: got SIGTERM or SIGINT<br />
Sep 28 11:34:34 raziel irattach: Stopping device irda0<br />
Sep 28 11:34:34 raziel irattach: exiting ...<br />
Sep 28 11:34:35 raziel irattach: executing: '/sbin/modprobe irda0'<br />
Sep 28 11:34:35 raziel irattach: executing: 'echo raziel > /proc/sys/net/irda/devname'<br />
Sep 28 11:34:35 raziel irattach: executing: 'echo 1 > /proc/sys/net/irda/discovery'<br />
Sep 28 11:34:35 raziel irattach: Starting device irda0<br />
Sep 28 11:34:35 raziel kernel: irlap_change_speed(), setting speed to 9600<br />
<br />
But when wammu tries to find the phone (which is right in front of the left side of laptop, where the IR port supposedly is AND it has IR reception enabled):<br />
<br />
Starting /dev/ttyS0 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']<br />
Starting /dev/ttyS1 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']<br />
Starting /dev/ttyS2 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']<br />
Scanning for bluetooth devices using PyBluez<br />
Could not access Bluetooth subsystem (error accessing bluetooth device)<br />
Finished /dev/ttyS0 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']<br />
Finished /dev/ttyS1 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']<br />
Finished /dev/ttyS2 - ['at19200', 'at115200', 'fbusdlr3', 'fbus', 'mbus', 'fbuspl2303']<br />
All finished, found 0 phones<br />
<br />
This phone does not have bluetooth so im basically out of options, ideas anyone?<br />
<br />
Any suggestions much appreciated<br />
<br />
--[[User:Havok1977|Havok1977]] 12:05, 28 Sep 2006 (CEST)<br />
<br />
== No irrecord output ==<br />
<br />
So I loaded lirc_sir on my T43 and it says all is ok. However I don't seem to get anything out of irrecord. I am pretty sure my remote control is ok. What am I missing?<br />
<br />
--[[User:mr.dnme|mr.dnme]] 19:29, 25 Jan 2008</div>Mr.dnmehttps://www.thinkwiki.org/w/index.php?title=Talk:Problem_with_non-ThinkPad_hard_disks&diff=29622Talk:Problem with non-ThinkPad hard disks2007-05-06T19:21:32Z<p>Mr.dnme: </p>
<hr />
<div>I replaced my R52's Hard disk by ST9100823A 100G/5400, when the system stared, it shows error information.<br />
<br />
How could I solve the problem, if you know, please email to me wangdongmail@hotmail.com<br />
<br />
Thanks<br />
<br />
== Downgrade the BIOS to v1.01 ==<br />
<br />
To the poster ("TellIT systems"?): can you explain what is the "BUG" in later versions? What is the source of this information?<br />
<br />
Can anyone report his experience with the BIOS downgrade?<br />
<br />
--[[User:Thinker|Thinker]] 22:05, 26 Nov 2005 (CET)<br />
----<br />
<br />
It seems he is talking, not about the BIOS for entry model R52/T43 models, but about the embedded-controller (EC) firmware.<br />
<br />
As such the download link is wrong.<br />
<br />
And yes, what is the bug that requires you to downgrade the EC firmware? Without more detail, I would be inclined to remove it.<br />
<br />
--[[User:Tonko|Tonko]] 02:34, 27 Nov 2005 (CET)<br />
<br />
I looked around the German website a bit, and found this document: http://www.tell-it.ch/harddisk.php<br />
<br />
It does not explain anything more. As such I think the prudent thing to do is '''NOT''' backlevel your firmware, but to wait until we either have more details, or an official firmware update from Lenovo.<br />
<br />
I will remove the Downgrade Bios piece from the main page as it is clearly wrong anyway in its current form.<br />
<br />
--[[User:Tonko|Tonko]] 02:45, 27 Nov 2005 (CET)<br />
----<br />
<br />
Tonko, the ancient version numbers fooled me too, but the [http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-59379 IBM page] he links to is about R52 BIOS firmware, not EC firmware. It's plausible that BIOS 1.01 didn't yet include the disk detection code, so maybe the downgrade will indeed silence the warnings. I updated the description to reflect this. Of course, the story about a "bug" is probably wrong -- if test was deliberately introduced due to broken hardware, it is unlikely to be removed in future versions.<br />
<br />
--[[User:Thinker|Thinker]] 20:13, 27 Nov 2005 (CET)<br />
----<br />
<br />
Thinker, the download page he linked to, also applies to T43 entry-models.<br />
<br />
He was saying to downgrade the BIOS from 1.03 to 1.01, but the latest BIOS is actually at 1.20, while the EC firmware is currently at 1.03, which made me think he was not talking about a BIOS downgrade, but an EC downgrade.<br />
<br />
In any case, without more details I would strongly suggest not to downgrade your firmware as it may possibly break things. BIOS and EC for instance need to be matched typically, and it is possible that newer machines are not compatible with these older firmware releases (not sure if the flash tool will allow you to flash that far back in that case or not).<br />
<br />
--[[User:Tonko|Tonko]] 17:08, 28 Nov 2005 (CET)<br />
----<br />
<br />
Agreed. Maybe the downgrade instructions date back to when BIOS 1.03 and T43 model 1xxx were the latest versions; they sure don't look good now.<br />
<br />
--[[User:Thinker|Thinker]] 17:21, 28 Nov 2005 (CET)<br />
----<br />
<br />
Tell IT systems comment: The Problem anyway has solved this way - without any failures.<br />
A newer [http://www-306.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-59097 BIOS Upgrade] is yet available now: Original Text of the description:<br />
"A new BIOS setup option, that allows system startup without pressing<br />
the ESC key on POST 2010 warning message.<br />
Its location is 'BIOS Setup menu'->'Startup'->'Boot after message for Hard drive...'.<br />
Note: The cause of the 2010 message is using unsupported hard drive firmware<br />
version. Please use supported version as much as you can." <br />
<br />
Not nice to see that IBM/Lenovo does no more support the industral standard..<br />
----<br />
<br />
'''To Tell IT systems''': Thanks for sharing your solution, but when posting to the Wiki please respect the existing content and organization. About the new BIOS, there are already a couple of references to the new BIOS higher up in the article, so there's no need to repeat that. About the suggested BIOS downgrade, do you mean the BIOS firmware or the Embedded Controller firmware? The versions number you posted seem to match the Embedded Firmware, which has nothing to do with that message. The latest versions of the BIOS are 1.2x, not 1.0x. Also, how can you be sure that the error message is bug, rather than a warning about a true hardware problem?<br />
<br />
--[[User:Thinker|Thinker]] 19:17, 6 Dec 2005 (CET)<br />
----<br />
<br />
I've update my T43 EC to 1.04 and BIOS to 1.24, although it really has an option in the BIOS that allow the system to boot when ERROR 2010.<br />
<br />
However, I found that it really has a compatibility problem with my new Seagate 80 HDD<br />
(ST9809211A).<br />
<br />
Poor.....<br />
<br />
--[[User:ecowalker|ecowalker]] 23:38:17, 17 Jan 2006 (GMT+8)<br />
----<br />
<br />
==Seagate Momentus 7200.1==<br />
<br />
Comments by [[User:Jbaldini|Jbaldini]]:<br />
<br />
SUBMITTED September 1st, 2006<br />
<br />
I can only speak for the Seagate Momentus 7200.1 ST910021A (100GB 7200RPM) listed above.<br />
<br />
It does NOT work out of the box, and all serials have the same firmware 1.03 from Seagate (I called them). No user has reported this drive to work and users have reported that it gives the error after the IBM firmware to get it up to version 1.07. I also upgraded the firmware manually with IBM's util which you have to do because it only automatically updates if the drive contains an older "IBM" version of the firwmare. Of course with no help from the directions below or Seagate support, just upgraded the firmware based on running the Seagate util and see it's parameters listed.<br />
To upgrade the IBM firmware the directions given on the link at the bottom were also wrong applying to the Seagate drives.<br />
But there is no need to upgrade that drive with IBM's firm.<br />
<br />
This drive will always cause the error for every person on one of the laptops, I bought when because this create hope and the WARNING is inaccurate as I mentioned since they all have 1.03 "out of the box" which doesn't work. Seagate knows it doesn't work.<br />
<br />
I also performed a low level format, took between 9 and 11 hours, still didn't work. Just wanted to make sure.<br />
Do not buy this drive for those laptops. I'm going to down grade the R52 BIOS since there are no reported problems running any ATA drive in a system like this using a SATA to PATA bridge but I'll be using a different drive. Not the 150 dollar momentus.<br />
<br />
Hope this helps some people not make the same mistake I did. I strongly caution against purchasing any momentus for these laptops based on this experience.<br />
<br />
Thanks,<br />
<br />
J<br />
<br />
UPDATE***** September 1st, 2006<br />
Just downgraded the BIOS, not sure the limitation but it won't boot the 100GB Seagate Momentus but boots the 30GB travelstar fine which has always worked so downgraded BIOS has either drive or boot partition limitation, I really don't care which, I'm loading the new BIOS again since this downgrading was a stupid idea (by the way, Seagate recommended too) but it doesn't work for this drive. I have to say IBM or Lenovo has really disappointed on this I used to think (no pun intended) Thinkpad were solid, and it's only these goofball models, who would use a pata to sata bridge ???? just require a fricken serial 2.5 drive or use an PATA interface. Good thing I got this craptop for free.<br />
<br />
J<br />
----<br />
<br />
== HTS721080G9AT00 ==<br />
<br />
It seems there is a working solution for this module:<br />
<br />
1. Download the now well known bootable hard drive firmware CD from Lenovo - I used revision fwhd44 (fwhd44.iso): <br />
http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-62282 <br />
2. Boot from that CD after you burned it <br />
3. Exit to the DOS prompt. <br />
4. Type: (changing the letter I to a letter O essentially) <br />
Code: <br />
copy MC4IA51A.bdr MC4OA51A.bdr <br />
<br />
5. Type: <br />
Code: <br />
hfui15.exe OA51A MC41IA51.bdr /F mpcA5IAb.tbl <br />
<br />
6. Hit "U" in the flash program to start <br />
7. After you get the FAIL message, hit a key to return to the DOS prompt <br />
8. Type: <br />
Code: <br />
hfui15.exe IA51A MC41IA51.bdr /F mpcA5IAb.tbl <br />
<br />
9. Hit "U" in the flash program to start <br />
10. You should get a PASS this time and be all set.<br />
<br />
== TOSHIBA MK1032GAX ==<br />
I have firmware version AB211A, the version that comes with Lenovo's ISO is AB223E.<br />
The CD says my firmware needs no update (but of course I get the 2010)<br />
Did anyone try to use the flasher (HFUT10.EXE) to force flash with AB223E.CD2?</div>Mr.dnmehttps://www.thinkwiki.org/w/index.php?title=2668-8AG&diff=226082668-8AG2006-06-03T09:18:32Z<p>Mr.dnme: </p>
<hr />
<div>= IBM ThinkPad T43 2668-8AG Specifications =<br />
<br />
== CPU and Memory ==<br />
{|<br />
|Processor Manufacturer || Intel<br />
|-<br />
|Processor Class || (Pentium M Dothan)<br />
|-<br />
|Processor Name || Intel Pentium M 750<br />
|-<br />
|Processor Speed || 1.86 GHz<br />
|-<br />
|Installed Memory || 512 MB<br />
|-<br />
|Maximum Memory || 2 GB<br />
|- <br />
|Memory Technology || DDR2 SDRAM - 533 MHz<br />
|-<br />
|Cache Size || 2 MB<br />
|}<br />
== Storage ==<br />
{|<br />
|Hard Drive Capacity || 60 GB <br />
|-<br />
|Included Drives || DVD Multi Recorder<br />
|}<br />
<br />
== Display and Graphics ==<br />
{|<br />
|Display Size || 15.0 inch<br />
|-<br />
|Display Type || TFT active matrix<br />
|-<br />
|Graphics Processor || ATI MOBILITY RADEON X300<br />
|-<br />
|Graphics Memory || 64 MB<br />
|-<br />
|Included Video Card || Graphics card - PCI Express x16<br />
|-<br />
|Resolution ||1024 x 768 pixels<br />
|-<br />
|Max. External Resolution || 2048 x 1536 pixels<br />
|}<br />
<br />
== Battery ==<br />
{|<br />
|Battery Model || 6 cell<br />
|-<br />
|Battery Life || 4 hour(s)<br />
|-<br />
|Battery Type || Lithium ion<br />
|}<br />
<br />
== Communications and Networking ==<br />
{|<br />
|Bluetooth || Yes<br />
|-<br />
|Modem Speed || 56 Kbps<br />
|-<br />
|Network LAN || Broadcom BCM5751M Gigabit Ethernet<br />
|-<br />
|Network WLAN || Intel PRO/Wireless 2915ABG MiniPCI card<br />
|}<br />
<br />
== Software ==<br />
{|<br />
|Shipped Operating System || Microsoft Windows XP Professional<br />
|}<br />
<br />
== Connectors ==<br />
{|<br />
|Interface Provided ||Parallel Port, S-Video, VGA, Phone line, Headphone, Ethernet 10Base-T/100Base-TX/1000Base-T<br />
|-<br />
|Connectors ||2 x Hi-Speed USB - 4 pin USB Type A, 1 x parallel - IEEE 1284 (EPP/ECP) - 25 pin D-Sub (DB-25), 1 x display / video - VGA - 15 pin HD D-Sub (HD-15), 1 x infrared - IrDA, 1 x modem - phone line - RJ-11, 1 x network - Ethernet 10Base-T/100Base-TX/1000Base-T - RJ-45, 1 x display / video - S-video output - 4 pin mini-DIN, 1 x docking / port replicator, 1 x microphone - input - mini-phone mono 3.5 mm , 1 x audio - line-out/headphones - mini-phone stereo 3.5 mm<br />
|}<br />
<br />
== General Product Info ==<br />
{|<br />
|Input Devices || Keyboard, Touchpad, TrackPoint<br />
|-<br />
|Included Sound Card || Intel 82801FB (ICH6) rev. 03<br />
|-<br />
|Weight || 5,1 lbs<br />
|-<br />
|Also known as || ...<br />
|-<br />
|Manufacturer Part No. || 2668-8AG<br />
|-<br />
|Dimension || 31 mm x 329 mm x 268 mm (HxWxD)<br />
|-<br />
|Warranty || 3 years, international IBM warranty<br />
|}<br />
<br />
[[Category:T43]]</div>Mr.dnmehttps://www.thinkwiki.org/w/index.php?title=Hardware_Specifications&diff=22607Hardware Specifications2006-06-03T09:03:38Z<p>Mr.dnme: /* Available Models */</p>
<hr />
<div>{{Usage|<br />
*Choose a model name to get a list of all currently available information related to this Model.<br />
*Choose a type-and-model number to get the specs of that specific model.<br />
}}<br />
Here you can learn about specific ThinkPads specifications.<br />
<br />
Furthermore, you may<br />
*compare the [[ThinkPad series]] (G, R, T, X, Z),<br />
*get an overview of the [[ThinkPad History]] or<br />
*learn about the name [[ThinkPad]].<br />
<br />
==IBM/Lenovos hardware specs==<br />
* '''Lenovo ThinkPads'''<br />
** For current Lenovo ThinkPad G, R, T, X and Z series models look for the official specs listed in [ftp://ftp.software.ibm.com/pc/pcinstitute/psref/tabook.pdf tabook.pdf]<br />
** For withdrawn Lenovo ThinkPads, look at [ftp://ftp.software.ibm.com/pc/pcinstitute/psref/ltwbook.pdf ltwbook.pdf]<br />
* '''Withdrawn IBM ThinkPads'''<br />
** For A, G, T and X series models look for the official IBM specs listed in [ftp://ftp.software.ibm.com/pc/pcinstitute/psref/tawbook.pdf tawbook.pdf]<br />
** For R series models look for the official IBM specs listed in [ftp://ftp.software.ibm.com/pc/pcinstitute/psref/trwbook.pdf trwbook.pdf]<br />
** For i series models look for the official IBM specs listed in [ftp://ftp.software.ibm.com/pc/pcinstitute/psref/tiwbook.pdf tiwbook.pdf]<br />
** For 200, 300, 500, 600 and 700 series models look for the official IBM specs listed in [ftp://ftp.software.ibm.com/pc/pcinstitute/psref/twbook.pdf twbook.pdf]<br><br />
** Or try searching the IBM announcements letters [http://www.ibm.com/news/usalet/ here].<br />
<br />
==Available Models==<br />
{| cellspacing="0" cellpadding="5" border="1"<br />
|- style="text-align:left;"<br />
!Numbered!!A series!!G series!!R series!!S series!!T series!!X series!!Z series!!others<br />
|- style="text-align:left;vertical-align:top;"<br />
|<br />
'''[[:Category:390X | ThinkPad 390X]]'''<br />
*[[2626-L0U]]<br />
<br />
'''[[:Category:600E | ThinkPad 600E]]'''<br />
<br />
'''[[:Category:600X | ThinkPad 600X]]'''<br />
<br />
'''[[:Category:700 | ThinkPad 700]]'''<br />
<br />
'''[[:Category:760ED | ThinkPad 760ED]]'''<br />
<br />
'''[[:Category:760XD | ThinkPad 760XD]]'''<br />
<br />
'''[[:Category:770 | ThinkPad 770]]'''<br />
<br />
'''[[:Category:770E | ThinkPad 770E]]'''<br />
*[[9548-510]]<br />
*[[9548-51U]]<br />
*[[9548-52U]]<br />
<br />
'''[[:Category:770X | ThinkPad 770X]]'''<br />
*[[9549-7AO]]<br />
'''[[:Category:770Z | ThinkPad 770Z]]'''<br />
<br />
||<br />
'''[[:Category:A20m | ThinkPad A20m]]'''<br />
<br />
'''[[:Category:A20p | ThinkPad A20p]]'''<br />
<br />
'''[[:Category:A21e | ThinkPad A21e]]'''<br />
<br />
'''[[:Category:A21m | ThinkPad A21m]]'''<br />
<br />
'''[[:Category:A21p | ThinkPad A21p]]'''<br />
<br />
'''[[:Category:A22e | ThinkPad A22e]]'''<br />
<br />
'''[[:Category:A22m | ThinkPad A22m]]'''<br />
<br />
'''[[:Category:A22p | ThinkPad A22p]]'''<br />
<br />
'''[[:Category:A30 | ThinkPad A30]]'''<br />
<br />
'''[[:Category:A30p | ThinkPad A30p]]'''<br />
<br />
'''[[:Category:A31 | ThinkPad A31]]'''<br />
<br />
'''[[:Category:A31p | ThinkPad A31p]]'''<br />
<br />
||<br />
'''[[:Category:G40 | ThinkPad G40]]'''<br />
<br />
'''[[:Category:G41 | ThinkPad G41]]'''<br />
<br />
||<br />
'''[[:Category:R30 | ThinkPad R30]]'''<br />
<br />
'''[[:Category:R31 | ThinkPad R31]]'''<br />
<br />
'''[[:Category:R32 | ThinkPad R32]]'''<br />
<br />
'''[[:Category:R40 | ThinkPad R40]]'''<br />
*[[2722-9BM]]<br />
*[[2722-DG1]]<br />
<br />
'''[[:Category:R40e | ThinkPad R40e]]'''<br />
<br />
'''[[:Category:R50 | ThinkPad R50]]'''<br />
*[[1829-3HU]]<br />
<br />
'''[[:Category:R50p | ThinkPad R50p]]'''<br />
<br />
'''[[:Category:R50e | ThinkPad R50e]]'''<br />
*[[1834-J8G]]<br />
<br />
'''[[:Category:R51 | ThinkPad R51]]'''<br />
*[[1829-K6G]]<br />
*[[1829-L7G]]<br />
*[[1830-DG4]]<br />
<br />
'''[[:Category:R52 | ThinkPad R52]]'''<br />
*[[1846-B5G]]<br />
*[[1859-4AU]]<br />
<br />
||<br />
'''[[:Category:S30|ThinkPad S30]]'''<br />
<br />
'''[[:Category:S31|ThinkPad S31]]'''<br />
||<br />
'''[[:Category:T20|ThinkPad T20]]'''<br />
*[[2647-44G]]<br />
<br />
'''[[:Category:T21|ThinkPad T21]]'''<br />
*[[2647-97G]]<br />
<br />
'''[[:Category:T22|ThinkPad T22]]'''<br />
<br />
'''[[:Category:T23 | ThinkPad T23]]'''<br />
*[[2647-9RG]]<br />
*[[2647-7G1]]<br />
*[[2647-8QU]]<br />
<br />
'''[[:Category:T30 | ThinkPad T30]]'''<br />
*[[2366-52U]]<br />
*[[2366-83U]]<br />
*[[2366-91U]]<br />
*[[2366-FBG]]<br />
*[[2366-GU1]]<br />
*[[2366-JBG]]<br />
*[[2366-R7G]]<br />
<br />
'''[[:Category:T40 | ThinkPad T40]]'''<br />
<br />
'''[[:Category:T40p | ThinkPad T40p]]'''<br />
*[[2373-G1U]]<br />
<br />
'''[[:Category:T41 | ThinkPad T41]]'''<br />
<br />
'''[[:Category:T41p | ThinkPad T41p]]'''<br />
*[[2373-315]]<br />
*[[2373-GEG]]<br />
*[[2373-GGG]]<br />
*[[2373-GHG]]<br />
<br />
'''[[:Category:T42 | ThinkPad T42]]'''<br />
*[[2373-6ZG]]<br />
*[[2373-9XU]]<br />
*[[2373-CH6]]<br />
*[[2373-F1G]]<br />
*[[2373-F7G]]<br />
*[[2373-FWG]]<br />
*[[2373-M1G]]<br />
*[[2373-VUW]]<br />
*[[2373-WGK]]<br />
*[[2378-FVU]]<br />
*[[2378-RSU]]<br />
*[[2379-DXU]]<br />
<br />
'''[[:Category:T42p | ThinkPad T42p]]'''<br />
*[[2373-HTG]]<br />
*[[2373-W6M]]<br />
*[[2373-Y4M]]<br />
<br />
'''[[:Category:T43 | Thinkpad T43]]'''<br />
*[[2668-A1U]]<br />
*[[2668-C2U]]<br />
*[[2668-8AG]]<br />
<br />
'''[[:Category:T43p | Thinkpad T43p]]'''<br />
<br />
'''[[:Category:T60 | ThinkPad T60]]'''<br />
<br />
'''[[:Category:T60p | ThinkPad T60p]]'''<br />
||<br />
'''[[:Category:X20 | ThinkPad X20]]'''<br />
<br />
'''[[:Category:X21 | ThinkPad X21]]'''<br />
*[[2662-66U]]<br />
<br />
'''[[:Category:X22 | ThinkPad X22]]'''<br />
*[[2662-95U]]<br />
*[[2662-9BU]]<br />
<br />
'''[[:Category:X23 | ThinkPad X23]]'''<br />
<br />
'''[[:Category:X24 | ThinkPad X24]]'''<br />
<br />
'''[[:Category:X30 | ThinkPad X30]]'''<br />
<br />
'''[[:Category:X31 | ThinkPad X31]]'''<br />
<br />
'''[[:Category:X32 | ThinkPad X32]]'''<br />
<br />
'''[[:Category:X40 | ThinkPad X40]]'''<br />
*[[2371-AVC]]<br />
'''[[:Category:X41 | ThinkPad X41]]'''<br />
<br />
'''[[:Category:X41 Tablet | ThinkPad X41 Tablet]]'''<br />
<br />
'''[[:Category:X60 | ThinkPad X60]]'''<br />
<br />
'''[[:Category:X60s | ThinkPad X60s]]'''<br />
||<br />
'''[[:Category:Z60t | ThinkPad Z60t]]'''<br />
<br />
'''[[:Category:Z60m | ThinkPad Z60m]]'''<br />
||<br />
'''[[:Template:I_Series | I Series]]'''<br />
'''[[:Category:PC110 | PC110]]'''<br />
*[[PC110]]<br />
'''[[:Category:TransNote|TransNote]]'''<br />
*[[2675-61G]]<br />
|}<br />
<br />
<br />
[[Category:Models]]</div>Mr.dnmehttps://www.thinkwiki.org/w/index.php?title=Talk:How_to_make_ACPI_work&diff=22606Talk:How to make ACPI work2006-06-03T08:09:14Z<p>Mr.dnme: /* Auto-wake on lid open - how to STOP? */</p>
<hr />
<div>{{NOTE|Please sign and date your posts, that is much easier than trying to track down on page history who wrote what!}}<br />
<br />
== X41 Woes ==<br />
I have tried the referred patch (Suspend to RAM) with the latest stable kernel (2.6.12.2): Reboot after wakeup.<br />
<br />
== T22 Woes ==<br />
<br />
Has anyone managed to get this working with a T22? The BIOS is upgraded, but it _never_ wakes up from sleep. Neither lid nor pwr button are noticed by the system.<br />
<br />
--Are you in suspend2ram? This works fine for me. I think you have to enable it in BIOS.<br />
<br />
== Sound-after-suspend not working with Mandriva 2006 ==<br />
With Mandriva 2006, suspend/resume works with ACPI, but sound quits working. <br />
This happens with the T20 and T22. The recommended Mandriva trick of setting "RESTORE_SOUND=yes" in the "suspend" script doesn't solve this. Other suggestions? - MarkStosberg mark@summersault.com<br />
<br />
== Solutions ==<br />
I had 2 different issues:<br />
- with my X21 I had to unload the alsa modules before suspend.<br />
- with my x23 I have to change the mixer settings to get it working again.<br />
<br />
(I hope it will help)<br />
<br />
== CIFS ==<br />
Hi all,<br />
<br />
I have found out that if I use cifs to mount Samba shares, I get lots of problems with suspend/hibernate (the cifsd breaks the shutdown process). Maybe it would be good to warn about this.<br />
<br />
Alex (alex at corcoles dot net)<br />
<br />
== Auto-wake on lid open - how to STOP? ==<br />
<br />
Anybody have any idea how to stop the machine (a T43p) from automatically waking up on lid open? My /etc/acpi/events only has a lm_lid file which is commented out - it should do nothing, and there is no plain 'lid' event. Is lm_lid an event only activated when in laptop-mode?<br />
<br />
----<br />
<br />
That's a good question, but I have the opposite problem: my T43 (2687) won't wakeup from S3 (suspend-to-RAM) when I open the lid, which is exactly what yours do, and what I wanted mine to.<br />
<br />
-- [[User:Hmh|hmh]] 2006-03-24 11:59:00 UTC-0300<br />
<br />
----<br />
<br />
Yes, I have the same problem - this 'feature' is exhibited in both O/S's on my T43p... I tried everything I could think of to stop it (changing/deleting the acpi event handlers, etc). There does not seem to be any BIOS option to "wake up on lid open."<br />
<br />
It has irritated me less over time; I find myself now using suspend if I don't want the feature, and sleep mode only if I anticipate that I will open it up and use. After all, suspend is pretty quick with 1 GB ram.<br />
<br />
-- [[User:gsmenden|gsmenden]] 2006-03-27 19:36:55 EST<br />
----<br />
Just a note...the term "suspend" refers to both, suspending to RAM and suspending to disk, the counterpart to the "sleep" term is "hibernate". We should try to stay clear about this everywhere to avoid confusion.<br />
<br />
[[User:Wyrfel|Wyrfel]] 10:24, 29 March 2006 (CEST)<br />
----<br />
<br />
There is a /proc/acpi/wakeup file here. (t42p). Currently shows: <br />
Device Sleep state Status<br />
LID 3 * enabled<br />
SLPB 3 * enabled<br />
PCI0 3 disabled<br />
UART 3 disabled<br />
PCI1 4 disabled<br />
USB0 3 disabled<br />
USB1 3 disabled<br />
AC9M 4 disabled<br />
<br />
Echoing the 4 letter code toggles that device as a wakeup device.. ie:<br />
root# echo " LID" > /proc/acpi/wakeup<br />
root# cat /proc/acpi/wakeup<br />
Device Sleep state Status<br />
LID 3 *disabled<br />
<br />
Does that work for any of you guys? <br />
[[User:Nirik|Nirik]] 23:15, 29 Mar 2006 (MST)<br />
<br />
----<br />
<br />
I encountered the same problem and echoing to /proc/acpi/wakeup made the LID, the SLPB and the UART disabled (on my T43 - no matter what I did). The syslog told me that it was due to the fact they all share the same ACPI GPE.<br />
<br />
After reading much on ACPI and the kernel handling, I think the reason is that the kernel code activates all _PSW supporting devices (which includes the LID).<br />
<br />
I wanted to refrain from altering kernel code so I modified the ACPI DSDT (funny).<br />
At first I changed the GPE for the LID so it won't share it with the UART and the SLBP (which I believe is the "FN" button). Then when I saw it worked, but I had to keep echoing "LID disable" to /proc/acpi/wakeup so I erased the _PSW and _PRW entirely from the control method of the _LID device.<br />
<br />
Now my laptop only wakes up when "FN" is pressed. I can post the DSDT modification or elaborate on my solution if you please.<br />
<br />
[[User:mr.dnme|Mr DNME]] 11:00 3 May 2006 (UTC+0300)<br />
<br />
----<br />
<br />
== R50e - suspend to ram with DRI on ==<br />
<br />
Does anyone got this working? After resume the X do not refresh properly applications (the panel, application content and background).</div>Mr.dnme