Closed tonydm closed 9 months ago
same for me
It appears that @RudraSwat has too many irons in the fire. He's a brilliant young man but I fear he hasn't the discipline to manage multiple projects. And, perhaps, there's other extenuating circumstances that we are not aware. Looking at a couple pages of listed issues, I don't see a single response from @RudraSwat. BlendOS is an awesome project and is/was much more exciting than VaniliaOS. But alas, I fear he's abandoned it. Looking back at his projects activity, I see very little activity. Too bad. I'm going to move on for now and perhaps sometime in the future we'll see this project take shape, if someone else hasn't. Best
Hi, I usually don't monitor the issues on this repo, just the ones against the individual repositories. blendOS is nowhere near abandoned, and I'm thinking of features for the next release. I haven't been able to reproduce this on any of my systems, and only just noticed this bug from an email from GitHub since you tagged me. Could you, perhaps, join the Discord server for blendOS and mention this issue there just to confirm it's not an issue only for you? Thanks :)
Hi @RudraSwat
for me it is a clevo N130WU... I can not speak for @tonydm. True is that we have both hanging systems.
@tonydm do you have a WD NVME SSD?
It appears that @RudraSwat has too many irons in the fire. He's a brilliant young man but I fear he hasn't the discipline to manage multiple projects. And, perhaps, there's other extenuating circumstances that we are not aware. Looking at a couple pages of listed issues, I don't see a single response from @RudraSwat. BlendOS is an awesome project and is/was much more exciting than VaniliaOS. But alas, I fear he's abandoned it. Looking back at his projects activity, I see very little activity. Too bad. I'm going to move on for now and perhaps sometime in the future we'll see this project take shape, if someone else hasn't. Best
I understand your concern. He hasn't. I'm sorry he hasn't responded @tonydm, he's probably busy with school or something blendOS-related. I believe he's trying to get some fixes into ubuntu unity before the UI freeze.
Thanks for trying blend at least.
also did you use etcher to flash the USB?
also did you use etcher to flash the USB?
yes
@frankenstein91 what happens when you wait for the systemd jobs to time out?
@frankenstein91 what happens when you wait for the systemd jobs to time out?
they freeze
fixed by removing my NVME SSD and booting from DVD
wow.
Ah great, I'll close this issue then.
@RudraSwat - I wasn't able to follow up yesterday as I was otherwise unavailable. With that said, my issue is not resolved so I'm curious why the issue "I opened" was Closed?
I'm pleased and excited to hear that the project is not dead and that you have plans to improve. But with respect... you mentioned that you "don't monitor the issues on this repo". Why? That's what Github is for; to post a project and a place to discuss issues and handle Pulls and Merge Requests. I get that Discord seems to be all the rage, but posting a project here and then effectively abandoning the "Issues" posted doesn't seem appropriate.
Then there's the issue I mentioned above. Why you closed this issue? Again, with respect, you seemed to have lost sight of the originator of the Issue. I'm baffled
@frankenstein91 - I don't have a WD NVME. I have a Samsung 970 EVO NVME, Samsung 860 EVO SSD, and 2 WD REDs spinning. I was attempting to install to the Samsung SSD 860 EVO. This is not my primary drive. The Samsung 970 EVO NVME is my primary. I like others mentioned, downloaded the ISOs several times both KDE and Gnome. I burned with Etcher and also tried with dd on several USB sticks. I cleared the target drive of any boot partitions, etc.
"what happens when you wait for the systemd jobs to time out?" - nothing, installation hangs. For context, left and came back several hours later.
Thank you
@tonydm are you able to remove the NVME for testing.
I have known and forgotten... and now know again, that some devices have problems with APST. On my old arch linux I had set a kernel parameter to fix it.
yesterday I booted Arch in debug and found it again... (WD and Samsung are known for that bug)
As blendOS is immutable I did not know how to set kernel parameters persistent... so I removed the device
@frankenstein91 Thanks for that info. I wasn't aware. The 970 NVME is my primary drive and I was using the 870 SSD to test. I'll pass for now. It's not hoop I want to jump through at this time for my daily driver. But thanks
I burned the blendos.iso using etcher to a samsung 128gb usb. Booted to usb and install initialization starts but hangs/fails just after
Hostname Service
and msg...AER: Error of this Agent reported first
. I have no idea what this represents. I have tried downloading the KDE iso again with no boot success. I've tried the Gnome version, same failure. I have tried a smaller capacity USB Thumb drive my last attempt using a 4GB thumb drive. I have other iso's/drives that boot via UEFI and have no issues. I am excited to try BlendOS, but DOA :(Thank you
inxi output w/ relative info