[Solved] Boot failure after upgrade to udev 0.84

After upgrading my system it no longer boot properly.
The kernel boots fine. Initrd executes and the normal init starts.
First of is the start of udev. This starts and immediately complains that nss_ldap is unable to contact the ldap server. Not very strange when networking isn't started yet.
After a little while and a few repetitions of the nss_ldap error message udev says its done.
After this activating swap fails but mounting Root readonly succeds. After this init proceeds with "Checking file system". This fails miserably saying "no such file or directory /dev/sda3" which is the previously mounted root filesystem.
It seems like udev gets busy when not able to connect to the ldap server and hence doesn't create the device nodes for my harddrive in time.
Because the check of the filesystem fails i end up on a rescue prompt. And when logging in to that and check /dev the sda* nodes are there.
Does anyone have a clue on how udev depends on nss_ldap? Any other thought on whats going on?

Ok, after some investigation it turns out that it seems like udev starts a few /sbin/vol_id on the disks/partitions attached. These processes in turn triggered nss_ldap which couldnt connect to the remote ldap server due to network not being up.
I have a less than beautiful solution to the problem. Altering nss_ldap to do soft binds instead of the default that is hard binding. When using hard bind and connect fails it uses an exponential backoff and tries again a little later. Changing to soft bind makes nss_ldap returning immediately when failing.
To change this edit /etc/nss_ldap.conf and change the line saying something like
#bind_policy hard
to
bind_policy soft
This at least helped me getting a system that boots again.

Similar Messages

System boot failure after upgrade from linux3.13.8-1 to linux3.14.6-1

I have tried to update the kernel again from 3.13 to 3.14 again, but no luck.
My arch system boot failure with black screen, tried [ctrl]+[alt]+[F1-6] and nothing happen, no any recure shell prompt out.
Then I boot with kernel debug parameters
systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M
althrough the screen was black, when I reboot and chroot into my system,
I entered the following to find any error messages, please see the link below:
journalctl -b -0 >> ~/3.13_no_problem.log
journalctl -b -1 >> ~/3.14-6_nodebug.log
journalctl -b -2 >> ~/3.14-6_debug.log
3.13_no_problem.log: http://pastebin.com/EQ2Mucq8
3.14-6_nodebug.log: http://pastebin.com/18TRZVRp
3.14-6_debug.log: http://pastebin.com/0QZJBPnf
In both 3.14 journal messages, I found some similar error message:
Jun 15 14:37:47 arch-desktop kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
Jun 15 14:37:47 arch-desktop kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D218 (len 62, WS 0, PS 0) @ 0xD234
Jun 15 14:37:55 arch-desktop kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
Jun 15 14:37:55 arch-desktop kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D218 (len 62, WS 0, PS 0) @ 0xD234
Jun 15 14:38:00 arch-desktop kernel: [drm:cypress_dpm_set_power_state] *ERROR* rv770_restrict_performance_levels_before_switch failed
Jun 15 14:38:01 arch-desktop kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
Jun 15 14:38:01 arch-desktop kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D218 (len 62, WS 0, PS 0) @ 0xD234
Jun 15 14:38:07 arch-desktop kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
Jun 15 14:38:07 arch-desktop kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D218 (len 62, WS 0, PS 0) @ 0xD234
Jun 15 14:38:13 arch-desktop kernel: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
Jun 15 14:38:13 arch-desktop kernel: [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D218 (len 62, WS 0, PS 0) @ 0xD234
I searched on internet, I think this is caused by my graphic card(ATI 5750), but I have no idea to solve it
I don't know my system boot failure due to these error or another things.
my PC specs:
motherbroad - gigabyte GA-P55A-UD3 (bios ver - F11)
cpu - i5-750
display - ati 5750
os - arch 64bit
Currently, I have downgraded back to 3.13.
I hope someone can give me some idea,
Thanks
Last edited by samtai (2014-06-17 12:17:02)

As there are errors associated with ntpd, I would temporarily disable the ntpd service and also ipv6.
If they are not the only problem, at least your logs would be easier to examine for other problems.

[SOLVED] Boot failure after system update

Been running nicely for a few months, but after a -Syu update yesterday morning, the boot process fails immediately after the bit about "Processing Udev events", which memory tells me is the point in the boot process where the screen resolution changes up, so it's my video driver I'm suspecting. I'm running a middle-aged PC with a middle-aged nVidia card, which the nouveau drivers have managed very nicely up to this point, but something in the latest kernel seems to be causing mischief. This machine dual-boots Arch with Windows 98; the latter is working just fine, as do other linux distros booted from a live CD, so I'm sure the hardware itself is OK.
After I see the line about processing Udev events, all I get is a completely black screen, but no report of "no signal" from the monitor. No key presses or Ctrl-Alt-Del combinations have any effect.
If I was to post the relevant log file, would some kind soul take a look? I'm no expert AT ALL, so please tell me which one(s) to post!
TIA,
Piers.
Last edited by pierssnell (2012-04-22 13:13:10)

Many thanks -- but I seem to have the same problem in single-user mode. Followed instructions in your second link, appending "single" or "Single" at the end of the "kernel..." line, and then pressing b. Same result as before, it gets as far as the line "Waiting for Udev to process uevents...... [BUSY]" and then screen goes to black.
My other difficulty is, and this is where I start sounding a bit feeble; I can look at errors.log, or everything.log, but it's all rather Greek to me, and even if I see something that makes it quite clear that it is the nouveau driver that needs re-installing, I really don't see how I can re-install the driver if I can't even get as far as a command prompt?
FWIW, I'm seeing in errors.log
"[drm] nouveau 0000:01:00.0: mem timing table length unknown: 14"
... but I've seen that before, and it's never been fatal.

[SOLVED] Boot loop after upgrade

Hi all,
When i try to boot arch, even in fallback mode, boot fail and go in loop.
loop happen just after the display of nvidia logo, then it try to do something (not showed in screen), it fail, and the nvidia logo is showen again.
I can't access to GDM, i can't turn off computer (have to remove battery from my laptop), i can't access to terminal/console/virtual console.
Last things i've made:
- full update system (pacman -Syu)
- changed /etc/environment adding this line (i was trying to solve tearing problem):
CLUTTER_PAINT=disable-clipped-redraws:disable-culling
CLUTTER_VBLANK=True
nothing seem to work
i've already removed the 2 added lines from another linux distro i've on the same computer, so i don't think /etc/environment is a problem here
don't know what to do and how to solve...
any hints?
thanks
Nico
Last edited by tracuboTL (2012-02-07 14:43:30)

I have exactly the same problem,
Did a full update with pacman.
I haven't updated with yaourt, because I had some problems and rebooted, but now I cannot access the terminal.
If I switch to tty1, I constantly switch back. Ctrl+Alt+Backspace is not enabled and I'm not sure it would work.
I've tried to only boot to runlevel 3, but gdm is in the daemons or I did something wrong because I boot into X again.
Anyone have an idea how to solve this?
Thanks
EDIT: solved it for me
Step 1: on boot let GRUB only boot to init 1
Step 2: change config files so not to start X
Step 3: reboot so you have networking support
Step 4: search in aur if you have a your own cairo package (pacman -Qm)
Step 5: rebuilt that cairo package
Step 6: start X
* step 2 and 3 are maybe not needed if you know how to get networking in init 1. Re;ember to undo the changes in Step 2 so X starts at boot again.
Last edited by tmske (2012-02-06 18:15:15)

[SOLVED]X start failure after upgrade: dri3,present modules missing

I start X with ~.xinitrc from console, which won"t work after last upgrade --first in two weeks.
(EE) Server terminated with error (1).Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
Xorg.log.0 :
[51:778] (EE) intel: Failed to load module "dri3" (module does not exist, 0)
[51:779] (EE) intel: Failed to load module "present" (module does not exist, 0)
Installed packages (EDIT: completed):
xf86-video-intel-2.99.{914-4,916-1}-i686 and also tried with xf86-video-intel-git, with "SNA" acceleration.
intel-dri 10-2.7-3
dri2proto 2.8-2
dri3proto 1.0-1
xf86driproto 2.1.1-3
Linux 3.15.5-2-ARCH i686
Linux CK Atom 3.16.2-1
Issue occurred after upgrading from v2.99.912-1 to v2.99.914+. I was going to try downgrade xf86-video-intel to v2.99.912-1 (as in the first thread in Refs) but went in a dependency conflict, with the older intel driver requiring glamor-egl which conflicts with xorg-server ':-|
Atom netbook
lspci:
00:02.0 VGA compatible controller: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller
Some refs :
» [SOLVED] X start failure after upgrade https://bbs.archlinux.org/viewtopic.php?pid=1426837
» [Solved] xf86-video-Intel-2.99.912-1 breaks xorg https://bbs.archlinux.org/viewtopic.php?id=182932
Last edited by kozaki (2014-09-12 09:45:53)

The issue occurred after upgrading from xf86-video-intel-v2.99.912-1 to v2.99.914+ and xorg-server-1.15.2-1 to 1.16.0-6 (and -devel).
same issue if:
- Switching accelaration method to "UXA" as per https://bugs.archlinux.org/task/40860
- Adding Option "DRI" "False"
Digged a bit:
- same modules errors but appears to be a Gnome bug (X starts): https://bbs.archlinux.org/viewtopic.php?pid=1441716
- same modules errors but X starts up without problems http://www.linuxquestions.org/questions … 175511372/
makes me doubt if this issue is related to the modules not found. Which is the single indication I found so far x-/
Any light on where can the issue comes from? hardware is pretty much standard even if getting a bit old. Never had Xorg related issue so far on this pancake.
Last edited by kozaki (2014-09-11 11:05:42)

Problem: Mac won't boot up after upgrade to 10.5.4

Upgraded MacBook Air (SSD model) to 10.5.4 last night. Got a couple of boots where MBA showed a grey panel in the centre of the screen (in 4 languages) saying that I needed to restart my computer. On the third try got the white Apple startup, then a plain light blue screen. I know from previous upgrades that can sit for a while, so I left it overnight. In the morning, still blue. Power off, power on, grey panel telling me to restart again. Seems to be in a cycle of twice with a grey box, then the blue screen. Any ideas?
Everything is backed up, so if I get it sort-of working, I can restore to my last good 10.5.3 and take it from there.

Hi,
it happened to me too.
I've G4 mini with 1Gb RAM: with 10.5.3 everything was working fine.
Once upgraded to 10.5.4 and reboot, the Mac just won't start: blue screen with mouse cursor but nothing more.
Additionally, the mac becomes extremely noisy as for some process taking out all the CPU.
It's the second time I got a system failure after upgrading Leopard: this starts to be annoying.
M.

[SOLVED] Broken setup after upgrading to 2.6.29

I am running a x86_64 system.
I have been running kernel26-2.6.28.7-2 for a while now. Upgrade to kernel26-2.6.28.8-1 caused some problem for me so I installed the older version from /var/cache/pacman/pkg/. After upgrading day before yesterday to 2.6.29.1, I can boot and login to the system but pretty much nothing works. The obvious problem that I can find out is that everyting is trying to load modules from 2.6.28-ARCH. After logging in even 'uname -r' reports 2.6.28-ARCH. I do have the /lib/modules/2.6.29-ARCH folder with all the modules.
Any help will be much appreciated. I can provide further information if required. Thank you.
Last edited by partha (2009-04-20 03:13:17)

I was able to solve it. The problem was I was using grub installed from Ubuntu. So, there was some problem loading the kernel. Installing grub from arch fixed it. Thanks.

[SOLVED] System freeze after upgrade linux-3.12.9-2 to linux-3.13.4-1

After upgrading from kernel 3.12.9 to 3.13.4 (booth x86_64 architecture) i detected system freeze after round about 0.5s of the login screen about 80% of the time.
So i first thought it coulbe be the the ati driver and uninstalled that via livecd/chroot.
But the same thing happens in comand line only mode.
Afterwards i setup at ssh server to get into the maschine if it is still running, but is was also not responding to that.
Downgrading to 3.12.9 solved the issue. In journalctl i could not find any usefull information.
Last edited by schlumpfimsumpf (2014-04-10 19:16:57)

Me wrote:
It is same for me. Wont boot, and crash before I can write mine pass to text screen. I use lts at now.
H/W path Device Class Description
===============================================
system GA-970A-UD3
/0 bus GA-970A-UD3
/0/0 memory 128KiB BIOS
/0/4 processor Athlon
/0/4/a memory 128KiB L1 cache
/0/4/c memory 2MiB L3 cache
/0/b memory 128KiB L1 cache
/0/29 memory 8GiB System Memory
/0/29/0 memory DIMM 1600 MHz (0,6 ns) [empty]
/0/29/1 memory DIMM 1600 MHz (0,6 ns) [empty]
/0/29/2 memory 4GiB DIMM 1600 MHz (0,6 ns)
/0/29/3 memory 4GiB DIMM 1600 MHz (0,6 ns)
/0/100 bridge RD890 PCI to PCI bridge (external gfx0 port B)
/0/100/0.2 generic RD990 I/O Memory Management Unit (IOMMU)
/0/100/2 bridge RD890 PCI to PCI bridge (PCI express gpp port B)
/0/100/2/0 display GF106 [GeForce GTS 450]
/0/100/2/0.1 multimedia GF106 High Definition Audio Controller
/0/100/4 bridge RD890 PCI to PCI bridge (PCI express gpp port D)
/0/100/4/0 bus EJ168 USB 3.0 Host Controller
/0/100/4/0/0 usb3 bus xHCI Host Controller
/0/100/4/0/0/2 storage ADATA USB Flash Drive
/0/100/4/0/1 usb2 bus xHCI Host Controller
/0/100/9 bridge RD890 PCI to PCI bridge (PCI express gpp port H)
/0/100/9/0 eth0 network RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
/0/100/a bridge RD890 PCI to PCI bridge (external gfx1 port A)
/0/100/a/0 bus EJ168 USB 3.0 Host Controller
/0/100/a/0/0 usb8 bus xHCI Host Controller
/0/100/a/0/1 usb7 bus xHCI Host Controller
/0/100/11 storage SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode]
/0/100/12 bus SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
/0/100/12/1 usb6 bus OHCI Host Controller
/0/100/12/1/5 input M Dongle
/0/100/12.2 bus SB7x0/SB8x0/SB9x0 USB EHCI Controller
/0/100/12.2/1 usb1 bus EHCI Host Controller
/0/100/13 bus SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
/0/100/13/1 usb9 bus OHCI Host Controller
/0/100/13/1/1 input USB Receiver
/0/100/13.2 bus SB7x0/SB8x0/SB9x0 USB EHCI Controller
/0/100/13.2/1 usb4 bus EHCI Host Controller
/0/100/14 bus SBx00 SMBus Controller
/0/100/14.2 multimedia SBx00 Azalia (Intel HDA)
/0/100/14.3 bridge SB7x0/SB8x0/SB9x0 LPC host controller
/0/100/14.4 bridge SBx00 PCI to PCI Bridge
/0/100/14.4/7 multimedia SAA7134/SAA7135HL Video Broadcast Decoder
/0/100/14.4/e bus VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller
/0/100/14.5 bus SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
/0/100/14.5/1 usb10 bus OHCI Host Controller
/0/100/15 bridge SB700/SB800/SB900 PCI to PCI bridge (PCIE port 0)
/0/100/16 bus SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
/0/100/16/1 usb11 bus OHCI Host Controller
/0/100/16/1/3 multimedia USB Web Camera
/0/100/16/1/4 multimedia USB Sound Device
/0/100/16.2 bus SB7x0/SB8x0/SB9x0 USB EHCI Controller
/0/100/16.2/1 usb5 bus EHCI Host Controller
/0/101 bridge Family 15h Processor Function 0
/0/102 bridge Family 15h Processor Function 1
/0/103 bridge Family 15h Processor Function 2
/0/104 bridge Family 15h Processor Function 3
/0/105 bridge Family 15h Processor Function 4
/0/106 bridge Family 15h Processor Function 5
/1 scsi6 storage
Working again. I think problem was the partition was full.
Last edited by gyurman (2014-04-13 07:51:22)

