aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/x86/base-files/etc
Commit message (Collapse)AuthorAgeFilesLines
* base-files: x86 fix 01_leds Syntax errorStan Grishin2023-05-291-1/+1
| | | | | | | | | | | | Cezary Jackiewicz reported: | Syntax error in line /etc/board.d/01_leds#L22 - missing "\" Fixes: c191c2d46f00 ("x86: base-files add support for Sophos 135r3/135r3w") Reported-by: Cezary Jackiewicz <cezary@eko.one.pl> Signed-off-by: Stan Grishin <stangri@melmac.ca> (buffed up commit message) Signed-off-by: Christian Lamparter <chunkeey@gmail.com> (cherry picked from commit 4b8b2f4f978d6df586dd7ce4dcc3e1286b93bd48)
* x86: base-files add support for Sophos 135r3/135r3wStan Grishin2023-05-202-0/+11
| | | | | | | | | | | | | | The Sophos SG/XG-135 revision 3 has odd numbering of eth ports where the WAN port (as marked on the case) is: `eth6` and `eth0`, `eth1`, `eth2`, `eth3`, `eth5`, `eth7`, `eth8` are LAN ports. Port `eth4` seems to be the SFP port. Also add the missing LED definition for supported Sophos devices. Original discussion at: https://forum.openwrt.org/t/openwrt-on-revision-3-of-sophos-desktop-appliances/152912 Signed-off-by: Stan Grishin <stangri@melmac.ca>
* x86: add Barracuda Networks F12 interfacesTomasz Maciej Nowak2023-02-031-0/+8
| | | | | | | | | | | | | | | | | | | | Match interface numbers with printed numbers on device enclosure and assign first port as WAN interface. Notes Serial console is available through RJ-45 port with Cisco pinout baud: 19200, parity: none, flow control: none The device is setup with UEFI. To enter setup hold DEL or ESC key on boot. Default UEFI Administrator password is: bcndk1 For users using graphics IC it's advisable to disable display with: i915.disable_display=1 appending to kernel command line inside bootloader, to save about 0.5-0.6W energy on idle. For users not using graphics IC, disable it in UEFI, this will save about 1.5W energy on idle. Pins marked CN19 are ATX power On/Off button. Signed-off-by: Tomasz Maciej Nowak <tmn505@gmail.com>
* x86: Add APU6 board support for startup detectionPhilip Prindeville2023-01-112-1/+7
| | | | | | | The APU6 is similar to the APU4 except for eth0 having an SFP cage instead of RJ45. Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
* x86: setup netdev paths for MX100Martin Kennedy2022-09-101-1/+13
| | | | | | | | | | | | | | | | The Meraki MX100 has ten 1000BASE-T and 2 SFP ethernet ports through 3, 4-port PCIe devices. The default enumeration of these network devices' names does not correspond to their labeling. Fix this by explicitly naming the devices, mapping against their sysfs path. Note that these default network names can only be up to 8 characters, because we can have up to 8 characters of modifiers (e.g. ^br-, .4096$), and because the maximum network interface name is 16 characters long. Signed-off-by: Martin Kennedy <hurricos@gmail.com> [lowercase subject] Signed-off-by: Paul Spooren <mail@aparcar.org>
* x86: Add support for Sophos XG 85 and XG 86 devicesRaylynn Knight2022-03-261-1/+2
| | | | | | | | | | | | This commit builds on previous efforts to add support for Sophos devices. * Add support for Sophos XG 85 with/without wireless * Add support for Sophos XG 86 with/without wireless Tested on Sophos XG 85w rev1 and XG 86 rev 1 Signed-off-by: Raylynn Knight <rayknight@me.com>
* gpio-cdev: re-add nu801 userspace driverChris Blake2022-03-251-1/+1
| | | | | | | | | | | | | | | | | | | | | This reverts commit 80b7a8a7f5a0a88fde6dd19f097df4d7cac9ff04. Now that 5.10 is the default kernel for all platforms, we can bring back the NU801 userspace driver for platforms that rely on it. Currently it's used on the MX100 x86_64 target, but other Meraki platforms use this controller. Note that we also now change how we load nu801. The way we did this previously with procd worked, but it meant it didn't load until everything was up and working. To fix this, let's call nu801 from boot and re-trigger the preinit blink sequence. Since nu801 runs as a daemon this is now something we can do. Signed-off-by: Chris Blake <chrisrblake93@gmail.com> (removed empty line, currently only MX100 uses it so: @TARGET_x86) Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* x86: fix support for Sophos SG/XG wireless productsRaylynn Knight2022-02-191-8/+8
| | | | | | | | | | Correct typo that caused network interfaces for Sophos SG/XG wireless devices to not be configured properly. Tested on Sophos SG 135wr2, Sophos XG 125wr2 and Sophos SG 105wr1 Signed-off-by: Raylynn Knight <rayknight@me.com>
* x86: add/improve support for Sophos SG/XG productsRaylynn Knight2021-12-291-1/+11
| | | | | | | | * Add support for Sophos SG/XG-115 r1, r2 with/without wireless * Add support for Sophos SG/XG-125 r1, r2 with/without wireless * Add wireless support for SG/XG-105 Signed-off-by: Raylynn Knight <rayknight@me.com>
* x86: add/improve support for Sophos SG/XG productsStan Grishin2021-12-111-1/+8
| | | | | | | | | * Better product ID for Sophos SG/XG-105 models * Add support for Sophos SG/XG-135 r1, r2 with/without wireless Signed-off-by: Stan Grishin <stangri@melmac.ca> [Changed subject to x86 - probably eaten somewhere, the PR had it] Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* Revert "gpio-cdev: add nu801 userspace driver"Christian Lamparter2021-10-101-1/+1
| | | | | | | | | | | This reverts commit f536f5ebddd9c532a08ac4a9be3ef0c02f7bfeb8. As Hauke commented, this causes builder failures on 5.4 kernels. This revert includes changes to the mx100 kernel modules dependency as well as the uci led definitions. Tested-by: Chris Blake <chrisrblake93@gmail.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* x86: add support for Meraki MX100Chris Blake2021-10-102-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit will add support for the Meraki MX100 in OpenWRT. Specs: * CPU: Intel Xeon E3-1200 Series 1.5GHz 2C/4T * Memory: 4GB DDR3 1600 ECC * Storage: 1GB USB NAND, 1TB SATA HDD * Wireless: None * Wired: 10x 1Gb RJ45, 2x 1Gb SFP UART: The UART header is named CONN11 and is found in the center of the mainboard. The pinout from Pin 1 (marked with a black triangle) to pin 4 is below: Pin 1: VCC Pin 2: TX Pin 3: RX Pin 4: GND Note that VCC is not required for UART on this device. Booting: 1. Flash/burn one of the images from this repo to a flash drive. 2. Take the top off the MX100, and unplug the SATA cable from the HDD. 3. Hook up UART to the MX100, plug in the USB drive, and then power up the device. 4. At the BIOS prompt, quickly press F7 and then scroll to the Save & Exit tab. 5. Scroll down to Boot Override, and select the UEFI entry for your jumpdrive. Note: UEFI booting will fail if the SATA cable for the HDD is plugged in. The issue is explained under the Flashing instructions. Flashing: 1. Ensure the MX100 is powered down, and not plugged into power. 2. Take the top off the MX100, and unplug the SATA cable from the HDD. 3. Using the Mini USB female port found by the SATA port on the motherboard, flash one of the images to the system. Example: `dd if=image of=/dev/sdb conv=fdatasync` where sdb is the USB device for the MX100's NAND. 4. Unplug the Mini USB, hook up UART to the MX100, and then power up the device. 5. At the BIOS prompt, quickly press F7 and then scroll to the Boot tab. 6. Change the boot order and set UEFI: USB DISK 2.0 as first, and USB DISK 2.0 as second. Disable the other boot options. 7. Go to Save & Exit, and then select Save Changes and Reset Note that OpenWRT will fail to boot in UEFI mode when the SATA hard drive is plugged in. To fix this, boot with the SATA disk unplugged and then run the following command: `sed -i "s|hd0,gpt1|hd1,gpt1|g" boot/grub/grub.cfg` Once the above is ran, OpenWRT will boot when the HDD is plugged into SATA. The reason this happens is the UEFI implementation for the MX100 will always set anything on SATA to HD0 instead of the onboard USB storage, so we have to accomidate it since OpenWRT's GRUB does not support detecting a boot disk via UUID. Signed-off-by: Chris Blake <chrisrblake93@gmail.com>
* x86: add upgrade support to diag.shChris Blake2021-06-101-0/+4
| | | | | | | | | Similar to how this is done in the diag.sh found in the base-files package, we should blink our status LED (if we have one) during the upgrade process. This follows the same blink pattern as seen at ./package/base-files/files/etc/diag.sh#L36 Signed-off-by: Chris Blake <chrisrblake93@gmail.com>
* x86: add Roqos Core RC10 ethernet interfacesTomasz Maciej Nowak2021-06-061-0/+3
| | | | | | | | | | | | | | | | | | | eth0 -> single NIC (i211at) eth1 -> single NIC (i211at) -> 4-port unmanaged switch (BCM53125U) Notes UART is exposed on J4 connector, pinout starting from pin marked 1: 1. GND, 2. NC?, 3. NC?, 4. RX, 5. TX, 6. NC? baud: 115200, parity: none, flow control: none The board is setup by coreboot with UEFI. To enter setup screen hold ESC key on boot. The 5-LED multicolor matrix is attached on first I2C device named "Synopsys DesignWare I2C adapter" at address 0x60. Controlling values are stored in /opt/roqos/etc/rcLED.conf of original firmware. Remember to backup the original firmware, there are no downloadable copies. Signed-off-by: Tomasz Maciej Nowak <tmn505@gmail.com>
* x86/base-files: add support for Sophos SG/XG-105Stan Grishin2021-03-261-0/+3
| | | | | | | This adds detection of the Sophos SG-105 and Sophos XG-105 models and assignment of ethernet ports these models have to LAN/WAN. Signed-off-by: Stan Grishin <stangri@melmac.net>
* treewide: remove execute bit and shebang from board.d filesAdrian Schmutzler2021-03-062-2/+0
| | | | | | | | | | | | | | | | So far, board.d files were having execute bit set and contained a shebang. However, they are just sourced in board_detect, with an apparantly unnecessary check for execute permission beforehand. Replace this check by one for existance and make the board.d files "normal" files, as would be expected in /etc anyway. Note: This removes an apparantly unused '#!/bin/sh /etc/rc.common' in target/linux/bcm47xx/base-files/etc/board.d/01_network Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* x86: add led driver for PC Engines APU1Andreas Eberlein2021-02-202-5/+5
| | | | | | | | | This driver adds the LED support for the PC Engines APU1. This integrates the Linux kernel driver and includes a patch to support newer firmware versions. Also the default LED configuration is updated to use the correct devices. Signed-off-by: Andreas Eberlein <foodeas@aeberlein.de>
* x86: fix missing led variable warning during bootPetr Štetiar2019-06-251-0/+2
| | | | | | | | Fixes following warning during the boot: WARNING: Variable 'led' does not exist or is not an array/object Signed-off-by: Petr Štetiar <ynezz@true.cz>
* Revert "base-files: add console to inittab"Alexander Couzens2019-05-251-1/+0
| | | | | | | This reverts commit cde52cb4866fe8cf4a19bb2bb32ff7802e542e19. When using OpenWrt in qemu, the shell is unsuable Signed-off-by: Alexander Couzens <lynxis@fe80.eu>
* base-files: add console to inittabPaul Spooren2019-05-211-0/+1
| | | | | | | | | | | When running OpenWrt inside an LXC container no shell is opend as LXC defaults to a virtual /dev/console. This patch allows to enter a shell after starting the container via `lxc-start`, without it is only posible to access a shell on tty1 via `lxc-console`. Signed-off-by: Paul Spooren <mail@aparcar.org>
* x86: Add APU3 reference to x86 board.dKristian Evensen2018-05-182-2/+2
| | | | | | | | | | | There is a new APU-model available, APU3. The device is configured in the same way as the APU1 and APU2, so the same LED/network setup can be used. I considered changing the case to pc-engines-apu*, but I chose to follow the existing pattern and add the full board name. Signed-off-by: Kristian Evensen <kristian.evensen@gmail.com>
* treewide: use only board_name function to get nameMathias Kresin2017-07-152-6/+2
| | | | | | | | | | | | Do not parse /tmp/sysinfo/board_name, /proc/cpuinfo or the device tree compatible string directly. Always use the board_name function to get the board name. The admswconfig package still reads /proc/cpuinfo directly. The code looks somehow broken and the whole adm5120 which uses this package looks unmaintained. Leave it as it is for now. Signed-off-by: Mathias Kresin <dev@kresin.me>
* Add missing APU1 reference to x86 board.dKristian Evensen2017-06-062-2/+2
| | | | | | | | | | | | x86 board.d only contains a case for the APU2, not the APU1. This causes, for example, network configuration not to be created correctly. Even though the APU1 seems to reaching EOL, there a still a lot of them out there. The APU1 and APU2 is configured in the same way and this patch should also be considered for stable, as the error also exists there. Signed-off-by: Kristian Evensen <kristian.evensen@gmail.com>
* x86: Add board configs for the PC Engines APU2Chris Blake2017-02-152-0/+8
| | | | | | | | This adds the default LED and network settings for the PC Engines APU2 when running under the x86 target. [dwmw2: Change Ethernet port setup] Signed-off-by: Chris Blake <chrisrblake93@gmail.com>
* x86: Enable DIAG LED on GeosDavid Woodhouse2017-02-152-1/+79
| | | | | | | | | Based on a patch from Chris Blake <chrisrblake93@gmail.com>, except let's do it by using the LED configuration instead of hard-coding it for each board type. And try using /bin/board_detect to do the default behaviour, on the first boot where the config hasn't yet been generated. Signed-off-by: David Woodhouse <dwmw2@infradead.org>
* x86: Move Traverse Geos configs into x86 base-filesChris Blake2017-02-152-0/+45
| | | | | | | | | | This change moves the files in 657418d to the root of the x86 target. This is done in preperation for adding more devices under other subtargets. CC: David Woodhouse <dwmw2@infradead.org> Signed-off-by: Chris Blake <chrisrblake93@gmail.com>
* x86/generic: add xen DomU supportFelix Fietkau2017-01-161-0/+1
| | | | | | Copy the relevant config options from the xen_domu subtarget Signed-off-by: Felix Fietkau <nbd@nbd.name>
* image / basefiles: make console password configurableJohn Crispin2016-04-181-2/+2
| | | | | Signed-off-by: Daniel Dickinson <openwrt@daniel.thecshore.com> Signed-off-by: John Crispin <john@phrozen.org>
* x86: remove redundant default network configFelix Fietkau2016-01-281-26/+0
| | | | | | Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 48530
* x86: remove old soekris config hacks, install a more appropriate default ↵Felix Fietkau2014-10-123-37/+7
| | | | | | | | /etc/config/network with lan+wan Signed-off-by: Felix Fietkau <nbd@openwrt.org> SVN-Revision: 42888
* network: Unbind DHCPv6 from underlying interfacesSteven Barth2014-10-081-1/+1
| | | | | | | | | This allows IPv6 to set up without IPv4 being up thus IPv6-only or IPv6+DS-Lite working with the default config. Signed-off-by: Steven Barth <steven@midlink.org> SVN-Revision: 42848
* x86: change /dev/console to tty to fix job controlJohn Crispin2013-08-041-0/+4
| | | | | | | | | | | | Job control is turned off because it cannot obtain controlling terminal on /dev/console, so it is impossible to do any job control operation behind real x86 device (keyboard+monitor or virtualized). This patch switches /dev/console to tty devices for ash on x86 generic target. Signed-off-by: Jiri Slachta <slachta@cesnet.cz> SVN-Revision: 37693
* Change default IPv6 config to enable DHCPv6-PDSteven Barth2013-04-221-1/+1
| | | | SVN-Revision: 36384
* Adapt default network configuration for IPv6Steven Barth2013-04-091-0/+8
| | | | SVN-Revision: 36278
* x86/soekris: Add defconfig for soekris net4801 and net4826Felix Fietkau2011-01-263-0/+48
| | | | | | | | | Add default config file for net4801 and 4826 and initial script to copy config file like it is done for other platforms. Patch from: kentarou matsuyama <matsuyama@thinktube.com> SVN-Revision: 25103
* add preinit modularization work by Daniel Dickinson (cshore)Felix Fietkau2010-01-251-2/+0
| | | | SVN-Revision: 19331
* silence a bogus preinit messageFelix Fietkau2007-10-241-1/+1
| | | | SVN-Revision: 9429
* get rid of per-profile base-filesGabor Juhos2007-09-291-0/+2
SVN-Revision: 9069
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-10 10:45:22 +0000