I have Fedora 12 and I'm using it as a server and there's no keyboard. Everything works fine, except that I can't reboot. I can see the system coming up, but at the end it seems to stop / hang. Maybe something todo with gdm, I don't know!
View 4 RepliesIf I change the keyboard shortcut for Open a Terminal in System > Preferences it will not stay in there if i log-out or reboot. When i log back in the shortcut is set to disabled, and I have tried different key combos and they give the same result. I am using Fedora 14 btw and hopefully you guys know of a solution. I tried making a custom command also using the gnome-terminal command but the terminal launches with a different directory other than my home directory when using that method.
View 2 Replies View RelatedI downloaded the Fedora 11 KDE livecd, installed it, and after the reboot when I get to that "firstboot" screen, I can't move the mouse, the keyboard doesn't work, I have to hold down the power button to turn off the computer.
View 11 Replies View RelatedI have been working on this problem for a year now. It is becoming critical because I need to upgrade Linux. I really want Ubuntu.
Keyboard works fine at power on. I can edit BIOS options. I put in the CD or DVD, it starts fine. Keyboard works for selecting boot options. Once the installation begins however, no more keyboard...
This is true across every version and distribution of Linux I have come across- I have dozens of liveCDs -EXCEPT Linux Mint 8.
Laptop = Acer 5517
Running Linux Mint 8 & Windows 7
I have no USB Legacy Emulation BIOS option
I've tried this: [url]
I installed Ubuntu using Wubi, and the boot loader does not detect my keyboard. Does the windows boot loader only support PS2 keyboards? Would there be a workaround... like install DOS drivers for it? I have a logitech s520 keyboard.
When in Windows, I can select what OS to use, but is there a way I can select which OS to use while booted into Ubuntu? Is there a program that will let me modify the windows boot loader from within Ubuntu?
I have tried fedora 14th and also latest ubuntu but my lenovo notebook keyboard did not detected by OS. i think it is due to some kernel missing. keyboard work if acpi=off. My laptop is "Lenovo s10-3c". 1GB RAM, 160 GB Disk.
View 3 Replies View RelatedI'm trying to install slackware 32 bit 13.1.After loading kernel it asks for keyboard configuration, but keyboard (usb wireless) doesn't work.
Keyboard works on the old 13.0 installation, on bios and also in the boot options of 13.1 installation cd.
I've tried removing legacy usb support and changing usb2.0 speed from high to full. Nothing changed.
Anybody with this strange problem? (kernel of setup seems also to detect it correctly as a trust keyboard).
I just installed Fedora 13 on a Medion E1210. The main problem i have is that the keyboard of the notebook doesn't work. If i use an external USB-keyboard it works fine.
View 2 Replies View RelatedGot myself in a bit of a squeeze here. I was messing around with the Xorg install on my Fedora 12 system. I ended up reinstalling it. Now my mouse and keyboard work fine in single user mode / terminal. But if I try and boot to X they dont work at the login screen. HAL and udev are booting. Ive done a udevadm monitor test in single user mode and its seeing the devices connect and disconnect. Ive also tried both USB and PS2 devices. Same issue. Ive tried playing with xorg.conf and generating it with Xorg -configure :1 I dont know to use to fix it. After banging my head against the wall for 20+ hours I decided it was time to ask for help. m just Lynxing around the web at the moment =X
View 2 Replies View RelatedGot new keyboard yesterday. Could easy set up it when was logged in. After reboot it doesn't work at all. Running fc11-2.6.32.21. Has anyone have any ideas / solutions?
View 3 Replies View RelatedI'm running fedora 13 on a Dell Latitude E6500. It's a dual 64-bit system.
It was working, but then I tried to swap caps lock and control.
I used:
System->Preferences->Keyboard
Layouts->USA->Options
Then, under Control Key Position, I selected swap caps lock and control.
Now, my keyboard won't work in the Keyboard Preferences test area or in any other window or when the screen-lock comes on.
I tried logging out. I tried rebooting. I tried deleting my .gnome2 directory. Nothing seems to work. I can use the keyboard on other accounts, so the keyboard is not the problem.
I use Fedora 13 x86_64. Recently i installed q4 wine and booting froze with message "registering binary handler for windows applications". Then on removing q4 wine boot froze at "unexpectedly disconnected from boot status daemon".I also removed wine, smolt.
[Code]..
I have problems with keyboard layout switcher. On Gnome everything works. But when I start to use other DE I can't switch keyboard layout by default. So I create xorg.conf, but anyway it doesn't work...
View 1 Replies View RelatedI'm having intermittent problems booting with my USB keyboard. Originally the problem was at the screen for entering my passphrase to unlock my LUKS volumes. The BIOS would recognize both USB keyboard and mouse, the BIOS passed off to GRUB with no problem and GRUB would take over the boot process. In the troubleshooting process I had changed grub.conf to show the menu with a 15 second display. ASUS BIOS also has a boot OS delay to allow access to ASUS Extra or hit ESC to skip the delay and then the GRUB menu comes up and I am able to edit the lines of boot commands and then enter to boot. I'll loose the keyboard when it gets to the point of entering the Passphrase.
I have changed the following BIOS settings:
USB Legacy: enabled (default Auto)
APCI 2.0 Support: Disabled (default Enabled)
My hardware is:
MoBo: ASUS M4A88TD-V EVO/USB3 BIOS ver: 1601
RAM: A-Data 4GB DDR3 (2x2GB sticks)
CPU: AMD Phenom II x4 965
PSU: OCZ Technology ModXstream-Pro 600W
[Code]...
It had been working fine for about 2 or 3 days and then today it took a half hour to boot up. I had even tried an old PS/2 keyboard and got the same results. In the past that keyboard would boot and then I was able to shutdown change back to my USB keyboard and boot up fine. I'm wondering if I'm right in thinking that it's a defective MoBo. If so and I'm able to return it to the store (MicroCenter in Duluth, GA) should I just get the same as a replacement or go with another MoBo from ASUS, or go with another MoBo by another mfg? If I should go with the 3rd option anyone have any recommendations? I have had Gigabyte in the past but they only seem to last about 18 months and had issues with the 2 DVD drives (closing on their own after I opened them, that stopped after switching to ASUS)
I had also installed F14 when I still had the last Gigabyte MoBo which sort of blew up taking down the CPU and PSU about a week later. I'm now on the first week with the ASUS MoBo.
Ubuntu 10.10 doesn't boot at all. The liveCD only boots once every like 30 attempts, installing from liveCD froze, but the Alternate CD worked and installed ubuntu. Now when I try to boot into it using GRUB, it freezes at the beginning of the boot process.With normal boot it freezes at line: Starting AppArmor profiles Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox.With recovery mode it freezes even before showing me anything
A little kinda like the liveCD, if I try like 30 times, it might manage to boot once in normal mode.That line keeps on repeating, the the xxx.xxx integer changes each time, and this goes on forever.I tried removing my floppy drive, but it didn't help.I tried to boot with fd0=noprobeThe one time it booted, when I restarted, it froze while trying to restart.
Back during the early days of live usb drives (F9) before persistent overlays were not ready for prime time, I created an approach to do persistence by injecting a special rc.local file into my custom live usb spin. This script mounts a file containing an encrypted ext3 filesystem using losetup which prompts for a password.
This scheme worked well for F9 and F10 but is now broken for F11 because the keyboard is not enabled at the time rc.local is executed. Obviously, all the work done to F11 for speeding up the boot time and moving the boot to the first console has broken my approach.
i have a usb mouse and keyboard and am testing booting without rhgb quiet on the previous kernel version. however the keyboard is not working at this point, which i only noticed just now.
View 2 Replies View RelatedOver the weekend my MoBo, MPU, & PSU decided to retire so I had to replace everything including memory. I originally had a Gigabyte GA-MA790FX-DS5 MoBo with Athlon II x2 and Corsair 800MHz $GB RAM. I used my current USB keyboard and USB wireless Logitech trackball which the wireless had issues, but I don't use that now. Now I have an ASUS M4A88TD-V EVO/USB3, AMD Phenom II x4 and A_Data 4GB DDR3 1333 MHz RAM. I still have the same USB keyboard which worked fine on the old MoBo and now have a wired USB mouse. I had installed F14 prior to the fried chips incident and all was working fine. With the new MoBo I have 2 issues as follows:
1. On boot both the USB keyboard and the USB mouse are detected by the BIOS, but when the screen comes up to enter my passphrase for my encrypted deviceshe keyboard is unresponsive. I have gotten it to work by hitting the "ESC" key steadily just before this screen pops up. The BIOS settings for USB seem to have only turning on Legacy USB devices option which seems to have no impact on this problem.2. When I shut down, the system does not power off and the display will show that the system is halted. All BIOS settings in regards to Power make reference to Sleep or Suspend modes, power mode after loss of AC power.can furnish the exact wording of all power related settings and USB per the manual
I'm trying to get FC13 running on a Toshiba SG20 - no keyboard, no monitor. grub.conf and the entry KEYBOARDTYPE=pc and I think that's where it's hanging. Can I say KEYBOARDTYPE=none ? There is nothing, that I can find, even on the gnu-grub site as to options for KBT.
I can attach the drive to my desktop - has screen and keyboard - and the system boots fine. However when I boot on my desktop I get the blue screen with the FC13 logo - semi circle - looks like a top laying on it's side.
Computer: Toshiba Satellite Pro L510 laptop, 10.10.This has always happened but I have gotten around it by time-out and putting my menu.list in order. When I first boot the machine (switch on for the day from computer being off) I get to the grub options to select a kernel and I have no keyboard. No up/down arrows so have to go with the kernel on top of the list (not always desirable).
When I get to the log-in screen if I hit restart and go back to the grub screen I have a keyboard and can select any kernel. If I login to the kernel I have full keyboard, no problem. If I then restart, I have keyboard at the grub list.
Nutshell: It is only when starting the computer fresh that the keyboard is dead at grub menu (and then only). Any time after that, once the computer has been switched on, if I restart I have keyboard at grub menu and can select different kernels. (Of course, if I switch the computer off and back on again, no keyboard ...)
I am running F14. I have usb keyboard and mouse, very cheap but working. There is slight problem with keyboard when I boot machine with keyboard no usb port is working, when I plug it in after system loads it is working fine.
Code:
[0.111940] usbcore: registered new interface driver usbfs
[0.111986] usbcore: registered new interface driver hub
[0.112080] usbcore: registered new device driver usb
[1.950117] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[1.950124] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[1.950131] usb usb1: Product: EHCI Host Controller
[1.950136] usb usb1: Manufacturer: Linux 2.6.35.6-48.fc14.i686 ehci_hcd
[1.950141] usb usb1: SerialNumber: 0000:00:10.3
[1.951097] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
[1.951104] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 .....
I have a very strange problem with Fedora 13 on my home PC. When booting it just hangs at random points in the boot process. When it happend the first time, I thought the PC probably is completed frozen, but then I discovered that hitting the return button got the boot process going on again, but just step by step. That means on every boot I have to keep hitting the return button until gnome starts up, that's very annoying. So for any reason the boot process seems to switch to interactive mode somehow...
I already removed the kernel boot options rhgb and quiet to see, where exactly this happens in the boot process. But as I said, it seems to be completely random. Sometimes it's when "Starting udev", sometimes, when setting up eth card, when starting atd, and so on. It's different every time.
By the way, a similar thing happens when shutting down. It can take up to half an hour until the PC really shuts down. But it's usually going faster if I just keep hitting return after issueing the shutdown command (which actually looks a bit dull). But the PC finally shuts down at some point. That's not the case when booting up. I thought, maybe there's some kind of timeout problem. But even waiting for two hours, the PC does not startup without keeping hammering the return button
I am running Vista on my C: drive and I just got Fedora 11. I planned to dual boot Vista and fedora 11. I Downloaded the Live CD from the site (680 +- MB) and burned the files IN the .iso file to an empty DVD and CD. Shrank my D: drive and now have about 27 GiB wort of unpartitioned space. I booted from the Live CD. everything went OK until i chose Boot from the Boot Menu that came up. First it took me to a screen with the following message:
ACPI: expecting a [reference] package element found type 5. and then in went on to boot normally. Then when it reached the user login screen, I found that my mouse and keyboard were'nt responding and that there was no lights on any of the keys. I checked the USB cables and did a hard shutdown and booted from the Live CD again, but the problem persists.
I was a windows user and am new to unix. I did not want to format the drives as I don't want to lose any data. Installation was successful but I am taken straight to Windows OS selection screen.
Here are some data that may be helpful:
HDD: 2TB partitioned to 9 drives ( 1 ext4, 1 swap and 7 NTFS drives) code...
I tried fixing grub, but when I type "root (hd0,11)" , it says - it has exceeded the cylinder limit of BIOS. I need help in getting fedora up and running.
Please note that formatting or altering the current drive structure is NOT an option for me. I bet there is a work around to this problem.
I'm trying to install F11 on a machine that was running well under F10 just a few hours ago. I made some changes to the disk configuration, involving the addition of a dmraid-controllable fakeRAID card (SiL 3124 I think) and creating a RAID 0 array out of the two drives connected to the motherboard itself (Intel ICH7R). Otherwise the machine's configuration is identical to the way it was when running F10. My problem is thus: when I boot from the installation DVD (64-bit), the boot process doesn't make it even to anaconda. Here is the error I get, right after md devices are autoconfigured:
[code]....
I booted F12 live cd with virtualbox and installed it on a USB stick(4GB). The installation was a success but, when I try to boot it, it doesn't work. Do I have to install the grup manually?
View 3 Replies View RelatedMy pc has two operating system, XP and Fedora 14 I was setted PC to Auto turn on with BIOS, after turning on, system was booting in fedora automatically after 10 seconds.
But, After i upgrade to fedora 15 via terminal(Preupgrade), that auto booting has disabled. I should Press Enter to boot into Fedora 15. It should be have auto booting into feodra 15 like when i was fedora 14.
Problem one: My keyboard wasn't working. Solution one: Needed a new xorg.conf file.
Problem two: How to open a programme in terminal without rendering the terminal unresponsive until that programme is closed. Solution two: Append a '&' at the end of the command. For example: gedit test-file & [/SOLVED]
The problem is, my keyboard doesn't respond when I first boot into Ubuntu. None of the keys seem to work except the 'power' key (which helps me turn this laptop on or off). During the second boot, I incessantly press the space bar hoping for something to happen. Only when the boot process completes and I see my desktop does the keyboard, finally, respond. That is precisely how I'm typing this very moment. I had not faced this problem on Windows. I use a laptop (an old one but not too old).
Nothing happens during the first boot regardless the key I press on any time.
It is a nuisance to restart my laptop and periodically strain my space bar for the keyboard to respond on the second boot (It refuses to respond on the first boot, regardless of what I do).
When I, sometimes, open files using gedit through terminal by typing: ~$ gedit PATH, what happens is that I am then unable to use any other commands on the same terminal until I close gedit or open another terminal. I can type in the terminal but nothing happens until I exit gedit. I would like my terminal to be responsive whilst I am working on gedit simultaneously. I hope it is not impossible...
I'm bonding the two NICs on my FC10 server to create a bonded LAG between it and my Cisco Catalyst switch, but during kernel init, the system always give me a notice that "bond0 doesn't appear to exist" so it skips it.Once I log in, I can always open Network Manager and the bond0 interface goes from "Inactive" to "Active" and bond0 immediately works, and I can restart the appropriate network services and everything is fine. But any idea why this bonding wouldn't be initializing during boot up? The ports on the Cisco are configured for hard set speed and duplex and portfast is turned off on them.Is there a guide for best practices for creating LAGs (bonded interfaces) between FC10 and Cisco switches?
View 4 Replies View RelatedI created a Fedora 13 x86 live image on USB using [URL] I've set it to boot using the USB and when it does I see the 10 sec countdown (or the options if I press a key), I tried all the options to boot the image but the screen just turns black for a few seconds and then the the monitor goes into "power saving mode" and nothing happens (I waited like 10 minutes). What's going on? I am trying to install fedora into an empty (secondary) HD, in the main HD I only have a win XP, and I don't want to burn a cd/dvd that's why I am trying to boot the USB.
View 2 Replies View Related