/tech/ - Does anyone know how to wholly replace a syslinux boot with grub2? I'm trying to load some squashfs read only live usbs but I need grub so I can pass some grub commands before the kernel loads. syslinux is A SHIT and there are no useful modules like in g

Name
Subject
E-mail
Message	Max message length: 6144
Files	Drag files to upload or click here to select them Maximum 5 files / Maximum size: 20.00 MB

Spoiler images
Password	(used to delete files and postings)
Use bypass

Anonymous 02/04/2020 (Tue) 02:37:44 No.1478

Does anyone know how to wholly replace a syslinux boot with grub2? I'm trying to load some squashfs read only live usbs but I need grub so I can pass some grub commands before the kernel loads. syslinux is A SHIT and there are no useful modules like in grub. The live images have the kernel separate from the system rootfs, and I have no problem targeting the kernel in grub, and the initrd seems useless from what I could see from the init script in it, like I could just pass flags to the kernel directly instead of fucking around with a bunch of useless if statement busybox bullshit. I managed to get it to work for one system, with no initrd and everything, but I can't reproduce it in a second system. Why is everything a fucking script and all the real commands undocumented. Anyway, I've been working at it for ages and tomorrow I'll just try the hail mary of passing grub-install to a drive with the live image written and see if it overwrites the syslinux bullshit, but I was hoping anons here might have a better idea. Also, what are the odds of getting a working system from source off github? I've never done a custom build, but I need to because I want to include some legacy drivers as well as grub. Everything seems to be automagically made with bootroot and docker but it doesn't really tell me how to build a custom version. for clarity, I have no problem getting to grub and booting the efi files, but the kernel can't find the squashfs root even though I pass the flags, so something's fucking up in my /boot/grub/grub.cfg, and yes I'm writing it by hand because I'm autistic like that.

sage Anonymous 02/04/2020 (Tue) 05:15:21 No.1480

What is the full purpose of what you're trying to do ? Make a USB with multiple live CDs ? Either way, if you're getting to grub, you can pop into grub's terminal thing and poke around to see what it can see. I'm 80% sure you're using relative paths(/dev/sda1 or hd0 or whatever) for telling it where the files are and you should use device IDs. That would be one reason why it works on one machine and not another.

Anonymous 02/04/2020 (Tue) 06:00:47 No.1481

this is now the Does anyone know? thread Does anyone know how I would go about pairing a hidden bluetooth device to my computer? for some dumb reason certain bootleg console controllers hide themselves from everything other than the console, not even official controllers seem to do this

Anonymous 02/07/2020 (Fri) 18:10:43 No.1520

>>1480 I'm trying to boot a kernel which uses a squashfs filesystem. I succeeded by just passing the right kernel arguments by hand in grub but there were various issues like certain kernels didn't work unless they were specifically passed partition labels as opposed to /dev/sdXX or UUIDs. Effectively I'm trying to do something which is further than my competency, but if it was properly documented there wouldn't be an issue. I've been around long enough to know that almost any system has a dozen or half dozen undocumented bugs that the community is aware of, but the assholes never bother to mention it unless directly asked, and sometimes not even then.

Anonymous 02/07/2020 (Fri) 20:02:50 No.1521

>>1520 both grub efi and grub legacy setup are very different to each other. Make sure you don't mix up between these two setup.

Anonymous 02/11/2020 (Tue) 01:25:20 No.1589

>>1521 I'm using EFI exclusively, and it looks like the syslinux install uses some weird cut-down version of grub anyway, but it just didn't have the modules. I've got it sorted out now, but it was a pain figuring out which kernel parameters to pass. Things really aren't fully documented, lots of switches and kernel options that are never mentioned at GNU or anywhere else.

Anonymous 02/11/2020 (Tue) 19:04:49 No.1599

>>1481 I'm not sure if anyone has a bluetooth sniffer but it's probably as simple as directly targeting the MAC address. >hcitool - This utility can be used for command-line scanning and obtaining the ever-important MAC address when connecting with other tools. >gatttool - Included with the Bluez library, this is a great tool for honing in on specific values of a General Attribute, or GATT characteristic as defined in the Bluetooth specification. >ubertooth-btle - Included with the Ubertooth software; out of all of the Bluetooth tools, this one will be used quite a lot. While hopping and chasing through the Bluetooth spectrum, you’ll occasionally get a complete chunk of Bluetooth traffic while sniffing with this utility. Don’t let the BTLE part of this fool you - all pairing takes place in Bluetooth 4.x in the low energy realm, so if nothing else, this is a great way to get a sniffer trace of the pairing process. Just be prepared for multiple tries and some patience, and when completed, you will have a nice pcap-formatted output file to analyze.