Re: Portupgrade now supports pkgng [/usr/ports/UPDATING]
On 10/28/2012 03:00 AM, Bryan Drewery wrote: PKGNG is a replacement for the pkg_* tools that record package data in /var/db/pkg. It also allows for binary package upgrades. If you are wanting to use pkgng for binary packages, there's no need to use portupgrade anymore. Just 'pkg install name', 'pkg upgrade', etc. Understood. Thanks. For some reason I thought I could use the PKGNG tool set together with portupgrade the same way the pkg_* tools are used. Is there a straightforward way to go back to using the pkg_* tools in 9.1? Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problem with libpng + Mozilla applications on FreeBSD 8.3
On Sunday 28 October 2012 01:17:46 Manish Jain wrote: Consider me a newbie here. How do I do wide-reinstall ? You can do this with ports-mgmt/portmaster. See the section Using portmaster to do a complete reinstallation of all your ports at the end of the examples section of the man page. I don't mind pulling in and building a few more ports as long as it is not the whole GNOME2 metaport Rebuilding everything is the least complicated way of fixing the problem. It's a big job but if you don't do that then you're likely to have to keep doing even more firefighting in the future. -- Mike Clarke ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
ports index out-of-date
Hi, it seems that the problem (last reported and fixed around Oct 17) still persists: # cd /usr/ports # fetch http://www.FreeBSD.org/ports/INDEX-9.bz2 INDEX-9.bz2 100% of 1621 kB 161 kBps 00m00s # ls -al IN* -rw-r--r-- 1 root wheel 1660069 Oct 20 18:13 INDEX-9.bz2 jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Wine-fbsd64 updated to 1.5.16 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.5.16 have been uploaded to mediafire [2]. The packages for FreeBSD 10 use the pkgng [3] format. Please read the installation messages, if you use the nVidia graphics driver, for further information. FAQ --- Q: wine: failed to initialize: / usr/local/lib32/wine/ntdll.dll.so: Undefined symbol _ThreadRuneLocale A: This problem is specific to FreeBSD-9.0, please either stick with wine-1.5.10 or update to a newer version of FreeBSD (-STABLE or 9.1). Apologies for the inconvenience. Q: Creating pkgng packages for FreeBSD-9 A: When there is no demand for FreeBSD-8 packages I'll create additional pkgng packages for FreeBSD-9. Since it is possible to install the existing pkg packages in a pkgng environment (which I do) this is not a high priority. Regards, David [1] MD5 (wine-1.5.x-freebsd8/wine-fbsd64-1.5.16,1.tbz) = fae74f2dc33226f9c69d28b4dfb928b8 MD5 (wine-1.5.x-freebsd9/wine-fbsd64-1.5.16.1.txz) = 467b906e0ec3ecca7f9441a02c69381c MD5 (wine-1.5.x-freebsd10/wine-fbsd64-1.5.16,1.txz) = 353f259b1820b9aeee6caf423a0b98e1 [2] http://www.mediafire.com/wine_fbsd64 [3] http://wiki.freebsd.org/pkgng signature.asc Description: This is a digitally signed message part.
Re: Portupgrade now supports pkgng [/usr/ports/UPDATING]
On 10/28/2012 2:16 AM, Alexander Kapshuk wrote: On 10/28/2012 03:00 AM, Bryan Drewery wrote: PKGNG is a replacement for the pkg_* tools that record package data in /var/db/pkg. It also allows for binary package upgrades. If you are wanting to use pkgng for binary packages, there's no need to use portupgrade anymore. Just 'pkg install name', 'pkg upgrade', etc. Understood. Thanks. For some reason I thought I could use the PKGNG tool set together with portupgrade the same way the pkg_* tools are used. pkgng obsoletes portupgrade -P and pkg_add -r. Even if portupgrade -P did have pkg support, it would not work right because of different OPTIONS/dependencies, and the desync between your local ports tree and the remote package server's versions. You can use 'pkg install' to replace 'portupgrade -P' right now, and just not use -P if you want to use the port. But it will not go smoothly. Picking one of the other is best. (Ports or packages) If you're managing multiple servers with packages, I recommend checking out ports-mgmt/poudriere (http://fossil.etoilebsd.net/poudriere) as it will build the binary packages to create your own remote pkgng repository. poudriere+pkgng really do obsolete portupgrade all together. Is there a straightforward way to go back to using the pkg_* tools in 9.1? If you have not installed, upgraded, or deinstalled anything, yes. You can cp all of the package dirs from /var/db/pkg.bak into /var/db/pkg, and remove WITH_PKGNG from /etc/make.conf and then run pkgdb -fu again. Thanks. -- Regards, Bryan Drewery bdrewery@freenode/EFNet ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Why RELENG_9 branch is labeled as PRERELEASE and freebsd.org says FreeBSD is currently at 9.1-RC2 ?
Le Sat, 27 Oct 2012 16:54:45 -0700, Yuri y...@rawbw.com a écrit : RELENG_9 is supposed to represent the latest branch of 9.1. De facto, code says it is PRERELEASE (sys/conf/newvers.sh). But freebsd.org on its front page says 9.1 is at RC-2. So how can I get RC-2 through cvsup except through RELENG_9 which gives PRERELEASE ? RELENG_9 should be called 9-STABLE, if you want 9.1 use RELENG_9_1 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade now supports pkgng [/usr/ports/UPDATING]
Le Sat, 27 Oct 2012 21:22:32 +0300, Alexander Kapshuk alexander.kaps...@gmail.com a écrit : Having done all of the above, I ran portupgrade to update all the pkgs that needed upgrading on my system, and got the message below: root@box0:/root/tmp # portupgrade -varRP --batch -L '%s_%s' USING PKGNG Packages are not yet suported. Use pkg(8) directly. That doesn't sound like portupgrade supports pkgng, or did I misread the message in the UPDATING file? pkg is able to make packages upgrade by itself. I think the good way to update with packages is pkg updgrade then portupgrade to build the ports without packages avalaible. Anyway I had many problems with portupgrade and pkg (basically It was not able to build its database because of inconsistency in ports dependencies), portmaster with pkgng patch looks better. Regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade now supports pkgng [/usr/ports/UPDATING]
Got it. Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Portupgrade now supports pkgng [/usr/ports/UPDATING]
On 10/28/2012 04:27 PM, Patrick Lamaiziere wrote: pkg is able to make packages upgrade by itself. I think the good way to update with packages is pkg updgrade then portupgrade to build the ports without packages avalaible. Anyway I had many problems with portupgrade and pkg (basically It was not able to build its database because of inconsistency in ports dependencies), portmaster with pkgng patch looks better. Regards. Understood. Thanks. I'll look into that. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
No sound from speaker, using Realtek ALC269 and snd_hda
Hi all, I have an asus eeepc 1001px, on which I installed 9-stable. I, since day one, never had any sound coming out of the speaker, but when I plug a headphone in the jack, I have the sound -in the headphones. The chipset is a Realtek ALC269 which some people said is supported. I read, and re-read the man page for snd_hda so many times, but I just can't make it work. Here's what I have right now in my device.hints Code: hint.hdaa.0.nid20.config=as=1 seq=0 device=Speaker hint.hdaa.0.nid26.config=as=1 seq=15 device=Headphones hint.hdaa.0.nid18.config=as=2 seq=0 #hint.hdaa.0.gpio_config=0=set hint.hdaa.0.config=forcestereo,ivref50,ivref80,ivref100,ivref,vref hint.pcm.0.config=gpio0,gpio1,gpio2,gpio3,gpio4,gpio5,gpio6,gpio7 hint.pcm.0.vol=100 This is my n'th attempt, I pretty tried everything I could imagine. Here's my verbose dmesg http://dpaste.com/818967/plain/ Am I missing something? Is my understanding of pinouts correct? Thank you for your attention, and help! :) hdacc0: Realtek ALC269 HDA CODEC at cad 0 on hdac0 hdacc0: Root Node at nid=0: 1 subnodes 1-1 hdaa0: Realtek ALC269 Audio Function Group at nid 1 on hdacc0 hdaa0: Audio Function Group at nid=1: 34 subnodes 2-35 hdaa0: NumGPIO=2 NumGPO=0 NumGPI=0 GPIWake=0 GPIUnsol=1 hdaa0: GPIO0: disabled hdaa0: GPIO1: disabled hdaa0: Original pins configuration: hdaa0: nid 0xas seq device conn jackloccolor misc hdaa0: 18 99a30920 2 0 Mic Fixed ATAPI OnboardUnknown 9 hdaa0: 20 99130110 1 0 Speaker Fixed ATAPI OnboardUnknown 1 hdaa0: 23 41f0 15 0 Speaker None 1/8 Rear Black 1 hdaa0: 24 41f0 15 0 Speaker None 1/8 Rear Black 1 hdaa0: 25 41f0 15 0 Speaker None 1/8 Rear Black 1 hdaa0: 26 0121441f 1 15 HeadphonesJack 1/8 Rear Green 4 hdaa0: 27 41f0 15 0 Speaker None 1/8 Rear Black 1 hdaa0: 29 4006852d 2 13 Line-out None Digital 0x00 Purple 5 hdaa0: 30 41f0 15 0 Speaker None 1/8 Rear Black 1 hdaa0: 33 41f0 15 0 Speaker None 1/8 Rear Black 1 hdaa0: Patching widget caps nid=29 0x0040 - 0x0070 hdaa0: Patched pins configuration: hdaa0: nid 0xas seq device conn jackloccolor misc hdaa0: 18 99a30920 2 0 Mic Fixed ATAPI OnboardUnknown 9 hdaa0: 20 99130110 1 0 Speaker Fixed ATAPI OnboardUnknown 1 hdaa0: 23 41f0 15 0 Speaker None 1/8 Rear Black 1 DISA hdaa0: 24 41f0 15 0 Speaker None 1/8 Rear Black 1 DISA hdaa0: 25 41f0 15 0 Speaker None 1/8 Rear Black 1 DISA hdaa0: 26 0121441f 1 15 HeadphonesJack 1/8 Rear Green 4 hdaa0: 27 41f0 15 0 Speaker None 1/8 Rear Black 1 DISA hdaa0: 30 41f0 15 0 Speaker None 1/8 Rear Black 1 DISA hdaa0: 33 41f0 15 0 Speaker None 1/8 Rear Black 1 DISA hdaa0: 2 associations found: hdaa0: Association 0 (1) out: hdaa0: Pin nid=20 seq=0 hdaa0: Pin nid=26 seq=15 hdaa0: Association 1 (2) in: hdaa0: Pin nid=18 seq=0 hdaa0: Tracing association 0 (1) hdaa0: Pin 20 traced to DAC 2 hdaa0: Pin 26 traced to DAC 2 and hpredir 0 hdaa0: Association 0 (1) trace succeeded hdaa0: Tracing association 1 (2) hdaa0: Unable to trace pin 18 to ADC 8, undo traces hdaa0: Pin 18 traced to ADC 9 hdaa0: Association 1 (2) trace succeeded hdaa0: Looking for additional DAC for association 0 (1) hdaa0: Looking for additional ADC for association 1 (2) hdaa0: Tracing input monitor hdaa0: Tracing other input monitors hdaa0: Tracing nid 18 to out hdaa0: Tracing beeper hdaa0: nid 29 traced to out hdaa0: Headphones redirection for association 0 nid=26 using unsolicited responses. hdaa0: FG config/quirks: forcestereo ivref50 ivref80 ivref100 ovref50 ovref80 ovref100 ivref ovref vref hdaa0: hdaa0: +---+ hdaa0: | DUMPING HDA NODES | hdaa0: +---+ hdaa0: hdaa0: Default Parameter hdaa0: - hdaa0: Stream cap: 0x0001 hdaa0: PCM hdaa0: PCM cap: 0x000e0560 hdaa0: 16 20 24 bits, 44 48 96 192 KHz hdaa0: IN amp: 0x hdaa0: OUT amp: 0x hdaa0: hdaa0: nid: 2 hdaa0:Name: audio output hdaa0: Widget cap: 0x001d hdaa0: STEREO hdaa0: Association: 0 (0x8001) hdaa0: OSS: pcm (pcm) hdaa0: Stream cap: 0x0001 hdaa0: PCM hdaa0: PCM cap: 0x000e0560 hdaa0: 16 20 24 bits, 44 48 96 192 KHz hdaa0: Output amp: 0x00025757 hdaa0: mute=0 step=87 size=2 offset=87 hdaa0: hdaa0: nid: 3 [DISABLED] hdaa0:Name: audio output hdaa0: Widget cap: 0x001d hdaa0: STEREO hdaa0: Stream cap: 0x0001 hdaa0: PCM hdaa0:
9.1-RC2: clang can no longer build a kernel that boots
I'm seeing that on 9.1-RC2 (i386), clang can no longer build a kernel that boots. Any kernel I build would get stuck at Timecounters tick every 1.000 msec. However, building the same kernel with gcc has no problems. Also, if I build the kernel with clang from 9.0-RELEASE, it also works fine. I tried this with both my custom kernel config as well as GENERIC, and I'm seeing the same thing. Anyone else seeing this? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 9.1-RC2: clang can no longer build a kernel that boots
Let me clarify. If I build the 9.1-RC2 kernel using the clang binary from 9.0-RELEASE, it boots fine. On Sun, Oct 28, 2012 at 9:41 AM, Mike Cui cui...@gmail.com wrote: I'm seeing that on 9.1-RC2 (i386), clang can no longer build a kernel that boots. Any kernel I build would get stuck at Timecounters tick every 1.000 msec. However, building the same kernel with gcc has no problems. Also, if I build the kernel with clang from 9.0-RELEASE, it also works fine. I tried this with both my custom kernel config as well as GENERIC, and I'm seeing the same thing. Anyone else seeing this? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: OT: gEDA, SPICE, electronic cad/simulation
On Sun, Oct 28, 2012 at 11:27:25AM -0600, we recorded a bogon-computron collision of the ru...@bogodyn.org flavor, containing: 3) SPICE (and ng-spice) always uses the first character of a device line to determine the type of the device. While most designers will draw a circuit with an IC in it and give the IC a name like U1, the character u in the first position on a device line means lossy transmission line in spice, not IC. Thus, in your netlist you're simply telling the simulator to create a lossy transmission line using nodes 0, 4, 3 and +9v as its four ports, and it's getting confused by all the extra parameters on the line. My mistake. U is the Uniform Lossy RC line, not the lossy transmission line. The URC device takes 3 nodes and a model name, and so it's used 0, 4, and 3 as the nodes, and then gotten confused about the unknown model named +9v. It then gets confused about the remaining parameters on the line. Point remains the same, you can't specify an IC named U1 in a spice netlist by calling the device U1. You need to use an X subcircuit instantiation line and an associated .subckt subcircuit definition. -- Tom RussoKM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236http://kevan.org/brain.cgi?DDTNM And, isn't sanity really just a one-trick pony anyway? I mean all you get is one trick, rational thinking, but when you're good and crazy, oooh, oooh, oooh, the sky is the limit! --- The Tick ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: OT: gEDA, SPICE, electronic cad/simulation
Date: Sun, 14 Oct 2012 22:26:34 +1000 From: Da Rock freebsd-questi...@herveybayaustralia.com.au Subject: OT: gEDA, SPICE, electronic cad/simulation I'm struggling with this damn gEDA/SPICE thing - I think I have gEDA schem figured, but I can't be sure because I can't test it. For the life of me I can't seem to get my head around it, but then I might just be too tired. Can anyone point out what I'm missing? I open geda, create a sch file (circuit), and then run gnetlist -g spice-sdb sch-file. I then run ngspice (or gspiceui) but it comes up with errors over the 555 (U1) and diodes (d?) I'm running like this: Error on line 9 : d1 2 0 unknown unable to find definition of model unknown - default assumed Error on line 13 : u1 0 4 3 +9v 1 4 5 +9v unknown unable to find definition of model +9v - default assumed unknown parameter (4) I see some folks have tried to answer you, but it seems that it's expected that these models somehow already exist on your system and you're just not finding them. That's not the case. Without seeing the entire netlist, I can't be precise, but there are several important things to know about SPICE and device models: 1) SPICE provides only the infrastructure for simulating diodes, i.e. a module that lets you specify all the parameters of a diode and which will then simulate the circuit using the parameters you provide. A model in this case means a set of parameters, which is specified in a .model card. Basically, your schematic has defined a diode without telling the simulator the name of a model card to look for, so gnetlist has inserted unknown as the model name. You then did not provide a .model unknown d card to define unknown as a diode model. No open-source SPICE-like simulator provides model cards for common devices. You either have to find one from a manufacturer's web site, find one someone has posted on a web site somewhere, or extract the relevant parameters yourself (this list sorted in order of increasing complexity). Commercial spice packages do come with enormous model, libraries, but you pay big, big bucks for those versions. Werner Hoch wrote a system called spicelib for gEDA that attempts to download a large number of spice-compatible models from vendor web sites and massage them to work with ng-spice. I have run it once, and found that it needed a little patching up to make it work on FreeBSD instead of Linux (for example, the md5sum program is used througout, and this doesn't exist on BSD --- I had to hand-edit scripts all over the place to make it use md5 instead). Even so, there are few basic parts in these model libraries. Once in a while I have found cool web sites with hundreds of spice models for common discrete parts. They disappear after a year or five. You *COULD* try adding .model unknown d to your netlist to let ng-spice use all the default parameters for the diode. It might not work well, but it *will* shut up the error. It's what SPICE wound up doing itself when it couldn't find the model named unknown. For details about spice diode models, see, for example, http://www.acsu.buffalo.edu/~wie/applet/spice_pndiode/spice_diode_table.html 2) There is no 555 model in SPICE, ng-spice, or any other spice. Such devices are always simulated by creating a subcircuit model (.subckt). gschem will gleefully create a line in your netlist for such a device, but unless you also provide a subcircuit model for it, you won't be able to simulate it, no way, no how. ng-spice does NOT come with a 555 subcircuit model, nor does geda/gschem. gschem merely provides a symbol for such a device. Try googling for spice 555 model subcircuit and go from there. One post in the thread on this site: http://www.electro-tech-online.com/general-electronics-chat/5806-spice-555-timer.html has a UA555 subcircuit model that you may be able to use, if you make sure that the subcircuit pins match the pins gschem/gnetlist are assigning. 3) SPICE (and ng-spice) always uses the first character of a device line to determine the type of the device. While most designers will draw a circuit with an IC in it and give the IC a name like U1, the character u in the first position on a device line means lossy transmission line in spice, not IC. Thus, in your netlist you're simply telling the simulator to create a lossy transmission line using nodes 0, 4, 3 and +9v as its four ports, and it's getting confused by all the extra parameters on the line. To create a subcircuit instance (which is what you want), you need to use the X device. The format of the X device is: Xname [nodes] subcircuit definition name so, in your case, you would want something like: XU1 0 4 3 +9v 1 4 5 +9v UA555 and a .subckt UA555 card like the one in the post I mentioned in point 2 above. Note
Re: Why RELENG_9 branch is labeled as PRERELEASE and freebsd.org says FreeBSD is currently at 9.1-RC2 ?
On 10/28/2012 07:17, Patrick Lamaiziere wrote: RELENG_9 should be called 9-STABLE, if you want 9.1 use RELENG_9_1 Hm, if they wanted to keep RELENG_9 as stable 9.X branch, why then 9.1-PRERELEASE is there? Is PRERELEASE considered more stable than RC? This looks strange to me. Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Problem with connecting FreeBSD 8.3 to wireless network
On 28-Oct-12 05:53, Polytropon wrote: On Sun, 28 Oct 2012 05:47:46 +0530, Manish Jain wrote: On 28-Oct-12 01:49, Polytropon wrote: I don't mind pulling in and building a few more ports as long as it is not the whole GNOME2 metaport. It could very well be the whole Gnome 2 metaport. :-( Hi All, After reading all the replies to my earlier post Problem with libpng + Mozilla applications on FreeBSD 8.3, I finally summoned up the courage to build the GNOME2 metaport from the ports directory. Since this would not be possible within my lifetime with my usual internet connection, I paid for and succeeded in getting temporary access to a wireless network. Win XP connects to the network pretty smoothly, so there was much reason for hope that things would go smoothly on my FreeBSD 8.3 installation too. I tried configuring the Atheros device to the network as explained in the FreeBSD handbook. But I am having usual rate of success, which is not very high. All the required modules are present in the kernel, as can be seen below : # kldload ath kldload: can't load ath: File exists # kldload wlan_tkip kldload: can't load wlan_tkip: File exists But dmesg returns no output for ath0 : # dmesg | grep -i ath Empty output ifconfig returns the following output : # ifconfig bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=c019bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO,LINKSTATE ether b8:88:e3:45:63:b1 inet6 fe80::ba88:e3ff:fe45:63b1%bge0 prefixlen 64 scopeid 0x2 nd6 options=3PERFORMNUD,ACCEPT_RTADV media: Ethernet autoselect (none) status: no carrier lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=3RXCSUM,TXCSUM inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 nd6 options=3PERFORMNUD,ACCEPT_RTADV tun0: flags=8051UP,POINTOPOINT,RUNNING,MULTICAST metric 0 mtu 1500 options=8LINKSTATE inet 10.0.0.1 -- 10.0.0.2 netmask 0xff00 Opened by PID 767 Since there is no mention of ath0, I did not expect creating the wlan0 pseudo-device would be a simple matter, and I was right : # ifconfig wlan0 create wlandev ath0 ifconfig: SIOCIFCREATE2: Device not configured Manually trying to create the pseudo-device ath0 presents equally unpleasant output : # ifconfig ath0 create ifconfig: SIOCIFCREATE2: Invalid argument pciconf does show my device, but I do not know how to make use of the information (please refer the last few lines of the output) : # pciconf -lv hostb0@pci0:0:0:0: class=0x06 card=0x06491025 chip=0x01048086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' class = bridge subclass = HOST-PCI vgapci0@pci0:0:2:0: class=0x03 card=0x06491025 chip=0x01068086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' class = display subclass = VGA none0@pci0:0:22:0: class=0x078000 card=0x06491025 chip=0x1e3a8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = simple comms ehci0@pci0:0:26:0: class=0x0c0320 card=0x06491025 chip=0x1e2d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = serial bus subclass = USB hdac0@pci0:0:27:0: class=0x040300 card=0x06491025 chip=0x1e208086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = multimedia subclass = HDA pcib1@pci0:0:28:0: class=0x060400 card=0x06491025 chip=0x1e108086 rev=0xc4 hdr=0x01 vendor = 'Intel Corporation' class = bridge subclass = PCI-PCI pcib2@pci0:0:28:1: class=0x060400 card=0x06491025 chip=0x1e128086 rev=0xc4 hdr=0x01 vendor = 'Intel Corporation' class = bridge subclass = PCI-PCI ehci1@pci0:0:29:0: class=0x0c0320 card=0x06491025 chip=0x1e268086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = serial bus subclass = USB isab0@pci0:0:31:0: class=0x060100 card=0x06491025 chip=0x1e5e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = bridge subclass = PCI-ISA atapci0@pci0:0:31:2: class=0x01018f card=0x06491025 chip=0x1e018086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = mass storage subclass = ATA none1@pci0:0:31:3: class=0x0c0500 card=0x06491025 chip=0x1e228086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = serial bus subclass = SMBus atapci1@pci0:0:31:5: class=0x010185 card=0x06491025 chip=0x1e098086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = mass storage subclass = ATA bge0@pci0:2:0:0: class=0x02 card=0x06471025 chip=0x16b514e4 rev=0x10 hdr=0x00 vendor = 'Broadcom Corporation' class = network subclass = ethernet none2@pci0:2:0:1: class=0x080501 card=0x06471025 chip=0x16bc14e4 rev=0x10 hdr=0x00 vendor = 'Broadcom
Re: Problem with connecting FreeBSD 8.3 to wireless network
On 10/28/12 20:50, Manish Jain wrote: # dmesg | grep -i ath Empty output Doesn't look like your atheros network card has been detected by your system. Did you check the ath(4) man page to see if your particular piece of hardware is supported on FreeBSD 8.3? http://www.freebsd.org/cgi/man.cgi?query=athsektion=4manpath=FreeBSD+8.3-RELEASE HARDWARE The ath driver supports all Atheros Cardbus and PCI cards, except those that are based on the AR5005VL chipset. I'm running: box0=; uname -a FreeBSD box0.my.domain 9.1-RC2 FreeBSD 9.1-RC2 #0 r241133: Tue Oct 2 17:11:45 UTC 2012 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 And my atheros card is supported. box0=; dmesg | grep ath ath0: Atheros 5424/2424 mem 0xd600-0xd600 irq 16 at device 0.0 on pci2 ath0: AR2425 mac 14.2 RF5424 phy 7.0 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: No sound from speaker, using Realtek ALC269 and snd_hda
On 28.10.2012 17:12, Big Yuuta wrote: I have an asus eeepc 1001px, on which I installed 9-stable. I, since day one, never had any sound coming out of the speaker, but when I plug a headphone in the jack, I have the sound -in the headphones. The chipset is a Realtek ALC269 which some people said is supported. Now driver support most of CODECs. I don't know cases when specific CODEC would be a problem, and Realtek CODECs from functional side are better then many others. But many systems have custom wiring and laptops are usually more problematic there. I read, and re-read the man page for snd_hda so many times, but I just can't make it work. Here's what I have right now in my device.hints Code: hint.hdaa.0.nid20.config=as=1 seq=0 device=Speaker hint.hdaa.0.nid26.config=as=1 seq=15 device=Headphones hint.hdaa.0.nid18.config=as=2 seq=0 As I see, these three hints are replicating existing configuration and effectively useless. #hint.hdaa.0.gpio_config=0=set hint.hdaa.0.config=forcestereo,ivref50,ivref80,ivref100,ivref,vref hint.pcm.0.config=gpio0,gpio1,gpio2,gpio3,gpio4,gpio5,gpio6,gpio7 hint.pcm.0.vol=100 This is my n'th attempt, I pretty tried everything I could imagine. Here's my verbose dmesg http://dpaste.com/818967/plain/ Am I missing something? Is my understanding of pinouts correct? CODEC configuration looks good and I see no problems in driver output. I think most likely problem is in CODEC wiring and power amplifier. Your CODEC has two GPIO lines and EAPD line. That gives 8 possible combinations. I would recommend you to try them all. GPIOs, as you tried could be set with hint.hdaa.0.gpio_config tunable. EAPD line can be controlled (0 or 100) by the ogain mixer control. Unluckily with this output I can't completely identify your system to check what Linux does for it. Could you send me `devinfo -vr` output. -- Alexander Motin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Why RELENG_9 branch is labeled as PRERELEASE and freebsd.org says FreeBSD is currently at 9.1-RC2 ?
Yuri yuri at rawbw.com writes: On 10/28/2012 07:17, Patrick Lamaiziere wrote: RELENG_9 should be called 9-STABLE, if you want 9.1 use RELENG_9_1 Hm, if they wanted to keep RELENG_9 as stable 9.X branch, why then 9.1-PRERELEASE is there? Is PRERELEASE considered more stable than RC? This looks strange to me. Yuri http://svnweb.freebsd.org/base/releng/9.1/sys/conf/newvers.sh?view=log Go back to Revision 227495, read log text, click View and scroll down to see TYPE=FreeBSD 34 REVISION=9.0 BRANCH=PRERELEASE Then back off and move the log up by repeating as above. Hopefully you understand his drill :-) jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problem with connecting FreeBSD 8.3 to wireless network
Forgot to mention the full name of the adapter : Atheros AR5B125 Regards, Manish Jain bourne.ident...@hotmail.com On 29-Oct-12 00:20, Manish Jain wrote: On 28-Oct-12 05:53, Polytropon wrote: On Sun, 28 Oct 2012 05:47:46 +0530, Manish Jain wrote: On 28-Oct-12 01:49, Polytropon wrote: I don't mind pulling in and building a few more ports as long as it is not the whole GNOME2 metaport. It could very well be the whole Gnome 2 metaport. :-( Hi All, After reading all the replies to my earlier post Problem with libpng + Mozilla applications on FreeBSD 8.3, I finally summoned up the courage to build the GNOME2 metaport from the ports directory. Since this would not be possible within my lifetime with my usual internet connection, I paid for and succeeded in getting temporary access to a wireless network. Win XP connects to the network pretty smoothly, so there was much reason for hope that things would go smoothly on my FreeBSD 8.3 installation too. I tried configuring the Atheros device to the network as explained in the FreeBSD handbook. But I am having usual rate of success, which is not very high. All the required modules are present in the kernel, as can be seen below : # kldload ath kldload: can't load ath: File exists # kldload wlan_tkip kldload: can't load wlan_tkip: File exists But dmesg returns no output for ath0 : # dmesg | grep -i ath Empty output ifconfig returns the following output : # ifconfig bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=c019bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO,LINKSTATE ether b8:88:e3:45:63:b1 inet6 fe80::ba88:e3ff:fe45:63b1%bge0 prefixlen 64 scopeid 0x2 nd6 options=3PERFORMNUD,ACCEPT_RTADV media: Ethernet autoselect (none) status: no carrier lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 options=3RXCSUM,TXCSUM inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 nd6 options=3PERFORMNUD,ACCEPT_RTADV tun0: flags=8051UP,POINTOPOINT,RUNNING,MULTICAST metric 0 mtu 1500 options=8LINKSTATE inet 10.0.0.1 -- 10.0.0.2 netmask 0xff00 Opened by PID 767 Since there is no mention of ath0, I did not expect creating the wlan0 pseudo-device would be a simple matter, and I was right : # ifconfig wlan0 create wlandev ath0 ifconfig: SIOCIFCREATE2: Device not configured Manually trying to create the pseudo-device ath0 presents equally unpleasant output : # ifconfig ath0 create ifconfig: SIOCIFCREATE2: Invalid argument pciconf does show my device, but I do not know how to make use of the information (please refer the last few lines of the output) : # pciconf -lv hostb0@pci0:0:0:0:class=0x06 card=0x06491025 chip=0x01048086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' class = bridge subclass = HOST-PCI vgapci0@pci0:0:2:0:class=0x03 card=0x06491025 chip=0x01068086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' class = display subclass = VGA none0@pci0:0:22:0:class=0x078000 card=0x06491025 chip=0x1e3a8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = simple comms ehci0@pci0:0:26:0:class=0x0c0320 card=0x06491025 chip=0x1e2d8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = serial bus subclass = USB hdac0@pci0:0:27:0:class=0x040300 card=0x06491025 chip=0x1e208086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = multimedia subclass = HDA pcib1@pci0:0:28:0:class=0x060400 card=0x06491025 chip=0x1e108086 rev=0xc4 hdr=0x01 vendor = 'Intel Corporation' class = bridge subclass = PCI-PCI pcib2@pci0:0:28:1:class=0x060400 card=0x06491025 chip=0x1e128086 rev=0xc4 hdr=0x01 vendor = 'Intel Corporation' class = bridge subclass = PCI-PCI ehci1@pci0:0:29:0:class=0x0c0320 card=0x06491025 chip=0x1e268086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = serial bus subclass = USB isab0@pci0:0:31:0:class=0x060100 card=0x06491025 chip=0x1e5e8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = bridge subclass = PCI-ISA atapci0@pci0:0:31:2:class=0x01018f card=0x06491025 chip=0x1e018086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = mass storage subclass = ATA none1@pci0:0:31:3:class=0x0c0500 card=0x06491025 chip=0x1e228086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = serial bus subclass = SMBus atapci1@pci0:0:31:5:class=0x010185 card=0x06491025 chip=0x1e098086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' class = mass storage subclass = ATA bge0@pci0:2:0:0:class=0x02 card=0x06471025 chip=0x16b514e4 rev=0x10 hdr=0x00 vendor = 'Broadcom Corporation' class
Re: Problem with connecting FreeBSD 8.3 to wireless network
On Mon, 29 Oct 2012, Manish Jain wrote: Those in a position to help but smugly choose not to may soon start experiencing a dramatic decline in their good fortunes. I'm not in a position to help, but I can explain a couple of things. # kldload ath kldload: can't load ath: File exists # kldload wlan_tkip kldload: can't load wlan_tkip: File exists This tells you that the module in question has already been loaded, or is present in the kernel. [snip] none5@pci0:3:0:0: class=0x028000 card=0x661711ad chip=0x0032168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' class = network The 'none..' tells you that no driver was attached to the device. I suspect that Alexander Kapshuk's reply is relevant here: that your Atheros card is not supported by the driver. I know it's not much help, but maybe it's nonzero. Good luck. -- Chris Hill ch...@monochrome.org ** [ Busy Expunging / ] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: No sound from speaker, using Realtek ALC269 and snd_hda
Thank you, Alexander! On Sun, Oct 28, 2012 at 8:28 PM, Alexander Motin m...@freebsd.org wrote: On 28.10.2012 17:12, Big Yuuta wrote: hint.hdaa.0.nid20.config=as=1 seq=0 device=Speaker hint.hdaa.0.nid26.config=as=1 seq=15 device=Headphones hint.hdaa.0.nid18.config=as=2 seq=0 As I see, these three hints are replicating existing configuration and effectively useless. You're absolutely right! These are the same as the original ones. #hint.hdaa.0.gpio_config=0=set hint.hdaa.0.config=forcestereo,ivref50,ivref80,ivref100,ivref,vref hint.pcm.0.config=gpio0,gpio1,gpio2,gpio3,gpio4,gpio5,gpio6,gpio7 hint.pcm.0.vol=100 This is my n'th attempt, I pretty tried everything I could imagine. Here's my verbose dmesg http://dpaste.com/818967/plain/ Am I missing something? Is my understanding of pinouts correct? CODEC configuration looks good and I see no problems in driver output. I think most likely problem is in CODEC wiring and power amplifier. Your CODEC has two GPIO lines and EAPD line. That gives 8 possible combinations. I would recommend you to try them all. GPIOs, as you tried could be set with hint.hdaa.0.gpio_config tunable. EAPD line can be controlled (0 or 100) by the ogain mixer control. You mean combinations like: hint.hdaa.0.gpio_config=0=set 1=set 2=set Where the values could be set or keep? But then again, the man also cites clear, disable, input. So that'd make more than 8 possible permutations? Or is it something else? Can you please give me an example? Also, can I, after booting, just try with: kenv hint.hdaa.0.gpio_config=0=set 1=set 2=set kdunload snd_hda.ko kdload snd_hda.ko or should I reboot each time? Unluckily with this output I can't completely identify your system to check what Linux does for it. Could you send me `devinfo -vr` output. Sure! I'm attaching it Again thanks for all your work on the subject, and your help! P.S. Here's some extra output from dmesg when I set: dev.hdac.0.pindump=1 hdaa0: Dumping AFG pins: hdaa0: nid 0xas seq device conn jackloccolor misc hdaa0: 18 99a30920 2 0 Mic Fixed ATAPI OnboardUnknown 9 hdaa0: Caps: IN hdaa0: 20 99130110 1 0 Speaker Fixed ATAPI OnboardUnknown 1 hdaa0: Caps:OUTEAPD Sense: 0x (disconnected) hdaa0: 23 41f0 15 0 Speaker None 1/8 Rear Black 1 DISA hdaa0: Caps:OUT hdaa0: 24 41f0 15 0 Speaker None 1/8 Rear Black 1 DISA hdaa0: Caps: IN OUT VREF Sense: 0x (disconnected) hdaa0: 25 41f0 15 0 Speaker None 1/8 Rear Black 1 DISA hdaa0: Caps: IN VREF Sense: 0x (disconnected) hdaa0: 26 0121441f 1 15 HeadphonesJack 1/8 Rear Green 4 hdaa0: Caps: IN OUT HP Sense: 0x (disconnected) hdaa0: 27 41f0 15 0 Speaker None 1/8 Rear Black 1 DISA hdaa0: Caps: IN OUT Sense: 0x (disconnected) hdaa0: 30 41f0 15 0 Speaker None 1/8 Rear Black 1 DISA hdaa0: Caps:OUT Sense: 0x (disconnected) hdaa0: 33 41f0 15 0 Speaker None 1/8 Rear Black 1 DISA hdaa0: Caps:OUT HP Sense: 0x (disconnected) hdaa0: NumGPIO=2 NumGPO=0 NumGPI=0 GPIWake=0 GPIUnsol=1 hdaa0: GPIO0: disabled hdaa0: GPIO1: disabled nexus0 apic0 ram0 I/O memory addresses: 0x0-0x9fbff 0x10-0x7f68 acpi0 Interrupt request lines: 9 I/O ports: 0x10-0x1f 0x22-0x3f 0x44-0x4d 0x50-0x5e 0x63 0x65 0x67-0x6f 0x72-0x7f 0x80 0x84-0x86 0x88 0x8c-0x8e 0x90-0x9f 0xa2-0xbf 0xe0-0xef 0x25c-0x25f 0x380-0x383 0x400-0x41f 0x480-0x4bf 0x4d0-0x4d1 0x800-0x87f I/O memory addresses: 0xc-0xc 0xe-0xf 0xe000-0xefff 0xfec0-0xfec00fff 0xfed14000-0xfed19fff 0xfed1c000-0xfed1 0xfed2-0xfed3 0xfed5-0xfed8 0xfed9-0x acpi_ec0 pnpinfo _HID=PNP0C09 _UID=0 at handle=\_SB_.PCI0.SBRG.EC0_ I/O ports: 0x62 0x66 cpu0 pnpinfo _HID=none _UID=0 at handle=\_PR_.P001 ACPI I/O ports: 0x814 acpi_throttle0 est0 p4tcc0 acpi_perf0 cpufreq0 cpu1 pnpinfo _HID=none _UID=0 at handle=\_PR_.P002 ACPI I/O ports: 0x814 acpi_throttle1 est1 p4tcc1 acpi_perf1 cpufreq1 pcib0 pnpinfo _HID=PNP0A08 _UID=0 at handle=\_SB_.PCI0 I/O ports: 0xcf8-0xcff pci0 hostb0 pnpinfo vendor=0x8086 device=0xa010 subvendor=0x1043 subdevice=0x83ac class=0x06 at
Re: No sound from speaker, using Realtek ALC269 and snd_hda
On 28.10.2012 22:09, Big Yuuta wrote: CODEC configuration looks good and I see no problems in driver output. I think most likely problem is in CODEC wiring and power amplifier. Your CODEC has two GPIO lines and EAPD line. That gives 8 possible combinations. I would recommend you to try them all. GPIOs, as you tried could be set with hint.hdaa.0.gpio_config tunable. EAPD line can be controlled (0 or 100) by the ogain mixer control. You mean combinations like: hint.hdaa.0.gpio_config=0=set 1=set 2=set As I've told, there are only two GPIO pins, so only 0=X 1=Y, plus ogain mixer control. Where the values could be set or keep? But then again, the man also cites clear, disable, input. So that'd make more than 8 possible permutations? Or is it something else? Can you please give me an example? GPIO pins are bidirectional, but I have doubt that input or high impedance (disable) state could be used to control something. keep is also useless, as by default these pins are disabled. So you have only set and clear. Also, can I, after booting, just try with: kenv hint.hdaa.0.gpio_config=0=set 1=set 2=set kdunload snd_hda.ko kdload snd_hda.ko Yes, that should work. or should I reboot each time? I don't think it is required. -- Alexander Motin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: No sound from speaker, using Realtek ALC269 and snd_hda
On Sun, Oct 28, 2012 at 9:42 PM, Alexander Motin m...@freebsd.org wrote: On 28.10.2012 22:09, Big Yuuta wrote: CODEC configuration looks good and I see no problems in driver output. I think most likely problem is in CODEC wiring and power amplifier. Your CODEC has two GPIO lines and EAPD line. That gives 8 possible combinations. I would recommend you to try them all. GPIOs, as you tried could be set with hint.hdaa.0.gpio_config tunable. EAPD line can be controlled (0 or 100) by the ogain mixer control. You mean combinations like: hint.hdaa.0.gpio_config=0=set 1=set 2=set As I've told, there are only two GPIO pins, so only 0=X 1=Y, plus ogain mixer control. So that would be: hint.hdaa.0.gpio_config=0=set 1=set hint.hdaa.0.gpio_config=0=set 1=clear hint.hdaa.0.gpio_config=0=clear 1=set hint.hdaa.0.gpio_config=0=clear 1=clear which I try with: mixer ogain 0:0 mixer ogain 100:100 I'm going to check once again, but I think that unfortunately that didn't work. I hope that I forgot a combination! Thanks again, Alexander ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: No sound from speaker, using Realtek ALC269 and snd_hda
Unfortunately, trying with the different combinations didn't work. I wrote this tiny script just to make sure I'm not forgetting a case: #!/bin/sh echo testing with: $1 - $2; kenv hint.hdaa.0.gpio_config=0=$1 1=$2; kldunload snd_hda.ko; kldload snd_hda.ko; mplayer song.mp3; and I run it like this: ./test.sh set set ./test.sh set clear ./test.sh clear set ./test.sh clear clear And nothing came out of the speaker, alas :( What's strange is that the speaker actually works with OSS from ports, but when I use it (OSS) with mplayer it crashes the whole system whenever I try to skip in a video/audio file On Sun, Oct 28, 2012 at 9:58 PM, Big Yuuta init...@gmail.com wrote: On Sun, Oct 28, 2012 at 9:42 PM, Alexander Motin m...@freebsd.org wrote: On 28.10.2012 22:09, Big Yuuta wrote: CODEC configuration looks good and I see no problems in driver output. I think most likely problem is in CODEC wiring and power amplifier. Your CODEC has two GPIO lines and EAPD line. That gives 8 possible combinations. I would recommend you to try them all. GPIOs, as you tried could be set with hint.hdaa.0.gpio_config tunable. EAPD line can be controlled (0 or 100) by the ogain mixer control. You mean combinations like: hint.hdaa.0.gpio_config=0=set 1=set 2=set As I've told, there are only two GPIO pins, so only 0=X 1=Y, plus ogain mixer control. So that would be: hint.hdaa.0.gpio_config=0=set 1=set hint.hdaa.0.gpio_config=0=set 1=clear hint.hdaa.0.gpio_config=0=clear 1=set hint.hdaa.0.gpio_config=0=clear 1=clear which I try with: mixer ogain 0:0 mixer ogain 100:100 I'm going to check once again, but I think that unfortunately that didn't work. I hope that I forgot a combination! Thanks again, Alexander ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: No sound from speaker, using Realtek ALC269 and snd_hda
On 28.10.2012 23:20, Big Yuuta wrote: Unfortunately, trying with the different combinations didn't work. I wrote this tiny script just to make sure I'm not forgetting a case: #!/bin/sh echo testing with: $1 - $2; kenv hint.hdaa.0.gpio_config=0=$1 1=$2; kldunload snd_hda.ko; kldload snd_hda.ko; mplayer song.mp3; and I run it like this: ./test.sh set set ./test.sh set clear ./test.sh clear set ./test.sh clear clear And nothing came out of the speaker, alas :( Alas. I'll just remind one more time about `mixer ogain`. Also check that pin sensing is working. Try to plug in/out headphones. With verbose messages enabled, you should see messages about that on console and in logs. What's strange is that the speaker actually works with OSS from ports, but when I use it (OSS) with mplayer it crashes the whole system whenever I try to skip in a video/audio file On Sun, Oct 28, 2012 at 9:58 PM, Big Yuuta init...@gmail.com wrote: On Sun, Oct 28, 2012 at 9:42 PM, Alexander Motin m...@freebsd.org wrote: On 28.10.2012 22:09, Big Yuuta wrote: CODEC configuration looks good and I see no problems in driver output. I think most likely problem is in CODEC wiring and power amplifier. Your CODEC has two GPIO lines and EAPD line. That gives 8 possible combinations. I would recommend you to try them all. GPIOs, as you tried could be set with hint.hdaa.0.gpio_config tunable. EAPD line can be controlled (0 or 100) by the ogain mixer control. You mean combinations like: hint.hdaa.0.gpio_config=0=set 1=set 2=set As I've told, there are only two GPIO pins, so only 0=X 1=Y, plus ogain mixer control. So that would be: hint.hdaa.0.gpio_config=0=set 1=set hint.hdaa.0.gpio_config=0=set 1=clear hint.hdaa.0.gpio_config=0=clear 1=set hint.hdaa.0.gpio_config=0=clear 1=clear which I try with: mixer ogain 0:0 mixer ogain 100:100 I'm going to check once again, but I think that unfortunately that didn't work. I hope that I forgot a combination! Thanks again, Alexander -- Alexander Motin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Why RELENG_9 branch is labeled as PRERELEASE and freebsd.org says FreeBSD is currently at 9.1-RC2 ?
Le Sun, 28 Oct 2012 11:48:19 -0700, Yuri y...@rawbw.com a écrit : RELENG_9 should be called 9-STABLE, if you want 9.1 use RELENG_9_1 Hm, if they wanted to keep RELENG_9 as stable 9.X branch, why then 9.1-PRERELEASE is there? Is PRERELEASE considered more stable than RC? This looks strange to me. This is because of the release process. At some point (beta) the stable branch (RELENG_9 here) is named -PRERELEASE. After (for release candidate) a new branch (RELENG_9_1) is created and named 9.1-XXX. This branch will be the 9.1 release and changes should be only bug fixes. RELENG_9 continues its own way. So yes, RELENG_9 should be named 9-STABLE. That will be fixed after the release. I guess nobody takes the time to change the name or they are too busy with the release of 9.1. Regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: No sound from speaker, using Realtek ALC269 and snd_hda
On Sun, Oct 28, 2012 at 10:34 PM, Alexander Motin m...@freebsd.org wrote: On 28.10.2012 23:20, Big Yuuta wrote: Unfortunately, trying with the different combinations didn't work. I wrote this tiny script just to make sure I'm not forgetting a case: #!/bin/sh echo testing with: $1 - $2; kenv hint.hdaa.0.gpio_config=0=$1 1=$2; kldunload snd_hda.ko; kldload snd_hda.ko; mplayer song.mp3; and I run it like this: ./test.sh set set ./test.sh set clear ./test.sh clear set ./test.sh clear clear And nothing came out of the speaker, alas :( Alas. I'll just remind one more time about `mixer ogain`. My bad, I forgot to tell you that I tried it with mixer ogain 0:0 and mixer ogain 100:100 for every case. Also check that pin sensing is working. Try to plug in/out headphones. With verbose messages enabled, you should see messages about that on console and in logs. Ah, yes, I should give this a try! Thank you so much, Alexander! I'll keep you informed :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Audacity Upgrade 1.x - 2.x Craps Out
I am trying an upgrade to audacity (1.x to 2.x) but it has crapped out; nothing in updating about audacity issues. http://pastebin.com/WxPvgKXf I can live with 1.x for now (as I have work I'm 5 days behind on already and need to get caught up), but I would like to return to using 2.x (I was using 2.x in Ubuntu). I'm doing my best to move all my work over to FreeBSD. -- Yours in Christ, Joseph A Nagy Jr Whoever loves instruction loves knowledge, But he who hates correction is stupid. -- Proverbs 12:1 Emails are not formal business letters, whatever businesses may want. Original content CopyFree (F) under the OWL http://owl.apotheon.org signature.asc Description: OpenPGP digital signature
ipod | ifuse
Hello, I have tried to reach IOS6 from fuse on FreeBSD9. It seems like a bug and am not sure how to report it: Unknown USB device: vendor 0x05ac product 0x129e bus uhub1 Darrel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
VIA Pico-ITX ethernet sound issues
I have a VIA Pico-ITX system (the original Artigo system) and have installed 9.0 RELEASE. The BIOS has been updated to the most recent release. With ACPI enabled, dmesg shows the boot process finds the sound controller hdac0: VIA VT8251/8237A High Definition Audio Controller mem 0x9fffc000-0x9fff irq 17 at device 1.0 on pci128 pcm0: HDA VIA VT1708_8 PCM #0 Analog at cad 0 nid 1 on hdac0 pcm1: HDA VIA VT1708_8 PCM #1 Digital at cad 0 nid 1 on hdac0 but does not find the ethernet interface. I see no reference at all. With ACPI disabled, dmesg shows it finds the ethernet interface vr0: VIA VT6105 Rhine III 10/100BaseTX port 0xde00-0xdeff mem 0xdfeff000-0xdfeff0ff irq 18 at device 6.0 on pci2 vr0: Quirks: 0x0 vr0: Revision: 0x8b and shows a problem with what I think is the sound controller unknown: PNP0c01 can't assign resources (memory) unknown: PNP0c02 can't assign resources (memory) I'm hoping to use this small system to create an internet radio and clearly need both ethernet and audio. Any ideas on how to get both ethernet and audio working? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
LED rope lights
Hello, We are glad you are on the market for led lightings. Light Source Industrial Limited here,main products are LED spots Lamp, and Bulbs,Tube Light, LED panel light, LED tree light, LED Christmas lights, and LED down light,LED acrylic motif lights, Please visit our company website: www.cn-lightsource.com; if any item you are interested in, please contact us at any time. I look forward to hearing from you! Best regards, Alison zhang Light Source Industrial Limited Tel: 0086 7525536816 0086 75533696626 Mobile: 008615347451788 Email: alisonzhan...@163.com Hotmail: chinalightsou...@hotmail.com www.cn-lightsource.com skype: alisonzhangcn1 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: NVIDIA proprietary driver error
On 26/10/2012 19:06, Ashkan Rahmani wrote: i have an option in bios boot vga controller selection for which have 2 options windows 7/vista and reserved. Thank you for reply, That xorg.conf generetaed by Xorg -configure. yes I tried nvidia-xsetting. On start I got error which says There is not any compatible device detected or some things like this. nvidia-xconfig generate very simple xorg.cong with just one screen or monitor, sets nvidia as driver, but not work. I got same error (in /var/log/xorg.0.log) actually: no device detected. Beside all of this stuffs, There is a point, BusID, Xorg -configure set BusID to PCI:1:0:0 and nvidia-xconfig set it PCI:0:2:0 Because Xorg generated xorg.conf works (of course with incorrect resolution and with lag) I changed BusID in nvidia-xconfig PCI:0:2:0 to PCI:1:0:0. not worked! May be error come from NVIDIA Optimus. Did changing the bios settings help? I have come across some more info - it is an issue with optimus which is a technology to allow switching between lower power usage intel graphics and higher performing nvidia graphics. I didn't hear any certainty about turning it off in bios but there is a record of linux not supporting it. A project called bumblebee targets getting support on linux. The two busid's reflect the intel and nvidia devices - did you try removing nvidia and using only the intel settings? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Famp Server
Dear All, I freel freebsd is very good in networking server but it make work hard for compiling the Famp package (Freebsd, apache, mysql, php) i would like to ask the developers to compile a package that its a one select and install which will do everything for the famp server rather than downloading selecting extensions, installing this and that exectra. thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