[solved] dhcpcd problem after upgrading to 6.0.4/6.0.5

I cant access any network after upgrading to 6.0.4 or 6.0.5.
Im using the Linux-Kernel 3.10.3.
Does anyone have the same problem?
Downgrading to 5.6.8 solved this problem.
Here is the output of dhcpcd and wpa_supplicant:
dhcpcd[28734]: version 6.0.4 starting
dhcpcd[28742]: wlan0: starting wpa_supplicant
dhcpcd[28734]: eth0: waiting for carrier
dhcpcd[28734]: wlan0: waiting for carrier
dhcpcd[28734]: wlan0: carrier acquired
dhcpcd[28734]: wlan0: soliciting an IPv6 router
dhcpcd[28734]: wlan0: rebinding lease of 192.168.0.104
dhcpcd[28734]: wlan0: soliciting a DHCP lease
dhcpcd[28734]: wlan0: carrier lost
dhcpcd[28734]: wlan0: carrier acquired
dhcpcd[28734]: wlan0: soliciting an IPv6 router
dhcpcd[28734]: wlan0: rebinding lease of 192.168.0.104
dhcpcd[28734]: wlan0: leased 192.168.0.104 for 86400 seconds
dhcpcd[28734]: wlan0: adding host route to 192.168.0.104 via 127.0.0.1
dhcpcd[28734]: wlan0: adding route to 192.168.0.0/24
dhcpcd[28734]: wlan0: adding default route via 192.168.0.1
dhcpcd[28734]: forked to background, child pid 28849
Successfully initialized wpa_supplicant
wlan0: SME: Trying to authenticate with f8:df:a8:33:0e:7f (SSID='VHC' freq=2452 MHz)
wlan0: Trying to associate with f8:df:a8:33:0e:7f (SSID='VHC' freq=2452 MHz)
wlan0: Associated with f8:df:a8:33:0e:7f
wlan0: WPA: Key negotiation completed with f8:df:a8:33:0e:7f [PTK=TKIP GTK=TKIP]
wlan0: CTRL-EVENT-CONNECTED - Connection to f8:df:a8:33:0e:7f completed [id=2 id_str=]
wlan0: CTRL-EVENT-DISCONNECTED bssid=f8:df:a8:33:0e:7f reason=3 locally_generated=1
wlan0: SME: Trying to authenticate with f8:df:a8:33:0e:7f (SSID='VHC' freq=2452 MHz)
wlan0: Trying to associate with f8:df:a8:33:0e:7f (SSID='VHC' freq=2452 MHz)
wlan0: Associated with f8:df:a8:33:0e:7f
wlan0: WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
wlan0: WPA: Could not verify EAPOL-Key MIC - dropping packet
wlan0: WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
wlan0: WPA: Could not verify EAPOL-Key MIC - dropping packet
wlan0: Authentication with f8:df:a8:33:0e:7f timed out.
wlan0: CTRL-EVENT-DISCONNECTED bssid=f8:df:a8:33:0e:7f reason=3 locally_generated=1
wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=2 ssid="VHC" auth_failures=1 duration=10
wlan0: Failed to initiate AP scan
wlan0: Failed to initiate AP scan
wlan0: Failed to initiate AP scan
wlan0: CTRL-EVENT-DISCONNECTED bssid=f8:df:a8:33:0e:7f reason=3 locally_generated=1
wlan0: Failed to initiate AP scan
wlan0: Failed to initiate AP scan
wlan0: CTRL-EVENT-DISCONNECTED bssid=f8:df:a8:33:0e:7f reason=3 locally_generated=1
wlan0: CTRL-EVENT-DISCONNECTED bssid=f8:df:a8:33:0e:7f reason=3 locally_generated=1
wlan0: CTRL-EVENT-SSID-REENABLED id=2 ssid="VHC"
wlan0: SME: Trying to authenticate with f8:df:a8:33:0e:7f (SSID='VHC' freq=2452 MHz)
wlan0: Trying to associate with f8:df:a8:33:0e:7f (SSID='VHC' freq=2452 MHz)
wlan0: Associated with f8:df:a8:33:0e:7f
wlan0: WPA: Key negotiation completed with f8:df:a8:33:0e:7f [PTK=TKIP GTK=TKIP]
wlan0: CTRL-EVENT-CONNECTED - Connection to f8:df:a8:33:0e:7f completed [id=2 id_str=]
wlan0: CTRL-EVENT-DISCONNECTED bssid=f8:df:a8:33:0e:7f reason=3 locally_generated=1
wlan0: SME: Trying to authenticate with f8:df:a8:33:0e:7f (SSID='VHC' freq=2452 MHz)
wlan0: Trying to associate with f8:df:a8:33:0e:7f (SSID='VHC' freq=2452 MHz)
wlan0: Associated with f8:df:a8:33:0e:7f
wlan0: CTRL-EVENT-DISCONNECTED bssid=f8:df:a8:33:0e:7f reason=3 locally_generated=1
wlan0: SME: Trying to authenticate with f8:df:a8:33:0e:7f (SSID='VHC' freq=2452 MHz)
wlan0: Trying to associate with f8:df:a8:33:0e:7f (SSID='VHC' freq=2452 MHz)
wlan0: Associated with f8:df:a8:33:0e:7f
wlan0: CTRL-EVENT-DISCONNECTED bssid=f8:df:a8:33:0e:7f reason=3 locally_generated=1
dbus: wpas_dbus_bss_signal_prop_changed: Unknown Property value 7
Edit:
I reported this.
Last edited by rosenrot (2013-08-08 13:35:18)

