Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Could not connect to swc-launch #70

Open
cyanate opened this issue Aug 22, 2017 · 9 comments
Open

Could not connect to swc-launch #70

cyanate opened this issue Aug 22, 2017 · 9 comments

Comments

@cyanate
Copy link

cyanate commented Aug 22, 2017

I've installed mesa-git with wayland support, but when starting velox I'm getting:

[swc:libswc/swc.c:123] ERROR: Could not connect to swc-launch

This seems to be a libswc problem, but you've written that, too.

@michaelforney
Copy link
Owner

How are you starting velox? You need to launch it with swc-launch. For example, swc-launch velox.

mesa with wayland support should be irrelevant since swc uses wld, not mesa.

@biblepix
Copy link

Hello everybody, I have been trying to set up velox too, but I am getting a similar error message:
'swc-launch velox'
gives me:
Running on /dev/tty7
Failed to activate VT: no such device or address
But /dev/tty7 exists and is accessible. Can you help me?

@michaelforney
Copy link
Owner

Looks like you are getting an error from

if (ioctl(fd, VT_ACTIVATE, vt) == -1) {

Where are you running swc-launch velox from? Can you add a line to print out the value of vt before that error message?

@biblepix
Copy link

I'm running it from a non-X login terminal; there is no other line of output before VT.

@michaelforney
Copy link
Owner

I meant you should add a print statement so I can try to figure out what is going on.

In fact, an strace log might be even more helpful

strace swc-launch velox

(you will likely need to run this as root)

@biblepix
Copy link

biblepix commented Nov 12, 2018 via email

@michaelforney
Copy link
Owner

michaelforney commented Nov 12, 2018

Thanks, that's really helpful.

ioctl(5, VT_ACTIVATE, 0xb7756fb4)

This line looks bogus to me. It should be passing the VT number to activate (in this case 7), not a pointer. I can't really explain this since vt is set at

vt = minor(st.st_rdev);
, and is not modified until it is passed to the ioctl here:
if (ioctl(fd, VT_ACTIVATE, vt) == -1) {

Perhaps you could add printf("vt: %d\n", vt); in between each of those ioctls between when vt is set on line 353, and used on line 385?

My only thought is that somehow the structures in the linux headers used to build swc-launch don't match your running kernel, which is causing one of the ioctls to clobber the value of vt.

Could you describe your operating system and the toolchain you used to build swc?

@michaelforney
Copy link
Owner

michaelforney commented Nov 12, 2018

Whoops, I meant ioctl(5, VT_ACTIVATE, 0xb7756fb4) looks bogus. The VT_SETMODE looks fine.

@DmitryHetman
Copy link

How are you starting velox? You need to launch it with swc-launch. For example, swc-launch velox.

mesa with wayland support should be irrelevant since swc uses wld, not mesa.

Is it bad for performance?

@michaelforney michaelforney transferred this issue from michaelforney/velox Mar 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants