I have kuduz installed but am wondering if there is a way to probe hardware with Fedora without having to reboot? Ioscan command is not found in my terminal and I can't find it in my Package Manager or a RPM search. A GUI version would also be of interest but not mandatory.I'm a Mandriva defector that is wheening off of Drake Tools.
View 2 Replies
If i install new hardware using a vmguest or physical system How can I detect it.
disk
nic
memory
etc.
In AIX we just run cfgmgr -v. Is there a similar command in Red Hat?I am guessing a reboot will pick it up if the device drivers are common enough and in the kernel already. I want to know how to do this dynamically with the system on-line if possible.
I just installed Fedora 11 on an AMD CPU PC. I get the following error during boot up.Aug 22 21:42:07 dragon8 kernel: aic7xxx: probe of 0000:00:0a.0 failed with error -38 Because the aic7xxx has the error, it does not load the st module. I manually loaded the st module, but the /dev/st? devices do not get created, I assume because of the aix7xxx error.I can access the Adaptec AHA-2940W Bios during boot up and see the 2 tape drives that are connected to it.
View 2 Replies View RelatedI am trying to use a rig with Gigabyte GA-880GA-UD3H mother board and Intel 82574L based NIC (EXPI9301CTBLK) under CentOS 5.5. Unfortunately I have issue with the NIC - during boot it fails to initialize:
[Code]....
I receive the same result with the original e1000e driver from the distribution, the latest elrepo driver and the latest driver from Intel site (as seen in the example). I have tried also 2.6.37 kernel version - with the same result. The adapter however works fine under Windows (MiniXP from Hiren's BootCD) and with Ubuntu 10.10 LiveCD.
I have a new F12 install, and my syslog is filling up with messages about USB. I have 2 USB devices plugged in directly to the mobo (bluetooth keyboard receiver, touchscreen), and it keeps redetecting them and then disabling the port for some reason.
A small sample of what keeps on repeating:
Quote:
I have a problem with the GM45 Chipset of Intel in Linux Debian amd64. My machine is a laptop Dell Inspiron 1545.The command lspci correctly list this device but i can't change the resolution and preferences. Also my monitor doesnt show a high quality image.Another question, how can I probe my video performance in Debian?
View 2 Replies View RelatedI have two dual boot systems, each running Fedora 11 and a version of Windows.When I boot into Windows after running Fedora on either, the Windows time is wrong and I have to reset it. But, if I reboot from Windows into Windows, the Windows time is right . I think this results from different ways Fedora and Linux keepi track of time and what they do to the real time hardware clock.Could someone explain exactly what is going wrong and how I can resolve the problem?
View 1 Replies View RelatedI upgraded to Fedora 10 using preupgrade. It installed fine and everything loaded fine. Unfortunately the mouse would not work so I restarted my laptop. Now Fedora won't load at all the PC just turns on then keeps rebooting itself. I really want to avoid using the recovery disk. How to rectify?
View 1 Replies View RelatedHow can I restart the X server without rebooting? This used to be "CTR-ALT-BACKSPACE",but that doesn't seem to work anymore.
View 11 Replies View RelatedAbout 2 weeks ago i installed ubuntu 10.10 and downloaded fresh network drivers. I ran autorun.sh, the module was compiled and installed, i could see it with lsmod. But after rebooting the old module appeared again, but no file for him were in modules directory because autorun.sh removed old module file. Some time passed and I figured out that it is initrd who is guilty. I couldn't check it because i already deleted ubuntu and installed Fedora 14 Beta. Today i tried to repeat my steps and installed new network module on Fedora. But when i rebooted and started again i was surprised - new module works instead my old one. Everything is fine So, my question, does Fedora use initrd? I saw some files in /boot that which are initrd files (as i think). Or may be not every fedora system uses initrd or something else?
View 7 Replies View RelatedMy laptop (as many others) has a hardware switch which turns wireless/bluetooth disabled. If after booting up the system I switch on this key, the wireless would still remain disabled and I need to reboot the system to be able to connect to any network.
I have tried
Code:
rfkill unblock all
ifconfig wlan0 up
Is there any way to activate wireless without rebooting the system?
Internet worked great.
Now while booting there's an error message that says something like, smbus2 probe smb2 not found. While this is on the screen the background turns green.
The networking applet shows the network present but will not accept the security password and connect.
I have a clean install of mythbuntu 10.10 and I am trying to get a DVB-T USB stick working for the last 2 weeks. Its a MobiDTV and it seems to have the same chipset/USB ID as EzCap_DVB_T_Stick. I followed the instructions on the [URL] and eventually got the driver compiled (I had to amend some code, change "Bool" pointers to "bool" and add a FIRMWARE MAX_NAME 30 constant). I also copied the af9035 FW file to the firmware directory.
lsusb:
Bus 002 Device 004: ID 15a4:1001 Afatech Technologies, Inc. AF9015/AF9035 DVB-T stick
but it is not working; probe is failing:
dmesg:
[ 105.104195] DRIVER_RELEASE_VERSION : v2.0-1
[ 105.104203] FW_RELEASE_VERSION : v8_8_52_0
[ 105.104209] API_RELEASE_VERSION : 200.20081203.0
[ 105.110713] [Device_init] Error 1
[ 105.110733] dvb_usb_af903x: probe of 2-5:1.1 failed with error 9
I bought the hardware with Windows 7 MCE in mind. I have no Windows 7 disk so I installed Mythbuntu on it to see if build was solid and now I don't want Windows any more.
I'm looking through dmesg and see
Code:
nvidia: probe of 0000:00:03.5 failed with error -1
the corresponding bus is
Code:
00:03.5 Co-processor: nVidia Corporation MCP79 Co-processor (rev b1)
Subsystem: nVidia Corporation Device cb79
Flags: 66MHz, fast devsel, IRQ 16
Memory at 93300000 (32-bit, non-prefetchable) [size=512K]
Kernel modules: nvidia
from where I infer that the module is correctly loaded though. Do you guys know what is the -1 error code? is there any way I could check if the coprocessor is currently working?
I'm using Probe to monitor Tomcat5. The problem is that I've multiple instances of Tomcat.Can be used Probe to monitor multiples instances of Tomcat without having to deploy it to each instance?
View 2 Replies View RelatedOS:Debian Linux 2.6.32-5-amd64 Should i need to worry about these error messages? If 'Yes', how to check and fix? When it boot,
/var/log/syslog
Mar 2 23:29:03 ipb167 kernel: [ 1.465629] PM: Error -22 checking image file
Mar 2 23:29:03 ipb167 kernel: [ 4.110123] amd64_edac: probe of 0000:00:18.2 failed
[code]....
I am having trouble upgrading from old grub to grub-pc. I have a clean install of 9.10 on a system with a new ASUS motherboard with Nvidia RAID configured as RAID 0.Although I read the page on SATA pseudo-RAID, this doesn't seem to apply, as both 9.10 and Windows XP installed cleanly without any additional drivers required.I did notice that contrary to the documentation, 9.10 installed with grub v0.97, not the new one as claimed. It is working fine, but just to be ornery, I'm trying to upgrade to the new one, and this is where I ran into trouble.Whenever I try to run grub-upgrade, I get an error from grub-probe that 'no mapping exists for' my raid partition. Apparently grub-probe can deal with the device, but not with the fs_uuid, as follows:
twescott@latitude:~$ sudo grub-probe -t device /boot/grub
/dev/mapper/nvidia_fcacbeib5
twescott@latitude:~$ sudo grub-probe -t fs_uuid /boot/grub
grub-probe: error: no mapping exists for `nvidia_fcacbeib5'
The system seems to be recognizing the RAID with no problems, as in:
twescott@latitude:~$ sudo blkid
/dev/mapper/nvidia_fcacbeib1: UUID="28D83EB2D83E7DDE" TYPE="ntfs"
/dev/mapper/nvidia_fcacbeib2: UUID="4344165e-07c3-4da6-b640-da9bf964a74e" TYPE="swap"
/dev/sda: TYPE="nvidia_raid_member"
[code]....
I'm thinking the problem may be in my grub device.map file, which only lists the SATA raw device aliases, but I may be completely wrong:
twescott@latitude:~$ cat /boot/grub/device.map
(hd0) /dev/sda
(hd1) /dev/sdb
Since i installed fedora 12 i cannot successfully shutdown or reboot my pc as was possible with fedora 11: i already tried with no luck with desktop button, the commands 'poweroff', the 'shutdown -h now' and the 'reboot' but the system go to the bliking cursor and hangs without powering off (and reboot while requested). And i have to hard poweroff the system... (GRRRR)If i go on the console I can only see the system terminating services and saying "halting system" and then hangs...
Now i have kenel 2.6.32.12-115.fc12.i686.PAE, but this problem happened with last 5 preceeding.I use the mjm installation guide since fedora 7 (or later) and i had the following HW (lspci).
My fedora 14 is upgraded from fedora 13, which was upgraded from fedora 12. Everything seems fine, but recently I met across a very strange thing.Fedora 14 shutdown properly, but it won't reboot. It will hang at the last step(I guess that is the last step: [*****.*****] Restarting system.The picture of the last steps before it hangs is attached. Please someone give me a hint how to diagnose it ?
View 6 Replies View RelatedIt is my first time to install fedora 13 and touch linux system.
I burn the DVD edition to install offline. The installation completed and rebooted the system. However, the process stop at the startup screen. And I press escape and find that the process stops at following line: Starting Avahi daemon ...
I don't konw what this line means and how I can deal with.
My computer specification:
CPU P4 2.66GHz
RAM 512M DDR400
Motherboard GA-8IPE775-G
Display Geforce 6200
I have downloaded the latest iso from the Fedora site (15 32-bit). I am using a netbook and so I have used the tool suggested on the site to copy the iso to my usb drive. Before this I formatted it to fat32 in Windows and then used the tool. When I rebooted with my USB drive, all that shows is a blinking _. I tried repeating the process again but the same happened.
View 1 Replies View RelatedWe have a server running CentOS 5 Linux 2.6.18-128.1.16.el5xen #1 SMP Tue Jun 30 06:39:23 EDT 2009 x86_64 x86_64 x86_64 GNU Linux. We've seen at random times that the server will just reboot and nothing is logged in messages. I tried to enable kdump but was only able to get a 5.4 gig dump since our /var directory is set to 10GB. Here is the messages I see before and after the server restart. I had thought that when a kernel panics, it is supposed to halt the system and not reboot it. My /proc/sys/kernel/panic is set to 0. I can run an update but want to have some sort of idea what is causing the issue and if the update will fix anything.
May 13 20:05:22 hlotmt01 xinetd[3609]: EXIT: bpcd status=0 pid=1071 duration=1(sec)
May 13 20:05:22 hlotmt01 xinetd[3609]: START: bpcd pid=1072 from=10.203.1.1
May 13 20:05:23 hlotmt01 xinetd[3609]: EXIT: bpcd status=0 pid=1072 duration=1(sec)
[code]....
I'm having troubles using this not so new webcam. I didnt found any thread that have a problem like mine. In older kernel versions the webcam started working compiling and installing zc3xx module, but as far as I googled and lsmod this module now comes with default kernel. As I can see, the module itself recognizes the webcam, but fails in the process.Does someone have some idea of fixing? Should I report it to launchpad (and so, which section?)?
View 2 Replies View RelatedI updated Fedora 14 with the new kernel-2.6.35.12-88.fc14.i686 but when I reboot its rebooting automatically after showing the bios. What can I do now.
View 3 Replies View Relatedis it possible to restart /start/stop all services at the same time without rebooting?
View 3 Replies View Related"Sleep" is not supposed to permanently kill off the network service. restarting the NetworkManager / network services DOES NOT WORK. Why this blatent and crippling bug is allowed tp persist? I dont want to "rasberry reboot" like windows, this has been the only forced reboot
View 4 Replies View RelatedI just downloaded Fedora 10, burned the CD, installed the program, etc. Everything went just fine, but after rebooting the screen turns gibberish, totally unreadable. I now it's the video card, NVIDIA but how do I fix it? I installed Fedora 8 which worked just great, no issues. My machine is Intel Core 2 7300, Geforce 9600GT my other machine, is AMD-64 5000, Geforce 9500 GT, same problem happens when trying to install Centos 5.
View 5 Replies View RelatedI've installed Squeeze 2.6.32-5-amd64 on my laptop (Alienware M17X R3, Intel i7 Sandybridge, ATI Technologies Inc Broadway [ATI Mobility Radeon HD 6800 Series])The screen is 17", with maximum resolution of 1920 x 1080. After a default install of the operating system, the maximum resolution I can select is 1280 x 1024.My research so far has suggested that I need to edit the /etc/X11/xorg.conf file and provide xorg with the necessary resolution.
Again, by default, the xorg.conf file is not created. This leads me to believe that xorg is scanning my hardware at startup and providing me with whatever it thinks is appropriate. I tried following these instructions to generate an xorg.conf file. This process created an xorg.conf file under /root/.
When I copy this xorg.conf file to /etc/X11, I get a blank (i.e. black) screen. Deleting this file restores the default resolution 1280 x 1024.This system is dual booting with Windows 7. Under windows I am able to get a 1920 x 1080 resolution, so I know my hardware is up to it.At this stage I have yet to install the drivers for the Radeon graphics card.What are my options regarding configuring xorg to give me a higher screen resolution?
Code...
To find the appropriate firmware without knowing the make or brand of your wireless chip, you can use the command:
#fw-detect
But apparently debian package do not offer this useful tool, well, certainly for sidux exclusively.
Is there a package of fw-detect eventually?
I created a new partition in Windows Vista which, after rebooting, screwed up Grub. I believe that I need to reinstall Grub and everything should be fine, and I remember reading the command to do this on this forum, but I can't find it. When I boot, I now get a black screen with white letters instead of the Grub boot menu. It says something about "Minimal Grub" at the top and gives me a prompt that looks like this.
grub>
I can boot the live CD and I have internet access with it, but I can not remember the terminal command to repair Grub. Can someone tell me this command?
