Re: automount usb flash drive?
Seems like the only thing that will work for me is to make a one-line shell script. I tried the various things you mentioned. I have yet to look at how to use amd(8). Setting vfs.usermount=1 and changing the ownership to the user name in question allows me to mount the usbkey without su'ing. I still can't get the usbd.conf to run an attach command on the umass* action. Thanks for your help. On Apr 6, 2005 4:01 PM, Roland Smith [EMAIL PROTECTED] wrote: On Wed, Apr 06, 2005 at 03:32:14PM -0400, Todd Shirk wrote: I was trying to figure out how to have a usb flash drive automount when I plug it in. I currently have the following line in /etc/fstab /dev/da0s1 /mnt/usbkey msdos rw,-m700,noauto 0 0 and the following in /etc/devfs.conf perm da0s1 0666 devfs.conf only works for devices available at boot time. For devices you can plug in at runtime you should use /etc/devfs.rules: [foobar=10] add path 'da*s*' mode 0666 And you should have the following in /etc/rc.conf: devfs_system_ruleset=foobar The contents of devfs.rules are fed to devfs(8), so see it's manual page. when I do the following command line command the usb flash drive mount fine # mount /mnt/usbkey But, when I'm in KDE viewing media:/ Removable Device (da0s1) is shown is unmounted. At the user level command line and in KDE, I receive /dev/da0s1: Operation not permitted. For a user to be able to use a filesystem, there are a couple of things that need to be done: - The sysctl variable vfs.usermount must be set to 1 (in /etc/sysctl.conf). - The user in question must own the mount point. I'm not sure if part of the issue is permissions or if I'm missing a piece for the auto-mounting to happen. I think the latter. Normally usbd(8) is notified of USB events, but in this case it seems to get events for the umass* device, not the da*s* device that you'll want to use. There have been people who've used a shell-script called by usbd to figure out the connection between umass-da from dmesg output and then mount the filesystem, but that doesn't do umounts. It's also complicated if you want it to work for multiple users, unless you give it 777 permissions. You could also give amd(8) a try. I found that making a one-line shell script to do the mounting is much less hassle. Roland -- R.F. Smith /\ASCII Ribbon Campaign r s m i t h @ x s 4 a l l . n l \ /No HTML/RTF in e-mail http://www.xs4all.nl/~rsmith/ X No Word docs in e-mail public key: http://www.keyserver.net / \Respect for open standards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Issue compiling JDK15
Hi, I've been attempting to compile JDK15 on my AMD64 laptop. I have linux redhat 8 installed for linux compatibility and the linux-sun-jdk1.4.2 installed so that the /usr/ports/java/jdk15 would use the appropriate javac compiler to compile JDK15 natively. I reach a point where I receive the following message. execv(): Bad address Error trying to exec /usr/local/linux-sun-jdk1.4.2/bin/javac. Check if file exists and permissions are set correctly. gmake[3]: *** [.compile.classlist] Error 1 gmake[3]: Leaving directory '/usr/ports/java/jdk15/work/j2se/make/java/java' gmake[2]: *** [all] Error 1 gmake[2]: Leaving directory '/usr/ports/java/jdk15/work/j2se/make/java' gmake[1] *** [all] Error 1 gmake[1]: Leaving directory '/usr/ports/java/jdk15/work/j2se/make' gmake: *** [j2se-build] Error 2 *** Error code 2 Stop in /usr/ports/java/jdk15. I've checked and /usr/local/linux-sun-jdk1.4.2/bin/javac exists and permissions appear adequate. For giggles I chmod 777 on the file with the same results. Any thoughts? Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot use cvsup with 5.3-release
I ran into a problem like that when I did an upgrade to 5.4-prelease. I found for me, that for port updates it seems to look at your release level in your options. I went into root and ran sysinstall. I selected Options. At the bottom of the left hand column is the option Release Name. I changed it to 5.3-RELEASE. I'd probably check there, another thing I'll do is try a couple other cvsup sites. On Apr 7, 2005 1:58 PM, Tetsuji Maverick Rai [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I want to keep my ports up to date. in 5.3-release (i386) So I copied a sample ports-supfile and edit as follows (just changed my host) However I got this message and I cannot figure out what Release means. In http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html#CVSUP-CONFIG-VERS Release is defined as cvs. su-3.00# cvsup -g -L 2 ports-suprile Parsing supfile ports-supfile Release not specified for collection host=cvsup.jp.FreeBSD.org What am I doing wrong? Thanks in advance!! - -my ports-supfile # $FreeBSD: src/share/examples/cvsup/ports-supfile,v 1.32 2004/05/24 06:23:15 cjc Exp $ # # This file contains all of the CVSup collections that make up the # FreeBSD-current ports collection. # # CVSup (CVS Update Protocol) allows you to download the latest CVS # tree (or any branch of development therefrom) to your system easily # and efficiently (far more so than with sup, which CVSup is aimed # at replacing). If you're running CVSup interactively, and are # currently using an X display server, you should run CVSup as follows # to keep your CVS tree up-to-date: # # cvsup ports-supfile # # If not running X, or invoking cvsup from a non-interactive script, then # run it as follows: # # cvsup -g -L 2 ports-supfile # # You may wish to change some of the settings in this file to better # suit your system: # host=cvsup.jp.FreeBSD.org # This specifies the server host which will supply the # file updates. You must change it to one of the CVSup # mirror sites listed in the FreeBSD Handbook at # http://www.freebsd.org/doc/handbook/mirrors.html. # You can override this setting on the command line # with cvsup's -h host option. # base=/var/db # This specifies the root where CVSup will store information # about the collections you have transferred to your system. # A setting of /var/db will generate this information in # /var/db/sup. Even if you are CVSupping a large number of # collections, you will be hard pressed to generate more than # ~1MB of data in this directory. You can override the # base setting on the command line with cvsup's -b base # option. This directory must exist in order to run CVSup. # prefix=/usr # This specifies where to place the requested files. A # setting of /usr will place all of the files requested # in /usr/ports (e.g., /usr/ports/devel, /usr/ports/lang). # The prefix directory must exist in order to run CVSup. # Defaults that apply to all the collections # # IMPORTANT: Change the next line to use one of the CVSup mirror sites # listed at http://www.freebsd.org/doc/handbook/mirrors.html. *default host=cvsup.jp.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix src-all # If you seem to be limited by CPU rather than network or disk bandwidth, try # commenting out the following line. (Normally, today's CPUs are fast enough # that you want to run compression.) *default compress ## Ports Collection. # # The easiest way to get the ports tree is to use the ports-all # mega-collection. It includes all of the individual ports-* # collections, ports-all #(after this, all are commented out) - - - -- Tetsuji 'Maverick' Rai PGP Key fingerprint = 2021 6BF9 CEA3 73DE FF17 B326 F4DA F04E F784 3B85 gpg fingerprint Aviation Jokes: http://www.geocities.com/tetsuji_rai/ Profile http://maverick.ns1.name/ http://maverick.IsASecret.com/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFCVXTO9NrwTveEO4URAuEXAJ9t41/Ffs17D29HGXOiuk+1W9sXIgCeJQ9a +bVZ1ipsSH1h+/yD0haAp7Q= =Xsbt -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
automount usb flash drive?
I was trying to figure out how to have a usb flash drive automount when I plug it in. I currently have the following line in /etc/fstab /dev/da0s1 /mnt/usbkey msdos rw,-m700,noauto 0 0 and the following in /etc/devfs.conf perm da0s1 0666 when I do the following command line command the usb flash drive mount fine # mount /mnt/usbkey But, when I'm in KDE viewing media:/ Removable Device (da0s1) is shown is unmounted. At the user level command line and in KDE, I receive /dev/da0s1: Operation not permitted. I'm not sure if part of the issue is permissions or if I'm missing a piece for the auto-mounting to happen. Any thoughts? Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hardware problems after installing 5.4 pre-release
I've tried installing gnome and windowmaker to test the sound. Each act the same as KDE. Mplayer works with sound but nothing else. I, also, installed xmms and tested, no sound. The sound graphics are idle, seeming to indicate that the sound is not being generated in the applications. I, also, tried the command line app cdcontrol. # cdcontrol -f /dev/acd0 play 1 no sound. Does mplayer use a kernel independent sound driver? On Tue, 29 Mar 2005 01:03:08 +0200, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: On Mon, 28 Mar 2005 17:08:47 -0500 Todd Shirk [EMAIL PROTECTED] wrote: Here's an update on the sound issue. I ported down and compiled mplayer. I popped in a DVD and typed on the command line: # mplayer dvd:// With that I got sound to play. I then recompile xine, but xine still has no sound. KDE is also soundless. this sounds a little bit like KDE's sound-daemon (artsd) is not working well or something like that what happens with your sound if you use e.g. icewm or fluxbox or windowmaker ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hardware problems after installing 5.4 pre-release
You referred to kldstat. I'm not sure what I'm looking for with that or what switch I may need to use. I typed and received the following information: # kldstat Id Refs AddressSize Name 18 0x8010 7c36b8 kernel 21 0x808c4000 50c8 udbp.ko 32 0x808ca000 20ae0netgraph.ko 41 0x808eb000 5f98 ugen.ko 51 0x808f1000 3918 ums.ko I added the founding command and got the following results: # kldload snd_driver # kldstat Id Refs AddressSize Name 1 59 0x8010 7c36b8 kernel 21 0x808c4000 50c8 udbp.ko 32 0x808ca000 20ae0netgraph.ko 41 0x808eb000 5f98 ugen.ko 51 0x808f1000 3918 ums.ko 61 0xa7842000 78d snd_driver.ko 71 0xa7843000 1a7d snd_ad1816.ko 81 0xa7845000 1b9d snd_als4000.ko 91 0xa7847000 1fdd snd_cmi.ko 101 0xa7849000 221d snd_cs4281.ko 112 0xa784c000 3f3a snd_csa.ko 121 0xa785 8add snd_ds1.ko 131 0xa7859000 4375 snd_emu10k1.ko 141 0xa785e000 2c81 snd_es137x.ko 152 0xa7861000 240a snd_ess.ko 164 0xa7864000 1a85 snd_sbc.ko 171 0xa7866000 181d snd_fm801.ko 182 0xa7868000 6e8a snd_mss.ko 191 0xa786f000 227d snd_ich.ko 201 0xa7872000 3e5d snd_maestro.ko 211 0xa7876000 5b3d snd_maestro3.ko 221 0xa787c000 e41d snd_neomagic.ko 231 0xa788b000 184d snd_sb8.ko 241 0xa788d000 1bed snd_sb16.ko 251 0xa788f000 251d snd_solo.ko 261 0xa7892000 221d snd_t4dwave.ko 271 0xa7895000 169d snd_via82c686.ko 281 0xa7897000 225d snd_vibes.ko After doing that, I still do not have any sound. I notice that snd_via8233 is not in the resulting list of loaded drivers in kldstat. My assumption is that it didn't load through kldload since it's being loaded at the kernel level. With the command of: # cat /dev/sndstat FreeBSD Audio Driver (newpcm) Installed devices: pcm0: VIA VT8235 at io 0x1000 irq 10 (5p/1r/0v channels duplex default) It would seem that my sound driver is loading. The audio software seems to believe that there is a sound card to attach to. Could there be a problem with the sound driver I'm using. Would there be a reason why snd_via8233 works fine in 5.3 and not 5.4 pre-release? Also, could the usb mouse problem be part of the same problem, reasoning being that there may be a global hardware issue and that it may be conflicts in device handling vs. a configuration issue? Regardless, I'm happy and willing to try any thoughts. I, also, tried to manually choose snd_via8233 with this result: # kldload snd_via8233 kldload: can't load snd_via8233: File exists In the meantime, I'll try to trace down some helpful error messages from the usb mouse problem. On Thu, 24 Mar 2005 23:15:41 +0100, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: On Thu, 24 Mar 2005 22:07:57 + Todd Shirk [EMAIL PROTECTED] wrote: (MYKERNEL is the GENERIC plus the lines needed for loading the sound system and the via8233 sound driver for my sound card) device sound device snd_via8233 (with mergemaster I chose i for each file, indicating to use tempory) I booted into the new environment and started KDE3.4. I noticed that I had no sound and no usb mouse functionality. I did the following: # cat /dev/sndstat FreeBSD Audio Driver (newpcm) Installed devices: pcm0: VIA VT8235 at io 0x1000 irq 10 (5p/1r/0v channels duplex default) did you check with kldstat which module for sounds was loaded ? and tried : kldload snd_driver ? see e.g. : http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/sound-setup.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hardware problems after installing 5.4 pre-release
To add information on the usb mouse problem when I plug my usb mouse in to the 2 usb 2.0 ports, I get the first error at the command line: uhub1: device problem (SET_ADDR_FAILED), disabling port 2 uhub1: device problem (SET_ADDR_FAILED), disabling port 1 Like the sound, the usb mouse was working fine with FreeBSD 5.3, but stop functioning after rebuild world to 5.4 pre-release. On Mon, 28 Mar 2005 13:50:36 +, Todd Shirk [EMAIL PROTECTED] wrote: You referred to kldstat. I'm not sure what I'm looking for with that or what switch I may need to use. I typed and received the following information: # kldstat Id Refs AddressSize Name 18 0x8010 7c36b8 kernel 21 0x808c4000 50c8 udbp.ko 32 0x808ca000 20ae0netgraph.ko 41 0x808eb000 5f98 ugen.ko 51 0x808f1000 3918 ums.ko I added the founding command and got the following results: # kldload snd_driver # kldstat Id Refs AddressSize Name 1 59 0x8010 7c36b8 kernel 21 0x808c4000 50c8 udbp.ko 32 0x808ca000 20ae0netgraph.ko 41 0x808eb000 5f98 ugen.ko 51 0x808f1000 3918 ums.ko 61 0xa7842000 78d snd_driver.ko 71 0xa7843000 1a7d snd_ad1816.ko 81 0xa7845000 1b9d snd_als4000.ko 91 0xa7847000 1fdd snd_cmi.ko 101 0xa7849000 221d snd_cs4281.ko 112 0xa784c000 3f3a snd_csa.ko 121 0xa785 8add snd_ds1.ko 131 0xa7859000 4375 snd_emu10k1.ko 141 0xa785e000 2c81 snd_es137x.ko 152 0xa7861000 240a snd_ess.ko 164 0xa7864000 1a85 snd_sbc.ko 171 0xa7866000 181d snd_fm801.ko 182 0xa7868000 6e8a snd_mss.ko 191 0xa786f000 227d snd_ich.ko 201 0xa7872000 3e5d snd_maestro.ko 211 0xa7876000 5b3d snd_maestro3.ko 221 0xa787c000 e41d snd_neomagic.ko 231 0xa788b000 184d snd_sb8.ko 241 0xa788d000 1bed snd_sb16.ko 251 0xa788f000 251d snd_solo.ko 261 0xa7892000 221d snd_t4dwave.ko 271 0xa7895000 169d snd_via82c686.ko 281 0xa7897000 225d snd_vibes.ko After doing that, I still do not have any sound. I notice that snd_via8233 is not in the resulting list of loaded drivers in kldstat. My assumption is that it didn't load through kldload since it's being loaded at the kernel level. With the command of: # cat /dev/sndstat FreeBSD Audio Driver (newpcm) Installed devices: pcm0: VIA VT8235 at io 0x1000 irq 10 (5p/1r/0v channels duplex default) It would seem that my sound driver is loading. The audio software seems to believe that there is a sound card to attach to. Could there be a problem with the sound driver I'm using. Would there be a reason why snd_via8233 works fine in 5.3 and not 5.4 pre-release? Also, could the usb mouse problem be part of the same problem, reasoning being that there may be a global hardware issue and that it may be conflicts in device handling vs. a configuration issue? Regardless, I'm happy and willing to try any thoughts. I, also, tried to manually choose snd_via8233 with this result: # kldload snd_via8233 kldload: can't load snd_via8233: File exists In the meantime, I'll try to trace down some helpful error messages from the usb mouse problem. On Thu, 24 Mar 2005 23:15:41 +0100, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: On Thu, 24 Mar 2005 22:07:57 + Todd Shirk [EMAIL PROTECTED] wrote: (MYKERNEL is the GENERIC plus the lines needed for loading the sound system and the via8233 sound driver for my sound card) device sound device snd_via8233 (with mergemaster I chose i for each file, indicating to use tempory) I booted into the new environment and started KDE3.4. I noticed that I had no sound and no usb mouse functionality. I did the following: # cat /dev/sndstat FreeBSD Audio Driver (newpcm) Installed devices: pcm0: VIA VT8235 at io 0x1000 irq 10 (5p/1r/0v channels duplex default) did you check with kldstat which module for sounds was loaded ? and tried : kldload snd_driver ? see e.g. : http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/sound-setup.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hardware problems after installing 5.4 pre-release
Here's an update on the sound issue. I ported down and compiled mplayer. I popped in a DVD and typed on the command line: # mplayer dvd:// With that I got sound to play. I then recompile xine, but xine still has no sound. KDE is also soundless. Hopefully this helps. On Mon, 28 Mar 2005 14:43:46 +, Todd Shirk [EMAIL PROTECTED] wrote: To add information on the usb mouse problem when I plug my usb mouse in to the 2 usb 2.0 ports, I get the first error at the command line: uhub1: device problem (SET_ADDR_FAILED), disabling port 2 uhub1: device problem (SET_ADDR_FAILED), disabling port 1 Like the sound, the usb mouse was working fine with FreeBSD 5.3, but stop functioning after rebuild world to 5.4 pre-release. On Mon, 28 Mar 2005 13:50:36 +, Todd Shirk [EMAIL PROTECTED] wrote: You referred to kldstat. I'm not sure what I'm looking for with that or what switch I may need to use. I typed and received the following information: # kldstat Id Refs AddressSize Name 18 0x8010 7c36b8 kernel 21 0x808c4000 50c8 udbp.ko 32 0x808ca000 20ae0netgraph.ko 41 0x808eb000 5f98 ugen.ko 51 0x808f1000 3918 ums.ko I added the founding command and got the following results: # kldload snd_driver # kldstat Id Refs AddressSize Name 1 59 0x8010 7c36b8 kernel 21 0x808c4000 50c8 udbp.ko 32 0x808ca000 20ae0netgraph.ko 41 0x808eb000 5f98 ugen.ko 51 0x808f1000 3918 ums.ko 61 0xa7842000 78d snd_driver.ko 71 0xa7843000 1a7d snd_ad1816.ko 81 0xa7845000 1b9d snd_als4000.ko 91 0xa7847000 1fdd snd_cmi.ko 101 0xa7849000 221d snd_cs4281.ko 112 0xa784c000 3f3a snd_csa.ko 121 0xa785 8add snd_ds1.ko 131 0xa7859000 4375 snd_emu10k1.ko 141 0xa785e000 2c81 snd_es137x.ko 152 0xa7861000 240a snd_ess.ko 164 0xa7864000 1a85 snd_sbc.ko 171 0xa7866000 181d snd_fm801.ko 182 0xa7868000 6e8a snd_mss.ko 191 0xa786f000 227d snd_ich.ko 201 0xa7872000 3e5d snd_maestro.ko 211 0xa7876000 5b3d snd_maestro3.ko 221 0xa787c000 e41d snd_neomagic.ko 231 0xa788b000 184d snd_sb8.ko 241 0xa788d000 1bed snd_sb16.ko 251 0xa788f000 251d snd_solo.ko 261 0xa7892000 221d snd_t4dwave.ko 271 0xa7895000 169d snd_via82c686.ko 281 0xa7897000 225d snd_vibes.ko After doing that, I still do not have any sound. I notice that snd_via8233 is not in the resulting list of loaded drivers in kldstat. My assumption is that it didn't load through kldload since it's being loaded at the kernel level. With the command of: # cat /dev/sndstat FreeBSD Audio Driver (newpcm) Installed devices: pcm0: VIA VT8235 at io 0x1000 irq 10 (5p/1r/0v channels duplex default) It would seem that my sound driver is loading. The audio software seems to believe that there is a sound card to attach to. Could there be a problem with the sound driver I'm using. Would there be a reason why snd_via8233 works fine in 5.3 and not 5.4 pre-release? Also, could the usb mouse problem be part of the same problem, reasoning being that there may be a global hardware issue and that it may be conflicts in device handling vs. a configuration issue? Regardless, I'm happy and willing to try any thoughts. I, also, tried to manually choose snd_via8233 with this result: # kldload snd_via8233 kldload: can't load snd_via8233: File exists In the meantime, I'll try to trace down some helpful error messages from the usb mouse problem. On Thu, 24 Mar 2005 23:15:41 +0100, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: On Thu, 24 Mar 2005 22:07:57 + Todd Shirk [EMAIL PROTECTED] wrote: (MYKERNEL is the GENERIC plus the lines needed for loading the sound system and the via8233 sound driver for my sound card) device sound device snd_via8233 (with mergemaster I chose i for each file, indicating to use tempory) I booted into the new environment and started KDE3.4. I noticed that I had no sound and no usb mouse functionality. I did the following: # cat /dev/sndstat FreeBSD Audio Driver (newpcm) Installed devices: pcm0: VIA VT8235 at io 0x1000 irq 10 (5p/1r/0v channels duplex default) did you check with kldstat which module for sounds was loaded ? and tried : kldload snd_driver ? see e.g. : http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/sound-setup.html
Hardware problems after installing 5.4 pre-release
I'm running FreeBsd/amd64 on a Gateway 7422GX. I installed the 5.3-release version and configured the OS to function properly with the hardware except for the built-in wireless and the infamous conexant softmodem. I read up on some wireless setups to get my wireless card working. In the process, I decided to try my first attempt at a rebuild of world with the latest cvsup stable-supfile download (March 24, 2005). I used the method of: # make buildworld # make buildkernel KERNCONF=MYKERNEL # make installkernel KERNCONF=MYKERNEL # reboot selected singleuser mode from startup menu # fsck -p # mount -u / # mount -a -t ufs # swapon -a # mergemaster -p # make installworld # mergemaster # reboot (MYKERNEL is the GENERIC plus the lines needed for loading the sound system and the via8233 sound driver for my sound card) device sound device snd_via8233 (with mergemaster I chose i for each file, indicating to use tempory) I booted into the new environment and started KDE3.4. I noticed that I had no sound and no usb mouse functionality. I did the following: # cat /dev/sndstat FreeBSD Audio Driver (newpcm) Installed devices: pcm0: VIA VT8235 at io 0x1000 irq 10 (5p/1r/0v channels duplex default) So, the driver seems to be loading, but I'm getting no sound. I've, also, done the following to try to get the sound back. # sysctl hw.snd.pcm0.vchans=8 # sysctl hw.snd.maxautovchans=8 I checked my mixer levels in KDE and added hint.pcm.0.vol=100 to the /boot/device.hints being that the usb mouse also stopped working, I think there might be an issue with the hardware discovery routines in bootup or a configuration file that 5.3 used was overwritten with the rebuilding of world. I'm quite new to FreeBSD and am trying to get a good grasp on the general workings of the OS. So, assume that I need step by step guidelines. Perhaps, since I'm dealing with a pre-release, some of the functionality is missing by design. I have assumed that STABLE would mean that functioning hardware from the prior release will continue functioning with STABLE. I've stayed clear of CURRENT assuming things may often be broken in that branch, as it is experimental. Any help in enlightening me on my hardware issues will be greatly appreciated. # uname -a FreeBSD Todds-Notebook.linksys 5.4-PRERELEASE FreeBSD 5.4-PRERELEASE #0: Thu Mar 24 14:26:05 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MYKERNEL amd64 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
