On Sat, Dec 31, 2016 at 10:11:45AM +, Maciej W. Rozycki wrote:
> (...)
> You need to keep the `*(.alphalib)' line only, i.e. drop the first and
> the last line added by the patch, as the output section statement and its
> curly braces surrounding input section specifiers are already
On Sat, Dec 31, 2016 at 12:43:37AM -0600, Bob Tracy wrote:
> On Fri, Dec 30, 2016 at 10:07:06PM +0100, Helge Deller wrote:
> > (...)
> > Another possibility could be to put all the lib functions into
> > a "alphalib" section into the final vmlinux.
> > For
On Fri, Dec 30, 2016 at 10:07:06PM +0100, Helge Deller wrote:
> (...)
> Another possibility could be to put all the lib functions into
> a "alphalib" section into the final vmlinux.
> For that add at the top of each of the .S files in lib/
> .section .alphalib,"ax"
> and apply the attached
On Thu, Dec 29, 2016 at 10:23:04PM -0500, Matt Turner wrote:
> FWIW, when I saw your first email I tried compiling with gcc-4.9.4,
> 5.4.0, and 6.2.0. All compiled my config fine.
That's worth quite a bit to me, actually :-). Tells me that downgrading
my toolchain is probably a waste of time and
I'm guessing this is Alpha-specific at the moment, because I'm getting a
world-class lettin' alone from the kernel developers.
Saw another binutils update come through a couple of days ago, so tried
another from-scratch kernel build. No change in the outcome. This
"smells" like a gcc or
r any help in resolving this.
--Bob
On Tue, Dec 13, 2016 at 08:07:10AM -0600, Bob Tracy wrote:
> Got all the way to the end of the 4.9-final kernel build, and ran into the
> following:
>
> LD init/built-in.o
> arch/alpha/lib/lib.a(strcat.o): In function `strcat':
> (.text
On Wed, Apr 20, 2016 at 01:46:13AM +0100, Maciej W. Rozycki wrote:
> I can see if I can find anything suspicious there if you send me original
> copies (i.e. those that oopsed) of arch/alpha/kernel/irq_alpha.o and
> arch/alpha/kernel/core_cia.o.
>
> > Machine has been stable since the machine
On Mon, Apr 18, 2016 at 09:52:43PM -0500, Bob Tracy wrote:
> 4.6.0-rc4 build complete, including suggested (by Alan Young) "Verbose
> Machine Checks" option set to level 2 by default. System rebooted, and
> now we wait... Thanks for everyone's continued patience.
W
On Mon, Apr 18, 2016 at 02:47:40PM +0100, Maciej W. Rozycki wrote:
> On Mon, 18 Apr 2016, Bob Tracy wrote:
>
> > Build delayed slightly. Ran into "fs/binfmt_em86.o" build failure
> > patched by Daniel Wagner back in February (incompatible-pointer-types
> > wa
On Sun, Apr 17, 2016 at 10:58:48PM -0500, Bob Tracy wrote:
> On Mon, Apr 18, 2016 at 02:32:54AM +0100, Maciej W. Rozycki wrote:
> > I'd be tempted to run with the patch below to see what's the value of
> > `la_ptr' early on in processing (`entInt' code in entry.S looks sane to
Apologies in advance for the "poor" quality of this bug report. No idea
how to proceed, because the issue historically has been intermittent to
non-existant for reasons unknown.
Within 24 hours of booting my Alpha (PWS 433au), I'm pretty much
guaranteed to see a "machine check" Oops which
On Fri, Mar 04, 2016 at 02:52:09PM +0100, Julien Cristau wrote:
> On Fri, Mar 4, 2016 at 07:45:36 -0600, Bob Tracy wrote:
>
> > The subject system has been unreachable for at least the past 12 hours.
> > Scheduled maintenance? Hardware failure? Backhoe-induced network
&
The subject system has been unreachable for at least the past 12 hours.
Scheduled maintenance? Hardware failure? Backhoe-induced network
outage or power failure?
--Bob
On Wed, Feb 24, 2016 at 08:27:42PM +1300, Michael Cree wrote:
> On Tue, Feb 23, 2016 at 12:23:44PM -0500, Alex Winbow wrote:
> > On Sat, 20 Feb 2016, Helge Deller wrote:
> >
> > >On 20.02.2016 08:41, Michael Cree wrote:
> > >>On Sat, Feb 20, 2016 at 12:09:49AM -0500, Alex Winbow wrote:
> > >>>
(Comments below apply to the "unstable/sid" version of Debian.)
The subject program has a rather sizable memory leak on Alpha. Stuff
starts breaking due to the OOM condition (USB device driver loads fail
with paging errors), and "top" confirms "packagekitd" consuming a
disproportionate share of
On Wed, Dec 09, 2015 at 10:19:16PM -0600, Bob Tracy wrote:
> The subject program has a rather sizable memory leak on Alpha.
Here's a link to a relevant bug report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802306
Also, it does no good to stop the packagekit service: it simply resta
Unrelated to the specific upgrade issues, there's a larger problem with
Debian since the switch to "systemd". Namely, if any upgrade touches
something controlled by "systemd", the odds of being able to do a clean
shutdown/reboot drop to approximately zero: the shutdown process hangs
due to
On Wed, Sep 16, 2015 at 10:26:03PM +1200, Michael Cree wrote:
> kdepim is now built.
Wonderful!
Still working on our issues with getting glib2.0 built. As you
mentioned in a separate message, the official build environment
doesn't include "gdb", so "run-assert-msg-test.sh" exits cleanly without
On Sat, Sep 12, 2015 at 02:21:25PM +1200, Michael Cree wrote:
> glib2.0 FTBFS (test-suite failures) and is holding up Gnome. If you
> could work your magic on that one too I would be mightily pleased!
I got lucky with "cmake". Let's see if lightning will strike twice :-).
--Bob
On Fri, Sep 11, 2015 at 10:43:24AM +0100, Simon Brown wrote:
> Thanks Bob, What was the fix?
Quick answer: see the discussion at bugs.debian.org for bug 789807.
Somewhat longer answer... On alpha, and maybe other architectures,
there's no guarantee that the byte in front of a character array is
Getting the dependencies for "kde-baseapps" built would be a huge help
in trying to clear what is now a 278-package backlog of held packages
on my local system.
Also would love to see the build dependencies for the "kdepim" source
package satisfied: that's a big part of the KDE upgrade mess.
On Fri, Sep 11, 2015 at 07:33:21PM +1200, Michael Cree wrote:
> On Thu, Sep 10, 2015 at 12:05:54AM -0500, Bob Tracy wrote:
> > On Tue, Sep 08, 2015 at 07:56:29AM +1200, Michael Cree wrote:
> > > The main problem is
> > > that cmake FTBFS (Bug #789807) thus a growing prop
On Tue, Sep 08, 2015 at 07:56:29AM +1200, Michael Cree wrote:
> The main problem is
> that cmake FTBFS (Bug #789807) thus a growing proportion of the
> archive is unbuildable on Alpha.
See your private e-mail. I may have a handle on this beast. Won't
burden the rest of the list with my
With unstable, this happens from time to time. At the moment, I've
got 203 held packages as follows:
apt apt-utils aptitude aptitude-common build-essential cdrdao
cheese-common cmake-data cpp cups-filters cups-filters-core-drivers
ecj ecj-gcj epiphany-browser-data evince-common evolution-common
On Mon, Jun 01, 2015 at 11:42:45AM +0200, Helge Deller wrote:
(...)
Other than that I noticed that I'm unable to boot the linux-4.0 debian kernel
on my machine. Anyone has observed that too?
aboot messages:
aboot b vmlinuz-4.0.0-2-alpha-generic ro root=/dev/sda3 console=ttyS0
aboot:
On Sat, Feb 28, 2015 at 08:45:38AM +0100, Helge Deller wrote:
I've prepared some installation medias for
DEBIAN 8.0 on ALPHA (debian-ports unstable release!)
Thank you for making these available! I was dreading the day I might
have to do a from scratch install after a catastrophic hardware
A quick look around shows new packages for Alpha showing up on the
server, but debian/dists/unstable/Contents-alpha.gz (and the Contents
files for several other architectures as well) is empty.
Is there an estimated time to repair? Thanks in advance...
--Bob
--
To UNSUBSCRIBE, email to
Dang fingers... Don't work so well this early in the morning. Subject
should have been as for *this* message.
On Wed, Dec 10, 2014 at 08:16:16AM -0600, Bob Tracy wrote:
A quick look around shows new packages for Alpha showing up on the
server, but debian/dists/unstable/Contents-alpha.gz
On Fri, Jul 04, 2014 at 07:18:23PM +1200, Michael Cree wrote:
On Fri, Jul 04, 2014 at 12:12:45AM -0500, Bob Tracy wrote:
Is there a reason the subject package isn't available in the debian-ports
archive for alpha? The build logs say everything built properly at least
128 days ago
Is there a reason the subject package isn't available in the debian-ports
archive for alpha? The build logs say everything built properly at least
128 days ago, and the package is a dependency for several KDE packages
currently being held back in my installation queue.
I'll try to roll my own in
On Wed, Jun 04, 2014 at 10:39:00PM +1200, Michael Cree wrote:
On Wed, Jun 04, 2014 at 01:05:20PM +0300, m...@ukr.net wrote:
First of all I'm the one shouting for instructions about how to
install ble eding edge Debian Sid on alpha
I still have a draft copy of the instructions. Might be a
It could be as simple as liblogging-stdlog0 not having been put in the
queue to build, but the upgrade of rsyslog to version 7.6.2-1 is being
held pending the availability of the liblogging-stdlog0 package. The
liblogging package builds fine locally.
While I'm on your screens, the list of held
Seeing this on alpha also. Kernel version 3.12.0-rc1.
Is a fix similar to what Geert submitted for m68k appropriate here?
See http://marc.info/?l=linux-archm=137820065929216w=2 for the
details.
--Bob
--
To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org
with a subject of
On Sun, Aug 25, 2013 at 04:52:48PM +1200, Michael Cree wrote:
I also noted in the changelog of the recent upload to debian-ports of the
xserver radeon video driver a comment to the effect that KMS is now only
supported. This may be problematic to anyone running a radeon card, a
stock standard
Just a heads-up, since many Alpha users have Radeon cards... If you
have KMS enabled and you're experimenting with the latest 3.11.0-rcX
kernels, you probably want to grab an up-to-date snapshot of at *least*
the radeon firmware subdirectory.
The kernel firmware repository is available at
I suddenly went from approx. 13 updates held back to nothing available.
Site hardware failure of some kind?
--Bob
--
To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
On Wed, Aug 14, 2013 at 08:29:05PM +1200, Michael Cree wrote:
I have just installed the cinnamon desktop to try it out and it pulled in
gnome-settings-daemon and, guess what, the bug is still there. It still
crashes. I remember this bug: it crashes when trying to load a plugin.
I saw it two
On Sat, Jul 27, 2013 at 06:26:58PM +1200, Michael Cree wrote:
gdm3 has just been built on Alpha and I am now uploading it to Debian-Ports.
It might take half a day or so to appear on the mirrors.
Grabbed it. Thanks.
Would be interesting to see if #681195 is fixed though I see that the last
I've reached an impasse as far as being able to apply further updates to
my Debian unstable system. Not sure if there are any updates planned
for gdm3, but all of the pending (held back) gnome updates seem to
require removal of gdm3. I note the availability of a gdm
compatibility package
On Mon, Jul 15, 2013 at 07:15:09AM +1200, Michael Cree wrote:
gdm3 has not been buildable on Alpha for more than 39 days because its build
dependencies are not satisfied.
But was gdm3 even working for you? It was crashing last year and I filed
a bug report but I was not aware of it being
On Fri, Aug 17, 2012 at 11:04:14PM +1200, Michael Cree wrote:
On 28/04/12 09:32, Bob Tracy wrote:
On Fri, Apr 27, 2012 at 12:42:10PM +1200, Michael Cree wrote:
I am fairly certain that the crash is this:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660960
The backtraces I got all
On Mon, Jun 25, 2012 at 06:57:06PM -0500, Bob Tracy wrote:
(...)
On the original subject of USB cards, it turns out my other USB card is
simply a later revision of the same VIA card that doesn't work, and the
later rev doesn't work either. Time to go find a NEC chipset USB card.
Found one
On Mon, Jun 25, 2012 at 12:28:19AM -0500, Bob Tracy wrote:
I'll see about getting another video card to try. Any recommendations
as far as something that will support 1280x1024x24 on a PWS? In the
meantime, I can try backing off the resolution to 1024x768x24 to see if
that makes
On Mon, Jun 25, 2012 at 01:34:51AM -0500, Bob Tracy wrote:
On Mon, Jun 25, 2012 at 12:28:19AM -0500, Bob Tracy wrote:
I'll see about getting another video card to try. Any recommendations
as far as something that will support 1280x1024x24 on a PWS? In the
meantime, I can try backing
On Sun, Jun 24, 2012 at 04:42:39PM +1200, Michael Cree wrote:
Oh! A VIA USB card. I had a USB card recovered from a PC at work that
proved unreliable in the PWS and the XP1000 and my recollection is that
it had a VIA chipset. I thought the card must be faulty, but maybe
there really is a
On Sun, Jun 24, 2012 at 09:23:43AM +0200, Uwe Schindler wrote:
I had a NEC controller also running perfect!
That's two votes for the NEC.
I tried removing the VIA controller this evening to see if that fixed my
video issues: it didn't :-(. I don't know if something is permanently
damaged, or
On Mon, Jun 25, 2012 at 12:02:40AM -0500, Bob Tracy wrote:
I tried removing the VIA controller this evening to see if that fixed my
video issues: it didn't :-(.
(...)
I'll see about getting another video card to try. Any recommendations
as far as something that will support 1280x1024x24
I recently retired an old AMD K6-III/450 system that had a serviceable
USB controller in it, so I tried transplanting it to my Alpha. The
kernel seems to detect it just fine and load the appropriate drivers,
but there's evidently a conflict of some kind between the USB card and
my Radeon 7500.
On Sun, Jun 24, 2012 at 11:59:15AM +1200, Michael Cree wrote:
On 23/06/12 18:43, Bob Tracy wrote:
I recently retired an old AMD K6-III/450 system that had a serviceable
USB controller in it, so I tried transplanting it to my Alpha. The
kernel seems to detect it just fine and load
On Sat, Jun 23, 2012 at 08:35:38PM -0500, Bob Tracy wrote:
On Sun, Jun 24, 2012 at 11:59:15AM +1200, Michael Cree wrote:
On 23/06/12 18:43, Bob Tracy wrote:
I recently retired an old AMD K6-III/450 system that had a serviceable
USB controller in it, so I tried transplanting it to my Alpha
On Tue, May 29, 2012 at 05:44:01PM +1200, Michael Cree wrote:
I see the latest src:shadow package (version 1:4.1.5.1-1) includes the
following in the changelog:
* New upstream release:
- login: log into utmp(x) but not into wtmp (this is done by
pam_lastlog). Log to utmp(x) was broken
On Sat, Apr 28, 2012 at 08:59:52PM +1200, Michael Cree wrote:
The alpha specific ipc patch in bug 650151 [1] has been applied, and
interestingly there were no GPREL16 relocation errors in linking despite
absence of --no-relax during linking, as far as I can tell from the
build log.
It
On Fri, Apr 27, 2012 at 12:42:10PM +1200, Michael Cree wrote:
I am fairly certain that the crash is this:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660960
The backtraces I got all ended in madvise() --- which is what the bug
report is about.
The available facts fit the theory, so
On Sat, Apr 28, 2012 at 11:08:12AM +1200, Michael Cree wrote:
OK, I'll see if I can do a manual build of iceweasel 12.0 this weekend.
I won't build the latest version in unstable as there is no point in
building a version that still has the madvise() lockup bug.
The 12.0 code base *probably*
On Mon, Feb 27, 2012 at 05:33:34PM +1300, Michael Cree wrote:
On 27/02/2012, at 5:13 PM, Bob Tracy wrote:
On Sun, Feb 26, 2012 at 02:30:16PM +1300, Michael Cree wrote:
I've also just upgraded to iceweasel 10.0.2-1+alpha and have it
running
on the xfce4 desktop. It worked for a while reading
On Sun, Apr 01, 2012 at 10:26:03PM -0500, Bob Tracy wrote:
On Sat, Mar 31, 2012 at 11:40:30PM -0500, Bob Tracy wrote:
On Sun, Apr 01, 2012 at 01:07:20PM +1200, Michael Cree wrote:
Note that qt4-x11 at version 4.7.4-3 has just been built and is now
installed at debian-ports. You might
On Tue, Apr 24, 2012 at 10:08:41AM +1200, Michael Cree wrote:
On 24/04/2012, at 9:18 AM, Bob Tracy wrote:
Happy day! KDE is now working again, at least remotely (NX session).
I'll try a console session later as time permits.
Nice.
Any idea what the culprit was?
No idea whatsoever
On Sat, Mar 31, 2012 at 11:40:30PM -0500, Bob Tracy wrote:
On Sun, Apr 01, 2012 at 01:07:20PM +1200, Michael Cree wrote:
Note that qt4-x11 at version 4.7.4-3 has just been built and is now
installed at debian-ports. You might like to try upgrading to see if
that makes any difference
On Sun, Apr 01, 2012 at 01:07:20PM +1200, Michael Cree wrote:
Note that qt4-x11 at version 4.7.4-3 has just been built and is now
installed at debian-ports. You might like to try upgrading to see if
that makes any difference.
Grabbing the updated packages now... I'll let you know.
Unrelated
I don't know exactly when things broke, as it has been a good while
since I've had the time to do much with the Alpha. (Been trying to
retire a K6-III/450 system for a while, and finally got moved into an
i7-2600S. Yes, I like it :-)). Both plasma-desktop and kderunner are
crashing during
A recent update broke updating of /var/run/utmp -- /run/utmp.
who returns nothing and exits with a status of 0. who -a shows all
the virtual consoles at LOGIN state, the correct system boot time, and
the correct current run-level.
last seems to be working correctly, so wtmp is fine.
Anyone else
On Sun, Feb 26, 2012 at 02:30:16PM +1300, Michael Cree wrote:
I've also just upgraded to iceweasel 10.0.2-1+alpha and have it running
on the xfce4 desktop. It worked for a while reading a few web pages, but
has now locked up and it using whatever spare CPU it can take. I can
still use the
On Mon, Feb 27, 2012 at 05:54:52PM +1300, Michael Cree wrote:
(...) I do have a
Radeon HD4350 card installed and it's great to see the modern features
exploited. I am not sure how smoothly and prettily it will run with
an older 7000 series Radeon card.
Compositing was/is an issue with
On Fri, Feb 24, 2012 at 11:44:29PM -0600, Bob Tracy wrote:
On Sat, Feb 25, 2012 at 06:08:52PM +1300, Michael Cree wrote:
There is a new version, 10.0.2-1+alpha, accepted into debian-ports
unreleased about 24 hours ago. Please try that.
Just noticed it. Downloading/installing now, along
The subject version of iceweasel hangs while trying to load the default
Google search page. The prior version worked fine. The kernel mutex
fix for the pulseaudio issue seems to be valid: my firefox-8 build
didn't crash when I clicked on the main pull-down menu (upper-left of
the firefox
On Fri, Feb 24, 2012 at 10:28:43PM -0600, Bob Tracy wrote:
The subject version of iceweasel hangs while trying to load the default
Google search page. The prior version worked fine. The kernel mutex
fix for the pulseaudio issue seems to be valid: my firefox-8 build
didn't crash when I
On Sat, Feb 25, 2012 at 06:08:52PM +1300, Michael Cree wrote:
There is a new version, 10.0.2-1+alpha, accepted into debian-ports
unreleased about 24 hours ago. Please try that.
Just noticed it. Downloading/installing now, along with a udev update.
This will be the first one of *those* I
On Sun, Feb 19, 2012 at 11:45:53AM +1300, Michael Cree wrote:
So how is Gnome3 for you?
It always starts up in fallback mode for me. I do have radeon KMS
runnning, but mesa is using the software DRI renderer. That might be
why it starts in fallback mode.
Ahh, that's because I am
There have been libjpeg62 and libjpeg62-dev updates held back for many
months due to dependency issues. In particular, when I tried
apt-get install libjpeg62 libjpeg62-dev this morning to check the
current status, I got the following proposed removals:
libcupsimage2-dev libdirectfb-dev
On Sat, Feb 18, 2012 at 07:59:13AM +1300, Michael Cree wrote:
Why are you trying to install libjpeg62? Almost everything now depends
on libjpeg8.
Ah... libjpeg62 *is* the cruft :-). I installed libjpeg8-dev, and
the dam burst: more updates are now applying.
--Bob
--
To UNSUBSCRIBE, email
On Sun, Feb 12, 2012 at 02:37:44PM +1300, Michael Cree wrote:
You may have noticed that we have the majority of the unstable
distribution (was over 95% a week ago) built at Debian-Ports. It is
reasonably up-to-date with many problems in the toolchain fixed, the
kernel up to date, Gnome 3 built
On Sun, Feb 12, 2012 at 03:56:41PM -0600, Bob Tracy wrote:
Got a new bug I need to file against the radvd package: the radvd
process ID stored in /var/run/radvd/pid is the predecessor of two child
processes that get spawned (and detach: ppid == 1). Thus, init level
changes don't work
On Wed, Jan 25, 2012 at 09:43:03PM +1300, Michael Cree wrote:
On 25/01/12 20:24, Bob Tracy wrote:
On Mon, Jan 23, 2012 at 07:23:50PM +1300, Michael Cree wrote:
The udev problem with the missing accept4 syscall on Alpha is now fixed.
ACK. Upgrading libc6.1 (and other packages) as I type
On Mon, Jan 23, 2012 at 07:23:50PM +1300, Michael Cree wrote:
The udev problem with the missing accept4 syscall on Alpha is now fixed.
ACK. Upgrading libc6.1 (and other packages) as I type this. Thanks for
pushing through an updated kernel.
--Bob
--
To UNSUBSCRIBE, email to
On Wed, Dec 14, 2011 at 11:04:11PM +0100, Pino Toscano wrote:
(KDE4 causing hard system lockups/freezes during console
sessions, but not FreeNX sessions.)
Hm I see.
My next hint would be try to disable the compositing of kwin (the window
manager), maybe it somehow detects it is available
On Mon, Dec 05, 2011 at 11:18:46AM -0600, Bob Tracy wrote:
The recent upgrade to console-common (version 0.7.86) is badly broken.
(...)
console-common 0.7.87 is now available, together with a compatible
initscripts upgrade. The upgraded packages install cleanly: it is
safe to remove the hold
Maybe I missed it, but was there a solution (or at least an
explanation) for the gcc-4.6 kernel build issue where we were getting
GPREL16 errors when using the -msmall-data flag?
--Bob
--
To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
On Wed, Dec 14, 2011 at 08:02:32PM +1300, Michael Cree wrote:
On 13/12/11 01:58, Bob Tracy wrote:
Wonderful news concerning gcc/g++-4.6, and I think rebuilding several of
our (Alpha's) more questionable packages would be a worthwhile
exercise.
We are now defaulting to gcc-4.6 on Alpha
On Mon, Dec 12, 2011 at 09:34:05PM +1300, Michael Cree wrote:
Bob, I've just recompiled iceweasel and icedove with gcc-4.6 and full
optimisation (other than --no-relax in the linker) and the crashes in
those two packages have disappeared. I am sending this message with
icedove from my
On Sat, Dec 10, 2011 at 08:03:46PM +0100, Pino Toscano wrote:
If it's the virtuoso process to create issue, you can try disabling the
semantic desktop (which uses the virtuoso DB): either you uninstall the
virtuoso packages, or disable nepomuk for your user in a console with:
$ kwriteconfig
Armed with nearly three times the RAM I used to have, I screwed up my
courage and tried a plasma-desktop session on the console. It locked up
the machine as it did on all prior attempts, but now that the machine
isn't paging itself to death, it seems easier to start narrowing down
cause and
I'm not normally inclined to give any vendor free advertising, but
reasonably priced RAM upgrade options for one of our systems of choice
are getting hard to find, so please accept this recommendation in that
spirit. 18004memory.com is currently selling a 2x256MB kit on eBay for
US$25: PC66 ECC
On Thu, Dec 08, 2011 at 12:14:04PM -0500, Lennart Sorensen wrote:
Any particular model number on the site? My previous attempt to buy
ram for my PWS didn't work out (it doesn't like the ram).
Here's the link to the eBay listing:
The recent upgrade to console-common (version 0.7.86) is badly broken.
Lots of resulting initscript / service script loops that will prevent
your machine from booting after the upgrade. See Debian bugs #650995
and #651000 for the gory details.
Until a version 0.7.86 is available, place a hold
I don't suppose the fact that the major graphical environments are less
than svelte is much of a revelation, but if people are wanting to run
them on older hardware, it's presumably useful to know at least roughly
what the minimum hardware requirements are. Anyway, here's another
data point for
No contest: the -O1 version runs *much* faster on my PWS 433au. I still
don't trust the optimizer, but the performance gains are too great to ignore.
Well done, Michael!
--Bob
--
To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
On Sun, Nov 27, 2011 at 01:19:57PM +1300, Michael Cree wrote:
As I understand it -O1 only turns on straightforward optimisations such
as keeping often used local variables in CPU registers. On a CPU with
many registers, such as the Alpha, this gives a huge performance lift.
I presume you
On Sun, Nov 27, 2011 at 01:34:55PM +1300, Michael Cree wrote:
On 26/11/11 17:05, Bob Tracy wrote:
Might have to have you crank out an official -O0 or
-O1 build of QT4 so I can release the hold on 25 binary packages.
OK, I'll take a look at that one. I presume you mean qt4-x11
On Sun, Nov 27, 2011 at 04:42:17AM +, Matt Turner wrote:
Hardly worth it. There's no upgrade for a PWS that's going to make it fast.
Fast is relative. Besides, if nearly tripling the amount of RAM in my
system can eliminate even a little of the paging I'm seeing during
larger package
On Fri, Nov 25, 2011 at 09:23:01PM +1300, Michael Cree wrote:
...
2) Set optimization to use -O1 not -O2.
3) Now this one is *very* *interesting*. I added -Wl,--no-relax to
LDFLAGS in debian/rules, but I think I got it wrong, because --no-relax
did not appear anywhere in the logs, i.e.,
On Sat, Nov 26, 2011 at 01:49:21PM +1300, Michael Cree wrote:
On 26/11/11 01:20, Bob Tracy wrote:
:-). There was a recent binutils upgrade. I wonder...
No, binutils is not fixed. The GPREL16 relocation error still occurs
with other packages. I suspect the use of -O1 may cause
On Thu, Nov 24, 2011 at 09:52:16PM +1300, Michael Cree wrote:
On 24/11/11 04:06, Bob Tracy wrote:
On Tue, Nov 22, 2011 at 04:12:53PM -0600, Bob Tracy wrote:
Search for #649641: pulseaudio mutex issue on Alpha architecture.
The workaround mentioned in the report for ARM also works
On Fri, Nov 25, 2011 at 06:43:06PM +1300, Michael Cree wrote:
On 25/11/11 17:25, Bob Tracy wrote:
BEWARE the recent udev upgrade: it suffers from the same problem as
the previous version -- the stubbed-out syscalls.
The problem is not in udev.
That's a technicality :-). udev was built
On Tue, Nov 22, 2011 at 04:12:53PM -0600, Bob Tracy wrote:
Search for #649641: pulseaudio mutex issue on Alpha architecture.
The workaround mentioned in the report for ARM also works for Alpha.
I'll leave it to a package maintainer to explain why :-).
Anyway, pulseaudio mutex failures
Search for #649641: pulseaudio mutex issue on Alpha architecture.
Let's hope this gets addressed: it's getting really difficult to test
new browser builds otherwise.
--Bob
--
To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
On Wed, Nov 16, 2011 at 04:16:54PM -0600, Bob Tracy wrote:
The subject release appeared less than a day ago, so it seemed like a
good time to try out gcc/g++-4.6. Will try a non-optimized build
without the nsThreadUtils* patches to see how that goes. When I last
tried such a build (version
On Tue, Nov 15, 2011 at 11:55:59PM -0600, Bob Tracy wrote:
(...)
Separate from the optimizer issue, KMS bugs apparently *not* specific to
Alpha are being seen by others, and they are seeing black screens, system
freezes, etc., same as I am.
Bottom line: I have high hopes of having a working
Source: qt4-x11
Version: 4:4.7.3-8
Severity: important
Tags: patch
Dear Maintainer,
Due to a bug in the g++-4.4 optimizer, the normal -O2 build of qt4-x11
binary packages results in segfaults on the alpha architecture when apps
are run that use the qt4 libraries. This includes kdm and the KDE4
Our old friend is back:
Assertion 'pthread_mutex_unlock(m-mutex) == 0' failed at
pulsecore/mutex-posix.c:106, function pa_mutex_unlock(). Aborting.
An easy way to reproduce: run either firefox or iceweasel, then click on
the drop-down menu in the upper-left corner -- the application
immediately
The subject release appeared less than a day ago, so it seemed like a
good time to try out gcc/g++-4.6. Will try a non-optimized build
without the nsThreadUtils* patches to see how that goes. When I last
tried such a build (version 4.0.1), I got segfaults until I put the
nsThreadUtils* patches
101 - 200 of 386 matches
Mail list logo
