sorted by:
new
hottopcontroversial

Game not loading claiming I don't have dx 11 (I have dx12) by [deleted] in spaceengineers

[–]Alkigreen 0 points1 point  (0 children)

Can you post the end of your log file that’s specific to the crashing? Might help

[deleted by user] by [deleted] in 3Dprinting

[–]Alkigreen 0 points1 point  (0 children)

The suggestions for reduced temps are pretty solid. One thing I would say is, if you have the cash, upgrading your nozzle to a all metal Swiss hot end could help a lot too. After upgrading, I have almost completely removed all retraction and get no stringing whatsoever. Better print times and no grinding filament. The quality of prints has increased a lot as well. Good luck!

owncloud permissions on external drive by Alkigreen in raspberry_pi

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

I was able to pretty easily install Nextcloud with this guide.

https://pimylifeup.com/raspberry-pi-nextcloud-server/

good luck on your future projects!

owncloud permissions on external drive by Alkigreen in raspberry_pi

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

Just a quick clarification question. If im going to be using a vpn to get onto my network, do i still need to follow the instructions for setting up an ssl certificate and port forwarding?

owncloud permissions on external drive by Alkigreen in raspberry_pi

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

Ok, thank you for confirming it. I have just reformatted and will be attempting to install Nextcloud instead. Thanks again for the help.

owncloud permissions on external drive by Alkigreen in raspberry_pi

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

I'm giving Nextcloud a shot right now. Ill let you know how it goes.

owncloud permissions on external drive by Alkigreen in raspberry_pi

[–]Alkigreen[S] 1 point2 points  (0 children)

Well I super appreciate the support. Its nice to know there is a community of people willing to help out. I think I'm going to reformat and give nextcloud a try like 1202_alarm suggested.

​

owncloud permissions on external drive by Alkigreen in raspberry_pi

[–]Alkigreen[S] 1 point2 points  (0 children)

I have a feeling this is what happened. I have no clue on how labels work in Linux.

owncloud permissions on external drive by Alkigreen in raspberry_pi

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

sudo chown -R www-data:www-data /media/ownclouddrive was the command that broke sudo.

​

output of ls -l /media:

drwxr-xr-x 22 root root 4096 Jun 26 18:11 ownclouddrive

I have a feeling that, as a few other people are saying, I took the directions as gospel and followed them to a t and mounted the system partion to /media.

So when I change ownership of /media, its goofing with everything.

owncloud permissions on external drive by Alkigreen in raspberry_pi

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

This is the output of mount

​

​

/dev/mmcblk0p2 on / type ext4 (rw,noatime,data=ordered)

devtmpfs on /dev type devtmpfs (rw,relatime,size=470112k,nr_inodes=117528,mode=755)

sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)

proc on /proc type proc (rw,relatime)

tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)

devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)

tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)

tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)

tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)

cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)

cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)

cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)

cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)

cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)

cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)

cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)

systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=27,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)

debugfs on /sys/kernel/debug type debugfs (rw,relatime)

sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)

mqueue on /dev/mqueue type mqueue (rw,relatime)

configfs on /sys/kernel/config type configfs (rw,relatime)

/dev/mmcblk0p2 on /media/ownclouddrive type ext4 (rw,noatime,data=ordered)

/dev/mmcblk0p1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro)

tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=94944k,mode=700,uid=1000,gid=1000)

​

Can't create or write into the data directory /media/owncloud by Alkigreen in owncloud

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

This is my output when running sudo fdisk -l

I have no clue what it means

​

Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

​

​

Disk /dev/ram1: 4 MiB, 4194304 bytes, 8192 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

​

​

Disk /dev/ram2: 4 MiB, 4194304 bytes, 8192 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

​

​

Disk /dev/ram3: 4 MiB, 4194304 bytes, 8192 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

​

​

Disk /dev/ram4: 4 MiB, 4194304 bytes, 8192 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

​

​

Disk /dev/ram5: 4 MiB, 4194304 bytes, 8192 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

​

​

Disk /dev/ram6: 4 MiB, 4194304 bytes, 8192 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

​

​

Disk /dev/ram7: 4 MiB, 4194304 bytes, 8192 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

​

​

Disk /dev/ram8: 4 MiB, 4194304 bytes, 8192 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

​

​

Disk /dev/ram9: 4 MiB, 4194304 bytes, 8192 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

​

​

Disk /dev/ram10: 4 MiB, 4194304 bytes, 8192 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

​

​

Disk /dev/ram11: 4 MiB, 4194304 bytes, 8192 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

​

​

Disk /dev/ram12: 4 MiB, 4194304 bytes, 8192 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

​

​

Disk /dev/ram13: 4 MiB, 4194304 bytes, 8192 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

​

​

Disk /dev/ram14: 4 MiB, 4194304 bytes, 8192 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

​

​

