Some FreeBSD issues


 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers Some FreeBSD issues
# 8  
Old 06-11-2003
An on-board sound card with VIA chipset, as you have correctly guessed. I don't know what you exactly mean by a "kernel drive", though.

As I mentioned, when I increased the virtual channel settings to 4 (default 0) problems came. KsCD had no problems. Noatun/kaboodle playing MP3s had serious jitter and XMMS played them with the wrong tone (just like a vinyl record playing at a wrong speed) that I'd found it better to mute the sound card as it's too hard for my ears, although the blocking problem is indeed solved as advertised. Possibly VSC may work with a better sound card, but I don't know. My experience is not an acceptable one so I set it back to defaults.

Is the Linux sound architecture very much different from that of FreeBSD? I haven't heard about similar problems with sound device blocking on Linux before.

Yes, I use Gnome 1.x on SuSE. Possibly a correct choice for not upgrading to 2.x as Gnome/Gtk+ 2.x apps are simply too slow. At least that's really slow on my FreeBSD partition. I need to tweak the .gtkrc settings to use fonts in my locale or text won't appear correctly. Are there more well-documented guides/manuals of the .gtkrc series file format online? I have tried googling but it seems not much can be found, especially those concerning fonts/fontsets. I found http://developer.gnome.org/doc/API/g...rce-files.html but not exactly in a good format for understanding it and it just gives very brief description of each option and doesn't totally explain the mechanism, like when .gtkrc or .gtkrc-2.0 are used respectively etc.
# 9  
Old 06-11-2003
Quote:
Originally posted by cbkihong
An on-board sound card with VIA chipset, as you have correctly guessed. I don't know what you exactly mean by a "kernel drive", though.
Typo.

Meant to be "Kernel driver". I am using `device pcm` in my kernel for my VIA based K7EMPro El-Cheapo Soyo box with VIA VT82C686A AC97 codec without any sound quality problems. Just the blocking action under KDE. No blocking problem under Gnome 1.4.
# 10  
Old 06-11-2003
Quote:
Originally posted by auswipe
I am using `device pcm`[...] with VIA VT82C686A AC97 codec without any sound quality problems. Just the blocking action under KDE. No blocking problem under Gnome 1.4.
That's exactly the case with me. Sound quality problems only occur when messing around with VSC. Possibly I can only live with Gnome or use noatun instead in a KDE session, or I just flip back to SuSE when i would like to play mp3s.

Thank you.
# 11  
Old 06-13-2003
A quick follow-up question

A quick follow-up question:

If I use the port system I know I can pass additional make options to it. However, how can I know what options are available? If I do the ./configure; make; make install way I can use ./configure --help to get a list of the compilation options. But what about for ports in FreeBSD?
# 12  
Old 06-13-2003
That's a real good question. I normally just look at the Makefile and see the options in the Makefile.

I'll see if there is a better way than vi'ing the Makefile and report back if I find it.
# 13  
Old 06-13-2003
Re: A quick follow-up question

Quote:
Originally posted by cbkihong
A quick follow-up question:

If I use the port system I know I can pass additional make options to it. However, how can I know what options are available? If I do the ./configure; make; make install way I can use ./configure --help to get a list of the compilation options. But what about for ports in FreeBSD?
mezz had the answer over at FreeBSDForums.com in this thread.

You can go into the port and run `make patch`. All the relevant files and patches will be downloaded and applied. You can then change to the work sub-dir and the portname sub-dir and execute the ./configure --help and set the options you want and then `make && make install` like you are used to.

One word of warning though. If you go ahead and compile from the /work/<portname> sub-dir FreeBSD utilities like "portupgrade" will not automagically work. You'll have update the port yourself.

Here is an example on my FreeBSD 4.8 machine after `make patch` had already been ran for /usr/ports/editors/vim:

