Hi Jimmy,
On Tue, May 28, 2019 at 10:15:28AM -0700, Jimmy Johnson wrote:
> >On Mon, May 27, 2019 at 10:13:12AM -0700, Jimmy Johnson wrote:
> >>On 05/26/2019 11:03 PM, Andy Smith wrote:
> >>>There doesn't seem to be any point in interacting further.
> >>
> >>Andy that's the most helpful thing
On 05/28/2019 08:44 AM, Andy Smith wrote:
Hello,
On Mon, May 27, 2019 at 10:13:12AM -0700, Jimmy Johnson wrote:
On 05/26/2019 11:03 PM, Andy Smith wrote:
There doesn't seem to be any point in interacting further.
Andy that's the most helpful thing you've said,
I guess you missed the
On 2019-05-28, Joe Pfeiffer wrote:
>
> The exim4 installation provides a symbolic link
>
> snowball:558$ ls -l /usr/sbin/sendmail
> lrwxrwxrwx 1 root root 5 May 7 11:44 /usr/sbin/sendmail -> exim4*
>
Actually, the right way to configure reportbug on a local-mail-only system is
to "run the
Curt writes:
> On 2019-05-28, Joe Pfeiffer wrote:
>
>> experimental: 1.18.0-1
>> Please try to verify if the bug you are about to report is already
>> addressed by these releases. Do you still want to file a report
>> [y|N|q|?]?
>
> Think I might've entered 'q' here on the off chance it
Hello,
On Mon, May 27, 2019 at 10:13:12AM -0700, Jimmy Johnson wrote:
> On 05/26/2019 11:03 PM, Andy Smith wrote:
> >There doesn't seem to be any point in interacting further.
>
> Andy that's the most helpful thing you've said,
I guess you missed the response where the very first thing I did
On Tuesday 28 May 2019 09:48:35 am Erik Christiansen wrote:
> On 28.05.19 08:59, Gene Heskett wrote:
> > On Tuesday 28 May 2019 08:34:37 am Erik Christiansen wrote:
> > > That said, one could upgrade just that one package, and try it
> > > out. If it is fixed, you're on a winner then and there.
On Tue, May 28, 2019 at 09:49:47AM -0400, Gene Heskett wrote:
> On Tuesday 28 May 2019 09:29:41 am to...@tuxteam.de wrote:
[...]
> A long enough run at it? :) I never gave it any great thought other than
> you don't write like somebody from "east of the river". (where
> river=Mississippi)
On Tuesday 28 May 2019 09:35:17 am Greg Wooledge wrote:
> On Tue, May 28, 2019 at 08:32:38AM -0400, Gene Heskett wrote:
> > Thats a piece of cake Reco. On a new install, set both the hostname
> > and the domainname, then add them, with the ipv4 net address into
> > the hosts file. Then make
On Tuesday 28 May 2019 09:30:59 am Erik Christiansen wrote:
> On 28.05.19 14:59, to...@tuxteam.de wrote:
> > On Tue, May 28, 2019 at 08:51:41AM -0400, Gene Heskett wrote:
> >
> > [...]
> >
> > > But who or what is the gatekeeper to make sure the address you
> > > choose, supposedly at random,
On Tuesday 28 May 2019 09:29:41 am to...@tuxteam.de wrote:
> On Tue, May 28, 2019 at 09:19:55AM -0400, Gene Heskett wrote:
> > On Tuesday 28 May 2019 08:59:41 am to...@tuxteam.de wrote:
>
> [...]
>
> > > The third time, you owe me a beer ;-P
> >
> > You're on, but you'll have to come and get it,
On 28.05.19 08:59, Gene Heskett wrote:
> On Tuesday 28 May 2019 08:34:37 am Erik Christiansen wrote:
> > That said, one could upgrade just that one package, and try it out. If
> > it is fixed, you're on a winner then and there. "Fixed" beats
> > "reported", as you can get on with the next issue.
>
On Tue, May 28, 2019 at 08:32:38AM -0400, Gene Heskett wrote:
> Thats a piece of cake Reco. On a new install, set both the hostname and
> the domainname, then add them, with the ipv4 net address into the hosts
> file. Then make resolv.conf back into a real file, with 2 lines, one to
> set the
On 28.05.19 14:59, to...@tuxteam.de wrote:
> On Tue, May 28, 2019 at 08:51:41AM -0400, Gene Heskett wrote:
>
> [...]
>
> > But who or what is the gatekeeper to make sure the address you choose,
> > supposedly at random, isn't in use someplace next door or half the
> > planet away? There may
On Tue, May 28, 2019 at 09:19:55AM -0400, Gene Heskett wrote:
> On Tuesday 28 May 2019 08:59:41 am to...@tuxteam.de wrote:
[...]
> > The third time, you owe me a beer ;-P
>
> You're on, but you'll have to come and get it, and it will be miller64
> because I'm diabetic [...]
It's quite
On Tuesday 28 May 2019 08:59:41 am to...@tuxteam.de wrote:
> On Tue, May 28, 2019 at 08:51:41AM -0400, Gene Heskett wrote:
>
> [...]
>
> > But who or what is the gatekeeper to make sure the address you
> > choose, supposedly at random, isn't in use someplace next door or
> > half the planet away?
On Tuesday 28 May 2019 08:48:06 am Dan Purgert wrote:
> Gene Heskett wrote:
> > only talk to it. But if I leave the radio on, I've a neighbor whose
> > phone will use it in a heartbeat regardless
> > [...]
>
> Sounds like someone forgot to set security on their wifi...
I thought that was what I
Hi.
On Tue, May 28, 2019 at 08:32:38AM -0400, Gene Heskett wrote:
> On Tuesday 28 May 2019 01:49:29 am Reco wrote:
>
> > Hi.
> >
> > On Mon, May 27, 2019 at 05:06:24PM -0400, Gene Heskett wrote:
> > > On Monday 27 May 2019 03:19:44 pm Reco wrote:
> > > > On Mon, May 27, 2019 at
On Tue, May 28, 2019 at 08:51:41AM -0400, Gene Heskett wrote:
[...]
> But who or what is the gatekeeper to make sure the address you choose,
> supposedly at random, isn't in use someplace next door or half the
> planet away? There may be some sort of an enforcement in ipv6, but I've
> not
On Tuesday 28 May 2019 08:34:37 am Erik Christiansen wrote:
> On 28.05.19 08:02, Gene Heskett wrote:
> > On Monday 27 May 2019 11:18:49 pm Joe Pfeiffer wrote:
> > > Gene Heskett writes:
> > > Your version (1.14.6-2) of network-manager appears to be out of
> > > date. The following newer
On Tuesday 28 May 2019 07:00:13 am Erik Christiansen wrote:
> On 27.05.19 17:06, Gene Heskett wrote:
> > Thats fine, shows the loop local stuff, but how does one determine
> > the ipv6 address for picnc.coyote.den for instance. I think it
> > somehow related to picnc's mac address, but thats just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Gene Heskett wrote:
> only talk to it. But if I leave the radio on, I've a neighbor whose
> phone will use it in a heartbeat regardless
> [...]
Sounds like someone forgot to set security on their wifi...
-BEGIN PGP SIGNATURE-
On 05/28/2019 08:02 AM, Gene Heskett wrote:
On Monday 27 May 2019 11:18:49 pm Joe Pfeiffer wrote:
Gene Heskett writes:
On Monday 27 May 2019 03:42:52 pm Jonas Smedegaard wrote:
Quoting Gene Heskett (2019-05-27 19:42:46)
On Monday 27 May 2019 03:46:00 am Curt wrote:
On 2019-05-27,
On 28.05.19 08:02, Gene Heskett wrote:
> On Monday 27 May 2019 11:18:49 pm Joe Pfeiffer wrote:
>
> > Gene Heskett writes:
> > Your version (1.14.6-2) of network-manager appears to be out of date.
> > The following newer release(s) are available in the Debian archive:
> > experimental: 1.18.0-1
On Tuesday 28 May 2019 01:49:29 am Reco wrote:
> Hi.
>
> On Mon, May 27, 2019 at 05:06:24PM -0400, Gene Heskett wrote:
> > On Monday 27 May 2019 03:19:44 pm Reco wrote:
> > > On Mon, May 27, 2019 at 02:09:45PM -0400, Gene Heskett wrote:
> > > > On Monday 27 May 2019 08:58:14 am
On Monday 27 May 2019 11:18:49 pm Joe Pfeiffer wrote:
> Gene Heskett writes:
> > On Monday 27 May 2019 03:42:52 pm Jonas Smedegaard wrote:
> >> Quoting Gene Heskett (2019-05-27 19:42:46)
> >>
> >> > On Monday 27 May 2019 03:46:00 am Curt wrote:
> >> > > On 2019-05-27, wrote:
> >> > > > If
On 27.05.19 23:32, Jimmy Johnson wrote:
> No, seriously I would like to get some user feedback to the question.
> And also why is net-tools being deprecated?
It's not. You and I fully approve of it, so it's fine for the use cases
in which it gives the desired results. (See ifconfig use on this
On 27.05.19 17:06, Gene Heskett wrote:
> Thats fine, shows the loop local stuff, but how does one determine the
> ipv6 address for picnc.coyote.den for instance. I think it somehow
> related to picnc's mac address, but thats just a WAG.
On coyote, it'll look something like line 3:
$ ifconfig
On Tue, May 28, 2019 at 10:59:41AM +0300, Reco wrote:
> Hi.
>
> On Tue, May 28, 2019 at 07:47:36AM -, Curt wrote:
> > On a more serious note, as exim is set up to deliver only local mail on
> > many machines (default installation), what happens when you cannot hand
> > your bug report
Hi.
On Tue, May 28, 2019 at 07:47:36AM -, Curt wrote:
> On a more serious note, as exim is set up to deliver only local mail on
> many machines (default installation), what happens when you cannot hand
> your bug report over to a sendmail-like MTA?
The expected thing happens.
Your
Quoting Curt (2019-05-28 09:47:36)
> On 2019-05-28, Joe Pfeiffer wrote:
>
> > experimental: 1.18.0-1
> > Please try to verify if the bug you are about to report is already
> > addressed by these releases. Do you still want to file a report [y|N|q|?]?
>
> Think I might've entered 'q' here
On 2019-05-28, Joe Pfeiffer wrote:
> experimental: 1.18.0-1
> Please try to verify if the bug you are about to report is already addressed
> by these releases. Do you still want to file a report [y|N|q|?]?
Think I might've entered 'q' here on the off chance it represented the word
quit.
On 05/27/2019 12:54 PM, Brian wrote:
On Mon 27 May 2019 at 10:19:45 -0700, Jimmy Johnson wrote:
On 05/27/2019 12:46 AM, Curt wrote:
On 2019-05-27, wrote:
If Network Manager is giving you grief, please go bark up /that/ tree
(I can't say much about N-M, because I banned it from my boxes
Hi.
On Mon, May 27, 2019 at 05:06:24PM -0400, Gene Heskett wrote:
> On Monday 27 May 2019 03:19:44 pm Reco wrote:
>
> > On Mon, May 27, 2019 at 02:09:45PM -0400, Gene Heskett wrote:
> > > On Monday 27 May 2019 08:58:14 am rhkra...@gmail.com wrote:
> > > > On Monday, May 27, 2019 12:41:36
On Mon, May 27, 2019 at 05:06:24PM -0400, Gene Heskett wrote:
[...]
> Thats fine, shows the loop local stuff, but how does one determine the
> ipv6 address for picnc.coyote.den for instance. I think it somehow
> related to picnc's mac address, but thats just a WAG.
There's not THE ip address.
Gene Heskett writes:
> On Monday 27 May 2019 03:42:52 pm Jonas Smedegaard wrote:
>
>> Quoting Gene Heskett (2019-05-27 19:42:46)
>>
>> > On Monday 27 May 2019 03:46:00 am Curt wrote:
>> > > On 2019-05-27, wrote:
>> > > > If Network Manager is giving you grief, please go bark up /that/
>> > > >
On 2019-05-27 22:22, Gene Heskett wrote:
Then what was I looking at 3 hours ago, looked like a login form to me,
wanted my username, my real name and my email address. That popped up
and denied me access when I clicked on add bug in the upper right
corner
of the screen? It flat refused to let
On Monday 27 May 2019 06:45:42 pm Brian wrote:
> On Mon 27 May 2019 at 17:22:30 -0400, Gene Heskett wrote:
> > On Monday 27 May 2019 03:25:21 pm Brian wrote:
> > > On Mon 27 May 2019 at 13:42:46 -0400, Gene Heskett wrote:
> > > > On Monday 27 May 2019 03:46:00 am Curt wrote:
> > > > > On
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
rhkra...@gmail.com wrote:
> On Monday, May 27, 2019 12:41:36 AM Gene Heskett wrote:
>> On Sunday 26 May 2019 10:09:49 pm Andy Smith wrote:
>
> below>
>
>> You are determined to exterminate any and all users of a hosts file,
>> staticly defined
On Mon 27 May 2019 at 17:22:30 -0400, Gene Heskett wrote:
> On Monday 27 May 2019 03:25:21 pm Brian wrote:
>
> > On Mon 27 May 2019 at 13:42:46 -0400, Gene Heskett wrote:
> > > On Monday 27 May 2019 03:46:00 am Curt wrote:
> > > > On 2019-05-27, wrote:
> > > > > If Network Manager is giving
On Monday 27 May 2019 03:42:52 pm Jonas Smedegaard wrote:
> Quoting Gene Heskett (2019-05-27 19:42:46)
>
> > On Monday 27 May 2019 03:46:00 am Curt wrote:
> > > On 2019-05-27, wrote:
> > > > If Network Manager is giving you grief, please go bark up /that/
> > > > tree (I can't say much about
On Monday 27 May 2019 03:25:21 pm Brian wrote:
> On Mon 27 May 2019 at 13:42:46 -0400, Gene Heskett wrote:
> > On Monday 27 May 2019 03:46:00 am Curt wrote:
> > > On 2019-05-27, wrote:
> > > > If Network Manager is giving you grief, please go bark up /that/
> > > > tree (I can't say much about
On Monday 27 May 2019 03:19:44 pm Reco wrote:
> On Mon, May 27, 2019 at 02:09:45PM -0400, Gene Heskett wrote:
> > On Monday 27 May 2019 08:58:14 am rhkra...@gmail.com wrote:
> > > On Monday, May 27, 2019 12:41:36 AM Gene Heskett wrote:
> > > > On Sunday 26 May 2019 10:09:49 pm Andy Smith wrote:
>
On Mon 27 May 2019 at 10:19:45 -0700, Jimmy Johnson wrote:
> On 05/27/2019 12:46 AM, Curt wrote:
> > On 2019-05-27, wrote:
> > >
> > >
> > > If Network Manager is giving you grief, please go bark up /that/ tree
> > > (I can't say much about N-M, because I banned it from my boxes about
> > >
Quoting Gene Heskett (2019-05-27 19:42:46)
> On Monday 27 May 2019 03:46:00 am Curt wrote:
>
> > On 2019-05-27, wrote:
> > > If Network Manager is giving you grief, please go bark up /that/
> > > tree (I can't say much about N-M, because I banned it from my
> > > boxes about ten years ago: I
On Mon 27 May 2019 at 13:42:46 -0400, Gene Heskett wrote:
> On Monday 27 May 2019 03:46:00 am Curt wrote:
>
> > On 2019-05-27, wrote:
> > > If Network Manager is giving you grief, please go bark up /that/
> > > tree (I can't say much about N-M, because I banned it from my boxes
> > > about ten
On Mon, May 27, 2019 at 02:09:45PM -0400, Gene Heskett wrote:
> On Monday 27 May 2019 08:58:14 am rhkra...@gmail.com wrote:
>
> > On Monday, May 27, 2019 12:41:36 AM Gene Heskett wrote:
> > > On Sunday 26 May 2019 10:09:49 pm Andy Smith wrote:
> >
> > > "you", below>
> >
> > > You are determined
On Monday 27 May 2019 08:58:14 am rhkra...@gmail.com wrote:
> On Monday, May 27, 2019 12:41:36 AM Gene Heskett wrote:
> > On Sunday 26 May 2019 10:09:49 pm Andy Smith wrote:
>
> "you", below>
>
> > You are determined to exterminate any and all users of a hosts file,
> > staticly defined network.
On Monday 27 May 2019 03:46:00 am Curt wrote:
> On 2019-05-27, wrote:
> > If Network Manager is giving you grief, please go bark up /that/
> > tree (I can't say much about N-M, because I banned it from my boxes
> > about ten years ago: I was at a customer's, in his LAN via an
> > Ethernet, when
On 05/27/2019 01:51 AM, Jonas Smedegaard wrote:
Quoting Curt (2019-05-27 09:46:00)
On 2019-05-27, wrote:
If Network Manager is giving you grief, please go bark up /that/
tree (I can't say much about N-M, because I banned it from my boxes
about ten years ago: I was at a customer's, in his LAN
On 05/27/2019 12:46 AM, Curt wrote:
On 2019-05-27, wrote:
If Network Manager is giving you grief, please go bark up /that/ tree
(I can't say much about N-M, because I banned it from my boxes about
ten years ago: I was at a customer's, in his LAN via an Ethernet, when
N-M suddenly saw a WLAN
On Monday 27 May 2019 02:56:07 am to...@tuxteam.de wrote:
> On Mon, May 27, 2019 at 12:41:36AM -0400, Gene Heskett wrote:
>
> [...]
>
> > I don't think so. ipv6 I'm sure is nice where its available. Where
> > it is not available, its a pain in the ass because even if you set
> > it up as a
On 05/26/2019 11:03 PM, Andy Smith wrote:
There doesn't seem to be any point in interacting further.
Andy
Andy that's the most helpful thing you've said, you are trolling Gene a
longtime Debian Linux User who is having problems adjusting to not
having Debian Linux any longer, like so
On Monday 27 May 2019 02:03:27 am Andy Smith wrote:
> Hello,
>
> On Mon, May 27, 2019 at 12:41:36AM -0400, Gene Heskett wrote:
> > On Sunday 26 May 2019 10:09:49 pm Andy Smith wrote:
> > > On Sat, May 25, 2019 at 11:25:26AM -0400, Gene Heskett wrote:
> > > > No Andy, it didn't drink my last beer
On Mon, May 27, 2019 at 08:58:14AM -0400, rhkra...@gmail.com wrote:
> On Monday, May 27, 2019 12:41:36 AM Gene Heskett wrote:
> > On Sunday 26 May 2019 10:09:49 pm Andy Smith wrote:
>
> below>
>
> > You are determined to exterminate any and all users of a hosts file,
> > staticly defined
On Monday, May 27, 2019 12:41:36 AM Gene Heskett wrote:
> On Sunday 26 May 2019 10:09:49 pm Andy Smith wrote:
> You are determined to exterminate any and all users of a hosts file,
> staticly defined network. Its ideal for small home networks.
Hmm, that's interesting -- is there an analog to
Quoting Curt (2019-05-27 09:46:00)
> On 2019-05-27, wrote:
> > If Network Manager is giving you grief, please go bark up /that/
> > tree (I can't say much about N-M, because I banned it from my boxes
> > about ten years ago: I was at a customer's, in his LAN via an
> > Ethernet, when N-M
On Mon, May 27, 2019 at 07:46:00AM -, Curt wrote:
> On 2019-05-27, wrote:
> >
> >
> > If Network Manager is giving you grief, please go bark up /that/ tree
[...]
> This is a grave bug. I suppose we can assume from your description that
> the seedier the wifi portal, the more likely it is
On 2019-05-27, wrote:
>
>
> If Network Manager is giving you grief, please go bark up /that/ tree
> (I can't say much about N-M, because I banned it from my boxes about
> ten years ago: I was at a customer's, in his LAN via an Ethernet, when
> N-M suddenly saw a WLAN out there, out the window
On Mon, May 27, 2019 at 12:41:36AM -0400, Gene Heskett wrote:
[...]
> I don't think so. ipv6 I'm sure is nice where its available. Where it is
> not available, its a pain in the ass because even if you set it up as a
> static ipv4, N-M will tear it down in 5 minutes or less. And N-M is a
>
Hello,
On Mon, May 27, 2019 at 12:41:36AM -0400, Gene Heskett wrote:
> On Sunday 26 May 2019 10:09:49 pm Andy Smith wrote:
> > On Sat, May 25, 2019 at 11:25:26AM -0400, Gene Heskett wrote:
> > > No Andy, it didn't drink my last beer (Murphy does that), or kill
> > > any kittens but it did totally
On Sunday 26 May 2019 10:09:49 pm Andy Smith wrote:
> Hello,
>
> On Sat, May 25, 2019 at 11:25:26AM -0400, Gene Heskett wrote:
> > On Saturday 25 May 2019 07:33:01 am Andy Smith wrote:
> > > My recollection was that none of that was ever established in any
> > > of the threads you posted here, so
Hello,
On Sat, May 25, 2019 at 11:25:26AM -0400, Gene Heskett wrote:
> On Saturday 25 May 2019 07:33:01 am Andy Smith wrote:
> > My recollection was that none of that was ever established in any of
> > the threads you posted here, so that is a really weird thing to keep
> > stating. Did IPv6 use
On Saturday 25 May 2019 12:36:51 pm rhkra...@gmail.com wrote:
> > On Sat, May 25, 2019 at 06:52:00AM -0400, Gene Heskett wrote:
> > > the installer locked me to ipv6, and the nearest ipv6 connectivity
> > > is probably in Pittsburgh PA, 140 some miles north of me. The
> > > installer hasn't
> On Sat, May 25, 2019 at 06:52:00AM -0400, Gene Heskett wrote:
> > the installer locked me to ipv6, and the nearest ipv6 connectivity
> > is probably in Pittsburgh PA, 140 some miles north of me. The
> > installer hasn't brains enough to try ipv4 when it can't find
> > anything working in ipv6.
On Saturday 25 May 2019 07:33:01 am Andy Smith wrote:
> On Sat, May 25, 2019 at 06:52:00AM -0400, Gene Heskett wrote:
> > the installer locked me to ipv6, and the nearest ipv6 connectivity
> > is probably in Pittsburgh PA, 140 some miles north of me. The
> > installer hasn't brains enough to try
On Sat, May 25, 2019 at 06:52:00AM -0400, Gene Heskett wrote:
> the installer locked me to ipv6, and the nearest ipv6 connectivity
> is probably in Pittsburgh PA, 140 some miles north of me. The
> installer hasn't brains enough to try ipv4 when it can't find
> anything working in ipv6.
My
On Saturday 25 May 2019 06:37:05 am Andrei POPESCU wrote:
> On Jo, 02 mai 19, 16:19:08, Gene Heskett wrote:
> > On Thursday 02 May 2019 14:18:53 Pascal Hambourg wrote:
> > > Le 02/05/2019 à 13:25, Gene Heskett a écrit :
> > > > Ha anything been done to forcedeth
On Jo, 02 mai 19, 16:19:08, Gene Heskett wrote:
> On Thursday 02 May 2019 14:18:53 Pascal Hambourg wrote:
>
> > Le 02/05/2019 à 13:25, Gene Heskett a écrit :
> > > Ha anything been done to forcedeth since wheezy?
> >
> > Why are you asking ?
> >
> > &
On Thursday 02 May 2019 14:18:53 Pascal Hambourg wrote:
> Le 02/05/2019 à 13:25, Gene Heskett a écrit :
> > Ha anything been done to forcedeth since wheezy?
>
> Why are you asking ?
>
> > I have installed the LCNC version of stretch
>
> What is LCNC and how does
Le 02/05/2019 à 13:25, Gene Heskett a écrit :
Ha anything been done to forcedeth since wheezy?
Why are you asking ?
I have installed the LCNC version of stretch
What is LCNC and how does if differ from vanilla stretch ?
The network was easy to make work after the install (the installer
Gene Heskett wrote:
...
> And theres no way to even trace its failure because strace is not
> installed. The error message is very explicit, RTNETWORK, whatever the
> heck that is, says "file exists", followed by "failed."
>
> Do I file a bug against force
Greetings all;
Ha anything been done to forcedeth since wheezy? I have installed the
LCNC version of stretch on two machines so far, an old Dell GX520 and
this machine, which has an Asus M2n-sli deluxe mobo, which has nvidia
ethernet ports using forcedeth.
The network was easy to make work
Bruce Ward a écrit :
On Thu, Jun 18, 2015 at 11:12:49PM +1200, Bruce Ward wrote:
An entry options forcedeth ms=0 msix=0 in some /etc/modprobe.d/foo.conf
should do thr trick, no?
I have tried putting the line
forcedeth msi=0 msix=0
into /etc/modules as appeared to work
On Fri, 2015-06-19 at 14:05 +1200, Bruce Ward wrote:
Thanks Selim, that fixed it.
Glad you got it working, but there's certainly a bug there.
If you have the time, maybe you could file a bug (preferably directly
upstream) or see if it already has been reported.
--
Cheers,
Sven Arvidsson
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Jun 19, 2015 at 02:05:37PM +1200, Bruce Ward wrote:
Thanks Selim, that fixed it.
[selim]
options forcedeth msi=0 msix=0
^^^
Should be like this.
Yes, solution is /etc/modprobe.d/forcedeth.conf containing
options
Installing Jessie 8.1.0 on an Asrock N68-VGS3 FX motherboard. This has
Giga PHY RTL8211CL ethernet, which lspci reports as:
00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
It uses the forcedeth driver module, which seems to need parameters
msi=0 msix=0 to work. If I blacklist
)
It uses the forcedeth driver module, which seems to need parameters
msi=0 msix=0 to work. If I blacklist the driver, I can load it
with modprobe forcedeth msi=0 msix=0 and all is fine. However, it
needs this after every reboot and I have not found a way to
successfully load the module
of it :-(
On Fri, Jun 19, 2015 at 09:06:30AM +1200, Bruce Ward wrote:
An entry options forcedeth ms=0 msix=0 in some /etc/modprobe.d/foo.conf
should do thr trick, no?
Of course, perhaps you tried that already and I'm mis-interpreting
your question completely. Apologies if that's the case.
No I have
Hi Tomas
On Thu, Jun 18, 2015 at 11:12:49PM +1200, Bruce Ward wrote:
Installing Jessie 8.1.0 on an Asrock N68-VGS3 FX motherboard. This
has Giga PHY RTL8211CL ethernet, which lspci reports as:
00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
It uses the forcedeth driver module
On Fri, Jun 19, 2015 at 09:06:30AM +1200, Bruce Ward wrote:
An entry options forcedeth ms=0 msix=0 in some /etc/modprobe.d/foo.conf
should do thr trick, no?
Of course, perhaps you tried that already and I'm mis-interpreting
your question completely. Apologies if that's the case.
No I
%.
Any hints or workarounds?
Regards,
Klaus
# dmesg |grep -i forcedet
[1.528115] forcedeth: Reverse Engineered nForce ethernet driver.
Version 0.64.
[1.529046] forcedeth :00:0a.0: PCI INT A - Link[LMAC] - GSI 20
(level, low) - IRQ 20
[1.529055] forcedeth :00:0a.0
On Sun, 16 Jan 2011 11:56:54 +0100, Klaus Pieper wrote:
using
00:0a.0 Ethernet controller: nVidia Corporation MCP79 Ethernet (rev b1)
I have occasional (i.e. occuring about every 6 weeks) hangups of this
device.
Ping to and from the machine does work, but loss is over 70%.
Any hints
Hi Camaleon,
Does ifdown eth0 ifup eth0 restore the connectivity?
Didn't try.
If you are running lenny, I would try with an updated updated kernel (if
this can be an option at your side) :-?
It's squeeze. I have been waiting since 2.6.26 for a kernel fix. I might
try 2.6.37.
Linux
forcedet
[1.528115] forcedeth: Reverse Engineered nForce ethernet driver.
Version 0.64.
[1.529046] forcedeth :00:0a.0: PCI INT A - Link[LMAC] - GSI 20
(level, low) - IRQ 20
[1.529055] forcedeth :00:0a.0: setting latency timer to 64
[1.594154] forcedeth :00:0a.0: ifname
?
Regards,
Klaus
# dmesg |grep -i forcedet
[ 1.528115] forcedeth: Reverse Engineered nForce ethernet driver.
Version 0.64.
[ 1.529046] forcedeth :00:0a.0: PCI INT A - Link[LMAC] - GSI 20
(level, low) - IRQ 20
[ 1.529055] forcedeth :00:0a.0: setting latency timer to 64
[ 1.594154
Hello,
Recently I've got a mainboard with MCP73 chipset (don't have model info,
however I can provide it later if required) and would like to use
onboard network card. I have installed 2.6.18-6 and seems it's forcedeth
module doesn't support this chipset. The following link was very helpful
/2008 11:16, George Chelidze wrote:
Hello,
Recently I've got a mainboard with MCP73 chipset (don't have model info,
however I can provide it later if required) and would like to use
onboard network card. I have installed 2.6.18-6 and seems it's forcedeth
module doesn't support this chipset
Hello all,
just a heads up on a problem I had. I build a small Debian Stable i386 media
server on a Asrock K8NF6G-VSTA motherboard running BIOS version P1.2,
everything worked well, until i flashed the BIOS up to version 1.6. That's
when the forcedeth driver began complaining about bad MAC
Ramesh wrote:
wondering if things have changed and I should try getting new image.
Or something is specifically wrong with my MB that prevents forcedeth
to work properly
Possibly you can try out compiling the 2.6.17.13 kernel with the NIC
driver built-in. Pulling in the netinst iso
Ragu apologies for the off list communication, redirected to list.
Raghavendra Bhat wrote:
Ramesh wrote:
wondering if things have changed and I should try getting new image.
Or something is specifically wrong with my MB that prevents forcedeth
to work properly
Possibly you can try out
I have a Biostar T6100+amd64 setup and I tried netinst image for amd64
about a month ago and it could not get the nforce4 NIC to work.
It will identify load the forcedeth driver but nothing would happen
after that. I can see eth0 but it would not get address from dhcp
server. Even if I assign
I've been seeing the error:
Aug 18 21:24:59 titan kernel: eth-gig1: too many iterations (6) in nv_nic_irq.
in the logs when there is heavy network traffic on my Sarge/amd64
system. The error is produced by the kernel module forcedeth for the
on-board gigabit ethernet controller.
Suggestions
forcedeth for the
on-board gigabit ethernet controller.
Suggestions I've found through googling indicate using the
'max_interrupt_work' module parameter and setting it to a larger value,
rather than the default 5.
I've done this, and setting it to 15 results in similar errors:
Aug 22 21
Jemand ähnliches beobachtet und eventuell Workarounds parat?
Hat jemand mit einer NForce4-Ultra Chipsatz forcedeth Karte keine
derartigen Probleme mit der 17er Reihe?
--
Markus Schulz
meine Spülmaschine heißt Nicole und arbeitet autonom... ansprechendes
ergonomisches 3D-UI, sprachgesteuert
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthias Popp wrote:
Hallo
Warum wird der Nforce Treiber nicht als Debianpaket angeboten? Gerade die
Netzwerkkarte macht immer wieder Probleme. Sie soll ja mit dem Forcedeth
Treiber funktionieren, es klappt aber nicht immer. Ich rede nicht
Matthias Popp schrieb:
Sogar im 2.6.8. nur das Problem ist er funktioniert nicht immer, gerade mit
Kernel 2.6.12 gehabt, aber selbst die aktuellsten Kernel funktionieren
manchmal nicht.
Ich habe es mit einem 2.6.15 oder .16'er Kernel zum laufen gebracht.
Sogar FAI funktioniert damit
Am Freitag 21 Juli 2006 14:29 schrieb David Burau:
ich versuche von den nvidia-Treiber zurück zu den normalen Treiberen
zu kommen. Kernel ist 2.6.13 und Chipsatz nForce 4 Ultra. Leider
kommt aber immer wenn ich die Modules forcedeth oder snd_intel8x0
versuch zu laden. Die Fehlermeldung: FATAL
Hallo
Warum wird der Nforce Treiber nicht als Debianpaket angeboten? Gerade die
Netzwerkkarte macht immer wieder Probleme. Sie soll ja mit dem Forcedeth
Treiber funktionieren, es klappt aber nicht immer. Ich rede nicht von dem
Deb für die Grafikkarte.
--
with best regards from Dortmund
Matthias Popp schrieb:
Hallo
Warum wird der Nforce Treiber nicht als Debianpaket angeboten? Gerade die
Netzwerkkarte macht immer wieder Probleme. Sie soll ja mit dem Forcedeth
Treiber funktionieren, es klappt aber nicht immer. Ich rede nicht von dem
Deb für die Grafikkarte.
soweit ich
On 22.07.06 14:28:36, Matthias Popp wrote:
Warum wird der Nforce Treiber nicht als Debianpaket angeboten? Gerade die
Netzwerkkarte macht immer wieder Probleme. Sie soll ja mit dem Forcedeth
Treiber funktionieren, es klappt aber nicht immer.
Das kann mind. 2 Gruende geben:
1. Niemand hat
1 - 100 of 123 matches
Mail list logo
