<gchristensen> eh?
<gchristensen> I am surprised
clever has joined #nixos-aarch64
<gchristensen> d'oh
<samueldr> d'oh?
<gchristensen> had this uncommitted locally:
<gchristensen> -REV=refs/heads/nixos-18.09
<gchristensen> +REV=refs/heads/nixos-19.03
<samueldr> don't you have some service nagging you on uncommitted stuff?
<samueldr> :)
<gchristensen> I do
<gchristensen> but that doesn't mean it is effective
<gchristensen> hrm its compiling a kernel
<gchristensen> why am I compiling a kernel
<samueldr> isn't there a kernel option activated for the networking stuff?
<gchristensen> is there?
<samueldr> maybe not
<gchristensen> lol...
<gchristensen> oops
<gchristensen> kernelPackages = pkgs.linuxPackages_4_14;
<gchristensen> linux_4_17 = pkgs.linux_4_17.override
<gchristensen> okay building-and-deploying 19.03 with 5.1
<gchristensen> ...linking...
orivej has quit [Ping timeout: 248 seconds]
<gchristensen> okay. 19.03.
<gchristensen> apologies :) I thought I had updated already
<samueldr> neat, the raspberry pi 3B just boots an armv7l image (as expected)
ryantrinkle has joined #nixos-aarch64
ryantrinkle has quit [Ping timeout: 248 seconds]
v0|d has joined #nixos-aarch64
<samueldr> so, it takes only one change in nixpkgs that cannot be done through overlays or configuration options to cross-compile sd-image for all three arm flavours supported
<samueldr> and here's what's required https://github.com/samueldr/cross-system
<samueldr> the diff file has the only change required in nixpkgs
<samueldr> everything else self-contained in configuration.nix, and explained (sometimes badly)
<samueldr> with this I learned that xterm is installed even on systems without display managers
v0|d has quit [Ping timeout: 248 seconds]
orivej has joined #nixos-aarch64
v0|d has joined #nixos-aarch64
zupo has joined #nixos-aarch64
orivej has quit [Ping timeout: 245 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
cmacrae`` has joined #nixos-aarch64
cmacrae`` has quit [Quit: ERC (IRC client for Emacs 26.1)]
cmacrae has joined #nixos-aarch64
zupo has joined #nixos-aarch64
cmacrae` has joined #nixos-aarch64
cmacrae has quit [Ping timeout: 248 seconds]
<cmacrae`> Hey peeps o/ I know it's a common problem, but does anyone have a solid solution for getting past the issue of getting stuck on 'Starting kernel ...' on a Raspberry Pi 3 B+? I've managed to build a new image with the help of samueldr & sphalerite, but it never gets past 'Starting kernel ...'
<gchristensen> if I had to guess, your `console` kernel parameter isn't set properly
<gchristensen> where are you seeing "Starting kernel..."
<cmacrae`> Hmm, I'm not doing anything special to the SD image that's being generated, other than increasing the /boot size. So, I can't imagine why the console param would differ from that which is set by the normal build job
<cmacrae`> Seeing 'Starting kernel ...' just when I power on the Pi
cmacrae` is now known as cmacrae
<gchristensen> how do you see it?
<gchristensen> like on a TV?
<cmacrae> Oh sorry, haha
<cmacrae> Yes, on a monitor
<gchristensen> ok
<cmacrae> Is that to perhaps suggest that the kernel is actually starting, but its output just isn't displayed
<gchristensen> yeah, so I'm not super informed but I bet it is the console param.
<gchristensen> the ARM standard is to use /dev/ttyAMA1 (iirc) for the console
orivej has joined #nixos-aarch64
<gchristensen> but rpi uses /dev/ttyS1 or something
<cmacrae> Ah okay, interesting - thanks for the advice! I'll have a search and poke about
<gchristensen> okay yeah so ttyAMA0 is the standard one
<gchristensen> and rpi is probably ttyS0
<gchristensen> (but do look it up.)
<cmacrae> Thanks!
<cmacrae> Yeah, found some references to it in the sd-image.nix expression
<cmacrae> Just going to follow the config I've applied and see if I've somehow clobbered it somewhere
<gchristensen> ok
<gchristensen> you might even be able to edit it from the bootloader
<cmacrae> Good shout
kvaster has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
jackdk_ has joined #nixos-aarch64
<samueldr> the upstream kernel (which we use in aarch64 images) has to use the modesetting driver for raspberry pis to show messages
<samueldr> that driver is not included in the initrd
<samueldr> so the raspberry pi will look stuck at "Starting kernel..." (the last message from u-boot) until stage-2 is started
<samueldr> I guess nothing stops us from adding the vc4 modesetting drivers to the initrd, especially now that boot is going in the main partition
<samueldr> oh, and adding to that, the boot may look stuck for a while if resizing the partition on the sd image takes a while, for whatever reason that might be
cmacrae has quit [Quit: ERC (IRC client for Emacs 26.1)]
orivej has quit [Ping timeout: 272 seconds]
jackdk_ has quit [Ping timeout: 272 seconds]
jtojnar has joined #nixos-aarch64
v0|d has quit [Ping timeout: 268 seconds]
kvaster has quit [Ping timeout: 245 seconds]
orivej has joined #nixos-aarch64
kvaster has joined #nixos-aarch64
kvaster has quit [Ping timeout: 248 seconds]
kvaster has joined #nixos-aarch64
CodeKiwi has joined #nixos-aarch64
kvaster has quit [Ping timeout: 252 seconds]
andi-_ has joined #nixos-aarch64
andi-_ has quit [Client Quit]
zupo has joined #nixos-aarch64
andi-_ has joined #nixos-aarch64
zupo_ has joined #nixos-aarch64
andi-_ has quit [Client Quit]
zupo has quit [Ping timeout: 258 seconds]
andi-_ has joined #nixos-aarch64
andi-_ has quit [Client Quit]
andi-_ has joined #nixos-aarch64
ekleog has quit [Ping timeout: 252 seconds]
ekleog_ has joined #nixos-aarch64
andi- has quit [Quit: WeeChat 2.4]
andi-_ is now known as andi-
andi- has quit [Remote host closed the connection]
andi- has joined #nixos-aarch64
mthst has joined #nixos-aarch64
andi- has quit [Remote host closed the connection]
andi- has joined #nixos-aarch64
zupo_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
CodeKiwi is now known as DigitalKiwi
mthst has quit [Quit: the bouncer died]
mthst has joined #nixos-aarch64
mthst has quit [Client Quit]
mthst has joined #nixos-aarch64