Using bluetooth keyboard in grub bootloader - linux

I want to choose between several OS's during startup. How can i manage this by using my bluetooth keyboard/Cellphone or at least my IR remote?

One solution is to boot the linux system first, and then add the boot once command to grub for booting another system the next time. This will take time, but works without any hardware.
Using keys via IR remote did not work so far.

Disclaimer: I'm not an expert for GRUB and I'm using my general knowledge about PC hardware and software here.
As far as I know, GRUB is using BIOS to get input from the user. Thus, unless your PC (or other device you're running GRUB on) has support for Bluetooth/IR remotes in BIOS, there's no way you can do what you're asking for. Also, if you happen to have a wireless keyboard with host side wireless base, which is pluggable into a standard USB or PS/2 port, it might work (as long as BIOS sees such a keyboard as a normal wired keyboard connected to USB or PS/2 port).
Other alternative would be to modify GRUB (add support for Bluetooth/IR remotes/etc), but that's a story of a completely different complexity. :)

I would verify the keycodes coming from your ir dongle using showkey.
Then make sure the grub keymap handles them.
Personally I have yet to changing the grub keymap to work for me.
I have a tablet loaded with grub and I know the keycodes the buttons give in ubuntu but when I modify the keymap to make down and enter two of the buttons I never get a response in grub. But if undo my keymap changes and hook up a usb keyboard it works fine.

I am also keen to use my Bluetooth keyboard when selecting my OS in GRUB. It makes no sense to place 2 keyboards on the table just to choose a choice. I think it is good for GRUB to host a bit of Linux (just the BT part) so that it loads the module for the BT device to work.
Nevertheless, this may mean that you will have to re-pair your device once you are in your preferred OS, unless you wish to use up all your BT chips with just GRUB/Windows/Linux. And, as far as I can tell, the commercial products support up to only 3 BT connections usually.

Related

Jetson TK1 booting issues

Received my Jetson TK1 yesterday. After unboxing it and configuring the Linux GUI, rebooting the device with a mouse (cordless) attached to its USB 3.0 port takes it to some sort of Command line page where it probably loads some files and then the screen starts printing " [ . ] ". Nothing happens beyond that until I restart the board without any USB peripheral and then the device boots into the normal Linux GUI. Unable to figure out what's wrong with my board and why is it not working properly.(I am a newbie to LINUX)
P.S.: Connecting the monitor via HDMI after switching on the device gives no visual output, just a blank screen. Is it possible to connect the device via network adapter for remote access even it the screen is running blank?
The question is quite old, but as some people might get frustrated with it, I'll provide the answer for most probable cause.
Upgrading the board running 19.X release causes libglx.so to be corrupted. The issue have been actively discussed on NVIDIA forums and the best way to solve it is to upgrade to 21.X.
Otherwise, you can try recovering the libglx.so in the usr/lib/xorg/modules/extensions/ from Tegra124_Linux_R19.3.0_armhf.tbz2.
Could you possibly provide a bit more information about your situation.
Are you able to go to command mode by pressing 'CTRL+F1' or 'CTRL+ALT+F1'?
If that works, it means your Jetson operating system is working but only the GUI is not working properly.
Yes, You can use ssh to your Jetson (what I do) if only the GUI of Jetson is broken and your OS is working properly. Note that in order to do so you need to know ip address of your Jetson and perform some possible router configuration.
Note: Sometimes if you have a USB device connected to your system (jetson), the jetson might mistakenly assume the USB is storage type and therefore tries to boot up from the USB. This leads to failure since it can not load any OS of the USB. (I'm not sure if this is the case for you)

How can we use Linux from a small storage pen drive? Does it work on micro-controllers also?

I generally hear that LINUX OS can be downloaded on flash, pen drive (floppy disk?) etc. How we can do that?
I have RHEL 5.4 source code - so how can download it into pen drive and how much space is required?
What other functionality I can add apart from the OS - so that when I boot from that storage device I can make use of them?
Can we download Linux OS into micro-controllers also?
I generally hear that LINUX OS can be downloaded on flash, pen drive (floppy disk?) etc. How > we can do that?
If you can't get it to work on your own, you can buy a ready made Linux on a USB drive from
a site like http://www.osdisc.com or http://www.cheapbytes.com
Not all PCs, especially older PCs, can boot from the USB Drive. Even some newer PCs are beginning to ship with security features that can interfere with booting code. When it does work, you have to find out the proper way to boot the USB drive. You might have only a few seconds during reboot to enter the right key, or it will boot Windows (if Windows is installed). The key to get to the BIOS Boot Menu might be delete or escape or F10 or some other key (varies with PC motherboard manufacturer). A message on the screen that flashes by rather quickly might mention keys you can press. Boot to a specific device or changing boot order can also often be found in the BIOS setup.
There is a linux utility called unetbootin that will create a USB drive that will boot linux. It does not create a USB boot drive from a source code distribution, but rather from an ISO file representing a live CD or the live CD itself.
Since large USB drives (e.g. 32GB) are relatively inexpensive, if you want to compare systems or have multiple systems there is a way to have multiple linux and other operating systems on one USB drive and be able to choose which to boot into. See, for instance, http://www.pendrivelinux.com/ which has a wide variety of procedures for making a bootable USB using either windows or Linux to set up the USB and booting a variety of systems.
I have RHEL 5.4 source code - so how can download it into pen drive
and how much space is required?
RHEL 5.4 is a bit old. You need the Live CD, if there was one.
The ISO file can take up 600+MB. You want space left over to use the system. 2GB for the pen drive is OK. Sometimes you can get by with less.
What other functionality I can add apart from the OS - so that when I
boot from that storage device I can make use of them?
Upon boot the operating system will often recognize sound cards, other usb devices, the hard drives, etc. You need to know how to use these things within Linux, and how to enable them if they are not configured. Some Linux distributions have a place to put packages that are to be autoinstalled when a USB pen drive based system initializes. In this way you can "install" software from the distribution archives that are not included on the standard live system, even if you don't have internet access.
Can we download Linux OS into micro-controllers also?
People run it on raspberry pi and such, but the versions of Linux on non-PC hardware that has low memory are often quite tiny compared to a desktop version. They can be tiny enough to be challenging to work with or expand.

KVM Switch and Happy Hacking Keyboard Pro 2

I have been using HHKB Pro 2 for almost a year, one at home and one at work. Now I have to work with two computers (PC and Mac) for which I decided to buy KVM switch.
I picked one and expected nothing wrong with that, but when I plugged it in, HHKB was not working either with PC nor with Mac. I tried several keyboards and all worked flawlessly expect the mentioned HHKB. I tried the second one with the same result. With that in mind, I purchased another KVM switch, which was hardware switched (the previous one listened to ScrollLock which is supported by HHKB by using Fn key). To my surprise, it didn't work either.
Now I have tho KVM switches that work flawlessly with any keyboard BUT that damned HHKB Pro 2.
Is there any KVM switch that can handle this (or to be more precise, is there any that HHKB can deal with, because obviously there's something wrong with HHKB, not with KVMs).
Do you have any experience with that?
Thanks.
HHKB Pro 2 has got USB hub and that seems to be causing trouble with most of the KVM switches.
KVM switches expect keyboard to be attached to its keyboard port. So when HHKB Pro 2 is attached, KVM switch finds an USB hub and just stops. It won't go beyond USB hub to look for keyboard which might be attached to it.
So are there any KVM switches that works fine with HHKB Pro 2?
One of the ATEN's KVM switch worked although it was a bit unstable.
May be their recent models might work with increased stability if you want to give it a try.
However, I would suggest free software solution like "Synergy" (http://synergy-foss.org/) if you have display for each of your computers.

Can a profile on a Razer Nostromo be carried over to another PC without Nostromo drivers or programming software?

I would like to get myself a Nostromo for hotkeys (i.e. Ctrl+z, Ctrl+x, Ctrl+c, etc) so that I can increase my productivity at work, and type using the Dvorak keyboard layout (which is what I am already most proficient in) without having do deal with all the wonky keyboard shortcut remappings. I would also like to carry it between home and work without having to reprogram it (I won't be able to install the drivers or programming software on my work PC).
I checked the user guide, the vendor website, and all of the technical specs / FAQ and all I could find was that "macros are saved to my awesome PC." I'm fine with that, but what about key mappings? It doesn't say whether programmed key mappings are stored to the device and can run without drivers being installed if the hardware is plugged into a new PC. I recall also reading somewhere that the keypad can be used as a standard game controller without device-specific drivers installed, but again no mention on whether or not key mappings will work in this mode, or whether a profile saved to the device will work without drivers installed.
If anyone has one of these, can you let me know whether it is possible to use the Nostromo (and existing programmed key mappings) without having to install device software?
Thanks!
To answer my own question - no, the nostromo does not appear to work as a keyboard without drivers installed, and the profiles do not transfer between two PCs.

Is there a way to ask the Linux Kernel to re-run its PCI initialization code?

I'm looking for either a kernel mode call that I can make from a driver, a userland utility, or a system call that will ask the Kernel to look at the PCI bus and either completely re-run its initialization, or initialize a specific device. Specifically, I need the Kernel to recognize a device that was added to the bus after boot and then configure its address space, interrupt, and other configuration parameters, and finally enable the device so that I can load the driver for it (unless this all happens as part of the driver load).
I'm stuck on the 2.4.x series Kernel for this, and am currently working with 2.4.20, but will be moving to 2.4.37 if it matters. The distro is a stripped down Red Hat 7.3 running in a ram disk, but I can add in whatever tools are needed to get this working (as long as they play nice with 2.4 series).
If some background would help clarify what I'm trying to do: From a cold boot, once in Linux I use GPIO to program an FPGA. Part of the FPGA, once programmed, implements a simple PCI device. Currently, after programming the FPGA, I reboot the system and Linux recognizes the device after coming up and loads the driver for it.
Instead of needing that reboot, I'd like to simply ask the Kernel to do whatever it does during boot up to find PCI devices (I have the Kernel configured to find PCI devices on its own, instead of asking the BIOS for that information, so the BIOS won't need to know about this device (I hope)).
I believe that Linux is capable of seeing the device after it is programmed but before a reboot, because scanpci will show the device after I program it, as will lspci -H 1. I just need a way to get it into /proc/pci, configured and enabled.
This below command will help the user to rescan it complete root hub.
echo "1" > /sys/class/pci_bus/0000\:00/rescan
You could speed up the reboot with kexec, if you don't figure out how to get the PCI scan redone. You could ask this on the LKML, if you haven't already.
unloading/reloading the module doesn't help, does it?
http://www.linuxjournal.com/article/5633 suggests you should be able to do it with 2.4 kernels using pcihpfs.
If that isn't working, maybe the driver doesn't support hotplug?
It would probably crash the system if you reconfigured the addresses of other PCI devices while they are in use.
A better way would be to just configure the new card. If your kernel has support for Cardus devices, it already knows how to configure a newly-inserted PCI device (which is what Cardbus is). You just need to figure out how to get the kernel to do it...
It should be possible for a kernel module to do this. Even if you can't get built-in hotplug code, you should be able to set the pci resources using calls to pci_bus_write_config_dword() and friends. There is probably some IRQ routing setup to do as well.

Resources