Re: Wierd partition behaviour with BTRFS
On Mar 12, 2014, at 7:22 PM, Chris Murphy wrote: > I think you've stumbled into a bug. Since Btrfs directly supports multiple > devices, it's like LVM or raid in this respect, and for LVM and RAID, > anaconda might be eager to configure multiple device layouts this way. > > So I'm going to bet dollars to donuts this is a Btrfs raid0 volume. I just tried this with Rawhide, and it is rather easy to create a multiple device Btrfs volume and maybe not realize it. The resulting volume uses data profile single, metadata profile raid1. This can be confirmed with: btrfs fi df / Data profile single allocations in 1GB chunks to the block device (partition) with the most free space. When free space remaining among all devices is the same, it round robin allocates in 1GB increments. The metadata being raid1 means both SSD and HDD have a copy of the file system. The way data profile single works is it allocates in 1GB chunks to the block device (partition) that has the most free space, until both have the same free space remaining, and then it alternates between them in 1GB chunks. The metadata however is raid1, so the SSD and the hard drive each have a copy of the file system. So if yours is configured this way, it's probably not critical to change it. The metadata going to the SSD isn't much, and since the HDD has much more space probably all data chunks are allocated on it for the near/medium term. But conversion to single device Btrfs is straightforward, three btrfs commands will do it. And then some extras to reclaim the space on the SSD for /var or / or whatever. Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: How do I select which monitor kdm will display login on?
On 09/03/14 17:17, Robin Laing wrote: I have a dual monitor, well, one monitor and one projector that I have configured for presentations. System is using F20. Presently when I start the computer, kdm's login prompt is on the projector instead of the monitor. There are no settings in the system settings configuration to select the monitor. I was having similar issues with GDM, where it would set up the order of the monitors incorrectly, despite what was in the X configuration or the desktop settings. Interestingly enough, the order was correct when I logged in. Anyway, I switched to lightdm. It's not as pretty as kdm, if that even matters but it presents the login dialog on whatever monitor the mouse happens to be on. If you move the mouse to another display, the dialog follows. Seemed to me to be an elegant solution. -- Ian Chapman. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Wireless dropping Router
On 03/12/2014 09:14 PM, Jim wrote: FC18/KDE , I can no longer update F18 any more I have a Dell D600 Latitude that is dropping the router dd-wrt. Wireless networking is okay for about 20- 30 minutes before it drops If I try to reconnect Wlan0 and Connections there is no dd-wrt router shown in Connections to connect to. I have to restart the Laptop to get dd-wrt router to show up in Network Connections so I can reconnect. The wireless card on laptop uses the b43legacy driver The wireless card is a Broadcom BCM4306 Do you have another wireless card you can try? an external one? Your card may be failing. There is the issue that F18 is no longer supported as well but everything else being equal if it worked before then it should still work, unless, there is something wrong with the router or the card. You can rule out updates to F18 causing the issue. That's an upside. Did you have any issues getting it to work with F18 to start with? Have you updated the router recently? Have you tried reseating the wireless card? Just because its internal doesn't mean you can't try it. Assuming you know how to get to it. You should be able to find the manual on the Dell support page. If I had a nickel for every time re-seating a component worked...well you know. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Saving Fedora when installing Windows?
Allegedly, on or about 12 March 2014, Timothy Murphy sent: > I've always regarded the Windows bootloader as a black box, > my occasional journeys into the Windows Registry having proved > disastrous. Depending on the version of Windows, and what you want to do, it can be just a boot.ini file in the root directory. Or one can use a graphical tool in Windows to change boot parameters, and it'll fiddle with whatever's used, for you. A bit of internet searching should find you a method that you can handle. > But I don't see how both can be on offer - > do they use the MBRs of different drives? Or partitions... -- [tim@localhost ~]$ uname -rsvp Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64 All mail to my mailbox is automatically deleted, there is no point trying to privately email me, I will only read messages posted to the public lists. George Orwell's '1984' was supposed to be a warning against tyranny, not a set of instructions for supposedly democratic governments. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Wierd partition behaviour with BTRFS
On Mar 12, 2014, at 7:11 PM, Patrick O'Callaghan wrote: > (Sorry for the subject line but it's the best I could come up with) > > I recently installed F20 on a new system with a 120GB SSD and 1TB hard > drive. I'm using the SSD for /, /boot, /var and swap, and the hard drive > for /home. I decided to live on the edge and partition /home as BTRFS. > All this was done from Anaconda with no subsequent changes except adding > a few labels. > > This is what I find: > > $ lsblk --fs > NAME FSTYPE LABEL UUID >MOUNTPOINT > sda > > ├─sda1 ext4 boot > 6d5929d8-fd35-49e6-a8bf-aab5309dad77 /boot > ├─sda2 btrfs fedora_pxeclient-arch-0-undi-002001-d4-3d-7e-f4-1b-08 > 22fecad3-619d-4a9b-aace-35a2e4e04c49 /home > ├─sda3 ext4 root > 6a9a800c-309b-4b69-b269-884ad495e7b9 / > ├─sda4 > > ├─sda5 ext4 var > d5955869-af07-4d6e-b1b3-6ccb31208b41 /var > └─sda6 swap > 1431e6d2-531e-46cd-8633-1cf878c6b2a1 [SWAP] > sdb > > └─sdb1 btrfs fedora_pxeclient-arch-0-undi-002001-d4-3d-7e-f4-1b-08 > 22fecad3-619d-4a9b-aace-35a2e4e04c49 > > Note that /dev/sda2 and /dev/sdb1 have the same UUID and label. I think you've stumbled into a bug. Since Btrfs directly supports multiple devices, it's like LVM or raid in this respect, and for LVM and RAID, anaconda might be eager to configure multiple device layouts this way. So I'm going to bet dollars to donuts this is a Btrfs raid0 volume. What do you get for btrfs fi df /home #this is short for btrfs filesystem df /home > > $ df -h > FilesystemSize Used Avail Use% Mounted on > /dev/sda3 68G 8.5G 56G 14% / > devtmpfs 7.8G 0 7.8G 0% /dev > tmpfs 7.9G 5.6M 7.8G 1% /dev/shm > tmpfs 7.9G 1.1M 7.9G 1% /run > tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup > tmpfs 7.9G 72K 7.9G 1% /tmp > /dev/sda1 477M 113M 335M 26% /boot > /dev/sda5 27G 1.8G 24G 7% /var > /dev/sda2 932G 73G 858G 8% /home > > Note that /dev/sda2 is mounted and /dev/sdb1 is not. However /dev/sda2 > has around 1TB of space, so it's clearly the hard drive. Yeah the multiple device mounting behavior is different. You can mount either device and the entire volume is thus mounted, you don't have to be explicit as btrfs finds its other parts and uses them; it only complains when it can't find them. > What's going on, and should I be worried? Well, it's raid0 so yeah I'd make a backup of anything important. It is possible to do an online conversion to a single device layout, but depending on what you have in /home it might actually be easier to back it up, blow away the current btrfs partitions, and redo the mkfs on just sdb1, add the new UUID to your fstab, mount the new /home and restore from backup. But I leave that up to you. The conversion is straight forward and it should work, I've done it a bunch of times but you know… "yay btrfs with crossed fingers". > > Also, how can I change the label of the BTRFS partition? I used the > "btrfs filesystem label ..." command but although it registers the > change, the existing fedora_pxeclient label still shows up > in /dev/disk/by-label. What do you get for btrfs fi show And does the first line Label: match the new label or the old? Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Wireless dropping Router
On 03/12/2014 06:14 PM, Jim wrote: FC18/KDE , I can no longer update F18 any more You do know, don't you, that F18 has passed End Of Life and there will never be any more updates for it, even for security? -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Wireless dropping Router
FC18/KDE , I can no longer update F18 any more I have a Dell D600 Latitude that is dropping the router dd-wrt. Wireless networking is okay for about 20- 30 minutes before it drops If I try to reconnect Wlan0 and Connections there is no dd-wrt router shown in Connections to connect to. I have to restart the Laptop to get dd-wrt router to show up in Network Connections so I can reconnect. The wireless card on laptop uses the b43legacy driver The wireless card is a Broadcom BCM4306 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Wierd partition behaviour with BTRFS
(Sorry for the subject line but it's the best I could come up with) I recently installed F20 on a new system with a 120GB SSD and 1TB hard drive. I'm using the SSD for /, /boot, /var and swap, and the hard drive for /home. I decided to live on the edge and partition /home as BTRFS. All this was done from Anaconda with no subsequent changes except adding a few labels. This is what I find: $ lsblk --fs NAME FSTYPE LABEL UUID MOUNTPOINT sda ├─sda1 ext4 boot 6d5929d8-fd35-49e6-a8bf-aab5309dad77 /boot ├─sda2 btrfs fedora_pxeclient-arch-0-undi-002001-d4-3d-7e-f4-1b-08 22fecad3-619d-4a9b-aace-35a2e4e04c49 /home ├─sda3 ext4 root 6a9a800c-309b-4b69-b269-884ad495e7b9 / ├─sda4 ├─sda5 ext4 var d5955869-af07-4d6e-b1b3-6ccb31208b41 /var └─sda6 swap 1431e6d2-531e-46cd-8633-1cf878c6b2a1 [SWAP] sdb └─sdb1 btrfs fedora_pxeclient-arch-0-undi-002001-d4-3d-7e-f4-1b-08 22fecad3-619d-4a9b-aace-35a2e4e04c49 Note that /dev/sda2 and /dev/sdb1 have the same UUID and label. $ df -h FilesystemSize Used Avail Use% Mounted on /dev/sda3 68G 8.5G 56G 14% / devtmpfs 7.8G 0 7.8G 0% /dev tmpfs 7.9G 5.6M 7.8G 1% /dev/shm tmpfs 7.9G 1.1M 7.9G 1% /run tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup tmpfs 7.9G 72K 7.9G 1% /tmp /dev/sda1 477M 113M 335M 26% /boot /dev/sda5 27G 1.8G 24G 7% /var /dev/sda2 932G 73G 858G 8% /home Note that /dev/sda2 is mounted and /dev/sdb1 is not. However /dev/sda2 has around 1TB of space, so it's clearly the hard drive. What's going on, and should I be worried? Also, how can I change the label of the BTRFS partition? I used the "btrfs filesystem label ..." command but although it registers the change, the existing fedora_pxeclient label still shows up in /dev/disk/by-label. poc -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Making an Accessible Network Install?
Hi guys, I was wondering if it were possible to put Speakup on a CD of Fedora, give it software speech, and make an accessible network install disk? There used to be one, but sadly it is out of business now and has fallen much by the wayside. I knowthe Live CD has Orca if you get the Gnome version, but one of the places that accessibility is lacking in the install process is the network install disc. thoughts welcome. Hunter -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: btrfs subvolume as an iSCSI target?
On Mar 12, 2014, at 6:18 PM, Rick Stevens wrote: > On 03/12/2014 04:23 PM, Dan Mossor issued this missive: >> I've been combing the web for a couple days, and most hits I'm finding >> regarding using a btrfs subvolume as an iSCSI target are posts from the >> 2009/2010 timeframe stating that that functionality is broken. >> >> I'm working on a couple projects here, and one of those involves the >> research into iSCSI targets and initiators, and the testing thereof. I >> have an F20 system with a 1.3TB btrfs master subvolume (across three >> dissimilar devices), and want to create a subvolume within that to serve >> as an iSCSI target. >> >> The traditional methods, specifically those mentioned in the Fedora Wiki >> and the tgtadm man pages, place the emphasis on using devices (/dev/sdx) >> or files (dd if=/dev/zero of=/array/target1 bs=1k count=1). I realize >> that using the file is probably the easiest thing to do in this >> instance, but that's not the point of my project - I am intentionally >> trying to designate the btrfs subvolume as the target. >> >> The issue I believe that is going to stop me is that tgtadm expects a >> block device as the target, and btrfs does not provide that. Is there a >> workaround, other than using a file in the subvolume as the target? Is >> there work in progress to enable this feature, either in the >> scsi-target-utils package or within the btrfs framework? > > iSCSI stands for "internet SCSI", a way to share raw devices over normal > network mechanisms rather than having to have a storage farm (e.g. > fiberchannel switches or SAS concentrators and a ton of cables). As far > as I know, the functionality you want will never be available. iSCSI > is intended to share raw devices, not subdirectories (that's what things > like NFS and CIFS are for). It's a reasonable inquiry as ZFS does support iSCSI export of a zvol, but this is built into ZFS directly. https://btrfs.wiki.kernel.org/index.php/Project_ideas#block_devices_.27btrvols.27 No one has taken this yet though, so no work so far. Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: btrfs subvolume as an iSCSI target?
On Mar 12, 2014, at 5:23 PM, Dan Mossor wrote: > > The issue I believe that is going to stop me is that tgtadm expects a block > device as the target, and btrfs does not provide that. Is there a workaround, > other than using a file in the subvolume as the target? Is there work in > progress to enable this feature, either in the scsi-target-utils package or > within the btrfs framework? A btrfs subvolume is a separate file tree, but it's not a block device. It has no fixed size or number of sectors, which is the case for a block device. I don't think there's a plan to change this. https://btrfs.wiki.kernel.org/index.php/SysadminGuide#Subvolumes Using a file is unlikely to be a good work around because Btrfs is COW, so it writes new blocks even for overwriting files. For a large file with a lot of active re-writes, it causes a lot of fragmentation. This includes VM images. There's a lot of work still being done in the autodefrag code, but right now the emphasis is for smaller files like small databases and log files that are constantly being written to with random writes. The workaround is to set xattr +C on the file, either setting it on a containing folder which will cause any new file to inherit +C, or to set it on an empty file. This turns off datacow for the file, which as a consequence also turns off data checksumming. So I think you're better off using LVM LV to export the iSCSI target and format it Btrfs, if Linux is what's going to use the iSCSI target. Sparse usage can be done with LVM thin provisioning. Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: fedora 20 login screen
On 03/12/2014 05:17 PM, Ed Greshko wrote: or su - systemsettings If you're going to use su, and only expect to run one command as root: su -c systemsettings will do even better. HTH, HAND. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: btrfs subvolume as an iSCSI target?
On 03/12/2014 04:23 PM, Dan Mossor issued this missive: I've been combing the web for a couple days, and most hits I'm finding regarding using a btrfs subvolume as an iSCSI target are posts from the 2009/2010 timeframe stating that that functionality is broken. I'm working on a couple projects here, and one of those involves the research into iSCSI targets and initiators, and the testing thereof. I have an F20 system with a 1.3TB btrfs master subvolume (across three dissimilar devices), and want to create a subvolume within that to serve as an iSCSI target. The traditional methods, specifically those mentioned in the Fedora Wiki and the tgtadm man pages, place the emphasis on using devices (/dev/sdx) or files (dd if=/dev/zero of=/array/target1 bs=1k count=1). I realize that using the file is probably the easiest thing to do in this instance, but that's not the point of my project - I am intentionally trying to designate the btrfs subvolume as the target. The issue I believe that is going to stop me is that tgtadm expects a block device as the target, and btrfs does not provide that. Is there a workaround, other than using a file in the subvolume as the target? Is there work in progress to enable this feature, either in the scsi-target-utils package or within the btrfs framework? iSCSI stands for "internet SCSI", a way to share raw devices over normal network mechanisms rather than having to have a storage farm (e.g. fiberchannel switches or SAS concentrators and a ton of cables). As far as I know, the functionality you want will never be available. iSCSI is intended to share raw devices, not subdirectories (that's what things like NFS and CIFS are for). By creating a file (on any filesystem) and using that as the iSCSI target, you're using that file as a raw device and the iSCSI consumer can format it to whatever they want (or use the existing filesystem if it knows what it is). -- - Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com - - AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 - -- - Blessed are the peacekeepers...for they shall be shot at - - from both sides. --A.M. Greeley- -- -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: fedora 20 login screen
On 03/13/14 01:50, Dustin Kempter wrote: > im trying to config my laptop running fedora 20. in system settings I have > installed some themes for the login screen but none of them will show up. it > says they are installed on the "get new themes" window but they dont show up. > any advice Yes... Sounds like you are running KDE and the kdm display manager. It also sounds like you are running systemsettings as a regular user. In a terminal window you can run sudo systemsettings or su - systemsettings and it will run under root and the changes will be made. -- Getting tired of non-Fedora discussions and self-serving posts -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: fedora 20 login screen
On 03/12/2014 12:50 PM, Dustin Kempter wrote: im trying to config my laptop running fedora 20. in system settings I have installed some themes for the login screen but none of them will show up. it says they are installed on the "get new themes" window but they dont show up. any advice thanks It would help us greatly in helping you to know which desktop you're using - the default Gnome, the alternative KDE, or one of the spins such as MATE or LXDE. -- Dan Mossor Systems Engineer at Large Fedora QA Team Volunteer FAS: dmossor IRC: danofsatx San Antonio, Texas, USA -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
btrfs subvolume as an iSCSI target?
I've been combing the web for a couple days, and most hits I'm finding regarding using a btrfs subvolume as an iSCSI target are posts from the 2009/2010 timeframe stating that that functionality is broken. I'm working on a couple projects here, and one of those involves the research into iSCSI targets and initiators, and the testing thereof. I have an F20 system with a 1.3TB btrfs master subvolume (across three dissimilar devices), and want to create a subvolume within that to serve as an iSCSI target. The traditional methods, specifically those mentioned in the Fedora Wiki and the tgtadm man pages, place the emphasis on using devices (/dev/sdx) or files (dd if=/dev/zero of=/array/target1 bs=1k count=1). I realize that using the file is probably the easiest thing to do in this instance, but that's not the point of my project - I am intentionally trying to designate the btrfs subvolume as the target. The issue I believe that is going to stop me is that tgtadm expects a block device as the target, and btrfs does not provide that. Is there a workaround, other than using a file in the subvolume as the target? Is there work in progress to enable this feature, either in the scsi-target-utils package or within the btrfs framework? -- Dan Mossor Systems Engineer at Large Fedora QA Team Volunteer FAS: dmossor IRC: danofsatx San Antonio, Texas, USA -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora 18 not booting after lots of successful boot ups
On Mar 12, 2014, at 1:11 PM, Chris Murphy wrote: > Anyway I always do a 1/2 dozen reboots with it enabled, checking > systemd-analyze each time; and then disable it and reboot and check > systemd-analyze again. That is, I do this with each new major version of systemd. Because this readahead code is constantly being tweaked, so eventually it might benefit my use case. There are some tips here: http://freedesktop.org/wiki/Software/systemd/Optimizations/ Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora 18 not booting after lots of successful boot ups
For posterity: https://bugzilla.redhat.com/show_bug.cgi?id=696821 It's not exactly the OP's problem, but there appears to be a kernel bug that can cause systemd readahead problems. Anyway I always do a 1/2 dozen reboots with it enabled, checking systemd-analyze each time; and then disable it and reboot and check systemd-analyze again. At least in my configurations, there's no difference so I just leave it disabled. Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora 18 not booting after lots of successful boot ups
On Mar 12, 2014, at 4:36 AM, takCoder wrote: > systemd-readahead[416]: Failed to open pack file: Read-only system I'm not sure the problem is Bluetooth at all. Systemd has a way to optimize boot times with its own read ahead mechanism, and puts the hint for what to read ahead in (I'm guessing) this pack file. I don't know why the file system is read only at this point though, so that seems to be the real problem. I'd start out by booting single user mode (rescue.target in systemd vernacular). Do this by pressing e at the grub menu to edit the entry, find the linux line, and add to the end of it the word single. Use the mount command to see that all relevant file systems are in fact mounted rw and not ro. If / or /var is ro, then you are slightly better off booting from alternate media like a live desktop image, and running fsck on the problematic volume rather than running it on a mounted ro volume. But if you do run it on the ro volume, immediately reboot after repairs by using reboot -f. Also while you're at it, use df -h to see if for some reason a volume is full. If everything file system wise is OK, then you'll need to add some other boot parameters to try to track this down. Remove both the quiet rhgb options, and add systemd.log_level=debug systemd.log_target=console options. This will produce rather verbose messages on the console but should better pinpoint where the problem is. It is also possible to just disable the readahead. If you successfully boot single user with a rw mounted file system: systemctl disable systemd-readahead-collect.service systemd-readahead-drop.service systemd-readahead-replay.service It's unlikely that it makes much of a difference performance wise anyway. And it's probably not worth spending much time troubleshooting and filing bugs since Fedora 18 is EOL anyway. Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Saving Fedora when installing Windows?
On Mar 12, 2014, at 7:06 AM, Timothy Murphy wrote: > Chris Murphy wrote: > >>> I want to upgrade Windows XP on my laptop to Windows 7, >>> but I'd like to be sure that I can get back to Linux afterwards. >>> (I'm sure Windows installation will over-write the MBR.) > >> Which version of Fedora? > > I'm running Fedora-20/KDE. > >>> One thing I tried without success in the past >>> was to specify a USB stick when running grub2-install. > >> Sure, and then at the grub prompt you can use ls to find the designation >> for the drive and partition, then use configfile >> (hdx,msdosy)/grub2/grub.cfg which will produce the grub menu and let you >> boot. Then you can reinstall grub to the hard drive once booted. > > Last time I tried this I didn't get a grub prompt > when re-starting the machine with the USB stick in. > > Is that what you are suggesting? > As far as I could see, the MBR written on the USB stick > did not contain the required information to start the grub2 loader. > What grub2-install command, precisely, did (or would) you give? For this you use grub-mkrescue. http://www.gnu.org/software/grub/manual/grub.html#Invoking-grub_002dmkrescue That's why it's easier to use a livecd, or even easier is use the rescue boot option on DVD or netinstall media, which causes anaconda to find your installation, and properly mount everything at /mnt/sysimage so that all you have to do is chroot it, and then reinstall grub. chroot /mnt/sysimage grub2-install /dev/sdX grub2-mkconfig -o /boot/grub2/grub.cfg >> Or you can just do this from Live Desktop written to a USB stick. > > I did try installing Fedora KDE Live CD on the stick - > is that what you are suggesting? - > but I found the grub version that ran on the stick (presumably grub2) > was not the best - > it didn't seem possible to use it interactively. GRUB2 doesn't have an interactive mode when you're booted in linux, it has a set of script commands that run stand alone: e.g. grub2-install, grub2-mkconfig. > > Possibly my experience is due to my ignorance of grub2 usage. > But I also tried using a CentOS Live USB stick, > and had no better luck. Well that's a completely different beast because it uses GRUB legacy, there are more differences than similarities between the two GRUBs. GRUB2 is a rewrite. GRUB legacy is unmaintained by upstream for something like 8 years. They don't even provide help for it on their mailing list anymore. Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Saving Fedora when installing Windows?
On Mar 12, 2014, at 6:39 AM, Timothy Murphy wrote: > Tim wrote: > >>> I want to upgrade Windows XP on my laptop to Windows 7, >>> but I'd like to be sure that I can get back to Linux afterwards. >>> (I'm sure Windows installation will over-write the MBR.) > >> Some people modify the Windows bootloader, so that *it* can be used to >> boot Linux. You *can* have the Linux bootloader set up to choose >> between booting Windows and Linux, *and* the Windows bootloader set up >> to choose which to boot. > > That's interesting. > I've always regarded the Windows bootloader as a black box, > my occasional journeys into the Windows Registry having proved disastrous. > > But I don't see how both can be on offer - > do they use the MBRs of different drives? No, in this case the Windows boot manager chainloads GRUB rather than the usual way which is for GRUB to chain load Windows. By configuring them to have options chainload each other, it's a circle. Whose code occupies the MBR bootstrap region is the bootloader that comes up first. Chris Murphy -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
how do i use 2 external computer screens?
i just got a laptop with dual video cards. how would i set it up to use 2 external screens? thanks -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
fedora 20 login screen
im trying to config my laptop running fedora 20. in system settings I have installed some themes for the login screen but none of them will show up. it says they are installed on the "get new themes" window but they dont show up. any advice thanks -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora 18 not booting after lots of successful boot ups
On Wed, 2014-03-12 at 17:57 +0330, takCoder wrote: > would anyone please give me any hints? > can I disable bluetooth servive from repair mode? [Please don't top-post on the Fedora lists. See the Guidelines document referenced at the end of every post.] F18 is EOL, i.e. no longer supported, however you might try booting in rescue mode, then: 1) chroot /mnt/... (root of the system you're trying to fix) 2) systemctl disable bluetooth.service I've no idea if this will work. poc -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: AMD Catalyst Control Center doesn't work
On Wed, Mar 12, 2014 at 14:10:31 +, Marko Vojinovic wrote: ATI is known to have a notoriously lousy support for Linux in general and Fedora in particular. For their low-end and oldish cards, they provide specs on which the Linux community has built the open-source radeon driver (which works well). For their high-end cards, they refuse to provide specs (so no open-source driver), while their closed-source catalyst (fglrx) driver is a miserable POS that is almost never up-to-date with the latest kernel and X. There was a period where they weren't providing specs on post r200 chips. However currently they are providing specs for most of the GPU features. Lately they have been opening up more even for the video encoding and decoding features. (They have to be really careful there, as if there is information released that lets people bypass DRM and gets their chips black listed in Windows it could cost them a lot of money.) In contrast, nVidia does not give away the specs for their cards, but their closed-source driver simply Just Works(tm). Also, recently nVidia folks decided to provide some (limited) specs to the open-source nouveau devs, so there seems to be some light at the end of that tunnel... ;-) Their drivers don't do kms which is going to be a problem as ums is in the process of going away. They do seem to be making some changes for the better. Intel has arguably the nest support for graphics (but just their in house stuff, not the designs they purchased). However their built in graphics devices aren't as powerful as the high end cards for AMD and nVidia. If you don't need that power, then Intel is a good choice. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora 18 not booting after lots of successful boot ups
would anyone please give me any hints? can I disable bluetooth servive from repair mode? Best Regards, t.a.k On Wed, Mar 12, 2014 at 2:06 PM, takCoder wrote: > Hi All, > > I'm new in fedora world and here's my first unsolved problem there.. It's > an un-reasoned hang during boot up of a healthy system.. > > I have installed fedora 18 on a ssd, followed a given process to install > required packages of my goal system, and it was working fine before.. > > Today I powered my system up and it hanged during boot up.. using 'e' key > and changing gfxpayload value to text showed me this error: > Starting Bluetooth Service... > systemd-readahead[416]: Failed to open pack file: Read-only system > > I googled it but I could not find the given error.. > > Actually there is no need for bluetooth service on my system, but I can't > figure it out what exactly the error is. > > Would someone please give me a hand on this? I would really appreciate > that.. > > Kind regards, > takcoder > -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: AMD Catalyst Control Center doesn't work
On 03/12/2014 10:10 AM, Marko Vojinovic wrote: > You want the Driver option to be "radeon". Or better yet, rename/remove > your xorg.conf file and let X configure itself automatically. I'm new to fedora. I know how to do that in Debian.. reconfigure-xserver-xorg I don't see a "radeon" driver, is fglrx close? -- Paul Cartwright Registered Linux User #367800 and new counter #561587 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: AMD Catalyst Control Center doesn't work
On 03/12/2014 10:17 AM, Rex Dieter wrote: > Marko Vojinovic wrote: > >> ATI is known to have a notoriously lousy support for Linux in general >> and Fedora in particular. For their low-end and oldish cards, >> they provide specs on which the Linux community has built the >> open-source radeon driver (which works well). For their high-end cards, >> they refuse to provide specs (so no open-source driver), > I've been a long-time advocate for AMD/ATI, largely due to their making > available the specs. Do you have references or citations to support the > claim that specs are not available for some/high-end cards? > > -- Rex > the reason I switched to AMD/ATI cards was I had lousy results with Nvidia cards! -- Paul Cartwright Registered Linux User #367800 and new counter #561587 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: AMD Catalyst Control Center doesn't work
Marko Vojinovic wrote: > ATI is known to have a notoriously lousy support for Linux in general > and Fedora in particular. For their low-end and oldish cards, > they provide specs on which the Linux community has built the > open-source radeon driver (which works well). For their high-end cards, > they refuse to provide specs (so no open-source driver), I've been a long-time advocate for AMD/ATI, largely due to their making available the specs. Do you have references or citations to support the claim that specs are not available for some/high-end cards? -- Rex -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: AMD Catalyst Control Center doesn't work
On Wed, 12 Mar 2014 09:11:01 -0400 Paul Cartwright wrote: > I have googled & read all I could find, with no apparent solution in > sight. I have a Dell desktop with a Radeon HD 5670 video card : > lspci|grep VGA > 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. > [AMD/ATI] Redwood XT [Radeon HD 5670/5690/5730] > > I installed the amd catalyst via the file: > amd-catalyst-13.12-linux-x86.x86_64.run. Catalyst driver mostly does not support Fedora, and more often than not it just doesn't work. Uninstall it, and use the default open-source radeon driver (see below). > my xorg.conf file shows this: > ection "Device" > Identifier "aticonfig-Device[0]-0" > Driver "fglrx" You want the Driver option to be "radeon". Or better yet, rename/remove your xorg.conf file and let X configure itself automatically. ATI is known to have a notoriously lousy support for Linux in general and Fedora in particular. For their low-end and oldish cards, they provide specs on which the Linux community has built the open-source radeon driver (which works well). For their high-end cards, they refuse to provide specs (so no open-source driver), while their closed-source catalyst (fglrx) driver is a miserable POS that is almost never up-to-date with the latest kernel and X. In contrast, nVidia does not give away the specs for their cards, but their closed-source driver simply Just Works(tm). Also, recently nVidia folks decided to provide some (limited) specs to the open-source nouveau devs, so there seems to be some light at the end of that tunnel... ;-) IOW, forget catalyst and use the radeon driver. And if radeon driver doesn't work for your card, you are out of luck. HTH, :-) Marko -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Saving Fedora when installing Windows?
Mark Haney wrote: >> I want to upgrade Windows XP on my laptop to Windows 7, but I'd >> like to be sure that I can get back to Linux afterwards. (I'm sure >> Windows installation will over-write the MBR.) > A quick google popped this up: > https://ask.fedoraproject.org/en/question/8561/cannot-boot-to-fedora-after-installing-windows7/ Thanks for the pointer. I'll try out what is suggested there. I think the suggestion is to transfer the whole Fedora DVD to a USB stick. I only tried transferring a Live CD to the stick, and this does not offer a Linux Rescue boot option, as far as I could see. -- Timothy Murphy e-mail: gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin 2, Ireland -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Saving Fedora when installing Windows?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/12/14 08:39, Timothy Murphy wrote: > Tim wrote: > >>> I want to upgrade Windows XP on my laptop to Windows 7, but I'd >>> like to be sure that I can get back to Linux afterwards. (I'm >>> sure Windows installation will over-write the MBR.) > >> Some people modify the Windows bootloader, so that *it* can be >> used to boot Linux. You *can* have the Linux bootloader set up >> to choose between booting Windows and Linux, *and* the Windows >> bootloader set up to choose which to boot. > > That's interesting. I've always regarded the Windows bootloader as > a black box, my occasional journeys into the Windows Registry > having proved disastrous. > > But I don't see how both can be on offer - do they use the MBRs of > different drives? > > I've actually done this before. And it can be handy. But for me, the sheer terror of mucking with the NT boot loader kept me from doing it more than once. It was really just to say I did. And there is a trick to it when using MBRs on different drives. But I don't remember the exact details (I did this before Win7 was released, God knows what kind of funky voodoo magic would be needed with Win7 or 8. - -- Mark Haney Network/Systems Administrator Practichem W: (919) 714-8428 Fedora release 20 (Heisenbug) 3.13.4-200.fc20.x86_64 -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTIFzuAAoJEM/YzwEAv6e70bAH/ifOxTb0Qq/wN2mD1OKex2ZH TgHfJGLSeDxG9gDQuXXJKVFF0k8TlOmNOiDsNBFnWV8q1garsjeEG7HpEU8PZUM7 WwByuhmygSlWJ/qnPI5V3TLl9SPsVqLi29mFOtESzeCWfT6MQyIXYQfzKhDCUCzi cWBI5u7ztsSETX2TblcsEdnlG4E2CuxTAtaat+o6nf9Fw8/u0jIL0bxYfdO9AVAp V9Hm8a3YYHdIvlMJ7AuCO8T9D25tguHjFHECF6KavzFGQVFgxwAtPQDRqFciancJ D5MP+eC1KLpb7QtQGMcPXJxJWZmlpBNyooxxZJvXAgPfBk2SHENsdU/LdQFk7C8= =d0hZ -END PGP SIGNATURE- -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
AMD Catalyst Control Center doesn't work
I have googled & read all I could find, with no apparent solution in sight. I have a Dell desktop with a Radeon HD 5670 video card : lspci|grep VGA 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Redwood XT [Radeon HD 5670/5690/5730] I installed the amd catalyst via the file: amd-catalyst-13.12-linux-x86.x86_64.run. I see the amd catalyst control center & Administrative mode items in my menus ( System-Preferences-Hardware). when I select either menu item, nothing happens. my xorg.conf file shows this: ection "Device" Identifier "aticonfig-Device[0]-0" Driver "fglrx" BusID "PCI:1:0:0" EndSection but a rpm -q fglrx says it is not installed. I'm confused. There is an annoying lag when I drag windows, and I was trying to configure the display, but nothing seems to work. -- Paul Cartwright Registered Linux User #367800 and new counter #561587 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Saving Fedora when installing Windows?
Chris Murphy wrote: >> I want to upgrade Windows XP on my laptop to Windows 7, >> but I'd like to be sure that I can get back to Linux afterwards. >> (I'm sure Windows installation will over-write the MBR.) > Which version of Fedora? I'm running Fedora-20/KDE. >> One thing I tried without success in the past >> was to specify a USB stick when running grub2-install. > Sure, and then at the grub prompt you can use ls to find the designation > for the drive and partition, then use configfile > (hdx,msdosy)/grub2/grub.cfg which will produce the grub menu and let you > boot. Then you can reinstall grub to the hard drive once booted. Last time I tried this I didn't get a grub prompt when re-starting the machine with the USB stick in. Is that what you are suggesting? As far as I could see, the MBR written on the USB stick did not contain the required information to start the grub2 loader. What grub2-install command, precisely, did (or would) you give? > Or you can just do this from Live Desktop written to a USB stick. I did try installing Fedora KDE Live CD on the stick - is that what you are suggesting? - but I found the grub version that ran on the stick (presumably grub2) was not the best - it didn't seem possible to use it interactively. Possibly my experience is due to my ignorance of grub2 usage. But I also tried using a CentOS Live USB stick, and had no better luck. -- Timothy Murphy e-mail: gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin 2, Ireland -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Saving Fedora when installing Windows?
Tim wrote: >> I want to upgrade Windows XP on my laptop to Windows 7, >> but I'd like to be sure that I can get back to Linux afterwards. >> (I'm sure Windows installation will over-write the MBR.) > Some people modify the Windows bootloader, so that *it* can be used to > boot Linux. You *can* have the Linux bootloader set up to choose > between booting Windows and Linux, *and* the Windows bootloader set up > to choose which to boot. That's interesting. I've always regarded the Windows bootloader as a black box, my occasional journeys into the Windows Registry having proved disastrous. But I don't see how both can be on offer - do they use the MBRs of different drives? -- Timothy Murphy e-mail: gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin 2, Ireland -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
RE: Java under Fedora
Patrick Kobly wrote: > FWIW, If you're looking to do anything moderately serious, you're going to > want to use Maven to manage your build and dependencies... I normally use Eclipse, but when looking into servlets I thought it would be simplest to use Java directly, at least to begin with. I find Eclipse has several drawbacks - eg, the editor that comes with it seems to me to have serious faults, so that sections of the source programs are likely to disappear into a black hole. But it also has advantages, particularly in debugging, and for me these just about outweigh the disadvantages. I looked at Maven very briefly, but it looked excessively complicated to me. But I am not a serious Java user, -- Timothy Murphy e-mail: gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin 2, Ireland -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Saving Fedora when installing Windows?
Allegedly, on or about 11 March 2014, Timothy Murphy sent: > I want to upgrade Windows XP on my laptop to Windows 7, > but I'd like to be sure that I can get back to Linux afterwards. > (I'm sure Windows installation will over-write the MBR.) Some people modify the Windows bootloader, so that *it* can be used to boot Linux. You *can* have the Linux bootloader set up to choose between booting Windows and Linux, *and* the Windows bootloader set up to choose which to boot. That allows you to use either to boot up, and can be handy if you accidentally pick the wrong one - you can just reverse the decision when the other's bootloader screen came up, not to mention handy for if you get a glitch that modifies your usual way of booting up. -- [tim@localhost ~]$ uname -rsvp Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64 All mail to my mailbox is automatically deleted, there is no point trying to privately email me, I will only read messages posted to the public lists. George Orwell's '1984' was supposed to be a warning against tyranny, not a set of instructions for supposedly democratic governments. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Bluetooth mouse won't connect - SOLVED
On Sat, 2014-03-08 at 22:21 +, Patrick O'Callaghan wrote: > On Sun, 2014-03-09 at 04:52 +0800, Ed Greshko wrote: > > On 03/08/14 22:01, Patrick O'Callaghan wrote: > > > Various things about mice, such as: > > > > > >> > [ 3.188] (II) config/udev: Adding input device 2.4G Receiver > > >> > (/dev/input/mouse1) > > >> > [ 3.188] (II) No input driver specified, ignoring this device. > > > > No driver seems suspicious > > For now I solved the problem by using a different (non-BT) wireless > mouse. Just to close this off: I removed and reinstalled the BT mouse under Gnome and now it works (including under KDE). So it's probably not the Nvidia driver. poc -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Fedora 18 not booting after lots of successful boot ups
Hi All, I'm new in fedora world and here's my first unsolved problem there.. It's an un-reasoned hang during boot up of a healthy system.. I have installed fedora 18 on a ssd, followed a given process to install required packages of my goal system, and it was working fine before.. Today I powered my system up and it hanged during boot up.. using 'e' key and changing gfxpayload value to text showed me this error: Starting Bluetooth Service... systemd-readahead[416]: Failed to open pack file: Read-only system I googled it but I could not find the given error.. Actually there is no need for bluetooth service on my system, but I can't figure it out what exactly the error is. Would someone please give me a hand on this? I would really appreciate that.. Kind regards, takcoder -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: f20 lvm - inactive LV
- Original Message - From: "Chris Murphy" To: mkopa...@gmail.com, "Community support for Fedora users" Sent: Monday, March 10, 2014 3:29:13 AM Subject: Re: f20 lvm - inactive LV I would start with: journalctl -b -x -o short-monotonic --no-pager And then start search for some of the above items, like pvscan, to see if it's scanning for PVs and if it finds anything, and if it activates anything, and if not why not. Status can also be helpful. According to your advise i did review logs and found few disturbing and not clear errors: pvscan[792]: device-mapper: suspend ioctl on failed: Invalid argument pvscan[792]: Unable to suspend rootvg-varlv (253:9) lvm[796]: Monitoring RAID device rootvg-varlv for events. pvscan[774]: device-mapper: suspend ioctl on failed: Invalid argument pvscan[774]: Unable to suspend rootvg-tmplv (253:14) lvm[796]: Monitoring RAID device rootvg-tmplv for events. pvscan[792]: device-mapper: suspend ioctl on failed: Invalid argument pvscan[792]: Unable to suspend rootvg-usrlv (253:20) lvm[796]: Monitoring RAID device rootvg-usrlv for events. pvscan[774]: device-mapper: suspend ioctl on failed: Invalid argument pvscan[774]: Unable to suspend rootvg-rootlv (253:25) pvscan[774]: rootvg: refresh before autoactivation failed. lvm[796]: Monitoring RAID device rootvg-rootlv for events. pvscan[792]: rootvg: refresh before autoactivation failed. lvm[690]: 1 logical volume(s) in volume group "datavg" monitored lvm[690]: 26 logical volume(s) in volume group "rootvg" monitored lvm[690]: 4 logical volume(s) in volume group "lxcvg" monitored systemd[1]: Started Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling. -- Subject: Unit lvm2-monitor.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit lvm2-monitor.service has finished starting up. -- what does mean suspend in that case ? -- regards, Michal -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
