Ok, so it is better to use
du -a | sed 's/^.* //'
Browsing the source for drawterm, I can't figure out where bufimage
(and a few others) are ever defined.
$ grep bufimage . -r
./include/draw.h:extern uchar* bufimage(Display*, int);
./libdraw/alloc.c: a = bufimage(d, 1+4+4+1+4+1+4*4+4*4+4);
./libdraw/alloc.c: a = bufimag
Hello 9fans
Just wanted to let you know that Plan 9 runs fine (except for a
PCMCIA-related problem, see below) on my JVC MP-XP3 Netbook.
I installed Plan 9 using the latest ISO-Image ("Dec 14 2009") which I
downloaded yesterday.
System: JVC MP-XP3
Intel Pentium III (750 MHz)
SIS 630 with VGA, L
The following resolutions work with the VESA driver:
800x600x32
800x600x16
800x600x8
I tried using 1024x600x8 but it didn't work, rio complains about
something with the vgadb.
Is there a way how I can nevertheless use this resolution?
Try editing /lib/vgadb and adding "xga=1024x600"
Best re
the database on sourceforge has about 3x the devices listed.
here's a little before-and-after
before:
3.0.0: net 02.00.00 14c1/0008 9 0:d80c 16777216 1: 16
2:d904 1048576 3: 16
Myricom Inc.
4.0.0: net 02.00.00 8086/1096 11 0:d912
The Wiki's supported hardware list is getting quite moldy.
I've created a new page for known broken hardware, working on
the theory that people pissed off are more likely to document
breakage than the blissful are their success.
It's linked from the supported hardware page.
--lyndon
> gcc -o drawterm main.o cpu.o readcons.o secstore.o latin1.o
>
> That fails on OS X 10.6,
You need to add -m32 option to gcc for OXS 10.6.
Oh, boy, I'm just a newbie to OSX world.☺
Kenji
On Wed, Dec 30, 2009 at 5:23 PM, wrote:
> > gcc -o drawterm main.o cpu.o readcons.o secstore.o latin1.o
> >
> > That fails on OS X 10.6,
>
> You need to add -m32 option to gcc for OXS 10.6.
> Oh, boy, I'm just a newbie to OSX world.☺
>
> Kenji
>
>
> Depends actually. If you're on a 32bit Intel,
On Wed Dec 30 19:18:18 EST 2009, lyn...@orthanc.ca wrote:
> The Wiki's supported hardware list is getting quite moldy.
>
> I've created a new page for known broken hardware, working on
> the theory that people pissed off are more likely to document
> breakage than the blissful are their success.
>
> i believe that richard miller has the intel D945GCLF2
> working via some careful hacking. (i.e. a hand-coded
> mp table.)
It was easier to buy something that actually worked. As for that
Intel piece of shit, I'm going to blend it during the transition
to 2010.
--lyndon
On Wed, Dec 30, 2009 at 6:44 PM, Lyndon Nerenberg (VE6BBM/VE7TFX) <
lyn...@orthanc.ca> wrote:
> > i believe that richard miller has the intel D945GCLF2
> > working via some careful hacking. (i.e. a hand-coded
> > mp table.)
>
> It was easier to buy something that actually worked. As for that
> In
On Wed Dec 30 21:47:08 EST 2009, lyn...@orthanc.ca wrote:
> > i believe that richard miller has the intel D945GCLF2
> > working via some careful hacking. (i.e. a hand-coded
> > mp table.)
>
> It was easier to buy something that actually worked. As for that
> Intel piece of shit, I'm going to blen
> i think it would be more valuable to explain exactly what's
> not working and point to some of the workarounds, if they exist.
What's not working is the ACPI component of the BIOS. The P9 boot
fails very early on (right after E820 I think). FreeBSD runs, but
something in the ACPI code wakes up
made into a contrib package. contrib quanstro/pci.
also fixed the fact i'd started with an old version of pci.
- erik
On Wed Dec 30 13:30:12 EST 2009, news...@lava.net wrote:
> > The following resolutions work with the VESA driver:
> >
> > 800x600x32
> > 800x600x16
> > 800x600x8
> >
> > I tried using 1024x600x8 but it didn't work, rio complains about
> > something with the vgadb.
> >
> > Is there a way how I can n
> pcmcia0=type=rtl8139 port=0x400 irq=10
Nope. "pcmcia0" tells the kernel what kind of PCMCIA
bridge you have; since you have CardBus (which is better),
you shouldn't have one of those lines unless you need to
disable the CardBus driver and use the old PCMCIA code
instead. One reason to do that,
> > ether0=rtl8139
>
> This is also wrong. You want "ether0=type=rtl8319".
good catch. it should be "ether0=type=rtl8139"
though. one should not need this oft mis-typed
line unless
- you wish to force the a particular ordering of controller
types. say you want the rtl8139 to be the first cont
I appreciate your help very much.
On 12/31/09, Dave Eckhardt wrote:
>> pcmcia0=type=rtl8139 port=0x400 irq=10
>
> Nope. "pcmcia0" tells the kernel what kind of PCMCIA
> bridge you have; since you have CardBus (which is better),
> you shouldn't have one of those lines unless you need to
> disable
I just booted without any "ether0=" and "pcmcia0=" lines and the
problem persists.
Only change is that on boot I see "rtl8139: port 0x400 in use" only
once and not two times as I mentioned in my previous message.
Best regards,
F. Caulier
On 12/31/09, erik quanstrom wrote:
>> > ether0=rtl8139
>>
19 matches
Mail list logo
