Okay, my 64 bit does not have wireless at all. And under FC 8 everything still workes fine, wo what could be the solution?
Okay, my 64 bit does not have wireless at all. And under FC 8 everything still workes fine, wo what could be the solution?
Right, no Wireless....
Do you have a Ricoh Chipset (for SD/MMC slot) in your laptop ?
I dont have a laptop. I am not sure about this chipset (what ist ist?) But I have a 9 in 1 USB card reader connected (as well as a USB bluetooth dongle)
Does that help?
Yes, but for more details, can you use this command on a terminal and post here the results ?
the command is "lspci".
To use it, open a terminal window (On Gnome : Main Menu >> System >> Terminal).
In the black window, write lspci and hit the ENTER key.
This command will list all hardware that are in your PCI Bus, it will help to determine what kind of hardware you have.
Thanks!
Thanks, here the console output:
And, what do you say?Code:00:00.0 Memory controller: nVidia Corporation CK804 Memory Controller (rev a3) 00:01.0 ISA bridge: nVidia Corporation CK804 ISA Bridge (rev f3) 00:01.1 SMBus: nVidia Corporation CK804 SMBus (rev a2) 00:02.0 USB Controller: nVidia Corporation CK804 USB Controller (rev a2) 00:02.1 USB Controller: nVidia Corporation CK804 USB Controller (rev a3) 00:04.0 Multimedia audio controller: nVidia Corporation CK804 AC'97 Audio Controller (rev a2) 00:06.0 IDE interface: nVidia Corporation CK804 IDE (rev f2) 00:07.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f3) 00:08.0 IDE interface: nVidia Corporation CK804 Serial ATA Controller (rev f3) 00:09.0 PCI bridge: nVidia Corporation CK804 PCI Bridge (rev f2) 00:0a.0 Bridge: nVidia Corporation CK804 Ethernet Controller (rev f3) 00:0b.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev f3) 00:0c.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev f3) 00:0d.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev f3) 00:0e.0 PCI bridge: nVidia Corporation CK804 PCIE Bridge (rev a3) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 01:00.0 VGA compatible controller: nVidia Corporation G71 [GeForce 7300 GS] (rev a1) 05:0a.0 RAID bus controller: Silicon Image, Inc. SiI 3114 [SATALink/SATARaid] Serial ATA Controller (rev 02) 05:0b.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) 05:0c.0 Ethernet controller: Marvell Technology Group Ltd. 88E8001 Gigabit Ethernet Controller (rev 13)
Guys,
This seems to be a similar thread to:
http://forums.fedoraforum.org/showpost.php?p=1163714
I was experience spontaneous reboots on my Fedora 10, x86-64 system. My post is in that thread, but I'll repeat it here:
I'm on a Dell SC1430, dual quad, 2GB RAM, Nvidia 8800GT. I did not have any reboots or lockups under Fedora 7, the last distro I had installed on the box.
After trying two things:
1) upgrading my software to the latest version
2) trying nohpet on the kernel command line
I still got the reboots. With or without Gnome loaded. A few weeks back, I disable apic (ie, added "noapic" on the kernel command line. And I've been free of reboots.
So now, I will need to dig a little deeper and/or file a proper bug to understand why adding "noapic" seemingly resolved the issue.
'sodo
Last edited by cacasodo; 3rd March 2009 at 05:07 AM.
Some time ago, when I started with Ubuntu, I couldn't install it because I had a problem with my bios or something... It always said: MP-BIOS bug : Timer not connected to IO-APIC
so I searched for a solution, and it seemed that I had to install it with the option noapic.
Then everything worked fine,
altough I never really understood what the problem was.
Now that I use fedora (F9), I didn't use the noapic option, but everytime I boot it shows the message again.
I tried googling it,
but it seems that nobody really knows what the bug means.
maybe you could try updating your bios?
please tell me if you found an other answer to this...
Grtz,
Thomas
Has anyone tried making a fresh install?
I remember having the problem back in the early days of F10 (and nomodeset fixed it somehow). Anyway I moved to Debian for a few months and last month, but when I installed F10 x86_64 again (and forgot to use the nomodeset), after afull system update the thing hasn't complained.
Might have something to do with a weird log file or something, but could be worth a shot.
Thanks.
Joe.
Workstation: EliteDesk
AMD Ryzen 5 PRO 2600, 32GB DDR4,
256GB M.2, 480GB SSD, 1TB HDD.
Fedora 42.
Hi again!
Scott, i've saw your lsmod....you really don't have a ricoh chipset...so this is not the cause of the problem...Our ethernet are the same (Mavell), but I don't think that its crashing Fedora.
Well, I turned off my Compiz, the crashes didnt stop, but now I can "retrieve" the control of the System with the ALT+TAB keys when it stops.
Perhaps something serious combined with a light Compiz bug are doing this dirty job =(
Guys, I'm getting so confused about it.
I will try the "noapic" parameter at Grub, and if it not solve the question, I will try to Re-Install the system.
Last edited by angiolucci; 27th February 2009 at 04:31 AM.
Okay, I tried noapic, nomodeset and nohpet - but it still crashes.
I actually have an error during the startup from nvidia:
Segmentation fault in /etc/rc.d/init.d/functions - line 439
Can that have something to do with it?
Regards,
Scott
Scott,
Perhaps. You should investigate what is on line 439 of /etc/rc.d/init.d/functions
tdfranc,
Good thought. My BIOS is up-to-date, though.
angio,
in this thread on Fedora 10 lockups:
http://forums.fedoraforum.org/showth...=205950&page=1
some users make mention of changing their default window manager from Gnome to a more lightweight one, like XFCE. Read up on that thread to see if any of those suggestions help.
joe,
a full system update on my system didn't solve my reboots. Only the noapic did.
sodo
noapic does not resolve the issue. Please gave a look at this similar thread:
http://forums.fedoraforum.org/showth...=205950&page=7
Thanks cacasodo and cxsfforum.
I'm reading the similar threads.....
It's intersting, a lot of people with the same issue (or very similar), and I think it's not caused by an ATI or another graphic driver.....there are some Intel GMA (like the mine !!) such as ATI chipsets ...
Since Fedora older versions ( 8 and 9 ) aren't crashing, the cause of the problems maybe a new mechanism in Fedora 10 and not a hardware or driver issue...
Well, I'm on Fedora 9 now.....but it crashes too!!!
I Don't know what I must do to stop the random lock up.
I will give up and try another distro =(
is anybody out there to help me?
my dual boot laptop-vista/fedora10-compaq presario cq40 is not loading fedora, i rebooted several times but after showing the progression graphics, it is not showing the login screen, freezes with multi-colour screen, i am not even able to shutdown the system
infact i did some updates and installed xine and mplayer some hours back.
could you give me any suggetions