Tecra M7 : new bios shutdowns the digitizer when closing the lid.

it took me a moment to find the problem : power saving ? attacking wacom ? no. some very stupid "feature" in the new bios from Toshiba.
quote from the toshiba download site:
*Version 1.70 - 2006-10-24*
*Incorporated Intel requirements for improved stability.*
**Made changes to ensure that the digitizer is not activated when the LCD is closed.**
*Version 1.60 - 2006-09-21*
*Changed the temperature parameters.*
i have no idea what they were thinking but since when i move i often close the lid, it's very, very annoying because i need to reboot in order to get my tablet working again. the more recent features are not a matter, i'll keep xp pro.
now give me a download link to get the version 1.6 of the tecra M7 bios. thanks in advance, i count on you.

Hello
Fact is that Toshiba offers all tablet PCs with WXP tablet edition and many additional software that offer full functionality when you use this tablet PC in tablet or normal mode.
So, in my opinion you should use tablet edition and install all available Toshiba tools and utilities.
I dont have much experience with tablet PCs but if you check Toshiba Europe support and download page under http://eu.computers.toshiba-europe.com > Support & Download you will see that your Tecra is fully supported for WXP tablet edition and you can download all necessary stuff.
Interesting is that there is also ready for download Installation instruction document with exact installation order.
You can also visit Canadian download page under http://209.167.114.38/support/Download/ln_bymodel.asp and see what is available there.
I really think you need to install all Toshiba specific tools and utilities to have full control and possibility to use it in both modes.
Sorry I cannot tell you more about all this.

Similar Messages

I need a new Bios for the MSI k7n2 L!!!!!!!!

I need a new bios for the MSI k7n2 L, because i need more voltage for the MIcroprocesor and more voltage for the DDR.
Anybody know if exist some bios BETA or something,
And when MSI will release the New bios for this mother?
Thank for respond
Sory for my english
N7.net | SebaS

I hope you find one...(doubtlfully tho)....alot of people would like to have what you asked for......
One question why do you feel you need more voltages?
Is the system unstable?..........or do you just want to overclock more?

New BIOS for the MEGA.

We need one......for a number of reasons.
We need Prescott support, so the Celeron D would be an option. Northwood Celerons are getting scarce since they're out of production. My MEGA 651 could easily handle a slightly hotter Celeron....say 2.4 D. Most boards will handle Prescotts with only a BIOS upgrade. I have no reason to suspect otherwise with these MEGA boards.
My MEGA 651 has no option in the BIOS to adjust/change/turn off the fan control circuit. I would like to use Speedfan to control fan speeds.....but cannot. The board's own controller and the Speedfan program conflict, causing unstable fan operation. Most boards using auto-fan control let the user adjust the operation. The mega BIOS could be up-graded to do so.
I'd like to see some FSB adjustment in the BIOS....more than 100/133.
There are many improvements a new BIOS could offer....at very little cost to MSI. Maybe Doctor Stu could use some of his clout to get one written.

i don't have any clout
the 651 is an old model, so i doubt if we'll see any updates from MSI now, seeing as they will be pushing the new 865PRO now
unfortunately i also believe that the lack of prescott support is down to the SiS 651 chipset used, rather than MSI themselves

New Bios for the KT4 Ultra bfisr mobo

Hello all!
This is the first post for me in this forum, and i want to ask you guys if they fixed the new 1.4 bios and temp reading for the KT4 ultra motherboard?
Currently i am running bios 1.3 but like to stay uppdated hardware wise.
Would you guys recommend flashing to this new bios?
I used the LiveUpdate 2 utility last time and it worked flawlessly.
Hows the overclocking options in the new 1.4 bios?
Do Msi mess with the ram timings from bios to bios like my old abit mobo did?had to put slower timings from every uppgrade of bios with that board...does msi do the same thing?I wanna be able to run cas2 etc as i do atm.
Well that was it basicly.
All answers will be higly preciated.
TIA.

Hi,
Nope, the temp reading problem isn't fixed yet.
As it's still there in version 1.5B1.
MSI is investigating this.
As for HD speed, I have not seen a fix so far.
So if your system is stable at BIOS 1.3, stay with it.
As BIOS'ses are NOT updates but bug-fixes.
They only update they do is giving support for newer CPU's if needed.
Best not flash if you don't have problems.

