Hi all
I seem to be having Issues getting my New Xmas gift to pair properly. I am running FC6 on a pentium4 box. here is the packages I have installed on: bluez-utils-cups-3.7-2 bluez-libs-devel-3.7-1 bluez-hcidump-1.32-1 bluez-bluefw-1.0-6 bluez-utils-3.7-2 bluez-libs-3.7-1 pybluez-0.9.1-3.fc6 bluez-gnome-0.6-1.fc6
openpbx-bluetooth-1.2-3.rc2.svn2282.fc6 kdebluetooth-1.0-0.19.beta3 gnome-bluetooth-0.7.0-12.fc6 gnome-bluetooth-devel-0.7.0-12.fc6 gnome-bluetooth-libs-0.7.0-12.fc6 nautilus-sendto-bluetooth-0.7-5.fc6 Now I don't know if I am missing a package or if some may be outdated and need updating. Especially the kdebluetooth package. I have read pages for days on the web trying to to get a handle on what to do as this is the very first time I every worked with bluetooth
on starting bluetooth service the log reads Dec 30 09:49:50 Dads hcid[5878]: Bluetooth HCI daemon Dec 30 09:49:50 Dads hcid[5878]: Register path:/org/bluez fallback:1 Dec 30 09:49:50 Dads hcid[5878]: HCI dev 0 registered Dec 30 09:49:50 Dads hcid[5878]: Register path:/org/bluez/hci0 fallback:0 Dec 30 09:49:50 Dads hcid[5878]: HCI dev 0 already up Dec 30 09:49:50 Dads hcid[5878]: Device hci0 has been added Dec 30 09:49:50 Dads hcid[5878]: Starting security manager 0 Dec 30 09:49:50 Dads hcid[5878]: Device hci0 has been activated Dec 30 09:49:50 Dads hcid[5878]: Default passkey agent (:1.8, /org/kde/kbluetooth_1234) registered Dec 30 09:49:51 Dads sdpd[5884]: Bluetooth SDP daemon
using hciconfig -a here is the output hci0: Type: USB BD Address: 00:02:76:0C:D6:03 ACL MTU: 1017:8 SCO MTU: 64:0 UP RUNNING PSCAN ISCAN RX bytes:601 acl:0 sco:0 events:43 errors:0 TX bytes:700 acl:0 sco:0 commands:43 errors:0 Features: 0xff 0xff 0x8d 0xfe 0x9b 0xf9 0x00 0x80 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'usbHeadset' Class: 0x120104 Service Classes: Networking, Object Transfer Device Class: Computer, Desktop workstation HCI Ver: 2.0 (0x3) HCI Rev: 0x4116 LMP Ver: 2.0 (0x3) LMP Subver: 0x430e Manufacturer: Broadcom Corporation (15) Now using the hcitool I scan, inq, and cc with these results [root@Dads ~]# hcitool scan Scanning ... 00:E0:98:49:2A:92 MATTHEW 00:1C:EF:0A:F3:01 NS-BTHDST [root@Dads ~]# hcitool inq 00:1C:EF:0A:F3:01 Inquiring ... 00:E0:98:49:2A:92 clock offset: 0x2fe5 class: 0x300104 00:1C:EF:0A:F3:01 clock offset: 0x0efe class: 0x240404 # hcitool info 00:1C:EF:0A:F3:01 Requesting information ... BD Address: 00:1C:EF:0A:F3:01 LMP Version: 2.0 (0x3) LMP Subversion: 0xbf1 Manufacturer: Cambridge Silicon Radio (10) Features: 0xff 0xff 0x8f 0x78 0x18 0x18 0x00 0x80 <3-slot packets> <5-slot packets> <encryption> <slot offset> <timing accuracy> <role switch> <hold mode> <sniff mode> <park state> <RSSI> <channel quality> <SCO link> <HV2 packets> <HV3 packets> <u-law log> <A-law log> <CVSD> <paging scheme> <power control> <transparent SCO> <broadcast encrypt> <enhanced iscan> <interlaced iscan> <interlaced pscan> <inquiry with RSSI> <AFH cap. slave> <AFH class. slave> <AFH cap. master> <AFH class. master> <extended features> # hcitool cc 00:1C:EF:0A:F3:01 # hcitool lq 00:1C:EF:0A:F3:01 Not connected. then I try this
# rfcomm -i hci0 connect 0 00:1C:EF:0A:F3:01 Can't connect RFCOMM socket: Connection refused
log entries after the rfcomm command are Dec 30 09:58:07 Dads hcid[5878]: link_key_request (sba=00:02:76:0C:D6:03, dba=00:1C:EF:0A:F3:01) Dec 30 09:58:07 Dads hcid[5878]: pin_code_request (sba=00:02:76:0C:D6:03, dba=00:1C:EF:0A:F3:01) Dec 30 09:58:07 Dads hcid[5878]: Passkey agent replied with an error: org.freedesktop.DBus.Error.UnknownMethod, Method "Request" with signature "ss" on interface "org.bluez.PasskeyAgent" doesn't exist
Config files hcid.conf # # HCI daemon configuration file. #
# HCId options options { # Automatically initialize new devices autoinit yes;
# Security Manager mode # none - Security manager disabled # auto - Use local PIN for incoming connections # user - Always ask user for a PIN # security auto;
# Pairing mode # none - Pairing disabled # multi - Allow pairing with already paired devices # once - Pair once and deny successive attempts pairing multi;
# Default PIN code for incoming connections passkey "0000"; }
# Default settings for HCI devices device { # Local device name # %d - device id # %h - host name name "%h-%d";
# Local device class class 0x120104;
# Default packet type #pkt_type DH1,DM1,HV1;
# Inquiry and Page scan iscan enable; pscan enable;
# Default link mode # none - no specific policy # accept - always accept incoming connections # master - become master on incoming connections, # deny role switch on outgoing connections lm accept;
# Default link policy # none - no specific policy # rswitch - allow role switch # hold - allow hold mode # sniff - allow sniff mode # park - allow park mode lp rswitch,hold,sniff,park; }
rfcomm.conf # # RFCOMM configuration file. #
rfcomm0 { # # Automatically bind the device at startup bind no; # # # Bluetooth address of the device device 00:1C:EF:0A:F3:01; # # # RFCOMM channel for the connection channel 1; # # # Description of the connection # comment "Example Bluetooth device"; }
Please help me shed some light on this. Through the whole command process I am never asked to input the pin that the headset wants which I believe is a bug. Also with kdebluetooth I am unable to Configure services or add devices. when I go to setup my device I get a crash. the backtrace info is as follows
(no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208932656 (LWP 6026)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [KCrash handler] #6 0x0670d7ff in QString::latin1 () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #7 0x0670ef42 in QString::ascii () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #8 0x0011e316 in KBluetooth::DBusSignal::newMessage () from /usr/lib/libkbluetooth.so.0 #9 0x0011e5a0 in KBluetooth::DBusSignal::sendString () from /usr/lib/libkbluetooth.so.0 #10 0x0011e5fc in KBluetooth::DBusSignal::sendString () from /usr/lib/libkbluetooth.so.0 #11 0x00120e9b in KBluetooth::InputDevice::connect () from /usr/lib/libkbluetooth.so.0 #12 0x08051f0d in QWidget::setUpdatesEnabled () #13 0x08052106 in QWidget::setUpdatesEnabled () #14 0x080533f4 in QWidget::setUpdatesEnabled () #15 0x063f116a in QObject::activate_signal () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #16 0x063f1b5d in QObject::activate_signal () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #17 0x0678695c in QButton::clicked () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #18 0x06495afd in QButton::mouseReleaseEvent () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #19 0x0642d7f5 in QWidget::event () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #20 0x06387cab in QApplication::internalNotify () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #21 0x06389307 in QApplication::notify () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #22 0x05cf2921 in KApplication::notify () from /usr/lib/libkdecore.so.4 #23 0x0631efa6 in QETWidget::translateMouseEvent () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #24 0x0631daa6 in QApplication::x11ProcessEvent () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #25 0x0632f90b in QEventLoop::processEvents () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #26 0x063a1250 in QEventLoop::enterLoop () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #27 0x063a1116 in QEventLoop::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #28 0x063877bf in QApplication::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 #29 0x08050d26 in QWidget::setUpdatesEnabled () #30 0x009e6dec in __libc_start_main () from /lib/libc.so.6 #31 0x0804d201 in QWidget::setUpdatesEnabled ()
Thanks for any help with this matter Don
On Sun December 30 2007 18:10:53 Donald Reader wrote:
Also with kdebluetooth I am unable to Configure services or add devices. when I go to setup my device I get a crash. the backtrace info is as follows
On the kde side of things you need to update kdebluetooth to a later version were this is fixed.
...dex
On Sun, 2007-12-30 at 23:47 +0000, dexter wrote:
On Sun December 30 2007 18:10:53 Donald Reader wrote:
Also with kdebluetooth I am unable to Configure services or add devices. when I go to setup my device I get a crash. the backtrace info is as follows
On the kde side of things you need to update kdebluetooth to a later version were this is fixed.
...dex
Thank you again for the help and I am looking for a updated package
Don
On Sun, 2007-12-30 at 21:53 -0800, Donald Reader wrote:
On Sun, 2007-12-30 at 23:47 +0000, dexter wrote:
On Sun December 30 2007 18:10:53 Donald Reader wrote:
Also with kdebluetooth I am unable to Configure services or add devices. when I go to setup my device I get a crash. the backtrace info is as follows
On the kde side of things you need to update kdebluetooth to a later version were this is fixed.
...dex
Thank you again for the help and I am looking for a updated package
Don
Be aware that the latest version of kdebluetooth is beta8. If you still encounter crashes, please post a bug report in http://bugzilla.redhat.com
- Gilboa
Man I am ready to give up on this project. I have looked for an updated package that will work on my system with no results what so ever. Even tried the packages for the fc8 and fc9 releases LOL even though I should not have. the only one that comes close to working is kdebluetooth.i386 0:1.0-0.16.20060908svn.fc6. The only issue with it is I still can not get the darn pin input box to popup like it should. It does read the headset. Also need to get the headset and hands free services activated some how as that might be the issue. Again I don't my head from a hole in the ground on this one.
SomeOne PLEASE help
Don
On Dec 31, 2007 9:02 PM, Donald Reader fc-list@reader.ws wrote:
Man I am ready to give up on this project. I have looked for an updated package that will work on my system with no results what so ever. Even tried the packages for the fc8 and fc9 releases LOL even though I should not have. the only one that comes close to working is kdebluetooth.i386 0:1.0-0.16.20060908svn.fc6. The only issue with it is I still can not get the darn pin input box to popup like it should. It does read the headset. Also need to get the headset and hands free services activated some how as that might be the issue. Again I don't my head from a hole in the ground on this one.
SomeOne PLEASE help
Don
Don,
A. FC6 has been EOL'ed and is no longer supported. You should consider upgrading your FC6 machine to F7 or F8. B. You're using an old (and unsupported) version of kdebluetooth. You cannot install newer versions of kdebluetooth (taken from F7/8) on FC6 as they require newer versions of the bluetooth tool-chain that are only included in F7 (or above).
... In short, if you want to use kdebluetooth, you'll have to upgrade to a -supported- version of Fedora.
- Gilboa
On Tue, 2008-01-01 at 00:28 +0200, Gilboa Davara wrote:
On Dec 31, 2007 9:02 PM, Donald Reader fc-list@reader.ws wrote:
Man I am ready to give up on this project. I have looked for an updated package that will work on my system with no results what so ever. Even tried the packages for the fc8 and fc9 releases LOL even though I should not have. the only one that comes close to working is kdebluetooth.i386 0:1.0-0.16.20060908svn.fc6. The only issue with it is I still can not get the darn pin input box to popup like it should. It does read the headset. Also need to get the headset and hands free services activated some how as that might be the issue. Again I don't my head from a hole in the ground on this one.
SomeOne PLEASE help
Don
Don,
A. FC6 has been EOL'ed and is no longer supported. You should consider upgrading your FC6 machine to F7 or F8. B. You're using an old (and unsupported) version of kdebluetooth. You cannot install newer versions of kdebluetooth (taken from F7/8) on FC6 as they require newer versions of the bluetooth tool-chain that are only included in F7 (or above).
... In short, if you want to use kdebluetooth, you'll have to upgrade to a -supported- version of Fedora.
- Gilboa
Thanks and it is easier said than done as far a updating the whole operating system. I don't have but the one computer and I can't be offline for that long of a time. I also am having major issues with my cd burner so burning new cds is out of the question and most of my spare blanks went into getting fc6 burned. I knew I was going to get upgrade or get lost. I really wish there was an easy way to upgrade without wasting a few dozen disc's again. I read somewhere it can be done so now need to find out how.
I have run fedora for years and could usually find the answers to issues on my own. I finally get to the point of fustration that I decided to join this list in hopes of getting some answers. You would think that it being an older version someone would have an answer or at least a few links. This has sure taught me a lesson about trying to get help anywhere. As usual left on your own no matter what. and to think I have talked ppl into getting and running fedora on their computers and they usually come to me for answers and I can usually find them if I don't already know it. The one time I seemed to get stumped and I am told upgrade. Sounds to me like fc8 is a headache and I don't need my computer down or not able to connect to my servers online
Thanks Don
i have not experienced any headaches with fedora 8.At least nothing major, a couple of minor issues overall but nothing that shut me down, just minor annoyances really. Perhaps my experience is unique? A dozen disc's? Try one disc. Yeah one disc is all i needed to burn. --- Donald Reader fc-list@reader.ws wrote:
On Tue, 2008-01-01 at 00:28 +0200, Gilboa Davara wrote:
On Dec 31, 2007 9:02 PM, Donald Reader fc-list@reader.ws wrote:
Man I am ready to give up on this project. I have looked for an updated package that will work on my system with no results what so ever. Even tried the packages for the fc8 and fc9 releases LOL even though I should not have. the only one that comes close to working is kdebluetooth.i386 0:1.0-0.16.20060908svn.fc6. The only issue with it is I still can not get the darn pin input box to popup like it should. It does read the headset. Also need to get the headset and hands free services activated some how as that might be the issue. Again I don't my head from a hole in the ground on this one.
SomeOne PLEASE help
Don
Don,
A. FC6 has been EOL'ed and is no longer supported. You should consider upgrading your FC6 machine to F7 or F8. B. You're using an old (and unsupported) version of kdebluetooth. You cannot install newer versions of kdebluetooth (taken from F7/8) on FC6 as they require newer versions of the bluetooth tool-chain that are only included in F7 (or above).
... In short, if you want to use kdebluetooth, you'll have to upgrade to a -supported- version of Fedora.
- Gilboa
Thanks and it is easier said than done as far a updating the whole operating system. I don't have but the one computer and I can't be offline for that long of a time. I also am having major issues with my cd burner so burning new cds is out of the question and most of my spare blanks went into getting fc6 burned. I knew I was going to get upgrade or get lost. I really wish there was an easy way to upgrade without wasting a few dozen disc's again. I read somewhere it can be done so now need to find out how.
I have run fedora for years and could usually find the answers to issues on my own. I finally get to the point of fustration that I decided to join this list in hopes of getting some answers. You would think that it being an older version someone would have an answer or at least a few links. This has sure taught me a lesson about trying to get help anywhere. As usual left on your own no matter what. and to think I have talked ppl into getting and running fedora on their computers and they usually come to me for answers and I can usually find them if I don't already know it. The one time I seemed to get stumped and I am told upgrade. Sounds to me like fc8 is a headache and I don't need my computer down or not able to connect to my servers online
Thanks Don
--
fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs
On Mon, 2007-12-31 at 15:43 -0800, Donald Reader wrote:
This has sure taught me a lesson about trying to get help anywhere. As usual left on your own no matter what.
Grizzle like that and you're unlikely to get much help. It's moderately easy to install without having to install from a collection of discs, if you have hard drive space to spare during the install.
After reading your message, I'm not that inclined to help beyond pointing out the basics of one simple method:
1. Download and burn the rescue disc ISO. 2. Download the install DVD ISO to a hard drive partition with plenty of space, and leave it there. If you use systems without multiple partitions, or without any large enough, then you can use a main partition, just remove the prior files before trying to install (*). 3. Boot the rescue disc, choose install from hard drive, pick the hard drive partition with the DVD ISO on it, make sure that partition isn't reformatted during the install process (it shouldn't let you, it should protest if you try, but I wouldn't depend on something like that).
* Presuming something like one partition for / and most sub-directories. One could boot the rescue disc, and switch over to another console and "rm -rfd" everything but the location where you've saved the ISO file. It's probably a good idea to rename /home/ if you want to keep it. Let the new install create a new home, then copy over older bits after the install. Not everything in /home works well between different releases. Then you'd switch back to the install console, and carry on using the installer.
There's a plethora of websites describing different methods of installing without doing it from multiple discs. Just find one that details a method you can follow.
On Tue, 2008-01-01 at 11:55 +1030, Tim wrote:
On Mon, 2007-12-31 at 15:43 -0800, Donald Reader wrote:
This has sure taught me a lesson about trying to get help anywhere. As usual left on your own no matter what.
Grizzle like that and you're unlikely to get much help. It's moderately easy to install without having to install from a collection of discs, if you have hard drive space to spare during the install.
After reading your message, I'm not that inclined to help beyond pointing out the basics of one simple method:
- Download and burn the rescue disc ISO.
- Download the install DVD ISO to a hard drive partition with plenty of
space, and leave it there. If you use systems without multiple partitions, or without any large enough, then you can use a main partition, just remove the prior files before trying to install (*). 3. Boot the rescue disc, choose install from hard drive, pick the hard drive partition with the DVD ISO on it, make sure that partition isn't reformatted during the install process (it shouldn't let you, it should protest if you try, but I wouldn't depend on something like that).
- Presuming something like one partition for / and most sub-directories.
One could boot the rescue disc, and switch over to another console and "rm -rfd" everything but the location where you've saved the ISO file. It's probably a good idea to rename /home/ if you want to keep it. Let the new install create a new home, then copy over older bits after the install. Not everything in /home works well between different releases. Then you'd switch back to the install console, and carry on using the installer.
There's a plethora of websites describing different methods of installing without doing it from multiple discs. Just find one that details a method you can follow.
Thank You everyone
First I must apologize for the post as frustration got the best of me. I have been trying to read up on installing without physically burning the media and hopefully will be able to do that before long as for now I have a client that is going to be doing a server move and can't afford for anything to go wrong with a new install at this time.
Some good news is I did get a connection finally with the headset now all I have to do is figure out how to get the audio services up and running so I can use them LOL.
To explain a little this is the very first time I have ever posted to a list for any help as I have always been gun shy of the fact that I have read lots of lists and forums where questions get answered with Read The Freaking Manual or upgrade system to the newest. It just seemed that is the way it was headed in my eyes. Again I apologize to the whole list and thank everyone for the responses
Don
On Mon, 2007-12-31 at 18:56 -0800, Donald Reader wrote:
On Tue, 2008-01-01 at 11:55 +1030, Tim wrote:
On Mon, 2007-12-31 at 15:43 -0800, Donald Reader wrote:
This has sure taught me a lesson about trying to get help anywhere. As usual left on your own no matter what.
Grizzle like that and you're unlikely to get much help. It's moderately easy to install without having to install from a collection of discs, if you have hard drive space to spare during the install.
After reading your message, I'm not that inclined to help beyond pointing out the basics of one simple method:
- Download and burn the rescue disc ISO.
- Download the install DVD ISO to a hard drive partition with plenty of
space, and leave it there. If you use systems without multiple partitions, or without any large enough, then you can use a main partition, just remove the prior files before trying to install (*). 3. Boot the rescue disc, choose install from hard drive, pick the hard drive partition with the DVD ISO on it, make sure that partition isn't reformatted during the install process (it shouldn't let you, it should protest if you try, but I wouldn't depend on something like that).
- Presuming something like one partition for / and most sub-directories.
One could boot the rescue disc, and switch over to another console and "rm -rfd" everything but the location where you've saved the ISO file. It's probably a good idea to rename /home/ if you want to keep it. Let the new install create a new home, then copy over older bits after the install. Not everything in /home works well between different releases. Then you'd switch back to the install console, and carry on using the installer.
There's a plethora of websites describing different methods of installing without doing it from multiple discs. Just find one that details a method you can follow.
Thank You everyone
First I must apologize for the post as frustration got the best of me. I have been trying to read up on installing without physically burning the media and hopefully will be able to do that before long as for now I have a client that is going to be doing a server move and can't afford for anything to go wrong with a new install at this time.
Some good news is I did get a connection finally with the headset now all I have to do is figure out how to get the audio services up and running so I can use them LOL.
To explain a little this is the very first time I have ever posted to a list for any help as I have always been gun shy of the fact that I have read lots of lists and forums where questions get answered with Read The Freaking Manual or upgrade system to the newest. It just seemed that is the way it was headed in my eyes. Again I apologize to the whole list and thank everyone for the responses
---- I for one would never use the work 'Freaking' when the natural choice seems to convey a much clearer sentiment.
You should note though, that the list frowns on HTML mail...yes, you are sending HTML mail to this list.
see... http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
The history of people suggesting that you RTFM has real roots...
http://www.catb.org/~esr/faqs/smart-questions.html
You'll find it easier to get what you need from mail lists by reading the above links
Craig
On Mon, 2007-12-31 at 18:56 -0800, Donald Reader wrote:
Thank You everyone
First I must apologize for the post as frustration got the best of me. I have been trying to read up on installing without physically burning the media and hopefully will be able to do that before long as for now I have a client that is going to be doing a server move and can't afford for anything to go wrong with a new install at this time.
Some good news is I did get a connection finally with the headset now all I have to do is figure out how to get the audio services up and running so I can use them LOL.
To explain a little this is the very first time I have ever posted to a list for any help as I have always been gun shy of the fact that I have read lots of lists and forums where questions get answered with Read The Freaking Manual or upgrade system to the newest. It just seemed that is the way it was headed in my eyes. Again I apologize to the whole list and thank everyone for the responses
Don
In theory, you can (re)install/upgrade fedora without burning a single CD.
0. Backup. A faulty upgrade may kill your data. I'm serious. (And F8's upgrade is known to be, err, sensitive...). Keep in mind that in general, a fresh install (no matter what OS you are using) tends to work better (cleaner, faster, etc) then an upgrade.
1. Download the vmlinuz and initrd.img files from any fedora mirror (E.g. [1]) and copy them to your /boot directory.
2. Open (as root) /etc/grub.conf, and add the following entry using one of your existing grub entries as template:
title Fedora 8 upgrade root (hd0,0) kernel /vmlinuz askmethod initrd /initrd.img
3. Save the URL from which you downloaded the files. (E.g. [2]) Write it on a piece of paper.
4. Configure the network device.
5. Select HTTP installation, type the download URL.
6. Upgrade/install.
- Gilboa
(x86_64) [1] http://mirrors.kernel.org/fedora/releases/8/Fedora/x86_64/os/isolinux/ [2] http://mirrors.kernel.org/fedora/releases/8/Fedora/x86_64/os/
Gilboa Davara wrote:
- Backup. A faulty upgrade may kill your data. I'm serious. (And F8's
upgrade is known to be, err, sensitive...). Keep in mind that in general, a fresh install (no matter what OS you are using) tends to work better (cleaner, faster, etc) then an upgrade.
I completely disagree. Upgrade and install both work exactly the same. Have you actually tried both, or do you just _know_?
I don't know what you mean by "your data", but /home should be on a separate partition, not affected by upgrade or install.
As I recall, the OP was worried that the new system might not work. In that case he would be better advised to do an upgrade, IMHO. He still has the chance to do a clean install if there is a problem. In other words, he gets two bites at the cherry.
A better solution, if he has the space, is to do a clean install on another partition, so that old and new systems are both available.
Personally, I would download and burn the KDE Live CD, which will give some idea if Fedora 8 will run on his system.
On Tue, 2008-01-01 at 13:40 +0100, Timothy Murphy wrote:
Gilboa Davara wrote:
- Backup. A faulty upgrade may kill your data. I'm serious. (And F8's
upgrade is known to be, err, sensitive...). Keep in mind that in general, a fresh install (no matter what OS you are using) tends to work better (cleaner, faster, etc) then an upgrade.
I completely disagree. Upgrade and install both work exactly the same. Have you actually tried both, or do you just _know_?
Know. (dep-solve bug)
... Beyond that, I once (RH8?) suffered from a kernel OOPS during an upgrade - left me with a dead OS. Since then, I never attempted to do an upgrade on a live system. (Though I continue to test the upgrade procedure on VM's for the sake of my co-workers)
Other then that, doing a fresh install + manual migration (configuration files, etc) is actually faster then the upgrade option. (And gives you a cleaner OS - especially if you are using 3'rd party repositories.)
P.S. I once lost a Debian installation due to a simple upgrade. (3->4) This is not a Fedora/RH-only problem.
I don't know what you mean by "your data", but /home should be on a separate partition, not affected by upgrade or install.
Doing -anything- on live OS (be that upgrade, or risky maintenance) without a recent backup is a job-altering-decision.
Lose all your data once (due to a failed upgrade/installation/kernel crash) and you'll never make this mistake again.
As I recall, the OP was worried that the new system might not work. In that case he would be better advised to do an upgrade, IMHO. He still has the chance to do a clean install if there is a problem. In other words, he gets two bites at the cherry.
A better solution, if he has the space, is to do a clean install on another partition, so that old and new systems are both available.
As I said, it's far easier (... and faster!) to do a fresh install on a spare partition and migrate all the configuration files to the new installation.
It usually takes me ~90 minutes (including the actual installation over NFS) to switch from F-N to F-N+1.
Personally, I would download and burn the KDE Live CD, which will give some idea if Fedora 8 will run on his system.
Doubt it. The basic LiveCD is radically different from a fully updated (and well configured) F8 installation.
- Gilboa
Gilboa Davara wrote:
On Tue, 2008-01-01 at 13:40 +0100, Timothy Murphy wrote:
Gilboa Davara wrote:
- Backup. A faulty upgrade may kill your data. I'm serious. (And F8's
upgrade is known to be, err, sensitive...). Keep in mind that in general, a fresh install (no matter what OS you are using) tends to work better (cleaner, faster, etc) then an upgrade.
I completely disagree. Upgrade and install both work exactly the same. Have you actually tried both, or do you just _know_?
Know. (dep-solve bug)
<snip>
As I said, it's far easier (... and faster!) to do a fresh install on a spare partition and migrate all the configuration files to the new installation.
I have to agree with Gilboa here. An upgrade installs the new packages and then removes the old packages, while an install wipes the selected filesystems and simply installs into the clean space.
This solves several nagging problems that can effect an upgraded system.
As for backup, the minimal set of stuff that really requires a backup are: /etc #Configuration data /var #spool, www, ftp and such /home #if not on a separate file system that can be preserved /usr/local #again, if not on a separate filesystem
The remaining filesystems that should usually be on mounted sections (root, usr, srv, usr, boot) can be wiped/reformatted.
I will note that the "default" filesystem layout selected by the F8 installer (anaconda version) is *not* quite as robust as it could be. It seems too much like another commercial OS in that it only makes two filesystems (boot and root) and crams everything together in root. This requires the user to make full backups at upgrade time.
At a minimum I recommend three partitions: boot, root and home At "best" I use: root, boot, usr, usr/local, home, var, tmp, srv
There are good reasons for such separation, and there are some standard recommendations for sizes, but that is another discussion.
On Tue, 2008-01-01 at 11:02 -0500, G.Wolfe Woodbury wrote:
I will note that the "default" filesystem layout selected by the F8 installer (anaconda version) is *not* quite as robust as it could be.
Nods...
It seems too much like another commercial OS in that it only makes two filesystems (boot and root) and crams everything together in root. This requires the user to make full backups at upgrade time.
Not really. You can use a backup tool that lets you pick directories to backup, and just back up the required parts of the tree, whether they're separate partions, or not.
<snip>
As I said, it's far easier (... and faster!) to do a fresh install on a spare partition and migrate all the configuration files to the new installation.
I have to agree with Gilboa here. An upgrade installs the new packages and then removes the old packages, while an install wipes the selected filesystems and simply installs into the clean space.
This solves several nagging problems that can effect an upgraded system.
As for backup, the minimal set of stuff that really requires a backup are: /etc #Configuration data /var #spool, www, ftp and such /home #if not on a separate file system that can be preserved /usr/local #again, if not on a separate filesystem
The remaining filesystems that should usually be on mounted sections (root, usr, srv, usr, boot) can be wiped/reformatted.
I will note that the "default" filesystem layout selected by the F8 installer (anaconda version) is *not* quite as robust as it could be. It seems too much like another commercial OS in that it only makes two filesystems (boot and root) and crams everything together in root. This requires the user to make full backups at upgrade time.
The above statement is not true. I have only on / filesystem and I back up /home /root /etc/ and anything else I want to backup using tar before each upgrade. This is especially useful when you want to restore your old home directory in the directory the installed created. Untarring with the -k option does not overwrite the files already existing in the directory so the new versions of the gnome configuration files (for example) are preserved.
At a minimum I recommend three partitions: boot, root and home At "best" I use: root, boot, usr, usr/local, home, var, tmp, srv
There are good reasons for such separation, and there are some standard recommendations for sizes, but that is another discussion.
-- Wolfe
-- ======================================================================= A wise person makes his own decisions, a weak one obeys public opinion. -- Chinese proverb ======================================================================= Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam@sbcglobal.net
Donald Reader wrote:
Man I am ready to give up on this project. I have looked for an updated package that will work on my system with no results what so ever. Even tried the packages for the fc8 and fc9 releases LOL even though I should not have. the only one that comes close to working is kdebluetooth.i386 0:1.0-0.16.20060908svn.fc6.
I think the advice you were given was mistaken. It was not necessary in FC-6 to have kdebluetooth in order to run bluetooth. IIRC, kdebluetooth was not available for FC-6, in any Fedora repository.
-
Aaron Konstam -
Craig White -
dexter -
Donald Reader -
G.Wolfe Woodbury -
Gilboa Davara -
Max -
Tim -
Timothy Murphy