Re: Silo breakage creating woody r2 CDs for sparc
> Can I ask one favour for in future, though - if any more changes are > made in future to core tools like silo, mkisofs etc. that will affect > CD/DVD image generation, can you please give us just a little bit of > warning? At the moment, without the information about the new isofs.b > you gave me a way back up this messy thread, we wouldn't be able to > make working (bootable) sparc images for sarge or sid. Generally I fix the debian-cd sparc scripts myself. So once cvs.d.o is accepting logins again, I'll fix it there for sarge/sid. > On that front, how is the sparc end of the debian-installer work > going? I have the stuff building but not very tested right now. I need to find time to get back into it. -- Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ WatchGuard - http://www.watchguard.com/
Re: Silo breakage creating woody r2 CDs for sparc
On Tue, Dec 02, 2003 at 02:56:43PM -0500, Ben Collins wrote: >> Thanks very much for the support, Ben. I've been working hard trying >> to get some sparc CDs created, and I didn't think asking for some help >> to get this job done was particularly out of order. Apparently I was >> wrong. I hope you have time to get the installer and CDs ready for the >> sarge release... > >No, you didn't ask, you bitched and moaned and got pretty damn rude >about it. Just asking would have gotten you a nice reply with >explanation, and help avoiding the problem. Apparently you don't know >how to ask nicely and would rather be an ass about it. To top it off, >it's your own damn fault and you felt like pointing fingers. Yes, I did. Sorry, it's been a _very_ long couple of days, without much sleep in the middle and I've been getting defensive and rude when I shouldn't have been. Apologies. It gets very frustrating in these situations when a long task that normally works with minimal intervention suddenly needs a lot of attention. Things seem a lot more under control now, and I'm slowly working my way through the rest of the arches to help Phil. This shouldn't have turned into a flaming match - again, I'm sorry. I don't want to fall out over this... Can I ask one favour for in future, though - if any more changes are made in future to core tools like silo, mkisofs etc. that will affect CD/DVD image generation, can you please give us just a little bit of warning? At the moment, without the information about the new isofs.b you gave me a way back up this messy thread, we wouldn't be able to make working (bootable) sparc images for sarge or sid. On that front, how is the sparc end of the debian-installer work going? Thanks, -- Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED] Can't keep my eyes from the circling sky, Tongue-tied & twisted, Just an earth-bound misfit, I... signature.asc Description: Digital signature
Re: XFree86 on Sunblade 150
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have seen similar problems on an Ultra 5 when trying to use a TFT screen. In my case the whole screen was very shakey and i couldnt mange to adjust the screen to cope. If your screen is a TFT (dont know is a SB150 is vga or not) try hitching up a CRT. On Tuesday 02 December 2003 20:58, Ryan Terry (MessEdUp) wrote: > I am trying to configure X on a SunBlade 150. > > I am using the ati Mach64 server, and it is working enough to where I can > get a desktop and I can set my resolution, and see things just fine. > > The problem I have is that the top 2 inches of the screen seem to "bend" to > the right about a half inch. Other than this the X-Server seems to be > running well. > > I have drawn up a VERY dirty sketch of what the screen looks like just to > try to explain, it can be found here: > > http://www.violentsin.com/images/X-Distoreted.png > > Any help would be appreciated. > > MessEdUp > [EMAIL PROTECTED] > #clanvs on irc.gamesnet.net > http://www.violentsin.com > [EMAIL PROTECTED] (MSN IM) - -- and thus ended my pointles ramblings. David Leggett [EMAIL PROTECTED] http://www.asguard.org.uk http://www.site-control.org Get my public GPG key from http://www.asguard.org.uk/~david/david.asc Fingerprint: 432E 4EAD E1E5 26BB 29EB 47FA CBDE AB17 0D23 C76B -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/zShsy96rFw0jx2sRAsAQAJ9tz/q0i3fFxepN0V5n3ITUgjzODQCcCRt0 ezimNvcOs0XUEGwKfPIl4uU= =ohNn -END PGP SIGNATURE-
Re: XFree86 on Sunblade 150
Ryan Terry (MessEdUp) wrote: I am trying to configure X on a SunBlade 150. I am using the ati Mach64 server, and it is working enough to where I can get a desktop and I can set my resolution, and see things just fine. The problem I have is that the top 2 inches of the screen seem to "bend" to the right about a half inch. Other than this the X-Server seems to be running well. I have drawn up a VERY dirty sketch of what the screen looks like just to try to explain, it can be found here: http://www.violentsin.com/images/X-Distoreted.png Any help would be appreciated. What you've described/drawn sounds like less of an X problem and more of an adjustment problem on the monitor. You should be able to use the buttons on the monitor to adjust out the bend. Of course, if that messes up the console image, then I'm wrong. (Wouldn't be the first time I was wrong; there was that time in 1974) -- Kent
XFree86 on Sunblade 150
I am trying to configure X on a SunBlade 150. I am using the ati Mach64 server, and it is working enough to where I can get a desktop and I can set my resolution, and see things just fine. The problem I have is that the top 2 inches of the screen seem to "bend" to the right about a half inch. Other than this the X-Server seems to be running well. I have drawn up a VERY dirty sketch of what the screen looks like just to try to explain, it can be found here: http://www.violentsin.com/images/X-Distoreted.png Any help would be appreciated. MessEdUp [EMAIL PROTECTED]#clanvs on irc.gamesnet.nethttp://www.violentsin.com[EMAIL PROTECTED] (MSN IM)
Still confused (Was: Re: SILO Fun)
Ok, I am still confused. I booted from the cd, in rescue mode, and then went to the shell to do some looking around: # df Filesystem 1k-blocks Used Available Use% Mounted on /dev/ram0 3524 3151 373 89% / /dev/sda1 3974908 76032 3696960 2% /target /dev/sda4 125779 30874 88411 26% /target/var # cd target # ls bin etc lib procusr bootfloppy lost+found rootvar cdrom homemnt sbinvmlinuz dev initrd opt tmp # ls -l boot -rw-r--r--1 root root 321829 Dec 1 19:08 System.map-2.2.20-sun4cd m lrwxrwxrwx1 root root1 Dec 1 19:39 boot -> . -rw-r--r--1 root root 1024 Aug 15 2002 cd.b -rw-r--r--1 root root 2982 Dec 1 19:08 config-2.2.20-sun4cdm lrwxrwxrwx1 root root1 Dec 1 19:39 etc -> . -rw-r--r--1 root root 1024 Aug 15 2002 fd.b -rw-r--r--1 root root 512 Aug 15 2002 first.b -rw-r--r--1 root root 1024 Aug 15 2002 generic.b -rw-r--r--1 root root 784 Aug 15 2002 ieee32.b -rw-r--r--1 root root 7680 Dec 1 19:35 old.b -rw-r--r--1 root root59904 Dec 1 19:43 second.b -rw-r--r--1 root root 2350 Aug 15 2002 silo.conf -rw-r--r--1 root root57512 Aug 15 2002 silotftp.b -rw-r--r--1 root root 512 Aug 15 2002 ultra.b -rw-r--r--1 root root 890942 Dec 1 19:08 vmlinuz-2.2.20-sun4cdm # /vmlinuz is defined as: lrwxrwxrwx1 root root 27 Dec 1 19:08 vmlinuz -> boot/vmlinuz-2.2.20-sun4cdm /etc/silo.conf is defined as # ls -l etc -rw-r--r--1 root root 2091 Dec 1 19:33 adduser.conf -rw-r--r--1 root root 44 Dec 1 19:25 adjtime [...] lrwxrwxrwx1 root root 17 Dec 1 19:40 silo.conf -> ../boot/silo.conf # so, it would make me think it does exist. So, why is Silo complaining? Boot device: /sbus/[EMAIL PROTECTED],80/[EMAIL PROTECTED],0 File and args: SILO Buggy old PROMs don't allow reading past 1GB from start of the disk. Send c omplains to SMCC Read error on block 360452 (tried 4096, got -1) Cannot find /etc/silo.conf (Unknown ext2 error) Couldn't load /etc/silo.conf No config file loaded, you can boot just from this command line Type [prompath;]part/path_to_image [parameters] on the prompt E.g. /iommu/sbus/espdma/esp/[EMAIL PROTECTED],0;4/vmlinux root=/dev/sda4 or 2/vmlinux.live (to load vmlinux.live from 2nd partition of boot disk) boot:
Re: Silo breakage creating woody r2 CDs for sparc
> Some consistency of the changes might not hurt. The fact that the
> debian-cd code in both woody _and_ unstable still depends on very
> specific behaviour of old versions of silo and mkisofs is a bit of a
> problem here:
Each release the debian-cd code changes because the dist changes. That
has included the boot stuff and arguments to mkisofs, aswell as
switching back and forth between mkisofs and mkhybrid.
This is nothing different. Mkisofs upstream would not accept the
-silo-boot patch, and so the Debian maintainer of mkisofs threw it out
aswell, and I was left with no way to make bootable sparc CD's in
unstable. So me being the SILO maintainer, I spent a lot of time writing
isofs.b to replace the old cd.b, so that an unpatched mkisofs could in
fact build bootable sparc CD's. Thing is, this only affects unstable,
NOT WOODY.
> > silo_deb=`ls $MIRROR/pool/main/s/silo/silo_*.deb | tail -1`
> > # put the relevant parts of SILO boot loader
> > (ar p $silo_deb data.tar.gz | \
> > tar zxf - -C $inst/ ./boot/{cd,second}.b)
>
> >I'm not taking any blame or guilt from your problems. You caused your
> >own headache.
>
> Thanks very much for the support, Ben. I've been working hard trying
> to get some sparc CDs created, and I didn't think asking for some help
> to get this job done was particularly out of order. Apparently I was
> wrong. I hope you have time to get the installer and CDs ready for the
> sarge release...
No, you didn't ask, you bitched and moaned and got pretty damn rude
about it. Just asking would have gotten you a nice reply with
explanation, and help avoiding the problem. Apparently you don't know
how to ask nicely and would rather be an ass about it. To top it off,
it's your own damn fault and you felt like pointing fingers.
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/
Re: Silo breakage creating woody r2 CDs for sparc
On Tue, Dec 02, 2003 at 12:51:52PM -0500, Ben Collins wrote:
>On Tue, Dec 02, 2003 at 03:57:46PM +, Steve McIntyre wrote:
>> On Tue, Dec 02, 2003 at 10:26:54AM -0500, Ben Collins wrote:
>> >> For now I'm going to leave the sparc images as they are. If there's no
>> >> way to test, then I'm going to wait until the boot-sparc script is
>> >> known to work. I'll work on the easier architectures first.
>> >
>> >I know they wont work, because isofs.b doesn't work like cd.b did, and
>> >you used a mkisofs that that was expecting that.
>>
>> No, I didn't, In the end I've used a woody mkisofs and the woody
>> silo. If _they_ don't work together, then things are screwed
>> altogether. That's how the r0 and r1 images are made, as far as I
>> know. Yes or no?
>
>If you used woody silo and woody mkisofs, then you are good to go.
Thank you. That's the information I was hoping to get out of you
several mails ago.
>> A mirror is a mirror. It's getting ludicrous to expect people
>> to set up a completely separate woody-only mirror to build CDs. All
>> the other architectures work fine in this scenario.
>
>How the hell do you expect to build woody CD's if you are using shit
>from unstable to build it? It's even more ludicrous for you to expect
>that to work. Woody CD's should build from woody. How can you expect
>that things don't change across over a year of development?
Some consistency of the changes might not hurt. The fact that the
debian-cd code in both woody _and_ unstable still depends on very
specific behaviour of old versions of silo and mkisofs is a bit of a
problem here:
> silo_deb=`ls $MIRROR/pool/main/s/silo/silo_*.deb | tail -1`
> # put the relevant parts of SILO boot loader
> (ar p $silo_deb data.tar.gz | \
> tar zxf - -C $inst/ ./boot/{cd,second}.b)
>I'm not taking any blame or guilt from your problems. You caused your
>own headache.
Thanks very much for the support, Ben. I've been working hard trying
to get some sparc CDs created, and I didn't think asking for some help
to get this job done was particularly out of order. Apparently I was
wrong. I hope you have time to get the installer and CDs ready for the
sarge release...
--
Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED]
Welcome my son, welcome to the machine.
signature.asc
Description: Digital signature
Re: /lib64/libc.so.6: unexpected reloc type 0x08
On Tue, Dec 02, 2003 at 12:01:00PM -0500, Andy Dougherty wrote: > On Mon, 1 Dec 2003, Ben Collins wrote: > > You probably want 32-bit anyway, so try this instead: > [sparc32] > > Yes, I agree that's usually the case, but in this case in particular I > wanted 64-bits :-). glibc was broken, Ben and DaveM fix it. Just wait to the next glibc in your debian mirrors. -solca
Re: Silo breakage creating woody r2 CDs for sparc
On Tue, Dec 02, 2003 at 03:57:46PM +, Steve McIntyre wrote: > On Tue, Dec 02, 2003 at 10:26:54AM -0500, Ben Collins wrote: > >> For now I'm going to leave the sparc images as they are. If there's no > >> way to test, then I'm going to wait until the boot-sparc script is > >> known to work. I'll work on the easier architectures first. > > > >I know they wont work, because isofs.b doesn't work like cd.b did, and > >you used a mkisofs that that was expecting that. > > No, I didn't, In the end I've used a woody mkisofs and the woody > silo. If _they_ don't work together, then things are screwed > altogether. That's how the r0 and r1 images are made, as far as I > know. Yes or no? If you used woody silo and woody mkisofs, then you are good to go. > >So you are telling me that the problem is that you are pulling stuff > >from unstable, and using unstable to build, and things are failing > >because of that? If so, then that's your mistake, not mine. Build on > >woody, and point to a woody mirror, not unstable. I can imagine the > >amount of problems you would have building that way. > > A mirror is a mirror. It's getting ludicrous to expect people > to set up a completely separate woody-only mirror to build CDs. All > the other architectures work fine in this scenario. How the hell do you expect to build woody CD's if you are using shit from unstable to build it? It's even more ludicrous for you to expect that to work. Woody CD's should build from woody. How can you expect that things don't change across over a year of development? I'm not taking any blame or guilt from your problems. You caused your own headache. -- Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ WatchGuard - http://www.watchguard.com/
Re: /lib64/libc.so.6: unexpected reloc type 0x08
On Mon, 1 Dec 2003, Ben Collins wrote: > See another post about fixing 64-bit with some temporary packages I > built. Yes, thank you. > You probably want 32-bit anyway, so try this instead: [sparc32] Yes, I agree that's usually the case, but in this case in particular I wanted 64-bits :-). Thanks again, Andy Dougherty [EMAIL PROTECTED]
dual 150 mhz hypersparc ss20
I shifted my firewall/email/dhcp/dns back over to my AMD system and my ss20 is for sale if someone wants it to work on the Ross Hypersparc dual cpu SMP boot problem. The system: ss20 chassis 2 Ross Hypersparc 150mhz cpus 512M Ram a video card in the chassis (not sure which) Antares fast wide scsi card FWS/2 (qlogic based, hence not visisble 2.2.x kernels) HME ethernet (along with basic Lance) another couple of ethernet cards not installed in the chassis, not sure what flavor or whether they work 2 Sun keyboards (one missing a key cap), one Sun mouse VGA adapter (requires high sync speed monitor) 9 G drive currently in the chassis (attached to slower internal SCSI) external 3 drive bay SCA enclosure; high grade cable to connect one extra 9G Seagate ST39173WC SCA drive one extra 4G Fujitsu M2954ESP SCA drive cdrom in the chassis works, though slow (just regular older cdrom drive) floppy drive in the chassis may be broken I paid out about $1,000 for this about two years ago. I had it setup in a server room at the CDC to test out a java based app we were developing on Sol/sparc. In that setup I had _all_ of the drives in the small external SCA box (extra fan in front of the drives) attached to the fast wide scsi controller and it ran fine SMP mode for about a year. I brought it home last February. Couple of months ago loaded debian sparc stable on it then upgraded (?) to unstable. 2.2.25 kernel ran fine on it SMP. 2.4.x and 2.6.x failed to run SMP, though 2.4.x ran uniprocessor fine. I ended up using 2.2.25 SMP. Then when the debian upgrade glitched and it was necessary to bump to a 2.4.x kernel I downgraded to uniprocessor 2.4.22. That's been stable, though I miss the second CPU. BTW, because the 2.2.25 kernel has trouble with the qlogic device I ran it with a single 9G drive in the box. When I recently shifted to uniprocessor 2.4.22 the qlogic fast wide SCSI controller showed up but I wasn't ready to have the extra noise in my work space. HINT: these are noisy clickity drives and the fans are audible in the standalone SCA enclosure. I briefly had ssl custom compiled and fast ssh on it. I gave up on the source-compile under debian because that tangled more often than it worked. Ended up switching over to lshc as a ssh replacement, though postfix/tls still ran through slow ssl library and took 10 seconds to crunch the keys. I tried to switch over to gentoo on top of debian (didn't have extra partition to do the gentoo install in its own space) and that blew up on me. Silly of me to try, actually. Anyway, I'd like to get $300 plus shipping out of it. Shipping could cost a bit because of the weight and size and hassle of putting it all together ?? $50 for shipping/handling? I live about an hour north of Atlanta (Gainesville) if someone is nearby and wants to do a purchase/pickup and save on shipping. Make an offer if the $300 is too high, though I'll wait awhile before I sell below $300 and try a few more routes, first. I used keyboard/minicom to do the linux install. I tried to purchase a cheap multi-sync monitor but it wasn't up to the speed put out by the video card and ended up returning the monitor. Now it's rigged headless and I control via ssh over local lan. I can leave the current debian setup on the disk or wipe it. Heitzso heitzso at growthmodels dot com
Re: Silo breakage creating woody r2 CDs for sparc
On Tue, Dec 02, 2003 at 10:26:54AM -0500, Ben Collins wrote: >> For now I'm going to leave the sparc images as they are. If there's no >> way to test, then I'm going to wait until the boot-sparc script is >> known to work. I'll work on the easier architectures first. > >I know they wont work, because isofs.b doesn't work like cd.b did, and >you used a mkisofs that that was expecting that. No, I didn't, In the end I've used a woody mkisofs and the woody silo. If _they_ don't work together, then things are screwed altogether. That's how the r0 and r1 images are made, as far as I know. Yes or no? >So you are telling me that the problem is that you are pulling stuff >from unstable, and using unstable to build, and things are failing >because of that? If so, then that's your mistake, not mine. Build on >woody, and point to a woody mirror, not unstable. I can imagine the >amount of problems you would have building that way. A mirror is a mirror. It's getting ludicrous to expect people to set up a completely separate woody-only mirror to build CDs. All the other architectures work fine in this scenario. -- Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED] You lock the door And throw away the key There's someone in my head but it's not me pgpuLOjbsMZKl.pgp Description: PGP signature
Re: Silo breakage creating woody r2 CDs for sparc
> For now I'm going to leave the sparc images as they are. If there's no > way to test, then I'm going to wait until the boot-sparc script is > known to work. I'll work on the easier architectures first. I know they wont work, because isofs.b doesn't work like cd.b did, and you used a mkisofs that that was expecting that. So you are telling me that the problem is that you are pulling stuff from unstable, and using unstable to build, and things are failing because of that? If so, then that's your mistake, not mine. Build on woody, and point to a woody mirror, not unstable. I can imagine the amount of problems you would have building that way. Besides, the woody/sarge build scripts in debian-cd are seperate. I can change the sarge one to be correct, and leave the woody one the same, but you will still have to fix your build environment. Heck, just make a minimum chroot to build out of. -- Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ WatchGuard - http://www.watchguard.com/
Re: Silo breakage creating woody r2 CDs for sparc
On Tue, Dec 02, 2003 at 09:52:41AM -0500, Ben Collins wrote: >> >The path to isofs.b needs to be absolute on the build machine (not >> >relative to the CD root). The "..." is literal, it means use isofs.b to >> >boot any sort of sparc (sun4c,sun4m,sun4d,sun4u). >> >> Some warning of these changes would have been useful. Does this mean >> that the set of images I've just produced are now useless? > >I had forgotten that I had put silo 1.3.x into stable. Wasn't >intentional. I didn't realize that mkisofs had changed in woody. That's >pretty broken in itself (or maybe you are running testing/unstable to do >the CD builds, which is probably not a good idea either). No, silo 1.2.x is still in woody. The mkisofs and silo versions I'm now using are the woody ones, by dint of forcing things in the build script. My development machine (the one with the mirror attached) is running unstable, but the silo problem would have shown up there anyway - the script to make Sparc bootable CDs grabs the latest one directly out of the mirror. And can you please work out your differences with Joerg and/or the mkisofs maintainer so we can get these going again? >The images you produced are broken, I'm sure. My mistake on the silo >problem, but you could calm down a bit. Things happen. Is there any easy way to check them? It would be nice not to have to start _again_. It's becoming impractical already to make CDs for woody due to the mixture of breakages and the sheer length of time taken to build them; I shudder to think what sarge is going to be like at this rate. For now I'm going to leave the sparc images as they are. If there's no way to test, then I'm going to wait until the boot-sparc script is known to work. I'll work on the easier architectures first. -- Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED] You raise the blade, you make the change... You re-arrange me 'til I'm sane... pgp1Fh0iqGq57.pgp Description: PGP signature
Re: Silo breakage creating woody r2 CDs for sparc
> >The path to isofs.b needs to be absolute on the build machine (not > >relative to the CD root). The "..." is literal, it means use isofs.b to > >boot any sort of sparc (sun4c,sun4m,sun4d,sun4u). > > Some warning of these changes would have been useful. Does this mean > that the set of images I've just produced are now useless? I had forgotten that I had put silo 1.3.x into stable. Wasn't intentional. I didn't realize that mkisofs had changed in woody. That's pretty broken in itself (or maybe you are running testing/unstable to do the CD builds, which is probably not a good idea either). The images you produced are broken, I'm sure. My mistake on the silo problem, but you could calm down a bit. Things happen. -- Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ WatchGuard - http://www.watchguard.com/
Re: Silo breakage creating woody r2 CDs for sparc
On Tue, Dec 02, 2003 at 08:14:13AM -0500, Ben Collins wrote:
>On Tue, Dec 02, 2003 at 01:31:26AM +, Steve McIntyre wrote:
>>
>>
>> We're late getting the r2 images created, and changes to the packages
>> that we need to use don't help. The script to make sparc CDs bootable
>> contains the following:
>>
>> silo_deb=`ls $MIRROR/pool/main/s/silo/silo_*.deb | tail -1`
>> # put the relevant parts of SILO boot loader
>> (ar p $silo_deb data.tar.gz | \
>> tar zxf - -C $inst/ ./boot/{cd,second}.b)
>>
>> This currently picks up silo_1.3.1-2_sparc.deb, which doesn't contain
>> a cd.b file at all, so the sparc build fails. Generally after an hour
>> of frantic disk-thrashing. I don't know if the change to silo is
>> deliberate or not, but for now I'm patching the script to use the bits
>> out of silo_1.2.5-2_sparc.deb instead, as that seems to have what we
>> need. If this is wrong, please shout!
>
>The silo cd boot step changed. You'll need isofs.b and second.b, and
>you'll need to move silo.conf to /boot on the CD. Then change the
>mkisofs incantation to include these bootable options:
>
> -r -G /boot/isofs.b -B ...
>
>The path to isofs.b needs to be absolute on the build machine (not
>relative to the CD root). The "..." is literal, it means use isofs.b to
>boot any sort of sparc (sun4c,sun4m,sun4d,sun4u).
Some warning of these changes would have been useful. Does this mean
that the set of images I've just produced are now useless?
--
Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED]
Support the Campaign for Audiovisual Free Expression: http://www.eff.org/cafe/
pgpoRrnJAn24o.pgp
Description: PGP signature
Re: Silo breakage creating woody r2 CDs for sparc
On Tue, Dec 02, 2003 at 01:31:26AM +, Steve McIntyre wrote:
>
>
> We're late getting the r2 images created, and changes to the packages
> that we need to use don't help. The script to make sparc CDs bootable
> contains the following:
>
> silo_deb=`ls $MIRROR/pool/main/s/silo/silo_*.deb | tail -1`
> # put the relevant parts of SILO boot loader
> (ar p $silo_deb data.tar.gz | \
> tar zxf - -C $inst/ ./boot/{cd,second}.b)
>
> This currently picks up silo_1.3.1-2_sparc.deb, which doesn't contain
> a cd.b file at all, so the sparc build fails. Generally after an hour
> of frantic disk-thrashing. I don't know if the change to silo is
> deliberate or not, but for now I'm patching the script to use the bits
> out of silo_1.2.5-2_sparc.deb instead, as that seems to have what we
> need. If this is wrong, please shout!
The silo cd boot step changed. You'll need isofs.b and second.b, and
you'll need to move silo.conf to /boot on the CD. Then change the
mkisofs incantation to include these bootable options:
-r -G /boot/isofs.b -B ...
The path to isofs.b needs to be absolute on the build machine (not
relative to the CD root). The "..." is literal, it means use isofs.b to
boot any sort of sparc (sun4c,sun4m,sun4d,sun4u).
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/
Re: Console problem at Enterprise 3000
Carlos, I dont know about the enterprise 3000, but all the Sparcs I have worked with only have a framebuffer. Make sure you have frame buffer support compiled into your kernel. Leith -- http://qasr.mine.nu Carlos Emir M. Macedo wrote: Hi, I've recently installed Debian Woody at an Sparc Enterprise 3000. Everything went ok, except the console. It works fine at default installation, but after kernel recompilation, I can´t useit (tty1 to tty6) anymore. I can logon through ssh. No reported errors at system logs. I've been working with Debian for a long time, but never with Sparc platform. Could someone help me? Thanks in advance. = Carlos Emir Mantovani Macedo Technical Support Tecnologia Bancária S.A. +55 11 3244-1900 R. 8817 [EMAIL PROTECTED] http://www.tecban.com.br = As informações existentes nessa mensagem são para uso restrito, sendo seu sigilo protegido por lei. Caso não seja destinatário, saiba que leitura, divulgação ou cópia são proibidas. Favor apagar as informações e notificar o remetente. O uso impróprio será tratado conforme as normas da empresa e a legislação em vigor. The informations contained in this message are restricted, and its confidentiality protected by law. In case you are not theaddressee, be aware that the reading, spreading and copy of this message is unauthorized. Please, delete this message and notify the sender. The improper use of this information will be treated according the company's internal rules and legal laws.
Re: Silo breakage creating woody r2 CDs for sparc
On Tue, 2 Dec 2003, David S. Miller wrote: > On Tue, 2 Dec 2003 02:33:56 + > Steve McIntyre <[EMAIL PROTECTED]> wrote: > > > If this next attempted build fails, I'm going to abandon the sparc > > images altogether, and recommend that woody r2 does not include sparc > > CDs. Does anybody actually care in the SLIGHTEST about supporting > > sparc CDs? It certainly doesn't look that way. It's now 2.30am here, > > and I'm going to bed. I'll check in the morning if the CDs built, but > > as it stands right now I'd be quite surprised... > > Why don't you wait a bit for Ben Collins to wake up and read > his email so that he can help you with these problems? > > I fully recognize the amount of time and effort you are putting > into trying to get these CDs built, but posting as if an immediate > response is required and throwing a tantrum won't fix the problem. > > Let's wait for what Ben has to say about this ok? I think a lot of > people would like to have Sparc CD images if possible. > > > I dont think Steve was commenting on if users wanted sparc CDs. He was talking about if anyone in Debian wanted to support sparc CDs. Brian
Re: Silo breakage creating woody r2 CDs for sparc
On Tue, Dec 02, 2003 at 01:50:17AM -0800, David S. Miller wrote: >On Tue, 2 Dec 2003 02:33:56 + >Steve McIntyre <[EMAIL PROTECTED]> wrote: > >> If this next attempted build fails, I'm going to abandon the sparc >> images altogether, and recommend that woody r2 does not include sparc >> CDs. Does anybody actually care in the SLIGHTEST about supporting >> sparc CDs? It certainly doesn't look that way. It's now 2.30am here, >> and I'm going to bed. I'll check in the morning if the CDs built, but >> as it stands right now I'd be quite surprised... > >Why don't you wait a bit for Ben Collins to wake up and read >his email so that he can help you with these problems? > >I fully recognize the amount of time and effort you are putting >into trying to get these CDs built, but posting as if an immediate >response is required and throwing a tantrum won't fix the problem. > >Let's wait for what Ben has to say about this ok? I think a lot of >people would like to have Sparc CD images if possible. The build appears to have worked, FWIW. I've checked that the jigdo files are valid by rebuilding images from them, and I'm uploading the jigdo bits (slowly) now to cdimage. I wasn't especially expecting an immediate response last night, but it does get really annoying when there are multiple mails every day now, pestering for the new r2 images, and the toolchain needed to build them has just been allowed to rot by the architecture maintainers. Apologies for the tantrum, but _please_ can we get architecture folks to put some effort into the CD creation process...? -- Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED] "It's actually quite entertaining to watch ag129 prop his foot up on the desk so he can get a better aim." [ seen in ucam.chat ] pgpW1ynFz1D6A.pgp Description: PGP signature
Re: Silo breakage creating woody r2 CDs for sparc
On Tue, 2 Dec 2003 02:33:56 + Steve McIntyre <[EMAIL PROTECTED]> wrote: > If this next attempted build fails, I'm going to abandon the sparc > images altogether, and recommend that woody r2 does not include sparc > CDs. Does anybody actually care in the SLIGHTEST about supporting > sparc CDs? It certainly doesn't look that way. It's now 2.30am here, > and I'm going to bed. I'll check in the morning if the CDs built, but > as it stands right now I'd be quite surprised... Why don't you wait a bit for Ben Collins to wake up and read his email so that he can help you with these problems? I fully recognize the amount of time and effort you are putting into trying to get these CDs built, but posting as if an immediate response is required and throwing a tantrum won't fix the problem. Let's wait for what Ben has to say about this ok? I think a lot of people would like to have Sparc CD images if possible.
