9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: hiro <23hiro@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Raspberry Pi 4 stability dependent in RAM
Date: Sun, 22 Nov 2020 11:48:20 +0100	[thread overview]
Message-ID: <CAFSF3XPHiTsK=aOR9GC+yyFH-uOqVbx9DxZ16q+A0zdxXs5=qw@mail.gmail.com> (raw)
In-Reply-To: <CAFSF3XOC+Bc3QDWSqk+07z0PMEeJL=Z9vyYj3X=vrUPLuN3QXA@mail.gmail.com>

i should not have said anything

[11561053.235151] xhci_hcd 0000:01:00.0: @000000001ed0c6e0 00000000
00000000 0e000000 02048000
[11572206.218075] Under-voltage detected! (0x00050005)
[11572207.738154] bcmgenet fd580000.genet eth0: Link is Down
[11572211.898285] bcmgenet fd580000.genet eth0: Link is Up -
1Gbps/Full - flow control off
[11572212.458226] Voltage normalised (0x00000000)
[11585621.202242] xhci_hcd 0000:01:00.0: ERROR Transfer event for
disabled endpoint slot 2 ep 3

gonna move back to my seagate dockstar (kirkwood) for this thing :(
at least then the rpi is free for a stateless 9front terminal again
(easier to reboot when there's problems like the above :()

On 11/14/20, hiro <23hiro@gmail.com> wrote:
> well they have FCC compliance, so i'd hope it's just internal
> interference due to lack of rf separation on the board. unless the fcc
> test is so busted that they were able to activate a less-problematic
> pixel clock and never tried the full possible range? :D
>
> since i don't have a github account i don't think they will listen to
> me about my issues with the device.
>
> but anyway they should hire an RF engineer and not me. if they tried
> the common combinations at all they should have noticed themselves, no
> ?
>
> i have been using 4k@60hz when i experienced my problem, bluetooth
> cannot be switched to 5ghz.
>
> i'm just happy it works at all, i was just gonna return it otherwise
> like i did with the earlier rpi version. don't have time to make
> bug-wishlists for future raspberry christmas trees (took them 8 years
> already to make the first rpi with working ethernet+usb).
>
> On 11/14/20, Bakul Shah <bakul@iitbombay.org> wrote:
>> There were reports of 2560x1440 res generating RF noise in the 2.4GHz
>> band
>> wifi channel 1. The proposed solution (by Eben Upton) was to use channel
>> 4
>> or higher or use 5GHz wifi band at this res. And supposedly there is a
>> firmware fix for this. No idea about the bluetooth issue. You should
>> report
>> these issues either on their forum or one of their github repos.
>>
>>> On Nov 14, 2020, at 7:14 AM, hiro <23hiro@gmail.com> wrote:
>>>
>>> well, for me hdmi reliably stops working when i turn on the bluetooth
>>> keyboard and versa.
>>> clearly RF interference was none of their concern when they made this
>>> chip.
>>> if your monitor suggests a different pixel clock you might get lucky
>>> and it's just good enough, but your signal quality is gonna suffer no
>>> matter what

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Te91377223453b8c0-M3206bd878f444f406e0fb927
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  reply	other threads:[~2020-11-22 10:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-14  0:30 a
2020-11-14  0:56 ` a
2020-11-14  9:35 ` Richard Miller
2020-11-14 11:14   ` Steve Simon
2020-11-14 11:24     ` Richard Miller
2020-11-14 11:24     ` Richard Miller
2020-11-14 14:48       ` hiro
2020-11-14 15:05         ` Richard Miller
2020-11-14 15:12           ` hiro
2020-11-14 16:58             ` Bakul Shah
2020-11-14 18:12               ` hiro
2020-11-22 10:48                 ` hiro [this message]
2020-11-23 22:46                   ` [9fans] node-red Bakul Shah
2020-11-14 15:29           ` [9fans] Raspberry Pi 4 stability dependent in RAM Richard Miller
2020-11-14 16:15             ` hiro
2020-11-18 23:13   ` Anthony Sorace
2020-11-19  0:15     ` Thaddeus Woskowiak
2020-11-19  7:37       ` Steve Simon
2020-11-19  8:27     ` Skip Tavakkolian
2020-11-20 23:05     ` Stuart Morrow

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAFSF3XPHiTsK=aOR9GC+yyFH-uOqVbx9DxZ16q+A0zdxXs5=qw@mail.gmail.com' \
    --to=23hiro@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).