Hi Vincent, "VV" == Vincent Vandeweijer writes:
VV> Yeah neat he, Xorg and a 2.4... try loggin in :) :) VV> Guess I had exactly the same problem. A totally wrong layout. I VV> found a modified keymap somewhere on the internet, can't remember VV> where. [...] yeah, thanks... i've also found some xkb/keycodes/sun maps on the net (for Xorg+linux2.4+type5 keyboard); but fortunately by now i don't need them anymore - i'm now happily running Linux 2.6.14 on sid (with Xorg) :-) (and on 2.6 this workaround is not needed). what i had to do: it was somewhat tricky to install the kernel package in the first place: i was running linux 2.4.27, and installing 2.6.14 was giving errors when creating initrd. i had to install 2.6.12 first, boot from there (and it was very helpful advice to use append="video=atyfb:off" in silo.conf because otherwise the screen was unusable even in text mode), and then install 2.6.14. in 2.6.12, text console worked great (except i had to reconfigure console-data to use KERNEL mapping, otherwose the keyboard was unusable even in text mode), but Xorg was crashing. i also tried 2.6.15-rc5 and Xorg also crashes there: i get traces in /var/log/messages like these: Dec 17 18:33:00 localhost kernel: Call Trace: Dec 17 18:33:00 localhost kernel: [0000000000440f58] copy_process+0x978/0xe60 Dec 17 18:33:00 localhost kernel: [0000000000441480] do_fork+0x40/0x1e0 Dec 17 18:33:00 localhost kernel: [0000000000407194] linux_sparc_syscall32+0x34/0x40 Dec 17 18:33:00 localhost kernel: [00000000701e7bfc] 0x701e7bfc Dec 17 18:33:00 localhost kernel: Call Trace: Dec 17 18:33:00 localhost kernel: [0000000000475e44] exit_mmap+0x64/0x160 Dec 17 18:33:00 localhost kernel: [000000000044054c] mmput+0x2c/0xc0 Dec 17 18:33:00 localhost kernel: [000000000048eb2c] flush_old_exec+0x18c/0x880 Dec 17 18:33:00 localhost kernel: [000000000042fe4c] load_elf_binary+0x3cc/0x15c0 Dec 17 18:33:00 localhost kernel: [000000000048f40c] search_binary_handler+0x8c/0x2a0 Dec 17 18:33:00 localhost kernel: [00000000004af21c] compat_do_execve+0x1dc/0x220 Dec 17 18:33:00 localhost kernel: [000000000042711c] sparc32_execve+0x3c/0xa0 Dec 17 18:33:00 localhost kernel: [0000000000407194] linux_sparc_syscall32+0x34/0x40 Dec 17 18:33:00 localhost kernel: [00000000701e7d68] 0x701e7d68 Dec 17 18:33:43 localhost kernel: Call Trace: Dec 17 18:33:43 localhost kernel: [0000000000476470] unmap_region+0x70/0x140 Dec 17 18:33:43 localhost kernel: [0000000000476b94] do_munmap+0x174/0x240 Dec 17 18:33:43 localhost kernel: [0000000000476c7c] sys_munmap+0x1c/0x40 Dec 17 18:33:43 localhost kernel: [0000000000407194] linux_sparc_syscall32+0x34/0x40 Dec 17 18:33:43 localhost kernel: [00000000007c6960] 0x7c6960 and "Invalid pty, process: Xorg ..." on the terminal... the X screen remains blank (and as if no switch to "graphics mode" was performed), but X and all apps continues to work etc... that was with 2.6.12 and 2.6.15-rc5.... i was lucky to decide to try 2.6.14, and it magically worked there!!! the keyboard works too. VV> I'll also link my xorg.confs here: VV> http://osiris.dyndns.info/stuff/xorg.conf - for my 2.6.12 kernel VV> http://osiris.dyndns.info/stuff/xorg.conf.2.4.kernel - yeah, VV> right. This one is the old conf for my 2.4.27 kernel. thanks! will try it out (now the only thing i'd like to do is to switch on the "video acceleration" if that's possible...). VV> Note that i'm using an Elite 3D. Not the onboard ati card. I VV> heard somewhere that the ati framebuffer in some 2.6 kernels was VV> at least to say buggy :( You'll need to change some parameters to VV> match my xorg.confs with your Creator 3D. yup. VV> Oh and that "0000:01:02.0 VGA compatible controller: ATI VV> Technologies Inc 3D Rage I/II" is not your Creator 3D card, at VV> least i think so. A Creator 3Dcard is not a pci card but an UPA VV> card (again, if i remember correct). It will not show up on VV> lspci. I guess it'll have an 13w3 connector and not a D-Sub like VV> most PC-type cards. Anyway... yup, right... i have Creator 3D inserted not in a PCI slot... and this machine has also an on-board ATI card (for video capturing)... VV> Hope it's of any help. your advices are very helpful, thanks a lot!!! Best, v. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]