I recently installed Fedora 13 (64-bit). I am completely new to Linux. I want the NumLock key to be on upon booting into Fedora. I have tried turning that option on inside the BIOS but it appears that Fedora ignores it. Is there perhaps a way to do it within Fedora?
I have tried everything including the "setleds" command and still can't seem to get my machine to have numlock on at startup. It is enabled in the bios. Anyone have this working and care to share?!
I am in a situation to boot fedora 15 live cd in to command line mode, not graphical mode, for some testing purpose. how to change argument during booting mode
In KDE 4.5.2 I can't find where to lock up NUMLOCK. How do you do to have numlock on all the time? I have /etc/sysconfig/hardware/keyboard/kbd-numlock already on yes. If I try to change it I have an error : kbd service is not started.
I'm using a laptop that doesn't have a numlock key and would like to be able to switch numlock on and off without having to plug in an external keyboard.Is there a command or app that will let me do this?
I am running Centos 5 as a server(runlevel 3) without a GUI. Purely Text Interface. The GUI is not even installed.
trying to get numlock to get turned on before login,preferably at GRUB but at least before the login prompt. I have tried numlockx but as I have no GUI it does not work. How do I do this?
In a debian squeeze box + Xfce the numlock is never enabled at login. Is there some daemon or some configuration to turn numlock on everytime I log into my Xfce session?
I want to have numlock always on in the log-in screen, but I can't get it to work - I always have to activate it manually. I've tried out System Settings > Keyboard > Numlock > Turn on both as normal user and as root, but it simply doesn't work. I'm using openSuse 11.2 x64 w/ Kde 4.3.4 (updated from 4.3.1 w/ Kde repositories).
I have numlock set to on in my system BIOS. After Opensuse 11.2 starts to boot it turns numlock off. After entering my password KDE turns numlock back on. I have just changed my login password to include some number and out of habit try to input the numbers using the keypad - which always fails because Opensuse turned off numlock during boot. This is very inconvenient having to hit the numlck key to enable the keypad. Why is Opensuse disabling numlock during boot and how can I fix it so it stays turned on from boot right through until KDE4 has fully loaded?
Using squeeze here. Until recent updates to xserver, my numlock worked as expected, but now the damn thing won't stay on anymore. Numlockx is still broken as it's always been for me in that it turns the numlock on but not the led on the keybord. I'm using slim as a login manager which everytime it's updated they set the numlock option to disabled for whaterver reason, but then that doesn't work if I enable it anyway (why have it?). So what is it with debain/(Linux) and their obsession with disabled numlocks at login, I don't get it?
I have set the Space Saver as my keyboard layout in the KDE control center*, but Shift+NumLock/ScrollLock still does not work as it should to disable NumLock. I have tried both ibm_space_saver and ibm_spacesaver (isn't this practically a duplicate entry?) and restarted after each, to no avail.
Also, a second, possibly related problem -- why, at the login screen, does it take so long for my keyboard and mouse to start working? Maybe ten seconds after the login prompt seems to be ready -- only then can I actually do anything.
* I think this should be in Keyboard & Mouse instead of Regional & Language, but I can understand why it's there.
I get the usual kernel panic that kills the system, everything is unresponsive, if the screen is in screensaver it won't come out just the usual caps and numlock key flashing, if I have a tty open there is nothing dumped to screen. I have seen this happen when transferring large amounts of files to a USB NTFS formatted drive, but I have isolated that and made it occur when just doing a dist-upgrade.
I am pretty sure it is hardware but I am not sure where as this is the second build (last was 7.10 so I thought I would rebuild). dmesg and syslog don't show anything obvious beyond the below in syslog shortly before the panic. May 6 21:52:58 computar kernel: [79.296570] ondemand governor failed, too long transition latency of HW, fallback to performance governor I tried disabling ondemand by simply doing the below to no avail.
I have an HP laptop with a separate numlock keypad. About six months ago, I noticed the number keys were not pressing numbers. I eventually googled it and found that there's a setting in Ubuntu to set the numlock keys as cursor movement.
System > Preferences > Keyboard Preferences > Mouse Keys > DESELECT "Pointer Can Be Controlled Using the Keypad"
I did this and the numlock keys worked. However, a few reboots later I noticed the behavior was back. Again I googled and deselected the checkbox. I noticed again today that this unwanted behavior has returned. Why aren't my preferences persistent?
When shutting down OpenSuSE 11.2, it sometimes locks up on the "init.d/kdb stop" command and the Caps and Numlock key just flash and I can't do anything but hold the power button to shut off. Why does it do that? I have a Dell 5100 Inspiron laptop, 2.4GHz CPU, 1.5GB ram.
I've got 5 users who share a bunch of virtual Windows XP guests via VRDP (VirtualBox RDP access), and I'm having some problems with managing their NumLock state. They all use rdesktop to access the Windows XP machines. This works very well, as long as all of them have NumLock enabled. If one of them disables it by mistake, and then logs into one of the Windows XP machines, NumLock is disabled and some of the programs they use start to act really weird. This is causing us some grief.
So I'd like to be able to enable NumLock on all the computers (they are all running Slackware 12.2) before X, while X runs and while KDE is running. And when NumLock is enabled for the entire system, thenI'd like to remove the ability to disable NumLock altogether. NumLock should always be enabled for these users, no matter what. It would be really nice if Linux/X/KDE/whatever just honored the BIOS setting, but I haven't been able to figure out how to do that. Oh, and I'd really like if the NumLock LED was ON, so everybody are made aware of the fact that they have NumLock turned on.
ps. I've tried remapping the keys on the numeric pad with xmodmap, but that doesn't solve the problem. The actual NumLock state must be set to avoid problems with the troubled Windows programs.
I'm on Debian testing Gnome 3.18 and I searched, tried, searched and tried... no way! numlock will always stays off whenever I reboot and reach login screen.
.... I checked bios settings > numlock is on - installed numlockx - added those lines to /etc/gdm3/Init/Default (if [ -x /usr/bin/numlockx ]; then /usr/bin/numlockx on fi) - checked dconf gnome /settings-daemon /peripherals /keyboard remember-numlock-state: true ....
I have a Compaq CQ40-616TU Laptop. I have installed fedora 11 64 bit more then 20 times and facing the same problems. The Problems are
1) After booting into the fedora it get hanged up and blue screen with the logo of fedora. 2) Some time it shows message that "Could not update /var/lib/gdm/.IC Eauthirity" 3) I have also updated through yum but still facing the same problem 4) I have also tried fedora 12 but during installation process it shows message that no suitable hardware found.
i decided to install ubuntu in my PC,i downloaded the .ISO image and i installed it in my USB. After trying it and all that i observed that i really liked it and i decided to formally install it to my computer in the hard drive. When i reached the partition thing,i selected to dual boot with Vista and select between each them in every startup,when i clicked FORWARD it gave me an error which i did not read(because,again im a noob) so i clicked cancel.
Today i wanted to go through the process again and now really install it,so again i went to the time zone part and i clicked forward but then,instead of taking me straight to the partition phase,it appeard a window saying "The installer has detected that the following disks have mounted partitions: /dev/sda ...." I clicked yes,to unmount this partitions so it took me to the partition thing,once there i selected the option to install Ubuntu with Vista and select between them i neach startup,then i clicked forward and went to the username/computer name process,once i finished i continued to the next part,the installation,but i selected to import all of my WIndows VIsta default user data,after that i clicked forward and went to the installation process,i went down stairs to eat soemthing while it finishes,i came back and it was finished,it asked me to reboot so i clicked in Restart Now.
When it tried to boot,appeared an error saying: Error: no such devide found: #################### Grub load(or something like that) grub rescue: and it was a command line,since there i havent been able to boot into vista or Ubuntu,im really scared because is the first thing related to OS installing ive done,so i booted my USB and ran the trial and right now im trying to find out what to do from that trial version. I just went to the INSTALL UBUNTU 10.04 LTS application under the System>Administration Menu and found out that in the partition phase the Install and allow to select between both systems in eahc startup option,i dont know what to do,i foudn out that my HD has still all its data(MUsic/Videos/Folders/Programs/ect.)its just that i cannot boot from it. Also in GParted it appears as /dev/sda1/ and a warning icon besides it,also when i go into information, thers this warning there [URL]
I am using a linux kernel 2.6.36 using mips architecture. I have succesfully booted the machine through Flash memory, but it is not booting through nfs. It is getting stuck at the stage where the image starts loading. In short the vmlinux.img file is being copied properly to nfsroot but the image is not loading.
I've been searching the forums for any posts that cover my problem, but most of the booting problems I've found are different from mine.Anywho, the situation:ell laptop, 2 partitions, first is Windows XP, second is Ubuntu Karmic.Whenever I turn on my computer the first loading screen that shows up (is this the BIOS? Excuse my little knowledge of this stuff), before GRUB loads, is really slow. It takes about a minute to load.However, whenever I restart from my XP partition, it suddenly loads fast! And this does not happen when restarting from my Ubuntu partition or anything
I have just installed Fedora 8 off a magazine dvd I had but it won't boot...What I have done is I got Easeus' Partition Manager 3.0 Home Edition and created a 25 GB partition, then i rebooted the system with the Fedora 8 disk in to install it whic it did, no errors, (but I did say not to install the boot loader because i have Windows 2000 installed aswell) then after it has installed it boots straight to windows. It doesn't ask me to boot to Fedora, it goes straight to windows.I am totally stumped as why I can' boot to Fedora.
I went directly from F9 to F11, and so "Plymouth" came as a very unpleasant surprise. I read the thread,
[URL]
about getting the graphical animation, but it didn't address the root problem. Whether you see the animation, the bubble in the middle of the screen filling up with white, or the three-color bar at the bottom of the page, Plymouth seems to be completely useless.
I tried an experiment. I disconnected the eth0 cable and rebooted. Absolutely nothing appeared on the screen to show that there was a problem, much less what it was. With the old system, the progress bar would be immediately replaced with the "details" to show that eth0 "failed" to be started. If one wanted, which I often did, one could manually switch to see the "details" (all the processes and demons started) throughout the whole boot.
I just can't understand removing such an important feature of the boot process. Where do people get ideas like this? Being able to get into the real goings-on of an OS has always been the hallmark of UNIX/Linux systems. I hope I'm wrong, but it seems the new Fedora philosophy is more and more like Microsoft's.
But here's my question: Is there any way I can restore the way the boot screen worked under F9?
How would I go installing Fedora to a USB stick and then booting from it?Does my BIOS have to support booting from a USB stick? because I don't think I have an option for that.So can someone explain to me how installing to and booting from a USB stick works?
I was wondering if some one can help me to find outwhich file I need to edit in order to umount a NTFS that I mount at boot time, before I reboot or turn of the computer.I edit your /etc/fstab and add it this line in order to mount on boot./dev/sda1 /mnt/windows ntfs-3g defaults 0 0
I had fedora-11 installed and the kernel version was 2.6.29 I downloaded new kernel version 2.6.33.2 and did following,
make mrproper make make modules_install make install
when I rebooted and selected 2.6.33.2 from grub entry, fedora logo came and spalshed, after that monitor started blinking and now its not going anywhere, i can see blank screen and nothing else. If I do ctrl+alt+del it shuts down the system normally.
I tried interactive mode also system did fine untill this point "registering binary handler for windows application" after that the same problem came, monitor started blinking and screen is blank., Any pointer regarding this will be helpful , what exactly went wrong? I can provide more info if u need it.
I have purchased one new HP Laptop dv6 pavillion and installed Fedora 12 along with Windows 7 Now the Windows is not booting.. Before installing fedora it was working fine.. System Configuration: 320 Hard disk, 2.13 GHz, Nvidia Geforce Graphic, Ram 3 GB while giving fdisk -l command in Fedora windows is showing below System as SFS...
I have installed the latest Fedora on an external (USB) hard drive. Is it possible to alter part of the program so that I can run this external hard drive on any machine regardless of it's operating system?