Another nb question: network won't start at boot

I am running Arch 0.5 in a notebook with a 3c574 pmcia card (3com). I've set everything up (gateway, dns, etc) and installed cardmgr... when i load it and type "/etc/rc.d/network start" everything works fine.. the problem is that the network is not loading at boot, i have to start it manually every time the system is restarted (already tried adding network start to rc.local). The DAEMON array is like that:
DAEMON=(pcmcia network crond inetd)
Can i get it work by itself?
Ps: sorry about any gramatical errors, english is not my primary language

i've tried a workaround like that... made a rc script with "/etc/rc.d/network start" and added it before "network" in the daemons array... it worked, but i still get the loading errors. Look at the last lines of my boot sequence (i had to write it by hand heheh):
[ Starting PCMCIA Services BUSY ]
/sbin/ifconfig eth0 down
cardmgr[111]: watching 2 sockets
DONE ]
[ Starting Network BUSY ]
SIOCSIFADDR: No such device
eth0: unknown interface: No such device
SIOCSIFNETMASK: No such device
SIOCSIFBRDADDR: Cannot assign requested address
FAILED ]
[ Starting Network DONE ]
[ Starting Cron Daemon DONE ]
[ Starting inetd DONE ]
DAEMON=(pcmcia crond [maybe something else here] network inetd)
i'll try that too hehe, thanks

Similar Messages

Newbie question :network can't start

i install archlinux in vmware4 workstation on win2003(my network card is sis-900) ,but i found the network can not start.
now how can i solve this problem?
plz don't tell me reinstall!

Aaah, we're getting closer now.
Now if you'd tell us why using the aptly named module "sis900" won't do the job, I or someone else might get close to helping you out. If you simply don't know how to load this module at all, I suggest you read the manpage to "modules.conf", that's what it's there for. In most cases the line "alias eth0 sis900" added to this file will do the trick nicely, and automagically load the module when the eth0 device is somehow accessed, for example during network setup.
No, you don't need to reboot to try that out. After you've made changes to the rc.conf or modules.conf, simply try restarting the networking subsystem only with the command /etc/rc.d/network restart or /etc/rc.d/network start, and have a look at the results with ifconfig, which should display your eth0 device on success. Again, the manpages and documentation are your friend. Check the message log and dmesg if the module loading somehow doesn't work, error messages are dumped there.
Noticed I'm still guessing what your actual problem might be? Refine your question. Guessing costs time I don't really have.
Greets,
Dennis

Network won't start @ boot since recent hotplug update

Hello All,
The recent hotplug update rendered my network inoperable. Previous to the recent hotplug update network had no issues at all.
At boot, the network daemon is returning FAILED (in all red)
FYI: I tried the Wiki site before posting but it's down for some reason.
As root, if I manually "network start", usually it fires up, occasionally it does not, and requires a second attempt. It has never failed beyond the second attempt.
Action Taken: In the rc.conf file I removed hotplug. After reading some threads here, it looks like many of you have done the same thing. I put the required modules I know my system needs into the modules section of the rc.conf file, in the order that they are needed.
The result? No change in behaviour! I still have to login as root, and issue a "network start" to get the thing on it's feet. After that... it's smooth sailing.
I noticed in the network script itself a sleep 2 statement. I know what this does, but I wonder if the new setup that came down the wire with this AM's pacman -Syu, needs another one of these sleep statements somewhere else in the network shell script.
Suggestions and assistance is appreciated.
Sincerely,
Dave Babb

