Re: [osol-discuss] pcie_hp_init: initialize hotplug controller failed with -1
It is a hardware bug on some x86 systems. While the problem PCI bridges show the hotplug capability in their device registers, the system does not really support PCI hotplug slots on those PCI bridges. No real impacts to the system. This is issue is tracked by bug ID 6904360. It will be fixed soon. Colin Milan Jurik wrote: Hi, Alexander píše v út 15. 12. 2009 v 09:31 -0800: Hello. After updating OpenSolaris from snv_126 to snv_129 I started to receive the following messages on boot: Dec 15 19:15:36 opensolaris genunix: [ID 936769 kern.info] pcieb0 is /p...@0,0/pci8086,2...@1 Dec 15 19:15:36 opensolaris pcie: [ID 441510 kern.warning] WARNING: pcie_hp_init: initialize hotplug controller failed with -1 Dec 15 19:15:36 opensolaris pcie: [ID 552151 kern.warning] WARNING: pcieb1: Failed setting hotplug framework Dec 15 19:15:36 opensolaris npe: [ID 236367 kern.info] PCI Express-device: pci8086,2...@1c, pcieb1 Dec 15 19:15:36 opensolaris genunix: [ID 936769 kern.info] pcieb1 is /p...@0,0/pci8086,2...@1c Dec 15 19:15:36 opensolaris pcie: [ID 441510 kern.warning] WARNING: pcie_hp_init: initialize hotplug controller failed with -1 Dec 15 19:15:36 opensolaris pcie: [ID 552151 kern.warning] WARNING: pcieb2: Failed setting hotplug framework Dec 15 19:15:36 opensolaris npe: [ID 236367 kern.info] PCI Express-device: pci8086,2...@1c,1, pcieb2 Dec 15 19:15:36 opensolaris genunix: [ID 936769 kern.info] pcieb2 is /p...@0,0/pci8086,2...@1c,1 Dec 15 19:15:36 opensolaris pcie: [ID 441510 kern.warning] WARNING: pcie_hp_init: initialize hotplug controller failed with -1 Dec 15 19:15:36 opensolaris pcie: [ID 552151 kern.warning] WARNING: pcieb3: Failed setting hotplug framework Dec 15 19:15:36 opensolaris npe: [ID 236367 kern.info] PCI Express-device: pci8086,2...@1c,2, pcieb3 Dec 15 19:15:36 opensolaris genunix: [ID 936769 kern.info] pcieb3 is /p...@0,0/pci8086,2...@1c,2 Dec 15 19:15:36 opensolaris pcie: [ID 441510 kern.warning] WARNING: pcie_hp_init: initialize hotplug controller failed with -1 Dec 15 19:15:36 opensolaris pcie: [ID 552151 kern.warning] WARNING: pcieb4: Failed setting hotplug framework Dec 15 19:15:36 opensolaris npe: [ID 236367 kern.info] PCI Express-device: pci8086,2...@1c,3, pcieb4 Dec 15 19:15:36 opensolaris genunix: [ID 936769 kern.info] pcieb4 is /p...@0,0/pci8086,2...@1c,3 Dec 15 19:15:36 opensolaris pcie: [ID 441510 kern.warning] WARNING: pcie_hp_init: initialize hotplug controller failed with -1 Dec 15 19:15:36 opensolaris pcie: [ID 552151 kern.warning] WARNING: pcieb5: Failed setting hotplug framework What does it mean??? There were some significant changes added to snv_128. Please, log new bug on bugs.opensolaris.org and add description of your system. Best regards, Milan ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] snv_129 problems with hotplug and speedstep
Bruno Damour wrote: Hello, I upgraded my box yesterday from sxce b127 to sxce b129. Everything went smoothly but I get two worrying error messages : - hotplug failure : Dec 12 10:12:30 unknown pcie: [ID 441510 kern.warning] WARNING: pcie_hp_init: initialize hotplug controller failed with -1 Dec 12 10:12:30 unknown pcie: [ID 552151 kern.warning] WARNING: pcieb2: Failed setting hotplug framework I just replied in another email thread for the same issue, quoted here: It is a hardware bug on some x86 systems. While the problem PCI bridges show the hotplug capability in their device registers, the system does not really support PCI hotplug slots on those PCI bridges. No real impacts to the system. This is issue is tracked by bug ID 6904360. It will be fixed soon. Colin ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Indiana Wish List
-web cam Works to some extent already with Ekiga. True, but many new cameras are UVC compliant but require firmware to be uploaded to it before it can operate using the generic UVC driver. The world of webcams are very diverse. There are so many different chips that are vendor private. It is a tough job to develop a bunch of webcam drivers to support them all. Fortunately, there are quite a few compliant to UVC and need not firmwares. More info see the following links. http://opensolaris.org/os/community/on/flag-days/pages/2007012201/ http://blogs.sun.com/colin/entry/usb_webcams_and_video_conferencing Colin ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] maxtor onetouch III 1TB USB storage snv_b64a
The USB FAQ storage section might help you. http://www.sun.com/io_technologies/usb/USB-Faq.html#Storage The scsa2usb.conf property is mentioned in question 20. - Colin Stefan Parvu wrote: For FireWire: nope. Nothing reported from scsa1394 driver. However after your suggestion Im able to see now: c4t0d0p0. [EMAIL PROTECTED]rmformat -l Looking for devices... 1. Logical Node: /dev/rdsk/c4t0d0p0 Physical Node: /[EMAIL PROTECTED],0/pci1043,[EMAIL PROTECTED],1/[EMAIL PROTECTED]/[EMAIL PROTECTED],0 Connected Device: Maxtor OneTouch III 0303 Device Type: Removable Bus: USB Size: 476.9 GB Label: None Access permissions: Medium is not write protected. 2. Logical Node: /dev/rdsk/c0t0d0p0 Physical Node: /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED],0 Connected Device: HL-DT-ST DVDRAM GSA-4167B DL10 Device Type: CD Reader Bus: IDE Size: Unknown Label: Unknown Access permissions: Unknown Why only 500GB ? Well, I think this device has two modes of operating: RAID 0 and 1. By default it was set as RAID 0 and it was formatted as MacOS partition. I did change that from windows to RAID 1... I will try to swtich it back to RAID 0 and see what I get in Solaris. big thanks for pointers about scsa2usb.conf property. stefan 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] USB Video Cam
If you need help regarding as developing solaris drivers, please feel free to send email to [EMAIL PROTECTED] or [EMAIL PROTECTED], I am glad to help. Colin Kaiwai Gardiner wrote: Hi, Yeap, I'm current learning some C - hopefully porting the Linux driver for the Ricoh camera won't take too long - I've had a look through it, and it seems to be quite a compact/well written driver. Thank you for your email, Matthew On 25/06/07, *Colin Zou* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Kaiwai Gardiner wrote: I'm trying to get Ekiga working with my USB camera. According to dmesg: Jun 24 10:19:44 rachmaninov usba: [ID 912658 kern.info http://kern.info] USB 2.0 interface-association (usbia5ca,1810.config1.0) operating at hi speed (USB 2.x) on USB 2.0 root hub: [EMAIL PROTECTED], usbvc0 at bus address 3 Jun 24 10:19:44 rachmaninov genunix: [ID 936769 kern.info http://kern.info] usbvc0 is /[EMAIL PROTECTED],0/pci103c,[EMAIL PROTECTED],7/[EMAIL PROTECTED]/[EMAIL PROTECTED] I am unable to connect to the camera via ekiga - to which I wonder whether firmware is needed, of which this camera (a rebranded ricoh camera) has. If your webcam need firmware, then you have to develop a firmware download driver or tool first. I tested several logitech webcams before, they works well with usbvc(7D) driver and ekiga. More detail see my blog. http://blogs.sun.com/colin/entry/usb_webcams_and_video_conferencing - Colin ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] USB Video Cam
Kaiwai Gardiner wrote: I'm trying to get Ekiga working with my USB camera. According to dmesg: Jun 24 10:19:44 rachmaninov usba: [ID 912658 kern.info] USB 2.0 interface-association (usbia5ca,1810.config1.0) operating at hi speed (USB 2.x) on USB 2.0 root hub: [EMAIL PROTECTED], usbvc0 at bus address 3 Jun 24 10:19:44 rachmaninov genunix: [ID 936769 kern.info] usbvc0 is /[EMAIL PROTECTED],0/pci103c,[EMAIL PROTECTED],7/[EMAIL PROTECTED]/[EMAIL PROTECTED] I am unable to connect to the camera via ekiga - to which I wonder whether firmware is needed, of which this camera (a rebranded ricoh camera) has. If your webcam need firmware, then you have to develop a firmware download driver or tool first. I tested several logitech webcams before, they works well with usbvc(7D) driver and ekiga. More detail see my blog. http://blogs.sun.com/colin/entry/usb_webcams_and_video_conferencing - Colin ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] Re: [driver-discuss] Project Proposal: Fingerprint Authentication
+1 Gaopeng Chen - Sun China wrote: Fingerprint Authentication == Project Overview: - The biometrics technology grows fast. Fingerprint authentication is widely used in many situations. It's a valuable feature to support fingerprint in Solaris. This project is going to provide a complete and extendible solution to support fingerprint in Solaris. Project Description: Since the fingerprint devices have not standard class specifications and USB is the most popular I/O interface. We plan to support varied USB fingerprint readers by presenting a user-land driver framework(libfpr) based on libusb. A PAM module(pam_fpr) is presented to support dual-mode (user-passwd and fingerprint) authentication. The fingerprint management tool(fprmgmt) will be delivered, and gdm/login will be updated to support dual-mode login. The architecture is as the following, gdm/login xscreensaver ... fprmgmt == PAM services and tool | || | -- | PAM | pam_fpr == fingerprint auth/tok module | fpr_modules libfpr == userland fingerprint drivers | libusb 1) libfpr is a library of fingerprint reader drivers based on libusb. It provides a set of functions to let upper level applications operate the fingerprint devices. And it provides another set of interfaces for advanced users, who can developed a module for a customized fingerprint device. The module can be loaded and integrated as a part of libfpr. 2) pam_fpr is a pluggable module for PAM stack as well as an application based on libfpr. It implements pam_sm_authenticate() and pam_sm_chauthtok() to make it possible to enroll or identify with fingerprint. To support dual-mode (user-passwd and fingerprint) authentication, the architecture of pam_fpr is designed with multiple threads. Users can login by either user-passwd or fingerprint with dual-mode. 3) fprmgmt is tool to manage the fingerprint records. Users can register or un-register their fingerprint by it. A GUI will be wrapped to make it nice-looking and friendly to users. gdm is selected as the default login GUI. Project Target: --- 1) First step, this project focuses on the support of desktop systems. It stores and manages the fingerprint records in local system. 2) Second step, NIS, NIS+, LDAP and SunRay support will be considered. Communities of interest: --- Device Drivers Security Desktop ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Project Proposal: OpenSolaris Programming Contest in China Academic Developers
+1 joey wrote: Hi Folks, Attached please find the Project proposal for the OpenSolaris programming contest in China academic developers. Your comments and backing are appreciated! Thanks, OpenSolaris Programming Contest Proposal 1. Executive Summary This proposal is to organize the OpenSolaris Programming Contest within academic developers in China. The goal of the programming contest is to cultivate the OpenSolaris academic developers in China, as well as grow the OpenSolaris community. The contest will target at 20,000 Sun Studio active users as well as 20,000 OpenSolaris registration. As the side result, several Intern candidates will be selected out of the winners for the Campus Ambassador program. The proposal focuses on China academic developers now, but it can be easily expanded to academic developers across the world, or even commercial developers in the future. 2. Background With the OpenSolaris Curriculum Program, there are over 90 China universities integrated OpenSolaris into the Operating System Curricula. Since this January, OpenSolaris Registration Promotion has been launched on OpenTech website in China and it has attracted over 14,000 OpenSolaris developers to register and request for OpenSolaris Starter Kit. Moreover, the success of ACM/ICPC Xi'An Regional Contest on OpenSolaris has proven the viability of programming contest using OpenSolaris and Sun Studio. To make the development environment widely available for new developers, we have set up the cutting-edge server (unix-center.net) installed with Solaris and Sun Studio in China. In the past 6 weeks, over 10,000 people have login this server to try the development environment. 3. The Program To enable the contestants to innovate based on OpenSolaris, several factors are key to the success of the contest: a. Rules to keep the contest attractive, fair play and innovation-oriented b. Effective promotion to catch the right people in right way at right time c. Engineering support from the OpenSolaris community and Solaris team As the contestant, he/she will attend the contest with the below procedure: Register the projects = Attend the free training = Implement the project = Test the project = Submit the project From the organization point, the below steps are critical: (1) Prepare for the contest rules (awards; registration, implementation and submission rules), advertise plan, supporting infrastructure (project website and technical advisory board); (2) Hold university roadshow to widely spread the contest; (3) Offer free training on OpenSolaris programming to academic developers both on-campus and on-line; (4) Provide technical support for the contestant during the project implementation; (5) Evaluate the OpenSolaris contest to choose out winners. Once the winners come out, the Campus Ambassador recruiting team will interview the Intern candidates. 3.1 Contest Rules The contestants have to register and submit the work by the deadline. 3.1.1 Eligibility All university student, undergraduate and postgraduate, are eligible to the participate the OpenSolaris programming contest. The contestants will register the contest as a group: 1) Each group consists of at most 3 players; 2) The group needs to invite a professor to act as the mentor; 3) Each group will have to choose a project from our published project list or propose a new project from their research; 4) A lead is selected to register the project and submit the source code on line on behalf of the whole group. 3.1.2 Registration A successful registration includes: 1) Each group member has to register a user on opensolaris.org 2) Submit project proposal and group information on the project page 3) Request DVD on OpenTech to set up the environment 4) Register on Unix-center.net to try the development environment (OpenSolaris and Sun Studio) After the registration, the group will be granted with: 1) A notification e-mail to congratulate their successful registration; 2) Under the project page, there will be a repository to contain all the documents and source code for the project; 3.1.3 Implementation 1) All source codes, creative or derivative, should be compliant with the Common Development and Distribute License (CDDL); 2) The project should be compiled and tested with Sun Studio (Studio 11, Studio Express or Studio 12 EA); 3) To ensure the compatibility, all the project should run the sanity test on unix-center.net; 3.1.4 Submission 1) The submitted source code should be licensed under CDDL; 2) All submission should be done on the project page on-line; 3) The complete submission will include project source code tarball, demo, user guides, supporting tools, etc.; 4) The newer submission will replace the existing submission without the version check tool. After the submission, a notification e-mail will send to the lead. 3.1.5 Review
[osol-discuss] Project Proposal: Enhance the support of USB webcams
This project will deliver a set of userland libs and applications, and maybe some small patches to the existing USB webcam drivers. USB webcams are popular now, they are widely used in desktop/laptop systems. Some video applications, like video conferencing, can not work without these devices. At present, USB webcam drivers running in OS kernel support some basic webcam functions, like read video stream from the device, issue some video control commands to the device, decode video formats, etc. However, it is too difficult to develop/update kernel drivers to support all the fancy features from webcam vendors. Some new features (like face tracing, pan, etc.) are vendor specific, and people need implementing proprietary algorithms to support them. Therefore, it is not easy to support these features in kernel drivers, especially in class drivers. To further illustrate the problem, let's take USB video class spec (see usb.org) as an example. This class spec defines common video interfaces that a USB webcam may have, but these interfaces can not cover the new features mentioned above. From the hardware view, the spec does allow webcam vendors to extend their own fancy features by implementing some extra functions in the device. From the software view, although webcam vendors can write their own device drivers to support the fancy features, it is really a tough task to re-write a kernel driver. A much better choice is, keeping the kernel driver untouched or making only slight modifications to the kernel driver, instead, we implement the vendor specific features in userland libs and applications. The first stage of this project will focus on supporting some Logitech webcams. Because they are popular in the market and there are several models of them are compliant to USB video class spec. There is a usb video class driver available for these class compliant webcams, so some basic video features are already supported by the driver. It is feasible to enhance the support of the webcams complaint to USB video class spec first. Communities this project is related to: Device Drivers, Desktop, Laptop. Colin Zou ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Hardware Compatilibility
I guess this PCI serial controller is not supported. Is it OK for you to use usb-to-serial adapters instead of PCI serial controllers? Solaris support three kinds of usb-to-serial adapters. See http://www.sun.com/io_technologies/USB-Faq.html Colin Matthew Smith wrote: Hi I would like to migrate my little server (Athlon XP2000, 1Gb RAM), which is currently running Gentoo Linux, to Solaris so that I can benefit from ZFS. There don't appear to be any applications that I can not a) live without or b) recompile. My only sticking point is hardware - I have a Stallion PCI serial controller (the type with the external plug box, expandable to 64 ports); this I can't live without. Google hasn't turned up anything useful searching on Stallion and Solaris (apart from a person of that name) and I know for a fact that Stallion doesn't provide Solaris drivers, because I asked them and they were very rude about it. However, I believe the Linux driver (part of the standard kernel distribution) is third-party and was wondering whether such a thing also existed for Solaris. Cheers M 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] ADSL modem support
Second. Albert Qu wrote: This project will deliver some modules and a config tool to support ADSL modem on opensolaris, include ethernet and usb interface. Asymmetric Digital Subscriber Line (ADSL), please refer to http://en.wikipedia.org/wiki/ADSL, is a form of DSL, a data communication technology that enables faster data transmission over copper telephone lines than a conventional modem can provide. ADSL can transmit up to 6 Mbps to a subscriber, and as much as 832 kbps or more in both directions. ADSL has transformed the existing public information network from one limited to voice, text and low resolution graphics to a powerful, ubiquitous system. ADSL is available in various speeds and pricing throughout the United States, Canada, Europe and Asia. There are emerging markets in the Caribbean and through out Latin America. China had hit its 42 millionth customer in 2005. ADSL is connecting our homes with the whole world. Now solaris just supports ADSL with ethernet interface, and we must extend sppptun to support USB ADSL modem. It involves some atm protocols and RFCs. It is our another target to develop an easy dialing tools for customers. Customers often complain that it is very difficult to set up an ADSL modem in solaris. This projects will develop a config tool to support popular dialing, such as modem, ADSL, mobile phones etc. Communities this project is related to: Drivers, Desktop, Laptop. This project would have a mailing list, adsl at opensolaris dot org. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] EVDO anyone?
William Pool wrote: I was curious if there is any EVDO support or a group working on it? You mean EVDO card support? -William 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] USB oddity with build48
Have you tried builds earlier than 48 on the same machine? Beside mouse, have you tried other usb devices? please run the following commands and send me the output file - uname -a - cat /etc/motd - cat /etc/driver_aliases - dmesg - prtconf -D - prtconf -v - login command line console, run the following command with the mouse attached and get the output # echo ::usba_debug_buf | mdb -k Ian Collins wrote: I've noticed that the dtlogin will fail to start on my laptop (a Dell M60) if my mouse is plugged into a particular USB port. I have to power off, move the mouse and restart. I see the following warnings in messages: Oct 19 20:43:52 laptop usba: [ID 912658 kern.info] USB 1.10 device (usb9da,6) operating at low speed (USB 1.x) on USB 1.10 root hub: [EMAIL PROTECTED], hid0 at bus address 2 Oct 19 20:43:52 laptop usba: [ID 349649 kern.info] A4Tech USB Optical Mouse Oct 19 20:44:02 laptop usba: [ID 691482 kern.warning] WARNING: /[EMAIL PROTECTED],0/pci1028,[EMAIL PROTECTED],7 (ehci0): No SOF interrupts have been received, this USB EHCI hostcontroller is unusable If anyone is interested, I can investigate further. Ian ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [Fwd: [osol-discuss] Keyspan Drivers and Firmware in B45]
I found some interesing drivers in B45. SUNWuksp USB Keyspan serial driver SUNWukspfw USA49WLC firmware for USB Keyspan serial The reason why I find them interesting is that I've been looking for a way to use my old Type 5 keyboards on my PC. One of the methods mentioned uses a modified Keyspan serial to USB converter. The converter is modified to convert the TTL signals from the keyboard to RS-232 levels and add a 8 pin mini-DIN connector. Would these drivers allow me to use this device? http://keyspan.com/products/usb/usa19hs/homepage.spml this device can surely work with SUNWuksp driver, see manpage usbsksp(7D). Another supported device is Keyspan USA49WLC. I'd also heard rumors years ago about being able to use a Type 5 on a Macintosh, but I've been unable to verify this. If this is true there's another Keyspan converter that may work unmodified. http://www.keyspan.com/products/usb/usa28x/homepage.spml this device is not supported (at least no one tested) by the driver. Can anyone verify that these drivers would work with these devices? Thanks, John Weekley ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Re: Project Proposal: Wireless USB Support
[EMAIL PROTECTED] wrote: Wireless USB finally coming out of the labs http://eetimes.com/news/latest/showArticle.jhtml?articleID=189600587pgno=1 Interesting, but I thought one of the reasons to have cables was power? Yes. My idea is, Wireless USB is not a good choice for devices need be powered by usb cables, like a usb stick or a usb hard disk. In the mean while, there are also a lot of usb devices always need a dedicated power cable (like a printer, scanner), and a lot of other usb devices always need a built in battery (like a digital camera, PDA, cell phone, and some other hand held devices). And, if look at the current wireless keyboard/mouse solution, there are always a built in battery in them. In short, for a small part of usb devices, usb cable is a good power source; and for a lot of others, usb cables will be abandoned when WUSB becomes popular. My idea about the future PC boxes is, USB2.0 ports and WUSB host controllers will co-exist. WUSB devices and USB devices with cables will co-exist. (Why is Wireless USB needed when you have bluetooth? My current idea is, WUSB is expected to be cheap and it's easy to compliant or co-exist with the current usb solution. Major hardware vendors are promoting this technology actively, it is expected that new PC boxes will be shipped with integrated WUSB host controller. Will we have all the bluetooth implementation security issues all over again?) Need more investigation on this. There is a security section in WUSB spec. Casper ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Project Proposal: Wireless USB Support
Darren J Moffat wrote: Colin Zou wrote: This project will deliver a framework (including a security sub-framework), some device drivers and a config tool to support wireless USB on opensolaris. Please ensure that [EMAIL PROTECTED] is aware of the security requirements before you complete your design and also give us the chance to review the design before you commit to it. Sure, thanks for reminding. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] Project Proposal: Virtual Console
Seconded. This project will definitely benefit solaris users. Riny Qian wrote: The Virtual Console project would provide multiple consoles and switch between Xserver and consoles for Solaris. There are two areas of work envisioned: 1. Multiple consoles 2. Switch between Xserver and consoles This project is affiliated with the Device Driver community, and would have its own mailing list, [EMAIL PROTECTED] Initial leaders: Lingbo Tang Riny Qian ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
