Re: Console fonts SOLVED :-)

[rhkramer]

On Sunday, May 07, 2017 08:54:26 AM rhkra...@gmail.com wrote:
> On Sunday, May 07, 2017 08:49:13 AM rhkra...@gmail.com wrote:
> > ATM, I don't plan to try googling for them, but, having said that, after
> > I send this, I just might do that, as my curiosity is re-aroused.  If I
> > come across something, soon or further in the future, I'll try to post
> > it here.
> 
> Oh, try googling and/or searching ebay for ["video projector"
> cellphone]--you will get plenty of links to explore.

Oh, two things:

   * on ebay, I found a lot of things that I'll call "passive" projectors, 
which apparently consist of a cardboard box with a lens on the front (and 
maybe one or more mirrors)--designed to have a cellphone placed in the unit 
and then the image projected through the lens.  I would expect the image to be 
pretty dim.

   * here's a "non-passive" one that seems to have lots of inputs, can use 12 
VDC, etc.  (I've copied the specifications, below, and note that I picked this 
one randomly from ebay--it was one of the ones near the top of the search 
results):

60'' Multimedia Projector Home Cinema Theater HDMI VGA TV USB For PC Cellphone

http://www.ebay.com/itm/60-Multimedia-Projector-Home-Cinema-Theater-HDMI-VGA-
TV-USB-For-PC-Cellphone-/201423728262

I guess the fact that the native resolution is 640x480 but it can support 
1920x1080 means that the image is "interpolated" (right word?) down to 
640x480.  I suspect most of them work this way, but there may be exceptions.


Projection Technology   LCD
Native Resolution   VGA (640x480)
Supported Resolution1080P (1920x1080)
Input Voltage(V)100-240V，12V, 2000mA
Brightness(Lumens)  500
Brightness Range100 to 999 Lumens
Aspect Ratio4:3 and 16:9
Contrast Ratio  400:1
OSD Languages   Chinese, Russian, Portuguese, Italian, Spanish, German, 
French, English
Projection Screen Size (inch)   20-60 Inch
Projection Distance (m) 1.25-4M
Video Formats   3GP, MP4, H.264, MPEG, VOB, MOV, AVI
Audio Formats   ACC/ACC+, WAV, WMA, MP3
Picture Formats JPG, PNG, GIF, BMP, JPEG
Connectors  HDMI Input, SD Card Slot, USB, VGA Port, 3-in-1 AV In
Speakers Included   Yes, built-in

Re: Console fonts SOLVED :-)

[rhkramer]

On Sunday, May 07, 2017 08:49:13 AM rhkra...@gmail.com wrote:
> ATM, I don't plan to try googling for them, but, having said that, after I
> send this, I just might do that, as my curiosity is re-aroused.  If I come
> across something, soon or further in the future, I'll try to post it here.

Oh, try googling and/or searching ebay for ["video projector" cellphone]--you 
will get plenty of links to explore.

Re: Console fonts SOLVED :-)

[rhkramer]

On Sunday, May 07, 2017 06:23:00 AM GiaThnYgeia wrote:
> That is great news
> I am now wondering instead of 7-10" screens if there is a tiny battery
> powered projector out there that you can use with it, as my tired old
> eyes find even my 21" tiring :)

Well, I've never had one, but I have seen small portable projectors advertised 
at what seemed to be ridiculously low prices (and fairly low lumens)--I don't 
really remember lumens or prices, but I'm guessing that, because I thought 
they were ridiculously low they might have been around $50 or less and 400 
lumens or less (and maybe 640x480 or less).

At the time(s), I didn't pay any attention to whether they were battery 
operated or not, but a typical advertised "use case" was to take to a customer 
site to show a video to one or a small group of (potential) customers.

ATM, I don't plan to try googling for them, but, having said that, after I 
send this, I just might do that, as my curiosity is re-aroused.  If I come 
across something, soon or further in the future, I'll try to post it here.

Re: Console fonts SOLVED :-)

[GiaThnYgeia]

That is great news
I am now wondering instead of 7-10" screens if there is a tiny battery
powered projector out there that you can use with it, as my tired old
eyes find even my 21" tiring :)

Now debian can add udoo to their architecture list from 9 onwards.

2 thumbs up

Larry Dighera:
> I gave up on Jessie, and installed Stretch as you and others in the 
> debian-users mailing list advised. 
> 
> Installing Debian Stretch (testing) from this link: 
> 
>  on the Udoo X86 required placing the rtl8168g-2.fw driver in the root 
> directory of the USB ISO installation medium to support the Edimax Nano 
> 150Mbps Wireless 802.11b/g/n USB Adapter. 
> The driver was downloaded from this page:
>  https://packages.debian.org/source/stretch/firmware-nonfree
>   
> http://http.debian.net/debian/pool/non-free/f/firmware-nonfree/firmware-nonfree_20161130.orig.tar.xz
> 
> The specific 'rtl8168g-2.fw' driver required was extracted from the 
> compressed tar archive with 7-Zip.
> 
> Stretch runs great! 
> 

-- 
 "The most violent element in society is ignorance" rEG

"Who died and made you the superuser?"  Brooklinux

"keep rocking in the non-free world" Neilznotyoung

Console fonts SOLVED :-)

[Larry Dighera]

I gave up on Jessie, and installed Stretch as you and others in the 
debian-users mailing list advised. 

Installing Debian Stretch (testing) from this link: 

 on the Udoo X86 required placing the rtl8168g-2.fw driver in the root 
directory of the USB ISO installation medium to support the Edimax Nano 150Mbps 
Wireless 802.11b/g/n USB Adapter. 
The driver was downloaded from this page:
 https://packages.debian.org/source/stretch/firmware-nonfree
  
http://http.debian.net/debian/pool/non-free/f/firmware-nonfree/firmware-nonfree_20161130.orig.tar.xz

The specific 'rtl8168g-2.fw' driver required was extracted from the compressed 
tar archive with 7-Zip.

Stretch runs great! 

Re: Console fonts

[David Wright]

On Wed 03 May 2017 at 10:08:42 (-0700), Larry Dighera wrote:
> On Tue, 2 May 2017 20:22:01 -0500, David Wright  
> wrote:
> >On Tue 02 May 2017 at 12:20:01 (-0700), Larry Dighera wrote:
> >
> >> Yes.  It's a new single-board computer platform that began shipping ~April
> >> 14, 2017.  I can personally confirm that Tails Linux X11 runs fine on this
> >> platform, and the manufacturer (Udoo) claims to have successfully installed
> >> Debian.  
> >[...]
> >> Given the Udoo team claims to have installed Debian on their hardware, and
> >> Tails Linux runs on it, I'd prefer to sort out the issues, and see if I
> >> (we?) can effect a useable system.
> >
> >I'm sorry if everyone knows which Debian (jessie, stretch, sid)
> >and kernel version that the Udoo team installed. My deduction
> >from the lines above was that the OP ran Tails¹, not that the
> >Udoo team ran Tails.
> >
> 
> That is correct.  I apologize for any ambiguity.

No blame intended. I received a private email to which this was a
general reply. The ambiguity is elsewhere.

> While I am currently unable to locate the post asserting the Udoo team
> successfully installed Jessie, this post from a Udoo user alludes to a
> successful Jessie install:
> http://www.udoo.org/forum/threads/no-audio-output-on-linux-over-hdmi.6803/
> 
> On the other hands, there is a user also encountering the blank-screen
> syndrome with Jessie on the Udoo X86 platform:
> http://www.udoo.org/forum/threads/linux-xfce-debian-jessie-blank-screen.6854/
> 
> And another who found stretch more stable than Jessie:
> http://www.udoo.org/forum/threads/debian-jessie-linux-os-installation.6819/#post-26261
> 
> I believe this may have been where I saw the mention of Debian on the Udoo
> X86 platform: http://www.udoo.org/docs-x86/Software_&_OS_Distro/Linux.html
> 
> When/if I receive a response to my inquiry from the Udoo support team
> regarding which Jessie distribution they installed, I'll post it here.
> 
> Larry
> 
> PS: It is the integrated Arduino hardware and very low power requirement
> that make this new platform interesting to me for portable/battery-power
> use.  

I'm just watching this to see if it's a cheap way of getting some
up-to-date hardware now I've stopped moving house for a while.
While jessie has delivered some new functionality on my old hardware
(but also lost some), it hasn't delivered any appreciable speed gain.

Cheers,
David.

Re: Console fonts

[David Wright]

On Wed 03 May 2017 at 09:31:37 (-0700), Larry Dighera wrote:
> On Tue, 2 May 2017 18:46:34 -0500, David Wright  
> wrote:
> >On Tue 02 May 2017 at 12:20:01 (-0700), Larry Dighera wrote:
> >> Release-critical bugs status
> >> 
> >> Tue May 2 17:00:00 UTC 2017
> >> 
> >> Total number of release-critical bugs: 1649
> >> Number that have a patch: 271
> >> Number that have a fix prepared and waiting to upload: 38
> >> Number that are being ignored: 78
> >> Number concerning the current stable release: 699
> >> Number concerning the next release: 149
> >> 
> >> 
> >> The reason for installing Debian was because I have been impressed with its
> >> stability and few update issues compared to other Linux flavors I've used,
> >> so I was/am reluctant to overwrite Jessie with Stretch.
> >
> >Scaling up the words of that ridiculous advert:
> >699 (stable/jessie) is greater than 149 (testing/stretch).
> >
> >But, seriously, those figures need a lot of interpreting.
> >
> 
> Are you intimating that the current stable Debian release (Jessie) contains
> ~4.5 times the number of release-critical bugs of stretch!?  

That's right…and this ratio will increase until stretch is released.
If you look at the full history graph at
https://bugs.debian.org/release-critical/graph.png
you can see that as any release date approaches, the green line
(testing) falls (developers are squashing bugs in preparation for
release), but the blue line (stable) rises (bugs are still being
found). Security bugs get fixed in stable, but other bugs might
not be. If they get fixed in the upstream version, the status of
stable (it stays the same) prevents their upgrading and may
prevent their inclusion entirely.

Some background on bugs:

https://www.debian.org/Bugs/Developer#severities
https://release.debian.org/testing/rc_policy.txt
https://people.debian.org/~vorlon/rc-bugsquashing.html

