Hi,
I've got an Optimus V (W350STQ) and I've seen that there have been problems with the fan, seemingly cause by the bios. First of all, I'm running bios 1.0.0.9 and EC 1.0.0.3 and I occasionally get the fans going 100% for an hour or so. I'd like to see that fixed, but I will see how the other thread develops.
I also have some other problems, perhaps also with the bios, and I wonder if anybody can help - I'd like to know if my issues are real issues and not just Linux bugs! If we find these are genuine bios problems, will Clevo fix them with some badgering from pcspecialist?
1) I cannot change the Advanced settings in the bios. If I go into that menu, it shows an option for bluetooth which I cannot select. I can exit that section and there are no other options, where I might have expected, for example, controls for virtualisation. This brings me to 2)...
2) On booting, I get an error message - "Your BIOS is broken; DMAR reported at address 0!" This is related to virtualisation and from what I can gather, pops up when the DMAR table is genuinely broken or when virtualisation is disabled in the bios. But as I said in 1), I can't check or change this.
So, can people on Windows run a virtual machine? I might try installing an old version of MS Virtual PC which won't work without VT-d and see if it works, in order to find out if it is enabled or not. Does anybody have any experience running a VM on this machine that can help? My first attempts at running W7 under kvm result in the W7 setup telling me it couldn't configure something, which is unusual. Related?
3) Graphics driver errors - this could be a problem with the open source nvidia drivers, I don't know. What's interesting is that I can't find this error for non Clevo machines. If you look at http://retrace.fedoraproject.org/faf/problems/1130416/ (click on the 175743 tab), there is the same crash as I have had, but on the W230ST (13" Optimus). I get the same error message. Above it, I get some more messages, including:
nouveau E[ VBIOS][0000:01:00.0] 0x8955[0]: unknown opcode 0xaa
...
nouveau E[ PBUS][0000:01:00.0] MMIO read of 0x00000000 FAULT at 0x10f20c [ IBUS ]
...
nouveau E[ PBUS][0000:01:00.0] MMIO read of 0x00000000 FAULT at 0x17e8dc [ IBUS ]
...
mtrr: type mismatch for e0000000,10000000 old: write-back new: write-combining
...
nouveau E[ DRM] Pointer to TMDS table invalid
Maybe this is all irrelevant, however, as I can't find other references to this, perhaps it's something to do with the Clevo bios. It would be interesting to see if this goes away if the DMAR error goes away.
4) Brightness control problems - probably a Linux driver problem, but may be related to the above problems with the graphics drivers. The OS settings brightness control has no effect on the screen brightness. It does seem to change the brightness number though - the hotkeys on-screen indicator setting follows the OS setting. In fact, using the OS setting seems to be the only way to turn this value back up - the hotkeys will lower it, but not raise it. I've seen other threads about a W7 hotkey fix, so maybe something similar can be done for Linux.
Finally, it would be interesting to know how these problems interact with the fan issue. I guess the GTX765m interacts with the fans via a temperature sensor somehow, but if communication is broken in some way, as suggested by the graphics driver errors above, perhaps this might cause erratic fan behaviour.
I've got an Optimus V (W350STQ) and I've seen that there have been problems with the fan, seemingly cause by the bios. First of all, I'm running bios 1.0.0.9 and EC 1.0.0.3 and I occasionally get the fans going 100% for an hour or so. I'd like to see that fixed, but I will see how the other thread develops.
I also have some other problems, perhaps also with the bios, and I wonder if anybody can help - I'd like to know if my issues are real issues and not just Linux bugs! If we find these are genuine bios problems, will Clevo fix them with some badgering from pcspecialist?
1) I cannot change the Advanced settings in the bios. If I go into that menu, it shows an option for bluetooth which I cannot select. I can exit that section and there are no other options, where I might have expected, for example, controls for virtualisation. This brings me to 2)...
2) On booting, I get an error message - "Your BIOS is broken; DMAR reported at address 0!" This is related to virtualisation and from what I can gather, pops up when the DMAR table is genuinely broken or when virtualisation is disabled in the bios. But as I said in 1), I can't check or change this.
So, can people on Windows run a virtual machine? I might try installing an old version of MS Virtual PC which won't work without VT-d and see if it works, in order to find out if it is enabled or not. Does anybody have any experience running a VM on this machine that can help? My first attempts at running W7 under kvm result in the W7 setup telling me it couldn't configure something, which is unusual. Related?
3) Graphics driver errors - this could be a problem with the open source nvidia drivers, I don't know. What's interesting is that I can't find this error for non Clevo machines. If you look at http://retrace.fedoraproject.org/faf/problems/1130416/ (click on the 175743 tab), there is the same crash as I have had, but on the W230ST (13" Optimus). I get the same error message. Above it, I get some more messages, including:
nouveau E[ VBIOS][0000:01:00.0] 0x8955[0]: unknown opcode 0xaa
...
nouveau E[ PBUS][0000:01:00.0] MMIO read of 0x00000000 FAULT at 0x10f20c [ IBUS ]
...
nouveau E[ PBUS][0000:01:00.0] MMIO read of 0x00000000 FAULT at 0x17e8dc [ IBUS ]
...
mtrr: type mismatch for e0000000,10000000 old: write-back new: write-combining
...
nouveau E[ DRM] Pointer to TMDS table invalid
Maybe this is all irrelevant, however, as I can't find other references to this, perhaps it's something to do with the Clevo bios. It would be interesting to see if this goes away if the DMAR error goes away.
4) Brightness control problems - probably a Linux driver problem, but may be related to the above problems with the graphics drivers. The OS settings brightness control has no effect on the screen brightness. It does seem to change the brightness number though - the hotkeys on-screen indicator setting follows the OS setting. In fact, using the OS setting seems to be the only way to turn this value back up - the hotkeys will lower it, but not raise it. I've seen other threads about a W7 hotkey fix, so maybe something similar can be done for Linux.
Finally, it would be interesting to know how these problems interact with the fan issue. I guess the GTX765m interacts with the fans via a temperature sensor somehow, but if communication is broken in some way, as suggested by the graphics driver errors above, perhaps this might cause erratic fan behaviour.