PDA

View Full Version : f7 freezes on boot if ethernet and/or eternal hd are connected



apost
11th October 2007, 04:04 AM
it also has frozen halfway through playing a movie twice now. with the movie thing, i first thought it was having some powersaving or screensaver related duel to the death, but i disabled all of those options and movies still freeze. i don't have a dvd player these are avi's that probably have the right codecs in place or why do they play fine for like an hour?

anyone got any ideas about this? i never expected fedora to freeze up so much. in fact i thought i would practically never have to reboot again! now i am hard-rebooting all the time ):

if someone can tell me how to pull up a diagnostic audit (which would probably help) i would appreciate it!

thanks! <3

-alana

ppesci
11th October 2007, 04:15 AM
For the freeze with ethernet connected, search some usefull messages in the log file /var/log/messages every line has the log time, may be you can locate something useful. About the movie, I think is a codec problem. Avi format codec is reverse egineering and some nasty things can happen.

HTH

stevea
11th October 2007, 04:24 AM
You'll find a lot of messages from apps in /var/log/messages and while booted you see the kernel and esp the driver initialization messages from "dmesg | less". Look through these for problems.

You're problem sounds odd. I suspect you have two or more distinct problems, or else some hardware problem.

Look at the network problem first. During bootup there are a lot of one-line messages as services are started. Exactly which message appears with the hang(with enet connected). Does it really hang or is just extremely slow. Misconfigured systems often stall for many minutes at the ntp time service or the sendmail service.

What program are you using to play AVI's ?

Here are some package install/config notes. http://www.gagme.com/greg/linux/f7-tips.php

apost
11th October 2007, 06:32 AM
i am using mplayer.. i followed the steps outlined on a few of the FAQ sites in the "read here first linux n00b" thread(s).

although i install things using su, i think maybe if i was logged in as root every time i changed something, i would have fewer problems. is that what people usually do? i keep thinking i have to avoid root because of security.

here is a bunch of information from the messages file. i don't know what is useful, what is repetition, and what is to be expected. there are clearly problems with my wifi driver, which i gave up trying to install since i have a regular cabled connection in-reach. i guess my problems will continue until i resolve that driver? i don't know if totally disabling it is a good idea because i DO want to get it working at some time..


