openSUSE Forums > Archives > SF Archives > ARCHIVES - OpenSUSE Beta » Rc1_x64: 20 Second Delay After Logging In

Go Back   openSUSE Forums > Archives > SF Archives > ARCHIVES - OpenSUSE Beta
Forums FAQ Members List Search Today's Posts Mark Forums Read


ARCHIVES - OpenSUSE Beta Questions specific to OpenSUSE Linux Beta releases
(Questions that apply to both beta and release versions should be posted in the appropriate SUSE Help forums)

 
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 31-May-2008, 02:10
stefan1975
Guest
 
Posts: n/a
Default

Hi,

I have two setups of RC1 running, an elderly desktop, wired with x86 and a brand new dualcore wireless x64 laptop. What i noticed is that after logging in the laptop although newer takes MUCH longer to load. there is a delay of around 20 seconds before the taskmanager icons are loaded, the desktop loads them immediately.

At first I thought this was the wireless network starting up, but that is a process that is initiated after all the docked taskmanager icons are loaded and so after the 20 second delay.

does anyone have this as well? is it a x64 "feature" or something to do with a laptop?

stefan
  #2 (permalink)  
Old 01-Jun-2008, 02:44
WehrMacht
Guest
 
Posts: n/a
Default

Quote:
Hi,

I have two setups of RC1 running, an elderly desktop, wired with x86 and a brand new dualcore wireless x64 laptop. What i noticed is that after logging in the laptop although newer takes MUCH longer to load. there is a delay of around 20 seconds before the taskmanager icons are loaded, the desktop loads them immediately.

At first I thought this was the wireless network starting up, but that is a process that is initiated after all the docked taskmanager icons are loaded and so after the 20 second delay.

does anyone have this as well? is it a x64 "feature" or something to do with a laptop?

stefan
[/b]
Same here.

I'm also using the 64 bit version on a HP laptop and I experience the exact same thing!

Also my wireless doesn't auto-connect, I have to manually connect each time.
  #3 (permalink)  
Old 01-Jun-2008, 13:32
stefan1975
Guest
 
Posts: n/a
Default

well it is not the networkmanager, nor the update applet. I tried disabling them both. Right after loading the bootsplash and displaying the KDE desktop and before the taskmanager icons are loaded there is a "dot" in the task manager tray and there it sits for around 20 seconds after which the login sound plays and the autostarted apps are loaded.

strange. stefan
  #4 (permalink)  
Old 02-Jun-2008, 13:26
WehrMacht
Guest
 
Posts: n/a
Default

Quote:
well it is not the networkmanager, nor the update applet. I tried disabling them both. Right after loading the bootsplash and displaying the KDE desktop and before the taskmanager icons are loaded there is a "dot" in the task manager tray and there it sits for around 20 seconds after which the login sound plays and the autostarted apps are loaded.

strange. stefan
[/b]
It might be the audio subsystem or the volume control.

They both give me plenty of grief!!

I get a message about (some) sound thing has crashed, reverting to ALSA, and the sound in PysolFC is very scratchy sometimes. I thnk it's this newfangled sound system they're using (can't remember the name now), but Ubuntu users are complaining about it too.

I'll try NOT loading the volume control (which incidentally doesn't work with my mute/vol controls either!), see if that works.
  #5 (permalink)  
Old 02-Jun-2008, 13:49
WehrMacht
Guest
 
Posts: n/a
Default

The volume control doesn't load for me, I think it crashes.

This is from /var/log/messages:

Jun 2 20:39:52 linux-k3ak pulseaudio[3496]: core-util.c: setpriority(): Permission denied
Jun 2 20:39:52 linux-k3ak pulseaudio[3496]: main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted
Jun 2 20:39:52 linux-k3ak pulseaudio[3496]: main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted
Jun 2 20:39:53 linux-k3ak pulseaudio[3496]: alsa-util.c: Error opening PCM device hw:0: Device or resource busy
Jun 2 20:39:53 linux-k3ak pulseaudio[3496]: module.c: Failed to load module "module-alsa-sink" (argument: "device_id=0 sink_name=alsa_output.pci_10de_44a_sound_card_0_al sa_playback_0"): initialization failed.
Jun 2 20:39:53 linux-k3ak pulseaudio[3496]: alsa-util.c: Device front:0 doesn't support 44100 Hz, changed to 48000 Hz.
Jun 2 20:39:53 linux-k3ak pulseaudio[3496]: alsa-util.c: Cannot find fallback mixer control "Mic".
Jun 2 20:40:39 linux-k3ak pulseaudio[3496]: protocol-esound.c: pulsecore/protocol-esound.c: Failed to create sink input.
Jun 2 20:41:31 linux-k3ak pulseaudio[3496]: protocol-esound.c: pulsecore/protocol-esound.c: Failed to create sink input.
Jun 2 20:42:29 linux-k3ak pulseaudio[3496]: protocol-esound.c: pulsecore/protocol-esound.c: Failed to create sink input.
Jun 2 20:42:53 linux-k3ak pulseaudio[3496]: protocol-esound.c: pulsecore/protocol-esound.c: Failed to create sink input.
Jun 2 20:43:21 linux-k3ak pulseaudio[3496]: protocol-esound.c: pulsecore/protocol-esound.c: Failed to create sink input.
Jun 2 20:45:06 linux-k3ak pulseaudio[3496]: protocol-esound.c: pulsecore/protocol-esound.c: Failed to create sink input.

I'm going to try and get rid of pulseaudio, and go back to alsa, see if that fixes it
  #6 (permalink)  
Old 02-Jun-2008, 13:59
WehrMacht
Guest
 
Posts: n/a
Default

Yup, that fixed ALL my problems with audio

I can now run multiple audio apps and no broken sound and progs refusing to run.

Also the long delay and "dot" in the systray are gone and my mixer now loads on boot.

Just search for "pulse" in Yast2 and remove everything
 

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




 

Search Engine Friendly URLs by vBSEO 3.3.0 RC2