PDA

View Full Version : Loading Keymap at boottime takes ages


Julipan
30th December 2008, 03:14 PM
Hi all,

I've just installed Fedora 10 on a Mac G4 and though the installation went very smooth I'm left with one major problem.

On every boot, the first thing that happens is that I get a message saying:
Loadng /lib/kbd/keymaps/i386/qwerty/no.map
which remains the only thing on the screen for several minutes until the booting finally proceeds. Furthermore, the console text I see when shutting down the computer is mostly garbled.

As I don't really need the console to use any particular keymap, I have tried changing it to both Swedish, UK and US keymaps without any difference. I have tried editing /etc/sysconfig/keyboard as well as adding lang=en to the boot parameters in yaboot.conf. Since none of these seem to make any difference (the machine still tries to load the same Norwegian keymap no matter what I supply in the aforementioned files), I would greatly appreciate any help in solving my problem.

all the best,
/Stian

UPDATE:
I've done some more trying and testing and discovered that it does not hang every time. In the course of about 50 reboots it booted properly two times. Incidentally, both of these times were after I had done a change that I thought might help. The first of these was to run "loadkeys [path to another keymap]" and the second was to add "setkmap=us" to the boot parameter in yaboot.conf. Naturally, I was thrilled that these seemed to fix the problem, but upon the next reboot it was back to the old "Loading" message.

I also tried overwriting "no.map" and "no.map.gz" with other keymap files, and since it didn't change a thing I'm fairly sure there's nothing wrong with the keymap file itself, but rather with loading any keymap at this point. I've fiddled around with different configuration files in /etc, like rc.sysinit, but couldn't find any reference to the keymap loading.

ppesci
1st January 2009, 04:54 PM
when you change /etc/sysconfig/keyboard file, you change the line to:

KEYTABLE="us"

right?. See there is no .map or .map.gz extensions.

HTH

faizlo
2nd January 2009, 07:45 PM

I have the same problem, and no I do not have any of these extensions.

faizlo

ppesci
3rd January 2009, 02:28 AM
Maybe the problem is where the init process is loading the keymap. It must be loaded from /lib/kbd/keymaps/mac/all directory for ppc machines. But you can do a test.

After linux start, get a console and try:

loadkeys /lib/kbd/keymaps/i386/qwerty/us.map

and

loadkeys /lib/kbd/keymaps/mac/all/us.map

to see if there is a difference. If so, i think the problem can be in initrd. Maybe you need to change it or fill a bug report.

HTH

faizlo
3rd January 2009, 04:10 PM
Hi,

I tried to load it, here is the output:
$ loadkeys /lib/kbd/keymaps/i386/qwerty/us.map
Loading /lib/kbd/keymaps/i386/qwerty/us.map.gz
Couldnt get a file descriptor referring to the console

Fazilo

ppesci
3rd January 2009, 05:26 PM
Maybe is the reason in startup take too much time.

Did you try the second command?. That is:

loadkeys /lib/kbd/keymaps/mac/all/us.map

to see if you get the same error?

HTH

faizlo
3rd January 2009, 05:58 PM
I am on a Linux system.
But I tried the command with mac, and it gave the same error.

Faizlo

ppesci
3rd January 2009, 08:40 PM
Check if you have /dev/console file in your file system.

faizlo
4th January 2009, 12:27 AM
yes, i have this file
it is a character file.

ppesci
4th January 2009, 02:46 AM
As root, take a look of the system log file to find if there are some informative messages about the problem.

The file is /var/log/messages

HTH

faizlo
5th January 2009, 06:08 PM
problem solved. I think it was related to my usb ports not the keyboard map.
There used to be an error message about a certain hub not defined and that port X is not reachable. This was the main problem (in my case).

But, in general, fedora 10 is not as good as I expected.

faizlo