Subscrition on New Resolution State fires also when closed

Hey there,
we do have a Installation of Scom 2012 R2 over here:
i created two subscriptions:
One for new Alerts and another one for closed Alerts.
Now i am facing the issue, my New Subscription (Criteria; Severity=Critical Resolution State=New) fires also, when the state is changed to Closed.
So i have for a new and closed Alert three Mails in my box (two with new and one with closed)
Any ideas?
best regards
Chris

Hi,
I assume there is something missed when you configure subscritions, would please re-check how did you configure new alert subscription and close alert subscription.
In addition, the two links below should be helpful to troubleshooting notification issues:
Alert notification troubleshooting in System Center Operations Manager
http://blogs.technet.com/b/operationsmgr/archive/2010/08/11/alert-notification-troubleshooting-in-system-center-operations-manager-2007.aspx
How To: Test Notification Settings & How To Solve Issues
http://thoughtsonopsmgr.blogspot.com/2011/03/how-to-test-notification-settings-how.html
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Sets into sleep when closing le lid, even with the display connected

I have the problem, that when I close the lid of my MacBook, it goes to sleep mod. This even happens when I connect the display. Even following the steps on the Apple.com page, it still goes into sleep mode.
Please help me avoid this sleep mode problem, I want to use my display instead of my computers screen. (yes, I have a wireless keyboard and mouse, paired all of them)
Thanks

Welcome to the Apple Discussions!
You can't avoid it. This is the way it's supposed to work.
If you have the AC adapter plugged in, an external display plugged in and an external mouse and keyboard (USB or Bluetooth), you can WAKE the computer after it's gone to sleep with the lid closed. But it will go to sleep when you close it. This is detailed here:
http://support.apple.com/kb/HT3131
-Doug

[SOLVED] how to prevent suspending/sleeping when closing laptop lid

