SliTaz Forum
Vous n'êtes pas connecté.
Pages: 1
Hello everyone.
Speaking of LinuxFromScratch, my best wishes for the enterprise of Filou and Shann, and while waiting for an official distro I turn to the experts for advice: I built based on the guide LFS-BOOK-10.0 the whole system. It seems to work ... except that I can not get the audio (alsa working). The device from udev is detected, but from alsaconf is not...
It seems to be missing the initial configuration asound.conf. Does anyone know how to create it?
I've done several tests but I don't understand it anymore. I would like a tip on how to try to configure the device from the command line.
I attach the output of some commands, and the screenshot of my SliTaz-Build10 :-)
Salve, a tutti.
A proposito di LinuxFromScratch, i miei auguri per l'impresa di Filou e Shann, e nell'attesa di una distro ufficiale mi rivolgo agli esperti per un consiglio: mi sono costruito basandomi sulla guida LFS-BOOK-10.0 l'intero sistema. Sembra funzioni... salvo che non riesco ad avere l'audio (alsa funzionante). La periferica da udev viene rilevata, ma da alsaconf no...
Sembra manchi la configurazione iniziale asound.conf. Qualcuno sa come si la crea?
Ho fatto varie prove ma non ci capisco più nulla. Gradirei una dritta su come tentare da riga di comando a configurare la periferica.
Vi allego l'output di alcuni comandi, e lo screenshot del mio SliTaz-Build10 :-)
[attachment=49898,3072]
dmesg
[ 0.000000] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC268: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[ 0.000000] snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 0.000000] snd_hda_codec_realtek hdaudioC0D0: hp_outs=1 (0x15/0x0/0x0/0x0/0x0)
[ 0.000000] snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0
[ 0.000000] snd_hda_codec_realtek hdaudioC0D0: dig-out=0x1e/0x0
[ 0.000000] snd_hda_codec_realtek hdaudioC0D0: inputs:
[ 0.000000] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x19
[ 0.000000] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18
[ 0.000000] input: HDA Intel Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input4
[ 0.000000] input: HDA Intel Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input5
[ 0.000000] ALSA device list:
[ 0.000000] No soundcards found.
aplay: device_list:274: no soundcards found...
lspci
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
alsactl: load_state:1735: No soundcards found...
lsmod
Module Size Used by
r592 20480 0
memstick 16384 1 r592
sdhci_pci 45056 0
cqhci 20480 1 sdhci_pci
sdhci 49152 1 sdhci_pci
mmc_core 102400 3 sdhci,cqhci,sdhci_pci
uvcvideo 90112 0
firewire_ohci 40960 0
firewire_core 61440 1 firewire_ohci
videobuf2_vmalloc 16384 1 uvcvideo
videobuf2_memops 16384 1 videobuf2_vmalloc
videobuf2_v4l2 24576 1 uvcvideo
videobuf2_common 36864 2 videobuf2_v4l2,uvcvideo
radeon 1224704 0
videodev 180224 3 videobuf2_v4l2,uvcvideo,videobuf2_common
mc 32768 4 videodev,videobuf2_v4l2,uvcvideo,videobuf2_common
hwmon 20480 1 radeon
i2c_algo_bit 16384 1 radeon
ttm 77824 1 radeon
drm_kms_helper 159744 1 radeon
drm 389120 3 drm_kms_helper,radeon,ttm
syscopyarea 16384 1 drm_kms_helper
sysfillrect 16384 1 drm_kms_helper
sysimgblt 16384 1 drm_kms_helper
fb_sys_fops 16384 1 drm_kms_helper
i2c_core 40960 5 videodev,drm_kms_helper,i2c_algo_bit,radeon,drm
intel_agp 20480 0
intel_gtt 20480 1 intel_agp
agpgart 32768 4 intel_agp,intel_gtt,ttm,drm
btusb 40960 0
btrtl 16384 1 btusb
btbcm 16384 1 btusb
btintel 20480 1 btusb
ath9k 94208 0
bluetooth 339968 5 btrtl,btintel,btbcm,btusb
ecdh_generic 16384 1 bluetooth
ecc 24576 1 ecdh_generic
ath9k_common 16384 1 ath9k
ath9k_hw 421888 2 ath9k_common,ath9k
ath 32768 3 ath9k_common,ath9k,ath9k_hw
mac80211 454656 1 ath9k
cfg80211 303104 4 ath9k_common,ath9k,ath,mac80211
rfkill 24576 2 bluetooth,cfg80211
r8169 73728 0
snd_hda_codec_hdmi 49152 1
realtek 20480 0
snd_hda_codec_realtek 98304 1
libphy 77824 2 r8169,realtek
snd_hda_codec_generic 61440 1 snd_hda_codec_realtek
ledtrig_audio 16384 2 snd_hda_codec_generic,snd_hda_codec_realtek
snd_hda_intel 32768 0
snd_intel_dspcfg 16384 1 snd_hda_intel
snd_hda_codec 98304 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
snd_hwdep 16384 1 snd_hda_codec
snd_hda_core 57344 5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
uhci_hcd 32768 0
ehci_pci 16384 0
ehci_hcd 49152 1 ehci_pci
Hors ligne
Adding sound instructions are in "BLFS:beyond linux from scratch" in the 'Multimedia" chapter.
http://www.linuxfromscratch.org/blfs/view/stable/multimedia/libdriv.html
The software may need to be patched before it is compiled:"LFS Patches Project"
http://www.linuxfromscratch.org/patches/downloads/
An asound.conf is configured by the user on an as needed basis.
If alsa can't find the soundcard due to a driver issue an asound.conf is not the solution.
https://www.alsa-project.org/wiki/Asoundrc
Your lsmod output is showing required sound modules are not loaded!
You should have soundcore.ko,snd.ko,snd-pcm.ko,snd-timer.ko loaded.
Check /lib/modules/[c][/c]uname -r[c][/c]/modules.dep for loaded module depends that are not loaded.
Hors ligne
Thanks for the help mojo!
The problem stemmed from eudev and its xxx.rules... which were causing horrible names to network devices. I had messed around too much, then I found a way around the problem (touch > /etc/udev/rules.d/80-net-name-slot.rules) and everything is working properly again.
tux@slitaz:~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 1: ALC268 Digital [ALC268 Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
despite everything the peripheral is set incorrectly and needs a fix in the drivers or you can work around it with a ~/asoundconf user that changes the default settings
pcm.!default {
type plug
slave {
pcm "hw:0,1"
}
}
I still need to find out how to get audio with firefox (apulse?)
-----------------------------------------------------------------------------------------------------------------------
Grazie dell'aiuto mojo!
Il problema mi nasceva da eudev e dai suoi xxx.rules... che causavano nomi orribili alle periferiche di rete. Avevo pasticciato troppo, poi ho trovato come aggirare il problema (touch > /etc/udev/rules.d/80-net-name-slot.rules) e tutto mi riprende a funzionare correttamente.
tux@slitaz:~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 1: ALC268 Digital [ALC268 Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
nonostante tutto la periferica viene settata in modo errato e serve una correzione nei driver oppure lo si può aggirare con un ~/asoundconf utente che varia le impostazioni di default
pcm.!default {
type plug
slave {
pcm "hw:0,1"
}
}
Mi rimane ancora da scoprire come avere l'audio con firefox (apulse?)
Hors ligne
@gibor
Firefox audio with apulse
# tazpkg -gi apulse
# leafpad /usr/share/applications/firefox-official.desktop
replace line
Exec=firefox-official %u to
Exec=/usr/bin/apulse firefox-official %u
-------------------------
Firefox audio whit pulseaudio
https://forum.slitaz.org/topic/issue-with-pulseaudio#post-37164
Hors ligne
@gibor this sounds promising - how much Ram uses your idle desktop?
htop is good tool to measure
Hors ligne
@Rerivero
thanks for the tip! apulse was already compiled. the only thing missing was how to start it with firefox.
@Kultex
Allego lo screenshot di htop.
Poi chiedo se qualcuno sa dove risiede, o come levare e reimpostare rlimit. Perché all'avvio mi tocca inserire nella riga del grub “ignore_rlimit_data” altrimenti mi da dei problemi nell'esecuzione di alcuni programmi tipo cc1 o firefox [attachment=49908,3076]
Hors ligne
I have no idea about rlimits, but maybe this helps you - https://manpages.debian.org/jessie/manpages-dev/setrlimit.2.en.html
114MB is really good - I have been cheating and I was working on a minimal fluxbox respin of MX-Linux - I am on 150MB - it will be ready the next days - so we can compare......
Hors ligne
Hi Gibor (and thanks for your wishes),
as I see you already have a working full (?!) desktop.
How much LFS vs SliTaz is your build?
Do you have any experiences to share? Do's and don'ts? Or does (B)LFS provide all the necessary / interesting information?
Cheers!
Hors ligne
Hi Filou, I try to answer you in order helping me with a translator....
My build is still under construction, but I can already use it for ordinary things. For now there are working: firefox, thunderbird, the openoffice suite, mplayer, leafpad, mtpaint and three games installed without my knowledge during the compilation of some package (Block Attack, Checkers, Sudoku).
The second question I think you want to know the size on disk, and if not try to explain better (sorry but the fault is mine, for what I understand of English).
The build with all compilers installed currently occupies about 9.1Gb. The kernel sources are also included. All other sources are on an external partition and are about 15Gb.
I would not know how to share a build as it is. Especially since it would be impossible for me to upload it.
If you want advice on how to build it, I could try, but know that I'm not a programmer. My real training is in electronics and telecommunications. So I can make gross mistakes... I often go by trial and error, except to delve into the sources when they fail, to try to patch them to get them done.
The intent is to get a linux build with the fluency and speed unique to slitaz. Now the boot is 10sec. At full desktop it's about 20sec total. Not bad compared to many others!
Hors ligne
Hi gibor,
thank you for the information. I see that you work exactly like me, just that you continued on the LFS path as it seems and I took a sooner side-step into the slitaz direction.
I'm impressed what you already set up, in fact Web, Mail and Office are the main uses for a PC, which you already achieved. It would be interesting to hear, which packages needed to most patching (and what type of patches) to get this far.
sofia-m offered the do some translators work, as he said to speak Italian and English fluently and could help out.
So if you have some knowledge to share, which packages made the most problems and how you solved them, this could be helpful. If you posted in Italian, I guess sofia-m could then translate afterwards...
Thank you so far!
Hors ligne
gibor - can you make an iso of your system? - I cannot help developing, but maybe debugging something or configuring the desktop ???????
Hors ligne
Ciao Kultex, l'idea c'era ma la distro è troppo voluminosa. Per fare una iso da uppare dovrei riuscire a strippare una base ridotta per una live.
Così per ora assomiglia molto ad una versione di Archilinux, con compilatori e s.o. che convivono nella stessa partizione, in modo da essere pronti per assemblare nuovi sorgenti.
Siccome ci si innamora delle proprie creature, la trovo bella così com'è, senza packages manager ed altri orpelli che non nomino che giravano sottobanco...
14Gb il filesystem con consumo di ram in idle di 90Mb ed un boot da 20” a desktop finito, che altro mi può servire ancora?!?! ;-)
Hors ligne
Tento nel provare a condividere una versione test ristretta del mio slitaz a 64bit. Il pacchetto da 153Mb contiene la root della partizione compreso il kernel 5.8.3. il tutto scompattato occupa circa 1Gb, e contiene le seguenti utilità:
Gparted
openbox
lxpanel
pcmanfm
leafpad
epdfview
viewnior
L'avvio richiede di passare al kernel l'opzione “ignore_rlimit_data” purtroppo debbo ancora trovare la causa di questa limitazione (sembra in mmap per la compabilità di gpg).
Di base preparate una partizione in ext3/ext4 e scompattateci il file sopra (lzma).
Passate al boot con un grub4dos già inserito o come credete meglio voi.
Si può preparare anche per una live, ma intanto mi piacerebbe scoprire se si avvia su altri pc.
I try to share a restricted version of my 64bit slitaz. The 153Mb package contains the root of the partition including the kernel 5.8.3. the whole unpacked occupies about 1Gb, and contains the following utilities:
Gparted
openbox
lxpanel
pcmanfm
leafpad
epdfview
viewnior
Booting requires to pass to the kernel the option "ignore_rlimit_data" unfortunately I still have to find the cause of this limitation (it seems in mmap for gpg compability).
Basically prepare an ext3/ext4 partition and unpack the file on it (lzma).
Go to boot with a grub4dos already inserted or as you think best.
You can also prepare it for a live, but in the meantime I'd like to find out if it boots on other Pcs.
https://disk.yandex.com/d/wMssAlByFcPIZA
Hors ligne
perfect - thx a lot - I will try as soon as possible - at the moment a bit difficult - to much things to do...
Hors ligne
Cuneiform patch for gcc-10 at 64bit
patch https://paste.slitaz.org/?cfab37ded1f8cbff#pA3v7dL2Icjyr5Niq/LR58SZwU6TkHWh77ma/sagLXU=
wget https://launchpad.net/cuneiform-linux/1.1/1.1/+download/cuneiform-linux-1.1.0.tar.bz2
tar -xvf cuneiform-linux-1.1.0.tar.bz2
cd cuneiform-linux-1.1.0
patch -p0 < ../cuneiform-PatchFile.txt
mkdir build && cd build
cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=debug \
-DCMAKE_CXX_FLAGS:STRING=-Wno-narrowing ..
make && make install
cuneiform
Cuneiform for Linux 1.1.0
Usage: cuneiform [-l languagename -f format --dotmatrix --fax --singlecolumn -o result_file] imagefile
Hors ligne
we are so very very far from https://www.slitaz.org/en/doc/scratchbook/ !
1 word:
WHY?
Hors ligne
and probably also from that:
https://doc.slitaz.org/en:cookbook:toolchain
what happens if I try to do that actually? (no) success (in which version of SliTaz)?
Hors ligne
@oui
why not!
I didn't use any of those guides, because they are all too old. As no version of slitaz supported 64bit fully.
Read the previous posts and you will find on what basis I developed the LFS-BLFS.
perché no!
Non ho usato nessuna di quelle guide, perché sono tutte troppo vecchie. Come nessuna versione di slitaz supportava i 64bit in modo completo.
Leggi i post precedenti e troverai su quali basi ho sviluppato la LFS.
Hors ligne
Hi Gibor
You are asking
«@oui
why not!»
simply because it is not SliTaz any more if does not works according the old documentation from Christophe any more :-) !
if I remember right, Chritophe did show us the way to build SliTaz not from some LFS+BLFS, not from Debain, not from Slackware, not from other distributions but directly from the sources being on each of the official sites of the creators of the used and selected applications!
it is a totally different way and purpose and it is or it not SliTaz any more at all.
following your logic, Puppy Linux would be SliTaz! Puppy Linux was officially made using Slackware...
the logic from Christophe was completely different:
- he did look for the minimal set of applications needing,
- he did search the "original" source codes
- he did compile them after shrinking from the ballast (his distribution did immediately but only contain French, his language, German, Italian and English, not more - it was a factor how to shring some sources from very important among of not often used code and annexed documentations)
his compatriot Thierry Nuittens, also a initially only French speaking Swiss man, did do parallel the same matter as probably you: he did create the distro Nutyx, see https://nutyx.org, from LFS book! and you, you copy only, and bad, Nutyx now...
SliTaz us an acronym and it has to do with "be independant" from LFS etc.
If dependant, I would prefer a kind of SliTaz dependant from Debian/Devuan sources!
(it is the limit of NuTyx: after NuTyx, difficult to get more... But NuTyx did become in the time a very complete but limited standard distribution, where only one is not available, the 30.000 thousand and more Debian applications!)
Hors ligne
For me it is only important to have a distro that boots quickly and has no unnecessary parasitic routines.
The system I have created uses the slitaz init.d scripts and works as I wanted.
It is well known that many distributions are basically clones with few differences between them, and this is the habit of many.
So think what you want, but the system to give it a definition is based on slitaz, then if it bothers me I can just call it "build" or any other name, but the substance does not change. as does the construction of many competing distros.
Per me è importante solo avere una distro che avvii in tempi rapidi e che non abbia routine parassite inutili.
Il sistema che ho creato usa gli script init init.d di slitaz e lavora come volevo.
Poi che molte distribuzioni siano in fondo tutte dei cloni con poche differenze fra loro questo si sa, è abitudine di molti.
Quindi pensala come vuoi, ma il sistema per dargli una definizione è basato su slitaz, poi se la cosa da fastidio posso chiamarlo solo "build" o con qualsiasi altro nome, ma la sostanza non cambia. come non cambia la costruzione di molte distro concorrenti.
Hors ligne
... if I may ...
as far as I remember, the underlying idea and first scripts for SliTaz had been derived from LFS, since LFS is nothing more than a documentation about how to set up a working Linux system from source code.
If I am not mistaken, this is also the reason why a couple of package receipts still contain LFS patches.
The main contribution on top of that was the minimalistic adaptions - as oui described - that turned a quite big LFS system into SliTaz by replacing many functionalities by busybox and some more by shell scripts and stripping all components down to the bone.
I agree that a "true" LFS system is not identical with a SliTaz system, but what some of us try to achieve is updating this faboulous tiny system to recent libraries and 64 bit in order for SliTaz to be usable with recent mainstream software like browsers, office suites etc.
I myself used LFS in order to have a functioning recent basement for a new SliTaz wok.
I am using a patched wok and by that compile the packages the "SliTaz-way". Is this "orgiginal SliTaz"? I don't know, but I am open for a better alternative.
As far as I can see in the forum activity of the last months, there is a VERY small group of us who dedicate ANY time into this. My own intention was to CONTRIBUTE, not to lead or compile everything on my own, but it seems that the "elder's advice" is sparsely available.
If you have any suggestions on how we could better - or faster - or slimmer - or ??? - proceed on our way to a "64 bit SliTaz-like distro" I would be glad to hear and eventually support them.
I don't think though, that a blame of "badly copying" anyone's work is a very constructive step ahead...
Hors ligne
> I myself used LFS in order to have a functioning recent basement
> for a new SliTaz wok.
... which is exactly what is needed at this stage. But once all the problems with the resulting SliTaz base system have been ironed out, this system should itself be used to run the wok and everything that comes with it, so the system becomes self-hosting. I think, this is what Oui was referring to.
Hors ligne
Hello everyone,
Filou wrote:
"As far as I can see in the forum activity of the last months, there is a VERY small group of us who dedicate ANY time into this. My own intention was to CONTRIBUTE, not to lead or compile everything on my own, but it seems that the "elder's advice" is sparsely available."
I follow the development of the topic https://forum.slitaz.org/topic/slitaz-future with great enthusiasm, as I believe that we see in the progress and development of this topic a "Future of SliTaz". I would like to help, but unfortunately I don't have technical knowledge, what I can do is help test the ISOs, either via the USB device (Live USB) or by installing SliTaz on a hard drive and reporting the test results.
If the "advice of the elderly" does not persist, then there are some doubts:
Who is the person or people who create a new SliTaz 5.0 Release ISO (weekly) and publish it?
The most recent ISO is from the 18th of July 2021. What's the point of that, publishing a new ISO, then another and another... Has the current ISO solved the problems of the previous one? Or does the new ISO have the problems of the old one and now have new problems?
Can you understand my doubt?
marcelocripe
----------
Olá a todos,
Filou escreveu:
"As far as I can see in the forum activity of the last months, there is a VERY small group of us who dedicate ANY time into this. My own intention was to CONTRIBUTE, not to lead or compile everything on my own, but it seems that the "elder's advice" is sparsely available."
Eu acompanho o desenvolvimento do tópico https://forum.slitaz.org/topic/slitaz-future com muito entusiamo, pois acredito que vemos no andamento e no desenvolvimento deste tópico um "Futuro do SliTaz". Eu gostaria de pode ajudar, mas infelizmente eu não possuo conhecimentos técnicos, o que eu posso fazer é ajudar a testar as ISOs, seja executando através do dispositivo USB (Live USB) ou instalando o SliTaz em um disco rígido e reportar os resultados dos testes.
Se os "elder's advice" não respondem, então ficam algumas dúvidas:
Quem é a pessoa ou quem são as pessoas que criam uma ISO nova do SliTaz 5.0 Rolling release (semanalmente) e a publica?
A ISO mais recente é do dia 18 Julho de 2021. Qual é o sentido nisso, publicar uma ISO nova, depois outra e outra ... A ISO atual resolveu os problemas da anterior? Ou a nova ISO possui os problemas da anterior e agora possui novos problemas?
Conseguem compreender a minha dúvida?
marcelocripe
Hors ligne
Pages: 1
[ Généré en 0.018 secondes, 7 requêtes exécutées - Utilisation de la mémoire: 1.61 MiO (Pic : 1.77 MiO) ]