Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - VastOne

Pages: 1 2 [3] 4 5 ... 259
32
Thanks, those I can control and fix

 8)

33
NM was never a part of VSIDO

ceni is now Ceni

Some dumbass thought it would be cute to rename it and not use any symlinks

sudo Ceni works fine

34
I have little time to investigate what's the difference between partition label and partition name (since msdos disks obviously do support labels, so wtf!?) together with what changed in Debian that suddenly made this an issue.
So I've just taken a blunt approach and made the installer check if labels are supported, before trying to populate the UI with them.

See here: https://gitlab.com/Cofi/trios-installer/commit/90310e899dab429d5c62a95a10e92898225ae434

So the biggest potential "issue" if I got it wrong is that the labels won't show in the UI when they are actually supported.
If I get some time later today I'll go through the install fully (by mistake I booted into a VM I need/cannot format the disk), and burn the ISO on the flash and check it out on the metal... Right now it doesn't get stuck on the partition list screen.
With that said, until I get to it, I suggest testing in a VM only, just in case  :) Also, as usual, the fix is in the "testing" branch, so make sure you build the installer from it :)

Hey filip .. I have found an issue with the grub install section that I think is related to this that we solved

The only known issues I am aware of is that grub stalls during the install with the following message

Code: [Select]
WARNING: Device /dev/sda1 not initialized in udev database even after waiting 1000000 microseconds
I think it is an installer issue related to what @filip fixed in locating the drives, I think the grub part of the installer also cannot find the drives but does the install fine anyway

THat message can be seen of you run the installer from terminal

I do not see this message on a normal grub install or update to grub, it is only from within the installer

35
  • Updated VSIDO to latest Debian SID kernel – 4.19.0-4-amd64 #1 SMP Debian 4.19.28-2 (2019-03-15)
  • Updated all applications to the latest SID levels

All changes can be seen and discussed in the VSIDO Change sub forum

All files and torrents can be downloaded from the VSIDO Download page

________________________________


After nearly a year, I have made some changes..

There is only the x64 and x64_uEFI versions now and forevermore

We are up to kernel 4.19 and I anticipate going to 5 in the next month

The only known issues I am aware of is that grub stalls during the install with the following message

Code: [Select]
WARNING: Device /dev/sda1 not initialized in udev database even after waiting 1000000 microseconds
I think it is an installer issue related to what @filip fixed in locating the drives, I think the grub part of the installer also cannot find the drives but does the install fine anyway

I also have a new machine now, a uEFII machine donated to VSIDO by Luke / lwfitz so I can do all real time testing now onto HW

I also want to thank jedi, whose friendship and patience are one of the rocks behind VSIDO

Enjoy and please let me know of any issues

36
Artwork & Screenshots / Re: 2019 Screenshot Thread
« on: March 26, 2019, 11:19:32 PM »
New machine and the first new ISO's in almost a year now building


 

37
General Support / uEFI and grub2
« on: March 22, 2019, 12:15:32 AM »
Back story is simple, I have been away for a while and caught up with almost everything regarding the VSIDO build but there seems to be a big change in what ever grub uEFI uses (i know it is grub-efi-amd64) but something is completely different

Before (and still with legacy x64 VSIDO) to make sure eth0 was the correct name of the network interface all we had to do was make sure net.ifnames=0 is on the GRUB_CMDLINE_LINUX_DEFAULT= line in /etc/default/grub file

That has not changed, and as a matter of fact the line is there on a liveCD but what appears to have changed is grub-efi-amd no longer reads /etc/default/grub

The proof is this.. When you boot to the test uEFI ISO that is now available and tab to edit the grub line and add net.ifnames=0 to  the Linux (kernel) line it does in fact boot correctly with eth0 as the network interface name

So the question is simple

When you do add that parameter on a liveCD boot, what exactly is it being written to?

This all works as it should on Legacy x64 VSIDO which is also in that directory suggesting that it is definitely a uefi grub issue only

38
I have uploaded the working x64 to the Test directory..

I am (re)building the uEFI (not working) for testing and will upload it to testing when it is done

39
First round of testing on V-Box a complete success ...

By Midnight CST there should be new ISO's

Thank you filip!!!

40
Thank you filip.. When I get home later tonight I will install and confirm the fix

I no longer understand debians need to just change shit for the sake of change ...  ??? >:( ::)

41
It only worked for me in V-Box by completely removing the drives in gparted and recreating them in gparted.. Once I did BOTH and only both then they both showed up

It kept failing if I did only one drive so if you are not in a V-Box make sure you have only what drive you want to use installed

This is the Ugly Stick approach to an install until this issue is resolved

Thanks RatMan for the feedback and help

42
Artwork & Screenshots / Re: 2019 Screenshot Thread
« on: March 18, 2019, 11:33:40 PM »
Nice 5.02 Kernel there Jedi...

Anyone heard anything about when it will hit Debian Repos?

44
Artwork & Screenshots / Re: 2019 Screenshot Thread
« on: March 18, 2019, 12:56:33 AM »
^ Yes Obi-Wan, Yes

45
On the python questions, I have no idea.. seems backwards compatibility has taken a backseat in the Debian world and seems more a question for the developers of the installer

mtools is stock installed in VSIDO

I am not sure on the gpt question, if I understand it all you would have to wipe everything to go to a gpt partition table so if you have to do the same with an msdos table, why would you?  As to if I am missing a msdos partition table, these machines and V-Box setup have always had the exact same msdos partition tables from the beginning...

The solution (create a msdos partition table while in LiveCD) seems as if that is the issue, but how is that possible if there always was a partition table and the April 2018 ISO's no doubt see the partitions and partition table

 ??? ??? ???

Pages: 1 2 [3] 4 5 ... 259