Maybe I should post this somewhere else, but I just upgraded to the 12.1 milestone 5 thinking it might fix the issues I was having in 11.4 with such slow yast->software management downloads. Kpackagekit wasn’t updating the download speeds to any meaningful information either (in 11.4). But it seems like once the download starts it flys through the download. The same thing on refreshing repositories, adding repositories, downloading the list of community repositories. It errors, time-outs, etc… I don’t know what the problem is. Maybe its an opensuse network problem, although I don’t see how I was able to instantly start downloading my 12.1 milestone 5 DVD at 750-900 kb/s if that was the sole problem.
I have:
Asus p8h61-M LE/CSM motherboard
4gb of memory
i5-2500k sandy bridge
AR2413 D-LInk DWL-G510 rev b Wireless Card using ath5k
And just so you know, I am also having slow starts to yast downloads, refreshing repositories, etc… on my laptop using 11.4 too. I’m not having this problem in Ubuntu 11.04. I like Opensuse and want to be using it in the final release of opensuse 12.1 but if my yast downloads don’t improve its back to Ubuntu I will go, unfortunately.
So far my experience with 12.1 milestone 5 has been pleasant. I didn’t have internet access with kde at first couldn’t use ifup either, but now I’m using NetworkManager in kde. NetworkManager worked fine in gnome3 which I installed durring installation. It took about a half hour to download 15 packages at 49 mb because of my network problem with yast. I’m wondering if using zypper would patch the problem. Kdevelop4 says system configuration error and quits, it may be because I didn’t format my /home partition, but I deleted ~/.kde4/share/apps/kdevelop and ~/.kde4/share/config/kdeveloprc
It worked.
Honestly I had read about doing that before, editing /etc/resolv.conf…but I didn’t think that was the issue because firefox was doing fine. I edited my /etc/resolv.conf to just nameserver 8.8.8.8 and yast is flying away. I should have tried that earlier. Can someone point me in the direction of doing this ipv6 thing system wide. The only place I even see the option is in yast->network settings->Traditional method with ifup and then selecting it next to DHCP ipv4 only. And ifup isn’t working for me anyhow. It says something about power management error
linux-c8g7:/home/craig # ifup wlan0
wlan0 device: Atheros Communications Inc. AR2413 802.11bg NIC (rev 01)
command 'iwconfig wlan0 power off' returned
Error for wireless request "Set Power Management" (8B2C) :
SET failed on device wlan0 ; Operation not supported.
wlan0 warning: wpa_supplicant already running on interface
and I should have ifdown wlan0 before I ifup to get rid of that wpa-supplicant warning. But same ifup problem either way.
Also, why is it that it just started messing with my system ( the ipv6 thing) I’ve been using 11.4 for quite a while and we have the same ISP.
On 09/09/2011 01:16 PM, cw9000 wrote:
>
> It worked.
> Honestly I had read about doing that before, editing
> /etc/resolv.conf…but I didn’t think that was the issue because
> firefox was doing fine. I edited my /etc/resolv.conf to just nameserver
> 8.8.8.8 and yast is flying away. I should have tried that earlier.
> Can someone point me in the direction of doing this ipv6 thing system
> wide. The only place I even see the option is in yast->network
> settings->Traditional method with ifup and then selecting it next to
> DHCP ipv4 only. And ifup isn’t working for me anyhow. It says
> something about power management error
>
>
> Code:
> --------------------
> linux-c8g7:/home/craig # ifup wlan0
> wlan0 device: Atheros Communications Inc. AR2413 802.11bg NIC (rev 01)
> command ‘iwconfig wlan0 power off’ returned
> Error for wireless request “Set Power Management” (8B2C) :
> SET failed on device wlan0 ; Operation not supported.
> wlan0 warning: wpa_supplicant already running on interface
> --------------------
> and I should have ifdown wlan0 before I ifup to get rid of that
> wpa-supplicant warning. But same ifup problem either way.
>
> Also, why is it that it just started messing with my system ( the ipv6
> thing) I’ve been using 11.4 for quite a while and we have the same ISP.
You likely disabled IPv6 with 11.4. That was what was usually recommended, but
that should not be done now or in the future. How some ISP’s get by with
misconfigured name servers is beyond me, but they do.
That power management “error” is not significant, but you should be able to get
rid ot it with an edit of /etc/sysconfig/network/ifcfg-wlan0.
I edited WIRELESS_POWER to “none” via Yast->/etc/syconfig editor->Hardware->Network->wlan0. it was on “no”. I haven’t turned it back on to ifup to test yet. But thanks for pointing me to that anyway.
On a side note I was getting random system freezes in opensuse 11.4, and that was another big reason for going with the new 12.1 milestone 5. At first (on new install of 12.1) I encountered no freezes. I was playing music, I had my system up for 3 days with no freezes.
I thought all was good.
Then I installed vlc via Index of /pub/vlc/SuSE/Factory/ and I watched a movie (avi file). Not only was it not in sync ( the sound/picture) but I got through about 10 minutes of the movie and I got a freeze ( the same words were said over and over again from the movie and my computer was unresponsive, oh and when this happened before in opensuse 11.4 I would try to ssh into it to no avail, so I didn’t bother, nor do I have that port open so I don’t know what the logs have to say).
Then it happened again while browsing the internet and listening to music (amarok). Then a couple days later (yesterday) I was lightscribing a cd with Lacie Lightscribe (4L-gui) and browsing the internet ( I had made like 10 cds and was on the 10th one) and it froze in the middle of lightscribing. So far today I haven’t had any freezes and I’ve had my computer on since yesterday’s freeze and I’ve been listening to a lot of mp3s.
That was my main reason for trying out Ubuntu was to get rid of the freezes. Ubuntu froze, too. And I’ve tried xset -dpms. Nothing seems to get rid of the freezes completely. I’ve even contemplated getting new memory ( I don’t know the brand of my memory and THUS its not on Asus QVL-qualified vendor list). I blamed it on my Sandy Bridge processor being too new. Now with Kernel 3+ I don’t know if I can blame it on that. I’ve even tried nomodeset and it still froze in 11.4. I just want this thing to be stable. I don’t have windows on this computer so I can’t compare–as far as freezes go.
for some reason my setting of WIRELESS_POWER to “none” didn’t take effect through yast ( maybe I hit the wrong button, its a possibility), but after editing it through nano the power problem on my wlan0 went away. BTW the reason it wasn’t working before was because I hadn’t put in my IPv4 Gateway on the tab Routing in Yast->Network Settings. Stupid mistake, I just figured I had put that in in the static ip settings page.
so ifup is working fine
So if anybody can help with my freezing problem that would be super (this thread has been productive I’ve fixed 2/3)
edit: and no I don’t expect a new version to be stable right away, but freezes that were occuring in 11.4 are still happening. So I don’t think it has to do with it being an unrealeased version. Maybe…maybe the beta version will fix EVERYTHING, even my love life, (mwa ha ha) but I just wanted to make sure there wasn’t some obvious reason for the freezes.
Anyway, thanks
-peace
I too have a problem accessing the repositories - even though my hardware really should be ‘top of the art’. I tried some of the recommendations in this thread, but they really did not help. And some of them do seem rather far-fetched. Anyway, I should not have to edit strange conf files, set mysterious parameters or to disable ‘iPv6’. Suitable, reliable internet connections should be an automatic responsibility of an operating system. I feel kind of sorry, and may be I will give it yet another try - but this is unacceptable for my new server and I seriously consider either another distribution of Linux or may be even Windows for my new server. I simply MUST be able to get updates without any trouble.
I am fully aware that others will feel differently - but I consider this a BUG in Suse 12.1. When people write here they bear witness to a certain amount of knowledge and commitment and I am not the only one with this problem. And it is no new thing for Suse (there were some debate about this back in 2008 and may be even before). I believe the ‘brass’ og Linux ought to take this more seriously than just referring if to the forums. Hope they will accept this challenge, but they better be fast - a lot faster than their repositories or whatever causes this problem.
On 03/08/2012 10:46 AM, hoegstedt wrote:
>
> I too have a problem accessing the repositories - even though my
> hardware really should be ‘top of the art’. I tried some of the
> recommendations in this thread, but they really did not help. And some
> of them do seem rather far-fetched. Anyway, I should not have to edit
> strange conf files, set mysterious parameters or to disable ‘iPv6’.
> Suitable, reliable internet connections should be an automatic
> responsibility of an operating system. I feel kind of sorry, and may be
> I will give it yet another try - but this is unacceptable for my new
> server and I seriously consider either another distribution of Linux or
> may be even Windows for my new server. I simply MUST be able to get
> updates without any trouble.
Why are you using MS5? A lot of things have been fixed since that was released!
In particular, there were changes to apper, which is the update GUI.
You need to give a few more details. Note that any IPv6 problems at this stage
are a consequence of your ISP, not with Linux or openSUSE. In 12.1, all
components handle IPv6 just fine. To see if that is your problem, you can always
edit /etc/resolv.conf and insert 2 lines containing ‘nameserver 8.8.8.8’ and
‘nameserver 8.8.4.4’ AHEAD of any other nameserver lines.
> I am fully aware that others will feel differently - but I consider
> this a BUG in Suse 12.1. When people write here they bear witness to a
> certain amount of knowledge and commitment and I am not the only one
> with this problem. And it is no new thing for Suse (there were some
> debate about this back in 2008 and may be even before). I believe the
> ‘brass’ og Linux ought to take this more seriously than just referring
> if to the forums. Hope they will accept this challenge, but they better
> be fast - a lot faster than their repositories or whatever causes this
> problem.
Most of us have no problems with any network access. Yes, there are corner
cases, but that is why we are here to help you.
What happens if you open a terminal and enter the command