# 3.7.10 alpha release

**URL:** <https://forum.elivelinux.org/t/3-7-10-alpha-release/1462>\
**Category:** Betatest\
**Created:** [September 15, 2019, 2:29pm UTC](https://forum.elivelinux.org/t/3-7-10-alpha-release/1462 "2019-09-15T14:29:29Z")\
**Posts on this page:** 20\
**Page:** 4

<div class="post-metadata">

**Author:** ![triantares](https://forum.elivelinux.org/user_avatar/forum.elivelinux.org/triantares/32/2550_2.png) [@triantares](https://forum.elivelinux.org/u/triantares)\
**Post date:** [September 25, 2019, 8:55am UTC](https://forum.elivelinux.org/t/3-7-10-alpha-release/1462/61 "2019-09-25T08:55:31Z")

</div>

> [@Thanatermesis](#):
>
> ![image](https://forum.elivelinux.org/uploads/default/original/2X/0/0ca2f585c8cea7a5bd2416eb6aa2e07c5d8f6397.png)

The text needs some correcting. 😸  
In case you want to create a new partition on your hard disk, you need to abort the installation in the next screen and start over. The first steps of the installer will offer the opportunity to use the partitioner and change the state of your disks.

---

<div class="post-metadata">

**Author:** ![Franc](https://forum.elivelinux.org/user_avatar/forum.elivelinux.org/franc/32/729_2.png) [@Franc](https://forum.elivelinux.org/u/Franc)\
**Post date:** [September 25, 2019, 1:53pm UTC](https://forum.elivelinux.org/t/3-7-10-alpha-release/1462/62 "2019-09-25T13:53:00Z")

</div>

Hi!

Installation & partitioning...  
Perhaps a clear indication, somewhere, previously, about the requirements/options as partitions, for different cases (legacy / uefi / secure boot / winloose / x32 / x64...) should be a point, avoiding the user to "didn't know / forget" when installer asks about /bios, /boot or so and cancel to go GParted & co..?

Ih!

BTW: Elive x64 is the only Linux system I know that "eventually" needs this /bios partition: why this particularity? Sounds to me as a risk that should be somewhat controlled regularly (each start?) by the OS via sd5 summ or so..?

---

<div class="post-metadata">

**Author:** ![Franc](https://forum.elivelinux.org/user_avatar/forum.elivelinux.org/franc/32/729_2.png) [@Franc](https://forum.elivelinux.org/u/Franc)\
**Post date:** [September 27, 2019, 8:39am UTC](https://forum.elivelinux.org/t/3-7-10-alpha-release/1462/63 "2019-09-27T08:39:00Z")

</div>

Hello!

> [@Thanatermesis](#):
>
> issues with suspend / hibernate

This part, on the eeepc 1015pn, is resolved by installing eeepc-apci-scripts via synaptic..! 🙂  
But the same operation didn't resolve the lack of sound fn keys, nor wifi-bluetooth on/off one...  
About the "waves" on/off, did you eventually have a shell command to deal with it (already looked after that but no real results for now)?

Salutations!

---

<div class="post-metadata">

**Author:** ![Thanatermesis](https://forum.elivelinux.org/user_avatar/forum.elivelinux.org/thanatermesis/32/3_2.png) [@Thanatermesis](https://forum.elivelinux.org/u/Thanatermesis)\
**Post date:** [September 28, 2019, 12:07am UTC](https://forum.elivelinux.org/t/3-7-10-alpha-release/1462/64 "2019-09-28T00:07:20Z")

</div>

> [@triantares](#):
>
> The text needs some correcting. 😸  
> In case you want to create a new partition on your hard disk, you need to abort the installation in the next screen and start over. The first steps of the installer will offer the opportunity to use the partitioner and change the state of your disks.

thanks, I updated it on the installer but... 🤔

the part which says "to use the partitioners **in the correct state** of your disks" doesn't means to change the state of the disks, it really means that the disks are "a correct status to be correctly partitoned" (I probably didn't spellt this correctly on my phrase).

_More specifically: This means that the hard disk needs to have the encryption layers disabled and all partitions umounted (only then you can change the partitions schemes, otherwise you will get an error about that), this is done automatically on the start of the installer, that is what i meant on that message_

will wait your reply @triantares before to commit this change

> [@Franc](#):
>
> Perhaps a clear indication, somewhere, previously, about the requirements/options as partitions, for different cases (legacy / uefi / secure boot / winloose / x32 / x64...) should be a point, avoiding the user to "didn't know / forget" when installer asks about /bios, /boot or so and cancel to go GParted & co..?

that's included in the "give me extra help during installation" 🙂 (but this message is old, maybe it can have an update / improvement

> [@Franc](#):
>
> BTW: Elive x64 is the only Linux system I know that "eventually" needs this /bios partition: why this particularity? Sounds to me as a risk that should be somewhat controlled regularly (each start?) by the OS via sd5 summ or so..?

not exactly for x64, this is more like this:

- MSDOS type disks doesn't require anything
- GPT type disks requires a BIOS partition
- EFI booting computers needs a EFI partition

but the installer autodetects every case and tells you which one you need to have during install 🙂

> [@Franc](#):
>
> This part, on the eeepc 1015pn, is resolved by installing eeepc-apci-scripts via synaptic..! 🙂

interesting... can you show me the link given from this command? (run it on the eeepc machine)

> sudo dmidecode | elivepaste

next:

> [@Franc](#):
>
> But the same operation didn't resolve the lack of sound fn keys, nor wifi-bluetooth on/off one...

run the command **xev** and on the white window press one of these buttons, show me the result that appears in your termina FROM the parenthesis, like this example:

> state 0x0, keycode 36 (keysym 0xff0d, **Return** ), same\_screen YES,

> [@Franc](#):
>
> About the "waves" on/off, did you eventually have a shell command to deal with it (already looked after that but no real results for now)?

it doesn't looks like 🤔

---

<div class="post-metadata">

**Author:** ![triantares](https://forum.elivelinux.org/user_avatar/forum.elivelinux.org/triantares/32/2550_2.png) [@triantares](https://forum.elivelinux.org/u/triantares)\
**Post date:** [September 28, 2019, 6:17am UTC](https://forum.elivelinux.org/t/3-7-10-alpha-release/1462/65 "2019-09-28T06:17:23Z")

</div>

> [@Thanatermesis](#):
>
> the part which says "to use the partitioners **in the correct state** of your disks" doesn't means to change the state of the disks, it really means that the disks are "a correct status to be correctly partitoned" (I probably didn't spellt this correctly on my phrase).

Ah, I see.  
in that case:  
In case you want to create a new partition on your hard disk, you need to abort the installation in the next screen and start over. The first steps of the installer will offer the opportunity to use the partitioner and allow altering your disk geometry.

Just keeping it simple, then. 😸

---

<div class="post-metadata">

**Author:** ![triantares](https://forum.elivelinux.org/user_avatar/forum.elivelinux.org/triantares/32/2550_2.png) [@triantares](https://forum.elivelinux.org/u/triantares)\
**Post date:** [September 28, 2019, 11:06am UTC](https://forum.elivelinux.org/t/3-7-10-alpha-release/1462/66 "2019-09-28T11:06:31Z")

</div>

A suggestion or 2 for @Thanatermesis concerning the instaler.

- Regarding the UEFI and secure boot, we have always had to disable secure boot which is what triggers this add BIOS/GPT partition in the first place.  
I, for one had forgotten on some machines to reset that.

Maybe a suggestion should also be added to reboot with "secure boot" enabled making the installer use the BIOS/GPT partition that's probably already there.

- The pop-up "verifying integrity" takes quite a while with no feedback at all, while hitting OK  
just makes it dissapear.

Maybe having only a moving pop-up like the ones before and after is better....or disable the OK button and show a progress bar?

- On a machine with multiple OSes the partitions get shown but, if like me you have multiple versions of the same installed .... it gets confusing without having noted the partition schemes before.

Maybe adding the partition size of the discovered OSes is a nice addition to make chosing easier?

---

<div class="post-metadata">

**Author:** ![maxinou](https://forum.elivelinux.org/user_avatar/forum.elivelinux.org/maxinou/32/496_2.png) [@maxinou](https://forum.elivelinux.org/u/maxinou)\
**Post date:** [September 28, 2019, 1:31pm UTC](https://forum.elivelinux.org/t/3-7-10-alpha-release/1462/67 "2019-09-28T13:31:41Z")

</div>

> [@Thanatermesis](#):
>
> note: I have see on the reports that some people press this cancel button, some of these reports included an extremely slow never-finishing install (so its good) and some others just pressed by some uknown reason

I'm sorry I'm one of those people, as I installed a lot the alpha releases in my crappy laptops first times system was apparently frozen (due to my low RAM) so I cancel and start again, other times I didn't agree with my choices (pop-up that I clicked too fast without read them because after multiple installation I didn't put attention on them) or even because I change my first idea to partition my HDD and didn't want installer to finish..... I'm sorry if those multiple cancellation gives you a headache... in any case installer had been very improved since first alpha release and now even 64 bit release install is slow, but fine in my 1 GB RAM Acer laptop

> [@Thanatermesis](#):
>
> Ok let me answer this "requested" feature for some time 🙂  
> _mentions: @Rebel450, @triantares, @yoda_
> 
> It is true that is a good feature to have, but **I won't invest** time on making it in the near future, because of:
> 
> - it is a not-so-needed feature for the cost to pay to have it, which is:
> - **will require a probably entire rewrite of the installer itself (and its 13k lines of code, 66k words in the code)**
> - it will be dangerous 🙂
> 
> Now let me explain the details of that:
> 
> the installer was originally made 10 years ago, and since then it has been improving in every aspect and also its code, but since the code has originally a type of structure (functions + linear steps), to add the feature to "go back in steps" would require a big rewrite, with everything being much more "based in functions" and much more dynamic. Everything should be changed since their linear steps should be install just callback steps, this is a really big massive work (probably an entire month), and even worse, this will lead to tons of new unknown states, for example, calling a function that calls another with an unexpected value/variable, or lacking values in next steps, or updating a value that should not... this is extremely delicated thing (and so dangerous) in an installer, since a partition that should be not formated can be formated, or similar things

In that case I agree with you, leave installer in peace because normally it will be used only one time (I install alphas so much times that I know actually my WiFi password without need to read it LOL)

---

<div class="post-metadata">

**Author:** ![maxinou](https://forum.elivelinux.org/user_avatar/forum.elivelinux.org/maxinou/32/496_2.png) [@maxinou](https://forum.elivelinux.org/u/maxinou)\
**Post date:** [September 28, 2019, 2:27pm UTC](https://forum.elivelinux.org/t/3-7-10-alpha-release/1462/68 "2019-09-28T14:27:07Z")

</div>

BTW, in 32 bits release sometimes conky battery indicator is shown twice, and one of those indicator is always 0% while another shows real battery charge status (100% in this case)

![image](https://forum.elivelinux.org/uploads/default/original/2X/5/5bfbdb3489001ae2b01503a2cc2ba4c269c9cc38.png)

I doesn't verify if it happens in 64 bit release too....

---

<div class="post-metadata">

**Author:** ![Thanatermesis](https://forum.elivelinux.org/user_avatar/forum.elivelinux.org/thanatermesis/32/3_2.png) [@Thanatermesis](https://forum.elivelinux.org/u/Thanatermesis)\
**Post date:** [September 29, 2019, 12:42am UTC](https://forum.elivelinux.org/t/3-7-10-alpha-release/1462/69 "2019-09-29T00:42:44Z")

</div>

> [@triantares](#):
>
> Regarding the UEFI and secure boot, we have always had to disable secure boot which is what triggers this add BIOS/GPT partition in the first place.  
> I, for one had forgotten on some machines to reset that.

Hum... this not works exactly that way (if i understood correctly)

- secureboot has nothing to do with everything else, it just boots systems which are signed and that's all (depends on UEFI btw)
- a GPT-table disk requires a BIOS partition (required for legacy-boot), unless the computer booted in UEFI which then needs an EFI partition

> [@triantares](#):
>
> - The pop-up "verifying integrity" takes quite a while with no feedback at all, while hitting OK  
> just makes it dissapear.

noted

> [@triantares](#):
>
> - On a machine with multiple OSes the partitions get shown but, if like me you have multiple versions of the same installed .... it gets confusing without having noted the partition schemes before.  
> Maybe adding the partition size of the discovered OSes is a nice addition to make chosing easier?

this is what exactly does (at least in some selection of partition gui's), it shows multiple information from them like the filesystem, the size (if im not wrong), and the OS included inside too (if any). Again: if im not wrong 🙂 , if you can add a screenshot of your specific case I can check how it could be improved

> [@maxinou](#):
>
> I'm sorry if those multiple cancellation gives you a headache...

not at all! I was brainstorming this "button pressed sometimes" to know if there's a usability problem there. If im not wrong, the cancel button is now disabled for the upgrade-mode and this should be not an issue (but maybe when low-ram? hum! tell me if you see an issue with that!)

> [@maxinou](#):
>
> in any case installer had been very improved since first alpha release and now even 64 bit release install is slow, but fine in my 1 GB RAM Acer laptop

yeah! and pretty much improved since the version included in the stable version too!

> [@maxinou](#):
>
> BTW, in 32 bits release sometimes conky battery indicator is shown twice, and one of those indicator is always 0% while another shows real battery charge status (100% in this case)

hum, that should happen when you have 2 batteries, but maybe is a bug, show me the result of this command on your machine @maxinou:

> acpi  
> sudo acpi

---

<div class="post-metadata">

**Author:** ![triantares](https://forum.elivelinux.org/user_avatar/forum.elivelinux.org/triantares/32/2550_2.png) [@triantares](https://forum.elivelinux.org/u/triantares)\
**Post date:** [September 29, 2019, 10:53am UTC](https://forum.elivelinux.org/t/3-7-10-alpha-release/1462/70 "2019-09-29T10:53:50Z")

</div>

> [@Thanatermesis](#):
>
> if you can add a screenshot of your specific case I can check how it could be improved

Yes, I can. I used vokoscreen whilst installing and saved them on an external USB drive. :smiley14:

 ![Elive_Screenshot_2019-09-29_12%3A47%3A58__700x337](https://forum.elivelinux.org/uploads/default/original/2X/2/2cf687ea5ba71d7c6385a84b2d808af47ea456ee.png)

In this case I'm in the unclear which one I actually wanted to upgrade .......... I did remember that one was a smaller test partition. So having a partition size mentioned might be nice.  
No big thing, just a thought. 😸

---

<div class="post-metadata">

**Author:** ![triantares](https://forum.elivelinux.org/user_avatar/forum.elivelinux.org/triantares/32/2550_2.png) [@triantares](https://forum.elivelinux.org/u/triantares)\
**Post date:** [September 29, 2019, 10:57am UTC](https://forum.elivelinux.org/t/3-7-10-alpha-release/1462/71 "2019-09-29T10:57:58Z")

</div>

> [@Thanatermesis](#):
>
> a GPT-table disk requires a BIOS partition (required for legacy-boot), unless the computer booted in UEFI which then needs an EFI partition

Exactly ...... so if booted in legacy mode the EFI partition will not be seen and the question about the BIOS partition pops up.  
If rebooted in UEFI the installer would use that EFI partition without prompting ........ always worth a try, hey? 🤔

---

<div class="post-metadata">

**Author:** ![zbd](https://forum.elivelinux.org/user_avatar/forum.elivelinux.org/zbd/32/777_2.png) [@zbd](https://forum.elivelinux.org/u/zbd)\
**Post date:** [September 29, 2019, 2:05pm UTC](https://forum.elivelinux.org/t/3-7-10-alpha-release/1462/72 "2019-09-29T14:05:22Z")

</div>

In 3.7.10 in live mode now, and I get no lag so far, so you may be onto something...

---

<div class="post-metadata">

**Author:** ![Thanatermesis](https://forum.elivelinux.org/user_avatar/forum.elivelinux.org/thanatermesis/32/3_2.png) [@Thanatermesis](https://forum.elivelinux.org/u/Thanatermesis)\
**Post date:** [September 29, 2019, 11:02pm UTC](https://forum.elivelinux.org/t/3-7-10-alpha-release/1462/73 "2019-09-29T23:02:24Z")

</div>

> [@triantares](#):
>
> In this case I'm in the unclear which one I actually wanted to upgrade .......... I did remember that one was a smaller test partition. So having a partition size mentioned might be nice.

ah, you mean this one, hum...

It is meant that with the hostname (machine name), the original version and even the partition number/disk should be enough to know but... ok, I have noted it in my big TODO tasks lists in the section of the installer, i will make a look 🙂

> [@triantares](#):
>
> Exactly ...... so if booted in legacy mode the EFI partition will not be seen and the question about the BIOS partition pops up.  
> If rebooted in UEFI the installer would use that EFI partition without prompting ........ always worth a try, hey? 🤔

not sure to understand, yes, this is what the installer does (using what is needed to use for each case), and it also automatically pick that partition if is automatically found (without asking), so this is a good thing

> [@zbd](#):
>
> In 3.7.10 in live mode now, and I get no lag so far, so you may be onto something...

im also trying to upload version 3.7.11 but something strange is happening in my internet, connection is stable but any ssh connection is cut 😕 we will need to wait for 3.7.11

---

<div class="post-metadata">

**Author:** ![Rebel450](https://forum.elivelinux.org/user_avatar/forum.elivelinux.org/rebel450/32/2737_2.png) [@Rebel450](https://forum.elivelinux.org/u/Rebel450)\
**Post date:** [September 30, 2019, 7:07am UTC](https://forum.elivelinux.org/t/3-7-10-alpha-release/1462/74 "2019-09-30T07:07:20Z")

</div>

> [@Thanatermesis](#):
>
> we will need to wait for 3.7.11

It would be good to have a short note about the changes made, may be on top of the pending release thread of the new alpha or so ....

With the time we loose the overview about what has changed in comparison to the former release,  
also because fixes and changes were made 'on the fly' between from your side.  
So it is a bit hard to follow ( all ! forum messages needs to be read and noted for having a chance to know about progress made )

Note:  
Especially for PR -  
it's time to find a common way of communication about the progress made

- what was optimized under the hood
- what was changed

I am sure you will have a documentation about your steps made,  
may be it's easy just copy & paste the " milestones"  
? ? ?

Kdrgds

---

<div class="post-metadata">

**Author:** ![Thanatermesis](https://forum.elivelinux.org/user_avatar/forum.elivelinux.org/thanatermesis/32/3_2.png) [@Thanatermesis](https://forum.elivelinux.org/u/Thanatermesis)\
**Post date:** [October 1, 2019, 2:49pm UTC](https://forum.elivelinux.org/t/3-7-10-alpha-release/1462/75 "2019-10-01T14:49:07Z")

</div>

> [@Rebel450](#):
>
> It would be good to have a short note about the changes made, may be on top of the pending release thread of the new alpha or so ....

everything on its own time 🙂 lol

Done!: [3.7.11 alpha release](https://forum.elivelinux.org/t/3-7-11-alpha-release/1495)

---

<div class="post-metadata">

**Author:** ![Rebel450](https://forum.elivelinux.org/user_avatar/forum.elivelinux.org/rebel450/32/2737_2.png) [@Rebel450](https://forum.elivelinux.org/u/Rebel450)\
**Post date:** [October 1, 2019, 5:06pm UTC](https://forum.elivelinux.org/t/3-7-10-alpha-release/1462/76 "2019-10-01T17:06:02Z")

</div>

> [@Thanatermesis](#):
>
> Done!: [3.7.11 alpha release](https://forum.elivelinux.org/t/3-7-11-alpha-release/1495)

_ **Wow** _ !!! :omfg: & :hug:  
:madness:

---

<div class="post-metadata">

**Author:** ![Thanatermesis](https://forum.elivelinux.org/user_avatar/forum.elivelinux.org/thanatermesis/32/3_2.png) [@Thanatermesis](https://forum.elivelinux.org/u/Thanatermesis)\
**Post date:** [October 4, 2019, 11:36pm UTC](https://forum.elivelinux.org/t/3-7-10-alpha-release/1462/77 "2019-10-04T23:36:02Z")

</div>

> [@triantares](#):
>
> - The pop-up "verifying integrity" takes quite a while with no feedback at all, while hitting OK  
> just makes it dissapear.
> 
> Maybe having only a moving pop-up like the ones before and after is better....or disable the OK button and show a progress bar?

implemented 🙂

---

<div class="post-metadata">

**Author:** ![Dominyk](https://forum.elivelinux.org/letter_avatar_proxy/v4/letter/d/ebca7d/32.png) [@Dominyk](https://forum.elivelinux.org/u/Dominyk)\
**Post date:** [November 26, 2019, 10:42am UTC](https://forum.elivelinux.org/t/3-7-10-alpha-release/1462/78 "2019-11-26T10:42:09Z")

</div>

Touchscreen on a Samsung Tablet, 'On Screen'...... not present..... Am I missing something? Cannot install without Keyboard.....

---

<div class="post-metadata">

**Author:** ![triantares](https://forum.elivelinux.org/user_avatar/forum.elivelinux.org/triantares/32/2550_2.png) [@triantares](https://forum.elivelinux.org/u/triantares)\
**Post date:** [November 26, 2019, 9:40pm UTC](https://forum.elivelinux.org/t/3-7-10-alpha-release/1462/79 "2019-11-26T21:40:05Z")

</div>

No you're not missing something, it's not there.  
Despite my personal ramblings and persuasions ...... "onboard" has never been added by default in the greeter. If you can (using an external keyboard) you can add it yourself to have it available at a next boot.  
We made a Howto here:

> [@3.7.3 betatesting experiences](https://forum.elivelinux.org/t/3-7-3-betatesting-experiences/1157/178):
>
> For people wanting onboard (virtual keyboard) in the lightdm-greeter, which is a handy feature to have around for touchscreens as well is for broken keyboards. Configure " /etc/lightdm/lightdm-gtk-greeter" as root with sudo. i.e " sudo nano /etc/lightdm/light-dm-greeter". Go to the end of the file under [screen] and remove the # and add " onboard" behind " keyboard=" thus: [Elive\_Screenshot\_2019-06-07\_19%3A20%3A44\_\_2132x1126] Save it and on next login you' ll have the option added to the …

---

<div class="post-metadata">

**Author:** ![Thanatermesis](https://forum.elivelinux.org/user_avatar/forum.elivelinux.org/thanatermesis/32/3_2.png) [@Thanatermesis](https://forum.elivelinux.org/u/Thanatermesis)\
**Post date:** [December 12, 2019, 4:39pm UTC](https://forum.elivelinux.org/t/3-7-10-alpha-release/1462/80 "2019-12-12T16:39:03Z")

</div>

> [@triantares](#):
>
> We made a Howto here:
> 
> [3.7.3 betatesting experiences](https://forum.elivelinux.org/t/3-7-3-betatesting-experiences/1157/178) [Betatest](https://forum.elivelinux.org/c/get-involved/betatest)

I think you should move this good post to a new thread in the Howto's section 🙂

[Previous page](https://forum.elivelinux.org/t/3-7-10-alpha-release/1462.md?page=3)

[Next page](https://forum.elivelinux.org/t/3-7-10-alpha-release/1462.md?page=5)
