OpenSUSE :: The Probing Hardware Process Gets Stuck At The Probing Monitor Phase?
Apr 7, 2010
I am trying to find out what's my soundcard model as my sound is not working very well.I am using YasT2 - > Hardware Information to find out what is the problem. The probing hardware process starts but gets stuck at the probing monitor phase (49%). I have tried to rerun the process after rebooting the pc. I have let the process to run for a few hours but still it was stuck at the 49%What should I try to do to skip this obstacle and get information about my sound hardware.
I have just installed F10 via DVD download onto my Dell Desktop with Nvidia GE6800 graphics card and twin LCD Monitors. I have configured Dual Boot with Grub (Windows XP Home and F10). After installing and configuring the correct driver from Nvidia I am now observing a strange problem when booting into Fedora.
On cold boot the system starts and gets to Probing EDD (edd=off to disable)... and then freezes, however if I then warm boot Ctrl Alt Del the system boots into F10 with no problem. I had to disable the latest Kernel update because I couldn't start graphical interface with it so I only boot into the original Kernel.
I'm new to openSUSE, this is the first time i try to install openSUSE version 11.4. on my IBM Thinkpad T43 (on which SUSE Linux version 8.0 has been running before without problems). I have downloaded the ISO images and successfully burned the ISO images on a blank DVD. Having placed my openSUSE DVD in the drive and rebooted my laptop I can see the boot screen.
I then select installation with arrow up/down and press enter. Choosing language and keyboard layout works fine, as well as accepting the license agreement. However, when it comes to 'System Probing' the installation stops at 'Search for system files'. The cursor shows a little turning disk but the rest of the screen is blocked.
Probing EDD (edd=off to disable) .... then the boot hang up for a few minutes with a flashing cursor immediately after the message and finally it booted the default OpenSuse 11.1 in the usual way. I tried to search LQ, Wikipedia, Google... but even if the message has been reported by many people, nobody gave the answer to the question running in my mind:
Code:
What is EDD? Should I start to think about the funeral for my beloved notebook? Should I consider to do an additional backup copy of the backup of my disk, just for sure?
I am testing PCLinux 2009.1 prior to installing. My desktop currently runs on ME and has been out of use for some time. It still works however and I can still get online. I'm currently using a laptop running XP. I would like to make use of my old desktop and tried to test PCLinux 2009.1 today. I followed the instructions obtained online and booted from the Linux cd. The pc booted up ok and displayed the first screen allowing me to select the "Live CD" option. After enter my system hung up at "Probing SCSI Devices:Segmentation fault".
I have a Toshiba a105-s2236 laptop and am trying to install Fedora 14. Is there any way to tell Fedora not to look for the pcmcia slots on boot? My live CD is freezing at the point where it tries to probe the pcmcia socket IO port.
I tried adding the 3 to get to a console, but that fails as well. I had to add acpi=off to the kernel boot args to even get it to go this far. Even using the nopcmcia option, it still tries to probe the socket's IO port.
The Fedora 12 (64 bit) install freezes right after the "probing EDD (edd=off) .... ok" comes up. I have to do a hard reboot to get the system back. I am currently running Fedora 8 (64bit) and everything works fine. The Fedora 11 (64 bit) install runs. (I don't really want Fedora 11, so I didn't complete the install). The Fedora 12 (32 bit) install runs. (I don't really want 32bit Fedora, so ...). The Fedora 12 (64 bit) install only runs if I add mem=xxx. (I would like to be on this version)
I'll be doing the full install soon, but what should I look for once I have it installed to figure out what the issue is? Why do I now have to pass the memory size when 8 and 11 seems to be able to figure that out? I have a dell optiplex 740 with 4Gb of ram. AMD Athlon x2 64bit processor.
im building a storage pod following the backblaze build url. This build requires two power sources. One powers the boot drive, the mother board and 20 of the hard drives while the other powers the remaining 25 drives. When I power up the 25 drives first and the boot drive etc 2nd I recieve the message "Probing edd=off to disable" the system then freezes there. If I power up the boot drive etc then the 25 drives then it boots up normally with no problems. When ever I restart I recieve the same message since the 25 drives are already running when it boots.
I dont want to add edd=off to the boot command since i cannot have some drives not being detected all the time in my raid configurations. I have tried updating the bios and that didnt help. I have also installed a different os and receive the same message.
I am running Linux version 2.6.26-2-amd64 (Debian 2.6.26-21lenny4)Motherboard: Intel BOXDG43NB LGA 775 G43 ATX Motherboard
All of my specs are the same as the ones listed in the Backblaze build.
Ksysguard has always before shown a process table on one tab and the system load charts on a second tab. Loading Ksysguard produces an error message: "The file /home/*/.kde4/share/apps/ksysguard/Processtable.sgrd does not contain valid XML." That file contains nothing, as it's size in Dolphin is 0. Have updated KDE in Yast; removed Ksysguard 4 (which installed ver. 3) then re-installed ver 4. Still lack the process table.
This is OpenSuse 11.4 on a Toshiba A665 laptop. In other respects the system works perfectly, well almost. I'm examining a large number of files recovered by scalpel from a disk image created by ddrescue. This problem appeared while working through the nnnnnnnn.doc files. Most of them open in LibreOffice, but some produce an error message ("Not a Word 95 document"), open as slides (which is OK), or seem to freeze LO (with a CPU core at 100% in ksysguard). Lacking the process table, I'm having trouble killing the LO process (ps doesn't deliver the process number as expected; still studying it).
I have a hard to reproduce (seen a couple times in a month) issue where my program seems like it is hung (not increasing in cputime), however, it is in the runnable state and never gets to run. The cpus are 99% idle according to vmstat and the load is 5 (which is equal to the number of threads in my program that are in the R state) according to ps, and there are no processes on the system in the 'D' state. The other major oddity is that one of the migration threads has a cputime usage almost equal to the uptime of the system. Typically migration threads have a cputime on the order of seconds across hundreds of days of uptime, but in this case the migration thread has DAYS of cputime according to ps.
The last time this happened, I went around saving as much /proc/X information that I could into logs for referring to later, before I had to reboot the box to get it running back to normal. (because in this state, a kill -9 is not heeded by my program)Does anyone have any idea what could cause this? I am not sure if this is a scheduling bug or a bug in my program (the likelier case).I have a wealth of logs to look through if anyone can suggest something specific to look for.
I have currently installed the ubuntu 11.04 natty narwhal edition through the wubi installer alongside windows 7. I wanted to just check out what the kde environment had to offer differently from the default desktop environment which is gnome unity environment.
I installed the kde environment using some sudo command given by google. After using kde environment for a few hours, I just began to feel, I liked the default gnome environment better (in classic mode) as compared to kde as I was more used to the former.
So I uninstalled kde with another sudo command which I got by googling. At the final step of the uninstallation, I admit I am not sure whether what I did was right or wrong. There was sth related to 'daemon' that popped up eventually and I chose yes for that and kde was uninstalled successfully or atleast that's what I thought.
But to my horror, when i tried rebooting my laptop to ubuntu gnome, the blue coloured kubuntu logo was popping once again and I had to go back to the synaptic package manager and delete sth called the 'plymouth' package to remove the kubuntu logo.
Now after doing all these, when I tried booting ubuntu, I was not able to get to the gnome login screen. The screen was just stuck with the ubuntu logo and the process bar blinking and gnome never started.
When I pressed the Esc key to check out what was happening from behind, I could see that some processes were being checked and there was a [ok] after everything and there was a [FAIL] next to "starting CPU interrupts balancing daemon". And the terminal screen ended with "stopping system V run level compatibility". I am not sure if this might be the root cause of blocking the boot-up. But I couldn't get a screenshot of those intermittent terminal screens as I was not in a position to type in any commands such as fbgrab which can be used to grab a screenshot of the terminal screen.
Eventually after intense googling, I figured how to manually configure gnome to start up. I pressed the Cnt + Alt +F1 as soon as the white ubuntu logo popped up and after logging in into my ubuntu account through the terminal interface, I typed in the following things:
And then voila I got the gnome login screen. I temporarily heaved a sigh of relief. (by the way I saw something flash quickly on the terminal moments before it went to the gnome login screen like "you need not init this way or sth"..I just couldn't catch sight of it properly as it flashed only for a few moments)
But I am not satisfied. Obviously there might be a way to set this problem right isn't it? Kindly someone pls throw some light on this issue. I want gdm to be automatically activated during boot. Its a big pain to manually configure it everytime I boot. Is it possible to do a windows restore to set the ubuntu right? But I saw in some forums mention that something called the boot.ini will botch up if we perform a system restore in win 7.
Method that does not involve uninstalling ubuntu and reinstalling it. This is because I have done a lot of tweaks, optimisations and installed lot of apps in it. I do not have a system image backup as well. So it will be a nightmare to do all these things over and over again. The mistake or rather the drawback from my side is I just have my laptop alone and do not have another standalone desktop to experiment with linux.
I am pretty new to Linux OS's, but I have gone through the process of installing linux onto several of my system already. The problem I am having is when I attempt to install Fedora 14 onto my Unbuntu 10.10 (erasing Unbuntu to be specific) I am stuck at the Post-Installation process. I am using a CD-RW to install Fedora onto my Ubuntu, and I installed Ubuntu onto the computer originally with another CD-R.
I assume this usually takes a few minutes, as the pop-up says that it may take several, but it has been several hours with no progress. I was pretty far into the installation when the pop up appeared, and it said: "Post-Installation: Performing post-installation filesystem changes. This may take several minutes.". As I said, it has been several hours.
i got basic knowledge about creating a single child from a parent using fork(). But when it comes into creating multiple children, i am simply stuck. I am trying to create two processes from a parent and it would wait for both two processes to finish. my attempt is as below
it stuck after loading. should got login window. instead it show me a blank page and a blinking courser i can only press ctrl+alt+del it will reboot my laptop n stuck after the loading process
I have currently installed the ubuntu 11.04 natty narwhal edition through the wubi installer alongside windows 7. I wanted to just check out what the kde environment had to offer differently from the default desktop environment which is gnome unity environment.
I installed the kde environment using some sudo command given by google. After using kde environment for a few hours, I just began to feel, I liked the default gnome environment better (in classic mode) as compared to kde as I was more used to the former.
So I uninstalled kde with another sudo command which I got by googling. At the final step of the uninstallation, I admit I am not sure whether what I did was right or wrong. There was sth related to 'daemon' that popped up eventually and I chose yes for that and kde was uninstalled successfully or atleast that's what I thought.
But to my horror, when i tried rebooting my laptop to ubuntu gnome, the blue coloured kubuntu logo was popping once again and I had to go back to the synaptic package manager and delete sth called the 'plymouth' package to remove the kubuntu logo.
Now after doing all these, when I tried booting ubuntu, I was not able to get to the gnome login screen. The screen was just stuck with the ubuntu logo and the process bar blinking and gnome never started.
When I pressed the Esc key to check out what was happening from behind, I could see that some processes were being checked and there was a [ok] after everything and there was a [FAIL] next to "starting CPU interrupts balancing daemon". And the terminal screen ended with "stopping system V run level compatibility". I am not sure if this might be the root cause of blocking the boot-up. But I couldn't get a screenshot of those intermittent terminal screens as I was not in a position to type in any commands such as fbgrab which can be used to grab a screenshot of the terminal screen.
Eventually after intense googling, I figured how to manually configure gnome to start up. I pressed the Cnt + Alt +F1 as soon as the white ubuntu logo popped up and after logging in into my ubuntu account through the terminal interface, I typed in the following things:
And then voila I got the gnome login screen. I temporarily heaved a sigh of relief. (by the way I saw something flash quickly on the terminal moments before it went to the gnome login screen like "you need not init this way or sth"..I just couldn't catch sight of it properly as it flashed only for a few moments)
But I am not satisfied. Obviously there might be a way to set this problem right isn't it? Kindly someone pls throw some light on this issue. I want gdm to be automatically activated during boot. Its a big pain to manually configure it everytime I boot. Is it possible to do a windows restore to set the ubuntu right? But I saw in some forums mention that something called the boot.ini will botch up if we perform a system restore in win 7.
Method that does not involve uninstalling ubuntu and reinstalling it. This is because I have done a lot of tweaks, optimisations and installed lot of apps in it. I do not have a system image backup as well. So it will be a nightmare to do all these things over and over again. The mistake or rather the drawback from my side is I just have my laptop alone and do not have another standalone desktop to experiment with linux.
I'm not sure what caused it, but it happened right after running 'yum update'. It may be because it installed a new kernel, and there are now two kernels listed in my grub.conf and at boot; 2.6.31 and 2.6.32. System boots through a list of things it's starting up and stalls out at ATL or ADL or ADM maybe. It hangs there for a minute or so then flickers. This happens every time at boot. It's a bit difficult to post more information since I can't get past that part of the boot process, and I can't seem to be able to skip it either. It may be worth mentioning that this is a mini-itx motherboard. Intel Atom 330 1.6, 2GB DDR2, onboard GeForce 9400m. It's a zotac ionitx-a-u. I've installed a fresh copy of Fedora 12 lxde.
I've been plagued with this problem for weeks. It finishes writing the DVD but after it ejects and reloads, it doesn't go through the verification process. Yet I never fail to hand-verify the DVD using 'cmp'.
In this case today I created a multi-directory DVD and had an .iso image made first. It's still sitting there in /tmp (with a backup copied to /opt so I can close out k3b). How would I verify the .iso against what's on the DVD? How does k3b do it? Hopefully this means a command line solution.
BTW what are the command line apps for burning and verifying a DVD? I'm not so hot on graphical apps for this task anymore.
I am looking for a simple process monitor to monitor CPU, ram, swap usage of selected processes and log the information to a csv file at a specified interval.
Or is there a way pipe the information I want from top to a csv file?
We have the below script, to check the process MEDT, if it doesn't run , then it will send a message immediately. the same script, if I want to check if it is continously running for more than 1 hour, then it should do the action mentioned below.
I use linux and Unix and I want to monitor the memory usage for process. To prevent memory leakage and out of memory of the system. Any command or sytnax , have more better and presentable data than below command about memory usage of one process ?
How can I periodically monitor memory usage of a process in linux.Can it be dumped in some file.So that later I can see what was the process behaviour in taking memory.
there's this process on my system monitor that opens and closes by itself it does not have a description or a name and makes my hard drive spin like hell
I have looked for and found several tools to show a system's total network usage. I have not, however, been able to find any that show this information in the context of individual processes. Do any such tools for linux exist?
I have a few AWS instances (linux micro, fedora-like) that occasionally (4x every 24hours) trip a CloudWatch monitor for CPU utilization. alarm => 85% at 5 minute slices.
The problem with this is that we're unsure WHAT is causing it. I have an idea to poll cpu usage every 5 mins and if there's a spike (eg, => 85%) then dump some process table stuff exposing the offenders.
I have Fedora Linux 13 64bit system. I use System Monitor to check which process is taking how much memory and cpu. Normally I have dozens of Chrome and Firefox windows open. The Processes tab shows which process is taking how much cpu/ram resources but I unfortunately there is no option like right click and make the window active that matches the PID (the one process that I have currently highlighted). Usually there is a chrome process taking up 30 or 40 percent of CPU while dozens other chrome processes taking much less cpu. I must determine which chrome window ( or any application which has multiple instances running) is taking that much CPU time. So can some one help me to solve this problem?
I have Fedora Linux 13 64bit system. I use System Monitor to check which process is taking how much memory and cpu. Normally I have dozens of Chrome and Firefox windows open. The Processes tab shows which process is taking how much cpu/ram resources but I unfortunately there is no option like right click and make the window active that matches the PID (the one process that I have currently highlighted). Usually there is a chrome process taking up 30 or 40 percent of CPU while dozens other chrome processes taking much less cpu. I must determine which chrome window ( or any application which has multiple instances running) is taking that much CPU time.
