Re: [gentoo-user] alsa problem
2007/10/13, Hans-Werner Hilse [EMAIL PROTECTED]: Hi, On Sat, 13 Oct 2007 22:23:35 +0800 Chuanwen Wu [EMAIL PROTECTED] wrote: Yes,both my Windows XP and another linux os Redflag have sound. Is there anyway that I can use the Redflag's modules to driver my gentoo? Only by using its kernel, too. Then you would just copy the kernel (and initrd, if needed, but this might be a bag of problems if the initrd depends on stuff from the base system) from /boot and the according module tree from /lib/modules. Oh, I just forgot that the Redflag is a i386 OS but the gentoo is amd64 OS. So gentoo can't use the Redflag's modules and kernel(vice versa). I think it would at least be interesting what /proc/asound/version is like on the redflag distro. Also it would be interesting if they use in-kernel ALSA or separate drivers and if the latter is the case, then they might provide source packages -- which potentially include patches that add support for your device. Let 's have a look at the Redflag's alsa information:(all the operations I did below were in the Redflag OS) # cat /proc/asound/cards 0 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0xfe9fc000 irq 20 ***in gentoo it is irq 21 here. ** # cat /proc/asound/devices 0: [ 0] : control 1:: sequencer 16: [ 0- 0]: digital audio playback 17: [ 0- 1]: digital audio playback 24: [ 0- 0]: digital audio capture 33:: timer # cat /proc/asound/version Advanced Linux Sound Architecture Driver Version 1.0.14rc3. Compiled on Jul 25 2007 for kernel 2.6.22.1-9 (SMP). I notice that the alsa version is 1.0.14rc3 which is the unstable one before 1.0.14. But I tried 1.0.14rc3, and the result is as similar as when I use in-kernel alsa driver. # grep SND /boot/config-2.6.22.1-9 CONFIG_SND=m CONFIG_SND_TIMER=m CONFIG_SND_PCM=m CONFIG_SND_HWDEP=m CONFIG_SND_RAWMIDI=m CONFIG_SND_SEQUENCER=m CONFIG_SND_SEQ_DUMMY=m CONFIG_SND_OSSEMUL=y CONFIG_SND_MIXER_OSS=m CONFIG_SND_PCM_OSS=m CONFIG_SND_PCM_OSS_PLUGINS=y CONFIG_SND_SEQUENCER_OSS=y CONFIG_SND_RTCTIMER=m CONFIG_SND_SEQ_RTCTIMER_DEFAULT=y CONFIG_SND_DYNAMIC_MINORS=y # CONFIG_SND_SUPPORT_OLD_API is not set CONFIG_SND_VERBOSE_PROCFS=y # CONFIG_SND_VERBOSE_PRINTK is not set # CONFIG_SND_DEBUG is not set CONFIG_SND_MPU401_UART=m CONFIG_SND_OPL3_LIB=m CONFIG_SND_OPL4_LIB=m CONFIG_SND_VX_LIB=m CONFIG_SND_AC97_CODEC=m CONFIG_SND_DUMMY=m CONFIG_SND_VIRMIDI=m CONFIG_SND_MTPAV=m CONFIG_SND_MTS64=m # CONFIG_SND_SERIAL_U16550 is not set CONFIG_SND_MPU401=m CONFIG_SND_PORTMAN2X4=m CONFIG_SND_CS4231_LIB=m CONFIG_SND_ADLIB=m # CONFIG_SND_AD1816A is not set # CONFIG_SND_AD1848 is not set # CONFIG_SND_ALS100 is not set # CONFIG_SND_AZT2320 is not set # CONFIG_SND_CMI8330 is not set # CONFIG_SND_CS4231 is not set # CONFIG_SND_CS4232 is not set CONFIG_SND_CS4236=m # CONFIG_SND_DT019X is not set # CONFIG_SND_ES968 is not set # CONFIG_SND_ES1688 is not set CONFIG_SND_ES18XX=m # CONFIG_SND_GUSCLASSIC is not set # CONFIG_SND_GUSEXTREME is not set # CONFIG_SND_GUSMAX is not set # CONFIG_SND_INTERWAVE is not set # CONFIG_SND_INTERWAVE_STB is not set CONFIG_SND_OPL3SA2=m # CONFIG_SND_OPTI92X_AD1848 is not set # CONFIG_SND_OPTI92X_CS4231 is not set # CONFIG_SND_OPTI93X is not set CONFIG_SND_MIRO=m # CONFIG_SND_SB8 is not set CONFIG_SND_SB16=m CONFIG_SND_SBAWE=m # CONFIG_SND_SB16_CSP is not set # CONFIG_SND_SGALAXY is not set # CONFIG_SND_SSCAPE is not set # CONFIG_SND_WAVEFRONT is not set CONFIG_SND_AD1889=m CONFIG_SND_ALS300=m CONFIG_SND_ALS4000=m CONFIG_SND_ALI5451=m CONFIG_SND_ATIIXP=m CONFIG_SND_ATIIXP_MODEM=m CONFIG_SND_AU8810=m CONFIG_SND_AU8820=m CONFIG_SND_AU8830=m CONFIG_SND_AZT3328=m CONFIG_SND_BT87X=m # CONFIG_SND_BT87X_OVERCLOCK is not set CONFIG_SND_CA0106=m CONFIG_SND_CMIPCI=m CONFIG_SND_CS4281=m CONFIG_SND_CS46XX=m CONFIG_SND_CS46XX_NEW_DSP=y CONFIG_SND_CS5535AUDIO=m CONFIG_SND_DARLA20=m CONFIG_SND_GINA20=m CONFIG_SND_LAYLA20=m CONFIG_SND_DARLA24=m CONFIG_SND_GINA24=m CONFIG_SND_LAYLA24=m CONFIG_SND_MONA=m CONFIG_SND_MIA=m CONFIG_SND_ECHO3G=m CONFIG_SND_INDIGO=m CONFIG_SND_INDIGOIO=m CONFIG_SND_INDIGODJ=m CONFIG_SND_EMU10K1=m CONFIG_SND_EMU10K1X=m CONFIG_SND_ENS1370=m CONFIG_SND_ENS1371=m CONFIG_SND_ES1938=m CONFIG_SND_ES1968=m CONFIG_SND_FM801=m CONFIG_SND_FM801_TEA575X_BOOL=y CONFIG_SND_FM801_TEA575X=m CONFIG_SND_HDA_INTEL=m CONFIG_SND_HDSP=m CONFIG_SND_HDSPM=m CONFIG_SND_ICE1712=m CONFIG_SND_ICE1724=m CONFIG_SND_INTEL8X0=m CONFIG_SND_INTEL8X0M=m CONFIG_SND_KORG1212=m CONFIG_SND_KORG1212_FIRMWARE_IN_KERNEL=y CONFIG_SND_MAESTRO3=m CONFIG_SND_MAESTRO3_FIRMWARE_IN_KERNEL=y CONFIG_SND_MIXART=m CONFIG_SND_NM256=m CONFIG_SND_PCXHR=m CONFIG_SND_RIPTIDE=m CONFIG_SND_RME32=m CONFIG_SND_RME96=m CONFIG_SND_RME9652=m CONFIG_SND_SONICVIBES=m CONFIG_SND_TRIDENT=m CONFIG_SND_VIA82XX=m CONFIG_SND_VIA82XX_MODEM=m CONFIG_SND_VX222=m CONFIG_SND_YMFPCI=m CONFIG_SND_YMFPCI_FIRMWARE_IN_KERNEL=y CONFIG_SND_AC97_POWER_SAVE=y CONFIG_SND_USB_AUDIO=m
Re: [gentoo-user] alsa problem
Hi, On Sun, 14 Oct 2007 15:25:12 +0800 Chuanwen Wu [EMAIL PROTECTED] wrote: Yes,both my Windows XP and another linux os Redflag have sound. Is there anyway that I can use the Redflag's modules to driver my gentoo? Only by using its kernel, too. Then you would just copy the kernel (and initrd, if needed, but this might be a bag of problems if the initrd depends on stuff from the base system) from /boot and the according module tree from /lib/modules. Oh, I just forgot that the Redflag is a i386 OS but the gentoo is amd64 OS. So gentoo can't use the Redflag's modules and kernel(vice versa). Hm, I see. I think the different IRQs are not really worth mentioning, since they get automatically assigned. All that fooling around with different versions of ALSA didn't help much, so it boils down to - either it's a modified kernel what Redflag uses (I agree they use in-kernel ALSA), or - it's really an AMD64 vs. i386 matter. When I do #modprobe snd_hda_intel(or #alsaconf), I can see the message below appending to the ouput of dmesg: ACPI: PCI Interrupt :00:1b.0[A] - GSI 21 (level, low) - IRQ 21 PCI: Setting latency timer of device :00:1b.0 to 64 stac92xx_auto_fill_dac_nids: No available DAC for pin 0x0 I had a really deep look into /usr/src/linux/sound/pci/hda/patch_sigmatel.c, but nothing really rings a bell. I think this indicates the problem (since nothing will get routed correctly when it fails on the first pin, 0). But I don't think the problem is located in the function that prints this error. In any case, after printing that error, the initialization of the pin routing fails with an error. So it's definately a driver issue, not something about machine configuration. In any case, I think you should report to the alsa mailinglist. FWIW, I can't currently access www.alsa-project.org either. You can find the subscription interface here: https://lists.sourceforge.net/lists/listinfo/alsa-user I'm sorry that after all this there isn't really much success. One could certainly do more debugging by comparing a 32bit vs a 64bit kernel with the exact same config otherwise. That might actually prove that there's something fishy. -hwh -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] update-grub? I have no such thing.
On Sonntag, 14. Oktober 2007, Mark Shields wrote: And no, you don't need it. Writing and maintaining your own menu.lst ( grub.conf) works just fine. well, I have a 'vmlinuz' entry and a 'vmlinuz.old' entry. Since make install creates the proper symlinks there is no grub.conf/menu.lst editing needed. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] alsa problem
2007/10/14, Hans-Werner Hilse [EMAIL PROTECTED]: Hi, On Sun, 14 Oct 2007 15:25:12 +0800 Chuanwen Wu [EMAIL PROTECTED] wrote: Yes,both my Windows XP and another linux os Redflag have sound. Is there anyway that I can use the Redflag's modules to driver my gentoo? Only by using its kernel, too. Then you would just copy the kernel (and initrd, if needed, but this might be a bag of problems if the initrd depends on stuff from the base system) from /boot and the according module tree from /lib/modules. Oh, I just forgot that the Redflag is a i386 OS but the gentoo is amd64 OS. So gentoo can't use the Redflag's modules and kernel(vice versa). Hm, I see. I think the different IRQs are not really worth mentioning, since they get automatically assigned. All that fooling around with different versions of ALSA didn't help much, so it boils down to - either it's a modified kernel what Redflag uses (I agree they use in-kernel ALSA), or - it's really an AMD64 vs. i386 matter. When I do #modprobe snd_hda_intel(or #alsaconf), I can see the message below appending to the ouput of dmesg: ACPI: PCI Interrupt :00:1b.0[A] - GSI 21 (level, low) - IRQ 21 PCI: Setting latency timer of device :00:1b.0 to 64 stac92xx_auto_fill_dac_nids: No available DAC for pin 0x0 I had a really deep look into /usr/src/linux/sound/pci/hda/patch_sigmatel.c, but nothing really rings a bell. I think this indicates the problem (since nothing will get routed correctly when it fails on the first pin, 0). But I don't think the problem is located in the function that prints this error. In any case, after printing that error, the initialization of the pin routing fails with an error. So it's definately a driver issue, not something about machine configuration. In any case, I think you should report to the alsa mailinglist. FWIW, I can't currently access www.alsa-project.org either. You can find the subscription interface here: https://lists.sourceforge.net/lists/listinfo/alsa-user I'm sorry that after all this there isn't really much success. One I am really appreciate for your patience and help. And I have learned some ways to detect and trace my os's status from you. could certainly do more debugging by comparing a 32bit vs a 64bit kernel with the exact same config otherwise. That might actually prove that there's something fishy. The 64bit os support is not very well at the moment. After I switch to 64bit os, I have found some applications and driver did not support 64bit os,like Eclipse. But thing will get better and better. -hwh -- [EMAIL PROTECTED] mailing list -- wcw -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] SSH: No X11 forwarding any longer
I wrote: Yes. Well, I usually have forwarding enabled automatically in /etc/ssh/ssh_config, but I always try with -X or -Y anyway. What is the actual error from the client? $DISPLAY is not set. But I notice a change since yesterday: I now get this warning: Warning: No xauth data; using fake authentication data for X11 forwarding. Don't know what causes this, I emerged a couple of things due to world update and (still!) some problems with the expat update, but nothing which I would think has to do with ssh. Anyway, DISPLAY still does not get set. I sort of found the solution to my problem, but still do not fully understand what happened. First I thought I had to add X to the server's use flags. Looked like I then had DISPLAY set, but still got the warning about missing xauth data. When trying to start an X application, I got this: Xlib: connection to localhost:10.0 refused by server Xlib: Invalid MIT-MAGIC-COOKIE-1 key xterm Xt error: Can't open display: localhost:10.0 Then I looked at the configs again, and in the man page for ssh_config I finally found this: XAuthLocation Specifies the full pathname of the xauth(1) program. The default is /usr/openwin/bin/xauth. /usr/openwin? I added XAuthLocation /usr/bin/xauth to the client's /etc/ssh/ssh_config, and now all was fine. Even without the X use flag. Looking at a gentoo box I did not update for a while, I see the man page there tells the default location is /usr/bin/xauth. Okay, now I know this change is responsible. But why aren't forum and this list flooded with people experiencing the same problem as me? Alex -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Emerging java with gcj
Florian Philipp wrote: I've noticed that the gcj use flag is not enabled by default and therefore all java code is compiled to byte code instead of native binaries, am I correct? gcj can compile java code directly to machine code, and I'm pretty sure that the Sun compiler just compiles to byte code. I have no experience with gcj though, so I can't answer your second question... I wonder how I can change that. Just re-emerge gcc with USE=gcj and all packages containing java code? Is it even a good idea? -- Randy Barlow http://electronsweatshop.com -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Emerging java with gcj
On 10/14/07, Randy Barlow [EMAIL PROTECTED] wrote: Florian Philipp wrote: I've noticed that the gcj use flag is not enabled by default and therefore all java code is compiled to byte code instead of native binaries, am I correct? gcj can compile java code directly to machine code, and I'm pretty sure that the Sun compiler just compiles to byte code. I have no experience with gcj though, so I can't answer your second question... I wonder how I can change that. Just re-emerge gcc with USE=gcj and all packages containing java code? Is it even a good idea? Probably not, but you could always try it and report back to the list... :o) Nothing that needs to work with a class loader, like applets do, will work. I would expect some problems with introspection. Moreover, last I tried it, there were buckets of incompatibility with the Java libraries. Maybe it's more mature now. Kevin O'Gorman, PhD
Re: [gentoo-user] Emerging java with gcj
Hi, On Thu, 11 Oct 2007 13:59:23 +0200 Florian Philipp [EMAIL PROTECTED] wrote: I've noticed that the gcj use flag is not enabled by default and therefore all java code is compiled to byte code instead of native binaries, am I correct? I think the gcj flag toggles if java support is added at all. gcj itself can compile to bytecode (class files) or native binary code. In order to generate java bytecode, the flag -C has to be specified. I wonder how I can change that. Just re-emerge gcc with USE=gcj and all packages containing java code? Is it even a good idea? It will take a lot more time when emerging gcc. Whether you need it depends on what you are planning to do with it... If you just need a full blown JDK, the gcj might not be exactly what you want. Gcj also brings the gij interpreter, which can be used to run java bytecode. -hwh -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] SSH: No X11 forwarding any longer
On Sunday 14 October 2007, Alex Schuster wrote: Then I looked at the configs again, and in the man page for ssh_config I finally found this: XAuthLocation Specifies the full pathname of the xauth(1) program. The default is /usr/openwin/bin/xauth. /usr/openwin? I added XAuthLocation /usr/bin/xauth to the client's /etc/ssh/ssh_config, and now all was fine. Even without the X use flag. Looking at a gentoo box I did not update for a while, I see the man page there tells the default location is /usr/bin/xauth. Okay, now I know this change is responsible. But why aren't forum and this list flooded with people experiencing the same problem as me? Perhaps because most use vanilla ssh to manage servers? I have every now and then used an ssh tunnel to forward VNC connections, but that is exceptional as far as my usage of ssh goes. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] loopback into gentoo iptables
On 05/10/2007, Hans-Werner Hilse [EMAIL PROTECTED] wrote: Hi, On Fri, 5 Oct 2007 10:42:42 -0500 Walter Willis [EMAIL PROTECTED] wrote: I have modem asdl zyxel 660 and activate loopback with command: ip nat loopback on Where do you enter that and why? What is the thing _you_ call a loopback? On what device or machine does it exist? You don't seem to be talking about the ifup tool (since you talk about ip, which however does not know the nat mode?!?), and you don't seem to be talking about the lo device either. the ask is: it is into gentoo linux with iptables ? Errm, again: What? Setting up you loopback device on gentoo is done automatically by /etc/init.d/net.lo. Should be run on bootup by rc, check rc-update show. Setting up NAT works using a sysctl (or the procfs). Restricting the NAT works using iptables. the compiler module especial for function? E Again, not sure what you are asking here... Yes, you need kernel modules for both NAT to work and as well netfilter modules for the chains and targets and matches you want to use with iptables. They don't really have to be modules, you can compile them statically into the kernel as well. If unsure, rephrase your question -- and be a bit more verbose on what you intend to do... A bit more information might as well cure lack of proper vocabulary... Give examples, try to describe the setting. My telepathic abilities are getting rusty these days, but if guessing is allowed I think that the OP wanted to set up gentoo so that he could access the Zyxel router's firewall and modify its rules, from the Gentoo desktop. Either that, or he's thinking of building an embedded image for Zyxel?! More info would no doubt help. If not anything else, tell us what Zyxel can and cannot do - if it allows ssh access to its OS, then you may be able to set up firewall builder on the Gentoo box and use that to access/setup the Zyxel firewall. If you are running OpenWRT (not sure if this would run on Zyxel, but just don't stop me guessing now) you should be able to cook something so that firewall builder could hook into it. Best of luck, -- Regards, Mick -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] update-grub? I have no such thing.
On 10/14/07, Volker Armin Hemmann [EMAIL PROTECTED] wrote: On Sonntag, 14. Oktober 2007, Mark Shields wrote: And no, you don't need it. Writing and maintaining your own menu.lst ( grub.conf) works just fine. well, I have a 'vmlinuz' entry and a 'vmlinuz.old' entry. Since make install creates the proper symlinks there is no grub.conf/menu.lst editing needed. -- [EMAIL PROTECTED] mailing list Of course, those are symlinks. Specifying the actual kernel rather than a symlink ensures you're always booting from the correct kernel. I have one entry in grub.conf pointing to /vmlinuz , the others point to specific kernels. -- - Mark Shields
