Re: error compiling 2.6.5-rc2
> > > /bin/sh: line 1: scripts/bin2c: No such file or directory >> There is a "scripts/bin2c.c" if that what you mean. >> >> I also removed the CONFIG_IKCONFIG option, now I get another error: >> >> [EMAIL PROTECTED]:/usr/src/linux$ cat image.err >> /bin/sh: line 1: scripts/conmakehash: No such file or directory > Somehow the stuff in scripts/ is not getting built. 2.6.5-rc2 > rearranges the build rules for this, but it certainly looks to me like > it still works. I don't know that I can debug this, but does 'make > scripts' build these things (bin2c, conmakehash, and other programs)? > Peter I haven't tried "make scripts"; but now 2.6.5-rc-bk2 (released today) builds fine. I just saw that 2.6.5-rc-bk2 Makefile has the following changes (partial listing): @@ -563,7 +563,7 @@ # Handle descending into subdirectories listed in $(SUBDIRS) .PHONY: $(SUBDIRS) -$(SUBDIRS): prepare-all +$(SUBDIRS): prepare-all scripts $(Q)$(MAKE) $(build)=$@ and decided to try it out, and it works! Thanks, Mustafa
Re: KDE 3.2
On Tue, 16 Mar 2004, James McNeill wrote: > Date: Tue, 16 Mar 2004 15:37:49 +1100 > From: James McNeill <[EMAIL PROTECTED]> > To: Timothy Ward <[EMAIL PROTECTED]> > Cc: debian-sparc@lists.debian.org > Subject: Re: KDE 3.2 > Resent-Date: Mon, 15 Mar 2004 22:37:20 -0600 (CST) > Resent-From: debian-sparc@lists.debian.org > > is already: > > deb ftp://download.au.kde.org/pub/kde/stable/3.2/Debian stable main > is not ready for sparc, is only for i386. apt-get update ... 91% [1 Packages 0] Err ftp://download.au.kde.org stable/main Packages Unable to fetch file, server said '/pub/kde/stable/3.2/Debian/dists/stable/main/binary-sparc/Packages.gz: No such file or directory ' ... and with ncftp ... ncftp / > cd pub/kde/stable/3.2/Debian/dists/stable/main ls ncftp ...bian/dists/stable/main > ls binary-i386/ Release.in ... /* --- */ /* Andres Carlos Roman */ /* */ /*Secretaria de Programacion Universitaria */ /*UNIVERSIDAD NACIONAL DEL LITORAL */ /* Pje. Martinez 2652 - S3002AAB Santa Fe - Argentina */ /* tel +54(342)455-4245 - FAX +54(342)457-1240 */ /* --- */
Re: error compiling 2.6.5-rc2
[Mustafa Hussein] > > > /bin/sh: line 1: scripts/bin2c: No such file or directory > There is a "scripts/bin2c.c" if that what you mean. > > I also removed the CONFIG_IKCONFIG option, now I get another error: > > [EMAIL PROTECTED]:/usr/src/linux$ cat image.err > /bin/sh: line 1: scripts/conmakehash: No such file or directory Somehow the stuff in scripts/ is not getting built. 2.6.5-rc2 rearranges the build rules for this, but it certainly looks to me like it still works. I don't know that I can debug this, but does 'make scripts' build these things (bin2c, conmakehash, and other programs)? Peter signature.asc Description: Digital signature
Re: SS20 won't talk to my hub
[EMAIL PROTECTED] > When plugged into my (cheap, 100/10Mb) hub, my SS20 refuses to be > reached. It can't be pinged or otherwise contacted, despite the link > light being on. It does talk to my other machines when directly > connected with a cross-over cable however. Friend of mine had this problem recently with a LANCE chip on sparc, and not even a 10baseT hub seemed to help. She didn't try your crossover solution. What worked was to acquire an external AUI->TP transceiver. My theory is that the LANCE 10baseT transceivers tend to be flaky. Peter signature.asc Description: Digital signature
Alternative Network Configuration
Hi, I was wondering if anyone knew of a way ot have debian ask for various network configs during boot on my Netra. The thing is that it mainly uses a fixed configuration, and only needs a DHCP configuration once a week. Is there a way to have a program ask for Config A or Config B ? Thanks in advance ! Regards, Neil P.S. I presume this mail is more for debian-users but I've only got this list for now...
RE: netra X1 tftp boot..and install
Thanks Neil, I have recently been trying an install via a CD, having replaced the secondary HDD with a cd-rom. This is working well for me at the moment, but I'm sure I'll give the netboot another go at some point using your guidelines. thanks for the input. Regards This e-mail is confidential and may be privileged. It may be read, copied and used only by the intended recipient. If you have received it in error, please contact the sender immediately by return e-mail or by telephoning +44 (0)20 7934 9000. Please then delete the e-mail and do not disclose its contents to any person. We believe, but do not warrant that this e-mail and any attachments, are virus free. You should take full responsibility for virus checking. SBG Companies reserve the right to monitor all email communications through their internal and external networks.
Re: mutt / Bus error (retry)
On Mon, 2004-03-15 at 16:41 +0100, Olivier Mueller wrote:
> On Mon, 2004-03-15 at 16:16, Ben Collins wrote:
> > THen I'd say there's a bug in either libssl, or how mutt uses ssl
> > (probably this one). File a bug on mutt.
>
> already done 2 months ago: http://bugs.debian.org/228855 :)
well, it is still broken: I'm asking myself:
- is there anybody using mutt+tls/ssl here ?
- or is the problem only on my own sparc box?
If you'd like to try, what happens if you put this
in your .muttrc:
set imap_user="[EMAIL PROTECTED]"
set spoolfile={mail.omx.ch}
set folder={mail.omx.ch}
mailboxes {mail.omx.ch}
and then start mutt ? Here it is still:
"Connecting to mail.omx.ch... Bus error"
thx & regards,
Olivier
--
___
Olivier Müller - PGP key ID: 0x0E84D2EA - Switzerland
E-Mail: http://omx.ch/mail/ - AIM/iChat: swix3k
Re: SS20 won't talk to my hub
On Monday 22 Mar 2004 10:01, [EMAIL PROTECTED] wrote: > Hi All, > > New to linux on sparc, but I have had a good search and can't find an > answer to a little problem I've run into... > > When plugged into my (cheap, 100/10Mb) hub, my SS20 refuses to be reached. > It can't be pinged or otherwise contacted, despite the link light being on. > It does talk to my other machines when directly connected with a cross-over > cable however. > > >From what I've read already, I think my hub isn't negotiating properly > > with > > the lance ethernet device. > If it's a cheap hub, it's quite possible that the hub doesn't support 10Mbit/s at half-duplex, or it breaks the auto-negotiation standards in some way. I suggest that you try and borrow another hub if you can and see if that works. -- David Johnson http://www.david-web.co.uk/
RE: SS20 won't talk to my hub
> -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: 22 March 2004 10:02 > To: debian-sparc@lists.debian.org > Subject: SS20 won't talk to my hub > > When plugged into my (cheap, 100/10Mb) hub, my SS20 refuses > to be reached. > It can't be pinged or otherwise contacted, despite the link > light being on. > It does talk to my other machines when directly connected > with a cross-over > cable however. > > From what I've read already, I think my hub isn't negotiating > properly with > the lance ethernet device. Hmm...the SS20 has 10Mb ethernet on board...if you're plugging into a 'cheap 100/10Mb hub' the chances are that it's one of the nasty old things that partitions it's 10Mb and 100Mb connections onto different networks rather than bridging between the two as a switch would. If this is the case and all your other kit connected to the hub is 100Mb you'll have no comms between the two networks. Try forcing one of the other devices on the hub to 10Mb and see if you can ping it then. Gary
Re: temp solution: sun fire v100 / gcc 3 woes
> After spending 3 days tweaking, I figured it out! Gcc 3.2 / 3.3 seems > unable to build a kernel for my Sun Fire V100. It compiles without fatal > errors, but upon booting the Sun crashes: > > SILO Version 1.4.4 > boot: 2.4.25 -p > Allocated 8 Megs of memory at 0x4000 for kernel > Loaded kernel version 2.4.25 > Illegal Instruction > ok You're sure you end up with a 64 bit binary ? I'm running a 2.4.25 kernel compiled with gcc 3.3. (this all assuming your CPU is a sparc64)/ Igmar
SS20 won't talk to my hub
Hi All, New to linux on sparc, but I have had a good search and can't find an answer to a little problem I've run into... When plugged into my (cheap, 100/10Mb) hub, my SS20 refuses to be reached. It can't be pinged or otherwise contacted, despite the link light being on. It does talk to my other machines when directly connected with a cross-over cable however. >From what I've read already, I think my hub isn't negotiating properly with the lance ethernet device. I'm running a fresh install of Woody, ethtool and mii-setup don't seem to be compatible with the lance chip however. Has anyone else had this problem, or have any pointers? I'd prefer to avoid having to get a new hub. Any help/suggestions much appreciated, Dan mail2web - Check your email from the web at http://mail2web.com/ .
temp solution: sun fire v100 / gcc 3 woes
After spending 3 days tweaking, I figured it out! Gcc 3.2 / 3.3 seems unable to build a kernel for my Sun Fire V100. It compiles without fatal errors, but upon booting the Sun crashes: SILO Version 1.4.4 boot: 2.4.25 -p Allocated 8 Megs of memory at 0x4000 for kernel Loaded kernel version 2.4.25 Illegal Instruction ok I tried kernels 2.4.25, 2.4.26-pre3 and 2.6.4 and gcc 3.2 and 3.3 (from Debian Testing) but to no avail. Also, the Debian package kernel-image-2.4.24-sparc64_35_sparc.deb gives the same error. Luckily, compiling with egcs64_19980921 works ok! (through editing arch/sparc64/Makefile) The Sun Fire V100 is actually a Netra X1 plus a CDrom drive and upgraded PROM (4.0.18 in stead of 4.0.6). The Netra X1 works fine though with a gcc3 compiled kernel. Strange huh? But it gets stranger... Some years ago I bougt two Sun Fire V100's. Only this week I found out that they give different bootup messages: Sun Fire V100 (UltraSPARC-IIe 548MHz), No Keyboard OpenBoot 4.0, 768 MB memory installed, Serial #51606773. Ethernet address 0:3:ba:13:74:f5, Host ID: 831374f5. opposite to: Sun Netra X1 (UltraSPARC-IIe 548MHz), No Keyboard OpenBoot 4.0, 768 MB memory installed, Serial #51800813. Ethernet address 0:3:ba:16:6a:ed, Host ID: 83166aed. They have the same PROM (4.0.16) though. But.. the V100 which names itself X1, actually boots fine with a gcc3 compiled kernel. The other V100, which seems to be a true V100 (but also PROM 4.0.16) will only boot an egcs64-compiled kernel. I hope this information is useful for someone :) Willem
