Jump to content
funtoo forums

lambd0x

Members
  • Content Count

    16
  • Joined

  • Last visited

About lambd0x

  • Rank
    Member

Online

Personal

  • Location
    Brazil
  1. Yes, bash is a programming language: "https://stackoverflow.com/questions/28693737/is-bash-a-programming-language" ... langs able to write code in: Bash Julia Pascal Ada Lisp FORTRAN COBOL ... best lang: Bash Julia Pascal Ada Lisp FORTRAN COBOL ... want to learn: Bash Julia Pascal Ada Lisp FORTRAN COBOL
  2. lambd0x

    Screenshots

    Hi there, my everyday desktop is pretty stable now (currently it uses Awesome WM 4.2), but from time to time I change something here and there. Full description and pics are available through the link: https://github.com/lambd0x/Greenity
  3. lambd0x

    Firefox 57 and alsa

    Hi, noone. If you downgrade your firefox enough, let's say to 48.0. You can work with alsa, instead of pulse. This is a developer move from mozilla since pulseaudio provides better sound architecture for the project or so it was said. More information about it, see: -https://bugzilla.redhat.com/show_bug.cgi?id=1431371 -http://www.omgubuntu.co.uk/2017/03/firefox-52-no-sound-pulseaudio-alsa-linux
  4. lambd0x

    Libreoffice 5.4.2.2 fails to build close to the end

    Yes, last week it was made available the version 5.4.0. And since then I've been dealing with some kde packages, libreoffice failing output requested: https://bpaste.net/show/6247d76800e2 After rebuilding the suggest pkg, libreoffice built fine. Thx.
  5. lambd0x

    Libreoffice 5.4.2.2 fails to build close to the end

    Sorry, the build log seems to be the same. https://bpaste.net/show/8c283264e3e3
  6. lambd0x

    Libreoffice 5.4.2.2 fails to build close to the end

    Didn't work. Nothing changed.
  7. pkg flags: https://bpaste.net/show/a7f2f847de90 system settings: https://bpaste.net/show/7d6bdbd43237 build log: https://bpaste.net/show/4393b5c5c326
  8. lambd0x

    Can't boot on my Funtoo

    I noticed the that burned OS in my pen was odd. Took a friend's pen and tried again burning the same rescuecd and it worked out. Discovered too, that there are some .iso images that doesn't contain a valid MBR inside of it. To activate a correction to this a user can look for the isohybrid tool, then burn the .iso with dd in the pen. steps to sucessfully create a .iso with a valid MBR section "bootable pendrive" (it worked in all distros, even FreeBSD) that I've tried so far :) ) BTW: it you get interested in burning an OpenBSD OS I suggest you use image_name.fs (don't try to install it in a HP machine, its BIOS sucks :P ) with a pen in your notebook/PC... sudo emerge -av syslinux dosfstools isohybrid ~/path_to_your_iso lsblk (to identify which device is your pen) if you need to format your pen, rather use fat32: sudo mkfs.vfat -I path_to_your_pen then: sudo dd if=~/path_to_your_iso of=path_to_your_pen ("/dev/sdb" in my OS for e.g.) wait a few minutes to let it write to your pendrive, by the end of the process it shall report you its activities. notes: isohybrid is available under the syslinux package mkfs.vfat is available under the dosfstools package
  9. lambd0x

    Can't boot on my Funtoo

    Well, nevermind fellas. I solved here :) Thanks for those of you that spared your time reading my problem.
  10. lambd0x

    Can't boot on my Funtoo

    Yesterday night I performed a global upgrade of all my packages, noticed that it had genkernel updates included. The system upgraded nice and clean. I was doing my work while it worked. Turned off my PC after a depclean. But it seems that I had to eselect and boot-update the new kernel before doing that for now I can't boot to my OS anymore. Ok... Burned a System rescuecd 4.7.1 (the most recent on the install page). To try mounting my Funtoo installation directories and doing what I forgot last night. My problem is, everytime I boot this System rescuecd from my pen or any of the latest versions of it. I get at certain boot part of this cd what follows: 'Error: Cannot mount sysrcd.dat (none ....kernel details....)' and it gives me the basic terminal. (By the way, I'm currently having to use my Windows instalation, that's the only one that still works and burning the systemrescuecd with lili, (this kind of thing) is one of those situations that never gave any problem such as I reported... I'm stuck, for it never happened to me before. My computer hardware is very recent too. Can any of you guys possibly have an idea for me? Thanks in advance.
  11. lambd0x

    Alsa, no sound

    I managed to get everything working including Firefox. Thanks for all the help.
  12. lambd0x

    Alsa, no sound

    Got audio working without a .asoundrc in my desktop when using vlc. But not in my firefox.
  13. lambd0x

    Alsa, no sound

    Hi! So I need to create a .asoundrc defining the other card to play. I assume your .asoundrc doesn't work for me. Considering that I got these two: cat /proc/asound/cards 0 [HDMI ]: HDA-Intel - HDA Intel HDMI HDA Intel HDMI at 0xf0514000 irq 31 1 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xf0510000 irq 32 but what is the required syntax to set the correct card in this file? So far I tried what I read at gentoo/funtoo alsa page: nano .asoundrc pcm.!default { type hw card 0 } ctl.!default { type hw card 1 } Another thing, I saw at the same page that there is a command to test my audio card output. But it reports that the file or the directory doesn't exist, is it normal? aplay -D default test.wav aplay: main:722: audio open error: No such file or directory
  14. lambd0x

    Alsa, no sound

    Hi, I found a way to get alsamixer working and managed to change it's configurations. It does identify: default, HDA Intel HDMI(chip Intel haswell) and HDA Intel PCH(chip Realtek ALC887-V). However just the last one shows up channels to be configured. I've unmuted Master, but no sound yet. The results your requested... Terminal 1: ... [ +0.083369] input: HDA Intel HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.0/sound/card0/input8 [ +0.000042] input: HDA Intel HDMI HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.0/sound/card0/input9 [ +0.000035] input: HDA Intel HDMI HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.0/sound/card0/input10 [ +0.035024] sound hdaudioC1D2: autoconfig: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line [ +0.000002] sound hdaudioC1D2: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ +0.000001] sound hdaudioC1D2: hp_outs=1 (0x1b/0x0/0x0/0x0/0x0) [ +0.000001] sound hdaudioC1D2: mono: mono_out=0x0 [ +0.000000] sound hdaudioC1D2: inputs: [ +0.000002] sound hdaudioC1D2: Rear Mic=0x18 [ +0.000001] sound hdaudioC1D2: Front Mic=0x19 [ +0.000001] sound hdaudioC1D2: Line=0x1a [ +0.000001] sound hdaudioC1D2: CD=0x1c [ +0.009288] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/sound/card1/hdaudioC1D2/input11 [ +0.000436] input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card1/input12 [ +0.000072] input: HDA Intel PCH Front Mic as /devices/pci0000:00/0000:00:1b.0/sound/card1/input13 [ +0.000077] input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sound/card1/input14 [ +0.000078] input: HDA Intel PCH Line Out as /devices/pci0000:00/0000:00:1b.0/sound/card1/input15 ... Terminal 2: modprobe: INFO: custom logging function 0x409d40 registered modprobe: INFO: context 0xaf9260 released I've been looking for other clues and came across profiling and mix-ins. Wouldn't be necessary to use them in order to play something? I have setup a core flavor so far. Details above: !!! Found 2 make.conf files, using both '/etc/make.conf' and '/etc/portage/make.conf' === Enabled Profiles: === arch: pure64 build: current subarch: intel64-haswell-pure64 flavor: core mix-ins: (not set) === All inherited flavors from core flavor: === minimal (from core flavor) I also ran the alsa script again and it gave me what follows: This script visits the following commands/files to collect diagnostic information about your ALSA installation and sound related hardware. dmesg lspci lsmod aplay amixer alsactl /proc/asound/ /sys/class/sound/ ~/.asoundrc (etc.) See './alsa-info.sh --help' for command line options. Automatically upload ALSA information to www.alsa-project.org? [y/N] : y Uploading information to www.alsa-project.org ... Done! Your ALSA information is located at http://www.alsa-project.org/db/?f=1706580caa6746a247a8eb3e6a203e78e4114aa4 Please inform the person helping you. By the way, as I did get alsamixer working from removing every older config file of it and reinstalling it the emerging again alsa-lib my volumeicon recognizes the configs set by alsamixer.
  15. lambd0x

    Alsa, no sound

    ALSA Information Script v 0.4.64 -------------------------------- This script visits the following commands/files to collect diagnostic information about your ALSA installation and sound related hardware. dmesg lspci lsmod aplay amixer alsactl /proc/asound/ /sys/class/sound/ ~/.asoundrc (etc.) See './alsa-info.sh --help' for command line options. cat: /proc/asound/version: No such file or directory grep: /proc/asound/cards: No such file or directory cat: /proc/asound/cards: No such file or directory cat: /proc/asound/modules: No such file or directory ls: cannot access /dev/snd/*: No such file or directory grep: /proc/asound/cards: No such file or directory /usr/sbin/alsactl: save_state:1595: No soundcards found... cat: /tmp/alsa-info.v7YNDCLcjD/alsactl.tmp: No such file or directory Automatically upload ALSA information to www.alsa-project.org? [y/N] : y Uploading information to www.alsa-project.org ... Done! Your ALSA information is located at http://www.alsa-project.org/db/?f=7e7f3a22ee5151087b0052fd1b3a45e2107b48b8 Please inform the person helping you.
×