HCL dell xps 13 Q2B2

[j]

i5-2467M CPU @ 1.60GHz; intel HD; sandy bridge; BIOS A03

Q2R2 fresh install worked, 2nd time, only had blinking white cursor on top left of screen after first install.  2nd try may have worked because I left DVD plugged in for first boot.

qvm-backup/restore generally worked, lost yum.repo.d config in old template, would be nice to be able to bring old templates along.

also could use advise about how to auto start daemons in way that doesn't go away after restart of domU.

First boot after qvm-backup-restore kde reverted back to old look and feel and I can no longer access the system settings.

cpu continues to run hot ~127 deg. F at idle

upgrade from Q2R1 (which wasn't working 100% after upgrade from Q1) to Q2R2 failed - with complaints about unable to find/connect to mirrors during the upgrade portion of dom0

Because usb stick install failed for Q1 I stuck with a dvd install plugged into the right or USB2/3 port.

[Marek Marczykowski]

On 01.03.2013 20:38, j wrote:
> i5-2467M CPU @ 1.60GHz; intel HD; sandy bridge; BIOS A03
>
> Q2R2 fresh install worked, 2nd time, only had blinking white cursor on top
> left of screen after first install. 2nd try may have worked because I left
> DVD plugged in for first boot.
>
> qvm-backup/restore generally worked, lost yum.repo.d config in old
> template, would be nice to be able to bring old templates along.

Currently backup utility doesn't allow to backup default template, only user
created one (qvm-clone).
For that purpose I keep list of manually installed packages in template in
separate file and after template reinstall I manually add additional
repositories (rpmfusion) and call:
yum install `cat my-packages.txt`
then apply manual (all two) changes to files in /etc.

Anyway backup of "system" template can be useful feature.

> also could use advise about how to auto start daemons in way that doesn't
> go away after restart of domU.

/rw/config/rc.local

> First boot after qvm-backup-restore kde reverted back to old look and feel
> and I can no longer access the system settings.
>
> cpu continues to run hot ~127 deg. F at idle

I have the same issue, downgrade to 3.7.4 kernel fixes it. I'm trying to find
out what is wrong.

> upgrade from Q2R1 (which wasn't working 100% after upgrade from Q1) to Q2R2
> failed - with complaints about unable to find/connect to mirrors during the
> upgrade portion of dom0

This is why reinstall is recommended way...

> Because usb stick install failed for Q1 I stuck with a dvd install plugged
> into the right or USB2/3 port.

I hope that with R2B2 installing from USB should work much better, especially
USB3.0 should work. Can you just check if installer is booting from USB3 port?
I've successfully installed system on USB3.0 disk, but my system isn't capable
of _booting_ from USB3.0 port, so cannot check this fully...

--
Best Regards / Pozdrawiam,
Marek Marczykowski
Invisible Things Lab

[j]

On Friday, March 1, 2013 11:38:38 AM UTC-8, j wrote:

i5-2467M CPU @ 1.60GHz; intel HD; sandy bridge; BIOS A03

Q2R2 fresh install worked, 2nd time, only had blinking white cursor on top left of screen after first install.  2nd try may have worked because I left DVD plugged in for first boot.

qvm-backup/restore generally worked, lost yum.repo.d config in old template, would be nice to be able to bring old templates along.

also could use advise about how to auto start daemons in way that doesn't go away after restart of domU.

First boot after qvm-backup-restore kde reverted back to old look and feel and I can no longer access the system settings.

sudo systemsettings from dom0 still works 

[Marek Marczykowski]

On 01.03.2013 21:41, j wrote:
> On Friday, March 1, 2013 11:38:38 AM UTC-8, j wrote:
>> First boot after qvm-backup-restore kde reverted back to old look and feel
>> and I can no longer access the system settings.
>>
> sudo systemsettings from dom0 still works

Really sudo is required here?

If you don't have any important KDE settings you can remove ".kde" directory
and restart system (or logout and login again) to use defaults.

[j]

On Friday, March 1, 2013 11:59:20 AM UTC-8, Marek Marczykowski wrote:

On 01.03.2013 20:38, j wrote:
> i5-2467M CPU @ 1.60GHz; intel HD; sandy bridge; BIOS A03
>
> Q2R2 fresh install worked, 2nd time, only had blinking white cursor on top
> left of screen after first install.  2nd try may have worked because I left
> DVD plugged in for first boot.
>
> qvm-backup/restore generally worked, lost yum.repo.d config in old
> template, would be nice to be able to bring old templates along.

Currently backup utility doesn't allow to backup default template, only user
created one (qvm-clone).
For that purpose I keep list of manually installed packages in template in
separate file and after template reinstall I manually add additional
repositories (rpmfusion) and call:
yum install `cat my-packages.txt`
then apply manual (all two) changes to files in /etc.

Anyway backup of "system" template can be useful feature.

> also could use advise about how to auto start daemons in way that doesn't
> go away after restart of domU.

/rw/config/rc.local

> First boot after qvm-backup-restore kde reverted back to old look and feel
> and I can no longer access the system settings.
>
> cpu continues to run hot ~127 deg. F at idle

I have the same issue, downgrade to 3.7.4 kernel fixes it. I'm trying to find
out what is wrong. 

I found your kernel tree in trak, and the non-default-git-branches in http://qubes-os.org/trac/wiki/QubesBuilder,

do I just set BRANCH_kernel=devel-3.7.4-1 or some such and type make?

[j]

On Friday, March 1, 2013 12:48:56 PM UTC-8, Marek Marczykowski wrote:

On 01.03.2013 21:41, j wrote:
> On Friday, March 1, 2013 11:38:38 AM UTC-8, j wrote:
>> First boot after qvm-backup-restore kde reverted back to old look and feel
>> and I can no longer access the system settings.
>>
> sudo systemsettings from dom0 still works

Really sudo is required here?

If you don't have any important KDE settings you can remove ".kde" directory
and restart system (or logout and login again) to use defaults.

[fixing egregious top post] 

Yes, deleting .kde was the right choice, it also fixed the trouble I was having with setting shortcut keys.

[Marek Marczykowski]

On 01.03.2013 23:10, j wrote:
>
>
> On Friday, March 1, 2013 11:59:20 AM UTC-8, Marek Marczykowski wrote:
>>
>> On 01.03.2013 20:38, j wrote:
>>> cpu continues to run hot ~127 deg. F at idle
>>
>> I have the same issue, downgrade to 3.7.4 kernel fixes it. I'm trying to
>> find
>> out what is wrong.
>>
>
> I found your kernel tree in trak, and the non-default-git-branches in
> http://qubes-os.org/trac/wiki/QubesBuilder,
>
> do I just set BRANCH_kernel=devel-3.7.4-1 or some such and type make?

Actually in master branch reset to commit "version 3.7.4" and then compile.
Anyway I'm currently debugging this issue (this is third system with the same
problem) and hopefully will release fixed package soon.

[j]

I also noticed with the xps 13 that I no longer have any control over the screen brightness with R2B2, just at 100% all the time, kde tries to dim and says that it is dimming but the brightness doesn't go down.

With R1 and R2B1 I was able to set the powersave mode to use a less bright screen.  More specifically there were a few levels on the continuum that would work... there were some other levels on the continuum where the screen would flash (rapidly changing brightness).

[Alex Dubois]

Same on MacBook Pro (which is now almost usable, I will report in another thread) but only XFCE, KDE is fine.

Alex

--
You received this message because you are subscribed to the Google Groups "qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.