Thinkpads Forum

Just installed latest bios: http://forum.51nb.com/thread-1716835-1-1.html

Keyboard now works as expected. There is also possibility to swap ctrl and fn.

I didn't notice any other changes. Fan is too sensitive.

Running pwmconfig I see the message "Note that many motherboards do not have pwm
circuitry installed, even if your sensor chip supports pwm." Think that's the case here, where the 51nb guys didn't install it because they didn't feel it was necessary? Is a BIOS update with basic fan controls even possible? Surely if they made the fans this sensitive they can ease it up a bit.

fatpolomanjr wrote:Think that's the case here, where the 51nb guys didn't install it because they didn't feel it was necessary?

In Thinkpads fan control is done by the firmware on the embedded controller. I also believe that the thinkpad_acpi module will not load without that EC present.
There will be good legal reasons why the 51nb mainboard cannot have this chip with the Lenovo firmware.

el-sahef wrote:I am relieved to hear that . I absolutely need them for my QXGA screens and the X62 tablet. I get used to those kits, screens without them become suddenly almost unusuable.

I see you've made really good headway on getting tablet stuff working (which I really want) so I'd make you a few kits for a fair trade regardless. I expect you've seen the QXGA experiment (and that it wasn't entirely successful). Or did a prism/waveguide transplant fix everything?

The fan issues might be a good call for development of a small sub-board to do fan control based on system temperature.

andykrej wrote: Keyboard now works as expected.

What was wrong before?

mdancer wrote:

andykrej wrote: Keyboard now works as expected.

What was wrong before?

Two keys were disabled on some keyboard layouts. Uk and Danish was affected. US was not.

Nothing surprising, but I've finally tested my LED retrofit kits with both rev1 and rev2 X62 boards, and everything seems to work as expected, that is, exactly like on the original X61.

Has any progress been made with Linux and the speaker?

Can somebody share the new bios version?

Bibin wrote:Has any progress been made with Linux and the speaker?

No hope here, as I see it, unless somebody can code a patch for alsa. I've tried all available card models for alc662. Looks like realtek requires special driver controls for speaker amplifier. Here are some quotes from alsa documentation which shows all the complications:

