From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu From: Adrian Tritschler Message-ID: <84y9ebe17i.fsf@smtp.monash.edu.au> Content-Type: text/plain; charset=us-ascii References: <90f569981f3b78a05622acd68c368104@plan9.bell-labs.com> Subject: Re: [9fans] Plan9 on IBM PC300PL...getting better Date: Thu, 23 May 2002 08:36:11 +0000 Topicbox-Message-UUID: 9a997a9c-eaca-11e9-9e20-41e7f4b1d025 >>>>> "rsc" == rsc writes: >> Attempting to boot off the boot floppies that it creates gives >> me the error message "panic: exception/interrupt 6" Russ> This is probably the wacko increment bug. We still need to Russ> fix the distribution archive. I like the bug's name. Russ> Copy 9load from your install floppy to your boot floppy and Russ> then see if the install floppy works. Yes, that worked. Many thanks! Possibly time to add that suggestion to the wiki. I found that the acme intro that is displayed for glenda is _very_ useful. I've actually managed to use acme to edit a few config files. Two further problems before I go away and shut up for a while: 1. The mouse pointer is accompanied by a great block of ugliness, sort of like the following two images (I've used a "T" where it has the arrow pointer), the first is for 1024x768x8, the second for 1280x1024x8. In both cases the "point" is the top left corner, so its difficult to correctly find things at 1280x1024: T== == ==T== == == == == == == == == == == == == The PC300 has a video card that seems to be identified in vgainfo.txt as: virge->snarf->s3generic Unknown ViRGE/Trio64+ - 0x8904 Trio64+ vga->attr: 0xC004B=S3 86C366 Video BIOS I added it to the section with the only other Trio64V+, but it doesn't appear "optimal" for this video card. Any suggestions for dealing with the pointer? 2. Updating I've tried to follow the update instructions from the Bell labs webpage, have registered an account, but when I run the scripts I get the following: post... !Adding key: dom=outside.plan9.bell-labs.com proto=p9sk1 user[bootes]: ajftnew password: ! srv tcp!source.cs.bell-labs.com!9fs: mount failed: authentication failed bind: /n/sources/plan9: '/n/sources' does not exist servermount: bind 181: bin How can I find out where/why the authentication is failing? I *think* I've got the network setup correctly, I've managed to successfully ssh to a machine outside the university. Adrian --------------------------------------------------------------- Adrian Tritschler mailto:Adrian.Tritschler@its.monash.edu.au ---------------------------------------------------------------