Re: [RFH] Update of Debian Installer for 2.6.29
Jurij Smakov wrote:
On Tue, Apr 21, 2009 at 09:51:56PM -0300, Otavio Salvador wrote:
Hello arch porters,
Most arches has 2.6.29 packages ready (AFAIK only hppa lacks them
right now) and I also did most changes for all arches on SVN to get
2.6.29 updating as easy as possible. Now, we need porters' help.
Please check your pet arch and update the kernel and modules for
2.6.29. This is quite important to us to start testing installer with
this kernel.
Well, 2.6.29 does not even boot on my SunBlade 1000, failing early in
the boot process:
I guess you found the culprit in the mean time (bad config for the 64bit
kernel)?
Cheers
Luk
Rebooting with command: boot
Boot device: disk File and args:
SILO Version 1.4.13
boot:
Allocated 8 Megs of memory at 0x4000 for kernel
Kernel doesn't support loading to high memory, relocating...done.
Loaded kernel version 2.6.29
Loading initial ramdisk (6348059 bytes at 0x40 phys, 0x40C0 virt)...
ERROR: Last Trap: Fast Data Access MMU Miss
Error -256
{0} ok
2.6.26 boots fine under the same conditions.
--
To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: debian unusable on niagara
On Mon, Apr 27, 2009 at 06:41:52PM -0700, David Miller wrote: I downloaded the tftpboot image provided from the Download section of the debian.org web site for Sparc. Can you provide the exact URL? My worry is that you might have downloaded one of the daily-built images, which may be in various states of brokenness. The Lenny netboot image is at http://ftp.nl.debian.org/debian/dists/lenny/main/installer-sparc/current/images/netboot/boot.img The bug I've mentioned, and which should be resolved in this image, is http://bugs.debian.org/504721. I see, however, that we never got a confirmation from the original reporter that the fix worked on his machine (it did work for mine). I've tested the lenny installer and it worked correctly with serial console (I remember we pushed some fixes for it pretty late in lenny release cycle). It's not exactly a serial console, even though the niagara console is implemented using a driver that sits on top of the serial core layer. If you test on a non-niagara system with serial console, it's not the same test. Not even remotely. The device name is different, it shows up differently in sysfs, etc. I believe we fixed it in Lenny r1 release, it would be great to it if you could upgrade to it and confirm it (or install from scratch using 5.0.1 media from http://www.debian.org/releases/lenny/debian-installer). I'll give it a try and report back. Thanks. -- Jurij Smakov ju...@wooyd.org Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: debian unusable on niagara
On Tue, Apr 28, 2009 at 12:57:12AM -0700, David Miller wrote: From: Jurij Smakov ju...@wooyd.org Date: Tue, 28 Apr 2009 08:54:07 +0100 The bug I've mentioned, and which should be resolved in this image, is http://bugs.debian.org/504721. I see, however, that we never got a confirmation from the original reporter that the fix worked on his machine (it did work for mine). So what is your system exactly? Is it a niagara box? It's a SunBlade 1000, but the symptoms described in this bug (reporter's box was Niagara) were the same on it, so I assumed that fixing it for my box fix it for Niagara as well (which is not necessarily true). -- Jurij Smakov ju...@wooyd.org Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: debian unusable on niagara
From: Jurij Smakov ju...@wooyd.org Date: Tue, 28 Apr 2009 08:54:07 +0100 The bug I've mentioned, and which should be resolved in this image, is http://bugs.debian.org/504721. I see, however, that we never got a confirmation from the original reporter that the fix worked on his machine (it did work for mine). So what is your system exactly? Is it a niagara box? -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: debian unusable on niagara
From: Jurij Smakov ju...@wooyd.org Date: Tue, 28 Apr 2009 09:09:34 +0100 On Tue, Apr 28, 2009 at 12:57:12AM -0700, David Miller wrote: From: Jurij Smakov ju...@wooyd.org Date: Tue, 28 Apr 2009 08:54:07 +0100 The bug I've mentioned, and which should be resolved in this image, is http://bugs.debian.org/504721. I see, however, that we never got a confirmation from the original reporter that the fix worked on his machine (it did work for mine). So what is your system exactly? Is it a niagara box? It's a SunBlade 1000, but the symptoms described in this bug (reporter's box was Niagara) were the same on it, so I assumed that fixing it for my box fix it for Niagara as well (which is not necessarily true). It won't, most likely because the device name is totally different for Niagara's console device vs. the serial console device used on all other types of boxes. -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: X/GDM fails on Ultra 10 w/ Creator 3D under Lenny
Chris Andrew wrote: I have exactly the same problem from an install today. I've got the same problem on a U1 with cgsix that was running Lenny (KDE desktop) without problems until I did a routine upgrade a few days ago. This appears affect not only the local screen but also VNC servers and XDMCP, so the machine is effectively a brick. Has anybody raised a bug? If there's a way of reverting the offending change can somebody post a URL or an idiot's guide please. -- Mark Morgan Lloyd markMLl .AT. telemetry.co .DOT. uk [Opinions above are the author's, not those of his employers or colleagues] -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
FTBFS on sparc: __sync_test_and_add_4
Hi sparc porters. I'm writing to ask for your assistance on a FTBFS on my package csound on sparc. The build log is here[1]. The failure is the following: libCsoundAC.so.5.2: undefined reference to `__sync_fetch_and_add_4' Csound uses __sync_lock_test_and_set for spinlocks, and tests for their existence at build time to use them. Sparc's gcc apparently provides said function, since the test succeeds, but I'm getting the above failure (note that __sync_fetch_and_add_4 is nowhere mentioned in the csound sources). What is a possible cause for this? I don't have access to sparc machines so I'm kind of unsure what to do here. Note that csound uses -Wl,--as-needed for most of its libraries. Please CC me on replies, I'm not suscribed. [1] https://buildd.debian.org/fetch.cgi?pkg=csoundver=1%3A5.10.1%7Edfsg1-2arch=sparcstamp=1240144021file=log Saludos, Felipe Sateler -- To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
