Last Monday I took the effort to update a thread in unreviewed HOWTO’s about how to get the alx driver operational for the different kernels. This took me about 3 hours of digging out the relevant material, running local tests on different machines and editing the post. Now it is gone.
Obviously, the technical staff of this forum site do not care to keep fairly recent backups of their contents. Supposing they intend to **** off people trying to help other openSUSE users I must say: Yes, you succeed very well. Don’t count on me in the future.
Hi
If you read the announcements you will see things are slowly syncing back. It’s on the nntp side and easy enough to repost if one was to ask the staff in cordial manner.
What announcement? The banner I see says “feel free to repost”. That’s what I did (abbreviated version, because I really have no time to do all the work again).
On 2013-08-29 17:53, vodoo wrote:
>
> Last Monday I took the effort to update a thread in unreviewed HOWTO’s
> about how to get the alx driver operational for the different kernels.
> This took me about 3 hours of digging out the relevant material, running
> local tests on different machines and editing the post. Now it is gone.
This one?
Subject: Re: Get your wired ethernet working with Attansic Ethernet
controller [1969:1091]
Date: Mon, 26 Aug 2013 12:26:03 GMT
+++·······················
As a workaround (12.2 and 12.3) it was possible to install the package
alx-kmp-<your_kernel-version>.<arch>.rpm (pick the one matching your
kernel) from ‘Index of /repositories/home:/Akoellh:/Kernelmodules’
(http://tinyurl.com/mutchj7) and then type as root:
·······················+±
I have a copy. My setup caches messages for months.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
On 2013-08-29 22:46, consused wrote:
>
> malcolmlewis;2581798 Wrote:
>> I guess my crystal ball broke as well… but a PM, email would
>> suffice to get something restored in this case…
> How long before the missing threads are restored?
I understand they can not restore all of them. Only a few on personal
request.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
On 2013-08-30 11:46, consused wrote:
>
> robin_listas;2581855 Wrote:
>>
>> I understand they can not restore all of them. Only a few on personal
>> request.
> Did the last banner say that? It’s gone here.
No, it did not. They said that here, in a post somewhere.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
On Fri 30 Aug 2013 02:13:08 PM CDT, Carlos E. R. wrote:
On 2013-08-30 11:46, consused wrote:
>
> robin_listas;2581855 Wrote:
>>
>> I understand they can not restore all of them. Only a few on personal
>> request.
> Did the last banner say that? It’s gone here.
No, it did not. They said that here, in a post somewhere.
Hi
The original banner hoped they would restore via nntp. The second banner
said to post again. I said a PM to an admin would/could get it restored
if it was to be had on nntp… sheesh you would think it’s the end of
the world sometimes…
I also suggested a POLITE request, they go a bit further at getting
something sorted. Even here in soapbox, posts that breach the T&C’s can
lead to further action by forum staff.
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 12.3 (x86_64) GNOME 3.8.3 Kernel 3.7.10-1.16-desktop
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below…
> Obviously, the technical staff of this forum site do not care to keep
> fairly recent backups of their contents
Well, you’re wrong about that - we do actually have recent backups, but
the exploit used was a few days earlier than it was discovered.
Forum information is/has been populated back from the NNTP side of
things, and your HowTo should still be there. If it isn’t on the web
side, we can pretty easily copy it back.
So please, instead of being angry with us for being hacked using a
previously unknown hack and having to restore from a few days ago,
understand that we and the technical staff did everything in our power
to get things back up and running as quickly as possible.
Our outage was less than 24 hours, and the data gone from the web side is
< 3 days old (and most of that should have come back). We weren’t down
for 7 days trying to resolve this, AND we didn’t lose any user
passwords to the hackers.
> Last Monday I took the effort to update a thread in unreviewed HOWTO’s
> about how to get the alx driver operational for the different kernels.
> This took me about 3 hours of digging out the relevant material, running
> local tests on different machines and editing the post. Now it is gone.
>
> Obviously, the technical staff of this forum site do not care to keep
> fairly recent backups of their contents. Supposing they intend to ****
> off people trying to help other openSUSE users I must say: Yes, you
> succeed very well. Don’t count on me in the future.
— snip —
Unfortunately, the method described in post http://tinyurl.com/k9ecw7a
does not work anymore for updated kernels from the 12.2 update repository.
As a workaround (12.2 and 12.3) it was possible to install the package
alx-kmp-<your_kernel-version>.<arch>.rpm (pick the one matching your
kernel) from ‘Index of /repositories/home:/Akoellh:/Kernelmodules’
(http://tinyurl.com/mutchj7) and then type as root:
Code:
modprobe alx
systemctl reload network.service
However, this failed for me for 12.2 i586 kernel 3.4.47-2.38-desktop.
GET DRIVER SOFTWARE:
Download http://tinyurl.com/brtpztc to any local directory of your taste.
Unpack with:
Code:
tar xvlf compat-drivers-2013-03-04-u.tar.bz2
cd compat-drivers-2013-03-04-u
HACK THE CODE To make it compile on 12.2 I had to comment-out lines
49-52 in file include/linux/compat-3.8.h to make it look like this:
Code:
/**
kref_get_unless_zero - Increment refcount for object unless it is
zero.
@kref: object.
Return non-zero if the increment succeeded. Otherwise return 0.
This function is intended to simplify locking around refcounting for *
objects that can be looked up from a lookup structure, and which are *
removed from that lookup structure in the object destructor.
Operations on such objects require at least a read lock around *
lookup + kref_get, and a write lock around kref_put + remove from lookup
structure. Furthermore, RCU implementations become extremely tricky.
With a lookup followed by a kref_get_unless_zero with return value
check
locking in the kref_put path can be deferred to the actual removal
from * the lookup structure and RCU lookups become trivial. /
/ vodoo hack static inline int __must_check kref_get_unless_zero(struct
kref *kref)
{
return atomic_add_unless(&kref->refcount, 1, 0);
}
*/
COMPILE AND INSTALL Select the alx driver and compile:
Code:
./scripts/driver-select alx
make
Install as user root:
Code:
su -c ‘make install’
Enable your new alx driver (as user root):
Code:
modprobe alx
systemctl restart network.service
This worked for me. Good luck. This alx driver should work for:
As a writer myself, I always keep backups of the things I write. I
suggest that anyone else who does writing do the same, just in case the
unthinkable happens.
The current concern is not the length of the outage, but it is where contributors’ posts appear to be missing from some recovered threads. At the time of writing, I can see one (or more) technical thread with a single post in it from an NNTP user (26 Aug), not the OP, and all other previous posts from the thread including the OP’s and mine are not there. What is the point of recovering just a single NNTP post, when the thread context and alternative advisories are probably lost.
The current concern is not the length of the outage, but it is where contributors’ posts appear to be missing from some recovered threads. At the time of writing, I can see one (or more) technical thread with a single post in it from an NNTP user (26 Aug), not the OP, and all other previous posts from the thread including the OP’s and mine are not there. What is the point of recovering just a single NNTP post, when the context and alternative advisories are probably lost.
> On Fri 30 Aug 2013 02:13:08 PM CDT, Carlos E. R. wrote:
>
> On 2013-08-30 11:46, consused wrote:
>>
>> robin_listas;2581855 Wrote:
>>>
>>> I understand they can not restore all of them. Only a few on personal
>>> request.
>> Did the last banner say that? It’s gone here.
>
> No, it did not. They said that here, in a post somewhere.
>
>
>
> Hi
> The original banner hoped they would restore via nntp. The second banner
> said to post again. I said a PM to an admin would/could get it restored
> if it was to be had on nntp… sheesh you would think it’s the end of
> the world sometimes…
>
> I also suggested a POLITE request, they go a bit further at getting
> something sorted. Even here in soapbox, posts that breach the T&C’s can
> lead to further action by forum staff.
Hey, it was not me who was complaining.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
That’s the post I proposed to retrieve, but I got no “go ahead” :-?
> As a writer myself, I always keep backups of the things I write. I
> suggest that anyone else who does writing do the same, just in case the
> unthinkable happens.
Yes, specially on a long writeup
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
No, but you answered my question (also not a complaint) that was directed more at Malcolm. His response seems to be summarizing the play of the thread so far, so I didn’t take it personally ;).
On Fri, 30 Aug 2013 19:36:02 +0000, consused wrote:
> The current concern is not the length of the outage, but it is where
> contributors’ posts appear to be missing from some recovered threads. At
> the time of writing, I can see one (or more) technical thread with a
> single post in it from an NNTP user (26 Aug), not the OP, and all other
> previous posts from the thread including the OP’s and mine are not
> there.
> What is the point of recovering just a single NNTP post, when the thread
> context and alternative advisories are probably lost.
Let us know what threads they are, and we can look to see if there’s
something we can recover - even if it’s just to reply from the NNTP side
and quote the missing message.
On Fri, 30 Aug 2013 19:33:14 +0000, Carlos E. R. wrote:
> Yes, specially on a long writeup
Indeed.
The thing that really annoys me about Vodoo’s post is the assumption that
staff just doesn’t care. You know what? If we didn’t care, we would
have left the forums hacked instead of taking the actions we did to clear
the problem up.
I took time out from billable hours to diagnose and do what I could to
help - and it’s just rude to imply (or to outright say) that we obviously don’t care about what we’re doing here.
Especially when it personally cost me billable hours to do what I was
able to do to help with the diagnosis and recovery. I shouldn’t have
to explain that, but it would seem that I do.
I don’t mind volunteering my time here, but when the level of
appreciation expressed is the sort of thing that Vodoo said, well, it
makes me question whether I should continue or not, because in all
honesty, I don’t need that kind of “appreciation” for giving up my time
when a crisis hits.
Next time, maybe I should opt for the billable hours instead, because at
least there I get the satisfaction of getting paid for the work I do,
instead of collecting criticism from people who feel the need to tell
those of us who volunteer our time that we’re inadequate and obviously
don’t care about what we do here.
I’ve been doing online community work most of my life (my first
experiences in online communities were BBS’ back in the mid 80’s), and I
have never seen volunteer staff treated this way by community members.
Admins will get a lot of mails.