Re: multi sparc bootable CDROM
Eric Delaunay [EMAIL PROTECTED] writes: I'm working on the CDROM boot method for Debian/SPARC (sparc32) based on silo and I discovered silo is able to bootstrap ultra workstations too. Therefore I could provide a setup with 2 kernels, one for old sparcs (sun4c sun4m) and another for ultrasparcs (sun4u). However I don't know if there are incompatibilities between Debian sparc32 dist the ultrapenguin kernel. In case there is no such incompatibilities, could you package an ultrapenguin kernel that could be included on the CDROM (isofs, loop, initrd net support compiled in the kernel) ? In particular, silo can detect which system you are running and select the correct kernel, if you format the silo.conf correctly. (I've mentioned this before.) Additionally, you can use tilo to make a single tftpboot image that works on both systems. I already have 2.2.0-pre4 packaged as a Debian package at: /user/u11/ftp/pub/debian but the package name is: kernel-image-2.2.0_1.00_sparc.deb (this one is missing loop support). ** What should I name the kernel packages? ** It was compiled on a Debian system. (Not Ultrapenguin.) It is a sparc64 kernel that I grabbed out of CVS. (There is also a root and install image for UltraSparc at the same site.) I can provide you with proper source and binary packages, if you wish, just let me know what the packages should be named. One other issue: You must have the most recent binutils package in the root and base images (if you have /sbin/insmod64, then you have the right modutils.) We will also have to make sure the install program can install the right modules and kernel. Users will need egcs64_19980921-2 and a patched version of binutils to build a kernel themselves (it can be built on a Sparc32 system). I'm uploading the new egcs64 package, but I'm not uploading binutils, because I'm not sure it would get into slink... (It would make the source out of sync with the i386 version.) I'll try to get you proper kernel packages later today. What else do you want in the kernel? What drivers should I compile as modules (quad ethernet, bigmac ethernet, fibre channel)? Steve [EMAIL PROTECTED]
Re: missing packages in slink (continued)
VM writes: Is there a xf86setup package for sparc? Since sparc xservers are not using XF86Config at all, I don't think such package have to be provided but I could be wrong... just a comment from an end-user: when I set up my sun, I had to create /dev/kbd manually, /dev/fb* by running MAKEDEV and /dev/mouse by symlinking -- is this resolved? How do you create /dev/fb* ? May be it is the reason why I can't get X running. It complain about no screen found (The /dev/kbd and /dev/sunmouse are missing but I have already create them manually). --- PHAM Dinh Tuan | e-mail: [EMAIL PROTECTED] Laboratoire de Modelisation et Calcul | Tel: +33 4 76 51 44 23 BP 53, 38041 Grenoble cedex (France) | Fax: +33 4 76 63 12 63 ---
Re: missing packages in slink (continued)
Well, my build daemon has picked up the following so far. When I get a chance, I'll compile all the failure logs into a summary. [EMAIL PROTECTED] ls *changes a2ps_4.10.4-4_sparc.changes pciutils_1.10-1_sparc.changes asclassic_1.1b-3_sparc.changes wmaker_0.20.3-2_sparc.changes dds2tar_2.4.21-2_sparc.changes xteddy_1.2-1_sparc.changes libjpeg_6a-12_sparc.changes xtide_2.0b3-2.1_sparc.changes login.app_1.2.1-5_sparc.changes yforth_0.1beta-9_sparc.changes mdutils_0.35-22_sparc.changeszile_1.0a5-3_sparc.changes mpich_1.1.0-6_sparc.changes zsh_3.1.2-10_sparc.changes I'll upload these soonish, when I've had a chance to sanity check them. Interestingly, hardly any of these were on eric's list, but my buildd is sure that they were out of date. Jules /+---+-\ | Jelibean aka | [EMAIL PROTECTED] | 6 Evelyn Rd| | Jules aka | [EMAIL PROTECTED] | Richmond, Surrey | | Julian Bean | [EMAIL PROTECTED]| TW9 2TF *UK* | ++---+-+ | War doesn't demonstrate who's right... just who's left. | | When privacy is outlawed... only the outlaws have privacy. | \--/
Re: XWindow in Sparc4
Hi Debian Sparc users, Excuse me if I'm sending this mail twice. I already send a mail yesterday about setting X in a Sparc4 and none answered :( If you mean a sparcStation4 with the tcx onboard graphics, then yes, the debian X packages should work on it. Regards, /Anders -- -- Of course I'm crazy, but that doesn't mean I'm wrong. Anders Hammarquist | [EMAIL PROTECTED] Physics student | Hem: +46 31 47 69 27 Chalmers University of Technology, G|teborg, Sweden | Mob: +46 707 27 86 87
Debian Sparc installations
This weekend I installed (in a fairly minimal configuration) Debian Linux on two Sparcs: one LX and one SS2. I've got a few questions, several comments, and don't know whether one should file bug reports for a work in progress, so I'll post this here, in the hope that some kind soul will shove me in the right direction. Most things in the installation worked quite well. There were a couple of problems with the SS2, though; I had put a brand new drive into it, and (perhaps because of this?) the installation program didn't want to partition and format the drive, but kept bouncing me back to the select a color or mono monitor screen. I ran fdisk and mke2fs from the vc2, did network config by hand, and copied the files over onto one of the partitions via an nfs mount, but the installation program still wouldn't let me mount the partitions. Finally I guessed that I should mount /dev/sda1 to /target, and everything suddenly worked. I'm quite at a loss to explain why this can be done by hand, but not by the menu interface. (Incidentally, this was with the tftpboot image.) A possible bug in the installation program? The floppy installation on the LX didn't have this problem (but, then, it had a previously-used hard drive.) I didn't try out all of the disks; at the install from a mounted partition point, I did an nfs mount of the base set, and continued from there. There was no long delay in searching for the drivers or base set at all. However, both on the SS2 and the LX, the insert drivers into the kernel step fails; the program complains about not being able to find sed (I counldn't find it, either), and, as a result, nothing on the drivers floppy gets added. I'm not sure if it should, yet, and I don't miss much except the serial ports, which don't get configured at all. Perhaps someone can give me some tips. Other problems: more is immediately broken, since the ncurses package is a more recent version, and there is no package with the old version still available. I use less all the time, anyway, but this may also have broken other things in the utils package. I can't reinstall it, since the package depends upon the old ncurses library; should I just make a symlink for now? Or recompile them? gcc and friends seem to work OK (I tried them out once on frotz), which is a very good sign indeed. Since I was downloading packages ad libitum, I didn't try running dselect or apt, so I can't report (or complain) about them. I have noticed a couple of little things which need fixing, though: jed requires jed-common; the Packages listing states that this is in binary-sparc, but it's in binary-all. The same applies to tetex-base, and several others. X fails with complaints about the lack of /dev/kbd. Is this something which gets made with a proper dselect installation? I would run makedev, but I've noticed that the Other Distribution assigns /dev/kbd the major number 11, minor 0, which is scd0 with Debian, and I'd rather leave it alone until I know what the Right Thing To Do is. And there's probably some marvelous Debian package which sets up everything correctly, anyway :-) All in all, I'm quite impressed and delighted that so much works so smoothly. And I suppose I should volunteer to help in some way. Any suggestions?
Sparc4 install
I have just been given the OK to try an install on a Sparc4 that's not being used. I'm wondering what the state of the Sparc port is an what my caveats are. Where can I get install information similar to the install guide for the x86 side? I am very familiar with the x86 side so I'm hoping to knowck out this install smoothly. Any info is appreciated!! -Ian --- Ian Setford Brite Voice Systems (972)389-3251
How to obtain a list of deb packages after [Select] of dselect
I have successfully gone through the floppy base install of the system. I do not want to install via ppp since I only have a 28.8 modem. Is there a way I can obtain the list of needed packages via dselect or apt? So that I can download all of my needed files from an ethernet connection and dump them into my Jazz drive. I am trying to avoid mirroring those binary* directories since I am not about to create a CD. Thanks.
Re: missing packages in slink (continued)
Jules Bean [EMAIL PROTECTED] writes: Well, my build daemon has picked up the following so far. When I get a chance, I'll compile all the failure logs into a summary. [EMAIL PROTECTED] ls *changes a2ps_4.10.4-4_sparc.changes pciutils_1.10-1_sparc.changes asclassic_1.1b-3_sparc.changes wmaker_0.20.3-2_sparc.changes dds2tar_2.4.21-2_sparc.changes xteddy_1.2-1_sparc.changes libjpeg_6a-12_sparc.changes xtide_2.0b3-2.1_sparc.changes login.app_1.2.1-5_sparc.changes yforth_0.1beta-9_sparc.changes mdutils_0.35-22_sparc.changeszile_1.0a5-3_sparc.changes mpich_1.1.0-6_sparc.changes zsh_3.1.2-10_sparc.changes I'll upload these soonish, when I've had a chance to sanity check them. I build pciutils a few weeks ago (because I have an Ultra5). IIRC I had a problem uploading it, and dinstall rejected it. When you sanity check libjpeg (and any other libfoo package). Make sure the altdev packages were built. Steve [EMAIL PROTECTED]
Re: Sparc4 install
Ian Setford wrote: I have just been given the OK to try an install on a Sparc4 that's not being used. I'm wondering what the state of the Sparc port is an what my caveats are. Where can I get install information similar to the install guide for the x86 side? I am very familiar with the x86 side so I'm hoping to knowck out this install smoothly. Start with downloading dists/slink/main/disks-sparc/current and check the sparc_release_note.txt doc. Hope this help. -- Eric Delaunay | La guerre justifie l'existence des militaires. [EMAIL PROTECTED] | En les supprimant. Henri Jeanson (1900-1970)
Re: Debian Sparc installations
John Chapman wrote: This weekend I installed (in a fairly minimal configuration) Debian Linux on two Sparcs: one LX and one SS2. I've got a few questions, several comments, and don't know whether one should file bug reports for a work in progress, so I'll post this here, in the hope that some kind soul will shove me in the right direction. Most things in the installation worked quite well. There were a couple of problems with the SS2, though; I had put a brand new drive into it, and (perhaps because of this?) the installation program didn't want to partition and format the drive, but kept bouncing me back to the select a color or mono monitor screen. I ran fdisk and mke2fs from the vc2, did network config by hand, and copied the files over onto one of the partitions via an nfs mount, but the installation program still wouldn't let me mount the partitions. Finally I guessed that I should mount /dev/sda1 to /target, and everything suddenly worked. I'm quite at a loss to explain why this can be done by hand, but not by the menu interface. (Incidentally, this was with the tftpboot image.) A possible bug in the installation program? For sure :-(( The installation program is providing its own fdisk parser (libfdisk it is). It may fail on garbage in the partition sector of the disk... I didn't experienced with this problem and I don't have time to fix it now. Sorry. The workaround is to run fdisk manually then the installation program should stop to segfault after the system has reread the partition table of your hard drive. Are you sure you needed to run all the steps by hand ? The floppy installation on the LX didn't have this problem (but, then, it had a previously-used hard drive.) I didn't try out all of the disks; at the install from a mounted partition point, I did an nfs mount of the base set, and continued from there. There was no long delay in searching for the drivers or base set at all. However, both on the SS2 and the LX, the insert drivers into the kernel step fails; the program complains about not being able to find sed (I counldn't find it, either), and, as a result, nothing on the drivers floppy gets added. I'm not sure if it should, yet, It will be fixed in the next bootdisks release. and I don't miss much except the serial ports, which don't get configured at all. Perhaps someone can give me some tips. Other problems: more is immediately broken, since the ncurses package is a more recent version, and there is no package with the old version still available. I use less all the time, anyway, but this may also have broken other things in the utils package. I can't reinstall it, since the package depends upon the old ncurses library; should I just make a symlink for now? Or recompile them? gcc and friends seem to work OK (I tried them out once on frotz), which is a very good sign indeed. In fact, util-linux is out-dated and should be recompiled. # dpkg -I util-linux_2.7.1-3.deb ... Pre-Depends: libc6 (= 2.0.91), ncurses3.4 ... Since I was downloading packages ad libitum, I didn't try running dselect or apt, so I can't report (or complain) about them. I have noticed a couple of little things which need fixing, though: jed requires jed-common; the Packages listing states that this is in binary-sparc, but it's in binary-all. The same applies to tetex-base, and several others. Not a problem at all because all binary-all packages are symlinked to each binary-arch tree. # cd slink/main/binary-sparc/editors # ls -l jed-common_0.98.7-14.deb lrwxrwxrwx 1 root root 49 Jan 21 21:25 jed-common_0.98.7-14.deb - ../../binary-all/editors/jed-common_0.98.7-14.deb X fails with complaints about the lack of /dev/kbd. Is this something which gets made with a proper dselect installation? I would run makedev, but I've noticed that the Other Distribution assigns /dev/kbd the major number 11, minor 0, which is scd0 with Debian, and I'd rather leave it alone until I know what the Right Thing To Do is. And there's probably some marvelous Debian package which sets up everything correctly, anyway :-) Aargh :-(( In fact I lose the fixes I made to MAKEDEV to handle sparc specific devices for the base system. I fixed the stuff in place, so it was overwritten by a new makedev package when I did an upgrade and I completely forgot to send a patch to the maintainer. Grrr :-(( I will rewrite it for the next bootdisks release. They will provide /dev/kbd, /dev/fb* /dev/sunmouse in the base system. BTW, /dev/kbd is really major 11, minor 0 but *char* device while /dev/scd0 is major 11, minor 0 and *block* device. Try the following commands to create missing devices: # mknod /dev/kbd c 11 0 # mknod /dev/fb0 c 29 0 # mknod /dev/sunmouse c 10 6 All in all, I'm quite impressed and delighted that so much works so smoothly. And I suppose I should volunteer to help in some way. Any suggestions? We don't have enough testers to
Re: missing packages in slink (continued)
Jules Bean wrote: Well, my build daemon has picked up the following so far. When I get a chance, I'll compile all the failure logs into a summary. [EMAIL PROTECTED] ls *changes a2ps_4.10.4-4_sparc.changes pciutils_1.10-1_sparc.changes asclassic_1.1b-3_sparc.changes wmaker_0.20.3-2_sparc.changes dds2tar_2.4.21-2_sparc.changes xteddy_1.2-1_sparc.changes libjpeg_6a-12_sparc.changes xtide_2.0b3-2.1_sparc.changes login.app_1.2.1-5_sparc.changes yforth_0.1beta-9_sparc.changes mdutils_0.35-22_sparc.changeszile_1.0a5-3_sparc.changes mpich_1.1.0-6_sparc.changes zsh_3.1.2-10_sparc.changes I'll upload these soonish, when I've had a chance to sanity check them. Is pciutils really working on sparc ? ;-? Interestingly, hardly any of these were on eric's list, but my buildd is sure that they were out of date. I just checked the packages included in Tasks Profiles which are required to build working bootdisks ;-) But, for sure, many more packages are out of date, like util-linux, for example. BTW, I reviewed another time the Tasks Profiles list and discovered more inexisting packages: checker courtney fdflush (is this needed at all ? sparc floppy drives are auto-eject, therefore this package seems to be useless) genpower lockvc Regards. -- Eric Delaunay | La guerre justifie l'existence des militaires. [EMAIL PROTECTED] | En les supprimant. Henri Jeanson (1900-1970)
Re: multi sparc bootable CDROM
Well, I thought about this and found more problems I didn't solve yet: debian-sparc32 is based on 2.0.35 kernel (at least for installation) but debian-ultra is 2.2 based. At least modules serial console device are differents. Therefore I need a specific install program to locate the right drivers' disk imagen on the cdrom, and maybe more... I'm willing to work on sparc32 bootdisks cdrom first then I will spend the rest of my spare time (if any) to combine both world. BTW, have you tried to build bootdisks dedicated to the ultra port based on the boot-floppies package ? Working bootdisks could be a start for me to see the differences. Regards. Steve Dunham wrote: Eric Delaunay [EMAIL PROTECTED] writes: I'm working on the CDROM boot method for Debian/SPARC (sparc32) based on silo and I discovered silo is able to bootstrap ultra workstations too. Therefore I could provide a setup with 2 kernels, one for old sparcs (sun4c sun4m) and another for ultrasparcs (sun4u). However I don't know if there are incompatibilities between Debian sparc32 dist the ultrapenguin kernel. In case there is no such incompatibilities, could you package an ultrapenguin kernel that could be included on the CDROM (isofs, loop, initrd net support compiled in the kernel) ? In particular, silo can detect which system you are running and select the correct kernel, if you format the silo.conf correctly. (I've mentioned this before.) Additionally, you can use tilo to make a single tftpboot image that works on both systems. I already have 2.2.0-pre4 packaged as a Debian package at: /user/u11/ftp/pub/debian but the package name is: kernel-image-2.2.0_1.00_sparc.deb (this one is missing loop support). ** What should I name the kernel packages? ** It was compiled on a Debian system. (Not Ultrapenguin.) It is a sparc64 kernel that I grabbed out of CVS. (There is also a root and install image for UltraSparc at the same site.) I can provide you with proper source and binary packages, if you wish, just let me know what the packages should be named. One other issue: You must have the most recent binutils package in the root and base images (if you have /sbin/insmod64, then you have the right modutils.) We will also have to make sure the install program can install the right modules and kernel. Users will need egcs64_19980921-2 and a patched version of binutils to build a kernel themselves (it can be built on a Sparc32 system). I'm uploading the new egcs64 package, but I'm not uploading binutils, because I'm not sure it would get into slink... (It would make the source out of sync with the i386 version.) I'll try to get you proper kernel packages later today. What else do you want in the kernel? What drivers should I compile as modules (quad ethernet, bigmac ethernet, fibre channel)? Steve [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Eric Delaunay | La guerre justifie l'existence des militaires. [EMAIL PROTECTED] | En les supprimant. Henri Jeanson (1900-1970)
