I tried an amd64 installation on an Intel DG965SS board with 8 GByte.
The system is very very slow (installation more than 1 day.) and
I got corrupt files from the net (e.g. apt-get update).
I have read that this should be a Intel Bios Bug since version
1669 (curr: 1719), if using more than 4
On Fri, 1 Feb 2008, Dr. Helmut G. Enders wrote:
I tried an amd64 installation on an Intel DG965SS board with 8 GByte.
The system is very very slow (installation more than 1 day.) and
I got corrupt files from the net (e.g. apt-get update).
I have read that this should be a Intel Bios Bug
Hi all,
with the new kernel version, there is a new module available: ath5k.
It shall replace madwifi. Has anyone get it running ?
I can load it, the device is seen, but I never get an IP via dhcp.
Maybe it dows still not work correctly. Can anybody confirm this ?
If yes, should we sent a
Hi
absolutely true. But then, who is so diligent to always do so,
especially
when developing your own code for scientific computation? I've written
some,
and only when it was for public consumption I cared to put all the
checks
in all the places... :P
Ehm, anyone that wants to avoid
On Fri, Feb 01, 2008 at 09:09:23AM +0100, Dr. Helmut G. Enders wrote:
I tried an amd64 installation on an Intel DG965SS board with 8 GByte.
The system is very very slow (installation more than 1 day.) and
I got corrupt files from the net (e.g. apt-get update).
I have read that this should be
I know this is not strictly an amd64 matter, but I just discovered something
odd (for me) and wanted to understand if it's just me.
I have an asus A6K, with one of the (in)famous broadcom wireless chips.
Until kernel 2.6.24 I was only able to (partially) use wifi via ndiswrapper,
meaning that I
On Thu, 31 Jan 2008, Lennart Sorensen wrote:
Insufficient ram does not EVER cause a segmentation fault. Only buggy
code causes segmentation faults.
If a bad programmer simply calls malloc and doesn't check that it
succeeded before using it, then you get a segmentation fault, but only
because
Giacomo Mulas:
[...] Where exactly was it ever made
known that you have to ifconfig up your wireless interface before you can
have it list the available networks?
I have no idea but I have made the same observation with an Atheros chip
when using madwifi (self-compiled from SVN).
J.
--
In
On Fri, Feb 01, 2008 at 02:01:35PM +0100, Giacomo Mulas wrote:
absolutely true. But then, who is so diligent to always do so, especially
when developing your own code for scientific computation? I've written some,
and only when it was for public consumption I cared to put all the checks
in all
Hi
I have an amd64 system that is still dualboot with XP. It has a 100GB
FAT32 that i use as my /home but since i barely use XP anymore and i
had some issues with FAT32 i'm gonna resize my 20GB XP partition (oh,
wait, i have game isos...) and change the fat to ext3. Also, my system
got infected
Hi
I am using a 64 bit computer but the problem might be general. But
anyway, is there any unknown trick in making a computer with two raid1
SATA disks boot with Grub?
I can mount /dev/md* when I boot the system on the install CD but I am
unable to install grub on /dev/sda nor /dev/sdb.
On Fri, Feb 01, 2008 at 04:10:25PM +0100, Gudjon I. Gudjonsson wrote:
Since you are discussing this. I spent yesterday on trying to debug
ngspice on amd64 with gdb and valgrind. It segfaults on amd64 but not on
i386. Can you point out some good documents on where to put those checks
you
-Original Message-
From: Gudjon I. Gudjonsson [mailto:[EMAIL PROTECTED]
Sent: Friday, February 1, 2008 04:19 PM
To: debian-amd64@lists.debian.org
Subject: Grub and raid
Hi
I am using a 64 bit computer but the problem might be general. But
anyway, is there any unknown trick in making a
Am Freitag, den 01.02.2008, 23:19 +0100 schrieb Gudjon I. Gudjonsson:
Hi
I am using a 64 bit computer but the problem might be general. But
anyway, is there any unknown trick in making a computer with two raid1
SATA disks boot with Grub?
[...]
Hi,
have a look at:
Hi again
On Fri, Feb 01, 2008 at 04:10:25PM +0100, Gudjon I. Gudjonsson wrote:
Since you are discussing this. I spent yesterday on trying to debug
ngspice on amd64 with gdb and valgrind. It segfaults on amd64 but not on
i386. Can you point out some good documents on where to put those checks
Nuno,
You can de-install unnecessary stuff anytime later. Using an interactive PM
eases the control over the package selection. It lets you browse and solve
dependency conflicts much more easily. Compared to 'real' graphical PMs like
synaptics, interactive aptitude has advanced features, but
Hans,
HAL does not depend on pmount, but pmount depends on libhal-storage.
KDE kio-plugins use pmount, while Gnome use gnome-volume-manager and gnome-vfs.
pmount installs an additional warpper pmount-hal.
According to the pmount manpage, you need users in the group 'plugdev'
(debian.)
But
On Fri, 01 Feb 2008 23:30:21 +0100, Gudjon I. Gudjonsson wrote:
But
anyway, is there any unknown trick in making a computer with two raid1
SATA disks boot with Grub?
I have two SATA disks on a nForce4 motherboard in RAID1, and boot happily
with Grub. The RAID was set up during installation
18 matches
Mail list logo