rosenrot wrote:I solved it with downgrading, I think its a Bug.
1. Not exactly a solution, more like a temporary workaround.
2. Please open a bug report, although dhcpcd 6.0.5-1 works fine for me.
3. When pasting configs, code or command output, please use [ code ] tags https://bbs.archlinux.org/help.php#bbcode
like this
It makes the code more readable and - in case of longer listings - more convenient to scroll through.

Safari Plug-In Failure after upgrading Flash Player

I've got OS X 10.9.2, Maverick, running on my iMac, and Safari 7.0.3.
Today I upgraded Flash Player to 13.0.0.182 version.
After upgrading I starting receiving the error message "Plug-in Failure" in every page I opened with video broadcasting, such as Youtube for instances, and no videos would be displayed anymore.
I already reinstalled Flash Player, rebooted my machine, have all plug-ins enabled in Safari Preferences, but no success whatsoever.
Think the solution could be downgrading to the early version of Flash Player, but have no idea how to do that now, since the Adobe site only allows me to UPgrade and not DOWNgrade.
Could anyone help me with this?
Many Thanks...

From the menu bar, select
 ▹ System Preferences… ▹ Flash Player ▹ Advanced
and click Delete All. Close the preference pane.
From the Safari menu bar, select
Safari ▹ Preferences... ▹ Privacy ▹ Remove All Website Data
and confirm. Test.

