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: Mysql
On mysql mailing archives I can read about a similar bug . Perhaps It could help anyone. In fact, for me, the problèm is that I can't recompile Mysql on my sparc cause it stop during te restartable call system test ! . Remove the lines concerning 'Big file support' from configure: # Big file support ? (Solaris 2.6 style) # This may have to be commented on Relient (Siemens) unix echo $ac_n "checking "for Sun style big file support"""... $ac_c" 1>&6 echo "configure:4534: checking "for Sun style big file support"" >&5 LFS_CFLAGS=`getconf LFS_CFLAGS 2>/dev/null` if test $? = 0 -a "$SYSTEM_TYPE" != "sni-sysv4" then CFLAGS="$CFLAGS $LFS_CFLAGS" CXXFLAGS="$CXXFLAGS $LFS_CFLAGS" # LFS_LDFLAGS=`getconf LFS_LDFLAGS` LDFLAGS="$LDFLAGS $LFS_LDFLAGS" LFS_LIBS=`getconf LFS_LIBS` LIBS="$LIBS $LFS_LIBS" echo "$ac_t"""Found. Using C $LFS_CFLAGS LD $LFS_LDFLAGS LIB $LFS_LIBS"" 1>&6 else echo "$ac_t"""No"" 1>&6 fi remove config.cache and run configure + make again! --- Nicolas On Tue, 3 Aug 1999, Teun Vink wrote: > On Mon, 2 Aug 1999, Nicolas PROCHAZKA wrote: > > > Hi, > > I 've just install mysql on debian potato release on Sparc 1 cause it > > doesn't match on Redhat 6.0 Sparc , but I have the same problème : > > Error 1003 Incorrect Information in file *.frm > > Please help me > > > > > > > me2 > > > Unfortunately I haven't seen a fix for this yet... > > Teun > > -- > Teun Vink [EMAIL PROTECTED] - http://www.vsts.nl > icq: 15001247 [EMAIL PROTECTED] - http://www.moonblade.net > "Pitr is killing himself howling over how Stef has given credit for > borrowing code from 'Hello World'" - Mike, User Friendly, 23-7-99 > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > Nicolas PROCHAZKA mailto:[EMAIL PROTECTED] http://maxibus.info.unicaen.fr/~nicolas ICQ:#34113768
Re: Mysql
On Mon, 2 Aug 1999, Nicolas PROCHAZKA wrote: > Hi, > I 've just install mysql on debian potato release on Sparc 1 cause it > doesn't match on Redhat 6.0 Sparc , but I have the same problème : > Error 1003 Incorrect Information in file *.frm > Please help me > > me2 Unfortunately I haven't seen a fix for this yet... Teun -- Teun Vink [EMAIL PROTECTED] - http://www.vsts.nl icq: 15001247 [EMAIL PROTECTED] - http://www.moonblade.net "Pitr is killing himself howling over how Stef has given credit for borrowing code from 'Hello World'" - Mike, User Friendly, 23-7-99
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: apt not working with sparc ipc
On Tue, Aug 03, 1999 at 12:07:18AM -0600, Jason Gunthorpe wrote: > > On Fri, 30 Jul 1999, Andrew Howell wrote: > > > Attached is strace output of the http sub process. > > > > It just gets stuck in a loop of > > > > _newselect(0x1, 0xefffeb48, 0, 0, 0)= 1 > > read(0, "", 4000) = 0 > > Ah, this is a different bug, the HTTP method was ignoring the signs of a > close FD (woops) It's fixed in CVS now - it would be nice to see straces > of the code leading up to the failure. Whatever is causing that FD to > close is the real culprit here. Yeah sorry I haven't had time to compile strace 4.0 yet. It doesn't compile cleanly under sparc it seems. Glad I helped you find a bug though :) Andrew -- Andrew Howell Managing Director Informed Technology E-mail: [EMAIL PROTECTED] Ph: 08 9380 4244 Fax: 08 9380 4354
Re: apt not working with sparc ipc
On Fri, 30 Jul 1999, Andrew Howell wrote: > Attached is strace output of the http sub process. > > It just gets stuck in a loop of > > _newselect(0x1, 0xefffeb48, 0, 0, 0)= 1 > read(0, "", 4000) = 0 Ah, this is a different bug, the HTTP method was ignoring the signs of a close FD (woops) It's fixed in CVS now - it would be nice to see straces of the code leading up to the failure. Whatever is causing that FD to close is the real culprit here. Jason
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
Re: SLILO
In a message dated 8/2/99 5:06:49 PM US Mountain Standard Time, [EMAIL PROTECTED] writes: > Earlier I suggested that something like the following be added to the > installation manual. I think something similar but more concise was in > fact added. > > Note that fdisk has a hidden command "s" meaning "create a new empty > Sun disklabel". > > (How hard would it be to make the installation program check the type > of partition table and warn the user?) Knowing about that little feature would have saved me a whole lot of trouble for the first time I set up Linux on my SPARC10. Jesse Molina-Lanners[EMAIL PROTECTED] Phoenix Arizona
Re: Newbie: Xsun cannot open /dev/kbd error 13
On Fri, Jul 30, 1999 at 12:31:28AM -0500, Charles Hawkins wrote: > slink on an IPC, cgi3, type 4 kbd. > /dev/kbd is c 11 0. > > When i try to run Xsun or startx i get: > Fatal server error: Cannot open /dev/kbd, error 13 > > Any ideas on what the above error means and how i can fix it? > > Any kind soul(s) want to help an absolute Linux novice through getting X > to work? hello, Maybe it can help you : http://x32.deja.com/getdoc.xp?AN=351523613&CONTEXT=933640052.431095814&hitnum=2 Cheers -- Lerale Erwan -- ClaraNET systemes -- [EMAIL PROTECTED] If idiots could fly, IRC would be an airport.
Re: SLILO
> I 've installed a debian potato on sparc 1 without problem (exept mysql ;) > but now o a sparc station LX (sun4m) slilo don't run , in fact the install > is ok but when slilo run, after reboot, the system tell me : wrong label (You mean SILO?) Earlier I suggested that something like the following be added to the installation manual. I think something similar but more concise was in fact added. Note that fdisk has a hidden command "s" meaning "create a new empty Sun disklabel". (How hard would it be to make the installation program check the type of partition table and warn the user?) Partitioning a disc The installation system gives you the option of partitioning a disc. If you select this option, it runs the command fdisk for you. The fdisk program can understand several different kinds of partition table. (The kernel can understand even more kinds; see linux/drivers/block/genhd.c.) The Sun's PROM, however, only understands Sun partition tables, so, if you want to be able to boot off your disc, make sure that fdisk mentions "Sun disk label" when you print the partition table using the command "p". If you start with a blank disc, fdisk will create a Sun partition table by default. However, if your disc was previously partitioned by a different system you will have to be careful at this point, or you will end up with an unbootable disc. In addition to having a Sun partition table, to be able to boot from the disc, the first partition, /dev/sdX1, must start at cylinder 0. This means that /dev/sdX1 contains the partition table and the boot block, as these are the first two sectors of the disc. Therefore you must be careful what you use /dev/sdX1 for. In particular, you must not use a partition starting at cylinder 0 for Linux swap, as that would overwrite the partition table and the boot block. You may, however, use such a partition for a UFS or EXT2 file system, as these file systems leave the first 1024 bytes undisturbed. It is also advised that the third partition, /dev/sdX3, should be of type "Whole disk" (5), though this may not be an absolute requirement for booting.
