00:08
wavirc22 has quit [Read error: Connection reset by peer]
00:08
wavirc22 has joined #nixos-aarch64
01:25
<
samueldr >
I figure it must be gater behind the domain name at the browser level
01:26
<
samueldr >
though the article makes it look like it might be simply "WebUSB"
02:04
<
clever >
samueldr: ive heard that webusb is somewhat like libusb, but the browser needs access to the nodes in /dev/bus/usb/
02:04
<
clever >
so you need the right udev rules to allow non-root access
02:07
<
samueldr >
though imagine being able to install mobile nixos from a chromium browser!
02:20
<
samueldr >
the spec is open, it could be implemented by other browsers
02:38
<
colemickens >
hm copies back to me from the community box are very slow, not sure if its expected?
02:39
h0m1 has quit [Ping timeout: 272 seconds]
02:40
h0m1 has joined #nixos-aarch64
02:59
Adluc has quit [Ping timeout: 272 seconds]
03:00
ehmry has quit [Ping timeout: 246 seconds]
03:04
ehmry has joined #nixos-aarch64
03:45
Adluc has joined #nixos-aarch64
04:54
orivej has quit [Ping timeout: 240 seconds]
05:52
Acou_Bass has quit [Ping timeout: 256 seconds]
05:59
Acou_Bass has joined #nixos-aarch64
06:00
leonardp has joined #nixos-aarch64
07:15
logand` has joined #nixos-aarch64
07:22
Acou_Bass has joined #nixos-aarch64
07:59
FRidh has joined #nixos-aarch64
09:15
LnL has quit [Ping timeout: 256 seconds]
09:21
orivej has joined #nixos-aarch64
09:31
pbb has quit [Ping timeout: 246 seconds]
09:55
kai_w has quit [Quit: Konversation terminated!]
09:55
pbb has joined #nixos-aarch64
09:59
orivej_ has joined #nixos-aarch64
09:59
orivej has quit [Ping timeout: 250 seconds]
10:04
LnL has joined #nixos-aarch64
10:04
LnL has quit [Changing host]
10:04
LnL has joined #nixos-aarch64
10:12
kai_w has joined #nixos-aarch64
10:18
zupo has joined #nixos-aarch64
10:18
zupo has quit [Client Quit]
10:18
zupo has joined #nixos-aarch64
11:10
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
12:22
wavirc22 has joined #nixos-aarch64
12:27
FRidh has quit [Ping timeout: 256 seconds]
12:27
FRidh2 has joined #nixos-aarch64
12:59
zupo has joined #nixos-aarch64
13:13
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
13:14
zupo has joined #nixos-aarch64
13:30
tilpner_ has joined #nixos-aarch64
13:31
tilpner has quit [Ping timeout: 240 seconds]
13:31
tilpner_ is now known as tilpner
13:32
FRidh2 has quit [Quit: Konversation terminated!]
13:32
FRidh2 has joined #nixos-aarch64
13:32
FRidh2 has quit [Client Quit]
13:33
FRidh has joined #nixos-aarch64
13:43
FRidh2 has joined #nixos-aarch64
13:43
FRidh has quit [Ping timeout: 240 seconds]
14:00
FRidh has joined #nixos-aarch64
14:01
FRidh2 has quit [Ping timeout: 250 seconds]
14:08
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
14:13
zupo has joined #nixos-aarch64
14:22
leonardp has quit [Ping timeout: 240 seconds]
14:39
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
15:00
zupo has joined #nixos-aarch64
15:30
wavirc22 has joined #nixos-aarch64
15:42
leonardp has joined #nixos-aarch64
16:40
zupo has quit [Ping timeout: 258 seconds]
16:41
zupo has joined #nixos-aarch64
16:44
wavirc22 has joined #nixos-aarch64
17:50
v0|d has quit [Ping timeout: 250 seconds]
17:57
v0|d has joined #nixos-aarch64
17:59
wavirc22 has joined #nixos-aarch64
18:19
lovesegfault has joined #nixos-aarch64
18:24
wavirc22 has joined #nixos-aarch64
18:32
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
18:34
wavirc22 has joined #nixos-aarch64
18:37
tilpner_ has joined #nixos-aarch64
18:39
tilpner has quit [Ping timeout: 256 seconds]
18:39
tilpner_ is now known as tilpner
18:58
h0m1 has quit [Quit: WeeChat 2.7.1]
18:59
h0m1 has joined #nixos-aarch64
19:04
{`-`} has joined #nixos-aarch64
19:07
zupo has joined #nixos-aarch64
19:17
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
19:21
<
{^_^} >
#66960 (by samueldr, 31 weeks ago, open): Tracking issue for Raspberry Pi 3B+ and the latest kernel
19:22
<
Valodim >
I see "Starting kernel..", and then it doesn't change anymore. It
*does* boot though, and I can log in via SSH
19:22
<
samueldr >
starting from a 20.03 burned image?
19:22
<
samueldr >
or starting from 19.03?
19:23
<
Valodim >
it was a 19.09 image (which worked as expected), updated to 20.03
19:23
<
Valodim >
default kernel, not latest
19:25
<
Valodim >
you mention in that issue that this shouldn't happen since 19.09 kernels. perhaps it's a different cause than the one in that issue
19:25
<
Valodim >
does look similar tho
19:25
<
Valodim >
anything I can do to debug? :) I do have ssh on the machine
19:26
puzzlewolf has joined #nixos-aarch64
19:26
<
samueldr >
the exact tracked issue was u-boot from a 19.03 image being too old, it didn't know about the raspberry Pi 3B+, so it wouldn't load the right device tree
19:26
<
samueldr >
you don't have serial logs for u-boot logs, right?
19:27
<
Valodim >
nope. is there a simple way to obtain those?
19:27
<
samueldr >
without serial I don't know
19:27
<
samueldr >
though I may have clues in `dmesg | head -n 50
19:27
<
Valodim >
gimme a sec
19:29
<
samueldr >
>> [ 0.000000] Machine model: Raspberry Pi 3 Model B
19:29
<
samueldr >
you have a 3B+, right?
19:30
<
Valodim >
huh. I might have been mistaken there, let me confirm
19:30
<
clever >
Valodim: the revision in /proc/cpuinfo gives you the exact details
19:30
<
samueldr >
clever: though what I wanted is the "maybe erroneous" name from the device tree :)
19:31
<
samueldr >
that's what I assume the issue is for #66960
19:31
<
Valodim >
clever: says CPU revision: 4
19:31
<
Valodim >
board doesn't have a +, seems I was wrong there
19:31
<
clever >
oh and u-boot may not forward the 32bit revision onward to linux
19:32
<
clever >
4 is definitely not the revision we want
19:33
<
clever >
Valodim: it would be a number like 0x00c03112
19:33
<
samueldr >
right, in that case it would be another issue, if it's not a 3B+
19:33
<
samueldr >
I don't know if 5.4 or 5.5 should be expected to work with HDMI
19:34
<
samueldr >
we might be missing a changed kernel configuration option
19:34
<
Valodim >
board says it's a 3B v1.2
19:35
<
clever >
Valodim: my 3b (non plus) says the same thing
19:36
<
samueldr >
yep, so it's well-identified
19:36
<
samueldr >
I can assure you that it's not #66960, but I'm not saying there's not another bug
19:37
<
Valodim >
helpful, in its own way
19:37
<
Valodim >
it did work as expected with the 19.09 installation image. I'll try downgrading to 19.09 with its default kernel, to see if that still works
19:37
<
samueldr >
or you could try setting 4.19 specifically on 20.03
19:38
<
samueldr >
or if you have another SD card around, download a fresh 20.03 image to see
19:39
<
Valodim >
setting 4.19 explicitly sounds good, I'll try that
19:39
<
srk >
I know 5.5 works but not sure if hdmi works as well, will try
19:41
<
samueldr >
it
*could* be a similar issue where the specific installed u-boot does something that the mainline kernel doesn't like
19:42
<
Valodim >
I do have another sd card too, will try a fresh 20.03 image as well
19:42
<
samueldr >
that would at least remove variables, and get us a good starting point to test
19:43
<
Valodim >
I'll report back when I tried a few things
19:43
<
Valodim >
thanks for your support so far!
19:45
<
Valodim >
the 4.19 isn't in the cache.. guess that'll take a while :)
19:45
<
Valodim >
by 4.19 you were referring to linuxPackages_4_19?
19:52
zupo has joined #nixos-aarch64
20:04
wavirc22 has joined #nixos-aarch64
20:21
FRidh has quit [Quit: Konversation terminated!]
21:02
bennofs has quit [Ping timeout: 246 seconds]
22:29
bennofs has joined #nixos-aarch64
22:38
lovesegfault has quit [Quit: WeeChat 2.7.1]
22:41
lovesegfault has joined #nixos-aarch64
23:13
Acou_Bass has quit [Ping timeout: 265 seconds]
23:25
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
23:30
h0m1 has quit [Ping timeout: 246 seconds]
23:32
h0m1 has joined #nixos-aarch64
23:46
lopsided98 has quit [Remote host closed the connection]
23:46
Acou_Bass has joined #nixos-aarch64
23:47
lopsided98 has joined #nixos-aarch64