You are not logged in.
gives no result.
Do I have to open the computer and reinsert Battery? As u know is not accessible from outside.
I am looking forward for any further help thank you again!!!!
Ok, so I tried it myself and it seems like the i2c-dev module isn't loaded automatically anymore.
# modprobe i2c-dev
After this, /dev/i2c-6 was available for me.
Hope this helps
Offline
# modprobe i2c-dev
After this, /dev/i2c-6 was available for me.
Hope this helps
Thank you very much. It did help!
Not when i run either
sudo i2cget -y 6 0x4f 175
or
sudo i2cget -y 6 0x4f 177
screen gets back but after reboot it is bricked again.
Sorry for my inpatient. command
sudo i2cget -y 6 0x4f 176
fixed it!!!!!
Thank you very much for your time, you are my today hero!
Last edited by jaruj9 (2015-11-03 19:59:35)
Offline
Sorry for my inpatient. command
sudo i2cget -y 6 0x4f 176
fixed it!!!!!
Thank you very much for your time, you are my today hero!
I'm glad that I could help.
I updated the lm-sensors wiki article, added a warning and linked to this thread to prevent future victims
Just out of interest: What exact model of Y50 do you have? The "old" ones (860m graphics and TN panel) or the new ones with IPS panels?
Would like to know if this only affects this exact TN panel that i had in my Y50 or all of them.
Last edited by 9233 (2015-11-03 20:11:03)
Offline
I'm glad that I could help.
I updated the lm-sensors wiki article, added a warning and linked to this thread to prevent future victims
Just out of interest: What exact model of Y50 do you have? The "old" ones (860m graphics and TN panel) or the new ones with IPS panels?
Would like to know if this only affects this exact TN panel that i had in my Y50 or all of them.
The old one. It is already 1.5 year old and yes with TN panel and 860m.
Thank you again!!
Offline
The old one. It is already 1.5 year old and yes with TN panel and 860m.
Thank you again!!
Okay thanks, I was curious to know if the new ones are affected too, but I doubt I'm willing to find out by trying
Have a nice day!
Offline
You need the same i2c modules you used to damage the display in the first place, i.e. i2c-dev and possibly some bus controller driver. Not eeprom.
Messing with RTC battery is pointless, as the "P" in EEPROM stands for "persistent".
Offline
You need the same i2c modules you used to damage the display in the first place, i.e. i2c-dev and possibly some bus controller driver. Not eeprom.
Messing with RTC battery is pointless, as the "P" in EEPROM stands for "persistent".
Oh, thanks for clarifying!
Offline
as the "P" in EEPROM stands for "persistent".
No it doesn't...
Electrically Erasable Programmable Read-Only Memory
Last edited by Slithery (2015-11-03 22:26:03)
Offline
And not all parameters are stored in EEPROM. Often it is NVRAM (Non Volatile Random Access Memory) -- this may be nothing more than CMOS static RAM backed up by (wait for it) a battery
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
mich41 wrote:as the "P" in EEPROM stands for "persistent".
No it doesn't...
Oops...
And not all parameters are stored in EEPROM. Often it is NVRAM (Non Volatile Random Access Memory) -- this may be nothing more than CMOS static RAM backed up by (wait for it) a battery
Go ahead and try. Half the princess and kingdom's hand if you manage to reset such panel by removing power for less than 20 years
Offline
Thxx Guysss!!!! my graphicals 970m
Offline
Hi all, I know this is a very old thread, but we have 2024 and I have a similar issue, which I believe started after running lm-sensors sensor-detect and answering yes to everything(no warning about this on lm-sensors github or the article I were reading).
I have a blinking white line, which is not persistent as it get smaller when the laptop is under load, so not totally the same as other have experienced, but 9 years has passed maybe the probe affect the hardware different or some other thing
I am not running Arch, but Linux Mint 20.2 Cinnamon, kernel 5.15.0-122-generic
Lenovo Thinkpad L540 20aua0f4jp, 16GB Ram, 240GB SSD, New UK keyboard, eDP AU Optronics B156XTN02.6 HD 1366x768 LCD H/W: 6A F/W:1 FRU 04X0513,
Link to specs:
https://pcsupport.lenovo.com/uu/en/prod … rce=Repair
Even though I am not running Arch, I hope some here can help me figure out if this is indeed lm-sensors again, and help me fix it - or if its hardware failure inside the laptop LCD cable or failing LCD.
Thank you in advance
Jan
Videos of the odd behaviour here: https://drive.google.com/drive/folders/ … drive_link
Offline
Linux Mint is not supported here as made clear to you when registering: https://bbs.archlinux.org/misc.php?action=rules
Ask on the channels of the distribution you're using.
Closing this necrobumped thread.
Offline