Code:
FreeBSD:root:/usr/ports/editors/vim $ cd work/
FreeBSD:root:/usr/ports/editors/vim/work $ cd vim61/
FreeBSD:root:/usr/ports/editors/vim/work/vim61 $ ./configure --help
Usage: configure [options] [host]
Options: [defaults in brackets after descriptions]
Configuration:
  --cache-file=FILE       cache test results in FILE
  --help                  print this message
  --no-create             do not create output files
  --quiet, --silent       do not print `checking...' messages
  --version               print the version of autoconf that created configure
Directory and file names:
  --prefix=PREFIX         install architecture-independent files in PREFIX
                          [/usr/local]
  --exec-prefix=EPREFIX   install architecture-dependent files in EPREFIX
                          [same as prefix]
  --bindir=DIR            user executables in DIR [EPREFIX/bin]
  --sbindir=DIR           system admin executables in DIR [EPREFIX/sbin]
  --libexecdir=DIR        program executables in DIR [EPREFIX/libexec]
  --datadir=DIR           read-only architecture-independent data in DIR
                          [PREFIX/share]
  --sysconfdir=DIR        read-only single-machine data in DIR [PREFIX/etc]
  --sharedstatedir=DIR    modifiable architecture-independent data in DIR
                          [PREFIX/com]
  --localstatedir=DIR     modifiable single-machine data in DIR [PREFIX/var]
  --libdir=DIR            object code libraries in DIR [EPREFIX/lib]
  --includedir=DIR        C header files in DIR [PREFIX/include]
  --oldincludedir=DIR     C header files for non-gcc in DIR [/usr/include]
  --infodir=DIR           info documentation in DIR [PREFIX/info]
  --mandir=DIR            man documentation in DIR [PREFIX/man]
  --srcdir=DIR            find the sources in DIR [configure dir or ..]
  --program-prefix=PREFIX prepend PREFIX to installed program names
  --program-suffix=SUFFIX append SUFFIX to installed program names
  --program-transform-name=PROGRAM
                          run sed PROGRAM on installed program names
Host type:
  --build=BUILD           configure for building on BUILD [BUILD=HOST]
  --host=HOST             configure for HOST [guessed]
  --target=TARGET         configure for TARGET [TARGET=HOST]
Features and packages:
  --disable-FEATURE       do not include FEATURE (same as --enable-FEATURE=no)
  --enable-FEATURE[=ARG]  include FEATURE [ARG=yes]
  --with-PACKAGE[=ARG]    use PACKAGE [ARG=yes]
  --without-PACKAGE       do not use PACKAGE (same as --with-PACKAGE=no)
  --x-includes=DIR        X include files are in DIR
  --x-libraries=DIR       X library files are in DIR
--enable and --with options recognized:
  --with-vim-name=NAME    what to call the Vim executable
  --with-ex-name=NAME     what to call the Ex executable
  --with-view-name=NAME   what to call the View executable
  --with-global-runtime=DIR    global runtime directory in 'runtimepath'
  --with-modified-by=NAME       name of who modified a release version
  --with-features=TYPE    tiny, small, normal, big or huge (default: normal)
  --with-compiledby=NAME  name to show in :version message
  --enable-perlinterp     Include Perl interpreter.
  --enable-pythoninterp   Include Python interpreter.
  --with-python-config-dir=PATH  Python's config directory
  --enable-tclinterp      Include Tcl interpreter.
  --with-tclsh=PATH       which tclsh to use (default: tclsh8.0)
  --enable-rubyinterp     Include Ruby interpreter.
  --enable-cscope         Include cscope interface.
  --enable-workshop       Include Sun Visual Workshop support.
  --enable-netbeans       Include NetBeans integration support.
  --enable-sniff          Include Sniff interface.
  --enable-multibyte      Include multibyte editing support.
  --enable-hangulinput    Include Hangul input support.
  --enable-xim            Include XIM input support.
  --enable-fontset        Include X fontset output support.
  --with-x                use the X Window System
  --enable-gui[=OPTS]     X11 GUI [default=auto] [OPTS=auto/no/gtk/gnome/motif/athena/beos/photon]
  --enable-gtk-check      If auto-select GUI, check for GTK [default=yes]
  --enable-gnome-check    If GTK GUI, check for GNOME [default=no]
  --enable-motif-check    If auto-select GUI, check for Motif [default=yes]
  --enable-athena-check   If auto-select GUI, check for Athena [default=yes]
  --with-gtk-prefix=PFX   Prefix where GTK is installed (optional)
  --with-gtk-exec-prefix=PFX Exec prefix where GTK is installed (optional)
  --disable-gtktest       Do not try to compile and run a test GTK program
  --with-gnome-includes=DIR Specify location of GNOME headers
  --with-gnome-libs=DIR   Specify location of GNOME libs
  --with-gnome            Specify prefix for GNOME files
  --with-motif-lib=STRING   Library for Motif
  --with-tlib=library     terminal library to be used
  --disable-acl           Don't check for ACL support.
  --disable-gpm           Don't use gpm (Linux mouse daemon).
  --disable-nls           Don't support NLS (gettext()).
FreeBSD:root:/usr/ports/editors/vim/work/vim61 $


Last edited by auswipe; 06-13-2003 at 05:35 PM..
# 14  
Old 06-14-2003
Thank you for helping me raise this question on the FreeBSD forums. The replies there do give me a lot of insights to investigate the ports system further.

I will see which method fits for each individual package I'm installing. Thx, you're very helpful.
 
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. BSD

FreeBSD DHCP wpa_supplicant Wi-Fi Issues

I just got FreeBSD up and running with an XFCE desktop on an old Gateway laptop. It works great, except the wireless setup is scaring me. I can connect to my home WiFi fine most of the time, but I'm concerned about other WiFi that I will need to connect to away from home. I understand that I can... (1 Reply)
Discussion started by: BrentBANKS
1 Replies

2. IP Networking

Test Network Routing Issues (FREEBSD and RHEL)

Hello, I'm attempting to setup a test network with a client-server based architecture using a proprietary application. The client works by communicating with the server on separate links (typically cellular connections) and then initiates a tunnel over each active link. However, in place of the... (0 Replies)
Discussion started by: shadyuk
0 Replies

3. AIX

Networking Issues - Opera, FreeBSD, AIX

(1) Hi, Am working on FreeBSD 7.4/i386 and installed Opera 11.01 through ports collection manually... But when I run first time am getting "opera: cannot connect X server. Error: Unknown error: 0" What is this error all about???? Please help me to sort out this issue!!! (2) Hi, currently am... (12 Replies)
Discussion started by: Priya Amaresh
12 Replies

4. BSD

FreeBSD AMD NFS over TCP issues

Hi! I have a major issue with FreeBSD 7.1 i386. We did a change in our Unix env where we exchanged home storage from a NetAPP running udp to a NetAPP running tcp. Now I cant mount homedirs since NFS/AMD seem to fallback to udp :( Trying to force it with amd options nfs_proto=tcp and so on. ... (0 Replies)
Discussion started by: Esaia
0 Replies

5. UNIX for Dummies Questions & Answers

Resolved: htpasswd issues (-b) on FreeBSD

I wrote a script to batch-create directories with .htaccess and .htpasswd files. I am using the following line to create the .htpasswd file: htpasswd -cb .htpasswd $USER $PASS However, I keep getting this message in return: Usage: htpasswd passwordfile username The -c flag creates a new... (1 Reply)
Discussion started by: Spetnik
1 Replies

6. Web Development

Using IP.Board on FreeBSD, having SQL/Apache Issues

Server: FreeBSD 7.2-RELEASE MYSQL Version: MYSQL 5.1.36 PHP Version: 5.2.10 (apache2handler) IP.Board Version: v3.0.2 Safe Mode: OFF For the most part previously IP.Board, forum software, has run fine without any issues. Regular web pages and .php pages seem to load fine without any issues.... (2 Replies)
Discussion started by: Dark Severance
2 Replies

7. Programming

Application crashes in FreeBSD 7.1 while working ok in FreeBSD 6.3

Hello there, My mulithreaded application (which is too large to represent the source code here) is crashing after installing FreeBSD 7.1-RELEASE/amd64. It worked properly on others machines (Dual Cores with 4GB of RAM - FreeBSD 6.2-RELEASE/i386). The current machine has 2x Core 2 Duo... (1 Reply)
Discussion started by: Seenquev
1 Replies

8. BSD

FreeBSD - Kernel Queries/Issues

All, I am a bit of a BSD newbie and haven't really played with it for years, but I have had a recent situation whereby someone attempted to load a custom kernel module and ended up breaking my BSD server. I managed to fix it by doing the following: Booting into loader mode: unload set... (3 Replies)
Discussion started by: drbabbers
3 Replies

9. UNIX for Advanced & Expert Users

snort installation on freebsd issues

i'm following the, "How to setup and secure Snort, MySQL and Acid on FreeBSD 4.6 Release" off of the snort.org website. in the documentation it says snort should be installed through the following: ----- make -DWITH_MYSQL -DWITH_FLEXRESP ; make install ----- later it says to do the... (13 Replies)
Discussion started by: xyyz
13 Replies

10. UNIX Desktop Questions & Answers

FreeBSD 4.7 X issues - assistance req'd please

question: i just installed FreeBSD 4.7 on my laptop, when i log in as root, i can startx no problem at all but when i try to start it as a user, i can't. otiginally it told me i needed to be a member of the group 'wheel' to do startx, no problem, added myself in /etc/group, but for some reason i... (1 Reply)
Discussion started by: Calum
1 Replies
Login or Register to Ask a Question