Hi all,
My laptop, a Lenovo Thinkpad T430u, suspends whenever I close the lid. It's been doing this since I first installed Arch. I want to turn this feature off. How can I do it?
Relevant information:
acpid is installed
the configuration file /etc/acpi/handler.sh
#!/bin/bash
# Default acpi script that takes an entry for all actions
case "$1" in
button/power)
case "$2" in
PBTN|PWRF)
logger 'PowerButton pressed'
logger "ACPI action undefined: $2"
esac
button/sleep)
case "$2" in
SLPB|SBTN)
logger 'SleepButton pressed'
logger "ACPI action undefined: $2"
esac
ac_adapter)
case "$2" in
AC|ACAD|ADP0)
case "$4" in
00000000)
logger 'AC unpluged'
00000001)
logger 'AC pluged'
esac
logger "ACPI action undefined: $2"
esac
battery)
case "$2" in
BAT0)
case "$4" in
00000000)
logger 'Battery online'
00000001)
logger 'Battery offline'
esac
CPU0)
*) logger "ACPI action undefined: $2" ;;
esac
button/lid)
case "$3" in
close)
logger 'LID closed'
open)
logger 'LID opened'
logger "ACPI action undefined: $3"
esac
case $(cat /proc/acpi/button/lid/LID0/state | awk '{print $2}') in
closed) XAUTHORITY=$(ps -C xinit -f --no-header | sed -n 's/.*-auth //; s/ -[^ ].*//; p') xset -display :0 dpms force off ;;
open) XAUTHORITY=$(ps -C xinit -f --no-header | sed -n 's/.*-auth //; s/ -[^ ].*//; p') xset -display :0 dpms force on ;;
esac
logger "ACPI group/action undefined: $1 / $2"
esac
# vim:set ts=4 sw=4 ft=sh et:
dmesg output:
[ 1530.790532] PM: Syncing filesystems ... done.
[ 1530.805678] PM: Preparing system for mem sleep
[ 1530.844445] Freezing user space processes ... (elapsed 0.01 seconds) done.
[ 1530.856658] Freezing remaining freezable tasks ... (elapsed 0.10 seconds) done.
[ 1530.963435] PM: Entering mem sleep
[ 1530.963572] Suspending console(s) (use no_console_suspend to debug)
[ 1531.123543] iwlwifi 0000:03:00.0: iwl_pcie_cmdq_reclaim: Read index for DMA queue txq id (9), index 207 is out of range [0-256] 208 208.
[ 1531.124216] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 1531.124579] sd 0:0:0:0: [sda] Stopping disk
[ 1531.360682] mei 0000:00:16.0: suspend
[ 1531.440517] ahci 0000:00:1f.2: power state changed by ACPI to D3hot
[ 1531.687309] PM: suspend of devices complete after 722.490 msecs
[ 1531.687784] PM: late suspend of devices complete after 0.469 msecs
[ 1531.688232] pcieport 0000:00:1c.3: System wakeup enabled by ACPI
[ 1531.714222] ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
[ 1531.727619] ehci-pci 0000:00:1a.0: System wakeup enabled by ACPI
[ 1531.754015] xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI
[ 1531.767422] PM: noirq suspend of devices complete after 79.565 msecs
[ 1531.768301] ACPI: Preparing to enter system sleep state S3
[ 1531.797647] PM: Saving platform NVS memory
[ 1531.799282] Disabling non-boot CPUs ...
[ 1531.900721] smpboot: CPU 1 is now offline
[ 1532.004162] smpboot: CPU 2 is now offline
[ 1532.107554] smpboot: CPU 3 is now offline
I have pmutils and tlpinstalled
tlp config
# tlp - Parameters for power save
# Hint: some features are disabled by default, remove the leading # to enable them
# Set to 0 to disable/1 to enable TLP
TLP_ENABLE=1
# Seconds laptop mode has to to wait after the disk goes idle before doing a sync.
# Non-zero value enables, zero disables laptop mode.
DISK_IDLE_SECS_ON_AC=0
DISK_IDLE_SECS_ON_BAT=2
# Dirty page values (timeouts in secs).
MAX_LOST_WORK_SECS_ON_AC=15
MAX_LOST_WORK_SECS_ON_BAT=60
# Select a cpu frequency scaling governor: ondemand/powersave/performance/conservative
# Important:
# - You *must* disable your distribution's governor settings or conflicts will occur
# - ondemand is sufficient for *almost all* workloads, you should know what you're doing!
#CPU_SCALING_GOVERNOR_ON_AC=ondemand
#CPU_SCALING_GOVERNOR_ON_BAT=ondemand
# Set the min/max frequency available for the scaling governor.
# Possible values strongly depend on your cpu. For available frequencies see
# tlp-stat output, Section "+++ Processor".
# Hint: Parameters are disabled by default, remove the leading # to enable them,
# otherwise kernel default values are used.
#CPU_SCALING_MIN_FREQ_ON_AC=0
#CPU_SCALING_MAX_FREQ_ON_AC=0
#CPU_SCALING_MIN_FREQ_ON_BAT=0
#CPU_SCALING_MAX_FREQ_ON_BAT=0
# Set the cpu "turbo boost" feature: 0=disable / 1=allow
# Requires an Intel Core i processor and kernel 3.7 or later.
# Important:
# - This may conflict with your distribution's governor settings
# - A value of 1 does *not* activate boosting, it just allows it
#CPU_BOOST_ON_AC=1
#CPU_BOOST_ON_BAT=0
# Minimize number of used cpu cores/hyper-threads under light load conditions
SCHED_POWERSAVE_ON_AC=0
SCHED_POWERSAVE_ON_BAT=1
# Kernel NMI Watchdog
# 0=disable (default, saves power) / 1=enable (for kernel debugging only)
NMI_WATCHDOG=0
# Change CPU voltages aka "undervolting" - Kernel with PHC patch required
# Freq:voltage pairs are written to /sys/devices/system/cpu/cpu0/cpufreq/phc_controls
# CAUTION: only use this, if you thoroughly understand what you are doing!
#PHC_CONTROLS="F:V F:V F:V F:V"
# Hard disk devices, separate multiple devices with spaces (default: sda).
# Devices can be specified by disk id too (lookup with: tlp diskid).
DISK_DEVICES="sda sdb"
# Hard disk advanced power management level: 1(max saving)..254(off)
# Levels 1..127 may spin down the disk.
# Separate values for multiple devices with spaces.
DISK_APM_LEVEL_ON_AC="254 254"
DISK_APM_LEVEL_ON_BAT="128 128"
# Hard disk spin down timeout:
# 0: spin down disabled
# 1..240: timeouts from 5s to 20min (in units of 5s)
# 241..251: timeouts from 30min to 5.5 hours (in units of 30min)
# (see 'man hdparm' for details)
#DISK_SPINDOWN_TIMEOUT_ON_AC="0 0"
#DISK_SPINDOWN_TIMEOUT_ON_BAT="0 0"
# Select io scheduler for the disk devices: noop/deadline/cfq (Default: cfq)
# Separate values for multiple devices with spaces.
#DISK_IOSCHED="cfq cfq"
# SATA aggressive link power management (ALPM):
# min_power/medium_power/max_performance
SATA_LINKPWR_ON_AC=max_performance
SATA_LINKPWR_ON_BAT=min_power
# PCI Express Active State Power Management (PCIe ASPM):
# default/performance/powersave
# Hint: needs kernel boot option pcie_aspm=force on some machines
PCIE_ASPM_ON_AC=performance
PCIE_ASPM_ON_BAT=powersave
# Radeon graphics clock speed (profile method): low/mid/high/auto/default
# auto = mid on BAT, high on AC; default = use hardware defaults
# (Kernel >= 2.6.35 only, not with fglrx driver!)
RADEON_POWER_PROFILE_ON_AC=high
RADEON_POWER_PROFILE_ON_BAT=low
# WiFi power saving mode: 1=disable/5=enable
# (Linux 2.6.32 and later, some adapters only!)
WIFI_PWR_ON_AC=1
WIFI_PWR_ON_BAT=5
# Disable wake on lan: Y/N
WOL_DISABLE=Y
# Enable audio power saving for Intel HDA, AC97 devices (timeout in secs).
# A value of 0 disables / >=1 enables power save.
SOUND_POWER_SAVE=1
# Disable controller too (HDA only): Y/N
SOUND_POWER_SAVE_CONTROLLER=Y
# Set to 1 to power off optical drive in UltraBay (ThinkPads only)
# when running on battery. A value of 0 disables this Feature (Default).
# Drive can be powered on again by releasing (and reinserting) the
# eject lever or by pressing the disc eject button on newer models.
# Note: an UltraBay hard disk is never powered off.
BAY_POWEROFF_ON_BAT=0
# Optical drive device to power off (default sr0)
BAY_DEVICE="sr0"
# Runtime Power Management for pci(e) bus devices
# (Kernel >= 2.6.35 only): on=disable/auto=enable
RUNTIME_PM_ON_AC=on
RUNTIME_PM_ON_BAT=auto
# Runtime PM for *all* pci(e) bus devices: 0=disable / 1=enable
# Warning: experimental option, could cause system instabilities
RUNTIME_PM_ALL=0
# Set to 0 to disable/1 to enable usb autosuspend feature
USB_AUTOSUSPEND=1
# Devices from the following list are excluded from usb autosuspend
# (separate with spaces). Use lsusb to get the id's.
# Note: input devices (usbhid) are excluded automatically
#USB_BLACKLIST="1111:2222 3333:4444"
# Set to 1 to disable autosuspend before shutdown/0 to do nothing
# (workaround for usb devices that cause shutdown problems)
#USB_AUTOSUSPEND_DISABLE_ON_SHUTDOWN=1
# Restore radio device state (bluetooth, wifi, wwan) from previous shutdown
# on system startup: 0=disable/1=enable
# Hint: the parameters DEVICES_TO_DISABLE/ENABLE_ON_STARTUP/SHUTDOWN below
# are ignored when this is enabled!
RESTORE_DEVICE_STATE_ON_STARTUP=0
# Radio devices to disable on startup: bluetooth wifi wwan
#DEVICES_TO_DISABLE_ON_STARTUP="bluetooth wifi wwan"
# Radio devices to enable on startup: bluetooth wifi wwan
#DEVICES_TO_ENABLE_ON_STARTUP="wifi"
# Radio devices to disable on shutdown: bluetooth wifi wwan
# (workaround for devices that are blocking shutdown)
#DEVICES_TO_DISABLE_ON_SHUTDOWN="bluetooth wifi wwan"
# Radio devices to enable on shutdown: bluetooth wifi wwan
# (to prevent other operating systems from missing radios)
#DEVICES_TO_ENABLE_ON_SHUTDOWN="wwan"
# Radio devices to enable when wireless radio switch is turned on:
# bluetooth wifi wwan (Ubuntu + ThinkPad only)
#DEVICES_TO_ENABLE_ON_RADIOSW="wifi wwan"
# Battery charge thresholds (ThinkPad only, tp-smapi or acpi-call kernel module required)
# Charging starts when the remaining capacity falls below the START_CHARGE_TRESH
# value and stops when exceeding the STOP_CHARGE_TRESH value.
# Main battery (values in %)
#START_CHARGE_THRESH_BAT0=75
#STOP_CHARGE_THRESH_BAT0=80
# Ultrabay or slice battery (values in %)
#START_CHARGE_THRESH_BAT1=75
#STOP_CHARGE_THRESH_BAT1=80
# Set to 1 to disable use of tpacpi-bat on Sandy Bridge or newer Thinkpads
# and force usage of tp-smapi instead
#DISABLE_TPACPIBAT=1
# tlp-rdw - Parameters for the radio device wizard
# Possible devices: bluetooth/wifi/wwan
# Hint: parameters are disabled by default, remove the leading # to enable them
# Radio devices to disable on connect
DEVICES_TO_DISABLE_ON_LAN_CONNECT="wifi wwan"
DEVICES_TO_DISABLE_ON_WIFI_CONNECT="wwan"
DEVICES_TO_DISABLE_ON_WWAN_CONNECT="wifi"
# Radio devices to enable on disconnect
DEVICES_TO_ENABLE_ON_LAN_DISCONNECT="wifi wwan"
#DEVICES_TO_ENABLE_ON_WIFI_DISCONNECT=""
#DEVICES_TO_ENABLE_ON_WWAN_DISCONNECT=""
# Radio devices to enable/disable when docked
#DEVICES_TO_ENABLE_ON_DOCK=""
#DEVICES_TO_DISABLE_ON_DOCK=""
# Radio devices to enable/disable when undocked
#DEVICES_TO_ENABLE_ON_UNDOCK="wifi"
#DEVICES_TO_DISABLE_ON_UNDOCK=""
thanks guys
I love arch
Last edited by beitme (2013-06-08 10:05:37)