Firefox boots slow after upgrading to v28

After upgrading to v28, firefox boots in 8secs instead of 1sec, only when I "Use hardware acceleration when available".
My graphics card is NVIDIA GeForce GTX 550 Ti, with 335.23 drivers installed.
The problem occurs in soft and hard boot (even if i close firefox and re-execute it.)
Is there something I could do?

If hardware acceleration in Firefox isn't working properly then you will have to disable it and possibly check if there is an update for the graphics display driver.
*https://support.mozilla.org/kb/upgrade-graphics-drivers-use-hardware-acceleration

4404 WLC stuck in boot loop after upgrade

In prepping for the upgrade to 4.1.185.0 I've got two controllers at different sites stuck in a boot loop after applying 4.0.219.0. Units will not even get to the <ESC> option menu.
ANy ideas?

Did you clear the configuration on the controller by using Option 5 in the boot menu? This will corrupt the boot image. You should not choose the clear config (option 5) from the boot menu on controllers running 3.2.78.0, 3.2.116.21, 3.2.150.6 or 3.2.150.10, 3.2.171.5 or 3.2.171.6, 4.0.155.5 or 4.0.179.8 and 4.0.179.11.

Boot problem after upgrading 2.7 to2.8

After upgrading 2.7 to 2.8 and booting the drive:
SunOS secondary boot Version 3.0
prom_panic: Could not mount filesystem
Then i have the loader debug prompt.
I can boot the drive using the installation floppy (so i see that upgrade is ok)
After booting with floppy i try "bootinstall" but it didn't change anything.
Nothing wrong in the upgrade_log.
The PC (old) is a Compaq deskpro with 2 SCSI drives.
They are two slices on the boot HD, one is for the Compaq diags the other is for solaris /. Compaq diags boot well.
Could someone help me ?
Thanks in advance,
Emmanuel
(Please excuse my poor syntax, i learn english in the manpages)

