On 08/21/2016 02:50 PM, Cinque Port Computers wrote:
Hi Guys,
I get the same kernel panic trying the Lubuntu Xenial iso so it must
be my local machine problem trying to run KVM/QEMU.
Cheers,
JackT.
------------------------------------------------------------------------
From: jackdtr...@outlook.com
To: israeld...@gmail.com
Date: Sun, 21 Aug 2016 20:39:25 +0100
CC: torios-dev@lists.launchpad.net
Subject: Re: [Torios-dev] Testing in VB: RE: OBI in xenial
Hi Israel,
Tried Xenial ToriOS in QEMU/KVM but get a kernel panic...
Cheers,
JackT
PS: I'll try Lubuntu in KVM as another comparison test later.
------------------------------------------------------------------------
Subject: Re: [Torios-dev] Testing in VB: RE: OBI in xenial
To: jackdtr...@outlook.com
CC: torios-dev@lists.launchpad.net; nio.wikl...@gmail.com
From: israeld...@gmail.com
Date: Sun, 21 Aug 2016 13:55:23 -0500
Hi Jack,
I will install VirtualBox when I get a chance. I highly recommend
using KVM (virt-manager) if your processor supports it.
It is MUCH better in so many ways, well at least for my usage. I can
easily copy the harddrive, or mount a shared drive between the two.
It made work on the xenial OBI go much better, as I could try
something, and simply copy it over to my VM and try something else.
Previously I would test (in VBox) by manually editing things via nano....
The Lubuntu list has had quite a bit of chatter on the VirtualBox
graphics issues.... so there is something there that doesn't always
work right.
On 08/21/2016 07:42 AM, Cinque Port Computers wrote:
Hi Guys,
I just tried Lubuntu 16.04.1 i386 iso and that comes up fine in
the Live session in VB.
Cheers,
JackT.
------------------------------------------------------------------------
From: jackdtr...@outlook.com <mailto:jackdtr...@outlook.com>
To: nio.wikl...@gmail.com <mailto:nio.wikl...@gmail.com>
Date: Sun, 21 Aug 2016 12:46:53 +0100
CC: torios-dev@lists.launchpad.net
<mailto:torios-dev@lists.launchpad.net>
Subject: Re: [Torios-dev] Testing in VB: RE: OBI in xenial
Hi Nio,
Thanks for the tip; I tried those but the RtCtrl + F1 then F7 just
leaves a black screen with non flashing cursor top left.
I'll browse around and see if Google finds anything useful on VB
and Xenial workings.
Cheers,
JackT.
> Subject: Re: [Torios-dev] Testing in VB: RE: OBI in xenial
> To: jackdtr...@outlook.com <mailto:jackdtr...@outlook.com>;
israeld...@gmail.com <mailto:israeld...@gmail.com>
> CC: torios-dev@lists.launchpad.net
<mailto:torios-dev@lists.launchpad.net>
> From: nio.wikl...@gmail.com <mailto:nio.wikl...@gmail.com>
> Date: Sun, 21 Aug 2016 13:32:53 +0200
>
> Sorry, instead you should use the compose key, probably the 'right
> control' key (instead of ctrl + alt).
>
>
> Den 2016-08-21 kl. 13:25, skrev Nio Wiklund:
> > Hi Jack,
> >
> > Did you try
> >
> > ctrl + alt + F1
> >
> > followed by
> >
> > ctrl + alt + F7
> >
> > Sometimes it gets graphics working for xenial in virtualbox.
> >
> > Best regards
> > Nio
> >
> > Den 2016-08-21 kl. 12:22, skrev Cinque Port Computers:
> >> Hi israel,
> >>
> >> Live session in VB: Worked out username was 'root' and
password 'torios'
> >> and tried to execute 'startx' but that failed 'no screens found'.
> >>
> >> Cheers,
> >> JackT.
> >>
> >>
> >>
------------------------------------------------------------------------
> >> From: jackdtr...@outlook.com <mailto:jackdtr...@outlook.com>
> >> To: israeld...@gmail.com <mailto:israeld...@gmail.com>
> >> Date: Sun, 21 Aug 2016 10:49:28 +0100
> >> CC: torios-dev@lists.launchpad.net
<mailto:torios-dev@lists.launchpad.net>
> >> Subject: [Torios-dev] Testing in VB: RE: OBI in xenial
> >>
> >> Hi Israel,
> >>
> >> Tried booting to Live session in VB several times but just
got to the
> >> tty1 login screen each time; what's the Live username and
password btw?
> >>
> >>
> >>
> >>
> >>
> >> Cheers,
> >> JackT.
> >>
> >>
> >>
> >>
> >>> To: nio.wikl...@gmail.com <mailto:nio.wikl...@gmail.com>;
torios-dev@lists.launchpad.net <mailto:torios-dev@lists.launchpad.net>
> >>> From: israeld...@gmail.com <mailto:israeld...@gmail.com>
> >>> Date: Sat, 20 Aug 2016 17:28:18 -0500
> >>> Subject: Re: [Torios-dev] OBI in xenial
> >>>
> >>> On 08/20/2016 12:33 AM, Nio Wiklund wrote:
> >>> > [bottom posting]
> >>> >
> >>> > Den 2016-08-19 kl. 23:17, skrev Israel:
> >>> >> On 08/19/2016 10:45 AM, Nio Wiklund wrote:
> >>> >>> Thanks for the update, Israel :-)
> >>> >>>
> >>> >>> Best regards
> >>> >>> Nio
> >>> >>>
> >>> >>> Den 2016-08-19 kl. 17:41, skrev Israel:
> >>> >>>> Hey Nio,
> >>> >>>>
> >>> >>>> I spent some time testing ISOmaker with Ubuntu Xenial
just to
> >>> see how
> >>> >>>> well it would work out of the box.
> >>> >>>>
> >>> >>>> And honestly the ISOmaker scripts worked well, and only
require a
> >>> >>>> bit of
> >>> >>>> adjustment, which were all good future-proofing
adjustments anyhow,
> >>> >>>> which will allow easy implementation of future
Ubuntu/Debian
> >> versions.
> >>> >>>>
> >>> >>>>
> >>> >>>> The liveCD booted and worked well.... however OBI had a
few issues.
> >>> >>>>
> >>> >>>> In *functions*
> >>> >>>>
> >>> >>>> if [[ "$ltest0" == "/cow" ]] || [[ "$ltest0" == "aufs"
]] || [[
> >>> >>>> "$ltest0" == "rootfs" ]]
> >>> >>>> then
> >>> >>>>
> >>> >>>> needed to include overlay (or at least I think this
will work)
> >>> >>>>
> >>> >>>> if [[ "$ltest0" == "/cow" ]] || [[ "$ltest0" == "aufs"
]] || [[
> >>> >>>> "$ltest0" == "rootfs" ]] *|| [[ "$ltest0" == "overlay" ]]*
> >>> >>>> then
> >>> >>>>
> >>> >>>> Secondly I modified the select_device()
> >>> >>>> to use a 'common' function
> >>> >>>> list_device_dialog()
> >>> >>>> which can also be used by grub-installer
> >>> >>>>
> >>> >>>> This may introduce a bug... so I will test it, but if
it works
> >>> as it
> >>> >>>> should it will simplify future modifications by using
the same
> >> code to
> >>> >>>> list devices (similar to the list_device) script
> >>> >>>>
> >>> >>>> I will be testing it in a new xenial iso I am working on.
> >>> >>>> reverting the changes will be trivial (since we use bzr
for version
> >>> >>>> control)
> >>> >>>> so if things don't work in xenial or mess up jessie it
will be
> >> easy to
> >>> >>>> revert.
> >>> >>>>
> >>> >>>> I think this test is important as the next Debian
version may
> >> well use
> >>> >>>> the new format for the squashfs.
> >>> >>>> It may be that I need to rework things further and this
will need
> >>> >>>> to be
> >>> >>>> put off but I want to let you know:
> >>> >>>> a) I am still working on things
> >>> >>>>
> >>> >>>> I will attempt to build a xenial and a jessie ISO and
test both of
> >>> >>>> them
> >>> >>>> to see if the change breaks (or fixes) either of them.
> >>> >>>>
> >>> >>>> I am much better versed in Bash these days, so making a
change like
> >>> >>>> this
> >>> >>>> should be trivial, but there is a possibility that I do
not fully
> >>> >>>> understand Nio's code and overlooked something important.
> >>> >>>>
> >>> >>>> The other important change is in *user-config*
> >>> >>>> I changed
> >>> >>>> DISTRO=$(chroot "${CHROOT}" bash -c "uname -v")
> >>> >>>> To:
> >>> >>>> DISTRO=$(chroot "${CHROOT}" bash -c "uname *-a*")
> >>> >>>>
> >>> >>>> and added
> >>> >>>> [[ "${DISTRO/Ubuntu}" != "${DISTRO}" ]] && [[
"${DISTRO/ 4.?.?}" !=
> >>> >>>> "${DISTRO}" ]] && LOGecho "This release of Ubuntu
kernel does not
> >>> >>>> support non PAE $DISTRO" && return
> >>> >>>> in the cpu() function after it checks the 64bit portion, as
> >> xenial has
> >>> >>>> no non-pae kernel so it is already a PAE kernel
> >>> >>>>
> >>> >>>> I am building this in
> >>> >>>>
> >>> >>>> ppa:israeldahl/obi-unstable
> >>> >>>>
> >>> >>>> So there should be no issues with our current progress
in jessie
> >>> >>>>
> >>> >>>> --
> >>> >>>> Regards
> >>> >>>>
> >>> >>>
> >>> >>
> >>> >> Hi Nio,
> >>> >>
> >>> >> I tested it pretty well, and found the major bugs, and
issues.
> >>> >>
> >>> >> i will rebuild in the unstable ppa and make an ISO for
testing (if
> >>> you
> >>> >> like)
> >>> >>
> >>> >> The major issue was the needed harware detector for
Debian (it checks
> >>> >> for missing firmware and installs it in Debian... non free
> >>> proprietary
> >>> >> stuff like wifi dongles etc...)
> >>> >>
> >>> >>
> >>> >> This is a good fix because we may want to base on Ubuntu
again at
> >>> some
> >>> >> point, and both versions will be about the same, as I use
Ubuntu to
> >>> >> build things (and run ToriOS in xenial) so I know the
tools work.
> >>> >>
> >>> >>
> >>> >
> >>> > Yes Israel,
> >>> >
> >>> > It is a good idea to make an ISO for testing in Xenial.
> >>> >
> >>> > Best regards
> >>> > Nio
> >>> Here is the link for this test ISO.
> >>> http://phillw.net/isos/torios/ToriOS-2016-08-19-beta-xenial.iso
> >>>
> >>> Let me know how it goes. I tested it a few times, and the
install (at
> >>> basic level) works.
> >>>
> >>> Network in the Live session did NOT work.
> >>>
> >>> Everything else worked as expected in the installed system
> >>>
> >>> --
> >>> Regards
> >>>
> >>>
> >>> --
> >>> Mailing list: https://launchpad.net/~torios-dev
<https://launchpad.net/%7Etorios-dev>
> >>> Post to : torios-dev@lists.launchpad.net
<mailto:torios-dev@lists.launchpad.net>
> >>> Unsubscribe : https://launchpad.net/~torios-dev
<https://launchpad.net/%7Etorios-dev>
> >>> More help : https://help.launchpad.net/ListHelp
> >>
> >> -- Mailing list: https://launchpad.net/~torios-dev
<https://launchpad.net/%7Etorios-dev> Post to :
> >> torios-dev@lists.launchpad.net
<mailto:torios-dev@lists.launchpad.net> Unsubscribe :
> >> https://launchpad.net/~torios-dev
<https://launchpad.net/%7Etorios-dev> More help :
> >> https://help.launchpad.net/ListHelp
> >
>
-- Mailing list: https://launchpad.net/~torios-dev
<https://launchpad.net/%7Etorios-dev> Post to :
torios-dev@lists.launchpad.net
<mailto:torios-dev@lists.launchpad.net> Unsubscribe :
https://launchpad.net/~torios-dev
<https://launchpad.net/%7Etorios-dev> More help :
https://help.launchpad.net/ListHelp
--
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
Yeah, some processors don't support KVM... there is a way to check, but
I don't know off the top of my head.
The md5sum for the ISO is
b21140806909f648785b1509488724f0
I will be updating the Jessie ISO in the near future, and then we can
test and I will add a zsync and symlinks for the Xenial ISO to prevent
the express need for MD5SUM hashes...
zsync is (of course) much easier for all of us.... but this is the
initial test phase just to see what we get. And for the first iteration
it was really pretty good.
--
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
