Saturday, December 21, 2024

Uri Shaked's TinyTapeout Ubuntu VM - If it Helps You Out

Never settle for less! If you have to give up schematic real estate to look at waveforms, you're settling for less! Don't!

Thankfully, chatG is helping out..

That aside, they're shipping this with the clipboard sharing turned off. (Why??). So:

I confirmed I have GNOME ($XDG_SESSION_TYPE returned wayland).

Now, this VM is running on Virtualbox. I am finding that I am not able to paste from Windows clipboard into the VM and vice versa. Do you know what can be done to accomplish this?

The inability to paste between your Windows host and the Ubuntu VM typically occurs because the clipboard sharing feature of VirtualBox is not enabled or functioning. Here's how you can fix it:

1. Enable Clipboard Sharing in VirtualBox Settings

Power Off your VM if it’s running.

Open VirtualBox and select your VM.

Click on Settings → General → Advanced tab.

Set Shared Clipboard to Bidirectional.

This allows clipboard sharing both ways (host to VM and VM to host).


Essential for productivity:

(Good news is that WIN+SHIFT+arrow does the same thing as in Windows)

Go into keyboard settings (WIN aka "Super" click and then type "keyboard shortcuts" to go into settings > Keyboard > Windows, or go through settings GUI)

1. Set your favorite shortcut for "Lower window below other windows (I use ALT + ~ (the one below the ESC key))

2. Set your favorite shortcut for "Toggle maximization state" (not the same as fullscreen mode). I use ALT+F1 (since that's what I use on Windows through Autohotkey)


Moving files from Win into the VM:

You can go through Settings, or, in the Devices window, when the VM is running, go to Shared Folders and designate a folder on Windows a shared folder. Edit it and check the box for Auto-mount.

Then, you can move stuff there and find it inside the VM in /media/sf_NAME_IN_WIN (means, avoid complicating stuff with spaces :))

And, once you get your file there, you might that root owns it - so you'll need to sudo chown on it to be able to use it without starting every command with sudo :)


boot disk space warning:

Please get in touch if you figure out the fix for this..

Low Disk Space on “boot"

The volume "boot" has only 0 bytes disk space remaining.


Failure to install because of NSF in /boot:

  353  sudo apt install fzf

  354  df -h /boot

  355  sudo apt-get remove --purge linux-image-X.X.X-XX-generic

  356  df -h /boot

  357  dpkg --list | grep linux-image

  358  uname -r

  359* sudo apt-get remove --purge linux-image-5.15.0-127-generic 

  360  df -h /boot

  361  dpkg --list | grep linux-image

  362  uname -r

  363  sudo apt install fzf

  364  which fzf

  365  sudo apt autoremove 

The first install gave me

zstd: error 25 : Write error : No space left on device (cannot write compressed block) 
E: mkinitramfs failure zstd -q -1 -T0 25
update-initramfs: failed for /boot/initrd.img-5.15.0-127-generic with 1.
dpkg: error processing package linux-firmware (--configure):

And chatGPT was able to guide me



No comments:

Post a Comment

Who Needs Cadence Anymore (for Schematic Tree Reporting that is :)? Make Your Own Reporter with chatGPT!

You know what I mean, if you've used Cadence - the SHIFT-T thing that gives you the schematic tree can be VERY useful, at times. No Cade...