my suggestion is to learn slovakian off the linux man-pages, then install free-bsd with russian language support, learn russian with those man-pages, then install solaris with the swedish language option and learn to speak man pages there

[Solved]Black screen after "waiting for udev uevents to be processed"

Hello friends,
Starting from late Dec., my laptop goes black screen after "waiting for udev uevents to be processed", after updating kernel to 2.26.32.*. The strange thing is that even the screen is black, the keyboard is working. For example, I can turn on/off the status lights of capslock and others. I guess something might be wrong with udev uevents configuration with regard to the latest kernel. I've noticed that in the new kernel, there are two drivers for intel integrated graphics. My laptop has a 855G, which is supposed to be functional by both drivers, at least according to the kernel description. Maybe because the udev is configured to use the second driver (for newer graphic chips), rather than the first driver, which caused the problem?
Regards,
Wen
Last edited by Wen (2010-01-28 13:14:28)

Have a look here: http://bbs.archlinux.org/viewtopic.php? … 70#p695670

[Solved]Terminology - Broken after upgrade

After running a system update it appears that Terminology is no longer working correctly.
i.e:
Background does not render properly, just shows black screen, Cannot use rightclick to make modifications, etc
Has anyone else experienced this issue?
=====================================
Fix:
Downgrade to package 0.6.1-1 from cache
pacman -U /var/cache/pacman/pkg/terminology-0.6.1-1-x86_64.pkg.tar.xz
=====================================
Last edited by cyberpsych0sis (2014-11-12 02:59:41)