Oct 11 01:14:19 localhost NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled...
Oct 11 01:14:19 localhost dhclient: bound to 207.5.xxx.xx -- renewal in 3372 seconds.
Oct 11 01:14:19 localhost NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) started...
Oct 11 01:14:19 localhost dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name
Oct 11 01:14:19 localhost dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
Oct 11 01:14:19 localhost dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
Oct 11 01:14:19 localhost NetworkManager: <info> Retrieved the following IP4 configuration from the DHCP daemon:
Oct 11 01:14:19 localhost NetworkManager: <info> address 207.5.xxx.xxx
Oct 11 01:14:19 localhost NetworkManager: <info> netmask 255.255.255.0
Oct 11 01:14:19 localhost NetworkManager: <info> broadcast 207.5.xxx.xxx
Oct 11 01:14:19 localhost NetworkManager: <info> gateway 207.5.xxx.x
Oct 11 01:14:19 localhost NetworkManager: <info> nameserver 207.5.xxx.x
Oct 11 01:14:19 localhost NetworkManager: <info> nameserver 207.5.xxx.x
Oct 11 01:14:19 localhost NetworkManager: <info> domain name 'xxxxxx.net'
Oct 11 01:14:19 localhost NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
Oct 11 01:14:19 localhost NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP Configure Get) complete.
Oct 11 01:14:19 localhost NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
Oct 11 01:14:19 localhost avahi-daemon[2578]: Withdrawing address record for ### on eth0.
Oct 11 01:14:19 localhost avahi-daemon[2578]: Leaving mDNS multicast group on interface eth0.IPv6 with address ###.
Oct 11 01:14:19 localhost avahi-daemon[2578]: Interface eth0.IPv6 no longer relevant for mDNS.
Oct 11 01:14:19 localhost avahi-daemon[2578]: Joining mDNS multicast group on interface eth0.IPv4 with address 207.5.xxx.xx.
Oct 11 01:14:19 localhost avahi-daemon[2578]: New relevant interface eth0.IPv4 for mDNS.
Oct 11 01:14:19 localhost avahi-daemon[2578]: Registering new address record for 207.5.xxx.xx on eth0.IPv4.
Oct 11 01:14:20 localhost NetworkManager: <info> Activation (eth0) successful, device activated.
Oct 11 01:14:20 localhost NetworkManager: <info> Activation (eth0) Finish handler scheduled.
Oct 11 01:14:20 localhost NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Oct 11 01:14:21 localhost avahi-daemon[2578]: Joining mDNS multicast group on interface eth0.IPv6 with address ###.
Oct 11 01:14:21 localhost avahi-daemon[2578]: New relevant interface eth0.IPv6 for mDNS.
Oct 11 01:14:21 localhost avahi-daemon[2578]: Registering new address record for ### on eth0.*.
Oct 11 01:14:21 localhost dnsmasq[2565]: reading /etc/resolv.conf
Oct 11 01:14:21 localhost dnsmasq[2565]: using nameserver 207.5.xxx.x#53
Oct 11 01:14:21 localhost dnsmasq[2565]: using nameserver 207.5.xxx.x#53
Oct 11 01:14:33 localhost kernel: bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.
Oct 11 01:14:33 localhost kernel: bcm43xx: core_up for active 802.11 core failed (-2)
Oct 11 01:14:33 localhost firmware_helper[3437]: Loading of /lib/firmware/bcm43xx_microcode5.fw for (unknown) driver failed: No such file or directory
Oct 11 01:14:36 localhost NetworkManager: <WARN> nm_device_802_11_wireless_scan(): could not trigger wireless scan on device eth1: No such device
Oct 11 01:14:56 localhost kernel: bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.
Oct 11 01:14:56 localhost kernel: bcm43xx: core_up for active 802.11 core failed (-2)
Oct 11 01:14:56 localhost firmware_helper[3446]: Loading of /lib/firmware/bcm43xx_microcode5.fw for (unknown) driver failed: No such file or directory
Oct 11 01:14:59 localhost NetworkManager: <WARN> nm_device_802_11_wireless_scan(): could not trigger wireless scan on device eth1: No such device
Oct 11 01:15:19 localhost kernel: bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.
Oct 11 01:15:19 localhost kernel: bcm43xx: core_up for active 802.11 core failed (-2)
Oct 11 01:15:19 localhost firmware_helper[3450]: Loading of /lib/firmware/bcm43xx_microcode5.fw for (unknown) driver failed: No such file or directory
Oct 11 01:15:23 localhost NetworkManager: <WARN> nm_device_802_11_wireless_scan(): could not trigger wireless scan on device eth1: No such device
Oct 11 01:17:23 localhost kernel: bcm43xx: Error: Microcode "bcm43xx_microcode5.fw" not available or load failed.
Oct 11 01:17:23 localhost kernel: bcm43xx: core_up for active 802.11 core failed (-2)
Oct 11 01:17:23 localhost firmware_helper[3457]: Loading of /lib/firmware/bcm43xx_microcode5.fw for (unknown) driver failed: No such file or directory
Oct 11 01:17:26 localhost NetworkManager: <WARN> nm_device_802_11_wireless_scan(): could not trigger wireless scan on device eth1: No such device

apost
11th October 2007, 06:36 AM
in regard to my external, there are a bunch of messages like this:


Oct 9 23:19:44 localhost kernel: FAT: Filesystem panic (dev sdb1)
Oct 9 23:19:44 localhost kernel: clusters badly computed (15679 != 15647)
Oct 9 23:19:53 localhost kernel: FAT: Filesystem panic (dev sdb1)
Oct 9 23:19:53 localhost kernel: clusters badly computed (15680 != 15648)
Oct 9 23:19:53 localhost kernel: FAT: Filesystem panic (dev sdb1)
Oct 9 23:19:53 localhost kernel: clusters badly computed (15681 != 15649)
Oct 9 23:19:53 localhost kernel: FAT: Filesystem panic (dev sdb1)
Oct 9 23:19:53 localhost kernel: clusters badly computed (15682 != 15650)

are these like windows' "corrupted data" messages? i could bring it to work and chkdsk / defrag. it's a pretty new WD mybook 500gb and hasn't been too sassy thus far

apost
11th October 2007, 06:40 AM
During bootup there are a lot of one-line messages as services are started. Exactly which message appears with the hang(with enet connected). Does it really hang or is just extremely slow. Misconfigured systems often stall for many minutes at the ntp time service or the sendmail service.


during bootup i get failure messages while it tries to connect on eth0 (wireless/broadcom) and eth1 (nic/marvell). it makes it past them and usually brings me to the login GUI.

the freeze on avi might be totally due to the file panic on the external, since that's where all my media is stored. i am going to copy something to my laptop hd and see if it plays fine without freezing up the whole situation.