Re: [Torios-dev] March Debian Testing ISO
Den 2018-03-16 kl. 01:09, skrev Israel: 1. It fails in the advanced mode, rather than the basic mode, correct? in the most recent version. The most recent version of the iso file fails at *both* the basic and advanced OBI level. But thinks worked last night (Swedish time) after update & upgrade, when I started from the previous version of the iso file (with md5sum=efa3eba6bf82fdadfa340fcfb19e1e2b). Best regards Nio -- Mailing list: https://launchpad.net/~torios-dev Post to : torios-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~torios-dev More help : https://help.launchpad.net/ListHelp
Re: [Torios-dev] March Debian Testing ISO
On 03/15/2018 04:47 PM, Nio Wiklund wrote: > Den 2018-03-15 kl. 21:54, skrev Nio Wiklund: >> Den 2018-03-15 kl. 20:54, skrev Nio Wiklund: >>> Den 2018-03-15 kl. 14:16, skrev Israel: On 03/15/2018 05:10 AM, Nio Wiklund wrote: Hi Nio > Hi again Israel, > > I tested again starting from the previous iso file with md5sum: > > efa3eba6bf82fdadfa340fcfb19e1e2b ToriOS-2018-03-13-beta-stretch-i386.iso > > This one works as it is, and after update & upgrade it can install the > PAE kernel (I tested in graphics mode at the basic OBI level into > another SSD this time.) > > But it suffers from one (minor) bug: > > It offers to check for updates, but fails: thinks that there is no > internet connection, even though it could fetch the PAE kernel via the > internet a few seconds ago. > > See the log file. > > Best regards > Nio I read your e-mails and have done some investigating based on your logs. 1. It fails in the advanced mode, rather than the basic mode, correct? in the most recent version. This is due to some improvements in the basic mode that I did not add to advanced yet (oops...) things should work better soon. 2. There is something wonky about the internet going on, I tested and found the same issue. Basically it seems like the issue is systemd. /etc/resolv.conf is no longer a normal file, but a symlink handled by systemd. So... I have been looking at Arch for some help, and found something good to try. :D I will try to get something up soon... but it will take a bit more testing. -- Regards -- Mailing list: https://launchpad.net/~torios-dev Post to : torios-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~torios-dev More help : https://help.launchpad.net/ListHelp
Re: [Torios-dev] March Debian Testing ISO
Den 2018-03-15 kl. 21:54, skrev Nio Wiklund: Den 2018-03-15 kl. 20:54, skrev Nio Wiklund: Den 2018-03-15 kl. 14:16, skrev Israel: On 03/15/2018 05:10 AM, Nio Wiklund wrote: Hi again, I found the following information about the i686 kernel at https://packages.debian.org/stretch/linux-image-4.9.0-6-686 The Linux kernel 4.9 and modules for use on PCs with one or more processors not supporting PAE. What about this link? https://packages.debian.org/stretch/linux-image-4.9.0-6-686-pae The Linux kernel 4.9 and modules for use on PCs with one or more processors supporting PAE. Best regards Nio Hey Nio, As it turns out, the code used in Jessie does precisely this :D And, as it were, I already had this code working for stretch. I disabled it, however, because I thought that the 686 kernel defaulted to PAE. So, I made a bug unintentionally, because I misunderstood Stretch. This is great news! This means Stretch will support the computers we want YAY!!! So, I am currently rebuilding OBI for Stretch and sometime soon you can: sudo apt update && sudo apt install obi-installer And try it out. I think I fixed all the issues you mentioned in a decent way. Mostly I just offer to start the Graphical environment for the user and restart the install process, or they can exit. Since it is for advanced users they should be able to figure the rest out. If you get a chance to check it out it will be this version: obi-installer - 3.4.0ubuntu0-345~ubuntu18.04.1 Thanks for catching this issue!! Hi Israel, 1. Graphical Installer I could install with the PAE kernel using the graphical installer :-) (I tested at the advanced OBI level). And the installed system can use all the RAM :-) 2. Text installer But I could not install at all using the text installer (in text mode). Some bug was introduced, because it worked in the previous version :-( There was a complaint that the chroot could not be started, and later on there were some errors, I guess because of that. The installer could continue (but maybe the result would be bad, but at the time zone I could not get the Swedish time zone accepted. The .profile file 'could not be found'. Best regards Nio Hi again Israel, Sorry for the confusion. 1. When I reported, that it worked to install using the graphical installer, it was an updated and upgraded system from the previous iso file with md5sum: efa3eba6bf82fdadfa340fcfb19e1e2b ToriOS-2018-03-13-beta-stretch-i386.iso 2. while the current iso file fails also with the graphical installer (tested at the advanced OBI level in both cases). 95e885db3b976cb1578d32d940674233 ToriOS-2018-03-15-beta-stretch-i386.iso I tried both without and with update & upgrade to the current obi-installer - 3.4.0ubuntu0-345~ubuntu18.04.1. I get complaints about failing chroot and am kicked back to an earlier menu of the installer after the second complaint about chroot (when trying to install the bootloader). Maybe something happened to the packages in the meantime? See the attached log files I tried also at the basic OBI level (with the newest iso file and updated obi-installer). There were errors in the information in the zenity windows: for example, nothing displayed in the final warning window, which can be scary. I continued anyway, because it was a test drive anyway. But I was kicked back to an earlier window of the installer. Best regards Nio Hi again Israel, I tested again starting from the previous iso file with md5sum: efa3eba6bf82fdadfa340fcfb19e1e2b ToriOS-2018-03-13-beta-stretch-i386.iso This one works as it is, and after update & upgrade it can install the PAE kernel (I tested in graphics mode at the basic OBI level into another SSD this time.) But it suffers from one (minor) bug: It offers to check for updates, but fails: thinks that there is no internet connection, even though it could fetch the PAE kernel via the internet a few seconds ago. See the log file. Best regards Nio Start at: Thu Mar 15 21:32:12 UTC 2018 [starter] Tarball path: /tarballs zmktbl to make the tarballs OBI path: /usr/share/OBI [starter] Had to find a tarball.. OBI found /tarballs/ToriOS-i386-stretch.tar.xz OS to install: ToriOS-i386-stretchMenu Title: OS to install: ToriOS-i386-stretch [starter] starter chose: i [obi] Found pid for Zenity in obi: 11032 [position_win] Found 0x0122 for the window to position [mkctl] obi_system=ToriOS-i386-stretch tarball=/tarballs/ToriOS-i386-stretch.tar.xz [obi] Selected Tarball: /tarballs/ToriOS-i386-stretch.tar.xz selecting mkp2p1 (with swap) [mkctl] obi_system=ToriOS-i386-stretch tarball=/tarballs/ToriOS-i386-stretch.tar.xz [list_drives] DRIVE: Name: ata-KINGSTON_SKC300S37A120G Dev: /dev/sda Size: 120GB [list_drives] DRIVE: Name: usb-Kanguru_FlashBlu Dev: /dev/sdb Size: 8011MB [obi-functions] ltest0=overlay ltest1=/sdb livedrive=/sdb tmpstr=Name: ata-KINGSTON_SKC300S37A120G Dev: /dev/sda Size: 120GB Name: usb-Kanguru_Flash
Re: [Torios-dev] March Debian Testing ISO
Den 2018-03-15 kl. 20:54, skrev Nio Wiklund: Den 2018-03-15 kl. 14:16, skrev Israel: On 03/15/2018 05:10 AM, Nio Wiklund wrote: Hi again, I found the following information about the i686 kernel at https://packages.debian.org/stretch/linux-image-4.9.0-6-686 The Linux kernel 4.9 and modules for use on PCs with one or more processors not supporting PAE. What about this link? https://packages.debian.org/stretch/linux-image-4.9.0-6-686-pae The Linux kernel 4.9 and modules for use on PCs with one or more processors supporting PAE. Best regards Nio Hey Nio, As it turns out, the code used in Jessie does precisely this :D And, as it were, I already had this code working for stretch. I disabled it, however, because I thought that the 686 kernel defaulted to PAE. So, I made a bug unintentionally, because I misunderstood Stretch. This is great news! This means Stretch will support the computers we want YAY!!! So, I am currently rebuilding OBI for Stretch and sometime soon you can: sudo apt update && sudo apt install obi-installer And try it out. I think I fixed all the issues you mentioned in a decent way. Mostly I just offer to start the Graphical environment for the user and restart the install process, or they can exit. Since it is for advanced users they should be able to figure the rest out. If you get a chance to check it out it will be this version: obi-installer - 3.4.0ubuntu0-345~ubuntu18.04.1 Thanks for catching this issue!! Hi Israel, 1. Graphical Installer I could install with the PAE kernel using the graphical installer :-) (I tested at the advanced OBI level). And the installed system can use all the RAM :-) 2. Text installer But I could not install at all using the text installer (in text mode). Some bug was introduced, because it worked in the previous version :-( There was a complaint that the chroot could not be started, and later on there were some errors, I guess because of that. The installer could continue (but maybe the result would be bad, but at the time zone I could not get the Swedish time zone accepted. The .profile file 'could not be found'. Best regards Nio Hi again Israel, Sorry for the confusion. 1. When I reported, that it worked to install using the graphical installer, it was an updated and upgraded system from the previous iso file with md5sum: efa3eba6bf82fdadfa340fcfb19e1e2b ToriOS-2018-03-13-beta-stretch-i386.iso 2. while the current iso file fails also with the graphical installer (tested at the advanced OBI level in both cases). 95e885db3b976cb1578d32d940674233 ToriOS-2018-03-15-beta-stretch-i386.iso I tried both without and with update & upgrade to the current obi-installer - 3.4.0ubuntu0-345~ubuntu18.04.1. I get complaints about failing chroot and am kicked back to an earlier menu of the installer after the second complaint about chroot (when trying to install the bootloader). Maybe something happened to the packages in the meantime? See the attached log files I tried also at the basic OBI level (with the newest iso file and updated obi-installer). There were errors in the information in the zenity windows: for example, nothing displayed in the final warning window, which can be scary. I continued anyway, because it was a test drive anyway. But I was kicked back to an earlier window of the installer. Best regards Nio Start at: Thu Mar 15 20:33:01 UTC 2018 [starter] Tarball path: /tarballs zmktbl to make the tarballs OBI path: /usr/share/OBI [starter] Had to find a tarball.. OBI found /tarballs/ToriOS-i386-stretch.tar.xz OS to install: ToriOS-i386-stretch Menu Title: OS to install: ToriOS-i386-stretch [starter] starter chose: o [setlevel] using: advanced [starter] Had to find a tarball.. OBI found /tarballs/ToriOS-i386-stretch.tar.xz OS to install: ToriOS-i386-stretch Menu Title: OS to install: ToriOS-i386-stretch OS to install: ToriOS-i386-stretch Menu Title: OS to install: ToriOS-i386-stretch [starter] starter chose: i [obi] Found pid for Zenity in obi: 8363 [position_win] Found 0x0122 for the window to position [mkctl] obi_system=ToriOS-i386-stretch tarball=/tarballs/ToriOS-i386-stretch.tar.xz [obi] Selected Tarball: /tarballs/ToriOS-i386-stretch.tar.xz selecting mkpxpy (with swap) [mkctl] obi_system=ToriOS-i386-stretch tarball=/tarballs/ToriOS-i386-stretch.tar.xz [confirm-partition] /dev/sda5 was not mounted [select-part2] after dialog or zenity: ans=sda6 [select-part2] rootpart=/dev/sda6 swappart=/dev/sda5 [select-part2] obi-root:/dev/sda6 obi-swap:/dev/sda5 [confirm-partition] /dev/sda6 was not mounted [confirm-partition] /dev/sda5 was not mounted [confirm-partition] g [confirm-partition] Installing ToriOS-i386-stretch /dev/sda6 with swap /dev/sda5 [confirm-partition] mklub ToriOS-i386-stretch /tarballs/ToriOS-i386-stretch.tar.xz /dev/sda6 /dev/sda5 [mkpxpy] ToriOS-i386-stretch /tarballs/ToriOS-i386-stretch.tar.xz [mkp] Found pid for Zenity in mkp: 8363 [position_win] Found 0x0120
Re: [Torios-dev] March Debian Testing ISO
Den 2018-03-15 kl. 20:54, skrev Nio Wiklund: Den 2018-03-15 kl. 14:16, skrev Israel: On 03/15/2018 05:10 AM, Nio Wiklund wrote: Hi again, I found the following information about the i686 kernel at https://packages.debian.org/stretch/linux-image-4.9.0-6-686 The Linux kernel 4.9 and modules for use on PCs with one or more processors not supporting PAE. What about this link? https://packages.debian.org/stretch/linux-image-4.9.0-6-686-pae The Linux kernel 4.9 and modules for use on PCs with one or more processors supporting PAE. Best regards Nio Hey Nio, As it turns out, the code used in Jessie does precisely this :D And, as it were, I already had this code working for stretch. I disabled it, however, because I thought that the 686 kernel defaulted to PAE. So, I made a bug unintentionally, because I misunderstood Stretch. This is great news! This means Stretch will support the computers we want YAY!!! So, I am currently rebuilding OBI for Stretch and sometime soon you can: sudo apt update && sudo apt install obi-installer And try it out. I think I fixed all the issues you mentioned in a decent way. Mostly I just offer to start the Graphical environment for the user and restart the install process, or they can exit. Since it is for advanced users they should be able to figure the rest out. If you get a chance to check it out it will be this version: obi-installer - 3.4.0ubuntu0-345~ubuntu18.04.1 Thanks for catching this issue!! Hi Israel, 1. Graphical Installer I could install with the PAE kernel using the graphical installer :-) (I tested at the advanced OBI level). And the installed system can use all the RAM :-) 2. Text installer But I could not install at all using the text installer (in text mode). Some bug was introduced, because it worked in the previous version :-( There was a complaint that the chroot could not be started, and later on there were some errors, I guess because of that. The installer could continue (but maybe the result would be bad, but at the time zone I could not get the Swedish time zone accepted. The .profile file 'could not be found'. Best regards Nio Attaching the log file Start at: Thu Mar 15 19:42:40 UTC 2018 [starter] Tarball path: /tarballs mktbl to make the tarballs OBI path: /usr/share/OBI [starter] Had to find a tarball.. OBI found /tarballs/ToriOS-i386-stretch.tar.xz OS to install: ToriOS-i386-stretchMenu Title: OS to install: ToriOS-i386-stretch [starter] starter chose: o [setlevel] using: advanced [starter] Had to find a tarball.. OBI found /tarballs/ToriOS-i386-stretch.tar.xz OS to install: ToriOS-i386-stretchMenu Title: OS to install: ToriOS-i386-stretch OS to install: ToriOS-i386-stretchMenu Title: OS to install: ToriOS-i386-stretch [starter] starter chose: i [mkctl] obi_system=ToriOS-i386-stretch tarball=/tarballs/ToriOS-i386-stretch.tar.xz [obi] Selected Tarball: /tarballs/ToriOS-i386-stretch.tar.xz selecting mkpxpy (with swap) [mkctl] obi_system=ToriOS-i386-stretch tarball=/tarballs/ToriOS-i386-stretch.tar.xz [confirm-partition] /dev/sda5 was not mounted [select-part2] after dialog or zenity: ans=sda6 [select-part2] rootpart=/dev/sda6 swappart=/dev/sda5 [select-part2] obi-root:/dev/sda6 obi-swap:/dev/sda5 [confirm-partition] /dev/sda6 was not mounted [confirm-partition] /dev/sda5 was not mounted [confirm-partition] g [confirm-partition] Installing ToriOS-i386-stretch /dev/sda6 with swap /dev/sda5 [confirm-partition] mklub ToriOS-i386-stretch /tarballs/ToriOS-i386-stretch.tar.xz /dev/sda6 /dev/sda5 [mkpxpy] ToriOS-i386-stretch /tarballs/ToriOS-i386-stretch.tar.xz [mkp] Extracting: /tarballs/ToriOS-i386-stretch.tar.xz [mkp] /tarballs/ToriOS-i386-stretch.tar.xz (the tarball) is expanded, syncing the drive [mkp] chroot command: sync [mkpxpy] [mkpxpy] blkid for /dev/sda5 = /dev/sda5: LABEL="obiswap" UUID="8afccbdf-71d0-4269-814e-0d4ad3621196" TYPE="swap" PARTUUID="c88bc6dc-05" (if exists) [mkpxpy] Use existing swap partition /dev/sda5 - keep its UUID [mkp] rootpart=/dev/sda6 [mkp] swappart=/dev/sda5 [mkp] NEW swap UUID=8afccbdf-71d0-4269-814e-0d4ad3621196 [mkp] rootpart=/dev/sda6 NEW root UUID=ee66b4db-2ed5-44e3-abe6-eda027a3e938 [mkp] Made /mnt/etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # # / was on /dev/sda6 during installation UUID=ee66b4db-2ed5-44e3-abe6-eda027a3e938 / ext4errors=remount-ro 0 1 # swap was on /dev/sda5 during installation UUID=8afccbdf-71d0-4269-814e-0d4ad3621196 noneswapsw 0 0 [mkp] chroot command: uname -a [hw-progress] ACPI [hw-progress] rtl8723ae [hw-progress] rtl8723ae [hw-progress] rtl8723ae [hw-progress] bluetooth [hw-progress] bluetooth [hw-progress] r8169 [hw-progress] r8169 [hw-progress] r8169 [h
Re: [Torios-dev] March Debian Testing ISO
Den 2018-03-15 kl. 14:16, skrev Israel: On 03/15/2018 05:10 AM, Nio Wiklund wrote: Hi again, I found the following information about the i686 kernel at https://packages.debian.org/stretch/linux-image-4.9.0-6-686 The Linux kernel 4.9 and modules for use on PCs with one or more processors not supporting PAE. What about this link? https://packages.debian.org/stretch/linux-image-4.9.0-6-686-pae The Linux kernel 4.9 and modules for use on PCs with one or more processors supporting PAE. Best regards Nio Hey Nio, As it turns out, the code used in Jessie does precisely this :D And, as it were, I already had this code working for stretch. I disabled it, however, because I thought that the 686 kernel defaulted to PAE. So, I made a bug unintentionally, because I misunderstood Stretch. This is great news! This means Stretch will support the computers we want YAY!!! So, I am currently rebuilding OBI for Stretch and sometime soon you can: sudo apt update && sudo apt install obi-installer And try it out. I think I fixed all the issues you mentioned in a decent way. Mostly I just offer to start the Graphical environment for the user and restart the install process, or they can exit. Since it is for advanced users they should be able to figure the rest out. If you get a chance to check it out it will be this version: obi-installer - 3.4.0ubuntu0-345~ubuntu18.04.1 Thanks for catching this issue!! Hi Israel, 1. Graphical Installer I could install with the PAE kernel using the graphical installer :-) (I tested at the advanced OBI level). And the installed system can use all the RAM :-) 2. Text installer But I could not install at all using the text installer (in text mode). Some bug was introduced, because it worked in the previous version :-( There was a complaint that the chroot could not be started, and later on there were some errors, I guess because of that. The installer could continue (but maybe the result would be bad, but at the time zone I could not get the Swedish time zone accepted. The .profile file 'could not be found'. Best regards Nio -- Mailing list: https://launchpad.net/~torios-dev Post to : torios-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~torios-dev More help : https://help.launchpad.net/ListHelp
Re: [Torios-dev] March Debian Testing ISO
On 03/15/2018 05:10 AM, Nio Wiklund wrote: > Hi again, > > I found the following information about the i686 kernel at > > https://packages.debian.org/stretch/linux-image-4.9.0-6-686 > > The Linux kernel 4.9 and modules for use on PCs with one or more > processors not supporting PAE. > > What about this link? > > https://packages.debian.org/stretch/linux-image-4.9.0-6-686-pae > > The Linux kernel 4.9 and modules for use on PCs with one or more > processors supporting PAE. > > Best regards > Nio Hey Nio, As it turns out, the code used in Jessie does precisely this :D And, as it were, I already had this code working for stretch. I disabled it, however, because I thought that the 686 kernel defaulted to PAE. So, I made a bug unintentionally, because I misunderstood Stretch. This is great news! This means Stretch will support the computers we want YAY!!! So, I am currently rebuilding OBI for Stretch and sometime soon you can: sudo apt update && sudo apt install obi-installer And try it out. I think I fixed all the issues you mentioned in a decent way. Mostly I just offer to start the Graphical environment for the user and restart the install process, or they can exit. Since it is for advanced users they should be able to figure the rest out. If you get a chance to check it out it will be this version: obi-installer - 3.4.0ubuntu0-345~ubuntu18.04.1 Thanks for catching this issue!! -- Regards -- Mailing list: https://launchpad.net/~torios-dev Post to : torios-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~torios-dev More help : https://help.launchpad.net/ListHelp
Re: [Torios-dev] March Debian Testing ISO
Hi Nio (inline below) On 03/15/2018 03:12 AM, Nio Wiklund wrote: > Den 2018-03-13 kl. 23:29, skrev Israel: >> On 03/13/2018 02:48 PM, Nio Wiklund wrote: >>> Den 2018-03-13 kl. 18:08, skrev Israel: >>> ... >>> Hi Israel, >>> >> Hi Nio >> (inlines below) >>> I downloaded the current iso file and tested it. >>> >>> 1. zsync failed for me (I tried twice). I have a user at phillw.net, >>> and I could identify the file and get it (and the md5sum) via sftp. >>> >> Hmmm... it may be because I zsync the symlink... I just amended this! >>> 2. I logged into the live graphical desktop environment. It looked >>> good, but I did not really test it this time. >>> >> Great! >>> 3. I rebooted and selected the OBI in text mode. It worked and I could >>> install ToriOS (at the basic OBI level) :-) >>> >> Excellent! >>> 4. I tried to reboot into the installed system. But the computer shut >>> down instead. Is this by intention? >>> >> Hmmm... not sure why this happened. I will look into things might >> be a systemd quirk >>> 5. I booted into the installed system and it works. I did only some >>> superficial tests. >>> >> This is great, I am glad it works at the most basic level!! >>> I hope to get better time for more tests later. >>> >>> Best regards >>> Nio >> >> > > Hi again, > > > 1. Looking more into the text mode installer: > > - At the advanced level it offers 'Use gparted and show help', but > gparted is a GUI tool. > > This should be changed somehow, for example to suggest to select > graphics mode and use gparted, or to use some text mode partitioning > tool (possible but more difficult). On the other hand, in a computer, > that does not work at all with ToriOS live in graphics mode, ToriOS is > not a suitable operating system. > > It is reasonable to do the partitioning in graphics mode, then reboot > and run the installation in text mode (which needs less RAM). > > Anyway, it works via 'obiroot' and 'obiswap' as it should :-) > > ... and the installation was successful, a working system was > installed, and the previous system was available via the grub menu :-) > This is a very good point. I had not thought of this, and will have to do some reconsidering here. I suppose I could offer to launch the Graphical Desktop, or use parted if the user chooses. It would be good if I could somehow make a tool to provide the same functionality, but that is too complex for ToriOS 2.0 maybe in 2.5/3.0 > > 2. RAM management > > - In the installed system I notice, that the available RAM reported is > only 2675 MiB (but 4096 MiB is installed). It seems that the PAE, > Physical Address Extension, does not work correctly although it is > supposed to be an i686 version of Debian. > > It is the same with ToriOS live, while for example Lubuntu Bionic i386 > (which also has an i686 linux kernel) reports 3918 MiB (some of the > 4096 MiB is used for some administration). > > - Testing the available RAM in ToriOS 1.0 (based on Jessie): > > - The live system is i586 (non-pae) and free -m reports 2680 MiB, > which is what should be expected. > > - I installed ToriOS 1.0 including the PAE kernel, linux > 3.16.0-5-686-pae. > > Free reports 3928 MiB, similar to what Lubuntu Bionic reports. > > So there is something fishy with the new ToriOS based on Stretch. > Either it really uses a non-PAE kernel, or a PAE kernel that is not > really working correctly. Have you checked if there is a separate PAE > alternative available from Debian? > > > Best regards > Nio -- Regards -- Mailing list: https://launchpad.net/~torios-dev Post to : torios-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~torios-dev More help : https://help.launchpad.net/ListHelp
Re: [Torios-dev] March Debian Testing ISO
On 03/15/2018 05:10 AM, Nio Wiklund wrote: > Den 2018-03-15 kl. 10:57, skrev Nio Wiklund: >> Den 2018-03-15 kl. 09:12, skrev Nio Wiklund: >>> Den 2018-03-13 kl. 23:29, skrev Israel: On 03/13/2018 02:48 PM, Nio Wiklund wrote: > Den 2018-03-13 kl. 18:08, skrev Israel: > ... > Hi Israel, > Hi Nio (inlines below) > I downloaded the current iso file and tested it. > > 1. zsync failed for me (I tried twice). I have a user at phillw.net, > and I could identify the file and get it (and the md5sum) via sftp. > Hmmm... it may be because I zsync the symlink... I just amended this! > 2. I logged into the live graphical desktop environment. It looked > good, but I did not really test it this time. > Great! > 3. I rebooted and selected the OBI in text mode. It worked and I > could > install ToriOS (at the basic OBI level) :-) > Excellent! > 4. I tried to reboot into the installed system. But the computer shut > down instead. Is this by intention? > Hmmm... not sure why this happened. I will look into things might be a systemd quirk > 5. I booted into the installed system and it works. I did only some > superficial tests. > This is great, I am glad it works at the most basic level!! > I hope to get better time for more tests later. > > Best regards > Nio >>> >>> Hi again, >>> >>> >>> 1. Looking more into the text mode installer: >>> >>> - At the advanced level it offers 'Use gparted and show help', but >>> gparted is a GUI tool. >>> >>> This should be changed somehow, for example to suggest to select >>> graphics mode and use gparted, or to use some text mode partitioning >>> tool (possible but more difficult). On the other hand, in a >>> computer, that does not work at all with ToriOS live in graphics >>> mode, ToriOS is not a suitable operating system. >>> >>> It is reasonable to do the partitioning in graphics mode, then >>> reboot and run the installation in text mode (which needs less RAM). >>> >>> Anyway, it works via 'obiroot' and 'obiswap' as it should :-) >>> >>> ... and the installation was successful, a working system was >>> installed, and the previous system was available via the grub menu :-) >>> >>> >>> 2. RAM management >>> >>> - In the installed system I notice, that the available RAM reported >>> is only 2675 MiB (but 4096 MiB is installed). It seems that the PAE, >>> Physical Address Extension, does not work correctly although it is >>> supposed to be an i686 version of Debian. >>> >>> It is the same with ToriOS live, while for example Lubuntu Bionic >>> i386 (which also has an i686 linux kernel) reports 3918 MiB (some of >>> the 4096 MiB is used for some administration). >>> >>> - Testing the available RAM in ToriOS 1.0 (based on Jessie): >>> >>> - The live system is i586 (non-pae) and free -m reports 2680 MiB, >>> which is what should be expected. >>> >>> - I installed ToriOS 1.0 including the PAE kernel, linux >>> 3.16.0-5-686-pae. >>> >>> Free reports 3928 MiB, similar to what Lubuntu Bionic reports. >>> >>> So there is something fishy with the new ToriOS based on Stretch. >>> Either it really uses a non-PAE kernel, or a PAE kernel that is not >>> really working correctly. Have you checked if there is a separate >>> PAE alternative available from Debian? >>> >>> >>> Best regards >>> Nio >> >> Hi again Israel, >> >> I tested in my old IBM Thinkpad T42 with a non-pae kernel, that can >> work with fake-pae and forcepae boot options. >> >> It booted into ToriOS Stretch without adding any forcepae boot >> option. I don't know if you have added it, but this is what I saw in >> a terminal window of the live session: >> >> --- >> Welcome to ToriOS >> root@torios ~ # lsb_release -a >> No LSB modules are available. >> Distributor ID: ToriOS >> Description: ToriOS GNU/Linux 9.4 (stretch) >> Release: 9.4 >> Codename: stretch >> root@torios ~ # uname -a >> Linux torios 4.9.0-6-686 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) >> i686 GNU/Linux >> root@torios ~ # grep ^flags /proc/cpuinfo >> flags : fpu vme de pse tsc msr mce cx8 sep mtrr pge mca >> cmov clflush dts acpi mmx fxsr sse sse2 ss tm pbe bts eagerfpu est tm2 >> root@torios ~ # grep pae /proc/cpuinfo >> root@torios ~ # >> --- >> >> When I boot the T42 with Lubuntu Bionic, I have to use the boot >> option forcepae, and a PAE flag is detected >> >> --- >> lubuntu@lubuntu: # grep -o pae /proc/cpuinfo >> pae >> --- >> >> This makes me think that the i686 debian system has a non-PAE kernel. >> >> Have you checked if there is a separate PAE kernel alternative >> available from Debian? >> >> Best regards >> Nio > > Hi again, > > I found the following information about the i686 kernel at > > https://packages.debian.org/stretch/linux-image-4.9.0-6-686 > > The Linux kernel 4.9 and modules for use on PCs with one or more > processors not supporting PAE. > > What about this link?
Re: [Torios-dev] March Debian Testing ISO
Den 2018-03-15 kl. 10:57, skrev Nio Wiklund: Den 2018-03-15 kl. 09:12, skrev Nio Wiklund: Den 2018-03-13 kl. 23:29, skrev Israel: On 03/13/2018 02:48 PM, Nio Wiklund wrote: Den 2018-03-13 kl. 18:08, skrev Israel: ... Hi Israel, Hi Nio (inlines below) I downloaded the current iso file and tested it. 1. zsync failed for me (I tried twice). I have a user at phillw.net, and I could identify the file and get it (and the md5sum) via sftp. Hmmm... it may be because I zsync the symlink... I just amended this! 2. I logged into the live graphical desktop environment. It looked good, but I did not really test it this time. Great! 3. I rebooted and selected the OBI in text mode. It worked and I could install ToriOS (at the basic OBI level) :-) Excellent! 4. I tried to reboot into the installed system. But the computer shut down instead. Is this by intention? Hmmm... not sure why this happened. I will look into things might be a systemd quirk 5. I booted into the installed system and it works. I did only some superficial tests. This is great, I am glad it works at the most basic level!! I hope to get better time for more tests later. Best regards Nio Hi again, 1. Looking more into the text mode installer: - At the advanced level it offers 'Use gparted and show help', but gparted is a GUI tool. This should be changed somehow, for example to suggest to select graphics mode and use gparted, or to use some text mode partitioning tool (possible but more difficult). On the other hand, in a computer, that does not work at all with ToriOS live in graphics mode, ToriOS is not a suitable operating system. It is reasonable to do the partitioning in graphics mode, then reboot and run the installation in text mode (which needs less RAM). Anyway, it works via 'obiroot' and 'obiswap' as it should :-) ... and the installation was successful, a working system was installed, and the previous system was available via the grub menu :-) 2. RAM management - In the installed system I notice, that the available RAM reported is only 2675 MiB (but 4096 MiB is installed). It seems that the PAE, Physical Address Extension, does not work correctly although it is supposed to be an i686 version of Debian. It is the same with ToriOS live, while for example Lubuntu Bionic i386 (which also has an i686 linux kernel) reports 3918 MiB (some of the 4096 MiB is used for some administration). - Testing the available RAM in ToriOS 1.0 (based on Jessie): - The live system is i586 (non-pae) and free -m reports 2680 MiB, which is what should be expected. - I installed ToriOS 1.0 including the PAE kernel, linux 3.16.0-5-686-pae. Free reports 3928 MiB, similar to what Lubuntu Bionic reports. So there is something fishy with the new ToriOS based on Stretch. Either it really uses a non-PAE kernel, or a PAE kernel that is not really working correctly. Have you checked if there is a separate PAE alternative available from Debian? Best regards Nio Hi again Israel, I tested in my old IBM Thinkpad T42 with a non-pae kernel, that can work with fake-pae and forcepae boot options. It booted into ToriOS Stretch without adding any forcepae boot option. I don't know if you have added it, but this is what I saw in a terminal window of the live session: --- Welcome to ToriOS root@torios ~ # lsb_release -a No LSB modules are available. Distributor ID: ToriOS Description: ToriOS GNU/Linux 9.4 (stretch) Release: 9.4 Codename: stretch root@torios ~ # uname -a Linux torios 4.9.0-6-686 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) i686 GNU/Linux root@torios ~ # grep ^flags /proc/cpuinfo flags : fpu vme de pse tsc msr mce cx8 sep mtrr pge mca cmov clflush dts acpi mmx fxsr sse sse2 ss tm pbe bts eagerfpu est tm2 root@torios ~ # grep pae /proc/cpuinfo root@torios ~ # --- When I boot the T42 with Lubuntu Bionic, I have to use the boot option forcepae, and a PAE flag is detected --- lubuntu@lubuntu: # grep -o pae /proc/cpuinfo pae --- This makes me think that the i686 debian system has a non-PAE kernel. Have you checked if there is a separate PAE kernel alternative available from Debian? Best regards Nio Hi again, I found the following information about the i686 kernel at https://packages.debian.org/stretch/linux-image-4.9.0-6-686 The Linux kernel 4.9 and modules for use on PCs with one or more processors not supporting PAE. What about this link? https://packages.debian.org/stretch/linux-image-4.9.0-6-686-pae The Linux kernel 4.9 and modules for use on PCs with one or more processors supporting PAE. Best regards Nio -- Mailing list: https://launchpad.net/~torios-dev Post to : torios-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~torios-dev More help : https://help.launchpad.net/ListHelp
Re: [Torios-dev] March Debian Testing ISO
Den 2018-03-15 kl. 09:12, skrev Nio Wiklund: Den 2018-03-13 kl. 23:29, skrev Israel: On 03/13/2018 02:48 PM, Nio Wiklund wrote: Den 2018-03-13 kl. 18:08, skrev Israel: ... Hi Israel, Hi Nio (inlines below) I downloaded the current iso file and tested it. 1. zsync failed for me (I tried twice). I have a user at phillw.net, and I could identify the file and get it (and the md5sum) via sftp. Hmmm... it may be because I zsync the symlink... I just amended this! 2. I logged into the live graphical desktop environment. It looked good, but I did not really test it this time. Great! 3. I rebooted and selected the OBI in text mode. It worked and I could install ToriOS (at the basic OBI level) :-) Excellent! 4. I tried to reboot into the installed system. But the computer shut down instead. Is this by intention? Hmmm... not sure why this happened. I will look into things might be a systemd quirk 5. I booted into the installed system and it works. I did only some superficial tests. This is great, I am glad it works at the most basic level!! I hope to get better time for more tests later. Best regards Nio Hi again, 1. Looking more into the text mode installer: - At the advanced level it offers 'Use gparted and show help', but gparted is a GUI tool. This should be changed somehow, for example to suggest to select graphics mode and use gparted, or to use some text mode partitioning tool (possible but more difficult). On the other hand, in a computer, that does not work at all with ToriOS live in graphics mode, ToriOS is not a suitable operating system. It is reasonable to do the partitioning in graphics mode, then reboot and run the installation in text mode (which needs less RAM). Anyway, it works via 'obiroot' and 'obiswap' as it should :-) ... and the installation was successful, a working system was installed, and the previous system was available via the grub menu :-) 2. RAM management - In the installed system I notice, that the available RAM reported is only 2675 MiB (but 4096 MiB is installed). It seems that the PAE, Physical Address Extension, does not work correctly although it is supposed to be an i686 version of Debian. It is the same with ToriOS live, while for example Lubuntu Bionic i386 (which also has an i686 linux kernel) reports 3918 MiB (some of the 4096 MiB is used for some administration). - Testing the available RAM in ToriOS 1.0 (based on Jessie): - The live system is i586 (non-pae) and free -m reports 2680 MiB, which is what should be expected. - I installed ToriOS 1.0 including the PAE kernel, linux 3.16.0-5-686-pae. Free reports 3928 MiB, similar to what Lubuntu Bionic reports. So there is something fishy with the new ToriOS based on Stretch. Either it really uses a non-PAE kernel, or a PAE kernel that is not really working correctly. Have you checked if there is a separate PAE alternative available from Debian? Best regards Nio Hi again Israel, I tested in my old IBM Thinkpad T42 with a non-pae kernel, that can work with fake-pae and forcepae boot options. It booted into ToriOS Stretch without adding any forcepae boot option. I don't know if you have added it, but this is what I saw in a terminal window of the live session: --- Welcome to ToriOS root@torios ~ # lsb_release -a No LSB modules are available. Distributor ID: ToriOS Description:ToriOS GNU/Linux 9.4 (stretch) Release:9.4 Codename: stretch root@torios ~ # uname -a Linux torios 4.9.0-6-686 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) i686 GNU/Linux root@torios ~ # grep ^flags /proc/cpuinfo flags : fpu vme de pse tsc msr mce cx8 sep mtrr pge mca cmov clflush dts acpi mmx fxsr sse sse2 ss tm pbe bts eagerfpu est tm2 root@torios ~ # grep pae /proc/cpuinfo root@torios ~ # --- When I boot the T42 with Lubuntu Bionic, I have to use the boot option forcepae, and a PAE flag is detected --- lubuntu@lubuntu: # grep -o pae /proc/cpuinfo pae --- This makes me think that the i686 debian system has a non-PAE kernel. Have you checked if there is a separate PAE kernel alternative available from Debian? Best regards Nio -- Mailing list: https://launchpad.net/~torios-dev Post to : torios-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~torios-dev More help : https://help.launchpad.net/ListHelp
Re: [Torios-dev] March Debian Testing ISO
Den 2018-03-13 kl. 23:29, skrev Israel: On 03/13/2018 02:48 PM, Nio Wiklund wrote: Den 2018-03-13 kl. 18:08, skrev Israel: ... Hi Israel, Hi Nio (inlines below) I downloaded the current iso file and tested it. 1. zsync failed for me (I tried twice). I have a user at phillw.net, and I could identify the file and get it (and the md5sum) via sftp. Hmmm... it may be because I zsync the symlink... I just amended this! 2. I logged into the live graphical desktop environment. It looked good, but I did not really test it this time. Great! 3. I rebooted and selected the OBI in text mode. It worked and I could install ToriOS (at the basic OBI level) :-) Excellent! 4. I tried to reboot into the installed system. But the computer shut down instead. Is this by intention? Hmmm... not sure why this happened. I will look into things might be a systemd quirk 5. I booted into the installed system and it works. I did only some superficial tests. This is great, I am glad it works at the most basic level!! I hope to get better time for more tests later. Best regards Nio Hi again, 1. Looking more into the text mode installer: - At the advanced level it offers 'Use gparted and show help', but gparted is a GUI tool. This should be changed somehow, for example to suggest to select graphics mode and use gparted, or to use some text mode partitioning tool (possible but more difficult). On the other hand, in a computer, that does not work at all with ToriOS live in graphics mode, ToriOS is not a suitable operating system. It is reasonable to do the partitioning in graphics mode, then reboot and run the installation in text mode (which needs less RAM). Anyway, it works via 'obiroot' and 'obiswap' as it should :-) ... and the installation was successful, a working system was installed, and the previous system was available via the grub menu :-) 2. RAM management - In the installed system I notice, that the available RAM reported is only 2675 MiB (but 4096 MiB is installed). It seems that the PAE, Physical Address Extension, does not work correctly although it is supposed to be an i686 version of Debian. It is the same with ToriOS live, while for example Lubuntu Bionic i386 (which also has an i686 linux kernel) reports 3918 MiB (some of the 4096 MiB is used for some administration). - Testing the available RAM in ToriOS 1.0 (based on Jessie): - The live system is i586 (non-pae) and free -m reports 2680 MiB, which is what should be expected. - I installed ToriOS 1.0 including the PAE kernel, linux 3.16.0-5-686-pae. Free reports 3928 MiB, similar to what Lubuntu Bionic reports. So there is something fishy with the new ToriOS based on Stretch. Either it really uses a non-PAE kernel, or a PAE kernel that is not really working correctly. Have you checked if there is a separate PAE alternative available from Debian? Best regards Nio -- Mailing list: https://launchpad.net/~torios-dev Post to : torios-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~torios-dev More help : https://help.launchpad.net/ListHelp
Re: [Torios-dev] March Debian Testing ISO
On 03/14/2018 04:16 AM, psutton wrote: > > On 13/03/18 22:29, Israel wrote: >> ... >>> 4. I tried to reboot into the installed system. But the computer shut >>> down instead. Is this by intention? >>> > This happened to me too, so I can confirm this behavior. > Paul Hi Paul, This is a tricky one. So choosing "r Reboot" should run one of these. torios-reboot -y || sudo reboot || sudo shutdown -r now torios-reboot will run 'reboot' if the user is root (which we are in the live system). reboot is a systemd legacy command inclusion. So it has something to do with systemd... but I am not sure how to make systemd work correctly. I am not sure I know how to fix this one right now... but perhaps I see if something else is happening that is unexpected... I am not entirely sure here -- Regards -- Mailing list: https://launchpad.net/~torios-dev Post to : torios-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~torios-dev More help : https://help.launchpad.net/ListHelp
Re: [Torios-dev] March Debian Testing ISO
On 13/03/18 22:29, Israel wrote: > On 03/13/2018 02:48 PM, Nio Wiklund wrote: >> Den 2018-03-13 kl. 18:08, skrev Israel: >> ... >> Hi Israel, >> > Hi Nio > (inlines below) >> I downloaded the current iso file and tested it. >> >> 1. zsync failed for me (I tried twice). I have a user at phillw.net, >> and I could identify the file and get it (and the md5sum) via sftp. >> > Hmmm... it may be because I zsync the symlink... I just amended this! >> 2. I logged into the live graphical desktop environment. It looked >> good, but I did not really test it this time. >> > Great! >> 3. I rebooted and selected the OBI in text mode. It worked and I could >> install ToriOS (at the basic OBI level) :-) >> > Excellent! >> 4. I tried to reboot into the installed system. But the computer shut >> down instead. Is this by intention? >> This happened to me too, so I can confirm this behavior. Paul > Hmmm... not sure why this happened. I will look into things might > be a systemd quirk >> 5. I booted into the installed system and it works. I did only some >> superficial tests. >> > This is great, I am glad it works at the most basic level!! >> I hope to get better time for more tests later. >> >> Best regards >> Nio > -- Paul Sutton http://www.zleap.net Torbay Tech Jam - 2nd Saturday of the Month at Paignton Library -- Mailing list: https://launchpad.net/~torios-dev Post to : torios-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~torios-dev More help : https://help.launchpad.net/ListHelp
Re: [Torios-dev] March Debian Testing ISO
On 03/13/2018 02:48 PM, Nio Wiklund wrote: > Den 2018-03-13 kl. 18:08, skrev Israel: > ... > Hi Israel, > Hi Nio (inlines below) > I downloaded the current iso file and tested it. > > 1. zsync failed for me (I tried twice). I have a user at phillw.net, > and I could identify the file and get it (and the md5sum) via sftp. > Hmmm... it may be because I zsync the symlink... I just amended this! > 2. I logged into the live graphical desktop environment. It looked > good, but I did not really test it this time. > Great! > 3. I rebooted and selected the OBI in text mode. It worked and I could > install ToriOS (at the basic OBI level) :-) > Excellent! > 4. I tried to reboot into the installed system. But the computer shut > down instead. Is this by intention? > Hmmm... not sure why this happened. I will look into things might be a systemd quirk > 5. I booted into the installed system and it works. I did only some > superficial tests. > This is great, I am glad it works at the most basic level!! > I hope to get better time for more tests later. > > Best regards > Nio -- Regards -- Mailing list: https://launchpad.net/~torios-dev Post to : torios-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~torios-dev More help : https://help.launchpad.net/ListHelp
Re: [Torios-dev] March Debian Testing ISO
On 03/13/2018 12:43 PM, Cinque Port Computers wrote: > Hi Israel, > > Installed fine using graphical installer to VB. Auto-login worked > this time and installing chromium browser worked fine via Common Tasks. > > More testing later. > > Regards, > Jack > > ... Awesome!! Thanks Jack! -- Regards -- Mailing list: https://launchpad.net/~torios-dev Post to : torios-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~torios-dev More help : https://help.launchpad.net/ListHelp
Re: [Torios-dev] March Debian Testing ISO
Den 2018-03-13 kl. 18:08, skrev Israel: Hey everyone, You can zsync/download the latest ISO. I have it named as ToriOS-Testing.iso Here are the links! All in one download and check: http://phillw.net/isos/torios/ToriOS-Testing.iso.zsync ISO and manual md5sum http://phillw.net/isos/torios/ToriOS-Testing.iso http://phillw.net/isos/torios/md5sum.testing Paul noticed some issues with the user configuration dialogs in his testing, and those are fixed, but *NOT* in this ISO... they will be in the next build. I also noticed I need to update JWM for this version... there may be some minor issues from this (jwm -p will complain about the 'Mouse' tag until I do update it) AFAIK autologin works... at least it has the past 4-5 times for me on my VMs, so this is fixed. Memory is now displayed properly in the text-mode-menu. Things work pretty well now, and PAE installation should NOT show up, since Stretch does not have a non-PAE kernel neither does bionic for that matter which we may need to address at some point. The 'firstrun' dialog should now actually work. If it doesn't: sudo apt update && sudo apt -y full-upgrade && firstrun And see if it works... I may not have gotten the update in (not sure I've rebuilt and tested and tweaked so much in the past few days I cannot say for sure if the update is in) So... test and see how close we are! -- Regards Hi Israel, I downloaded the current iso file and tested it. 1. zsync failed for me (I tried twice). I have a user at phillw.net, and I could identify the file and get it (and the md5sum) via sftp. 2. I logged into the live graphical desktop environment. It looked good, but I did not really test it this time. 3. I rebooted and selected the OBI in text mode. It worked and I could install ToriOS (at the basic OBI level) :-) 4. I tried to reboot into the installed system. But the computer shut down instead. Is this by intention? 5. I booted into the installed system and it works. I did only some superficial tests. I hope to get better time for more tests later. Best regards Nio -- Mailing list: https://launchpad.net/~torios-dev Post to : torios-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~torios-dev More help : https://help.launchpad.net/ListHelp
Re: [Torios-dev] March Debian Testing ISO
Hi Israel, Installed fine using graphical installer to VB. Auto-login worked this time and installing chromium browser worked fine via Common Tasks. More testing later. Regards, Jack From: Torios-dev on behalf of Israel Sent: 13 March 2018 5:08 PM To: torios- dev Subject: [Torios-dev] March Debian Testing ISO Hey everyone, You can zsync/download the latest ISO. I have it named as ToriOS-Testing.iso Here are the links! All in one download and check: http://phillw.net/isos/torios/ToriOS-Testing.iso.zsync ISO and manual md5sum http://phillw.net/isos/torios/ToriOS-Testing.iso http://phillw.net/isos/torios/md5sum.testing Paul noticed some issues with the user configuration dialogs in his testing, and those are fixed, but NOT in this ISO... they will be in the next build. I also noticed I need to update JWM for this version... there may be some minor issues from this (jwm -p will complain about the 'Mouse' tag until I do update it) AFAIK autologin works... at least it has the past 4-5 times for me on my VMs, so this is fixed. Memory is now displayed properly in the text-mode-menu. Things work pretty well now, and PAE installation should NOT show up, since Stretch does not have a non-PAE kernel neither does bionic for that matter which we may need to address at some point. The 'firstrun' dialog should now actually work. If it doesn't: sudo apt update && sudo apt -y full-upgrade && firstrun And see if it works... I may not have gotten the update in (not sure I've rebuilt and tested and tweaked so much in the past few days I cannot say for sure if the update is in) So... test and see how close we are! -- Regards -- Mailing list: https://launchpad.net/~torios-dev Post to : torios-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~torios-dev More help : https://help.launchpad.net/ListHelp
