ChanServ changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630)
<steev> xyaon: fwiw, http://sprunge.us/EfDLDb is my kernel config, and i'm using the c630-linux-6.3.y tree in my github, and usb seems to work here
<steev> though, i might be missing a few modules, Bus 001 Device 008: ID 0cf3:9271 Qualcomm Atheros Communications AR9271 802.11n
alpernebbi has quit [Ping timeout: 480 seconds]
indy has quit []
alpernebbi has joined #aarch64-laptops
indy has joined #aarch64-laptops
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
alpernebbi has quit [Quit: alpernebbi]
alpernebbi has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
svarbanov has joined #aarch64-laptops
laine has quit [Read error: Connection reset by peer]
laine has joined #aarch64-laptops
Xyaon has quit [Read error: Connection reset by peer]
Xyaon has joined #aarch64-laptops
Cyrinux9 has quit []
Cyrinux9 has joined #aarch64-laptops
iivanov has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
svarbanov has quit [Ping timeout: 480 seconds]
systwi has joined #aarch64-laptops
<robclark> ajhalaney[m]: so, how did you get systemd-boot installed in the first place.. (or is it already installed? I don't see some alternative efi payload but also not sure what I'm looking for)
hightower3 has joined #aarch64-laptops
hightower2 has quit [Ping timeout: 480 seconds]
stirl has joined #aarch64-laptops
stirl has quit []
stirl has joined #aarch64-laptops
<stirl> Hello, I just purchased a lenovo x13s and I was hoping to learn about what the status is on the linux support and if there is anything that I could potentially help with
<ajhalaney[m]> robclark -- you're going to be horribly frustrated with me since I don't recall what I really did originally (it was wayyy back and I followed the debian installer). But in a sane world systemd-boot-unsigned provides sd-boot, out at /usr/lib/systemd/boot/efi/systemd-bootaa64.efi, and you install it with bootctl, but that sort of requires you to be standing up already
<ajhalaney[m]> I asked a buddy who recently redid his setup, we'll see if he's got some streamlined answer better than "grab that binary and put it in the ESP"
<clover[m]> robclark: mount your root partition on /mnt/ and your existing efi partition on /mnt/boot (if you havent wiped that already) then chroot into /mnt/ and install sd-boot from there
<ajhalaney[m]> at this point I'm just trying to get the legit fedora kernel to work ok (or at least figure out what's missing compared to a steev branch + config) but things are going black on me after booting a bit. Poking that on the side the last day or two
<clover[m]> The X13s ships with an existing EFI system partition on the internal drive that you can use /dev/nvme0n1p1
<robclark> looks like I need to dnf install something.. been trying to chroot into it but current kernel build on that device doesn't have exfat and I think steev's kernel is unhappy on the device
<stirl> clover[m] Do I just need to grab an arm iso and I am good to go then?
<stirl> Is there an "approved" iso that tends to work better than others
<clover[m]> i mean you can use the one i built
<clover[m]> but thats set up with arch linux
<stirl> arch would be fine
<stirl> where can I find this iso
<stirl> much appreciated
<steev> why would my kernel be unhappy? :(
<robclark> see splat I pasted in #linux-msm
<stirl> should I start from a blank disk or will this install alongside windows
<clover[m]> i installed alongside windows
<clover[m]> wish i gave myself more space though lol. only gave myself like 120GB
<steev> oh, hrm
<stirl> I have 200 that I set aside but I have a new drive coming in the mail
<stirl> I don't really want to break the windows install if possible
<clover[m]> yeah just follow arch guide for dual booting with sd-boot and you should be good
<steev> robclark: that's an sc8280xp?
<robclark> sc7280
<stirl> What is the deal with the linux option in the bios>boot menu? it doesn't say much about what it actually does
<steev> robclark: maybe something in abelvesa's syncstate stuff
<clover[m]> it allows firmware to load a dtb (if it can find it on the efi partition) but you can leave it off and it should still boot if you use the kernel dtb option
<stirl> got it. secure boot? TPM? all off?
<clover[m]> secure boot off idk about TPM
<stirl> I haven't ever really turned it on for any of my other installs and don't know much about how it interfaces with linux
<stirl> or if it does at all
<ardb> better leave the TPM on in case windows wants to access it
<ardb> it is not described in the DT so linux will ignore it
<stirl> ardb -- thanks! I wasn't thinking about how it would affect the windows install, leaving it on
<clover[m]> robclark: kernels >= 6.0 seem to have issues booting from a USB drive. both myself and ubuntu devs have noticed this
<clover[m]> newer ones should work fine from nvme though
<clover[m]> just an fyi idk if you are trying to use a usb iso
<clover[m]> if you are trying to boot from USB i'd use steev's lenovo-x13s-5.19.0.tar.gz branch
<clover[m]> err, tag
<stirl> how do you boot the iso from nvme?
<steev> very carefully (this is jokes)
<Xyaon> steev: Thanks for the help, unfortunately on my machine that config doesn't boot, it drops me into emergency shell after not being able to find the root partition. I suspect the problem is with my initramfs.
<robclark> clover[m]: hmm, that would be inconvenient since I need to boot from usb to get anything on to nvme
<clover[m]> it works like 1 out of 20 times, randomly, unless you use the older kernel
<steev> robclark: i'll probably drop that patchset; it's for being able to drop clk_ignore_unused (iirc) but afaik, still needs more work
<Xyaon> Does anyone here use mkinitcpio? I've specified firmware files to be included, but I still think there is something wrong with my images, does it need any additional configuration?
<clover[m]> whats in your /etc/mkinitcpio.d ?
<clover[m]> also your /etc/mkinitcpio.conf
<steev> what is in the initramfs; as long as you have the modules for the filesystem, it should be able to load them? do you have the ufs modules?
<clover[m]> here are my modules: 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)
<Xyaon> ohhhh
<Xyaon> I didn't specify any of those in my config
<Xyaon> i don't have any files in mkinitcpio.d
<Xyaon> and I only have the default modules and firmware files in my config
<clover[m]> i have linux-x13s.preset
<clover[m]> im guessing this runs mkinitcpio for me whenever i update my linux package
<Xyaon> im on a c630
<clover[m]> oh lmao, then idk if those modules will work for you
<steev> unlikely
<Xyaon> yeah, I kinda realized that after reading it, but I appriciate the intentions
<steev> let me wake my c630 up, one moment
<steev> i have ufs_qcom in my /etc/initramfs-tools/modules, doesn't look like i have anything else specific to the c630/qcom though
<Xyaon> I'll try adding that
<steev> konradybcio: testing your rsc stuff; looks like i'm getting better battery times again, though, not near what i was
<steev> steev@limitless:~$ uptime
<steev> 12:20:17 up 15:31, 1 user, load average: 0.83, 0.76, 0.54
<steev> battery is at 45%
<steev> (sdm845)
<Xyaon> steev: Including ufs_qcom did sort of help as I now see logs regarding it during boot, although it still can't initialize it. Could you share an image? I'll try to figure out what i'm missing from there.
<steev> https://buildd-arm.kali.org/experiments/ has my initrd.img-6.3.5 that i use on the c630
<Xyaon> It's working now! :)
Cyrinux9 has quit []
agl7-x13s has joined #aarch64-laptops
<Xyaon> I added ufs_qcom phy_qcom_qmp_ufs phy_qcom_qmp_usb and qrtr to the modules section
<Xyaon> Thanks for the help!
<steev> :)
Cyrinux9 has joined #aarch64-laptops
<agl7-x13s> xyaon: You use ufs_qcom! Do you use it on a Samsung Galaxy Book S with '8cx Gen1' Soc?
<Xyaon> agl7-x13s: yoga c630 :/
<agl7-x13s> Which SoC have this? '8cx Gen1'? '8cx Gen2'? Or '8cx Gen3'?
<steev> 845
<steev> sdm845
<agl7-x13s> ok
<agl7-x13s> Also bevore the '8cx Gen1'.
<Xyaon> I don't think it's soc specific
<steev> yes, it's before the 8cx
<Xyaon> I think I may have misiterpreted something
<agl7-x13s> ok, the kernel module 'ufs_qcom' produces Errors which fills the log files on the "Samsung Galaxy Book S" with '8cx Gen1' SoC.
<jenneron[m]> agl7-x13s: can you be more specific what's wrong with ufs on galaxy book s?
<agl7-x13s> And the internal SSD (UFS) is only accessable over Windows 11 Pro.
<agl7-x13s> jenneron[m]: Yes, I will start once more the Galaxy Book S and look for the errors. It's some weeks bevor where I do this.
<jenneron[m]> most likely some kernel config issue
<jenneron[m]> ufs worked for other people
<agl7-x13s> jenneron[m]: I mean I try the linux-kernel from your github.com-Account, but I must look if this is true.
<agl7-x13s> jenneron[m]: ok, I will compile and try this ... I have a debian-Installation on an USB-Stick for the Galaxy Book S. But I will do this tomorrow, today I'am a little malad from my work.
<agl7-x13s> jenneron[m]: An I will go to bed at 10 pm o'clock, in one and a half hours.
<agl7-x13s> jenneron[m]: I copied your message about the linux-kernel and the .config! Thank you!
<agl7-x13s> jenneron[m]: At compiling of the linux-kernel will there produce a .dtb-file which must to load by grub?
<jenneron[m]> yes
<agl7-x13s> ok
<jenneron[m]> if you want specifics read pmOS packages
<jenneron[m]> or make an installation of it
<jenneron[m]> I did this mostly for reference
<jenneron[m]> installation on USB with dtb is tricky on these devices
<agl7-x13s> pmOS? Is that a linux-dristibution?
<jenneron[m]> yes
<agl7-x13s> have you a URL of the web site where I can look/read about it?
<agl7-x13s> Thanks, but i mean about pmOS?
<jenneron[m]> consider it as a way to install alpine
<jenneron[m]> postmarketos.org
<steev> jenneron[m]: btw, did you see vkoul pushed out v3 of the sc8180x stuff?
<agl7-x13s> ah ok
<jenneron[m]> nope, I haven't looked into these for a long
<jenneron[m]> I base on surface pro x branches anyway
<jenneron[m]> because we need usb mp for keyboard and touchpad
<jenneron[m]> once it is accepted I may take a look at upstreaming without keyboard and touchpad though
<qzed> I might have a try and rebase the SPX stuff onto those today or tomorrow evening
<agl7-x13s> jenneron[m]: Have I to get the linux-krnel above with "git clone ..."?
<jenneron[m]> why do you ask me
<agl7-x13s> Yes I see
<jenneron[m]> there are different ways to get source
<qzed> jenneron: btw, the spx/v6.3.1-usb-mp branch uses the usb-mp stuff that's been sent in (and other patches to get that working on 6.3) if you want a more upstream-aligned base
<jenneron[m]> it doesn't matter, just use correct branch and config
<agl7-x13s> jenneron[m]: Yes I see the different ways ...
<agl7-x13s> jenneron[m]: I see Alpline is a musl system ....
<agl7-x13s> Alpine
zxrom has left #aarch64-laptops [Leaving]
<robclark> hmm, x13s seems to have the habit of "fixing" my partition table if I don't have a windows partition (and by "fixing" I mean completely breaking)..
<stirl> that is troubling
<steev> that doesn't seem right, afaik, HdkR doesn't use windows at all on his
<HdkR> Yep, deleted Windows off of all four of mine
<HdkR> And I'm aware of at least four others that also have Windows completely deleted and haven't had issues either
<stirl> how much does the battery life suffer on linux compared to windows?
<stirl> specifically for x13s
<agl7-x13s> jenneron[m]: Under debian I get shell errors (/bin/sh). Which shell uses Alpine as default?
<agl7-x13s> jenneron[m]: also wehen i try to compile the kernel
<steev> stirl: no idea, i've never used windows on it long enough to see what the battery life is like, mostly because i can't do my work on windows
<stirl> steev -- I haven't been using mine long, but I haven't been able to get linux installed yet. Seems like the battery life is on par with m1 mac(if not a bit better) maybe 10-12 hours of runtime on windows
<agl7-x13s> jenneron[m]: I see the CONFIG_SHELL = sh in the Makefile in the root of the linux tree ... Hmmm
<clover[m]> battery life is like 9-10 hours of light usage on linux i'd say
<jenneron[m]> agl7-x13s: there is nothing special about it
<stirl> I'm upgrading from a x250 that gets about 2.5 so 9 is great
<robclark> steev, HdkR: hmm.. well, I dd from raw.xz and everything looks fine in cfdisk, then try to boot it which doesn't work, then boot back to usb and nvme is messed up.. I think this is the thing I saw on c630, where fw gets grumpy if there isn't a backup GPT at the end of the disk
<steev> maybe run cgpt repair on the disk before rebooting?
<steev> i dunno if that's really chros specific tho
<robclark> I guess cfdisk will offer to repair the missing (or rather just, not actually at end of disk) GPT.. maybe that is enough
<agl7-x13s> jenneron[m]: I get the following errors (in German "Fehler"): CHKSHA1 include/linux/atomic/atomic-arch-fallback.h
<agl7-x13s> LDS arch/arm64/kernel/vdso/vdso.lds
<agl7-x13s> CHKSHA1 include/linux/atomic/atomic-long.h
<agl7-x13s> CHKSHA1 include/linux/atomic/atomic-instrumented.h
<agl7-x13s> make[1]: *** [scripts/Makefile.build:250: arch/arm64/kernel/vdso/vgettimeofday.o] Fehler 2
<agl7-x13s> make: *** [arch/arm64/Makefile:199: vdso_prepare] Fehler 2
<agl7-x13s> ag@Debian-x13s:/Software/kernel_und_altest_System/gitlab.com_jenneron(GALAXY)/linux-master$
<agl7-x13s> jenneron[m]: There came also the Error : /bin/sh: 1: Syntax error: "(" unexpected
<agl7-x13s> after the "LDS" line
<agl7-x13s> I get once more the linux-master file, this time as a zip file
<HdkR> robclark: https://gist.github.com/Sonicadvance1/81e217b481efd6aa2fc58682d79f6ee4 My layout is fairly standard, no backup stuff
systwi_ has joined #aarch64-laptops
systwi has quit [Ping timeout: 480 seconds]
<robclark> oh, there was a version with 2TB drive? I didn't see that option
<HdkR> Nah, I upgraded it myself
<robclark> ahh
<HdkR> The SN740 is basically the only good choice and you need a little 2230 to 2242 M.2 adapter :P
<qzed> agl7-x13s: any chance you're based in/around Freiburg?
<agl7-x13s> qzed: Bevor 20 years I live in Ulm/Donau. Now I'am living in Schongau, 82 km away from Munich in south west
<qzed> agl7-x13s: ah darn, I'll be moving to Freiburg soon and you mentioned clubhouse (I assumed CCC or something like that xD)
<agl7-x13s> qzed: In Ulm I was often at the university (respectively there I host my open source project) and there I was in an offshoot/meeting of the CCC. Now in Schongau I'm working in a rehabilitation facility in the IT department and there I'm often in the clubhouse for mentally ill people, because I maintain the two computers for the visitors there. I'm often there in my free time.
<agl7-x13s> It's funny there!
<qzed> ah, that's nice!
<robclark> steev: hmm, maybe what I'm dd'ing to /dev/nvm0n1 is just not getting flushed to disk properly when I reboot? I guess I could try manually partitioning and copying individual partitions
<qzed> robclark: I had a weird problem recently that I guess might have been similar
<steev> robclark: possibly? i'd defer to ajhalaney[m] because i don't know what raw.xz is
<robclark> it is raw disk image compressed w/ xz
<qzed> copied grub to /efi and it didn't stick, like the whole partition only contained the windows bootloader
<robclark> yeah, that is kinda similar to what I'm seeing
<qzed> second try I ran sync after and that stuck... I'm still weirded out and asking myself how that happened...
<robclark> I have tried `sync` fwiw..
<qzed> I mean normally it should also do that when you unmount... but yeah... weird things happened
<steev> stupid question but do you have linux selected in the bios?
<steev> or did you not bother selecting that (rob)
<steev> i don't actually think it would affect things, just wondering if selecting linux would cause it to do less... windows-y things
<robclark> what does "select linux" mean?
<robclark> I didn't do anything like that but didn't occur to me that there would be such an option
<steev> they have some beta linux option in the bios
<robclark> huh, ok.. I'll look for it
<steev> i do not have the contacts to know what it *really* does
<agl7-x13s> qzed: 23 years ago I became mentally ill and therefore moved to the rehabilitation facility in Schongau. But in the meantime I am doing very well again. I studied technical computer science and because I work in the IT department, I am up to date with information technology. In the IT department I (unfortunately) have to work with Windows, but at home I mainly do Linux. I also have Windows on my notebooks (e.g. on the ThinkPad X13s and
<agl7-x13s> Samsung Galaxy Book S) but I try to get Linux running on these two ARM computers. On my two x86_64 notebooks I have Manjaro-Linux (Arch) on it. On my RaspberyPi/NanoPI small computers I have EndeavourOS, DietPI OS, RaspberryPi OS and also Manjaro OS.
<qzed> I'm happy to hear you're doing better! I have a sister in Heiligenbronn (she has mental and physical disabilities) so I do quite appreciate anyone working in that field
<jenneron[m]> agl7-x13s: i don't know, check whether you have all the build dependencies installed
<agl7-x13s> jenneron[m]: I can compile steev's linux kernel to debian .deb files without any problem. At your linux kernel (I have also tried with "git clone ...") I compile only with "make" and not with the parameters for deb files. Where can I look for the dependencies. I don't know what packages i have to install more.
<agl7-x13s> jenneron[m]: I have also installed bison, yacc and flex and the packages for building deb files (e.g. dephelper).
<cenunix[m]> Is there a way to update the bios of the x13s without windows, I just realized I haven’t updated it
<qzed> agl7-x13s: here's what we use for x86, I guess it shouldn't be all that different for arm64:
<agl7-x13s> qzed: Thank you!
<cenunix[m]> Thx emily
<agl7-x13s> jenneron[m]: I specified the packages to install that qzed gave me. In fact other packages were installed that I didn't have installed yet, except the package "build-deb" which was not found or is not present in the Debian repo. But I get exactly the same errors (from /bin/sh) at the same place (after the LDS line) as before. So no change.
<qzed> the apt build-dep command should install all the dependencies of the given package name but afaik you need to change some config for that and run apt update
<qzed> then apt build-dep linux should in theory install everything you need
<steev> it'll do way more than needed
<steev> since that gives what it takes to build the actual debian packages
<agl7-x13s> qzed: When I make "apt update" there are 235 packages which want ro be updated ... I do this first ....
<agl7-x13s> Haven't done an upgrade in a while ....
<clover[m]> making me jealous. arch arm package updates have been broken for about a week
<clover[m]> steev: kali link fixed :)
<agl7-x13s> jenneron[m]: So upgraded and did "apt build-dep linux" also, got some stuff still installed. But the same error from /bin/sh:
<agl7-x13s> ----------------------------------------------------------------
<agl7-x13s> ...
<agl7-x13s> LDS arch/arm64/kernel/vdso/vdso.lds
<agl7-x13s> make[1]: *** [scripts/Makefile.build:250: arch/arm64/kernel/vdso/vgettimeofday.o] error 2
<agl7-x13s> make: *** [arch/arm64/makefile:199: vdso_prepare] error 2
<agl7-x13s> ag@Debian-x13s:/Software/kernel_und_altest_System/gitlab.com_jenneron(GALAXY)/linux-master$
<agl7-x13s> -----------------------------------------------------------------
<agl7-x13s> I have specified "unstable" in the /etc/apt/sources.list and am actually up to date with general Linux software. It cannot be that here an old shell version under Debian is used which does not get along with the Makefiles/scripts!
<agl7-x13s> There is missing the line "/bin/sh: 1: Syntax error: "(" unexpected" after the LDS line
<agl7-x13s> Now it's 00:54 am o'clock .... I'am going to bed ... see you later
agl7-x13s has quit [Quit: Leaving]
<clover[m]> Kinda curious about fedora ARM. Did you get it working robclark?
<robclark> clover[m]: at this point I'm trying to hack things to boot arch but with pointing to my fedora rootfs (until I can get to the point of building my own kernel).. I've not had much luck yet w/ fedora's grub or systemd-boot (but the later case may be down to my semi-manually cobbled together conf)
<robclark> (so tbf, the problem could actually be the fedora kernel.. idk at this point)
<robclark> once I get past bootstrap it should be easier