Firmwares

[Aleksa2022]

Greetings! When building an image, even with the allfirmware parameter, messages are displayed in the log that no firmware was found. For example, some messages.

Module 5.10.89TS: vsock_loopback Notice, Firmware 06-2a-07 not found

---

Module 5.10.89TS: snd-hda-controller Notice! Module snd-hda-controller.ko not found for kernel 5.10.89TS

---

Firmware: /lib/firmware/nvidia/gm206/acr/ucode_load.bin Notice, Firmware nvidia/gm206/acr/bl.bin not found Notice, Firmware nvidia/gm204/acr/ucode_load.bin not found

These files are in the directories! How to overcome this problem?

[Thinstation]

That's one of the rough edges of Linux. ucode is a very generic name, and there may be lots of firmware files with a similar name, but we would actually dig for a folder and file nvidia/gm204/acr/ucode_load.bin. Some modules say they need more firmware than they actually do. That's why you get those messages. A developer might have a file with the right name that does something special if it exists, but a lot of the build time firmware messages are red herrings, thus they are Notices and not Errors.

[Aleksa2022]

Messages like this really annoy me: Machine: m704 Module 5.10.89TS: via Notice! Module via.ko not found for kernel 5.10.89TS Module 5.10.89TS: vsock_loopback Notice, Firmware 06-2a-07 not found Machine: up-core Module 5.10.89TS: dwc3 Notice! Module dwc3.ko not found for kernel 5.10.89TS Module 5.10.89TS: intel_rapl Notice! Module intel_rapl.ko not found for kernel 5.10.89TS Module 5.10.89TS: kvm-intel Notice! Module kvm-intel.ko not found for kernel 5.10.89TS Module 5.10.89TS: kvm Notice! Module kvm.ko not found for kernel 5.10.89TS Module 5.10.89TS: input-leds Notice! Module input-leds.ko not found for kernel 5.10.89TS Module 5.10.89TS: irqbypass Notice! Module irqbypass.ko not found for kernel 5.10.89TS Module 5.10.89TS: dwc3-pci Notice! Module dwc3-pci.ko not found for kernel 5.10.89TS Module 5.10.89TS: tpm_crb Notice! Module tpm_crb.ko not found for kernel 5.10.89TS Module 5.10.89TS: tpm_tis Notice! Module tpm_tis.ko not found for kernel 5.10.89TS Module 5.10.89TS: mmc_core Module 5.10.89TS: tpm_tis_core Notice! Module tpm_tis_core.ko not found for kernel 5.10.89TS Module 5.10.89TS: pwm-lpss-platform Module 5.10.89TS: dw_dmac_core Notice! Module dw_dmac_core.ko not found for kernel 5.10.89TS Module 5.10.89TS: video Notice! Module video.ko not found for kernel 5.10.89TS Module 5.10.89TS: snd-intel-nhlt Notice! Module snd-intel-nhlt.ko not found for kernel 5.10.89TS Machine: ga945-61 Module 5.10.89TS: input-leds Notice! Module input-leds.ko not found for kernel 5.10.89TS Module 5.10.89TS: pcspkr Notice! Module pcspkr.ko not found for kernel 5.10.89TS Module 5.10.89TS: shpchp Notice! Module shpchp.ko not found for kernel 5.10.89TS

There is a feeling that something will not work or will not work correctly ...

I can't understand what is missing - maybe you can tell me: on some stations (including virtual machines), the connection works through vmblast (vmview), on some it doesn't. I've already tried everything, but I can't figure out what's missing.

[Thinstation]

Some of the modules have been moved inside the kernel, but the machine profiles were never updated. I just made a change to the build script to give a different Notice when that is the case. This should reduce the number of missing notices that you receive.

You would need to know what's different about those machines. Not sure why a virtual machine would not work though. I would look at the logs. On a machine that fails, open a terminal, elevate to root, journalctl -xe to look at the systemd log, and cat /var/log/Xorg.0.log for the X log.

