.
Memory has always worked without errors.
Marc
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/50ba3a43.3090...@gmail.com
set the Memory Multiplier
to x4.00 (instead of x8.00) then Memtester86+ gets all the way through
test #5 (where all the errors had been coming from) with no errors. I
am now running memtester and it has passed the 'Solid Bits' test and
'Block Sequential' (which were the first that had errors
http://lists.debian.org/debian-user/2012/11/msg01468.html
From: Marc Shapiro marcns...@gmail.com
Last weekend I put together a new box to replace the one that has
been locking up repeatedly. The components are:
Gigabyte 970A-DS3 MB
8GB (2x4GB) Patriot G3 RAM
When I purchase
through 2 full passes of Memtest86+ with no errors.
Thank you, everyone, for your input. Thanks especially to Stan for
triggering my memory that I had written down the output from Memtest86+
so that I could see that it did not match what the package, and the
sticks themselves said they were
out of the Kingston that I had been
thinking about so I got a pair of 4GB Corsair sticks at 1333 MHz. I
have run them through 2 full passes of Memtest86+ with no errors.
Good to hear it's all working now. Curious, the pair of Patriot sticks
with the problem: did that package show signs of being
people will buy memory, swap stickers and
put their old memory in the package and return it. This can happen at
retail, but is very unlikely with Newegg et al as anything returned is
sold as open box not new.
No. It was two sets of Patriot memory. After the first pair gave
errors, I returned them
it.
Well, it's not just Memtest86+ that is reporting errors. I decided to
get a second opinion, as it were, and installed memtester from the
Debian repository. I let it run through 5 cycles of its tests. I have
included the results of the first loop below. The other loops were
similar. None
On Wed, 2012-11-28 at 23:38 -0800, Marc Shapiro wrote:
Do I really have bad memory?
You are using the computer without issues, while your RAM is stressed.
Did you run a RAM test that is not from a Debian distribution?
You RAM could be bad, but it's not likely.
As I've written several times.
On 11/28/2012 9:14 AM, Marc Shapiro wrote:
On 11/27/2012 11:09 PM, Stan Hoeppner wrote:
On 11/27/2012 11:29 PM, Marc Shapiro wrote:
Gigabyte 970A-DS3 MB
8GB (2x4GB) Patriot G3 RAM
The DIMMS are 1600. According to the BIOS the CPU Timing is at 200 and
the memory is at x8.0
a A mobo with the dual channel DDR400 memory
controller in the nVidia Northbridge and two sticks of Geil DDR400 that
routinely threw memory errors until I backed the timings off SPD by 1
clock. Typically these memory errors are caused by a few marginal
transistors in some cells that simply won't
In the absence of an updated Debian install (it's wiser not to update a
digital audio workstation too often) I used another install of current
Ubuntu Quantal 64-bit, Memtest86+ v4.20 and instead running it from the
same Parted Magic live CD, I run it from the lastest Parted Magic 64-bit
Live CD,
there's no guarantee that the RAM is
ok.
Memtest86+ can help to find a broken RAM, but it's not a secure test,
when there's no suspicion for new RAM.
Hth
Ralf
I disagree. My experience with MemTest86+ has been that when it detects
errors, you have a problem.
The other side of the issue is that memory
On 11/28/2012 02:32 AM, Ralf Mardorf wrote:
My apologize, but I don't have the time to read everything. I read that
you get errors when running Memtest. Do you have issues using the
computer?
Did you run Memtest from different distros (live media)?
I never have issues when using my computer
been that when it detects
errors, you have a problem.
The other side of the issue is that memory can test OK but that doesn't
mean your memory is being accessed reliably. Klaus Knopper recently
reported, and I can confirm, that sometimes chipsets aren't able to
handle simultaneous disk
On Wed, 2012-11-28 at 11:42 -0500, Doug wrote:
I'm surprised that Memtest gives different results depending on what
disk you run it from, I guess it would be a good idea to download a
stand-alone version and run a sanity check on the download. BTW,
Memtest has been around forever. I think I
been that when it detects
errors, you have a problem.
The other side of the issue is that memory can test OK but that doesn't
mean your memory is being accessed reliably. Klaus Knopper recently
reported, and I can confirm, that sometimes chipsets aren't able to
handle simultaneous disk and memory
+ that is reporting errors. I decided to
get a second opinion, as it were, and installed memtester from the
Debian repository. I let it run through 5 cycles of its tests. I have
included the results of the first loop below. The other loops were
similar. None of the five loops found any errors in the first 9
the box, but before I even installed the HD (from my old
machine), I booted up and ran Memtest86+. Memtest said that there were
errors, but I finished the install and everything seemed to run properly.
Over the next few days, I got Squeeze installed and did most of my
configuration with no apparent
in the nVidia Northbridge and two sticks of Geil DDR400 that
routinely threw memory errors until I backed the timings off SPD by 1
clock. Typically these memory errors are caused by a few marginal
transistors in some cells that simply won't function correctly at SPD
timings. I won't go as far as saying
My apologize, but I don't have the time to read everything. I read that
you get errors when running Memtest. Do you have issues using the
computer?
Did you run Memtest from different distros (live media)?
I never have issues when using my computer. If I run the same version of
Memtest from
On Ma, 27 nov 12, 21:29:19, Marc Shapiro wrote:
Last weekend I put together a new box to replace the one that has been
locking up repeatedly. The components are:
Gigabyte 970A-DS3 MB
8GB (2x4GB) Patriot G3 RAM
AMD FX-4100 Quad Core CPU
ASUS DVD/CD Writer
MSI
threads
transversing month boundaries? hence CC'ing listmaster.
listmaster, please keep debian-user in CC, as it concerns debian-users
searching the archives for information.
---
OK, found
http://lists.debian.org//debian-user/2012/08/msg02006.html
(Despite .xsession-errors being spelled
On Sat, Sep 01, 2012 at 01:19:49PM -0400, Frank McCormick wrote:
On 01/09/12 12:45 PM, Chris Bannister wrote:
On Sat, Sep 01, 2012 at 09:54:32AM +0200, lee wrote:
Frank McCormick debianl...@videotron.ca writes:
I keep seeing references to NVidia in my .xsesssion-errors file. I
(firefox
On Sat, Sep 01, 2012 at 01:40:50PM -0600, Bob Proulx wrote:
I have much egregious noise in that file. It would be good if there
was a campaign to clean it up. But it is a distributed culture of
sloppy programming over years that has contributed to it. It would
take a large effort to clean
On Sun, Sep 02, 2012 at 03:07:09PM -0600, Bob Proulx wrote:
Camaleón wrote:
Bob Proulx wrote:
Camaleón wrote:
But it seems the problem remains (read comment #45) so dunno why it was
archived with apparently no additional clues on the current status:
This was the message that
On Tue, Sep 04, 2012 at 12:59:04AM +1200, Chris Bannister wrote:
What I see by looking now is:
* 617940 is/was assigned to the libvdpau1 package
* notfixed 617940 2:1.0~rc3+svn20090426-2 removes any indication that
version 2:1.0~rc3+svn20090426-2 was fixed.
* libvdpau1 never
On Tue, Sep 04, 2012 at 12:43:11AM +1200, Chris Bannister wrote:
At least there is a bug open: see chameleon's post in this thread.
Correction was open, now closed and archived. :(
--
If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving
On Tue, 04 Sep 2012 00:59:04 +1200, Chris Bannister wrote:
On Sun, Sep 02, 2012 at 03:07:09PM -0600, Bob Proulx wrote:
(...)
This was the message that closed it. It was sent to 617940-done and
so the bug was marked as closed. The other bug was forcibly merged
with this one and so it
On Tue, Sep 04, 2012 at 12:59:04AM +1200, Chris Bannister wrote:
So what now?
If the bug needs re-opening, unarchive it and reopen it:
http://www.debian.org/Bugs/server-control
Probably something like this to cont...@bugs.debian.org
unarchive 617940
reopen 617940
thanks
It would be
On Sat, 01 Sep 2012 15:43:41 -0600, Bob Proulx wrote:
Camaleón wrote:
But it seems the problem remains (read comment #45) so dunno why it was
archived with apparently no additional clues on the current status:
This was the message that closed it. It was sent to 617940-done and so
the bug
Camaleón wrote:
Bob Proulx wrote:
Camaleón wrote:
But it seems the problem remains (read comment #45) so dunno why it was
archived with apparently no additional clues on the current status:
This was the message that closed it. It was sent to 617940-done and so
the bug was marked as
Frank McCormick debianl...@videotron.ca writes:
I keep seeing references to NVidia in my .xsesssion-errors file. I
(firefox:2707): atk-bridge-WARNING **: Could not locate registry
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared
object file: No such file or directory
On 09/01/2012 03:54 AM, lee wrote:
Frank McCormick debianl...@videotron.ca writes:
I keep seeing references to NVidia in my .xsesssion-errors file. I
(firefox:2707): atk-bridge-WARNING **: Could not locate registry Failed to
open VDPAU backend libvdpau_nvidia.so: cannot open shared object
The Wanderer wande...@fastmail.fm writes:
On 09/01/2012 03:54 AM, lee wrote:
Frank McCormick debianl...@videotron.ca writes:
I keep seeing references to NVidia in my .xsesssion-errors file. I
(firefox:2707): atk-bridge-WARNING **: Could not locate registry Failed to
open VDPAU backend
On 01/09/12 10:02 AM, The Wanderer wrote:
On 09/01/2012 03:54 AM, lee wrote:
Frank McCormick debianl...@videotron.ca writes:
I keep seeing references to NVidia in my .xsesssion-errors file. I
(firefox:2707): atk-bridge-WARNING **: Could not locate registry
Failed to
open VDPAU backend
On 08/31/2012 05:13 PM, Frank McCormick wrote:
I keep seeing references to NVidia in my .xsesssion-errors file. I
haven't used Nvidia for a couple of years. What could be hanging
around from those days ??
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared
object file
On Fri, 31 Aug 2012 16:13:41 -0400, Frank McCormick wrote:
I keep seeing references to NVidia in my .xsesssion-errors file. I
haven't used Nvidia for a couple of years. What could be hanging around
from those days ??
(firefox:2707): atk-bridge-WARNING **: Could not locate registry Failed
On 01/09/12 10:38 AM, Eduardo M KALINOWSKI wrote:
On 08/31/2012 05:13 PM, Frank McCormick wrote:
I keep seeing references to NVidia in my .xsesssion-errors file. I
haven't used Nvidia for a couple of years. What could be hanging
around from those days ??
Failed to open VDPAU backend
On 01/09/12 10:46 AM, Camaleón wrote:
On Fri, 31 Aug 2012 16:13:41 -0400, Frank McCormick wrote:
I keep seeing references to NVidia in my .xsesssion-errors file. I
haven't used Nvidia for a couple of years. What could be hanging around
from those days ??
(firefox:2707): atk-bridge-WARNING
On Sat, 01 Sep 2012 11:21:35 -0400, Frank McCormick wrote:
On 01/09/12 10:46 AM, Camaleón wrote:
On Fri, 31 Aug 2012 16:13:41 -0400, Frank McCormick wrote:
I keep seeing references to NVidia in my .xsesssion-errors file. I
haven't used Nvidia for a couple of years. What could be hanging
On Sat, Sep 01, 2012 at 09:54:32AM +0200, lee wrote:
Frank McCormick debianl...@videotron.ca writes:
I keep seeing references to NVidia in my .xsesssion-errors file. I
(firefox:2707): atk-bridge-WARNING **: Could not locate registry
Failed to open VDPAU backend libvdpau_nvidia.so
On 01/09/12 12:45 PM, Chris Bannister wrote:
On Sat, Sep 01, 2012 at 09:54:32AM +0200, lee wrote:
Frank McCormick debianl...@videotron.ca writes:
I keep seeing references to NVidia in my .xsesssion-errors file. I
(firefox:2707): atk-bridge-WARNING **: Could not locate registry
Failed to open
Camaleón wrote:
Frank McCormick wrote:
Camaleón wrote:
Frank McCormick wrote:
I keep seeing references to NVidia in my .xsesssion-errors file. I
haven't used Nvidia for a couple of years. What could be hanging
around from those days ??
I have much egregious noise in that file
On Sat, 01 Sep 2012 13:40:50 -0600, Bob Proulx wrote:
Camaleón wrote:
Frank McCormick wrote:
Camaleón wrote:
Frank McCormick wrote:
I keep seeing references to NVidia in my .xsesssion-errors file. I
haven't used Nvidia for a couple of years. What could be hanging
around from those
Camaleón wrote:
But it seems the problem remains (read comment #45) so dunno why it was
archived with apparently no additional clues on the current status:
This was the message that closed it. It was sent to 617940-done and
so the bug was marked as closed. The other bug was forcibly merged
in xsession-errors. But since mplayer depends on the library
I can't reinstall or use it.
Strange the bug has been hanging around so long with little or nothing
being done about it.
But then this one
(thunderbird:3332): GLib-GObject-WARNING **:
/build/buildd-glib2.0_2.32.3-1-i386-987P8N
I keep seeing references to NVidia in my .xsesssion-errors file. I
haven't used Nvidia for a couple of years. What could be hanging around
from those days ??
(firefox:2707): atk-bridge-WARNING **: Could not locate registry
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared
Hey guys,
After many years, I finally returned to Debian. Now I'm using Debian Wheeze
on my Thinkpad W510 for around 1 week now. The system is updated and it is
being shown as a very stable platform, even though this branch is called
Testing. I have being checking the logs, looking for errors
and it is being shown as a very stable platform, even though this branch
is called Testing. I have being checking the logs, looking for errors
and I found some that I would like to check if they are already known or
if they are specific to my hardware. Checking the .xsession-errors
file I found
These entries are logged in a later stage so it means that all of
the sata ports are throwing exception errors. To list them run:
dmesg | grep -i ata[1-12]
On boot i receive a message that my Marvel controller on my mobo can
only handle 2.5Gb/s so ASUS has given the incorrect specs for this mobo
On Sun, 01 Jul 2012 23:06:40 +0200, Mark Panen wrote:
On 01/07/2012 18:11, Camaleón wrote:
Is ata2 your hdd? Run dmesg | grep -i ata2 to find out.
yes looks like it:
[0.900101] ata2: SATA max UDMA/133 abar m2048@0xf3ff7000 port 0xf3ff7180
irq 35
[1.722809] ata2: SATA link up 1.5
On 02/07/2012 16:26, Camaleón wrote:
Is ata2 your hdd? Run dmesg | grep -i ata2 to find out.
ata8 is my HDD
[0.888232] ata8: SATA max UDMA/133 abar m2048@0xf7fff800 port
0xf7fff980 irq 36
[1.371432] ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 370)
[1.375914] ata8.00: ATA-8:
Hi,
I recently purchased a WD Cavier black 2TB SATA 6 HDD and it uses Marvel
on my motherboard with AHCI enabled.
Debian 6 is the only OS that will install on that drive, i have tried many.
I get this error while booting:
ata2.00: failed command: READ FPDMA QUEUED
Booting up takes very
Hello,
I use apticron on my debian stable server to get notified about updates.
Lately I keep getting messages like:
/etc/cron.daily/apticron:
W: Fehlschlag beim Holen von
http://ftp.de.debian.org/debian/dists/squeeze/Release.gpg Verbindung
mit ftp.de.debian.org:80 nicht möglich (141.76.2.4).
On Sun, 01 Jul 2012 15:56:25 +0200, Mark Panen wrote:
I recently purchased a WD Cavier black 2TB SATA 6 HDD and it uses Marvel
on my motherboard with AHCI enabled.
Debian 6 is the only OS that will install on that drive, i have tried
many.
I get this error while booting:
ata2.00:
On 01/07/2012 18:11, Camaleón wrote:
Is ata2 your hdd? Run dmesg | grep -i ata2 to find out.
yes looks like it:
[0.900101] ata2: SATA max UDMA/133 abar m2048@0xf3ff7000 port
0xf3ff7180 irq 35
[1.722809] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Am i right it's only
On Sun, Jul 01, 2012 at 05:59:58PM +0200, Florian Lindner wrote:
Lately I keep getting messages like:
/etc/cron.daily/apticron:
W: Fehlschlag beim Holen von
http://ftp.de.debian.org/debian/dists/squeeze/Release.gpg Verbindung
mit ftp.de.debian.org:80 nicht möglich (141.76.2.4). - connect
the script header
dpkg: error processing initscripts (--configure):
subprocess installed post-installation script returned error exit status 1
configured to not write apport reports
Errors were encountered while
processing:
initscripts
E: Sub-process /usr/bin
apport reports
�� � � � � � � � � � � � � � � � � � �Errors were encountered while
processing:
�initscripts
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. �Trying to recover:
[cut]
OK, so you have a conflict in the LSB headers for subversion
Errors were encountered while
processing:
initscripts
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
Setting up samba (2:3.5.6~dfsg-3squeeze8) ...
insserv: warning: script 'subversion' missing LSB tags
On Wednesday 13 June 2012 15:24:39 Arnt Karlsen wrote:
..network problems. Fix those, and try again.
Huh. Whadya know. I loaded Wheezy 64-bit and the same problem occurred.
Connected the system directly to the network interface and the problem
vanished. Connected it directly to the IPCop
On Sun, 17 Jun 2012 08:29:39 -0400, Jude DaShiell wrote:
Next time use a more descriptive subject to catch the user's attention ;-)
Script started on Sun 17 Jun 2012 08:26:58 AM EDT
jude@stmarys:~$ mdir a:/
plain_io: Input/output error
plain_io: Input/output error
init A: could not read
Script started on Sun 17 Jun 2012 10:44:21 AM EDT
jude@stmarys:~$ mformat a: -f 70[K20
mformat: init: set default params
jude@stmarys:~$ exit
exit
Script done on Sun 17 Jun 2012 10:45:00 AM EDT
That last line is strange since I did not erase /etc/mtools.conf and
mtoolstest also reports finding
On Sun, 17 Jun 2012 10:52:19 -0400, Jude DaShiell wrote:
Script started on Sun 17 Jun 2012 10:44:21 AM EDT
jude@stmarys:~$ mformat a: -f 70[K20
mformat: init: set default params
jude@stmarys:~$ exit
exit
(...)
Sir, if you remove the portion of the text you are replying to we lost
the
there, I'm going to reinstall. Or maybe
just install wheezy to keep both sites the same (the other site's
hardware is too new for squeeze).
Uhm, did you try using a different mirror? The GPG error is probably
because APT feed GPG a non-existing/empty file (due to the networking
errors).
Yes. I
Hello Neal,
Neal Murphy neal.p.mur...@alum.wpi.edu wrote:
Installed the https transport package to try https: in sources.list. But now
I
see a few Failed to connect to 2001:500:61:28::70: Network is unreachable
(or address 2607:ea00:101:3c0b:207:e9ff:fe00:e595). Why are any IPV6 addrs
both sites the same (the other site's hardware is too
new for squeeze).
Uhm, did you try using a different mirror? The GPG error is probably
because APT feed GPG a non-existing/empty file (due to the networking
errors).
Best regards,
Claudius
--
Incumbent, n.:
Person of liveliest
.
Checked. The host I'm working on shows no networking errors. The firewall
shows no errors. The resets do seem to come from the remote (seen using
tcpdump on the internet link). There've been no complaints from anyone at
that
site about poor or flaky network connections. It only seems to happen
I've been encountering these errors persistently for about the last week
too. I usually do echo $? to check the error level after any aptitude
operation now. I think ftp.us.debian.org has been designated a primary
server and if I understand the mirrors stuff on debian.org correctly
primary
On Jo, 14 iun 12, 04:09:29, Jude DaShiell wrote:
I think ftp.us.debian.org has been designated a primary server and if
I understand the mirrors stuff on debian.org correctly primary mirrors
are only to be used to push files to other secondary mirrors. If
that's the case, terciary
On Wednesday 13 June 2012 15:24:39 Arnt Karlsen wrote:
..network problems. Fix those, and try again.
Checked. The host I'm working on shows no networking errors. The firewall
shows no errors. The resets do seem to come from the remote (seen using
tcpdump on the internet link). There've been
Any idea what would cause the following errors and how to recover? The system
was fine until I installed updates recently.
--
Hit http://ftp.us.debian.org squeeze Release.gpg
Ign http://ftp.us.debian.org/debian/ squeeze/contrib Translation-en
Err http://ftp.us.debian.org/debian
Hello Neal,
Neal Murphy neal.p.mur...@alum.wpi.edu wrote:
W: Failed to fetch http://security.debian.org/dists/squeeze/updates/non-
free/i18n/Translation-en_US.gz Error reading from server - read (104:
Connection reset by peer) [IP: 128.31.0.36 80]
Looks like a connection problem. Is your
On Wed, 13 Jun 2012 13:48:44 -0400, Neal wrote in message
201206131348.44297.neal.p.mur...@alum.wpi.edu:
Any idea what would cause the following errors and how to recover?
The system was fine until I installed updates recently.
--
(...)
E: Some index files failed to download
17:50
To: debian-user@lists.debian.org
Onderwerp: Re: APT errors with Sid/armel on LaCie NAS
On Mon, 21 May 2012 10:20:52 +0200, Jeffrey Langerak wrote:
Hi!
Hi... please, no html formatting, thanks.
I have a LaCie Networkspace 2 and a EDMini V2, both ARM devices running
Debian Sid / Armel
Hi!
I have a LaCie Networkspace 2 and a EDMini V2, both ARM devices running
Debian Sid / Armel.
Since a week or 2 it seems that the devices cannot be upgraded anymore
via APT itself, issuing a apt-get update seems to go well, but doing
apt-get dist-upgrade fails with hash hum mismatches:
On Mon, 21 May 2012 10:20:52 +0200, Jeffrey Langerak wrote:
Hi!
Hi... please, no html formatting, thanks.
I have a LaCie Networkspace 2 and a EDMini V2, both ARM devices running
Debian Sid / Armel.
Since a week or 2 it seems that the devices cannot be upgraded anymore
via APT itself,
On 11/05/2012 17:31, Camaleón wrote:
Have you turned auto-negotiation off? :-?
No I haven't but it was disabled on the switch for some reason. I had it
enabled and now I have full duplex and the errors have gone. Ta :)
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
Background.
I have a machine with two NIC interfaces. I run them in a bond (failover
mode). I then have a bridging interface, br0, which uses bond0.
The bond0 is showing errors in ifconfig -a.
bond0 Link encap:Ethernet HWaddr b8:ad:6f:92:eb:c3
inet6 addr: fe80::baac:6eff:fe92
On Fri, 11 May 2012 14:33:27 +0100, Shaun wrote:
Background.
I have a machine with two NIC interfaces. I run them in a bond (failover
mode). I then have a bridging interface, br0, which uses bond0.
The bond0 is showing errors in ifconfig -a.
bond0 Link encap:Ethernet HWaddr b8:ad
On 11/05/2012 16:52, Camaleón wrote:
A couple of articles talking about transmission errors:
http://www.johnnypez.com/linux/ifconfig-eth0-shows-packet-errors/
http://www.linuxweblog.com/ifconfig-packet-errors
Thanks , I'll have a read of those tonight.
While the amount of packet errors
This could be it..
root@foxy:~# mii-tool eth0
eth0: no autonegotiation, 100baseTx-HD, link ok
root@foxy:~# mii-tool bond0
bond0: 10 Mbit, half duplex, link ok
Looks like the bond0 is on 10Mbit and the slaves on 100Mbit.
Oops!
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
On 11/05/2012 17:08, Shaun wrote:
This could be it..
root@foxy:~# mii-tool eth0
eth0: no autonegotiation, 100baseTx-HD, link ok
root@foxy:~# mii-tool bond0
bond0: 10 Mbit, half duplex, link ok
Looks like the bond0 is on 10Mbit and the slaves on 100Mbit.
Oops!
... which is a
On Fri, 11 May 2012 17:08:26 +0100, Shaun wrote:
This could be it..
root@foxy:~# mii-tool eth0
eth0: no autonegotiation, 100baseTx-HD, link ok
Have you turned auto-negotiation off? :-?
What's the output of ethtool eth0?
root@foxy:~# mii-tool bond0
bond0: 10 Mbit, half duplex, link ok
On Wed, 02 May 2012 12:59:02 -0400, Joey L wrote:
Guys - I posted this earlier and did not get enough options to run down
- does anyone have a few more ?
I am getting the errors below on an IBM X3650 7979 with Debian Squeeze -
with a SerRaid 8K Controller :
[ 90.376722] aacraid: Host
more ?
I am getting the errors below on an IBM X3650 7979 with Debian Squeeze -
with a SerRaid 8K Controller :
[ 90.376722] aacraid: Host adapter abort request (0,0,0,0)
[ 90.376797] aacraid: Host adapter abort request (0,0,0,0)
[ 90.376874] aacraid: Host adapter reset request. SCSI hang
On Thu, 03 May 2012 14:11:33 -0400, Joey L wrote:
Thanks for your input - that was me asking the same type of question
again. What I really need to know is how do I update latest Debian
Squeeze DVD with the correct drivers for my controller? DO you know
where I can get the latest aacraid
Guys - I posted this earlier and did not get enough options to run
down - does anyone have a few more ?
I am getting the errors below on an IBM X3650 7979 with Debian Squeeze
- with a SerRaid 8K Controller :
[ 90.376722] aacraid: Host adapter abort request (0,0,0,0)
[ 90.376797] aacraid
On Lu, 16 apr 12, 14:34:33, Tom Roche wrote:
(Apologies if this is not the correct place to post (is there an
apt-user or aptitude-user list?), but it's been helpful in past.)
This is the correct list for apt-get/aptitude usage in Debian ;)
[snip]
I see that you fixed your problem by using
I was playing with dd conv=noerror option. It continues reading the
input file(for example HDD/SSD partition) even in case there are read
errors. Which errors are critical for integrity of ext[234] file
system? As I understand, Linux views the file system as a common set
of objects- superblock
On 04/16/2012 09:26 PM, Tom Roche wrote:
Wayne Topa Mon, 16 Apr 2012 15:24:26 -0400
I just looked for lmde in the debian packages and it is not there
and it's not in the original post @
http://lists.debian.org/debian-user/2012/04/msg01217.html
either, because LMDE is not a package
I am
On Mon, Apr 16, 2012 at 9:26 PM, Tom Roche tom_ro...@pobox.com wrote:
So I did
sudo apt-get update
sudo apt-get dist-upgrade
sudo apt-get -f install
which got the packages fixed and installed, as verified by subsequent
In future, you might want to run sudo apt-get upgrade before sudo
Tom H wrote:
Tom Roche wrote:
So I did
sudo apt-get update
sudo apt-get dist-upgrade
sudo apt-get -f install
which got the packages fixed and installed, as verified by subsequent
In future, you might want to run sudo apt-get upgrade before sudo
apt-get dist-upgrade to make the
, at the end of a very long scroll (thank you,
gnome-terminal :-)
dpkg: dependency problems prevent configuration of
with regard to 35 different packages (followed by details for each one)
before ending with
Errors were encountered while processing: # sorted by me
brasero
evince
file-roller
gconf2
finished. However,
on finish it reported, at the end of a very long scroll (thank you,
gnome-terminal :-)
dpkg: dependency problems prevent configuration of
with regard to 35 different packages (followed by details for each one)
before ending with
Errors were encountered while processing: # sorted
configuration of
with regard to 35 different packages (followed by details for each one)
before ending with
Errors were encountered while processing: # sorted by me
brasero
evince
file-roller
gconf2
gdm3
gnome-applets
gnome-bluetooth
gnome-control-center
gnome-disk-utility
gnome-panel
(followed by details for each
one)
before ending with
Errors were encountered while processing: # sorted by me
brasero
evince
file-roller
gconf2
gdm3
gnome-applets
gnome-bluetooth
gnome-control-center
gnome-disk-utility
gnome-panel
gnome-power-manager
gnome-session
gnome-settings-daemon
Wayne Topa Mon, 16 Apr 2012 15:24:26 -0400
I just looked for lmde in the debian packages and it is not there
and it's not in the original post @
http://lists.debian.org/debian-user/2012/04/msg01217.html
either, because LMDE is not a package
I am guessing the lmde might be a Linux Mint
Tom Roche wrote:
Indulekha Mon, 16 Apr 2012 14:52:34 -0500
Have you tried apt-get -f install?
No, and using apt-get rather than aptitude was the right idea:
The nvidia sata drivers aren't working with the latest kernel either. I
wrote about that earlier and was told the drivers are present but the
drive isn't detected correctly by the installer. As of now, both
Slackware 13.0 and archlinux do not have problems installing on my sata
drive. I'll
701 - 800 of 3254 matches
Mail list logo
