Re: Russian Keyboard
Hello Joseph Is that problem specific to gnome ? If after dpkg-reconfigure xserver-xfree86 and selecting the russian keyboard does not work, you should ask the debian mailing liste for X, as the problem is likely to be non sparc specific ( you said it works fine in the console ) Manu Joseph Simantov a écrit : Hi Manu, I am using a 2.4 (the standard for 3.01). Please note that I have exactly the same problem when installing Aurora 1.92 or 2.0. Any advice would be much appreciated. Joseph --- Emmanuel Kasper [EMAIL PROTECTED] wrote: dpkg-reconfigure xserver-xfree86 ? Are you using a 2.4 or a 2.6 kernel ? Manu Joseph Simantov a �crit : Hi All, Can anybody please give me some advice on how to Russify an Ultra5/Debian 3.01 in Gnome?? While the Russian Menus and environment messages are displayed fine in Gnome, somehow I can't figure out the correct settings to switch the keyboard to Russian (It's a type5). On the other hand, the console works fine in Russian KOI-8... I suppose the settings are controlled by the 'Keyboard' entry in XF86Config-4, or am I wrong?? Any advice will be greatly appreciated! Joseph __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: 2.6.15-1-sparc64 issues on blade 100
On Feb 2, 2006, at 6:37 PM, Admar Schoonen wrote:
Dear Debian people,
I recently tried linux-image-2.6.15-1-sparc64 with an up to date
unstable on my
blade 100. I noticed a few issues:
1. Framebuffer is still a bit distorted. This is (or at least was)
a known
issue for recent kernels (bug id 317756). However, this bug is
closed, but
the problem still exists (at least on my blade 100). The
symptoms are that
some 'snow' or flickering occurs on the console when text is
scrolling and
Xorg will only start in 'low' refresh rates. The refresh rate
for 1400x1050
is 60 Hz, while for 2.6.9 kernels, I can run 1400x1050 @ 85 Hz.
Only at
1152x864 and lower, I can get 85 Hz refresh rates. Furthermore,
in all those
resolutions, some red dots appear, most notably when moving
windows.
A work around is to specify 'video=atyfb:off vga=normal', but
then the
console is slow, has no virtual consoles and my second mach64
card will not
be initialized (leaving me with just single head Xorg)
Am I the only one who still experiences this bug (ie:
flickering on console
and/or red dots in Xorg)?
Admar:
With regard to the video problems, you are welcome to try my fix to
the problem.
There were two problems I found, a missing flag
(M64F_SDRAM_MAGIC_PLL) and a bad clock rate
(230 instead of 235). Try applying some variation of the following
patch. This fix went to
2.6.16-rc1, but was partially overwritten by a subsequent patch.
Hopefully the full fix will
reappear shortly, and then the debian folks will pick it up.
If it does not fix your problem let me know; it means there is
likely something
wrong with my setup as well, and I just don't know it. If it does
help, let me know
so I can try harder to get it in for 2.6.16 final.
-- Luis, who likes his SB100
diff --git a/drivers/video/aty/atyfb_base.c b/drivers/video/aty/atyfb_base.c
index 485be38..3cd8d08 100644
--- a/drivers/video/aty/atyfb_base.c
+++ b/drivers/video/aty/atyfb_base.c
@@ -415,7 +415,7 @@ static struct {
{ PCI_CHIP_MACH64GN, 3D RAGE XC (Mach64 GN, AGP 2x), 230, 83, 63,
135, ATI_CHIP_264XL },
{ PCI_CHIP_MACH64GO, 3D RAGE XL (Mach64 GO, PCI-66), 230, 83, 63,
135, ATI_CHIP_264XL },
{ PCI_CHIP_MACH64GL, 3D RAGE XC (Mach64 GL, PCI-66), 230, 83, 63,
135, ATI_CHIP_264XL },
- { PCI_CHIP_MACH64GR, 3D RAGE XL (Mach64 GR, PCI-33), 230, 83, 63,
135, ATI_CHIP_264XL | M64F_SDRAM_MAGIC_PLL },
+ { PCI_CHIP_MACH64GR, 3D RAGE XL (Mach64 GR, PCI-33), 235, 83, 63,
135, ATI_CHIP_264XL | M64F_SDRAM_MAGIC_PLL },
{ PCI_CHIP_MACH64GS, 3D RAGE XC (Mach64 GS, PCI-33), 230, 83, 63,
135, ATI_CHIP_264XL },
{ PCI_CHIP_MACH64LM, 3D RAGE Mobility P/M (Mach64 LM, AGP 2x), 230,
83, 125, 135, ATI_CHIP_MOBILITY },
cd-rom not found
I recently purchased debian 3.1 for sparc platformsduring boot the cdrom is found but immediately after the install program search for devices it no longer knows about the cd-rom and keeps telling me the cd-rom is not found or the cd-rom is not in the tray/ I tried it on 2 boxes, sunfire v100 and my desktop blade 100
Re: cd-rom not found
On Wed, 8 Feb 2006 13:23:16 -0600 Donny Jekels [EMAIL PROTECTED] wrote: I recently purchased debian 3.1 for sparc platforms during boot the cdrom is found but immediately after the install program search for devices it no longer knows about the cd-rom and keeps telling me the cd-rom is not found or the cd-rom is not in the tray/ I tried it on 2 boxes, sunfire v100 and my desktop blade 100 You will have a lot more joy if you do a tftp boot and network install. There are a lot of issues with CD-based installs of 3.1 on those boxen. Regards, Ozz. pgp9Qi1AgZIU9.pgp Description: PGP signature
Re: cd-rom not found
On Wed, 2006-02-08 at 13:23 -0600, Donny Jekels wrote: I recently purchased debian 3.1 for sparc platforms during boot the cdrom is found but immediately after the install program search for devices it no longer knows about the cd-rom and keeps telling me the cd-rom is not found or the cd-rom is not in the tray/ I tried it on 2 boxes, sunfire v100 and my desktop blade 100 I just went through this just last week and finally got it to work. Here is what I did: I downloaded the netinstall iso and booted from it and choose the expert installation. At the point where it would search for the cdrom, scroll down and open a shell first. do a modprobe of the following modules: alim15x3 ide-cd ide-disk tulip Then check to see if /dev/cdrom points to a valid device. It should point into /dev/ide/.. This path should contain devices (down the directory tree a ways) for both your cd and your disks. You can even try mounting the cdrom to make sure that you can. Then exit the shell and continue on with the cdrom detection and installation. I have found that the cdrom driver in this configuration is not entirely reliable for heavy loads. Sometimes the cdrom will just lock up and I had to reset and reboot the machine again several times. Each time I would get a little further in the process until it completed. Once the system is installed the cd/dvd drive seems to be much more stable. Good luck. __ Spam Not spam Forget previous vote -- Daniel R. Bidwell | [EMAIL PROTECTED] Andrews University | Information Technology Services If two always agree, one of them is unnecessary Friends don't let friends do DOS In theory, theory and practice are the same. In practice, however, they are not. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
