<mangix>
hmmm I can't find where kernel- is specified
<mangix>
bah I'm pretty sure this involves taking the device appart
<mangix>
the more I look at this the more I think this PR is mistaken in that it installs OpenWrt in the first partition. It looks like most devices install to the second one.
mangix has quit [Ping timeout: 480 seconds]
srslypascal is now known as Guest1444
srslypascal has joined #openwrt-devel
mangix has joined #openwrt-devel
srslypascal is now known as Guest1445
srslypascal has joined #openwrt-devel
<mangix>
bricked my device, AGH.
Guest1444 has quit [Ping timeout: 480 seconds]
Guest1445 has quit [Ping timeout: 480 seconds]
<mangix>
behind door 1: restore. behind door 2: open up device and get this FIT thing working.
goliath has quit [Quit: SIGSEGV]
danitool has quit [Quit: Cubum autem in duos cubos, aut quadratoquadratum in duos quadratoquadratos]
<hurricos>
has anyone else here experienced "searching" state with realtek-poe?
<hurricos>
mangix: compatible denx,fit is correct
<hurricos>
mangix: fit! fit!
minimal has quit [Quit: Leaving]
lynxis has quit [Remote host closed the connection]
lynxis has joined #openwrt-devel
srslypascal is now known as Guest1452
srslypascal has joined #openwrt-devel
srslypascal has quit []
Guest1452 has quit [Ping timeout: 480 seconds]
<neggles>
mangix: you should definitely be using FITs if the stock firmware does, it's nice and easy, and you don't need to open it up
<neggles>
mangix: right, then `KERNEL := kernel-bin | lzma | fit lzma $$(KDIR)/image-$$(firstword $$(DEVICE_DTS)).dtb` and put `compatible = "denx,fit";` in the firmware partition you want to use in the DTS should do it, then if you want ubifs there's a few extra bit
<mangix>
that...sounds like it needs further dts changesa
<neggles>
well
<neggles>
do you have a separate kernel/rootfs
<neggles>
partition pair i mean
<neggles>
ah yes okay
<neggles>
so KERNEL_IN_UBI is a no
<neggles>
and we can't mess with the default partition layout or their custom uboot script will get angry
<mangix>
should kernel be in ubi?
<neggles>
from a sheer technical perspective, yes, the way this *should* be done is with a single mtdpart on the NAND that's just UBIFS, with the kernels as ubivols, but nobody does that except sophos that i've found
<mangix>
I know of dango doing that
<neggles>
it would be easy to convert to that if not for the custom u-boot shenanigans they're doing.
<neggles>
what you have instead is, kernel is a FIT image in a partition, then ubifs where rootfs_data is (the 'ubi' partition) - also why on earth is alt_firmware so huge??
<mangix>
good question :)
<mangix>
alt_firmware is partition 2. I didn't bother subdividing it.
<mangix>
sorry, bootimage 2
<neggles>
ah, so it contains its own u_env/factory/kernel/ubi or?
<neggles>
just kernel/ubi?
<mangix>
probably just kernel/ubi
<mangix>
the beginning is definitely the kernel
<neggles>
alrighty, well you should definitely break those two partitions out in the dts as kernel2/ubi2, but
<mangix>
somebody posted the stock firmware layout in the forum
<neggles>
ah yep found it
<neggles>
oh now that's interesting
<mangix>
hmm?
<neggles>
well for one their stock fw mapping overlaps 'config' with 'factory'
<neggles>
but you've got chunks of it in your OpenWrt dts - devinfo, s_env
<neggles>
wait no that's all in config. nvm.
<mangix>
ah ty for asking
<mangix>
so the stock firmware lumps up everything in a single partition
<neggles>
i forgot how base16 works for a moment there.
<mangix>
I subdivided it
<mangix>
the devinfo partition is configuration information for the stock firmware
<neggles>
yeah, the question is whether it's loading the fit image from ubifs or not and it looks like no >:(
<mangix>
the s_env partition is mostly empty
ekathva has joined #openwrt-devel
<mangix>
CBTInfo is completely useless
<neggles>
yeah not surprised
<mangix>
hmmm I see mediatek,mtd-eeprom = <&factory 0x0000>;
<mangix>
so I guess factory is mostly useless
<neggles>
well no, it's got the mediatek radio eeprom/cal data in it :P
<neggles>
but you'd want to flag it read-only
<mangix>
I wonder why I subdivided kernel and ubi. stock firmware seems to not do that.
<neggles>
based on their gpl sources, CBTInfo seems to be the NAND bad block map
<neggles>
oh hey
<mangix>
hey
<neggles>
it's also where it's storing... u-boot version info?
<neggles>
ahhh device info
<neggles>
just some strings, would ignore
<mangix>
strings on CBTInfo returns 5 strings. They all look useless
<neggles>
they are
<neggles>
but the CBT_BOOT_VERSION string is checked by the mtkboardboot command
<mangix>
sigh. looks like I have to disassemble this to investigate
<neggles>
however it *is* just a command, and it's only called by bootcmd=, not by anything fancy/hardcoded like overriding bootcmd
<neggles>
does the stock firmware have `fw_setenv` / `fw_printenv` ?
<mangix>
beats me
<neggles>
fair enough
<neggles>
can't get root on it?
<mangix>
I mean if I disassemble it and hook up serial, yes
<neggles>
what've you been doing so far? trying to feed it an image over recovery?
<mangix>
nothing. it's just sitting on my desk. I have no idea how to activate the tftp client
<mangix>
through serial it's option 3 or something like that
<neggles>
ah okay
<neggles>
it will also start a http recovery thing if autoboot fails
<mangix>
pretty sure autoboot succeeds
<mangix>
and then fails
<neggles>
yeah
<neggles>
you'd have to purposefully corrupt both flash banks
<mangix>
I mean there are two partitions
<mangix>
there should be a way to boot firmware2
<neggles>
there is, it boots firmware2 if u-boot environment variable bootimage = 2
<neggles>
runs `nboot firmware_2`
<mangix>
no idea how to get it set to 2
<neggles>
can't ssh into the factory fw?
<mangix>
I doubt it
rua has quit [Ping timeout: 480 seconds]
<mangix>
actually, the device doesn't boot right now
<mangix>
well, it does but ends up failing
<neggles>
it's kinda weird
<neggles>
they've got two firmwares, and it's counting how many times boot has failed
<neggles>
but it doesn't do anything with that info
<neggles>
normally you'd have a "if ( bootcount >= 10 ) { boot the other image }" type block
<mangix>
I mean I'm sure it does
<neggles>
am looking at the code rn
<neggles>
it does not
<mangix>
that jeff guy was complaining about the PR not handling that
<neggles>
ah, no, no i'm blind it does
rua has joined #openwrt-devel
<neggles>
if bootcount >= 3, change 1 to 2 and 2 to 1
<neggles>
i would say you will need to take the thing apart, yeah. and ugh their u-boot is compiled with no ubifs support. typical.
<mangix>
I mean it's Cybertan crapware
<neggles>
they were *so close* to doing this correctly
rua has quit [Ping timeout: 480 seconds]
<neggles>
oh that's bloody clever of them </s>
<neggles>
mangix: they've got a codepath in here that brings up the failsafe web ui... except they've disabled the failsafe webui.
<neggles>
and it doesn't look like it does any checking for buttons to trigger a tftp recovery. so if it won't boot at all, uart's all you've got.
<neggles>
er, s/boot at all/boot to a state you can get into it from/
<mangix>
lolwut?
<neggles>
if it can't load either kernel, there's a failsafe webui it'll try to load, but only if it was turned on at compile time
<neggles>
and the config they've used, has it turned off
<mangix>
would be fun to replace the bootloader with breed, but I doubt breed would support this unit properly
<neggles>
so if neither kernel loads it just goes back to sitting at the u-boot shell
<neggles>
it would be trivial to replace the u-boot with one that does have UBI/FIT support
<mangix>
which sounds great
<neggles>
but flashing it from an unopened device / without uart might be difficult depending on whether you're root if you ssh into the stock firmware
<neggles>
and booting/installing with stock bootloader still needs to be possible, so you'd end up with something like what we have for U6-LR - two targets, one for modded/custom uboot, one for factory
rua has joined #openwrt-devel
<neggles>
but yeah it just runs nandboot <first sector of firmware or firmware_2> depending
<neggles>
and some scripts need to be fiddled with to handle the bootcount and alternate firmware banks
<neggles>
mangix: I have to correct myself again, your KERNEL := and KERNEL_INITRAMFS := are correct - the tp-link eap615-wall is very similar just using NOR instead of NAND and with a single image
<neggles>
and tp-link's usual shenanigans we can ignore
<mangix>
from the fit patch?
<neggles>
yeah, it'll boot a FIT, it just has to be the bare FIT at the start of the partition
<neggles>
so for factory bootloader you'll need to decide how much to set aside for kernel, then split firmware and firmware_2 - like you already did for firmware
<neggles>
then if you want to ignore the alternate image bank, add a line to the sysupgrade script that does a `fw_setenv bootimage 1`
<neggles>
it's not super difficult to support booting from either / flashing to the alternate though, we've got scripts doing that for other devices
<mangix>
neggles: so the ethernet mac address is stored in devinfo. Instead of dealing with that, would it make sense to use ubootenv to store the mac address?
<neggles>
not really, i imagine it's at a fixed offset?
<mangix>
I think I'd need to get rid of lzma and fit lzma
<neggles>
kernel-bin | fit none $$(KDIR)/image-$$(firstword $$(DEVICE_DTS)).dtb
<neggles>
yeah
<neggles>
forgot about the extra lzma
<neggles>
it's allocating 32MiB for uncompressed kernels >:(
<mangix>
lolwut?
<mangix>
I find it strange that all other ramips devices use fit lzma though
<neggles>
it's a u-boot config option.
<neggles>
imo it's a u-boot bug.
<neggles>
but it's hardly their fault that vendor SDK kits / OEMs don't bother to actually learn how any of it works, and if your kernel image is <8MiB you never notice
<neggles>
lzma-loader could help you out here, or splitting initrd/rootfs into their own components of the FIT
<mangix>
the interesting part is, this limitation I seem to hit only with fit
<mangix>
oh
<neggles>
legacy image is self-decompressing
<mangix>
compilation failed
<neggles>
ah yeah KERNEL_SIZE
<neggles>
set that to 32768K for now
<mangix>
yeah I'm suspicious here
<mangix>
the other ramips devices seem to work find
<mangix>
*fine
<mangix>
image too big
<mangix>
yeah can't get this to work
<mangix>
time to abandon fit
Misanthropos has quit [Ping timeout: 480 seconds]
<mangix>
wonder if I should try flashing breed
<mangix>
gch981213: ping
mangix_ has joined #openwrt-devel
<mangix_>
back in production with the wrong mac address
<stintel>
neggles: it's just proprietary mtk stuff, there is bmt v2, bbt and nmbm
<stintel>
see target/linux/generic/files/drivers/mtd/nand/
<neggles>
fairo
robimarko has joined #openwrt-devel
<stintel>
also, I have 2 zr-2662, one of them shows it's initializing nmbm in bootloader output, the other doesn't, I suspect I nuked that part from the nand during my attempts to get the thing to boot
<mangix>
oh i see
mangix has quit [Remote host closed the connection]
<stintel>
also I don't have that BBT string in my mtd0 (bootloader), but having that string shouldn't necessarily mean the device uses BBT, I would suspect the bootloader can support it regardless of it being used
<neggles>
the gpl tarball for this thing is very complete h
<slh>
neggles: the good news would be ipq8072a (and not plain ipq8072, which would not have ath11k support and will probably never get any), but secure boot might still be enabled... other than that, have a look at https://github.com/robimarko/openwrt/tree/ipq807x-5.15
<robimarko>
Its probably IPQ8072A
<robimarko>
I dont think that there ever was v1 of anything else other than IPQ8074
mangix has joined #openwrt-devel
<neggles>
it is ipq8072a yes
<neggles>
but I don't have one :P
<neggles>
and I don't super wanna buy one, they don't even have 160mhz support
<neggles>
secure boot is enabled but trivial to disable
<neggles>
based on the brief poke around i had in a friend's one, it's the classic fw_setenv verify no
<robimarko>
What do you mean it doesnt have 160MHz?
<robimarko>
Thats weird, never seen qca8k switch on 100M uplink
<neggles>
have a boot log
<neggles>
it's not technically supported
<stintel>
I carry a patch for that
<neggles>
it's an AR8236
<robimarko>
Oh, thats a different thing
<neggles>
fun fact
<neggles>
the AR8236 and AR8327 have near-identical register maps
<neggles>
save for the lack of 1G config bits
<robimarko>
Yeah, that is how AR8327 got support in swconfig
<neggles>
i think the mistake i made here was i passed a phy-handle to eth0
<neggles>
so mvneta and qca8k are arguing over mdio stuff
<robimarko>
stintel: Oh, they actually got NAND working in 5.1.0 patch 1 release
<neggles>
for octeon ii or only octeon iii ?
<stintel>
do you have access to that source ?
<neggles>
i did manage to get it to detect the chip and read/write it, but the ecc was all broked
<stintel>
hmmm, I don't recall exactly what I had to do to mvneta to make it work on the oc200
<robimarko>
The familly is not listed, it just says: Added NAND driver support in linux kernel
<robimarko>
Yeah, I have Extranet acess
<neggles>
!
<neggles>
they wouldn't even give it to the company i work for despite us having a quite legitimate reason for it at the time :(
<robimarko>
Thats weird
<robimarko>
Extranet acess was way easier to get then any other NDA based stuff
<neggles>
they asked for the various company details for NDA reasons, i replied with same, heard nothing
<robimarko>
And unlike QCA and others its quite detailed
<neggles>
chased it up a few times, silence
<robimarko>
Thats weird, they have been granting stuff rather quickly
<neggles>
the doubly weird thing is if i go try to log in it says i have an account associated with my email
<neggles>
but the reset password email never arrives
<robimarko>
Yeah, cause they never approved the account
<robimarko>
I had a collegue with the same issue
<neggles>
also prevents me from opening another application
<neggles>
i've sent a dozen emails and the only replies i've had since last year are autoreplies saying one of the people i was emailing no longer works for marvell
<hurricos>
No, but then I don't have any access to 100G cards :^)
<neggles>
the 309 isn't going anywhere anytime soon
<neggles>
nor is the 317
<hurricos>
Yeah, Mikrotik gets my kudos for being consitent. It's just that I don't want to use their firmware ;)
<neggles>
hurricos: neither do i, but a 4x100G switch is also a 16x25G switch and 25G NICs are getting cheap
<hurricos>
err, what?
<neggles>
you can split a QSFP28 into 4x SFP28 with a DAC or a SR4 optic and an MTP breakout
<hurricos>
are you telling me there's some crazy kind of 100G QSFP
<hurricos>
...
<hurricos>
octopus. Wow, OK.
<neggles>
all 100G is QSFP28
<hurricos>
Well, I still don't need 25G.
<neggles>
unless it's part of 400G but shh
<hurricos>
:P
<neggles>
i have a CCR2004-1G-2XS-PCIe on the way
<neggles>
it's been delayed a month and a half though :(
<hurricos>
I've got one use-case for it
<hurricos>
hook fast, new, tiny-silicon crap to lots of spinning rust
<hurricos>
can't do it with anything but ethernet.
<hurricos>
at least nothing *cheap* other than ethernet.
<neggles>
what kind of fast new tiny silicon crap
<robimarko>
Edgecore EPS300 for those wanting 48x10G SFP+ with switchdev
<hurricos>
A Lab member is (for some reason) buying an M1 Max and is planning to leave it at the Lab
<hurricos>
I've promised not to destroy it, I probably will in the process of getting Linux on it though.
<neggles>
mac studio or laptop?
<hurricos>
Studio
<neggles>
cause asahi won't run on studio very well yet
<neggles>
and you can't destroy it
<hurricos>
Oh no?
<hurricos>
Oh no
<hurricos>
"yet"
<neggles>
well the devs have it running
<neggles>
it'll be "yeah this works" pretty soon
<hurricos>
No, they haven't even ordered it yet. Their work is buying it for them when they have their computer refresh up in July
<neggles>
half the peripherals are inaccessible as of yet
<neggles>
cause they're hanging off die 2
<hurricos>
Bah
<neggles>
but yeah those machines are effectively unbrickable as long as you're not insane enough to touch the 8mib SPI NOR
<hurricos>
uh
<neggles>
DFU-mode restore from any other mac
<hurricos>
oh.
<hurricos>
when you say touch ...
<neggles>
you can read it
<neggles>
just don't write to it
<hurricos>
you know, never mind. I'll just start browsing through OCP :rofl:
<hurricos>
OCP stuff on eBay.
<neggles>
there's nothing useful in there anyway
<hurricos>
The problem is that our build host is ancient and sucks power
<neggles>
and m1n1 hard write-locks it
<neggles>
even if you do nuke the SPI, apple can restore it, but that chip contains a number of machine-specific bits of caldata and certificate/crypto key
<neggles>
but there's just no reason at all to touch it, and if you don't you can *always* DFU restore
<neggles>
hmm, solidrun honeycomb lx2?
<hurricos>
Our problem is, we can't find a combination of cheap, poewr-efficient and able to access enough storage media (we have a minio instance people have come to depend on)
<hurricos>
pulling one socket and half the RAM out of the storage server drops the power consumption nearly in half, which is surprising given the number of disks
<hurricos>
(it's an R510)
<neggles>
oh god
<neggles>
what's it idle at?
<neggles>
300w?
<hurricos>
310.
<neggles>
replace it with a 720 or a 730 and you'll idle at under 100
<hurricos>
Fine in the winter.
<hurricos>
Really, now?
<neggles>
yes.
<neggles>
the 710 is westmere
<neggles>
720 is sandy/ivy
<neggles>
730 is haswell/broadwell
<hurricos>
as is the 510. I wasn't aware westmere was that much worse
<neggles>
it's half the performance for twice the power.
<hurricos>
my impression was that westmere-ep was half as awful as the previous gen :^)
<neggles>
11G poweredges all belong in ewaste.
<hurricos>
Lol
<neggles>
despite what r/homelab would have you believe.
<neggles>
actually
<neggles>
12 disks? how big?
<hurricos>
16 actual drives; 11 slots total for 3TB SAS HDDs; 10 of them are in the RAID10 array, I think we're using 7T of storage.
<hurricos>
then bcache on 2x NVMe drives in RAID1
<hurricos>
I should probably focus on the social problem at hand.
<hurricos>
Getting people to get their shit off of it.
<minimal>
hurricos: have you looked at minio alternatives after their mucking about its license?
<hurricos>
I haven't even touched it in a while, and that's sort of my problem
<minimal>
hurricos: ok. been meaning to look at seaweedfs as a S3-compatible alternative to minio
<hurricos>
It's why I was hacking on OpenWrt NASes for a while, because I could have just had the people hogging up space (incl. myself) come in with new drives of their own and bring stuff home
<neggles>
hurricos: R730XD, 12x IronWolf Pro 12TB drives, 2x1TB SATA SSDs, 2x E5-2650v3 with all power saving disabled and set to max performance https://i.imgur.com/GmTXfJ4.png
<hurricos>
JFC
<neggles>
the peak there is a backup copy job
<neggles>
if i switch it to a more energy efficient mode it drops 70w off
<neggles>
but it's in a DC and we're not hitting the 3kW we pay for so
<hurricos>
mind giving me an fio? :^)
<hurricos>
I can give you the exat run
<neggles>
it's a windows box
<neggles>
but i have windows fio so
<hurricos>
oh
<neggles>
the other DC has a 720XD with 12x8TB ironwolf pro and that one idles at 220
<neggles>
here is a fun fact: windows cannot count to 100 trillion
<hurricos>
neggles: those are all bare disks, aren't they?
<hurricos>
plain, spinning media? Yes, with 2G of cache, but still.
<neggles>
it's RAID6'd behind a PERC H730P but otherwise it's 12x12TB IronWolf Pro
<hurricos>
smh
<neggles>
the 720 in the other DC has a shittier raid controller and 4k clusters
<neggles>
lemme try dat
mattytap_ has joined #openwrt-devel
<neggles>
i expect badness
<hurricos>
For some reason, bcache collapses when asked to deal with 64K blocks, though it's probably bcache trying to merge writes because it thinks 10G is small enough
<hurricos>
it does absolutely no better with 50G though
<hurricos>
Yep, it's frantically trying to merge writes that are not mergeable. 4K averages 6K iops, 64K averages under 1500. My SSDs are probably also at fault, they're nothing enterprise
<hurricos>
WDC PC SN720 ... oh, wait, these are out of laptops.
felix_ has joined #openwrt-devel
mattytap has quit [Read error: Connection reset by peer]
<neggles>
there's also the weird ultra-long 1U 16x3.5 boxes
<hurricos>
It's only 7TB!
<neggles>
also if you want fast switch that's cheap and low-power
<hurricos>
That, I do
<neggles>
mellanox SX6012/6018/6036
<hurricos>
Oh, those ah
<neggles>
SX6012 = 12x40G with breakout, full layer 3, idles at 45w
<hurricos>
I have a Linux tree for thoes somewhere don't I?
<hurricos>
Yes, they use P2020 for management
<hurricos>
let me double check
<neggles>
yeah but switchx drivers
<neggles>
i have a bundle you can use to flash them with the latest mlnx-os for them and apply a license key with ALL THE FEATURES including the secret 'get root console' feature key
<hurricos>
Oh, I recently rm rf'd that tree while cleaning up
<hurricos>
:(
<hurricos>
lol
<neggles>
eh they're pretty bog-standard fsl with u-boot on the mgmt board side.
<hurricos>
You say "cheap and low power", but this is $1K.
<hurricos>
I suppose a good reason not to go with OCP is that I can actually get QSFP
<neggles>
they'll do 56GbE with ConnectX-3 Pro ENs as well
<neggles>
it's unreliable though and needs fancy expensive mellanox DACs
<hurricos>
"I dunno, does the switch support DSA?"
<hurricos>
:^)
<hurricos>
JOKE.
<hurricos>
joke.
<neggles>
honestly? maybe
<neggles>
i know Spectrum does
<hurricos>
It doesn't, unless said support has never been mentioned on a kernel mailing list
<hurricos>
ignal
<neggles>
probably not, no
<neggles>
Spectrum has full SONiC support at least
<robimarko>
Only Prestera, Spectrum and Sparx-5 have upstream switchdev drivers
<hurricos>
Sparx-5
<hurricos>
Ah, I recall that name
<neggles>
also i would suggest making a $200 offer on an 18-port https://www.ebay.com/itm/274825274073 rather than the 36 just cause they're quieter and a bit lower power.
<robimarko>
Sparx-5 is cool cause registers and full datasheet are public
<hurricos>
I also just realized this is the wrong IRC channel.
<neggles>
shall we move to the other one
<neggles>
or another one
<hurricos>
I have no idea which that would be :rofl:
<neggles>
fair. but yeah that cable turns a QSFP+ on a switch port into 4xSFP+. they also come in AOC and "an optic" forms.
<neggles>
this does *not* work with a NIC. only a switch.
<hurricos>
Right
<neggles>
the mellanox connectx VPI NICs support IB and Eth at the same time, the connectx EN are ethernet only, switch does both with a license key. the license key generation secret is fixed/static across all SwitchX and Spectrum switches.
<hurricos>
I think part of my problem is figuring out how to network this with anything we've got. With SFP+ ports, it's easy -- 1G SFP DACs which go straight into a ZyXEL or (probably) our HP PoE switch
<neggles>
you can drop a QSA into it and turn a 40G into a 10G which you can then drop a 10G-T transceiver into, or a 1/10G optic
<hurricos>
Whence my problem
<hurricos>
why not just a 10G switch? :^)
<neggles>
well yeah that's what i do :P
<neggles>
breakout cable into 4x10G on my 1G switch
<neggles>
pro tip if you replace the fans: they use a horrifically nonstandard pinout, and if you miswire it and hook the fan's ground wire to the tacho output pin, you'll blow out one of the i2c multiplexers and kill half the ports.
<hurricos>
speaking from experience
<neggles>
an F for my first SX6012.
<neggles>
annoyingly the only thing that's actually damaged is the i2c mux - it can't read the SFP module ID EEPROMs so no link.
<neggles>
if I can find an SX1012 (unmanaged IB-only version) I can drop the management COM from this one into it and magically it becomes a full-function SX6012 - the 1012 is just a 6012 with no mgmt COM
<neggles>
they used standard 4-pin molex KK254 headers... but the pinout is something like +V GND PWM TACH
<neggles>
jerks
<neggles>
anyway yeah. mine idles at 25w with noctuas in it
cyrozap has quit [Ping timeout: 480 seconds]
<neggles>
full line-rate L3, ipv4, ipv6, BGP, IS-IS even I think? OSPF of course, blah blah
<neggles>
and DCB for RoCEv1/v2.
<neggles>
and it is 1am so i must sleep, but have fun :P
cyrozap has joined #openwrt-devel
<hurricos>
thanks for the braindump :D
<neggles>
anytime :D I lied though my maybe-fixed oc200 image is built so lets see if i can haz dsa
<neggles>
nope. and now when it initializes ttyMV0 I lose serial console???
<neggles>
ok this is a tomorrow problem
<hurricos>
good night, neggles :^)
<neggles>
g'night :)
felix_ is now known as felix
dedeckeh has quit [Remote host closed the connection]
<mangix>
Tapper: kernel 5.15 is a bit special. ksmbd is part of linux now. The out of tree module should not be used.
<Tapper>
mangix So what do I need to do?
<Tapper>
Remove the packages in make menuconfig?
<Tapper>
Will luci-app-ksmbd work?
<Tapper>
mangix If it's all fucked up for now I can switch back to k5.10 for now.
<mangix>
yes it is messed up currently.
<mangix>
in multiple ways
valku has quit [Quit: valku]
<olmari>
..to history... I've never really thought of using openwrt on fileserver... or was that talk about osme backbone switching?
<Tapper>
mangix I am just going back to k5.10 then for now and see if ksmbd works.
Tapper1 has joined #openwrt-devel
Tapper has quit [Read error: Connection reset by peer]
<Tapper1>
mangix I flashed back to k5.10 but luci-app-ksmbd sstill not showing up in luci
<mangix>
what are your versions of ksmbd and ksmbd-tools?
<mangix>
neggles: didn't work
bluew has joined #openwrt-devel
dvn has quit [Quit: bye]
dvn has joined #openwrt-devel
Movedtomkg20001mkg20001io[m] has joined #openwrt-devel
mkg20001 has joined #openwrt-devel
Movedtomkg20001mkg20001io[m] has left #openwrt-devel [#openwrt-devel]
Movedtomkg20001mkg20001io[m] has joined #openwrt-devel
<Movedtomkg20001mkg20001io[m]>
Hi, I've set CONFIG_DEBUG=y and my packages still get stripped during build. Where did I fuck up?
mattytap_ has joined #openwrt-devel
bluew has quit [Read error: Connection reset by peer]
bluew has joined #openwrt-devel
mattytap__ has quit [Ping timeout: 480 seconds]
<Grommish>
Go to Global | Toolchain setting I believe and turn Strip'ing off
<Grommish>
Might be in Advanced, I can't check at the moment
<Tapper1>
mangix ksmbd-server - 3.4.4-1
<Tapper1>
ksmbd-utils - 3.4.4-1
<Tapper1>
That's from latest master.
srslypascal has quit [Remote host closed the connection]
srslypascal has joined #openwrt-devel
xdarklight has quit [Remote host closed the connection]
xdarklight has joined #openwrt-devel
digitalcircuit has quit [Remote host closed the connection]
Rondom has quit [Remote host closed the connection]
digitalcircuit has joined #openwrt-devel
enyc has quit [Remote host closed the connection]
Rondom has joined #openwrt-devel
<mkg20001>
Grommish k, thx. that did it. it sets CONFIG_NO_STRIP=y
<Grommish>
mkg20001: the CONFIG_DEBUG sets -ggdb and maybe some other things.. if you have a specific package youa re trying to debug, you can add a TARGET_CFLAGS+=-ggdb3 to force it
dansan has quit [Ping timeout: 480 seconds]
mangix_ has joined #openwrt-devel
Tapper1 has quit [Ping timeout: 480 seconds]
mirko has joined #openwrt-devel
dansan has joined #openwrt-devel
mangix has quit [Ping timeout: 480 seconds]
mangix_ has quit [Read error: Connection reset by peer]
mangix has joined #openwrt-devel
PtitGNU has quit [Quit: No Ping reply in 180 seconds.]