...]X]27P'ZMZ/(S:18L>&,"9_P"^15WS3_>/YU1TX!-.M%%Z8A0?^ M.BK`;FO12T1X;W)=QQ1NJ/-)FK0(FW9'/!IN[IZ^E,#4$\Y-4)C\^]!;G%%1[ MLT$\^U`A^ZD).!FF$\4W=SQ3`>3UJ,R$="12,W/-1,WY9I"N.>4YZG/UJ%%GY MH8U$6_.FB0=\BF,>:0M_D5&S9[50`QJ:$_NUJJS5)%%GRQQ5Q+CN='>+^]_X` MG_H(JL5!J[=K^^]/D3_T$55*XS63W((C'GBF%%-M3$=<<T$9I`1JG2G!33@,4 MF[!)[4`(W`Z8-(&XI),8]LTF[`H8QX?VJ2$\U7+8/K4L+<TD!>1J<34"OR,= M*?OX-,$/+<TQC@^M-+\TUF!'%%)...

... device support in the kernel"? That's one option. It could also be the wrong device was specified in the Xconfig. Seems this driver creates a normal fb device. Make sure you have /dev/fb0 and/or /dev/fb0autodetect. You could try the fbdev X driver: Driver "fbdev" without specifying a BusID. This is just to see if it detects a device. If it ...

...as meaning that X's "No devices detected" actually means "I'm not seeing the appropriate device support in the kernel"? Seems this driver creates a normal fb device. Make sure you have /dev/fb0 and/or /dev/fb0autodetect. You could try the fbdev X driver: Driver "fbdev" without specifying a BusID. This is just to see if it detects a device. If it does the...

... booting: /sbus@2,0/SUNW,leo@2,0: leo at x:x Also you should have leo ranges in /proc/iomem and /proc/ioport. Seems this driver creates a normal fb device. Make sure you have /dev/fb0 and/or /dev/fb0autodetect. You could try the fbdev X driver: Driver "fbdev" without specifying a BusID. This is just to see if it detects a device. If it does the issue is with the leo X ...

... support for it is in the kernel, my xorg.conf looks like this Section "Device" Identifier "Sun Leo (ZX)" Driver "sunleo" # BusID "SBUS:fb0" BusID "SBUS:/sbus@2,0/SUNW,leo@2,0" # Option "UseFBDev" "true" EndSection [...] Section "Screen" Identifier "Default Screen" Device...

... (Mach64 GR, PCI-33) [0x4752 rev 0x27] atyfb: 8M SDRAM (1:1), 29.498928 MHz XTAL, 230 MHz PLL, 83 Mhz MCLK, 63 MHz XCLK Console: switching to colour frame buffer device 160x64 atyfb: fb0: ATY Mach64 frame buffer device on PCI rtc_init: no PC rtc found [drm] Initialized drm 1.1.0 20060810 f007d64c: ttyS0 at MMIO 0x1fe020003f8 (irq = 9) is a 16550A f007f1a4: ttyS1 at MMIO 0x1fe020002e8 (irq ...

...XL (Mach64 GR, PCI-33) [0x4752 rev 0x27] atyfb: 8M SDRAM (1:1), 29.498928 MHz XTAL, 230 MHz PLL, 83 Mhz MCLK, 63 MHz XCL Console: switching to colour frame buffer device 160x64 atyfb: fb0: ATY Mach64 frame buffer device on PCI [drm] Initialized drm 1.1.0 20060810 f007263c: ttyS0 at MMIO 0x1fe020003f8 (irq = 9) is a 16550A f0073d68: ttyS1 at MMIO 0x1fe020002e8 (irq = 9) is a 16550A RAMDISK...

... rename it along the way: cat test.f90 program test use mod0, only : fb0=>fb use mod1, only : fb1=>fb write (*,*) fb0(), fb1() stop end program test So far, so good? Here is the compilation of the test .../mod0 -M$HOME/mod1 test.f90 -L. -lmod0 -lmod1 use mod0, only : fb0=>fb ^ "test.f90", Line = 2, Column = 23: ERROR: "FB" is ...

entering the command "dmesg | grep fb0 return nothing on one of the sparc, and : fb0 Creatot at xxxxxxx.xxxxxx type 48 DAC10 on the other : the prafik card is on an UPA port on the first machine. maybe to be on an UPA port causes the pb ? -- To UNSUBSCRIBE, email to debian-sparc-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

...]X]27P'ZMZ/(S:18L>&,"9_P"^15WS3_>/YU1TX!-.M%%Z8A0?^ M.BK`;FO12T1X;W)=QQ1NJ/-)FK0(FW9'/!IN[IZ^E,#4$\Y-4)C\^]!;G%%1[ MLT$\^U`A^ZD).!FF$\4W=SQ3`>3UJ,R$="12,W/-1,WY9I"N.>4YZG/UJ%%GY MH8U$6_.FB0=\BF,>:0M_D5&S9[50`QJ:$_NUJJS5)%%GRQQ5Q+CN='>+^]_X` MG_H(JL5!J[=K^^]/D3_T$55*XS63W((C'GBF%%-M3$=<<T$9I`1JG2G!33@,4 MF[!)[4`(W`Z8-(&XI),8]LTF[`H8QX?VJ2$\U7+8/K4L+<TD!>1J<34"OR,= M*?OX-,$/+<TQC@^M-+\TUF!'%%)...