soft lockup cpu on galaxy book s

[nullexistence]

[pierro78]

Any updates?

I am following the devs work on the aarch64-laptops irc and to my understanding there has not been notable progress lately although jenneron has worked on his Snapdragon Book S recently

[mothenjoyer69]

@pierro78 @matdomis Unfortunately nothing from my end; My Galaxy Book S has been loaned out for the foreseeable future, and I haven't quite been able to stomach the cost of buying a second unit yet. It is a device I am keen to return to when I am able to. It does look like jenneron has done some work lately, although I haven't touched base with them in a while.

[SNF444]

Hey all

Just wondering about the potential NAS applications with the work being done here. At this stage from my understanding is that the charging has issues but I'm wondering if enough power is delievered to keep the device on indefinitely as long as it remains plugged in ?

If thats the case does anyone know of any potential issues running things like docker or OMV, any virtual machines and shares etc.

It wouldn't require graphical desktops and the like, aswell touchscreen and similar features, acting only as a low powered NAS just for the sake of it.

[pierro78]

@SNF444 : the kernel provided in https://github.com/aarch64-laptops/debian-cdimage/issues/16#issuecomment-1231888011 is minimal and some features are not activated ... like, for example, network bridge needed by docker ... so you'd need to recompile your kernel if you want to do docker stuff with an up-to-date kernel ...

[SNF444]

Thanks for the quick reply , and alright I think thats doable I'll give it ago.

[pierro78]

comment from "agl7" on the aarch64-laptops irc : "As a Linux system I got Armbian to work. But not really either, there are always kernel panic errors."

https://oftc.irclog.whitequark.org/aarch64-laptops/2023-04-08 .

[SlowKnight0]

Hey I'm very much a novice when it comes to regular linux let alone talking about kernels and what not.

I've followed this page in a regular x64 Ubuntu vm:

https://github.com/Mani-Sadhasivam/debian-cdimage/tree/main/doc

And this error appeared in the very first of the Build kernel deb

When I look for the lexer.lex.c it isn't in the respoitory if thats correct.

Can anyone point in the right direction ?

[pierro78]

Hey I'm very much a novice when it comes to regular linux let alone talking about kernels and what not.

I've followed this page in a regular x64 Ubuntu vm:

https://github.com/Mani-Sadhasivam/debian-cdimage/tree/main/doc

And this error appeared in the very first of the Build kernel deb

When I look for the lexer.lex.c it isn't in the respoitory if thats correct.

Can anyone point in the right direction ?

are you trying to cross compile your ARM Snapdragon Galaxy Book S kernel ? it might be easier to compile it under windows on your ARM Snapdragon Galaxy Book S with WSL (that s what I did)

you have requirements (see https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel ) before compiling your kernel "flex not found" means you have not installed the "flex" package (see for example https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel )

[SlowKnight0]

Yes I think, I'm trying to build an installer for both your version and the battery fork, to install either alongside windows or standalone on the galaxy book s.

I did originally begin under wsl on the device itself but encountered the same issue (thanks lots for the answer)

I'm not entirely sure how to specifically target those source packages so I was going to start by following the guide I linked above.

Thanks for the help, and do you see any issues with my current path?

I had thought that building those sources into an image alone might mean that I could skip most of the steps but I'm thinking they will all still need to be done.

[pierro78]

I'm not entirely sure how to specifically target those source packages so I was going to start by following the guide I linked above.

Thanks for the help, and do you see any issues with my current path?

not really, myself I just followed the "Kernel Upgrade" section of https://github.com/aarch64-laptops/debian-cdimage and did not have any issue building my kernel packages from jenneron's sources ( aarch64-laptops irc ) (note that in the "Kernel Upgrade" section of https://github.com/aarch64-laptops/debian-cdimage they tell you how to install flex, etc ...)

[SlowKnight0]

Ah this crossed my mind, perhaps I should just do this instead.

So instead of I might do this.

When following your instructions on copying the dtb and installing the .deb etc.

Do I intially boot from the latest iso under

https://github.com/aarch64-laptops/debian-cdimage/releases

and follow those instructions with the your resource ? here

https://github.com/pierro78/galaxybooks8cxkerneldeb/releases/tag/v0.1

Reading those instructions it talks about firmware related to the flex 5g, guessing I just skip over those parts.

[oktaykarakiya]

I'd like to help out with the coding stuff, i dont have much experience with these things, but i can code, and if someone could help me a little initially i think that i could dedicate some time to code stuff for this wonderful device

[LeosDing]

All done under galaxy book s w767?

[pierro78]

All done under galaxy book s w767?

sure, you are in the AArch64-laptops github project here ....

[pierro78]

