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
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<craftyguy>
steev: suspend, in el1 or el2, is broken for me. I would love to debug it somehow, but no kernel messages are written to indicate it's resuming, and the last messages when going to s2idle seem fine. I'm sure there are more tricks to get possible debug output that might help, but I don't know what they are
<craftyguy>
(I've also been holding out hope for el2, but it would be great if some qcom employees would take an interest in it 😉😉)
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]
chrisl has joined #aarch64-laptops
hexdump0815 has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
enyalios_ has joined #aarch64-laptops
enyalios has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
davidinux 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]
chrisl has joined #aarch64-laptops
<bumble[m]>
@_oftc_craftyguy:matrix.org I'm using x13s w/ postmarketos and suspend seems fine
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chloex3 has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
<chloex3>
anyone know how to get fedora to successfully boot off of the live iso on the X13s? i've tried with the kernel args "arm64.nopauth clk_ignore_unused pd_ignore_unused modprobe.blacklist=qcom_q6v5_pas" and that's worked a few times but now it black screens on boot and the display turns off after about a minute or so
<chloex3>
i've tried messing with the devicetree stuff a bit but that doesn't work either :<
<Jasper[m]>
Alright, then the Device Tree stuff. What did you try?
<chloex3>
i had sc8280xp-lenovo-thinkpad-x13s.dtb sitting on an efi partition and so i tried to use that with "devicetree (hd1,gpt1)/sc8280xp-lenovo-thinkpad-x13s.dtb" in grub but that didn't really seem to change anything
<Jasper[m]>
What I did when installing (a while ago), was to copy over a DTB (extracted from the *-qcom rpm package) and put it on the fat32 partition of the liveusb. Then when grub shows up, I put in the devicetree line pointing to the DT
<Jasper[m]>
chloex3: Yes
<Jasper[m]>
That is combined with the kernel options right?
<chloex3>
yeah
<chloex3>
right now i seem to get the fedora boot screen for like, less than a second then my screen goes blank
<Jasper[m]>
Try to remove the quiet kernel option and see what it does
<chloex3>
wait, okay, i got it to boot again , seemingly the device tree on the partition i was trying on was bad or something and i tried copying it to my usb and trying that and it worked
<chloex3>
okay
<Jasper[m]>
Nice!
<craftyguy>
bumble: nice, glad it works for you :) I really have no clue why I seem to be the only one who can't suspend/resume
shoragan has quit [Ping timeout: 480 seconds]
ravikant_ has joined #aarch64-laptops
<JensGlathe[m]>
craftyguy: any odd device enabled? Like crypto unit or sth?
<craftyguy>
No clue. I am running the same kernel/config that bumble is
<craftyguy>
i just learned about pm_trace, I'll try to use that and see if I can blame this on a specific driver or ??
<JensGlathe[m]>
any deferrals?
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
SpieringsAE has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
ravikant_ has quit [Remote host closed the connection]
ravikant_ has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
ravikant_ has quit [Remote host closed the connection]
ravikant_ has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
ravikant_ 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]
shoragan has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
ravikant_ has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
vfdkjted has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
ravikant_ has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
pbrobinson has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
icecream95 has joined #aarch64-laptops
<icecream95>
Anyone feel like writing a test case for ANGLE developers, since apparently they have better things to do than write it themselves? https://issues.angleproject.org/issues/431097618
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
martiert_ has joined #aarch64-laptops
ravikant_ has joined #aarch64-laptops
martiert_work has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
pbrobinson has joined #aarch64-laptops
ravikant_ has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
<chloex3>
fedora seems to work beautifully on the X13s. the only real problems i have are audio being really distorted and hw accel being broken in some electron apps. does anyone know if audio will get better soon? or if it's just some config issue for me?
<\[m]>
for audio I think you need to switch to pulse audio for now iirc
chrisl has joined #aarch64-laptops
<\[m]>
there was some bug with pipewire or idk
<Jasper[m]>
I also think the problems with electon/chromium are being discussed above hahaha
<Jasper[m]>
*electron
<chloex3>
pulseaudio seems to make the audio slightly better xD
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<jdb[m]>
I wonder if anyone has or had a similar issue on sc8280xp or on x1/x1e with the laptop not fully shutting down?
<jdb[m]>
I'm facing this issue with the Surface Pro 11, it seems to be halting normally but in fact the battery keeps draining
<jdb[m]>
Anyone seeing this on the Surface Laptop 7 which should be very similar maybe?
<jdb[m]>
Or coud it be a simple config issue? I'm running Debian Trixie fwiw
chrisl has joined #aarch64-laptops
<jdb[m]>
The battery can be almost flat in 24h
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
<anthony25>
I never had the issue (yoga slim 7x)
<anthony25>
and there was periods during which I didn't use the laptop for 2 weeks, it was left shutdown and the battery was about where I left it 2 weeks before
chrisl has quit [Ping timeout: 480 seconds]
<jhovold>
chloex3, \[m]: the pipewire issues were fixed 6.15-rc1 (and the fixes backported) so there shouldn't be a need to switch to pulseaudio anymore
<jhovold>
I recently dropped the issue from the wiki since I figured everyone would be running a kernel with the fixes by now, I can add it back for a while longer
eirikkar has quit [Ping timeout: 480 seconds]
<jhovold>
craftyguy: really odd with your suspend issue on the x13s, I'm pretty sure I asked before, and you didn't have a modem, right? What about messing with disabling devices in the uefi setup as some folks did, you haven't done that either?
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<\[m]>
jhovold seems fedora 42 has 6.14 so myes
<\[m]>
not sure
<jhovold>
the fix was supposedly backported to 6.14.3, but perhaps the backport was incomplete
<jhovold>
(e.g. depending on some other change in 6.15-rc1, I never tested the backports myself)
chloex3_ has joined #aarch64-laptops
chloex3__ has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chloex3_1 has joined #aarch64-laptops
chloex3 has quit [Ping timeout: 480 seconds]
chloex3 has joined #aarch64-laptops
chloex3_ has quit [Ping timeout: 480 seconds]
chloex3__ has quit [Ping timeout: 480 seconds]
chloex3_ has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chloex3_1 has quit [Ping timeout: 480 seconds]
chloex3__ has joined #aarch64-laptops
<JensGlathe[m]>
There are similar sound issues on X1
<JensGlathe[m]>
Degradation over time
chloex3 has quit [Ping timeout: 480 seconds]
<jhovold>
the underlying issues affecting pipewire were the same on x13s and x1e, but there might be further issues
chloex3 has joined #aarch64-laptops
<jhovold>
Here's an updated wip branch for the X13s:
<jhovold>
- fix epoll hangs (e.g. in gnome) (6.16-rc5 regression)
chloex3_ has quit [Ping timeout: 480 seconds]
<lynxy>
oh, good timing- was just rebuilding for rc6 lol
chrisl has joined #aarch64-laptops
<Jasper[m]>
@jhovold I will try switching back to pipewire tonight if Fedora ships 6.14.3 and report back
<jhovold>
Jasper[m]: thanks!
chloex3__ has quit [Ping timeout: 480 seconds]
chloex3_ has joined #aarch64-laptops
chloex3__ has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<anthony25>
<JensGlathe[m]> Degradation over time << and for example iirc macc24 had hardware issues with their laptop (over-heating) after issues with speakers
<anthony25>
I prefer removing the speakers from the dts for now until there's some protection implemented
chloex3 has quit [Ping timeout: 480 seconds]
<macc24>
anthony25: it wasn't overheating, it just couldn't power off
<macc24>
at least that's what i suspect
<anthony25>
oh ok
<anthony25>
so similar to what jdb[m] is describing?
chloex3_ has quit [Ping timeout: 480 seconds]
<macc24>
fried speaker chips -> soc gets too confused to idle or something -> laptop always uses at least a couple watts even when off
<JensGlathe[m]>
Well this is some odd buffer issue, or „micro-crashes of the adsp“ (wtf)
<macc24>
i think it's similar... can't tell without knowing what caused it
<macc24>
also i had VERY distorted sound even on windows
chrisl has joined #aarch64-laptops
<anthony25>
yeah… I think Ubuntu made the right decision to disable the speakers by default for now
ravikant_ has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<dgilmore>
Fedora 42 has 6.15 now
<Jasper[m]>
@dgilmore nice, will still test that out then
ravikant_ has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
<JensGlathe[m]>
I have normal sound on Windows. Also normal sound on USB. It is some odd DSP issue. On X13s this is fixed.
<jdb[m]>
it seems my issue when trying to halt / poweroff my Surface Pro 11 was transient, or it depends on a specific condition, as I can't reproduce it right now...
<jdb[m]>
I can detect when things are working as expected, as the keyboard makes a small sound when it is powered down properly
<jdb[m]>
I will see if it happens again
<JensGlathe[m]>
nice debug feature
<jdb[m]>
indeed !
chrisl has quit [Ping timeout: 480 seconds]
ravikant_ has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
bionade24 has quit []
bionade24 has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chloex3 has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chloex3__ has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
<jdb[m]>
Val Packett: what did you mean by the pciset script earlier?
chrisl has quit [Ping timeout: 480 seconds]
<jdb[m]>
I would be interested in testing the same ASPM config
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
martiert has quit [Ping timeout: 480 seconds]
icecream95 has quit [Ping timeout: 480 seconds]
ravikant_ has quit [Remote host closed the connection]
ravikant_ has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
whiskey9 has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
ravikant_ has quit [Ping timeout: 480 seconds]
<steev>
jhovold: is audio supposed to work on the t14s with your kernel/config?
chloex3 has quit [Quit: WeeChat 4.6.3]
chrisl has quit [Ping timeout: 480 seconds]
<jhovold>
steev: yes, it works mostly fine
<steev>
hm, okay
<steev>
for me, on my t14s (oled), i am getting sound snd-x1e80100: WCD Playback: codec dai not found in my devices_deferred
<jhovold>
volume mapping is off, missing speaker protection, and occassional playback failures since some kernel release
<jhovold>
odd
<steev>
if i used JensGlathe[m]'s kernel which uses ubuntu's config, it seems to load just fine
<steev>
but that's a heavy config
<jhovold>
I'm using that config myself and sound works here, perhaps some change in timing is triggering another bug
<jhovold>
have you tried loading triggering a reprobe by loading the module manually?
<jhovold>
valpackett: thanks for reporting that aspm is broken for wifi, like mani said it is supposed to be enabled
<steev>
iirc, it wouldn't let me reload the module
<jhovold>
apparently it's yet another prwctrl regression in 6.15, 6.14 works as expected
<jhovold>
mani_s: ^
<steev>
i'm about to be in a meeting but will check after
chrisl has joined #aarch64-laptops
<mani_s>
jhovold, which pwrctrl regression? Is that related to the aspm issue or something else?
<mani_s>
aspm issue is not related to pwrctrl (though pwrctrl is the one exposing it).
<jhovold>
yes, it seems like a pwrctrl regression to me, qcom_pcie_enable_aspm() is no longer called for ath11k/ath12k since 6.15
<jhovold>
like the devices are not registered in time, only had a quick look
<mani_s>
well it is not a regression, but the way qcom_pcie_enable_aspm() is called. it was supposed to work only for already powered on devices
<mani_s>
I have the fixes ready. Will submit and CC you
<jhovold>
iirc, you did some pwrctrl rework in 6.15
<jhovold>
perfect, thanks
<jhovold>
but the wifi is left enabled by the boot firmware, but yeah, I can imagine things breaking with pwrctrl
<jhovold>
yeah, I did try ripping out pwrctrl and that makes sure that aspm is enabled again
<jhovold>
so definitely pwrctrl related
<jhovold>
and it's definitely a regression, since ASPM is enabled when booting a 6.14 kernel
<mani_s>
jhovold, that's interesting. maybe pwrctrl is turning off the device and enabling it back due to probe deferral?
<jhovold>
it seems like some registration ordering has changed, since qcom_pcie_enable_aspm() is no longer called for the ep
<jhovold>
iirc, that's sounds related to the pwrctrl rework you did
<jhovold>
qcom_pcie_host_post_init_2_7_0() does a bus walk, but the device is not there (yet)
<mani_s>
jhovold, but the issue in the pcie-qcom driver is that, qcom_pcie_enable_aspm() will only be called for devices enumerated during the controller driver probe i.e., already powered on devices
<jhovold>
right, that's the regression
<mani_s>
well, that's not the regression but the flaw in the pcie-qcom driver. It is supposed to enable ASPM even for hotplugged devices, not just for the ones already powered on by the bootloader
<mani_s>
I knew this limitation when I implemented that logic, but...
<jhovold>
it's most certainly a regression, since aspm is enabled in 6.14 but no longer in 6.15, there's literally no way around that fact
chrisl has quit [Ping timeout: 480 seconds]
<mani_s>
jhovold, I don't disagree with you. But just that I wanted to point out the fact that the issue existed even before then, just that it was not triggered
<jhovold>
sure, i don't doubt that
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<steev>
jhovold: when i attempt to modprobe -r the snd-soc-wcd938x-sdw driver, i end up with a lockup of some sort
<jhovold>
sounds like something's quite broken
<jhovold>
but soundwire is special
<steev>
it's not locked up locked up, just graphically - i can ssh in
<steev>
and attempting to modprobe e.g. snd-soc-wcd938x-sdw (which doesn't seem to probe the snd-soc-wcd938x?) causes the terminal i'm sshed into to lock up; likewise for snd-soc-wcd938x
<steev>
the machine itself is NOT it's just unresponsive wherever i modprobe something :D
chrisl has joined #aarch64-laptops
ironcastor has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<craftyguy>
jhovold: I do have a modem, but currently don't use it. I haven't tried messing with disabling devices in uefi, I could give that a try
chrisl has joined #aarch64-laptops
SpieringsAE has quit [Quit: SpieringsAE]
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<jhovold>
craftyguy: disabling devices in uefi should not be needed, and could potentially makes things worse, that's why I asked
<jhovold>
but i've seen some modem related regressions on the x1 crd here that affects suspend
<jhovold>
you could try unbinding modem driver before suspending and see if that helps
chrisl has joined #aarch64-laptops
chloex3 has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<craftyguy>
ah ok, I misunderstood. ya AFAIK I haven't disabled anything in uefi...
<craftyguy>
dang, I guess pm_trace is only available on x86
<ironcastor>
what's the best supported arm64 laptop?
<craftyguy>
the modem driver seems to be 'mhi-pci-generic' ? (according to lspci -k)
<chloex3>
anyone know how to get WWAN working on the X13s? i have the fcc unlock scripts enabled, but it shows "Timeout was reached" and spams logs as shown in screenshot https://i.imgur.com/pYh7dqD.png
<steev>
there was something about it maybe choosing the wrong sim slot a few days/weeks ago?
chrisl has joined #aarch64-laptops
<steev>
i don't have wwan on mine
chrisl has quit [Ping timeout: 480 seconds]
<jhovold>
craftyguy: yeah, that's the one
<jhovold>
other people with an x13s with a modem still seem able to suspend, but may be worth a try anyway
chrisl has joined #aarch64-laptops
<\[m]>
<ironcastor> "what's the best supported..." <- chromebook? 😆
<craftyguy>
jhovold: unbinding the modem didn't seem to help.
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
<bumble[m]>
wish you were having the great experience on x13s that I am. x13s+postmarketos have been excellent 👍️👍️ thank you
<craftyguy>
haha, glad to hear 😁 Ya my problem is bizarre. I'm still open to more ideas for how to debug it 😅
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
<steev>
bamse: any word from the firmware peeps?
<steev>
craftyguy: have you tried the test stuff (please note, i do not know what the test stuff is exactly, just some docs in thue kernel about testinng suspend (sorry for typos, i'm typing around the t14s on a different keyboard
chrisl has quit [Ping timeout: 480 seconds]
gabertron has quit [Remote host closed the connection]
<d0pefish>
was pretty terrifying trying to get git send-email to include the right recipients via get_maintainers etc and ensure the series was threaded properly with the cover letter, praying that I haven't catastrophically spammed the heck out of thousands of inboxes (!!)
<craftyguy>
steev: pm_test maybe? I haven't tried that yet, just discovered it.
chrisl has joined #aarch64-laptops
gabertron has quit [Remote host closed the connection]
gabertron has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<steev>
yeah, i think that's what i saw in my search, no idea if it works for arm64
chrisl has joined #aarch64-laptops
<jdb[m]>
d0pefish: You're welcome!
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
gabertron has quit [Remote host closed the connection]
xroumegue has joined #aarch64-laptops
gabertron has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
gabertron has quit [Remote host closed the connection]
<deathmist>
anyone with X1E Vivobook got slbounce (EL2 for QEMU/KVM etc) working? I can't get sltest to show a green line so I've not gone further than that yet. tried tcblaunch.exe with the following sha256sums: 6ebd501a16af0f66117ff822abaae5f255f822dcc566c3cafb16e3fb62953aba & f6fc6ac7b408b01ca79f53a5f3d72b907c5a580ea7db6c4827d37b4e4a858aed
gabertron has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
<deathmist>
the first one is from the original windows install (had it laying around windows.old dir still) and the latter from latest canary insider preview I've currently got multibooted
gabertron has quit [Remote host closed the connection]
gabertron has quit [Remote host closed the connection]
chrisl has quit [Ping timeout: 480 seconds]
pbrobinson has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
<angeloverlain[m]>
<jdb[m]> "I'm facing this issue with the..." <- I think this issue has occurred traditionally with surface devices. maybe check linux-surface on github?
pbrobinson has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<deathmist>
my sltest just hangs with something like this left on the display https://i.imgur.com/HkfA8Y4.png, have to hard poweroff with button. I copied all the files to ESP root
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
eirikkar has joined #aarch64-laptops
<jdb[m]>
angeloverlain: thanks for the suggestion
ravikant_ has joined #aarch64-laptops
gabertron has joined #aarch64-laptops
<jdb[m]>
robclark: thanks for the suggestion to try to reuse dpcd_quirk_list instead of the current patch
<robclark>
np
<jdb[m]>
And indeed, the Surface Pro 11 can use different panel options, at least OLED and LCD ones
<robclark>
turns out this isn't the first device that needs a quirk ;-)
<robclark>
yeah, ok.. then defn matching based on panel id would be better
<jdb[m]>
Sadly, but indeed not the first one!
<jdb[m]>
We will give it a try, based on the panel id, let's see if we get other suggestions on the mailing list