On Saturday 09 December 2000 05:05, you wrote:
> Jean Meloche <[EMAIL PROTECTED]> writes:
> > Linux version 2.2.17-29mdksmp ([EMAIL PROTECTED])
> > (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release))
> > #1 SMP Sat Nov 25 17:04:31 CET 2000
>
> what modprobe r128 does ? nota bene that r128 with kernel-2.2 is very
> bad maybe you can give a try to the 2.4.x kernel of cooker.
OK... I got a 2.4 kernel running by avoiding scsi modules, after all...
(==) R128(0): Write-combining range (0xe0000000,0x1000000)
(WW) R128(0): Cannot read colourmap from VGA. Will restore with default
[drm] failed to load kernel module "r128"
(0): [drm] drmOpen failed
(EE) R128(0): DRIScreenInit failed!
(II) R128(0): Memory manager initialized to (0,0) (1600,5242)
(II) R128(0): Reserved area from (0,1200) to (1600,1202)
(II) R128(0): Largest offscreen area available: 1600 x 4040
(==) R128(0): Backing store disabled
(==) R128(0): Silken mouse enabled
(II) R128(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Solid filled rectangles
8x8 mono pattern filled rectangles
Indirect CPU to Screen color expansion
Solid Lines
Dashed Lines
Offscreen Pixmaps
Setting up tile and stipple cache:
32 128x128 slots
29 256x256 slots
14 512x512 slots
(II) R128(0): Acceleration enabled
(II) R128(0): Using hardware cursor (scanline 2404)
(II) R128(0): Largest offscreen area available: 1600 x 4039
(II) R128(0): Direct rendering disabled
[root@rocks jean]# modprobe r128
/lib/modules/2.4.0-0.10mdk/kernel/drivers/char/drm/r128.o: init_module:
Cannot allocate memory
Hint: insmod errors can be caused by incorrect module parameters, including
invalid IO or IRQ parameters
/lib/modules/2.4.0-0.10mdk/kernel/drivers/char/drm/r128.o: insmod
/lib/modules/2.4.0-0.10mdk/kernel/drivers/char/drm/r128.o failed
/lib/modules/2.4.0-0.10mdk/kernel/drivers/char/drm/r128.o: insmod r128 failed
Cannot allocate memory?!?!?!
--
Jean Meloche
[EMAIL PROTECTED]
e-gold # 133947