I'd like to help out with the coding stuff, i dont have much experience with these things, but i can code, and if someone could help me a little initially i think that i could dedicate some time to code stuff for this wonderful device

did you try to talk about your project in the aarch64-laptops irc ??

[LeosDing]

Okay I reinstalled it and got it to kinda boot. It gets onto kernel cmdline, I keep the two sticks in so it doesn't lockup and it hangs on a black screen with a _ after that.

I have encountered the same problem as you, and I also need a random FAT32 USB drive to start. Otherwise, there will still be lockup issues.

How did you solve it later?

[pierro78]

How did you solve it later?

I think he re-compiled the kernel ( I have also recompiled it and made it available, see https://github.com/aarch64-laptops/debian-cdimage/issues/16#issuecomment-1231888011 )

[LeosDing]

How did you solve it later?

I think he re-compiled the kernel ( I have also recompiled it and made it available, see #16 (comment) )

In my case, the 5.11 kernel you compiled must have two typec HUBs plugged in to boot properly from the UFS disk.

[pierro78]

In my case, the 5.11 kernel you compiled must have two typec HUBs plugged in to boot properly from the UFS disk.

I compiled Jenneron's kernel sources and they are 5.19 and no need for USB sticks to boot, see https://github.com/aarch64-laptops/debian-cdimage/issues/16#issuecomment-1231888011 , see also the comment below for more details : https://github.com/aarch64-laptops/debian-cdimage/issues/16#issuecomment-1231898585

[LeosDing]

In my case, the 5.11 kernel you compiled must have two typec HUBs plugged in to boot properly from the UFS disk.

I compiled Jenneron's kernel sources and they are 5.19 and no need for USB sticks to boot, see #16 (comment) , see also the comment below for more details : #16 (comment)

Is your DTB compiled from the 5.19 kernel? Is this DTB file placed in /boot and added as a devicetree in grub.cfg? Or was it directly thrown into the /boot/efi/dtb directory?

[pierro78]

Is your DTB compiled from the 5.19 kernel? Is this DTB file placed in /boot and added as a devicetree in grub.cfg?

Exactly ! ( as I said in https://github.com/aarch64-laptops/debian-cdimage/issues/16#issuecomment-1231898585 )

[LeosDing]

Is your DTB compiled from the 5.19 kernel? Is this DTB file placed in /boot and added as a devicetree in grub.cfg?

Exactly ! ( as I said in #16 (comment) )

Following your steps, the 5.19 kernel you compiled will display the following boot time: EFI stub: Booting Linux Kernel... EFI Stub: Using DTB from configuration table EFI Stub: Exiting boot service... if add 'devicetree /sc8180x-samsung-galaxy-book-s.dtb' to grub.cfg (this dtb file from your 'linux-image-5.19.0-next-20220810-custom-..deb' file.), only show: _

Using ISO default kernel(5.11): Picture1. Do not plug in 2 typec hub(Failed and hang)

Picture2. Plug in 2 typec hub(Success startup)

[LeosDing]

Is your DTB compiled from the 5.19 kernel? Is this DTB file placed in /boot and added as a devicetree in grub.cfg?

Exactly ! ( as I said in #16 (comment) )

Following your steps, the 5.19 kernel you compiled will display the following boot time: EFI stub: Booting Linux Kernel... EFI Stub: Using DTB from configuration table
EFI Stub: Exiting boot service... if add 'devicetree /sc8180x-samsung-galaxy-book-s.dtb' to grub.cfg (this dtb file from your 'linux-image-5.19.0-next-20220810-custom-..deb' file.), only show: _

add 'console=tty0' under linux kernel line.

[LeosDing]

The 5.19 kernel you compiled requires the DTB file you provided to boot properly, and the DTB in this kernel cannot be used. The DTB in the 5.19 kernel that I compiled myself can boot the system normally. WIFI is ok. No longer requires two typec hubs to start.

Some issues:

1. 5.19 Kernel needs to add 'console=tty0'
2. Unable to recognize wired network card on typec hub
3. No sound card driver
4. Unable to identify battery and battery level
5. Touch screen cannot be used

Tomorrow, I will try the 6.0.6-battery kernel again and perhaps solve the above problems.

[oktaykarakiya]

Debian 12 came out, did anyone try?

[LeosDing]

Debian 12 came out, did anyone try?

It's auto upgrade to Debian 12.

[oktaykarakiya]

So you had Debian 11 and now you have Debian 12? how is it? (aka did you try Debian 12) Does everything work?

[LeosDing]

So you had Debian 11 and now you have Debian 12? how is it? (aka did you try Debian 12) Does everything work?

For me, just like 11, there's no big difference.