Changing Creator3D depth settings in Solaris
Hi, Forgive the off-topic nature of this request, but I've been trying to fairly compare Debian and Solaris 8 on my Ultra 30. The computer has a Creator3D in it. I was able to set the bit depth to 24 bits in Debian without too much trouble, but I have no idea how to change my depth from 8 bits to 24 bits in Solaris. Any suggestions? I ran a program called xdpyinfo, and it reported that the display was currently in the following: default visual id: 0x20 visual: visual id:0x20 class:PseudoColor depth:8 planes available colormap entries:256 red, green, blue masks:0x0, 0x0, 0x0 significant bits in color specification:8 bits while I believe I would like to be in the following: visual id:0x28 class:TrueColor depth:24 planes available colormap entries:256 per subfield red, green, blue masks:0xff, 0xff00, 0xff significant bits in color specification:8 bits - Sageev George 3641 Watt Way HNB/Room 403, UPC MC 2520 Los Angeles, CA 90089 213-740-9359 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Changing Creator3D depth settings in Solaris
Thanks for the answers, Jon and Ben: I think Jon might be right (with his long answer), because I do remember running a program on a remote computer that really looked like it was running with 24bpp, even though my local applications looked horrible. I'm seeing the wacky behavior when I run Outlook Express (for Solaris) and Gnome/Sawfish. Both look like they have an 8 bit colormap. I'll try playing with my .Xdefaults or .Xresources file .. the -defdepth and the -bpp tricks didn't work with xinit. -Sageev - Original Message - From: Jon Leonard [EMAIL PROTECTED] To: Sageev George [EMAIL PROTECTED]; debian-sparc@lists.debian.org Cc: Jon Leonard [EMAIL PROTECTED] Sent: Friday, July 26, 2002 4:21 PM Subject: Re: Changing Creator3D depth settings in Solaris On Fri, Jul 26, 2002 at 03:51:14PM -0700, Sageev George wrote: Hi, Forgive the off-topic nature of this request, but I've been trying to fairly compare Debian and Solaris 8 on my Ultra 30. The computer has a Creator3D in it. I was able to set the bit depth to 24 bits in Debian without too much trouble, but I have no idea how to change my depth from 8 bits to 24 bits in Solaris. Short answer: -defdepth 24 (Or something similar; it's been years and it'd be in the X server man page) The longer answer is that the Creator3D card and its relatives support multiple bit depths simultaneously, on a per-window basis. It's selected in the WindowID planes. A program that's aware of this can select the visual it wants, so you can run 24 bit programs even in the nominally 8-bit mode, and it works fine. The only difference is in the order that the server presents the list of available visuals, so naive programs just take the first one in the list. The decision to make the default 8 bit was made because there was still at the time a wide variety of common programs that just assumed 8-bit displays, and misbehaved badly otherwise... Jon Leonard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Comparing X performance on Debian and Solaris
I've been noticing that my Solaris installation on my Ultra 30 (with Creator 3D) seems more accelerated than the Debian installation when comparing a couple things in X. For instance, Netscape is very jumpy during scrolling in Debian, but smooth in Solaris, and if I drag windows around the workspace, in Debian the windows lag behind significantly, while in Solaris the lag is a lot smaller (but still there). I have read that there is proprietary microcode that enables the accelerated functions on an Elite 3D. Is there something similar missing from the XFree86 4.0 driver for the Creator 3D? I had tried recompiling the kernel in Debian, but I didn't create any kernels that were able to speed the graphics to the level that they are on the Solaris installation. Does anyone have any thoughts on what I might be doing wrong in my Debian installation? Or, is this the behavior to expect from Debian Woody 2.4 kernels? -Sageev - Sageev George 3641 Watt Way HNB/Room 403, UPC MC 2520 Los Angeles, CA 90089 213-740-9359 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Printing Problems on Ultra 30 - Solved!
Andrew: Your suggestion was good. Upon doing a search for the error message that I was getting (DMA write timed out) I found that a discussion in the linux-parport mailing list to be helpful. I am guessing here, but I think that the default way of accessing the parallel port, in the original kernel installed during my Woody upgrade, is interrupt-driven, protocol in hardware using DMA. So, my error message may be indicating that there is an unsuccessful attemp to use DMA to write to the hardware FIFO. Given this, I went into the options for recompiling a kernel and disabled Use FIFO/DMA if available. I am guessing that my printing will be slower now. The file, parport.txt, in kernel-source-2.4.18/Documentation, was also useful. -Sageev - Original Message - From: Andrew Sharp [EMAIL PROTECTED] To: debian-sparc@lists.debian.org Sent: Monday, June 17, 2002 8:07 PM Subject: Re: Printing Problems on Ultra 30 Andrew Sharp wrote: Sageev George wrote: While I've had some progress with trying to make my Ultra 30 print, I've had no real success. What I have done so far is adding the modules, parport_pc and lp. I have also did MAKEDEV par, MAKEDEV parport, and MAKEDEV lp. During the installation of the parport_pc module, I get the following messages: parport0: PC-style at 0x1fff13043bc (0x1fff13047bc), irq 7039808, dma 0 [PCSPP,T RISTATE,COMPAT,ECP,DMA] parport0: Printer, EPSON Stylus COLOR 800 During lp installation (I think), I get the following: lp0: using parport0 (interrupt-driven). When I try running the following (cat textfile.txt /dev/lp0), I get the following: lp0: compatibility mode DMA write timed out The last message repeats until I hit CTRL-C. I installed printtool, but it is not able to autodetect any printers, and it even question if I have added the parport module (which I have by this point). If it makes you feel any better, it has quit working on my PC hardware as well in the last couple of kernels. Don't know the details, because on that PC I also have windows, and printing still works with windows, so I'm just using windows when I need to print. This may not seem of much use, but it suggests that the problem is known to others and possibly there is a patch out there or the problem is due to be fixed soon. Or maybe someone knows a workaround. Fire up your search engine. Oh yeah, the experience is exactly the same, except I don't get the DMA write timed out message. a -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Printing problems still
I've had some progress with making my Ultra 30 print, but no real success. What I have done so far is adding the modules, parport_pc and lp. I have also did MAKEDEV par, MAKEDEV parport, and MAKEDEV lp. During the installation of the parport_pc module, I get the following messages: parport0: PC-style at 0x1fff13043bc (0x1fff13047bc), irq 7039808, dma 0 [PCSPP,T RISTATE,COMPAT,ECP,DMA] parport0: Printer, EPSON Stylus COLOR 800 During lp installation (I think), I get the following: lp0: using parport0 (interrupt-driven). When I try running the following (cat textfile.txt /dev/lp0), I get the following: lp0: compatibility mode DMA write timed out The last message repeats until I hit CTRL-C. I installed printtool, but it is not able to autodetect any printers, and it even question if I have added the parport module (which I have by this point). Any suggestions? -Sageev - Original Message - From: Sageev George [EMAIL PROTECTED] To: debian-sparc@lists.debian.org Sent: Sunday, June 16, 2002 8:48 PM Subject: Printing on Ultra 30 Hi: I've searched thru the archives for help on this, but I am still confused. I'm rather new to running Debian on an UltraSparc, so forgive my confusion. I'm currently running Woody using the 2.4.18 kernel. I wanted to use the system as a print server for my lab, but I am unable to make it print to a printer attached the parallel port. My questions are: Is printing supported in Woody? If so what steps do I need to take to make it work? My search thru the list archives make me think that I will have to recompile the kernel with some options set. Also, I will have to run MAKEDEV to create certain devices, and add some modules to modules.conf. When I tried modprobe, I found that bpp and parport_ax are not found. parport_pc, parport, and lp were found, though. Any help will be appreciated. -Sageev -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Printing Problems on Ultra 30
While I've had some progress with trying to make my Ultra 30 print, I've had no real success. What I have done so far is adding the modules, parport_pc and lp. I have also did MAKEDEV par, MAKEDEV parport, and MAKEDEV lp. During the installation of the parport_pc module, I get the following messages: parport0: PC-style at 0x1fff13043bc (0x1fff13047bc), irq 7039808, dma 0 [PCSPP,T RISTATE,COMPAT,ECP,DMA] parport0: Printer, EPSON Stylus COLOR 800 During lp installation (I think), I get the following: lp0: using parport0 (interrupt-driven). When I try running the following (cat textfile.txt /dev/lp0), I get the following: lp0: compatibility mode DMA write timed out The last message repeats until I hit CTRL-C. I installed printtool, but it is not able to autodetect any printers, and it even question if I have added the parport module (which I have by this point). Any suggestions? -Sageev - Sageev George 3641 Watt Way HNB/Room 403, UPC MC 2520 Los Angeles, CA 90089 213-740-9359 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