A speaker output often requires more additional controls like the external amplifier bits.
If none of the available models works, send a bug report.
If you are masochistic enough to debug the driver problem, note the following:
- The speaker (and the headphone, too) output often requires the
external amplifier. This can be set usually via EAPD verb or a
certain GPIO. If the codec pin supports EAPD, you have a better
chance via SET_EAPD_BTL verb (0x70c). On others, GPIO pin (mostly
it's either GPIO0 or GPIO1) may turn on/off EAPD.
- Some Realtek codecs require special vendor-specific coefficients to
turn on the amplifier. See patch_realtek.c.
- IDT codecs may have extra power-enable/disable controls on each
- Very rare but some devices don't accept the pin-detection verb until
triggered. Issuing GET_PIN_SENSE verb (0xf09) may result in the
codec-communication stall. Some examples are found in patch_realtek.c.

mdancer wrote: No hope here, as I see it, unless somebody can code a patch for alsa.

That's somewhat up my alley. I've written alsa drivers in the distant past, I can try to get back into enough to debug this.

Have you tried the Linux driver from realtek:
http://www.realtek.com/downloads/downlo ... Down=false

andykrej wrote:Have you tried the Linux driver from realtek

The compilation throws errors on my machine. Is there anyone who was able to compile them? Probably these sources need at least adjustment to recent kernels.

I made a little progress trying to compile the Realtek drivers for Linux by changing a few things, but then ran into different errors. I'll summarize where I got, but it wasn't very far at all. Xubuntu 16.04.1.

Error I get after first attempted compile:
error: macro "__DATE__" might prevent reproducible builds [-Werror=date-time]

This one is fixed by searching for "__DATE__" via grep:
Change that string to "Compiled on __DATE__ for kernel %s" in whatever files grep found (for me it was in acore/info.patch). Once that is fixed you get a new error:

error: implicit declaration of function ‘do_posix_clock_monotonic_gettime’ [-Werror=implicit-function-declaration]
do_posix_clock_monotonic_gettime(&tstamp);

I can't get around this one. Closest answer I've got is here.

Does that file include time.h? I believe that is where it should be declared.

The error is found in the file acore/timer.c (within the source code directory), particularly in the function snd_timer_notify1. In that file, #include <sound/timer.h> is included.

e: I noticed in the header file /include/adriver.h that timer.h is only included if the Linux version is older:
So I removed the #if #endif lines and it is no longer an error. However I now have many more compiling errors coming from pcm_native.c. BUT it was the same issue in the header file: fget_light was never properly declared because of an #if #endif block that only links a specific .h file if the Linux kernel is a certain version. Even if this is clumsy, I'm starting to notice a pattern: just use the dependencies provided with the Realtek 5.18 drivers.

It would probably be better if I could get it to compile with just the default functions given in the Kernel, rather than using what was included in the Realtek source code directories. Though that might not be possible for such older drivers.

Slight change of topic, but has anyone noticed USB detection problems in Windows (7 specifically, in my case) ? I was trying to copy backups from one external HDD to another but either of them are rarely detected. No issues on Ubuntu, and I haven't explored the issue further yet. It caught my attention just enough to bother me and see if anyone else had similar issues...
Will update with more specific behaviour later

R

mdancer wrote:Can somebody share the new bios version?

I have sent you a PM

I don't think compiling the old Linux driver to get audio working is a good idea. I made a lot of progress manually editing C files to be compatible with the current Linux headers, but it is too much of a hassle at this point to continue on.

I'm just trying to fiddle with pulseaudio and alsamixer now. At least it recognizes the sound card is a Realtek ALC662 (rev 3). Someone else has been asking around about this too.

@flyingfishfinger: In Windows 10 my USB detection has been swell. I haven't explored Windows 7 at all.

Well, I haven't had a chance to look at the issue futher because of a far bigger problem that came up.
I was playing around with some BIOS settings (SATA in particular, trying to get a Hackintosh installer to recognize any HDD - common problem with that stuff, but irrelevant to the current dilemma). On rebooting, I now have a fully black screen, but fan & HDD seem to run. No boot screen or anything. I had this issue once before while trying this same thing, but the problem went away after I powercycled including removing the main battery.

This time, however nothing works. Tried removing and reseating the BIOS battery after a few minutes, remove / replace HDDs / RAM / main battery / basically everything that could be unplugged, but still no luck. It's not just the backlight either, nothing (dark) on the screen.

I'll let it sit overnight and see if it's any better in the morning, but does anyone have better ideas in the meantime? I hope this isn't a brick, that'd be odd for a BIOS setting.

Started new thread for this

R

flyingfishfinger wrote: And I don't mean to hijack the sound discussion, please let me know if you rather I start a new thread...

We probably want to break each problem debugging discussion out to a new thread. I can see this one getting big really quick.

Yeeeah fair. Alright, I'll copy mine out.

R

flyingfishfinger wrote:Yeeeah fair. Alright, I'll copy mine out.

R

It's probably a good idea to mention the issue in this thread tho. That way we have a master bug index

wileE wrote:X62 Tablet by el-sahef with working tablet buttons and wacom digitizer.
Link to german thread. Large pic warning!
Wacom rotation is unresolved, and that machine desperately needs a daylight LED kit.

i need this... the successor to x220!

I just got my DHL tracking number. How long did the shipment take for those who've received it?

Pretty fast for California. Like no more than 3 days if I remember correctly.

It's already in Ohio, which is stunning. If DHL does Saturday deliveries, maybe I'll even get it tomorrow. I've got a few X61 systems lying around, so by the end of this I'll have three - One X62 by 51nb, one X62 I asembled myself, and one X61 with a modified AFFS screen. All should be pretty close and ripe for comparison.

I had two X61 systems. The T8100 with the SXGA+ mod got bumped up to an X62, while the T7300 with the XGA inherited the T8100; both with monty's LED solution.

DHL was crazy fast for me. I just showed up home and there it was sitting on a chair.

Does bluetooth which is connected to LCD cable work? Or it's just me who forgot to connect it while assembling the machine.