first, what are the stats on your machine - if it's slower, it *is* possible that the module isn't fully probed at the time of the network request.
SuperMicro dual 2Ghz Xeons, 400Mhz front side bus, 1gb of ram
second, post your full rc.conf here
# /etc/rc.conf - Main Configuration for Arch Linux
# Localization
# HARDWARECLOCK: set to "UTC" or "localtime"
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: fount in /usr/share/kbd/consolefonts (only needed for non-us)
# USECOLOR: use ANSI color sequences in startup messages
HARDWARECLOCK="localtime"
TIMEZONE=US/Mountain
KEYMAP=us
CONSOLEFONT=
USECOLOR="yes"
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# Networking
HOSTNAME="Dave"
# Module to load at boot-up (in this order)
# (prefix a module with a ! to disable it)
MODULES=(parport parport_pc lp mii eepro100 matrox_w1 usbcore ohci_hcd ehci_hcd uhci_hcd usbhid soundcore snd snd_timer snd_page_alloc snd_seq_device snd_rawmidi snd_mpu401_uart snd_pcm snd_intel8x0 snd_ac97_codec snd_pcm_oss snd_mixer_oss )
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# (prefix an interface in INTERFACES with a ! to disable it)
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
# eth0="eth0 67.143.249.22 netmask 255.255.255.252 broadcast 255.255.255.255"
lo="lo 127.0.0.1"
eth0="dhcp"
INTERFACES=(lo eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# (prefix a route in ROUTES with a ! to disable it)
#gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Daemons to start at boot-up (in this order)
# (prefix a daemon with a ! to disable it)
DAEMONS=(syslog-ng crond network cups)
# End of file
third, after boot when the network is still down, paste the output of "ifconfig -a" here.
eth0 Link encap:Ethernet HWaddr 00:30:48:11:96:21
BROADCAST NOTRAILERS MULTICAST MTU:1500 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1052 (1.0 Kb) TX bytes:2950 (2.8 Kb)
Interrupt:16 Base address:0x2000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:300 (300.0 b) TX bytes:300 (300.0 b)
sit0 Link encap:UNSPEC HWaddr 00-00-00-00-31-00-00-00-00-00-00-00-00-00-00-00
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
finally, after the network fails, try pinging something before you issue a network start again - it is possible that the script may be failing at some minor part while still starting the network (this would be due to permissions on some files/dirs most likely... perhaps the dhcp pid/cache files???)
ping fails to anyone. It responds with "Network is Unreachible"
Remember, when I log in as root, from the console, and issue a "network start", the network then fires up and operates normally.
Thanks for your help.
Dave.................

IMac Won't Start Up/Boot

My iMac won't start up. I've tried holding all kinds of key combinations while I turn it on, but it doesn't even get that far. It gets stuck on a folder with the Apple picture alternating with a question mark. It doesn't do anything else for a while, and then the fan turns on (???).

This is indicative of a corrupted system or drive. The first thing to try is:
Repairing the Hard Drive
Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported, then quit DU and return to the installer. Now shutdown the computer for a couple of minutes and then restart normally.
If DU reports errors it cannot fix, then you will need Disk Warrior (4.0 for Tiger) and/or TechTool Pro (4.5.2 for Tiger) to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
If this doesn't solve the problem then you will have to reinstall OS X. If the drive tests out OK per the above then you can reinstall without erasing the hard drive:
How to Perform an Archive and Install
1. Be sure to use Disk Utility first to repair the disk before performing the Archive and Install.
2. Do not proceed with an Archive and Install if DU reports errors it cannot fix. In that case use Disk Warrior and/or TechTool Pro to repair the hard drive. If neither can repair the drive, then you will have to erase the drive and reinstall from scratch.
3. Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When you reach the screen to select a destination drive click once on the destination drive then click on the Option button. Select the Archive and Install option. You have an option to preserve users and network preferences. Only select this option if you are sure you have no corrupted files in your user accounts. Otherwise leave this option unchecked. Click on the OK button and continue with the OS X Installation.
4. Upon completion of the Archive and Install you will have a Previous System Folder in the root directory. You should retain the PSF until you are sure you do not need to manually transfer any items from the PSF to your newly installed system.
5. After moving any items you want to keep from the PSF you should delete it. You can back it up if you prefer, but you must delete it from the hard drive.
6. You can now download a Combo Updater directly from Apple's download site to update your new system to the desired version as well as install any security or other updates. You can also do this using Software Update.
Why reward points?(Quoted from Discussions Terms of Use.)
The reward system helps to increase community participation. When a community member gives you (or another member) a reward for providing helpful advice or a solution to their question, your accumulated points will increase your status level within the community.
Members may reward you with 5 points if they deem that your reply is helpful and 10 points if you post a solution to their issue. Likewise, when you mark a reply as Helpful or Solved in your own created topic, you will be awarding the respondent with the same point values.

[SOLVED - partly] Minidlna won't start on boot, but OK otherwise

I am using an up-to-date system as of 2012-11-13. The problem is that minidlna fails to start on boot:
minidlna.service - minidlna server
Loaded: loaded (/usr/lib/systemd/system/minidlna.service; enabled)
Active: failed (Result: exit-code) since Tue, 2012-11-13 07:53:55 CET; 1h 33min ago
Process: 401 ExecStart=/usr/sbin/minidlna -P /var/run/minidlna/minidlna.pid (code=exited, status=255)
CGroup: name=systemd:/system/minidlna.service
Nov 13 07:53:59 earth minidlna[401]: [2012/11/13 07:53:54] minidlna.c:754: fatal: No IP address automatically detected!
So I guess it has to do something with the network, I am using DHCP, with systemd + net-auto-wired.service.
I have found this: https://ask.fedoraproject.org/question/ … r-dhcp-has
They have solved the problem by changing the after part in the unit by adding: dbus-org.freedesktop.NetworkManager.target
Since I do not use networkmanager, this is not an option for me. The current, unmanipulated state of the minidlna unit is:
[Unit]
Description=minidlna server
After=network.target
[Service]
Type=forking
User=nobody
ExecStart=/usr/sbin/minidlna -P /var/run/minidlna/minidlna.pid
PIDFile=/var/run/minidlna/minidlna.pid
[Install]
WantedBy=multi-user.target
What I have noticed is that it refers to a network.target in the after section, but it seems to me that I don't have one.
I only have:
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
basic.target loaded active active Basic System
cryptsetup.target loaded active active Encrypted Volumes
getty.target loaded active active Login Prompts
graphical.target loaded active active Graphical Interface
local-fs-pre.target loaded active active Local File Systems (Pre)
local-fs.target loaded active active Local File Systems
multi-user.target loaded active active Multi-User
remote-fs.target loaded active active Remote File Systems
sockets.target loaded active active Sockets
sound.target loaded active active Sound Card
swap.target loaded active active Swap
sysinit.target loaded active active System Initialization
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
JOB = Pending job for the unit.
12 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
Edit: having run the command again with the --all prefix:
Notice: network.target loaded inactive dead Network
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
basic.target loaded active active Basic System
cryptsetup.target loaded active active Encrypted Volumes
emergency.target loaded inactive dead Emergency Mode
final.target loaded inactive dead Final Step
getty.target loaded active active Login Prompts
graphical.target loaded active active Graphical Interface
local-fs-pre.target loaded active active Local File Systems (Pre)
local-fs.target loaded active active Local File Systems
multi-user.target loaded active active Multi-User
network.target loaded inactive dead Network
nss-lookup.target loaded inactive dead Host and Network Name Lookups
nss-user-lookup.target loaded inactive dead User and Group Name Lookups
remote-fs.target loaded active active Remote File Systems
rescue.target loaded inactive dead Rescue Mode
shutdown.target loaded inactive dead Shutdown
sockets.target loaded active active Sockets
sound.target loaded active active Sound Card
swap.target loaded active active Swap
sysinit.target loaded active active System Initialization
syslog.target loaded inactive dead Syslog
umount.target loaded inactive dead Unmount All Filesystems
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
JOB = Pending job for the unit.
21 loaded units listed.
To show all installed unit files use 'systemctl list-unit-files'.
My question is what should I add to the after part to make minidlna work upon booting? Wouldn't a graphical.target be an overkill?
Thanks in advance.
Last edited by szebenyib (2012-12-02 16:45:26)

szebenyib wrote:(However I cannot access the internet that way, maybe because of a bad network file. Honestly I have some space to improve my network knowledge.)
In the case of the possible bad network file. here is what it expects. First, you need to know the router's IP address. In the following I will assume 192.168.0.1 for the router's IP address.
192.168.0.1 is common for D-Link routers, but it does vary by router manufacturer and model. I believe 192.168.1.1 is common for Linksys.
/etc/conf.d/network
interface=eth0 # ethernet port to activate, usually eth0
address=192.168.0.110 # IP address you want the minidlna computer to have. the first 3 triads must be the same as the router's IP addr in this case 192.168.0 the fourth triad can be from 5 to 250
netmask=24
broadcast=192.168.0.255 # the first 3 triads must be the same as the router's IP address and the fourth triad should be 255
gateway=192.168.0.1 # the IP address of your router
In a terminal window, enter:
systemctl restart network.service
ping -c5 127.0.0.1
which is localhost. The -c5 means ping 5 times then quit. If you get: 5 packets transmitted, 5 received, 0% packet loss then the ping was successful, which means
that the ethernet port (usually eth0) is active. If this ping is not successful, go back and check the syntax and spelling in both /etc/conf.d/network and /etc/systemd/system/network.service
If the ping is successful:
ping -c5 192.168.0.1
and ping the router.
If you cannot ping the router's IP address, then there is still something wrong in one of the two involved files. or the router's settings need to be changed.
If you can ping the router's IP address successfully and still cannot get to the internet, you probably have DNS server issues.
ping -c5 google.com
ping -c5 8.8.8.8
If you cannot ping google.com but can ping 8.8.8.8 then you have DNS problems, see Arch WIKI resolv.conf
My network is a mixture of DHCP and STATIC IP addresses. In my router, I have the DHCP server enabled to give IP addresses between 192.168.0.10 and 192.168.0.60
this gives the router 50 DHCP addresses to work with which is more that enough for my home network. The rest of the addresses between 192.168.0.61 and 192.168.0.250
can be used as static addresses. Just an example, this can be changed as necessary.
HTH
Pudge

Openntpd won't start at boot [SOLVED]

Hi all!
My system clock is perpetually off by 4 hours, and I've narrowed it down to an issue with Openntpd; it seems to be refusing to start at boot time. Here are the relevant lines from daemon.log:
Sep 1 21:30:26 raskolnikov ntpd[1440]: Terminating
and the output of ps aux | grep ntpd:
[raskolnikov@raskolnikov ~]$ ps aux | grep ntpd
ntp 1323 0.0 0.0 3184 700 ? S 17:32 0:00 /usr/sbin/ntpd -s
root 1332 0.0 0.0 3292 256 ? Ss 17:32 0:00 /usr/sbin/ntpd -s
1000 1412 0.0 0.0 3616 800 pts/0 S+ 17:33 0:00 grep ntp
I can manually restart the daemon via /etc/rc.d/openntpd restart, which works fine, and the time is set correctly. However, when I reboot, the adjustments are wiped out, and the daemon does not start again (same message in daemon.log). I have the default ntpd.conf. I have found very little helpful information on Google, I would greatly appreciate it if someone could point me in the right direction, I've wasted quite a few hours this evening working on this problem! Thanks!
Edit: Just in case it's helpful, here is my daemons array from rc.conf:
DAEMONS=(syslog-ng !network acpid eee hal networkmanager netfs crond openntpd bitlbee)
Last edited by happycodemonkey (2009-09-02 03:55:46)

I've had this problem too, although I do not use networkmanager. I've found that openntpd fails to configure itself properly if the network is not up when it starts (in my case this happens when I background the network daemon and start openntpd in the daemons array).
My current working solution* is to add this line to rc.local:
(sleep 300 && /etc/rc.d/openntpd start) &
That will wait 5 minutes before starting the openntpd daemon which gives the network more than sufficient time to start. An alternative would be run "/etc/rc.d/openntpd restart" in an hourly cronjob if your network settings change often.
* Why not just unbackground the network daemon you ask? If the network isn't up then it takes a while to timeout and I don't want to wait to boot in that case.
Last edited by Xyne (2009-09-02 02:05:52)

Urgent Question:Indesign won't start up

the program indesign from CS5 Design premium has decided to just stop opening & running. I've re installed it 2x. It won't accept updates. this is ridiculous. Pay a lot for the programs so its not fun when they just stop working.

Some of my suggestions
If you are using windows OS, you can try opening the application as "Run as Administrator".
while installing the Design premium, did you install the full pack or just InDesign. try installing full pack or vise versa.
check for the system requirement before installing the software.
login to your system as admin and try installing it again.
if anything did not work, try installing it in another computer. If it works then the issue could be in your OS. you can format and install the OS again.
last chance is contact Adobe support.
hope it helps.

Downloaded Software Won't Start at Boot

I have downloaded and installed the ClamXav application and ClamXav Sentry. However, each time I boot, I receive a message that each program has been downloaded to the computer on a certain date and would I like to open it. My question is, why won't each program load automatically at log in? I have placed both items in my Login list in my Accounts Preferences.
ACP

Alan Pease wrote:
Thanks for the suggestion, V.K. I have now installed the apps in the Admin account as well as my user account.
what do you mean by that? the application should be installed only once for the whole computer. you have to launch it once from an admin account and it will stop bugging you. did you do that?

Firefox won't start on boot

I have a sporadic, but consistent problem with Firefox. Shortly after booting the computer, I try to launch Firefox, but it doesn't start. I open the task manager and can see firefox.exe running under the Processes tab. I will be patient, having waited for other things that might be monopolizing the memory (such as a startup AV scan) to finish. A couple of times, I waited as long as ten minutes, but the Firefox window never opened. My only solution is to reboot the computer. At that point I get several error messages:
"DDE Window Server not responding / End Program?"
and
"Acrodist.exe not responding / End Program?"
and then "Firefox is not responding / End Program?"
I did research on DDE Server Window and found that I could disable it in Windows Services - which I did. Yet, the error message still appears.
Running Windows XP with SP3.
Thanks for any help!

Hello gabryant, sometimes a problem with Firefox may be a result of malware installed on your computer, that you may not be aware of.
You can try these free programs to scan for malware, which work with your existing antivirus software:
* [http://www.microsoft.com/security/scanner/default.aspx Microsoft Safety Scanner]
* [http://www.malwarebytes.org/products/malwarebytes_free/ MalwareBytes' Anti-Malware]
* [http://support.kaspersky.com/viruses/disinfection/5350 Anti-Rootkit Utility - TDSSKiller]
* [http://general-changelog-team.fr/en/downloads/viewdownload/20-outils-de-xplode/2-adwcleaner AdwCleaner] (for more info, see this [http://www.bleepingcomputer.com/download/adwcleaner/ alternate AdwCleaner download page])
* [http://www.surfright.nl/en/hitmanpro/ Hitman Pro]
* [http://www.eset.com/us/online-scanner/ ESET Online Scanner]
[http://windows.microsoft.com/MSE Microsoft Security Essentials] is a good permanent antivirus for Windows 7/Vista/XP if you don't already have one.
Further information can be found in the [[Troubleshoot Firefox issues caused by malware]] article.
also, delete in your [http://kb.mozillazine.org/Profile_folder_-_Firefox#Windows profile folder] the [http://kb.mozillazine.org/User.js_file User.js] file you already have(except if you created).
The user.js file does not exist by default. If you create the file, forget it, if you have not create the file then delete the User.js file, to see if the problem goes away (some programs create and write in the file also).
thank you

XP Installation won't start using Boot Camp-any ideas?

When I put my XP SP2 disk into my us cd drive Boot Camp Assistant recognises it and restart my Mac Air Book. It then goes to the white screen as it boots up and an alternating folder sign with a question mark in it and a no entry sign (circle with a diagonal line through it) are displayed in the center screen indeffinitely. After the white screen comes up and before the symbols there is about 10 seconds as the cd drive appears to initialise and briefly accesses data.
I am unable to get passed this and so can'r install XP. I have partitioned the disk using Boot Camp. Any ideas? Is it the CD disk or drive, or is it a problem with my MAC Air Book?
Thanks very much in advance!
737guru.

EsseBoy wrote:
no mine's a 20 inch and I bought it last year.
i have installed windows on it before and then i removed it. I tried to install it again but permissions wasn't letting me so i refreshed my mac and now its going all dodgy on me
There's a lot of missing information here!
1) How did you remove it?
2) What do you mean by "permissions wasn't letting me"?
3) How did you "refresh" your Mac? Did you reinstall OS X through Erase & Install?
4) In what way(s) is it being "dodgy"?
~Lyssa

MBP won't start or boot up

Hi all, new to the mac world but learning alot! I have owned my Pro for 8 months now and work 50% of time in Thailand. This recent trip, my MBP simply stopped booting up. It starts fine with the normal start chime, noise from CD drive, then white screen with apple logo and spinning wheel. That's as far as it gets. I started using command s for single user and did a repair of the HD. This worked, I then rebooted using start up disk and pressing C. Still not starting, stopping at logo and spinning wheel. I then went to command v and watched for hang up. It seems to stop and repeat trying to access (com.apple.mDNSResponder [311]: posix_spawnp("/usr/sbin/mNDSResponder", ... No such file or directory.
I am at a loss as to what this is and how to get past this. I do remember that the last time I was on the machine, 3 days ago, I changed the permission of the hard drive for guests to read only. I am wondering if this is the problem. When I started in single mode, the root is read only. How can I change this if I need to? I am far from any mac repair facility and am 4 weeks from going back to Vancouver, soooo, I am hoping someone out there can assist me. I don't mind typing commands in at the root, I just don't know the language. I am working from a borrowed Toshiba for the time being, but I am missing my mac. Long and short of it is if I have to reformat, I don't mind, I have my install disks with me. Thanks

Okay, so no whiz kids have read this post yet. I got a little further by getting the cd drive to boot in single user, however it too stopped at a unable to read and write to someplace, this may be RAM problems, will try booting from one and the other RAM set independently, more to follow.

Won't Start after boot

Alright after I type in my password my background shows and so does my mouse clicker. I can move the clicker around,raise volume,etc the problem is that my menu bar in the bottom and my top bar never show except for the search button on the top right of the screen. Only that when I try to click on it, the mouse tells me that it is loading, what is the problem? I thought it would take a it a while to load, but doing that hasn't helped either.
This barely happened this morning after downloading the new itunes and quicktime updates and after restarting my computer, I don't want to lose all my files since I'm starting to think resetting the computer is the only way I'm going to be able to fix it.
Anybody please help!

Alright after I type in my password my background shows and so does my mouse clicker. I can move the clicker around,raise volume,etc the problem is that my menu bar in the bottom and my top bar never show except for the search button on the top right of the screen. Only that when I try to click on it, the mouse tells me that it is loading, what is the problem? I thought it would take a it a while to load, but doing that hasn't helped either.
This barely happened this morning after downloading the new itunes and quicktime updates and after restarting my computer, I don't want to lose all my files since I'm starting to think resetting the computer is the only way I'm going to be able to fix it.
Anybody please help!

Satellite pro A200 won't start up / boot

Hi,
my laptop is refusing to startup beyond the windows loading page, I disabled automatic restart and the message on the blue screen says:
STOP: c0000221 {Bad Image Checksum} The image oleaut32.dll is possibly corrupt. The header checksum does not match the computed checksum.
Does anyone know what I need to do?
Thanks in advance for any help.
Donal

Satellite Pro A200-16Y
Bug Check 0xC0000221: STATUS_IMAGE_CHECKSUM_MISMATCH
This indicates that a driver or a system DLL has been corrupted.
This bug check will display a descriptive text message. The name of the damaged file is displayed as part of the message.
Please give us the name of the file from the blue screen. If a path is available, be sure to include that.
If you have located an installation CD, learn to access the Recovery Console.
Description of the Windows XP Recovery Console for advanced users
-Jerry

Mac won't start with mavericks

Just tried to mbp and it won't start up

The boot drive is failing, or there is some other hardware fault.
Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.
Back up all data on the internal drive(s) before you hand over your computer to anyone. There are ways to back up a computer that isn't fully functional — ask if you need guidance.
If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you have at least two complete, independent backups, and you know how to restore to an empty drive from any of them.) Don’t erase the recovery partition, if present.
Keeping your confidential data secure during hardware repair
*An SSD doesn't need to be zeroed.

[SOLVED] Alsa won't start after upgrade

This is my last update:
[2010-07-18 08:59] Running 'pacman -Syu'
[2010-07-18 08:59] synchronizing package lists
[2010-07-18 08:59] starting full system upgrade
[2010-07-18 09:00] upgraded gtk-aurora-engine (1.5.1-1 -> 1.5.1-2)
[2010-07-18 09:00] #####################################
[2010-07-18 09:00] themes are moved in an extra package:
[2010-07-18 09:00] community/murrine-themes-collection
[2010-07-18 09:00] upgraded gtk-engine-murrine (0.90.3-1 -> 0.90.3-2)
[2010-07-18 09:00] upgraded imagemagick (6.6.2.0-22 -> 6.6.2.10-1)
[2010-07-18 09:00] Running OSS update script...
[2010-07-18 09:00]
[2010-07-18 09:00] -------------------------------------------------------------
[2010-07-18 09:00] Open Sound System was updated. Now you should restart the
[2010-07-18 09:00] daemon by running /etc/rc.d/oss restart.
[2010-07-18 09:00]
[2010-07-18 09:00] Please note that OSS stores some of its configuration files
[2010-07-18 09:00] at /usr/lib/oss. If you are upgrading from an older OSS
[2010-07-18 09:00] release and it doesn't work properly, try removing that
[2010-07-18 09:00] directory and reinstall this package.
[2010-07-18 09:00] -------------------------------------------------------------
[2010-07-18 09:00] upgraded oss (4.2_2002-2 -> 4.2_2003-1)
[2010-07-18 09:00] upgraded supertux (0.3.1-5 -> 0.3.3-1)
[2010-07-18 09:00] upgraded xine-lib (1.1.18.1-1 -> 1.1.18.1-2)
Pacman said to restart oss, so I did it. But I got loads of errors and a [FAIL], then I rebooted and got a [FAIL] for shutting down alsa.
Now alsa won't start at boot.
sudo /etc/rc.d/alsa start
Password:
:: Restoring ALSA Levels [BUSY] /usr/sbin/alsactl: load_state:1610: No soundcards found...
[FAIL]
And alsamixer won't run too:
alsamixer
cannot open mixer: No such file or directory
What can I do to fix this?
EDIT: I just removed the oss package and now it works fine
Last edited by spiridow (2010-07-18 08:17:16)

startx at the command line.
I just tried Xorg -reconfigure again, adding the AutoAddDevices = false option - still doesn't work, giving the error about config/hal. Without the option, it just goes back to the terminal with no errors.
Pacman log says the only thing upgraded today (after pacman) was the kernel, nvidia, and kernel-firmware. cdfs conflicted with the new kernel, so I removed it. Then I rebooted, and X stopped working. Downgrading those back again doesn't fix it. I don't get it.
>>EDIT:
Okay - what does cdfs have to do with Xorg???? This makes no sense. I downgraded the kernel pkgs and nvidia again, and this time installed cdfs, which I forgot to do last time. Now X starts. I don't really get it.
Maybe hal in xfce or some plugin needs to use cdfs for something?? I don't really know - but I'm just glad it's working. I guess I'll file a bug report for cdfs so it can be built to the new kernel and hold off upgrading until it's fixed with 2.6.31. sheesh! too weird.
Last edited by userlander (2009-10-10 23:27:36)

Another nb question: network won't start at boot

Similar Messages

Maybe you are looking for