Just in case, I have tried turning off HPET (this hardware does not have
any of those timers anyway). There is no change. The bug is as before.
This refers to http://archives.mandrivalinux.com/cooker/2006-01/msg03794.php
ael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject
I have applied the timer.c patch
https://bugtrack.alsa-project.org/alsa-bug/file_download.php?file_id=963type=bug
from
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1645
to a 2.6.18.3 kernel. The situation is exactly as before. aplaymidi
blocked and chronyd showing high CPU usage as
John Hasler wrote:
Edit /etc/chrony/chrony.conf and comment out the line
rtcfile /var/lib/chrony/chrony.rtc
This should allow Chrony to operate without interfering with your Midi
stuff.
Confirmed. I had forgotten to look in there. But this is a workaround
rather than a bug
John Hasler wrote:
Confirmed. I had forgotten to look in there. But this is a workaround
rather than a bug identification and fix isn't it?
Yes, it's just a workaround.
Well, thanks anyway. I guess that we don't even know if the problem is
with chronyd or with alsa or something more generic
Sorry, either I didn't receive your email or I deleted it somehow
without reading it. But you asked (in 400499):
forgot to ask if there was anything interesting in the Chrony logs.
The answer is: not as far as I can see.
A E Lawrence
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
Subject: alsa-utils: aplaymidi plays but 1 note: conflict with chrony
Package: alsa-utils
Version: 1.0.11-3bpo1
Severity: normal
*** Please type your report below this line ***
aplaymidi plays only the first note of a midi file. Strace shows that it
stops after
ioctl(3,
John Hasler wrote:
On 2.6.19, however chronyd does not show any unusual activity as shown by
top.
But aplaymidi still doesn't work?
Correct. It still blocks, snd_rtctimer, presumably. I haven't tried
attaching an gdb session to chronyd under 2.6.19, but could do so it it
is useful.
ael
Elimar Riesebieter wrote:
reassign 400499 chrony
thanks
On Mon, 04 Dec 2006 the mental interface of
ael told:
I suggest that this bug now be registered against chrony which appears
to be the cause of the problem.
done
Thank you for your excellent investigation ;)
Well, I haven't
John Hasler wrote:
Please look at this:
http://archives.mandrivalinux.com/cooker/2006-01/msg03794.php
I will also see if I can apply and test the timer.c.patch from
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1645
Looks as if it may be an alsa problem after all :-) I guess this
John Hasler wrote:
Please look at this:
http://archives.mandrivalinux.com/cooker/2006-01/msg03794.php
Interesting: as I write I am compiling a version of 2.6.18.3 with HPET
turned off. I wonder if chronyd was running there? I hope I have copied
in the reporter: perhaps he/she can tell us?
A E
xserver-xorg-input-joystick-1:1.1.0-1 seems to be completely broken as
reported here: I hit the same bug on 2 completely different machines,
one i386 and the other amd64 architecture.
Upstream appear to have extensively patched and presumably fixed the
problem on 13/3/2007. Any chance of a new
is not included in any of the binary
packages.
Surely grub2-documenation or some such should exist containing this manual?
Then grub2 might become useable?
Meanwhile, I guess people have to get the source and run tex2dvi on grub.texi
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ
Package: grub-rescue-pc
Version: 1.97~beta3-1
Severity: critical
Justification: breaks the whole system
$ ls -lh /usr/lib/grub-rescue/grub-rescue-floppy.img
-rw-r--r-- 1 root root 1.5M 2009-09-12 17:07
/usr/lib/grub-rescue/grub-rescue-floppy.img
A standard floppy is 1.44M, so
A standard floppy is 1.44M, so grub-rescue-floppy.img is too large to fit.
I was wrong about that :-( It wasn't a ki/kb confusion, but I naively
looked at
$df -B 1 /floppy/
Filesystem 1B-blocks Used Available Use% Mounted on
/dev/fd0 1457664317952 1139712 22%
It now looks as if this is a basic problem with floppies under current
kernels. See bug #548434.
Hope to test writing grub2 to a floppy under an old 2.6.24 kernel when
time permits.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe
Subject: fdutils: fdformat fails under current kernel(s)
Package: fdutils
Version: 5.5-20060227-3
Justification: renders package unusable
Severity: grave
*** Please type your report below this line ***
fdformat fails completely on current kernels.
example: (retyped by hand ,so typos possible...)
I too am seeing this error:
gnumeric: symbol lookup error: /usr/lib/libspreadsheet-1.9.10.so:
undefined symbol: foo_canvas_item_request_update
which is a show stopper. debian testing.
gnumeric Version: 1.9.10-2,
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
Installing gnumeric-doc_1.9.13-1_all.deb,
gnumeric-common_1.9.13-1_all.deb and gnumeric_1.9.13-1_i386.deb from
testing solved the problem here.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
Package: aptitude
Version: 0.4.11.11-1+b2
Severity: grave
Justification: renders package unusable
For over a month now (presumably since the last aptitude upgrade on testing)
I have been seeing segfaults recorded in /var/log/messages on two i386 boxes
and on an amd64, all running testing.
I
Acquire::cdrom::AutoDetect false;
fixed it here as well. Thanks. Sorry for long delay: maybe I wasn't
subscribed, but I didn't see your response before.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
Package: firestarter
Version: 1.0.3-8
Severity: grave
Justification: renders package unusable
-
Installing firefighter from aptitude:-
===
Unpacking firestarter (from .../firestarter_1.0.3-8_i386.deb) ...
.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
-trackball.rules
Here are the contents:
-
# Logitech Marble Mice PN 804377-, PN 810-000767 or
# PN 804251- connected via USB or PS/2
# Marble FX or Marble Mouse (ael)
ACTION!=add|change, GOTO=xorg_marble_end
KERNEL!=event
or
# PN 804251- connected via USB or PS/2
# Marble FX or Marble Mouse (ael)
ACTION!=add|change, GOTO=xorg_marble_end
KERNEL!=event*, GOTO=xorg_marble_end
#ENV{ID_PATH}!=platform-i8042-serio-1, GOTO=xorg_marble_end
# Above for PS/2, misses USB. name below seems to be enough
ATTRS{name}==ImExPS
Package: xserver-xorg-input-mouse
Version: 1:1.4.0-4
Severity: important
Tags: patch
Most logitech trackballs do not work because there is no fdi file included.
Either such a file needs to be included in this package since trackballs
are perhaps variants of mice, or there needs to be an extra
/policy/.
I think the package needs to install it somewhere like
/usr/share/hal/fdi/information/10freedesktop/
Thanks,
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Julien Cristau wrote:
On Sat, Nov 28, 2009 at 13:35:21 +, ael wrote:
Julien Cristau wrote:
You'll need to explain in more details what doesn't work, so that it can
be fixed properly instead of hacked around in an fdi file.
It is (default) button mapping. Of course, users may want
was installed on 29-10-09.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
first reports that a member of my
local LUG had tested on Gentoo and had no problems with the same kernel.
It seems to be something specific to Debian which is extremely odd,
given you have tested on ubuntu.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
Alain Knaff wrote:
On 10/11/09 17:42, ael wrote:
I tried setting the density to dd instead of hd -- something that I
had also tried on fdformat without success. gfloppy managed to
Sorry. I think I should have posted more about that, but the report was
so long already that I held back.
I
involved in formatting, I know.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
installing a new drive 0 or floppy controller.
Not enough raw space on this disk for this format
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I just retested fdformat and superformat on one of the machines
with current testing and kernel 2.6.32 .
fdformat fails in usual way as previously reported.
superformat also fails, but maybe this result gives a clue:-
#
Package: ekiga
Version: 3.2.1~git20090515.9d0263-1
Severity: grave
Justification: renders package unusable
Ekiga 3.2.1 cannot register with my several sip providers.
The accounts window shows: Could not register (Timeout)
Using another machine running ekiga 2.0.11 IIRC on the same network and so
calls are working (echo tests ok), so
maybe it is harmless.
So what is bug now? Is it that upon changing version, ekiga should be
started twice?
As above, I think it is just a reference to the upstream bug. Perhaps it
should stay open until the upstream bug is closed?
ael
Package: korganizer
Version: 4:4.2.2-1
Severity: normal
This may be related to #505770
All my appointments were lost - not displayed - because they were
attached to nob...@nowhere (by default from earlier versions?).
I discovered under 'settings' that Use email settings from System settings
had
Package: gpm
Version: 1.20.4-3.3
Severity: important
This update to gpm has broken my mouse support.
gpm seems to load (although initialy I saw crashes).
It seems to run as
gpm -m /dev/input/mice -t exps2
taken from /etc/gpm.conf. (It is hard to write this with no cut paste)
/deadlock. Maybe the hardware
itself latched up somehow: it certainly looks like something of that
sort.
So I suggest that this bug is closed: if it happens again, I can reopen.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble
properly.
Why should the nv driver interpret the tiiming data differently for different
interfaces?
In passing, it seems that the closed source nvidia driver also has problems
with this monitor on DVI-D. Is Dell doing something evil in its monitors?
ael
--
To UNSUBSCRIBE, email to debian-bugs
In my previous report I had only noticed a single byte difference in the EDID
dumps over
vga as opposed to DVI. In fact there are four:-
$ cmp -l edid.bin_vga edid.bin_DVI
11 33 34
21 16 200
100 24 21
128 113 333
My attempt to decode these didn't seem to match
the nv driver has another issue with panel size.
As far as I can see, this part of the edid specification (as on Wikipedia) is
unambiguous so a fix ought to be simple?
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
as if it is still a panel size problem with nv rather
than the
pixel clock.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: installation-reports
Severity: normal
SSD was Super Talent FEM32GF13M 32G SSD rather than the Acer supplied
8 GB version.
I selected ext4 to format the SSD. The installer choose a swap
partition of around 1 GB.
Could not get past the format/partition stage:
the installer kept saying
of problem negotiating the nfs version
between the client server? And a totally misleading error message?
ael
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.32 (PREEMPT)
Locale: LANG=en_GB.UTF-8
Package: offlineimap
Version: 6.2.0+nmu2
Severity: normal
I encountered the bug reported at:-
http://software.complete.org/software/issues/show/197
The fix there solved the problem. So the debian package needs updating?
-- System Information:
Debian Release: squeeze/sid
APT prefers
on an ext3/4 system.
So it seems that while the installer supports ext4, the installed target
system initrd does not.
So I guess that I will have to compile my own kernel on the target and
then change to ext4 via the rescue mode (it's the root partition) later.
ael
--
To UNSUBSCRIBE, email
.
Will experiment more later today: I ought to try the whole thing with
ext3 and see if I get swap partition problems again.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
no wasted space with partman,
so simply guess sizes.
The installation then completed without problems - using ext3.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: network-manager
Version: 0.7.2-2
Severity: wishlist
network-manager pulls in dhcp3-client dhcp3-common which are
unneccessary when static IPs are used.
So it becomes impossible to have a slim efficient installation
on light weight machines. Perhaps a meta-full package might be needed
on the earlier
dvds is cached somewhere: the dvd is changed, and when that cached path
is used later, it is, of course, no longer valid.
This bug would seem to make debian installation from multiple DVDs
nearly impossible: so pretty serious for those without high
bandwidth connections.
ael
Livelock here:
Not downloading .template file - `debian-testing-i386-DVD-4.template'
already present
100% 63548k/63548k scanning
`...n/k/kde4libs/kdelibs5-dbg_4.1.0-3_i386.deb'
$ ps -fw -C jigdo-file
UIDPID PPID C STIME TTY TIME CMD
ael 3811 3748 24 16:51 pts/1
Another case:
15:32:38 (248.34 KB/s) - `debian-testing-amd64-DVD-4.template' saved
[6179029/6179029]
100% 737k/737k scanning
`...erl/libxml-xerces-perl_2.7.0-0-7_amd64.deb'
$ ps -C jigdo-file -fw
UIDPID PPID C STIME TTY TIME CMD
ael 5596 5533 56 15:32 pts/1
Richard Atterer wrote:
Hi ael,
thanks for this! Unfortunately, as you suspect, the backtrace is not useful
without debugging information. :-/
I realise that :-(
I've just uploaded a version of jigdo-file which contains debugging
symbols: http://atterer.net/jigdo-file_0.7.3-2_i386.deb
On Sat, Mar 06, 2010 at 01:05:00PM +0100, Brice Goglin wrote:
ael wrote:
I could send my rules if it would be useful.
Yes, please, it could help some people, especially the submitter.
In my quick reply, I hadn't noticed that this was a bug report. My working
udev rules are already
Package: grub-rescue-pc
Version: 1.98-1
Severity: minor
packags description says:
This package contains two GRUB rescue images that have been built for
use with traditional PC/BIOS architecture:
- grub-rescue-floppy.img: floppy image.
- grub-rescue-cdrom.iso: El Torito CDROM image.
is broken?
Using --force did however work: I can't see why blocklists should
not be safe on a ro boot rescue floppy?
There needs to be a note, perhaps along the above lines, on how to
produce a floppy image.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
this package contains no binaries, no images, and not even a hint
about how to create rescue images or media. So it has no purpose as it
stands. Just adding a simple example of how to create rescue floppy and
one for a rescue iso would mean it has some use.
ael
is deprecated. Mode %d isn't recognized.
Use set gfxpayload=WIDTHxHEIGHT[xDEPTH] before
linux command instead.\n,
and so on
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe
, all these things
work.
So the mini version is broken?
ael
---
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.33 (PREEMPT)
Locale
Package: gnumeric
Version: 1.9.17-1
Severity: grave
Justification: renders package unusable
==
$gnumeric xxx.gnumeric
gnumeric: error while loading shared libraries:
libgoffice-0.8.so.7: cannot open shared object file: No such
gnumeric 1.10.0-1 from unstable fixes this problem, so perhaps this bug
can be closed.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
correlation with the spurious interrupt message, I doubt that I
have enough information to make a useful bug report. And I should
probably try with the latest git kernel before reporting. So it may take
a while
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
(ael)
ACTION!=add|change, GOTO=xorg_marble_end
KERNEL!=event*, GOTO=xorg_marble_end
#ENV{ID_PATH}!=platform-i8042-serio-1, GOTO=xorg_marble_end
# Above for PS/2, misses USB. name below seems to be enough
ATTRS{name}==ImExPS/2 Logitech Explorer Mouse, GOTO=marbles
ATTRS{name}==Logitech USB Trackball
, and I imagine that I will need to do the same for a
Synaptics touchpad on a netbook.
To save others the time and trouble, I am happy to make them available
to others. I could add them to an existing bug (probably the one on
trackballs). Or should they appear as examples in one of the packages?
ael
Trackball configuration moved from hal to udev, but with
xserver-xorg-core version 1.76-2 it has moved back to xorg.conf.
To help others with similar track balls, here are InputClass clauses
which work with a range of Logitech trackballs. Of course, you may want
to modify the details according to
install the package;
you should find them in /usr/lib/grub-rescue/, and the documentation in
/usr/share/doc/grub-rescue-pc/README.Debian should work.
Just checked on one machine and indeed the files are there...
Apologies if I somehow missed them.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist
: 1
MIS: 0
ael
--
- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-trunk-686 (SMP w/2 CPU cores)
Locale: LANG
I have just observed a correct boot (keyboard working), but with
the atkbd.c Spurious ACK ... present in /var/log/messages.
So this is much less clear than I thought.
I have a good and bad versions log /var/log/messages am now
wondering on how to best compare them. I need to look into a diff
the GUI and you go through the process, you will get
Ok, but it was not documented anywhere that I found.
PS I'm not the firestarter package maintainer
So the lack of documentation isn't your fault :-) Thanks for the reply.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ
Package: linux-2.6
Version: 2.6.32-9
Severity: important
File: linux-image-2.6.32-3
# dpkg -i /var/cache/apt/archives/linux-image-2.6.32-3-amd64_2.6.32-9_amd64.deb
(Reading database ... 231498 files and directories currently installed.)
Preparing to replace linux-image-2.6.32-3-amd64 2.6.32-9
Package: extlinux
Version: 2:3.85+dfsg-1
Severity: important
Please see bug 573962 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573962
which perhaps should have been transferred to to extlinux rather than
closed...
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
extlinux. Even after purging that
package /etc/kernel/postrm.d/extlinux remained! I had to manually
delete it.
I was not actually using extlinux to boot the host system.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
bug, purging extlinux did not remove the script
(which was a symbolic link), so maybe it was some historical relic which
might not recur.
I will try find time tomorrow to make the test...
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject
-
So yes, this bug needs to be re-opened a mechanism to flag whether or
not extlinux is booting the host system needs to be introduced.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
For the record, after replacing drives *and* cables, the problem
persists. I can only assume that it is the controller after all :-(
I think I will live without a floppy on that particular box.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject
); computed from UseEdidDpi
X config
Dec 26 12:39:45 NVIDIA(0): option
--[snip]--
===
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
Package: apt
Version: 0.8.0
Severity: important
Since testing update to 0.7.97.1, apt-cdrom -m add has ceased to work.
Example: with debian-testing-i386-DVD-1.iso mounted on /dvd:
/dev/loop3 on /dvd type iso9660 (rw,loop=/dev/loop3)
running apt-cdrom -m add gives:
Subject: installation-reports: Booting from USB stick not restricted to FAT
Package: installation-reports
Severity: minor
Tags: patch
*** Please type your report below this line ***
Documentation: http://d-i.alioth.debian.org/manual/en.i386/ch04s03.html
etc.
Section 4.3: Preparing Files for USB
.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Subject: jigdo-file: segfaults when called from jigdo-lite
Package: jigdo-file
Version: 0.7.3-1
Severity: important
While running jigdo lite:
==
[snip]
for searching through the list of mirrors: Try a two-letter
country code
to be an upstream problem...
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Just a note for anyone who comes across this report: it seems that
the problem is also occurs on SuSE, 10.3-11.2 -
Any kernel at or above 2.6.28 fails to fdformat a floppy.
That has been reported on the fdutils list and now there is a thread on
the kernel mailing list.
ael
, fdformat worked without problems on one i386
machine, but failed in the usual way on another.
My next message will report the results of Alain's test on the failing
machine.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble
Alain Knaff wrote:
Mark Hounschell wrote:
[...]
All kernels below 2.6.28 work on these boxes. All kernels 2.6.28 and higher do
NOT.
2.6.28 was when support for sector bases other than 0 or 1 were
introduced. So, rather than have sectors numbered from 1 to 18, you can
now have sectors
ael wrote:
Alain Knaff wrote:
then do a getfdprm -o /dev/fd0u1440 (or getfdprm /dev/fd0)
I should have mentioned that my tests were done under the current git
kernel:
# uname -a
Linux exact 2.6.32_exact-55846-gf405425 #194 Sun Dec 13 16:30:46 GMT
2009 i686 GNU/Linux
ael
Alain Knaff wrote:
On 14/12/09 12:27, ael wrote:
# getfdprm -o /dev/fd0u1440
2880 18 2 80 0 0x1b 0x00 0xcf 0x6c
# fdrawcmd drive=/dev/fd0u1440 readid 0 repeat=18
raw cmd: Invalid argument
... and if you try with /dev/fd0 instead?
Yes. I tried all the obvious things. The man/info page
Alain Knaff wrote:
On 14/12/09 15:58, ael wrote:
Any point in running under strace?
Yes, this would be useful, especially for analyzing the Invalid argument
issue.
Ok, Will try and fit it in later today. Meanwhile, what exactly is the
command line that should work? The one you suggested
Alain Knaff wrote:
On 14/12/09 15:58, ael wrote:
Any point in running under strace?
Yes, this would be useful, especially for analyzing the Invalid argument
issue.
Looks as if that was something to do with my command line. Below is the
strace giving the IO error which probably isn't much
Alain Knaff wrote:
On 14/12/09 16:24, ael wrote:
Alain Knaff wrote:
On 14/12/09 15:58, ael wrote:
Any point in running under strace?
Yes, this would be useful, especially for analyzing the Invalid
argument
issue.
Looks as if that was something to do with my command line. Below
change
0: 0
1: 0
2: 0
3: 1
4: 0
5: 7
6: 2
no disk change
0: 0
1: 0
2: 0
3: 1
4: 0
5: 8
6: 2
no disk change
0: 0
1: 0
2: 0
3: 1
4: 0
5: 9
6: 2
no disk change
0: 0
1: 0
2: 0
3: 1
4: 0
5: a
6: 2
no disk change
0: 0
1: 0
2: 0
3: 1
4: 0
5: c
6: 2
no disk change
ael
--
To UNSUBSCRIBE, email
for an hour or more, so can't report immediately.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
: 11
5: 12
5: 1
5: 2
5: 3
5: 6
5: 7
5: 9
5: a
???
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
sheet
and have only skimmed small portions, so I have some catching up to do...
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Alain Knaff wrote:
ael wrote:
Mark Hounschell wrote:
On 12/15/2009 10:08 AM, Alain Knaff wrote:
I mentioned I had multiple machines with this problem. Some running
different versions of SuSE. Mainly 11.0, which is where all the info
I've provided came from thus far. This machine also has
: 9
5: a
5: b
5: d
5: e
5: f
5: 10
5: 11
5: 12
5: 1
5: 2
5: 3
5: 4
5: 8
5: 9
5: a
5: b
5: c
5: d
5: e
5: f
5: 10
Is that what you wanted?
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
A.E.Lawrence wrote:
# fdrawcmd read 0 0 0 1 2 18 1 1 length=18432 /dev/null
remaining= 17920
0: 40 == So this is Abnormal termination?
1: 20 == CRC error? (id or data)
2: 20 == CRC error? (data)
Did I decode them correctly?
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ
Alain Knaff wrote:
A.E.Lawrence wrote:
Alain Knaff wrote:
ael wrote:
Is that what you wanted?
ael
Yes. All sectors are there, ... so I wonder why you are getting errors.
So, next round of tests: trying to read these sectors:
fdrawcmd recalibrate 0
fdrawcmd read 0 0 0 1 2 18 1 1 length
sector= 17
remaining= 0
0: 44
1: 20
2: 20
3: 0
4: 1
5: 11
6: 2
no disk change
sector= 18
remaining= 0
0: 44
1: 20
2: 20
3: 0
4: 1
5: 12
6: 2
no disk change
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
Package: hal
Version: 0.5.13-3
Severity: normal
Tags: patch
The recent xorg-xserver releases would not work on any of my machines, all of
which
use various Logitech trackballs. The following fdi file in /etc/hal/fdi/policy/
fixed the problem:
synaptic installs packages from dvds without problems. Perhaps this bug
should be re-assigned back to aptitude?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
1 - 100 of 491 matches
Mail list logo
