So I got my xg85 and have installed openwrt to it. I like it it's fast and is doing 250 down and 25 up SQM with out braking a swet.
One thing tho on the wiki for it it says to use the efi file to flash it, but it would not boot so I used the squashfs-combined.img.gz and it booted up just fine. Any one know why this is and what's going on? Should I be using the efi file or is it ok to stick with it how it is now?
it's a BIOS thing, could be different revision, or outdated on the one you got.
I haven't used EFI file on neither SG-105 nor SG-135. You may also want to extend the root partition on your XG-85 to all of the internal SSD.
1 Like
Hi I am not going to extend the root partition. Not yet anyway. I don't want to mess up sysupgrading and I don't install that many packages anyway. Thanks for letting me know about efi. There is not mutch on google on just what it is and why you would want to use it. Just things about old bios or uefi. I was digging because it says to use the efi file for flashing on the wiki.
I don't have the cable to find out what bios I have on my xg85 yet. I am going try and pick one up in a week or 2. Then If it's a verry old bios I mite flash back to the latest stock SW and then update the FW package. Then flash back to OpenWrt. I do know that there is at leste 3 bioses out there for the rev1 which I have.
Does it really matter...?
To me yes. I want to know all the things about my new box. That's just the way I role!
New(er) BIOSes could make your CPU run slower, due to the intel bugs discovered a couple of years ago.
Not really, if you get intel-microcode via a kernel upgrade or opkg doesn't really make a difference (and it's needed either way). The meltdown/ spectre and friends mitigations do cause significant slowdowns though, especially (but not limited to) interactive 'snappiness'.
that's what I was referring to ... 5 - 30% performance hit, depending on what the CPU's doing.
In my logs from the Kernel it says that I have the bios from 2017 and I think that is the latest anyway.
I'm pretty sure I have EFI working properly on an SG-135 and I didn't have to perform any kind of heroics to get it working. Please let me know if I can poke at anything for you.
root@sophos:~# grep name /tmp/board.json
"name": "Sophos SG-135r1"
root@sophos:~# fdisk -l /dev/sda
Disk /dev/sda: 447.13 GiB, 480103981056 bytes, 937703088 sectors
Disk model: ADATA SU635
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 2785922E-FF64-67DB-D7C1-D777E6133600
Device Start End Sectors Size Type
/dev/sda1 512 33279 32768 16M EFI System
/dev/sda2 33792 1133567 1099776 537M Microsoft basic data
/dev/sda3 1134592 2234367 1099776 537M Linux filesystem
/dev/sda4 2234368 937703054 935468687 446.1G Linux filesystem
/dev/sda128 34 511 478 239K BIOS boot
Partition table entries are not in disk order.
On a somewhat unrelated note, it looks like the dd method of install leaves the root partition type "Microsoft basic data" - probably safe to change it? Safer to leave it?
Edited to add, from logread:
Mon Nov 14 10:00:09 2022 kern.info kernel: [ 0.000000] SMBIOS 2.8 present.
Mon Nov 14 10:00:09 2022 kern.info kernel: [ 0.000000] DMI: Sophos SG/To be filled by O.E.M., BIOS 5.6.5 04/05/2017
I've only seen the set-partition-type operation associated with wiping the drive
I'm with r7800 on 500/300 Mbit and don't see issues. not using on top speeds most of the time and not having many devices, but still. what is the problem at your end? may be you have many apps on the router?
1 Like
Hi there mate. You cant get thoes speeds with SQM.
Hello Ramon,
Should those commands be pasted in System > Startup > Local Startup?
Thanks.
Yes, they should.
1 Like
that is true, but I don't need SQM with these max speeds
Yes, although you can try them without putting them there, but they won't survive a reboot then.
?
Where/how (instructions) would I enter those command please?
Paste them in cli, using ssh.