@ Karol, done
@ 65kid, here's my logind.conf
[Login]
#NAutoVTs=6
#ReserveVT=6
#KillUserProcesses=no
#KillOnlyUsers=
#KillExcludeUsers=root
#Controllers=
#ResetControllers=cpu
#InhibitDelayMaxSec=5
#HandlePowerKey=poweroff
#HandleSuspendKey=suspend
#HandleHibernateKey=hibernate
#HandleLidSwitch=ignore
#PowerKeyIgnoreInhibited=no
#SuspendKeyIgnoreInhibited=no
#HibernateKeyIgnoreInhibited=no
#LidSwitchIgnoreInhibited=yes
#IdleAction=ignore
#IdleActionSec=30min

IPod disconnected from iTunes when closing laptop lid

I recently received a new iPod Classic 120 Gb after the old one's battery died. When i connect the new one to my Macbook Pro and close the lid it disconnects from iTunes (it is still connected, it appears in Finder, just not in iTunes).
I got the latest version of iTunes and the iPod software. This never happened with the old iPod. Is there a fix for this?

Okay guys . I got some goodies up . For those interested:
- 2.6.22.12 kernel with CFS v22, hrtimers, powertop, Reiser4 and default CPU frequency governor 'ondemand'
- iwlwifi 1.1.21
- Authentec fingerprint reader driver
I guess that should get you going pretty much . The iwlwifi drivers have been built out-of-tree since my efforts to merging in the newer mac80211 stack & latest iwlwifi drivers amounted to nothing but a boatload of patch errors :-( (yes i can hack up patches to work but I felt like not doing it, since iwlwifi builds just fine out-of-tree). This kernel is tailored to the 6510 hardware, I cannot tell what is different in the 6170b lineup, but you definitely should not try this kernel on just any machine .
If you have any questions, drop me a line.
Credit of course to waninkoko for his kamikaze patchset, from which most of the patches come.
Update: to the latest 2.6.22.12 kernel + corresponding driver packages
Last edited by B (2007-11-11 16:39:48)

[Solved] preventing standby when closing laptop lid and more.

To be blunt, I'm on the verge of insanity at this point. I'm no newcomer to Arch, but this has me beat.
In short I'm not using my asus eepc 1015pem anymore, so I decided to make it a folding machine.
Everything works as intended except when I close the lid, it automatically goes to sleep and I haven't had any luck finding a solution.
All in all I have little use for any sort of power management, and things like CPU scaling and such, should obviously not be active.
So please do let me know where I can find the information I need.
My arch installation is completely basic and brand new, should that information matter
Best regards.
Last edited by zacariaz (2012-10-21 00:37:00)

2ManyDogs wrote:
zacariaz wrote:
WonderWoofy wrote:
You need to look into the powers of logind.conf (by that I mean the man page).
Also, I don't know why you would want to turn frequency scaling off. If it makes the cpu go full speed, so be it, but if not, it would be nice to not use quite as much power.
First of all, I want to thank you for the quick reply and secondly mention that this is a very low power device which will be running at full capacity 14/7, thus these think are not needed.
If it's running at "full capacity" cpu frequency scaling will allow the CPU to run at its top speed. There is no need to remove it. If at any point full speed is not required, even a low-power device will use less power with cpu scaling, and it allows the CPU to rest and cool off a little.
But hey, it's your box.
The reason it's important is only due to the doubt that the cpu might somehow be inhibited. If that's not the case, then it doesn't matter obviously.

Hard lockup when closing laptop lid (Linux 2.6.23)

I just found this out a few days ago, telling my laptop to shut down a few hours later, and still finding it running half a day later, severely overheated (!).
I am running a custom kernel (2.6.23.1 with some of the kamikaze broken out patches). I get this:
- I unplug the laptop USB mouse
- I close the lid
- I reopen the lid, only to find my system completely locked up (no screen refresh anymore, no possibility to switch to a virtual terminal, no possibility to restart X or restart the system (Ctrl+Alt+Del/Backspace aren't working at all).
I have no action specified for closing the lid (I plan on making it do suspend to RAM as soon as this issue is cleared up). Now if I leave the USB laptop mouse plugged in all works fine. I can close the lid, open it up again, and my system remains fully usable.
To make sure this wasn't just me being clumsy and compiling a bad kernel, I tried the 2.6.23-ARCH kernel from testing. It exhibits exactly the same behaviour. 2.6.22-ARCH works just fine.
Are there people having the same issue?
Last edited by B (2007-10-21 12:16:32)

Okay guys . I got some goodies up . For those interested:
- 2.6.22.12 kernel with CFS v22, hrtimers, powertop, Reiser4 and default CPU frequency governor 'ondemand'
- iwlwifi 1.1.21
- Authentec fingerprint reader driver
I guess that should get you going pretty much . The iwlwifi drivers have been built out-of-tree since my efforts to merging in the newer mac80211 stack & latest iwlwifi drivers amounted to nothing but a boatload of patch errors :-( (yes i can hack up patches to work but I felt like not doing it, since iwlwifi builds just fine out-of-tree). This kernel is tailored to the 6510 hardware, I cannot tell what is different in the 6170b lineup, but you definitely should not try this kernel on just any machine .
If you have any questions, drop me a line.
Credit of course to waninkoko for his kamikaze patchset, from which most of the patches come.
Update: to the latest 2.6.22.12 kernel + corresponding driver packages
Last edited by B (2007-11-11 16:39:48)

Challange to MSI.. New BIOS for the K8T that supports CoolNQuiet

MSI..
Lots of people are waiting. I hope that you will respond to this request soon. Asus already has theirs out!!?!?!
Simon

Quote
Originally posted by Bibihest
I just tried that beta BIOS, but it's not working for me at all... My speed is the same nomatter how long I wait.. Does anything else than CNQ need to be enabled in BIOS?? I don't think that Dynamic overclocking or anything else has to be enabled right??
Hope the next full bios will be out soon..
IT works. JUST read the faqs and you shuldnt have any problems.

P67A-GD55 Rev B3, When a new bios including Intel Raid Oprtion Rom 10.6.0.1091

P67A-GD55 Rev B3, When a new bios including Intel Raid Oprtion Rom 10.6.0.1091 ?
Hello,
I am the owner of a MSI motherboard P67A-GD55 (Rev B3).
The operating system Windows 7 Pro 64 bit is installed on a disk in AHCI OCZ Vertex 3120 Go SATA0 mounted on the port (version 3).
I get many bugs and blue screens.
This would be resolved with the latest driver Intel Rapid Storage Technology 10.6.0.1022.
It must been associated with a bios with the Intel RAID Option ROM 10.6.0.1091.
The latest bios for my motherboard is 1.E (or 1.14) version which includes Intel RAID Option ROM 10.5.0.1034.
Are there plans to release a new bios with the new ROM?
If not, is there a way to include the last Intel Option Rom in the bios 1.E?
Thank you in advance for your reply.
SM

Quote
I get many bugs and blue screens.
This would be resolved with the latest driver Intel Rapid Storage Technology 10.6.0.1022.
It must been associated with a bios with the Intel RAID Option ROM 10.6.0.1091.
What bugs and blue screens?
If this was a major issue as such, then everyone would be complaining about this.
>>Posting Guide<<

When will a new BIOS for K7N2G-LISR be released

Anyone have any idea when a new BIOS for the K7N2G-LISR will be released or if a new beta bios is available :D

I have a BIOS bug for MSI.
I can't disable the tv-out function. Therefore I can't watch any DVD's. I have to take out my G3 to enable me to adjust the onboard GFX settings and there is no option to disable tv-out as described in the manual.
I have emailed MSI and their tech support are either extremely busy or completely useless like their software.
This is completely driving me up the fecking wall!!!
I love MSI hardware but I have to avoid any MSI software like the plague... unfortunately the BIOS is unavoidable.
MSI, please sort this or I will be forced to return my hardware and look for another brand. I'm considering ABIT so be warned.
Could we draw up a list of bugs to give to MSI so we can try and get them sorted?
Sorry for the ranting, but theres not much I can do. :(
L8rz

When a new bios grrrrrrr for k8n

As title as i cant get a stable OC over 2185mhz grrrrrr
its a pain in the ***

I sent them this:
Quote
When will you guys be releasing a new bios for the K8N Neo Platinum that fixes the issues with false CPU temperature readings? As far as I know, none of the beta bioses that are out right now fix that particular issue. I have an AMD Athlon 64 3200+ (Clawhammer). My temperatures have ranged anywhere from 60C to 184C, it's obvious that these temperatures are wrong because the computer would should itself down somwhere around 75C. I am also sure the the CPU heatsink is seated correctly as I have reseated it many times. I took a look around on your forums and also noticed that I am not the only one having these problems as tons of people with Clawhammer and Newcastle cores are having the same problem. Is there an estimated release date for a fix on this?
Thanks, Alex
And this is what I got back:
Quote
Dear Alex,
Thank you for contacting MSI Technical Support.
The CPU temperature is different and there is tolerance difference between the data showed and the real temperature according to the CPU model and type and even produce date and manufactory . And this MB supports thermal protection function, it will prevent the MB and CPU from overheating. So please don't worry about the temperature.
We have tested various CPU with newcastle core in our lab but we can't find the same problem. We'll keep checking with AMD and contact them to get more different CPU to analyse it futher together with them. New BIOS will released right now if we have some findings and figure out the sloution. Sorry for any inconvenience caused.
Thanks for your supporting MSI product. Please feel free to let us know if you still have any further issues or inquires.
Best regards,
MSI Technical Support

Will there be a new bios

Will there be a new bios for the K8N neo platinum? or is 1.4 the last.
I know beta bioses are available, but I don't want to use those.

T2faag , yes there will be a new bios for Neo1 .Beta out with name 1.5b6 is proof of that .
When they are satisfied with the 1.5Betas they will release a 1.50 official based
of one or several of the betas with possible som last changes or merged changes.
But have no idea of the timeframe .
(boogieman ! you refer to Neo2 not Neo1 )

Tecra M7 : new bios shutdowns the digitizer when closing the lid.

Similar Messages

Maybe you are looking for