jasonwryan wrote:
Start it from another terminal and see what error it prints...
Also, please paste the list of packages that were included in your last upgrade.
Output from the pacman.log after upgrade:
[2014-11-11 18:21] [PACMAN] Running 'pacman -Syu'
[2014-11-11 18:21] [PACMAN] synchronizing package lists
[2014-11-11 18:22] [PACMAN] starting full system upgrade
[2014-11-11 18:30] [PACMAN] upgraded at-spi2-core (2.14.0-1 -> 2.14.1-1)
[2014-11-11 18:30] [PACMAN] upgraded avahi (0.6.31-13 -> 0.6.31-14)
[2014-11-11 18:30] [PACMAN] upgraded ca-certificates-mozilla (3.17.1-1 -> 3.17.2-1)
[2014-11-11 18:30] [PACMAN] upgraded calibre (2.8.0-1 -> 2.9.0-1)
[2014-11-11 18:30] [PACMAN] upgraded kmod (18-1 -> 18-2)
[2014-11-11 18:30] [PACMAN] upgraded libsystemd (216-3 -> 217-6)
[2014-11-11 18:30] [PACMAN] installed lz4 (123-1)
[2014-11-11 18:30] [PACMAN] upgraded systemd (216-3 -> 217-6)
[2014-11-11 18:30] [PACMAN] upgraded colord (1.2.3-1 -> 1.2.5-1)
[2014-11-11 18:30] [PACMAN] upgraded curl (7.38.0-3 -> 7.39.0-1)
[2014-11-11 18:30] [PACMAN] upgraded dhcpcd (6.6.0-1 -> 6.6.1-1)
[2014-11-11 18:30] [PACMAN] upgraded gcc-libs (4.9.1-2 -> 4.9.2-1)
[2014-11-11 18:30] [PACMAN] upgraded poppler (0.26.5-1 -> 0.28.1-1)
[2014-11-11 18:30] [PACMAN] upgraded evas_generic_loaders (1.11.2-1 -> 1.11.2-2)
[2014-11-11 18:30] [PACMAN] upgraded fakeroot (1.20.1-1 -> 1.20.2-1)
[2014-11-11 18:30] [PACMAN] upgraded gcc (4.9.1-2 -> 4.9.2-1)
[2014-11-11 18:30] [PACMAN] upgraded gnutls (3.3.9-1 -> 3.3.10-1)
[2014-11-11 18:30] [PACMAN] upgraded gstreamer (1.4.3-1 -> 1.4.4-1)
[2014-11-11 18:30] [PACMAN] upgraded gst-plugins-base-libs (1.4.3-1 -> 1.4.4-1)
[2014-11-11 18:30] [PACMAN] upgraded gst-plugins-base (1.4.3-1 -> 1.4.4-1)
[2014-11-11 18:30] [PACMAN] upgraded gtk3 (3.14.4-2 -> 3.14.5-1)
[2014-11-11 18:30] [PACMAN] upgraded ldns (1.6.17-1 -> 1.6.17-2)
[2014-11-11 18:30] [PACMAN] upgraded libedit (20140620_3.1-1 -> 20141030_3.1-1)
[2014-11-11 18:30] [PACMAN] upgraded libffi (3.1-2 -> 3.1-3)
[2014-11-11 18:30] [PACMAN] upgraded libltdl (2.4.2-14 -> 2.4.2-15)
[2014-11-11 18:30] [PACMAN] upgraded libtool (2.4.2-14 -> 2.4.2-15)
[2014-11-11 18:30] [PACMAN] upgraded logrotate (3.8.7-3 -> 3.8.8-2)
[2014-11-11 18:30] [PACMAN] upgraded man-db (2.7.0.2-2 -> 2.7.1-1)
[2014-11-11 18:30] [PACMAN] upgraded mesa-dri (10.3.2-1 -> 10.3.3-1)
[2014-11-11 18:30] [PACMAN] upgraded mesa (10.3.2-1 -> 10.3.3-1)
[2014-11-11 18:30] [PACMAN] upgraded mesa-libgl (10.3.2-1 -> 10.3.3-1)
[2014-11-11 18:30] [PACMAN] upgraded nss (3.17.1-1 -> 3.17.2-1)
[2014-11-11 18:30] [ALPM] warning: /etc/pacman.d/mirrorlist installed as /etc/pacman.d/mirrorlist.pacnew
[2014-11-11 18:30] [PACMAN] upgraded pacman-mirrorlist (20141028-1 -> 20141108-1)
[2014-11-11 18:30] [PACMAN] upgraded poppler-glib (0.26.5-1 -> 0.28.1-1)
[2014-11-11 18:30] [PACMAN] upgraded python-pygments (1.6-4 -> 2.0.1-1)
[2014-11-11 18:30] [PACMAN] upgraded systemd-sysvcompat (216-3 -> 217-6)
[2014-11-11 18:30] [PACMAN] upgraded terminology (0.6.1-1 -> 0.7.0-1)
[2014-11-11 18:30] [PACMAN] upgraded xorg-server-common (1.16.1-1 -> 1.16.2-1)
[2014-11-11 18:30] [PACMAN] upgraded xorg-server (1.16.1-1 -> 1.16.2-1)
And when I run Terminology from Xterm it doesn't seem to provide any errors.

[Solved] Boot failure after upgrade to udev 0.84

Similar Messages

Maybe you are looking for