9front - general discussion about 9front
 help / color / mirror / Atom feed
From: adr@SDF.ORG
To: 9front@9front.org
Subject: [9front] Re: Rio on cpu|Share files to unix on terminal
Date: Thu, 3 Jun 2021 03:43:07 +0000	[thread overview]
Message-ID: <YLhPy97UKb1AZIJZ@SDF.ORG> (raw)
In-Reply-To: <YLblNS6IQBe6s+ZZ@SDF.ORG>

On Wed, Jun 02, 2021 at 01:56:06AM +0000, adr@SDF.ORG wrote:
> Hi,
> I have a terminal configured (rpi4) and I want to shared a file
> system with another unix machine. I changed the service to cpu and
> configured it to start rio, mounting the draw device and mouse first.
> 
> All good but after creating some windows, rio will go crazy, windows
> will be resized randomly and the display will not represent the
> contents of the windows anymore.
> 
> The console message when the party starts is
> 
> rio: setname failed: unknown id for draw image
> 
> If one is able to kill rio you can start it again and all will be
> normal until the mess starts again.
> 
> It puzzled me because I'm pretty sure I had this very same issue
> the last time I used 9front a lot of years ago on a pc.
> 
> I would appreciate if someone points me to a reason of this behavior.
> 
> Regards,
> adr.

After following the boot process it's clear that the constrains are in the kernel,
I suppose is here /sys/src/9/bcm/main.c#245
	if(!cpuserver)
		/*
		 * give terminals lots of image memory, too; the dynamic
		 * allocation will balance the load properly, hopefully.
		 * be careful with 32-bit overflow.
		 */
		imagmem->maxsize = kpages;

Instead of changing the service variable on bootargs and configuring the cpuserver to run rio,
I'll configure the terminal to run the cpu services.

Just in case someone is thinking about this.

  reply	other threads:[~2021-06-03  6:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-02  1:56 [9front] " adr
2021-06-03  3:43 ` adr [this message]
2021-06-03 19:02   ` [9front] " fulton
2021-06-04 15:51     ` adr
2021-06-04 16:29       ` Sigrid Solveig Haflínudóttir
2021-06-04 18:42         ` adr
2021-06-04 19:02           ` Stanley Lieber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YLhPy97UKb1AZIJZ@SDF.ORG \
    --to=adr@sdf.org \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).