Il giorno mer, 19/04/2006 alle 00.42 +0100, Digby Tarvin ha scritto:
> > > dmesg also warns:
> > > "Kernel command line: root=/dev/hda6 ro libata.atapi_enabled=1"
> > > "Unknown boot option `libata.atapi_enabled=1': ignoring"
> > > which I assume was added by the install system but the syntax is
On Wednesday 19 April 2006 02:20, Frans Pop wrote:
> Hmm. Actually, I think I've read that modprobe.conf overrules anything
> that is in /etc/modprobe.d...
> Could you check if that is the case if you use the second method? Is
> there a file (maybe empty) /etc/modprobe.conf that could overrule what
On Wed, Apr 19, 2006 at 02:20:06AM +0200, Frans Pop wrote:
> On Wednesday 19 April 2006 01:42, Digby Tarvin wrote:
> > But the modprobe.d method doesn't work on my system for installation or
> > post installation, and I think there is a good chance the two issues
> > are be related.
>
[snip]
> In o
On Wednesday 19 April 2006 01:42, Digby Tarvin wrote:
> But the modprobe.d method doesn't work on my system for installation or
> post installation, and I think there is a good chance the two issues
> are be related.
This is the code that parses the option you pass as a kernel option:
if [ -n "$PA
On Wed, Apr 19, 2006 at 12:47:36AM +0200, Frans Pop wrote:
> On Wednesday 19 April 2006 00:12, Digby Tarvin wrote:
> > Actually I should have mentioned that I had tried correcting
> > the syntax in modprobe.d. I had changed /etc/modprobe.d/libata to
> > "options libata atapi_enabled=1"
> > which no
On Tue, Apr 18, 2006 at 10:17:36PM +0200, Frans Pop wrote:
> On Tuesday 18 April 2006 21:49, Digby Tarvin wrote:
> > I suppose 'change your hardware to something better supported' is
> > always going to be a possible solution to an installation problem,
> > but won't be much help to the next person
On Wednesday 19 April 2006 00:12, Digby Tarvin wrote:
> Actually I should have mentioned that I had tried correcting
> the syntax in modprobe.d. I had changed /etc/modprobe.d/libata to
> "options libata atapi_enabled=1"
> which no longer produces a syntax warning, but I still get
> "ata1(0): WARNI
On Tue, Apr 18, 2006 at 09:26:49PM +0200, Frans Pop wrote:
> On Tuesday 18 April 2006 20:04, Frans Pop wrote:
> > > # echo "libata.atapi_enabled=1" >/etc/modutils.d/local
> > >
> > > This file was supposed to be created by the installer, but there was
> > > an error in the code.
> >
> > Still no lu
On Tuesday 18 April 2006 20:04, Frans Pop wrote:
> > # echo "libata.atapi_enabled=1" >/etc/modutils.d/local
> >
> > This file was supposed to be created by the installer, but there was
> > an error in the code.
>
> Still no luck - are you sure about the directory? I had no
> /etc/modutils.d exitin
On Tue, Apr 18, 2006 at 03:04:43PM -0400, Rick Thomas wrote:
>
> Many of the old 10Mbit hubs didn't handle speed and/or duplex
> negotiation as well as modern specs require.
>
> Is it possible that the installer's driver software (or the associated
> configuration files) are less sophisticated
On Tuesday 18 April 2006 21:49, Digby Tarvin wrote:
> I suppose 'change your hardware to something better supported' is
> always going to be a possible solution to an installation problem,
> but won't be much help to the next person who tries the same
> combination.
Well, if you can find out why d
On Apr 18, 2006, at 2:04 PM, Frans Pop wrote:
The Realtek device is a 10/100 UTP interface, which was connected to
a 10Mb hub, which failed to work also.
It was not till I connected to a 10/100Mb hub that the network
started to work for the Debian install, so I suspect it was not
supporting
-- Forwarded Message --
Subject: Re: Bug#363331: installation-reports
Date: Tuesday 18 April 2006 19:38
From: Digby Tarvin <[EMAIL PROTECTED]>
To: Frans Pop <[EMAIL PROTECTED]>
Hi Frans,
Thanks for acknowledging my report...
On Tue, Apr 18, 2006 at 06:23:42PM +0200, Frans Pop
13 matches
Mail list logo
