load routerOS Drivers from USB drive in linux - linux

I'm trying to install routerOS(Mikrotik) from bootable USB drive on my PC.
it boots from USB at first and loads the Linux Kernel.
after detecting the H.D.D it requests me to insert the CD-ROM disk to installing the DRIVERS.
but the drivers are in the USB flash.
i opened the syslinux.cfg and isolinux.cfg files:
default system
label system
kernel linux
append load_ramdisk=1 initrd=initrd.rgz root=/dev/ram0
i'm thinking that the problem is here. it requests to load from CD-ROM.
how can i tell it to load the drivers from USB Flash?
** i've not worked with Linux.

In RouterOS you have 2 method of X86 installs.
CD-ROM ( not USB )
NetInstall
If your BIOS supports net boot and you have a Windows to run NetInstall, try with Mikoritk NetInstall

Related

PPP over ttyUSB device

i have up ruining machine with Slackware 14.02 kernel 4.4.131
i want to compile my own kernel in to the machine, how ever i don't have the kernel .config file, so i'm using generic one from the Slackware website.
after the kernel boot i'm stack on the pppd proces that the device is runing, with the error massage:
/usr/sbin/pppd: unrecognized option 'ttyUSB2'
pppd version 2.4.7
what seem that the pppd cannot open terminal over the ttyUSB2 connection. and that why i don't have keyboard. however at the builtin kernel the pppd is establishing connect and things working well
i tried to enable all the cnonfig of the ppp at the .config file
CONFIG_PPP=y
CONFIG_PPP_BSDCOMP=y
CONFIG_PPP_DEFLATE=y
CONFIG_PPP_FILTER=y
CONFIG_PPP_MPPE=m
CONFIG_PPP_MULTILINK=y
CONFIG_PPPOATM=m
CONFIG_PPPOE=y
CONFIG_PPTP=m
CONFIG_PPPOL2TP=m
CONFIG_PPP_ASYNC=y
CONFIG_PPP_SYNC_TTY=y
Thanks

How to load Yocto generated U-boot binaries to t1042d4rdb board

I created linux and U-boot images for NXP t1042d4rdb board using Yocto (using bitbake fsl-image-full command) on Ubuntu 16.04.6 . In my "yocto sdk directory"/"build directory"/tmp/deploy/images/t1042d4rdb directory, I have linux images and many binaries for u-boot (like u-boot.bin, u-boot-sdcard.bin, u-boot-nor.bin, u-boot-spi.bin ....).
you can see my /tmp/deploy/images/t1042d4rdb file here
I attached my UART serial converter to /dev/ttyUSB0 using minicom and wrote this command (found it on nxp forum)
"sudo dd if=u-boot.bin of=/dev/ttyUSB0 obs=4066 seek=1; sync"
nothing happened. Console messages from "dmesg" command
[ 4103.366033] ftdi_sio 3-4:1.0: FTDI USB Serial Device converter detected
[ 4103.366053] usb 3-4: Detected FT232RL
[ 4103.370147] usb 3-4: FTDI USB Serial Device converter now attached to ttyUSB
I am new at Yocto and U-boot. My question is, how can I load U-boot linux binaries to my board. Thanks for answers and any other suggestions.
Firstly, you cannot write serial port device (ttyUSB0) directly with dd despite it is not show any error your written data probably disappears because ttyUSB0 device just a communication device.
On Yocto build directory (tmp/deploy/images) you can probably find an .sdcard image file or an .wic image which is combined Linux kernel, U-Boot and Rootfs images. So you need to write this image to related block device that you will use as boot device. In this case you can write this image like this; "dd if= of=/dev/your-sd-card-device bs=1M sync".
I hope it will help your problem.

Difference between wic and hddimg format in yocto

I have generated a core-image-minimal image for my Intel board in Yocto.
Looking into tmp/deploy/images folder they are many images.
I flashed *.wic image using dd command on USB and it created two partitions ( Boot and Platform ) and allowed only to perform a live booting without allowing it to install on the hard disk of the board.
I then flashed *.hddimg on the USB using dd command. It only created a "boot" partition which has rootfs.img, syslinux and EFI folder.
Booting using USB provided me an "Install" option, which installed on the board and when I rebooted after installing, it displays "No bootable media found"
Using bootable image there are two partitions in the hard disk. Why it is not booting..
Steps followed:
Created an minimal yocto image using "bitbake core-image-minimal" command
Flashed the USB using the dd command.
sudo dd if=tmp/deploy/images/intel-corei7-64/core-image-minimal-intel-corei7-64.hddimg of=/dev/sdb
Clicked on install and typed “sda”
The installation was successful and when I tried to restart by removing the USB Drive, it says “No boot options found. Please install bootable media and restart."
What is the mistake I am doing here.
Which image to choose and when..
There was not much info about online, so I asked this question in the intel community and here is the response of that:
Generally a .wic image is intended to be installed directly to its final destination, whereas an hddimg is for evaluation and installation elsewhere.
By default meta-intel .wic images only have an EFI bootloader, and will not boot via legacy BIOS.
An hddimg will have both an EFI bootloader and the syslinux binaries that let it boot from legacy BIOS.
On startup with your installer USB image do you get a light gray screen with four options? If so it is booting via legacy BIOS.

module_platform_driver order and mounting rootf

I am working on some embedded Linux system and I'm trying to run Linux from USB pendrive. I put "root=/dev/sda3 rootwait" to commandline parameters of the Linux but it doesn't recognize the USB at all when it should mount /dev/sda3.
When I try to run from /dev/mmcblk0p2 everything is ok - Linux kernel recognizes this device BEFORE mounting the rootfs. The problem is only when I try to mount USB as a rootfs.
The USB is recognized only when I run the system from initramfs, but it recognized AFTER the rootfs is mounted.
My question is: how can I move initiation of USB subsystem before mounting rootfs?

Linux boot with usb 3G modem enabled as ttyACM0 device

im running Ubuntu 14.04.1 LTS (desktop), on an embedded device (Odroid U3) and
on boot, my 3G usb modem is seen as a ttyACM0 / ttyACM1 device, which is correct.
Post boot i am able to simply run wvdial..and from there I can get a connection...
I am running my system headless, and would ideally like to get the OS "converted" to more
of a server configuration(smaller) if possible. I have tried running the
the ubuntu server version here viewtopic.php?f=77&t=5123, along with
multiple versions of debian(7 / 7.4) but neither will detect the usb modem correctly on boot.
I am a newbie to linux, and the only thing that I have tried is
trying to force load some of the kernel modules on boot ( /etc/modules ) to try to
alter the detection of the device on boot. (cdc_acm, usbserial, ppp....etc), no luck.
On the ubuntu server version above I even updated the kernel to
version newer than the one currently on the working desktop version, still no luck,
Does anyone have experience with usb 3G modem detection on boot??,
Any ideas why it works on the 14.04.1 LTS desktop version , and not any others?,
thanks a ton...for any suggestions
Appears that there is a patch in 14.04 ubuntu boot that fixes the usb_modeswitch issues. After taking a raw ubuntu , adding usb_modeswitch , its now working just fine.
Did not even have to configure usb_modeswitch.

Resources