You are not logged in. Please login or register.
GParted forum → Live Media → German keyboard layout with gl_kbd=de does not work
tested with gparted 0.5.2-1
Does anyone know a workaround? Is this a bug?
gl_lang=de_DE works well for german localization, but not gl_kbd=de for the german keyboard layout.
Inside the Desktop "setxkbmap de" works well, but it will be nice to set this with the boot parameter.
Try gl_kbd=/usr/share/keymaps/i386/qwertz/de.kmap.gz
Or the correct keymap file from Debian system.
Try gl_kbd=/usr/share/keymaps/i386/qwertz/de.kmap.gz
Or the correct keymap file from Debian system.
Thanks for suggestion, I tried with:
kernel=/.images/disktools/gparted0521/vmlinuz boot=live live-media-path=.images/disktools/gparted0521 gl_lang=de_DE gl_kbd=/usr/share/keymaps/i386/qwertz/de.kmap.gz keyb=de gl_batch toram=filesystem.squashfs union=aufs noswap noprompt vga=791 ip=frommedia
and
kernel=/.images/disktools/gparted0521/vmlinuz boot=live live-media-path=.images/disktools/gparted0521 gl_lang=de_DE gl_kbd=/usr/share/keymaps/i386/qwertz/de-latin1.kmap.gz keyb=de gl_batch toram=filesystem.squashfs union=aufs noswap noprompt vga=791 ip=frommedia
But neither works.
Hello wla,
I can confirm your observation : neither gl_kbd=de nor keyb=de work. It isn't that obvious with GParted ( the only thing, you need to type, is a volume label ), but with terminal/console windows. gl_kbd=de should work within the GUI, keyb=de in console mode. As far as I can track the boot process, /etc/console/boottime.keymap.gz gets created with German keycodes, but nothing happens with it. In one of the involved shell scripts I read, that "keymap must be set before /usr is created", otherwise it would be ignored.
Maybe it's a timing problem. Anyway, it's a bug.
Best Regards
cmdr
To address this issue, I have uploaded a new testing GParted live (0.5.2-5), so please give it a try, and you can use:
kernel=/.images/disktools/gparted0521/vmlinuz boot=live live-media-path=.images/disktools/gparted0521 gl_lang=de_DE gl_kbd=/usr/share/keymaps/i386/qwertz/de.kmap.gz keyb=de gl_batch toram=filesystem.squashfs union=aufs noswap noprompt vga=791 ip=frommedia
or
kernel=/.images/disktools/gparted0521/vmlinuz boot=live live-media-path=.images/disktools/gparted0521 gl_lang=de_DE gl_kbd=/usr/share/keymaps/i386/qwertz/de-latin1.kmap.gz keyb=de gl_batch toram=filesystem.squashfs union=aufs noswap noprompt vga=791 ip=frommedia
Please post your restuls. Thanks.
Steven.
Problem solved with 0.5.2-5!
Both kernel lines work for GUI and console/terminal mode. I found a third possibility : gl_kbd=/etc/console/boottime.kmap.gz. This copy of a keymap file depends on keyb=de, and the path is shorter. Well, there is a fault message at boot, but it seems meaningless.
My question is, who needs a split language design between GUI and console ? Why not choose all with keyb=de/it/fr... and its related layout and variant parameters? Remember, that you only need your keyboard to type a volume name within the GUI (with restricted character usage), whereas in console mode it is a must to have your local keyboard design.
Best Regards
cmdr
cmdr,
Thanks. Good point. I agree that.
I will try to implement a better way for this.
Steven.
Thanks for this quick solution.
Could you give testing GParted live 0.5.2-7 a try?
Now it should be able to shorter as (i.e. gl_kbd is not required):
kernel=/.images/disktools/gparted0521/vmlinuz boot=live live-media-path=.images/disktools/gparted0521 gl_lang=de_DE keyb=de gl_batch toram=filesystem.squashfs union=aufs noswap noprompt vga=791 ip=frommedia
Please let us know the results.
Steven.
Hello Steven,
I just tested GParted live 0.5.2-7 with regard to German keyboard layout and may confirm, that it works flawlessly as expected, both in GUI and console mode. Unfortunately kernel parameter "gl_batch" no more works for me, my monitor shuts down, when X is started. Maybe the default graphic mode is not supported or the driver for my graphic card (ATI Radeon X1600 Pro Sapphire) has a problem. If I choose an appropriate mode manually, everything works fine.
Kind regards
cmdr
Hi Cmdr,
Thanks for confirming that "keyb" works there.
As for the graphic mode, I guess your VGA card uses the package "xserver-xorg-video-radeon",
in GParted live 0.5.2-7, xserver-xorg-video-radeon is 6.13.0-1, while in GParted live 0.5.2-5, it's 6.12.192-2... maybe the driver regresses...
Did you check /var/log/Xorg.0.log? Did you find some clues?
Steven.
Hi Steven,
Did you check /var/log/Xorg.0.log? Did you find some clues?
IMHO, yes.
dmesg
[ 0.497213] vesafb: framebuffer at 0xd0000000, mapped to 0xf8080000, using 3072k, total 16384k
[ 0.497221] vesafb: mode is 1024x768x16, linelength=2048, pages=9
[ 0.497225] vesafb: protected mode interface info at c000:a31c
[ 0.497230] vesafb: pmi: set display start = c00ca3aa, set palette = c00ca46c
[ 0.497235] vesafb: scrolling: redraw
[ 0.497240] vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0
[ 0.529469] Console: switching to colour frame buffer device 128x48
[ 0.561941] fb0: VESA VGA frame buffer device...
[ 23.644373] [drm] radeon kernel modesetting enabled.
[ 23.686749] radeon 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 23.700543] radeon 0000:01:00.0: setting latency timer to 64
[ 23.730433] [drm] radeon: Initializing kernel modesetting.
...
[ 23.778112] [drm] register mmio base: 0xFDCF0000
[ 23.791764] [drm] register mmio size: 65536
...
[ 23.876262] [drm] GPU reset succeed (RBBM_STATUS=0x10000140)...
[ 23.927208] [drm] Generation 2 PCI interface, using max accessible memory
[ 23.941049] [drm] radeon: VRAM 256M
[ 23.954779] [drm] radeon: VRAM from 0x00000000 to 0x0FFFFFFF
[ 23.968589] [drm] radeon: GTT 512M
[ 23.982041] [drm] radeon: GTT from 0x20000000 to 0x3FFFFFFF
[ 23.996119] radeon 0000:01:00.0: irq 25 for MSI/MSI-X
[ 23.996126] [drm] radeon: using MSI.
[ 24.009356] [drm] radeon: irq initialized.
[ 24.022596] [drm] Detected VRAM RAM=256M, BAR=256M
[ 24.023774] [drm] RAM width 128bits DDR
[ 24.025009] [TTM] Zone kernel: Available graphics memory: 439728 kiB.
[ 24.026171] [TTM] Zone highmem: Available graphics memory: 1557364 kiB.
[ 24.027329] [drm] radeon: 256M of VRAM memory ready
[ 24.028485] [drm] radeon: 512M of GTT memory ready.
[ 24.029613] [drm] GART: num cpu pages 131072, num gpu pages 131072
[ 24.032324] [drm] radeon: 1 quad pipes, 2 z pipes initialized.
[ 24.033500] [drm] PCIE GART of 512M enabled (table at 0x00040000).
[ 24.034623] [drm] radeon: cp idle (0x10000C03)
[ 24.035768] [drm] Loading R500 Microcode
[ 24.037163] platform radeon_cp.0: firmware: requesting radeon/R520_cp.bin
[ 24.055857] radeon_cp: Failed to load firmware "radeon/R520_cp.bin"
[ 24.057018] [drm:r100_cp_init] *ERROR* Failed to load firmware!
[ 24.058135] radeon 0000:01:00.0: failled initializing CP (-2).
[ 24.059242] radeon 0000:01:00.0: Disabling GPU acceleration
[ 24.060723] [drm] radeon: cp finalized
[ 24.061855] radeon 0000:01:00.0: f66fbb00 unpin not necessary...
[ 24.257195] fb: conflicting fb hw usage radeondrmfb vs VESA VGA - removing generic driver
[ 24.258245] Console: switching to colour dummy device 80x25
[ 24.259017] Console: switching to colour frame buffer device 160x64
[ 24.287413] fb0: radeondrmfb frame buffer device
...
[ 24.287489] [drm] Initialized radeon 2.0.0 20080528 for 0000:01:00.0 on minor 0Xorg.0.log
...(--) PCI:*(0:1:0:0) 1002:71c2:174b:0840 ATI Technologies Inc RV530 [Radeon X1600] rev 0, Mem @ 0xd0000000/268435456, 0xfdcf0000/65536, I/O @ 0x0000de00/256, BIOS @ 0x????????/131072
(--) PCI: (0:1:0:1) 1002:71e2:174b:0841 ATI Technologies Inc RV530 [Radeon X1600] (Secondary) rev 0, Mem @ 0xfdce0000/65536...
(II) VESA(0): initializing int10
(II) VESA(0): Primary V_BIOS segment is: 0xc000
(II) VESA(0): VESA BIOS detected
(II) VESA(0): VESA VBE Version 3.0
(II) VESA(0): VESA VBE Total Mem: 16384 kB
(II) VESA(0): VESA VBE OEM: ATI ATOMBIOS
(II) VESA(0): VESA VBE OEM Software Rev: 9.12
(II) VESA(0): VESA VBE OEM Vendor: (C) 1988-2005, ATI Technologies Inc.
(II) VESA(0): VESA VBE OEM Product: RV530
(II) VESA(0): VESA VBE OEM Product Rev: 01.00
(**) VESA(0): Depth 24, (--) framebuffer bpp 32
(==) VESA(0): RGB weight 888
(==) VESA(0): Default visual is TrueColor
(==) VESA(0): Using gamma correction (1.0, 1.0, 1.0)...
(Monitor)
(II) VESA(0): VESA VBE DDC supported
(II) VESA(0): VESA VBE DDC Level 2
(II) VESA(0): VESA VBE DDC transfer in appr. 1 sec.
(II) VESA(0): VESA VBE DDC read successfully
(II) VESA(0): Manufacturer: CPQ Model: 1332 Serial#: 1144599093
(II) VESA(0): Year: 1998 Week: 31
(II) VESA(0): EDID Version: 1.1
(II) VESA(0): Analog Display Input, Input Voltage Level: 0.700/0.700 V
(II) VESA(0): Sync: Separate
(II) VESA(0): Max Image Size [cm]: horiz.: 32 vert.: 24
(II) VESA(0): Gamma: 2.38
(II) VESA(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
(II) VESA(0): redX: 0.632 redY: 0.335 greenX: 0.295 greenY: 0.593
(II) VESA(0): blueX: 0.143 blueY: 0.066 whiteX: 0.283 whiteY: 0.298
(II) VESA(0): Supported established timings:
(II) VESA(0): 720x400@70Hz
(II) VESA(0): 640x480@60Hz
(II) VESA(0): 640x480@75Hz
(II) VESA(0): 800x600@60Hz
(II) VESA(0): 800x600@75Hz
(II) VESA(0): 832x624@75Hz
(II) VESA(0): 1024x768@60Hz
(II) VESA(0): 1024x768@75Hz
(II) VESA(0): Manufacturer's mask: 0
(II) VESA(0): Supported standard timings:
(II) VESA(0): #0: hsize: 800 vsize 600 refresh: 85 vid: 22853
(II) VESA(0): #1: hsize: 1024 vsize 768 refresh: 85 vid: 22881
(II) VESA(0): #2: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
(II) VESA(0): Supported detailed timing:
(II) VESA(0): clock: 25.2 MHz Image Size: 306 x 230 mm
(II) VESA(0): h_active: 640 h_sync: 656 h_sync_end 752 h_blank_end 800 h_border: 8
(II) VESA(0): v_active: 350 v_sync: 387 v_sync_end 389 v_blanking: 449 v_border: 6
(II) VESA(0): Ranges: V min: 48 V max: 125 Hz, H min: 30 H max: 69 kHz,
(II) VESA(0): Serial No: 831CF23AD925
(II) VESA(0): Monitor name: COMPAQ V75...
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Reloading /usr/lib/xorg/modules/libint10.so
(II) VESA(0): initializing int10
(II) VESA(0): Primary V_BIOS segment is: 0xc000
(II) VESA(0): VESA BIOS detected
(II) VESA(0): VESA VBE Version 3.0
(II) VESA(0): VESA VBE Total Mem: 16384 kB
(II) VESA(0): VESA VBE OEM: ATI ATOMBIOS
(II) VESA(0): VESA VBE OEM Software Rev: 9.12
(II) VESA(0): VESA VBE OEM Vendor: (C) 1988-2005, ATI Technologies Inc.
(II) VESA(0): VESA VBE OEM Product: RV530
(II) VESA(0): VESA VBE OEM Product Rev: 01.00
(II) VESA(0): virtual address = 0xb6161000,
physical address = 0xd0000000, size = 16777216
(II) VESA(0): Setting up VESA Mode 0x118 (1024x768)
(II) VESA(0): VBESetVBEMode failed, mode set without customized refresh.
(therefore flickering with 60Hz)
(==) VESA(0): Default visual is TrueColor
(==) VESA(0): Backing store disabled
(==) VESA(0): DPMS enabled
(WW) VESA(0): Option "PreferredMode" is not used
(==) RandR enabled
Firmware file radeon/R520_cp.bin not existing or wrong ?
Best Regards
cmdr
After discussed with Curtis, we agreed that the non-free, but distributable firmware should be included in GParted live to make live easier.
Therefore I have uploaded another testing one, GParted live 0.5.2-8. Could you please give it a try?
Thanks.
Steven.
Hello Steven,
sorry to say, but "gl_batch" doesn't work with 0.5.2-8 either. My monitor shuts down, when X is started.
(console / vga=791)
[ 0.518898] vesafb: framebuffer at 0xd0000000, mapped to 0xf8080000, using 3072k, total 16384k
[ 0.518905] vesafb: mode is 1024x768x16, linelength=2048, pages=9
[ 0.518910] vesafb: protected mode interface info at c000:a31c
[ 0.518915] vesafb: pmi: set display start = c00ca3aa, set palette = c00ca46c
[ 0.518920] vesafb: scrolling: redraw
[ 0.518925] vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0...
[drm] GPU reset succeed (RBBM_STATUS=0x10000140)
[ 24.506939] [drm] Generation 2 PCI interface, using max accessible memory
[ 24.520921] [drm] radeon: VRAM 256M
[ 24.534801] [drm] radeon: VRAM from 0x00000000 to 0x0FFFFFFF
[ 24.548752] [drm] radeon: GTT 512M
[ 24.562358] [drm] radeon: GTT from 0x20000000 to 0x3FFFFFFF
[ 24.576170] radeon 0000:01:00.0: irq 25 for MSI/MSI-X
[ 24.576177] [drm] radeon: using MSI.
[ 24.589550] [drm] radeon: irq initialized.
[ 24.603049] [drm] Detected VRAM RAM=256M, BAR=256M
[ 24.604265] [drm] RAM width 128bits DDR
[ 24.605469] [TTM] Zone kernel: Available graphics memory: 439728 kiB.
[ 24.606634] [TTM] Zone highmem: Available graphics memory: 1557364 kiB.
[ 24.607806] [drm] radeon: 256M of VRAM memory ready
[ 24.608965] [drm] radeon: 512M of GTT memory ready.
[ 24.610094] [drm] GART: num cpu pages 131072, num gpu pages 131072
[ 24.612812] [drm] radeon: 1 quad pipes, 2 z pipes initialized.
[ 24.614010] [drm] PCIE GART of 512M enabled (table at 0x00040000).
[ 24.615156] [drm] radeon: cp idle (0x10000C03)
[ 24.616327] [drm] Loading R500 Microcode
[ 24.617723] platform radeon_cp.0: firmware: requesting radeon/R520_cp.bin
[ 24.640703] [drm] radeon: ring at 0x0000000020000000
[ 24.641924] [drm] ring test succeeded in 9 usecs
[ 24.643230] [drm] radeon: ib pool ready.
[ 27.156012] [drm:radeon_fence_wait] *ERROR* fence(f6636f00:0x00000001) 504ms timeout going to reset GPU
[ 27.158633] [drm] CP reset succeed (RBBM_STATUS=0x10000140)
[ 27.159849] [drm] radeon: cp idle (0x10000000)
[ 27.161089] [drm] radeon: ring at 0x0000000020000000
[ 27.162315] [drm] ring test succeeded in 8 usecs
[ 27.163501] [drm] GPU reset succeed (RBBM_STATUS=0x10000140)
[ 27.164696] [drm:radeon_fence_wait] *ERROR* fence(f6636f00:0x00000001) 520ms timeout
[ 27.165895] [drm:radeon_fence_wait] *ERROR* last signaled fence(0x00000001)
[ 27.330231] [drm:r100_ib_test] *ERROR* radeon: ib test failed (sracth(0x15E4)=0xCAFEDEAD)
[ 27.331649] radeon 0000:01:00.0: failled testing IB (-22).
[ 27.332912] radeon 0000:01:00.0: failled initializing IB (-22).
[ 27.334072] radeon 0000:01:00.0: Disabling GPU acceleration
[ 27.335298] [drm] radeon: cp finalized
[ 27.336485] radeon 0000:01:00.0: f7362600 unpin not necessary
[ 27.338356] [drm] Default TV standard: PAL
[ 27.340011] [drm] Radeon Display Connectors
[ 27.341153] [drm] Connector 0:
[ 27.342272] [drm] VGA
[ 27.343370] [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c
[ 27.344496] [drm] Encoders:
[ 27.345617] [drm] CRT1: INTERNAL_KLDSCP_DAC1
[ 27.346742] [drm] Connector 1:
[ 27.347854] [drm] Composite
[ 27.348973] [drm] Encoders:
[ 27.350080] [drm] TV1: INTERNAL_KLDSCP_DAC2
[ 27.351184] [drm] Connector 2:
[ 27.352275] [drm] DVI-I
[ 27.353338] [drm] HPD1
[ 27.354394] [drm] DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c
[ 27.355481] [drm] Encoders:
[ 27.356578] [drm] CRT2: INTERNAL_KLDSCP_DAC2
[ 27.357670] [drm] DFP1: INTERNAL_KLDSCP_TMDS1
[ 27.519799] [drm] fb mappable at 0xD0040000
[ 27.520901] [drm] vram apper at 0xD0000000
[ 27.521991] [drm] size 5242880
[ 27.523052] [drm] fb depth is 24
[ 27.524120] [drm] pitch is 5120
[ 27.525161] fb: conflicting fb hw usage radeondrmfb vs VESA VGA - removing generic driver
It seems, that graphic card and monitor do not come to a mutual agreement, what graphic mode should be used best. I had the same effect on my old laptop with ATI Mach64 graphic processor. DDC request gives nothing but manufacturer name and physical screen size (in pixels) of the TFT Display. So these informations might not be sufficient in this case.
On my desktop, there are much more appropriate common (vesa) graphic modes, but obviously none is used.
When I manually select vesa driver and the same resolution as in console mode (1024x768, 16bit color depth), everything works fine on both systems.
My thoughts are:
1. Is there any possibility to test in advance ( before X crashes), if graphic card and monitor will harmonize and show the desktop ?
2. If a test, due to item 1, is possible and the result should be negative, there should be an automatic switching to vesa 791 (1024x768, 16bit), so that hopefully the screen doesn't stay black.
3. If item 1 is not practicable, there should be parameter "gl_batch_v", which causes the system to activate or create an appropriate "Xorg.conf" for those, who do NOT want to select vesa 791 manually again and again.
BTW, old "radeon_drv.so" (4.3.0) worked like a charm for my desktop and old laptop.
Best Regards
cmdr
Hi Cmdr,
1. Is there any possibility to test in advance ( before X crashes), if graphic card and monitor will harmonize and show the desktop ?
2. If a test, due to item 1, is possible and the result should be negative, there should be an automatic switching to vesa 791 (1024x768, 16bit), so that hopefully the screen doesn't stay black.
3. If item 1 is not practicable, there should be parameter "gl_batch_v", which causes the system to activate or create an appropriate "Xorg.conf" for those, who do NOT want to select vesa 791 manually again and again.
So far I have no idea about how to make (1) or (2). As for (3), I think it's possible. However, I have to know your idea fully so that I can implement that. Or maybe you can create a patch file to make that?
BTW, I have uploaded gparted live 0.5.2-9 in the testing branch, maybe you can give it a try.
Steven.
GParted forum → Live Media → German keyboard layout with gl_kbd=de does not work
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 2 official extensions. Copyright © 2003–2009 PunBB.