Re: unbreaking LibreOffices tests on at least release architectures
On Sun, Jun 18, 2023 at 10:32:55AM +0200, Rene Engelhard wrote: >Hi, > >Am 18.06.23 um 10:19 schrieb John Paul Adrian Glaubitz: >> On Sun, 2023-06-18 at 09:31 +0200, Rene Engelhard wrote: >> > Also note I am not talking about the debian-ports architectures. Those I >> > forgot and I have no problems making them stay into "testsuite ran but >> > results ignored" set. >> Why did you send this mail exclusively to debian-ports then? > >I (obviously) wrongly assumed that this was the magic address which >duplicates to every port. > >Must have misremembered. It still does - I got this copy via the debian-arm list... -- Steve McIntyre, Cambridge, UK.st...@einval.com "This dress doesn't reverse." -- Alden Spiess
Re: debian-installer now available in Ports
On Wed, Apr 12, 2017 at 01:55:08PM +0100, Steven Chamberlain wrote: >John Paul Adrian Glaubitz wrote: >> Thus, I was wondering whether any volunteers would be willing to help >> building >> ISO images for the various architectures. > >I'm already doing this for kfreebsd-amd64, but only the jessie-kfreebsd >suite: >http://jenkins.kfreebsd.eu/jenkins/view/cd/job/debian-cd_jessie-kfreebsd/lastBuild/console >and I had to patch debian-cd before it worked. (Didn't yet find time to >file bugs or submit those patches). Please post them! >I could probably set up similar jobs for kfreebsd-* sid now. > >> It's not necessary to run debian-cd on the same architecture as the >> target architecture of the ISO images. Exactly. There are sometimes difficulties with the tools needed to set up boot files etc., but they tend to be portable. >I did not even realise that. So I will add kfreebsd-i386 next. > >I expect there might be problems trying to build linux arches from a >kfreebsd host. But we should try to find out, and then maybe fix it. We were happily building kfreebsd-* images from a Linux host, so I'd expect it to work OK. I've offered before: I don't have the time personally to work on building ports images, but I'm more than happy to help other people getting them building on our official infrastructure... -- Steve McIntyre, Cambridge, UK.st...@einval.com Who needs computer imagery when you've got Brian Blessed?
Re: Bug#767682: D-I: installer hangs on re-formatting ext4 partition (having grub in the partition boot record).
On Wed, Feb 10, 2016 at 07:14:07PM +0100, Christian PERRIER wrote: >Quoting John Paul Adrian Glaubitz (glaub...@physik.fu-berlin.de): >> Hi! >> >> Coming back to the discussion after having re-assigned the bug to the >> partman-ext3 package. First of all, this particular bug was reported >> in Ubuntu as well [1], so I have linked this bug report to the LP bug >> report. >> >> Secondly, I would like to discuss here what is keeping us from adding >> "-F" to the mkfs.$filesystem call in 50format_ext3. I am currently >> not seeing any obvious, but I might just be missing something here. >> >> However, since we are using "-f" (the btrfs equivalent to mkfs.ext3's >> "-F") in partman-btrfs [2], I see no apparent reason not to use it if >> it helps resolving problems people are seeing on certain architectures >> and partition setups. > >Just read the bug log and got convinced. >So the patch would actually be: > >diff --git a/commit.d/format_ext3 b/commit.d/format_ext3 >index fe84d89..d86c545 100755 >--- a/commit.d/format_ext3 >+++ b/commit.d/format_ext3 >@@ -56,7 +56,7 @@ for dev in $DEVICES/*; do >usage='' >fi >if log-output -t partman --pass-stdout \ >- mkfs.$filesystem $device $usage >/dev/null; then >+ mkfs.$filesystem -F $device $usage >/dev/null; then > sync >status=OK >else > > >Objections for me to commit? It looks like an obvious fix - go ahead! -- Steve McIntyre, Cambridge, UK.st...@einval.com Into the distance, a ribbon of black Stretched to the point of no turning back
Re: Time to change the debian-ports list?
On Wed, Jul 22, 2015 at 05:38:17PM +0200, Wouter Verhelst wrote: On Fri, Jul 17, 2015 at 01:40:20PM +0100, Steve McIntyre wrote: On Thu, Sep 11, 2014 at 12:51:29PM +0100, Steve McIntyre wrote: On Wed, Sep 10, 2014 at 07:01:00PM +, Thorsten Glaser wrote: Alexander Wirt dixit: Could you please (technically) summarize what needs to be done from listmaster side? 1. Remove whatever debian-po...@lists.debian.org is right now 2. Create a new debian-po...@lists.debian.org mailing list which works just like the other regular lists 3. Announce the new debian-po...@lists.debian.org so that people can subscribe to it; document that there is no longer an address to reach *all* ports but that people should eMail the individual ports’ lists (and cross-post if needed, but only to the amount needed), and that the new debian-po...@lists.debian.org instead is a mailing list for discussion about a) debian-ports.org infrastructure b) porting Debian in general c) questions related to setting up a Debian port, including wanna-build, buildd, etc. That seems like a bad idea to me, tbh. There will be people who won't notice that the meaning of debian-ports@ has changed, and who will try to use it with its old meaning. If there are problems with the current meaning of debian-ports, can't we just retire the old alias and create a list under a different name? Is there much point to that? I've not heard anybody at all speak up in favour of the existing behaviour. If anybody does use try to use it that way in future, the new list will most likely be the best place for their mail to go... -- Steve McIntyre, Cambridge, UK.st...@einval.com I used to be the first kid on the block wanting a cranial implant, now I want to be the first with a cranial firewall. -- Charlie Stross -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150722170456.gc5...@einval.com
Re: Time to change the debian-ports list?
On Thu, Sep 11, 2014 at 12:51:29PM +0100, Steve McIntyre wrote: On Wed, Sep 10, 2014 at 07:01:00PM +, Thorsten Glaser wrote: Alexander Wirt dixit: Could you please (technically) summarize what needs to be done from listmaster side? 1. Remove whatever debian-po...@lists.debian.org is right now 2. Create a new debian-po...@lists.debian.org mailing list which works just like the other regular lists 3. Announce the new debian-po...@lists.debian.org so that people can subscribe to it; document that there is no longer an address to reach *all* ports but that people should eMail the individual ports’ lists (and cross-post if needed, but only to the amount needed), and that the new debian-po...@lists.debian.org instead is a mailing list for discussion about a) debian-ports.org infrastructure b) porting Debian in general c) questions related to setting up a Debian port, including wanna-build, buildd, etc. That's exactly it, yes. Thanks. :-) Hi Alexander et al,, Could we make a start on this please? More discussions on the d-ports expander today have reminded me how annoying the current setup is. -- Steve McIntyre, Cambridge, UK.st...@einval.com ...In the UNIX world, people tend to interpret `non-technical user' as meaning someone who's only ever written one device driver. -- Daniel Pead -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150717124020.ga13...@einval.com
Ports pages need updating on www.d.o
Hi folks, I've been trying to help out a bit with the port pages (under https://www.debian.org/ports/), starting with the ARM ports. We could really do with updating a lot of the information here - it's so old it's starting to smell bad! I've removed some of the older details (e.g. hardware support) that used to be under https://www.debian.org/ports/arm and replaced them with pointers to the wiki now. My reasoning here is that the wiki is more easily updated for more dynamic content like this, plus it's much easier for the wider community to contribute that way. I'd suggest that most of the other port pages would be better organised like this too, but that's a decision for porters to make for themselves. We also need to work on some of the other content around here. For example, the top-level ports page is still listing the ports from Wheezy rather than Jessie. Please take a look. In the webwml source, there's even a file to list maintainers for the various port pages. Until I touched it today, it hadn't been modified since 2005. It's clearly not very useful at the moment! -- Steve McIntyre, Cambridge, UK.st...@einval.com I suspect most samba developers are already technically insane... Of course, since many of them are Australians, you can't tell. -- Linus Torvalds -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150428223702.go21...@einval.com
Sparc32 Love?
Hello one and all, as I've come into the ownership of quite a few Sun4m SPARC32 machines in the past few weeks, I've gotten an old install of Sarge with a 2.4 kernel running on one and have been painfully compiling some necessary files to get newer programs working on the old and crufty system to be able to play nicely with it. So far it seems the only alternative to using an older version of Linux is OpenBSD, and although I've tried that, there hasn't been much luck with getting things to compile properly on it, not to mention that half the packages in their repos are MISSING! Sparc64 has them, i386 has them, but there's essential files like glib2 and other misc packages just plain MISSING. so this ends up in a day and a half compile that just segfaults with a core dump... not the happiest thing. I've already seen at least one person successfully boot a 3.1.5 kernel on my exact machine model I'm trying to do this on (SparcStation 5) back in 2011 on a built-from-scratch Gentoo installation... so why not Debian? is there still any interest at all anywhere from anyone to get even an unsupported Sparc32 port going again? it's a crime it's not already, since even GCC still supports Sparcv8 as a compiler argument so to stay compatible with the Leon and OpenSPARC cores-- this should make an unsupported port by the right person work out somewhat well, I'd think. so, I'm calling anyone out... anyone at all, willing to do an unofficial Sparc32 port of Wheezy or Jessie to the long-abandoned, closet-dwelling dusty machines that should actually be capable of something instead of sitting around just getting more expensive on auction sites... if they're that valuable, they should be actually able to DO something! even if the port goes ahead and targets only the OpenSPARC and Leon cores, it's still a good start! --Steve -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/caakahskhlvb5qi6z1y46hnf7o8ndjmao6gyzb7r4yt8eyix...@mail.gmail.com
Re: Time to change the debian-ports list?
On Wed, Sep 10, 2014 at 07:01:00PM +, Thorsten Glaser wrote: Alexander Wirt dixit: Could you please (technically) summarize what needs to be done from listmaster side? 1. Remove whatever debian-po...@lists.debian.org is right now 2. Create a new debian-po...@lists.debian.org mailing list which works just like the other regular lists 3. Announce the new debian-po...@lists.debian.org so that people can subscribe to it; document that there is no longer an address to reach *all* ports but that people should eMail the individual ports’ lists (and cross-post if needed, but only to the amount needed), and that the new debian-po...@lists.debian.org instead is a mailing list for discussion about a) debian-ports.org infrastructure b) porting Debian in general c) questions related to setting up a Debian port, including wanna-build, buildd, etc. That's exactly it, yes. Thanks. :-) -- Steve McIntyre, Cambridge, UK.st...@einval.com I suspect most samba developers are already technically insane... Of course, since many of them are Australians, you can't tell. -- Linus Torvalds -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2014095129.gg14...@einval.com
Re: Time to change the debian-ports list?
On Fri, Sep 05, 2014 at 06:39:10PM +0100, Steve McIntyre wrote: Hi folks, I believe the existing debian-ports setup (as an exploder pointing to all the different port lists) is not working well at all. It's a confusing setup to many people, which leads to lots of cross-list noise that's probably not warranted. Some of the traffic is also clearly meant to be discussing the debian-ports setup itself rather than individual ports, and that's also off-topic for those ports that are in the main archive. So, I propose: * Remove the confusion: turn debian-ports into a separate *normal* mailing list, announce it and let people subscribe to it as they see fit normally. This would be specifically for discussions about ports.debian.org and architectures hosted there. * Explicitly do *not* add another exploder to replace the old address: instead, *if* we want something to cover this use case, add a new list that interested people can subscribe to. Maybe debian-cross-ports or debian-architectures or something. Please feel free to suggest a better name! If such a list were to be set up, we could/should encourage existing architecture porters to sign up there too. Thoughts? Any dissenting opinions? Listmasters - are you happy to change things like I propose? -- Steve McIntyre, Cambridge, UK.st...@einval.com Armed with Valor: Centurion represents quality of Discipline, Honor, Integrity and Loyalty. Now you don't have to be a Caesar to concord the digital world while feeling safe and proud. -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140910150520.go24...@einval.com
Time to change the debian-ports list?
Hi folks, I believe the existing debian-ports setup (as an exploder pointing to all the different port lists) is not working well at all. It's a confusing setup to many people, which leads to lots of cross-list noise that's probably not warranted. Some of the traffic is also clearly meant to be discussing the debian-ports setup itself rather than individual ports, and that's also off-topic for those ports that are in the main archive. So, I propose: * Remove the confusion: turn debian-ports into a separate *normal* mailing list, announce it and let people subscribe to it as they see fit normally. This would be specifically for discussions about ports.debian.org and architectures hosted there. * Explicitly do *not* add another exploder to replace the old address: instead, *if* we want something to cover this use case, add a new list that interested people can subscribe to. Maybe debian-cross-ports or debian-architectures or something. Please feel free to suggest a better name! If such a list were to be set up, we could/should encourage existing architecture porters to sign up there too. Thoughts? -- Steve McIntyre, Cambridge, UK.st...@einval.com Welcome my son, welcome to the machine. -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140905173910.gf17...@einval.com
Re: Problems with X11 on Ultra10
On Sun, May 04, 2014 at 10:12:08PM +0100, Sad Clouds wrote: On Sun, 4 May 2014 13:38:15 -0400 David Gosselin d...@appleside.org wrote: I was curious as to what prompted you to try SBUS:/SUNW,ffb@1e,0 for the BusID value? Thanks, Dave Searched on google for debian on sparc64 and creator3d framebuffer and someone had their xorg.conf with that bus id. Xorg log file also makes references to that. Please do not cc: debian-ports on your messages. debian-ports is a meta-mailing list that forwards to the mailing lists for *all* of the Debian ports. Redirecting to debian-sparc. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Re: Bug#731806: debian-installer: FTBFS on sparc: genisoimage errors
On Mon, Apr 28, 2014 at 01:20:20PM +0200, Thomas Schmitt wrote: Hi, I may provide you access to a shell account on my machines if needed. Yes, please. Plus a directory tree ./tmp/miniiso/cd_tree which can cause the xorriso crash. Sparc architecture is extremely picky about alignement. Bad alignement, yields SIGSEGV whereas intel only do it in the less efficient way. I would suspect the habit of my libisofs predecessor developer to use structs as access frame for byte arrays read from file. But why then was it possible to produce debian-7.4.0-sparc-netinst.iso by xorriso-1.2.6 as can be read from its Preparer Id: XORRISO-1.2.6 2013.01.08.103001, LIBISOBURN-1.2.6, LIBISOFS-1.2.6, LIBBURN-1.2.6 Does debian-cd pull sparc trees onto a non-sparc machine ? Yes. We build all the release images on an amd64 machine, pettersson.d.o -- Steve McIntyre, Cambridge, UK.st...@einval.com The problem with defending the purity of the English language is that English is about as pure as a cribhouse whore. We don't just borrow words; on occasion, English has pursued other languages down alleyways to beat them unconscious and rifle their pockets for new vocabulary. -- James D. Nicoll -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140428113544.ga30...@einval.com
Re: Potential issues for most ports (Was: Re: Bits from the Release Team (Jessie freeze info))
On Sun, Nov 03, 2013 at 11:54:34AM +0100, Niels Thykier wrote: On 2013-10-29 17:48, Ian Jackson wrote: Niels Thykier writes (Re: Bits from the Release Team (Jessie freeze info)): [...] As mentioned we are debating whether the 5 DDs requirement still makes sense. Would you say that we should abolish the requirement for DD porters completely? I.e. Even if there are no (soon to be) DDs, we should consider the porter requirements fulfilled as long as they are enough active porters behind the port[0]? I don't have a good feel for the answer to that question. It's just that if it is the case that a problem with ports is the lack of specifically DDs, rather than porter effort in general, then sponsorship is an obvious way to solve that problem. If you feel that that's not really the main problem then a criterion which counts porters of any status would be better. I suppose a sponsor-only DD could be sufficient, provided that the sponsor knows the porters well enough to be willing to sign off on e.g. access to porter boxes. I guess the sponsor would also need to dedicate time to mentor (new?) porters on workflows and on quicks like when is a FTBFS RC and when it isn't etc. Why would the sponsor need to be involved in getting the porters access to porter boxes? Porter boxes exist so that DDs *not* involved in a port have access to a machine of the architecture and can keep their packages working. I've never heard of a porter who didn't have access to their own box for porting work. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Help with Wheezy CD testing on Saturday
Hi folks, As we're expecting to release this Saturday (4th May) and I'm going to be preparing the CDs and DVDs to go with the release, it would be lovely if we have some volunteers to help test the images. We have been doing testing of the daily, weekly and Release Candidate images as they're produced, but it would be nice to get more coverage in the testing, especially: * non-PC architectures * more obscure combinations of options like partitioning, filesystems etc. * different desktops with differing package sets I've started a wiki page at https://wiki.debian.org/Teams/DebianCD/ReleaseTesting/Wheezy and I'll be filling in more details there in the next couple of days, including some specific configurations that I'd like to see tested. If you can help us test on Saturday, please take a look and join me in #debian-cd where we'll be coordinating. Cheers, -- Steve McIntyre, Cambridge, UK.st...@einval.com Managing a volunteer open source project is a lot like herding kittens, except the kittens randomly appear and disappear because they have day jobs. -- Matt Mackall -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130502012910.gb28...@einval.com
Bug#673441: gcc-4.6: ICE on sparc while building boost1.49
Package: gcc-4.6 Version: 4.6.3-5 Severity: important The sparc build of boost 1.49 failed recently with a gcc ICE. The compiler output claims the bug is not reproducible (not sure how it would know that?) and may be a hardware or OS problem. Could a sparc person please try a build? gcc.compile.c++ bin.v2/libs/regex/build/gcc-4.6/release/debug-symbols-on/link-static/threading-multi/instances.o g++ -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pedantic -g -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_HAS_ICU=1 -DNDEBUG -I. -I/usr/include -c -o bin.v2/libs/regex/build/gcc-4.6/release/debug-symbols-on/link-static/threading-multi/instances.o libs/regex/build/../src/instances.cpp In file included from ./boost/regex/v4/regex.hpp:166:0, from ./boost/regex.hpp:31, from libs/regex/build/../src/instances.cpp:30: ./boost/regex/v4/regex_split.hpp:168:1: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See file:///usr/share/doc/gcc-4.6/README.Bugs for instructions. The bug is not reproducible, so it is likely a hardware or OS problem. ...failed gcc.compile.c++ bin.v2/libs/regex/build/gcc-4.6/release/debug-symbols-on/link-static/threading-multi/instances.o... -Steve -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120518181305.5677.99052.reportbug@localhost
Re: install net drivers
Dave Miller wrote: From: Jurij Smakov ju...@wooyd.org Date: Mon, 21 Mar 2011 09:26:10 + On Sun, Mar 20, 2011 at 10:05:11PM -0700, David Miller wrote: Please add CONFIG_NIU to the network drivers provided on the network install image. Installations on several Niagara variants is not possible without this. This was reported as http://bugs.debian.org/608516, and is fixed in 6.0.1 images (I've just verified that netinst image contains /lib/modules/2.6.32-5-sparc64/kernel/drivers/net/niu.ko in the nic-modules-2.6.32-5-sparc64-di_1.64+squeeze1_sparc.udeb). That's great. I must have had a 6.0 image. There was also a bug in the script generating the small CDs (such as the netinst) for 6.0.1, meaning you might have seen this problem in a 6.0.1 image. After that was fixed, rebuilt 6.0.1a images have been produced and distributed as replacements. -- Steve McIntyre, Cambridge, UK.st...@einval.com There's no sensation to compare with this Suspended animation, A state of bliss -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1q1d5b-et...@jack.mossbank.org.uk
Re: DSO linking changes for wheezy
On Tue, Nov 16, 2010 at 09:49:08AM +0100, Julien Cristau wrote: On Mon, Nov 15, 2010 at 21:29:07 -0500, Matt Turner wrote: I can't see why you think --as-needed is fundamentally wrong or unnecessary. Check out http://www.gentoo.org/proj/en/qa/asneeded.xml --as-needed has saved tons of time for upgrades like Cairo in Gentoo, where Cairo had been linked to glitz which is now useless and gone. Not a problem, if Cairo was properly exposing the dep. So when people upgraded Cairo, all the software that linked against it (and also unnecessarily linked against glitz) Why did it get linked against glitz? That's where the problem is. I think because -lglitz was in cairo's .pc file. That should be fixed by removing -lglitz from cairo's .pc file, not by passing --as-needed to the linker. I agree with you, -lglitz should never have been listed in the .pc file to begin with. However, *given* that it was there, the default --no-as-needed behavior means that removing libglitz is more painful than it would be otherwise, because instead of just rebuilding cairo itself without glitz, you must rebuild everything above cairo in the stack that used pkg-config for linking. I don't argue that this makes --as-needed *correct* as a default, but I think it's clear how using --as-needed may benefit a distribution in terms of reducing churn when library dependencies change. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101116171440.gf30...@virgil.dodds.net
Seeking machines for nightly builds of ITK
Hi, The insighttoolkit package is a large and active code base. They use a system of nightly build/test on a variety of machines [1] to ensure that the code works on all supported platforms. I run a build on my amd64 machine -- configured as the Debian ITK packages -- to expose issues early. I'd like to add some more Debian machines to cover all the architectures. This issue has some urgency now since ITK is presently embarking on an overhaul of the code that includes removing obsolete code, including support for old compilers systems, such as SGI. I'd like to ensure they don't break compilation for some of the lesser-used machines such as mips, arm, etc. Ideally, I'd like one machine that runs sid of each architecture. I already run the amd64 build. Can I use the official Debian developer machines for this task? If you have a non-amd64 machine with spare cycles each night that you can either set up a build [2] or let me log in to do it, please reply. Thanks, -Steve [1] http://public.kitware.com/dashboard.php?name=itk [2] http://www.itk.org/Wiki/ITK/Git#Dashboard signature.asc Description: Digital signature
Please upload boost-defaults 1.40.0.1
Hi, The latest version of boost-defaults is uploaded on all architectures except sparc. It was built a couple of days ago on buildd_sparc-spontini. Can someone please upload this? I'd like to have some rdeps rebuilt. Thanks, -Steve signature.asc Description: Digital signature
nfs boot of debian on leon/ 32bit-sparc
I'm attempting to boot a debian image located in a remote nfs directory. but I get the following message. Any ideas ? LXT971: Registered new driver Probing GRETH Ethernet Core at 0x8e00 Detected INTEL LXT971A Revision 2 Switching to default initialization 10/100 GRETH Ethermac at [0x8e00] irq 14. Running 100 Mbps full duplex TCP cubic registered IP-Config: Complete: device=eth0, addr=172.24.107.167, mask=255.255.0.0, gw=172.24.100.1, host=lsparky, domain=, nis-domain=(none), bootserver=172.24.106.98, rootserver=172.24.106.98, rootpath= Looking up port of RPC 13/2 on 172.24.106.98 Looking up port of RPC 15/1 on 172.24.106.98 VFS: Mounted root (nfs filesystem) readonly. Freeing unused kernel memory: 116k freed INIT: version 2.86 booting request_module: runaway loop modprobe net-pf-1 modprobe: FATAL: Could not load /lib/modules/2.6.21.1/modules.dep: No such file or directory modprobe: FATAL: Could not load /lib/modules/2.6.21.1/modules.dep: No such file or directory Notice: This e-mail is intended solely for use of the individual or entity to which it is addressed and may contain information that is proprietary, privileged, company confidential and/or exempt from disclosure under applicable law. If the reader is not the intended recipient or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If this communication has been transmitted from a U.S. location it may also contain data subject to the International Traffic in Arms Regulations or U.S. Export Administration Regulations and cannot be disseminated, distributed or copied to foreign nationals, residing in the U.S. or abroad, without the prior approval of the U.S. Department of State or appropriate export licensing authority. If you have received this communication in error, please notify the sender by reply e-mail or collect telephone call and delete or destroy all copies of this e-mail message, any physical copies made of this e-mail message and/or any file attachment(s). -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: free(): invalid nextd size?
On Mon, Sep 22, 2008 at 10:55:02AM +0200, Martin Zobel-Helas wrote: On Mon Sep 22, 2008 at 02:41:06 -0500, Steven Robbins wrote: The Sparc Buildd failed to build ITK [1], aparently because the build takes too long (see below). Or does the first line indicate something more nefarious? Would the buildd owner please re-try ITK? it could be a problem with the processort (being Ultra III). I will requeue on spontini, which is a Ultra II Thanks. It's been 8 days or so, with no sign of a sparc build. Any idea when we could expect one? Regards, -Steve signature.asc Description: Digital signature
RE: Netra X1 install problem/oddity
I've still got a few Netra X1's running. From my notes: First thing after booting the tftpimage jump to a shell and: modprobe -r dmfe modprobe -r tulip modprobe tulip Then you can continue the install. After it reboots to the new system: echo 'blacklist dmfe' /etc/modprobe.d/dmfe-blacklist If all else fails you could track down and delete dmfe.ko but you'd have to remember to do that after every kernel upgrade. The above method worked fine on my production boxes. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
DPL teams review 2008
multiple times where appropriate, once per team, but *excluding* teams for maintenance of individual packages) a. What teams do you work on? Are you an official member of those teams? b. How well do you think those teams are performing, in terms of getting things done? How are daily/regular tasks dealt with? And how about less common, one-off things? c. How do members of your teams communicate with each other about what they're working on? And how do they (as individuals or as a team) communicate with people outside of the team? Do you feel they coordinate well? d. Are there enough resources for your teams to do their jobs well? If not, what's missing? e. Anything else you'd like to mention? 3. Other teams -- a. What contact, if any, do you (as an individual) have with other teams? How well does that contact work? b. How well do your team(s) interact with other teams? c. If you have any issues in (a) or (b), how would you suggest to fix them? d. Any other observations about the various teams in Debian? === Other stuff === That's the list of things I'm hoping to learn more about from this review of teams. Of course, I'm sure there are many other things in Debian that you'd like to ask or tell me about. By all means, talk to me about them - I see it as part of my job to listen and do what I can to help. But please keep those separate from this survey - it'll help me to avoid my head exploding in all directions... :-) -- Steve McIntyre, Debian Project Leader [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: AW: [sun]debian
On Thursday 14 June 2007 01:25, Jurzitza, Dieter wrote: Hi folks, in case of U60 I can only confirm what Steve said, U60 is a great box for installing Debian. To connect a normal PC-Style monitor to your system you might want to consider a Raritan Sun VGA-Converter 13W3- D-Sub 15. Saves lots of headaches (though you won't get it for free). It is called Adapter:1395. Hope this helps, take care Good day, Dieter's suggestion is a good extra option. I've also been able to use 13W3-to-HD15 adapters to make PC multisync monitors work on Suns. This was painful until I learned to set the Sun video card's resolution to 1024x768 at a 70-76 Hz refresh rate before trying the PC monitor. The Suns were sending a video resolution (1120x900 at over 75 Hz refresh?) that was outside the syncing capability of every HD15 multisync monitor I had. -- SP Dieter -Ursprüngliche Nachricht- Von: Steve Pacenka [mailto:[EMAIL PROTECTED] Gesendet: Do 14.06.2007 02:59 An: debian-sparc@lists.debian.org Cc: Betreff: Re: [sun]debian On Wednesday 06 June 2007 05:23, Eric Rapilly wrote: I have some questions, may be you wille be able to answer me. I will * *** Harman Becker Automotive Systems GmbH Geschaeftsfuehrung: Dr. Peter Geiselhart - Michael Mauser - William S. Palin - Edwin Summers - Regis Baudot Sitz der Gesellschaft: Karlsbad - Registergericht: Mannheim HRB 361395 *** Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und loeschen Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the contents in this e-mail is strictly forbidden. ***
Re: X server fails to start after netinstall of Etch on Ultra 60
I finally solved the problem, thanks to the help of those who responded. I am running kernel version 2.6.18, and I installed afbinit using: apt-get install afbinit. Unfortunately, the version of afbinit I got was 1.0-1, and the bug fix is in the newer version 1.0-1.1, for which there does not appear to be a .deb package. I had to download the source code for version 1.0-1.1 from ftp.debian.org and compile it. My X server starts now. Evidently, you must have afbinit version 1.0-1.1 to make it work. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X server fails to start after netinstall of Etch on Ultra 60
On May 28, 8:00 am, Florian Zagler [EMAIL PROTECTED] wrote: On Sonntag, 27. Mai 2007 01:21, Steve Jones wrote: I managed to find afb.ucode on the Sunsolve website (in the 106144-28.zip patch file, dated 21Feb2003), and I placed it in /usr/ lib. Now, when the afbinit command runs I get the following error message: mmap user regs: Invalid argument The X server still fails to start. Also, in my /var/log/Xorg.0.log I have the following: (II) /dev/fb0: AFB: Detected Elite3D/M6. (II) /dev/fb0: BT498 (PAC2) ramdac detected (II) /dev/fb0: Detected Elite3D M3/M6, checking firmware... (II) /dev/fb0: ... AFB firmware not loaded (WW) /dev/fb0: Forcing no acceleration on Elite3D M3/M6 (==) SUNFFB(0): Backing store disabled (==) SUNFFB(0): Silken mouse enabled (**) Option dpms (**) SUNFFB(0): DPMS enabled (**) SUNFFB(0): DPMS enabled (WW) SUNFFB(0): Option UseFBDev is not used What concerns me most from the above is the AFB firmware not loaded message, although I don't know what to do about it. Did you try to load the firmware manually with the command /usr/sbin/afbinit /dev/fb0 /usr/lib/afb.ucode ? After that try to start the xserver with startx. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Yes, I should have mentioned that I did try running that command manually, and I got the same error message: mmap user regs: Invalid argument I just now tried running startx immediately after manually entering the command, but that failed to work. I don't understand the error message, and that may be the key to solving the problem. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X server fails to start after netinstall of Etch on Ultra 60
On May 28, 12:30 pm, Ulrich Teichert [EMAIL PROTECTED] wrote: Hi, [del] Did you try to load the firmware manually with the command /usr/sbin/afbinit /dev/fb0 /usr/lib/afb.ucode ? After that try to start the xserver with startx. [del] Yes, I should have mentioned that I did try running that command manually, and I got the same error message: mmap user regs: Invalid argument [del] Some, maybe silly, questions: 1. Are you root when you're running afbinit? 2. Does /dev/fb0 exist? 3. Does it point to the right card? HTH, Uli -- Dipl. Inf. Ulrich Teichert|e-mail: [EMAIL PROTECTED] Stormweg 24 |listening to: Channel 13 Is Haunted (Hex Dispensers) 24539 Neumuenster, Germany|Adrenalin (Supabond), Ne Me Touch Pas (Opération S) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Thank you for the silly questions. I value those just as highly as the others. 1. Yes, I always run afbinit as root. 2. Yes, I know /dev/fb0 exists because when I 'ls -l' on it, I get: crw-rw 1 root video 29, 0 2007-05-28 14:46 /dev/fb0 3. I don't know for sure; however there is no other 'fb...' in /dev, and there is nothing else in /dev that belongs to the 'video' group. I have only one graphics card (I double-checked), and Debian reports finding an Elite3D card, so I am assuming /dev/fb0 points to the right card.
Re: X server fails to start after netinstall of Etch on Ultra 60
On May 26, 4:10 pm, Florian Zagler [EMAIL PROTECTED] wrote: On Samstag, 26. Mai 2007 04:12, Steve Jones wrote: I did a fresh netinstall of Etch on my Ultra 60 with Elite3D graphics and 21 Sun CRT monitor. All worked well when I did this on a PC using the same Sun monitor. However, on the Ultra 60 the X server fails to start. The installation program seems to have detected the graphics card correctly. Below is an excerpt from my /etc/X11/xorg.conf. The Monitor section is identical on the PC, except on the PC the HorizSync and VertRefresh lines are absent. Can anyone advise me on how to get the X server working? You have to install the package afbinit and you need the firmware for the Elite3D. This file is called afb.ucode. You find it on the Solaris DVD or maybe on the net. The startscript supplied with afbinit may work or not. In my case I had to add the following line to /etc/rc.local to get the card working. /usr/sbin/afbinit /dev/fb0 /usr/lib/afb.ucode -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] I managed to find afb.ucode on the Sunsolve website (in the 106144-28.zip patch file, dated 21Feb2003), and I placed it in /usr/ lib. Now, when the afbinit command runs I get the following error message: mmap user regs: Invalid argument The X server still fails to start. Also, in my /var/log/Xorg.0.log I have the following: (II) /dev/fb0: AFB: Detected Elite3D/M6. (II) /dev/fb0: BT498 (PAC2) ramdac detected (II) /dev/fb0: Detected Elite3D M3/M6, checking firmware... (II) /dev/fb0: ... AFB firmware not loaded (WW) /dev/fb0: Forcing no acceleration on Elite3D M3/M6 (==) SUNFFB(0): Backing store disabled (==) SUNFFB(0): Silken mouse enabled (**) Option dpms (**) SUNFFB(0): DPMS enabled (**) SUNFFB(0): DPMS enabled (WW) SUNFFB(0): Option UseFBDev is not used What concerns me most from the above is the AFB firmware not loaded message, although I don't know what to do about it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
X server fails to start after netinstall of Etch on Ultra 60
I did a fresh netinstall of Etch on my Ultra 60 with Elite3D graphics and 21 Sun CRT monitor. All worked well when I did this on a PC using the same Sun monitor. However, on the Ultra 60 the X server fails to start. The installation program seems to have detected the graphics card correctly. Below is an excerpt from my /etc/X11/xorg.conf. The Monitor section is identical on the PC, except on the PC the HorizSync and VertRefresh lines are absent. Can anyone advise me on how to get the X server working? Section Device Identifier Sun Elite3D framebuffer or similar (SUNW,XXX- ) Driver sunffb Option UseFBDev true EndSection Section Monitor Identifier Generic Monitor Option DPMS HorizSync 28-51 VertRefresh 43-60 EndSection -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [SECURITY] [DSA 1294-1] New xfree86 packages fix several vulnerabilities
On Fri, May 18, 2007 at 11:07:52AM +0200, Josip Rodin wrote: Anyway, as far as getting something done, I would suggest opening an RT ticket and documenting in that ticket: [...] I did that now, thanks. I combined two sets of information in it - the specific details about this sparc machine that I sent to the mailing list, and general information about the location which I had already provided to DSA in an offer to host that other machine that they put out a few years ago. Looks good to me, thanks! If DSA has to go fishing for these details, chances are good that they /won't/ do so, because there are always fires going on that will take priority. I appreciate you being courteous to spell this out, but it's a problem in itself if one has to make these justifications... If as you say that our only sparc buildd is MIA for two weeks and not fixed yet, what greater fire is there, taking priority thoughout this time? Problems worse than two-week downtimes should probably make us all pretty scared... Uh, auric is not the only sparc buildd, it's just the only one configured for building oldstable-security (apparently). spontini is still up and building just fine for other suites, so if and when DSA decides they need to go for plan B wrt auric's downtime, getting oldstable-security set up on spontini would still be a quicker fix than provisioning a whole new buildd from scratch. As for problems worse than a two-week downtime, well, there's the 1.5-month downtime of goedel (alpha buildd redundancy), the one-month downtime of four of the arm buildds because of what may be an incompatibility between their kernel and sid's glibc, the three-day downtime of the only running i386 buildd... though when I mentioned fires, I was including auric itself in that reckoning. ;) Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Scheduling linux-2.6 2.6.21-[23]
\On Fri, May 18, 2007 at 05:42:21PM +0200, Bastian Blank wrote: On Fri, May 18, 2007 at 12:18:57PM +0200, Bastian Blank wrote: I'd like to schedule the linux-2.6 2.6.21-[23] upload for today. I'll disable sparc32 and all hppa images. - sparc32: see the other discussion. Ok, this seems to have Jurij's consent at least in principle. But this: - hppa: broken toolchain which makes it impossible to build them and we need linux-libc-dev. What is so urgent about linux-libc-dev that you need to break what wasn't broken before? glibc still depends on l-l-d | l-k-h, and almost all of the buildds still have l-k-h installed rather than l-l-d; but this change to disable hppa image building *ensures* that 2.6.21-2 is not releasable (is not suitable for testing), where 2.6.21-1 might have built just fine once the hppa toolchain was fixed. In the case of alpha, despite my irritation at having to revert this change from the trunk before *beginning* to test 2.6.21 builds, at least there was a kernel bug that needed to be fixed. But hppa's bug is in the toolchain, not in the kernel -- so this is certainly a regression, and once again it doesn't look like the hppa porters were even consulted before the change was made (firing off a notice to debian-hppa 5 hours before uploading is not consultation). -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [SECURITY] [DSA 1294-1] New xfree86 packages fix several vulnerabilities
On Fri, May 18, 2007 at 12:39:50AM +0200, Josip Rodin wrote: On Thu, May 17, 2007 at 11:22:02PM +0200, Moritz Muehlenhoff wrote: Debian Security Advisory DSA 1294-1[EMAIL PROTECTED] This update lacks builds for the Sparc architecture, due to problems on the build host. Packages will be released once this problem has been resolved. I am repeating my request to donate and host a sparc machine for Debian. (Details are in my previous mails to debian-sparc, but I will repeat if someone forgot or can't find.) It's been ready and waiting for a few weeks. At the same time, vore.d.o is long dead, spontini.d.o is in lockdown, auric.d.o is operational but restricted, and schulz.d.o has been in state 'setup' for weeks. http://buildd.debian.org/stats/graph2-week-big.png indicates some fluctuation, with a recent downturn for sparc buildds. I'm Cc:ing the security team and members of the wb-sparc group on Debian machines. What else needs to happen to get something done about this? Well, I'm only cc'ed on this because I have access to manipulate the buildd queues, but I would note that the reason sparc is late for this update is that auric has gone out to la-la land (hasn't been seen by w-b since May 3). So I imagine that setting up a new buildd from scratch is less of a priority right now than trying to get back the one that we already had configured. Anyway, as far as getting something done, I would suggest opening an RT ticket and documenting in that ticket: - hardware details of the hosting offer - bandwidth availability - any network security policies that may affect DSA access, or the purpose to which the machine can be put - local admin availability / expertise - *long-term outlook* for the hosting offer (e.g., I'm a senior exec with $org and have complete autonomy to decide to host this; or I've been with $org for $x years and have no plans to leave in the next $y years, and this hosting offer will be valid as long as I'm here; or Debian has 90% mindshare within $org and is enthusiastic about supporting the Debian Sparc port because we use it for $foo; vs. yeah, we've got a box we're not using and we don't need the rack space /yet/, so can you guys use it for the next month or two?) If DSA has to go fishing for these details, chances are good that they /won't/ do so, because there are always fires going on that will take priority. OTOH, if you present all of the salient information up front and the hosting offer stands on its own, it will be a lot easier for DSA to evaluate it compared with other hosting offers (and current hosting) and it should be a bit easier to get a yay/nay on whether DSA thinks it's a machine the project needs... Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New to Sparc Debian
On Monday 02 October 2006 10:03, Simon Tyler wrote: Hi all, I will be brand new to Debian (been a suse man of late). However, I have aquired an ultra 60 and wondered what anyone thought of Debian running on this machine and if you have any advise before I trash it. A U60, especially one with dual CPUs, is a great machine for Debian Linux. I've used one for a couple of years with very few software problems and with excellent driver compatibility. I'm readying a second one to replace an old X86-platform Debian server in my office. I use the earlier one dual headed, with Creator and Elite framebuffers, a couple of large (surplus) hard drives, a USB2 PCI card, an internal DVD-ROM drive, and wide or narrow SCSI externals. Currently it has an Ensoniq Audio PCI card. USB2 peripherals such as DVD burners, scanners, and hard drives have worked too. About the only thing I've ever had software problems with is onboard audio. I just drop in a cheap PCI card (currently Audio PCI, earlier a Yamaha YM744 card). Enjoy! -- SP Thanks in advance Si Regards Simon Tyler Lead Design Engineer Centurion Electronics PLC Satellite House Welwyn Garden City Herts AL7 1LY Tel: 01707 330550 Fax 01707 330866 Ext. 187 Email: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problem with resolution on ultra 5
On Saturday 19 August 2006 10:55, Steve Pacenka wrote: On Friday 18 August 2006 15:59, zagi wrote: Hi, I installed Debian Sarge on my ultra 5. It has ATI Technologies, Inc. 3D Rage I/II 215GT [Mach64 GT] graphic card. Max resolution that I can set in XF86Config-4 800x600. If I set any higher resolution Xserver will not start. It's possible that you have the earlier U5/10 motherboard that has 2M VRAM; later ones have 4M. 2M VRAM is not enough to support more than 800x600 at 24 bits. Cut back to 15 or 16 bits depth and you can get to at least 1024x768, and possibly to 1280x1024. My reply was not completely right. Of course 1280x1024 will only work at 8 bits depth within 2M VRAM ... The ATI Rage chipset supports other resolutions; perhaps 1152x900 or 1280x800 will work at 15/16 bits. See the Sparc Framebuffer FAQ. -- SP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: problem with resolution on ultra 5
On Friday 18 August 2006 15:59, zagi wrote: Hi, I installed Debian Sarge on my ultra 5. It has ATI Technologies, Inc. 3D Rage I/II 215GT [Mach64 GT] graphic card. Max resolution that I can set in XF86Config-4 800x600. If I set any higher resolution Xserver will not start. It's possible that you have the earlier U5/10 motherboard that has 2M VRAM; later ones have 4M. 2M VRAM is not enough to support more than 800x600 at 24 bits. Cut back to 15 or 16 bits depth and you can get to at least 1024x768, and possibly to 1280x1024. -- SP In log there is: (!!) ATI(0): Virtual resolutions will be limited to 2047 kB due to linear aperture size and/or placement of hardware cursor image area. (II) ATI(0): Using Block 0 MMIO aperture at 0xE0008400. (II) ATI(0): Using Block 1 MMIO aperture at 0xE0008000. (II) ATI(0): MMIO write caching enabled. (--) ATI(0): 2048 kB of SGRAM (1:1) detected (using 2047 kB). (WW) ATI(0): Cannot shadow an accelerated frame buffer. Anyone had this problem? /cheers, Zagi -- View this message in context: http://www.nabble.com/problem-with-resolution-on-ultra-5-tf2129290.html#a58 76559 Sent from the debian-sparc forum at Nabble.com. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sun UltraSPARCIIi Ultra 5 mouse not working
On Sunday 13 August 2006 22:18, SnarfPad wrote: Hi, I have a Sun UltraSPARCIIi 400mhz Ultra 5 desktop and after installing Sarge with mouse auto-detect options, the sun mouse attached to the keyboard doesnt work, also, a microsoft-compatible serial mouse attached wont work either, even after running xf86config and selecting auto for the mouse. If there a fix? For XFree86 and kernel 2.4, a Sun mouse appears at /dev/sunmouse, and with kernel 2.6 it appears at /dev/psaux . Protocol should be set to busmouse and ImPS/2 for the respective kernels. You'll probably have to edit these in by hand to the /etc/X11/X*.conf file. The M$ mouse probably should show up at /dev/ttyS0 or /dev/ttyS1 , depending on which port the mouse is attached to. -- SP Thanks! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: xorg lockup on ultra 5
On Tuesday 18 July 2006 04:26, Robert Lemmen wrote: hi folks, i got an ultra 5 that i recently upgraded from stable to testing, now X doesn't work anmore. i followed the instructions on the XorgOnSparc page of the wiki, everything went fine so far. if i do a startx, the screen goes blank, the machine emits a continuous beep and locks up hard. no keypressing makes it switch to console or kill the xserver. i can't say for sure how hard it actually locks up as i have no other computer around to check over the network, but if i redirect stdout and stderr to a file, i find nothing on the disc after the reboot (btw: the beeping doesn't happen if i redirect the oputput). the graphics card is an ATI Technologies Inc 3D Rage Pro 215GP (rev 5c) (lspci), xorg is at version 7.0.22 and the kernel (if that is of any interest) is a 2.6.7 (self-compiled from upstream sources). the xorg.conf is attached, the bits that are commented out are stuff i tried, the problem also appears with them in. has anybody seen this before? any pointers? hints where i could lokk? what i could try? I've almost never had an X lockup on an Ultra 5 or 10 in a couple of years of use with kernels 2.4 and 2.6. A U10 I have working 24/7 has exactly the same PCI report as yours. Most of my Debian on this box is Etch, with a sprinkling of Sid. I have had problems with earlier 2.6 kernels on other Ultras, and recently had a problem with Etch and 2.6.16 (probably unrelated to Xorg) that was solved by upgrading to Debian's kernel 2.6.17-1-sparc64 in Sid. The following things in your xorg.conf are suboptimal or nonworking (when used with recent 2.6 kernels), though I doubt if any would cause a hard lockup. 1. With a 2.6 kernel and a Sun type 5 serial keyboard the keyboard rules and model should be xorg and pc105, not sun and type5. 2. With a 2.6 kernel the Sun serial mouse device should be /dev/psaux not /dev/sunmouse. 3. I use a 15 bit depth rather than 16. As far as I know the graphic chipset supports 8, 15, 16, and 24. 4. I do use the dri module (in Xorg 6.9). -- good luck, SP thanks robert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ultra2 ... stuff
On Monday 17 July 2006 16:40, Kevin Diggs wrote: Hi, I finally stumbled around and got X working on this thing. I had to use sunffb as the device, set the mouse device to /dev/sunmouse, and change the protocol to MouseSystems. How do I get the resolution up to 1280x1024? Got a modeline, anyone? The resolution should be set in openboot to something supported by your monitor, as a value of the output-device variable. Here's a concise statement of how to do it http://www.sunhelp.org/faq/FrameBuffer.html#2a -- SP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFC: xorg configuration generation on sparc
On Friday 14 July 2006 01:18, Jurij Smakov wrote: * cfb and cfb32 modules are loaded by default on sparc. Currently sunffb driver (probably most common) depends on symbols from these modules. sunffb is also made a default driver, in case detection fails. I unfortunately can't test the variant xserver-xorg package until 7/23. Is sunffb (UPA in U30, U60, U2, U1?) really most common among Linux users, or is ati (blades, U5, U10, some PCI cards)? In both cases the new detection logic should find the right type. With all of these Tuxes visible at boot, it's a shame we can't use fbdev as a fallback. Does this actually work on any Sparc? Why not make an unrecognized framebuffer fail the install and provide a pointer to a manual process? People encountering the failure could be asked to post a Debian bug against xserver-xorg (or against xserver-xorg-video-sunffb to narrow it down to the platform) and provide a prtconf transcript. -- SP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X on ultra sparc 30
On Thursday 13 July 2006 17:33, Jeffrey Maples wrote: have a Sun Ultra 30 creator with a strange graphics card. I have been head over heals trying to figure out what it is. I have taken it out, and found nothing on it that tells me what chipset it is. I have successfully installed debian-sparc on this machine, but No matter what I do, when I try to start X it gives me the no screens found error. I tried this on generic vesa, vga, and fbdev drivers. Jeff, I assume you have console video working. Here are several things you can do. 1. There is a line in your dmesg kernel boot log that says what kind of video was detected. It will probably include the string afb or ffb and usually fb0. What does dmesg |grep fb say? 2. If the card is a full-length card that goes into a non-PCI slot, it should be either a Creator or Elite card. Both use the same Xfree or Xorg driver, sunffb. 3. Does your case say either Elite or Creator on it? (I've never seen an Ultra 30; my two Ultra 60's have Elite and Creator emblazoned on their front panels.) If you do have a Creator or Elite, what you do next depends on the Debian release. For Etch (Testing) or Sid (unstable), you will need to install the Debian Sid package called xserver-xorg-video-sunffb. Then edit your xorg.conf. If you're using Debian Sarge, the sunffb driver is part of xserver-xfree86 and you only need to edit your XF86Config.conf to say sunffb where you stuck fbdev etc. If your card is an Elite 3D one, you'll also need to install the afbinit package. That further requires a bit of non-distributable binary firmware from Solaris, that the afbinit documentation describes. With my luck you have a Sun PCI video card and the above will have been a waste :^) I have no idea how to go into the cmos, (if there is such a thing) on this sparc station. Press Stop and a at the same time, before the kernel starts booting. On a machine with a working X :^), Google for sun openboot for syntax. This is the first sparc ive ever dealt with. I know linux/ubuntu quite well on x86 and ppc machines. I have searched the net up and down, and can't find anything pertaining to my problem. Is this something that is supposed to work? or not? Any help would be appreciated. It's supposed to work, but it usually hasn't on Sparcs. There's a Debian Wiki xorg-on-sparc page established by Jurij Smakov to help with this config, and Jurij is right now trying to improve autodetection. (See his 7/7 message xorg hardware detection - please test on this mailing list.) Once you get your own config working, please consider entering your parameters on the Wiki page. -- good luck, SP Thanks in advance, Jeff [image: Edit/Delete Message]http://www.ubuntuforums.org/editpost.php?do=editpostp=1247918 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: xorg hardware detection - please test
On Saturday 08 July 2006 01:31, Jurij Smakov wrote: On Fri, 7 Jul 2006, Dirk Dettmann wrote: Am Freitag, 7. Juli 2006 08:45 schrieb Jurij Smakov: Hi Jurij, I've hacked together a script (attached) which parses prtconf output and outputs the name of corresponding xorg driver you should include SUNW,afb for the Elite 3D in your script. Hi Dirk and Dieter, It looks like both of you have the Elite 3D cards. The correct driver, I believe, is sunffb. What I'm not sure about is whether one needs to use afbinit to initialize the cards. Does it work with recent kernels? Can you run xorg successfully on these cards? sunffb is the correct xorg driver for Elite 3D and Creator 3D. afbinit is necessary for Elite 3D but not for Creator 3D. Empirical answers for two U60's: dual head, one of each card, kernel 2.6.16-1-sparc64-smp, xorg 6.9: okay (afbinit hard-locked with 2.6.17-1-sparc64-smp, needed a power cycle) single head, elite 3d, kernel 2.6.16-1-sparc64-smp, xorg 7.0: okay -- SP Best regards, Jurij Smakov[EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: xorg hardware detection - please test
On Friday 07 July 2006 02:45, Jurij Smakov wrote: Hi, I've hacked together a script (attached) which parses prtconf output and outputs the name of corresponding xorg driver. I've only included the information which I could find on my own machines and prtconf examples. Please test it on your box (you'll need prtconf from sparc-utils and awk). If you will get no output (which means that the script failed to detect any cards) or 'unknown' (found a card, but failed to map it to the driver), please submit output of prtconf -p -v on your machine as well as information about which xorg driver is appropriate for it. Thanks for your work on this. The script works okay on an Ultra 10, detecting onboard ati. One of my U60's has an afb (creator) and ffb (elite). The script reported unknown since the afb is earlier in the node list and there was no clause for SUNW,afb. To detect Creator 3D video and cg14 (SX framebuffer), add SUNW,afb ) driver='sunffb' ;; SUNW,sx ) driver='suncg14' ;; to the case statement near the end. Running the script triggers a watchdog reset on my SS20, so I could not verify correct operation. (Probably a hardware or kernel problem.) Does prtconf need /proc/openprom to be mounted, and are that mount and the sparc-utils package available during installation? Kernels 2.6 will not require prtconf. U60: /sys/class/graphics/fb0/name = Creator 3D /sys/class/graphics/fb1/name = Elite 3D U10: /sys/class/graphics/fb0/name = ATY Mach64 I would also appreciate information about which keyboard settings are appropriate for what keyboart types, so that we can implement it properly. I have only type5's, and they require an xorg pc105 map with Kernels 2.6. -- SP Best regards, Jurij Smakov[EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: xorg hardware detection - please test
On Saturday 08 July 2006 13:42, Jurij Smakov wrote: One of my U60's has an afb (creator) and ffb (elite). Is it a typo? I believe other people have said that afb (SUNW,afb) is actually the Elite 3D card. You're correct, sorry. afb is Elite, ffb, is Creator. Both use the sunffb xorg driver. I have a 501-4788 which is a Creator 3D FFB2+, listed in prtconf as SUNW,ffb . Empirical answers for two U60's: dual head, one of each card, kernel 2.6.16-1-sparc64-smp, xorg 6.9: okay Cool. Could you send me the xorg.conf file for this configuration? In case anyone else is intererested: http://wri.cfe.cornell.edu/sparc/u60dualhead-xorg69-xorg.conf http://wri.cfe.cornell.edu/sparc/u60dualhead-xorg69-Xorg.0.log (afbinit hard-locked with 2.6.17-1-sparc64-smp, needed a power cycle) Could you please file a bug and try to debug it? At least roughly, which call causes it to hang? You are using the latest afbinit (1.0-1.1), right? I don't really have the experience to debug hard locks. There were no messages to console, just a freeze with a dead keyboard (not even Stop-A would work). The afbinit installed now is 1.0-1.1; this lockup was a few weeks ago. -- SP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X.org and kernel problems on SunBlade 100
On Wednesday 05 July 2006 10:33, Daniel Liikamaa wrote: I've managed to install Debian etch on my SunBlade 100, but now I can't get X to work properly. I've set the resolution to 1600x1200 in xorg.conf, but when I start X, the resolution is set do 320x240 or something like that, it's not pretty. The only error message I get is Module mach64 not found, when it tries to load a kernel module (?!). The graphics card is an ATI Rage XL, the standard card for these machines. How can I get it to show decent resolutions? That rings a bell. I assume you're using Xorg 7.0. Did you end up with xserver-xorg-video-ati installed? (That one is not missing from Etch, unlike sunffb sunleo et al.) If not, apt-get install it. The X server should not trigger loading of kernel modules; it does load its own driver modules. Here is a working xorg.conf for an Ultra 5's onboard video, which also uses the ati driver: http://wri.cfe.cornell.edu/sparc/u5-xorg7-xorg.conf Also, to make the Type6 USB keyboard work properly in X, do I have patch the source and then compile x.org by myself? This is the only solution I've come across when googleing. Does your keyboard work without X? If it does, the kernel should be able to supply X with the right keycodes. Kernels 2.6.x remap all non-PC keyboards to PC types. A type 5 keyboard turns out to map to pc105 (who would've thunk it?). You could try the xorg keyboard section in my xorg.conf for U5. My xorg.conf file is generated with the Xorg -configure command. I don't think I've ever had that generate a completely working conf for any Sparc. My xorg.conf was generated via the deb installation (except for the keyboard section). Did you try: dpkg-reconfigure xserver-xorg -- SP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Xorg 7 on sparc64
On Tuesday 20 June 2006 11:30, Stuart Brady wrote: On Mon, Jun 19, 2006 at 11:02:56PM -0400, Steve Pacenka wrote: After installing xserver.xorg, the generated xorg.conf file was good for ATI video. It needed a keyboard touchup to use the correct map (sun(type5) instead of sun) and I don't yet have Ctrl-Alt-Fn key switching among vts. It assumed a low performance monitor. That's odd. I'm using pc105, and it works. The input layer in Linux 2.6 convert to the PC scancodes now. Are you sure xorg isn't just using default rules? I accepted the defaults presented by xserver-xorg's bare metal setup, which for $ARCH = sparc is XkbRules = sun and XkbModel = type5. I'm incorrect about using XkbRules = sun(type5). That may be correct for kernel 2.4 but it is wrong for 2.6. The correct values when using a type 5 keyboard and kernel 2.6 are XkbRules = xorg and XkbModel = pc105. Welcome back Ctrl-Alt-Fn. (These same values worked with 6.9, so upgraders may not be affected by the suboptimal Debian config script in xserver-org.) The problem is that xserver-xorg's Debian config script sets poor default keyboard rules for Sparc kernel 2.6. It uses (excuse pidgin shell) if architecture is sparc default XkbRules = sun else default XkbRules = xorg fi It could improve its defaults for Sparc and for non-Sparc 2.4 kernel users by if kernel = 2.4 case architecture sparc) Xkbrules = sun someotherarchitecture) XkbRules = otherarcpopularkeyboard *) Xkbrules = xorg esac else Xkbrules = xorg fi -- thanks, SP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Xorg 7 on sparc64
On Tuesday 20 June 2006 10:42, Martin Marques wrote: On Sat, 17 Jun 2006, Jurij Smakov wrote: Just to reconfirm: I've just reinstalled my Ultra5, updated it to the latest sid and installed xorg. The xorg.conf file it generates during installation is indeed broken, as it uses fbdev driver. The machine hangs solid when an attempt is made to do startx with this xorg.conf (bad!). Changing the driver to ati makes everything work nicely though. Versions of installed packages: xorg7.0.22 xserver-xorg-core 1.0.2-8 xserver-xorg-video-ati 6.5.8.0-1 The actual xorg.conf used and the log of the server starting up are available at http://www.wooyd.org/debian/xorg/xorg.conf-ultra5-ati http://www.wooyd.org/debian/xorg/xorg.log-ultra5-ati OK, I'm having some trouble with Xorg. I followed the procedure, installed the exact versions mentioned above, and X doesn't start. Martín, My fresh Ultra 5 config and log, for working video, keyboard, and mouse are at http://wri.cfe.cornell.edu/sparc/u5-xorg7-xorg.conf http://wri.cfe.cornell.edu/sparc/u5-xorg7-Xorg.0.log What are the diffs between your and my xorg.conf? Now, first of all I found that there is no x_accel module, so I added the line Option no_accel true. That remove this error: (WW) INVALID IO ALLOCATION b: 0x2c00400 e: 0x2c004ff correcting^G (EE) /usr/lib/xorg/modules/libxaa.so is an unrecognized module type (EE) ATI: Failed to load module xaa (unknown module type, 6) I get the WW warning. libxaa.so loads for me. But after that I got this error: (EE) /usr/lib/xorg/modules/libshadowfb.so is an unrecognized module type (EE) ATI: Failed to load module shadowfb (unknown module type, 6) I get cannot shadow an accelerated frame buffer. Both of the failing modules are part of the xserver-xorg-core package. Perhaps that package did not unpack properly or there is some disk corruption. (I've had some corruption on an IDE drive in an Ultra 10.) Did you try reinstalling that package via apt-get --reinstall install xserver-xorg-core The problem is that I can't set the frambuffer to off. My Console works with frame buffer, and I have been unlucky setting FB off in silo.conf: image=/boot/vmlinuz-2.6.17-rc3-sparc64 label=linux2.6.17 root=/dev/hda1 initrd=/boot/initrd.img-2.6.17-rc3-sparc64 append=video=sbusfb:off read-only Why does the framebuffer need to be turned off? atyfb is the kernel driver for the framebuffer in an Ultra 5. The full output from X is: Your /var/log/Xorg.0.log would be much more informative. Email it to me if you don't want to post it due to length. -- SP
anyone have a working initrd for sparc32 kernel 2.6.x?
I'm getting interrupt 15's (usually a memory error?) on a SS20 when loading initrds made on my box when trying 2.6.8 from Sarge and 2.6.17 from Sid. silo 1.4.11. For 2.6.17, I've been trying initramfs (klibc and klibc-utils from Sid as of yesterday) since mkinitrd.yaird wants a running 2.6. The initramfs version completes without messages. Any initrds or hints about coping with interrupt 15 bailouts while silo is loading? -- thanks, SP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Xorg 7 on sparc64
On Saturday 17 June 2006 16:46, Jurij Smakov wrote: Just to reconfirm: I've just reinstalled my Ultra5, updated it to the latest sid and installed xorg. The xorg.conf file it generates during installation is indeed broken, as it uses fbdev driver. The machine hangs solid when an attempt is made to do startx with this xorg.conf (bad!). Changing the driver to ati makes everything work nicely though. Versions of installed packages: xorg 7.0.22 xserver-xorg-core 1.0.2-8 xserver-xorg-video-ati6.5.8.0-1 I just finished a fresh U5 (w/4M VRAM) install of Etch; kernel 2.6.15-1. The ati Xorg 7.0 driver works without incident at 1024x768 in 24 bits. After installing xserver.xorg, the generated xorg.conf file was good for ATI video. It needed a keyboard touchup to use the correct map (sun(type5) instead of sun) and I don't yet have Ctrl-Alt-Fn key switching among vts. It assumed a low performance monitor. This is pretty good for a generated x*.conf file under Sparc, so I'd call this a success. The three packages cited above all have the same versions in my installation. Promising! -- SP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Xorg 7 on sparc64
On Saturday 17 June 2006 18:37, Martin Marques wrote: On Sat, 17 Jun 2006 22:56:46 +0200, Frans Pop [EMAIL PROTECTED] wrote: There is also: Bug#368214: Wrong keyboard configured for Sparc with 2.6 kernels And of course the recent: Bug#373821: Unavailable xserver-xorg-video-sun* necessary for many Sparc Which SPARC need these packages? Any Sparc32 (sunbw2, suntcx, suncg14, suncg3, suncg6) except Javastation, Sparc64 with Creator or Elite framebuffers (sunffb). -- SP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Xorg 7 on sparc64
On Thursday 15 June 2006 00:33, Jurij Smakov wrote: On Wed, 14 Jun 2006, Steve Pacenka wrote: I would hesitate to try Xorg 7 from Debian Sparc repositories except when thee is no alternative, i.e. bare metal. Working pre-7 versions have disappeared from Testing so there is no easy way to revert if 7.0 is broken. A definite mass breakage is that neither Testing nor Sid contains any of the xserver-xorg-video-sun* packages that provide drivers for ffb, tgx, leo, etc. Are those drivers available upstream and are not available as packages purely due to faulty packaging? Has this problem been brought to the attention of XSF in any way? According to David Nusinow of XSF, these drivers need a maintainer. He lacks hardware for testing. Source is in the XSF subversion repository. I've offered an Ultra 2, which may need memory if my scrounging does not succeed. I'm willing to be a tester for drivers of what I keep running in noncritical roles, which is Creator3D, Elite3D, cg14, and onboard ATI in U5/10. I'll try to build the unavailable packages and my own version of the xserver-xorg-video-ati package using XSF subversion sources. No promises about results or earliness. -- SP Best regards, Jurij Smakov[EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Xorg 7 on sparc64
On Tuesday 13 June 2006 14:38, Ludovic Courtès wrote: Has anybody else tried Xorg 7.0 on an Ultra 5 (or similar) with an ATI 3D Rage Pro? Or am I the only one experiencing problems? The wiki page [0] currently only shows Jurij's success with an ATI board and a failure with a Raptor board. At least, this proves that I can live without X. ;-) I would hesitate to try Xorg 7 from Debian Sparc repositories except when thee is no alternative, i.e. bare metal. Working pre-7 versions have disappeared from Testing so there is no easy way to revert if 7.0 is broken. A definite mass breakage is that neither Testing nor Sid contains any of the xserver-xorg-video-sun* packages that provide drivers for ffb, tgx, leo, etc. A U60 I'm building has no X after a misguided dist-upgrade that wiped out Xorg 6.9, which was working well. -- :^( , SP Thanks, Ludovic. [0] http://wiki.debian.org/XorgOnSparc
Bug#369890: silo: build-depends on gcc-2.95, which may be removed for etch
Package: silo Version: 1.4.11-0.2 Severity: serious The silo bootloader package build-depends on gcc-2.95 at the version currently in unstable, making it the only package of any substance which does so. The gcc-2.95 package itself is RC-buggy, failing to build with the current version of make; since there has been no interest expressed in fixing this bug by the maintainer, the likely outcome is that gcc-2.95 will be dropped from etch, leaving sparc without a releasable bootloader. There are two possible solutions: - silo gets updated to use a more recent compiler, dropping this build-dep - someone adopts gcc-2.95, fixing the FTBFS, and maintaining it for etch X-Debbugs-Cc: to debian-sparc. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Re: Sparc architecture requalification
On Sat, May 20, 2006 at 05:34:08AM +, Aurelien Jarno wrote: It has been a long time since the sparc status on the architecture requalification page [1] has been updated. A few things seems to have changed: - There is now 3 sparc buildds (mrpurply, spontini and auric), so I think the buildd redundancy box could be set to green. Yes, this appears to be correct; I checked with Ryan about this at DebConf, and we do seem to have full redundancy now for sparc buildds. - The kernel failures (that occurs only on SMP boxes) seems to be gone, at least on the build daemons. I don't know what has been done (if somebody know, please tell us), but the two packages that were killing the buildds (ie glibc and openoffice.org) are now building correctly (4 last uploads for the glibc, last upload for openoffice.org). What's been done is to install a kernel which is newer than any that are actually available in sid or etch. The fact that this seems to fix the problem is a positive step in the right direction, but it's not sufficient for the release qual as it leaves us with very low confidence in the usability of the port when we can't use the Debian kernels for etch on any of the relevant project machines.[1] So the ideal solution is that, now that we have a known-working version, someone determines whether 2.6.16 includes the same fixes and if not, gets them backported to 2.6.16 for etch. There is also the question of having appropriate kernel images on the buildds for the remainder of sarge's term as stable, but I don't see any way that this should be a blocker for sparc's inclusion as an etch release arch if the *current* buildd kernel problems don't make sparc unreleasable package-wise. If the kernel failures still appear to be present, would it be possible to qualify the port for non-SMP only? AIUI most of the sparc hardware people want to *use* Debian on is SMP kit, so I think it would be a shame to call a UP port releasable but would certainly take the opinions of the sparc porters into consideration. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ [1] independent of whether DSA actually uses stock Debian kernels on most Debian systems, which TTBOMK is actually not the case signature.asc Description: Digital signature
Re: SS5 install incomplete
On Thursday 11 May 2006 00:21, Dieszel wrote: When doing a network install, I get through the base install and on reboot fails back to openboot prompt (OK) with no explanation. Almost as if not booting to the correct partition. Any suggestions.. Debian version is sarge... I've had that happen on an SS20 with Sarge a couple of years ago. I had two drives. The Sarge installer didn't update the openprom boot-device variable which was left pointing to a drive other than the one where my silo got installed. Your openboot may have aliases for disk, disk1, disk2. Try boot disk1 or boot disk2. -- good luck, SP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
spark video problems
Will a standard PCI video card work with the ultra5? Thanks a lot for all of the wonderful help so far.
sparc video problems
I just purchased a ultra sparc 5 for the first time today. I am a virgin in sparc territory and am completely at a loss. I administrate several debian servers but all of them are x86 based. Well it has a regular looking VGA port on the back but when I hook the monitor up I get no video. Once in a while there will be lines across the screen but thats about it. It does beep so it sounds like it is posting and I can hear hard drive activity, but no video. I have tried changing the resolution using the following commands Stop a Setenv output-device screen:r1024x768x60 Reset But I still get nothingL The person I bought the machine from did include a 13w3 connecter but there is no place to plug the thing in. I know my monitor can easily support the 1024x768x60 resolution so I dont think that is the issue. Any help or ideas would be greatly appreciated.
Re: version of openoffice packages in testing/unstable
On Mon, 2006-03-20 at 10:44 +0100, Dr. Zimmermann wrote: Hi all, does anyone know what anticipates the compilation of newer openoffice packages ? The SPARC version stays at 2.0.0-5 while i386 and PPC versions have been updated to 2.0.1-5 several weeks ago in testing and recently to 2.0.2-1 in unstable. I have meandered through several CVS and Bugreport pages without finding any hint. Roger You should ask on the Debian oo.o list. Perhaps there is a need for more Debian packagers for Sparc oo.o. Going one step upstream, Jim Watson's .tar.bz2 multi-RPM packages are quite usable with Debian (at least as single-user installs). These are available from Openoffice.org mirrors, in the contrib/linuxsparc directory. Jim is up to 2.0.2. You also need to find install_linux.sh for oo.o. Maybe the one here will work: http://ftp.stardiv.de/pub/OpenOffice.org/developer/install_scripts/ For future reference, Jim's port wiki page is: http://wiki.services.openoffice.org/wiki/GNULinuxSparcPorting -- SP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Ultra 10 processor support
On Mon, 2006-03-20 at 14:56 +, Chris Andrew wrote: Hi, all. I have a 333 Ultra 10. I was just wondering whether it is possible to add more processors. I think the max speed processor I can get is 440, but 2 processors (or more) would be good. Any thoughts? Thanks, Chris If you're looking for Linux performance improvements in a U10, your processor is already pretty good. Getting the box up to 512M or 1G memory, or replacing the IDE hard drive with an ultra/wide SCSI one (along with a bootable PCI SCSI controller), could improve speed also, depending on where your bottlenecks are. The internal IDE controller is not very fast, and if you're using a lot of swap due to not having much memory you're paying a double penalty. If your applications would benefit mainly from dual CPUs, and if you don't need PCI, a 2x296 MHz Ultra 2 might be acquirable at a low price. I got one for US$69 once with 256M RAM, Creator graphics card, and CD. -- SP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
am i blacklisted?
Why aren't any of my posts getting through? -Steve P.S. If this gets through, see BTS 352183. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
unsubscribe
unsubscribe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Developer accessible SPARC machine
On Fri, Jan 06, 2006 at 05:13:54PM +1000, Andrew Pollock wrote: On Wed, Jan 04, 2006 at 12:22:57AM -0800, Steve Langasek wrote: Hi Andrew, On Tue, Jan 03, 2006 at 04:35:30PM -0800, Andrew Pollock wrote: I note that one of the issues with the Sparc port is the the lack of a developer accessible machine. At present, vore.debian.org is back on line; the underlying issue, though, seems to be that vore, like the buildds, won't necessarily *stay* on-line due to some hard-to-pin kernel bugs that keep taking the systems down. Anyway, I'm working with Stephen Frost (though working is a bit of an overstatement, he's currently waiting on me) to arrange hosting of a porter system with his employer; the space is all arranged, now it's just a matter of acquiring appropriate hardware. I have at my disposal, an Ultra 5. Nothing fantastic, I know, but I'm sure m68k's had less grunty boxes... It has a healthy amount of RAM, and I would put a new hard drive in it (or would accept a hard drive purchased by SPI or something). I think an Ultra 5 is probably a little light for our purposes: m68k's porter machine may be slower, but m68k also doesn't have, say, an openoffice.org port that might need debugging... Also, given the problems that consumer-grade DSL poses for system accessibility over the long term, I'd think that vore is still a better bet currently in spite of some past connectivity problems there, both connectivity-wise and bogomips-wise. Would you be willing to ship the system to Stephen if the search for better hardware pans out and vore proves unreliable in the long term? I'd prefer not to relinquish posession of the box. Could it be added to the pool of developer accessible machines anyway (with the more-the-merrier reasoning), or is it considered insufficiently grunty bogo-mips-wise? That'd be DSA's call; but given that it probably wouldn't be sufficient, it also seems unnecessary, so I guess it would be a low priority. You could always make a standing offer of individual accounts to DDs (or non-DDs, as we often have NMs who need help getting access for porting issues), I suppose? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Re: Developer accessible SPARC machine
Hi Andrew, On Tue, Jan 03, 2006 at 04:35:30PM -0800, Andrew Pollock wrote: I note that one of the issues with the Sparc port is the the lack of a developer accessible machine. At present, vore.debian.org is back on line; the underlying issue, though, seems to be that vore, like the buildds, won't necessarily *stay* on-line due to some hard-to-pin kernel bugs that keep taking the systems down. Anyway, I'm working with Stephen Frost (though working is a bit of an overstatement, he's currently waiting on me) to arrange hosting of a porter system with his employer; the space is all arranged, now it's just a matter of acquiring appropriate hardware. I have at my disposal, an Ultra 5. Nothing fantastic, I know, but I'm sure m68k's had less grunty boxes... It has a healthy amount of RAM, and I would put a new hard drive in it (or would accept a hard drive purchased by SPI or something). I think an Ultra 5 is probably a little light for our purposes: m68k's porter machine may be slower, but m68k also doesn't have, say, an openoffice.org port that might need debugging... Also, given the problems that consumer-grade DSL poses for system accessibility over the long term, I'd think that vore is still a better bet currently in spite of some past connectivity problems there, both connectivity-wise and bogomips-wise. Would you be willing to ship the system to Stephen if the search for better hardware pans out and vore proves unreliable in the long term? Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
bug tracking for non-RC architectures
Hi folks, For architectures that are not release candidates, we are going to need another way to track release critical bugs. The whole point of having architecture criteria is so the project can give higher priority to issues affecting release architectures (or all architectures) than to issues that are specific to an architecture that isn't meeting our standards for releasability; and we're not doing that very effectively if we leave such architecture-specific bugs at RC severity. OTOH, we don't want to lose sight of them by just downgrading the severities, as this would make it awkward to reintroduce the architecture as a release candidate without also silently reintroducing RC bugs. Usertags to the rescue! I've gone through the current list of release critical bugs at http://bugs.debian.org/release-critical/debian/all.html, identified the bugs that I believe are specific to one or more of arm, m68k, s390, and sparc, and have downgraded/usertagged them. The results for all archs can be seen here: http://bugs.debian.org/cgi-bin/pkgreport.cgi?which=tag[EMAIL PROTECTED]tag=rc-arm,rc-m68k,rc-s390,rc-sparcnam0=Statuspri0=pending:pending,forwarded,pending-fixed,fixed,donettl0=Outstanding,Forwarded,Pending%20Upload,Fixed%20in%20NMU,Resolvednam1=Architecturepri1=tag:rc-arm,rc-m68k,rc-s390,rc-sparcttl1=arm,m68k,s390,sparcord1=0,1,2,3 Per-architecture views are also available: http://bugs.debian.org/cgi-bin/pkgreport.cgi?which=tag[EMAIL PROTECTED]tag=rc-arm http://bugs.debian.org/cgi-bin/pkgreport.cgi?which=tag[EMAIL PROTECTED]tag=rc-m68k http://bugs.debian.org/cgi-bin/pkgreport.cgi?which=tag[EMAIL PROTECTED]tag=rc-s390 http://bugs.debian.org/cgi-bin/pkgreport.cgi?which=tag[EMAIL PROTECTED]tag=rc-sparc This gives us convenient access to the bug lists relevant to each architecture, so that they can be upgraded again if/when the architecture meets the release criteria. I strongly encourage you to use this same usertag convention (rc-$arch usertag, under user debian-release@lists.debian.org) when filing new bugs about breakage specific to your architecture. Please refer to Anthony Towns' announcement[0] if you have questions about the use of usertags. Oh, and this also gives porters a handy list of bugs affecting their architecture that they can be working on in between getting things back in line with the release arch standards. As always, porter NMUs are encouraged -- you don't need an RC bug as an excuse to fix a package for your architecture! Wouldn't it be great to have zero bugs on that page two months from now? :) Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ [0] http://lists.debian.org/debian-devel-announce/2005/09/msg2.html signature.asc Description: Digital signature
Re: how to get in openboot ???
On Sat, 2005-12-17 at 19:25 +0100, Marc Coevoet wrote: Ok I put a linux cdrom and try to boot cdrom it says: boot device;:/iommu/sbus/[EMAIL PROTECTED], 40/[EMAIL PROTECTED], 80/[EMAIL PROTECTED],0:d can't open disk label can't open disk label package .. Can the boot see the cdrom ?? is the cdrom faulty ??? This suggests that you have a SCSI CD drive set for ID=6. What vintage of system and drive are you using? When I've had CD problems installing Debian on older Sparcs, they have been because: - drive was an external one and terminator was not present - an old drive couldn't read the type of CD media reliably; CD-R is more compatible with older drives than CD-RW - drive was new enough, but the CD was bad or I burned it wrong; try another CD (of another brand if necessary) and burn it at a slow rate - drive was bad -- SP Op 17-dec-05 om 18:29 heeft Jan-Benedict Glaw het volgende geschreven: On Sat, 2005-12-17 18:26:49 +0100, Marc Coevoet [EMAIL PROTECTED] wrote: Q: How do I access OpenBoot? Pressing the keys L1 and A at the same time will bring you to the OpenBoot system. You will see the display where is the L1 key ?? I see F1 ... It's usually written as Stop on the keyboard. MfG, JBG -- Jan-Benedict Glaw [EMAIL PROTECTED]. +49-172-7608481 _ O _ Eine Freie Meinung in einem Freien Kopf| Gegen Zensur | Gegen Krieg _ _ O für einen Freien Staat voll Freier Bürger | im Internet! | im Irak! O O O ret = do_actions((curr | FREE_SPEECH) ~(NEW_COPYRIGHT_LAW | DRM | TCPA)); -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Setting time time causes system crash
I am running a stock Debian Linux kernel 2.6.8-2-sparc64 on a Sun Netra T1. If I set the system time using a time server via ntp or directly from the command line it causes the system to lock up. There are not entries in the system log to evidence the cause. Any ideas? hwclock --hctosys and hwclock --systohc don't seem to bother anything. Currently my system time is -42409 seconds off. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Setting time time causes system crash
Work Around: I set the time using ntpd (ntpd -g 1) in 1 second steps and it updated progressively to the correct time without a crash. I suspect that when I tried to update it in one step of more than 42000 seconds that caused the crash. FYI: Offsets greater than 1000 seconds cause ntpd to exit without actually changing the system time and when I tried to manually set it, I was making a 42000 second step. Probably could have accomplished the same thing in small manual steps of less than 1 seconds. Thanks for response everyone, SUN+Debian ROCKS! -Original Message- From: Steve Discher [mailto:[EMAIL PROTECTED] Sent: Thursday, December 15, 2005 9:48 AM To: debian-sparc@lists.debian.org Subject: Setting time time causes system crash I am running a stock Debian Linux kernel 2.6.8-2-sparc64 on a Sun Netra T1. If I set the system time using a time server via ntp or directly from the command line it causes the system to lock up. There are not entries in the system log to evidence the cause. Any ideas? hwclock --hctosys and hwclock --systohc don't seem to bother anything. Currently my system time is -42409 seconds off. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Setting time time causes system crash
T105 -Original Message- From: Clint Adams [mailto:[EMAIL PROTECTED] Sent: Thursday, December 15, 2005 10:25 AM To: Steve Discher Cc: debian-sparc@lists.debian.org Subject: Re: Setting time time causes system crash I am running a stock Debian Linux kernel 2.6.8-2-sparc64 on a Sun Netra T1. Is this a t105 and not a T1 AC200? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sparc build failure analysis (was Re: StrongARM tactics)
without worrying about the Failed state, yes? Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Re: Sparc build failure analysis (was Re: StrongARM tactics)
On Sun, Dec 11, 2005 at 02:38:35PM +0100, Jeroen van Wolffelaar wrote: On Sun, Dec 11, 2005 at 12:35:26AM -0800, Steve Langasek wrote: On Sat, Dec 10, 2005 at 06:53:47AM -0800, Blars Blarson wrote: FAILED But FAILED is an advisory state anyway; it doesn't directly benefit the port, at all, to have the package listed as Failed, this is just a convenience for folks sifting through the build failures (like the rarely used confirmed BTS tag is for maintainers). In the long-term, one of two things needs to happen with each of these build failures: the package needs to be added to P-a-s so the arch no longer tries to build it, or the package needs to be fixed -- via porter NMU if necessary. So as you have the list of these packages, as a porter you can proceed with figuring out which of the two categories each falls into, and take the necessary action without worrying about the Failed state, yes? Indeed, for practical buildd maintainance purposes, the distinction is not that important -- though 'Failed' is known to not benefit of a requeue, while 'Building:Maybe-Failed' might or might not, it's unkown, most archs should have enough surplus buildd power that retrying everything once in a while doesn't hurt. The major benefit is though to make it apparant for porters what to look into, without all the 'noise' in between of maybe-transient failures. One could also make sure that the FTBFS bugs are tagged (user-tagged) with [EMAIL PROTECTED] (etc) for example (or [EMAIL PROTECTED] There doesn't exist a [EMAIL PROTECTED] for example...), so that one can get a nice overview of all the porting bugs. It'd make sense to synchronise this across all architectures, so that it is consistent. http://lists.debian.org/debian-alpha/2005/12/msg00028.html Our porters can beat up your porters. ;) -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Re: testing security status
On Mon, Oct 10, 2005 at 05:50:01PM -0400, Joey Hess wrote: Another one of my periodic mails generated by checking every security holes listed on http://spohr.debian.org/~joeyh/testing-security.html as fixed in unstable but not in testing. CCing this time to the mailing lists for the ports that appear in the most issues below. You can grep for your architecture. (Ignoring all m68k problems.) abiword too young blocked on gmp/gcc-4.0 And on a lot of other things; gmp/gcc-4.0 is ready to go, so is no longer a blocker, but there are other libs abiword waits on that aren't ready to go yet. Also needs manual intervention from an ftpmaster to remove xfonts-abi. apachetop 9 days old blocked on gmp/gcc-4.0 clamav 20 days old! (DTSAs issued) blocked by gmp kismet 49 days old (DTSA issued) blocked by gmp python2.1 40 days old blocked by gmp python2.3 40 days old blocked by gmp Accepted with today's run (if aj commits the britney rerun). dia 7 days old missing sparc build blocked by gmp/gcc-4.0 It's also blocked by libpng, because it's been built against a version of libpng that had overly-strict shlibs. A sourceful upload to unstable would be best here, AFAICT. mozilla 25 days old (DTSAs issued for some issues) RC bugs missing alpha, arm, ia64 builds The newly-uploaded version fixes the alpha, arm, and ia64 build failures; it just needs to be built on hppa and sparc (and m68k). texmacs 85 days old! missing arm, hppa builds Will need a reupload to use g++-3.4 on arm/hppa/m68k. turqstat 28 days old missing hppa build blocked by gcc-4.0/gmp Also blocked by qt... xloadimage too young blocked by libpng hich is missing an arm build Should actually be rebuilt on arm and sparc to lose this libpng dependency; queued. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Re: Account on sparc machine(s) wanted
In article [EMAIL PROTECTED] you write: I am a member of Debian kernel team, working (to the extent of my abilities) on sparc-specific bugs. Recently I have moved and thus was forced to get rid of all my sparc hardware which I used for d-i testing and kernel work. The plans to get some new machines are on the way (Blars Blarson has a sparc32 box waiting for me and Andres Salomon is planning to ship an Ultra 5 my way), but it will take at least a few more weeks before I can lay my hands on them. In the meantime I can't even do test kernel builds or any basic testing/porting. If you have a possibility to open an account for me on a sparc box for this purpose, I would really appreciate it. If the box can be rebooted remotely or accessed via the serial console, that would be a huge plus. I have an Ultra 30 available - mail me a (PGP-signed) ssh key and I'll set you up. -- Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED] Welcome my son, welcome to the machine. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X3670A question
It is a stereo port. Here is info from Sun: Stereo Support Both Creator and Creator3D Graphics systems are stereo ready enabling users to view stereo images (Creator) or dynamic stereo 3D geometry (Creator3D) by adding the appropriate stereo viewing equipment. A sync port is provided on the back of the Creator Graphics module which interfaces to stereo viewing equipment. First generation systems feature a mini-stereo connector to carry the sync signal while second generation systems utilize an 8-pin mini-DIN connector. A Stereo-capable monitor is shipped with each Creator Graphics system. A compatible emitter and stereo glasses can be obtained from Stereographics Corporation (Part# ESUN: Emitter and Cable, and Part# CE2: Stereo Glasses) Regards, Steve Garrett On 9/9/05, Hartwig Atrops [EMAIL PROTECTED] wrote: Hello all.I yust received a Sun Ultra 60 wit a X3670A (501-5690) Creator 3D. TheCreator 3D has a 13W3 connector and a mini-Din (?) connector. What is thatmini-Din good for? Lots of useless Google hits ... Thanks,Hartwig--To UNSUBSCRIBE, email to [EMAIL PROTECTED]with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Booting Ultra 5 from external SCSI
On Mon, 2005-08-08 at 12:13 +0200, Dr. Zimmermann wrote: Hi Debians, my system is an ultra 5 with a 360 MHz CPU and 512 MB RAM. Getting frequent ide resets (specially under load) from the builtin ide drive/controller I'd like to use my external SCSI disk as boot and root device. SCSI adaptor and disk have been initially used under Solaris (5.8 and 5.9) and therefore are known to be OBP aware. Is anybody running such a configuration ? Greetings Roger, I recently installed Etch on a U5 with an internal SCSI drive and a PCI SCSI controller that is supported for booting via openprom. I removed the IDE hard drive, and used a businesscard ISO via the IDE CDROM (on its own cable) to boot the machine and start an Etch install. If so, are there any special requirements concerning the * disk partitioning Same as on an IDE drive on this platform. On Sparcs and Ultras, I use a small first partition as /boot, and the rest of the drive as / and swap, to live within the usual SILO partition location constraints. * openprom settings After the base installation completes and attempts to reboot --- dumped into openprom, as expected. There was no alias for the path through my SCSI controller to the drive. I puzzled out a path, saved it as diska (probably with nvalias), then set the boot device to diska. * silo configuration I probably used whatever the Etch installer set up. May have had to add an initrd statement. Using a 2.4.27 kernel. The FAQs I've found a more related to the older (sbus) systems though the hardware of the ultra 5 is more 'pc-like'. -- good luck, SP THNX, Roger -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Question regarding bootup | Debian on SPARC 4
Title: Message Hi All, I have a SPARC 4running sarge ona 2.6.12 sparc32 kernel. The question is, how can I get the box to boot up with no monitor or keyboard attached? The box boots fine with them attached but must hang when they are disconnected as not even the interfacecomes up. Any ideas? Cheers, Steve
RE: An (flamebait ?) idea to preserve debian on sparc32...
Hi Jurij et all, Is this using the link to initrd.img in /boot? I had to change my symlink to read the full path for both vmlinuz and intrd, otherwise it hangs on bootup as it couldn't find them ... I think. i.e. These symlinks hang: - lrwxrwxrwx 1 root root 33 Jul 19 20:02 initrd.img - boot/initrd.img-2.6.12-1-sparc32 lrwxrwxrwx 1 root root 30 Jul 19 20:01 vmlinuz - boot/vmlinuz-2.6.12-1-sparc32 And these work fine: - lrwxrwxrwx 1 root root 33 Jul 19 20:02 initrd.img - /boot/initrd.img-2.6.12-1-sparc32 lrwxrwxrwx 1 root root 30 Jul 19 20:01 vmlinuz - /boot/vmlinuz-2.6.12-1-sparc32 On boot, I see it creating the RAM disk and then releasing the memory later on. Shall I post you a copy of a my kern.log from a bootup? Cheers, Steve -Original Message- From: Jurij Smakov [mailto:[EMAIL PROTECTED] Sent: 31 July 2005 15:39 To: Steve Cc: debian-sparc@lists.debian.org Subject: RE: An (flamebait ?) idea to preserve debian on sparc32... On Sat, 30 Jul 2005, Steve wrote: Well, I have mailed to this list before and said ... I have a SPARC 4 sun4m working quite happily with the 2.6.12-1-sparc32 kernel running a fully upgraded sarge installation. Perhaps the reason for it being so happy is because this box is just being used a DNS/Syslog server with no monitor attached. Anyway, I shall continue to drop this bit of info into the list until someone explains why there seem to be so many issues when it would appear this box will run quite happily for quite some time before problems arise regarding new kernels or OS releases. Always willing to learn :-) Hi Steve, Unfortunately, the good old QA standard it works for me does not apply in this case :-). I am aware of multiple problems with this kernel. To mention a few: * The kernel you tested does not have initrd support, unlike other Debian kernels. I could not boot it with initrd (panic on boot), so I disabled it. 2.4.27 boots fine with initrd. * Debugging of the initrd problem indicated that occasionally (not every time, so you can be just lucky) the basic memory-copying routine corrupts the data it copies. That's a very serious problem, and I don't know an easy way to fix it. I suspect that this is responsible for the filesystem corruption under heavy load, I can reliably trigger it by dist-upgrade, and in this case it corrupts dpkg status files, which usually requires a reinstallation. * I have an independent confirmation, that the success/failure of 2.6.12 kernel to boot is correlated to the locations of the memory chips in the slots. I don't think it is acceptable to release a kernel with problems like these to our users. Best regards, Jurij Smakov[EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: An (flamebait ?) idea to preserve debian on sparc32...
Well, I have mailed to this list before and said ... I have a SPARC 4 sun4m working quite happily with the 2.6.12-1-sparc32 kernel running a fully upgraded sarge installation. Perhaps the reason for it being so happy is because this box is just being used a DNS/Syslog server with no monitor attached. Anyway, I shall continue to drop this bit of info into the list until someone explains why there seem to be so many issues when it would appear this box will run quite happily for quite some time before problems arise regarding new kernels or OS releases. Always willing to learn :-) Cheers all, Steve -Original Message- From: Romain Dolbeau [mailto:[EMAIL PROTECTED] Sent: 27 July 2005 10:23 To: debian-sparc@lists.debian.org Subject: An (flamebait ?) idea to preserve debian on sparc32... Hello all, I know I'm going to get flamed but here I go anyway... Right now it seems the sparc32 port is in trouble, due primarily to the kernel having support problem. It can be summed up by : 1) The 2.4 kernel has trouble on some 4m hardware, and 2.6 is almost non-working ; 2) userland (mostly glibc) doesn't work on v7 hardware (all sun4 and sun4c arch, plus the SM100 modules on sun4m). So my idea is: why not go over to a kernel and libc that actually support all of the above ? Namely, the NetBSD kernel... Debian already has started support for NetBSD on i386 and alpha ; why not try and add both sparc32/v7 and sparc32/v8 (the second being able to re-use most of the first userland) to that list ? The regular sparc port would become a pure v9 port, w/o the need to support legacy HW, and people running Debian on sparc32 would be able to continue to do so. Of course some will say why don't you run NetBSD then ?, which I do on my sun4 / sun4c (and even sun3 and sun3x :-) hardware, but I prefer apt-get and friends for my userland, as I'm sure others do. So, what do the sparc32 people think ? -- Romain Dolbeau [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Sarge may be last Debian release for 32 bit sparc systems
Hi All, I saw the following: - Reportedly, current 2.6 kernels do not work *at all* on sun4m. I mailed this list with an update ref: the SPARC 4 sun4m and the 2.6.12-1-sparc32 kernel which Jurij requested people try out. Works fine on my box, after 1 or 2 issues which were solved quite quickly with help from Jurij and Google :-) Its running sarge and I am just doing an update/upgrade on the system, everything seems to be going ok though. Just thought I would drop a mail. Cheers, Steve -Original Message- From: Steve Langasek [mailto:[EMAIL PROTECTED] Sent: 26 July 2005 03:15 To: debian-boot@lists.debian.org; debian-sparc@lists.debian.org Subject: Re: Sarge may be last Debian release for 32 bit sparc systems On Mon, Jul 25, 2005 at 02:06:46PM -0700, Blars Blarson wrote: In my opinion, we should drop support of all 32-bit sparc systems from Etch due to lack of people willing to spend the time to support them. This doesn't mean that we should delibaratly break things for them, but that the interest in continuing to support them is below what is needed to keep them as a viable part of Debian. Support of sun4c and sun4d was effectivly dropped from Sarge. The only reports trying d-i on this hardware that I remember seeing were failures, and noone bother to try to fix it. Upgrades from Woody may work, but were not well tested either. Were there actually install reports on sun4c and sun4d? I don't remember seeing any. Anyway, AIUI BenC killed these off years ago by changes to how gilbc was compiled. Sun4m is the last supported 32-bit sparc architecture. Reportedly, the 2.6 kernel does not work in multi-processor mode on them, and dropping support of 2.4 from Etch is being discussed. Reportedly, current 2.6 kernels do not work *at all* on sun4m. This according to Jurij Smakov, who appears to currently be the sparc kernel maintainer in Debian. Note that lack of hardware is not the problem, if anyone wants some sun4m systems (located in Los Angeles) let me know before they wind up in the recycle pile. I have one here; works fine under sarge with a 2.4 kernel. I have no intention of spending large amounts of my own time to keep 2.6 viable on this architecture, though, when as it stands the box I have is only powered up for use as a porting machine and it can't even be used to build Debian kernels because depmod bombs out. -- Steve Langasek postmodern programmer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge may be last Debian release for 32 bit sparc systems
On Mon, Jul 25, 2005 at 02:06:46PM -0700, Blars Blarson wrote: In my opinion, we should drop support of all 32-bit sparc systems from Etch due to lack of people willing to spend the time to support them. This doesn't mean that we should delibaratly break things for them, but that the interest in continuing to support them is below what is needed to keep them as a viable part of Debian. Support of sun4c and sun4d was effectivly dropped from Sarge. The only reports trying d-i on this hardware that I remember seeing were failures, and noone bother to try to fix it. Upgrades from Woody may work, but were not well tested either. Were there actually install reports on sun4c and sun4d? I don't remember seeing any. Anyway, AIUI BenC killed these off years ago by changes to how gilbc was compiled. Sun4m is the last supported 32-bit sparc architecture. Reportedly, the 2.6 kernel does not work in multi-processor mode on them, and dropping support of 2.4 from Etch is being discussed. Reportedly, current 2.6 kernels do not work *at all* on sun4m. This according to Jurij Smakov, who appears to currently be the sparc kernel maintainer in Debian. Note that lack of hardware is not the problem, if anyone wants some sun4m systems (located in Los Angeles) let me know before they wind up in the recycle pile. I have one here; works fine under sarge with a 2.4 kernel. I have no intention of spending large amounts of my own time to keep 2.6 viable on this architecture, though, when as it stands the box I have is only powered up for use as a porting machine and it can't even be used to build Debian kernels because depmod bombs out. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
RE: 2.6.12 testers wanted | sparc32 kernel on SPARC4 sun4m
Hi All, I upgraded to the 2.6.12 image with only a few minor issues on a SPARC 4 sun4m box (floppy drive only). I deleted and re-created the symlinks for the kernel and initrd after the kernel install as this looked like it would be the same issue I saw with the upgrade to 2.4.27. The symlinks were created as follows: - lrwxrwxrwx 1 root root 33 Jul 19 20:02 initrd.img - boot/initrd.img-2.6.12-1-sparc32 lrwxrwxrwx 1 root root 30 Jul 19 20:01 vmlinuz - boot/vmlinuz-2.6.12-1-sparc32 Changed them to: - lrwxrwxrwx 1 root root 33 Jul 19 20:02 initrd.img - /boot/initrd.img-2.6.12-1-sparc32 lrwxrwxrwx 1 root root 30 Jul 19 20:01 vmlinuz - /boot/vmlinuz-2.6.12-1-sparc32 After the upgrade I couldn't ssh to the box and my keyboard didn't work. I booted into the old 2.4.27 kernel, removed the console-data and console-tools packages (as suggested by Jurij, thanks) and rebooted. Seemed fine for the keyboard but I still couldn't ssh into the box even though I saw sshd had started. Added the following line to /etc/fstab: - none/dev/ptsdevptsgid=5,mode=6200 0 After a reboot and all worked fine. System seems happy enough on 2.6.12-1-sparc32. Cheers, Steve -Original Message- From: Jurij Smakov [mailto:[EMAIL PROTECTED] Sent: 13 July 2005 06:27 To: debian-sparc@lists.debian.org Subject: 2.6.12 testers wanted Hi, The kernel team is currently preparing the release of kernel 2.6.12. I have been testing the new release on sparc, with some mixed results. For sparc64 everything seems to look good, the kernel boots fine on my testing machine(s) and appears to function properly. I've received a report of it not booting on Netra X1, however the person who reported it have come up with a working kernel config. This config differs a bit from the one used in official kernels, so I hope that we'll be able to find the problem fairly soon. Note that tg3 driver has been readded to 2.6.12 Debian kernel source. On sparc32 things do not look good at all. First, all attempts to boot an initrd-enabled kernel have failed miserably, with kernel failing to mount initrd and subsequently panicking. Few days ago I have disabled initrd support and finally managed to get kernel to boot on my SS10 with HyperSparc CPU. Unfortunately, it appears to occasionally corrupt the filesystem under heavy memory/disk activity (such as sarge to sid upgrade). So, at this moment I am not sure whether it makes sense to build the sparc32 debs for 2.6.12 at all, as the kernel is pretty badly broken. It might be though, that the issues are specific to the Hypersparc CPU, so the images might work fine for others. In order to make a more informed decision about sparc32 and make sure that everything is fine on sparc64, it would be great if the preliminary debs would receive testing on a wider variety of hardware. Note, that testing the sparc32 image may COMPLETELY BREAK your system, so backup the data on the machine, if it is of any value. Even though there are currently now known issues on sparc64, backing up important stuff is always useful when testing the new kernels. The kernel images are available at http://www.wooyd.org/debian/kernels/2.6/ Please report your experiences either by replying to this thread, or to the SparcKernelStatus wiki page at http://wiki.debian.net/?SparcKernelStatus Thanks for your cooperation, Jurij Smakov[EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC P.S. Don't be alarmed by the fact that the packages are called linux-image now, instead of kernel-image. This renaming is part of the transition to a common kernel packaging scheme, in which all the kernel debs are built from the same source package. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Press L1-A to return to the boot prom
Title: Message Hi Frederic, That is the "stop" key(left hand side of the keyboard on the 5c) and the "a" key. If you do this when the box is initialising you will get the PROM prompt "ok" and if you do it when you see SILO, you will be at the "boot" prompt. The "ok" prompt allows you to do some system checking and change your boot options, floppy, cd, net etc and the "boot" prompt allows you to specify which specific kernel you want to boot from. I am sure there are other more experienced members on the list who can you better details of what you can/can't do from these prompts. Are you getting this on a kernel upgrade? If so, you may have to change your symlinks to read full paths /boot/vmlinuz-whatever rather than just boot/vmlinuz-whatever. Cheers, Steve -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 20 July 2005 12:05To: debian-sparc@lists.debian.orgSubject: Re: Press L1-A to return to the boot prom "Press L1-A to return to the boot prom" What key sequence is this? I have a Type 5 keyboard. - JAIMES Frédéric - RATP/EST/ISF 50-54, avenue Roger Salengro Bat. Chartreuse - LAC C42 94724 FONTENAY SOUS BOIS CEDEX Tel : 01.58.77.01.59 Fax: 01.58.77.02.18
RE: Booting Debian Sarge on SUN Ultra 10
Hi Oto, Not so sure that this will be the same issue I had with the SPARC4 but, have you checked your symlinks when you have booted up manually? I had an issue where the symlinks were not created correctly for my setup and once I had changed them to FULL paths, the system booted fine with no user interaction. Perhaps you can put some log info and let us know what you have done, does it boot when you do it manually? Cheers, Steve -Original Message- From: Oto Malencik [mailto:[EMAIL PROTECTED] Sent: 15 July 2005 12:27 To: debian-sparc@lists.debian.org Subject: Booting Debian Sarge on SUN Ultra 10 Dear sirs. I encountered following problem. While booting after installing Debian Sparc on SUN ULTRA 10 I see prompt: Boot: after pressing ENTER it appears Kernel doesn't support loading to high memory, restoring done. Loading Kernel 2.6.8 Loading initial ram disk . Fast Data Access NMU Miss and OS doesn't start Thanks for answer Best regards Oto Malencik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Debian on Sparc 4 - woody to sarge - more progress
Hi Jurij et all, I couldn't seem to see why I could type the full path and it would work, yet SILO couldn't get the info from silo.conf. My symlinks are there and so are the files. In the end I went OTT in silo.conf but it has fixed the problem. Now I need to see why I had it in the first place. Below is the info you requested, even though I can now reboot with no issues really. I have a few aesthetics to look at, why it changed my display to white and why I cannot see the correct Debian install dialogs (the blue ones). Being able to upgrade the kernel and access the debian site was the main issue here and that appears to be solved. Thanks a lot for your time Jurij et al, Steve dns:/# cat /etc/silo.conf root=/dev/sda1 partition=1 default=linux timeout=100 read-only image=1/boot/vmlinuz-2.4.27-2-sparc32 initrd=1/boot/initrd.img-2.4.27-2-sparc32 root=/dev/sda1 label=linux image=1/vmlinuz.old label=linux dns:/# ls -al total 55 drwxr-xr-x 20 root root 1024 Jul 1 16:35 . drwxr-xr-x 20 root root 1024 Jul 1 16:35 .. drwxr-xr-x2 root root 2048 Jul 1 13:06 bin drwxr-xr-x2 root root 1024 Jul 2 01:57 boot drwxr-xr-x2 root root 1024 Jun 30 21:38 cdrom drwxr-xr-x5 root root19456 Jul 2 11:48 dev drwxr-xr-x 40 root root 2048 Jul 2 11:48 etc drwxr-xr-x2 root root 1024 Jun 30 21:38 floppy drwxrwsr-x4 root staff1024 Jun 30 20:01 home drwxr-xr-x2 root root 1024 Jun 30 21:38 initrd lrwxrwxrwx1 root root 32 Jul 1 16:35 initrd.img - boot/initrd.img-2.4.27-2-sparc32 drwxr-xr-x5 root root 4096 Jun 30 21:51 lib drwx--2 root root12288 Jun 30 20:31 lost+found drwxr-xr-x2 root root 1024 Feb 8 2002 mnt drwxr-xr-x2 root root 1024 Jun 30 21:38 opt dr-xr-xr-x 35 root root0 Jul 2 2005 proc drwxr-xr-x3 root root 1024 Jul 1 18:00 root drwxr-xr-x2 root root 2048 Jul 1 13:02 sbin drwxrwxrwt3 root root 1024 Jul 2 11:40 tmp drwxr-xr-x 13 root root 1024 Jun 30 21:38 usr drwxr-xr-x 14 root root 1024 Jun 30 21:38 var lrwxrwxrwx1 root root 29 Jul 1 16:35 vmlinuz - boot/vmlinuz-2.4.27-2-sparc32 lrwxrwxrwx1 root root 27 Jun 30 20:51 vmlinuz.old - boot/vmlinuz-2.2.20-sun4cdm dns:/# ls -al /boot/ total 3567 drwxr-xr-x2 root root 1024 Jul 2 01:57 . drwxr-xr-x 20 root root 1024 Jul 1 16:35 .. -rw-r--r--1 root root 321829 Jun 30 20:51 System.map-2.2.20-sun4cdm -rw-r--r--1 root root 314634 Feb 15 11:38 System.map-2.4.27-2-sparc32 -rw-r--r--1 root root 1024 Aug 15 2002 cd.b -rw-r--r--1 root root 2982 Jun 30 20:51 config-2.2.20-sun4cdm -rw-r--r--1 root root12700 Feb 15 09:02 config-2.4.27-2-sparc32 -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 1101824 Jul 1 16:34 initrd.img-2.4.27-2-sparc32 -rw-r--r--1 root root 7680 Jun 30 21:53 old.b -rw-r--r--1 root root59904 Jul 2 11:44 second.b -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 Jun 30 20:51 vmlinuz-2.2.20-sun4cdm -rw-r--r--1 root root 842884 Feb 15 11:37 vmlinuz-2.4.27-2-sparc32 -Original Message- From: Jurij Smakov [mailto:[EMAIL PROTECTED] Sent: 02 July 2005 02:40 To: Steve Lewis Cc: debian-sparc@lists.debian.org Subject: RE: Debian on Sparc 4 - woody to sarge - more progress On Sat, 2 Jul 2005, Steve Lewis wrote: Hi All, Well, the sunlance addition to the modules.conf worked like a charm and I now see my interface card and can get on my network. Unfortunately I still have the boot problem. I think this is related to my silo.conf but have tried the following with no luck: - First attempt: - root=/dev/sda1 partition=1 default=Linux timeout=100 read-only image=1/vmlinuz label=linux initrd=initrd.img Try changing that to image=1/vmlinuz label=linux initrd=1/initrd.img Do you have the /initrd.img - /boot/initrd.img-2.4.27-sparc32 symbolic link set up? If you still have problems booting, post your final silo.conf file and the output of the following commands: ls -la / ls -la /boot Best regards, Jurij Smakov[EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe
Debian on Sparc 4 - woody to sarge - solved
All, I was wondering if the below issue was due to my symlinks? I wouldn't have thought so as they were created by installing the kernel package and initrd. A little later ... I started writing the above and thought I would just try it and see, after all, I know how to boot into it properly now if I get stuck (thanks a lot Jurij). Seems that the package install created symlinks in such a manner that silo didn't like them with the silo config I had. Changed the config to read: - dns:~# more /etc/silo.conf root=/dev/sda1 partition=1 default=linux timeout=100 read-only image=1/vmlinuz initrd=1/initrd.img label=linux image=1/vmlinuz.old label=linux Here is an ls -al on both directories (basically stated full paths /boot/file instead of boot/file), now works with no issues. Just my white screen to deal with, a minor problem compared to what has just been dealt with :-) dns:~# ls -al / total 57 drwxr-xr-x 21 root root 1024 Jul 2 17:55 . drwxr-xr-x 21 root root 1024 Jul 2 17:55 .. drwxr-xr-x2 root root 2048 Jul 1 13:06 bin drwxr-xr-x2 root root 1024 Jul 2 01:57 boot drwxr-xr-x2 root root 1024 Jun 30 21:38 cdrom drwxr-xr-x5 root root19456 Jul 2 18:02 dev drwxr-xr-x 41 root root 3072 Jul 2 18:02 etc drwxr-xr-x2 root root 1024 Jun 30 21:38 floppy drwxrwsr-x4 root staff1024 Jun 30 20:01 home drwxr-xr-x2 root root 1024 Jun 30 21:38 initrd lrwxrwxrwx1 root root 33 Jul 2 17:55 initrd.img - /boot/initrd.img-2.4.27-2-sparc32 drwxr-xr-x5 root root 4096 Jul 2 16:11 lib drwx--2 root root12288 Jun 30 20:31 lost+found drwxr-xr-x2 root root 1024 Feb 8 2002 mnt drwxr-xr-x2 root root 1024 Jun 30 21:38 opt dr-xr-xr-x 34 root root0 Jul 2 2005 proc drwxr-xr-x3 root root 1024 Jul 2 17:33 root drwxr-xr-x2 root root 2048 Jul 2 16:11 sbin drwxr-xr-x2 root root 1024 Jul 2 16:10 sys drwxrwxrwt3 root root 1024 Jul 2 17:55 tmp drwxr-xr-x 13 root root 1024 Jun 30 21:38 usr drwxr-xr-x 14 root root 1024 Jun 30 21:38 var lrwxrwxrwx1 root root 30 Jul 2 17:55 vmlinuz - /boot/vmlinuz-2.4.27-2-sparc32 lrwxrwxrwx1 root root 28 Jul 2 17:55 vmlinuz.old - /boot/vmlinuz-2.2.20-sun4cdm dns:~# ls -al /boot/ total 3567 drwxr-xr-x2 root root 1024 Jul 2 01:57 . drwxr-xr-x 21 root root 1024 Jul 2 17:55 .. -rw-r--r--1 root root 321829 Jun 30 20:51 System.map-2.2.20- sun4cdm -rw-r--r--1 root root 314634 Feb 15 11:38 System.map-2.4.27-2- sparc32 -rw-r--r--1 root root 1024 Aug 15 2002 cd.b -rw-r--r--1 root root 2982 Jun 30 20:51 config-2.2.20-sun4cdm -rw-r--r--1 root root12700 Feb 15 09:02 config-2.4.27-2- sparc32 -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 1101824 Jul 1 16:34 initrd.img-2.4.27-2- sparc32 -rw-r--r--1 root root 7680 Jun 30 21:53 old.b -rw-r--r--1 root root59904 Jul 2 17:59 second.b -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 Jun 30 20:51 vmlinuz-2.2.20- sun4cdm -rw-r--r--1 root root 842884 Feb 15 11:37 vmlinuz-2.4.27-2- sparc32 Would it be useful to create a mail to the list with the issues I experienced and resolutions, or just keep an eye on the mailing list? Thanks all, Steve -Original Message- From: Steve Lewis [mailto:[EMAIL PROTECTED] Sent: 02 July 2005 12:16 To: [EMAIL PROTECTED] Cc: debian-sparc@lists.debian.org Subject: RE: Debian on Sparc 4 - woody to sarge - more progress Hi Jurij et all, I couldn't seem to see why I could type the full path and it would work, yet SILO couldn't get the info from silo.conf. My symlinks are there and so are the files. In the end I went OTT in silo.conf but it has fixed the problem. Now I need to see why I had it in the first place. Below is the info you requested, even though I can now reboot with no issues really. I have a few aesthetics to look at, why it changed my display to white and why I cannot see the correct Debian install dialogs (the blue ones). Being able to upgrade the kernel and access the debian site was the main issue here and that appears to be solved. Thanks a lot for your time Jurij et al, Steve dns:/# cat /etc/silo.conf root=/dev/sda1 partition=1 default=linux timeout=100 read
RE: Debian on Sparc 4 - woody to sarge
Hi Jurij et all, Firstly, thanks for the help, it's appreciated. This is making more sense now ... finally ... sort of :) I have not as yet ever tried to upgrade a kernel and perhaps it would have been more straight forward if the releases had not just changed. I do not have a /boot partition. I have created a / partition on sda1 which is where my /boot directory is. Perhaps it would have been simpler if I had. I have vmlinux in / (root) which is symlinked to vmlinuz-2.2.20-sun4cdm in the /boot directory: - lrwxrwxrwx1 root root 27 Apr 2 16:52 vmlinuz - boot/vmlinuz-2.2.20-sun4cdm My silo.conf reads: - partition=1 root=/dev/sda1 timeout=100 image=1/vmlinuz label=linux read-only So, it seems (as I can boot with no problems from the current kernel and silo.conf) that once I have gone through the downloading of packages and editing the /etc/apt/sources.list again, the silo.conf should be edited to read: - root=/dev/sda1 partition=1 timeout=100 read-only image=1/vmlinuz label=linux initrd=/initrd.img image=1/vmlinuz.old label=linuxOLD initrd=/initrd.img.old I should then remove the existing symlink and create a new one called vmlinuz.old pointing to my 2.2.20 kernel and create a new symlink called vmlinuz pointing to the new 2.4.27 kernel Any issues on rebooting the new kernel would allow me to boot using the following: - linux image=1/boot/vmlinux-2.4.27-2-sparc32 initrd=1/boot/initrd.img-2.4.27-2-sparc32 root=/dev/sda1 And failing that to be able to use the old kernel by doing: - linux image=1/boot/vmlinux-2.2.20-sun4cdm initrd=1/boot/initrd.img-2.2.20-sun4cdm root=/dev/sda1 Do these need to be proceeded with the command 'boot'? I am not very familiar with where initrd installs into but looking at what you have written it seems like it also installs into the /boot directory. Does that all sound ok? I have used apt-get to download and install some of the packages, to gain some headway. The following may be of interest: - apt-get install modutils snip Architecture-specific modutils configuration not found, using defaults depmod: *** Unresolved symbols in /lib/modules/2.2.20/hfs.o apt-get install initrd-tools snip Setting up ash (0.3.8-37) ... scsi0: MEDIUM ERROR on channel 0, id 3, lun 0, CDB: 0x03 00 00 00 10 00 Info fld=0x1e7ec2, Current sd08:07: sns = f0 3 ASC=11 ASCQ=43 Raw sense data:0xf0 0x00 0x03 0x00 0x1e 0x7e 0xc2 0x0c 0x0d 0x32 0x04 0x2a 0x11 0x15 0x80 scsidisk I/O error: dev 08:07, sector 590354 Setting up cramfsprogs (1.1-6.woody1) ... Setting up stat (3.3-2) ... Setting up initrd-tools (0.1.79-0.woody1) ... Seems the errors setting up ash is related to /dev/sda7 which is my /usr partition. I have no idea if any of the errors above will affect the kernel upgrade or not. I have also used wget to download the kernel package but have not used dpkg to install it as yet: - wget http://ftp.debian.org/debian/pool/main/k/kernel-image-2.4.27-sparc/kerne l-image-2.4.27-2-sparc32_2.4.27-2_sparc.deb I have not edited the silo.conf or symlinks just yet, I thought it wiser to see if there any tips from this message. I remember that when the kernel package is installed that there is a question about symlinking but cannot quite remember it, something about doing it from scratch. Cheers for your time all, Steve -Original Message- From: Jurij Smakov [mailto:[EMAIL PROTECTED] Sent: 01 July 2005 01:39 To: Steve Lewis Cc: 'Debian Sparc' Subject: RE: Debian on Sparc 4 - woody to sarge On Thu, 30 Jun 2005, Steve Lewis wrote: I have since tried to upgrade my kernel to the kernel-image-2.4.27-2-sparc32_2.4.27-2_sparc.deb package but had a kernel panic, unable to mount root fs error on the reboot. I think this could be a silo.conf error. I did add the initrd line to silo.conf but I didn't include a root=/dev/sda1 line. I had a look around for a decent (full and complete) example of a silo.conf file but couldn't find one on the net. The manual page accessible with 'man silo.conf' command contains extensive documentation. Here's my working silo.conf: root=/dev/hda2 partition=1 default=Linux read-only timeout=100 image=/vmlinuz label=Linux initrd=/initrd.img image=/vmlinuz.old label=LinuxOLD initrd=/initrd.img.old Note that in my configuration /boot is a separate partition (/dev/hda1), which is also default (set by partition=1), so paths to the files are given relative to that partition. So setting image=/vmlinuz when the default partition is 1 will actually try to load file vmlinuz from the root of partition 1, which translates to /boot/vmlinuz. Also, if your silo.conf is broken, you still should be able to boot by typing something like this at the boot prompt: linux image=1/boot/vmlinux-2.4.27-2-sparc32 initrd=1/boot/initrd.img-2.4.27-2-sparc32 root=/dev/sda1 If you are still having trouble, post your silo.conf and we should be able to figure it out
RE: Debian on Sparc 4 - woody to sarge - some progress
Title: Message Hi All, Well, I gave it another bash, but I still experienceda problem with the reboot. Applicable outputseen are: - snip VFS: Disk quotas vdquot_6.5.1 devfs: v1.12c (20020818) Richard Gooch ([EMAIL PROTECTED]) devfs: boot_options 0x0 Console: switching to mono PROM 80x34 pty: 256 Unix98 ptys configured Floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 RAMDISK driver initialized: 16 RAM disks of 812K size 1024 blocksize Initializing Cryptographic API NET4: Linux TCP/IP 1.0 for NET4.0 IP: routing cache hash table of 512 buckets, 4Kbytes TCP: Hash tables configured (established 4096 bind 8192) NET4: Unix domian sockets 1.0/SMP for Linux NET4.0. VFS: Cannot open root device "sda1" or 08:01 Please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root fs on 08:01 Press L1-A to return to the boot prom I have no idea what L1-A is and cannot seem to get a prompt, so I rebooted and used 'stop-a' to get the boot prompt. I used the following command: - linux image=1/boot/vmlinuz-2.4.27-2-sparc32 initrd=1/boot/initrd.img-2.4.2.27-2-sparc32 root=/dev/sda1 It appeared to be working, decompressing the image, but then I just got what appeared to be theprom prompt back: - Uncompressing image... Loading initial ramdisk PROMLIB: obio_ranges 1 bootmem_init: Scan sp_banks, init_bootmem(spfn[20a],bpfn[20a],mlpfn[3faf]) free_bootmem: base[0] size[3faf000] reserve_bootmem: base[100] size[10d000] reserve_bootmem: base[0] size[20a000] reserve_bootmem: base[20a000] size[7f8] Booting Linux Type 'go' to resume Type help for more information Typing 'go' booted into Linux with the upgraded kernel surprisingly, I thought I was back at the beginning again ... shows you how often I have done that before ... never :-) So, before doing anything else, I thought it would be wise to check a few things and also understand why I got the problem booting into the new kernel and what to do to repair everything. I found out my ethernet interface is missing, an ifconfig -a just shows my loopback, which is possibly unfortunate. There is no associated hostname file in /etc anymore. I think this means I will have to configure the kernel which I have also not done before, so it could be interesting, which is why I say it is _possibly_ unfortunate :-) Checking the kern.log I see this is indeed a SPARC4 sun4m which clears up an earlier question: - ARCH: SUN4M TYPE: SPARCstation 4 :-) I also see that it has seen my ethernet interface as it states the MAC in the log. Checking the syslog I see only the following: - Ethernet address: MAC Whereas I used to see the below entries when it worked ok: - Ethernet address: MAC eth0: LANCE MAC eth0: using auto-carrier-detection. eth0: Carrier Lost, trying TPE As this was a completely basic system with hardly any software installed (wanted to upgrade it first) there is not too much to check, I can create, edit and remove files.It would be good to get to a system which needs no interaction on a reboot and can communicate with other devices though:-) Can anyone help out? Thanks again for your time all. Cheers, Steve
RE: Debian on Sparc 4 - woody to sarge - some progress
Title: Message Hi again All, After looking around a bit more it seems like this could be some sort of module issue. I have the correct settings in /etc/network/interfaces I noticed a post on the net regarding a similar issue which said that there was no discover1 seen in the output and that modules were being loaded specifically. Looking at the kern.log I cannot find a line with discover1 and I see 5 modules being loaded and lsmod shows them to be: - ext3 jbd sd_mod esp scsi_mod /etc/modules is empty but it says it should have a list of modules being loaded at boot time. under /etc/modutils/arch there isn't anything which looks like a sparc module, just alpha, atari, i386, various m68k files, various powerpc files, s390 and s390x Although in the modules.conf there is no processing of the arch files, so it seems that it isn't needed there. This could be tantamount to chasing a gazelle and about as much use asa chocolate fireguard but I see the file paths under modutils is empty but should specify a path to where the modules reside. Perhaps that is taken care of in the code somewhere as I see under /lib/modules there isa directory for both kernels. One thing to note here is that there are more modules under the old kernel, which as it is 2.2.x I wasn't sure if it was a modular kernel, I thought that was with 2.4.x only. I see under the /lib/module/2.2.x directory there is no sunhme.o, yet there isunder /lib/modules/2.4.x/kernel/drivers/net ... doesn'tsunhme.otake care of my eth0 interface?... or not as the case maybe :-) I have managed to find the 5 modules under various subdirectories of /lib/modules/2.4.x why are there just 5 loaded? I cannot find a reference to the 5 modules loaded in either the /etc/modules.conf or the associated /etc/modutils files. Seems I will definitely need some help here as I cannot manually configure the interface. Even though there is a reference to it in the kern.log, I get a "No such device" when I try to configure it. Here's hoping that someone out there knows the answer as I am very reluctant to just start editing files and rebooting, which I still have not done by the way ;-) Regards all, Steve -Original Message-From: Steve Lewis [mailto:[EMAIL PROTECTED] Sent: 01 July 2005 20:20To: debian-sparc@lists.debian.orgSubject: RE: Debian on Sparc 4 - woody to sarge - some progress Hi All, Well, I gave it another bash, but I still experienceda problem with the reboot. Applicable outputseen are: - snip VFS: Disk quotas vdquot_6.5.1 devfs: v1.12c (20020818) Richard Gooch ([EMAIL PROTECTED]) devfs: boot_options 0x0 Console: switching to mono PROM 80x34 pty: 256 Unix98 ptys configured Floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 RAMDISK driver initialized: 16 RAM disks of 812K size 1024 blocksize Initializing Cryptographic API NET4: Linux TCP/IP 1.0 for NET4.0 IP: routing cache hash table of 512 buckets, 4Kbytes TCP: Hash tables configured (established 4096 bind 8192) NET4: Unix domian sockets 1.0/SMP for Linux NET4.0. VFS: Cannot open root device "sda1" or 08:01 Please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root fs on 08:01 Press L1-A to return to the boot prom I have no idea what L1-A is and cannot seem to get a prompt, so I rebooted and used 'stop-a' to get the boot prompt. I used the following command: - linux image=1/boot/vmlinuz-2.4.27-2-sparc32 initrd=1/boot/initrd.img-2.4.2.27-2-sparc32 root=/dev/sda1 It appeared to be working, decompressing the image, but then I just got what appeared to be theprom prompt back: - Uncompressing image... Loading initial ramdisk PROMLIB: obio_ranges 1 bootmem_init: Scan sp_banks, init_bootmem(spfn[20a],bpfn[20a],mlpfn[3faf]) free_bootmem: base[0] size[3faf000] reserve_bootmem: base[100] size[10d000] reserve_bootmem: base[0] size[20a000] reserve_bootmem: base[20a000] size[7f8] Booting Linux Type 'go' to resume Type help for more information Typing 'go' booted into Linux with the upgraded kernel surprisingly, I thought I was back at the beginning again ... shows you how often I have done that before ... never :-) So, before doing anything else, I thought it would be wise to check a few things and also understand why I got the problem booting into the new kernel and what to do to repair everything. I found out my ethernet interface is missing, an ifconfig -a just shows my loopback, which is possibly unfortunate. There is no associated hostname file in /etc anymore. I think this means I will have to configure the kernel which I have also not done before, so it could be interesting, which is why I say it is _possibly_
RE: Debian on Sparc 4 - woody to sarge - some progress
Hi Patrick et al, I hadn't, just did and ... No such device Also dmesg just shows the same as the kern.log. Ethernet address MAC I used to (before kernel upgrade) have the following line in in kern.log on boot: - sunlance.c:v1.12 11/Mar/99 Miguel de Icaza ([EMAIL PROTECTED]) But I just noticed that it is missing since, also not present on dmesg. I thought perhaps that sunhme.o may find it, but perhaps that is just for the later ULTRA SPARC stations. I cannot see a lance module under the old /lib/modules/2.2.20 directory but as I mentioned in an earlier post, I thought only 2.4.x was modular. Interesting enough is that I have found a sunlance.o module under the following: - /lib/modules/2.4.27-2-sparc32/kernel/drivers/net/sunlance.o However, when I try and use it with modprobe I get the following error: - Modprobe: Can't locate module /lib/modules/2.4.27-2-sparc32/kernel/drivers/net/sunlance.o Strange too, modprobe -c shows that my kernel module path is /lib/module/kernel but the directory doesn't exist. I also have another top level path /lib/modules/2.4 which doesn't exist. Ah, in actual fact, I have just one toplevel directory which is correct, pointing to /lib/modules/2.4.27-2-sparc32 all the other path statements are pointing to /lib/modules/some directory and the directory doesn't exist. Perhaps that is why it cannot find the sunlance module. I suppose I could actually direct the output to a file, edit the paths and use the -C option to use the newly created config file. I wonder what I would break doing that :-) Cheers, Steve -Original Message- From: Patrick Morris [mailto:[EMAIL PROTECTED] Sent: 01 July 2005 23:31 To: Steve Lewis Cc: debian-sparc@lists.debian.org Subject: Re: Debian on Sparc 4 - woody to sarge - some progress Have you tried modprobe sunhme ? On Fri, 01 Jul 2005, Steve Lewis wrote: I see under the /lib/module/2.2.x directory there is no sunhme.o, yet there is under /lib/modules/2.4.x/kernel/drivers/net ... doesn't sunhme.o take care of my eth0 interface? ... or not as the case maybe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Debian on Sparc 4 - woody to sarge - some progress
I was too eager ... thanks Jurij, I tried modprobe sunlance.o instead of just sunlance. I was kinda getting into the right general idea but led myself astray a bit it seems. modprobe sunlance worked just fine. I shall have a good look around to see if there are any other modules which should be listed in /etc/modules as I certainly missed that. Now the question is this, as the interface issue will be cleared up on reboot, the error I experienced when I rebooted the new kernel: - snip VFS: Disk quotas vdquot_6.5.1 devfs: v1.12c (20020818) Richard Gooch ([EMAIL PROTECTED]) devfs: boot_options 0x0 Console: switching to mono PROM 80x34 pty: 256 Unix98 ptys configured Floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 RAMDISK driver initialized: 16 RAM disks of 812K size 1024 blocksize Initializing Cryptographic API NET4: Linux TCP/IP 1.0 for NET4.0 IP: routing cache hash table of 512 buckets, 4Kbytes TCP: Hash tables configured (established 4096 bind 8192) NET4: Unix domian sockets 1.0/SMP for Linux NET4.0. VFS: Cannot open root device sda1 or 08:01 Please append a correct root= boot option Kernel panic: VFS: Unable to mount root fs on 08:01 Press L1-A to return to the boot prom Was that a user issue because I have symlinks in / pointing to /boot and _also_ have the following silo.conf file? I still had the Please append a correct root= boot option even though it is clearly in my silo.conf $ cat /etc/silo.conf root=/dev/sda1 partition=1 timeout=100 read-only image=1/vmlinuz label=linux initrd=/initrd.img image=1/vmlinuz.old label=linuxOLD Getting there slowly but surely. I am still reluctant to reboot just yet as I would like to minimize fallout. Cheers, Steve -Original Message- From: Jurij Smakov [mailto:[EMAIL PROTECTED] Sent: 01 July 2005 23:58 To: Steve Lewis Cc: debian-sparc@lists.debian.org Subject: Re: Debian on Sparc 4 - woody to sarge - some progress On Fri, 1 Jul 2005, Patrick Morris wrote: Have you tried modprobe sunhme ? On Fri, 01 Jul 2005, Steve Lewis wrote: I see under the /lib/module/2.2.x directory there is no sunhme.o, yet there is under /lib/modules/2.4.x/kernel/drivers/net ... doesn't sunhme.o take care of my eth0 interface? ... or not as the case maybe Yes, the network card drivers used to be compiled into the kernel in 2.2.20, but are available as modules in 2.4. From previous postings it is clear that you have a Sun Lance network card, so the command to activate it should be 'modprobe sunlance', not sunhme. You can also add the name of the module (sunlance, that is) to /etc/modules, so it is automatically loaded on every boot. Best regards, Jurij Smakov[EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Debian on Sparc 4 - woody to sarge - more progress
Title: Message Hi All, Well, the sunlance addition to the modules.conf worked like a charm and I now see my interface card and can get on my network.Unfortunately I still have the boot problem. I think this is related to my silo.conf but have tried the following with no luck: - First attempt: - root=/dev/sda1partition=1default=Linuxtimeout=100read-only image=1/vmlinuz label=linux initrd=initrd.img image=1/vmlinuz.old label=linux -- Second attempt: - root=/dev/sda1partition=1default=Linuxtimeout=100read-only image=/vmlinuz label=linux initrd=initrd.img image=/vmlinuz.old label=linux The reason for tryingwithout the 1 in the image line was because I thought the 'partition=1' was perhaps making it read image=1/1/vmlinuz I also tried moving the file to the boot directory and doing a silo -C /boot/silo.conf, but that didn't work either. This _could_ be my last hurdle to finishing off the kernel upgrade and move to sarge on my SPARC4. I should really do this on my P3 as well, but may take a bit of time off :-) Thanks for your help all, Steve
RE: Debian on Sparc 4
Hi Jurij, Indeed, it does appear that I was tricked :) I edited the sources.list changed stable to woody and it seems that I may be on track to at least get this box up and running properly. Thanks a lot! I think the SPARC 4 is a sun4m architecture although I am no guru on SUN architecture at all. I don't know the differences between c and m but I think the sun4c is the SPARC 1 and 2. I shall have to take a closer look at this although looking at the SUN site I am sure it is sun4m. I shall see if sarge supports it. Perhaps the sun4m can use a = 2.4.21 kernel and then be upgraded to sarge. Thanks again for your help, Steve -Original Message- From: Jurij Smakov [mailto:[EMAIL PROTECTED] Sent: 30 June 2005 02:06 To: Steve Lewis Cc: debian-sparc@lists.debian.org Subject: Re: Debian on Sparc 4 On Wed, 29 Jun 2005, Steve Lewis wrote: The kernel which came with the woody floppies is 2.2.20-sun4cdm. To use apt-get and security updates requires libc6 and libc6 requires a kernel later than 2.4.21. I cannot seem to find a way of installing a kernel = 2.4.21 without installing additional packages which have dependencies on libc6. You are probably tricked by the fact that woody is no longer 'stable'. Sarge is the new 'stable' release, so whenever you put 'stable' into your sources.list, it tries to pull in the Sarge's files, which is not desired. Instead use 'woody' or 'oldstable' in your sources.list and you should be fine. I have looked at going to Sarge but I cannot seem to locate any of the usual installation floppy .bin images, rescue, root and driver. I believe that your machine is of sun4c subarchitecture, which is not officially supported by Sarge. Have a look at the page http://wiki.debian.net/?SparcSun4c which might help with the installation. Best regards, Jurij Smakov[EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Debian on Sparc 4 - woody to sarge
Thanks for the tip Martin, Looking at the page it seems I have the following, which is indeed sun4m: - SPARCstation 4 Processor(s): MicroSPARC II @ 70MHz Bus:SBus, 1 slot Architecture: sun4m Notes: Optional 16-bit audio, onboard framebuffer. All, I have since tried to upgrade my kernel to the kernel-image-2.4.27-2-sparc32_2.4.27-2_sparc.deb package but had a kernel panic, unable to mount root fs error on the reboot. I think this could be a silo.conf error. I did add the initrd line to silo.conf but I didn't include a root=/dev/sda1 line. I had a look around for a decent (full and complete) example of a silo.conf file but couldn't find one on the net. I was hoping that upgrading the kernel would allow me to move to the new stable 'sarge' release. Any good pointers? Once again though, getting my box back to a decent version of woody was not straight forward, I had to edit my source.list before completing the install as the floppy disks always point to stable, which of course is now 'sarge'. I tried getting the floppy rescue and driver files over the net thinking they may have been updated, but alas no. Cheers all, Steve -Original Message- From: Martin [mailto:[EMAIL PROTECTED] Sent: 30 June 2005 21:14 To: Debian Sparc Subject: RE: Debian on Sparc 4 I think the SPARC 4 is a sun4m architecture although I am no guru on SUN architecture at all. It is a sun4m machine. For hardware info for this generation of machine, this site: http://www.sunhelp.org/faq/sunref1.html is good (IMHO). I don't know the differences between c and m but I think the sun4c is the SPARC 1 and 2. They are a different abstract architecture, more critically sun4m machines use SPARC v8 processors rather then SPARC v7 in sun4c machines (I can't think of an exception - although there might be one). This only matters as SPARC v8 has unsigned int multiply and divides (as well as atomic swap I believe) which has to be emulated on SPARC v7 machines. In short, for a few key apps (such as ssh, GPG and libc), having support for SPARC v7 processors slows down the code on faster machines, thus (and as sun4c machines are getting quite old) there is limited support for them in Debian 3.1. I shall have to take a closer look at this although looking at the SUN site I am sure it is sun4m. I shall see if sarge supports it. Perhaps the sun4m can use a = 2.4.21 kernel and then be upgraded to sarge. I believe sarge on sun4m is viable, not sure about the status of 2.6 kernels on sun4m machines, know there used to be at least some bugs on SMP, check the archives and http://sparclinux.mit.edu/sparc/ if you have problems with it. HTH Cheers, - Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Debian on Sparc 4
Title: Message Hi All, I am fairly new to Debian on a SPARC, as you will no doubt surmise from the email:-) I have been using Solaris for a while. Ihave alsohad Debian running on a P3 fora couple of months and its been fine so far, no issues. I have an old SPARC 4 with no CD ROM, just a floppy drive and so I downloaded the floppies a month or so ago. It appears there are only floppy images for the Woody release. I have run into an issue which appears to be a bit chicken and egg and have found a few other people via google who have the same problem. I have, as yet, not seen a confirmed solution. The kernel which came with the woody floppies is 2.2.20-sun4cdm. To use apt-get and security updates requires libc6 and libc6 requires a kernel later than 2.4.21. I cannot seem to find a way of installing a kernel = 2.4.21 without installing additional packages which have dependencies on libc6. I have tried a few methods of installing the system withfloppies and via the net but I am stuck with this issue. I also tried to download the barest minimum and downloaded the kernel upgrade files I found under the sarge release to another box on the network in the hope of transferring them to the SPARC4. There seems to be no way of getting the filesacross to upgrade the kernel before I hit the libc6 issue. No wget, ftp, tftp, scp, ssh or anything that I have used before. So, it appears to me that the base install of the woody versioncontains software withlibc6 dependencies which in turn requires the later kernel; I don't think that kernel is available withthe SPARC floppies, I could be wrong though. I have looked at going to Sarge but I cannot seem to locate any of the usual installation floppy .bin images, rescue, root and driver. Has anyone experienced the same or a similar issue and found a workaround? Cheers for your time, Steve
Re: Bug#261824: time's up
On Wed, Mar 23, 2005 at 07:54:14AM -0500, Ben Collins wrote: I did the new upstream, so I can tell you that it was only a couple of lines of code changes, and they were tested well before being put into the silo repo. I don't think it needs extensive testing. It seems that this version of silo ended up being used to build the CDs for d-i RC3 (even though the .deb *on* the CDs came from testing), so it's already getting more extensive testing than I think we bargained for. It also seems to be holding up well under it, so I'm going ahead and approving 1.4.9-1 for testing, barring the appearance of any last-minute RC bugs. Thanks, -- Steve Langasek postmodern programmer On Wed, Mar 23, 2005 at 12:34:14AM -0800, Steve Langasek wrote: On Tue, Mar 22, 2005 at 05:30:55AM -0500, Ben Collins wrote: Can the silo I just uploaded go into testing atleast? It does fix some bugs. In fact, it may fix some of the rc silo bugs, but I need testing with it to make sure (didn't want to claim the bugs were fixed without testing by others first). It fixes the RC build-dependency bug, so it should probably go in; but given that it's a new upstream version, it should get a fair measure of testing first -- at least to verify it hasn't caused any major regressions, whether or not it fixes the outstanding bugs. Thanks, -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: Bug#261824: time's up
On Tue, Mar 22, 2005 at 05:30:55AM -0500, Ben Collins wrote: Can the silo I just uploaded go into testing atleast? It does fix some bugs. In fact, it may fix some of the rc silo bugs, but I need testing with it to make sure (didn't want to claim the bugs were fixed without testing by others first). It fixes the RC build-dependency bug, so it should probably go in; but given that it's a new upstream version, it should get a fair measure of testing first -- at least to verify it hasn't caused any major regressions, whether or not it fixes the outstanding bugs. Thanks, -- Steve Langasek postmodern programmer On Tue, Mar 22, 2005 at 02:54:12AM -0800, Steve Langasek wrote: severity 261824 important severity 267428 important thanks Time's up, folks; if no fix has been found yet for these bootloader bugs, they'll have to remain hardware-specific errata for sarge. They will no longer be allowed to block the release, since silo still works on the majority of sparc hardware. Someone should, however, document these problems for the install manual and/or d-i errata. If someone can determine one way or another whether the gcc-2.95 rebuild actually fixes the problem on Ultra5 for someone other than Geert, that would help me in deciding whether an NMU is warranted. signature.asc Description: Digital signature
Re: How to use 200 GB Disk on Ultra10?
On Sun, 2005-01-02 at 07:16 +0100, Roland Rick wrote: Hi everybody I have an old Ultra10 and want to use it as RAID1 mirror. Unfortunately I may not correctly see my 200 GB disks... Open Boot PROM: 3.11 Disk parameters, Maxtor modell 6Y200P0: HDS:SECT= 16:63 Max Cyls= 16'383 MaxLba = 398'297'088 Act Cyl = 395'136 GB Capacity = 200 If I try to partition with s an Sun device, and entering with 0 - 16 heads (default) - 63 sectors (default) - 16'381 cylinders (default: about 4567, cannot remember exactly) - 2 spare cylinders (= 16'383 physical cyl.) - interleave factor 1 (default) - 0 extra sectors per cyl (defaut), I get only a disk size of about 8 GB. What make I wrong? Is the disk size 200 GB not available for OBP 3.11? capacity = heads x sectors x cylinders x 512 bytes/sector 16 x 63 x 16381 x 512 ~= 8GB I understand that there are limits on the three values in a U10, I believe 255 heads, 63 sectors, and 16383 cyl. 120G and 80G drives work okay in my U10, with OBP 3.19.4 1999/04/28. Geometries are 14593 cyl, 255 heads, 63 sectors, and 9729/255/63 respectively. = Who knows a workaround? Candidate: recent kernel 2.6 with USB's EHCI (USB2) support + USB2 card + external USB2 drive box. (As others have indicated you would still need an internal drive to boot.) On another platform I get bonnie++ sequential read and write test results from an external USB2 drive of around 30 megabytes/sec, about double the rate for the similar vintage internal drives on the U10. -- good luck, SP I would really appreciate any help! Cheers, Roland PS: Happy new year!
Re: PCI hardware on sparc32?
On Mon, 2005-01-03 at 11:05 -0500, Jurij Smakov wrote: Hello, While investigating the bug #288140 it was found that keyboard works incorrectly on sparc32 if the CONFIG_PCI is set. A simple workaround which I've proposed (and which solves the problem) is to unset it in the kernel config. This solution, however, makes PCI hardware on sparc32 non-functional, which warrants a question whether anyone has/uses PCI stuff on sparc32. Please let me know if you do, we'll look for an alternative solution then. Sun's diskless Javastation Krups is sparc32 with PCI bus. (No slots.) Krups uses PC-spec keyboards and mice so may not be affected by this bug. I don't believe that the stock Debian kernels support netboot + NFS root, so a custom kernel config would be needed. -- SP Best regards, Jurij Smakov[EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- Steve Pacenka [EMAIL PROTECTED]
Re: Whats the trick?
On Sat, 2004-11-20 at 09:15, Walt L. Williams wrote: Greetings all I have been trying to load Sarge onto an Ultra 2. I have tried several things in an effort to load so it will boot. I seems to load ok after I do the modprobe work around. But when the system goes to re-boot it comes up and starts to run silo and promptly terminates Program terminated In the partitioning I have set the boot flag to on, then left it off. That didn't make any difference. I pulled the second CPU thinking there was something wrong with the SMP kernel. This also didn't make any difference. I've even selected the ext2 in the partitioning. That also didn't make any difference. Is the partition containing your boot kernel and silo.conf under 2 gigabytes in size and first in the partition table? My partition layout on a 9G drive is a ~50M /boot ext2 first, 256M swap, and / covering most of the rest of the drive. There's a whole disk Sun label as partition 3. Any thoughts? My system is an Ultra 2 with 256MB of ram and dual 200MHZ processors. It has a 9GB and an 18GB hard drive it it. I am hoping to make a web server out of it. It was loaded with Debain 3.0r0 . My U2 acquired in October has dual 296 MHz, one 9G HD, 384M RAM, Creator 3D graphics. I used the Sarge businesscard ISO from around October 21. Aside from the missing esp module, the install went perfectly and the machine has been in daily use as my primary office workstation for a month. This was the easiest and most robust Sparc Linux install I've done out of eleven. -- SP Any comments will be appreciated. Walt Williams
Re: CD malfunction on Sarge testing install Sparc
On Thu, 2004-11-18 at 13:56, Walt L. Williams wrote: Greetings This may be a little off topic. I just tried to install Sarge testing for Sparc which I downloaded just last on an Ultra2. I was able to boot from the CD but afterwards it (strangely) could not find the CDROM drive which it booted from and therefore would not install. I didn't know who else to report this to so I posted it here. Could someone please let the appropriate individuals know. This exact problem has been discussed recently in this list, and a related repair to the Sarge installer is in progress. The problem is that the installer did not autodetect the Ultra 2's SCSI controller and did not load its kernel module, so the SCSI CD-ROM drive (and also any SCSI hard drives) are inaccessible. Temporary workaround, at point when you have the can't find CD-ROM screen: ctrl-alt-f2 to get to a console modprobe esp modprobe sr_mod ctrl-alt-f1 retry to find the CD-ROM drive After this workaround, I was able to do a clean Sarge install on an Ultra 2 SMP box. -- SP Walt Williams
Re: Got sound going on a U60 debian smp
after checking modprobe -v cs4231 I got some errors showing that this wasn't working at all ... (missing symbols etc..) I just went back to Debian's 2.4.27-1-sparc64-smp on my U60 (normally I use a 2.6.8 to get USB2), and the cs4231 module loads and works. I loaded it with modprobe then reran /etc/init.d/audioctl start . I then found some info on the module you suggested cs4231 and followed a couple of steps to get my card producing output rmmod soundcore insmod audio insmod cs4231 That looks good. audioctl -f /dev/audio -w play.port=headphone I don't think /dev/audio is relevant here. Maybe try audioctl -w play.port=headphone There are examples of how to set PARAMS in /etc/default/audioctl . The initscript for audioctl runs something like audioctl -nw $PARAMS and PARAMS is set in /etc/default/audioctl . Not too complicated. lsmod output showed Module Size Used byNot tainted cs4231 21936 0 audio 23744 1 [cs4231] ac97_codec 16752 0 (unused) openprom5312 0 (autoclean) lp 8728 0 (autoclean) parport34064 0 (autoclean) [lp] autofs410236 0 (unused) hid17336 0 (unused) Get rid of ac97_codec . I was wondering what exactly to put in here and how this works I still have to track down some documentation for this but I found someone elses config that had the following in it char-major-14 soundcore alias sound-slot-0 cs4232 alias sound-service-0-0 sound # mixer alias sound-service-0-3 sound # /dev/dsp /dev/audio alias sound-service-0-6 sound # /dev/sndstat options cs4232 io=0x530 irq=5 dma=1 dma2=0 # numbers may vary You shouldn't need add any of that for the built-in sound, if you include cs4231 in /etc/modules . This is probably wrong for my setup but I ithink I need to understand whats going on before I go down this road. like wise for this recomendation Have you set the PARAMS variable PARAMS=play.port=line_out in /etc./default/audioctl ? Thanks for this info I will try to find some documentation on these files and parameters and go from there. The file /etc/default/audioctl contains many instructive comments. I am now working on the following. 1. Get the sound card playing raw at the correct level. 2. get xmms working with the sound card ... Currently raw files work but I think I am having issues using OSS pointing at /dev/audio (producing noise not music (could be sending wrong format to the device) If /dev/audio doesn't work, maybe /dev/dsp will. Try alsaplayer instead of xmms. I have had mixed results with xmms, but alsaplayer always works. -- good luck, SP
Re: Got sound going on a U60 debian smp
On Mon, 2004-11-08 at 17:10, Carl Wharehinga wrote: dear list members, Has anyone managed to get sound going on there U60. I cant :( but would like to. currently I am running 2.4.24-sparc64-smp kernel. I have tried with some standard PCI sound cards besides the on-board one but would prefer to use the on-board if this works. Any help would be appreciated What are the failure symptoms and what PCI cards have you tried? A U60's onboard sound does work with Linux; and the modules provided with the Sparc64 2.4 kernel suggest that two types of PCI soundcards should work: ones based on a particular Trident chipset and ones based on a chipset used in Creative Soundblaster PCI and possibly Ensoniq Audio PCI cards. For onboard sound have you done modprobe cs4231 or added cs4231 to /etc/modules ? Have you set the PARAMS variable PARAMS=play.port=line_out in /etc/default/audioctl ? In any Debian install a user account has to be a member of the audio group for the mixer or playback to work for that user. The mixer's volume level may default to 0. -- SP -- === Carl Wharehinga SolNet Solutions 70 The terrace, Wellington DDI:+64 4 462-5042 Mobile:+64 21 899-074 Fax:+64 4 462-5012 Attention: This email may contain information intended for the sole use of the original recipient. Please respect this when sharing or disclosing this email's contents with any third party. If you believe you have received this email in error, please delete it and notify the sender or [EMAIL PROTECTED] as soon as possible. The content of this email does not necessarily reflect the views of SolNet Solutions Ltd.
