The rEFInd thing, I think is actually a product of massive changes in the efistub kernel code, as I know that it was revamped significantly only recently (and when the troubles started).
In any case, I will keep the fingers crossed for you
]]>Hasn't fixed the rEFInd/EFI stub loader bug for me, though. The BIOS update got me bluetooth again but didn't affect the boot bug. Still, at least it *does* boot. Indeed, at least it switches on. In fact, it even reboots now which is somewhat amazing. (I thought maybe this was some Linux thing...)
]]>I really fail to understand how they could even think it was the right thing to ask you, the customer with 24-hour on-site service, to come to them.
In any case, I hope this is the fix you have been waiting for!
]]>[rant]
Lenovo still suck, though. Apart from anything else, I had to make two trips to them despite having an on-site next-business-day warranty, they did bugger all for over a week as they didn't have a driver (they told me they were ordering parts which seemed weird without seeing the machine but still), then they failed to set the model and serial number correctly so I got errors every boot after updating BIOS and then they tried to make me go to them again so they could avoid coming on-site to fix it. And these are the local people who are almost infinitely better than the centralised Lenovo lot.
[/rant]
*I use quotes around "next" because they were contacted Monday night and said they would be there Wednesday because calling after they closed technically counted as the next business day. I don't understand why they call it 24 hour on-site support then, if it is really "next business day support". And what happens on weekends, is it 24 hours after the next open Monday?
]]>When I called them, they said something about ordering parts and that they would call. 10 days later, nothing. When I call, they say they can come next week (more than 2 weeks after my initial call) and then look and then maybe order parts. This is next business day onsite support? In the end I took the damn thing to them but am not very happy because I don't drive and the person I bugged for a lift is not well and not at all happy about it. Grrr...
]]>Lenovo are finally taking a look. Of course, it behaved perfectly in their presence which more-or-less left me standing there saying "But there really is something seriously wrong with it. Honest." Also, I forgot the LTS kernel doesn't shutdown cleanly so I had to explain that really was a software thing. Grrrr....
Anyway, I hope they take a look and don't wipe my hard drive. (This would not be the end of the world but would be very aggravating.)
I am glad to hear that you are at least making some headway with Lenovo. I think that is how things always are... it is like your computer knows when you take it to a technician, so it behaves in an attempt to make you look like an ass. It really is unfortunate that these shutdowns are indeed so random...
]]>Anyway, I hope they take a look and don't wipe my hard drive. (This would not be the end of the world but would be very aggravating.)
]]>So I'm currently booted with hpet=disable to test but I *still* get "ACPI: HPET id" in the journal
Yeah, me too, but it doesn't matter - hpet gets recognized but not used, so no problem. I know if/when hpet is used, because I get the occasional pause.
Anyway, your laptop has a hardware problem, send it back
]]>cfr wrote:There is no occurrence of hpet in the output of journalctl -b after the switch to tsc.
Look *before* also. If you have e.g. "ACPI: HPET id:", then that's bad, if you're doing my test.
Just change your bootup commandline, and reboot, and see if the laptop's more stable. Too much chatter.
So I'm currently booted with hpet=disable to test but I *still* get "ACPI: HPET id" in the journal:
Ebr 01 19:28:58 MyComputer kernel: ACPI: HPET 00000000bafea000 00038 (v01 LENOVO TP-8Q 00001160 PTL 00000002)
Ebr 01 19:28:58 MyComputer kernel: ACPI: HPET id: 0x8086a301 base: 0xfed00000
Ebr 01 19:28:58 MyComputer kernel: hpet_acpi_add: no address or irqs in _CRS
That is, it has made a difference because I don't get a clockevent etc. but if the id alone indicates it isn't properly disabled, then hpet=disable alone doesn't seem to be cutting it.
I'm pretty sure there's a hardware issue but I've lost work twice today and I figured I'd try something just to try to reduce the symptoms...
EDIT: Certainly didn't work anyway... Trying the LTS kernel just for kicks really.
]]>Anyway, I'll try to find time to have a go tomorrow. Today's a bank holiday so I can't do anything today.
]]>The last time though, I had to ship the machine back. I have heard of people having to wait two weeks for this. But I got the box to overnight my machine on Tuesday, shipped it that same day, and got it back on Thursday morning. It was actually unbelievably fast.
Regarding your machine, you are certainly the one one I have heard of who has such extensive problems. And now it sounds like you have more than one. The shutdown thing you have been talking about for a while, and the funky ass firmware with the bluetooth, that same firmware that is picky with the UEFI/bios/GPT/MBR combos, and now with sometimes not even completing POST. That is not good.
To me, since you have paid for the extended warranty, and they seem somehow not know that, you should throw wild accusations of them blatantly stealing from you, and yell at them about owing you additional support time for the time in which you were not able to get it. You definitely need to make an (over the phone) scene... if the local people can't help you further.
]]>Thanks for the vote of confidence. Why can't Lenovo just develop a decent customer service department rather than forcing everybody to play such a time-consuming and frustrating game? They're worse than Apple and I didn't think much of Apple either. (But Apple's hardware seems more reliable.)
]]>