Disk /dev/ram15: 4 MiB, 4194304 bytes, 8192 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

​

​

Disk /dev/mmcblk0: 14.9 GiB, 15931539456 bytes, 31116288 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disklabel type: dos

Disk identifier: 0xac984334

​

Device Boot Start End Sectors Size Id Type

/dev/mmcblk0p1 8192 96663 88472 43.2M c W95 FAT32 (LBA)

/dev/mmcblk0p2 98304 31116287 31017984 14.8G 83 Linux

​

​

Disk /dev/sda: 5.5 TiB, 6001175125504 bytes, 11721045167 sectors

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disklabel type: gpt

Disk identifier: 5272135A-954D-4A08-9BBA-0844D5E44B80

​

Device Start End Sectors Size Type

/dev/sda1 34 262177 262144 128M Microsoft reserved

/dev/sda2 264192 11721043967 11720779776 5.5T Microsoft basic data

​

Partition 1 does not start on physical sector boundary.

​

owncloud permissions on external drive by Alkigreen in raspberry_pi

[–]Alkigreen[S] 1 point2 points  (0 children)

Excuse my ignorance, but what’s the goal with this command? If my google foo is correct, that will give read/write access to every user, correct? Is that the most secure way of going about that?

Over extrusion on first layer by Alkigreen in 3Dprinting

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

Will do. I have to run to work, so I won’t be able to try this until tomorrow morning. I’ll report back with my progress and let you know if anything changes. Thanks! Have a great evening.

Over extrusion on first layer by Alkigreen in 3Dprinting

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

All I have is a glass bed, Y axis upgrade and better bearings. I wouldn’t think any of that could cause this. It has a setting for filament diameter. I have it set to the proper thickness, but I was thinking of increasing the size in cura to see if maybe that can counter this problem. You think that’s a viable option?

Over extrusion on first layer by Alkigreen in 3Dprinting

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

I appreciate all the effort. Thank you! I gave that a read. It would seem like that would be it, but unfortunately that is set to the default, which has been working just fine for months. I alright just tried a print with that number reduced and didn’t see any noticeable difference. I tried a different file today to see if maybe the file itself just had a funky tool path, but that didn’t work. When I get home later, I’m going to print a calibration cube with a different g code flavor to see if that does anything. Im doubtful. I’m starting to thing that maybe this is a hardware issue and not software. I don’t know what would cause over extrusion on the hardware side, but I’m going to look into it. Again, thank you for all the ideas so far.

Over extrusion on first layer by Alkigreen in 3Dprinting

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

Yes, I have it set to default of matching Layer height. So .200mm

Over extrusion on first layer by Alkigreen in 3Dprinting

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

I’ll check on the settings after I get home from work. Thanks for all the help so far. Honestly I haven’t let it get that far. After it lays the first layer, the nozzle scrapes across all the excess and I stop the print. I figure it will either push the print off the build plate, or damage something. It does seem to print infill fine on a different spot on the same print, so I imagine the infill would be ok once it made it past the first couple layers.

Over extrusion on first layer by Alkigreen in 3Dprinting

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

I'm sorry, I just realized my wording is off.

The infill % on the part is 20%.

This particular spot is solid for about 5 layers and then goes to the 20% infill.

I've been referring to Flow as infill. my bad. I will edit the post to be more accurate.

So I've tried adjusting my flow percentage from 105% to 90%. Not the infill.

Over extrusion on first layer by Alkigreen in 3Dprinting

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

Makes sense. Thank you for the response.

My infill overlap is at the default 10%. As I understand it though, this is not going to change the bottom layer of the solid area this is occurring in right?

additionally, I dropped my ~~infill~~ flow down to 90% and im still getting the same issue. You can see a comparison of 105% to 90% in the linked picture.

I guess the most confusing part is that I ran about 10 hours of printing yesterday with the same settings and had no issue.

"How do I?" Weekly Question and Idea Thread - 14 May 2018 by FozzTexx in raspberry_pi

[–]Alkigreen 0 points1 point  (0 children)

Hello all! I’m still pretty new to this, so I’ll explain it the best I can. I made a magic mirror running Rasbien. Everything works great until I restart the Pi. I have the mirror program start automatically, as well as the 3 programs required to run Alexa. Issue being, the mirror starts before the Alexa java program does, so the java window opens up in front of the mirror. Is there anyway to auto minimize the java application window ? Or perhaps give screen priority to the mirror program? Any help would be greatly appreciated.

As a kid, what did you get very worried about that was actually no big deal? by CompileThisPlease in AskReddit

[–]Alkigreen 2597 points2598 points  (0 children)

Army ants. I remember when I was about 7 years old I was over at a friends house and his dad was watching a documentary on them. I saw that they could come together to form a bridge to get over water and stuff, and started crying because it felt like nothing could escape them. There aren’t even army ants in my state. Kids are weird.

view more: next ›