Problems with WLAN

[scritrolf]

Hello all,
I greatly appreciate this project and so far had lots of fun with the rather lower levels of linux deployments :)
I cannot get the wifi to work, however. There's two scenarios:

• All WIRELESS_* entries commented out in thinstation.conf.buildtime: The soon-to-be thinclient boots up in a couple of seconds and on the terminal, I can populate /etc/wpa.conf and run wpa_supplicant manually which established a connection to the network I configured
• All WIRELESS_* entries (show below) in thinstation.conf.buildtime: The soon-to-be-thinclient boots up, shows the splash, gets to approx 60% of the progress bar, stays there for 1-2 minutes, continues to about 90% of the progress bar where it hangs indefinitely. I cannot debug this as altough I loaded debug modules, disabled boot splash, and set haltonerror to false, I don't get a console anywhere.
  Here's the relevant config:
  WIRELESS_ESSID="MYESSID"
  WIRELESS_NWID=""
  WIRELESS_MODE="Managed"
  #WIRELESS_FREQ=""
  #WIRELESS_CHANNEL=""
  #WIRELESS_SENS=""
  #WIRELESS_RATE=""
  #WIRELESS_RTS=""
  #WIRELESS_FRAG=""
  WIRELESS_IWCONFIG=""
  WIRELESS_IWSPY=""
  WIRELESS_IWPRIV=""
  WIRELESS_WPAKEY="MYWPAPASSWORD"

Any ideas?

[Doncuppjr]

I think you only need MODE ESSID and WPAKEY Possibly the WEXT line Sent from Yahoo Mail for iPhone On Saturday, November 4, 2023, 12:52 PM, scritrolf ***@***.***> wrote: Hello all, I greatly appreciate this project and so far had lots of fun with the rather lower levels of linux deployments :) I cannot get the wifi to work, however. There's two scenarios: - All WIRELESS_* entries commented out in thinstation.conf.buildtime: The soon-to-be thinclient boots up in a couple of seconds and on the terminal, I can populate /etc/wpa.conf and run wpa_supplicant manually which established a connection to the network I configured - All WIRELESS_* entries (show below) in thinstation.conf.buildtime: The soon-to-be-thinclient boots up, shows the splash, gets to approx 60% of the progress bar, stays there for 1-2 minutes, continues to about 90% of the progress bar where it hangs indefinitely. I cannot debug this as altough I loaded debug modules, disabled boot splash, and set haltonerror to false, I don't get a console anywhere. Here's the relevant config: WIRELESS_ESSID="MYESSID" WIRELESS_NWID="" WIRELESS_MODE="Managed" #WIRELESS_FREQ="" #WIRELESS_CHANNEL="" #WIRELESS_SENS="" #WIRELESS_RATE="" #WIRELESS_RTS="" #WIRELESS_FRAG="" WIRELESS_IWCONFIG="" WIRELESS_IWSPY="" WIRELESS_IWPRIV="" WIRELESS_WPAKEY="MYWPAPASSWORD" Any ideas? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Doncuppjr]

This is example that I use often thinstation/ts/build/conf/octoprint/thinstation.conf.buildtime at 6.2-Stable · Thinstation/thinstation  | | | | | | | | | | | thinstation/ts/build/conf/octoprint/thinstation.conf.buildtime at 6.2-Stable · Thinstation/thinstation A framework for making thin and light Linux based images for x86 based machines and thinclients. - Thinstation/thinstation | | | | Sent from Yahoo Mail for iPhone On Saturday, November 4, 2023, 12:52 PM, scritrolf ***@***.***> wrote: Hello all, I greatly appreciate this project and so far had lots of fun with the rather lower levels of linux deployments :) I cannot get the wifi to work, however. There's two scenarios: - All WIRELESS_* entries commented out in thinstation.conf.buildtime: The soon-to-be thinclient boots up in a couple of seconds and on the terminal, I can populate /etc/wpa.conf and run wpa_supplicant manually which established a connection to the network I configured - All WIRELESS_* entries (show below) in thinstation.conf.buildtime: The soon-to-be-thinclient boots up, shows the splash, gets to approx 60% of the progress bar, stays there for 1-2 minutes, continues to about 90% of the progress bar where it hangs indefinitely. I cannot debug this as altough I loaded debug modules, disabled boot splash, and set haltonerror to false, I don't get a console anywhere. Here's the relevant config: WIRELESS_ESSID="MYESSID" WIRELESS_NWID="" WIRELESS_MODE="Managed" #WIRELESS_FREQ="" #WIRELESS_CHANNEL="" #WIRELESS_SENS="" #WIRELESS_RATE="" #WIRELESS_RTS="" #WIRELESS_FRAG="" WIRELESS_IWCONFIG="" WIRELESS_IWSPY="" WIRELESS_IWPRIV="" WIRELESS_WPAKEY="MYWPAPASSWORD" Any ideas? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[scritrolf]

Thanks for the very quick reply. I tried the config you mentioned but it's still getting stuck at about 90% of the progress bar of the splash screen. Here's the config files I'm using right now: https://scrit-my.sharepoint.com/:u:/g/personal/rolf_scr-it_de/ETNksjSd_aFFkRQ4mFfJhBwBK485WwBrEJ62yuSLkTy3jw?e=HtShIi

Booting from an USB Image written with mkmbrdrive btw...

Do you have any tips on how I could actually see what the kernel does when it's stuck? I tried the things mentioned in the wiki and also tried to mount /var/ from an extra partition on that stick but there's no logs on it.

Best regards,RS

[scritrolf]

Finally managed to make the boot process visible (via param kernelcmdline "loglevel=7" , param bootlogo false, param splash 0) but now I see the place where it stalls at first is when loading the bluetooth module. What could be the reason for this?

[Doncuppjr]

Idk, We never implemented Bluetooth. You can drop the module. Sent from Yahoo Mail for iPhone On Saturday, November 4, 2023, 5:38 PM, scritrolf ***@***.***> wrote: Finally managed to make the boot process visible (via param kernelcmdline "loglevel=7" , param bootlogo false, param splash 0) but now I see the place where it stalls at first is when loading the bluetooth module. What could be the reason for this? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>

[scritrolf]

Thanks, good idea :) I don't need it anyway.
But the boot still stalls. I've no idea what it tries to tell me :(
(the messages about the sda partitions are ok, there's a windows on it)

[Doncuppjr]

set param kernelcmdline "systemd.show_status=true rd.systemd.show_status=true" On Sunday, November 5, 2023 at 01:10:22 AM MST, scritrolf ***@***.***> wrote: Thanks, good idea :) I don't need it anyway. But the boot still stalls. I've no idea what it tries to tell me :( (the messages about the sda partitions are ok, there's a windows on it) — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: ***@***.***>

[scritrolf]

Thanks!