Problem with latest Realplayer
After upgrading to the latest Realplayer (via realplayer_7.0.2.1_i386.deb), I am now told "Cannot open the audio device. Another application may be using it." on startup. The audio device is _not_ busy, and other programs can make use of the soundcard. Realplayer fine before the upgrade. I haven't seen anyone else mentioning this as a problem, so I am at a bit of a loss as to its cause. Any ideas? I'm using a GUS Extreme and the (commercial) OSS drivers. -- Stig Are M. Botterli | Some men see things as they are and ask why. [EMAIL PROTECTED] | Others dream things that never were and ask why not. -- George Bernard Shaw
Re: Problem with latest Realplayer
On Mon, May 29, 2000 at 07:21:48PM +0100, Phillip Deackes wrote: >"Stig Are M. Botterli" <[EMAIL PROTECTED]> wrote: >> After upgrading to the latest Realplayer (via >> realplayer_7.0.2.1_i386.deb), >> I am now told "Cannot open the audio device. Another application may >> be >> using it." on startup. The audio device is _not_ busy, and other >> programs >> can make use of the soundcard. Realplayer fine before the upgrade. I >> haven't seen anyone else mentioning this as a problem, so I am at a >> bit of a >> loss as to its cause. Any ideas? >> I'm using a GUS Extreme and the (commercial) OSS drivers. > >Interesting. I tried using xmms (to play an mp3) and got the same >message. I had only the other day downloaded the new RealPlayer which >worked immediately. I had to go into xmms preferences and change *from* >the OSS to the eSound Plugin before it would work. > >I have just tried RealPlayer and needed to enable 'Native Sound Drivers' >to get this to work. Now both xmms and RealPlayer work fine. xmms works fine. However, I've found one peculiar way of playing. If I go to preferences and choose "Esound support", go out and try to play -> "Cannot open..." message, go back to preferences and then choose "Enable support for old OSS drivers", I am given _one_ shot at playing something. I have to keep repeating this procedure for every single item I want to play. Does this give anyone a clue as to what might be wrong? -- Stig Are M. Botterli | Some men see things as they are and ask why. [EMAIL PROTECTED] | Others dream things that never were and ask why not. -- George Bernard Shaw
Re: Problem with latest Realplayer
On Mon, May 29, 2000 at 05:13:04PM -0500, Brad wrote:
>On Mon, May 29, 2000 at 09:19:27PM +0200, Stig Are M. Botterli wrote:
>>
>> xmms works fine. However, I've found one peculiar way of playing. If I go
>> to preferences and choose "Esound support", go out and try to play ->
>> "Cannot open..." message, go back to preferences and then choose "Enable
>> support for old OSS drivers", I am given _one_ shot at playing something. I
>> have to keep repeating this procedure for every single item I want to play.
>> Does this give anyone a clue as to what might be wrong?
>
>Is esd running, or set to autostart when needed?
After installing EsounD and starting esd, playback works perfectly with the
"Enable support for old OSS drivers"-option, erratically with the "Use
native sound drivers"-option, and not at all ("Cannot open the audio
device..") with the "Esound Support"-option. Problem solved, I guess.
--
Stig Are M. Botterli | Some men see things as they are and ask why.
[EMAIL PROTECTED] | Others dream things that never were and ask why not.
-- George Bernard Shaw
Re: X Windows scripts
On Thu, 27 Mar 1997 01:18:31 -0800 (PST), Brian Fraser <[EMAIL PROTECTED]> wrote: >What I am really looking for is a copy of working scripts that do (or >close to) this type of setup, so that I can see what I am doing right (if >I am at all) and what I am doing write. Take a look at http://www.PLiG.org/xwinman/ >Brian Stig Are M. Botterli |"Always let people think you're dumber then [EMAIL PROTECTED]| you really are, they'll underestimate you. | Then you can obliterate them." -Greg Graffin
RE: ET6000
On 11-May-97 Lawrence Chim wrote: >Anyone using ET6000? >I am going to sell my diamond stealth and buy a ET6000 >based card, e.g. Jaton 128. >I just want to be sure that X run fine :) Runs fine here. You should get the XF86_SVGA server from the 3.2A distribution featuring greatly enhanced ET6000 support. You don't need anything else from the 3.2A distribution. Atleast I didn't. >Lawrence, Stig Are M. Botterli | "Always let people think you're dumber than [EMAIL PROTECTED]| you really are, they'll underestimate you. | Then you can obliterate them." -Greg Graffin -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Debian for PPC Macs
On 16-Jul-97 Rick Hawkins wrote: > >> For those of you interested in CHRP PPC machine, take a look at >> www.pios.de. Seems like a very flexible system, and it will be shipping >> with Linux and BeOS. I know what my next computer will be. > >They certainly look interesting, at least eventually. But at the moment >it seems to be an almost finsihed machine running an almost finished >port of linux which is only avaialble in a developers version for >several hundred dollars more than comparable x86 systems. Oh, well. >Next time . . . As the only proprietary part is the motherboard, which includes sound/midi, while the rest is made up of industry standard components, I very much doubt your estimate. Esp. as they haven't announced a price yet. You are probably confusing it with the Keenya, which is a Mac clone based on Motorola's Tanzania board. The reason I am considering this system is that I am also very attracted to the BeOS and the fact that it will most probably run a CHRP version of Rhapsody. For a Linux-only system it makes sense to stick to x86, esp. considering the competition Intel is seeing from Cyrix and AMD. Stig Are M. Botterli | "Always let people think you're dumber than [EMAIL PROTECTED]| you really are, they'll underestimate you. | Then you can obliterate them." -Greg Graffin -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Debian for PPC Macs
On 16-Jul-97 Rick Hawkins wrote: >> As the only proprietary part is the motherboard, which includes sound/midi, >> while the rest is made up of industry standard components, I very much doubt >> your estimate. Esp. as they haven't announced a price yet. You are probably >> confusing it with the Keenya, which is a Mac clone based on Motorola's >> Tanzania board. > >is it an at or atx format board then? I don't recall seeing anything to >that effect (but would be very happy if it were atx). ATX. You will find the technical spcifications following the transAM/Maxxtrem links. >rick Stig Are M. Botterli | "Always let people think you're dumber than [EMAIL PROTECTED]| you really are, they'll underestimate you. | Then you can obliterate them." -Greg Graffin -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
What soundcard?
Any hot tips regarding what soundcard I ought to get for my Linux box? Preferably one which is well supported, won't bother my CPU all that much, and of course sounds good. I am currently considering the Ensoniq Soundscape Elite or the Soundscape VIVO 90. The 'supported' part isn't really all that important, as most cards seem to be supported by the commercial, but fairly inexpensive, OSS/Linux. Stig Are M. Botterli | "Always let people think you're dumber than [EMAIL PROTECTED]| you really are, they'll underestimate you. | Then you can obliterate them." -Greg Graffin -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: ESS vs SB16 sound cards?
>By "ESS" I'm assuming you mean Ensoniq SoundScape. ESS and Ensoniq are two different companies. Regarding ESS, the ESS 688 and ESS1688 sucks. However, I am told that the ESS 1888 (?) is supposed to be ok. >Some of the mixer controls on the card are different from SB. That makes >it a bit challenging to use under Linux. For example, the MIDI mixer >interface is propritary. Last time I checked, unless you buy the >commercial version of the Linux sound driver, you can't mix MIDI. I assume you have the Vivo 90 card. I believe the other Soundscape cards are fully supported in OSS lite. Not sure though. Stig Are M. Botterli | "Always let people think you're dumber than [EMAIL PROTECTED] | you really are, they'll underestimate you. | Then you can obliterate them." -Greg Graffin -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Will my fonts every look good?
In article <[EMAIL PROTECTED]>, Bill Moseley wrote: > > $ dpkg -l | grep font > > ii gsfonts-x110.16 Make Ghostscript fonts available to X11. This package is a real uglificator. Replace it with a dummy equiv. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Will my fonts ever look good?
In article <[EMAIL PROTECTED]>, Bill Moseley wrote: > On Sat, 4 Jan 2003, Stig Are M. Botterli wrote: > >> In article <[EMAIL PROTECTED]>, Bill Moseley >wrote: >> > >> > $ dpkg -l | grep font >> > >> > ii gsfonts-x110.16 Make Ghostscript fonts available to X11. >> >> This package is a real uglificator. Replace it with a dummy equiv. > > I removed it with no real difference Depends on what fonts you use. Atleast on my machine, the not-so-pretty fonts provided by this package took precedence over some of my tt-fonts. I wasn't able to solve it short of removing it. >, but I didn't replace it > with anything. What package should I replace it with? Install the 'equivs' package and create a dummy gsfonts-x11, which will prevent the real package from being installed to satisfy dependencies. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Will my fonts every look good?
In article <[EMAIL PROTECTED]>, David Z Maze wrote: > "Stig Are M. Botterli" <[EMAIL PROTECTED]> writes: > >> In article <[EMAIL PROTECTED]>, Bill Moseley >wrote: >>> >>> ii gsfonts-x110.16 Make Ghostscript fonts available to X11. >> >> This package is a real uglificator. Replace it with a dummy equiv. > > Why do you say that? That package makes the PostScript fonts included > with the GhostScript PS interpreter available to X. My experience has > been that PostScript fonts are generally superior to bitmapped fonts, > except at what these days are unusually low resolutions; if you want a > non-standard resolution, bitmapped fonts are right out. I'd actually > consider this package essential to coming up with font support that > doesn't suck. Superior to bitmapped fonts, sure, but inferior to the scalable fonts it overrode. When I googled for a quick fix to my problem, I found I wasn't the only person who had issues with this package. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: no MTRR
In article <[EMAIL PROTECTED]>, Michael Montagne wrote: > > Relatedly I also get this when trying to start ROX, which started this > whole experience: > > (rox:8892): GdkPixbuf-WARNING **: Can not open pixbuf loader module > file > '/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory > > ** (rox:8892): WARNING **: Couldn't recognize the image file format > for > file '/usr/share/rox/images/rox-show-details.png' > > (rox:8892): GdkPixbuf-WARNING **: Can not open pixbuf loader module > file > '/etc/gtk-2.0/gdk-pixbuf.loaders': No such file or directory > > What can I do? I have exactly the same problem with both ROX and Synaptic. How is the '/etc/gtk-2.0/gdk-pixbuf.loaders' supposed to be generated? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: no MTRR
In article <avpqko$qr7$[EMAIL PROTECTED]>, Stig Are M. Botterli wrote: > > I have exactly the same problem with both ROX and Synaptic. How is the > '/etc/gtk-2.0/gdk-pixbuf.loaders' supposed to be generated? Ok, installing unstable/libgtk2.0-common, which includes '/usr/sbin/update-gdkpixbuf-loaders', should take care of that one. Unless you're already running unstable, chances are you'll get the following error as well: rox: relocation error: /usr/X11R6/lib/libXft.so.2: undefined symbol: XRenderCompositeText8 Look at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=174589 for a solution. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Kernel panic: VFS: Unable to mount root fs
Basically, if my /boot/vmlinuz image exceeds a certain size (the limit seems be somewhere around 90 bytes), the following occurs on boot: hdc6: bad access: block=2, count=2 end_request: I/O error, dev 16:06 (hdc), sector 2 EXT3-fs: Unable to read superblock hdc6: bad access: block=2, count=2 end_request: I/O error, dev 16:06 (hdc), sector 2 EXT2-fs: Unable to read superblock hdc6: bad access: block=0, count=1 end_request: I/O error, dev 16:06 (hdc), sector 0 NTFS: Reading super block failed Kernel panic: VFS: Unable to mount root fs on 16:06 While some googling revealed that I'm certainly not the only one being hit by this particular type of kernel panic, I found no solutions that seemed applicable to my situation. This has happened with 2.4.19, 2.4.20-pre10, and now 2.4.20-ck1, all compiled from kernel.org sources (ck1 from http://members.optusnet.com.au/ckolivas/kernel/). I have not tested any 2.4-kernel prior to 2.4.19. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel panic: VFS: Unable to mount root fs
In article <20021205080347.GE7442@ursine>, Paul Johnson wrote: > > On Thu, Dec 05, 2002 at 01:04:34AM +0000, Stig Are M. Botterli wrote: >> Basically, if my /boot/vmlinuz image exceeds a certain size (the limit se= >> ems be >> somewhere around 90 bytes), the following occurs on boot: > > Whoa! Huge kernel! Module some of that stuff out and it should > help if there's some hidden size limitation. I have a pretty big > kernel, the bzImage is 644,225 bytes. I did this, and got the kernel down to 719kB. However, the exact same thing occurs on boot (minus the three last lines, as I included NTFS- support as a module), so a hidden size limitation is obviously not the problem. Now I'm really wondering what actually 'solved' it for me with 2.4.19 and 2.4.20-pre10. My 2.4.20-pre10 (+ RML's preemption patch) image at 865kB boots, whereas an image approx. 20kB bigger panicked, and the only thing I can recall changing was turning some non-essential things into modules. That's why I was certain the problem was related to the size of the kernel image. >> hdc6: bad access: block=3D2, count=3D2 >> end_request: I/O error, dev 16:06 (hdc), sector 2 >> EXT3-fs: Unable to read superblock >> hdc6: bad access: block=3D2, count=3D2 >> end_request: I/O error, dev 16:06 (hdc), sector 2 >> EXT2-fs: Unable to read superblock >> hdc6: bad access: block=3D0, count=3D1 >> end_request: I/O error, dev 16:06 (hdc), sector 0 >> NTFS: Reading super block failed >> Kernel panic: VFS: Unable to mount root fs on 16:06 > > Is your drive going bad? Are the filesystems OK? I've seen nothing to indicate that there's anything wrong with neither my drives nor my filesystems. The system operates fine once booted. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel panic: VFS: Unable to mount root fs
In article <[EMAIL PROTECTED]>, Klaus Imgrund wrote: > On Thu, 05 Dec 2002 15:16:29 + >> > I had kernels bigger than 1 MB - no problem. > It would help if you remember what things you configured as modules. Unfortunately, I don't. > If you got i.e a driver for the wrong sound card compiled in the kernel > it can give you a kernel panic.If it is compiled as module the module > just doesn't load. Perhaps, but I doubt anything like that can cause this particular kernel panic. Anyway, I've been able to boot a vanilla 2.4.20 kernel, and I'll make my changes one by one, so that if I'm hit by this again I will hopefully be able to pinpoint what introduced it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kernel panic: VFS: Unable to mount root fs
In article <20021206045426.GA22017@ursine>, Paul Johnson wrote: > > Wait, are you trying to boot a kernel that doesn't have ext3 compiled > in on a system whose /etc/fstab specifies the / partition as being > ext3? Nope, ext2/ext3 have been included in the vmlinuz-image all along. I'll throw in another question here: from /etc/fstab: /dev/hdc6 / ext2errors=remount-ro 0 1 from dmesg: kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. ... EXT3 FS 2.4-0.9.19, 19 August 2002 on ide1(22,6), internal journal I know I initially created / as an ext2 partition, and I can't recall having converted it to ext3 (though I could be wrong, I've certainly thought about it, I just can't recall having actually done it yet), I also just tried adriot3:~# mount -v -t ext3 -o remount /dev/hdc6 / /dev/hdc6 on / type ext3 (rw) adriot3:~# mount /dev/hdc6 on / type ext2 (rw) So why the mount as EXT3 while booting? Anyway, I've now got 2.4.20, plus the patches I wanted, up and running fine, and hopefully this won't be an issue again. It was probably some silly mistake on my part. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Manipulating .debs
I wanted to remove a dependency from a debian package. I took it apart and edited the control-file, and put it back together. However, dpkg wouldn't recognize it as a debian package. 'file' reports it as a "current ar archive", while it reports the original .deb as a Debian binary package. So the question is, how do I 'brand' (ie give it the correct magic number) my manipulated .deb-file as a debian package? In this particular case I found that building a dummy equiv .deb for the package I didn't want installed on my system to be a better solution anyway. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Getting a Higher Version w/out upgrading
In article <[EMAIL PROTECTED]>, Hal Vaughan wrote: > > When thinking about this, I wonder: Is there a way to easily specify and add > versions later than in stable for only specific packages? In other words, is > there some way I can do an apt-get and specify Perl 5.8 (assuming it's > already packaged) without having to move to the testing or unstable branch? Add the following line to /etc/apt/apt.conf: APT::Default-Release "stable"; With this, apt-get will default to installing packages from stable. To install a more up-to-date .deb if available, simply throw in '-t testing' or '-t unstable' as an argument to apt-get. Works brilliantly. You will of course have to track the branch you want to pull in packages from. For easy version comparison, I'd suggest installing 'apt-show-versions': ~ $ apt-show-versions -a -p perl perl5.8.0-14install ok installed perl5.6.1-7 stable No testing version perl5.8.0-14unstable perl/unstable uptodate 5.8.0-14 'No testing version' because I don't track testing. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kernel recompile
In article <[EMAIL PROTECTED]>, Florian Struck wrote: > > make menuconfig > make dep > make modules > make-kpkg kernel_image > and dpkg -i "resulting-kernel.deb" Step two and three are both taken care of in step four. I also wouldn't leave out 'make-kpkg clean' before your fourth step. I had some trouble booting some of my kernels a while back, and I just couldn't find out what was causing it. It seemed very random. However, I've had no such trouble after I took a better look at the documentation and added 'make-kpkg clean' to my building procedure. make-kpkg clean make-kpkg kernel_image make-kpkg modules_image This is how I build my kernels, with sources from kernel.org (and a couple of manually applied patches). The third step is necessary to build a .deb for my binary nvidia driver. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
