* Re: [gentoo-user] Which drivers to use for audio and video?
2005-09-02 5:18 ` Walter Dnes
@ 2005-09-02 5:28 ` Mark Knecht
2005-09-03 15:36 ` waltdnes
2005-09-02 7:55 ` Neil Bothwick
` (2 subsequent siblings)
3 siblings, 1 reply; 9+ messages in thread
From: Mark Knecht @ 2005-09-02 5:28 UTC (permalink / raw
To: gentoo-user
On 9/1/05, Walter Dnes <waltdnes@waltdnes.org> wrote:
> > As for the ATI driver I set it up quickly today using the radeon
> > driver from xorg-x11.
>
> After reading your message, I tried Radeon, and it seems to work. I
> manually entered the frequencies for my monitor, and 1600 X 1200 works
> fine. Now I just need to get the sound chip working.
>
I set up sound today. I got both the on-board sound chip as well as
the HDSP 9652 working, although very little testing.
So far everything has worked nicely. Only a couple of small issues:
1) A false Gnome message every time I log in.
2) The 'default' sound card setting, since I'm using two devices.
Tomorro I hope to try the ATI proprietary driver to see if I can get 3D working.
There are a number of strange things I've run into. For instance, on
the mplayer emerge:
lightning ~ # emerge -pv mplayer
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[ebuild R ] media-video/mplayer-1.0_pre7-r1 (-3dfx) (-3dnow)
(-3dnowext) +X -aac -aalib +alsa (-altivec) -arts -bidi -bl
-cdparanoia -cpudetection -custom-cflags -debug -dga -directfb
(-divx4linux) -doc -dts -dv -dvb +dvd +dvdread -edl +encode +esd
-fbcon -ggi +gif +gtk +i8x0 +ipv6 +jack -joystick +jpeg -libcaca +lirc
-live -lzo +mad* -matroska -matrox (-mmx) (-mmxext) +mythtv -nas +nls
-nvidia +opengl -oss +png +real -rtc -samba +sdl (-sse) (-sse2)
(-svga) -tga -theora -truetype +v4l +v4l2 +vorbis* (-win32codecs)
-xanim -xinerama -xmms +xv +xvid -xvmc 0 kB
Total size of downloads: 0 kB
lightning ~ #
Note that 3dnow and mmx are disabled even though I have them enabled
in my make.conf file:
USE="radeon mmx mmxext sse sse2 3dnow 3dnowext gnome kde -arts ladspa
nptl nptlonly ladcca audiofile gimp gimpprint ppds usb alsa cdr dvd
dvdr dvdread caps jack jack-tmpfs fluidsynth tcltk sndfile v4l v4l2
mysql flac xscreensaver -samba i8x0 mythtv apache2 lirc mjpeg xvid
real"
I need to understand why that happens. /proc/cpuinfo says they should work:
lightning ~ # cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 47
model name : AMD Athlon(tm) 64 Processor 3000+
stepping : 0
cpu MHz : 1809.280
cache size : 512 KB
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext
fxsr_opt lm 3dnowext 3dnow pni lahf_lm
bogomips : 3588.09
TLB size : 1024 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc
lightning ~ #
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [gentoo-user] Which drivers to use for audio and video?
2005-09-02 5:28 ` Mark Knecht
@ 2005-09-03 15:36 ` waltdnes
0 siblings, 0 replies; 9+ messages in thread
From: waltdnes @ 2005-09-03 15:36 UTC (permalink / raw
To: gentoo-user
On Thu, Sep 01, 2005 at 10:28:27PM -0700, Mark Knecht wrote
> Note that 3dnow and mmx are disabled even though I have them enabled
> in my make.conf file:
What about your CFLAGS line? I assume that you're using "-march=k8".
It's supposed to implicitly include mmx and sse and sse2, but maybe the
mplayer make file gets cute, and tries reading CFLAGS. Here's my 32-bit
mode CFLAGS line...
CFLAGS="-O2 -pipe -fomit-frame-pointer -march=athlon -m3dnow -mmmx -msse -msse2 -msse3 -mfpmath=sse"
My emerge seems to have everything I asked for
[m3000][root][~] emerge -pv mplayer
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[ebuild R ] media-video/mplayer-1.0_pre7-r1 -3dfx +3dnow +3dnowext
+X +aac -aalib +alsa (-altivec) -arts -bidi -bl -cdparanoia +cpudetection
-custom-cflags -debug +dga -directfb +divx4linux -doc -dts -dv -dvb +dvd
+dvdread -edl +encode -esd -fbcon -ggi +gif -gtk -i8x0 -ipv6 -jack
-joystick +jpeg -libcaca -lirc -live -lzo -mad -matroska -matrox +mmx
+mmxext -mythtv -nas -nls -nvidia +opengl -oss +png +real -rtc -samba
+sdl +sse +sse2 -svga -tga +theora +truetype -v4l -v4l2 +vorbis
+win32codecs -xanim -xinerama -xmms +xv -xvid -xvmc 0 kB
Try the following command, and see what local flags it allows...
grep /mplayer: /usr/portage/profiles/use.local.desc
I think that local flags are supposed to be entered in
/etc/portage/package.use. Here's my entry...
media-video/mplayer cpudetection real sse2 3dnowext mmxext
My flags line is almost identical to yours. I'm missing "lahf_lm".
--
Walter Dnes <waltdnes@waltdnes.org>
My musings on technology and security at http://tech_sec.blog.ca
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [gentoo-user] Which drivers to use for audio and video?
2005-09-02 5:18 ` Walter Dnes
2005-09-02 5:28 ` Mark Knecht
@ 2005-09-02 7:55 ` Neil Bothwick
2005-09-02 8:55 ` Nick Rout
2005-09-03 3:44 ` Ian Hastie
3 siblings, 0 replies; 9+ messages in thread
From: Neil Bothwick @ 2005-09-02 7:55 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: text/plain, Size: 1679 bytes --]
On Fri, 2 Sep 2005 01:18:00 -0400, Walter Dnes wrote:
> > I'm setting up the same thing, although I used the 64-bit Gentoo
> > install CD. Why are you using 32-bit?
>
> I did some RTFM, and it appears that emerging 32-bit apps requires a
> bit of a hassle. You basically have to install a 32-bit chroot
> environment, which you drop into to do the 32-bit emerges. What apps
> would you want to emerge 32-bit, you ask? Here's a partial list, off
> the top of my head, of what you lose if you go 64-bit-only...
> - OpenOffice does not build in 64-bit mode.
No, but openoffice-bin works fine on AMD64, and the latest OOo is only
available as a binary package anyway.
> - 32-bit plugins for your web-browser of choice
True.
> - kiss "internet TV" goodbye, because...
> - RealPlayer is distributed as a 32-bit app
Which works in a 64 bit environment.
> The "final straw" for me was that LILO is masked out for 64 bits, and
> GRUB is the only available bootloader. GRUB seems to have been
> afflicted by Microsoft-featureitis disease. It's got a whole lot of
> additional complexity, which allows it to display an image of Clippy (or
> Tux) at bootup. Come-on guys; people need a *BOOTLOADER*, not a
> singing/dancing penguin or paperclip, at bootup.
So don't use that option, in the same way you don't use the equivalent
option in LILO. Like it or not, some people don't want to look at a bunch
of text when their computer boots, it scares or bores them. such an
option may not be for you but others do want it, which is why both
bootloaders have it.
--
Neil Bothwick
Top Oxymorons Number 32: Living dead
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [gentoo-user] Which drivers to use for audio and video?
2005-09-02 5:18 ` Walter Dnes
2005-09-02 5:28 ` Mark Knecht
2005-09-02 7:55 ` Neil Bothwick
@ 2005-09-02 8:55 ` Nick Rout
2005-09-03 3:44 ` Ian Hastie
3 siblings, 0 replies; 9+ messages in thread
From: Nick Rout @ 2005-09-02 8:55 UTC (permalink / raw
To: gentoo-user
On Fri, 2005-09-02 at 01:18 -0400, Walter Dnes wrote:
> The "final straw" for me was that LILO is masked out for 64 bits, and
> GRUB is the only available bootloader. GRUB seems to have been
> afflicted by Microsoft-featureitis disease. It's got a whole lot of
> additional complexity, which allows it to display an image of Clippy
> (or
> Tux) at bootup. Come-on guys; people need a *BOOTLOADER*, not a
> singing/dancing penguin or paperclip, at bootup.
what bolox.
follow the instructions on the gentoo install manual, which from memory
go:
emerge grub
$EDITOR /boot/grub/grub.conf
EITHER {
grub-install /dev/hda
}
OR {
grub
root (hd0,0)
setup (hd0)
quit
}
--
Nick Rout <nick@rout.co.nz>
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [gentoo-user] Which drivers to use for audio and video?
2005-09-02 5:18 ` Walter Dnes
` (2 preceding siblings ...)
2005-09-02 8:55 ` Nick Rout
@ 2005-09-03 3:44 ` Ian Hastie
2005-09-03 15:33 ` waltdnes
3 siblings, 1 reply; 9+ messages in thread
From: Ian Hastie @ 2005-09-03 3:44 UTC (permalink / raw
To: gentoo-user
On Fri, 2 Sep 2005 01:18:00 -0400
"Walter Dnes" <waltdnes@waltdnes.org> wrote:
> I did some RTFM, and it appears that emerging 32-bit apps requires a
> bit of a hassle. You basically have to install a 32-bit chroot
> environment, which you drop into to do the 32-bit emerges.
This is a hassle, but not a huge one. For a lot of things it isn't
actually necessary anyway.
> What apps
> would you want to emerge 32-bit, you ask? Here's a partial list, off
> the top of my head, of what you lose if you go 64-bit-only...
> - OpenOffice does not build in 64-bit mode.
openoffice-bin works very well.
> - 32-bit plugins for your web-browser of choice
<web browser of choice>-bin is again what you want. OK, you use some
flexibility in both of these, but the problem is only caused by closed
source 32 bit binaries anyway.
> - kiss "internet TV" goodbye, because...
> - RealPlayer is distributed as a 32-bit app
Which will work with multilib support. The plugin still requires the
32 bit precompiled browser though.
> - mplayer, itself, will compile in 64-bit mode. However, the
> "win32codecs" don't exist in a 64-bit equivalent.
There is now a mplayer-bin ebuild which supports win32codecs. It too
works very well.
> The "final straw" for me was that LILO is masked out for 64 bits,
> and GRUB is the only available bootloader. GRUB seems to have been
> afflicted by Microsoft-featureitis disease. It's got a whole lot of
> additional complexity, which allows it to display an image of Clippy
> (or Tux) at bootup. Come-on guys; people need a *BOOTLOADER*, not a
> singing/dancing penguin or paperclip, at bootup.
GRUB is just a boot loader. It's a very flexible one, but that's all.
If you don't want the graphics then you're under no obligation to use
them.
> What advantages does 64-bit mode offer? I don't have terabytes of
> RAM so that ability isn't required.
Well my Athlon64 can only use 40 bit address bus, that's 1TB of RAM. I
doubt I could fit it into the motherboard though.
address sizes : 40 bits physical, 48 bits virtual
> 64-bit mode is allegedly faster
> by default on other distros. This is probably true. The underlying
> reason for that is that in 64-bit mode, the gcc compiler defaults to
> include the flags "-mmmx -msse -msse2 -msse3
I hope not! My vintage of Athlon64 wouldn't like it at all.
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall
nx mmxext lm 3dnowext 3dnow
Notice there is no sse3 support.
> -m3dnow -mfpmath=sse"
> for the AMD64 cpu, which it doesn't do for 32-bit mode on the same
> chip. On a binary distro, you're stuck with what you're given. With
> Gentoo, we "Gentoo ricers" can set those flags in /etc/make.conf and
> get their benefit. So that advantage for 64-bit mode disappears in
> Gentoo.
The real underlying cause of better performance in 64 bit mode is that
it has twice as many CPU registers available. The x86 architecture
was always deficient in this respect and AMD64 had put this right at
long last. Personally I wouldn't have minded a few more, but that
probably isn't really necessary.
> > As for the ATI driver I set it up quickly today using the radeon
> > driver from xorg-x11.
>
> After reading your message, I tried Radeon, and it seems to work. I
> manually entered the frequencies for my monitor, and 1600 X 1200 works
> fine.
My NVIDIA works with the AMD64 Linux driver very well too. Of course
the OSS drivers in xorg-x11 also work well as long as you don't need 3D
support.
> Now I just need to get the sound chip working.
Which chip is it you have? My emu10k1 based Audigy 2 works well with
the in kernel driver. I'd expect most of the other OSS kernel
supported chips to work in 64 bit mode too.
--
Ian.
EOM
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [gentoo-user] Which drivers to use for audio and video?
2005-09-03 3:44 ` Ian Hastie
@ 2005-09-03 15:33 ` waltdnes
0 siblings, 0 replies; 9+ messages in thread
From: waltdnes @ 2005-09-03 15:33 UTC (permalink / raw
To: gentoo-user
On Sat, Sep 03, 2005 at 04:44:42AM +0100, Ian Hastie wrote
> "Walter Dnes" <waltdnes@waltdnes.org> wrote:
> Notice there is no sse3 support.
I got carried away there. It only goes up to sse2. Another goof on
my part was referring to the gcc 3.4.4 docs. I think we're still on
3.3.5.
> > Now I just need to get the sound chip working.
>
> Which chip is it you have? My emu10k1 based Audigy 2 works well with
> the in kernel driver. I'd expect most of the other OSS kernel
> supported chips to work in 64 bit mode too.
I finally got it going. My Google-fu hasn't been as good as it could
be. I tried earlier searching on my motherboard and "k8", and got
buried in a gazillion results, consisting mostly of people listing off
their system components, or else computer stores selling systems with
that motherboard. I tried a few more times and finally found someone
saying how he got his sound working. First, in "make menuconfig" ...
<M> Intel/SiS/nVidia/AMD/ALi AC97 Controller
And then at bootup...
modprobe snd-intel8x0
I could put the modprobe
--
Walter Dnes <waltdnes@waltdnes.org>
My musings on technology and security at http://tech_sec.blog.ca
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 9+ messages in thread