WNorfleet
1st August 2009, 02:12 PM
Faizlo, exactly what was the root of the problem causing the symptoms you saw, and how did you fix it? I've encountered precisely the same behavior you describe - boot takes 6.6 minutes, seems to hang with "Loading /lib/kbd/keymaps/i386/qwerty/us.map" displayed, console text mostly garbled. dmesg and /var/log/messages don't contain anything that looks suspicious to me, although I might be missing something. G4, F10. Otherwise, F10 is working fine. Sure am curious how you fixed this.

More info: Having changed the default plymouth plugin to "details", it appears that the hang is occurring prior to the execution of any startup scripts.

More info: Noticed this bug in dmesg (plus a few lines before and after):
NET: Registered protocol family 17
registered taskstats version 1
input: PMU as /devices/virtual/input/input4
Freeing unused kernel memory: 284k init
BUG: soft lockup - CPU#0 stuck for 61s! [plymouthd:495]
Modules linked in:
NIP: c01c194c LR: c01c1c84 CTR: 00000000
REGS: ee71f920 TRAP: 0901 Not tainted (2.6.27.37-170.2.104.fc10.ppc)
MSR: 00009032 <EE,ME,IR,DR> CR: 44222442 XER: 20000000
TASK = ef8d1ec0[495] 'plymouthd' THREAD: ee71e000
GPR00: 000000b4 ee71f9d0 ef8d1ec0 ef822000 00000080 ee734220 00000080 00004000
GPR08: ee645a00 f1880000 00000008 00000008 24002444
NIP [c01c194c] NVDmaWait+0x54/0x188
LR [c01c1c84] nvidiafb_imageblit+0x204/0x350
Call Trace:
[ee71fa10] [c01c1c84] nvidiafb_imageblit+0x204/0x350
[ee71fa50] [c01acdb8] bit_putcs+0x440/0x490
[ee71fb10] [c01a6a90] fbcon_putcs+0x2ac/0x2ec
[ee71fb40] [c0201834] do_update_region+0x120/0x170
[ee71fb70] [c0204ecc] redraw_screen+0x1b8/0x238
[ee71fba0] [c01a795c] fbcon_modechanged+0x32c/0x3a8
[ee71fbc0] [c01ab8ec] fbcon_event_notify+0xc8/0x750
[ee71fca0] [c0396e80] notifier_call_chain+0x48/0xa4
[ee71fcc0] [c005dc48] __blocking_notifier_call_chain+0x54/0x78
[ee71fcf0] [c019ba90] fb_notifier_call_chain+0x24/0x34
[ee71fd00] [c019d630] fb_set_var+0x248/0x274
[ee71fde0] [c019d7c8] fb_ioctl+0x16c/0x5f0
[ee71fed0] [c00ce7d4] vfs_ioctl+0x68/0x80
[ee71fee0] [c00ceba8] do_vfs_ioctl+0x3bc/0x3f4
[ee71ff10] [c00cec38] sys_ioctl+0x58/0x88
[ee71ff40] [c0013dfc] ret_from_syscall+0x0/0x38
--- Exception: c01 at 0xfee78a8
LR = 0xfee780c
Instruction dump:
601eca00 3ec02000 3ae00020 3b400008 83a302bc 3b000001 3b200024 480000e8
813d09e4 817d0400 80090044 815d0404 <5409f0be> 7f8b4840 419c00c0 801d040c
nvidiafb: DMA Wait Lockup
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
type=1404 audit(1256394162.257:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295
SELinux: 8192 avtab hash slots, 113834 rules.

WNorfleet
27th November 2009, 02:39 PM
FIXED: When the computer is viewed from the back, the keyboard must be connected to the left-hand-most USB port. If this is the case, boot is quick and service startup and shutdown messages display correctly. If the keyboard is connected to any other port, boot is exceedingly slow and service startup and shutdown messages are unreadable.

Update: NOT FIXED. The problem of slow booting described above is back. Don't know if this correlates with an update or if the period of normal booting was just a statistical fluke.