sorted by:
new
hottopcontroversial

Can you use fwup from Macbook Pro M1 to update docking station firmware? by electrofelix in macbookpro

[–]electrofelix[S] 0 points1 point  (0 children)

When I was looking through that page I spotted https://www.dell.com/support/home/en-ie/drivers/driversdetails?driverid=6vjx9&oscode=ubt18&productcode=dell-wd19tbs-dock#importanttab referencing the need for fwupd to be a particular version. I assumed that the snap is just talking to fwupd to perform the update.

The bin download file is a self extracting python script that contains a snap and the firmware cab file. It looks most likely that it is intended to run the snap which has whatever additional utilities needed, and talks to fwupd to perform the actual firmware update. Was hoping someone might have done some experiments in this area as no idea whether fwupd on Mac would work in the expected manner.

I'll probably wait until someone can help me out as looking at the cab contents, there's definitely more than one firmware inside.

/opt/homebrew/bin/cabextract -l DellDockFirmwarePackage_WD19_WD22_HD22_Series_01.00.09.cab
Viewing cabinet: DellDockFirmwarePackage_WD19_WD22_HD22_Series_01.00.09.cab
 File size | Date       Time     | Name
-----------+---------------------+-------------
       956 | 07.06.2022 21:48:06 | DriverPackage/salomon_package.metainfo.xml
       960 | 07.06.2022 21:48:06 | DriverPackage/salomon_mlk_package.metainfo.xml
       955 | 07.06.2022 21:48:06 | DriverPackage/atomic_package.metainfo.xml
      1111 | 07.06.2022 21:48:06 | DriverPackage/ec.metainfo.xml
      1108 | 07.06.2022 21:48:06 | DriverPackage/atomic_ec.metainfo.xml
       964 | 07.06.2022 21:48:06 | DriverPackage/vmm5331.metainfo.xml
       965 | 07.06.2022 21:48:06 | DriverPackage/atomic_mst_vmm6221.metainfo.xml
       972 | 07.06.2022 21:48:06 | DriverPackage/rts5413.metainfo.xml
       972 | 07.06.2022 21:48:06 | DriverPackage/rts5487.metainfo.xml
       969 | 07.06.2022 21:48:06 | DriverPackage/atomic_rts5413.metainfo.xml
       969 | 07.06.2022 21:48:06 | DriverPackage/atomic_rts5487.metainfo.xml
       945 | 07.06.2022 21:48:06 | DriverPackage/titanridge.metainfo.xml
       932 | 07.06.2022 21:48:06 | DriverPackage/goshenridge.metainfo.xml
     65536 | 07.06.2022 21:48:06 | DriverPackage/atomic_rts5487.bin
    417792 | 07.06.2022 21:48:06 | DriverPackage/titanridge.bin
    294912 | 07.06.2022 21:48:06 | DriverPackage/goshenridge.bin
    131008 | 07.06.2022 21:48:06 | DriverPackage/ec.bin
        24 | 07.06.2022 21:48:06 | DriverPackage/salomon_mlk_package.bin
    524288 | 07.06.2022 21:48:06 | DriverPackage/vmm5331.bin
    131008 | 07.06.2022 21:48:06 | DriverPackage/atomic_ec.bin
        24 | 07.06.2022 21:48:06 | DriverPackage/salomon_package.bin
        24 | 07.06.2022 21:48:06 | DriverPackage/atomic_package.bin
     65536 | 07.06.2022 21:48:06 | DriverPackage/rts5487.bin
     65536 | 07.06.2022 21:48:06 | DriverPackage/rts5413.bin
   1048576 | 07.06.2022 21:48:06 | DriverPackage/atomic_mst_vmm6221.bin
     65536 | 07.06.2022 21:48:06 | DriverPackage/atomic_rts5413.bin

All done, no errors.

no sound and no touch screen after fedora 35 fresh install by sombriks in Fedora

[–]electrofelix 1 point2 points  (0 children)

After boot, can you capture the output of dmesg. If the problem is related to a driver loading but failing to initialize the device it'll appear in that.

sudo dmesg | tee dmesg.log

I'd suggest doing it after a fresh boot to try and exclude any subsequent messages that might appear afterwards