Re: [osol-discuss] eSATA works fine?
I always install GRUB on the Solaris partition, never on MBR - because if there is a problem with GRUB, it is just a matter of activating the Solaris partition. If I install GRUB on MBR and if there is a problem, I have to reinstall GRUB, fix the configuration file, etc - much more work. It is easier to just activate the Solaris partition. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] eSATA works fine?
I dont think that was the problem. When I booted the PC, I press F12 which gives me a menu of different hardware I can boot from: CD, USB, Hard disks, etc. I chose to boot from hard disks, and I chose to boot from the internal system disk - but it didnt work - I could not boot Solaris. The problem was that only the Windows partition were activated. When I chose to boot only, WinXP or Win7 booted. I could not boot into GRUB, because GRUB is on the Solaris partition. I must set Solaris partition as "active", which boots into GRUB, which then allows me to boot any OS. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] eSATA works fine?
On 3/16/2011 3:22 PM, Orvar Korvar wrote: Ok, progress report: I installed an eSATA pci-express card and everything is fine. On my system disk, I have WinXP and S11e, and I can choose between them from GRUB. I have now attached an eSATA external disk and installed Win7 on it. The external eSATA disk must be powered on upon boot of the PC, otherwise it seems that the PC will not recognize the eSATA disk. I installed Win7 on the external disk, and upon reboot, I got to choose between Win7 and "older windows" - which means WinXP. I can not reach GRUB (i.e. not boot Solaris). In WinXP I could see my Solaris partition in the disk administration program "Control Panel -> bla bla". I saw that WinXP partition was marked as "active" so I tried to set Solaris partition as "active" but could not from within WinXP. I installed Acronis in Win7 and could now mark the Solaris partition as "active" and when I rebooted, I booted into GRUB! So now I could choose to boot S11e or Windows. If I choose to boot Windows, I see a another menu where I can choose between Win7 or "Older Windows" - which means WinXP. Thus, I have Win7 on an eSATA disk, and because my Solaris partition is "active" I always boot into GRUB. From there, I can boot which ever OS I want. If I power off the eSATA disk, I still boot into GRUB and can choose between Solaris and WinXP. Everything is working just as I wanted. Over and out. Oskar, Glad you got it straightened out. Your "problem", if you can call it that, was caused by the PC's BIOS putting the eSATA drive ahead of the internal SATA drives in the disk boot order. You should be able to go to the BIOS, and look for some menu option for Boot Order (or something like that). Change the order to have any "removable" or similar type device boot AFTER the first internal disk. It will then pick up GRUB on the internal disk, and you can adjust GRUB to boot Win7 via editing /rpool/boot/grub/menu.lst when booted to S11. Of course, your solution works, too. :-) -- Erik Trimble Java System Support Mailstop: usca22-123 Phone: x17195 Santa Clara, CA ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] eSATA works fine?
Ok, progress report: I installed an eSATA pci-express card and everything is fine. On my system disk, I have WinXP and S11e, and I can choose between them from GRUB. I have now attached an eSATA external disk and installed Win7 on it. The external eSATA disk must be powered on upon boot of the PC, otherwise it seems that the PC will not recognize the eSATA disk. I installed Win7 on the external disk, and upon reboot, I got to choose between Win7 and "older windows" - which means WinXP. I can not reach GRUB (i.e. not boot Solaris). In WinXP I could see my Solaris partition in the disk administration program "Control Panel -> bla bla". I saw that WinXP partition was marked as "active" so I tried to set Solaris partition as "active" but could not from within WinXP. I installed Acronis in Win7 and could now mark the Solaris partition as "active" and when I rebooted, I booted into GRUB! So now I could choose to boot S11e or Windows. If I choose to boot Windows, I see a another menu where I can choose between Win7 or "Older Windows" - which means WinXP. Thus, I have Win7 on an eSATA disk, and because my Solaris partition is "active" I always boot into GRUB. From there, I can boot which ever OS I want. If I power off the eSATA disk, I still boot into GRUB and can choose between Solaris and WinXP. Everything is working just as I wanted. Over and out. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] eSATA works fine?
Eric Trimble wrote: > > When determining what protocol is spoken over a > physical connection > between a host controller and a drive (or other > peripheral), you look > for the highest common denominator - thus, a 2.0 > controller will speak > 2.0 when talking to a 3.0 peripheral, but will speak > 1.0 when talking to > a 1.0 peripheral. So as an example, I have an Intel Motherboard DP35DP with 5 Sata and 1 E-Sata port. I have 2 sata disks connected to sata ports and an external E-Sata connected to the E-Sata port. Works on S10U8 with patches to about a year ago. When I do an LU to current patches, my current E-Sata disk disappears with the boot to the new patched environmnet and I have not been able to force the system to view the disk > > > When wondering whether a device is a chipset or a > physical layer change, > consider this: does the device actually change the > information being > transported through it, or does it merely change the > electrical form of > the message? Clearly something in the patched OS changed the driver from refusing to now enumerated a previously recognized device. > > Thus, the following would only change the electrical > form: > > eSATA - it changes the physical connector and cable, > but doesn't make > any other information change your comments seem orthogonal to my experience with my E-Sata device. Ben > -- > Erik Trimble > Java System Support > Mailstop: usca22-123 > Phone: x17195 > Santa Clara, CA -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] eSATA works fine?
>From the fact that there was at one time a project to add port multiplier >support, I'm thinking that there is a need for driver support; maybe not a >separate driver, but for the driver to be aware that such things might be >present at least. -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] eSATA works fine?
eSATA works the same way as regular SATA - you connect a drive to the eSATA connector, and if automount is enabled (volfs i believe) it will automount the disk. However if it doesn't, you can monitor dmesg for the device identifier and mount it yourself. SATA is also hot-swap, so you can remove the drive while the computer is running, just remember to unmount the disk before you do so. On Mon, Mar 7, 2011 at 09:22, Orvar Korvar wrote: > Ok, great info! Thanx a lot! I didnt knew that. I got to get myself an eSATA > chassi now. USB2 sucks badly. Thanx for this info, guys. > > A last question: how do I use eSATA? Similar to USB? I just plug the eSATA > disk in, and then it mounts automatically? Or I use "format" to see the disc > and mount it manually? -- " ' With the first link, the chain is forged. The first speech censured, the first thought forbidden, the first freedom denied, chains us all irrevocably.' Those words were uttered by Judge Aaron Satie as wisdom and warning... The first time any man's freedom is trodden on we’re all damaged." - Jean-Luc Picard, quoting Judge Aaron Satie, Star Trek: TNG episode "The Drumhead" - Alex Smith (K4RNT) - Sterling, Virginia USA ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] eSATA works fine?
Orvar, As mentioned, there is the physical hardware 'interfacing' component and then software component (protocol handler). There IS a software driver for USB 3.0, but currently not 'officially' implemented within the Solaris/OpenSolaris core environment by default yet. This will support xHCI and 5 Gb/s transfers. You can buy USB 3.0 hardware today though which will default to USB 1.0/2.0 transfer speeds (approx. 480 Mb/s) by design under the Solaris/OpenSolaris OS by default. The SIIG DP SuperSpeed USB 2-Port PCIe (JU-P20412-S2) PCIe card works well as an example. ~ Ken Mays --- On Sun, 3/6/11, Orvar Korvar wrote: > From: Orvar Korvar > Subject: Re: [osol-discuss] eSATA works fine? > To: opensolaris-discuss@opensolaris.org > Date: Sunday, March 6, 2011, 4:47 PM > >> eSATA is a physical > connector and electrical standard for SATA. > > So you are implying that eSATA does not need any drivers? > It is like an ordinary SATA controller, those dont need > drivers either? > > So what is the difference between eSATA and USB3.0? Why > does USB3 need a driver, isnt it a physical connector as > well? Is there a simple rule of thumb to tell which > connections need a driver, and which dont need a driver? > -- > This message posted from opensolaris.org > ___ > opensolaris-discuss mailing list > opensolaris-discuss@opensolaris.org > ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] eSATA works fine?
Ok, great info! Thanx a lot! I didnt knew that. I got to get myself an eSATA chassi now. USB2 sucks badly. Thanx for this info, guys. A last question: how do I use eSATA? Similar to USB? I just plug the eSATA disk in, and then it mounts automatically? Or I use "format" to see the disc and mount it manually? -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] eSATA works fine?
On 3/6/2011 1:51 PM, Orvar Korvar wrote: And 6Gbit SATA card needs a driver? Yes. You are confusing physical layer (connections and cables) with chip-level processing. Physical layer simply describes how the electrical signals are sent, and has nothing to do with the actual *content* of those signals. Each of the following requires some sort of chipset - this chipset interprets the information it gets from the computer, and converts it into the appropriate protocol. In general, a new PROTOCOL will require a new chipset. Certain chipsets will provide backwards compatibility (i.e. something handling a 3.0 protocol will likely also understand 2.0 and 1.0 of that particular protocol), but there is no forwards compatibility (i.e. a 2.0 chipset can't understand 3.0 protocol). SATA IDE SCSI FibreChannel USB (and many others). Chipsets require drivers. Physical layer changes do not. When determining what protocol is spoken over a physical connection between a host controller and a drive (or other peripheral), you look for the highest common denominator - thus, a 2.0 controller will speak 2.0 when talking to a 3.0 peripheral, but will speak 1.0 when talking to a 1.0 peripheral. When wondering whether a device is a chipset or a physical layer change, consider this: does the device actually change the information being transported through it, or does it merely change the electrical form of the message? Thus, the following would only change the electrical form: SAS/SATA port multiplexer/replicators - they don't change the information, merely create a 1-to-many electical signal. eSATA - it changes the physical connector and cable, but doesn't make any other information change SCSI Ultra2 -> Ultra320 cables - once again, merely the electrical signal is changed, not the information format FC multimode vs singlemode connectors - defines what type of laser signal is used to send the FC packets, and thus is just a electrical format To be perfectly honest, there is one category that is slightly confusing: protocol translators, often called "bridges". You most often see this in the "SAS to SATA bridge", though many Host Bus Adapters also contain a chip on them that does PCI-E to translation. These items are "magic black boxes" - they take an input signal, and "magically" convert it to some other. They do this independent of any OS or outside control, and thus, don't need a driver. Bridges don't alter the information content of the signal, but do alter the protocol being used - they act as super-translators. -- Erik Trimble Java System Support Mailstop: usca22-123 Phone: x17195 Santa Clara, CA ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] eSATA works fine?
And 6Gbit SATA card needs a driver? -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] eSATA works fine?
SATA does need an driver, the same eSATA uses actually USB 3.0 also needs a driver which i dont think is available yet, at least for solaris On Sun, Mar 6, 2011 at 6:47 PM, Orvar Korvar wrote: >>> eSATA is a physical connector and electrical standard for SATA. > > So you are implying that eSATA does not need any drivers? It is like an > ordinary SATA controller, those dont need drivers either? > > So what is the difference between eSATA and USB3.0? Why does USB3 need a > driver, isnt it a physical connector as well? Is there a simple rule of thumb > to tell which connections need a driver, and which dont need a driver? > -- > This message posted from opensolaris.org > ___ > opensolaris-discuss mailing list > opensolaris-discuss@opensolaris.org > ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] eSATA works fine?
For instance a port replicator, does it need a driver? How can I tell when a driver is needed, or not? -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] eSATA works fine?
>> eSATA is a physical connector and electrical standard for SATA. So you are implying that eSATA does not need any drivers? It is like an ordinary SATA controller, those dont need drivers either? So what is the difference between eSATA and USB3.0? Why does USB3 need a driver, isnt it a physical connector as well? Is there a simple rule of thumb to tell which connections need a driver, and which dont need a driver? -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] eSATA works fine?
On Sun, Mar 6, 2011 at 3:13 PM, Orvar Korvar wrote: > I suspect USB 3.0 needs Solaris drivers, and there are no such drivers yet? > I don't think there are USB 3.0 controller drivers. > How about eSATA? Does it need Solaris drivers as well? And where can I get > such drivers? Does eSATA work well? Do I need to use HCL compatible eSATA > chipset or something? What do I need to think about? eSATA is a physical connector and electrical standard for SATA. -Albert ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] eSATA works fine?
I suspect USB 3.0 needs Solaris drivers, and there are no such drivers yet? How about eSATA? Does it need Solaris drivers as well? And where can I get such drivers? Does eSATA work well? Do I need to use HCL compatible eSATA chipset or something? What do I need to think about? -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
