Tiny Core Base > Release Candidate Testing

Core v17.0beta1

<< < (2/4) > >>

Juanito:

--- Quote from: andyj on January 25, 2026, 10:53:45 AM ---Any headway on xf86-video-vmware.tcz for 32-bit?

--- End quote ---

It was posted yesterday or the day before in the 16.x and 17.x repos

aus9:
@Juanito
If interested ....had my first and so far only lock up during boot up on x86_64. I was in a bit of rush (yes my defining character ;)  but took a screenshot - rebooted and it failed to re-appear. Only then thinking maybe I should log it. Last few lines seem to be udev trying to settle an usb trackball with a certain brand.
image expires in 2 days. Yes I should have made it wider and then zoomed
https://i.postimg.cc/brPDzzW4/IMG-20260126-172107.png

andyj:

--- Code: ---tc@box:~$ version           
17.0-beta1

--- End code ---


--- Quote from: Juanito on January 25, 2026, 11:57:45 AM ---It was posted yesterday or the day before in the 16.x and 17.x repos

--- End quote ---

I don't know why, but tce-update thinks my system is up-to-date and I still don't have the latest vmware_drv.so.

Rich:
Hi andyj

--- Quote from: andyj on January 27, 2026, 07:03:38 AM --- ... I don't know why, but tce-update thinks my system is up-to-date and I still don't have the latest vmware_drv.so.
--- End quote ---
I just checked the 32 bit TC16 and TC17 repos. They show that
xf86-video-vmware.tcz was last updated on the 24th.

I checked the MD5 against the .md5.txt file in case the .md5.txt file
was a stale copy, but the 2 matched.

The current xf86-video-vmware.tcz.md5.txt is:

--- Code: ---e8fa69cd1cdd1e6793bd895d18264a35  xf86-video-vmware.tcz
--- End code ---

You aren't missing xf86-video-vmware.tcz.md5.txt by any chance. That
would cause the update to ignore xf86-video-vmware.tcz.

andyj:

--- Quote from: Rich on January 27, 2026, 09:03:46 AM ---You aren't missing xf86-video-vmware.tcz.md5.txt by any chance.

--- End quote ---
That was it, fixed. The vmware_drv.so works, and unlike 64-bit, it works correctly after cycling through the monitors. I still think the 64-bit problem is an FLWM problem, but I can't prove it yet.

The 32-bit kernel is still doing this occasionally doing this on shutdown:

--- Code: ---[  269.732658] EXT4-fs (sda1): unmounting filesystem 7e0105f6-901c-47b1-ae1d-d65be1a82a4c.
[  269.733797] EXT4-fs (sda1): Inode 1 (a538b8c0): inode tracked as orphan!
...and...
[  269.762345] EXT4-fs (sdb1): unmounting filesystem 1df63ddf-4e55-43f3-940c-5696f16aa53b.
[  269.773614] EXT4-fs (sdb1): Inode 1 (20fffd94): inode tracked as orphan!

--- End code ---
But the disks are clean on reboot.

Navigation

[0] Message Index

[#] Next page

[*] Previous page