You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(8) |
Nov
(9) |
Dec
(3) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(12) |
Feb
(10) |
Mar
|
Apr
(5) |
May
(3) |
Jun
|
Jul
(5) |
Aug
(7) |
Sep
(15) |
Oct
(4) |
Nov
(3) |
Dec
(7) |
2003 |
Jan
(5) |
Feb
(30) |
Mar
(5) |
Apr
(13) |
May
(12) |
Jun
(11) |
Jul
(1) |
Aug
(7) |
Sep
(2) |
Oct
|
Nov
(2) |
Dec
(7) |
2004 |
Jan
(4) |
Feb
(9) |
Mar
(16) |
Apr
(42) |
May
(5) |
Jun
(11) |
Jul
(3) |
Aug
(39) |
Sep
(5) |
Oct
(32) |
Nov
(27) |
Dec
|
2005 |
Jan
(11) |
Feb
(8) |
Mar
(22) |
Apr
(26) |
May
(9) |
Jun
(10) |
Jul
(7) |
Aug
(43) |
Sep
(23) |
Oct
(18) |
Nov
(15) |
Dec
(15) |
2006 |
Jan
(7) |
Feb
(16) |
Mar
(10) |
Apr
(1) |
May
(16) |
Jun
(8) |
Jul
(3) |
Aug
(35) |
Sep
(7) |
Oct
(4) |
Nov
(5) |
Dec
(1) |
2007 |
Jan
(2) |
Feb
(30) |
Mar
(6) |
Apr
(7) |
May
(5) |
Jun
|
Jul
(15) |
Aug
(12) |
Sep
(22) |
Oct
(48) |
Nov
(9) |
Dec
(7) |
2008 |
Jan
(3) |
Feb
(1) |
Mar
(1) |
Apr
|
May
(4) |
Jun
(1) |
Jul
(5) |
Aug
(4) |
Sep
(4) |
Oct
(2) |
Nov
(5) |
Dec
(1) |
2009 |
Jan
(3) |
Feb
|
Mar
|
Apr
(4) |
May
(2) |
Jun
(2) |
Jul
|
Aug
(1) |
Sep
(3) |
Oct
(2) |
Nov
(2) |
Dec
|
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
From: David J. <da...@we...> - 2002-08-23 19:17:28
|
On Thu, Aug 22, 2002 at 12:17:01PM -0700, James Simmons wrote: > > > Switching from one virtual console to another appears > > to clear the screen before writing the new one. > > > > Is there any way to prevent this? > > No. > Well, thanks. That sounds pretty definite. But does it have to be? Comparing sections of text by lining them up on adjacent virtual consoles and switching between them works so beautifully - a semi-colon instead of a colon anywhere on the screen just jumps out at you. Clearing the screen first is not only annoying and tiring for the eyes, it also means you have to go through the screen line by line (switching to and fro) for the same result. Are we going to have to sacrifice this facility in the name of progress? David |
From: James S. <jsi...@in...> - 2002-08-22 19:22:32
|
> Switching from one virtual console to another appears > to clear the screen before writing the new one. > > Is there any way to prevent this? No. |
From: David J. <da...@we...> - 2002-08-13 20:15:58
|
Switching from one virtual console to another appears to clear the screen before writing the new one. Is there any way to prevent this? David |
From: abcdefghijklmn <pra...@re...> - 2002-08-02 14:28:53
|
hi i have the frame buffer device enabled and it works fine with a single display. Now i have a dual display card. but when i start the Xfbdev i could enable only one screen using the /dev/fb0 have anyone tried dual head on framebuffer. can anyone tell me how to enable the second head /dev/fb1 i tried to create a device with minor number 32 same as /dev/fb0 but it doesn seem to work. Thanks in advance Prakash |
From: Prakash B. <pra...@ya...> - 2002-07-15 19:59:02
|
hi i want to use the silicon motion lynxEM+ driver for the Xfbdev server instead of the standard VGA driver. how could it b done?? Thanks in advance Prakash __________________________________________________ Do You Yahoo!? Yahoo! Autos - Get free new car price quotes http://autos.yahoo.com |
From: Petr V. <van...@vc...> - 2002-07-15 00:01:55
|
On Sun, Jul 14, 2002 at 04:10:29PM +0300, Ville Syrj=E4l=E4 wrote: > Is there a way to ge the framebuffer offset to userspace? I hacked > DirectFB to draw to the crtc2 display but currently I've had to hardcod= e > the framebuffer offset. So I need something I can feed to tmy G400. In what environment? With matroxfb you have special framebuffer which is displayed by CRTC2 engine. Offset is not explicitly exported, but if you'll take low 24 bits from fb_start, you'll get offset on G400/G450/G550 devices. Accessing CRTC2's memory through primary head's framebuffer is not supported. Best regards, Petr Vandrovec van...@vc... |
From: <sy...@sc...> - 2002-07-14 13:07:00
|
Is there a way to ge the framebuffer offset to userspace? I hacked DirectFB to draw to the crtc2 display but currently I've had to hardcode the framebuffer offset. So I need something I can feed to tmy G400. -- Ville Syrjälä sy...@sc... http://www.sci.fi/~syrjala/ |
From: <tm...@t-...> - 2002-07-07 11:50:31
|
hi list, i am a newbie to linux-fbdev and got a problem: i am trying to use the fbdev stuff from 2.4.18 on a ati rage lt (mach 64) chipset to make it sync the textmode on my hitachi hm4419-d fixed frequency monitor. everything runs fine so far, i can load the atyfb module and make fbset switch the video settings to a readable image, buit obviously the contrast and brightness of the image are very high. switching over to the restarted x-server reveals an image that is a bit scrambled in some parts (like being doubled, but not completely messed up) which is also equipped with far too much contrast. turning down the contrast on the monitor makes things a bit better, but it still is very high makeing me fear for my monitor's health :-) any hint? thx in advance, thorsten -- Thorsten Mika mailto:tm...@t-... Hamm / Germany TM5173-RIPE |
From: Krypton <kry...@in...> - 2002-07-01 17:20:09
|
I'm using EPSON S1D113806 framebuffer on a custom SA1110 SBC. I can boot my kernel-2.4.9-ac10-rmk2-np1 I see the penguin on the CRT screen. When the root.jffs2 image is loaded I see on the screen dirty lines when "Configuring dynamic linker" is called. During boot when char lines scrolling on the console tty0 the system do something same (dirty lines) on the CRT screen. I think the output tty is going to the video too. How to avoid that ? Do you have a suggestion about where to search if the framebuffer driver is assuming it can grab any memory it pleases and the rest of the kernel ? Does exist some file where there are entry points or function pointers for the fb ? Thank you ----- krypton8-AT-inwind-DOT-it |
From: James S. <jsi...@tr...> - 2002-05-31 21:11:10
|
Try the UseFBDev option with the X server. . --- |o_o | |:_/ | Give Micro$oft the Bird!!!! // \ \ Use Linux!!!! (| | ) /'\_ _/`\ \___)=(___/ On Fri, 10 May 2002, Marius Cucu wrote: > > I'm using RedHat Linux 7.2 on Kernel 2.4.18 with fbset suport for > nvidia chips. > The system doesn't respong when I shut down the X Server which is > configured to run with the nvidia module driver (from www.nvidia.com). > The same happens when I use FBDEV X server. > Everithing works fine when I run without fbdev compiled in kernel. > Thanks > > > _______________________________________________________________ > > Have big pipes? SourceForge.net is looking for download mirrors. We supply > the hardware. You get the recognition. Email Us: ban...@so... > _______________________________________________ > Linux-fbdev-users mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux-fbdev-users > |
From: Marius C. <Mar...@xn...> - 2002-05-10 17:41:54
|
I'm using RedHat Linux 7.2 on Kernel 2.4.18 with fbset suport for nvidia chips. The system doesn't respong when I shut down the X Server which is configured to run with the nvidia module driver (from www.nvidia.com). The same happens when I use FBDEV X server. Everithing works fine when I run without fbdev compiled in kernel. Thanks |
From: Latha <lat...@wi...> - 2002-05-06 09:10:22
|
Section "Files" # RgbPath "/usr/X11R6/lib/X11/rgb" FontPath "unix/:7100" EndSection Section "ServerFlags" EndSection Section "Keyboard" Protocol "Standard" AutoRepeat 500 30 LeftAlt Meta RightAlt Meta ScrollLock Compose RightCtl Control XkbKeycodes "xfree86" XkbTypes "default" XkbCompat "default" XkbSymbols "us(pc101)" XkbGeometry "pc" XkbRules "xfree86" XkbModel "pc104" XkbLayout "us" EndSection Section "Pointer" Protocol "MouseSystems" # Device "/dev/gpmdata" Device "/dev/psaux" # Device "/dev/ttyS0" # Device "/dev/ttyS1" Emulate3Timeout 50 Resolution 100 Buttons 3 Emulate3Buttons EndSection Section "Monitor" Identifier "Primary Monitor" VendorName "Unknown" ModelName "Unknown" HorizSync 31.5-48.5 VertRefresh 55-90 EndSection Section "Device" Identifier "Primary Card" EndSection Section "Screen" Driver "fbdev" Device "Primary Card" Monitor "Primary Monitor" SubSection "Display" Depth 8 # Depth 16 # Depth 24 # Depth 32 Modes "default" EndSubSection EndSection |
From: Iris H. <ir...@te...> - 2002-04-16 20:46:04
|
Hello! all, My video card is S3 ViRGE DX/GX. I compiled the kernel with VESA driver according to "Framebuffer Howto", and made change to grub like this: kernel /vmlinuz root=/dev/hda3 ro vga=ask After reboot, chose 80x25. In dmesg, console colour VGA+ 80x25 And cat /proc/fb, nothing there. /usr/sbin/fbset open /dev/fb0: no such device Any help would be highly appreciate! Iris |
From: <sim...@ya...> - 2002-04-14 20:12:59
|
Hello, I have just compiled kernel 2.4.18 and everything was perfect, apart from a nasty console which is 80x30 and too far off to the left. I started hacking around, and downloaded fbset, this gives me access to a nice console. I copied the ATI fb.modes file, and I do: $ fbset 800x600-72 This gives me the console I want, I just need to know how to set this as a kernel parameter instead. I don't like doing this in rc.sysinit because (1) I loose the Penguin logo, and (2) I'd like it to work automagically from the kernel boot. I have played with my grub.conf and tried several parameters using append, such as: video=atyfb:800x600-8 video=atyfb:mode:800x600-72 video=atyfb etc etc yet all have just given me a blank screen; If I login without being able to see what I type, then startx, I can get the console back by then quitting X. I have also tried standard vesa syntax vga=791 and such like but this does not work :( Does anyone have any hints? I can give additional information on request. Annexes: [1] dmesg context: ..snip... Starting kswapd Journalled Block Device driver loaded PCI: Found IRQ 9 for device 00:0b.0 radeonfb: ref_clk=2700, ref_div=60, xclk=16600 from BIOS Console: switching to colour frame buffer device 80x30 ^--- I don't seem to be able to get something better here radeonfb: ATI Radeon QD SDR SGRAM 32 MB radeonfb: CRT port CRT monitor connected [2] sample grub.conf lines append="video=atyfb:800x600-8" -> doesn't work append="atyfb:mode:800x600,font:SUN12x22" -> doesn't work, but font available in kernel. Doesn't work without font declaration either, or if I use cmode: to set bpp. TIA, Simon. ===== -- Simon White. Multiplatform Internet Specialist. Signature chopped. Yahoo! will add lots more lines every time I post anyway. __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com |
From: Gustavo V. <g_v...@ho...> - 2002-04-08 12:56:47
|
James, As you asked me. I took a lot at the dmesg file and I found: Console: colour VGA+ 80x25 And when I did the cat /proc/fb, there was nothing to see. I'm using an old vga ISA card. So I assume that the VESAVGA driver didn't support it. Then I tried with the VGA16-color graphics console driver. The options that I selected for re-compiling the kernel were: - VGA text console - Video mode selection support - Support for frame buffer devices - VGA 16-color graphics console - Advanced low level driver options - 2 bpp packed pixels support - 4 bpp packed pixels support - 8 bpp packed pixels support - 16 bpp packed pixels support - 24 bpp packed pixels support - 32 bpp packed pixels support Then when I reboot with that kernel and whites vertical lines appear on the screen and yellow points on the top of the screen. It must be the penguin. But then the screen doesn't change. Then I log in in dark. I do startx and I can take a look at the dmesg file: vga16fb: inilializing vga16fb: mapped to 0xc00a0000 fbcon_setup: NO support for fontwidth 8 fbcon_setup: type 4 (aux 0,depth 4) not supported Console: switching to colour frame buffer device 80x30 fb0: VGA16 VGA frame buffer device And I do the cat /proc/fb with the following result: 0 VGA16 VGA The fbset works too: mode "640x480-59" # D: 25.176 MHz, H: 31.469 kHz, V: 59,489 Hz geometry 640 480 640 480 4 timings 39721 48 16 39 8 96 2 rgba 6/0,6/0,6/0,0/0 endmode I could not change the mode. But it's not working properly. Any suggestion ? Gustavo >From: James Simmons <jsi...@tr...> >To: Gustavo Vilches <g_v...@ho...> >CC: lin...@li... >Subject: Re: [Linux-fbdev-users] Error: /dev/fb0: No such device >Date: Thu, 4 Apr 2002 11:09:57 -0800 (PST) > > > > > Hello , > > > > I compiled the kernel with the VESA frame buffer > > driver and made changes in lilo.conf by adding > > VGA=ask in addition to other standard enteries. > > > > The system booted ok , it asked for which mode I gave > > 80*43 and everything was working fine. After logging > > in as root , I gave the command > > > > cp /dev/fb0 screen > > > > It gave a error > > > > /dev/fb0 : No such device > > > > The documentation said that you can use /dev/fb0 in > > the same way as /dev/mem . > > > > Am I missing something ? > >What does dmesg say. Also can you do a cat /proc/fb. > > >_______________________________________________ >Linux-fbdev-users mailing list >Lin...@li... >https://lists.sourceforge.net/lists/listinfo/linux-fbdev-users _________________________________________________________________ Send and receive Hotmail on your mobile device: http://mobile.msn.com |
From: James S. <jsi...@tr...> - 2002-04-04 19:10:00
|
> Hello , > > I compiled the kernel with the VESA frame buffer > driver and made changes in lilo.conf by adding > VGA=ask in addition to other standard enteries. > > The system booted ok , it asked for which mode I gave > 80*43 and everything was working fine. After logging > in as root , I gave the command > > cp /dev/fb0 screen > > It gave a error > > /dev/fb0 : No such device > > The documentation said that you can use /dev/fb0 in > the same way as /dev/mem . > > Am I missing something ? What does dmesg say. Also can you do a cat /proc/fb. |
From: Gustavo V. <g_v...@ho...> - 2002-04-03 18:55:25
|
Hello , I compiled the kernel with the VESA frame buffer driver and made changes in lilo.conf by adding VGA=ask in addition to other standard enteries. The system booted ok , it asked for which mode I gave 80*43 and everything was working fine. After logging in as root , I gave the command cp /dev/fb0 screen It gave a error /dev/fb0 : No such device The documentation said that you can use /dev/fb0 in the same way as /dev/mem . Am I missing something ? Regards, Peter _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com |
From: Harsh A. <har...@ex...> - 2002-02-27 13:47:39
|
Hi, i want to call an image on console (but not via using zgv). what should i do? please help me. -- Harsh Ahuja Exaband (India) Private Limited, 24,Shantiniketan, East Marredpally, Secunderabad-26. ********************************************************************************* This email and any files transmitted along with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Mail recipients and senders are bound by the EXABAND (INDIA) PRIVATE LIMITED Non-Disclosure Policy. If you have not signed the Non-Disclosure Policy or if you feel you have received this mail in error, please notify sec...@uu... ********************************************************************************* |
From: Parson L. (NHQ-AC) <Par...@CS...> - 2002-02-26 12:43:22
|
>> I proceeded with the same command as before. "fbset -g 800 600 800 600 8" >> but then received "ioctl FBIOPUT_VSCREENINFO: Invalid argument". I then >> noticed that I was in 4bpp. Therefore I tried "fbset -g 800 600 800 600 4" >> and then this worked. >Sounds like you went from the VESA framebuffer to the vga16 framebuffer. >Can you do a cat /proc/fb and tell us what you see. Yes I have went to VGA16. I tried recompiled my kernel and enabled everything BUT VGA16, but then I had no more FB support. Also, enabling everything still gives me VGA16. I find this very strange that with Slack7.1 I could obtain more colors then with Slack8. Here are a few things that I have copied: root@laptop:~# dmesg | grep agpgart Linux agpgart interface v0.99 (c) Jeff Hartmann agpgart: Maximum main memory to use for agp memory: 93M agpgart: agpgart: Detected an Intel i815 Chipset. agpgart: detected 4MB dedicated video ram. agpgart: AGP aperture is 64M @ 0xf8000000 root@laptop:/proc# cat fb 0 VGA16 VGA root@laptop:~# fbset -i mode "832x620-38" # D: 25.176 MHz, H: 25.379 kHz, V: 37.935 Hz geometry 832 620 832 620 4 timings 39721 48 16 39 8 96 2 rgba 6/0,6/0,6/0,0/0 endmode Frame buffer device information: Name : VGA16 VGA Address : 0xa0000 Size : 65536 Type : VGA 16 colors in 4 planes Visual : PSEUDOCOLOR XPanStep : 8 YPanStep : 1 YWrapStep : 0 LineLength : 104 Accelerator : No Thanks, Luc P. |
From: James S. <jsi...@tr...> - 2002-02-21 21:21:00
|
> I proceeded with the same command as before. "fbset -g 800 600 800 600 8" > but then received "ioctl FBIOPUT_VSCREENINFO: Invalid argument". I then > noticed that I was in 4bpp. Therefore I tried "fbset -g 800 600 800 600 4" > and then this worked. Sounds like you went from the VESA framebuffer to the vga16 framebuffer. Can you do a cat /proc/fb and tell us what you see. |
From: Parson L. (NHQ-AC) <Par...@CS...> - 2002-02-21 12:59:10
|
I have a Sony VAIO laptop FX-150 with an i815 video. For many months I have use fbset with the following arguments "fbset -g 800 600 800 600 8". This enlarged my screen to about 80% used instead of like 50%. I was happy with this. This worked very well with SlackWare 7.1 with kernel 2.4.17 at the end. I recently installed SlackWare 8.0 and kept my .config file from SlackWare7.1 kernel 2.4.17. After installing Slack8 I downloaded the 2.4.17 kernel and applied my old .config to it. Compiled kernel and installed. I then again installed fbset-2.1 so I can obtain more screen then a little square of display in the center of my screen. I proceeded with the same command as before. "fbset -g 800 600 800 600 8" but then received "ioctl FBIOPUT_VSCREENINFO: Invalid argument". I then noticed that I was in 4bpp. Therefore I tried "fbset -g 800 600 800 600 4" and then this worked. Why can I not go back to 8bpp? I am using the same kernel config as before. The only change was from Slack7 to Slack8. Is there something in Slack8 that will not allow me to change bpp's? Thanks, Luc |
From: Geert U. <ge...@li...> - 2002-02-19 09:19:56
|
On Mon, 18 Feb 2002, Alberto Alonso wrote: > I have an interesting problem. > > I have a Gemini C1 graphics card, which is based on the > ET6000 chip but is adapted for fixed frequency monitors. > > When I run a 2.4.17 kernel with fb enabled the screen gets > divided in half, changing the text to a rather short font so that > it shows the same contents on both halves of the screen. > > I can log in and use the system normally, I can even > scrool after using cat on a long file. (both screen scroll > at the same time). I guess you're using vesafb, since AFAIK there's no native driver for the ET6000 yet? > If I log in and switch to runlevel 5, X windows fires up > normally and it doesn't have any of the splitting problems. X uses it's own driver. > However switching back to a VT will exhibit the problems. > > Any idea as to what I should be doing to fix the problem? > What files should I be looking at to figure out what is > going on? Since vesafb uses the video card as programmed by the BIOS code, there's nothing you can do, except for writing a native ET6000 frame buffer device. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li... In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds |
From: Alberto A. <al...@ma...> - 2002-02-19 05:32:21
|
I have an interesting problem. I have a Gemini C1 graphics card, which is based on the ET6000 chip but is adapted for fixed frequency monitors. When I run a 2.4.17 kernel with fb enabled the screen gets divided in half, changing the text to a rather short font so that it shows the same contents on both halves of the screen. I can log in and use the system normally, I can even scrool after using cat on a long file. (both screen scroll at the same time). If I log in and switch to runlevel 5, X windows fires up normally and it doesn't have any of the splitting problems. However switching back to a VT will exhibit the problems. Any idea as to what I should be doing to fix the problem? What files should I be looking at to figure out what is going on? I did download the fbset utility (is dated 1999) and looked at the mode running: [root@power linux]# /usr/sbin/fbset mode "640x480-59" # D: 25.176 MHz, H: 31.469 kHz, V: 59.489 Hz geometry 640 480 640 480 4 timings 39721 48 16 39 8 96 2 rgba 6/0,6/0,6/0,0/0 endmode Thanks, Alberto |
From: Henry J. <sl...@ya...> - 2002-02-19 02:22:46
|
Hi there, I am trying to install qt/embedded on my Debian box, after compiled it, = I started the sample program and found the screen is "in green". The = sample program requires a 16-bit color, I tried 1024x768 and 800x600, = both are in the same color tone. It's a PentiumPro 200 box, the display adapter is based on ATI Mach64CT = chip. The machine runs Debian potato with kernel 2.4.19, with atyfb = compiled as a loadable module. I was trying to test it with X frame buffer to see if this is a problem = of qt or atyfb, but I don't know how to change the color depth and the = resolution for X. My best guess is that the rgba 555 should be 565 for that display card. = I try to set rgba to 565 with setfb, it does not work. setfb --info = still shows rgba 555. How can I solve this problem? Thanks in advance. Henry |
From: Jurriaan on A. <thu...@xs...> - 2002-02-16 19:38:24
|
On Thu, Feb 07, 2002 at 02:46:36PM -0800, Alix Marchandise-Franquet wrote: > Hello, > > I hope this is the right place to ask this question, if not can you please > direct me to the appropriate newsgroup/mailing-list? > > I am trying to use the rivafb driver with an nvidia Geforce 2MX card. > I have a 2.4.16 kernel which I recompiled with rivafb. > When I boot my machine, I see the penguin which goes away after a while. > I don't think I am really using the framebuffer driver since with other > framebuffer drivers and cards the penguin stayed there and the font got > smaller. Also, nano-x, when compiled with the framebuffer setting > doesn't run (but it runs fine when built and run with X11). > > In the instructions for the vesafb driver, there are lines to add in > lilo.conf, I don't know what these are for rivafb. > > So my questions are: > 1) How can I know that I am using rivafb? If you type dmesg | less is there something like: fb: Voodoo5 memory = 65536K Console: switching to colour frame buffer device 133x54 fb0: 3Dfx Voodoo5 frame buffer device pty: 256 Unix98 ptys configured in there ? > 2) What needs to go in lilo.conf when using rivafb? my /etc/aboot.conf contains: 1:1/boot/vmlinux-2.4.18pre8.gz ro root=/dev/sda1 video=tdfx:1600x1200-16@85,nohwcursor 2:1/boot/vmlinux-2.4.17pre1.gz ro root=/dev/sda1 video=tdfx:1024x768-16@75 but you'll need another video= argument. > 3) I couldn't find any real info on rivafb, where would it be? > If all else fails (meaning nothing on google / google groups), read the source. Good luck, Jurriaan -- 'Has eighteen letters' does. GNU/Linux 2.4.18p7-rmap12a on Debian/Alpha 988 bogomips load:0.09 0.10 0.17 |