Re: kernel 2.0.37 compilation failure
On Thu, 5 Aug 1999, Anton Blanchard wrote: > > > Woaaah Apparently I'm very lucky, because the SLC here wasn't > > damaged. :-)) But I can confirm: X doesn't work if a kernel 2.2.x is > > running. > > (Tested up to 2.2.10) Text mode works fine if you ignore the big wipe stripe > > running down on the left side of the screen. ;-)) > > Don't worry, the SLC didn't die because of the bwtwo bug :) Its just old. > > > So There is NO chance to get 2.0.37 running...?? > > (btw. 2.2.x would be even better- but I don't dare to ask ;-)) > > The bwtwo driver is pretty simple so shouldn't be too hard to fix (hint to > anyone :) It wasn't too hard to fix. I checked a one-liner into the CVS tree last night, basically go into linux/drivers/video/bwtwofb.c, find the line which reads fb->physbase = phys; and make it read: fb->physbase = __get_phys(fb->sbdp->sbus_vaddrs[0]); -D
Re: kernel 2.0.37 compilation failure
> Woaaah Apparently I'm very lucky, because the SLC here wasn't > damaged. :-)) But I can confirm: X doesn't work if a kernel 2.2.x is running. > (Tested up to 2.2.10) Text mode works fine if you ignore the big wipe stripe > running down on the left side of the screen. ;-)) Don't worry, the SLC didn't die because of the bwtwo bug :) Its just old. > So There is NO chance to get 2.0.37 running...?? > (btw. 2.2.x would be even better- but I don't dare to ask ;-)) The bwtwo driver is pretty simple so shouldn't be too hard to fix (hint to anyone :) Anton
Re: kernel 2.0.37 compilation failure
On Tue, Aug 03, 1999 at 05:54:32PM +1000, Anton Blanchard wrote: > > > What's broken about it, i've got a bwtwo in a IPC running 2.2.10 and it > > appears > > to work fine. > > X doesnt work. I was going to look into it but as soon as I decided to my SLC > broke. Ahhh I never even considered running X on my IPC :) Andrew -- Andrew Howell Managing Director Informed Technology E-mail: [EMAIL PROTECTED] Ph: 08 9380 4244 Fax: 08 9380 4354
Re: kernel 2.0.37 compilation failure
Hi... > > What's broken about it, i've got a bwtwo in a IPC running 2.2.10 and it > > appears > > to work fine. > > X doesnt work. I was going to look into it but as soon as I decided to my SLC > broke. Woaaah Apparently I'm very lucky, because the SLC here wasn't damaged. :-)) But I can confirm: X doesn't work if a kernel 2.2.x is running. (Tested up to 2.2.10) Text mode works fine if you ignore the big wipe stripe running down on the left side of the screen. ;-)) So There is NO chance to get 2.0.37 running...?? (btw. 2.2.x would be even better- but I don't dare to ask ;-)) Andi
Re: kernel 2.0.37 compilation failure
Hi Thanks for your reply! :-) > You need 2.0 because the bwtwo is broken in 2.2. You don't need 2.0.37 > specifically. Yes of course- I know! :-) 2.0.35 runs very well here.. :-)) But my boss asked me if it would possible to upgrade to 2.0.37 because of security flaws in 2.0.35. Unfortunaltely, there seems no sparc patch available for this version Or am I only bad at searching...?? So my question is: Did anyone manage to get 2.0.37 running on a Sparc 4C system (here: Sun Sparc SLC) ? If so, please, please let me know! :-) TNX! -- cya ANDI
Re: kernel 2.0.37 compilation failure
> What's broken about it, i've got a bwtwo in a IPC running 2.2.10 and it > appears > to work fine. X doesnt work. I was going to look into it but as soon as I decided to my SLC broke. Anton
Re: kernel 2.0.37 compilation failure
On Tue, 3 Aug 1999, Andrew Howell wrote: > What's broken about it, i've got a bwtwo in a IPC running 2.2.10 and it > appears > to work fine. Some people apparently have a stripe down one side or something; I have no idea, I was just responding in kind to the message; 2.0.37 won't work. -D
Re: kernel 2.0.37 compilation failure
On Tue, Aug 03, 1999 at 12:52:56AM -0400, Derrick J Brashear wrote: > On Sun, 1 Aug 1999, Andreas Jaehnigen wrote: > > > Hi Debian Team... > > > > > > Compilation of kernel 2.0.37 fails here. System is a Sun Sparc 1... > > It fails because 2.0.37 doesn't include sparc patches. > > > Does anybody have a clue why this happens..? > > > > Kernel is 2.0.37. (Need this release, because in 2.2.x bwtwo support seems > > to > > You need 2.0 because the bwtwo is broken in 2.2. You don't need 2.0.37 > specifically. What's broken about it, i've got a bwtwo in a IPC running 2.2.10 and it appears to work fine. Console: switching to mono frame buffer device 142x54 fb0: bwtwo at 1.fe00 Andrew -- Andrew Howell Managing Director Informed Technology E-mail: [EMAIL PROTECTED] Ph: 08 9380 4244 Fax: 08 9380 4354
Re: kernel 2.0.37 compilation failure
On Sun, 1 Aug 1999, Andreas Jaehnigen wrote: > Hi Debian Team... > > > Compilation of kernel 2.0.37 fails here. System is a Sun Sparc 1... It fails because 2.0.37 doesn't include sparc patches. > Does anybody have a clue why this happens..? > > Kernel is 2.0.37. (Need this release, because in 2.2.x bwtwo support seems to You need 2.0 because the bwtwo is broken in 2.2. You don't need 2.0.37 specifically. > be broken.) Kernel 2.0.35 compiled successfully after applying the Sparc patch > (thanks to Christian Meder). For 2.0.37, there is no patch available > (right??). -D
kernel 2.0.37 compilation failure
Hi Debian Team... Compilation of kernel 2.0.37 fails here. System is a Sun Sparc 1... Does anybody have a clue why this happens..? Kernel is 2.0.37. (Need this release, because in 2.2.x bwtwo support seems to be broken.) Kernel 2.0.35 compiled successfully after applying the Sparc patch (thanks to Christian Meder). For 2.0.37, there is no patch available (right??). However, compilation fails with...: (Sorry for the long output I appended.) see you ANDI THANK YOU for any hints!! :-) .. make ARCH=sparc vmlinux make[1]: Entering directory `/usr/src/linux-2.0.37' make[1]: Circular /usr/src/linux-2.0.37/include/asm/pgtable.h <- /usr/src/linux-2.0.37/include/linux/mm.h dependency dropped. gcc -D__KERNEL__ -I/usr/src/linux-2.0.37/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strength-reduce -pipe -c -o init/main.o init/main.c /usr/src/linux-2.0.37/include/asm/posix_types.h: In function `__FD_ZERO': In file included from /usr/src/linux-2.0.37/include/linux/posix_types.h:48, from /usr/src/linux-2.0.37/include/linux/types.h:16, from init/main.c:17: /usr/src/linux-2.0.37/include/asm/posix_types.h:72: warning: initialization from incompatible pointer type /usr/src/linux-2.0.37/include/asm/posix_types.h:75: `__FDSET_INTS' undeclared (first use this function) /usr/src/linux-2.0.37/include/asm/posix_types.h:75: (Each undeclared identifier is reported only once /usr/src/linux-2.0.37/include/asm/posix_types.h:75: for each function it appears in.) /usr/include/asm/semaphore.h: In function `down': In file included from /usr/src/linux-2.0.37/include/linux/sched.h:22, from init/main.c:20: /usr/include/asm/semaphore.h:50: warning: implicit declaration of function `atomic_dec_return' /usr/include/asm/semaphore.h: In function `up': /usr/include/asm/semaphore.h:64: warning: implicit declaration of function `atomic_inc_return' /usr/src/linux-2.0.37/include/linux/string.h: At top level: In file included from init/main.c:25: /usr/src/linux-2.0.37/include/linux/string.h:31: warning: conflicting types for built-in function `memcpy' /usr/src/linux-2.0.37/include/linux/string.h:34: warning: conflicting types for built-in function `memcmp' /usr/src/linux-2.0.37/include/linux/mm.h: In function `expand_stack': In file included from init/main.c:33: /usr/src/linux-2.0.37/include/linux/mm.h:327: `RLIMIT_AS' undeclared (first use this function) make[1]: *** [init/main.o] Error 1 make[1]: Leaving directory `/usr/src/linux-2.0.37' make: *** [build] Error 2
