On Mon, May 08, 2006 at 09:42:50AM +0100, Philip Kendall wrote:
On Wed, May 03, 2006 at 07:02:20PM +0100, Philip Kendall wrote:
On Tue, May 02, 2006 at 12:07:37PM -0700, Steve Langasek wrote:
* I wondered why I was still booting the old kernel for a bit.
* I edited the symlinks in /boot to
On Wed, May 03, 2006 at 07:02:20PM +0100, Philip Kendall wrote:
On Tue, May 02, 2006 at 12:07:37PM -0700, Steve Langasek wrote:
Anyway, since you're running 2.4.27, your experiences with the drivers
unfortunately don't tell us anything about how things should be structured
for etch,
On Tue, May 02, 2006 at 12:07:37PM -0700, Steve Langasek wrote:
Anyway, since you're running 2.4.27, your experiences with the drivers
unfortunately don't tell us anything about how things should be structured
for etch, which uses a 2.6.15 kernel in the installer with all the bugfixes
and
On Mon, May 01, 2006 at 02:41:39PM -0700, Steve Langasek wrote:
Hi Phil,
On Mon, May 01, 2006 at 12:37:02PM +0100, Philip Kendall wrote:
On Tue, Jan 17, 2006 at 12:14:50PM -0500, Jay Estabrook wrote:
Many of the Alphas with builtin old/slow TULIPs give problems with
the current
On Tue, May 02, 2006 at 04:42:32PM +0100, Philip Kendall wrote:
Which kernel version is this with, and what is the PCI ID of your tulip
interface?
$ uname -a
Linux narn 2.4.27-2-generic #1 Tue Nov 22 17:12:59 UTC 2005 alpha GNU/Linux
narn:pak21:~$ lspci
:00:06.0 SCSI storage
On Tue, Jan 17, 2006 at 12:14:50PM -0500, Jay Estabrook wrote:
Many of the Alphas with builtin old/slow TULIPs give problems with
the current default driver (de2104x). I think it's NOT the driver's
fault, but some kinda quirky implementation on the mobos. Regardless,
it doesn't work
Hi Phil,
On Mon, May 01, 2006 at 12:37:02PM +0100, Philip Kendall wrote:
On Tue, Jan 17, 2006 at 12:14:50PM -0500, Jay Estabrook wrote:
Many of the Alphas with builtin old/slow TULIPs give problems with
the current default driver (de2104x). I think it's NOT the driver's
fault, but some
Hi Jay,
many thanks for your help, with the de4x5 module the networks runs
propperly.
Just one last question:
is there a way to make that permanent, so that the right module is
loaded at boot-time?
cu
cornelius
Jay Estabrook schrieb:
On Tue, Jan 17, 2006 at 11:35:39PM -0800, Steve
I have solved this type of configuration by setting the wrong modules
to the blacklist of hotplug/udev. The right module is then in /etc/modules.
If you do not put the modules into the blacklist, udev/hotplug will
load the *WRONG* module additionally (leads to crash/problems).
Uwe
At 13:20
On Tue January 24 2006 10:30, Uwe Schindler wrote:
I have solved this type of configuration by setting the wrong modules
to the blacklist of hotplug/udev. The right module is then in /etc/modules.
If you do not put the modules into the blacklist, udev/hotplug will
load the *WRONG* module
On Tue, Jan 17, 2006 at 11:35:39PM -0800, Steve Langasek wrote:
On Tue, Jan 17, 2006 at 12:14:50PM -0500, Jay Estabrook wrote:
On Tue, Jan 17, 2006 at 01:21:38PM +0100, Cornelius Weiss wrote:
i managed to install a debian-base-system from the net-install image on
a digital
Hi list,
i managed to install a debian-base-system from the net-install image on
a digital alpha-station255.
After the reboot of DI the installation couldn't be finished, as the
network isn't working.
On colsole it alwas says: Wanrning: No link beat Found
Is sombody aware of a solution for
On Tue, Jan 17, 2006 at 01:21:38PM +0100, Cornelius Weiss wrote:
i managed to install a debian-base-system from the net-install image on
a digital alpha-station255.
After the reboot of DI the installation couldn't be finished, as the
network isn't working.
On colsole it alwas says:
On Tue, Jan 17, 2006 at 12:14:50PM -0500, Jay Estabrook wrote:
On Tue, Jan 17, 2006 at 01:21:38PM +0100, Cornelius Weiss wrote:
i managed to install a debian-base-system from the net-install image on
a digital alpha-station255.
After the reboot of DI the installation couldn't be finished,
14 matches
Mail list logo