> >> Given the Udoo team claims to have installed Debian on their hardware, and
> >> Tails Linux runs on it, I'd prefer to sort out the issues, and see if I
> >> (we?) can effect a useable system.
> >
> >Reference? It's worth posting exactly what they installed;
> >distribution, kernel version, etc.
> >
> 
> I have submitted that question to the Udoo support team, and am awaiting a
> response. 
> 
> Also, there is a post here
> http://www.udoo.org/forum/threads/debian-jessie-linux-os-installation.6819/#post-26261
> that indicates that "Debian Stretch
> (debian-stretch-DI-rc3-amd64-xfce-CD-1.iso from
> [https://cdimage.debian.org/mirror/cdimage/stretch_di_rc3/amd64/iso-cd/]) is
> working much better for me than Jessie..."

Yes, that post was what made me ask. I assume that ♂ is an ordinary
user from their joining date; prolific though. (Nice aeroplane, BTW.)

Cheers,
David.

Re: Console fonts

[Felix Miata]

Larry Dighera composed on 2017-05-03 10:08 (UTC-0700):
...
> I believe this may have been where I saw the mention of Debian on the Udoo
> X86 platform: http://www.udoo.org/docs-x86/Software_&_OS_Distro/Linux.html

Quoting from there:

"Heads up! The processors of the UDOO X86 and the Wi-Fi/BT module are released
only few time ago so we suggest to use a recent distribution to find all the
latest drivers already installed and have all the devices operating properly."

Originally released ~24 months ago, Jessie is the oldest most recent "stable"
release among the top 25 in Distrowatch's page hit ranking.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: Console fonts

[Larry Dighera]

On Tue, 2 May 2017 20:22:01 -0500, David Wright 
wrote:

>On Tue 02 May 2017 at 12:20:01 (-0700), Larry Dighera wrote:
>
>> Yes.  It's a new single-board computer platform that began shipping ~April
>> 14, 2017.  I can personally confirm that Tails Linux X11 runs fine on this
>> platform, and the manufacturer (Udoo) claims to have successfully installed
>> Debian.  
>[...]
>> Given the Udoo team claims to have installed Debian on their hardware, and
>> Tails Linux runs on it, I'd prefer to sort out the issues, and see if I
>> (we?) can effect a useable system.
>
>I'm sorry if everyone knows which Debian (jessie, stretch, sid)
>and kernel version that the Udoo team installed. My deduction
>from the lines above was that the OP ran Tails¹, not that the
>Udoo team ran Tails.
>

That is correct.  I apologize for any ambiguity.

>
>Hence my thinking that there might be a reference to what the
>Udoo team installed that I (and perhaps others) hadn't seen.
>Sorry to mystify anyone.
>
>¹
>http://distrowatch.com/table.php?distribution=tails
>
>Cheers,
>David.

While I am currently unable to locate the post asserting the Udoo team
successfully installed Jessie, this post from a Udoo user alludes to a
successful Jessie install:
http://www.udoo.org/forum/threads/no-audio-output-on-linux-over-hdmi.6803/

On the other hands, there is a user also encountering the blank-screen
syndrome with Jessie on the Udoo X86 platform:
http://www.udoo.org/forum/threads/linux-xfce-debian-jessie-blank-screen.6854/

And another who found stretch more stable than Jessie:
http://www.udoo.org/forum/threads/debian-jessie-linux-os-installation.6819/#post-26261

I believe this may have been where I saw the mention of Debian on the Udoo
X86 platform: http://www.udoo.org/docs-x86/Software_&_OS_Distro/Linux.html

When/if I receive a response to my inquiry from the Udoo support team
regarding which Jessie distribution they installed, I'll post it here.

Larry

PS: It is the integrated Arduino hardware and very low power requirement
that make this new platform interesting to me for portable/battery-power
use.  

Re: Console fonts

[Larry Dighera]

On Tue, 2 May 2017 18:46:34 -0500, David Wright 
wrote:

>On Tue 02 May 2017 at 12:20:01 (-0700), Larry Dighera wrote:
>> On Sun, 30 Apr 2017 21:34:14 -0400, Felix Miata  
>> wrote:
>> >
>> >Even if OP can get the ttys working to his liking, I still think it's very
>> >likely a lost cause trying to use Jessie on his hardware. Stretch is very 
>> >near
>> >ready to release, and probably OP's better next move.
>> >
>> 
>> In this message thread:
>> http://www.udoo.org/forum/threads/debian-jessie-linux-os-installation.6819/
>> others have also suggested Stretch.  I looked at the existing bugs:
>> https://bugs.debian.org/release-critical/other/testing.html
>> https://bugs.debian.org/release-critical/
>> 
>> Release-critical bugs status
>> 
>> Tue May 2 17:00:00 UTC 2017
>> 
>> Total number of release-critical bugs: 1649
>> Number that have a patch: 271
>> Number that have a fix prepared and waiting to upload: 38
>> Number that are being ignored: 78
>> Number concerning the current stable release: 699
>> Number concerning the next release: 149
>> 
>> 
>> The reason for installing Debian was because I have been impressed with its
>> stability and few update issues compared to other Linux flavors I've used,
>> so I was/am reluctant to overwrite Jessie with Stretch.
>
>Scaling up the words of that ridiculous advert:
>699 (stable/jessie) is greater than 149 (testing/stretch).
>
>But, seriously, those figures need a lot of interpreting.
>

Are you intimating that the current stable Debian release (Jessie) contains
~4.5 times the number of release-critical bugs of stretch!?  

>
>> Given the Udoo team claims to have installed Debian on their hardware, and
>> Tails Linux runs on it, I'd prefer to sort out the issues, and see if I
>> (we?) can effect a useable system.
>
>Reference? It's worth posting exactly what they installed;
>distribution, kernel version, etc.
>

I have submitted that question to the Udoo support team, and am awaiting a
response. 

Also, there is a post here
http://www.udoo.org/forum/threads/debian-jessie-linux-os-installation.6819/#post-26261
that indicates that "Debian Stretch
(debian-stretch-DI-rc3-amd64-xfce-CD-1.iso from
[https://cdimage.debian.org/mirror/cdimage/stretch_di_rc3/amd64/iso-cd/]) is
working much better for me than Jessie..."

>
>Cheers,
>David.

Thank you for your interest in this issue, and your kind support.

Best regards,
Larry

Re: Console fonts

[David Wright]

On Tue 02 May 2017 at 12:20:01 (-0700), Larry Dighera wrote:

> Yes.  It's a new single-board computer platform that began shipping ~April
> 14, 2017.  I can personally confirm that Tails Linux X11 runs fine on this
> platform, and the manufacturer (Udoo) claims to have successfully installed
> Debian.  
[...]
> Given the Udoo team claims to have installed Debian on their hardware, and
> Tails Linux runs on it, I'd prefer to sort out the issues, and see if I
> (we?) can effect a useable system.

I'm sorry if everyone knows which Debian (jessie, stretch, sid)
and kernel version that the Udoo team installed. My deduction
from the lines above was that the OP ran Tails¹, not that the
Udoo team ran Tails.

Hence my thinking that there might be a reference to what the
Udoo team installed that I (and perhaps others) hadn't seen.
Sorry to mystify anyone.

¹
http://distrowatch.com/table.php?distribution=tails

Cheers,
David.

Re: Console fonts

[David Wright]

On Tue 02 May 2017 at 12:20:01 (-0700), Larry Dighera wrote:
> On Sun, 30 Apr 2017 21:34:14 -0400, Felix Miata  wrote:
> >
> >Even if OP can get the ttys working to his liking, I still think it's very
> >likely a lost cause trying to use Jessie on his hardware. Stretch is very 
> >near
> >ready to release, and probably OP's better next move.
> >
> 
> In this message thread:
> http://www.udoo.org/forum/threads/debian-jessie-linux-os-installation.6819/
> others have also suggested Stretch.  I looked at the existing bugs:
> https://bugs.debian.org/release-critical/other/testing.html
> https://bugs.debian.org/release-critical/
> 
> Release-critical bugs status
> 
> Tue May 2 17:00:00 UTC 2017
> 
> Total number of release-critical bugs: 1649
> Number that have a patch: 271
> Number that have a fix prepared and waiting to upload: 38
> Number that are being ignored: 78
> Number concerning the current stable release: 699
> Number concerning the next release: 149
> 
> 
> The reason for installing Debian was because I have been impressed with its
> stability and few update issues compared to other Linux flavors I've used,
> so I was/am reluctant to overwrite Jessie with Stretch.

Scaling up the words of that ridiculous advert:
699 (stable/jessie) is greater than 149 (testing/stretch).

But, seriously, those figures need a lot of interpreting.

> Given the Udoo team claims to have installed Debian on their hardware, and
> Tails Linux runs on it, I'd prefer to sort out the issues, and see if I
> (we?) can effect a useable system.

Reference? It's worth posting exactly what they installed;
distribution, kernel version, etc.

Cheers,
David.

Re: Console fonts

[Felix Miata]

Larry Dighera composed on 2017-05-02 12:20 (UTC-0700):
...
>>Possibly Grub could be reconfigured to make a
>>lesser mode like 1440x900 or less explicit. 

> I'm willing to edit grub, if you're willing to provide specific
> instructions.  Unfortunately, my Unix experience predates grub (AT Unix
> SVR3 ~1994).

In general, this is enough howto:
https://askubuntu.com/questions/19486/how-do-i-add-a-kernel-boot-parameter

When I want 1440x900 as the mode on my Jessie ttys, I append as instructed 
there:

video=1440x900@60

The result is that

# fbset; inxi -G

reports mode 1440x900 using 180 columns and 56 rows. That won't produce a tty
result you can appreciate before your missing /dev/fb0 problem is solved, but is
the manner in which troubleshooting parameters can be supplied to the kernel in
attempting to identify solutions to video (and other) problems.

>>Lack of /dev/dri/card0 explains why
>>X doesn't work, the kernel found no supported gfx device.

> It sounds like you've discovered the root cause of the issue.  I failed to
> find /dev/dri let alone card0.  I have no idea what this means.
Technically, I don't either, but the gist as I understand it is that you have
video hardware that pure Jessie does not support.

DRI is Direct Rendering Infrastructure, just one of a multitude of software bits
that comprise working video on a Linux PC.

>>When I boot an Intel video Jessie PC with no video parameters on cmdline,
>>root=LABEL=deb8jessie plymouth.enable=0 noresume

> ???

That shows the cmdline from that boot included no video parameters other than
one to disable Plymouth functionality.

To find out what video parameters were on your cmdline on current boot, do:

# cat /proc/cmdline

>>I've seen nothing in thread explicitly explaining why he has no /dev/fb0, but
>>unless and until /dev/fb0 exists, ttys are stuck in 80x25. Maybe that is
>>something installing a working Plymouth can fix. I don't know, as I never use
>>Plymouth, and suspect it would also be victim of unsupported hardware.

> I did install Plymouth: apt-get install Plymouth.  It didn't seem to make
> any noticeable change.  (There are some Plymouth entries in daemon.log and
> syslog.)  Subsequently running lightdm still yields a black display screen.

Since it didn't help, and unless you have reason to think you might want or need
Plymouth in the future, I recommend keeping your Jessie simpler by reversing the
process:

# apt-get purge plymouth

> Given the Udoo team claims to have installed Debian on their hardware, and
> Tails Linux runs on it, I'd prefer to sort out the issues, and see if I
> (we?) can effect a useable system.
I seriously doubt Udoo's team installed pure Debian Jessie on the hardware you
have. Tails 2.12 uses the same Xorg version as Jessie (1.16.4), but with
approximately the same kernel as Debian Stretch (4.9 vs 4.9.13). This suggests
Jessie might work for you if you enable backports and install a linux-image much
newer than Jessie's 3.16. To enable backports, see:

https://wiki.debian.org/Backports

Once enabled you can check availability before choosing whether or which to 
install:

# apt-cache search linux-image
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: Console fonts

[Larry Dighera]

Hello Felix,

Thank you for your informative response to my issue.

My comments in-line below:


On Sun, 30 Apr 2017 21:34:14 -0400, Felix Miata 
wrote:

>Larry Dighera composed on 2017-04-30 16:40 (UTC-0700):
>[...]
>Previously, in OP https://lists.debian.org/debian-user/2017/04/msg00534.html :
>http://www.udoo.org/
>***
>   Without anything there indicating date of release, that URI strongly 
> suggests
>to me nevertheless that his hardware is newer than Jessie can be expected to
>support.
>

Yes.  It's a new single-board computer platform that began shipping ~April
14, 2017.  I can personally confirm that Tails Linux X11 runs fine on this
platform, and the manufacturer (Udoo) claims to have successfully installed
Debian.  

Specs are here: http://www.udoo.org/new-resources-udoo-x86/
Intel® Celeron® N3160, Quad Core @1.6GHz (Turbo Boost 2.24GHz), 2MB
Cache, 6W TDP.
Integrated Intel® HD Graphics controller
Three independent display support
HW decoding of HEVC(H.265), H.264, MPEG2, MVC, VC-1, VP8, WMV9,
JPEG/MJPEG formats
HW encoding of H.264, MVC and JPEG/MPEG formats
Video Interfaces
HDMI connector
2 x miniDP++ connectors
Video Resolution
Up to 3840 x 2160 24bpp @ 30Hz, 2560 x 1600 24bpp @60Hz
CIR (Consumer InfraRed) Sensor
Arduino 101 compatible shield
Integrated 6-axis combo sensor with accelerometer and gyroscope


Here is data from Debian Jessie on the Udoo X86 platform:

--- System Information
Kernel name:Linux 
Network node Hostname:  UdooX86Debian 
Kernel release: 3.16.0-4-amd64 
Kernel version: #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) x86_64 GNU/Linux
Machine hardware name:   
Operating system:   

--- OS Release ---
PRETTY_NAME="Debian GNU/Linux 8 (jessie)"
NAME="Debian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=debian
HOME_URL="http://www.debian.org/;
SUPPORT_URL="http://www.debian.org/support;
BUG_REPORT_URL="https://bugs.debian.org/;

  CPU Information -
Architecture:  x86_64
CPU op-mode(s):32-bit, 64-bit
Byte Order:Little Endian
CPU(s):4
On-line CPU(s) list:   0-3
Thread(s) per core:1
Core(s) per socket:4
Socket(s): 1
NUMA node(s):  1
Vendor ID: GenuineIntel
CPU family:6
Model: 76
Model name:Intel(R) Celeron(R) CPU  N3160  @ 1.60GHz
Stepping:  4
CPU MHz:   499.800
CPU max MHz:   2332.3999
CPU min MHz:   499.8000
BogoMIPS:  3199.86
Virtualization:VT-x
L1d cache: 24K
L1i cache: 32K
L2 cache:  1024K
NUMA node0 CPU(s): 0-3
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 76
model name  : Intel(R) Celeron(R) CPU  N3160  @ 1.60GHz
stepping: 4
microcode   : 0x40a
cpu MHz : 499.800
cache size  : 1024 KB
physical id : 0
siblings: 4
core id : 0
cpu cores   : 4
apicid  : 0
initial apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 11
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology
nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3
cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand
lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept
vpid tsc_adjust smep erms
bogomips: 3199.86
clflush size: 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

processor   : 1
vendor_id   : GenuineIntel
cpu family  : 6
model   : 76
model name  : Intel(R) Celeron(R) CPU  N3160  @ 1.60GHz
stepping: 4
microcode   : 0x40a
cpu MHz : 499.800
cache size  : 1024 KB
physical id : 0
siblings: 4
core id : 1
cpu cores   : 4
apicid  : 2
initial apicid  : 2
fpu : yes
fpu_exception   : yes
cpuid level : 11
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology
nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3
cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand
lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept
vpid tsc_adjust smep erms
bogomips: 3199.86
clflush size: 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

processor   : 2
vendor_id   : GenuineIntel
cpu family  : 6
model   : 76
model name  : Intel(R) 

Re: Console fonts, was Re: Jessie for Udoo X86?

[David Wright]

On Sun 30 Apr 2017 at 16:40:49 (-0700), Larry Dighera wrote:
> 
> Hello David,
> 
> Thank you very much for taking the time to educate me about this display
> issue.
> 
> My comments in-line below:
> 
> 
> On Sun, 23 Apr 2017 22:19:47 -0500, David Wright <deb...@lionunicorn.co.uk>
> wrote:
> 
> >On Sun 23 Apr 2017 at 18:55:03 (-0700), Larry Dighera wrote:
> >
> >> I'd like to have more lines/rows and columns on the console tty.  I've read
> >> that 'vidcontrol' may do what I want, unfortunately 'apt-cache show
> >> vidcontrol' reports that it is virtual (unavailable).  
> >> 
> >> I am grateful for any clues you may be able to provide.
> >
> >Best to start a new thread with a new subject, but anyway…
> >
> >The Debian Way to set a default font for dmesg output, login prompt,
> >etc is (I think) to edit /etc/default/console-setup
> >I like Terminus fonts (package console-setup-linux, I think),
> >so I have:
> >
> >ACTIVE_CONSOLES="/dev/tty[1-6]"
> >CHARMAP="UTF-8"
> >CODESET="Lat15"
> >#FONTFACE="Fixed"
> >FONTFACE="Terminus"
> >FONTSIZE="10x20"
> >#FONTSIZE="12x24"
> >#FONTSIZE="14x28"
> >#FONTSIZE="16x32"
> >VIDEOMODE=
> >
> >in there, with various sizes available.
> >
> 
> The default console display size is 80 columns by 25 rows.  
> 
> Setting FONTFACE="Terminus" and FONTSIZE="12x6", in the hope reducing the
> font size from 10x20 would result in getting more characters on the console
> display, I found it didn't change anything.  I presume the 12 in 12x6 refers
> to the height of the character matrix block, and the 6 the width, so if
> that's correct it should permit about three times as many characters in a
> row.  

I think the cause may be explained in the earlier reply to this post.
I've not really played with the framebuffer specifications.

> I read the console-setup manual pages, and noticed SCREEN_WIDTH and
> SCREEN_HEIGHT mentioned, so I put SCREEN_WIDTH="50" in the
> /etc/default/console-setup file as a test to see if my edits were able to
> effect some viable change in the console display.  Upon reboot, indeed the
> screen was set to 50 columns, so I did a 'stty columns 80', and it was
> restored to the default 80x25 size.

As it says, these variables can only reduce the width used by default,
not increase it. I've never used them. I just set the fontsize and
then record the resulting size with COLUMNS/LINES for future reference.

> I suspect the failure to see any change when specifying FONTSIZE="12x6" was
> probably a result of a limitation of the Udoo X86's Intel HD-graphics
> display hardware limitations or the BIOS or something.

That may be the case.

> I found that 'setupcon' would cause the system to re-read the
> /etc/default/console-setup file, so I could test edits without rebooting.

If you're editing that file to make changes, then yes. But I
don't like using setupcon because I usually have an X server running,
which can interfere with things. (I might be maligning it; it could
be keyboard changes which interfere, I don't remember.)

> The 'setfont' command does appear to be an alternate method of loading
> console fonts.  But, it's difficult to know what valid arguments might be
> for my system.

That's why I posted my-font-usr-share-consolefonts which gives
the location of the possible files you can use. Just look through
/usr/share/consolefonts/

> I tried the 'resizecons' command with -lines 132, and indeed there was some
> change, however the screen was unreadable.  The resizecons man page is very
> terse.  
> 
> So, after much experimentation and frustration, I'm afraid I've failed to
> increase the amount of information that can be displayed on the console
> screen.  Oh well...  
> 
> I am very grateful for your kind assistance, David.  And I'm willing to keep
> trying if you are.  :-)
> >
> >However, I prefer using aliases like:
> >
> >alias my-font-tiny="setfont Lat15-Terminus12x6"
> >alias my-font-small="setfont Lat15-Terminus14"
> >alias my-font-medium="setfont Lat15-Terminus20x10"
> >alias my-font-large="setfont Lat15-Terminus24x12"
> >alias my-font-huge="setfont Lat15-Terminus28x14"
> >alias my-font-vast="setfont Lat15-Terminus32x16"
> >
> >because you can then have different font sizes on each VC.
> >I also have a bash function to choose an arbitrary font:
> >
> >function my-font-usr-share-consolefonts {
> >[ -z "$1" ] && printf '%s\n' "Usage:

Re: Console fonts

[Felix Miata]

Larry Dighera composed on 2017-04-30 16:40 (UTC-0700):
[...]
Previously, in OP https://lists.debian.org/debian-user/2017/04/msg00534.html :
http://www.udoo.org/
***
Without anything there indicating date of release, that URI strongly 
suggests
to me nevertheless that his hardware is newer than Jessie can be expected to
support.

GiaThnYgeia later wrote:
$ inxi -c10 -v3
Will list basic system info and hardware
***
I found nothing in the archive or on original reading of the thread 
responding
to this, but then later I did see OP wrote:

Intel quad-core Celeron N3160
2.24 GHz & Intel® Quark SE core 32 MHz plus 32-bit ARC core 32 MHz, Intel HD
Graphics 400 Up to 640 MHz 12 execution units, 4 GB DDR3L Dual Channel RAM
and 32GB eMMC Storage
***
This supports my suspicion. Later, OP provided logs, which contained:

Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64
root=UUID=f0748180-a596-4f02-85d8-34b09b57cb42 ro quiet
(EE) open /dev/dri/card0: No such file or directory
(EE) open /dev/dri/card0: No such file or directory
(EE) open /dev/fb0: No such file or directory
(EE) open /dev/fb0: No such file or directory
(EE) Screen 0 deleted because of no matching config section.
(EE) Screen 0 deleted because of no matching config section.
***
These support my suspicion, and explain why his ttys are stuck in 80x25 
mode,
unresponsive to later instruction from David Wright. Lack of /dev/fb0 is a not
unusual pre-KMS result from a kernel cmdline (from the selected Grub stanza, as
modified, if modified) that lacks anything telling the kernel not to enable
framebuffer, resulting in use of 80x25 text mode on the ttys. Since Jessie's
3.16 kernel does support KMS, his 1920x1080 Samsung SyncMaster display's native
mode should be picked up by KMS, but that depends on the kernel supporting his
Intel HD Graphics 400 device. Possibly Grub could be reconfigured to make a
lesser mode like 1440x900 or less explicit. Lack of /dev/dri/card0 explains why
X doesn't work, the kernel found no supported gfx device.

When I boot an Intel video Jessie PC with no video parameters on cmdline,
root=LABEL=deb8jessie plymouth.enable=0 noresume
I see kernel messages begin in 80x25 mode, after which the kernel figures out
the display's native mode and switches to it, resulting in ttys producing 210
columns by 65 rows.
# inxi -c0 -G
Graphics:  Card: Intel 82945G/GZ Integrated Graphics Controller
   Display Server: X.org 1.16.4 drivers: intel (unloaded: fbdev,vesa)
   tty size: 210x65 Advanced Data: N/A for root out of X

When I reboot same PC with framebuffer disabled to emulate OP's boot condition 
thus,
root=LABEL=deb8jessie plymouth.enable=0 noresume nomodeset
# ls -l /dev/fb*
ls: cannot access /dev/fb*: No such file or directory
the ttys stay in 80x25 mode:
# inxi -c0 -G
Graphics:  Card: Intel 82945G/GZ Integrated Graphics Controller
   Display Server: X.org 1.16.4 drivers: intel (unloaded: fbdev,vesa)
   tty size: 80x25 Advanced Data: N/A for root out of X

I've seen nothing in thread explicitly explaining why he has no /dev/fb0, but
unless and until /dev/fb0 exists, ttys are stuck in 80x25. Maybe that is
something installing a working Plymouth can fix. I don't know, as I never use
Plymouth, and suspect it would also be victim of unsupported hardware.

Even if OP can get the ttys working to his liking, I still think it's very
likely a lost cause trying to use Jessie on his hardware. Stretch is very near
ready to release, and probably OP's better next move.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: Console fonts, was Re: Jessie for Udoo X86?

[Larry Dighera]

Hello David,

Thank you very much for taking the time to educate me about this display
issue.

My comments in-line below:


On Sun, 23 Apr 2017 22:19:47 -0500, David Wright <deb...@lionunicorn.co.uk>
wrote:

>On Sun 23 Apr 2017 at 18:55:03 (-0700), Larry Dighera wrote:
>
>> I'd like to have more lines/rows and columns on the console tty.  I've read
>> that 'vidcontrol' may do what I want, unfortunately 'apt-cache show
>> vidcontrol' reports that it is virtual (unavailable).  
>> 
>> I am grateful for any clues you may be able to provide.
>
>Best to start a new thread with a new subject, but anyway…
>
>The Debian Way to set a default font for dmesg output, login prompt,
>etc is (I think) to edit /etc/default/console-setup
>I like Terminus fonts (package console-setup-linux, I think),
>so I have:
>
>ACTIVE_CONSOLES="/dev/tty[1-6]"
>CHARMAP="UTF-8"
>CODESET="Lat15"
>#FONTFACE="Fixed"
>FONTFACE="Terminus"
>FONTSIZE="10x20"
>#FONTSIZE="12x24"
>#FONTSIZE="14x28"
>#FONTSIZE="16x32"
>VIDEOMODE=
>
>in there, with various sizes available.
>

The default console display size is 80 columns by 25 rows.  

Setting FONTFACE="Terminus" and FONTSIZE="12x6", in the hope reducing the
font size from 10x20 would result in getting more characters on the console
display, I found it didn't change anything.  I presume the 12 in 12x6 refers
to the height of the character matrix block, and the 6 the width, so if
that's correct it should permit about three times as many characters in a
row.  

I read the console-setup manual pages, and noticed SCREEN_WIDTH and
SCREEN_HEIGHT mentioned, so I put SCREEN_WIDTH="50" in the
/etc/default/console-setup file as a test to see if my edits were able to
effect some viable change in the console display.  Upon reboot, indeed the
screen was set to 50 columns, so I did a 'stty columns 80', and it was
restored to the default 80x25 size.

I suspect the failure to see any change when specifying FONTSIZE="12x6" was
probably a result of a limitation of the Udoo X86's Intel HD-graphics
display hardware limitations or the BIOS or something.

I found that 'setupcon' would cause the system to re-read the
/etc/default/console-setup file, so I could test edits without rebooting.   

The 'setfont' command does appear to be an alternate method of loading
console fonts.  But, it's difficult to know what valid arguments might be
for my system.

I tried the 'resizecons' command with -lines 132, and indeed there was some
change, however the screen was unreadable.  The resizecons man page is very
terse.  

So, after much experimentation and frustration, I'm afraid I've failed to
increase the amount of information that can be displayed on the console
screen.  Oh well...  

I am very grateful for your kind assistance, David.  And I'm willing to keep
trying if you are.  :-)



>
>However, I prefer using aliases like:
>
>alias my-font-tiny="setfont Lat15-Terminus12x6"
>alias my-font-small="setfont Lat15-Terminus14"
>alias my-font-medium="setfont Lat15-Terminus20x10"
>alias my-font-large="setfont Lat15-Terminus24x12"
>alias my-font-huge="setfont Lat15-Terminus28x14"
>alias my-font-vast="setfont Lat15-Terminus32x16"
>
>because you can then have different font sizes on each VC.
>I also have a bash function to choose an arbitrary font:
>
>function my-font-usr-share-consolefonts {
>[ -z "$1" ] && printf '%s\n' "Usage: $FUNCNAME 
> /usr/share/consolefonts/.psf.gz
>sets the specified font on the current VC.
>The command name serves as a reminder of the fonts' location.
>Use filename-completion to specify the appropriate filename.
>Redundant elements of the filename are stripped out before use.
>Typically, filenames start Lat15- or Uni." >&2 && return 1
>local FILENAME="$(basename "$1")"
>setfont "${FILENAME%%.*}"
>}
>
>Typing my-font reminds me of the name of the command,
>and the name of the command reminds me of the path to type in.
> then lists the font files to use filename completion on.
>
>Cheers,
>David.

Thanks for that, but I'm not there yet.  :-)

Apparently it's possible to do something similar by creating additional
/etc/default/console-setup files with filenames e.g. console-setup-small to
enable setfont to load alternate console line and column setups also.

Console fonts, was Re: Jessie for Udoo X86?

[David Wright]

On Sun 23 Apr 2017 at 18:55:03 (-0700), Larry Dighera wrote:

> I'd like to have more lines/rows and columns on the console tty.  I've read
> that 'vidcontrol' may do what I want, unfortunately 'apt-cache show
> vidcontrol' reports that it is virtual (unavailable).  
> 
> I am grateful for any clues you may be able to provide.

Best to start a new thread with a new subject, but anyway…

The Debian Way to set a default font for dmesg output, login prompt,
etc is (I think) to edit /etc/default/console-setup
I like Terminus fonts (package console-setup-linux, I think),
so I have:

ACTIVE_CONSOLES="/dev/tty[1-6]"
CHARMAP="UTF-8"
CODESET="Lat15"
#FONTFACE="Fixed"
FONTFACE="Terminus"
FONTSIZE="10x20"
#FONTSIZE="12x24"
#FONTSIZE="14x28"
#FONTSIZE="16x32"
VIDEOMODE=

in there, with various sizes available.

However, I prefer using aliases like:

alias my-font-tiny="setfont Lat15-Terminus12x6"
alias my-font-small="setfont Lat15-Terminus14"
alias my-font-medium="setfont Lat15-Terminus20x10"
alias my-font-large="setfont Lat15-Terminus24x12"
alias my-font-huge="setfont Lat15-Terminus28x14"
alias my-font-vast="setfont Lat15-Terminus32x16"

because you can then have different font sizes on each VC.
I also have a bash function to choose an arbitrary font:

function my-font-usr-share-consolefonts {
[ -z "$1" ] && printf '%s\n' "Usage: $FUNCNAME 
/usr/share/consolefonts/.psf.gz
sets the specified font on the current VC.
The command name serves as a reminder of the fonts' location.
Use filename-completion to specify the appropriate filename.
Redundant elements of the filename are stripped out before use.
Typically, filenames start Lat15- or Uni." >&2 && return 1
local FILENAME="$(basename "$1")"
setfont "${FILENAME%%.*}"
}

Typing my-font reminds me of the name of the command,
and the name of the command reminds me of the path to type in.
 then lists the font files to use filename completion on.

Cheers,
David.

Re: console fonts and systemd (was ... Re: What can AppArmor do?)

[David Wright]

On Mon 06 Jun 2016 at 16:52:30 (+1200), cbannis...@slingshot.co.nz wrote:
> On Sun, Jun 05, 2016 at 09:16:23AM -0500, David Wright wrote:
> > And here's my observation. When you type real quotation marks (ie ‘’“”),
> > the correct glyphs appear on the screen. After changing font, those
> > glyphs turn into different glyphs, but freshly typed quotation marks
> > appear with the correct glyphs.
> > 
> > I have no idea why this happens, but it does mean that your statement
> > above needs qualification. The glyphs that change to a sort of D shape
> > with a squiggle on top, are these glyphs that were already on the
> > screen before you changed choice, or are they fresh glyphs written 
> > afterwards?
> 
> They were fresh glyphs written afterwards. The glyps I got were dependant on 
> the
> setting I chose in the second screen (after choosing UTF from the first.) 
> while
> doing 'dpkg-reconfigure console-setup'.
> 
> I've now got it set to 'Guess optimal character set' which does do the quotes.
> It was when choosing the other options i noticed the D shape with a squiggle 
> on
> top.
> 
> There is also setupcon (man setupcon) which may be of some interest.

Yes, that's what I used to use: setupcon -f console-setup.foo
(aliased, naturally) where foo was small/medium/large/huge and the
associated files (in /etc/default) had the appropriate CODESET="Lat15"
FONTFACE="Terminus" FONTSIZE="10x20" lines.

But now I just call up the actual font file, and just for one VC at a time.
(I wonder why it's FONTSIZE="10x20" but Lat15-Terminus20x10.)

> Once I got the dlyphs showing correctly I didn't bother with the 
> technicalities
> any further --- although what the option 'Guess optimal character set' is 
> actually
> doing behind the scenes *may* be an option for further perusal. 

/bin/setupcon is just a script. AFAICT guessing the CHARMAP just uses the
locale's value. In turn, guessing the CODESET uses $CHARMAP in a case
statement.

Cheers,
David.

Re: console fonts and systemd (was ... Re: What can AppArmor do?)

[cbannister]

On Sun, Jun 05, 2016 at 09:16:23AM -0500, David Wright wrote:
> And here's my observation. When you type real quotation marks (ie ‘’“”),
> the correct glyphs appear on the screen. After changing font, those
> glyphs turn into different glyphs, but freshly typed quotation marks
> appear with the correct glyphs.
> 
> I have no idea why this happens, but it does mean that your statement
> above needs qualification. The glyphs that change to a sort of D shape
> with a squiggle on top, are these glyphs that were already on the
> screen before you changed choice, or are they fresh glyphs written afterwards?

They were fresh glyphs written afterwards. The glyps I got were dependant on the
setting I chose in the second screen (after choosing UTF from the first.) while
doing 'dpkg-reconfigure console-setup'.

I've now got it set to 'Guess optimal character set' which does do the quotes.
It was when choosing the other options i noticed the D shape with a squiggle on
top.

There is also setupcon (man setupcon) which may be of some interest.

Once I got the dlyphs showing correctly I didn't bother with the technicalities
any further --- although what the option 'Guess optimal character set' is 
actually
doing behind the scenes *may* be an option for further perusal. 

-- 
The media's the most powerful entity on earth. 
They have the power to make the innocent guilty 
and to make the guilty innocent, and that's power.
 -- Malcolm X

Re: console fonts and systemd (was ... Re: What can AppArmor do?)

[David Wright]

Nowadays I use console-setup (specifically /etc/default/console-setup)
to set up my default console font (with alternatives commented out in
that file so I don't have to look them up).

However, to change fonts on the fly, I use setfont which has the
advantage that you can have different fonts on different VCs.
To make it easier to type the font names precisely (a necessity),
I use a function:
function my-font-usr-share-consolefonts {
local FILENAME=$(basename "$1")
setfont ${FILENAME%%.*}
}
which reminds me to start the argument with /usr/share/consolefonts/,
and then strips what's not necessary before handing it to setfont.
(I'm using bash-completion throughout, obviously).

On Wed 25 May 2016 at 08:04:27 (+1200), cbannis...@slingshot.co.nz wrote:
> So, actually the answer to your question is that I have no idea what font 
> I was running on this system to give the "wee squares"
> 
> If I choose Terminus instead of TerminusBold, then the ’ changes to a sort
> of D shape with a squiggle on top! I'm guessing the char was a right
> side single curly quote, that you posted David?

And here's my observation. When you type real quotation marks (ie ‘’“”),
the correct glyphs appear on the screen. After changing font, those
glyphs turn into different glyphs, but freshly typed quotation marks
appear with the correct glyphs.

I have no idea why this happens, but it does mean that your statement
above needs qualification. The glyphs that change to a sort of D shape
with a squiggle on top, are these glyphs that were already on the
screen before you changed choice, or are they fresh glyphs written afterwards?

Cheers,
David.

Re: console fonts and systemd (was ... Re: What can AppArmor do?)

[David Wright]

On Wed 25 May 2016 at 08:04:27 (+1200), cbannis...@slingshot.co.nz wrote:
> On Mon, May 23, 2016 at 03:20:32PM -0500, David Wright wrote:
> > On Tue 24 May 2016 at 01:13:34 (+1200), cbannis...@slingshot.co.nz wrote:
> > > On Sun, May 22, 2016 at 11:11:27AM +0100, Lisi Reisz wrote:
> > > > 
> > > > But I am only using  us-ascii, 
> > > > iso-8859-1, utf-8 
> > > > (locale)  and utf-8, with a locale of en_GB.UTF-8, so not very 
> > > > abstruse in view of the fact that I have correspondents in, and 
> > > > therefore 
> > > > correspondence from, Japan, Greece and Israel in addition to the 
> > > > Anglo-Saxon 
> > > > countries.
> > > 
> > > I'm running utf8 also, but if your font can't display the chars/glyphs 
> > > then
> > > it won't help.
> > 
> > If I’m not mistaken, it’s *your* font that’s lacking the necessary
> > glyphs, like ’. What is it, BTW?
> 
> I didn't think someone would read it that way. I was meaning "your" in a
> general way, not explicitly meaning Lisi's font. 
> 
> What is the systemd command to show the font being used on the console?
> (hint ... /etc/vconsole.conf doesn't exist)
> 
> After a bit of googling, It seems to be done via the console-setup package
> which I don't have installed! Weird.

Its priority is optional, so there's no pressing need to have it.

AFAICT there are a number of fonts used in the early stages of
booting. The first is obviously nothing to do with linux as it
comes with the BIOS and is "normal" size, perhaps 80 chars across
the screen.

The next font is grub's and I think it must be unifont as it has
almost everything I can think of. On my laptop, it's quite small,
perhaps 120 chars wide.

After grub with 'Loading Linux 3.16.0-4-686-pae ...'
'Loading initial ramdisk ...'
I get "Loading, please wait..." from initrd's init. It's written in a
normal size, but then the screen is reset, leaving it much smaller.
I assume that's the kernel's own compiled-in font.

After a load of messages have scrolled past, the console-setup
font is selected, and the screen changes to that font (losing
everything above that point in the scrollback buffer).

So I would assume that your tty was running with the kernel font.
I can only guess that that comes from the fonts in
drivers/video/console if you're running wheezy. I'm not sure
where they are in jessie. However, the ones in whezzy are small,
with a smattering of European diacriticals, greek, box-drawing
glyphs, blobs, and the all-important playing card glyphs.

> So I installed the console-setup package and chose (eventually):
> 
> UTF 
> Guess optimal character set   
> TerminusBold 
> 8x16 
> 
> and the wee squares disappeared (at least in this mail, I've deleted 
> the others in this thread.)
> 
> So, actually the answer to your question is that I have no idea what font 
> I was running on this system to give the "wee squares"
> 
> If I choose Terminus instead of TerminusBold, then the ’ changes to a sort
> of D shape with a squiggle on top! I'm guessing the char was a right
> side single curly quote, that you posted David?

Yes (and I don't normally type them into emails).

> Although, IIRC, the typographical single quotes and double quotes are a
> rather peculiar case anyway.

Well, they ought not to be as they're some of the commonest
punctuation characters in any literature (though not text emails).

Cheers,
David.

console fonts and systemd (was ... Re: What can AppArmor do?)

[cbannister]

On Mon, May 23, 2016 at 03:20:32PM -0500, David Wright wrote:
> On Tue 24 May 2016 at 01:13:34 (+1200), cbannis...@slingshot.co.nz wrote:
> > On Sun, May 22, 2016 at 11:11:27AM +0100, Lisi Reisz wrote:
> > > 
> > > But I am only using  us-ascii, iso-8859-1, 
> > > utf-8 
> > > (locale)  and utf-8, with a locale of en_GB.UTF-8, so not very 
> > > abstruse in view of the fact that I have correspondents in, and therefore 
> > > correspondence from, Japan, Greece and Israel in addition to the 
> > > Anglo-Saxon 
> > > countries.
> > 
> > I'm running utf8 also, but if your font can't display the chars/glyphs then
> > it won't help.
> 
> If I’m not mistaken, it’s *your* font that’s lacking the necessary
> glyphs, like ’. What is it, BTW?

I didn't think someone would read it that way. I was meaning "your" in a
general way, not explicitly meaning Lisi's font. 

What is the systemd command to show the font being used on the console?
(hint ... /etc/vconsole.conf doesn't exist)

After a bit of googling, It seems to be done via the console-setup package
which I don't have installed! Weird.

So I installed the console-setup package and chose (eventually):

UTF 
Guess optimal character set   
TerminusBold 
8x16 

and the wee squares disappeared (at least in this mail, I've deleted 
the others in this thread.)

So, actually the answer to your question is that I have no idea what font 
I was running on this system to give the "wee squares"

If I choose Terminus instead of TerminusBold, then the ’ changes to a sort
of D shape with a squiggle on top! I'm guessing the char was a right
side single curly quote, that you posted David?

Although, IIRC, the typographical single quotes and double quotes are a
rather peculiar case anyway.

-- 
The media's the most powerful entity on earth. 
They have the power to make the innocent guilty 
and to make the guilty innocent, and that's power.
 -- Malcolm X

Re: Tiny Console Fonts - Almost Fixed

[Roger Leigh]

On Fri, Aug 06, 2010 at 09:29:30AM -0400, Thomas H. George wrote:
 I gave up and installed kbd.  On boot up the initial font was large.
 About half way through the boot up the scripts changed to tiny fonts and
 then after a half dozen lines switched back to large fonts.  The console
 is now very readable but when mutt displays the threaded list of
 postings the lines and arrows are replaces by strange characters.

This is most likely due to a mismatch between your locale character
set (charmap) and the encoding of the console font.  I'd advise
using UTF-8 for both.  You can check the locale codeset with

% locale -k charmap
== charmap=UTF-8

Because the Linux console has a limited number of characters (512 IIRC),
you need to choose a subset of Unicodei, which is why there are
separate Uni1, Uni2 and Uni3 fonts.  I use Uni2 myself.  All have the
basic Latin characters, but different Greek/Cyrillic/Arabic/Symbol
characters.  IIRC Uni2 has more symbols, but try them all out to see
which works best for you.

If you're not using UTF-8, then you'll need to choose the exact same
encoding as your locale charmap.


Regards,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?   http://gutenprint.sourceforge.net/
   `-GPG Public Key: 0x25BFB848   Please GPG sign your mail.


signature.asc
Description: Digital signature

Re: Tiny Console Fonts - Almost Fixed

[Roger Leigh]

On Thu, Aug 05, 2010 at 09:12:20AM -0500, Jordon Bedwell wrote:
 Edit:
 kernel /boot/blah-blah-kernel root=/my/device ro quiet splash

 Add:
 vga=HEX


 Size 640x400 640x480 800x600 1024x768 1152x864 1280x1024 1600x1200
 +--
  8 bits |  0x300   0x301   0x3030x3050x1610x307 0x31C
 15 bits |? 0x310   0x3130x3160x1620x319 0x31D
 16 bits |? 0x311   0x3140x3170x1630x31A 0x31E

 In otherwords, changing the console resolution should solve your  
 problem.  You just have to be careful because you could end up with  
 squishy text but it will be bigger.

But, isn't this the wrong solution to the problem?  Changing to a lower
resolution and keeping the same font size is not as good as using the
native or maximal resolution of the monitor together with a larger,
clearer font.

While it's still possible to use the VGA=hex option, I've not seen
a graphics card where the resolution couldn't be specified directly
with video= for some time.  For example:
  video=radeonfb:1680x1050...@60
which allows the x and y resolution, bit depth and refresh rate to
all be specified.  I'm not sure if this still works with KMS since
it gets the correct values using DPMS, but I'm sure there's an
equivalent.

Overall, KMS seems to be a very good thing albeit with a few rough
edges for some users.


Regards,
Roger

-- 
  .''`.  Roger Leigh
 : :' :  Debian GNU/Linux http://people.debian.org/~rleigh/
 `. `'   Printing on GNU/Linux?   http://gutenprint.sourceforge.net/
   `-GPG Public Key: 0x25BFB848   Please GPG sign your mail.


signature.asc
Description: Digital signature

Re: Tiny Console Fonts - Almost Fixed

[Anthony Campbell]

On 05 Aug 2010, Javier Vasquez wrote:
 On 8/5/10, Jordon Bedwell jor...@envygeeks.com wrote:
  On 8/5/2010 12:54 PM, Sven Joachim wrote:
  The solution is to use a bigger font, as I had tried to explain.
 
  Yes, that was your solution, until he explained (which you merrily
  missed apparently) that even though he used your fix the font resets
  back to a small size a little ways into the boot.
 
 It's not that you got small fonts back.  It's that console-tools
 doesn't support the combination of font and size you selected.  A
 message is prompted out of dpkg-reconfigure when that happens usually.
  So using kbd instead of console-tools, and then running
 dpkg-reconfigure agian, usually takes care of that problem.
 
 -- 
 Javier.
 

Doesn't seem to work here. The small font I can live with, but if I
enable KMS another problem appears. Initially the console type face is
large. If I start X and go back to the console with ctrl-alt-F1 the type
face is small. If I do this a second time the console is completely
blank.

I've tried different settings (Terminus, VGA) in dpkg-reconfigure but
that seems to have no effect.

-- 
Anthony Campbell - a...@acampbell.org.uk 
Microsoft-free zone - Using Debian GNU/Linux
http://www.acampbell.org.uk - sample my ebooks
at http://www.smashwords.com/profile/view/acampbell


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100806101328.ga2...@ithaca.acampbell.org.uk

Re: Tiny Console Fonts - Almost Fixed

[Anthony Campbell]

On 06 Aug 2010, Anthony Campbell wrote:
  
 
 Doesn't seem to work here. The small font I can live with, but if I
 enable KMS another problem appears. Initially the console type face is
 large. If I start X and go back to the console with ctrl-alt-F1 the type
 face is small. If I do this a second time the console is completely
 blank.
 
 I've tried different settings (Terminus, VGA) in dpkg-reconfigure but
 that seems to have no effect.
 

Sorry to follow up to myself, but I found a solution in a bug report for
KMS. If I have the radeon module loaded at boot time the blank screen in
the console doesn't happen.

Anthony

-- 
Anthony Campbell - a...@acampbell.org.uk 
Microsoft-free zone - Using Debian GNU/Linux
http://www.acampbell.org.uk - sample my ebooks
at http://www.smashwords.com/profile/view/acampbell


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100806140843.ga2...@ithaca.acampbell.org.uk

Re: Tiny Console Fonts - Almost Fixed

[Thomas H. George]

On Thu, Aug 05, 2010 at 04:07:26PM -0400, Thomas H. George wrote:
 On Thu, Aug 05, 2010 at 02:49:48PM -0400, Tom H wrote:
  On Thu, Aug 5, 2010 at 1:49 PM, Thomas H. George li...@tomgeorge.info 
  wrote:
  
   I don't understand grub's menu.lst.  It begins with several entries
   and the beginning of the AUTOMAGIC KERNELS LIST and within this the
   start of the default options list.  Within this list is
  
   #kopt=root=UUID= where  is the UUID of the root partition which
   was previously known as /dev/sdb1
  
   The following entry is
   groot=(hd0,0)
  
   though at some point in the original setup I specified writing the MBR
   to /dev/sda and to /dev/sdb.  I had used lilo to write a different MBR
   to /dev/hda.  Subsequently grub failed to boot the system because it
   could not find the root partition but lilo could still boot the system
   and running update-grub corrected grub's problem.
  
   After a number of additional default entries the end of the default
   options list is reached.  Following this is the entry
  
   title           Debian GNU/Linux, kernel 2.6.30-1-amd64
   root            (hd0,0)
   kernel  /boot/vmlinuz-2.6.30-1-amd64 root=/dev/sdb1 ro
   initrd  /boot/initrd.img-2.6.30-1-amd64
  
   followed by several more such entries for earlier kernels and then the
   END DEBIAN AUTOMAGIC KERNELS LIST.  Since the current kernel and two
   other recent kernels were not included in the above list I added
  
   title           Debian GNU/Linux, kernel 2.6.32-5-amd64
   root            (hd0,0)
   kernel  /boot/vmlinuz-2.6.32-5-amd64 root=/dev/sdb1 ro quiet splash
   vga=0x311
  
   to the end of the file, saved the file, ran update-grub and rebooted.
   The scripts still change to the tiny font in middle of the reboot.
  
   Questions: Why are the newer kernels not included in the Automagic
   listings?  Is there a conflict between root (hd0,0) and root=/dev/sdb1?
   Why does the system still switch to tiny fonts during bootup?
   initrd  /boot/initrd.img-2.6.32-5-amd64
  
  kopt=... defines the /boot where the automagic kernels are and the
  options to give the kernel line for these kernels (sdb1, in your case)
  and groot=... defines the /boot where /boot/grub is (that's why it
  is (hdX,Y) and not (hdX) even though you've written grub's stage 1 to
  the mbr).
  
  Given that you installed grub to sda and sdb, you must have a raid
  setup so mixing an sdb1 / and an sda1 /boot is weird but the new
  kernels should be seen by update-grub; should is the operative
  word...
  
 I do not have a raid setup and /boot is in the root directory on sdb1.
 History: /sdb is a 71G hard drive and all the system subdirectories are
 subdirectories of the root directory.  sda is a 300G hard drive added to
 store large collections of music, photo and video files.  hda is left
 over from the days - long gone - when I thought I occasionally needed 
 run windoz.
 
 When I recently updated grub the installation script specifically
 recommended installing the MBR on each hard drive.  Earlier I had lilo
 put an MBR on hda and this proved useful when the grub boot failed as
 the lilo boot still worked.  I just tested booting from hda and found
 kernel-2.6.32-5 is now too large but the boot of kernel-2.6.32-3 still
 works and the system came up with 640x480 resolution and large fonts.
 This is not a result of the changes to grub.  When I was using
 kernel-2.6.32-3 I had to restore an old copy of xorg.conf otherwise the
 boot would not use the nv driver.  When I switched to kernel-2.6.32-5 I
 had to remove the xorg.conf file.
 
 
  I am curious though. Since you are running testing or unstable, could
  it be that your bootloader is grub2 and that update-grub is updating
  grub.cfg rather than menu.lst? That would also explain why vga=0x311
  was ineffective.
  
 You have pinpointed the problem.  The system is Squeeze and when
 update-grub is run it reports updating grub.cfg.
  
I gave up and installed kbd.  On boot up the initial font was large.
About half way through the boot up the scripts changed to tiny fonts and
then after a half dozen lines switched back to large fonts.  The console
is now very readable but when mutt displays the threaded list of
postings the lines and arrows are replaces by strange characters.

Tom
  --
  To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
  with a subject of unsubscribe. Trouble? Contact 
  listmas...@lists.debian.org
  Archive: 
  http://lists.debian.org/aanlktinqxmfeqzuxcd_t9vdlhs=q-vhznx1amoud1...@mail.gmail.com
  
  
 
 
 -- 
 To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: http://lists.debian.org/20100805200726.ga2...@tomgeorge.info
 
 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100806132930.ga3...@tomgeorge.info

Re: Tiny Console Fonts - Almost Fixed

[Thomas H. George]

On Wed, Aug 04, 2010 at 04:36:49PM +0200, Sven Joachim wrote:
 On 2010-08-04 15:57 +0200, Thomas H. George wrote:
 
  After installing linux-image-2.6.32-5-amd64 the console fonts are so
  small I must use reading glasses to make them out.  I have experimented
  with the consolechars -H 16 -d  command but this just makes the characters
  brighter.
 
  I assume the problem may be the setting of the monitor resolution.
 
 This is now done by the kernel for both Nvidia and Radeon cards, yes.
 It uses the native resolution of your display which gives you a sharp
 picture but also a small font by default.
 
  The
  monitor is 23 LCD monitor capable of 1920x1080 resolution.  Indeed, the
  small font is very sharp when viewed with my reading glasses but I wish
  it was twice as large so I would not have to bother with the glases.
 
 This should be easy to fix, fortunately.
 
  On the other hand, the font sizes and resolution in X windows is fine as
  it is.
 
  Is there a way change the console font size without changing the X
  windows resolution?
 
 Make sure you have the console-setup and kbd packages installed and use
 
 # dpkg-reconfigure console-setup
 
 to choose a console font that suits your taste; it will be set up on
 each boot.  You can also use the setfont utility to change the font
 temporarily.  Fonts are in the /usr/share/consolefonts directory.
 
 Sven
 
I followed these instructions chosing the Terminus font and a character
height of 32 and then rebooted.  The boot screen and initial scripts
were easy to read, actually larger than I need BUT

About half way through the boot up the scripts changed back to the tiny
fonts.  There was a line saying consolechars can only load fonts with a
height of 16, try installing setfont. Apt-get search found setfont in
kbd-compat but apt-get install reported that the latest version of
kbd-compat was already installed.

What now?

Tom

 -- 
 To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: http://lists.debian.org/87ocdila0u@turtle.gmx.de
 
 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100805135953.ga2...@tomgeorge.info

Re: Tiny Console Fonts - Almost Fixed

[Sven Joachim]

On 2010-08-05 15:59 +0200, Thomas H. George wrote:

 About half way through the boot up the scripts changed back to the tiny
 fonts.  There was a line saying consolechars can only load fonts with a
 height of 16, try installing setfont. Apt-get search found setfont in
 kbd-compat but apt-get install reported that the latest version of
 kbd-compat was already installed.

 What now?

Replace kbd-compat and console-tools by kbd, it is in my experience
*much* less buggy.

Sven


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87tyn9yx1y@turtle.gmx.de

Re: Tiny Console Fonts - Almost Fixed

[Jordon Bedwell]

On 8/5/2010 8:59 AM, Thomas H. George wrote:

I followed these instructions chosing the Terminus font and a character
height of 32 and then rebooted.  The boot screen and initial scripts
were easy to read, actually larger than I need BUT

About half way through the boot up the scripts changed back to the tiny
fonts.  There was a line saying consolechars can only load fonts with a
height of 16, try installing setfont. Apt-get search found setfont in
kbd-compat but apt-get install reported that the latest version of
kbd-compat was already installed.

What now?

Tom


Don't change the subject line unless you plan to change the topic.

sudo vim /boot/grub/menu.lst

Edit:
kernel /boot/blah-blah-kernel root=/my/device ro quiet splash

Add:
vga=HEX


Size 640x400 640x480 800x600 1024x768 1152x864 1280x1024 1600x1200
+--
 8 bits |  0x300   0x301   0x3030x3050x1610x307 0x31C
15 bits |? 0x310   0x3130x3160x1620x319 0x31D
16 bits |? 0x311   0x3140x3170x1630x31A 0x31E

In otherwords, changing the console resolution should solve your 
problem.  You just have to be careful because you could end up with 
squishy text but it will be bigger.



--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4c5ac6c4.4000...@envygeeks.com

Re: Tiny Console Fonts - Almost Fixed

[Anthony Campbell]

On 05 Aug 2010, Thomas H. George wrote:
  
 I followed these instructions chosing the Terminus font and a character
 height of 32 and then rebooted.  The boot screen and initial scripts
 were easy to read, actually larger than I need BUT
 
 About half way through the boot up the scripts changed back to the tiny
 fonts.  There was a line saying consolechars can only load fonts with a
 height of 16, try installing setfont. Apt-get search found setfont in
 kbd-compat but apt-get install reported that the latest version of
 kbd-compat was already installed.
 
 What now?
 
 Tom
 

Isn't this the KMS issue? I solved it by editing
/etc/modprobe.d/radeon-kms.conf, as suggested by 
/usr/share/doc/xserver-xorg-video-radeon.

The change to tiny font half-way through booting was exactly the symptom
I had before doing the above.

Anthony


-- 
Anthony Campbell - a...@acampbell.org.uk 
Microsoft-free zone - Using Debian GNU/Linux
http://www.acampbell.org.uk - sample my ebooks
at http://www.smashwords.com/profile/view/acampbell


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100805172652.ga2...@ithaca.acampbell.org.uk

Re: Tiny Console Fonts - Almost Fixed

[Thomas H. George]

On Thu, Aug 05, 2010 at 09:12:20AM -0500, Jordon Bedwell wrote:
 On 8/5/2010 8:59 AM, Thomas H. George wrote:
 I followed these instructions chosing the Terminus font and a character
 height of 32 and then rebooted.  The boot screen and initial scripts
 were easy to read, actually larger than I need BUT
 
 About half way through the boot up the scripts changed back to the tiny
 fonts.  There was a line saying consolechars can only load fonts with a
 height of 16, try installing setfont. Apt-get search found setfont in
 kbd-compat but apt-get install reported that the latest version of
 kbd-compat was already installed.
 
 What now?
 
 Tom
 
 Don't change the subject line unless you plan to change the topic.
 
 sudo vim /boot/grub/menu.lst
 
 Edit:
 kernel /boot/blah-blah-kernel root=/my/device ro quiet splash
 
 Add:
 vga=HEX
 
 
 Size 640x400 640x480 800x600 1024x768 1152x864 1280x1024 1600x1200
 +--
  8 bits |  0x300   0x301   0x3030x3050x1610x307 0x31C
 15 bits |? 0x310   0x3130x3160x1620x319 0x31D
 16 bits |? 0x311   0x3140x3170x1630x31A 0x31E
 
 In otherwords, changing the console resolution should solve your
 problem.  You just have to be careful because you could end up with
 squishy text but it will be bigger.
 
I don't understand grub's menu.lst.  It begins with several entries
and the beginning of the AUTOMAGIC KERNELS LIST and within this the
start of the default options list.  Within this list is 

#kopt=root=UUID= where  is the UUID of the root partition which
was previously known as /dev/sdb1

The following entry is

groot=(hd0,0)

though at some point in the original setup I specified writing the MBR
to /dev/sda and to /dev/sdb.  I had used lilo to write a different MBR
to /dev/hda.  Subsequently grub failed to boot the system because it
could not find the root partition but lilo could still boot the system
and running update-grub corrected grub's problem.

After a number of additional default entries the end of the default
options list is reached.  Following this is the entry

title   Debian GNU/Linux, kernel 2.6.30-1-amd64
root(hd0,0)
kernel  /boot/vmlinuz-2.6.30-1-amd64 root=/dev/sdb1 ro
initrd  /boot/initrd.img-2.6.30-1-amd64

followed by several more such entries for earlier kernels and then the
END DEBIAN AUTOMAGIC KERNELS LIST.  Since the current kernel and two
other recent kernels were not included in the above list I added 

title   Debian GNU/Linux, kernel 2.6.32-5-amd64
root(hd0,0)
kernel  /boot/vmlinuz-2.6.32-5-amd64 root=/dev/sdb1 ro quiet splash
vga=0x311

to the end of the file, saved the file, ran update-grub and rebooted.
The scripts still change to the tiny font in middle of the reboot.

Questions: Why are the newer kernels not included in the Automagic
listings?  Is there a conflict between root (hd0,0) and root=/dev/sdb1?
Why does the system still switch to tiny fonts during bootup?
initrd  /boot/initrd.img-2.6.32-5-amd64

 -- 
 To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a
 subject of unsubscribe. Trouble? Contact
 listmas...@lists.debian.org
 Archive: http://lists.debian.org/4c5ac6c4.4000...@envygeeks.com
 
 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100805174947.ga2...@tomgeorge.info

Re: Tiny Console Fonts - Almost Fixed

[Sven Joachim]

On 2010-08-05 19:26 +0200, Anthony Campbell wrote:

 On 05 Aug 2010, Thomas H. George wrote:
  
 I followed these instructions chosing the Terminus font and a character
 height of 32 and then rebooted.  The boot screen and initial scripts
 were easy to read, actually larger than I need BUT
 
 About half way through the boot up the scripts changed back to the tiny
 fonts.  There was a line saying consolechars can only load fonts with a
 height of 16, try installing setfont. Apt-get search found setfont in
 kbd-compat but apt-get install reported that the latest version of
 kbd-compat was already installed.
 
 What now?
 
 Tom
 

 Isn't this the KMS issue? I solved it by editing
 /etc/modprobe.d/radeon-kms.conf, as suggested by 
 /usr/share/doc/xserver-xorg-video-radeon.

This is not a solution but rather a workaround that may stop working at
some time in the future when xserver-xorg-video-radeon starts to
_require_ KMS.  Beside, it already won't work for Nvidia cards if you
want to use the Nouveau X driver.  So far, Thomas has not told anything
about his graphics card.

 The change to tiny font half-way through booting was exactly the symptom
 I had before doing the above.

The solution is to use a bigger font, as I had tried to explain.

Sven


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87aap1ymgi@turtle.gmx.de

Re: Tiny Console Fonts - Almost Fixed

[Jordon Bedwell]

On 8/5/2010 12:54 PM, Sven Joachim wrote:
 The solution is to use a bigger font, as I had tried to explain.

Yes, that was your solution, until he explained (which you merrily
missed apparently) that even though he used your fix the font resets
back to a small size a little ways into the boot.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4c5afbaa.5010...@envygeeks.com

Re: Tiny Console Fonts - Almost Fixed

[Javier Vasquez]

On 8/5/10, Sven Joachim svenj...@gmx.de wrote:
 On 2010-08-05 19:26 +0200, Anthony Campbell wrote:

 On 05 Aug 2010, Thomas H. George wrote:
 
 I followed these instructions chosing the Terminus font and a character
 height of 32 and then rebooted.  The boot screen and initial scripts
 were easy to read, actually larger than I need BUT

 About half way through the boot up the scripts changed back to the tiny
 fonts.  There was a line saying consolechars can only load fonts with a
 height of 16, try installing setfont. Apt-get search found setfont in
 kbd-compat but apt-get install reported that the latest version of
 kbd-compat was already installed.

 What now?

 Tom


 Isn't this the KMS issue? I solved it by editing
 /etc/modprobe.d/radeon-kms.conf, as suggested by
 /usr/share/doc/xserver-xorg-video-radeon.

 This is not a solution but rather a workaround that may stop working at
 some time in the future when xserver-xorg-video-radeon starts to
 _require_ KMS.  Beside, it already won't work for Nvidia cards if you
 want to use the Nouveau X driver.  So far, Thomas has not told anything
 about his graphics card.

 The change to tiny font half-way through booting was exactly the symptom
 I had before doing the above.

 The solution is to use a bigger font, as I had tried to explain.

 Sven


That's right.  Actually I always look for full resolution on console.
Before KMS, for some cards I had to load the corresponding module
through /etc/modules and for some of those, I also had to provide the
resolution parameters through /etc/modprobe.d/card_module.conf.  KMS
seems to always look for full resolution, so I've removed the stuff
from modules and modprobe.conf.  Notice some times uvesafb was the
only alternative to get required resolution, :-)

When you have bigger resolution on console, you need bigger fonts.
The recommendation Sven provided is the correct one (dpkg-reconfigure
console-setup).  However console-tools doesn't handle some fonts sizes
for some particular fonts, and thus, the solution is just to use
original kbd instead (which seems to support more fonts sizes).  This
has been required even before KMS showed up, unless you didn't care
about getting full/bigger resolution on console...

As an additional suggestion, I recommend using console-terminus (if
you want you can also try xfonts-terminus), so you select it as well
when running dpkg-reconfigure console-setup, :-)

-- 
Javier.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktik0dp3+2t0dsmdw1kgsp2v6rs2rzoa5g+rt+...@mail.gmail.com

Re: Tiny Console Fonts - Almost Fixed

[Javier Vasquez]

On 8/5/10, Jordon Bedwell jor...@envygeeks.com wrote:
 On 8/5/2010 12:54 PM, Sven Joachim wrote:
 The solution is to use a bigger font, as I had tried to explain.

 Yes, that was your solution, until he explained (which you merrily
 missed apparently) that even though he used your fix the font resets
 back to a small size a little ways into the boot.

It's not that you got small fonts back.  It's that console-tools
doesn't support the combination of font and size you selected.  A
message is prompted out of dpkg-reconfigure when that happens usually.
 So using kbd instead of console-tools, and then running
dpkg-reconfigure agian, usually takes care of that problem.

-- 
Javier.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktinp=hpjubb8dofazhqdh3dofeppanxwqbwvq...@mail.gmail.com

Re: Tiny Console Fonts - Almost Fixed

[Tom H]

On Thu, Aug 5, 2010 at 1:49 PM, Thomas H. George li...@tomgeorge.info wrote:

 I don't understand grub's menu.lst.  It begins with several entries
 and the beginning of the AUTOMAGIC KERNELS LIST and within this the
 start of the default options list.  Within this list is

 #kopt=root=UUID= where  is the UUID of the root partition which
 was previously known as /dev/sdb1

 The following entry is
 groot=(hd0,0)

 though at some point in the original setup I specified writing the MBR
 to /dev/sda and to /dev/sdb.  I had used lilo to write a different MBR
 to /dev/hda.  Subsequently grub failed to boot the system because it
 could not find the root partition but lilo could still boot the system
 and running update-grub corrected grub's problem.

 After a number of additional default entries the end of the default
 options list is reached.  Following this is the entry

 title           Debian GNU/Linux, kernel 2.6.30-1-amd64
 root            (hd0,0)
 kernel  /boot/vmlinuz-2.6.30-1-amd64 root=/dev/sdb1 ro
 initrd  /boot/initrd.img-2.6.30-1-amd64

 followed by several more such entries for earlier kernels and then the
 END DEBIAN AUTOMAGIC KERNELS LIST.  Since the current kernel and two
 other recent kernels were not included in the above list I added

 title           Debian GNU/Linux, kernel 2.6.32-5-amd64
 root            (hd0,0)
 kernel  /boot/vmlinuz-2.6.32-5-amd64 root=/dev/sdb1 ro quiet splash
 vga=0x311

 to the end of the file, saved the file, ran update-grub and rebooted.
 The scripts still change to the tiny font in middle of the reboot.

 Questions: Why are the newer kernels not included in the Automagic
 listings?  Is there a conflict between root (hd0,0) and root=/dev/sdb1?
 Why does the system still switch to tiny fonts during bootup?
 initrd  /boot/initrd.img-2.6.32-5-amd64

kopt=... defines the /boot where the automagic kernels are and the
options to give the kernel line for these kernels (sdb1, in your case)
and groot=... defines the /boot where /boot/grub is (that's why it
is (hdX,Y) and not (hdX) even though you've written grub's stage 1 to
the mbr).

Given that you installed grub to sda and sdb, you must have a raid
setup so mixing an sdb1 / and an sda1 /boot is weird but the new
kernels should be seen by update-grub; should is the operative
word...

I am curious though. Since you are running testing or unstable, could
it be that your bootloader is grub2 and that update-grub is updating
grub.cfg rather than menu.lst? That would also explain why vga=0x311
was ineffective.


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktinqxmfeqzuxcd_t9vdlhs=q-vhznx1amoud1...@mail.gmail.com

Re: Tiny Console Fonts - Almost Fixed

[Sven Joachim]

On 2010-08-05 20:08 +0200, Javier Vasquez wrote:

 That's right.  Actually I always look for full resolution on console.
 Before KMS, for some cards I had to load the corresponding module
 through /etc/modules and for some of those, I also had to provide the
 resolution parameters through /etc/modprobe.d/card_module.conf.  KMS
 seems to always look for full resolution, so I've removed the stuff
 from modules and modprobe.conf.  Notice some times uvesafb was the
 only alternative to get required resolution, :-)

I remember the times when I fiddled around with uvesafb on my laptop
which has i915 graphics.  Of course the crappy BIOS does not even
support the native resolution of the display, so I had to fix that
with 915resolution first.  I even wrote custom scripts that did this
from the initramfs to reduce the number of video mode changes.  KMS was
a big relief for me.

 When you have bigger resolution on console, you need bigger fonts.
 The recommendation Sven provided is the correct one (dpkg-reconfigure
 console-setup).  However console-tools doesn't handle some fonts sizes
 for some particular fonts, and thus, the solution is just to use
 original kbd instead (which seems to support more fonts sizes).  This
 has been required even before KMS showed up, unless you didn't care
 about getting full/bigger resolution on console...

I ditched console-tools when it suddenly started to switch to tty6 upon
boot¹.  Moving to kbd solved that problem and some others as well.

 As an additional suggestion, I recommend using console-terminus (if
 you want you can also try xfonts-terminus), so you select it as well
 when running dpkg-reconfigure console-setup, :-)

I did not mention console-terminus because console-setup already depends
on it, but it has some nice fonts indeed.

Sven


¹ http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570338


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87y6ckyj6a@turtle.gmx.de

Re: Tiny Console Fonts - Almost Fixed

[Thomas H. George]

On Thu, Aug 05, 2010 at 02:49:48PM -0400, Tom H wrote:
 On Thu, Aug 5, 2010 at 1:49 PM, Thomas H. George li...@tomgeorge.info wrote:
 
  I don't understand grub's menu.lst.  It begins with several entries
  and the beginning of the AUTOMAGIC KERNELS LIST and within this the
  start of the default options list.  Within this list is
 
  #kopt=root=UUID= where  is the UUID of the root partition which
  was previously known as /dev/sdb1
 
  The following entry is
  groot=(hd0,0)
 
  though at some point in the original setup I specified writing the MBR
  to /dev/sda and to /dev/sdb.  I had used lilo to write a different MBR
  to /dev/hda.  Subsequently grub failed to boot the system because it
  could not find the root partition but lilo could still boot the system
  and running update-grub corrected grub's problem.
 
  After a number of additional default entries the end of the default
  options list is reached.  Following this is the entry
 
  title           Debian GNU/Linux, kernel 2.6.30-1-amd64
  root            (hd0,0)
  kernel  /boot/vmlinuz-2.6.30-1-amd64 root=/dev/sdb1 ro
  initrd  /boot/initrd.img-2.6.30-1-amd64
 
  followed by several more such entries for earlier kernels and then the
  END DEBIAN AUTOMAGIC KERNELS LIST.  Since the current kernel and two
  other recent kernels were not included in the above list I added
 
  title           Debian GNU/Linux, kernel 2.6.32-5-amd64
  root            (hd0,0)
  kernel  /boot/vmlinuz-2.6.32-5-amd64 root=/dev/sdb1 ro quiet splash
  vga=0x311
 
  to the end of the file, saved the file, ran update-grub and rebooted.
  The scripts still change to the tiny font in middle of the reboot.
 
  Questions: Why are the newer kernels not included in the Automagic
  listings?  Is there a conflict between root (hd0,0) and root=/dev/sdb1?
  Why does the system still switch to tiny fonts during bootup?
  initrd  /boot/initrd.img-2.6.32-5-amd64
 
 kopt=... defines the /boot where the automagic kernels are and the
 options to give the kernel line for these kernels (sdb1, in your case)
 and groot=... defines the /boot where /boot/grub is (that's why it
 is (hdX,Y) and not (hdX) even though you've written grub's stage 1 to
 the mbr).
 
 Given that you installed grub to sda and sdb, you must have a raid
 setup so mixing an sdb1 / and an sda1 /boot is weird but the new
 kernels should be seen by update-grub; should is the operative
 word...
 
I do not have a raid setup and /boot is in the root directory on sdb1.
History: /sdb is a 71G hard drive and all the system subdirectories are
subdirectories of the root directory.  sda is a 300G hard drive added to
store large collections of music, photo and video files.  hda is left
over from the days - long gone - when I thought I occasionally needed 
run windoz.

When I recently updated grub the installation script specifically
recommended installing the MBR on each hard drive.  Earlier I had lilo
put an MBR on hda and this proved useful when the grub boot failed as
the lilo boot still worked.  I just tested booting from hda and found
kernel-2.6.32-5 is now too large but the boot of kernel-2.6.32-3 still
works and the system came up with 640x480 resolution and large fonts.
This is not a result of the changes to grub.  When I was using
kernel-2.6.32-3 I had to restore an old copy of xorg.conf otherwise the
boot would not use the nv driver.  When I switched to kernel-2.6.32-5 I
had to remove the xorg.conf file.


 I am curious though. Since you are running testing or unstable, could
 it be that your bootloader is grub2 and that update-grub is updating
 grub.cfg rather than menu.lst? That would also explain why vga=0x311
 was ineffective.
 
You have pinpointed the problem.  The system is Squeeze and when
update-grub is run it reports updating grub.cfg.
 
 --
 To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
 with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
 Archive: 
 http://lists.debian.org/aanlktinqxmfeqzuxcd_t9vdlhs=q-vhznx1amoud1...@mail.gmail.com
 
 


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100805200726.ga2...@tomgeorge.info

Tiny Console Fonts

[Thomas H. George]

After installing linux-image-2.6.32-5-amd64 the console fonts are so
small I must use reading glasses to make them out.  I have experimented
with the consolechars -H 16 -d  command but this just makes the characters
brighter.

I assume the problem may be the setting of the monitor resolution.  The
monitor is 23 LCD monitor capable of 1920x1080 resolution.  Indeed, the
small font is very sharp when viewed with my reading glasses but I wish
it was twice as large so I would not have to bother with the glases.

On the other hand, the font sizes and resolution in X windows is fine as
it is.

Is there a way change the console font size without changing the X
windows resolution?

Tom


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100804135712.ga5...@tomgeorge.info

Re: Tiny Console Fonts

[Sven Joachim]

On 2010-08-04 15:57 +0200, Thomas H. George wrote:

 After installing linux-image-2.6.32-5-amd64 the console fonts are so
 small I must use reading glasses to make them out.  I have experimented
 with the consolechars -H 16 -d  command but this just makes the characters
 brighter.

 I assume the problem may be the setting of the monitor resolution.

This is now done by the kernel for both Nvidia and Radeon cards, yes.
It uses the native resolution of your display which gives you a sharp
picture but also a small font by default.

 The
 monitor is 23 LCD monitor capable of 1920x1080 resolution.  Indeed, the
 small font is very sharp when viewed with my reading glasses but I wish
 it was twice as large so I would not have to bother with the glases.

This should be easy to fix, fortunately.

 On the other hand, the font sizes and resolution in X windows is fine as
 it is.

 Is there a way change the console font size without changing the X
 windows resolution?

Make sure you have the console-setup and kbd packages installed and use

# dpkg-reconfigure console-setup

to choose a console font that suits your taste; it will be set up on
each boot.  You can also use the setfont utility to change the font
temporarily.  Fonts are in the /usr/share/consolefonts directory.

Sven


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87ocdila0u@turtle.gmx.de

Re: Tiny Console Fonts

[Brian]

On Wed 04 Aug 2010 at 09:57:12 -0400, Thomas H. George wrote:

 Is there a way change the console font size without changing the X
 windows resolution?

You could try the console-setup command (as root).


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100804143036.gj26...@desktop

Re: Tiny Console Fonts

[Brian]

On Wed 04 Aug 2010 at 15:30:36 +0100, Brian wrote:

 You could try the console-setup command (as root).

This is misleading. It's 'dpkg-reconfigure console-setup' as
Sven Joachim says.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100804145244.gk26...@desktop

Re: Chinese console fonts?

[Osamu Aoki]

On Fri, Aug 15, 2008 at 07:09:10AM -0400, Zach Uram wrote:
 I downloaded a chinese webpage onto my remote server using wget (where
 I host my webserver - running Debian 4.0) and when I view it the
 Chinese haracters have been replaced with ASCII gibberish. Yet the
 original Chinese page displays fine in Firefox on my local machine
 (Ubuntu 6.06) and I can even see the Chinese characters in my console
 in Ubuntu when I load the file in emacs. So what packages do I need to
 install in Debian etch which will alow me view (and thus correctly
 download and save) Chinese webpages? I do not want X fonts since the
 server is only accessible via ssh and I don't run X on it.

It can be done with framebuffer consoles.  The only time I have seen
people using  framebuffer consoles are debian-installer in Asian
languages. (fbiterm, jfbterm, zhcon)

Quite honestly, your time is better spent to set up simple X setup with
UTF-8 terminal and international fonts.

If you have special needs such as Braille for blind person, I do not
know the answer.  (I do not even know how to convert text from normal
chinese to Braille friendly phonetic format.)

Osamu


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Chinese console fonts?

[Zach Uram]

I downloaded a chinese webpage onto my remote server using wget (where
I host my webserver - running Debian 4.0) and when I view it the
Chinese haracters have been replaced with ASCII gibberish. Yet the
original Chinese page displays fine in Firefox on my local machine
(Ubuntu 6.06) and I can even see the Chinese characters in my console
in Ubuntu when I load the file in emacs. So what packages do I need to
install in Debian etch which will alow me view (and thus correctly
download and save) Chinese webpages? I do not want X fonts since the
server is only accessible via ssh and I don't run X on it.

Zach


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Chinese console fonts?

[Osamu Aoki]

On Fri, Aug 15, 2008 at 07:09:10AM -0400, Zach Uram wrote:
 I downloaded a chinese webpage onto my remote server using wget (where
 I host my webserver - running Debian 4.0) and when I view it the
 Chinese haracters have been replaced with ASCII gibberish. Yet the
 original Chinese page displays fine in Firefox on my local machine
 (Ubuntu 6.06) and I can even see the Chinese characters in my console
 in Ubuntu when I load the file in emacs. So what packages do I need to
 install in Debian etch which will alow me view (and thus correctly
 download and save) Chinese webpages? I do not want X fonts since the
 server is only accessible via ssh and I don't run X on it.

It can be done with framebuffer consoles.  The only time I have seen
people using  framebuffer consoles are debian-installer in Asian
languages. (fbiterm, jfbterm, zhcon)

Quite honestly, your time is better spent to set up simple X setup with
UTF-8 terminal and international fonts.

If you have special needs such as Braille for blind person, I do not
know the answer.  (I do not even know how to convert text from normal
chinese to Braille friendly phonetic format.)

Osamu


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: [etch] console fonts disappear over time

[heba]

2007/7/3, Jakub Narojczyk [EMAIL PROTECTED]:

Hi, I have a strange problem. After some time working in X I noticed
that I can't run any xterminal (xterm, eterm...) I somehow manage to run
kde konsole. When I issue $xterm i get :

X Error of failed request:  BadName (named color or font does not exist)
   Major opcode of failed request:  45 (X_OpenFont)
   Serial number of failed request:  11
   Current serial number in output stream:  12


[cut]


The problem is clearly with fonts but the strange thing is that after
restarting Xsession it's all god. It happends after some time of using
X. I tried #dpkg-reconfigure fontconfig but it didn't help.
How else can I regenerate font cache or somthing? Does any one have an
idea why these fonts break after a while?

thanks
Kuba



have you try to install the addon font package?


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

[etch] console fonts disappear over time

[Jakub Narojczyk]

Hi, I have a strange problem. After some time working in X I noticed 
that I can't run any xterminal (xterm, eterm...) I somehow manage to run 
kde konsole. When I issue $xterm i get :


X Error of failed request:  BadName (named color or font does not exist)
  Major opcode of failed request:  45 (X_OpenFont)
  Serial number of failed request:  11
  Current serial number in output stream:  12

and $Eterm gives:
Eterm:  Error:  XError in function XOpenFont, resource 0x0061 
(request 45.0):  BadName (named color or font does not exist) (error 15)

Eterm:  Error:  Attempting to continue...
Eterm:  Error:  XError in function XCreateGlyphCursor, resource 
0x0061 (request 94.0):  BadFont (invalid Font parameter) (error 7)

Eterm:  Error:  Attempting to continue...
Eterm:  Error:  XError in function XChangeWindowAttributes, resource 
0x0062 (request 2.0):  BadCursor (invalid Cursor parameter) (error 6)

Eterm:  Error:  Attempting to continue...
Eterm:  Error:  XError in function XChangeWindowAttributes, resource 
0x0062 (request 2.0):  BadCursor (invalid Cursor parameter) (error 6)

Eterm:  Error:  Attempting to continue...
Eterm:  Error:  XError in function XChangeWindowAttributes, resource 
0x0062 (request 2.0):  BadCursor (invalid Cursor parameter) (error 6)

Eterm:  Error:  Attempting to continue...
Eterm:  Error:  XError in function XChangeWindowAttributes, resource 
0x0062 (request 2.0):  BadCursor (invalid Cursor parameter) (error 6)

Eterm:  Error:  Attempting to continue...
Eterm:  Error:  XError in function XChangeWindowAttributes, resource 
0x0062 (request 2.0):  BadCursor (invalid Cursor parameter) (error 6)

Eterm:  Error:  Attempting to continue...
Eterm:  Error:  XError in function XChangeWindowAttributes, resource 
0x0062 (request 2.0):  BadCursor (invalid Cursor parameter) (error 6)

Eterm:  Error:  Attempting to continue...
Eterm:  Error:  XError in function XChangeWindowAttributes, resource 
0x0062 (request 2.0):  BadCursor (invalid Cursor parameter) (error 6)

Eterm:  Error:  Attempting to continue...
Eterm:  Error:  XError in function XChangeWindowAttributes, resource 
0x0062 (request 2.0):  BadCursor (invalid Cursor parameter) (error 6)

Eterm:  Error:  Attempting to continue...
Eterm:  Error:  XError in function XChangeWindowAttributes, resource 
0x0062 (request 2.0):  BadCursor (invalid Cursor parameter) (error 6)

Eterm:  Error:  Attempting to continue...
Eterm:  Error:  XError in function XChangeWindowAttributes, resource 
0x0062 (request 2.0):  BadCursor (invalid Cursor parameter) (error 6)

Eterm:  Error:  Attempting to continue...
Eterm:  Error:  XError in function XChangeWindowAttributes, resource 
0x0062 (request 2.0):  BadCursor (invalid Cursor parameter) (error 6)

Eterm:  Error:  Attempting to continue...
Eterm:  Error:  XError in function XChangeWindowAttributes, resource 
0x0062 (request 2.0):  BadCursor (invalid Cursor parameter) (error 6)

Eterm:  Error:  Attempting to continue...
Eterm:  Error:  XError in function XChangeWindowAttributes, resource 
0x0062 (request 2.0):  BadCursor (invalid Cursor parameter) (error 6)

Eterm:  Error:  Attempting to continue...
Eterm:  Error:  XError in function XChangeWindowAttributes, resource 
0x0062 (request 2.0):  BadCursor (invalid Cursor parameter) (error 6)

Eterm:  Error:  Attempting to continue...
Eterm:  Error:  XError in function XChangeWindowAttributes, resource 
0x0062 (request 2.0):  BadCursor (invalid Cursor parameter) (error 6)

Eterm:  Error:  Attempting to continue...
Eterm:  Error:  XError in function XChangeWindowAttributes, resource 
0x0062 (request 2.0):  BadCursor (invalid Cursor parameter) (error 6)

Eterm:  Error:  Attempting to continue...
Eterm:  Error:  XError in function XChangeWindowAttributes, resource 
0x0062 (request 2.0):  BadCursor (invalid Cursor parameter) (error 6)

Eterm:  Error:  Attempting to continue...
Eterm:  Error:  XError in function XCreateGlyphCursor, resource 
0x0061 (request 94.0):  BadFont (invalid Font parameter) (error 7)

Eterm:  Error:  Attempting to continue...
Eterm:  Error:  Unable to load font 
-misc-fixed-medium-r-semicondensed--13-*-*-*-c-*-iso8859-2.  Falling 
back on fixed

Eterm:  FATAL:  Couldn't load the fallback font either.  Giving up.

The problem is clearly with fonts but the strange thing is that after 
restarting Xsession it's all god. It happends after some time of using 
X. I tried #dpkg-reconfigure fontconfig but it didn't help.
How else can I regenerate font cache or somthing? Does any one have an 
idea why these fonts break after a while?


thanks
Kuba


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: How to get those nice console fonts?

[Douglas Allan Tutty]

On Thu, Jan 18, 2007 at 11:37:36PM +, Brian Potkin wrote:
 Hello Douglas,
 
 I was interested in your reply to Daniel particularily as I have spent
 quite some time endeavouring to get a font to my liking on a 19 TFT
 screen without a framebuffer. With a CRT it was easy with svgatextmode
 but the problem (as I see it) is that a TFT has to be in its native
 resolution, 1280x1024 in my case, to get clear sharp fonts. And that
 means using a framebuffer.
 
 You mention getting a 21 screen and so I was wondering whether it was a
 CRT or TFT. If the latter, is setfont alone sufficient to get small,
 neat and readable fonts?
 

Hi Brian,

I don't mind receiving the personal mail, but this may be useful to
someone on the list, so I'm copying it there.


Sorry to tell you (and happy for me), its a 21 flat CRT drafting
monitor.

Have you tried the console-setup package (I'm downloading it now) and
the console-terminus font?

YMMV,

Doug.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: How to get those nice console fonts?

[Douglas Allan Tutty]

On Fri, Jan 19, 2007 at 06:38:54PM +, Brian Potkin wrote:
 On Thu, Jan 18, 2007 at 08:33:05PM -0500, Douglas Allan Tutty wrote:
  On Thu, Jan 18, 2007 at 11:37:36PM +, Brian Potkin wrote:
   Hello Douglas,
   
   I was interested in your reply to Daniel particularily as I have spent
   quite some time endeavouring to get a font to my liking on a 19 TFT
   screen without a framebuffer. With a CRT it was easy with svgatextmode
   but the problem (as I see it) is that a TFT has to be in its native
   resolution, 1280x1024 in my case, to get clear sharp fonts. And that
   means using a framebuffer.
   
   You mention getting a 21 screen and so I was wondering whether it was a
   CRT or TFT. If the latter, is setfont alone sufficient to get small,
   neat and readable fonts?
   
  
  Hi Brian,
  
  I don't mind receiving the personal mail, but this may be useful to
  someone on the list, so I'm copying it there.
 
 That's fine but it's not there yet.
  
  Sorry to tell you (and happy for me), its a 21 flat CRT drafting
  monitor.
 
 I was given something similar but with a curved screen. No longer used
 as it took up an enormous amount of room on the desk.
 
  Have you tried the console-setup package (I'm downloading it now) and
  the console-terminus font?
 
 console-setup doesn't appear to do more for font choice than setfont
 does. I'm familiar with the console-terminus font. It is a nice font but
 not quite what I want, even with a frame buffer. In text mode it is too
 large.
 

I haven't been down to my computer (sending this from upstairs via ssh)
to check out the new fonts stuff.

My 21 does 1600x1200 @ 75 Hz.  Combined with hardware mpeg HD decoding
and deinterlacing on the nVidia card and it makes for a great
movie-watching experience.  I don't like the inherant latency (or
whatever its called) of an LCD that makes movement appear blurry.  I
just wish I could afford a 40 CRT.

Hopefully, someone on the list with an LCD has some input.

Doug


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: How to get those nice console fonts?

[Daniel Haude]

Andrew Sackville-West wrote:

 I don't know much about this, but you seem to have 2 vga= options
 above. that could be part of the problem.

Look, wise guy. There's a good reason why there are 2 such options
given. In case you haven't figured it out youself, I'll tell you:

 I A M F U C K I N G S T U P I D

...that is to say, errr, thanks a lot for pointing it out! Sheesh! How
embarassing.

Problem solved.

--Daniel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: How to get those nice console fonts?

[Andrew Sackville-West]

On Wed, Jan 17, 2007 at 09:02:15AM +0100, Daniel Haude wrote:
 Andrew Sackville-West wrote:
 
  I don't know much about this, but you seem to have 2 vga= options
  above. that could be part of the problem.
 
 Look, wise guy. There's a good reason why there are 2 such options
 given. In case you haven't figured it out youself, I'll tell you:

okay... you got me. I was totally expexting to be flamed good...

 
  I A M F U C K I N G S T U P I D
 
 ...that is to say, errr, thanks a lot for pointing it out! Sheesh! How
 embarassing.

:)

 
 Problem solved.

:)

happy to help

A


signature.asc
Description: Digital signature

How to get those nice console fonts?

[Daniel Haude]

Hello,

I'd like to have my console (non-X) fonts small and neat like Knoppix's.
I tried the various vga=xxx kernel options but all of them produced
bigger and uglier fonts.

How is it done?
--Daniel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: How to get those nice console fonts?

[Florian Kulzer]

On Tue, Jan 16, 2007 at 12:04:37 +0100, Daniel Haude wrote:
 Hello,
 
 I'd like to have my console (non-X) fonts small and neat like Knoppix's.
 I tried the various vga=xxx kernel options but all of them produced
 bigger and uglier fonts.
 
 How is it done?

I use vga=0x303 and that looks exactly like Knoppix's fonts on my
terminals. However, I think this also depends on the kernel
configuration options related to the console fonts. Here is what I have:

$ grep -i font /boot/config-$(uname -r)
# CONFIG_FONTS is not set
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y

(I use a self-compiled kernel, therefore I do not know how the stock
 Debian kernels are set up in that respect.)

-- 
Regards,
  Florian


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: How to get those nice console fonts?

[Ismael Valladolid Torres]

Daniel Haude escribe:
 I'd like to have my console (non-X) fonts small and neat like Knoppix's.
 I tried the various vga=xxx kernel options but all of them produced
 bigger and uglier fonts.

I use vga=791 however it depends on your video card to support it.

Which video card is it?

Cordially, Ismael
-- 
Ismael Valladolid Torres  m. +34679156321
[1]La media hostiaj. [EMAIL PROTECTED]

1. http://lamediahostia.blogspot.com/


signature.asc
Description: Digital signature

Re: How to get those nice console fonts?

[Jochen Schulz]

Ismael Valladolid Torres:
 Daniel Haude escribe:

 I'd like to have my console (non-X) fonts small and neat like Knoppix's.
 I tried the various vga=xxx kernel options but all of them produced
 bigger and uglier fonts.
 
 I use vga=791 however it depends on your video card to support it.

Me too and that should work with any graphics adapter using vesafb.
Additionally, you can unstall console-terminus to get a not-so-bold font
which I think is very nice. You can preview it when running X and
installing xfonts-terminus.

J.
-- 
If I was Mark Chapman I would have shot John Lennon with a water pistol.
[Agree]   [Disagree]
 http://www.slowlydownward.com/NODATA/data_enter2.html


signature.asc
Description: Digital signature

Re: How to get those nice console fonts?

[Daniel Haude]

Florian Kulzer wrote:

 I use vga=0x303 and that looks exactly like Knoppix's fonts on my
 terminals. However, I think this also depends on the kernel
 configuration options related to the console fonts. Here is what I have:
 
 $ grep -i font /boot/config-$(uname -r)
 # CONFIG_FONTS is not set
 CONFIG_FONT_8x8=y
 CONFIG_FONT_8x16=y
 
 (I use a self-compiled kernel, therefore I do not know how the stock
  Debian kernels are set up in that respect.)

My stock kernel (2.4.27-3-k7) gives the same settings, but doesn't let
me change anything. In fact it seems to ignore any of the vga= options,
including vga=ask. Here's what I see in dmesg's output:

Kernel command line: root=/dev/hda5 ro vga=4 hdc=ide-scsi hdd=ide-scsi
vga=791
Initializing CPU#0
Detected 2104.783 MHz processor.
Console: colour VGA+ 80x30

This is sad because it's a non-X system and I'd like to see some more
info on the console screen.

Thanks for any hints,
--Daniel



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: How to get those nice console fonts?

[Daniel Haude]

Ismael Valladolid Torres wrote:

 I use vga=791 however it depends on your video card to support it.
 
 Which video card is it?

[EMAIL PROTECTED]:~$ lspci | grep VGA
:01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce
FX 5200] (rev a1)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: How to get those nice console fonts?

[Florian Kulzer]

On Tue, Jan 16, 2007 at 14:13:15 +0100, Daniel Haude wrote:
 Florian Kulzer wrote:
 
  I use vga=0x303 and that looks exactly like Knoppix's fonts on my
  terminals. However, I think this also depends on the kernel
  configuration options related to the console fonts. Here is what I have:
  
  $ grep -i font /boot/config-$(uname -r)
  # CONFIG_FONTS is not set
  CONFIG_FONT_8x8=y
  CONFIG_FONT_8x16=y
  
  (I use a self-compiled kernel, therefore I do not know how the stock
   Debian kernels are set up in that respect.)
 
 My stock kernel (2.4.27-3-k7) gives the same settings, but doesn't let
 me change anything. In fact it seems to ignore any of the vga= options,
 including vga=ask. Here's what I see in dmesg's output:
 
 Kernel command line: root=/dev/hda5 ro vga=4 hdc=ide-scsi hdd=ide-scsi
 vga=791
 Initializing CPU#0
 Detected 2104.783 MHz processor.
 Console: colour VGA+ 80x30
 
 This is sad because it's a non-X system and I'd like to see some more
 info on the console screen.

One thing I forgot to mention: I use the generic vesa framebuffer
compiled statically into the kernel. (I have an nvidia GeForce2 graphics
card, but I never found a reason to bother with the nvidia framebuffer
module.)

I would check with dmesg and lsmod which framebuffer module you are
using. Compiling the framebuffer code into the kernel might make a
difference for the availability of video modes at boot time. (I vaguely
remember that I had problems with the vga modes when I started to play
around with Linux, and I think that was the reason for me to compile
vesafb into the kernel. Unfortunately, however, I am not 100% sure of
this.)

-- 
Regards,
  Florian


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: How to get those nice console fonts?

[Daniel Haude]

Florian Kulzer wrote:

 I use vga=0x303 and that looks exactly like Knoppix's fonts on my
 terminals. However, I think this also depends on the kernel
 configuration options related to the console fonts. Here is what I have:
 
 $ grep -i font /boot/config-$(uname -r)
 # CONFIG_FONTS is not set
 CONFIG_FONT_8x8=y
 CONFIG_FONT_8x16=y
 
 (I use a self-compiled kernel, therefore I do not know how the stock
  Debian kernels are set up in that respect.)

My stock kernel (2.4.27-3-k7) gives the same settings, but doesn't let
me change anything. In fact it seems to ignore any of the vga= options,
including vga=ask. Here's what I see in dmesg's output:

Kernel command line: root=/dev/hda5 ro vga=4 hdc=ide-scsi hdd=ide-scsi
vga=791
Initializing CPU#0
Detected 2104.783 MHz processor.
Console: colour VGA+ 80x30

This is sad because it's a non-X system and I'd like to see some more
info on the console screen.

Thanks for any hints,
--Daniel


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: How to get those nice console fonts?

[Digby Tarvin]

On Tue, Jan 16, 2007 at 02:00:53PM +0100, Daniel Haude wrote:
 Florian Kulzer wrote:
 
  I use vga=0x303 and that looks exactly like Knoppix's fonts on my
  terminals. However, I think this also depends on the kernel
  configuration options related to the console fonts. Here is what I have:
  
  $ grep -i font /boot/config-$(uname -r)
  # CONFIG_FONTS is not set
  CONFIG_FONT_8x8=y
  CONFIG_FONT_8x16=y
  
  (I use a self-compiled kernel, therefore I do not know how the stock
   Debian kernels are set up in that respect.)
 
 My stock kernel (2.4.27-3-k7) gives the same settings, but doesn't let
 me change anything. In fact it seems to ignore any of the vga= options,
 including vga=ask. Here's what I see in dmesg's output:
 
 Kernel command line: root=/dev/hda5 ro vga=4 hdc=ide-scsi hdd=ide-scsi
 vga=791
 Initializing CPU#0
 Detected 2104.783 MHz processor.
 Console: colour VGA+ 80x30
 
 This is sad because it's a non-X system and I'd like to see some more
 info on the console screen.
 
 Thanks for any hints,

I found by accident that I got a *much* nicer font when I rebuilt
my kernel with a framebuffer driver. Otherwise I assume the system
is using some 'lowest common denominator' graphics which provides
limited font options. 

I still have to explore all of the other things one can do with
the framebuffer driver, like the fancy graphics during boot that
so many other distros come with as standard. 

A little superficial, but the sort of thing that is quite important
if you want convince non-technical people that it is a professional
quality system.

Regards,
DigbyT
-- 
Digby R. S. Tarvin  digbyt(at)digbyt.com
http://www.digbyt.com


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: How to get those nice console fonts?

[Angelo Bertolli]

Daniel Haude wrote:

Hello,

I'd like to have my console (non-X) fonts small and neat like Knoppix's.
I tried the various vga=xxx kernel options but all of them produced
bigger and uglier fonts.

How is it done?
  


I don't really  know how to change the fonts to any font that I want, 
but if I install the console-setup package, it automatically changes the 
fonts to a nicer version for me.


Angelo


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: How to get those nice console fonts?

[Alan Ianson]

On Tue January 16 2007 07:53, Angelo Bertolli wrote:
 Daniel Haude wrote:
  Hello,
 
  I'd like to have my console (non-X) fonts small and neat like Knoppix's.
  I tried the various vga=xxx kernel options but all of them produced
  bigger and uglier fonts.
 
  How is it done?

 I don't really  know how to change the fonts to any font that I want,
 but if I install the console-setup package, it automatically changes the
 fonts to a nicer version for me.

I have never looked at console-setup, must have a look at it. I always edit 
the /etc/console-tools/config file and set it to use the font I want for the 
console, default8x16 in my case.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: How to get those nice console fonts?

[Andrew Sackville-West]

On Tue, Jan 16, 2007 at 02:00:53PM +0100, Daniel Haude wrote:
 Florian Kulzer wrote:
 
  I use vga=0x303 and that looks exactly like Knoppix's fonts on my
  terminals. However, I think this also depends on the kernel
  configuration options related to the console fonts. Here is what I have:
  
  $ grep -i font /boot/config-$(uname -r)
  # CONFIG_FONTS is not set
  CONFIG_FONT_8x8=y
  CONFIG_FONT_8x16=y
  
  (I use a self-compiled kernel, therefore I do not know how the stock
   Debian kernels are set up in that respect.)
 
 My stock kernel (2.4.27-3-k7) gives the same settings, but doesn't let
 me change anything. In fact it seems to ignore any of the vga= options,
 including vga=ask. Here's what I see in dmesg's output:
 
 Kernel command line: root=/dev/hda5 ro vga=4 hdc=ide-scsi hdd=ide-scsi
 vga=791
 Initializing CPU#0
 Detected 2104.783 MHz processor.
 Console: colour VGA+ 80x30

I don't know much about this, but you seem to have 2 vga= options
above. that could be part of the problem.

A



signature.asc
Description: Digital signature

Re: How to get those nice console fonts?

[Douglas Tutty]

On Tue, Jan 16, 2007 at 12:04:37PM +0100, Daniel Haude wrote:
 Hello,
 
 I'd like to have my console (non-X) fonts small and neat like Knoppix's.
 I tried the various vga=xxx kernel options but all of them produced
 bigger and uglier fonts.
 
 How is it done?

Install the kbd package and configure it.  It brings in console-tools
which allows you to choose fonts.  This does not require setting up any
framebuffers.  The last time I used it, it worked great.  I plan to set
it up on my new box (21 screen) but there's no point on my current box
(9 screen).

Doug.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: console fonts

[Michelle Konzack]

Am 2005-01-31 01:18:21, schrieb sigi:
 moin!

 meinst du locales? da waehlst du einfach [EMAIL PROTECTED] aus, und 
 hast dein ¤ in der konsole...

Bei spanisch oder türkisch auch ?

Der Originalfond der bei der Installation installiert wird hat
KEIN ¤ Symbol, also mußte in die /etc/console-tools/config

SCREEN_FONT=lat0-16

eintragen, oder wenn Du UTF-8 mit latin, arabisch, cyrilisch
und hebräisch verwendest eben

SCREEN_FONT=LatArCyrHeb-16

Nur das ist nirgends beschrieben, welchen FONT du zu verwenden
hast.  Das geht nicht mal unter SARG.

Sowas nennt sich dann Benutzerfreundlich.

Normalerweise sollte der console SCREEN_FONT zusammen mit der
Keymap ausgewählt werden.

 sigi.

Greetings
Michelle

-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/ 
Michelle Konzack   Apt. 917  ICQ #328449886
   50, rue de Soultz MSM LinuxMichi
0033/3/8845235667100 Strasbourg/France   IRC #Debian (irc.icq.com)


signature.pgp
Description: Digital signature

Re: console fonts

[Felix M. Palmen]

Hallo Michelle,

* Michelle Konzack [EMAIL PROTECTED] [20050131 00:33]:
 Es geht aber nicht um mich, sondern um Normalanwender...  Wer weis
 denn, welchen FONT er einzustellen hat, wenn er das ¤ haben will ?

Normalanweder werden das in aller Regel nicht brauchen :) Wenn sie
/überhaupt/ etwas direkt an der Konsole machen, dann Dinge, die mit
us-ascii problemlos zurechtkommen.

Es gibt allerdings das Paket fonty mit weiteren Schriftarten für die
Konsole, das lässt sich auch über debconf konfigurieren.

Grüße, Felix

-- 
 | /\   ASCII Ribbon   | Felix M. Palmen (Zirias)http://zirias.ath.cx/ |
 | \ / Campaign Against | [EMAIL PROTECTED]  encrypted mail welcome |
 |  XHTML In Mail   | PGP key: http://zirias.ath.cx/pub.txt |
 | / \ And News | ED9B 62D0 BE39 32F9 2488 5D0C 8177 9D80 5ECF F683 |


signature.asc
Description: Digital signature

Re: console Fonts Umlaute

[Markus Feldmann]

Am Samstag, 29. Januar 2005 20:09 schrieb Andreas Pakulat:
  Oder aber ich muss dem kdm noch sagen, dass er in der ~/.xsession
  oder /etc/X11/Xsession.d/xsession nachgucken soll nach weiteren
  Variablen. Was meins du ?

 Kannst du nicht. Die Frage ist: Welche Session wählst du im kdm aus
 wenn du dich einloggst? Default(oder Debian, bin nicht ganz sicher)
 sollte $HOME/.xsession ausführen, wenn in dieser die Variablen und am
 Ende /usr/bin/startkde stehen solltest du ein KDE bekommen welches mit
 UTF-8 läuft.

Hallo,

habe es endlich geschafft mit dem ü,ö,ä obwohl ich nicht genau weiss was der 
Login Manager gemacht hat.
1. Ich habe den gdm als standard Login-manager definiert, in dem ich es über 
dselect einmal deinstalliert und wieder installiert habe danach hat mich 
dselect gefragt ob ich kdm,xdm oder gdm haben will. Habe gdm genommen.
2. Habe beim Login( bei dem Loginmanager gdm) mir die Sprache de_DE.UTF-8 
ausgesucht und dann mit dem User Markus angemeldet, da fragte er mich noch, 
bevor mein kde-desktop gestartet wurde, ob ich die Sprache de_DE.UTF-8 als 
Vorgabe nehmen will, dass habe ich bejaht.

Und das wars, hoffe ich.

Mal gucken was ich als nächstes wieder für ein Problem aufgabel. :-)
Fortsetzung folgt. :-)

mfg Markus

console fonts

[Michelle Konzack]

Hallo, 

mit 'dpkg-reconfigure console-data' kann man ja eine andere Keymap
auswhlen, aber wie kann man den Font neu setzen, wenn man nicht
/etc/console-tools/config editieren will oder aus der Unzahl von
Fonts nicht weis, welcher zu nehmen ist ?

Ich habe ber /usr/share/consolefonts keinerlei informationen
gefunden die mirweitergeholfen htten.

Greetings
Michelle

-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/ 
Michelle Konzack   Apt. 917  ICQ #328449886
   50, rue de Soultz MSM LinuxMichi
0033/3/8845235667100 Strasbourg/France   IRC #Debian (irc.icq.com)


signature.pgp
Description: Digital signature

Re: console fonts

[Felix M. Palmen]

Hallo Michelle,

* Michelle Konzack [EMAIL PROTECTED] [20050130 23:05]:
 mit 'dpkg-reconfigure console-data' kann man ja eine andere Keymap
 auswhlen, aber wie kann man den Font neu setzen, wenn man nicht
 /etc/console-tools/config editieren will oder aus der Unzahl von
 Fonts nicht weis, welcher zu nehmen ist ?

Du suchst consolechars. Verrt brigens auch ein kurzer Blick in
/etc/init.d/console-screen.sh

Gre, Felix

-- 
 | /\   ASCII Ribbon   | Felix M. Palmen (Zirias)http://zirias.ath.cx/ |
 | \ / Campaign Against | [EMAIL PROTECTED]  encrypted mail welcome |
 |  XHTML In Mail   | PGP key: http://zirias.ath.cx/pub.txt |
 | / \ And News | ED9B 62D0 BE39 32F9 2488 5D0C 8177 9D80 5ECF F683 |


signature.asc
Description: Digital signature

Re: console fonts

[Michelle Konzack]

Am 2005-01-30 23:53:04, schrieb Felix M. Palmen:
 Hallo Michelle,
 
 * Michelle Konzack [EMAIL PROTECTED] [20050130 23:05]:
  mit 'dpkg-reconfigure console-data' kann man ja eine andere Keymap
  ausw???hlen, aber wie kann man den Font neu setzen, wenn man nicht
  /etc/console-tools/config editieren will oder aus der Unzahl von
  Fonts nicht weis, welcher zu nehmen ist ?
 
 Du suchst consolechars. Verrät übrigens auch ein kurzer Blick in
 /etc/init.d/console-screen.sh

Das kenne ich schon seit ewigkeiten...

Es geht aber nicht um mich, sondern um Normalanwender...  Wer weis
denn, welchen FONT er einzustellen hat, wenn er das ¤ haben will ?

Oder Du mußt eine andere Sprache wählen ?

Der Font wird einmal bei der Installation eingestellt und kann dann
mittels 'dpkg-reconfigure' nicht mehr geändert werden...

 Grüße, Felix

Greetings
Michelle

-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/ 
Michelle Konzack   Apt. 917  ICQ #328449886
   50, rue de Soultz MSM LinuxMichi
0033/3/8845235667100 Strasbourg/France   IRC #Debian (irc.icq.com)


signature.pgp
Description: Digital signature

Re: console fonts

[sigi]

moin!

On Mon, Jan 31, 2005 at 12:33:04AM +0100, Michelle Konzack wrote:
 
 Es geht aber nicht um mich, sondern um Normalanwender...  Wer weis
 denn, welchen FONT er einzustellen hat, wenn er das  haben will ?
 
 Oder Du mut eine andere Sprache whlen ?

meinst du locales? da waehlst du einfach [EMAIL PROTECTED] aus, und 
hast dein  in der konsole...

sigi.


-- 
 | /\   ASCII ribbon   | **
 | \ / campaign against |  my gpg-key:
 |  XHTML in email  |  www.muffrika.net/gpg-key.txt
 | / \ and news | **

Re: console Fonts Umlaute

[Andreas Pakulat]

On 29.Jan 2005 - 01:24:41, Markus Feldmann wrote:
 ich nehme lieber die gnome-console, die scheint bestens zu funzen ohne das 
 ich 
 da nerven verlieren muss.

Bei der konsole von KDE geht das auch von alleine. 

 Kmail scheint damit nicht klar zu kommen wenn ich Umlaute tippe, z.b.
 
 Habe mal eine Mail an mich selbst geschickt mit utf-8 Zeichensatz,
 wo ich die Umlaute
 ü - ue
 ö - oe
 ä - ae
 eingegeben hatte. Schon bei der Erstellung der Mail kann ich diese Umlaute 
 nicht lesen. Und beim Empfang auch nicht.

Dann benutzt dein KDE kein UTF-8. Ich hatte schon geschrieben, das
bash.bashrc und profile in /etc bei grafischem Login nicht eingelesen
werden und wie du das umgehen kannst. Alternativ kannst du ja mal
ausprobieren, was passiert wenn du dich am Textprompt (Alt+F1)
anmeldets, dann den grafischen Login stoppst (z.B. /etc/init.d/kdm
stop) und dann startx eingibst. 

Andreas

-- 
If you think last Tuesday was a drag, wait till you see what happens tomorrow!


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: console Fonts Umlaute

[Andreas Pakulat]

On 28.Jan 2005 - 17:51:54, Markus Feldmann wrote:
 Am Freitag, 28. Januar 2005 11:56 schrieb Nico Jochens:
 Ich erhielt die folgende Fehlermeldung als ich unter Einstellungen(in meiner 
 konsole)-Schrift-Unicode umstellen wollte:
 ***
 Schriftart -misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1 nicht 
 gefunden.
 Hilfe finden Sie in README.linux.console.
 ***
 
 Werde erstmal gucken was es mit dieser fehlenden Schrift auf sich hat.

Du musst nicht unbedingt Unicode nehmen, hier läuft Linux. In
jedem Fall muss der dabei benutzte Font aber das Charset iso10646
enthalten. Du solltest xfonts-100dpi(-transcoded),
xfont-75dpi(-transcoded) und xfonts-base(-transcoded) sowie
xfonts-konsole installieren.

Andreas

-- 
A visit to a strange place will bring fresh work.


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: console Fonts Umlaute

[Markus Feldmann]

Am Freitag, 28. Januar 2005 12:41 schrieb Andreas Pakulat:
 1. Wenn du immer ber die Default-Sitzung dich einloggst kannst du
 eine Datei .xsession in deinem Home anlegen in dem mindestens
 folgendes stehen sollte:
 export LANG=de_DE.UTF-8
 x-session-manager

 2. Fge das LANG=de_DE.UTF-8 in eine neue Datei in /etc/XSession.d/
 ein. Ich bin mir nicht ganz sicher, dass das fr alle Sitzungen gilt,
 aber ich denke schon...

Ok ich habe mich dazu durchgerungen dies global fuer alle Sitzungen zu machen,
habe also 2 Dateien anglegt:
1. /etc/X11/Xsession.d/xsession

2. /home/markus/.xsession

in denen beide folgendes entahlten ist:
export LANG=de_DE.UTF-8

Du musst nicht unbedingt Unicode nehmen, hier luft Linux. In
jedem Fall muss der dabei benutzte Font aber das Charset iso10646
enthalten. Du solltest xfonts-100dpi(-transcoded),
xfont-75dpi(-transcoded) und xfonts-base(-transcoded) sowie
xfonts-konsole installieren.

Habe ich alle installiert.
und noch zustzliche fonts, plus den xfs der anscheinend auch wichtig sein 
kann oder, der soll wohl fonts bereit stellen weis aber nicht ob mein client 
das auch ohne ihn hinkriegt?


Ich habe weiter unten einen kleinen Auschnitt meiner Verzeichnisstruktur 
von /etc/X11 zum Schluss dieser Mail angehaengt, da ich mir noch nicht ganz 
sicher war ob du denn /etc/Xsession.d/ oder /etc/X11/Xsession.d/ meintest.

mfg Markus


***
[EMAIL PROTECTED]: ls -R   -U /etc/X11/ 
etc/X11/:
X
de
fr
fs
ja
ro
xdm
xkb
xsm
Xresources
rgb.txt
cursors
fonts
xserver
xinit
sysconfig
Xsession
ja_JP.eucJP
XF86Config-4.custom
applnk
ko_KR.eucKR
XF86Config-4
default-display-manager
Xsession.d
rstart
Xwrapper.config
Xsession.options
app-defaults

/etc/X11/de:
app-defaults

/etc/X11/de/app-defaults:
XEmacs

/etc/X11/fr:
app-defaults

/etc/X11/fr/app-defaults:
XEmacs

/etc/X11/fs:
config.bak
config
xfs.options

/etc/X11/ja:
app-defaults

/etc/X11/ja/app-defaults:
XEmacs

/etc/X11/ro:
app-defaults

/etc/X11/ro/app-defaults:
XEmacs

/etc/X11/xdm:
Xresources
Xaccess
Xservers
Xsession
Xreset
Xstartup
xdm-config
xdm.options
pixmaps
Xwilling

/etc/X11/xdm/pixmaps:
debian.xpm
debianbw.xpm
XFree86.xpm
XFree86bw.xpm

/etc/X11/xkb:
README.config
xkbcomp
geometry.dir
rules
types
README
compat.dir
semantics
keymap.dir
types.dir
geometry
compat
compiled
symbols
keymap
symbols.dir
keycodes.dir
keycodes
README.enhancing

/etc/X11/xkb/rules:
sgi
sun
README
sgi.lst
xfree86.lst
xfree86.xml
xfree86-it.lst
sun.lst
xfree86

/etc/X11/xkb/types:
pc
caps
default
mousekeys
basic
extra
README
complete
iso9995

/etc/X11/xkb/semantics:
default
basic
xtest
complete

/etc/X11/xkb/geometry:
hp
pc
ibm
nec
sgi
sun
dell
sony
digital
kinesis
amiga
README
northgate
omnibook
everex
fujitsu
keytronic
ataritt
winbook
microsoft
chicony
macintosh

/etc/X11/xkb/geometry/ibm:
thinkpad

/etc/X11/xkb/geometry/sgi:
O2
indy
indigo

/etc/X11/xkb/geometry/digital:
lk
pc
unix

/etc/X11/xkb/compat:
pc
leds
misc
pc98
default
mousekeys
norepeat
basic
japan
xtest
README
complete
keypad
accessx
group_led
iso9995
xfree86

/etc/X11/xkb/symbols:
al
am
be
ar
bg
ca
az
br
bs
by
de
dk
cz
ee
el
es
fi
gb
fr
hp
ie
hr
hu
il
ir
is
it
iu
jp
la
lo
lt
mk
lv
ml
mm
mt
nl
no
pc
pl
pt
ro
se
si
ru
sk
sr
th
tj
ua
tr
us
vn
yu
ben
dev
guj
gur
kan
nec
ori
pl2
sgi
tel
sun
tml
syr
ctrl
czsk
inet
lock
ralt
sony
tr_f
compose
digital
de_CH
en_US
ge_la
ge_ru
fr_CH
group
hr_US
hu_US
mt_us
ogham
pc104
syr_phonetic
sapmi
se_FI
se_NO
se_SE
README
ru_yawerty
altwin
dvorak
keypad
fujitsu
level3
lt_std
iso9995-3
srvr_ctrl
th_pat
th_tis
ca_enhanced
us_intl
hu_qwerty
il_phonetic
cz_qwerty
us_group2
us_group3
xfree68
macintosh
sk_qwerty

/etc/X11/xkb/symbols/hp:
us

/etc/X11/xkb/symbols/pc:
al
am
be
ar
bg
ca
br
ch
by
de
dk
cz
ee
el
es
fi
gb
fr
ie
hr
hu
il
ir
is
it
iu
jp
la
lo
lt
mk
lv
ml
mm
mn
mt
nl
no
pc
pl
pt
ro
se
si
ru
sk
sr
th
tj
ua
tr
us
vn
yu
ben
dev
guj
gur
kan
ori
pl2
tel
tml
syr
en_US
ge_la
ge_ru
latin
mt_us
ogham
syr_phonetic
sapmi
fr-latin9
dvorak
th_pat
th_tis
us_intl
il_phonetic
cz_qwerty
sk_qwerty

/etc/X11/xkb/symbols/nec:
jp

/etc/X11/xkb/symbols/sgi:
jp

/etc/X11/xkb/symbols/sun:
se
us

/etc/X11/xkb/symbols/sony:
us

/etc/X11/xkb/symbols/digital:
lk
pc
us
vt

/etc/X11/xkb/symbols/fujitsu:
jp
us

/etc/X11/xkb/symbols/xfree68:
amiga
ataritt

/etc/X11/xkb/symbols/macintosh:
de
dk
es
fi
gb
fr
it
nl
no
pt
se
us
de_CH
fr_CH

/etc/X11/xkb/keymap:
sgi
sun
sony
digital
amiga
README
ataritt
xfree86
xfree98
macintosh

/etc/X11/xkb/keymap/sgi:
be
bg
ca
de
dk
cz
es
fi
gb
fr
hu
it
jp
no
pl
pt
se
ru
sk
th
us
de_CH
en_US
fr_CH
dvorak
cz_qwerty
sk_qwerty

/etc/X11/xkb/keymap/sun:
de
es
fi
fr
no
pl
se
ru
uk
us

/etc/X11/xkb/keymap/digital:
us

/etc/X11/xkb/keycodes:
hp
ibm
sgi
sun
sony
digital
amiga
README
powerpcps2
fujitsu
riscpc
aliases
ataritt
xfree86
xfree98
macintosh

/etc/X11/xkb/keycodes/sgi:
indy
iris
indigo

/etc/X11/xkb/keycodes/digital:
lk

Re: console Fonts Umlaute

[Markus Feldmann]

Mein kmail funzt trotzdem nicht. :-(

Wie kann ich denn ueberpruefen, welche Umgebungsvariblen ich unter KDE habe?

Wie kann ich ueberpruefen ob die Fonts auch wirklich da sind wo sie 
hingehoeren?

mfg Markus


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: console Fonts Umlaute

[Andreas Pakulat]

On 29.Jan 2005 - 13:17:13, Markus Feldmann wrote:
 Am Freitag, 28. Januar 2005 12:41 schrieb Andreas Pakulat:
 Habe ich alle installiert.
 und noch zusätzliche fonts,

Siehst du das^ ? Irgendwie kodiert dein KMail die Mail falsch, es
macht aus jedem Umlaut ein doppelt UTF-8 kodiertes Zeichen, sprich
wenn ich den Satz nehmen würde und nach latin1 (== de_DE) kodieren
hätte ich einen normalen UTF-8 kodierten Satz und das ä würde
angezeigt.

 plus den xfs der anscheinend auch wichtig sein 
 kann oder, der soll wohl fonts bereit stellen weis aber nicht ob mein client 
 das auch ohne ihn hinkriegt?

Der ist unnötig, xfs dient zur Verteilung von Fonts in einem Netzwerk.
Du solltest die /etc/X11/XF86Config-4 noch überprüfen ob die
transcoded Fonts auch benutzt werden, dazu sollten Einträge der
folgenden Art vorhanden sein:

FontPath /usr/lib/X11/fonts/misc:unscaled
FontPath /usr/lib/X11/fonts/100dpi:unscaled

zusätzlich zu entsprechenden Angaben ohne :unscaled und vor den
Angaben ohne :unscaled plaziert.

 Ich habe weiter unten einen kleinen Auschnitt meiner Verzeichnisstruktur 
 von /etc/X11 zum Schluss dieser Mail angehaengt, da ich mir noch nicht ganz 
 sicher war ob du denn /etc/Xsession.d/ oder /etc/X11/Xsession.d/ meintest.

Schrub ich /etc/Xsession.d? Ich meinte natürlich /etc/X11/Xsession.d

Was du uns nicht erzählst: Funktioniert nun alles oder nicht?

Andreas

-- 
You will remember something that you should not have forgotten.


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: console Fonts Umlaute

[Markus Feldmann]

Am Samstag, 29. Januar 2005 14:18 schrieb Andreas Pakulat:

  plus den xfs der anscheinend auch wichtig sein

Den habe ich wieder deinstalliert.

 Du solltest die /etc/X11/XF86Config-4 noch überprüfen ob die
 transcoded Fonts auch benutzt werden, dazu sollten Einträge der
 folgenden Art vorhanden sein:

 FontPath /usr/lib/X11/fonts/misc:unscaled
 FontPath /usr/lib/X11/fonts/100dpi:unscaled

 zusätzlich zu entsprechenden Angaben ohne :unscaled und vor den
 Angaben ohne :unscaled plaziert.

Scheint da zu sein abgesehen davon das meine X Konfiguration(nvidia) noch 
nicht ganz glücklich ist.
Aber darueber will ich jetzt noch nicht reden, dies wird ein neues Kapitel.

Hier ein Auszug meiner /etc/X11/XF86Config-4 Datei

*
feld-bert:/etc/X11# cat XF86Config-4
# XF86Config-4 (XFree86 X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the XF86Config-4 manual page.
# (Type man XF86Config-4 at the shell prompt.)
#
# This file is automatically updated on xserver-xfree86 package upgrades 
*only*
# if it has not been modified since the last upgrade of the xserver-xfree86
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following commands as root:
#
#   cp /etc/X11/XF86Config-4 /etc/X11/XF86Config-4.custom
#   md5sum /etc/X11/XF86Config-4 /var/lib/xfree86/XF86Config-4.md5sum
#   dpkg-reconfigure xserver-xfree86

Section Files
FontPathunix/:7100# local font server
# if the local font server has problems, we can fall back on these
FontPath/usr/lib/X11/fonts/misc
FontPath/usr/lib/X11/fonts/cyrillic
FontPath/usr/lib/X11/fonts/100dpi/:unscaled
FontPath/usr/lib/X11/fonts/75dpi/:unscaled
FontPath/usr/lib/X11/fonts/Type1
FontPath/usr/lib/X11/fonts/CID
FontPath/usr/lib/X11/fonts/Speedo
FontPath/usr/lib/X11/fonts/100dpi
FontPath/usr/lib/X11/fonts/75dpi
EndSection

Section Module
Loaddbe
Loadddc
Loadextmod
Loadfreetype
Loadglx
Loadtype1
EndSection

Section InputDevice
Identifier  Generic Keyboard
Driver  keyboard
Option  CoreKeyboard
Option  XkbRules  xfree86
Option  XkbModel  pc105
Option  XkbLayout de
Option  XkbVariantnodeadkeys
EndSection

Section InputDevice
Identifier  Configured Mouse
Driver  mouse
Option  CorePointer
Option  Device/dev/psaux
Option  Protocol  ExplorerPS/2
Option  ZAxisMapping  4 5
EndSection
Section InputDevice
Identifier  Generic Mouse
Driver  mouse
Option  SendCoreEventstrue
Option  Device/dev/input/mice
Option  Protocol  ImPS/2
Option  ZAxisMapping  4 5
EndSection

Section Device
Identifier  geforce4
Driver  vesa
Option  UseFBDev  true
Option  NoLogotrue
EndSection

Section Monitor
Identifier  Generic Monitor
HorizSync   30-96
VertRefresh 50-160
Option  DPMS
EndSection

Section Screen
Identifier  Default Screen
Device  geforce4
Monitor Generic Monitor
DefaultDepth16
SubSection Display
Depth   1
Modes   1024x768 800x600 640x480
EndSubSection
SubSection Display
Depth   4
Modes   1024x768 800x600 640x480
EndSubSection
SubSection Display
Depth   8
Modes   1024x768 800x600 640x480
EndSubSection
SubSection Display
Depth   15
Modes   1024x768 800x600 640x480
EndSubSection
SubSection Display
Depth   16
Modes   1024x768 800x600 640x480
EndSubSection
SubSection Display
Depth   24
Modes   1024x768 800x600 640x480
EndSubSection
EndSection

Section ServerLayout
Identifier  Default Layout
Screen  Default Screen
InputDevice Generic Keyboard
InputDevice Configured Mouse
InputDevice Generic Mouse
EndSection

Section DRI
Mode0666
EndSection

Re: console Fonts Umlaute

[Markus Feldmann]

Am Samstag, 29. Januar 2005 14:18 schrieb Andreas Pakulat:

 Was du uns nicht erzählst: Funktioniert nun alles oder nicht?

Habe noch was wichtiges vergessen, wenn ich ich
/etc/ninit.d/kdm stop
startx

mit dem root Benutzer mache und dann kmail aufrufe um eine neue
Mail zu verfaassen funzt das mit den Umlauten, sieht also so aus als wenn ihn 
meine Variablen teilweise nicht interessieren.

Vielleicht sollte ich noch dazu sagen das ich mit dem root nicht die kde 
Oberfäche benutze sondern die gnome Oberfläche.

Oder aber ich muss dem kdm noch sagen, dass er in der ~/.xsession 
oder /etc/X11/Xsession.d/xsession nachgucken soll nach weiteren Variablen.
Was meins du ?

mfg Markus

Re: console Fonts Umlaute

[Markus Feldmann]

Am Samstag, 29. Januar 2005 14:18 schrieb Andreas Pakulat:

  plus den xfs der anscheinend auch wichtig sein

Den habe ich wieder deinstalliert.

 Du solltest die /etc/X11/XF86Config-4 noch überprüfen ob die
 transcoded Fonts auch benutzt werden, dazu sollten Einträge der
 folgenden Art vorhanden sein:

 FontPath /usr/lib/X11/fonts/misc:unscaled
 FontPath /usr/lib/X11/fonts/100dpi:unscaled

 zusätzlich zu entsprechenden Angaben ohne :unscaled und vor den
 Angaben ohne :unscaled plaziert.

Scheint da zu sein abgesehen davon das meine X Konfiguration(nvidia) noch 
nicht ganz glücklich ist.
Aber darueber will ich jetzt noch nicht reden, dies wird ein neues Kapitel.

Hier ein Auszug meiner /etc/X11/XF86Config-4 Datei

*
feld-bert:/etc/X11# cat XF86Config-4
# XF86Config-4 (XFree86 X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the XF86Config-4 manual page.
# (Type man XF86Config-4 at the shell prompt.)
#
# This file is automatically updated on xserver-xfree86 package upgrades 
*only*
# if it has not been modified since the last upgrade of the xserver-xfree86
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following commands as root:
#
#   cp /etc/X11/XF86Config-4 /etc/X11/XF86Config-4.custom
#   md5sum /etc/X11/XF86Config-4 /var/lib/xfree86/XF86Config-4.md5sum
#   dpkg-reconfigure xserver-xfree86

Section Files
        FontPath        unix/:7100                    # local font server
        # if the local font server has problems, we can fall back on these
        FontPath        /usr/lib/X11/fonts/misc
        FontPath        /usr/lib/X11/fonts/cyrillic
        FontPath        /usr/lib/X11/fonts/100dpi/:unscaled
        FontPath        /usr/lib/X11/fonts/75dpi/:unscaled
        FontPath        /usr/lib/X11/fonts/Type1
        FontPath        /usr/lib/X11/fonts/CID
        FontPath        /usr/lib/X11/fonts/Speedo
        FontPath        /usr/lib/X11/fonts/100dpi
        FontPath        /usr/lib/X11/fonts/75dpi
EndSection

Section Module
        Load    dbe
        Load    ddc
        Load    extmod
        Load    freetype
        Load    glx
        Load    type1
EndSection

Section InputDevice
        Identifier      Generic Keyboard
        Driver          keyboard
        Option          CoreKeyboard
        Option          XkbRules      xfree86
        Option          XkbModel      pc105
        Option          XkbLayout     de
        Option          XkbVariant    nodeadkeys
EndSection

Section InputDevice
        Identifier      Configured Mouse
        Driver          mouse
        Option          CorePointer
        Option          Device                /dev/psaux
        Option          Protocol              ExplorerPS/2
        Option          ZAxisMapping          4 5
EndSection
Section InputDevice
        Identifier      Generic Mouse
        Driver          mouse
        Option          SendCoreEvents        true
        Option          Device                /dev/input/mice
        Option          Protocol              ImPS/2
        Option          ZAxisMapping          4 5
EndSection

Section Device
        Identifier      geforce4
        Driver          vesa
        Option          UseFBDev              true
        Option          NoLogo                true
EndSection

Section Monitor
        Identifier      Generic Monitor
        HorizSync       30-96
        VertRefresh     50-160
        Option          DPMS
EndSection

Section Screen
        Identifier      Default Screen
        Device          geforce4
        Monitor         Generic Monitor
        DefaultDepth    16
        SubSection Display
                Depth           1
                Modes           1024x768 800x600 640x480
        EndSubSection
        SubSection Display
                Depth           4
                Modes           1024x768 800x600 640x480
        EndSubSection
        SubSection Display
                Depth           8
                Modes           1024x768 800x600 640x480
        EndSubSection
        SubSection Display
                Depth           15
                Modes           1024x768 800x600 640x480
        EndSubSection
        SubSection Display
                Depth           16
                Modes           1024x768 800x600 640x480
        EndSubSection
        SubSection Display
                Depth           24
                Modes           1024x768 800x600 640x480
        EndSubSection
EndSection

Section ServerLayout
        Identifier      Default Layout
        Screen          Default Screen
        InputDevice     Generic Keyboard
        InputDevice     Configured Mouse
        InputDevice     Generic Mouse
EndSection

Section DRI
        Mode    0666
EndSection

Re: console Fonts Umlaute

[Andreas Pakulat]

On 29.Jan 2005 - 15:42:59, Markus Feldmann wrote:
 Am Samstag, 29. Januar 2005 14:18 schrieb Andreas Pakulat:
  Was du uns nicht erzählst: Funktioniert nun alles oder nicht?
 
 Habe noch was wichtiges vergessen, wenn ich ich
 /etc/ninit.d/kdm stop
 startx
 
 mit dem root Benutzer mache und dann kmail aufrufe um eine neue
 Mail zu verfaassen funzt das mit den Umlauten, sieht also so aus als wenn ihn 
 meine Variablen teilweise nicht interessieren.

Lass das mit dem root-Benutzer, du solltest das als normaler User
probieren. Davon abgesehen: Korrekt der KDM interessiert sicht nicht
für deine Variablen

 Vielleicht sollte ich noch dazu sagen das ich mit dem root nicht die kde 
 Oberfäche benutze sondern die gnome Oberfläche.

In jedem fall ist die aber mit UTF-8.

 Oder aber ich muss dem kdm noch sagen, dass er in der ~/.xsession 
 oder /etc/X11/Xsession.d/xsession nachgucken soll nach weiteren Variablen.
 Was meins du ?

Kannst du nicht. Die Frage ist: Welche Session wählst du im kdm aus
wenn du dich einloggst? Default(oder Debian, bin nicht ganz sicher)
sollte $HOME/.xsession ausführen, wenn in dieser die Variablen und am
Ende /usr/bin/startkde stehen solltest du ein KDE bekommen welches mit
UTF-8 läuft.

-- 
Be careful!  Is it classified?


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: console Fonts Umlaute

[Markus Feldmann]

Am Freitag, 28. Januar 2005 02:10 schrieb Andreas Pakulat:
 On 28.Jan 2005 - 01:32:47, Markus Feldmann wrote:
  Andreas Pakulat wrote:
   On 27.Jan 2005 - 13:18:31, Markus Feldmann wrote:
   Hallo liebe Newsleser,

 Nee, dies ist eine ML.

   Auf der console muss man unicode_start ausführen, dann klappts auch
   mit den Umlauten. Wobei bei Sarge sollte das eigentlich automatisch
   passieren

 Sag mal, kannst du mal http://learn.to/quote lesen? Irgendwie
 zitierst du dasselbe doppelt...

   Auf der console muss man unicode_start ausführen, dann klappts auch
 
  habe es gemacht aber das hat nicht hingaunen
 
  feld-bert:/home/markus# unicode_start
  Won't set unicode mode: not a VT.
  feld-bert:/home/markus#
 
  Weiss Jemand was er mit VT meint?

 Ja, das du das in der konsole von KDE machst und nicht in der
 Console. VT = VirtualTerminal = Alt+F1-F6

 Hmm, du benutzt offensichtlich ein XTerm (bzw. einen anderen
 Terminal-Emulator unter X11), wenn ich mich nicht irre ist das XTerm
 das du benutzt aber nicht ganz UTF-8 fähig. Was benutzt du denn -
 konsole von KDE, XTerm, ETerm, gnome-terminal?

 Andreas

 --
 You will be reincarnated as a toad; and you will be much happier.
Hallo Andreas,

danke erstmal.
Du hattest recht aber irgendwie scheint der MC damit trotzdem nicht
zurecht zu kommen.
Unter KDE 3.3 benutze ich die console, gibts eine Möglichkeit den MC trotzdem 
richtig darzustellen. Auf die console kann ich auch verzichten.

Nur was soll ich statt dessen verwenden.

Achso und wegen meinen doppelt geschriebenen Emails, ich wollte eigentlich 
über knode Beiträge schreiebn und nicht über kmail, aber scheint wohl nicht 
hinzuhauen.
Weiss aber nicht warum.
Schreibst Du denn über einen Email,- oder über einen News-Client?

mfg Markus

Re: console Fonts Umlaute

[Nico Jochens]

On Fri, Jan 28, 2005 at 11:46:29AM +0100, Markus Feldmann wrote:
 Am Freitag, 28. Januar 2005 02:10 schrieb Andreas Pakulat:
  On 28.Jan 2005 - 01:32:47, Markus Feldmann wrote:
  
  []
 
  Hmm, du benutzt offensichtlich ein XTerm (bzw. einen anderen
  Terminal-Emulator unter X11), wenn ich mich nicht irre ist das XTerm
  das du benutzt aber nicht ganz UTF-8 fähig. Was benutzt du denn -
  konsole von KDE, XTerm, ETerm, gnome-terminal?
 
 danke erstmal.
 Du hattest recht aber irgendwie scheint der MC damit trotzdem nicht
 zurecht zu kommen.
 Unter KDE 3.3 benutze ich die console, gibts eine Möglichkeit den MC trotzdem 
 richtig darzustellen. Auf die console kann ich auch verzichten.
 
 Nur was soll ich statt dessen verwenden.

Gar nix. Wenn es tatsächlich das Programm Konsole (mit K) ist, das kann
definitiv UTF-8. Nur aterm, wterm und Eterm können kein UTF-8, alle
anderen ja.

schöne Grüße aus Hamburg,

Nico

-- 
It`s not a trick...it`s Linux!  |  web: www.linico.de
   ---°°--- |  mailto: [EMAIL PROTECTED]
  Nico Jochens - MCSE und CNA   |  Registered Linux User #313928
   Hamburg, Germany |  PGP-Signature: kommt noch

Re: console Fonts Umlaute

[Andreas Pakulat]

On 28.Jan 2005 - 11:46:29, Markus Feldmann wrote:
 Am Freitag, 28. Januar 2005 02:10 schrieb Andreas Pakulat:
  On 28.Jan 2005 - 01:32:47, Markus Feldmann wrote:
  Ja, das du das in der konsole von KDE machst und nicht in der
  Console. VT = VirtualTerminal = Alt+F1-F6
 
  Hmm, du benutzt offensichtlich ein XTerm (bzw. einen anderen
  Terminal-Emulator unter X11), wenn ich mich nicht irre ist das XTerm
  das du benutzt aber nicht ganz UTF-8 fähig. Was benutzt du denn -
  konsole von KDE, XTerm, ETerm, gnome-terminal?
 Hallo Andreas,

Irgendwie saugt dein Quotingstil immernoch. Bitte nur das zitieren auf
das man sich auch bezieht.

 danke erstmal.
 Du hattest recht aber irgendwie scheint der MC damit trotzdem nicht
 zurecht zu kommen.

Hier macht der (fast) keine Probleme. Das einzige was nicht geht ist
in dessen Kommandozeile Umlaute eingeben - da sollte man gleich mal
nen Bugreport schreiben...

 Unter KDE 3.3 benutze ich die console, gibts eine Möglichkeit den MC trotzdem 
 richtig darzustellen. Auf die console kann ich auch verzichten.

_k_onsole heisst das Teil und genau das nutze ich auch. Der mc stellt
ordentlich kodierte Dateinamen auch ordentlich dar. Werden die
Dateinamen denn ausserhalb eines mc bei nem Listing mittels ls
ordentlich dargestellt? Das einzige was mir noch einfällt: Laut deinem
ersten Posting setzt du die Sprache in /etc/bash.bashrc und
/etc/profile, das reicht eventuell nicht aus wenn du dich grafisch
einloggst. Dann werden die 2 Dateien nämlich nicht gelesen (IIRC) und
deine grafische Oberfläche läuft mit LANG=C... Um das zu ändern gibts
2 Möglichkeiten:

1. Wenn du immer über die Default-Sitzung dich einloggst kannst du
eine Datei .xsession in deinem Home anlegen in dem mindestens
folgendes stehen sollte:
export LANG=de_DE.UTF-8
x-session-manager

2. Füge das LANG=de_DE.UTF-8 in eine neue Datei in /etc/XSession.d/
ein. Ich bin mir nicht ganz sicher, dass das für alle Sitzungen gilt,
aber ich denke schon...

 Nur was soll ich statt dessen verwenden.

Die konsole ist vollkommen OK. Unterstützt UTF-8 wunderbar. 

 Achso und wegen meinen doppelt geschriebenen Emails, ich wollte eigentlich 
 über knode Beiträge schreiebn und nicht über kmail, aber scheint wohl nicht 
 hinzuhauen.
 Weiss aber nicht warum.

Die Emails sind ja nicht doppelt geschrieben, es ist halt nur: Du
quotest meine komplette Mail und dann nimmst du nochmal nen Teil
daraus und pastest ihn in deine Antwort hinein. Deswegen der Hinweis
auf http://learn.to/quote.

Davon abgesehen kamen diese Mail von dir über das Mail2News-Gateway,
was man sehr schön daran sehen kann, das der Referenes-Header korrekt
gesetzt ist.

 Schreibst Du denn über einen Email,- oder über einen News-Client?

Da dies eine ML ist schreibe ich natürlich mittels Emailclient.

Andreas

-- 
You will be winged by an anti-aircraft battery.


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: console Fonts Umlaute

[Andreas Kroschel]

* Markus Feldmann:

 Du hattest recht aber irgendwie scheint der MC damit trotzdem nicht
 zurecht zu kommen.
 Unter KDE 3.3 benutze ich die console, gibts eine Möglichkeit den MC
 trotzdem richtig darzustellen. Auf die console kann ich auch verzichten.

mc selbst ist es, der kein utf8 kann. Für die Suse-Version gibt es hier
http://www.suse.de/~nadvornik/mc.html Patches, das zu beheben, wobei hier
http://melkor.dnp.fmph.uniba.sk/~garabik/debian-utf8/HOWTO/howto.html
empfohlen wird, die gepatchte Redhat-Version zu verwenden.

Grüße,
kro
-- 
Veteran of the Bermuda Triangle Expeditionary Force 1990-1951


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: console Fonts Umlaute

[Christian Schmidt]

Hallo Markus,

Markus Feldmann, 28.01.2005 (d.m.y):

[Fullquote geloescht]

Bitte lies und beherzige http://learn.to/quote.

 Achso und wegen meinen doppelt geschriebenen Emails, ich wollte eigentlich 
 über knode Beiträge schreiebn und nicht über kmail, aber scheint wohl nicht 
 hinzuhauen.
 Weiss aber nicht warum.
 Schreibst Du denn über einen Email,- oder über einen News-Client?

Schau in die Header, da erfaehrst Du oftmals mehr.

Gruss,
Christian Schmidt
-- 
Es gibt Ableitungen, die sich nicht wesentlich unterscheiden.
-- Annegret Habel, Formale Sprachen


signature.asc
Description: Digital signature

Re: console Fonts Umlaute

[Markus Feldmann]

Am Freitag, 28. Januar 2005 11:56 schrieb Nico Jochens:
 Gar nix. Wenn es tatsächlich das Programm Konsole (mit K) ist, das kann
 definitiv UTF-8. Nur aterm, wterm und Eterm können kein UTF-8, alle
 anderen ja.

Hallo,
also ich habe die Anleitung unter
http://melkor.dnp.fmph.uniba.sk/~garabik/debian-utf8/HOWTO/howto.html
und kann nun auch im VT(Virtual Terminal, nicht die konsole unter KDE) 
Umlaute eintippen danke Jungs, aber die console unter KDE3.3
scheint dies nicht so richtig zu erfreuen.

Ich erhielt die folgende Fehlermeldung als ich unter Einstellungen(in meiner 
konsole)-Schrift-Unicode umstellen wollte:
***
Schriftart -misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1 nicht 
gefunden.
Hilfe finden Sie in README.linux.console.
***

Werde erstmal gucken was es mit dieser fehlenden Schrift auf sich hat.

mfg Markus

Re: console Fonts Umlaute

[Markus Feldmann]

ich nehme lieber die gnome-console, die scheint bestens zu funzen ohne das ich 
da nerven verlieren muss.

Kmail scheint damit nicht klar zu kommen wenn ich Umlaute tippe, z.b.

Habe mal eine Mail an mich selbst geschickt mit utf-8 Zeichensatz,
wo ich die Umlaute
 - ue
 - oe
 - ae
eingegeben hatte. Schon bei der Erstellung der Mail kann ich diese Umlaute 
nicht lesen. Und beim Empfang auch nicht.

mfg Markus

console Fonts Umlaute

[Markus Feldmann]

Hallo liebe Newsleser,

vielleicht kann mir ja jemand sagen wie ich dieses Problem beseitigen
kann.

Mein Problem ist das ich Dateinamen, Ordnernamen u.s.w. nicht mehr 
richtig dargestellt bekomme. dies gilt insbesondere wenn ich mit
dem mc arbeite,
Habe ein Screenshot davon gemacht im Amhang.
Hoffe es ist nicht zu groß.

X Apllikationen scheinen nicht davon betroffen zu sein.
Weiterhin habe ich bemerkt das er arge Probleme hat mit den Umalauten
in der Konsole, bash ... nur halt nicht mit X Programmen.
Wenn ich versuche einen einzelnen Umlaut-Buchstaben zu schreiben,
kommt gar kein Buchstabe raus.
Tippe ich 2 oder mehr ein kommt immer der (n-1) te Buchstabe
zu Tage also:
eingetippt --- auf dem Schirm erscheint
üä   --- ü
öä   --- ö
ää   --- ä
üöä  --- üö
ääü  --- ää
äöö  --- äö
u.s.w.


Habe versucht alles auf meinem Rechner auf Unicode umzustellen.

Hier nich ein paar Daten von meinem Rechner
Debian - Sarge
Kernel-Version 2.6.8

Nun ein paar Ausgaben die wichtig sind:
markus:-$ locale charmap
UTF-8
markus:-$ locale
LANG=de_DE.UTF-8
LC_CTYPE=de_DE.UTF-8
LC_NUMERIC=de_DE.UTF-8
LC_TIME=de_DE.UTF-8
LC_COLLATE=de_DE.UTF-8
LC_MONETARY=de_DE.UTF-8
LC_MESSAGES=de_DE.UTF-8
LC_PAPER=de_DE.UTF-8
LC_NAME=de_DE.UTF-8
LC_ADDRESS=de_DE.UTF-8
LC_TELEPHONE=de_DE.UTF-8
LC_MEASUREMENT=de_DE.UTF-8
LC_IDENTIFICATION=de_DE.UTF-8
LC_ALL=
markus:-$ locale -a
C
de_DE
[EMAIL PROTECTED]
de_DE.iso88591
[EMAIL PROTECTED]
de_DE.utf8
[EMAIL PROTECTED]
deutsch
german
POSIX
markus:~$ cat /etc/bash.bashrc | grep export
export LANG=de_DE.UTF-8
markus:~$ cat /etc/profile | grep export
export PATH PS1
export LANG=de_DE.UTF-8
markus:~$ 

mfg Markus

Re: console Fonts Umlaute

[Andreas Pakulat]

On 27.Jan 2005 - 13:18:31, Markus Feldmann wrote:
 Hallo liebe Newsleser,
 
 vielleicht kann mir ja jemand sagen wie ich dieses Problem beseitigen
 kann.

Auf der console muss man unicode_start ausführen, dann klappts auch
mit den Umlauten. Wobei bei Sarge sollte das eigentlich automatisch
passieren

Andreas

-- 
Your mode of life will be changed for the better because of new developments.


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: console Fonts Umlaute

[Markus Feldmann]

Andreas Pakulat wrote:

 On 27.Jan 2005 - 13:18:31, Markus Feldmann wrote:
 Hallo liebe Newsleser,
 
 vielleicht kann mir ja jemand sagen wie ich dieses Problem beseitigen
 kann.
 
 Auf der console muss man unicode_start ausführen, dann klappts auch
 mit den Umlauten. Wobei bei Sarge sollte das eigentlich automatisch
 passieren
 
 Andreas
 

Hallo,

 Auf der console muss man unicode_start ausführen, dann klappts auch
habe es gemacht aber das hat nicht hingaunen

feld-bert:/home/markus# unicode_start
Won't set unicode mode: not a VT.
feld-bert:/home/markus#

Weiss Jemand was er mit VT meint?

mfg Markus

Re: console Fonts Umlaute

[Andreas Pakulat]

On 28.Jan 2005 - 01:32:47, Markus Feldmann wrote:
 Andreas Pakulat wrote:
  On 27.Jan 2005 - 13:18:31, Markus Feldmann wrote:
  Hallo liebe Newsleser,

Nee, dies ist eine ML.

  Auf der console muss man unicode_start ausführen, dann klappts auch
  mit den Umlauten. Wobei bei Sarge sollte das eigentlich automatisch
  passieren

Sag mal, kannst du mal http://learn.to/quote lesen? Irgendwie
zitierst du dasselbe doppelt...

  Auf der console muss man unicode_start ausführen, dann klappts auch
 habe es gemacht aber das hat nicht hingaunen
 
 feld-bert:/home/markus# unicode_start
 Won't set unicode mode: not a VT.
 feld-bert:/home/markus#
 
 Weiss Jemand was er mit VT meint?

Ja, das du das in der konsole von KDE machst und nicht in der
Console. VT = VirtualTerminal = Alt+F1-F6

Hmm, du benutzt offensichtlich ein XTerm (bzw. einen anderen
Terminal-Emulator unter X11), wenn ich mich nicht irre ist das XTerm
das du benutzt aber nicht ganz UTF-8 fähig. Was benutzt du denn -
konsole von KDE, XTerm, ETerm, gnome-terminal? 

Andreas

-- 
You will be reincarnated as a toad; and you will be much happier.


-- 
Haeufig gestellte Fragen und Antworten (FAQ): 
http://www.de.debian.org/debian-user-german-FAQ/

Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Console Fonts and Keymaps

[Sam Halliday]

hi there,

while i was trying to set up my keyboard's map by hand (which is a new mac
layout), i suddenly became very confused with how debian handles standards
compliant console fonts.

the default setup was SCREEN_FONT=lat0-sun16 in /etc/console-tools/config. this
confuses me. i have been googling to actually find out the differences between
all the Latin-X encodings, and i cannot find any documentation on what Latin-0
is (or what the sun part is)... everyone seems to just say it is the same as
Latin-9 why then are there 2 standards for the same thing? also, i do not like
this font set as it lacks many characters (such as the sterling symbol). and the
euro is decimal value 252, and not 164 as it should be in Latin-9
[http://www.cs.tut.fi/~jkorpela/latin9.html]

i decided that using Latin-9 would be the way to go, after seeing that it
contains the euro symbol. however, when i tried the fonts 
  /usr/share/consolefonts/lat9-16.psf.gz
  /usr/share/consolefonts/lat9v-16.psf.gz
  /usr/share/consolefonts/lat9u-16.psf.gz
  /usr/share/consolefonts/lat9w-16.psf.gz
i could not see any euro! (what does the vuw mean?) and in fact, several
characters were still missing... such as the section symbol. (when i refer to
section in a keymap file, i get the not equals symbol printed out).

could somebody please help me select a standards compliant Latin-9 (iso-8859-15)
set of console fonts so that i can write my keymapping and have all the symbols
displayed!! (hopefully i won't have the same hassles with aterm fonts and X
fonts in general)

cheers,
Sam
-- 
Free High School Science Texts
  http://www.nongnu.org/fhsst/
Sam's Homepages
  http://fommil.homeunix.org/~samuel/
  http://www.ma.hw.ac.uk/~samuel/


pgpGVKTXrCTWC.pgp
Description: PGP signature

Re: Console Fonts and Keymaps

[Sam Halliday]

hi there,
 while i was trying to set up my keyboard's map by hand (which is a new mac
 layout), i suddenly became very confused with how debian handles standards
 compliant console fonts.

grrr... sorry i missed the if you are using a framebuffer, make sure you apply
this to all the virtual terminals or only tty1 will be effected. things are
looking better now!


pgp3PDhiAbEFz.pgp
Description: PGP signature

Larger console fonts

[Deboo]

   How to get bigger console fonts? I've compiled the kernel with all
   console fonts available including the SUN8x12 and other one. It's
   too big for a 15 inch screen. Though it sure is nice for the eyes.

   Isn't there any other console font smaller than this SUN font and
   bigger than the normal consol font? I've got an ATI Rage Pro 128 card
   and have framebuffer support compiled in. Anyone using bigger console
   fonts, I'd like to listen to their experiences.

Regards,
Deboo


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Console fonts in rxvt

[George Georgalis]

On Tue, Feb 11, 2003 at 08:21:11PM -0800, Eric G. Miller wrote:
On Tue, Feb 11, 2003 at 10:06:06PM -0500, George Georgalis wrote:
 Hi, another question on the same topic...
 
 On Tue, Feb 11, 2003 at 02:32:49PM -0700, Cameron Matheson wrote:
 
 What are you using as a font name?  You just use any font that X
 recognizes (use xfontsel to get the font-name).  With aterm, i use the
 
 How does one specify the font:
 -jmk-neep alt-medium-r-normal-*-*-140-*-*-c-*-iso8859-1
 
 there is a space in the name and I can't get it to work with rxvt...

Wrap it in quotes.

Have you done it? I've tried single / double quotes and \  to no
avail... but I am setting a variable ($fn) and using -fn $fn on the
command line (in a script). maybe that's my problem?

// George


-- 
GEORGE GEORGALIS, System Admin/Architectcell: 347-451-8229 
Security Services, Web, Mail,mailto:[EMAIL PROTECTED] 
Multimedia, DB, DNS and Metrics.   http://www.galis.org/george 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Console fonts in rxvt

[Steve Lamb]

On Thu, 13 Feb 2003 11:46:55 -0500
George Georgalis [EMAIL PROTECTED] wrote:
 Have you done it? I've tried single / double quotes and \  to no
 avail... but I am setting a variable ($fn) and using -fn $fn on the
 command line (in a script). maybe that's my problem?

{grey@teleute:~} rxvt -fn '-jmk-neep
alt-medium-r-normal-*-*-140-*-*-c-*-iso8859-1'

Started up just fine.  *shrug*

-- 
 Steve C. Lamb | I'm your priest, I'm your shrink, I'm your
   PGP Key: 8B6E99C5   | main connection to the switchboard of souls.
   |-- Lenny Nero - Strange Days
---+-



msg30556/pgp0.pgp
Description: PGP signature

Re: Console fonts in rxvt

[Colin Watson]

On Thu, Feb 13, 2003 at 11:46:55AM -0500, George Georgalis wrote:
 Have you done it? I've tried single / double quotes and \  to no
 avail... but I am setting a variable ($fn) and using -fn $fn on the
 command line (in a script). maybe that's my problem?

Word splitting happens after parameter expansion, so spaces in $fn will
be treated as word separators. Use -fn $fn instead.

-- 
Colin Watson  [[EMAIL PROTECTED]]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Console fonts in rxvt

[Jacob S .]

On Thu, 13 Feb 2003 11:46:55 -0500
George Georgalis [EMAIL PROTECTED] wrote:

 On Tue, Feb 11, 2003 at 08:21:11PM -0800, Eric G. Miller wrote:
 On Tue, Feb 11, 2003 at 10:06:06PM -0500, George Georgalis wrote:
  Hi, another question on the same topic...
  
  On Tue, Feb 11, 2003 at 02:32:49PM -0700, Cameron Matheson wrote:
  
  What are you using as a font name?  You just use any font that X
  recognizes (use xfontsel to get the font-name).  With aterm, i use
 the 
  How does one specify the font:
  -jmk-neep alt-medium-r-normal-*-*-140-*-*-c-*-iso8859-1
  
  there is a space in the name and I can't get it to work with
 rxvt...
 
 Wrap it in quotes.
 
 Have you done it? I've tried single / double quotes and \  to no
 avail... but I am setting a variable ($fn) and using -fn $fn on the
 command line (in a script). maybe that's my problem?
 
 // George

Yes, though I did it with Times New Roman. Using a format similar to 
rxvt -fn -jmk-neep alt-medium-r-normal-*-*-140-*-*-c-*-iso8859-1
worked for me. (Note: the quotes only go around the font name, not the
full command.)

HTH,
Jacob

- 
GnuPG Key: 1024D/16377135

In a world without fences, who needs Gates?
http://www.linux.org/



msg30574/pgp0.pgp
Description: PGP signature