[Aleksa2022]

There are no problems with virtual machines. Here, I'm attaching a log from one of the problematic machines. PCoIP works fine... Xorg.0.log

[Aleksa2022]

Decided to try loading proprietary Nvidia drivers... I thought it would somehow improve the situation... As a result, I got an even worse result: "The system was not able to go graphical....." Attached is the report nvidia.txt

[Aleksa2022]

Run a full rebuild: --autodl --update --allmodules --license accept Here's what I got in the logs... Attached fragments... Errors of Rebuild thinstation.txt

[Aleksa2022]

Here is another station. At this station, an attempt to connect via vmblast results in a reconnect... The equipment configuration was reshot on a new one to eliminate possible errors in the previous scan. The previous build was done by another person a few months ago. With his configuration, but with the new version of Thinstation, it doesn't work...

Just in case, here is a list of modules for this station module i915 module iTCO_wdt module gpio-ich module iTCO_vendor_support module joydev module i2c-algo-bit module drm_kms_helper module snd-hda-codec-realtek module snd-hda-codec-generic module ledtrig-audio module snd-hda-intel module ata_generic module pata_acpi module snd-intel-dspcfg module coretemp module ata_piix module cec module snd-hda-codec module libata module snd-hwdep module snd-hda-core module serio_raw module drm module scsi_mod module snd-pcm module i2c-i801 module i2c-smbus module lpc_ich module snd-timer module r8169 module snd module realtek module intel-agp module soundcore module intel-gtt module parport_pc module parport

Xorg.0.log

[Thinstation]

There are no problems with virtual machines. Here, I'm attaching a log from one of the problematic machines. PCoIP works fine... Xorg.0.log

I'm not sure what's happening here, it looks like the communication between the video card and monitor keeps resetting, maybe a bad pin or cable.

[Thinstation]

Here is another station. At this station, an attempt to connect via vmblast results in a reconnect...

I glx is broken because you made an attempt to install the proprietary nvidia driver. Their installer does not behave itself very well, and breaks the TS build system if you try and use it. You have to completely reset your chroot.

[Aleksa2022]

Here is another station. At this station, an attempt to connect via vmblast results in a reconnect...

So I tried to install a proprietary driver when nothing worked with the other ... This was the last option that came to my mind ...

[Aleksa2022]

There are no problems with virtual machines. Here, I'm attaching a log from one of the problematic machines. PCoIP works fine... Xorg.0.log

I am very confused by the fact that with the same monitor and cable, one of the stations works fine for me ... I have 2 stations (2 desktops and 1 really thin client). The thin client works, but stationary computers with different fillings (Gigabyte and Asus motherboards, with an integrated video card and with an external one) do not work... This confuses me a lot...

[Thinstation]

When I look at the log, I see the monitor redetected several times. I've never seen that before. Try a different monitor and cable.

[Aleksa2022]

When I look at the log, I see the monitor redetected several times. I've never seen that before. Try a different monitor and cable.

Okay. Thank you. I'll try to find another cable tomorrow and try... To be honest, I have been working with computers for a long time, but I have never come across such that the cable and monitor work normally with one computer, but not with another. Honestly, it's weird. But I will definitely try to change something, at least to calm my soul.

[Aleksa2022]

Here is another problem: periodically, during the build, such messages appear. rmdir: failed to remove './temp-efi': Device or resource busy If this is not manually unmounted, then df -h after a certain number of builds will show something like this: /dev/loopXX ....... /thinstation/ts/build/temp-efi Often it is with this component that such problems arise.

Literally just got such a problem on a completely clean system - downloaded git, executed with default settings /setup-chroot and /build --autodl --update --allmodules --license accept

[Aleksa2022]

In general, I still don’t understand anything ... I replaced the cable - it was VGA, it became DVI. I collected it with different parameters, the result is the same - the connection works via PCoIP, but not via vmblast... Xorg.0 (mesa3d_disable).log Xorg.0 (mesa3d_enable).log

