ChanServ changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Chrome OS Trogdor Devices - Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630 - Lenovo ThinkPad X13s - and various other snapdragon laptops) - https://oftc.irclog.whitequark.org/aarch64-laptops
Elon_Musk has quit []
<Jasper[m]>
@amstan @steev spammer^
<steev>
i'm only on irc, and can't delete messages from irc
<HdkR>
But why would you want to delete such a good deal? </s>
<amstan>
done!
<amstan>
we don't need no starlink here, we have the power of arm!
<abby>
that's irc-side spam
enyalios_ has joined #aarch64-laptops
enyalios has quit [Ping timeout: 480 seconds]
tobhe_ has joined #aarch64-laptops
tobhe has quit [Ping timeout: 480 seconds]
chenxuecong[m] has joined #aarch64-laptops
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
alfredo has quit [Remote host closed the connection]
sally has quit [Quit: sally]
sally has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
icecream95 has joined #aarch64-laptops
funderscore is now known as f_
<icecream95>
Do I get a prize for getting to 222 days uptime on my chromeblet, without suspending at all?
<icecream95>
("Yes, a new kernel release to install")
<SpieringsAE>
does anyone here have the lenovo yoga c630
<SpieringsAE>
?
<SpieringsAE>
if so, do you have "ti_sn65dsi86 2-002d: Failed to create device link (0x180) with pwm-backlight" in dmesg?
alfredo has joined #aarch64-laptops
<SpieringsAE>
ignore the i2c bus and address, those both dont match my sevicw
<SpieringsAE>
device
<travmurav[m]>
SpieringsAE: fwiw I get that on my aspire1
<travmurav[m]>
I think it's about having some modules in kernel/initramfs and other in rootfs
<SpieringsAE>
I don't have an initramfs on this system lol
<SpieringsAE>
but a lot of stuff is built-in, very purpose built kernel
<SpieringsAE>
only 4gb of eMMC :(
<SpieringsAE>
drm is also initializing super slow
<SpieringsAE>
like 13 seconds after systemd starts up
<SpieringsAE>
which happens at 4 seconds
<SpieringsAE>
gpu is initialized at 1.7 seconds
<SpieringsAE>
but the display not until 17+ seconds
<travmurav[m]>
SpieringsAE: hm I'm now also not sure if I have both things =y (or in initramfs)
<SpieringsAE>
the edp-panel driver detects the panel at 4 seconds
<travmurav[m]>
but I thiiiink this never broke anything for me
<SpieringsAE>
I mean the backlight does come on and the display works fine
<SpieringsAE>
but I feel like that error shouldn't be there
<travmurav[m]>
right
<travmurav[m]>
well I've never bothered figuring out what's wrong exactly xD
srinik has quit [Remote host closed the connection]
srinik has joined #aarch64-laptops
srinik has quit [Ping timeout: 480 seconds]
srinik has joined #aarch64-laptops
alfredo has quit [Remote host closed the connection]
enyalios has joined #aarch64-laptops
enyalios_ has quit [Ping timeout: 480 seconds]
<SpieringsAE>
wooooo I finally got this POC broadcom/cypress wifi/bt chipset working
<SpieringsAE>
the sdio bus is my mortal enemy
srinik has quit [Ping timeout: 480 seconds]
srinik has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
jhovold has joined #aarch64-laptops
SpieringsAE has quit [Remote host closed the connection]
alfredo1 has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
alfredo1 has quit [Ping timeout: 480 seconds]
srinik has quit [Ping timeout: 480 seconds]
srinik has joined #aarch64-laptops
iivanov has quit [Quit: Leaving...]
Melody91 has quit [Ping timeout: 480 seconds]
monkeybusiness has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
enyalios has quit [Remote host closed the connection]
enyalios has joined #aarch64-laptops
<smoorgborg[m]>
FYI: Running Ubuntu Concept on T14s with 6.12.0-22-qcom-x1e, I get instant blue screen of death (no text), and reboot after some seconds when I'm copying from a USB3 key I have.
enyalios has quit [Remote host closed the connection]
<tobhe_>
yeah, add `cutmem 0x8800000000 0x8fffffffff` to your /boot/grub/grub.cfg
<tobhe_>
downside: turns your 64 GB RAM into 32 GB
<smoorgborg[m]>
but that solves it?? totally strange
<tobhe_>
we suspect a firmware bug
<smoorgborg[m]>
my machine has been rock solid otherwise without it
<tobhe_>
it only happens on "heavy" peripheral access
<smoorgborg[m]>
I've written various stuff to USB keys using rpi-imager without issues, so it's strange. Don't know if it's specific to that one key or not. But I guess it's a generic problem if you have a known workaround for it
<smoorgborg[m]>
Where do I put the cutmem in the Ubuntu grub builder config files for it to work?
enyalios has joined #aarch64-laptops
jkm has joined #aarch64-laptops
<tobhe_>
try GRUB_BADRAM=0x8800000000,0xf800000000 in /etc/default/grub
<tobhe_>
and update-grub
<smoorgborg[m]>
Thanks! Is the problem detectable by using a RAM testing tool btw, or is it only in combination with IO of sorts?
<tobhe_>
Can't say that I have tested that but I suspect it will only happen in combination with IO
Guest6484 has joined #aarch64-laptops
Guest6484 has quit []
srinik has quit [Ping timeout: 480 seconds]
jkm has quit [Quit: Lost terminal]
jglathe_volterra has joined #aarch64-laptops
jglathe_volterra has quit [Remote host closed the connection]
jhovold has quit [Ping timeout: 480 seconds]
davidinux has joined #aarch64-laptops
davidinux has quit [Remote host closed the connection]
davidinux has joined #aarch64-laptops
mbuhl has quit [Remote host closed the connection]