Booted successfully from USB flash drive created by the livecd-iso-to-disk script, but the console log contains some peculiarities. The entire log is as: http://ryniker.ods.org/errors/vista_snap3_console First, a kernal fault: ------------[ cut here ]------------ WARNING: at kernel/trace/ftrace.c:1003 ftrace_bug+0x198/0x27e() (Not tainted) Hardware name: GT5426E Modules linked in: usb_storage(+) Pid: 84, comm: modprobe Not tainted 2.6.31-23.fc12.x86_64 #1 Call Trace: [<ffffffff81064244>] warn_slowpath_common+0x95/0xc3 [<ffffffffa0003b68>] ? usb_usual_ignore_device+0x8/0x90 [usb_storage] [<ffffffff81064299>] warn_slowpath_null+0x27/0x3d [<ffffffff810d4a0e>] ftrace_bug+0x198/0x27e [<ffffffffa0003b68>] ? usb_usual_ignore_device+0x8/0x90 [usb_storage] [<ffffffff810d5c66>] ftrace_convert_nops+0x201/0x2b9 [<ffffffffa0003b68>] ? usb_usual_ignore_device+0x8/0x90 [usb_storage] [<ffffffff810d5d6a>] ftrace_module_notify+0x4c/0x7f [<ffffffff815099c5>] notifier_call_chain+0x72/0xba [<ffffffff81086db1>] ? __blocking_notifier_call_chain+0x4c/0x8e usb 1-7: new high speed USB device using ehci_hcd and address 3 [<ffffffff81086dc8>] __blocking_notifier_call_chain+0x63/0x8e [<ffffffff81086e1a>] blocking_notifier_call_chain+0x27/0x3d [<ffffffff810a466a>] sys_init_module+0xb7/0x249 [<ffffffff81011f42>] system_call_fastpath+0x16/0x1b ---[ end trace 3cbbc5618e6ce794 ]--- ftrace faulted on writing [<ffffffffa0003b68>] usb_usual_ignore_device+0x8/0x90 [usb_storage] Second, some pieces are missing, or perhaps not in the right place: squashfs: version 4.0 (2009/01/31) Phillip Lougher /sbin/dmsquash-live-root: 121: umount: not found /sbin/dmsquash-live-root: 166: umount: not found /sbin/dmsquash-live-root: 166: umount: not found /sbin/dmsquash-live-root: 166: grep: not found /sbin/dmsquash-live-root: 166: umount: not found Third, status 1 usually denotes an error, but I do not know about this case: init: readahead-collector.event main process (423) terminated with status 1 Fourth: WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/. This causes no problem, and one can spend all day (week, month...) running around fixing "deprecation warnings" and the like, when these will be fixed upstream in time. The problem here is what creates this empty (length=0) file, something not "upstream" but in Fedora's build process, I guess. That is something that might be fixed, especially as this message occurs five times. Bottom line, however, is the F12-Snap3-x86_64-Live system worked well for me. -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
