missing boot menu entry since R3.0 + network detection only after router reboot

[skat...@gmail.com]

On my HDD I'm running two OS: Qubes and Win7(outside Qubes)

When updating to R3.0 or R3.1rc1 (by clean install) the boot menu entry for Windows is missing.
Executing the update command for grub2 after installation didn't help.
However, if I reinstall R2.0 the Windows entry in the boot menu shows up again.

Having installed R3.0 or R3.1rc1 I can still boot Windows from the command line of the grub console by typing the single commands and I also can edit the grub.cfg to add the missing entry/commands manually but why doesn't this work automatically anymore (as it used to be with R1.0 as well as with R2.0)?

Another issue is, that my router (AVM Fritzbox 7112) does not detect my computer when I boot R3.0 or R3.1rc1 unless I restart my router after R3.0 is up and running.
Having to reboot my router each time I start Qubes prevents me from using these newer releases and was not necessary with R2.0 and R1.0!?

Thx. for help!

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Tue, Dec 29, 2015 at 02:53:50AM -0800, skat...@gmail.com wrote:
> On my HDD I'm running two OS: Qubes and Win7(outside Qubes)
>
> When updating to R3.0 or R3.1rc1 (by clean install) the boot menu entry for Windows is missing.
> Executing the update command for grub2 after installation didn't help.
> However, if I reinstall R2.0 the Windows entry in the boot menu shows up again.
>
> Having installed R3.0 or R3.1rc1 I can still boot Windows from the command line of the grub console by typing the single commands and I also can edit the grub.cfg to add the missing entry/commands manually but why doesn't this work automatically anymore (as it used to be with R1.0 as well as with R2.0)?

Detecting other OSes is specifically disabled for security reasons[1].
So you need to add such entry manually (in /etc/grub.d/40_custom). We
need to document this[2]...

> Another issue is, that my router (AVM Fritzbox 7112) does not detect my computer when I boot R3.0 or R3.1rc1 unless I restart my router after R3.0 is up and running.
> Having to reboot my router each time I start Qubes prevents me from using these newer releases and was not necessary with R2.0 and R1.0!?

That's strange. Are you talking about wire network, or wireless? Do you
get any error message?

[1]
https://github.com/QubesOS/qubes-secpack/blob/master/QSBs/qsb-020-2015.txt
[2] https://github.com/QubesOS/qubes-issues/issues/1564

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJWgp6EAAoJENuP0xzK19csdWoH/01ptEIHSrYrXdMKqf3Yvcvt
Snz6cJ5IcrFZl4pm82fdLh6sDx0D4gifmtXGiwogWQcSBr7VgvfCq6K6WeIK7/8M
1aynlYRqr5h4NMSKXq6Oy9a38PqnSwIGVmOTFBFoFQAjg3i11a3BB5M2dlqpw3HR
slw2h62tF+Hk1qvPdlO9dP30JDY/TBrt9KhvYzV3Iz5mayEa/R0ZZW0Wh6pMRy9g
eNqJx52OaPRNAgQD5fw6Cg4K3Ztw61Mr9m/vE77El+XVmJ2RYJ4s5CiOSz7V+0ge
syX4BN/KoUYjRblSbs6N6QoQlhZJqhqLoRiCr5y8NkCee/xe4caDUgqSx2waQA8=
=qT7U
-----END PGP SIGNATURE-----

[Tom]

Am Dienstag, 29. Dezember 2015 15:54:22 UTC+1 schrieb Marek Marczykowski-Górecki:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>

Hi Marek,

Thx. for the quick response!

1) Dual boot: I understand from Joanna's Bulletin #20 that I can reduce the security risk of dual boot systems by not running any user AppVMs while updating the Qubes-system (Dom0 & TemplatesVM). Is this correct?

2) Network issue: my router and desktop computer are connected by LAN and I don't get any error messages (besides having no internet access). When I check with my router (from another WLAN-device) it does not show an active connection to my dektop computer - just as it was still powered off. However, when I reboot my router it does detect my desktop computer and Qubes is also showing a message that a network connection is now available.

Maybe my router is part of this issue but on the other hand I had no problems running R1.0 and R2.0 with it!?

Thx. again for your advice!

BR, Tom

