Sony Vaio VGN-N27LH - some questions SOLVED

SOLVED - I installed the sony_acpi module from AUR and run the following to dim:
echo "4" > /proc/acpi/sony/brightness
Would still be grateful if anyone could advise on what else I need to consider when running linux on a laptop.  My original questions/post is below.
So I took the plunge and bought my first latop.
However, running linux is significantly more difficult and I'm feeling somewhat swamped.  On my desktop I just installed Arch and it ran fine.  With the laptop there are issues of power management, speed-stepping,suspend to disk, ACPI, etc, which are all new terms for me.  As I say, on the desktop I just installed Arch and it ran fine.  Nothing else to worry about.
Let's start at the beginning.  I installed the beta version as I couldn't get an internet connection with my older version.  Having done some reading I've installed a few things and added some daemons but am still struggling to lower the brightness of the laptop.
Below are some details:
[darrendowlut@MyBoX Linux Stuff]$ lspci
00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)
00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) Serial ATA Storage Controller IDE (rev 02)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02)
02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8036 PCI-E Fast Ethernet Controller (rev 16)
06:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
08:03.0 CardBus bridge: Texas Instruments PCIxx12 Cardbus Controller
08:03.1 FireWire (IEEE 1394): Texas Instruments PCIxx12 OHCI Compliant IEEE 1394 Host Controller
08:03.2 Mass storage controller: Texas Instruments 5-in-1 Multimedia Card Reader (SD/MMC/MS/MS PRO/xD)
# /etc/rc.conf - Main Configuration for Arch Linux
MODULES=(sky2 ipw3945 sonypi speedstep_centrino cpufreq_powersave cpufreq_conservative cpufreq_powersave cpufreq_stats cpufreq_userspace freq_table)
DAEMONS=(syslog-ng ipw3945d network cpudyn acpid hal powersaved alsa netfs !crond)
I'll be honest, I've no idea what half of those modules and daemons do!  I just know they are installed and load fine - there are no errors when the system boots.  What's more, I haven't edited any configuration files so whether those daemons are actually doing anything is anyones guess.
So, any ideas on how to get the brightness down?  Equally, are there issues that I need to be aware of when running linux on a laptop.  It seems to be running quite hot and I dont know whether this is normal or not?
Please don't shoot the noob.  Help greatfully received.  Be gentle.
Thanks.
Last edited by Ipsofacto (2007-04-09 16:56:39)

wiki has some info, one of the Vaio pages is written by
although its quite outdated it might give some hints (laptop-mode-tools for example) and inspire you to writte a new wikipage
they say kernel 2.6.21 has the vaio brightness control inside him, so I'm waiting for 2.6.22 to see how things work with Vaios
laptops aren't more difficult than desktops, Vaios are pain in the butt (its the first and the last I'll ever buy )

