Re: Turtle Beach Montego
I'd love for someone to prove otherwise, but as far as I know there is still no driver available for any Vortex or Vortex2 card, which of course includes the Turtle Beach Montego. SJG On Sun, 14 Mar 1999, Jesse Lee wrote: I have a turtle beach montego sound card. Can it work under linux? If so what driver do i use? I have a dual boot macine and by the time you read this Hope fully I will have kernel 2.2.3 installed(hopefully reiterated)!! any info is greatly appreciated (newbie here:) Jesse Lee (aka Dade)
Re: Kernel Compile Attemp #2
On Mon, 8 Mar 1999, Doug Dine wrote: Well, in my second attempt now to compile my kernel for sound support here is the error message after make config. make [1]: as86: Command not found make[1]: *** [bootsect.o] Error 127 make[1]: Leaving directory /usr/src/kernel-source-2.0.34/arch/i386/boot make: *** [zImage] Error 2 I believe this indicates you don't have the bin86 package installed. SJG
apt forgets to install?
I use the apt method in dselect. I have no trouble selecting and downloading the various packages, but upon completion they just remain there! a 'dpkg --pending --configure' fails to install anything. I went through and did an apt-get install on each package individually and had no problem (that I can see), but I wouldn't mind having apt/dpkg do the job for me! Thanks. SJG
Re: New Install
I expect all to go smoothly except possibly my 56K Winmodem and my Turtle Beach Montego Audio Card. Can anyone give me any information that may help me in that area? You won't have any luck with the Montego any time soon :( Though if you ever happen to find out otherwise let me know!! Even SB compatability mode would be fine. SJG
Re: kernel 2.2.0
Others can/will correct me, but I'll try to help... Can someone tell me what is the different between the developement version from the stable version of a kernel? Dev kernels are works in progress, and have a tendancy to be very unstable and can occasionally do nasty things. The stable version is of course, stable, and is one that is no longer in development and has been more rigrously tested. Is kernel 2.2.0 stable or dev? 2.2.0 is part of the stable line. 2.2.1, 2.2.2, 2.2.3, etc will be minor bug fixes, but still considered 'stable'. I believe 2.2, 2.4, 2.6, etc will all be 'stable', while odd numbered versions (2.1, 2.3, 2.5...) will be development versions. What is the different between 2.2.0.tar.bz2 and 2.2.0.tar.gz? They are compressed with different programs (bzip and gzip). Most machines will have gzip, fewer machines have bzip. What does it mean when there is and question mark (?) in front of the file instead of the other symbol? Beats me :) I'm sure dselect explains it. How come all I hear about is kernel 2.0.36 and kernel 2.2.0, what the following version in between, are they not working linux-2.0.4.tar.gz 08-Jul-1996 00:00 5.7M . to linux-2.0.9.tar.gz 26-Jul-1996 00:00 5.7M As you can see by the dates and version numbers, these are very old. 2.0.36 2.0.4. linux-2.1.0.tar.bz230-Sep-96 14:23 4.7M . to linux-2.1.99.tar.gz01-May-98 00:21 10.7M These are development kernels (evident by the odd numbers, 2.1). You generally don't want to use these unless you have a specific need. Hope that helps and is at least somewhat accurate. SJG
Re: CD Burning
I am very new Linux user. I have taken the time to download the raw files from the debian-cd mirror site closest to me. I wanted to master my own CD that way. I unfortuneatly only have a DOS/Windows95 machine to work with. Does anyone know of a dos or windows cd-writer that will accept raw formatted files. I have Adaptec CD Creator for win95 and it doesn't like them. Any thoughts would be very helpful. I am looking forward to getting my feet wet with Linux. I believe the CD page said you could rename the .raw file to .iso to make it recognized by Windows programs... SJG
Re: GDB problems
Breakpoint 1 at 0xbab4: file program.c, line 4. (gdb) r Starting program: /home/IA/baptista/./program Breakpoint 1 at 0x81f6c80: file program.c, line 4. Cannot insert breakpoint 1: Cannot access memory at address 0x81f6c80. Regards,Paulo Henrique I started getting this error as well right after upgrading a number of packages to potato from slink. Glad to know it isn't me losing my mind, but a solution would be wonderful. I have yet to find one :( SJG
GNOME dependencies
I tried (via dselect) to choose all the latest GNOME packages, but when it would go to the dependency screen and number of required libraries would come up 'not available'. Is there any additional source I need apt to look at for these libraries? Or should I simply not try installing GNOME 0.99.x and drop back to 0.30.x? Thanks. SJG
XEmacs beta builds
Does anyone maintain .deb files of the recent XEmacs betas? I know someone does this for the Enlightenment CVS snapshots, so I figured a similar thing for XEmacs might exist. Thanks. SJG
GCC/e2fsck probs resolved
Thanks to all who replied. I did a e2fsck on the drive, then reinstalled the GCC package and have had no problem since. Life is good :) SJG
Montego sound setup
Can anyone point me to a doc that explains how to get sound support from a Turtle Beach Montego A3dXstream soundcard? I'm assuming a dedicated driver has yet to make it into the kernel, but I'm hoping I can get _some_ sound from it...Thanks. SJG
GCC Compile problems relating to DMA
I recently installed slink, with gcc v2.7.2.3. Any attempts to do any compiling with gcc fail with a series of hard drive errors which seem to releate to some sort of DMA error (ie., hdb: dma_intr ). I apologize for not having the whole error here. I have two Western Digital IDE drives installed, one a newer 6.4gig UDMA drive, and an older 1.6gig DMA drive. slink is installed on the smaller 1.6 drive (/dev/hdb3). The drives are detected correctly in the bootup message and I have seen no other errors thus far... but I'm unfortunately in great need of gcc locally at the moment! Any pointers/tips/fixes would be GREATLY appreciated ASAP. Scott J. Geertgens
Re: GCC Compile problems relating to DMA
Thanks for the reply. I booted off of the rescue disk (I only have one partition, so I couldn't have it mounted while I tried to fsck it). Running fsck simply came back with device clean... do I need to send any flags? Someone also suggested that I disable DMA on the drive via hdparm -d 0 /dev/hdb. I tried this, but that simply changes the error from dma_intr to read_intr, which I believe seems to correlate that something is in fact wrong with a sector on the disk. SJG This happened to me, and I switched to single-user mode (init 1), and ran fsck.ext2 /dev/harddrivedevice. After that, reinstall the gcc packages. This should mark the sectors bad so the kernel won't write files to them. Any one else with more experience care to comment? -- Stephen Pitts [EMAIL PROTECTED] webmaster - http://www.mschess.org
Re: irc.debian.org - No DNS
Took me a while to find it, but the (main) #debian channel is now on irc.linpeople.org. SJG On Fri, 15 Jan 1999, Chris Hoover wrote: It appears that the dns for irc.debian.org is fscked up. When I try to ping it, I get unknown host. Does anyone know of another irc server I can use to get on the #debian channel? -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Repairing a HD with fsck?
I recently posted a message about GCC not being able to compile due to dma_intr and/or read_intr errors. After receiving a response here and scouring the net I've realized that the problem lies on the drive itself (bad blocks or similar). My question is how do I go about fixing the problem? Will a forced fsck (fsck.ext2 -f /dev/hdb3) be sufficient? I know that when Debian installs, it gives the option to scan for and mark bad sections of the disk... will I need to reinstall to insure that no files are sitting on corrupt sections of the disk? (Re-installing is an option for me). Or is there anyway to 'recover' the data from those bad block and fix everything without going to such extemes? Thanks. Scott J. Geertgens
Re: Q's about upgrading to hamm
On Fri, 5 Dec 1997, Christopher Jason Morrone wrote: Ok, I'd like to upgrade to hamm, because there are some things there that I need. I'm following the libc5 to libc6 howto, but I've got a couple questions/comments. The first conflict arose when I tried to install the second package, libc6_2.0.5c-0.1 . It conflicted with the pthreads package. No biggy, I just got rid of the threads. Then I tried again and got this: Selecting previously deselected package libc6. dpkg: regarding libc6_2.0.5c-0.1.deb containing libc6: libc5 conflicts with libc6 libc6 (version 2.0.5c-0.1) is to be installed. dpkg: error processing libc6_2.0.5c-0.1.deb (--install): conflicting packages - not installing libc6 Errors were encountered while processing: libc6_2.0.5c-0.1.deb Can I just force it? Will that cause problems later? I recently did this upgrade myself and ran into the same conflict. I went ahead and forced it, and there didn't seem to be any adverse effects in doing so. I did notice there was a newer version of libc5 in the hamm directories, which made some reference of being better behaved in a libc6 environment so it _may_ be possible to upgrade to that new libc5 package first and then put libc6 on. Doing so doesn't seem to be a necessity, however, since my machine seemed to do fine just by forcing. SJG -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: XF86Config question
Hello, all, Anyway, when running X, I'm troubled by streaks (don't know how else to describe them) at higher resolutions, which I suspect are related to the dot clocks I've chosen. Namely, the higher the clock, the more pronounced the streaking. This streaking only occurs when the mouse is near or traverses a window border. Thus, if I move the mouse on a blank background (either on the desktop or fully within a window, I do not see any streaking). Video Chipset: Trident TGUI9680-1. Programmable clocks. In /usr/doc/X11, there may be a README.trident or similar that can give you some ideas. We have a PC here at the office with a Cirrus Logic video card that sufferes the same problems, and yes, it has something to do with a high dot clock setting. For the SVGA server (which I assume you are using?) there were options like fifo_conservative and no_bitblt, etc., that were supposed to help. Hopefully similar options would be available to you? Okay...there is a README.trident file. The options you may want to experiment with are fast_dram or slow_dram and maybe tgui_pci_read_off and tgui_pci_write_off. The file is in the above path I mentioned. Hopefully that will lead you to a solution... SJG -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: 1.2 Upgrade Experience
My suggestion to the debian team would be to add a feature to dselect that would flag certain packages as 'on hold', install as much as possible, then go back and try to install the failed packages again. The dependencies are all correct, but order of installing makes a difference as well. I vaguely assumed that pre-depends was a mechanism to handle this situation. Is that not so? If it is, then are all those packages missing the pre-depends flag? ...RickM... Hmmm...that's true. I kinda assumed the same thing. Maybe it is just a broken feature right now? I'm not sure why the pre-depends aren't working right... SJG -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
XWD printing
In order to get the correct colormap on my remote X11 windows, I have to run in 16bpp in Linux. I need to print these Xwindows to a printer (in postscript format). The general method for doing this is to use xwd or xwpick to dump the screen to a file. However, I have been unable to find a utility that will do this in 16bpp mode! Does one exist? I have tried xwpick and xwd-xwd2ps. Thanks! SJG -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Remote X11 Windows
I realize this isn't a Debian-specific problem, but I was hoping for some help anyway :) I use my Linux machine(s) here at the office to accept remote displays from the Solaris machines where our big graphing programs are installed (namely PV-Wave and NCAR Graphics if that helps). I encounter two problems: 1. If I run in 16-bit mode on the Linux machine, the remote Xwindow that opens on my display will have the wrong colormap. This can be fixed by running Linux in 8-bit mode but why should I have to do that? Is there any way around this? This problems applies mainly with the use of PV-Wave. 2. Other programs (NCAR Graphics and its related radar RDSS utilities to name a few, as well as in-house software) refuse to send the correct colormap even in 8-bit mode. I'm really hoping there is a variable I can set, or an alternate method of starting X to solve these problems. Thanks for any ideas anyone has. Pointers to the correct documentation is certainly welcome. I've looked, but obviously in the wrong areas. SJG -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: 1.2 Upgrade Experience
While upgrading, a number of packages (about 10 of the over 100) failed to install. The result of this was that after the first round of attempted installations of the new/updated packages, the ftp access method for dselect no longer worked. This was very disconcerting! -gavin... When I first installed Debian, this really spooked me as well. I managed to watch the messages as they flew by, and was able to note that all of the packages that failed depended on perl being installed. The way the files were selected though, perl is one of the later things to be installed, so everything installed before it that depends on it will fail. How's that for a sentence? Anyway, I found that by simply doing a 'dpkg -i perl' and then a 'dpkg -i dpkg...', everything worked once again and all other failed packages could then be installed and set up by dselect. My suggestion to the debian team would be to add a feature to dselect that would flag certain packages as 'on hold', install as much as possible, then go back and try to install the failed packages again. The dependencies are all correct, but order of installing makes a difference as well. SJG -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: NFS trouble
I keep getting the following message when trying to NFS mount any of the exported filesystems. mount clntupd_create: RPC: Program not registered Check that on the nfs server that mountd is running. This one is usually NOT started from inetd but instead is started from one of the rc files I realize this is most likely the correct answer, but I will add another solution just for the sake of completeness. At one point I _did_ have all the correct daemons running (nfsd, mountd), and still came up with this error. It turned out that I had fiddled around with /etc/hosts.allow and /etc/hosts.deny too much and shut off nearly everything. This generates the same error as not having mountd running. Wonderfully descriptive :) SJG
