Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 13 years ago.
Improve this question
I'm trying to boot Linux on a GPS device from a SD card.
I have found some informations about the device on Internet and apparently it's possible to load a customized Windows CE.
To achieve this, they use a boot loader file that has the extention ".bld"
I extracted the ISO of Ubuntu MID on the SD card, but there is no files with a bld extension. I guess it use a different boot loader system .. which doesn't seem to work on the device.
So my question is;
Is there a way to use a "bld" file to boot Linux ? If so, how can I create the file ?
I'm sorry if the question is stupid or off-track, I don't know much about boot loaders ..
In case you wonder, here's the device:
http://www.curtisint.com/web/browser.asp?productID=GPD359&catName=GLOBAL%20POSITIONING%20SYSTEM
More detailed specs (and mod site):
http://gpd359.wikidot.com/article:outofbox
Edit: Turns out I only had to put a file named "YFGo2CE.bld" (the file only contains a random string) on the SD card and reset the device. From there I can boot directly in WindowsCE and load the suggested Haret ROM tool.
Thanks!
One thing you might want to look at is the Haret ROM tool. It can be found and more information here
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I have a question that is why Linux driver need to compile with Linux source if a new hardware in the unsupported list of Linux kernel? but Windows driver just only need to double click setup.exe, don't need to compile...
Is it the kernel type different? microkernel vs monolithic kernel? or any other reason? thank you.
This is mainly to do with Linux' Monolithic Kernel. This in contrast to Windows' kernel which does not include drivers and drivers are written using the Windows Driver Model which is plug-and-play. Read about the differences in their respective Driver Architectures here.
I would suggest you give this article on Loadable Kernel Modules a read.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I have an ISO image (stock Ubuntu 13.10 DVD ISO image) loaded into memory pre-OS and I'm trying to start the Linux installation process from this image. GRUB can recognize the image as a cd and I can start the installation (I'm experimenting with an UEFI platform, and using an UEFI version of GRUB so it can recognize the image as a valid block device with a supported file system).
My problem is the kernel cannot find the install media (which is expected) so it panics early on. I realize I can write a simple block device driver so the kernel can find the image but for the sake of portability, is there a way to mount tmpfs/ramfs at a specific start address? Or is there a way to tell the kernel that there is a file system at a specific address?
Thanks
Compile your kernel with the ISO filesystem as a built-in. Specify the ISO image as the initrd image. The contents of the ISO will probably need modified to understand this new way of booting as, unlike a normal initrd image, you will not want to be unmounting it to mount the real root filesystem.
Note that the preferred way would probably be to write a kernel module that recognizes and mounts the ISO and put it in a smaller initramfs image instead. The above is just an idea about how you might accomplish it without writing a module.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
Specifically, I was running Ubuntu 10.04 (Lucid Lynx), and accidentally mounted an empty device (partition) at /usr/src. I forgot to unmount the empty device and on rebooting Ubuntu greets me with a message similar to the following:
"Ubuntu will now start in low-graphics mode as it can't find the
configuration for relevant drivers"
And then it sits idle just like that, with a dark screen (after I click okay on the above dialog box). It also gives me an option to configure the options myself (which I am not comfortable doing).
I am suspecting that this is related to /usr/src being empty as that is the only stupid thing I remember doing. Can somebody explain if this is really the case?
No, it is not. This directory is empty by default but you can have some source trees in it, for example linux kernel source tree. Anyway it is unlikely that some files from that directory are used during the boot process.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I have an USB modem that I use on Ubuntu. I have also a program which communicate with this device using its ttyUSBxx number.
My problem is that every time I unplug/plug the device again, or when I reboot my PC, the device gets a new ttyUSB number, for example: ttyUSB0 or ttyUSB1.
How can I force this device to always use the same number (say: ttyUSB0)?
udev is Linux's dynamic device manager. udev persists information about devices you plug in, and you can modify this information so that it adds a specific 'symlink' in the directory for this device.
Now, your usb modem's definition should be inside the folder /etc/udev/rules.d/, and the filename will be something like 50-udev.rules. The file contains one line per device, (you can use a number of tools to help identify the correct line. See below link on using udevinfo)
Now, you can edit the relevant line, or even better, create another file and copy the relevant line into it. The filename should start with a lower number (e.g. 49-my-modem.rules), so that it gets loaded first. You need to add the following to the end of the line:
, SYMLINK="ttyUSBmodem"
Now, your device should come up as /dev/ttyUSBmodem (aswell as the dynamically assinged /dev/ttyUSB[0-9])
For more help with identifying the correct line and the whole process, see here:
http://noctis.de/archives/16-HowTo-fixed-name-for-a-udev-device.html
HTH
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
Suppose I want to create my own desktop envoriment for Linux, without X. Like Google with the Android did. Where do I start? Is it actually a normal application that just draws stuff, and starts after the kernel boot? And how does it draw it? Using OpenGL or is there something more generic? And graphics drivers, how is it going? You should develop custom graphics drivers for your desktop or it comes with the Linux kernel?
Note: It's for normal PCs and not embedded devices.
Thanks.
See: DirectFB (and Wikipedia).
You can use the frame buffer device.
There are a few toolkits that render directly to the frame buffer for embedded device - even fully featured toolkits like Qt and wxWidgets can do it.
Well, you could study how OS X works in some detail.
You're probably best advised to keep most of the X server... it has a set of good device drivers already, and they're a very large part of the work.