Similar Messages

  • Sony VAIO (VGN-NW130D) - Will Sony provided Windows 10 drivers for this model?

    Hello Sony, I have a Sony VAIO (VGN-NW130D). I purchased it new in 2009. It had Windows Vista preinstalled and a bought a Windows 7 disc for my computer. Here are my questions: http://community.sony.com/t5/VAIO-Windows-10/Windows-10-upgrade-Information/m-p/513320#U513320In the above link PeterT mentions the models that Sony will provide Windows 10 drivers for. Will these be the only models Sony will provided drivers for? http://esupport.sony.com/CA/p/os10upgrade.plIn the above link Sony says it will provide drivers for models that had Windows 7 and 8 preinstalled. What if you bought a Windows 7 disc? I have tried to install Windows 10 by forcing it to do so by command prompt, and by Installing it from Microsoft's website. Both tries where unsuccessful. It would get stuck on the black upgrading screen at 32% overall and 6% installing windows features and drivers. I reserved my copy of Windows 10 and my computer meets Windows 10 requirements. If my computer meets Microsoft's requirements my PC manufacturer should provide the Windows 10 drivers. If Sony choose not to provided Windows 10 drivers for all their PC that are compatible with Windows 10, it will be really off putting and resulting in me never purchasing another Sony PC. It tarnishes a company's reputation when they do unfair things like this. This would just not be fair Sony. Sincerely,Concerned Sony customer (thinking of switching to a Mac after this horrible experience)

    Light wrote:
    Hello, Thanks for the replay. How do you know what vendors our computers need drivers from? Do you know if Microsoft might provide us with drivers? Been reading some of the other posts and found out that Sony has sold the VAIO brand. I will never be buying another Sony computer or other Sony products again. This is just bad customer service.Sony has said that we will have to get drivers from Microsoft.  Or we will have to use the drivers that come with Win 10.  You have to read other topics in this forum to find this. I have two VAIO's that aren't on the Sony supported list and one VAIO that IS on the supported list. I have to wait until Sony proivides the drivers for my supported VAIO. I will have to wait until Microsoft provides drivers for my other VAIO's. I have a fourth desktop generic PC that I have upgraded from XP to Win 7.  I tried to install Win 10 on it but the Win 10 video driver only supported VGA for my legacy video board.  I rolled Win 10 back to Win 7 and I will wait until I can get a Win 10 driver for my video card.  If I can't get one, I will have to replace the video board with something that has Win 10 drivers. I won't have that option for my VAIO's because I can't replace the video boards.  If Microsoft or GeForce don't provide a driver for my video boards, I will not install Win 10.  I don't like it as much as Win 7, from what I've seen so far.

  • Sony VAIO VGN-FW11E - can't set brightness

    Hello everyone!
    I have really annoying problem with my laptop - setting brightness just don't work. I have tested many others distributions and this work only under Ubuntu 9.10 beta. I think that is connected with this. How can I use this patch  in arch?
    Laptop: Sony VAIO VGN-FW11E
    Graphic card: ATI Radeon HD3470
    I'm sorry for my english but people in polish forum just can't help me ;p

    oskar.einstein wrote:
    @B I'm not able to make so specific changes like you said. I can build something from AUR, sometimes also make some changes to PKBUILD's but doing something with dsdt is to hard for me.
    @litemotiv
    Do you think I shoud compile new kernel with new sony-laptop module inside?
    hmm, i'm not certain that will fix it for you..
    do you already have a fixed dsdt for your laptop? if you do, the best way is to compile a kernel with these lines added to the kernel config file:
    CONFIG_STANDALONE=n
    CONFIG_ACPI_CUSTOM_DSDT=y
    CONFIG_ACPI_CUSTOM_DSDT_FILE="DSDT.hex"
    that will definitely fix the brightness issue. the sony-laptop module is built by default, so you don't have to compile that specifically (the module is needed to get the function-keys on your keyboard working, it shouldn't have any influence on the brightness itself).
    if you don't have a custom dsdt yet, you need to make one following the instructions on the vaiobuntu blog. it's a bit daunting at first, but i assure you that it's doable.
    Last edited by litemotiv (2009-10-26 21:11:30)

  • M4 SSD 256GB 2.5 inch sometimes not booting on Sony Vaio VGN-FZ11E

    I installed a Crucial m4 SSD 256GB 2.5 inch on the Sony Vaio laptop VGN FZ11E using the kit provided. The operating system used is Windows Vista. The drive worked great the first time I booted the laptop, but since the second booting the system sometime stops while booting and I have to force the computer to restart till at some points it works (which can be after 1, 2, 3, 4 or even more attempts). The computer starts and the drive works for the first 10 seconds or so, then when the WLAN light of the laptop comes up, it stops working (no hard disk light). I have installed the last firmware, checked the drivers and made sure that the m4 drive is recognised and prioritized in the BIOS (this is the only drive installed, and it has a partition which is hidden). I have done a Power Cycle as recomended on the Crucial website, but this did not solve the problem. Any suggestions?

    Hi, I have the same issue you are describing, with "Operating system not found", not the one laurentzo says. My VAIO VGN-FE11H with BIOS R0174J3 gets stuck at this point, and that happens many times with this version of BIOS. With version R0074J3 also happened, but I have the perception that it was less usual. Anyway, I tried to upgrade my BIOS because the failure is unacceptable, and 8 of 10 times I can´t boot my laptop because the disk is not recognised, despite the fact that when it boots, everything works perferctly. My BX100 250GB firmware is MU02, and my situation is quite desperating, because the workaround that you suggest isn't working.Would you please update this firmware, or would you know any BIOS parameter that could make it boot at least half of the times??P.S.: I have also tried enabling AHCI on BIOS, etc.

  • Docking Station for Sony Vaio VGN-Z899GPB also know as PCG6122L

    Can anyone supply the part number for the docking station for a Viao laptop model number above? Thanks,Tony

     
    Hi TonyD,
    Welcome to Sony Community!
    We have limited information regarding the part number of the docking station (parts or accessories) of your unit. You may visit https://sony.encompass.com/ or call them for further assistance. They will be asking for the serial number or service tag number of your unit. They will be able to help you out as well about the parts and accessories of your unit. 
    Hope the link helps. 
    Thanks,
    Vincent 
    If my post answers your question, please mark it as "Accept as Solution"
     

  • Sony VAIO VGN nr475n Processor upgrade

    I want to speed up my vgn nr475n. I considered a processor and RAM upgrade so can you tell me which is the maximum GHz for my model and the best ram upgrade?

    So the market specs say the followinghttps://docs.sony.com/release/SPECS/VGNNR475NS_mksp.pdf Memory upgradeable to 4GB (also the chipset documentation states the max memory to be 4GB)
    Sometimes you can go beyond the memory specification because the manufacturer BIOS allows it and the hardware to go beyond 4GB to 8GB DOES existhttp://www.crucial.com/ProductDisplay?urlRequestType=Base&catalogId=10151&categoryId=&productId=10979&urlLangId=-1&langId=-1&top_category=&parent_category_rn=&storeId=10151 Processor is the Intel® Core™2 Duo Processor T5670 (2M Cache, 1.80 GHz, 800 MHz FSB)http://ark.intel.com/products/35163/Intel-Core2-Duo-Processor-T5670-2M-Cache-1_80-GHz-800-MHz-FSB Chipset is the Intel® GM965 Express Chipsethttp://ark.intel.com/products/29821#@specifications In the case of your VGN-NR475N, the Core2 Duo T5670 doesn't show a compatible products section which usually displays the list of compatible chipsets which in turn shows compatible processors. Looking at the Intel GM965 Express chipset specifications shows compatible processors and the fastest listed that has the same 800 MHz FSB like the currently installed T5670 is the Intel® Core™2 Duo Processor T9500 (6M Cache, 2.60 GHz, 800 MHz FSB). Supposedly the Intel GM965 also supports Extreme processors, but becareful the liklihood of compatibility on those processors are lower. Please note all of this information is speculative, but it's based off of existing documentation, there is a reasonable amount of certainty that the upgrades will work. It's all experimentation in the end. Lastly, upgrade to an SSD. That's the biggest bump in terms of performance although going to a Core 2 Duo T9500 will be noticiable. Use CPUID CPU-Z to confirm the specs on your laptophttp://www.cpuid.com/softwares/cpu-z.html Good luck! 

  • HT1349 I have a sony Vaio (VGN-NS190J).  Recently, my I tunes library does not stay in I tunes upon shutting my computer down.  When I start the computer up and open I tunes, I have to have I tunes find all my music files and repopulate? help please

    Can somebody help......regarding the above question..... I have had I tunes on this computer for several years without a problem.  I do use webroot as an antivirus software.  I have Windows Vista operating system and I am using the latest version of Itunes available.  When ever I open Itunes, my music, books, ect, ect. files are always gone and I have to ask Itunes to find them on my computer almost every time I open Itunes.  This problem has been going on now for about the last 6 months.  Nothing else wrong with computer.  Another issue associated:  I can create a playlist one night, and the next day I open  Tune, it's gone.  I would really appreciate any help.  Thank you.

    It can be that the library path, or files, are corrupted. What happens if you set a different path to save the library?

  • [SOLVED]Custom DSDT not loading - OEM battery doesn't work - Sony Vaio

    EDITING ORIGINAL POST TO POST SOLUTION so I don't do a massive bump
    Installed windows and ran the BIOS flasher that came with the battery. Didn't work until I changed a line in the plaintext configuration file (config.ini or something) it comes with. Changed "Capacity: 20" to "Capacity: -10". This changed the battery charge requirement from 20% to negative ten percent (any negative number will do), allowing the program to run and flash the BIOS. Didn't realize I could do that, but it fixed  the problem 100%.
    #### BEGIN ORIGINAL POST: ################################
    Hey guys,
    I'm a bit of a linux noob, but I've spent many hours this week trying to fix this issue on my own and have learned a lot about making custom kernels, hardware stuff, ACPI, and ABS. However, nothing I've done has worked and I've hit a wall. For reference, I'm on a Sony Vaio VGN-FZ4000 with linux-3.0 base kernel, gnome3/gdm. The battery is made in china and doesn't list a manufacturer, just model number BPS8, 52000mAh.
    [Backstory]
    So I recently got an OEM battery to replace the broken original, which hasn't worked since before I installed arch (though it worked with an Arch install I did a couple years ago). When I first plugged it in, the gnome battery symbol popped up listing the battery at 0% with an exclamation icon. I unplugged from AC power and the laptop still ran, but the battery monitor just said it was at 0% and 'Estimating' remaining time. I figured this was a glitch with gnome or just because it was this battery's first cycle so I let it run down until it hard-crashed. Then I plugged back into AC and tried to turn on the computer, but it wouldn't do anything until I removed the battery.
    Looking into the problem I discovered this was due to the ACPI firmware table DSDT being compiled for Windows, which has, shall we say, fewer restrictions on sanity than the Intel ASL compiler used for UNIX systems. Sure enough I extracted /sys/firmware/acpi/tables/DSDT to find that its section about the battery contained the entry 'Zero' for Battery Technology, which translates to "non-rechargeable", rather than 'One', which makes it chargeable. acpitool confirmed this; my system thought the battery was non-rechargeable and was constantly discharging it. Needless to say I've only been putting it in temporarily to test solutions since.
    [/backstory]
    [tl;dr] DSDT firmware contains malformed battery description, now I can't get my system to run with a custom DSDT. [/tl;dr]
    Attempted solutions:
    [1]
    Extract, modify, recompile DSDT and include it with the kernel compilation .config options
    CONIFG_ACPI_CUSTOM_DSDT=y
    CONFIG_ACPI_CUSTOM_DSDT_FILE="/usr/src/custom_dsdt.hex
    CONIFG_STANDALONE=n
    as suggested here, a page linked to by the arch wiki page on DSDT.
    I followed the instructions but no matter what this has generated errors during the kernel compilation, sometimes due to every line containing unexpected \231 (or other numbers) characters, sometimes finding some error in the DSDT file and then claiming that the driver it was compiling (ol.c somewhere in the drivers/acpi section I believe) had references to undefined functions all over the place. I CANNOT compile with a custom DSDT specified.
    [2]
    Place recompiled DSDT in /lib/initcpio/custom.dsdt and add 'dsdt' to the HOOKS in mkinitcpio (and rebuild the initramfs-linux-*.img, of course). Another version of this included recompiling the kernel with CONFIG_STANDALONE disabled.
    In neither of these situations has the running DSDT ever been anything but the BIOS-supplied one and not once has the battery shown any different behavior.
    acpitool and $ cat /proc/acpi/battery/BAT0/info have consistently claimed the information specified in the BIOS-supplied DSDT; the battery is non-rechargeable and is discharging at an unknown rate. Sometimes acpi will even report that the battery has zero capacity.
    The arch wiki does say mkinitcpio doesn't support the dsdt hook as of 2.6.30, but [1] didn't work either and mkinitcpio -H dsdt still told me to try this so I did.
    [3]
    The final solution I have tried has been to do [2] but to recompile the kernel with the legacy support for battery and ac adapter stuff disabled. I tried this because it was suggested in the kernel.log;
    Sep  13 11:51:03 localhost kernel: [   11.740059] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
    Sep  13 11:51:03 localhost kernel: [   11.753434] ACPI: AC Adapter [ADP1] (on-line)
    The corresponding line now reads
    ACPI: AC Adapter [ADP1] (on-line)
    (The same goes for the battery BAT0)
    but all this does is remove the battery/ and adp1/ folders from /proc/acpi/ and break acpitool functionality. The log still doesn't mention the dsdt hook, either.
    [4]
    The old way to do this was to use the acpi-dsdt-initrd-patch-* patch, but that hasn't been updated for modern kernels, presumably because of the new "functionality" from mkiniticpio. The current kernel .config doesn't include any options for ACPI initrd/initramfs support or reading a DSDT from initramfs, which is the functionality provided by this patch.
    This covers all the methods I've been able to find on the internet and I'm at a loss for what to do. Am I doing something wrong in [1]? Under what conditions will the compiler fail/succeed with a CONFIG_ACPI_CUSTOM_DSDT_FILE?
    When I recompile I fix the 'Zero' definition and a couple compiler errors and warnings. The errors come from section length definitions, which read as 0x00000000 rather than the appropriate max-min value so I fix those, and the warnings come from _T_* methods belonging to the compiler, so I refactor the code to remove the initial underscores. The last warning comes from an isolated And statement that's within brackets (compiler complains it doesn't do anything), but if I remove that the compiler fails hard.
    Thanks to anyone who's read this far.  Please let me know if you have any ideas how to get my system to use a customized DSDT.
    Last edited by paraffin (2011-09-29 23:20:30)

    Thanks for the offer, Radioactive man However, I'm actually compiling a customized kernel with the linux-ck and -sony patches, so your packages won't help. (The custom kernel works fine and I've tested this battery behavior on the the regular, -ck, and -sony kernels as well)
    Anyway, so I tried another compile with
    CONFIG_PREVENT_FIRMWARE_BUILD=n in addition to the options listed in [1] and that time it compiled.
    Unfortunately it still didn't load the DSDT!
    I did catch a quick little error message that turned up in kernel.log though;
    /var/log/kernel.log:Sep 15 11:50:24 localhost kernel: [    0.925780] acerhdf: unknown (unsupported) BIOS version Sony Corporation/VGN-FZ4000E/R2110J7, please report, aborting!
    acerhdf is a fan controller module for the Aspire One, and perhaps I left that in the kernel config and it's preventing the custom DSDT from loading, even though the acerhdf module never gets loaded itself, nor is it in my rc.conf or anything else... If that was the cause of all this, I'm gonna be angry...
    Anyway, this message does not appear with my latest kernel build because I took off the custom DSDT option, hoping to be able to use ACPI_CUSTOM_METHOD=y, which supposedly allows one to inject a custom AML method into a debug fs. It wouldn't have worked anyway, as it doesn't let you modify Device sections, but even with a dummy method insertion it didn't give my root modification privileges as it was supposed to...
    Will try recompiling AGAIN with this CONFIG_ACERHDF=n (it's simply 'not set' in my current .config), while also enabling the custom kernel etc. If this doesn't work I have no idea what I'll do.
    Anyway, thanks for your help and time:

  • Loading Officejet 7610 software caused Sony Vaio XP to crash

    Hi
    Loaded software for newly bought Officejet 7610 on my Sony Vaio (VGN-BX196VP) XP laptop
    In Programs clicked on Officejet 7610 - there was a warning of a threat from Norton re the file: HPOfficejet7610series\bin\HPsolutionsportal.hta
    But I ignored it - there couldn't be a problem here? - result -black screen with "Operating system not found"
    Many solutions on the web - would be grateful for any advice
    Thanks
    JF

    Hi hp7610,
    Welcome to the HP Forums.
    I see that you are having an issue with installing the printer on to you Windows xp computer.
    Before attempting to reinstall the printer, I suggest that we disable and firewalls or anti virus protection programs that you may have running.
    Here is the link for the HP Officejet 7610 series Full Feature Software and Drivers for Windows xp.
    Save this file to the Desktop and double click the new icon when the download is complete.
    Please feel free to write me back if you have any other questions.
    Cheers,  
    Click the “Kudos Thumbs Up" at the bottom of this post to say “Thanks” for helping!
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    W a t e r b o y 71
    I work on behalf of HP

  • Laptop-mode-tools/cpufrequtils Questions [SOLVED]

    I am running a Sony Vaio VGN-FW480J and am trying to optimize these two tools to save battery life and hard drive life span.   I have added @laptop-mode to my daemon array and acpi-cpufreq to modules. A few issues I immediately notice:
    1) cpufreq doesn't revert back to higher frequencies if I unplug and plug power source back in (before unplugging: CPU 0 - 800 MHz, CPU 1 - 2.00 GHz; after both are 800 and won't change if I plug power source back in)
    2) I believe the hard disk is actually spinning down more frequently (and fan is almost always on, even when no work is being done).  Here are the relevant files/the ones that I have altered.
    laptop-mode.conf
    # Configuration for Laptop Mode Tools
    # There is a "system" to the configuration setting names:
    # CONTROL_something=0/1 Determines whether Laptop Mode Tools controls
    # something
    # LM_something=value Value of "something" when laptop mode is active
    # NOLM_something=value Value of "something" when laptop mode is NOT
    # active
    # AC_something=value Value of "something" when the computer is running
    # on AC power
    # BATT_something=value Value of "something when the computer is running
    # on battery power
    # There can be combinations of LM_/NOLM_ and AC_/BATT_ prefixes, but the
    # available prefixes are different for each setting. The available ones are
    # documented in the manual page, laptop-mode.conf(8). If there is no LM_/
    # NOLM_ in a setting name, then the value is used independently of laptop
    # mode state, and similarly, if there is no AC_/BATT_, then the value is used
    # independently of power state.
    # Some options only work on ACPI systems. They are marked ACPI-ONLY.
    # Note that this configuration file is a fragment of shell script: you
    # can use all the features of the shell scripting language to achieve your
    # desired configuration.
    # Modules
    # Laptop Mode Tools modules have separate configuration files, that can be
    # found in /etc/laptop-mode/conf.d. Please look through these configuration
    # files as well, there are many useful power saving tools in there!
    # Enable/Disable laptop-mode-tools execution
    # Set it to 0 to completely disable laptop-mode-tools from running
    ENABLE_LAPTOP_MODE_TOOLS=1
    # Configuration debugging
    # Set this to 1 if you want to see a lot of information when you start/stop
    # laptop_mode.
    VERBOSE_OUTPUT=0
    # Set this to 1 if you want to log messages to syslog
    LOG_TO_SYSLOG=1
    # Run in shell debug mode
    # Enable this if you would like to execute the entire laptop-mode-tools program
    # in shell debug mode. Warning: This will create a lot of text output
    # If you are debugging an individual module, perhaps you would want to enable
    # each module specific debug mode (available in module conf files)
    DEBUG=0
    # When to enable laptop mode
    # "Laptop mode" is the mode in which laptop mode tools makes the computer
    # consume less power. This includes the kernel "laptop_mode" feature, which
    # allows your hard drives to spin down, as well as various other settings which
    # can be tweaked by laptop mode tools. You can enable or disable all of these
    # settings using the CONTROL_... options further down in this config file.
    # Enable laptop mode when on battery power.
    ENABLE_LAPTOP_MODE_ON_BATTERY=1
    # Enable laptop mode when on AC power.
    ENABLE_LAPTOP_MODE_ON_AC=1
    # Enable laptop mode when the laptop's lid is closed, even when we're on AC
    # power? (ACPI-ONLY)
    ENABLE_LAPTOP_MODE_WHEN_LID_CLOSED=0
    # Enable all simple zero-configuration auto modules
    # This option enables all simple modules (listed below) without requiring
    # the user to enable each module individually
    # List of modules which can be automatically enabled with this setting are:
    # ac97-powersave
    # cpufreq
    # dpms-standby
    # eee-superhe
    # ethernet
    # exec-commands
    # hal-polling
    # hdparm
    # intel-hda-powersave
    # intel-sata-powermgmt
    # runtime-pm
    # sched-mc-power-savings
    # sched-smt-power-savings
    # terminal-blanking
    # usb-autosuspend
    # wireless-ipw-power
    # wireless-iwl-power
    # wireless-power
    # Set this to 1 to enable all simple zero-configuration auto modules listed above.
    # NOTE: You can explicitly enable/disable any of the above modules by changing their
    # values in the individual settings file
    ENABLE_AUTO_MODULES=1
    # When to enable data loss sensitive features
    # When data loss sensitive features are disabled, laptop mode tools acts as if
    # laptop mode were disabled, for those features only.
    # Data loss sensitive features include:
    # - laptop_mode (i.e., delayed writes)
    # - hard drive write cache
    # All of the options that follow can be set to 0 in order to prevent laptop
    # mode tools from using them to stop data loss sensitive features. Use this
    # when you have a battery that reports the wrong information, that confuses
    # laptop mode tools.
    # Disabling data loss sensitive features is ACPI-ONLY, and it only works if
    # your battery gives off frequent ACPI events to indicate a change in battery
    # level.
    # NOTE: If your battery does NOT give off battery events often enough, you can
    # enable the battery-level-polling module to make this work. Look at the
    # file /etc/laptop-mode/conf.d/battery-level-polling.conf for more information.
    # Disable all data loss sensitive features when the battery level (in % of the
    # battery capacity) reaches this value.
    MINIMUM_BATTERY_CHARGE_PERCENT=3
    # Disable data loss sensitive features when the battery reports its state
    # as "critical".
    DISABLE_LAPTOP_MODE_ON_CRITICAL_BATTERY_LEVEL=1
    # Controlled hard drives and partitions
    # For spinning down your hard drives, laptop mode will remount file systems and
    # adjust hard drive spindown timeouts. These parameters specify which
    # devices and partitions are affected by laptop mode.
    # The drives that laptop mode controls.
    # Separate them by a space, e.g. HD="/dev/hda /dev/hdb". The default is a
    # wildcard, which will get you all your IDE and SCSI/SATA drives.
    HD="/dev/[hs]d[abcdefgh]"
    # The partitions (or mount points) that laptop mode controls.
    # Separate the values by spaces. Use "auto" to indicate all partitions on drives
    # listed in HD. You can add things to "auto", e.g. "auto /dev/hdc3". You can
    # also specify mount points, e.g. "/mnt/data".
    PARTITIONS="auto /dev/mapper/*"
    # If this is enabled, laptop mode tools will assume that SCSI drives are
    # really SATA drives that only _look_ like SCSI drives, and will use hdparm
    # to control them. Set this to 0 if you have /dev/sd devices and you want
    # laptop mode tools to use the "sdparm" command to control them.
    ASSUME_SCSI_IS_SATA=1
    # Hard drive behaviour settings
    # These settings specify how laptop mode tools will adjust the various
    # parameters of your hard drives and file systems.
    # Maximum time, in seconds, of work that you are prepared to lose when your
    # system crashes or power runs out. This is the maximum time that Laptop Mode
    # will keep unsaved data waiting in memory before spinning up your hard drive.
    LM_BATT_MAX_LOST_WORK_SECONDS=600
    LM_AC_MAX_LOST_WORK_SECONDS=360
    # Should laptop mode tools control readahead?
    CONTROL_READAHEAD=1
    # Read-ahead, in kilobytes. You can spin down the disk while playing MP3/OGG
    # by setting the disk readahead to a reasonable size, e.g. 3072 (3 MB).
    # Effectively, the disk will read a complete MP3 at once, and will then spin
    # down while the MP3/OGG is playing. Don't set this too high, because the
    # readahead is applied to _all_ files that are read from disk.
    LM_READAHEAD=3072
    NOLM_READAHEAD=128
    # Should laptop mode tools add the "noatime" option to the mount options when
    # laptop mode is enabled?
    CONTROL_NOATIME=0
    # Should laptop use relatime instead of noatime? The "relatime" mount option has
    # more standards-compliant semantics, and allows more applications to work,
    # while retaining a low level of atime updates (i.e., disk writes).
    USE_RELATIME=0
    # Should laptop mode tools control the hard drive idle timeout settings?
    CONTROL_HD_IDLE_TIMEOUT=1
    # Idle timeout values. (hdparm -S)
    # Default is 2 hours on AC (NOLM_HD_IDLE_TIMEOUT_SECONDS=7200) and 20 seconds
    # for battery and for AC with laptop mode on.
    LM_AC_HD_IDLE_TIMEOUT_SECONDS=20
    LM_BATT_HD_IDLE_TIMEOUT_SECONDS=20
    NOLM_HD_IDLE_TIMEOUT_SECONDS=7200
    # Should laptop mode tools control the hard drive power management settings?
    # Set to 0 to disable
    CONTROL_HD_POWERMGMT="auto"
    # Power management for HD (hdparm -B values)
    BATT_HD_POWERMGMT=128
    LM_AC_HD_POWERMGMT=254
    NOLM_AC_HD_POWERMGMT=254
    # Should laptop mode tools control the hard drive write cache settings?
    CONTROL_HD_WRITECACHE=0
    # Write cache settings for HD (hdparm -W values)
    NOLM_AC_HD_WRITECACHE=1
    NOLM_BATT_HD_WRITECACHE=0
    LM_HD_WRITECACHE=0
    # Settings you probably don't want to touch
    # It is usually not necessary to change these parameters. They are included
    # for completeness' sake.
    # Change mount options on partitions in PARTITIONS? You don't really want to
    # disable this. If you do, then your hard drives will probably not spin down
    # anymore.
    CONTROL_MOUNT_OPTIONS=1
    # Dirty synchronous ratio. At this percentage of dirty pages the process
    # which calls write() does its own writeback.
    LM_DIRTY_RATIO=60
    NOLM_DIRTY_RATIO=40
    # Allowed dirty background ratio, in percent. Once DIRTY_RATIO has been
    # exceeded, the kernel will wake pdflush which will then reduce the amount
    # of dirty memory to dirty_background_ratio. Set this nice and low, so once
    # some writeout has commenced, we do a lot of it.
    LM_DIRTY_BACKGROUND_RATIO=1
    NOLM_DIRTY_BACKGROUND_RATIO=10
    # kernel default settings -- don't touch these unless you know what you're
    # doing.
    DEF_UPDATE=5
    DEF_XFS_AGE_BUFFER=15
    DEF_XFS_SYNC_INTERVAL=30
    DEF_XFS_BUFD_INTERVAL=1
    DEF_MAX_AGE=30
    # This must be adjusted manually to the value of HZ in the running kernel
    # on 2.4, until the XFS people change their 2.4 external interfaces to work in
    # centisecs. This can be automated, but it's a work in progress that still
    # needs some fixes. On 2.6 kernels, XFS uses USER_HZ instead of HZ for
    # external interfaces, and that is currently always set to 100. So you don't
    # need to change this on 2.6.
    XFS_HZ=100
    # Seconds laptop mode has to to wait after the disk goes idle before doing
    # a sync.
    LM_SECONDS_BEFORE_SYNC=2
    cpufreq.conf
    # Configuration file for Laptop Mode Tools module cpufreq.
    # For more information, consult the laptop-mode.conf(8) manual page.
    # CPU frequency scaling and throttling
    # Laptop mode tools can automatically adjust your kernel CPU frequency
    # settings. This includes upper and lower limits and scaling governors.
    # There is also support for CPU throttling, on systems that don't support
    # frequency scaling.
    # This feature only works on 2.6 kernels.
    # IMPORTANT: In versions 1.36 and earlier, these settings were included in the
    # main laptop-mode.conf configuration file. If they are still present, they
    # overrule the settings in this file. To fix this, simply delete the settings
    # from the main config file.
    # Enable debug mode for this module
    # Set to 1 if you want to debug this module
    DEBUG=0
    # Should laptop mode tools control the CPU frequency settings?
    # Set to 0 to disable
    CONTROL_CPU_FREQUENCY="auto"
    # Legal values are "slowest" for the slowest speed that your
    # CPU is able to operate at, "fastest" for the fastest speed,
    # "medium" for some value in the middle, or any value listed in
    # /sys/devices/system/cpu/cpu*/cpufreq/scaling_available_frequencies.
    # The "governor" can be any governor installed on your system, this usually
    # includes "ondemand", "conservative", and "performance". The
    # "IGNORE_NICE_LOAD" setting specifies that background programs that have
    # a low priority ("nice level") should not cause the CPU frequency to
    # be increased. (You generally want this to be enabled in battery mode.)
    BATT_CPU_MAXFREQ=fastest
    BATT_CPU_MINFREQ=slowest
    BATT_CPU_GOVERNOR=ondemand
    BATT_CPU_IGNORE_NICE_LOAD=1
    LM_AC_CPU_MAXFREQ=fastest
    LM_AC_CPU_MINFREQ=slowest
    LM_AC_CPU_GOVERNOR=ondemand
    LM_AC_CPU_IGNORE_NICE_LOAD=1
    NOLM_AC_CPU_MAXFREQ=fastest
    NOLM_AC_CPU_MINFREQ=slowest
    NOLM_AC_CPU_GOVERNOR=ondemand
    NOLM_AC_CPU_IGNORE_NICE_LOAD=0
    # Should laptop mode tools control the CPU throttling? This is only useful
    # on processors that don't have frequency scaling.
    # (Only works when you have /proc/acpi/processor/CPU*/throttling.)
    # This is only useful on older P4 processors that do not support frequency
    # scaling. On such processors, this is the only way to reduce power consumption
    # but at the cost of higher performance penalty.
    # Enable this only if you have a processor that does not support frequency scaling
    # On most new processors, you might want to disable it.
    # Set to 0 to disable.
    CONTROL_CPU_THROTTLING=0
    # Legal values are "maximum" for the maximum (slowest) throttling level,
    # "minimum" for minimum (fastest) throttling level, "medium" for a value
    # somewhere in the middle (this is usually 50% for P4s), or any value listed
    # in /proc/acpi/processor/CPU*/throttling. Be careful when using "maximum":
    # this may be _very_ slow (in fact, with P4s it slows down the processor
    # by a factor 8).
    BATT_CPU_THROTTLING=medium
    LM_AC_CPU_THROTTLING=medium
    NOLM_AC_CPU_THROTTLING=minimum
    battery-level-polling.conf
    # Configuration file for Laptop Mode Tools module battery-level-polling.
    # For more information, consult the laptop-mode.conf(8) manual page.
    # Battery level polling settings
    # This module allows laptop mode to react to battery level changes, even if the
    # battery does not send out frequent ACPI events for such battery level changes.
    # Note that this does NOT make ACPI-only features work on non-ACPI hardware.
    # Enable debug mode for this module
    # Set to 1 if you want to debug this module
    DEBUG=0
    # Enable this setting to enable battery level polling.
    ENABLE_BATTERY_LEVEL_POLLING=1
    hal-polling.conf
    # Configuration file for Laptop Mode Tools module hal-polling.
    # For more information, consult the laptop-mode.conf(8) manual page.
    # HAL polling settings
    # If you enable this module, laptop mode tools will control the polling of
    # your CD/DVD drives by HAL. Disabling polling saves a considerable amount of
    # power, but for some older CD/DVD drives it means that inserted CDs are no
    # longer autodetected. In such cases, you must turn this option off.
    # Alternatively, you can configure laptop mode tools to turn HAL polling on only
    # when the laptop is running on AC power. This would mean that CDs are not
    # autodetected while the laptop is running on battery power, but the power
    # savings may be worth the extra manual labour when you insert a CD.
    # Enable debug mode for this module
    # Set to 1 if you want to debug this module
    DEBUG=0
    # Control HAL polling?
    # Set to 0 to disablei, vs "auto".
    CONTROL_HAL_POLLING=0
    # Disable HAL polling on battery?
    BATT_DISABLE_HAL_POLLING=0
    # Disable HAL polling on AC?
    AC_DISABLE_HAL_POLLING=0
    # Drives to apply HAL polling settings to
    HAL_POLLING_DEVICES="/dev/scd?"
    Please let me know if you require any additional information. Thank you in advance for any help.
    Last edited by Aesir (2011-04-14 14:35:09)

    Aesir wrote:Can I make BATT_CPU_GOVERNOR=conservative even if it is not listed in the scaling_available_governors file?
    If your governor isn't listed in scaling_available_governors, it won't work.  See stqn's link for info on adding governors.
    stqn wrote:Edit2: oh well, scrolling a bit up, the wiki says you don't need to add governors if you're using laptop-mode-tools... I don't know.
    You do need governors if you're using laptop-mode-tools, because all laptop-mode-tools does is flip between them automatically.
    If you're using cpufrequtils, you'll need the userspace governor for it to work properly.  I don't use cpufrequtils personally, so I'm not sure how to get it to work in conjunction with laptop-mode-tools.  You may have to disable frequency scaling in laptop-mode-tools by changing CONTROL_CPU_FREQUENCY to 0 in cpufreq.conf
    Edit - now that I think about it, maybe laptop-mode-tools and cpufrequtils know how to load the modules themselves automatically.  I guess try it and see if they can.  You can check which governor is in use with:
    $ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
    You can also manually change governors by running (as root):
    #  echo "conservative" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
    Of course, substitue the governor you want.
    Last edited by redden0t8 (2011-03-29 19:27:12)

  • Recording a movie using a Sony Vaio Motion Eye?

    So I have a Sony Vaio VGN-FZ38M, with an in-built motion eye camera. Whenever I try and use this in Premiere it doesn't work; the device is, apparently online. Is there a fix for this? There is another capture program that came with my laptop which I can use, but I'd rather capture it in Premiere because that's what I'm using to edit it.
    I am using Premiere Elements 4 on Vista Home Premium 32-bit.
    Thanks in advance :)

    your camera may be being used by other Sony utility and therefore PRe wont get the handle. Ask SOny for help.

  • [SOLVED] Sony Vaio Keys don't work (probably udev issue)

    Hardware: SONY VAIO VPC-EH2L1R
    Linux distribution: archlinux, XFCE
    udev versions: 177, 178 (core), udev-git 20120123-1 (AUR)
    keyboard driver: evdev
    At least a week earlier I had some of Sony Vaio Keys working: Volume control (Fn+F2: mute, Fn+F3: down, Fn+F4: up) and Brightness control (Fn+F5: down, Fn+F6: up). Other Vaio Keys (Fn+F1: touchpad switch, Fn+F7: switch video mode, Fn+F12: suspend) never worked.
    At some point (I think after updating to udev-177-1) Brightness control keys stopped working. Volume control keys still work.
    Brightness control still works directly via acpi.
    I know this may sound like this bug, but that solution doesn't work for me - neither updating to udev-git nor manually loading the keymap.
    My keyboards are:
    [ajaxas@r2d2 ~]$ /lib/udev/findkeyboards
    AT keyboard: input/event0
    module: input/event1
    which are actually:
    [ajaxas@r2d2 ~]$ cat /proc/bus/input/devices
    I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
    N: Name="AT Translated Set 2 keyboard"
    P: Phys=isa0060/serio0/input0
    S: Sysfs=/devices/platform/i8042/serio0/input/input0
    U: Uniq=
    H: Handlers=kbd event0
    B: PROP=0
    B: EV=120013
    B: KEY=402000000 3803078f800d001 feffffdfffefffff fffffffffffffffe
    B: MSC=10
    B: LED=7
    I: Bus=0010 Vendor=104d Product=0000 Version=0000
    N: Name="Sony Vaio Keys"
    P: Phys=
    S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/SNY5001:00/input/input1
    U: Uniq=
    H: Handlers=kbd rfkill event1
    B: PROP=0
    B: EV=13
    B: KEY=1f16cf0000 c00000000 10010000000000 200000000 600e00102c00 380000240300400 e000000000000 0
    B: MSC=10
    Now, the funny thing is that (I think) udev loads my keymap correctly:
    [ajaxas@r2d2 ~]$ cat /sys/class/dmi/id/{sys_vendor,product_name}
    Sony Corporation
    VPCEH2L1R
    Here is this keymap module-sony (which worked until recently!):
    [ajaxas@r2d2 ~]$ cat /lib/udev/keymaps/module-sony
    0x06 mute # Fn+F2
    0x07 volumedown # Fn+F3
    0x08 volumeup # Fn+F4
    0x09 brightnessdown # Fn+F5
    0x0A brightnessup # Fn+F6
    0x0B switchvideomode # Fn+F7
    0x0E zoom # Fn+F10
    0x10 suspend # Fn+F12
    - but here is where it starts getting curiouser and curiouser.
    My Volume control keys seem to be mapped to input/event0 (keyboard itself):
    [root@r2d2 ajaxas]# /lib/udev/keynap -i input/event0
    scan code: 0xA0 key code: mute
    scan code: 0xAE key code: volumedown
    scan code: 0xB0 key code: volumeup
    and these scan codes correspond not to my keymap (0x06, 0x07, 0x08), but to /lib/udev/keymaps/force-release/common-volume-keys:
    [ajaxas@r2d2 ~]$ cat /lib/udev/keymaps/force-release/common-volume-keys
    0xa0 #mute
    0xae #volume down
    0xb0 #volume up
    So I assume, udev uses force-release rules before other keymaps and maps my Volume control keys to input/event0 (how? I couldn't find the rule!), which is more or less fine with me, but!
    My Brightness control keys, mapped as 0x09 and 0x0A in the keymap, are reported by udev as:
    [root@r2d2 ajaxas]# /lib/udev/keymap -i input/event1
    scan code: 0x10 key code: brightnessdown
    scan code: 0x11 key code: brightnessup
    If I change my keymap file (0x09 -> 0x10, 0x0A -> 0x11) and load keymap manually, nothing changes. And when I reboot with this changed keymap, udev reports this for my Brightness control keys:
    [root@r2d2 ajaxas]# /lib/udev/keymap -i input/event1
    scan code: 0x10 key code: fn_f5
    scan code: 0x11 key code: fn_f6
    Again, nothing works, and keys are not reported as Brightness control keys anymore.
    As I said earlier, updating udev doesn't help.
    Could somebody please help me?
    EDIT: added keyboard driver (evdev) reference.
    Last edited by ajaxas (2012-01-25 13:52:54)

    jst wrote:
    ajaxas wrote:Okay, this is stupid but it was XFCE's fault. If anyone with the same problem reads this, try creating a new user account and see if it's actually udev or only your shitty DE. -_-
    How did you solve this? I realized I have the same problem with XFCE, but could not solve it
    I don't really remember. As a matter of fact, I've already switched to KDE and I'm quite content with it

  • [SOLVED] ACPI power issues with Sony Vaio Pro 13

    tl;dr backstory:
    Sony VAIO Pro 13 (SVP13215CDB) laptop was working great (Win 8.1).
    Installed Win10 Tech Preview. A week later, it started going to sleep randomly and on certain key-presses (perhaps after performing Sony Vaio Software updates. I'm not 100% sure). I wiped all partitions installing Win7 in legacy mode. It still went to sleep randomly.
    I restored to factory default Win8.1 with Sony Vaio software up-to-date. It still went to sleep randomly.
    Took it to an electronics repair shop, to see if they could fix it, and they said it can't be fixed in any way without replacing motherboard, but that's basically a new laptop.
    So I turned to Arch Linux.
    I have completed the basic install from the Wiki, and it no longer sleeps/shuts down randomly, but it will gracefully shutdown when certain events/keypresses occur.
    I installed acpid and used "acpi_listen >> acpi.log" to determine what causes the system to perform a graceful shutdown. Here is the result of acpi.log (each line was a shutdown event):
    button/power PBTN 00000080 00000000 # Unplugged power adapter.
    button/power PBTN 00000080 00000000 # Running on battery and idle. Perhaps battery percent update caused this?
    button/power PBTN 00000080 00000000 # Plugged in power adapter.
    button/power PBTN 00000080 00000000 # Fn-F1 Touchpad Disable
    button/power PBTN 00000080 00000000 # Fn-F5 Brightness Down
    button/power PBTN 00000080 00000000 # Fn-F6 Brightness Up
    button/power PBTN 00000080 00000000 # Fn-F7 LCD/External Display
    button/power PBTN 00000080 00000000 # Fn-1 (Weird. It has no extra function).
    As you can see, they all seem to trigger the same shutdown event.
    I have seen on other posts that these ACPI signals can be disabled or assigned to other commands, which would be an acceptable workaround if it stops my laptop from erroneously shutting down. Is this doable?
    Also, I was not able to reflash the Sony VAIO firmware when using Windows, as Sony's package software is amazing wouldn't allow flashing an equal or lesser firmware version. Perhaps there is a way in Arch to force a reflash if I can get my hands on the firmware blob?
    Thanks .
    Last edited by SafeToRemoveACPI (2014-11-25 22:55:55)

    linux /boot/vmlinuz-linux root=UUID=<UUID here> rw quiet acpi=off
    Like this?
    I did that, and it disabled my laptop keyboard entirely. In doing so, it disables the key-presses that would normally shutdown the laptop, including the power button. So the only way to shut it down is a hard shutdown via long-press of the power button. Thanks, though.
    Update: Issue Solved. I will update post tonight. Flashing the BIOS again resolved the ACPI issues.
    Last edited by SafeToRemoveACPI (2014-11-25 22:54:13)

  • Shift+ some keys missed in jumanji, dwm on Sony Vaio F12

    I have a strange issue on my Sony Vaio F12. Shift + some keys seem to become <some keys> only. For example Shift+space in jumanji is interpreted as Space only. Shift+Mod4+Ctrl+Q in dwm isn't caught properly, while Shift+Mod4+Enter is. xev seem to get it right, though. The state is 0x0 when pressing Space only, and 0x1 at Shift+Space.
    (Note: I'm currently moving to a fresh Arch install (x86_64) on a new computer. These key combinations, including the dwm one, worked fine on my old 32bit install on a Dell XPS m1330, so the configs should be right).
    Any ideas?
    Thanks in advance,
    halhen

    Thanks for the suggestion about customizing function keys, however, since the keys currently do nothing there's nothing to be re-mapped. (Such as VolumeUp => Page Up.)
    As far as I can tell, use of the Fn key actually blocks the arrow key press events on the Yoga, so not even Up, Down. Left, Right presses are received by the OS if/when the function key is pressed. (This be can verified in any basic text editing program such as Notepad. Additionally, I wrote a program to display any/all received key events and confirmed no event occurs in such cases.)
    The keyboard firmware or driver must be receiving the key state changes but simply ignores any arrow key event if the function key is pressed. I suspect any change to this behavior would have to come from the firmware or driver, which currently intercepts the hardware button presses before the OS may have a chance to redirect them. So I think the Lenovo hardware/software guys would have to enable this, which I figured it wouldn't hurt to ask.
    I like the use of the function key in conjunction with the arrows because that way I don't need to move my fingers off the arrow keys in order to move the text cursor to the beginning or end of a line. (I certainly still find the fixed Home and End keys on the keyboard necessary.)
    (Oh, and I apologize for inserting an image >50k, I didn't know the forum rules concerning a maximum image size.)

  • Some SONY DVD RW DW-U21A questions

    Hi, I have a G5 Dual 2Ghz with a SONY DVD RW DW-U21A drive in it. I have some questions I have not been able to get answers to. Hoping to get some help here
    1. Can it PLAY dual-layer data discs? My friend burned me a disc on his dual-layer drive. Can I safely insert that into this drive and access the files like any other disc?
    2. Can I use 16x media to burn DVDs? I know I'd only be able to burn at a maximum of 8x, but I have heard conflicting reports of whether you can use 16x media at ALL in the drive. With 8x media drying up in the stores, this is important. People have said, why not try it? I'd rather have a definitive answer and not A) mess up my drive or B) waste money on discs I can't use.
    3. I have a music CD that won't mount. The computer justs pits it out. there is nothing wrong with the CD. Plays fine everywhere else. I cleaned out the system cache and got it to mount ONCE in the G%, but now it is spitting it out again. Anyone heard of this issue?
    Thanks for the help!

    Same drive in this dual 2.5.
    1. Yes. Shouldn't have any problems.
    2. Yes. You won't mess up your drive.
    3. I have no idea. Has the disc been cursed with some sort of copy protection?

Maybe you are looking for