torios-dev team mailing list archive

[Nio Wiklund <nio.wiklund@xxxxxxxxx>]

Hi again Israel,
[inline]
Best regards
Nio

Den 2015-09-27 kl. 19:39, skrev Israel:
> On 09/27/2015 11:18 AM, Nio Wiklund wrote:
>> Den 2015-09-27 kl. 17:14, skrev Israel:
>>> ...
>> Hi again Israel,
>>
>> I will show you the nm-icon in the live system - maybe it is a white dot
>> on a red background now, not a cross (x).
>>
>> The other systems were not found, but the installed system boots :-)
>>
>> The nm-icon is 'OK' in the installed system.
>>
>> After sudo update-grub, the other systems are recognized and there is a
>> grub menu.
>>
>> Best regards
>> Nio
>>
>> ps/ This is a short test (by no means complete). /ds
> Hi Nio,
> If there was a change in nm-applet then this might be the fix we want. 
> See if you can connect to wireless (basically, does it work, even if the
> icon is odd?)

Running live in my Toshiba, wired internet works but shows the icon with
a white dot on read background, maybe because the wireless in not
connecting. It has improved from the white X on red, maybe it is what it
should be. I remember since before, that I need the trusty kernel (by
upgrading to 12.04.5 and its hardware enablement stack) to make the
wireless connecting.

In my IBM Thinkpad with a Pentium M, the live session is connecting with
the precise kernel, and it displays the nm-applet without any white dot
or white X on red background. It looks good :-)

> I am pretty stumped on the grub issue.... maybe we could try installing
> and updating grub, from grub-pc on the ISO, and then copying the
> grub.cfg?  Do you think this would work?  AFAIK it shouldn't pick up the
> liveCD, but it might...  Or, what other options do you think we have?
> I try (in this recent one) installing grub twice, and running
> update-grub 2 times... nothing seems to change it.  the one that failed
> miserably for you I was running
> grub-install --root-directory=/mnt "$device"
> from the liveCD and then updating grub in the chroot
> 
> for i in /dev /dev/pts /proc /sys /run
> do
>  mount -B "$i" "/mnt$i"
> done && echo "mounted device file systems"
> chroot /mnt "update-grub"
> for i in /dev/pts /dev /proc /sys /run
> do
>   umount "/mnt$i"
> done && echo "unmounted device file systems"
> 
> Not sure what to do, what do you suggest?  I know you have indicated you
> believe that the chroot it the culprit, but I am not sure how to run
> update-grub without it (and create the grub file)

I suggest that you add an option to the script firstrun: 'Update the
boot alternatives in the grub menu', which will run

sudo update-grub

An alternative it to force that command to run after reboot. And it
should be mentioned in the instructions/manual/release notes.

> It seems, that the old grub file created earlier in the mkp* script is
> not being overwritten but the update.  Could this be an/the issue?
>  I suppose we could chroot, mount the correct things (like in the script
> grub-installer) and then run grub-mkconfig -o /boot/grub/grub.cfg
> this might work... but maybe it is not picking up the other devices
> because they are not mounted like in the fstab, or whatever.... could it
> be that the fstab needs to be generated differently?  Just some thoughts
> and new directions.  I always appreciate your years of experience and
> wisdom in these areas!  Thanks so much for all the help you have given
> during this very long process :)
>