Am Dienstag, 29. Dezember 2015 15:54:22 UTC+1 schrieb Marek Marczykowski-Górecki:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Wed, Dec 30, 2015 at 01:15:00AM -0800, Tom wrote:
> Am Dienstag, 29. Dezember 2015 15:54:22 UTC+1 schrieb Marek Marczykowski-Górecki:
> > On Tue, Dec 29, 2015 at 02:53:50AM -0800, Tom wrote:
> > > On my HDD I'm running two OS: Qubes and Win7(outside Qubes)
> > >
> > > When updating to R3.0 or R3.1rc1 (by clean install) the boot menu entry for Windows is missing.
> > > Executing the update command for grub2 after installation didn't help.
> > > However, if I reinstall R2.0 the Windows entry in the boot menu shows up again.
> > >
> > > Having installed R3.0 or R3.1rc1 I can still boot Windows from the command line of the grub console by typing the single commands and I also can edit the grub.cfg to add the missing entry/commands manually but why doesn't this work automatically anymore (as it used to be with R1.0 as well as with R2.0)?
> >
> > Detecting other OSes is specifically disabled for security reasons[1].
> > So you need to add such entry manually (in /etc/grub.d/40_custom). We
> > need to document this[2]...

> > [1]
> > https://github.com/QubesOS/qubes-secpack/blob/master/QSBs/qsb-020-2015.txt
> > [2] https://github.com/QubesOS/qubes-issues/issues/1564
>

> 1) Dual boot: I understand from Joanna's Bulletin #20 that I can reduce the security risk of dual boot systems by not running any user AppVMs while updating the Qubes-system (Dom0 & TemplatesVM). Is this correct?

Having that issues fixed (packages referenced in that bulletin) it
doesn't matter now. What does matter is having another disks/partiotions
attached to dom0. We have specifically disabled os-prober (an
application to detect other OSes on the same disk) to not touch (and
parse) those additional disks/partitions.

As for the windows boot entry, you can add it manually in
/etc/grubd.2/40_custom, for example:

menuentry "Windows 7 (loader) (on /dev/sda1)" --class windows --class os
{
insmod part_msdos
insmod ntfs
set root='(hd0,msdos1)'
chainloader +1
}

Then regenerate grub configuration with:

sudo grub2-mkconfig -o /boot/grub2/grub.cfg

> > > Another issue is, that my router (AVM Fritzbox 7112) does not detect my computer when I boot R3.0 or R3.1rc1 unless I restart my router after R3.0 is up and running.
> > > Having to reboot my router each time I start Qubes prevents me from using these newer releases and was not necessary with R2.0 and R1.0!?
> >
> > That's strange. Are you talking about wire network, or wireless? Do you
> > get any error message?
> >
>

> 2) Network issue: my router and desktop computer are connected by LAN and I don't get any error messages (besides having no internet access). When I check with my router (from another WLAN-device) it does not show an active connection to my dektop computer - just as it was still powered off. However, when I reboot my router it does detect my desktop computer and Qubes is also showing a message that a network connection is now available.
>
> Maybe my router is part of this issue but on the other hand I had no problems running R1.0 and R2.0 with it!?

I have no idea, sorry. Check logs in sys-net, maybe there you'll find
some hints.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJWg7tSAAoJENuP0xzK19cs8kIH/1hy/oH8WoOhObD3zSg71Ar4
S2J1nbo74ygZnViJlzvrmgyRmj+9X0pmbbYXZkPjIC7ufbm7+x5JLOfHoLzGIvw0
dSoLEq3X688PqU9P8CbCXb1lme3Iytd6kqIhon7aKFqXMEYfqAO8lMna9vfeAtNM
rz8duu6uMJrv7gkucXHCPHXbTA8Qslwd4yD4Mdye2f9kBtmW+eEXOex3m70h6tXL
XrzD5ppS/c6S7lNdnZt3pRFyFUhAKiZvAZwfgfPqj9VMZFeaHE1DUKQnhCu32a83
V9vUq6lRE8OyYZtOPQlN/IXmjAT5Ir+U7wp0KqZafOu8uxaEWIJSJ5evGhojXGk=
=+Ez5
-----END PGP SIGNATURE-----