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
chrisl has joined #aarch64-laptops
craftyguy has quit [Remote host closed the connection]
chrisl has quit [Ping timeout: 480 seconds]
craftyguy has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
hexdump01 has joined #aarch64-laptops
reng has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
davidinux has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
tobhe_ has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
tobhe has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
hexdump0815 has joined #aarch64-laptops
hexdump02 has quit [Ping timeout: 480 seconds]
checkfoc_us9 has quit []
checkfoc_us9 has joined #aarch64-laptops
akhilpo has quit []
akhilpo has joined #aarch64-laptops
akaWolf0 has joined #aarch64-laptops
<akaWolf0> hi, guys. anyone had a problem with Linux kernel doesn't see a disk? bootloader working fine, initrd is loading, but then it can't mount rootfs because it completely can't see the internal disk. I didn't update kernel, system packages. just after one of the cycle of shutdown/turn-on it stopped to work.
hexa- has quit [Quit: WeeChat 4.4.3]
hexa- has joined #aarch64-laptops
<akaWolf0> Windows is working fine.
<akaWolf0> https://ibb.co/6RVJJ8Xq I don't know if that is related the error with psci
<akaWolf0> yeah, at x13s
<steev> do you have the pci and nvme drivers in the initramfs?
<akaWolf0> well I didn't change literally nothing and it worked well before
<akaWolf0> only one reason of change I can imagine -- Windows updates/drivers/firmware
<akaWolf0> so since it worked before I guess those drivers should be in initramfs
eluks has quit [Remote host closed the connection]
eluks has joined #aarch64-laptops
<akaWolf0> steev, should I check for those drivers to be sure?
chrisl has joined #aarch64-laptops
<akaWolf0> is there any breaking change in the firmware maybe? so it's just incompatible...
chrisl has quit [Ping timeout: 480 seconds]
<JensGlathe[m]> Do you have the /etc/initramfs.tools/modules file?
<akaWolf0> you mean in rootfs? or in the loaded initramfs?
<akaWolf0> 5.19 ready image doesn't work, 6.2 my builded kernel doesn't work, 6.10.6 doesn't work
<JensGlathe[m]> it will be part of the generated initramfs.
<akaWolf0> MODULES=(nvme phy_qcom_qmp_pcie pcie_qcom i2c_hid_of i2c_qcom_geni leds_qcom_lpg pwm_bl qrtr pmic_glink_altmode gpio_sbu_mux phy_qcom_qmp_combo panel-edp msm phy_qcom_edp)
<akaWolf0> this is the config for the current latest kernel which I have (6.10.6)
<akaWolf0> but I didn't regenerate initramfs and it worked before
<akaWolf0> didn't rebuild kernel
<JensGlathe[m]> ok... booted from external USB stick / ssd?
<JensGlathe[m]> I guess my modules has also pwm_bl, but this should only affect screen if at all
lucanis has joined #aarch64-laptops
davidinux has joined #aarch64-laptops
<JensGlathe[m]> and no other kernel available on the disk?
<JensGlathe[m]> ok did the Windows update re-enable secure boot or something?
<JensGlathe[m]> since you mentioned firmware
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<steev> i don't see any bios update for my x13s
ungeskriptet__ has quit [Remote host closed the connection]
ungeskriptet has joined #aarch64-laptops
jhovold has joined #aarch64-laptops
akaWolf0 has quit [Remote host closed the connection]
<steev> did do a windows update which reset the boot config, but not secure boot; luckily i have a uefi shell entry in my grub config
<jhovold> dgilmore: that ath12k probe failure is unfortuantely a known regression, I've seen it a couple of times on the crd since 6.13
<jhovold> looks like a regression due to pwrctl/pwrseq
lucanis has quit [Read error: Connection reset by peer]
<jhovold> dgilmore: just posted a patch that should enable the modem in your t14s, can you give it a try?
<jhovold> but before testing the patch, can you send the output of 'grep 221 /sys/kernel/debug/gpio'
_mike is now known as masked
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
srinik has joined #aarch64-laptops
kalebris has quit [Remote host closed the connection]
kalebris has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
cyrinux9 has quit []
chrisl has joined #aarch64-laptops
cyrinux9 has joined #aarch64-laptops
kalebris has quit [Remote host closed the connection]
kalebris has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
number0ne has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
cyrinux94 has joined #aarch64-laptops
cyrinux9 has quit [Ping timeout: 480 seconds]
srinik has quit [Ping timeout: 480 seconds]
jglathe_angrybox has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
cyrinux949 has joined #aarch64-laptops
srinik has joined #aarch64-laptops
cyrinux94 has quit [Ping timeout: 480 seconds]
srinik has quit [Read error: Connection reset by peer]
<dgilmore> jhovold: can test. booting it up now to get the output
<dgilmore> jhovold: gpio221 : out high func0 4mA no pull
<jhovold> perfect, thanks, and that's before adding the patch, right?
<dgilmore> yep. just building the kernel now
number0ne has quit [Read error: Connection reset by peer]
number0ne has joined #aarch64-laptops
number0ne_ has joined #aarch64-laptops
number0ne has quit [Read error: Connection reset by peer]
srinik has joined #aarch64-laptops
tudorel has joined #aarch64-laptops
number0ne_ has quit [Remote host closed the connection]
number0ne_ has joined #aarch64-laptops
<dgilmore> jhovold: the pcie port does not come up
number0ne_ has quit [Remote host closed the connection]
number0ne_ has joined #aarch64-laptops
number0ne_ has quit [Remote host closed the connection]
number0ne_ has joined #aarch64-laptops
number0ne_ has quit [Remote host closed the connection]
number0ne_ has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
cyrinux949 has quit []
cyrinux949 has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<jhovold> dgilmore: the controller should show up (it does here), are you sure you're using the right dtb?
<jhovold> dgilmore: this is your problem:
<jhovold> [ 28.793242] platform regulator-wwan: deferred probe pending: (reason unknown)
<jhovold> [ 28.793243] platform 1c00000.pci: deferred probe pending: platform: supplier regulator-wwan not ready
<dgilmore> I triple checked I had the right dtb
<dgilmore> I wonder if that goes back to
<dgilmore> [ 1.401029] qcom-pcie 1c08000.pci: supply vddpe-3v3 not found, using dummy regulator
<JensGlathe[m]> both from the devkit, it has a LAN card in this slot
<dgilmore> nope that is just me looking in the wrong place
<jhovold> JensGlathe[m]: dgimlore's is testing a patch for t14s
<JensGlathe[m]> I know
<jhovold> no idea why the fixed regulator would fail to probe...
<JensGlathe[m]> the wwan is on pcie5, right?
<jhovold> yes
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
tudorel has quit [Quit: WeeChat 4.3.1]
<jhovold> dgilmore: I took a look at the fixed regulator code, but can't see why it would probe defer (without providing a reason)
<jhovold> perhaps you can add some printks to reg_fixed_voltage_probe() to figure out what is going on
chrisl has joined #aarch64-laptops
ungeskriptet_ has joined #aarch64-laptops
ungeskriptet has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
<dgilmore> Will take a look at the code
<JensGlathe[m]> I took another look at the devkit, there are a few dummy regulators, too.
<JensGlathe[m]> 1c00000 is pcie5
<JensGlathe[m]> 1c08000 is pcie4
<JensGlathe[m]> 1bc8000 is pcie6
<JensGlathe[m]> 🤔
<JensGlathe[m]> * 1bf8000 is pcie6
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
srinik has quit [Ping timeout: 480 seconds]
number0ne_ has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
number0ne_ has joined #aarch64-laptops
todi1 has quit [Remote host closed the connection]
number0ne has joined #aarch64-laptops
number0ne_ has quit [Read error: Connection reset by peer]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
ungeskriptet_ has quit [Remote host closed the connection]
ungeskriptet has joined #aarch64-laptops
number0ne has quit [Read error: Connection reset by peer]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
todi has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
jhovold has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
eirikkar has quit [Quit: Ping timeout (120 seconds)]
eirikkar has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
<sre> Would it be easy to add support for the LED in the T14s lid (i.e. is it just a simple GPIO)? Would be nice to change the state based on system suspend.
chrisl has quit [Ping timeout: 480 seconds]
cyrinux9490 has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
cyrinux949 has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
lucanis has joined #aarch64-laptops
<steev> i don't believe so, i believe its hooked up to the ec and most devices don't have an ec driver (yet)
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]