Re: [9fans] Using proportional fonts in Acme for Programming
Speaking of fonts in Acme, using the default, I spent extra amount of time tracking down a bug in my gs(1) source, which was the mix-up between -lijs and -Iijs. Apparently 'I' is shorter than 'l' by some portion of a pixel. how could I possibly miss that ak P.S.: This isn't Acme's fault - it's the same trouble in the font I'm using to type this message - in GMail in Firefox.
Re: [9fans] HP: Printing with the Illiterate
However, I think you need the ijs
driver, which is not built by default (it probably should be).
To enable it, edit /sys/src/cmd/gs/mkfile to add ijs to the
device list and then rebuild using the instructions in the
mkfile.
I thought I'd built gs(1) this way with proper ijs support,
but `{gs -h} quickly made me realise otherwise. It was
a hoax; there's quite a bit more that's needed in order
to build with ijs support: for one, the ijs/ directory is
missing, which contains the proper headers and other
sources; other edits need to be made to the mkfile,
as well as to src/plan9.mak. Using Prof. Okamaoto's
sources from a while back, I've finally got it built,
and I'll test whether I can now print something (still
using the old hpijs 1.5, as it supports OfficeJet 5500 -
I figure, close enough).
Furthermore, changes needed to be made to
/sys/lib/lp/process/gspipeijs, which was clearly geared
for Prof. Okamoto's own setup (notice the switch
statement: $GSOPT is nil for any model numbers other
than the ones specific to his HP PSC printer). Small,
but necessary and elusive (the output of `{gs -} from
gspipeijs is very misleading). I think $GSTMPFILE also
needs to be changed.
I hope everything in /sys/lib/ghostscript is proper with
regards to this; I would really dislike problems due to
missing files there. I don't know anything about them.
My changes for building gs(1) with ijs required a lot of
out-of-the-garden stuff. I'm guessing the problem has never
before occurred because the code has been left dormant
and no one has made use. Thus, perhaps increasing the
size of gs(1) sources in distribution with the appropriate
data and files to build with ijs support is unnecessary.
Most of it is just taking what Prof. Okamoto had already
done; if anyone would like, I can document these changes
to gs(1) sources.
Best,
ak
[9fans] laptop install woes
I'm trying to get my circa 2006 laptop working with Plan 9. Its a Gateway MX3414 with: North Bridge: NVIDIA C51MV South Bridge: MCP51 - ignored NVIDIA GeForce Go 6100 graphics - works fine with 1024x768x16 VESA NVIDIA MCP51 ethernet controller - not detected NVIDIA MCP51 PATA controller - buggy? see below... I am using the install CD from June 25th. Boot messages, kmesg, pci output, and linux lspci output are attached. There is a pause of 1-2 mins after each of the the reading drive 0x80 offset 0 into seg:off 0x600... messages are printed to the screen while booting from CD. Then the startup menu appears. I boot from the CD and do not perform an install yet. I also tried booting from Erik's atom iso, but don't get very far. eg: PBS1 Plan 9 from Bell Labs ELCR: 0CA0 pcirouting: south bridge 10de, 0260 not found aoepnp(nil) found 11 e820 entries Boot devices: fd0 fd1 boot from: It doesn't detect IDE controller, so no local disk/CD-ROM to boot from. Thanks for any help. Hopefully something can be worked out. Jamie PBS1 Plan 9 from Bell Labs ELCR: 0CA0 pcirouting: South bridge 10de, 0260 not found islba: drive 0x80 extensions version 48.0 cx 0x5 extgetsize: drive 0x80 info flags 0x1 bios0: drive 0x80: 100,030,242,816 bytes, type 3 dev A0 port 1F0 config 0C5A capabilities 2F00 mwdma 0007 udma 203F LLBA sec tors 195371568 dev A0 port 170 config 85C0 capabilities 0F00 mwdma 0007 udma 0407 found partition sdD0!cdboot!; 52712+1440 reading drive 0x80 offset 0 into seg:off 0x600...biosdiskcall: int 13 op 0x4 2 drive failed, ah error code 0x80 sectread: bios failed to read 512 @ sector 0 of 0x80 reading drive 0x80 offset 1 into seg:off 0x600...biosdiskcall: int 13 op 0x4 2 drive failed, ah error code 0x80 sectread: bios failed to read 512 @ sector 1 of 0x80 Plan 9 E820: 0009dc00 memory E820: 0009dc00 000a reserved E820: 000d2000 0010 reserved E820: 0010 3ef1 memory E820: 3ef1 3ef18000 acpi reclaim E820: 3ef18000 3ef8 acpi nvs E820: 3ef8 3f00 reserved E820: 3f00 4000 reserved E820: e000 f000 reserved E820: fec0 fec1 reserved E820: fee0 fee01000 reserved E820: fff8 1 reserved 126 holes free 00018000 0009d000 544768 002ee000 1000 265363456 265908224 bytes free cpu0: 1605MHz AuthenticAMD AMD64 (cpuid: AX 0x40F82 0x178BF BFF) ELCR: 0CA0 pcirouting: ignoring south bridge PCI.0.10.0 10DE/0260 #u/usb/ep1.0 ohci: port 0xE000 irq 11 #u/usb/ep2.0 ehci: port 0xE0001000 irq 7 1007M memory 256M kernel data, 751M user, 1376M swap usbd...root is from (tcp, local)[local!#S/sdD0/data]: kfs...version...time init: starting /bin/rc mouseport is (ps2, ps2intellimouse, 0, 1, 2)[ps2]: vgasize [640x480x8]: 1024x768x16 monitor is [xga]: vesa 0.0.0: mem 05.00.00 10de/02f30 0.0.1: mem 05.00.00 10de/02fa0 0.0.2: mem 05.00.00 10de/02fe0 0.0.3: mem 05.00.00 10de/02f80 0.0.4: mem 05.00.00 10de/02f90 0.0.5: mem 05.00.00 10de/02ff0 0.0.6: mem 05.00.00 10de/027f0 0.0.7: mem 05.00.00 10de/02fe0 0.10.0: brg 06.01.00 10de/02600 0.10.1: smb 0c.05.00 10de/0264 10 4:3041 5:3001 64 0.10.3: --- 0b.40.00 10de/0271 10 0:b004 262144 0.11.0: usb 0c.03.10 10de/026d 11 0:b0004000 4096 0.11.1: usb 0c.03.20 10de/026e7 0:b0005000 256 0.13.0: disk 01.01.8a 10de/02650 4:3081 16 0.16.0: brg 06.04.01 10de/026f 255 0.16.1: aud 04.03.00 10de/026c 11 0:b000 16384 0.20.0: brg 06.80.00 10de/02690 0.24.0: brg 06.00.00 1022/11000 0.24.1: brg 06.00.00 1022/11010 0.24.2: brg 06.00.00 1022/11020 0.24.3: brg 06.00.00 1022/11030 0.3.0: brg 06.04.00 10de/02fd 255 0.5.0: vid 03.00.00 10de/02475 0:b200 16777216 1:c00c 268435456 2: 16 3:b104 16777216 4: 16 0.9.0: mem 05.00.00 10de/02700 6.9.0: net 02.00.00 10ec/8185 11 0:6001 256 1:b3400 512 00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2) Subsystem: Gateway 2000 Device 0317 Flags: bus master, 66MHz, fast devsel, latency 0 Capabilities: [44] HyperTransport: Slave or Primary Interface Capabilities: [e0] HyperTransport: MSI Mapping Enable+ Fixed- 00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2) Subsystem: Gateway 2000 Device 0317 Flags: 66MHz, fast devsel 00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2) Subsystem: Gateway 2000 Device 0317 Flags: 66MHz, fast devsel 00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2) Subsystem: Gateway 2000 Device 0317 Flags: 66MHz, fast devsel 00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2) Subsystem: Gateway 2000 Device 0317 Flags: bus master, 66MHz, fast devsel, latency 0 00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2) Subsystem: Gateway 2000 Device 0317 Flags: bus master, 66MHz, fast
Re: [9fans] audio standards -- too many to choose from
Thanks, very interesting read. I think he lied, he was perfectly aware of how the piracy issue would turn out, and he had it all planned :D On Fri, Aug 14, 2009 at 11:54 PM, Skip Tavakkolian9...@9netics.com wrote: an old interview with some relevance http://www.wired.com/wired/archive/3.08/thompson.html
Re: [9fans] Plan 9 hg with private repositories
re: /etc/ssh/sshd_config on unix to support sshv1 see: http://plan9.bell-labs.com/wiki/plan9/Connecting_to_other_OSes/index.html -Steve
[9fans] Dell E4300?
Anyone here had a chance to try a Dell E4300? It's a nice, compact system, but it really refuses to boot Plan 9: It has on-board SATA hd, SATA cd-rom, etc. I tried quanstro's 9atom.iso, and with the SATA controller in AHCI mode, it'll start booting, but hangs at: 4 = 818807+1020832+474972=2314611 entry: f0100020 Plan 9 In modes other than AHCI, neither the stock or quanstro's cd's will recognize any devices other than fd0, and even then won't boot from it. The stock cd will hang here in AHCI mode: PBS1... Plan 9 from Bell Labs ELCR: 0C08 pcirouting: South bridge 8086, 2917 not found Any idea where to start looking? (besides for a different laptop, that is :) ) Thanks!! -Ben
Re: [9fans] Dell E4300?
Anyone here had a chance to try a Dell E4300? It's a nice, compact system, but it really refuses to boot Plan 9: It has on-board SATA hd, SATA cd-rom, etc. I tried quanstro's 9atom.iso, and with the SATA controller in AHCI mode, it'll start booting, but hangs at: 4 = 818807+1020832+474972=2314611 entry: f0100020 Plan 9 In modes other than AHCI, neither the stock or quanstro's cd's will recognize any devices other than fd0, and even then won't boot from it. i think there's a good chance things can work. clearly we're relatively close to booting, because we've gotten this far. my semi-educated guess here is that either we've done something antisocial in 9load that has corrupted some SMM mode memory. the leading potential culprit here is ahci. or that some SMM-driven device, like a usb mouse that is presented to the os as a ps/2 mouse is messing up. the easiest debugging step is to turn off usb completely. also, make sure to check for bios updates. do you have a cpu server? is your laptop PXE bootable? even a useable network card would work. if so, it will be much easier to narrow down the problem quickly. The stock cd will hang here in AHCI mode: PBS1... Plan 9 from Bell Labs ELCR: 0C08 pcirouting: South bridge 8086, 2917 not found i'll add this southbridge to my cd. this will definately not hurt. could you send me pci output? if you use lspci from linux make sure to use -vn so the vid/did appear. the descriptive strings are fairly useless. - erik
Re: [9fans] Dell E4300?
i'll add this southbridge to my cd. this will definately not hurt. could you send me pci output? if you use lspci from linux make sure to use -vn so the vid/did appear. the descriptive strings are fairly useless. Sorry, I don't use Linux much. This machine currently runs OpenSolaris. Below is the output from 'prtconf -pv' which should be more-or-less similar to Linux's 'lspci -vn'. If you'd prefer the Linux output, I can go download a LiveCD really quick... Thanks much for your time!! -Ben System Configuration: Sun Microsystems i86pc Memory size: 4048 Megabytes System Peripherals (PROM Nodes): Node 0x01 bios-boot-device: '82' stdout: name: 'i86pc' Node 0x02 existing: 00db2000..0bc58801. name: 'ramdisk' Node 0x03 bus-type: 'isa' device_type: 'isa' name: 'isa' Node 0x04 compatible: 'pciex_root_complex' device_type: 'pciex' reg: .. #size-cells: 0002 #address-cells: 0003 name: 'pci' Node 0x05 reg: .... compatible: 'pci8086,2a40.1028.24d.7' + 'pci8086,2a40.1028.24d' + 'pci1028,24d' + 'pci8086,2a40.7' + 'pci8086,2a40' + 'pciclass,06' + 'pciclass,0600' model: 'Host bridge' power-consumption: 0001.0001 fast-back-to-back: devsel-speed: max-latency: min-grant: subsystem-vendor-id: 1028 subsystem-id: 024d unit-address: '0' class-code: 0006 revision-id: 0007 vendor-id: 8086 device-id: 2a40 name: 'pci1028,24d' Node 0x06 assigned-addresses: 83001010..f6c0..0040.c3001018..e000..1000.81001020..ef98..0008.a1001000..03b0..000c.a1001000..03c0..0020.82001000..000a..0002 reg: 1000.....03001010....0040.43001018....1000.01001020....0008.a1001000..03b0..000c.a1001000..03c0..0020.82001000..000a..0002 compatible: 'pci8086,2a42.1028.24d.7' + 'pci8086,2a42.1028.24d' + 'pci1028,24d' + 'pci8086,2a42.7' + 'pci8086,2a42' + 'pciclass,03' + 'pciclass,0300' model: 'VGA compatible controller' power-consumption: 0001.0001 fast-back-to-back: devsel-speed: interrupts: 0001 max-latency: min-grant: subsystem-vendor-id: 1028 subsystem-id: 024d device_type: 'display' unit-address: '2' class-code: 0003 revision-id: 0007 vendor-id: 8086 device-id: 2a42 name: 'display' Node 0x07 assigned-addresses: 83001110..f6b0..0010 reg: 1100.....03001110....0010 compatible: 'pci8086,2a43.1028.24d.7' + 'pci8086,2a43.1028.24d' + 'pci1028,24d' + 'pci8086,2a43.7' + 'pci8086,2a43' + 'pciclass,038000' + 'pciclass,0380' model: 'Video controller' power-consumption: 0001.0001 fast-back-to-back: devsel-speed: max-latency: min-grant: subsystem-vendor-id: 1028 subsystem-id: 024d unit-address: '2,1' class-code: 00038000 revision-id: 0007 vendor-id: 8086 device-id: 2a43 name: 'pci1028,24d' Node 0x08 assigned-addresses: 8200c810..f6ae..0002.8200c814..f6adb000..1000.8100c818..efe0..0020 reg: c800.....0200c810....0002.0200c814....1000.0100c818....0020 compatible: 'pci8086,10f5.1028.24d.3' + 'pci8086,10f5.1028.24d' + 'pci1028,24d' + 'pci8086,10f5.3' + 'pci8086,10f5' + 'pciclass,02' + 'pciclass,0200' model: 'Ethernet controller' power-consumption: 0001.0001 devsel-speed: interrupts: 0001 max-latency: min-grant: subsystem-vendor-id: 1028
[9fans] Matrox DualHead2Go
Hi, I don't quite know what I'm asking, I'm just fishing for responses :) I got a Matrox DualHead2Go which splits a vga signal across multiple monitors. Atm. I have it driving two screen with a duplicated image but if you supply it one of these modes : edid 2048x76...@60hz clock=113.75 shb=2136 ehb=2200 ht=2352 vrs=771 vre=786 vt=806 hsync=+ vsync=- edid 2048x76...@75hz clock=137.81 shb=2120 ehb=2176 ht=2296 vrs=769 vre=784 vt=800 hsync=+ vsync=- edid 2560x102...@60hz clock=189.82 shb=2608 ehb=2720 ht=2968 vrs=1025 vre=1037 vt=1066 hsync=+ vsync=- edid 2048x76...@85hz clock=165.39 shb=2160 ehb=2232 ht=2408 vrs=769 vre=781 vt=808 hsync=- vsync=- It will become two distinct screens, half on each monitor. You can see form my Vesa mode dump that we don't have that in the list. My nvidia card (8600 GT dual SLI) is aslo unrecognised by the vganvida.c pci | grep vid 3.0.0:vid 03.00.00 10de/0402 10 0:f900 16777216 1:c00c 268435456 2: 16 3:f604 33554432 4: 16 5:cc01 128 4.0.0:vid 03.00.00 10de/0402 10 0:fd00 16777216 1:d00c 268435456 2: 16 3:fa04 33554432 4: 16 5:dc01 128 edid mfrMTX edid serialstr edid name edid product768 edid serial 1363750341 edid version1.3 edid mfrdate2007.44 edid size (cm) 41x31 edid gamma 2.21 edid vert (Hz) 0-0 edid horz (Hz) 0-0 edid pclkmax0 edid flags standby suspend activeoff edid 640x48...@60hz clock=25.175 shb=648 ehb=792 ht=800 vrs=490 vre=492 vt=525 hsync=- vsync=- edid 640x48...@75hz clock=31.5 shb=640 ehb=840 ht=840 vrs=481 vre=484 vt=500 hsync=- vsync=- edid 800x60...@60hz clock=40 shb=800 ehb=1056 ht=1056 vrs=601 vre=605 vt=628 hsync=+ vsync=+ edid 800x60...@75hz clock=49.5 shb=800 ehb=1056 ht=1056 vrs=601 vre=604 vt=625 hsync=+ vsync=+ edid 1024x76...@60hz clock=65 shb=1024 ehb=1344 ht=1344 vrs=771 vre=777 vt=806 hsync=- vsync=- edid 1024x76...@75hz clock=78.75 shb=1024 ehb=1312 ht=1312 vrs=769 vre=772 vt=800 hsync=+ vsync=+ edid 1280x102...@75hz clock=135 shb=1280 ehb=1688 ht=1688 vrs=1025 vre=1028 vt=1066 hsync=+ vsync=+ edid 2048x76...@60hz clock=113.75 shb=2136 ehb=2200 ht=2352 vrs=771 vre=786 vt=806 hsync=+ vsync=- edid 2048x76...@75hz clock=137.81 shb=2120 ehb=2176 ht=2296 vrs=769 vre=784 vt=800 hsync=+ vsync=- edid 2560x102...@60hz clock=189.82 shb=2608 ehb=2720 ht=2968 vrs=1025 vre=1037 vt=1066 hsync=+ vsync=- edid 2048x76...@85hz clock=165.39 shb=2160 ehb=2232 ht=2408 vrs=769 vre=781 vt=808 hsync=- vsync=- vesa flagUlinear|Hlinear vesa sigVESA 3.0 vesa oemNVIDIA 96.132 vesa vendor NVIDIA Corporation vesa product vesa rev vesa cap 8-bit-dac vesa mem14680064 vesa mode 0x100 640x400x8 m8 packed vesa mode 0x101 640x480x8 m8 packed vesa mode 0x102 800x600x4 m4 planar vesa mode 0x103 800x600x8 m8 packed vesa mode 0x104 1024x768x4 m4 planar vesa mode 0x105 1024x768x8 m8 packed vesa mode 0x106 1280x1024x4 m4 planar vesa mode 0x107 1280x1024x8 m8 packed vesa mode 0x10e 320x200x16 r5g6b5 direct vesa mode 0x10f 320x200x32 x8r8g8b8 direct vesa mode 0x111 640x480x16 r5g6b5 direct vesa mode 0x112 640x480x32 x8r8g8b8 direct vesa mode 0x114 800x600x16 r5g6b5 direct vesa mode 0x115 800x600x32 x8r8g8b8 direct vesa mode 0x117 1024x768x16 r5g6b5 direct vesa mode 0x118 1024x768x32 x8r8g8b8 direct vesa mode 0x11a 1280x1024x16 r5g6b5 direct vesa mode 0x11b 1280x1024x32 x8r8g8b8 direct vesa mode 0x130 320x200x8 m8 packed vesa mode 0x131 320x400x8 m8 packed vesa mode 0x132 320x400x16 r5g6b5 direct vesa mode 0x133 320x400x32 x8r8g8b8 direct vesa mode 0x134 320x240x8 m8 packed vesa mode 0x135 320x240x16 r5g6b5 direct vesa mode 0x136 320x240x32 x8r8g8b8 direct vesa mode 0x13d 640x400x16 r5g6b5 direct vesa mode 0x13e 640x400x32 x8r8g8b8 direct vesa mode 0x145 1600x1200x8 m8 packed vesa mode 0x146 1600x1200x16 r5g6b5 direct vesa mode 0x14a 1600x1200x32 x8r8g8b8 direct vesa mode 0x147 1400x1050x8 m8 packed (unoffered) vesa mode 0x148 1400x1050x16 r5g6b5 direct (unoffered) vesa mode 0x149 1400x1050x32 x8r8g8b8 direct (unoffered) vesa mode 0x152 2048x1536x32 x8r8g8b8 direct
Re: [9fans] laptop install woes
This is pretty much a show-stopper for me. I guess it's time to find a new laptop with supported hardware. or a usb ethernet device
Re: [9fans] file server?
2009/8/14 Lyndon Nerenberg lyn...@orthanc.ca: This is what we do at Sandia. We have one machine which serves cpu/auth/file, but the actual Venti disks are in a Coraid connected via GigE. The fossil disk is in the server, but if it dies we can just build a new one. Which reminds me of an often overlooked but important point: Save your fossil vac scores on another machine! Amen, a dozen times! Having lost the lot once or twice due to stupidity or hardware failures I've now got this under control, still not entirely happy with my venti arena archiving and seeking inspiration there. I'll add the description of my trivial home system to the mix. A ubuntu linux PC running p9p's venti, a plan9 cpu/fossil-fileserver running under QEMU and drawterm. A few times I've tried running 9vx but for unknown reasons I can crash it as soon as I look at it sideways - I suspect either operator error or oddities of my setup. All running on a P4 shuttle system tucked into the corner of my desk. Without them, your seperate venti server is JBOD :-P Well, not quite. You can eventually find the right vac score, but you have to manually mount each and every score in the venti until you find the right one. See /sys/src/cmd/venti/words/dumpvacroots. You could probably semi-automate the process by writing a script that mounted each of the scores in turn, checking the mtime of something like /sys/log/timesync in each, and sorting the vac scores accordingly. On my setup I aux/clog the fileserver console to a u9fs mounted directory on a UNIX server. You could also cobble something up that scans the fossil console for vac scores and emails them to an offsite address. For me, cron runs fossil/last and mails it to gmail --lyndon Adrain -- Adrian
