Raid 0 for dual SSD's in optical drv together with RAID 5 in internal bays
Hi,
I would like to add two 100GB SSD's in the second optical drive space in RAID 0 for boot.
This can be done with a special bracket and cables to the SATA connections on the motherboard. So far so good.
Now I have 4 drive bays I could fill with 4x2TB black caviars for data and I was wondering if I can have those ran via the a RAID 5...
Anybody have advice as to wether this is possible and if the Apple RAID card is the preferred option?
Thanks!!
Thomas
Hi Thomas,
welcome on board
I think first of all your SSDs should support RAID. Secondly, what I learned reading the forum entries that Apple RAID card is far not the best possible option.
Why you would not like to use soft raid?
Message was edited by: Munas
Similar Messages
-
HP ENVY 15: Slow 4K read speed for Dual SSD's in RAID 0 - Needs to be addressed!
Crystalmark scores 2nd gen Envy 15:
Read/Write
SEQ 352 / 215
512K 270 / 195
4K 14.2 / 110
http://forum.notebookreview.com/showthread.php?t=427278&page=754
read write
418.2 / 213.9 seq
251.3 / 181.1 random 512k
9.8 / 53.17 random 4k
http://forum.notebookreview.com/showthread.php?t=427278&page=750
4k Read Speed MUCH SLOWER than without Raid 0 (~20-25 mb/s)Not exactly sure, I pulled those benchmarks off of notebookreview. All I know from reading the forum is that HP Envy 15's in RAID 0 seem to be severely underperforming 4k read speeds relative to the same SSD's not in RAID 0. The 4k random read is the MOST IMPORTANT benchmark for real world performance.
Other posts in the old HP forum have cited that disabled C1E could possibly fix the 4k read issue, however the Envy 15 seems to have no way to access this option in the BIOS. -
Best practice for dual SSD RAID0 boot drive configuration
What is optimal stripe size for RAID0 OS/Boot Drives in OSX Software RAID?
You are talking about SSD too.
Usually the default or 16/32k would be fine for all those small frequent I/Os.
RAID though can affect SSD TRIM and it may depend on the SSDs. There are RAID optimized editions.
http://eshop.macsales.com/shop/internalstorage/Mercury_Extreme_SSDSandforce
http://macperformanceguide.com/SSD-RealWorld-SevereDuty.html -
Student licens for one program together with other licens
I have the "light version" of Adobe Suite through my work place (psd, indd, ai, bridge). Now I need AfterEffects wich is not covered in my work licens. How can I add a licens for After Effects without having to pay for all the programs I already have? I am also a student, can i have a student licens for a single program and use it together with my work licens?
Moving this discussion to the Adobe Creative Cloud forum.
Danielajuvall are you wishing to utilize your own membership to After Effects on the same computer you are utilizing a Creative Cloud for Team/Enterprise membership? -
Apple RAID card w/SSD in Optical Bay
If I've got this right, you cannot use the Apple RAID card in the new Mac Pro if you have even one SSD drive in any of the four HD bays. What I'm trying to determine is if you can use the Apple RAID card if the four HD bays all have 'normal' drives installed, but still want to use an SSD as a 5th drive, and locate it in the lower optical bay.
Hope the question makes sense, and I hope someone knows the answer!
Thanks.Hi rlhinc,
If you have not already purchased an Apple RAID card, and you only want to set up a RAID 0, as your post on another thread suggests, why not set up a software RAID 0 using Disk Utility:
http://macperformanceguide.com/Storage-HowToSetupRAID.html
With any RAID configuration the drives should all be identical, whether you are using 2, 3 or 4 drives.
I have 4 WD VelociRaptor 300GB drives in a striped (Scratch + Data) RAID 0 configuration in the 4 hard drive bays of my 2009 Nehalem Mac Pro, and set this up with Disk Utility.
The OS and my applications are on an SSD which is installed in the lower optical drive bay, and this set up works fine:
http://macperformanceguide.com/Mac-InstallingSSD.html
Regards,
Bill -
My initial goal with this project is to increase the performance of AE by lower render and editing time. My first thought with this project was to replace the standard HDD in my MacBook Pro with a faster drive. Faster drive=faster project completion.
Upon further investigation running through the forums a lot of people are running multipule drive machines a spectating there read and write drives to spectate ones to maximize the performance. I know some of the people who have thunderbolt ports are doing raid0 to accomplish this sadly I do not have thunder bolt.
What I would like to do is pull out the super drive and replace with a second HDD to accomplish this same type of idea. The HDD drive in the optical bay would be a traditional 7200rpm drive in the range from 750gb to 1TB to store the majority of the large files I have. The main drive I would change to a smaller SSD drive for my OS and apps.
All that being said I want the best return on my investment.
Would I see significant improvement in my work flow? Or is it just a waste of time/money?
If I did do that how would I set the settings in AE to take advantage of the dual drive correctly?
Here are the specs of my MacBook
2.8ghz core 2 duo
8GB ram (max)
500gb 5400rpm drive
OS Snow Leopard
Thanks for the help in advanceUnless you make excessive use of footage sources that require such massive file I/O, the advantage will be zero. Likewise, any advantages with using an SSD or RAID for disk cache will only show up, if the project is so complex, that using cached data will be faster than calculating stuff dynamically. AE has always worked this way and it still does, even if CS6 takes a much more aggressive approach to some of those things. It all comes down to what you do in your projects and it's the same like when to use MP rendering and when not or al lthose endless threads on the best computer for AE. There are no simple answers here. In the end, you could indeed spend a lot of money for nothing.
Mylenium -
Thinking of puting dual SSD drives in my MacBook Pro (by removing the optical drive). I'm thinking there are two configuration options...
I could STRIPE it for a super fast single volume, OR, I could put the OS on one drive, and the swap file and virtual machine (Boot Camp?) on the other drive.
Oh also thinking of a single SSD with a 1Tb drive in the optical bay.
Thoughts?Is there any reason you're not just going to get a 120GB SSD in the first place? [OWC has a 120GB SSD for under $300|http://eshop.macsales.com/shop/internalstorage/Mercury_Extreme_SSD_Sandforce/Solid_StatePro]. So unless you already bought the drives....
As to your actual question of whether OSX can boot from software RAID, I do not know specifically. I believe that it can, (correct me if I'm wrong) but I have never tried.
However, I would be quite concerned about booting from a RAID0 or simple spanned volume. You lose one disk, you lose all data. You'd want to be very certain about your backups. Yes, SSDs are more durable than platters, but Murphy doesn't care about such things. If it were me, I would NOT RAID the drive, but just use one for booting OSX, and the other for data. (But I'm probably more paranoid than most people. )
Me personally, I updated my 2008 MBP with a [Seagate 500GB hybrid drive|http://www.newegg.com/Product/Product.aspx?Item=N82E16822148591]. I needed the capacity for virtual machines but SSDs over 200GB are not at a good price point yet. So the hybrid is what I settled on. I'm finding that the platters don't spin up that much, which implies that the MBP is reading a lot from the 4GB cache on the drive, just like it would if it were a true SSD. So it's almost like having a SSD for most things until I fire up a virtual machine. YMMV, of course. -
Can I install a SSD on an optical drive in a HP Envy Phoenix
I just purchased a customized HP ENVY Phoenix Desktop - 810-350se CTO with a Raid 5 configuration (3 x 2 TB), but I noticed and researched that it seems that is better to have a SSD installed to have your computer access data faster, of course, I want to use it for the OS installed on it. So I have two questions?
1.) Can I change the configuration so I can add an SSD on a optical drive? (This will be the 4th drive). Since I am already using 3 HDD on a Raid 5 configuration and there wouldn't be any more space left, I am assuming that I can only use an empty optical drive space and install an SSD?
2.) Is there a limitation of how many drives and capacity HDD can be installed on the motherboard?
My proposed solution is to keep the 3 HDD and install a 4th drive (SSD) on the optical drive and use it for the OS (Windows 8.1).
Any suggestions and/or recommendations is highly appreciated it.
Thank you.
3rd Generation Intel(R) Core(TM) i7-4960X processor
•4TB 7200 RPM SATA 6G RAID Hard Drive
This question was solved.
View Solution.Hi,
Your PC is already using a Windows 8 boot loader and if you load the SSD in UEFI mode then you will add another Windows 8 boot loader to the eligible boot device menu. This will lead to confusion. I would suggest that you avoid this situation by trying the following procedure:
Be sure to create the external HP recovery media
Install the SSD on port 1 or 2
Disable secure boot in the BIOS and switch to legacy mode
Boot into the Intel OPROM and rebuild the RAID 5 array
Boot back into the BIOS and enable UEFI mode
Boot the external HP recover media and load the SSD (SSD recommended size is 240 GB or larger)
Once you are up and running then go into Disk Management and format the RAID array as GPT
The above procedure may or may not work but it's what I would first try.
HP DV9700, t9300, Nvidia 8600, 4GB, Crucial C300 128GB SSD
HP Photosmart Premium C309G, HP Photosmart 6520
HP Touchpad, HP Chromebook 11
Custom i7-4770k,Z-87, 8GB, Vertex 3 SSD, Samsung EVO SSD, Corsair HX650,GTX 760
Custom i7-4790k,Z-97, 16GB, Vertex 3 SSD, Plextor M.2 SSD, Samsung EVO SSD, Corsair HX650, GTX 660TI
Windows 7/8 UEFI/Legacy mode, MBR/GPT -
Adding ssd to mac pro with raid hdd
Hi,
In upgrading my 2008 mac pro (currently with hdds in raid) i'd like to add in an SSD with a clean install of yosemite and reformat the raid hdds for storage. What's the best method to accomplish this? I'll have to start over with the raid configuration i'm assuming because I need to give up a place for the SSD.
Thanks,
micabornMac Pro 2006, 2007 and 2008 models have two SATA data connectors on the motherboard, hidden in plain sight. They can be accessed by using a cable kit such as this one:
http://eshop.macsales.com/item/NewerTech/MPQXES2/
You can install the SSD in the second Optical bay. It has no moving parts, and does not run especially hot.
There are MUCH faster ways to run a High-end SSD, by installing it on a PCI slot adapter card, but you should try installing a 2.5" SSD drive as a first step. You may need to re-organize where you store things, like in this article:
User Tip: Creating a lean, fast Boot Drive -
RAID for speed....for use with home recording
Hi all, I want to get my G5 dual 2.0 faster for home recording with logic 8 using another hard drive. I was told RAID is the way to go? I am NOT familiar with RAID at all or how to do this but I am very good at picking this stuff up. Unfortunately this G5 only has 4 slots for RAM so I can only max out at 4GB. Can anyone tell me how to make this machine fastest I can make it? Thank you. BTW I have 160GB hard drive now running Leopard, which is the highest I can go.
Xserve RAID is a Fibre Channel Storage Area Network (FC SAN) storage hardware product, and it has been discontinued. The replacement product is the Promise SAN storage controller series, and that is probably out of your price range.
As for RAID...
RAID-0 is also known as striping. Clumps of data are written to each disk, so you end up with the aggregate speed of two disks. But if one disk fails, you're rolling in your backups.
RAID-1 is also known as mirroring or shadowing, and you can survive the loss of one disk. Read performance is decent, write performance is slower as you have to write to both disks.
RAID-5 is a format best avoided; it's an old scheme from when disks were dinky and expensive. This format engenders massive I/O recovery loads on failures (approximately 80% of your total I/O bandwidth into the array is consumed for hours, and potentially as long as overnight for a bigger array), and the load increases as disk capacity increases, and (surprisingly) prone to blowing a second disk during recovery due to the I/O load, and leaving you with a catastrophic array failure. The bigger your disks (or the more unstable your disks), the more likely a second error will arise during recovery, meaning that RAID-5 is a format best avoided. It's comparatively slow. The Apple hardware RAID-5 controller performance isn't comparable with mid- or upper-end SAN-based controller RAID performance, in my experience with both. (Various of those SAN controllers have fully virtualized storage, so the whole concept of RAID is, well, rather different.)
RAID-6 (various names) is a variant of RAID-5, with additional replicated data. If you want RAID-5, then RAID-6 is usually a better choice as it's less prone to blowing a disk during recovery.
RAID-10 is a combination of RAID-0 and RAID-1, where you have striping across a mirror. It's a decent-performing RAID controller, and it doesn't have the massive recovery load.
RAID-50 is a combination of RAID-0 and RAID-5.
http://en.wikipedia.org/wiki/RAID
RAID is not an archival strategy. If your data is important, you need a copy not on your RAID array.
Best bang for your money is probably a used Intel-based server of some ilk; the QPI-based Xeon boxes are screaming-fast boxes. A box swap for whatever G5 box this is. Spending a whole lot on a G5-class box isn't going to be particularly effective.
Best "cheap" bang for your money is probably a SSD; your existing capacity is in the same range as the entry-level SSD drives. A disk upgrade. Below that, you're left with either an internal upgrade, or (depending on which G5 box you have) a PCI-X-based, or a FireWire-based or USB-based external storage, in decreasing relative order of performance.
As for home recording, if you're running a G5-class box, then pretty much anything out there will work; performance will probably be adequate. Once you figure out what your I/O load and your CPU load might be, you'll probably either be happy with a minimal (disk) upgrade, or you'll be looking for a new box. You'll inevitably be looking at a box upgrade over time as the PPC gear falls off the supported list for the products you're using, however. -
If you have an interest in using RAID, then the MS Word document attached to this post may be useful information. Scroll all the way to the bottom for the attachment.
RAID for Consumer PCs
Table of Contents
RAID
RAID 0
RAID 1
RAID 5
RAID 10 (0+1)
INTEL Controller Support for Different RAID Configurations
Background Information for Creating a RAID configuration.
Considerations:
Performance comparisons
Creating a RAID 0 Array
Creating a RAID 1 Array
Creating a RAID 5 Array
Creating a RAID 10 (0+1) Array
Conversion from RAID 0 to RAID 5
RAID 0 to RAID 5 Observations
Other RAID Migrations
*************DISCLAIMER***********
RAID
RAID is an acronym for Redundant Array of Inexpensive Disks and also commonly called Redundant Array of Independent Disks. A RAID array is created when one or more hard disks or one or more solid state disks (SSD) are combined to form a logical volume using one of several different configurations. Consumer level PCs typically use RAID 0, RAID 1, RAID 5 and occasionally RAID 10 (0+1). The RAID configuration choice is dependent on the requirements for redundancy, speed and capacity. The choice of a RAID configuration will be a compromise between speed, redundancy, capacity and cost. The different RAID configuration options can be restricted by hardware limitations.
RAID 0
A RAID 0 volume is created when 2 hard disks are used and then data is spanned or striped across the different hard disks. The process of spanning data across different hard disks is also called scatter loading. By spreading data across multiple hard disks, a significant performance improvement can be gained. However, should one of the hard disks fail, then the entire RAID 0 configuration becomes unusable. A RAID 0 volume combines the capacity of the hard drives being used in the configuration.
RAID 1
A RAID 1 configuration is created when 2 hard disks are used and then data on hard drive 1 is replicated to hard drive 2. The process is also called data mirroring. This configuration provides for redundancy in the event of a single hard drive failure but at the expensive of a degradation to write performance as data has to be written to multiple hard drives. Since the data is being replicated between two volumes the overall capacity is limited to that of one hard drive.
RAID 5
A RAID 5 configuration is similar to a RAID 0 array except RAID 5 deploys distributed parity also referred to as checksum data. Blocks of data are stripped across three or more hard drives and each hard drive contains block level recreation data (parity). In the event of a hard drive failure, parity will allow for the data to be accessed through a dynamic data creation process. The downside to the dynamic data creation process is a reduction in performance until the failing hard drive can be replaced. RAID 5 performs best for supporting read accesses as write operations will be slower while the parity blocks are being updated. Parity data does consume disk space. A three hard drive RAID 5 array will have about the same total data capacity as a two hard drive RAID 0 array.
RAID 10 (0+1)
A RAID 10 configuration also called RAID 0+1 can be implemented in two different methods depending on the hardware being used. The below left configuration is a striped RAID 1 array being replicated and the below right configuration is a RAID 0 array being replicated. A RAID 10 configuration can provide a RAID 0 performance level even with the loss of one hard disk. The downside to RAID 10 is the reduced configuration capacity.
INTEL Controller Support for Different RAID Configurations.
The RAID configurations used in this document are based on the INTEL SATA controller.
See the below table.
NOTE: Even though your system board may have the appropriate Intel controller,
not all system boards will provide RAID functionality.
Background Information for Creating a RAID configuration.
You can create a RAID configuration provided that:
The PC cabinet can accommodate additional hard drive(s) if needed.
The system board has the necessary open SATA port(s) if needed.
A SATA controller that can support the desired RAID configuration.
You can determine the status of your RAID configuration by using the Intel Rapid Storage Technology (IRST) software. If you don’t have this software on your PC then you can download IRST from the Intel web site. I recommend that you use the latest version available from Intel. Background information can be obtained from the IRST User Guide. When you launch IRST, the help topics are an excellent source of information. You can access IRST by going into the Control Panel and select Intel Rapid Storage Technology. You can also access IRST from the lower right Task Bar location. IRST should resemble a hard drive icon and normally it has a green check mark. By default IRST is set as delayed startup so don’t expect to see it active right after boot up. The Intel images being used in this document are from IRST version 11.1.0.1006.
If the SATA controller in your PC is not set to RAID then read this Microsoft article if you are running VISTA or Windows 7. You need to run the MrFixIT script before you reboot your PC in the bios and make the SATA controller mode change to RAID. The script will then allow Windows to choose the correct driver when you reboot your PC. If you plan on using a boot drive image restore then be sure to run the script just prior to making taking your image backup. That way your backup image is set to allow Windows to choose the correct SATA driver.
Before creating any RAID configuration, always make backups of your data and image the boot hard disk to external media such as an USB drive. Additionally, be sure that your imaging product boot disk is functional, particularly if the PC’s boot hard disk is part of the RAID configuration. Its best to use a commercial hard disk imaging product as support and functionality is generally better than the “freebie” software.
Be sure that your PC is running the latest available BIOS. BIOS updates are used to update the Intel ROM firmware. Additionally, check for hard drive and SSD firmware updates.
Summary of preparation steps in priority order:
Backup your data.
Test out your recovery and restore procedures.
Update the following: BIOS, hard drive firmware, SSD firmware
Update IRST
Execute the Microsoft MrFixIt if your PC is not set to RAID mode in the bios.
Create an image of your boot hard drive.
Considerations:
After replacing a failed hard drive, don’t expect the rebuild process to be fast. All of the data that existed on the failed hard drive must be either regenerated using parity data or replicated to the new hard drive.
I recommend that you use an uninterruptable power supply (UPS) when using RAID 5. Cached write data needs to be written to hard drive in the event of a power failure to avoid the loss of data. You might want to consider disabling write back cache if you are not using an UPS. There is a performance reduction by doing so at the expense of improving data integrity.
If you need a RAID array over 2 TB then your PC needs: UEFI bios, 64 bit operating system, GPT formated hard drives. Review this Microsoft article on Windows and GPT FAQs.
Since a MBR formated array will limit the useable space to 2 TB it’s therefore best to use hard drives that are 1 TB or less for RAID 0, 5 and 10.
Consider the data growth rate and the size of the array. The Intel controller will limit the number of hard drives. The size of the PC cabinet and available system board SATA ports will also be growth constraints. It’s not uncommon for a business to experience an annual data growth rate of 20 percent.
If you need a RAID solution beyond the typical consumer level RAID configurations, then you should review the RAID options available from HP.
RAID technology in not infalible so you need to consider backups. A voltage spike inside your PC could render the RAID unusable and unrecoverable. Corrupted data or a virus are other reasons for keeping backups. An external USB connected hard drive might be sufficient for backups.
Throughly test your backup and restore software. Always keep more than one backup copy of your data.
Performance comparisons:
All of the hard drives benchmarked are Hitachi 1.5 TB SATA III hard drives connected as SATA II devices. HD Tune was used to benchmark the seniaros using default settings.
Configuration
Average MB/s
Maximum MB/s
Single hard drive
113
152
RAID 0
222
289
RAID 1
104
142
RAID 5
221
288
RAID 10 (0+1)
220
274
Creating a RAID 0 Array.
If you are configuring the Windows boot drive into a RAID 0 array, then you need to use the Intel option ROM method for creating the array. Tapping Cntl-i at boot up will get you into the Intel option ROM firmware setup utility. Once the array has been created then boot up your image recovery disk and load the array from your image backup.
If you are creating a RAID 0 data only array then you can use the IRST when running Windows to create the array. You can also use the Intel option ROM firmware setup utility. Even though this HP VISTA RAID setup article is dated, it does have some excellent information.
Launch IRST.
You can observe in the above image the status of the hard drives attached to the Intel SATA controller. Now click on Create. Select Optimized Disk (RAID 0) then click on Next.
Configure the RAID 0 array by selecting two hard drives of the same size and click on Next.
Next click on Create Volume.
A warning window will appear. Click on OK.
The new RAID volume is now created. However, you now need to use Windows Disk Management to ready the volume for use.
Creating a RAID 1 Array.
If you are configuring the Windows boot drive into a RAID 1 array, then you need to use the Intel option ROM method for creating the array. Tapping Cntl-i at boot up will get you into the Intel option ROM firmware setup utility. Once the array has been created then boot up your image recovery disk and load the array from your image backup.
If you are creating a RAID 1 data only array then you can use the IRST when running Windows to create the array. You can also use the Intel option ROM firmware setup utility. Even though this HP VISTA RAID setup article is dated, it does have some excellent information.
Launch IRST.
You can observe the above status of the hard drives attached to the Intel SATA controller. Now click on Create.
Select Real-time data protection (RAID 1) and click NEXT.
Configure the RAID 1 array by selecting two hard drives of the same size and click on Next.
Next click on Create Volume.
The new RAID volume is now created. However, you now need to use Windows Disk Management to ready the volume for use.
Creating a RAID 5 Array.
A RAID 5 array will require three to four hard drives. While it is possible to convert a RAID 0 to a RAID 5 array, I recommended that you consider building the RAID 5 array from scratch rather than use a conversion method.
If you are configuring the Windows boot drive into the RAID 5 array, then you need to use the Intel option ROM method for creating the array. Tapping Cntl-i at boot up will get you into the Intel option ROM firmware setup utility. Once the array has been created then boot up your image recovery disk and load the array from your image backup.
If you are creating a RAID 5 data only array then you can use the IRST when running Windows to create the array. You can also use the Intel option ROM firmware setup utility. Even though this HP VISTA RAID setup article is dated, it does have some excellent information.
The following procedure will build the RAID 5 array with three hard drives using IRST.
Launch IRST.
During this create process, I will be using the last three hard drives
listed in the above image under Storage System View. Now click Create.
Select Efficient data hosting and protection (RAID 5) and click
On Next.
Select the three hard drives for RAID 5 and click on Next.
Review the volume creation selections then click on Create Volume.
Review the final warning then click on OK.
Now click on OK and review the final array status.
Creating a RAID 10 (0+1) Array.
A RAID 10 (0+1) array will require four hard drives.
If you are configuring the Windows boot drive into the RAID 10 (0+1) array, then you need to use the Intel option ROM method for creating the array. Tapping Cntl-i at boot up will get you into the Intel option ROM firmware setup utility. Once the array has been created then boot up your image recovery disk and load the array from your image backup.
If you are creating a RAID 10 (0+1) data only array then you can use the IRST when running Windows to create the array. You can also use the Intel option ROM firmware setup utility. Even though this HP VISTA RAID setup article is dated, it does have some excellent information.
The following procedure will build the RAID 10 (0+1) array using four hard drives using IRST.
Launch IRST.
This create process will be using the last four hard drives listed in the above image under Storage System View. Notice that the hard drives are not the same size. Two of the hard drives are 1.5 TB and two hard drives are 2 TB. While it’s recommended to use all hard drives of the same size, it’s not required. The RAID 10 creation progam will pick to two smallest hard drives for the striped pair and then the two largest hard drives for replication pair but not the opposite as the two largest hard drives if used as the striped pair would not fit on the two smaller hard drives for replication. Now click Create.
Select Balanced performance and data protection (RAID 10) and click
on Next.
Select the four hard drives for RAID 10 and click on Next.
Notice that IRST is set to create a RAID 10 volume with the capacity of 2.7 TB.
Review the volume creation selections then click on Create Volume.
Review the final warning then click on OK.
Now click on OK and review the final array status.
Conversion from RAID 0 to RAID 5
If you have a RAID 0 hard disk configuration and you are concerned that a hard drive failure will cause your PC to crash or results in data loss then you might have an option to use RAID 5. A RAID 5 three drive configuration can survive a single hard drive failure but not two failing hard drives. While there are other RAID configurations possible, this document will only be addressing a three hard drive configuration using the Intel SATA controller. Some of the newer HP PCs can accommodate three hard drives and can be configured when ordered with RAID 5.
Observe the below image. This PC has a RAID 0 2.7 TB array. To build the RAID 5 array, you will need to add (configure) an additional hard drive into the array. Click on Manage and then add an eligible hard drive to the array.
Note: all data on the hard drive to be added to the array will be lost since parity and data from the existing array needs to be written to the added hard drive to create the RAID 5 array. Take backups of your existing array in case something goes wrong.
Once you are on the Manage screen then click on Change type.
The following screen will appear:
Select the drive to be included into the array and click on OK.
When the migration process begins, the Status is now indicating migrating and the Type is RAID 5. The hard drive added was 2 TB which meets the minimum amount. BE PATIENT! The migration process will take a very long time for an in place migration to complete.
It’s much faster to delete out the original RAID 0 volume, create the new RAID 5 volume and then reload the original RAID 0 image from your backups. I recommend that you consider
this method verses the in place approach.
Click on Status to show the migration progress.
RAID 0 to RAID 5 Observations
I was able to shut down and boot the RAID configuration before the migration process had completed. The in place migration method was very slow, about 3% per hour and hence my recommendation to use a differnet method. Booting up from different hard drive before the migration process has completed results in a BSOD on boot up.
After completing the RAID 5 conversion, I did receive a message from IRST indicating that one or more volumes is protected against a hard drive failure.
Other RAID Migrations
While there are other RAID migrations options available, they can be platform (chipset) specific. Review this Intel Chipset article on supported RAID migrations. Even though the Intel RAID migration has a safety function built into the process in the event of a power loss or shutdown, it’s always best to have a complete set of up-to-date backups.
The migration process can be painfully slow. The migration time is largely dependent on the hard drive sizes and the number of hard drives involved in the overall migration. In some cases it might be faster to build the RAID array from scratch and then load the data back to the array verses using an in place migration process.
It is possible to increase the overall RAID array (volume) size with some RAID configurations by adding hard drives to the array. The overall size of the array may be limited by how the array had been previously formatted by Windows. Review the information under the Considerations topic in this document.
*********updated August 21, 2013
If you are using SSDs in a RAID 0 configuration then you will need to have the Intel 7 or 8 chipset plus Intel Rapid Storage Technology (IRST) version 11 or higher to get Windows TRIM support to function. The latest version of IRST as of 8/21/2013 that I have seen is 12.7.1036.
*************DISCLAIMER***********
There may be inaccuracies with the information contained in this document so please consider that when using RAID.
*************DISCLAIMER***********
HP DV9700, t9300, Nvidia 8600, 4GB, Crucial C300 128GB SSD
HP Photosmart Premium C309G, HP Photosmart 6520
HP Touchpad, HP Chromebook 11
Custom i7-4770k,Z-87, 8GB, Vertex 3 SSD, Samsung EVO SSD, Corsair HX650,GTX 760
Custom i7-4790k,Z-97, 16GB, Vertex 3 SSD, Plextor M.2 SSD, Samsung EVO SSD, Corsair HX650, GTX 660TI
Windows 7/8 UEFI/Legacy mode, MBR/GPT
Attachments:
RAID for Consumer PCs.doc 3761 KBGreat document
I am a volunteer. I am not an HP employee.
To say THANK YOU, press the "thumbs up symbol" to render a KUDO. Please click Accept as Solution, if your problem is solved. You can render both Solution and KUDO.
The Law of Effect states that positive reinforcement increases the probability of a behavior being repeated. (B.F.Skinner). You toss me KUDO and/or Solution, and I perform better.
(2) HP DV7t i7 3160QM 2.3Ghz 8GB
HP m9200t E8400,Win7 Pro 32 bit. 4GB RAM, ASUS 550Ti 2GB, Rosewill 630W. 1T HD SATA 3Gb/s
Custom Asus P8P67, I7-2600k, 16GB RAM, WIN7 Pro 64bit, EVGA GTX660 2GB, 750W OCZ, 1T HD SATA 6Gb/s
Custom Asus P8Z77, I7-3770k, 16GB RAM, WIN7 Pro 64bit, EVGA GTX670 2GB, 750W OCZ, 1T HD SATA 6Gb/s
Both Customs use Rosewill Blackhawk case.
Printer -- HP OfficeJet Pro 8600 Plus -
Hyper Disk Layout and Raid For Essintal Server 2012 R2 With Exchange
Hi would raid mirror be good enough support configuration on single server run both essentials server 2012 and exchange 2013 new to exchange look for input and suggestions
user load is very light just 5
boot disk 120 gig ssd on it own Controller run 2012 run with hyper v installed
2 x 3 Tb raid 1 by Lsi 1064e raid control essentials server 2012 disk are vhdx fixed size two each
2 x 2 Tb raid 1 by Lsi 1064e raid control 2012 R2 server disk are vhdx fixed size two each
System specs is 2 x Amd opertron 4122 with 32 gig of Ram 4 core to each os
Andy AHi would raid mirror be good enough support configuration on single server run both essentials server 2012 and exchange 2013 new to exchange look for input and suggestions
user load is very light just 5
boot disk 120 gig ssd on it own Controller run 2012 run with hyper v installed
2 x 3 Tb raid 1 by Lsi 1064e raid control essentials server 2012 disk are vhdx fixed size two each
2 x 2 Tb raid 1 by Lsi 1064e raid control 2012 R2 server disk are vhdx fixed size two each
System specs is 2 x Amd opertron 4122 with 32 gig of Ram 4 core to each os
1) Boot Hyper-V from cheap SATA or even USB stick (see link below). No point in wasting SSD for that. Completely agree with Eric. See:
Run Hyper-V from USB Flash
http://technet.microsoft.com/en-us/library/jj733589.aspx
2) Don't use RAID controllers in RAID mode rather (as you already got them) stick with HBA mode passing disks AS IS, add some more SSDs and configure Storage Spaces in RAID10 equivalent mode and use SSDs as a flash cache. See:
Storage Spaces Overview
http://technet.microsoft.com/en-us/library/hh831739.aspx
Because having single pool touching all spindles would provide you better IOPS compared to creating "islands of storage" that are waste or performance and hell of management.
3) Come up with IOPS requirements for your workload (no idea from above) keeping in mind RAID10 provides ALL IOPS for reads and half IOPS for writes (because of mirroring). So as single SATA can do maybe 120-150 IOPS and single SAS can do up to 200 (you
don't provide any model names so we have to guess) you may calculate how many IOPS your config would give away in a best and worst case scenario (write back cache from above will help but you always need to come from a WORST case). See calculator link below.
IOPS Calculator
http://www.wmarow.com/strcalc/
Hope this helped a bit :)
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts. -
Cannot configure X for dual monitor
Hello, I just reinstalled my Arch and I'm trying to configure X with a dual monitor setup using nouveau driver.
This is what I get after login:
This is what I get after using xrandr to setup:
xrandr --output HDMI-1 --left-of VGA-1
This is the content of /etc/X11/xorg.conf.d/20-nouveau.conf
Section "Monitor"
Identifier "Asus"
Option "LeftOf" "Dell"
Option "Primary" "False"
EndSection
Section "Monitor"
Identifier "Dell"
Option "Primary" "false"
EndSection
Section "Device"
Identifier "Card"
Driver "nouveau"
Option "monitor-VGA-1" "Dell"
Option "monitor-HDMI-1" "Asus"
EndSection
Section "Screen"
Identifier "Screen"
Device "Card"
Monitor "Dell"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1920x1080" "1680x1050"
Virtual 3600 1080
EndSubSection
EndSection
Section "ServerLayout"
Identifier "Default Layout"
Screen "Screen"
EndSection
This is the content of the X log from start till xrandr command
[ 10.963]
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
[ 10.963]
X.Org X Server 1.12.3.901 (1.12.4 RC 1)
Release Date: 2012-08-03
[ 10.963] X Protocol Version 11, Revision 0
[ 10.963] Build Operating System: Linux 3.4.4-2-ARCH x86_64
[ 10.963] Current Operating System: Linux markus 3.4.8-1-ARCH #1 SMP PREEMPT Thu Aug 9 21:21:22 CEST 2012 x86_64
[ 10.963] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=1019adcf-1c5a-4321-b685-a0b1ee8185d8 ro quiet
[ 10.963] Build Date: 09 August 2012 10:04:44AM
[ 10.963]
[ 10.963] Current version of pixman: 0.26.2
[ 10.963] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 10.963] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 10.963] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Aug 16 17:44:51 2012
[ 11.022] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 11.066] (==) ServerLayout "Default Layout"
[ 11.066] (**) |-->Screen "Screen" (0)
[ 11.066] (**) | |-->Monitor "Dell"
[ 11.067] (**) | |-->Device "Card"
[ 11.067] (==) Automatically adding devices
[ 11.067] (==) Automatically enabling devices
[ 11.141] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 11.141] Entry deleted from font path.
[ 11.141] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 11.141] Entry deleted from font path.
[ 11.141] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 11.141] Entry deleted from font path.
[ 11.141] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 11.141] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 11.141] Entry deleted from font path.
[ 11.141] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 11.141] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/
[ 11.141] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 11.141] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 11.141] (II) Loader magic: 0x7c8b00
[ 11.141] (II) Module ABI versions:
[ 11.141] X.Org ANSI C Emulation: 0.4
[ 11.141] X.Org Video Driver: 12.1
[ 11.141] X.Org XInput driver : 16.0
[ 11.141] X.Org Server Extension : 6.0
[ 11.143] (--) PCI:*(0:2:0:0) 10de:0848:1043:82e2 rev 162, Mem @ 0xfb000000/16777216, 0xf0000000/134217728, 0xf8000000/33554432, I/O @ 0x0000ec00/128, BIOS @ 0x????????/131072
[ 11.143] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 11.143] (II) LoadModule: "extmod"
[ 11.144] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 11.179] (II) Module extmod: vendor="X.Org Foundation"
[ 11.179] compiled for 1.12.3.901, module version = 1.0.0
[ 11.179] Module class: X.Org Server Extension
[ 11.179] ABI class: X.Org Server Extension, version 6.0
[ 11.179] (II) Loading extension MIT-SCREEN-SAVER
[ 11.179] (II) Loading extension XFree86-VidModeExtension
[ 11.179] (II) Loading extension XFree86-DGA
[ 11.179] (II) Loading extension DPMS
[ 11.179] (II) Loading extension XVideo
[ 11.179] (II) Loading extension XVideo-MotionCompensation
[ 11.179] (II) Loading extension X-Resource
[ 11.179] (II) LoadModule: "dbe"
[ 11.179] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 11.183] (II) Module dbe: vendor="X.Org Foundation"
[ 11.183] compiled for 1.12.3.901, module version = 1.0.0
[ 11.183] Module class: X.Org Server Extension
[ 11.183] ABI class: X.Org Server Extension, version 6.0
[ 11.183] (II) Loading extension DOUBLE-BUFFER
[ 11.183] (II) LoadModule: "glx"
[ 11.183] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 11.209] (II) Module glx: vendor="X.Org Foundation"
[ 11.209] compiled for 1.12.3.901, module version = 1.0.0
[ 11.209] ABI class: X.Org Server Extension, version 6.0
[ 11.209] (==) AIGLX enabled
[ 11.209] (II) Loading extension GLX
[ 11.209] (II) LoadModule: "record"
[ 11.210] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 11.217] (II) Module record: vendor="X.Org Foundation"
[ 11.217] compiled for 1.12.3.901, module version = 1.13.0
[ 11.217] Module class: X.Org Server Extension
[ 11.217] ABI class: X.Org Server Extension, version 6.0
[ 11.217] (II) Loading extension RECORD
[ 11.217] (II) LoadModule: "dri"
[ 11.217] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 11.236] (II) Module dri: vendor="X.Org Foundation"
[ 11.236] compiled for 1.12.3.901, module version = 1.0.0
[ 11.236] ABI class: X.Org Server Extension, version 6.0
[ 11.236] (II) Loading extension XFree86-DRI
[ 11.236] (II) LoadModule: "dri2"
[ 11.236] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 11.245] (II) Module dri2: vendor="X.Org Foundation"
[ 11.245] compiled for 1.12.3.901, module version = 1.2.0
[ 11.245] ABI class: X.Org Server Extension, version 6.0
[ 11.245] (II) Loading extension DRI2
[ 11.245] (II) LoadModule: "nouveau"
[ 11.255] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[ 11.282] (II) Module nouveau: vendor="X.Org Foundation"
[ 11.282] compiled for 1.12.2, module version = 1.0.1
[ 11.282] Module class: X.Org Video Driver
[ 11.282] ABI class: X.Org Video Driver, version 12.0
[ 11.282] (II) NOUVEAU driver
[ 11.282] (II) NOUVEAU driver for NVIDIA chipset families :
[ 11.282] RIVA TNT (NV04)
[ 11.282] RIVA TNT2 (NV05)
[ 11.282] GeForce 256 (NV10)
[ 11.282] GeForce 2 (NV11, NV15)
[ 11.282] GeForce 4MX (NV17, NV18)
[ 11.282] GeForce 3 (NV20)
[ 11.282] GeForce 4Ti (NV25, NV28)
[ 11.282] GeForce FX (NV3x)
[ 11.282] GeForce 6 (NV4x)
[ 11.282] GeForce 7 (G7x)
[ 11.282] GeForce 8 (G8x)
[ 11.283] GeForce GTX 200 (NVA0)
[ 11.283] GeForce GTX 400 (NVC0)
[ 11.283] (++) using VT number 7
[ 11.286] drmOpenDevice: node name is /dev/dri/card0
[ 11.286] drmOpenDevice: open result is 8, (OK)
[ 11.286] drmOpenByBusid: Searching for BusID pci:0000:02:00.0
[ 11.286] drmOpenDevice: node name is /dev/dri/card0
[ 11.286] drmOpenDevice: open result is 8, (OK)
[ 11.286] drmOpenByBusid: drmOpenMinor returns 8
[ 11.286] drmOpenByBusid: drmGetBusid reports pci:0000:02:00.0
[ 11.286] (II) [drm] nouveau interface version: 1.0.0
[ 11.287] (II) Loading sub module "dri"
[ 11.287] (II) LoadModule: "dri"
[ 11.287] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 11.287] (II) Module dri: vendor="X.Org Foundation"
[ 11.287] compiled for 1.12.3.901, module version = 1.0.0
[ 11.287] ABI class: X.Org Server Extension, version 6.0
[ 11.287] (II) NOUVEAU(0): Loaded DRI module
[ 11.287] drmOpenDevice: node name is /dev/dri/card0
[ 11.287] drmOpenDevice: open result is 9, (OK)
[ 11.287] drmOpenDevice: node name is /dev/dri/card0
[ 11.287] drmOpenDevice: open result is 9, (OK)
[ 11.287] drmOpenByBusid: Searching for BusID pci:0000:02:00.0
[ 11.287] drmOpenDevice: node name is /dev/dri/card0
[ 11.287] drmOpenDevice: open result is 9, (OK)
[ 11.287] drmOpenByBusid: drmOpenMinor returns 9
[ 11.287] drmOpenByBusid: drmGetBusid reports pci:0000:02:00.0
[ 11.287] (II) [drm] DRM interface version 1.4
[ 11.287] (II) [drm] DRM open master succeeded.
[ 11.287] (--) NOUVEAU(0): Chipset: "NVIDIA NVaa"
[ 11.287] (**) NOUVEAU(0): Depth 24, (--) framebuffer bpp 32
[ 11.287] (==) NOUVEAU(0): RGB weight 888
[ 11.287] (==) NOUVEAU(0): Default visual is TrueColor
[ 11.287] (==) NOUVEAU(0): Using HW cursor
[ 11.287] (==) NOUVEAU(0): GLX sync to VBlank disabled.
[ 11.287] (==) NOUVEAU(0): Page flipping enabled
[ 11.288] (==) NOUVEAU(0): Swap limit set to 2 [Max allowed 2]
[ 11.327] (II) NOUVEAU(0): Output VGA-1 using monitor section Dell
[ 11.327] (**) NOUVEAU(0): Option "Primary" "false"
[ 11.381] (II) NOUVEAU(0): Output HDMI-1 using monitor section Asus
[ 11.381] (**) NOUVEAU(0): Option "LeftOf" "Dell"
[ 11.381] (**) NOUVEAU(0): Option "Primary" "False"
[ 11.410] (II) NOUVEAU(0): EDID for output VGA-1
[ 11.410] (II) NOUVEAU(0): Manufacturer: DEL Model: 4066 Serial#: 825569612
[ 11.410] (II) NOUVEAU(0): Year: 2011 Week: 35
[ 11.410] (II) NOUVEAU(0): EDID Version: 1.3
[ 11.410] (II) NOUVEAU(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V
[ 11.410] (II) NOUVEAU(0): Sync: Separate Composite SyncOnGreen
[ 11.410] (II) NOUVEAU(0): Max Image Size [cm]: horiz.: 51 vert.: 29
[ 11.410] (II) NOUVEAU(0): Gamma: 2.20
[ 11.410] (II) NOUVEAU(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
[ 11.410] (II) NOUVEAU(0): First detailed timing is preferred mode
[ 11.410] (II) NOUVEAU(0): redX: 0.633 redY: 0.340 greenX: 0.319 greenY: 0.621
[ 11.410] (II) NOUVEAU(0): blueX: 0.154 blueY: 0.042 whiteX: 0.313 whiteY: 0.328
[ 11.410] (II) NOUVEAU(0): Supported established timings:
[ 11.410] (II) NOUVEAU(0): 720x400@70Hz
[ 11.410] (II) NOUVEAU(0): 640x480@60Hz
[ 11.410] (II) NOUVEAU(0): 640x480@75Hz
[ 11.410] (II) NOUVEAU(0): 800x600@60Hz
[ 11.410] (II) NOUVEAU(0): 800x600@75Hz
[ 11.410] (II) NOUVEAU(0): 1024x768@60Hz
[ 11.410] (II) NOUVEAU(0): 1024x768@75Hz
[ 11.410] (II) NOUVEAU(0): 1280x1024@75Hz
[ 11.410] (II) NOUVEAU(0): Manufacturer's mask: 0
[ 11.410] (II) NOUVEAU(0): Supported standard timings:
[ 11.410] (II) NOUVEAU(0): #0: hsize: 1152 vsize 864 refresh: 75 vid: 20337
[ 11.410] (II) NOUVEAU(0): #1: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
[ 11.410] (II) NOUVEAU(0): #2: hsize: 1920 vsize 1080 refresh: 60 vid: 49361
[ 11.410] (II) NOUVEAU(0): Supported detailed timing:
[ 11.410] (II) NOUVEAU(0): clock: 148.5 MHz Image Size: 509 x 286 mm
[ 11.410] (II) NOUVEAU(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
[ 11.410] (II) NOUVEAU(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
[ 11.410] (II) NOUVEAU(0): Serial No: WPDV118P151L
[ 11.410] (II) NOUVEAU(0): Monitor name: DELL P2311H
[ 11.410] (II) NOUVEAU(0): Ranges: V min: 56 V max: 76 Hz, H min: 30 H max: 83 kHz, PixClock max 175 MHz
[ 11.410] (II) NOUVEAU(0): EDID (in hex):
[ 11.410] (II) NOUVEAU(0): 00ffffffffffff0010ac66404c313531
[ 11.410] (II) NOUVEAU(0): 231501030e331d78ea0cb4a257519f27
[ 11.410] (II) NOUVEAU(0): 0a5054a54b00714f8180d1c001010101
[ 11.410] (II) NOUVEAU(0): 010101010101023a801871382d40582c
[ 11.410] (II) NOUVEAU(0): 4500fd1e1100001e000000ff00575044
[ 11.410] (II) NOUVEAU(0): 56313138503135314c0a000000fc0044
[ 11.410] (II) NOUVEAU(0): 454c4c205032333131480a20000000fd
[ 11.410] (II) NOUVEAU(0): 00384c1e5311000a2020202020200054
[ 11.410] (II) NOUVEAU(0): EDID vendor "DEL", prod id 16486
[ 11.426] (II) NOUVEAU(0): Using EDID range info for horizontal sync
[ 11.426] (II) NOUVEAU(0): Using EDID range info for vertical refresh
[ 11.426] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 11.426] (II) NOUVEAU(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
[ 11.426] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 11.426] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 11.426] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 11.426] (II) NOUVEAU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 11.426] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 11.426] (II) NOUVEAU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 11.426] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 11.427] (II) NOUVEAU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 11.427] (II) NOUVEAU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 11.427] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 11.427] (II) NOUVEAU(0): Modeline "1920x1080"x60.0 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -hsync +vsync (67.1 kHz e)
[ 11.427] (II) NOUVEAU(0): Printing probed modes for output VGA-1
[ 11.427] (II) NOUVEAU(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz UeP)
[ 11.427] (II) NOUVEAU(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 11.427] (II) NOUVEAU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 11.427] (II) NOUVEAU(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 11.427] (II) NOUVEAU(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
[ 11.427] (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 11.427] (II) NOUVEAU(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 11.427] (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 11.427] (II) NOUVEAU(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 11.427] (II) NOUVEAU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 11.427] (II) NOUVEAU(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 11.481] (II) NOUVEAU(0): EDID for output HDMI-1
[ 11.481] (II) NOUVEAU(0): Manufacturer: ACI Model: 22f1 Serial#: 16843009
[ 11.481] (II) NOUVEAU(0): Year: 2008 Week: 31
[ 11.481] (II) NOUVEAU(0): EDID Version: 1.3
[ 11.481] (II) NOUVEAU(0): Digital Display Input
[ 11.481] (II) NOUVEAU(0): Max Image Size [cm]: horiz.: 47 vert.: 30
[ 11.481] (II) NOUVEAU(0): Gamma: 2.20
[ 11.481] (II) NOUVEAU(0): DPMS capabilities: Off
[ 11.481] (II) NOUVEAU(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[ 11.481] (II) NOUVEAU(0): Default color space is primary color space
[ 11.481] (II) NOUVEAU(0): First detailed timing is preferred mode
[ 11.481] (II) NOUVEAU(0): redX: 0.649 redY: 0.335 greenX: 0.283 greenY: 0.605
[ 11.481] (II) NOUVEAU(0): blueX: 0.151 blueY: 0.073 whiteX: 0.313 whiteY: 0.329
[ 11.481] (II) NOUVEAU(0): Supported established timings:
[ 11.481] (II) NOUVEAU(0): 720x400@70Hz
[ 11.481] (II) NOUVEAU(0): 640x480@60Hz
[ 11.481] (II) NOUVEAU(0): 640x480@67Hz
[ 11.481] (II) NOUVEAU(0): 640x480@72Hz
[ 11.481] (II) NOUVEAU(0): 640x480@75Hz
[ 11.481] (II) NOUVEAU(0): 800x600@56Hz
[ 11.481] (II) NOUVEAU(0): 800x600@60Hz
[ 11.481] (II) NOUVEAU(0): 800x600@72Hz
[ 11.481] (II) NOUVEAU(0): 800x600@75Hz
[ 11.481] (II) NOUVEAU(0): 832x624@75Hz
[ 11.481] (II) NOUVEAU(0): 1024x768@60Hz
[ 11.481] (II) NOUVEAU(0): 1024x768@70Hz
[ 11.481] (II) NOUVEAU(0): 1024x768@75Hz
[ 11.481] (II) NOUVEAU(0): 1280x1024@75Hz
[ 11.481] (II) NOUVEAU(0): 1152x864@75Hz
[ 11.481] (II) NOUVEAU(0): Manufacturer's mask: 0
[ 11.481] (II) NOUVEAU(0): Supported standard timings:
[ 11.481] (II) NOUVEAU(0): #0: hsize: 1680 vsize 1050 refresh: 60 vid: 179
[ 11.481] (II) NOUVEAU(0): #1: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
[ 11.481] (II) NOUVEAU(0): #2: hsize: 1440 vsize 900 refresh: 60 vid: 149
[ 11.481] (II) NOUVEAU(0): #3: hsize: 1440 vsize 900 refresh: 75 vid: 3989
[ 11.481] (II) NOUVEAU(0): #4: hsize: 1400 vsize 1050 refresh: 60 vid: 16528
[ 11.481] (II) NOUVEAU(0): #5: hsize: 1152 vsize 864 refresh: 75 vid: 20337
[ 11.481] (II) NOUVEAU(0): Supported detailed timing:
[ 11.481] (II) NOUVEAU(0): clock: 146.2 MHz Image Size: 474 x 296 mm
[ 11.481] (II) NOUVEAU(0): h_active: 1680 h_sync: 1784 h_sync_end 1960 h_blank_end 2240 h_border: 0
[ 11.481] (II) NOUVEAU(0): v_active: 1050 v_sync: 1053 v_sync_end 1059 v_blanking: 1089 v_border: 0
[ 11.481] (II) NOUVEAU(0): Serial No: 88LMVD003225
[ 11.481] (II) NOUVEAU(0): Ranges: V min: 56 V max: 75 Hz, H min: 31 H max: 81 kHz, PixClock max 175 MHz
[ 11.481] (II) NOUVEAU(0): Monitor name: ASUS-LS221Hÿÿ
[ 11.481] (II) NOUVEAU(0): Supported detailed timing:
[ 11.481] (II) NOUVEAU(0): clock: 148.5 MHz Image Size: 474 x 296 mm
[ 11.481] (II) NOUVEAU(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
[ 11.481] (II) NOUVEAU(0): v_active: 1080 v_sync: 1089 v_sync_end 1095 v_blanking: 1125 v_border: 0
[ 11.481] (II) NOUVEAU(0): Supported detailed timing:
[ 11.481] (II) NOUVEAU(0): clock: 148.5 MHz Image Size: 474 x 296 mm
[ 11.481] (II) NOUVEAU(0): h_active: 1920 h_sync: 2448 h_sync_end 2492 h_blank_end 2640 h_border: 0
[ 11.481] (II) NOUVEAU(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
[ 11.481] (II) NOUVEAU(0): Supported detailed timing:
[ 11.481] (II) NOUVEAU(0): clock: 74.2 MHz Image Size: 474 x 296 mm
[ 11.481] (II) NOUVEAU(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
[ 11.481] (II) NOUVEAU(0): v_active: 540 v_sync: 542 v_sync_end 547 v_blanking: 562 v_border: 0
[ 11.481] (II) NOUVEAU(0): Supported detailed timing:
[ 11.481] (II) NOUVEAU(0): clock: 74.2 MHz Image Size: 474 x 296 mm
[ 11.481] (II) NOUVEAU(0): h_active: 1920 h_sync: 2448 h_sync_end 2492 h_blank_end 2640 h_border: 0
[ 11.481] (II) NOUVEAU(0): v_active: 540 v_sync: 542 v_sync_end 547 v_blanking: 562 v_border: 0
[ 11.481] (II) NOUVEAU(0): Supported detailed timing:
[ 11.481] (II) NOUVEAU(0): clock: 74.2 MHz Image Size: 474 x 296 mm
[ 11.481] (II) NOUVEAU(0): h_active: 1280 h_sync: 1720 h_sync_end 1760 h_blank_end 1980 h_border: 0
[ 11.481] (II) NOUVEAU(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
[ 11.481] (II) NOUVEAU(0): Number of EDID sections to follow: 1
[ 11.482] (II) NOUVEAU(0): EDID (in hex):
[ 11.482] (II) NOUVEAU(0): 00ffffffffffff000469f12201010101
[ 11.482] (II) NOUVEAU(0): 1f120103802f1e782e78f5a655489b26
[ 11.482] (II) NOUVEAU(0): 125054bfef80b30081809500950f9040
[ 11.482] (II) NOUVEAU(0): 714f0101010121399030621a274068b0
[ 11.482] (II) NOUVEAU(0): 3600da281100001c000000ff0038384c
[ 11.482] (II) NOUVEAU(0): 4d56443030333232350a000000fd0038
[ 11.482] (II) NOUVEAU(0): 4b1f5111000a202020202020000000fc
[ 11.482] (II) NOUVEAU(0): 00415355532d4c5332323148ffff0107
[ 11.482] (II) NOUVEAU(0): Printing probed modes for output HDMI-1
[ 11.482] (II) NOUVEAU(0): Modeline "1920x1080"x50.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz UeP)
[ 11.482] (II) NOUVEAU(0): Modeline "1680x1050"x60.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz eP)
[ 11.482] (II) NOUVEAU(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
[ 11.482] (II) NOUVEAU(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1089 1095 1125 -hsync -vsync (67.5 kHz e)
[ 11.482] (II) NOUVEAU(0): Modeline "1920x1080"x50.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
[ 11.482] (II) NOUVEAU(0): Modeline "1920x1080"x60.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
[ 11.482] (II) NOUVEAU(0): Modeline "1400x1050"x60.0 121.75 1400 1488 1632 1864 1050 1053 1057 1089 -hsync +vsync (65.3 kHz e)
[ 11.482] (II) NOUVEAU(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 11.482] (II) NOUVEAU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 11.482] (II) NOUVEAU(0): Modeline "1440x900"x75.0 136.75 1440 1536 1688 1936 900 903 909 942 -hsync +vsync (70.6 kHz e)
[ 11.482] (II) NOUVEAU(0): Modeline "1440x900"x59.9 106.50 1440 1520 1672 1904 900 903 909 934 -hsync +vsync (55.9 kHz e)
[ 11.482] (II) NOUVEAU(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 11.482] (II) NOUVEAU(0): Modeline "1280x720"x50.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
[ 11.482] (II) NOUVEAU(0): Modeline "1280x720"x60.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
[ 11.482] (II) NOUVEAU(0): Modeline "1440x576"x50.0 27.00 1440 1464 1590 1728 576 580 586 625 interlace -hsync -vsync (15.6 kHz e)
[ 11.482] (II) NOUVEAU(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
[ 11.482] (II) NOUVEAU(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
[ 11.482] (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 11.482] (II) NOUVEAU(0): Modeline "1440x480"x59.9 27.00 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz e)
[ 11.482] (II) NOUVEAU(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e)
[ 11.482] (II) NOUVEAU(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
[ 11.482] (II) NOUVEAU(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 11.482] (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 11.482] (II) NOUVEAU(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
[ 11.482] (II) NOUVEAU(0): Modeline "720x576"x50.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
[ 11.482] (II) NOUVEAU(0): Modeline "720x480"x59.9 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
[ 11.482] (II) NOUVEAU(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz e)
[ 11.482] (II) NOUVEAU(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 11.482] (II) NOUVEAU(0): Modeline "640x480"x66.7 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz e)
[ 11.482] (II) NOUVEAU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 11.482] (II) NOUVEAU(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 11.482] (II) NOUVEAU(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 11.482] (II) NOUVEAU(0): Output VGA-1 connected
[ 11.482] (II) NOUVEAU(0): Output HDMI-1 connected
[ 11.482] (II) NOUVEAU(0): Using user preference for initial modes
[ 11.482] (II) NOUVEAU(0): Output VGA-1 using initial mode 1920x1080
[ 11.482] (II) NOUVEAU(0): Output HDMI-1 using initial mode 1920x1080
[ 11.482] (II) NOUVEAU(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 11.482] (--) NOUVEAU(0): Virtual size is 3600x1080 (pitch 0)
[ 11.482] (**) NOUVEAU(0): Driver mode "1920x1080": 148.5 MHz (scaled from 0.0 MHz), 67.5 kHz, 60.0 Hz
[ 11.482] (II) NOUVEAU(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz UeP)
[ 11.482] (**) NOUVEAU(0): Driver mode "1280x1024": 135.0 MHz (scaled from 0.0 MHz), 80.0 kHz, 75.0 Hz
[ 11.482] (II) NOUVEAU(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 11.482] (**) NOUVEAU(0): Driver mode "1280x1024": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.0 Hz
[ 11.482] (II) NOUVEAU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 11.482] (**) NOUVEAU(0): Driver mode "1152x864": 108.0 MHz (scaled from 0.0 MHz), 67.5 kHz, 75.0 Hz
[ 11.482] (II) NOUVEAU(0): Modeline "1152x864"x75.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 11.482] (**) NOUVEAU(0): Driver mode "1024x768": 78.8 MHz (scaled from 0.0 MHz), 60.1 kHz, 75.1 Hz
[ 11.482] (II) NOUVEAU(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
[ 11.482] (**) NOUVEAU(0): Driver mode "1024x768": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
[ 11.482] (II) NOUVEAU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 11.482] (**) NOUVEAU(0): Driver mode "800x600": 49.5 MHz (scaled from 0.0 MHz), 46.9 kHz, 75.0 Hz
[ 11.482] (II) NOUVEAU(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 11.482] (**) NOUVEAU(0): Driver mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.3 Hz
[ 11.482] (II) NOUVEAU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 11.482] (**) NOUVEAU(0): Driver mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.5 kHz, 75.0 Hz
[ 11.482] (II) NOUVEAU(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 11.482] (**) NOUVEAU(0): Driver mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
[ 11.482] (II) NOUVEAU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 11.482] (**) NOUVEAU(0): Driver mode "720x400": 28.3 MHz (scaled from 0.0 MHz), 31.5 kHz, 70.1 Hz
[ 11.482] (II) NOUVEAU(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 11.482] (**) NOUVEAU(0): Display dimensions: (510, 290) mm
[ 11.482] (**) NOUVEAU(0): DPI set to (179, 94)
[ 11.482] (II) Loading sub module "fb"
[ 11.482] (II) LoadModule: "fb"
[ 11.496] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 11.507] (II) Module fb: vendor="X.Org Foundation"
[ 11.508] compiled for 1.12.3.901, module version = 1.0.0
[ 11.508] ABI class: X.Org ANSI C Emulation, version 0.4
[ 11.508] (II) Loading sub module "exa"
[ 11.508] (II) LoadModule: "exa"
[ 11.508] (II) Loading /usr/lib/xorg/modules/libexa.so
[ 11.517] (II) Module exa: vendor="X.Org Foundation"
[ 11.517] compiled for 1.12.3.901, module version = 2.5.0
[ 11.517] ABI class: X.Org Video Driver, version 12.1
[ 11.517] (II) Loading sub module "shadowfb"
[ 11.517] (II) LoadModule: "shadowfb"
[ 11.517] (II) Loading /usr/lib/xorg/modules/libshadowfb.so
[ 11.522] (II) Module shadowfb: vendor="X.Org Foundation"
[ 11.522] compiled for 1.12.3.901, module version = 1.0.0
[ 11.522] ABI class: X.Org ANSI C Emulation, version 0.4
[ 11.522] (--) Depth 24 pixmap format is 32 bpp
[ 11.523] (II) NOUVEAU(0): Opened GPU channel 2
[ 11.527] (II) NOUVEAU(0): [DRI2] Setup complete
[ 11.527] (II) NOUVEAU(0): [DRI2] DRI driver: nouveau
[ 11.527] (II) NOUVEAU(0): [DRI2] VDPAU driver: nouveau
[ 11.529] (II) EXA(0): Driver allocated offscreen pixmaps
[ 11.529] (II) EXA(0): Driver registered support for the following operations:
[ 11.529] (II) Solid
[ 11.529] (II) Copy
[ 11.529] (II) Composite (RENDER acceleration)
[ 11.529] (II) UploadToScreen
[ 11.529] (II) DownloadFromScreen
[ 11.529] (==) NOUVEAU(0): Backing store disabled
[ 11.529] (==) NOUVEAU(0): Silken mouse enabled
[ 11.529] (II) NOUVEAU(0): [XvMC] Associated with Nouveau GeForce 8/9 Textured Video.
[ 11.529] (II) NOUVEAU(0): [XvMC] Extension initialized.
[ 11.529] (==) NOUVEAU(0): DPMS enabled
[ 11.529] (II) NOUVEAU(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 11.529] (WW) NOUVEAU(0): Option "Primary" is not used
[ 11.529] (--) RandR disabled
[ 11.529] (II) Initializing built-in extension Generic Event Extension
[ 11.529] (II) Initializing built-in extension SHAPE
[ 11.530] (II) Initializing built-in extension MIT-SHM
[ 11.530] (II) Initializing built-in extension XInputExtension
[ 11.530] (II) Initializing built-in extension XTEST
[ 11.530] (II) Initializing built-in extension BIG-REQUESTS
[ 11.530] (II) Initializing built-in extension SYNC
[ 11.530] (II) Initializing built-in extension XKEYBOARD
[ 11.530] (II) Initializing built-in extension XC-MISC
[ 11.530] (II) Initializing built-in extension SECURITY
[ 11.530] (II) Initializing built-in extension XINERAMA
[ 11.530] (II) Initializing built-in extension XFIXES
[ 11.530] (II) Initializing built-in extension RENDER
[ 11.530] (II) Initializing built-in extension RANDR
[ 11.530] (II) Initializing built-in extension COMPOSITE
[ 11.530] (II) Initializing built-in extension DAMAGE
[ 11.843] (EE) AIGLX error: Calling driver entry point failed
[ 11.852] (EE) AIGLX: reverting to software rendering
[ 11.852] (II) AIGLX: Screen 0 is not DRI capable
[ 12.107] (II) AIGLX: Loaded and initialized swrast
[ 12.107] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[ 12.120] (II) NOUVEAU(0): NVEnterVT is called.
[ 12.331] (II) NOUVEAU(0): Setting screen physical size to 1016 x 285
[ 12.331] resize called 3840 1080
[ 12.709] (II) config/udev: Adding input device Power Button (/dev/input/event5)
[ 12.709] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 12.709] (II) LoadModule: "evdev"
[ 12.709] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 12.748] (II) Module evdev: vendor="X.Org Foundation"
[ 12.748] compiled for 1.12.3.901, module version = 2.7.3
[ 12.748] Module class: X.Org XInput Driver
[ 12.748] ABI class: X.Org XInput driver, version 16.0
[ 12.748] (II) Using input driver 'evdev' for 'Power Button'
[ 12.748] (**) Power Button: always reports core events
[ 12.748] (**) evdev: Power Button: Device: "/dev/input/event5"
[ 12.748] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 12.748] (--) evdev: Power Button: Found keys
[ 12.748] (II) evdev: Power Button: Configuring as keyboard
[ 12.748] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input5/event5"
[ 12.748] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 12.748] (**) Option "xkb_rules" "evdev"
[ 12.748] (**) Option "xkb_model" "evdev"
[ 12.748] (**) Option "xkb_layout" "it"
[ 12.792] (II) config/udev: Adding input device Video Bus (/dev/input/event6)
[ 12.792] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 12.792] (II) Using input driver 'evdev' for 'Video Bus'
[ 12.792] (**) Video Bus: always reports core events
[ 12.792] (**) evdev: Video Bus: Device: "/dev/input/event6"
[ 12.792] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 12.792] (--) evdev: Video Bus: Found keys
[ 12.792] (II) evdev: Video Bus: Configuring as keyboard
[ 12.792] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A03:00/device:19/LNXVIDEO:00/input/input6/event6"
[ 12.792] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[ 12.793] (**) Option "xkb_rules" "evdev"
[ 12.793] (**) Option "xkb_model" "evdev"
[ 12.793] (**) Option "xkb_layout" "it"
[ 12.794] (II) config/udev: Adding input device Power Button (/dev/input/event4)
[ 12.794] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 12.794] (II) Using input driver 'evdev' for 'Power Button'
[ 12.794] (**) Power Button: always reports core events
[ 12.794] (**) evdev: Power Button: Device: "/dev/input/event4"
[ 12.794] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 12.794] (--) evdev: Power Button: Found keys
[ 12.794] (II) evdev: Power Button: Configuring as keyboard
[ 12.794] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input4/event4"
[ 12.794] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
[ 12.794] (**) Option "xkb_rules" "evdev"
[ 12.794] (**) Option "xkb_model" "evdev"
[ 12.794] (**) Option "xkb_layout" "it"
[ 12.796] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/event0)
[ 12.796] (**) Logitech USB-PS/2 Optical Mouse: Applying InputClass "evdev pointer catchall"
[ 12.796] (II) Using input driver 'evdev' for 'Logitech USB-PS/2 Optical Mouse'
[ 12.796] (**) Logitech USB-PS/2 Optical Mouse: always reports core events
[ 12.796] (**) evdev: Logitech USB-PS/2 Optical Mouse: Device: "/dev/input/event0"
[ 12.796] (--) evdev: Logitech USB-PS/2 Optical Mouse: Vendor 0x46d Product 0xc043
[ 12.796] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found 12 mouse buttons
[ 12.796] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found scroll wheel(s)
[ 12.796] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found relative axes
[ 12.796] (--) evdev: Logitech USB-PS/2 Optical Mouse: Found x and y relative axes
[ 12.796] (II) evdev: Logitech USB-PS/2 Optical Mouse: Configuring as mouse
[ 12.796] (II) evdev: Logitech USB-PS/2 Optical Mouse: Adding scrollwheel support
[ 12.796] (**) evdev: Logitech USB-PS/2 Optical Mouse: YAxisMapping: buttons 4 and 5
[ 12.796] (**) evdev: Logitech USB-PS/2 Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 12.796] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:02.0/usb3/3-1/3-1:1.0/input/input0/event0"
[ 12.796] (II) XINPUT: Adding extended input device "Logitech USB-PS/2 Optical Mouse" (type: MOUSE, id 9)
[ 12.796] (II) evdev: Logitech USB-PS/2 Optical Mouse: initialized for relative axes.
[ 12.796] (**) Logitech USB-PS/2 Optical Mouse: (accel) keeping acceleration scheme 1
[ 12.796] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration profile 0
[ 12.796] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration factor: 2.000
[ 12.796] (**) Logitech USB-PS/2 Optical Mouse: (accel) acceleration threshold: 4
[ 12.797] (II) config/udev: Adding input device Logitech USB-PS/2 Optical Mouse (/dev/input/mouse0)
[ 12.797] (II) No input driver specified, ignoring this device.
[ 12.797] (II) This device may have been added with another device file.
[ 12.797] (II) config/udev: Adding input device LOGITECH G110 G-keys (/dev/input/event1)
[ 12.797] (**) LOGITECH G110 G-keys: Applying InputClass "evdev keyboard catchall"
[ 12.797] (II) Using input driver 'evdev' for 'LOGITECH G110 G-keys'
[ 12.797] (**) LOGITECH G110 G-keys: always reports core events
[ 12.797] (**) evdev: LOGITECH G110 G-keys: Device: "/dev/input/event1"
[ 12.797] (--) evdev: LOGITECH G110 G-keys: Vendor 0x46d Product 0xc22b
[ 12.797] (--) evdev: LOGITECH G110 G-keys: Found keys
[ 12.797] (II) evdev: LOGITECH G110 G-keys: Configuring as keyboard
[ 12.797] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:02.1/usb1/1-2/1-2.1/1-2.1:1.0/input/input1/event1"
[ 12.797] (II) XINPUT: Adding extended input device "LOGITECH G110 G-keys" (type: KEYBOARD, id 10)
[ 12.797] (**) Option "xkb_rules" "evdev"
[ 12.797] (**) Option "xkb_model" "evdev"
[ 12.797] (**) Option "xkb_layout" "it"
[ 12.797] (II) config/udev: Adding input device Gaming Keyboard G110 (/dev/input/event2)
[ 12.797] (**) Gaming Keyboard G110: Applying InputClass "evdev keyboard catchall"
[ 12.797] (II) Using input driver 'evdev' for 'Gaming Keyboard G110'
[ 12.797] (**) Gaming Keyboard G110: always reports core events
[ 12.797] (**) evdev: Gaming Keyboard G110: Device: "/dev/input/event2"
[ 12.797] (--) evdev: Gaming Keyboard G110: Vendor 0x46d Product 0xc22a
[ 12.797] (--) evdev: Gaming Keyboard G110: Found keys
[ 12.797] (II) evdev: Gaming Keyboard G110: Configuring as keyboard
[ 12.797] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:02.1/usb1/1-2/1-2.3/1-2.3:1.0/input/input2/event2"
[ 12.797] (II) XINPUT: Adding extended input device "Gaming Keyboard G110" (type: KEYBOARD, id 11)
[ 12.797] (**) Option "xkb_rules" "evdev"
[ 12.797] (**) Option "xkb_model" "evdev"
[ 12.797] (**) Option "xkb_layout" "it"
[ 12.798] (II) config/udev: Adding input device Gaming Keyboard G110 (/dev/input/event3)
[ 12.798] (**) Gaming Keyboard G110: Applying InputClass "evdev keyboard catchall"
[ 12.798] (II) Using input driver 'evdev' for 'Gaming Keyboard G110'
[ 12.798] (**) Gaming Keyboard G110: always reports core events
[ 12.798] (**) evdev: Gaming Keyboard G110: Device: "/dev/input/event3"
[ 12.798] (--) evdev: Gaming Keyboard G110: Vendor 0x46d Product 0xc22a
[ 12.798] (--) evdev: Gaming Keyboard G110: Found keys
[ 12.798] (II) evdev: Gaming Keyboard G110: Configuring as keyboard
[ 12.798] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:02.1/usb1/1-2/1-2.3/1-2.3:1.1/input/input3/event3"
[ 12.798] (II) XINPUT: Adding extended input device "Gaming Keyboard G110" (type: KEYBOARD, id 12)
[ 12.798] (**) Option "xkb_rules" "evdev"
[ 12.798] (**) Option "xkb_model" "evdev"
[ 12.798] (**) Option "xkb_layout" "it"
[ 12.798] (II) config/udev: Adding input device UVC Camera (046d:081b) (/dev/input/event7)
[ 12.798] (**) UVC Camera (046d:081b): Applying InputClass "evdev keyboard catchall"
[ 12.798] (II) Using input driver 'evdev' for 'UVC Camera (046d:081b)'
[ 12.798] (**) UVC Camera (046d:081b): always reports core events
[ 12.798] (**) evdev: UVC Camera (046d:081b): Device: "/dev/input/event7"
[ 12.798] (--) evdev: UVC Camera (046d:081b): Vendor 0x46d Product 0x81b
[ 12.798] (--) evdev: UVC Camera (046d:081b): Found keys
[ 12.798] (II) evdev: UVC Camera (046d:081b): Configuring as keyboard
[ 12.798] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:04.1/usb2/2-2/2-2.2/2-2.2:1.0/input/input7/event7"
[ 12.798] (II) XINPUT: Adding extended input device "UVC Camera (046d:081b)" (type: KEYBOARD, id 13)
[ 12.798] (**) Option "xkb_rules" "evdev"
[ 12.798] (**) Option "xkb_model" "evdev"
[ 12.798] (**) Option "xkb_layout" "it"
[ 84.333] (II) NOUVEAU(0): NVLeaveVT is called.
[ 144.460] (II) NOUVEAU(0): NVEnterVT is called.
[ 144.544] (II) NOUVEAU(0): EDID vendor "DEL", prod id 16486
[ 144.544] (II) NOUVEAU(0): Using hsync ranges from config file
[ 144.544] (II) NOUVEAU(0): Using vrefresh ranges from config file
[ 144.544] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 144.544] (II) NOUVEAU(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
[ 144.544] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 144.544] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 144.544] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 144.544] (II) NOUVEAU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 144.544] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 144.544] (II) NOUVEAU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 144.544] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 144.544] (II) NOUVEAU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 144.544] (II) NOUVEAU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 144.544] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 144.544] (II) NOUVEAU(0): Modeline "1920x1080"x60.0 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -hsync +vsync (67.1 kHz e)
[ 154.758] (II) NOUVEAU(0): EDID vendor "DEL", prod id 16486
[ 154.758] (II) NOUVEAU(0): Using hsync ranges from config file
[ 154.758] (II) NOUVEAU(0): Using vrefresh ranges from config file
[ 154.758] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 154.758] (II) NOUVEAU(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
[ 154.758] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 154.758] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 154.758] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 154.758] (II) NOUVEAU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 154.758] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 154.758] (II) NOUVEAU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 154.758] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 154.758] (II) NOUVEAU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 154.758] (II) NOUVEAU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 154.758] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 154.758] (II) NOUVEAU(0): Modeline "1920x1080"x60.0 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -hsync +vsync (67.1 kHz e)
[ 154.880] resize called 1920 1080
[ 233.862] (II) NOUVEAU(0): EDID vendor "DEL", prod id 16486
[ 233.862] (II) NOUVEAU(0): Using hsync ranges from config file
[ 233.862] (II) NOUVEAU(0): Using vrefresh ranges from config file
[ 233.862] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 233.862] (II) NOUVEAU(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
[ 233.862] (II) NOUVEAU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 233.862] (II) NOUVEAU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
[ 233.862] (II) NOUVEAU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 233.862] (II) NOUVEAU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 233.862] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[ 233.862] (II) NOUVEAU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
[ 233.862] (II) NOUVEAU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 233.862] (II) NOUVEAU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
[ 233.862] (II) NOUVEAU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e)
[ 233.862] (II) NOUVEAU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 233.862] (II) NOUVEAU(0): Modeline "1920x1080"x60.0 172.80 1920 2040 2248 2576 1080 1081 1084 1118 -hsync +vsync (67.1 kHz e)
[ 233.920] resize called 3600 1080
Any hints on what it's not working? I use Slim as login manager, and when it comes up, the left screen only show a small portion of the screen.Option "monitor-VGA-1" "Dell"
Option "monitor-HDMI-1" "Asus"
Do you need the word monitor in there? I was under the impression you only needed "VGA-1". I'm having a similar problem to you though so don't take my advice too carefully (why didn't I back up my old conf file :'()
Edit; You do.
Here is my krandrrc from when I used KDE. Could you put something in your autostart as a hack?
[Display]
ApplyOnStartup=true
StartupCommands=xrandr --output VGA-1 --pos 1920x0 --mode 1440x900 --refresh 59.8874\nxrandr --output DVI-I-1 --pos 0x0 --mode 1920x1080 --refresh 60\nxrandr --output VGA-1 --primary
[Screen_0]
OutputsUnified=false
UnifiedRect=0,0,0,0
UnifiedRotation=1
[Screen_0_Output_DVI-I-1]
Active=true
Rect=0,0,1920,1080
RefreshRate=60
Rotation=1
[Screen_0_Output_VGA-1]
Active=true
Rect=1920,0,1440,900
RefreshRate=59.8874435424805
Rotation=1
Last edited by SS4 (2012-08-16 23:49:09) -
Dual Booting Ubuntu Linux and Windows on a RAID 1 setup
Hi,
I just bought a Lenovo W530 with Windows 7 and two 500GB hard drives in a RAID 1 setup, is there a way for me to install Linux with dual boot while maintaing my RAID 1 setup?
Thanks.Hi
Welcome To Lenovo Community
if you want both in a raid on two drives, there is no way simpler than using fakeraid.
Windows simply has only the fakeraid as a software raid and can't be run from a linux software raid. An Ubuntu 10.10 install to fakeraid is relatively simple but should not be undertaken without some understanding of what a raid install looks like or behaves.
As a starter, some simple rules have to be followed:
1) Install Win 7 first
2) If Win 7 occupies the whole raid drive, use Win 7 disk manager to shrink it to make room for Ubuntu.
3) Use gparted on a live cd to place all your unallocated space for installing Ubuntu into an extended partition. This will insure that you will not likely exceed the 4 primary partition limit and thus bar an Ubuntu install.
Once prepared as above you should be able to install Ubunto to the largest unallocated space, as long as the partitioner recognizes the raid (ie the win 7 partitions will show in gparted). You should plan to run the install from the live cd so that you have determined beforehand that 10.10 will run on your system.
http://ubuntuforums.org/showthread.php?t=1600991
Hope This Helps
Cheers!!!
WW Social Media
Important Note: If you need help, post your question in the forum, and include your system type, model number and OS. Do not post your serial number.
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"!
Follow @LenovoForums on Twitter!
How to send a private message? --> Check out this article.
English Community Deutsche Community Comunidad en Español -
PCIe SATA Cards for RAID for video: Seritek 2ME4-E vs Sonnet Tempo E4P
Hey Folks,
I'm just about to purchase bigger, faster RAID system for my video editing needs. I've already purchased 1TB Barracudas for the drives and I have decided on the Burly dual PM for the enclosure. http://www.burlystorage.com/ccp0-catshow/burlydualpm.html
The questions is which card? I've had a seritek 2 port card and also their expresscard for years without a problem. But some tests I've seen indicate that the Sonnet is a bit faster. Then again, I know that some people had problems with the firmware at least as recently as last spring.
What do people say? Hatter and Japamac, I'm hoping to hear from you.FirmTek:
If you would like the ability to support port multiplier enclosures and 3rd party SMART applications, the FirmTek SeriTek/e6G would be my choice for a low cost 2-port 6G controller with these features. This card features hot swap and is also able to hot plug Oxford 936/946 based enclosures without the need for a restart. Installation is easy.
I use the SeriTek/e6G in the 2009 Mac Pro with Mac OS X 10.6.5. The PCIe 2.0 slots in the 2009 model provide optimized performance. >
http://www.firmtek.com/seritek/seritek-e6g/
You want a 4x or above card usually, one that has more bandwidth and performance, than those low end 1x 2-port cards that can't drive enough MB/sec to make using multiple drives / multiple enclosures.
Well, seeing you went with Seagate, not my cup of tea, I would have said WD Black Caviar 2TB drives instead.
Sonnet 4-port E4P is what I have used but it or its drivers may be an issue, totally unsure.
PM today is limited by today's drives. When it came out drives were slow by comparison, a mere 75MB/sec while today one drive can shovel 90-125MB/sec or half of what a PM can handle. You only get in real world about 250MB/sec maybe (overhead takes away from that 300MB/sec per port). That means while 6Gb is great, PM enclosures like FirmTek5PM need a new faster PM chip. Again, no idea where that is or when we will see it.
Maybe you should ask about SAS and be looking at even higher end RAID controllers from Areca perhaps.
Maybe you are looking for
-
How to save an image from canvas to jpeg2000 format?
good day! i would like some help about jj2000. i wish to save an image from canvas to a jpeg2000 format file. how will i do it using the jj2000? i just need to save it to a file. please help!!! thank you in advance! lrds
-
OS - Linux SunAppServ 9.1 Hi, I want to create in AdminPanel on 4848 port new ConnectionPool in Resources/JDBC. To do this I can chose Postgres Vendor but I want to use my new Postgres driver because default is not work. I hava postgresql-8.2-505.jdb
-
How to call html page rear adf button
Hello, I've an html page with javascript code and css in adf project. Is it possible to call my html page rear an adf button if yes how?
-
J2ee:tutorial:savingsaccount problem connecting to cloudscape database
I'm running Windows ME, and have been working through the tutorial. I thought I had most of my path problems cleared up, but appartently one remains. Having successfully deployed the 'SavingsAccountApp.ear' when running it, the follow error is return
-
SO8 Debian Installation doesn`t work
Hi Had someone intalles SO8 an a Debian system? Where can I find a installation guide for debian? Thanks