Thanks again for the help.
On Fri, Mar 1, 2013 at 8:10 AM, Shea Levy wrote:
> You can build with from a git checkout of nixpkgs (or nixos) by adding the
> flags -I nixpkgs=/path/to/nixpkgs (or -I nixos=/path/to/nixos) on the
> nixos-rebuild command line.
>
> On Feb 28, 2013, at 20:23, Patrick W
You can build with from a git checkout of nixpkgs (or nixos) by adding the
flags -I nixpkgs=/path/to/nixpkgs (or -I nixos=/path/to/nixos) on the
nixos-rebuild command line.
On Feb 28, 2013, at 20:23, Patrick Wheeler
wrote:
> Rather then mounting the store and mutating it, what is a better met
Rather then mounting the store and mutating it, what is a better method of
testing out this type of solution?
On Thu, Feb 28, 2013 at 7:20 PM, Patrick Wheeler <
patrick.john.whee...@gmail.com> wrote:
>
> I mangled my store and updated xf86videovmware,
> https://github.com/NixOS/nixpkgs/pull/33
I mangled my store and updated xf86videovmware,
https://github.com/NixOS/nixpkgs/pull/338, and it fixed the problem. I now
have graphics again.
Thanks for the help,
Patrick
On Thu, Feb 28, 2013 at 3:14 PM, Patrick Wheeler <
patrick.john.whee...@gmail.com> wrote:
> No problem, thanks for takin
No problem, thanks for taking a look at it. I think my last journalctl was
logged when display-manager.services failed. I restarted the system and
here are the two logs.
systemctl:
http://pastebin.com/QxFwZcxm
journalctl -bu display-manager.service:
http://pastebin.com/1GdpBznw
My native effor
Sorry we're having such a hard time figuring out this issue... I
suspect it's an X driver problem and the nix-1.2 change is unrelated.
Just to double check, you said when you ran systemctl it showed that
display-manager.service had failed? If it's not too much of a hassle can
you paste the outp
I just wanted to update with that the graphical live cd for the latest
nixos when installed through VMware also does not boot into the graphical
interface and hast the same behavior as my installation.
On Tue, Feb 26, 2013 at 11:09 AM, Patrick Wheeler <
patrick.john.whee...@gmail.com> wrote:
> Y
On 02/26/2013 12:21 AM, Patrick Wheeler wrote:
Sorry for the small repeat here.
Are you talking about the github branch?
https://github.com/NixOS/nixpkgs/tree/stdenv-updates
or use the following channel?
The channel should follow the branch. IMO it's easiest to have binary
cache enabled, t
Yes that is when it is not booting in graphical mode and anything that
depends on X server will report not finding a screen.
It also reports success to me as it is booting up so it does
not surprise me that it is logged that way. As it is booting up it give a
green completed checkmark for X11 and
Hi Patrick,
No, there's no need to switch. When you ran the journalctl command, was that
during a boot where the X server failed? The log you shared looked like
everything was working.
~Shea
On Feb 26, 2013, at 1:01, Patrick Wheeler
wrote:
> I garbage collected all of the paths that verify
I garbage collected all of the paths that verify had problems, while
staying on the same channel. Grub with nixos-rebuild seems to be in working
order but the display-manager is still not up and running however.
Is there still any advantage to trying stdenv-updates still? Any
other suggestions?
P
* or use the following channel?
http://hydra.nixos.org/job/nixos/stdenv-updates/channel/channel/latest
Apology fore the repeated posts my web browser was acting up on me a little.
On Mon, Feb 25, 2013 at 5:21 PM, Patrick Wheeler <
patrick.john.whee...@gmail.com> wrote:
> Sorry for the small rep
Sorry for the small repeat here.
Are you talking about the github branch?
https://github.com/NixOS/nixpkgs/tree/stdenv-updates
or use the following channel?
On Mon, Feb 25, 2013 at 3:16 PM, wrote:
> Generally any broken paths is a bad sign, the fact that there are quite a
> few is more trou
@Vladimir
That is the system I was on before the updates.
nixos-version reports:
0.2pre4505_e40... now
@shea
I am not well educated on the available standard channels are you talking
about this:
http://hydra.nixos.org/job/nixos/stdenv-updates/channel/channel/latest
?
On Mon, Feb 25, 2013 at
On 02/25/2013 09:52 PM, Patrick Wheeler wrote:
`nix-stor --verify --check-contents`
http://pastebin.com/EezSb9NU
/nix/store/ivnjbpksshmh10d6c3gsk2aa32lwxpk8-nixos-0.1pre4014_78bd54c-f0997b9
This might be the system you're running, is it?
The others shouldn't affect booting at all.
Vlada
sm
Generally any broken paths is a bad sign, the fact that there are quite
a few is more troubling... Did you have a disk failure at any point? If
you don't mind the time involved in doing the build, I'd consider
switching to stdenv-updates, rebuilding, and garbage collecting your old
profiles (on
`nix-stor --verify --check-contents`
http://pastebin.com/EezSb9NU
Thanks for taking a look at it.
Patrick
On Mon, Feb 25, 2013 at 2:43 PM, Patrick Wheeler <
patrick.john.whee...@gmail.com> wrote:
> configuration.nix:
> http://pastebin.com/Mfam4J07
>
> journalctl -bu ...
> http://pastebin.com/v
configuration.nix:
http://pastebin.com/Mfam4J07
journalctl -bu ...
http://pastebin.com/vrLchuDT
I had been using it nix-store --verify --check-contents night but must
have gotten impatient and canceled half way so the file I was using as a
log only had a few entries. I will can tell you though t
Hi Patrick,
To help debug, can you:
a) paste configuration.nix
b) paste the output of 'journalctl -bu display-manager.service'
c) run, as root, 'nix-store --verify --check-contents' (will take some
time!) and report the output?
Thanks,
Shea
On 2013-02-25 14:43, Patrick Wheeler wrote:
> On vmwa
On vmware 4.1.3
Starting with nixos and nix 1.1
My problem is that after trying to update from nix 1.1 to nix 1.2 or 1.3 I
was not longer able to get xserver/X11 to work. If you have any insight to
a solution please let me know below is a very rough time line, additional
information and some fail
20 matches
Mail list logo