[Aleksa2022]

I can't figure out why hwlister.sh doesn't generate firmware.list. It seems that this is the problem...

[Thinstation]

Maybe your machine does not need any firmware.

On Tue, Feb 8, 2022 at 12:26 AM Aleksa2022 @.***> wrote:

I can't figure out why hwlister.sh doesn't generate firmware.list. It seems that this is the problem...

— Reply to this email directly, view it on GitHub https://github.com/Thinstation/thinstation/issues/697#issuecomment-1032338287, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVW47REKLX3U6SXHTF4JTTU2DHTXANCNFSM5NVCT2LQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you commented.Message ID: @.***>

[Doncuppjr]

Send the journalctl -xe of the nouveau machine. 

On Tuesday, February 8, 2022, 04:52:46 AM PST, ThinStation @.***> wrote:

Maybe your machine does not need any firmware.

On Tue, Feb 8, 2022 at 12:26 AM Aleksa2022 @.***> wrote:

I can't figure out why hwlister.sh doesn't generate firmware.list. It seems that this is the problem...

— Reply to this email directly, view it on GitHub https://github.com/Thinstation/thinstation/issues/697#issuecomment-1032338287, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVW47REKLX3U6SXHTF4JTTU2DHTXANCNFSM5NVCT2LQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you commented.Message ID: @.***>

— Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you are subscribed to this thread.Message ID: @.***>

[Aleksa2022]

Maybe your machine does not need any firmware. … On Tue, Feb 8, 2022 at 12:26 AM Aleksa2022 @.> wrote: I can't figure out why hwlister.sh doesn't generate firmware.list. It seems that this is the problem... — Reply to this email directly, view it on GitHub <#697 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVW47REKLX3U6SXHTF4JTTU2DHTXANCNFSM5NVCT2LQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you commented.Message ID: @.>

If everything worked fine on this machine, I would not think about the firmware either. The problem is that I have about 50 machines with a similar configuration and I need the system to work like clockwork on the bench, otherwise I can't release it to work... On another bench machine, with a different filling, but with the same monitor and cable, everything works fine. I have many such clients. But I can't release a system that won't work on all clients... So I'm trying to figure out what's going on and how it can be fixed.

[Aleksa2022]

Found this entry in the logs: pci 0000:03:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format) Now to understand how to win it?..

I suggest adding functionality to hwlister to catch such errors and save them in a report, along with other files. I would probably add such functionality there myself, but I am not very familiar with Linux - in fact, I am getting to know it now.

P.S.: VGA: G98 [GeForce 8400 GS Rev. 2] Motherboard: Asus P5B SE

[Aleksa2022]

I found the reason. It turned out that these problems occur with vmview, versions higher than 8.1.0_2012.

[Aleksa2022]

The following solution is offered on the Internet: check

GStreamer core library and gstreamer-libav 1.0 GStreamer core library and fluendo 1.0 gcc 6.4 or later

When a RHEL 7 client user connects to a published Windows Server desktop using the VMware Blast display protocol and attempts to log out from the session, Horizon Client might hang. This issue is caused by conflicting processes associated with version 1.8.8 of the PC/SC Lite (pcsclite) library. Workaround: On RHEL 7 systems, upgrade the pcsclite library to a version later than 1.8.8.

I’m still not very good with Linux, I haven’t found all the libraries (maybe I was looking in the wrong place)

[Thinstation]

prt-get info gst-libav prt-get info gstreamer prt-get info gst-plubins-base prt-get info pcsc-lite

[Thinstation]

I think the [Firmware Bug] is erroneous and can be ignored.

ThinStation is a great Linux to learn from.

[Aleksa2022]

I think the [Firmware Bug] is erroneous and can be ignored.

ThinStation is a great Linux to learn from.

Thanks a lot! I would gladly ignore it if everything worked as it should. Many experiments have shown that vmviews above 8.1.0 do not work properly. The occurrence of this error is just one of the evidences that there are problems with vmview...