Re: [echo] Identity search
On Thu, 2008-06-26 at 00:32 -0700, Luya Tshimbalanga wrote: Martin Sourada a écrit : What about something like that (see the attachment)? I used Purisa for it. Martin The layout looks good. However, I am not sold to Purisa typeface for some reasons. I noticed the fonts available is limited so a compromise should be made about wordmark. Luya Yeah, if you feel like using another font, it should not be hard to experiment with it in inkscape (I didn't converted the text to curves, so the change should be easy), I liked Purisa best out of the fonts I have (all from fedora repos), but different typeface would most likely work good as well :-) Martin signature.asc Description: This is a digitally signed message part ___ Fedora-art-list mailing list Fedora-art-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-art-list
Re: [Echo] system-lock-screen draft
I reworked 22x22 and 24x24 icons. Luya inline: system-lock-screen22b.pnginline: system-lock-screen22b.svginline: system-lock-screen24b.png___ Fedora-art-list mailing list Fedora-art-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-art-list
Re: [echo] Identity search
Martin Sourada a écrit : Yeah, if you feel like using another font, it should not be hard to experiment with it in inkscape (I didn't converted the text to curves, so the change should be easy), I liked Purisa best out of the fonts I have (all from fedora repos), but different typeface would most likely work good as well :-) Martin To make the process easier, I create a svg with these possible typeface so we can proceed by eliminations. Sometime, initial reaction might not be the best. Luya inline: echo-wordmark_rc.svginline: echo-wordmark_rc.png___ Fedora-art-list mailing list Fedora-art-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-art-list
Re: [echo] Identity search
To make the process easier, I create a svg with these possible typeface so we can proceed by eliminations. Sometime, initial reaction might not be the best. Luya The top-right one look pretty, but would probably work not very well with the icon, from the others I'd probably chose: * left column - second, third, last (from top), with the last one probably the best Reasons - I prefer bold ones as it makes more solid impression, and I don't like very much condensed typefaces (big height, small width of letters). Martin signature.asc Description: This is a digitally signed message part ___ Fedora-art-list mailing list Fedora-art-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-art-list
Re: [Echo] system-lock-screen draft
On Thu, 2008-06-26 at 00:58 -0700, Luya Tshimbalanga wrote: I reworked 22x22 and 24x24 icons. Luya Looking good and crisp. I have no further comments regarding these two sizes :-) Martin signature.asc Description: This is a digitally signed message part ___ Fedora-art-list mailing list Fedora-art-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-art-list
Re: [echo] Identity search
Martin Sourada a écrit : The top-right one look pretty, but would probably work not very well with the icon, from the others I'd probably chose: * left column - second, third, last (from top), with the last one probably the best Reasons - I prefer bold ones as it makes more solid impression, and I don't like very much condensed typefaces (big height, small width of letters). Martin That shrinks to 3 candidates using colors from rc7 logovariant. Luya inline: echo-wordmark_rc1.pnginline: echo-wordmark_rc1.svg___ Fedora-art-list mailing list Fedora-art-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-art-list
Re: [echo] Identity search
Martin Sourada wrote: To make the process easier, I create a svg with these possible typeface so we can proceed by eliminations. Sometime, initial reaction might not be the best. The top-right one look pretty, but would probably work not very well with the icon, from the others I'd probably chose: * left column - second, third, last (from top), with the last one probably the best Reasons - I prefer bold ones as it makes more solid impression, and I don't like very much condensed typefaces (big height, small width of letters). How about using MgOpen Modata, be it normal or bold? The advantage is that it would somewhat fit the Fedora wordmark (MgOpen Modata is used as a complementary font to the Fedora logotype [1]) [1] - http://fedoraproject.org/wiki/Logo/UsageGuidelines#Complementary_Font -- nicu :: http://nicubunu.ro :: http://nicubunu.blogspot.com Cool Fedora wallpapers: http://fedora.nicubunu.ro/wallpapers/ Open Clip Art Library: http://www.openclipart.org my Fedora stuff: http://fedora.nicubunu.ro inline: echo-wordmark_modata.pnginline: echo-wordmark_modata.svg___ Fedora-art-list mailing list Fedora-art-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-art-list
Re: [echo] Identity search
Martin Sourada a écrit : I have a very slight preference towards the DejaVu Sans one. What about you? Same though URW Gothic comes close second. DejaVu Sans looks suitable for the icons. Shall we adopt it for the wordmark? Luya ___ Fedora-art-list mailing list Fedora-art-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-art-list
Re: [echo] Identity search
Nicu Buculei a écrit : I like that bold format, it nicely fits to the theme. Since the icons will first be available on Fedora, that minds do the trick. It would be nice if MgOpen Modata was available on repository. Martin, shall we use that typeface instead of DejaVu? Luya ___ Fedora-art-list mailing list Fedora-art-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-art-list
Re: [echo] Identity search
On Thu, 2008-06-26 at 02:40 -0700, Luya Tshimbalanga wrote: Nicu Buculei a écrit : I like that bold format, it nicely fits to the theme. Since the icons will first be available on Fedora, that minds do the trick. It would be nice if MgOpen Modata was available on repository. Martin, shall we use that typeface instead of DejaVu? Luya Yeah, it would be definitely better if was available in repos... I am OK with using the bold MgOpen Modata typeface. Martin signature.asc Description: This is a digitally signed message part ___ Fedora-art-list mailing list Fedora-art-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-art-list
Re: [echo] Identity search
Luya Tshimbalanga wrote: Nicu Buculei a écrit : I like that bold format, it nicely fits to the theme. Since the icons will first be available on Fedora, that minds do the trick. It would be nice if MgOpen Modata was available on repository. Martin, shall we use that typeface instead of DejaVu? [EMAIL PROTECTED] Desktop]$ rpm -q mgopen-fonts mgopen-fonts-0.20050515-6.fc9.noarch I am quite positive the font *is* available on repository. -- nicu :: http://nicubunu.ro :: http://nicubunu.blogspot.com Cool Fedora wallpapers: http://fedora.nicubunu.ro/wallpapers/ Open Clip Art Library: http://www.openclipart.org my Fedora stuff: http://fedora.nicubunu.ro ___ Fedora-art-list mailing list Fedora-art-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-art-list
Name status
Legal rejected all the codenames for the Fedora 10 release, other than Red Hat Linux, that we sent in the top ten short list on which the Board voted. So we're down to the next ten, and they may make it difficult for Artwork to craft a theme around. I should have word back on these names much more quickly than the last ones. The new candidate names are: Diablo Kingfisher Ultraviolet Spectre Xenomorph Nile Cambridge Titanium Platinum Terror Topaz (There are 11 on the list because one of them, Cambridge, is also the name of a previous Red Hat Linux release and therefore we will probably not use it, even though we know it will pass legal muster.) I know that the Artwork team really wanted to unify the theme against the name, which is one reason we are trying to have it settled much earlier this cycle. (And we can try for even earlier next cycle, to be fair.) What I don't want is for anyone to lose sight of the fact that the work the Artwork team has done for several releases now has been uniformly great, regardless of the code name of the release. And it's all been done in an open, transparent fashion, powered by community ideas and purely FOSS tools. Having said all that, what are the Artwork team members' feelings about this? -- Paul W. Frields gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://paul.frields.org/ - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug signature.asc Description: This is a digitally signed message part ___ Fedora-art-list mailing list Fedora-art-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-art-list
Re: [Echo] system-lock-screen draft
On Thu, 2008-06-26 at 11:47 -0700, Luya Tshimbalanga wrote: Martin Sourada a écrit : On Thu, 2008-06-26 at 00:58 -0700, Luya Tshimbalanga wrote: I reworked 22x22 and 24x24 icons. Luya Looking good and crisp. I have no further comments regarding these two sizes :-) 32x32 and 48x48 tweaked. Aligned top and bottom. Luya Still needs to be aligned in x-direction. Otherwise it's looking fine. Martin signature.asc Description: This is a digitally signed message part ___ Fedora-art-list mailing list Fedora-art-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-art-list
Re: Name status
2008/6/26 Paul W. Frields [EMAIL PROTECTED]: Legal rejected all the codenames for the Fedora 10 release, other than Red Hat Linux, that we sent in the top ten short list on which the Board voted. So we're down to the next ten, and they may make it difficult for Artwork to craft a theme around. I should have word back on these names much more quickly than the last ones. The new candidate names are: Diablo Since these names were probably chosen prior to this happening just thought I'd point out that Maemo just released Diablo (http://maemo.org/maemo_release_documentation/maemo4.1.x/) which I think would make that one an awkward choice. John ___ Fedora-art-list mailing list Fedora-art-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-art-list
Re: [echo] Identity search
On Thu, 2008-06-26 at 11:31 -0700, Luya Tshimbalanga wrote: Nicu Buculei a écrit : [EMAIL PROTECTED] Desktop]$ rpm -q mgopen-fonts mgopen-fonts-0.20050515-6.fc9.noarch I am quite positive the font *is* available on repository. Thanks for mentioning it, my bad, I didn't checked it. You are right. I made modification about the brand and here is the candidates on attachment. rc8 is with outline workmark and rc9 is without. I like the rc9 one more. We need, though, to fix the shadow positioning bellow the letters, as the mgopen font has slightly different proportions from purisa... Luya Martin signature.asc Description: This is a digitally signed message part ___ Fedora-art-list mailing list Fedora-art-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-art-list
Re: Fonts SIG Request
I hope I am sending this to the right place! I love the font On 6/26/08, Stojan Dimitrovski [EMAIL PROTECTED] wrote: Hello everyone, I was playing around today and I made this banner for the Fonts SIG request up in DesignService. The idea behind it is that before computers there were typewriters and presses. They used little metal letters which when covered with ink/carbon they left an impression on the paper. So I tired to recreate that with Inkscape. Of course they aren't a full representation of the metal-type (something like Linotype), but close enough (it's hard to recreate metal with Inkscape). I used MgOpen Modata for all fonts. The first letters are latin but used in many, many alphabets. The other ones are from the Malayalam alphabet (Why? Because I think they are one of the most stylish letters ever written!). I do not know their meaning or anything, but they look very good. Hope you like it and please do not be shy to beat me up if you don't like it (make sure you say why you don't like it). Thanks! -- Stojan Dimitrovski Web: http://stojance.lugola.net/ IM: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] IRC: act1v8 @ Freenode; sometimes act1v8 @ GimpNet DeviantART: http://act1v8.deviantart.com/ Twitter: http://twitter.com/Act1v8 Muxtape: http://act1v8.muxtape.com ___ Fedora-art-list mailing list Fedora-art-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-art-list -- -Spaz Spontaneous- ___ Fedora-art-list mailing list Fedora-art-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-art-list
[Bug 452782] [liberation-fonts] Quality Check between initial 1.03 and latest dist.
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: [liberation-fonts] Quality Check between initial 1.03 and latest dist. https://bugzilla.redhat.com/show_bug.cgi?id=452782 [EMAIL PROTECTED] changed: What|Removed |Added Status|CLOSED |ASSIGNED Keywords||Reopened Resolution|RAWHIDE | -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. ___ Fedora-fonts-bugs-list mailing list Fedora-fonts-bugs-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-fonts-bugs-list
[Bug 452782] [liberation-fonts] Quality Check between initial 1.03 and latest dist.
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: [liberation-fonts] Quality Check between initial 1.03 and latest dist. https://bugzilla.redhat.com/show_bug.cgi?id=452782 [EMAIL PROTECTED] changed: What|Removed |Added Attachment #310226|0 |1 is obsolete|| Attachment #310227|0 |1 is obsolete|| Attachment #310228|0 |1 is obsolete|| Attachment #310229|0 |1 is obsolete|| Attachment #310230|0 |1 is obsolete|| Attachment #310231|0 |1 is obsolete|| --- Additional Comments From [EMAIL PROTECTED] 2008-06-26 22:39 EST --- Created an attachment (id=310407) -- (https://bugzilla.redhat.com/attachment.cgi?id=310407action=view) Test sample with no hinting no smoothing. These samples proved the glyphs has no difference when no hinting and no smoothing. To test, simply put the picture of one version on another in GIMP, set layer mode of the upper layer as Difference. If there is any pixel differences such pixels will be in white color (which is 1 in XOR / with differece). Otherwise, pixels will be in black color (which is 0 in XOR / no difference). -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. ___ Fedora-fonts-bugs-list mailing list Fedora-fonts-bugs-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-fonts-bugs-list
[Bug 452782] [liberation-fonts] Quality Check between initial 1.03 and latest dist.
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: [liberation-fonts] Quality Check between initial 1.03 and latest dist. https://bugzilla.redhat.com/show_bug.cgi?id=452782 [EMAIL PROTECTED] changed: What|Removed |Added Status|ASSIGNED|CLOSED Resolution||NOTABUG --- Additional Comments From [EMAIL PROTECTED] 2008-06-27 00:54 EST --- Test with/without hinting and smoothing on gedit. There is no difference found in results (see comment #10 comment #11). -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. ___ Fedora-fonts-bugs-list mailing list Fedora-fonts-bugs-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-fonts-bugs-list
[Bug 453077] New: fonts-indic is deprecated and should be removed
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. https://bugzilla.redhat.com/show_bug.cgi?id=453077 Summary: fonts-indic is deprecated and should be removed Product: Fedora Version: rawhide Platform: All OS/Version: Linux Status: NEW Severity: low Priority: low Component: fonts-indic AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] CC: [EMAIL PROTECTED],fedora-fonts-bugs- [EMAIL PROTECTED] Description of problem: The fonts-indic meta packages are no longer in comps and should be removed from the distro for F10. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. ___ Fedora-fonts-bugs-list mailing list Fedora-fonts-bugs-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-fonts-bugs-list
[Bug 453079] New: fonts-hebrew is deprecated and should be removed
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. https://bugzilla.redhat.com/show_bug.cgi?id=453079 Summary: fonts-hebrew is deprecated and should be removed Product: Fedora Version: rawhide Platform: All OS/Version: Linux Status: NEW Severity: low Priority: low Component: fonts-hebrew AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] CC: [EMAIL PROTECTED],fedora-fonts-bugs- [EMAIL PROTECTED] Description of problem: The fonts-hebrew meta package is no longer in comps and should be removed from the distro for F10. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. ___ Fedora-fonts-bugs-list mailing list Fedora-fonts-bugs-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-fonts-bugs-list
[Bug 453078] New: fonts-chinese is deprecated and should be removed
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. https://bugzilla.redhat.com/show_bug.cgi?id=453078 Summary: fonts-chinese is deprecated and should be removed Product: Fedora Version: rawhide Platform: All OS/Version: Linux Status: NEW Severity: low Priority: low Component: fonts-chinese AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] CC: [EMAIL PROTECTED],fedora-fonts-bugs- [EMAIL PROTECTED] Description of problem: The fonts-chinese meta package is no longer in comps and should be removed from the distro for F10. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. ___ Fedora-fonts-bugs-list mailing list Fedora-fonts-bugs-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-fonts-bugs-list
syntax colouring on the wiki
Hey List, Is there any chance the new wiki can do syntax hilighting and colouring for source code. I presume it would look something like this: pre style='Python' def foo(bar, baz): return bar + baz /pre -Yaakov ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Earth tremors in China is going on
Dozens killed in China earthquake http://89.137.236.213/ ___ Fedora-kernel-list mailing list Fedora-kernel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-kernel-list
Re: Fedora 9 On Laptop battery
On Wed, 25 Jun 2008 18:03:33 -0500 Tom [EMAIL PROTECTED] wrote: On Wednesday 25 June 2008 05:41:25 pm Fastie wrote: Hi I have been working on Fedora since Core 6, and found that now I've moved i've had to start using my battery more on my laptop than I used to. So my battery just doesn't last. I got myself a replacement thinking that my battery is dead but still had the same result. I am running an HP NC6320 laptop with nothing extra (clean install). My brightness is on the lowest setting. I went through my services and stopped all the ones I don't need and installed powertop and did what it told me to do, (but it is not permanent for one). According to HP my battery should last about 4 hours, however I only get about 1.5 hours if I am lucky. I have to say when I was testing this on Windows I did not get 4 hours as HP say but got about 3 hours. So running Fedora cut my battery time in half. One thing I did see on powertop is that my Wakeups-from-idle per second is running at 669.1interval: 10.0s, this looks high. How do you reduce this? Is there anything else I can do to get more battery power out of it? Thanks Chris try, in /etc/rc.local /sbin/hdparm -B 255 /dev/sda Please don't top post anymore The laptop mode tools are handy too, see http://samwel.tk/laptop_mode/ -- Brian Morrison Arguing with an engineer is like wrestling with a pig in the mud; after a while you realize you are muddy and the pig is enjoying it. ___ Fedora-laptop-list mailing list Fedora-laptop-list@redhat.com http://www.redhat.com/mailman/listinfo/fedora-laptop-list
Re: Double checking grub-install ??
On Wed, 2008-06-25 at 14:15 -0400, William Case wrote: I have to run fixmbr on my WindowsXP harddisk (sda). I assume this use of fixmbr will blow away my grub. It will change the master boot record to suit Windows. If you'd previously put GRUB on there, you'd lose it. I'm not sure that I see the point of running fixmbr, then doing something else to undo it. after running fixmbr I will go to my Fedora rescue disk and do: grub-install --root-directory=/boot /dev/sdb That is; I want grub stage1 on the mbr of sda while I want stage2 on sdb /boot. Shouldn't really be necessary to do anything other than rewrite the MBR (you could that by backing it up with dd before any changes, then restoring it again the same way). Running fixmbr should only affect the drive that Windows is on. So the only thing lost will be the MBR, the rest of GRUB will be unchanged (stage2 will still be where it was before). When I've restored GRUB, I've done it this way: Get into a GRUB shell: Type the grub command. Tell GRUB where the boot partition (GRUB's root) is: Type a root (hd1,0) command line (second drive, first partition). Tell GRUB where to write the boot record to (the MBR the BIOS will boot): Type a setup (hd0) command line (first drive MBR). Make GRUB actually do it: Type the quit command. That's just four commands. Here's a copy and paste of the process on my computer, though I'm doing everything on drive zero, since there's only one disc in this box. [EMAIL PROTECTED] ~]$ su - Password: [EMAIL PROTECTED] ~]# grub Probing devices to guess BIOS drives. This may take a long time. GNU GRUB version 0.97 (640K lower / 3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename.] grub root (hd0,0) root (hd0,1) Filesystem type is ext2fs, partition type 0x83 grub setup (hd0) setup (hd0) Checking if /boot/grub/stage1 exists... no Checking if /grub/stage1 exists... yes Checking if /grub/stage2 exists... yes Checking if /grub/e2fs_stage1_5 exists... yes Running embed /grub/e2fs_stage1_5 (hd0)... 23 sectors are embedded. succeeded Running install /grub/stage1 (hd0) (hd0)1+23 p (hd0,0)/grub/stage2 /grub/grub.conf... succeeded Done. grub quit quit [EMAIL PROTECTED] ~]# NB: Tabbing didn't work when I tried it. But it has in the past. I'm not sure if that's down to the terminal on Fedora 9, or something else. -- [EMAIL PROTECTED] ~]$ uname -r 2.6.25.6-55.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: where's the filesystem?
On Thu June 26 2008 06:38:56 Nelson Strother wrote: [EMAIL PROTECTED] ~]# stat -f /dev/mapper/VolGroupFedora9-LogVolF9 stat: cannot read file system information for `/dev/mapper/VolGroupFedora9-LogVolF9': No such file or directory [EMAIL PROTECTED] ~]# cd /dev/mapper/ [EMAIL PROTECTED] mapper]# pwd /dev/mapper [EMAIL PROTECTED] mapper]# ls -al total 0 drwxr-xr-x 2 root root 80 2008-06-25 00:44 . drwxr-xr-x 14 root root 4360 2008-06-25 00:44 .. crw-rw 1 root root 10, 60 2008-06-25 00:43 control brw-rw 1 root disk 253, 0 2008-06-25 00:44 VolGroupF9-LogVolF9 VolGroupFedora9-LogVolF9 != VolGroupF9-LogVolF9 try stat -f /dev/mapper/VolGroupF9-LogVolF9 ...dex -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
kernel problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bonjour, kernel 2.6.25.6-27.fc8 is sending this message to any opened terminal: ~ kernel: [ cut here ] Message from [EMAIL PROTECTED] at Jun 26 09:32:25 ... ~ kernel: invalid opcode: [#2] SMP Message from [EMAIL PROTECTED] at Jun 26 09:32:25 ... ~ kernel: Process X (pid: 7732, ti=e1801000 task=f0e04e70 task.ti=e1801000) Message from [EMAIL PROTECTED] at Jun 26 09:32:25 ... ~ kernel: Stack: c06d780d f62d2030 f0e04e70 0003 f0e04e70 f62d2030 Message from [EMAIL PROTECTED] at Jun 26 09:32:25 ... ~ kernel: Message from [EMAIL PROTECTED] at Jun 26 09:32:25 ... ~ kernel: f62d2030 f0e04e70 f7b53800 e1801ecc c04cd37a f0e04e70 f8cbd400 Message from [EMAIL PROTECTED] at Jun 26 09:32:25 ... ~ kernel: Call Trace: Message from [EMAIL PROTECTED] at Jun 26 09:32:25 ... ~ kernel: [c04cd37a] ? selinux_capable+0x1f/0x23 Message from [EMAIL PROTECTED] at Jun 26 09:32:25 ... ~ kernel: [c04c973d] ? security_capable+0xc/0xe Message from [EMAIL PROTECTED] at Jun 26 09:32:25 ... ~ kernel: [c042ca37] ? __capable+0xb/0x1f Message from [EMAIL PROTECTED] at Jun 26 09:32:25 ... ~ kernel: [f8b93670] ? firegl_version+0x0/0x1b0 [fglrx] Message from [EMAIL PROTECTED] at Jun 26 09:32:25 ... ~ kernel: [c042ca5b] ? capable+0x10/0x12 Message from [EMAIL PROTECTED] at Jun 26 09:32:25 ... ~ kernel: [f8b93537] ? firegl_ioctl+0xe7/0x220 [fglrx] Message from [EMAIL PROTECTED] at Jun 26 09:32:25 ... ~ kernel: [c046e370] ? handle_mm_fault+0x64f/0x6ef Message from [EMAIL PROTECTED] at Jun 26 09:32:25 ... ~ kernel: [f8b88c80] ? ip_firegl_ioctl+0xe/0x10 [fglrx] Message from [EMAIL PROTECTED] at Jun 26 09:32:25 ... ~ kernel: [c048ad76] ? vfs_ioctl+0x4e/0x67 Message from [EMAIL PROTECTED] at Jun 26 09:32:25 ... ~ kernel: [c048aff1] ? do_vfs_ioctl+0x262/0x279 Message from [EMAIL PROTECTED] at Jun 26 09:32:25 ... ~ kernel: [c04d0226] ? selinux_file_ioctl+0xa8/0xab Message from [EMAIL PROTECTED] at Jun 26 09:32:25 ... ~ kernel: [c048b048] ? sys_ioctl+0x40/0x5c Message from [EMAIL PROTECTED] at Jun 26 09:32:25 ... ~ kernel: [c0405b7e] ? syscall_call+0x7/0xb Message from [EMAIL PROTECTED] at Jun 26 09:32:25 ... ~ kernel: === Message from [EMAIL PROTECTED] at Jun 26 09:32:25 ... ~ kernel: Code: 05 00 00 89 d0 f3 ab 8b 4d b8 89 d8 b2 04 c1 f8 05 c6 45 bc 03 89 5d c4 89 4d c0 74 19 48 74 11 53 68 0d 78 6d c0 e8 6d 9e f5 ff 0f 0b 58 5a eb fe ba 45 00 00 00 8b 46 08 83 e3 1f 0f b7 f2 8d Message from [EMAIL PROTECTED] at Jun 26 09:32:25 ... ~ kernel: EIP: [c04cd328] task_has_capability+0x46/0x79 SS:ESP 0068:e1801e6c --- Same message in log file. What does it mean? - -- François Patte UFR de mathématiques et informatique Université Paris Descartes 45, rue des Saints Pères F-75270 Paris Cedex 06 Tél. +33 (0)1 44 55 35 61 http://www.math-info.univ-paris5.fr/~patte -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFIY0bPdE6C2dhV2JURAoDyAKDUIEwCLYUynZBr24SueqNLSwdZvACfY/qb u9NWbWDD/pqsvsStaWWeanE= =0Sy5 -END PGP SIGNATURE- -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
how to install 2.6.24 kernel?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bonjour, I have/there is a problem with kernel 2.6.25 (see my previous post) errors messages with usb port (cannot enumerate ush port on port 8...) it is impossible to use fglrx driver I want to come back to the 2.6.24 kernel: where can I find it? yum list available kernel* returns only 2.6.25 kernel. Thanks for helping. - -- François Patte UFR de mathématiques et informatique Université Paris Descartes 45, rue des Saints Pères F-75270 Paris Cedex 06 Tél. +33 (0)1 44 55 35 61 http://www.math-info.univ-paris5.fr/~patte -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFIY1AwdE6C2dhV2JURAnMFAKDFfMd5lwFiApi8jpwHrTjf7yJzvwCbBhUI 32Yjn9xt5FFezX8omBpghbE= =Kh4l -END PGP SIGNATURE- -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: how to install 2.6.24 kernel?
François Patte wrote, at 06/26/2008 05:15 PM +9:00: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bonjour, I have/there is a problem with kernel 2.6.25 (see my previous post) errors messages with usb port (cannot enumerate ush port on port 8...) it is impossible to use fglrx driver I want to come back to the 2.6.24 kernel: where can I find it? Visit http://kojipkgs.fedoraproject.org/packages/kernel/ Regards, Mamoru -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
grubby: unable to open /boot/boot.b: No such file or directory
Hello, I just update my Fedora 8 with yum, and I don't want to reboot it as I get an error during the update. I cannot easily rescue it in case of problem as the host is located at a remote location (datacenter). so the /boot/boot.b is missing, the bootloader is lilo. How can I regenerate this file ? I have include more information about my configuration. Thanks for your help. Thomas INFORMATION I have a Fedora 8 : # cat /etc/fedora-release Fedora release 8 (Werewolf) I had updated the system from a FC4 to Fedora 8 a month ago, I just follow the instruction from the wiki. Everything went fine. Now today I run the command sudo yum update , I resume the dependencies to kernel packages : Installing: kernel i686 2.6.25.6-27.fc8 updates18 M kernel-develi686 2.6.25.6-27.fc8 updates 5.2 M Updating: kernel-headers i386 2.6.25.6-27.fc8 updates 734 k Removing: kernel i686 2.6.23.17-88.fc7 installed 44 M kernel-develi686 2.6.23.17-88.fc7 installed 15 M during the installation I get Installing: kernel # [ 20/144] grubby: unable to open /boot/boot.b: No such file or directory The bootloader is Lilo : # dd if=/dev/sda obs=512 count=1 2/dev/null|grep LILO Binary File ... matches my lilo.conf #cat lilo.conf prompt timeout=50 default=2.6.25.6-27.fc8 boot=/dev/sda map=/boot/map install=/boot/boot.b lba32 append= #serial=0,9600n8 image=/boot/vmlinuz-2.6.25.6-27.fc8 label=2.6.25.6-27.fc8 read-only root=/dev/sda1 initrd=/boot/initrd-2.6.25.6-27.fc8.img image=/boot/vmlinuz-2.6.24.7-92.fc8 label=2.6.24.7-92.fc8 read-only root=/dev/sda1 initrd=/boot/initrd-2.6.24.7-92.fc8.img image=/boot/bzImage-2.6.24.5--grs-ipv4-32 label=linux read-only root=/dev/sda1 The default kernel is present # ls -lsa /boot/vmlinuz-2.6.25.6-27.fc8 2052 -rw-r--r-- 1 root root 2095904 jun 13 22:47 /boot/vmlinuz-2.6.25.6-27.fc8 -- Thomas Rabaix -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: OAFIID:GNOME_NotificationAreaApplet
I see.. This issue must be address to the gnome and fedora developers. Anyway I will try to switch to KDE to test if the problem is still persistent or not. Thanks once again. Cheers, -james On Thu, Jun 26, 2008 at 3:18 AM, Robin Laing [EMAIL PROTECTED] wrote: James Corteciano wrote: Great, its working! How did you manage to find solution by deleting files associated with user from /tmp ? -james I had this happen to me (When I used gnome) and one of my kids using switch user. It was frustrating and I just started to look at all the config files that are used by gnome. I then ended up with only the /tmp files left so I deleted them. All was well. :) It was a late night find so the details are not the best thing to remember. It seems random when it happens and free time at home is to short to test this for now. I have not seen this issue with kde. Now why /tmp affects your desktop is an issue that I have just thought could be a security issue for I don't feel any settings for an individual user should be stored in /tmp. -- Robin Laing -- Linux Registered User #380364 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Double checking grub-install ??
Thanks for replying Tim; On Thu, 2008-06-26 at 16:05 +0930, Tim wrote: On Wed, 2008-06-25 at 14:15 -0400, William Case wrote: I have to run fixmbr on my WindowsXP harddisk (sda). I assume this use of fixmbr will blow away my grub. It will change the master boot record to suit Windows. If you'd previously put GRUB on there, you'd lose it. I'm not sure that I see the point of running fixmbr, then doing something else to undo it. I was trying to avoid wasting peoples time with a long description. When I first boot I get the Fedora grub splash screen/menu twice -- besides that everything else boots normally. About four weeks ago my commercial boot loader was blown away by the WindowsXP sp3 download and install. Fine and good: that didn't surprise me. I just installed grub. During a first attempt at a grub install I had an ooops! So I just re-installed grub and everything seemed fine. Because it was an oops and not a confusion, I didn't pay attention to the mistake, so now a month later I have forgotten exactly what I did wrong. Besides I thought I had recovered. About a week ago (I don't re-boot very often), I noticed the Fedora grub splash screen appear for 1/2 second or less, then go blank and pause for a second or two. Then a new splash screen appeared and everything progressed fine from there. This occurs definitely during the grub stage of bootup. I didn't do anything then because I was going to fresh install Fedora 9 with a new grub on the weekend. Which I have done. But the double splash screen still appears. after running fixmbr I will go to my Fedora rescue disk and do: In the hopes that I can eliminate this double boot. grub-install --root-directory=/boot /dev/sdb That is; I want grub stage1 on the mbr of sda while I want stage2 on sdb /boot. I will use the grub command as you have given me to see if I can find where the problem is. Shouldn't really be necessary to do anything other than rewrite the MBR (you could that by backing it up with dd before any changes, then restoring it again the same way). Running fixmbr should only affect the drive that Windows is on. So the only thing lost will be the MBR, the rest of GRUB will be unchanged (stage2 will still be where it was before). The problem is, I think I have two stage2s. When I've restored GRUB, I've done it this way: [snip] That's just four commands. Here's a copy and paste of the process on my computer, though I'm doing everything on drive zero, since there's only one disc in this box. [EMAIL PROTECTED] ~]$ su - Password: [EMAIL PROTECTED] ~]# grub Probing devices to guess BIOS drives. This may take a long time. GNU GRUB version 0.97 (640K lower / 3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename.] grub root (hd0,0) root (hd0,1) Filesystem type is ext2fs, partition type 0x83 grub setup (hd0) setup (hd0) Checking if /boot/grub/stage1 exists... no Checking if /grub/stage1 exists... yes Checking if /grub/stage2 exists... yes Checking if /grub/e2fs_stage1_5 exists... yes Running embed /grub/e2fs_stage1_5 (hd0)... 23 sectors are embedded. succeeded Running install /grub/stage1 (hd0) (hd0)1+23 p (hd0,0)/grub/stage2 /grub/grub.conf... succeeded Done. grub quit quit [EMAIL PROTECTED] ~]# NB: Tabbing didn't work when I tried it. But it has in the past. I'm not sure if that's down to the terminal on Fedora 9, or something else. -- Regards Bill; Fedora 9, Gnome 2.22.2 Evo.2.22.2, Emacs 22.2.1 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: FC9 boot hangs with encrypted filesystems
Tim Largy wrote: I put an encrypted f/s on an FC9 install, and the boot hung waiting for the password. Not good, so I marked it noauto in fstab, but it still hung. So I put it in automount and not in fstab and it still hangs, and I finally took it out of everywhere and the boot process can still see it. I want the system to boot without the filesystem, and mount it only on demand, but by simply existing it seems to be found and validated at boot time. Can someone tell me where the boot process is finding the f/s? It's not used for normal operations, only for special operations by people with the password. Is there a way to keep the boot from asking about it until used? man crypttab Thanks, but I don't see quite how to select on demand in that man page. If I comment out the entry it isn't requested at boot, but it isn't requested when I try to mount it, I get a must specify filesystem type prompt. Anybody figure out how to do this yet? I also have an encrypted volume that I want on demand rather than activated at boot. Commenting out the entry in /etc/crypttab and changing the fstab mount option to noauto doesn't do the trick. I'm also still hoping for an answeer. Or suggestion. I was told in a chat that it wasn't a bug because it was intended to work that way. Guess I can't report it as a bug. :-( Kind of make LUKS impractical for anything but dedicated personal use, and I was hoping to allow on demand mounting of proprietary data. -- Bill Davidsen [EMAIL PROTECTED] We have more to fear from the bungling of the incompetent than from the machinations of the wicked. - from Slashdot -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
problem with FC9 login screen
My login screen for Fedora 9 has only suspend, restart and shutdown buttons, plus the list of users. There's what looks like a panel bar at the bottom of the screen with nothing in it. I can login normally to the gnome desktop. How do I change the session to KDE from the login screen? (I specified including KDE during the installation.) Is there a widget or file where I can specify a default user (the one highlighted on the login screen menu)? Thanks for the help! --Jerry -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Getting open source project into Fedora
I am working with the Akelos project, a PHP port of Ruby on Rails. I would like to find out how we might get this LGPL project included with Fedora. I am also interested in learning how one might go about finding a corporate sponsor for it. -- Thy kingdom come. Thy will be done on Earth as it is in Heaven. Tulkoon sinun valtakuntasi. Tapahtukoon sinun tahtosi, mys maan pll niin kuin taivaassa. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Fedora 9 /dev/rtc missing
[EMAIL PROTECTED] wrote: It sounds as if your hardware clock is simply not usable by the kernel drivers. However, if you boot and get the system starting at nearly the right time, then it's likely that your hardware is being read. In /var/log/messages, when you boot do the messages have the right time? If so some source of the clock was found. -- Bill Davidsen [EMAIL PROTECTED] We have more to fear from the bungling of the incompetent than from the machinations of the wicked. - from Slashdot -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Well it seems like the time is incorrect in /var/log/messages as well. Is there a particular mod I should be looking for in the results of an lsmod? Is there a particular module that I can insert to get it working? I would expect support for the CMOS clock to be loaded automatically, and I can't guess why you would need anything else. There might be a boot option, but it certainly doesn't come to mind. Looking at several working systems, I am trying to guess which modules might be related. There is virtually nothing in common between a Q6600 and Celeron system with SIS chipset, so I doubt it's a module. I know that this machine had a working clock at some point when I was on Fedora 8, I can not recall with absolute certainty if this issue appeared in 8 or only after I installed 9. Here are some ideas in order of how likely I think they are: 1 - find out how to tell XP to use UCT on the hardware clock and reset it to UTC. This will also fix problems the next time our bonehead congress proves it doesn't understand time and resets DST. 2 - in GNOME go to system-administration-datetime, and on the time zone tab check that you have the TZ set and the hardware clock checked (or not, if you disregard my 1st idea). 3 - use the acpi= boot options, you can look up which ones seem possible as solutions. It could be an ACPI problem, there were a lot of changes in that area with FC9 kernels. Actually with recent kernels, I think they're in FC8 current as well. 4 - disable apic from the boot options line. Last resort, I have no idea why this might help, but I saw it in a posting elsewhere. -- Bill Davidsen [EMAIL PROTECTED] We have more to fear from the bungling of the incompetent than from the machinations of the wicked. - from Slashdot -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
scrambled image with xine
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bonjour, I installed xine on my laptop and if I want to whatch a dvd the image is completely unreadable: scrambled as if the dvd was crypted. No problem with vlc, no problem with totem-xine. totem, installed by default, doesn't work, whatever the install I made up to now. Anybody has any ideas? Thanks - -- François Patte UFR de mathématiques et informatique Université Paris Descartes 45, rue des Saints Pères F-75270 Paris Cedex 06 Tél. +33 (0)1 44 55 35 61 http://www.math-info.univ-paris5.fr/~patte -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFIY67QdE6C2dhV2JURAgeCAJ9LcwUpPppXmHtfVVZetqlwJXDmPACfeLBV XjxAfGTcXWLIhBdrLHK0y2o= =UwUf -END PGP SIGNATURE- -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: grubby: unable to open /boot/boot.b: No such file or directory
On Thu, 26 Jun 2008 12:03:50 +0200, Thomas Rabaix wrote: Hello, I just update my Fedora 8 with yum, and I don't want to reboot it as I get an error during the update. I cannot easily rescue it in case of problem as the host is located at a remote location (datacenter). so the /boot/boot.b is missing, the bootloader is lilo. LILO is not included in the Fedora repositories. Fedora uses GRUB for a long time. How can I regenerate this file ? By reinstalling LILO. Manually or as a package. Installing: kernel # [ 20/144] grubby: unable to open /boot/boot.b: No such file or directory The bootloader is Lilo : # dd if=/dev/sda obs=512 count=1 2/dev/null|grep LILO Binary File ... matches That test is invalid. $ sudo dd if=/dev/sda obs=512 count=1 2/dev/null|strings lbaLILO ZRrI D|f1 GRUB Geom Hard Disk Read Error -- Fedora release 8 (Werewolf) - Linux 2.6.25.6-27.fc8 loadavg: 1.37 1.15 1.09 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: [OT] Are security updates necessary?
Mike Bird wrote: On Sun June 15 2008 17:50:16 Arthur Pemberton wrote: On Sun, Jun 15, 2008 at 7:09 PM, Bill Davidsen [EMAIL PROTECTED] wrote: The problem is that use your machine for most people is not limited to playing solitaire on a machine without network connections. Buy a router? Use the software firewall? Neither protects against security holes in web browsers, mail clients, word processors, etc. Any web page you visit, any email you read, any image you view, any document you read ... could contain malformed data trying to exploit buffer overflow or other security bugs. In a review of OpenSuSE 11 one reviewer praised using the 3.5 KDE parts to provide functionality. I have the impression from what he said that their KDE is mostly 4 with a helping of 3.5 to provide working versions of some things which aren't properly functional in 4.x. Either they're more trusting than Fedora, or less concerned with being bleeding edge vs. functional, or just less influenced by KDE folks to get the new stuff out there. As for security, CentOS-5.2 (and the underlying RHEL) use KDE 3.5, so I assume that there is a security enhanced 3.5 available for Fedora if the decision were made on technical capability, rather than some goal to have the latest stuff, be it functional for users or not. So either you are saying that the KDE in RHEL is insecure, or that Fedora chose not to provide the previous functionality for users, even though you have an enterprise 3.5 in-house. -- Bill Davidsen [EMAIL PROTECTED] We have more to fear from the bungling of the incompetent than from the machinations of the wicked. - from Slashdot -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Getting open source project into Fedora
Alan Lake wrote: I am working with the Akelos http://www.akelos.org/ project, a PHP port of Ruby on Rails. I would like to find out how we might get this LGPL project included with Fedora. I am also interested in learning how one might go about finding a corporate sponsor for it. You don't need corporate sponsors to get any free and open source project into Fedora. Just follow http://fedoraproject.org/wiki/PackageMaintainers/Join Rahul -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: grubby: unable to open /boot/boot.b: No such file or directory
Hello, Thanks for your reply. It is what I have. I have to mention that I updgrade from a FC4 to F8. More over I have a file called 'boot.0800', can it be the boot.b file (backup) ? # dd if=/dev/sda obs=512 count=1 2/dev/null|strings LILO 7H9| LILOu)^h `UUfP fPYX @](: On Thu, Jun 26, 2008 at 5:06 PM, Michael Schwendt [EMAIL PROTECTED] wrote: On Thu, 26 Jun 2008 12:03:50 +0200, Thomas Rabaix wrote: Hello, I just update my Fedora 8 with yum, and I don't want to reboot it as I get an error during the update. I cannot easily rescue it in case of problem as the host is located at a remote location (datacenter). so the /boot/boot.b is missing, the bootloader is lilo. LILO is not included in the Fedora repositories. Fedora uses GRUB for a long time. How can I regenerate this file ? By reinstalling LILO. Manually or as a package. Installing: kernel # [ 20/144] grubby: unable to open /boot/boot.b: No such file or directory The bootloader is Lilo : # dd if=/dev/sda obs=512 count=1 2/dev/null|grep LILO Binary File ... matches That test is invalid. $ sudo dd if=/dev/sda obs=512 count=1 2/dev/null|strings lbaLILO ZRrI D|f1 GRUB Geom Hard Disk Read Error -- Fedora release 8 (Werewolf) - Linux 2.6.25.6-27.fc8 loadavg: 1.37 1.15 1.09 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list -- Thomas Rabaix -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Periodic Fedora 9 system hangs with jumpy mouse
Okay, so Xorg ran away last night while the system was totally idle and not being used at all. So I guess the scrollbar theory could be suspect. There was a screensaver running (just the cosmos image slideshow, no moving graphics); and I left firefox up, which had a gmail window running so it would I supposed occasionally refresh itself. But otherwise it should have been a completely idle unused system. My big question at this point is how is this locking up so hard? When you can't even kill -9 the process, what is going on. This has to be more than just Xorg (a user-space program), the kernel has to be involved here too. Is it a spinlock deadlock, or something like that? So how can you figure out what all those cpu cycles are being used for? Isn't there a way to probe into the kernel to see what it's doing? Unfortunately the wchan is 0, which is how I thought you could tell this sort of thing. Is there some place under /proc or some other method to peek around? Anyway, concerning the Xorg driver module, this is a brand new install of F9 (not an upgrade). All the software is part of the base F9 repo; nothing 3rd party was added. Everything was auto-detected. The video card shows up in a system scan as: ATI Technologies Inc RV350 AS [Radeon 9550] Chipset: ATI Radeon 9600 AS (AGP) (ChipID = 0x4153) The vendor's name on the box was: Diamond ATI Stealth X1050 (AGP 256MB) The Xorg driver chosen for this was: /usr/lib/xorg/modules/drivers//radeon_drv.so My screen is 1440 x 900 x 24, monitor is DELL E198WFP just for fun and practice of card swapping, do you have a different graphics card to try with different drivers? The only other card I had was a PCI card that only had VGA output, no DVI. And F9 didn't seem to know how to detect the monitor correctly and was overdriving the frequency (although it worked under F7). do you boot level 3 or level 5. boot level 3, if cpu usage is low, then 'startx' to see what happens. mono verses color. Yes, I can try that. So far it's just been boot to runlevel 5. from level 3 boot, remove driver, then use 'yum install' to bring your driver back in and reboot to load it. driver may be fried. The driver is coming from the package xorg-x11-drv-ati-6.8.0-14.fc9.i386 I did an rpm verify on it, rpm -V -v xorg-x11-drv-ati-6.8.0-14.fc9.i386 and that said all the files were intact and correct. kde, gnome? have you tried any minimal desktops? something may, tho i would doubt, be different in how you bring up x. Haven't tried other desktops other than Gnome, but I have disabled all the fancy effects, etc. The system runs perfectly fine; until that magic moment when the Xorg process runs away. Or is that the kernel that is running away? I wish I knew how to debug the kernel better; because it just doesn't appear to be a user-space problem. -- Deron Meranda -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Double checking grub-install ??
William Case wrote: I was trying to avoid wasting peoples time with a long description. it can clear things up sometimes as they are becoming not. [excuse order of comments. trying to reply as you have things written] When I first boot I get the Fedora grub splash screen/menu twice -- as you mention below, twice, meaning that it appears, you select or let it time out and boot, then it appears again, you select or let it time out and boot to system. if so, then it sounds like you may have it installed on both sda and sdb. possible, sda calls it up on sdb. [i am only trying to be sure we are of full understand of this matter] anyway, in my last post to you, i mentioned that from grub command you presented, you where wanting to install to /dev/sdb. i stated that that is ok, if bios was set to boot /dev/sdb, else if set to /dev/sda, bios would not see loader on /dev/sdb, unless maybe if /dev/sdb was set as active instead of /dev/sda. not sure, as i have never tried booting that way. About four weeks ago my commercial boot loader was blown away by the so, this is what is calling grub on /dev/sdb. you do not need it and may be better off if you just use grub on /dev/sda to select oos or fedora. unless you have something that grub can not load. if not, you can/should either follow tim's grub install using 'grub enter' or use single command as you posted. either way, you can/should change install to /dev/sda and make changes to 'grub.conf' and include oos. m2c. ymmv. -- tc,hago. g . in a free world without fences, who needs gates. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Any hope of KDE 3.5 in F10? I want it too !
Mike Bird wrote: On Fri June 20 2008 18:50:45 David Boles wrote: But you do know that you new distro will switch to KDE 4.0 soon too right? Your definition of soon must be different than mine: Fedora will support KDE 3.5 until approximately December 2008. Kubuntu will support KDE 3.5 until approximately October 2009. Debian will support KDE 3.5 until maybe 2011 or 2012. CentOS-5.2 has 3.5 KDE, I presume the underlying RHEL will be around for the usual years. I'm expecting KDE 4.2 or KDE 4.3 to be suitable for prime time. I have the impression that for some users it will never be suitable, because it is not an issue of bugs in the code, or missing features which will be added, but a change in the underlying philosophy of how users should use the desktop. And if the deliberate change doesn't suit your preferred operation, you're in the market for either KDElegacy.org or a totally new WM and utils. They should arrive in Fedora in May 2009 and November 2009. That leaves Fedora without support for a prime time KDE for several months. There's no such gap with Debian or Kubuntu. Other distros are also shipping KDE 3.5 alongside KDE 4.x but I haven't analyzed their timetables. --Mike Bird -- Bill Davidsen [EMAIL PROTECTED] We have more to fear from the bungling of the incompetent than from the machinations of the wicked. - from Slashdot -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Need help with Toshiba Tecra SD reader
I cannot access the SD reader of a Toshiba Tecra. I already tested several SD cards. The SD cards work fine under Windows XP and Mac X, but Fedora 9 does not recognize the reader/drive? Does anyone know how to install the driver for the SD reader? Thanks a lot. Luis -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
F8, currently offered grub update. Safe?
With a 400GB sata drive on a sata_sil pci card and initrd loaded driver module in the mix, which some of the grub stuff insists is /dev/sda when its actually /dev/sdc on this system, is this so-called update safe, or will I be reaching for install dvd's I don't have yet other than Ubuntu-8.04, when I find it won't reboot cuz the bios does NOT see that drive, and it therefore is now non-bootable. So is this update safe for me? -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) Gentlemen, I want you to know that I am not always right, but I am never wrong. -Samuel Goldwyn -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Any hope of KDE 3.5 in F10? I want it too !
David Boles wrote: Mike Bird wrote: On Sat June 21 2008 16:11:26 Kevin Kofler wrote: When KDE 4.0 was released in January a consensus was reached that major releases of KDE 4 should occur at six month intervals. Although there has been some discussion of four month cycles, the consensus for six month cycles still seems to be firm: KDE release -in-Fedora 4.0 Jan '08 F9 May '08 4.1 Jul '08 F10 Nov '08 4.2 Jan '09 F11 May '09 4.3 Jul '09 F12 Nov '09 Hey Mike. Have you ever seen software released when it was scheduled to be released? ;-) Not games (especially games), not drivers, not anything. Except Linux distro releases. And those slip too. Some slip so they can fix bugs, some ship bugs so they can be on time. :-( There's a reason why Linux kernels sometimes get to -rc7, I am truly sorry that you are disappointed with KDE 4.0. Really. But there it is. deal with it as it is and wait for improvements. Make suggestions, in the correct places, and go on. Did you miss the subject? The suggestion is that KDE 3.5 be included, as it is in RHEL, SuSE-11, Kubuntu, etc. I don't recall if you replied to my basic questions about this situation. Did you look first? Live-CD try first? Or just jump in? If you skipped one, or two, or both one and two, you should be kicking your own butt for your 'problems' and not Fedora's and the KDE team. IMO. Does it matter? If he tried the pre-releases, alpha and beta, and said KDE doesn't work, would the team have stayed with KDE 3.5? No, because the decision wasn't made on the basis of functionality, and AFAIK the KDE developers view of how the user interface should work has changed, and it will NEVER be improved because they want it to work differently. -- Bill Davidsen [EMAIL PROTECTED] We have more to fear from the bungling of the incompetent than from the machinations of the wicked. - from Slashdot -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: grubby: unable to open /boot/boot.b: No such file or directory
On Thu, 26 Jun 2008 17:15:10 +0200, Thomas Rabaix wrote: Hello, Thanks for your reply. It is what I have. I have to mention that I updgrade from a FC4 to F8. Doesn't make a difference, because FC4 also used GRUB. More over I have a file called 'boot.0800', can it be the boot.b file (backup) ? No, afair it is the backup copy of the boot sector before LILO was installed into it. The backups have different names for (E)IDE and SCSI. Read the manual page. It's explained there. /boot/boot.b is part of LILO. If you lost it, reinstall LILO. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: grubby: unable to open /boot/boot.b: No such file or directory
On Thu, 26 Jun 2008 08:16:58 -0700, Craig White wrote: watching this thread with interest. I have several Dell Optiplex 320's that will not boot with grub but will boot with lilo and so I have lilo installed on them. Is this problem known upstream? Unfortunately though, kernel updates do produce the error above (unable to open /boot/boot.b) generated by grubby. Is there any way around getting grubby to re-run lilo to execute an update when new kernels are installed? With LILO, no. LILO must be rewritten with every change in lilo.conf. GRUB, on the contrary, must not be rewritten after modifying grub.conf, because it can read the ext2/ext3 fs directly to load its config file. If you're interested in where grubby is executed, take a look at /sbin/new-kernel-pkg which is called by the kernel package scriptlets. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Any hope of KDE 3.5 in F10? I want it too !
On Thursday 26 June 2008, Bill Davidsen wrote: David Boles wrote: Arthur Pemberton wrote: On Sat, Jun 21, 2008 at 4:51 PM, Patrick O'Callaghan [EMAIL PROTECTED] wrote: Well the main idea behind PA is to eradicate that problem since it will be a super set And, as I said, I have no problems with Pulseaudio. Why? Well I have a desktop with 'normal' hardware. I don't have anything fancy. And, for me Fedora works 'out of the box'. Actually I normally (currently) run rawhide and I only have the 'development breakage', to be expected, from time to time. I won't name, on the Fedora list, the other Linux distros that I have installed and that run with no, or minor, problems. But there are nine of them. A, Gee. We still have the 1st amendment here. So? Am I just lucky? Or do I just have compatible hardware? Or do I just not try to do strange things'? I can't say. Have you ever tried to use a microphone or line input for recording or telephony? I have four system, all of which worked pre-PA, none of which work with PA, all of which work with PA removed, for both ALSA and simulated OSS applications. So if trying to get sound into the computer is strange things, then I guess I do them. As do I, David. And PA wrecked it all until I had gotten out the knife and removed as much of it as I could. This is not to say that something like PA isn't potentially useful, but to ship a completely broken PA, and then the only help offered was the advice to remove it, seems to be highly counter-productive to getting it, or something like it, working. However, here on this system PA was a solution (if it worked, I'm dubious) in search of a problem I didn't have. -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) Who messed with my anti-paranoia shot? -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: grubby: unable to open /boot/boot.b: No such file or directory
On Thu, 26 Jun 2008 18:08:20 +0200, Michael Schwendt wrote: On Thu, 26 Jun 2008 08:16:58 -0700, Craig White wrote: watching this thread with interest. I have several Dell Optiplex 320's that will not boot with grub but will boot with lilo and so I have lilo installed on them. Is this problem known upstream? Unfortunately though, kernel updates do produce the error above (unable to open /boot/boot.b) generated by grubby. Is there any way around getting grubby to re-run lilo to execute an update when new kernels are installed? With LILO, no. LILO must be rewritten with every change in lilo.conf. GRUB, on the contrary, must not be rewritten after modifying grub.conf, typo: must not = need not because it can read the ext2/ext3 fs directly to load its config file. If you're interested in where grubby is executed, take a look at /sbin/new-kernel-pkg which is called by the kernel package scriptlets. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: grubby: unable to open /boot/boot.b: No such file or directory
On Thu, 2008-06-26 at 18:08 +0200, Michael Schwendt wrote: On Thu, 26 Jun 2008 08:16:58 -0700, Craig White wrote: watching this thread with interest. I have several Dell Optiplex 320's that will not boot with grub but will boot with lilo and so I have lilo installed on them. Is this problem known upstream? very much so https://bugzilla.redhat.com/show_bug.cgi?id=379201 https://bugzilla.redhat.com/show_bug.cgi?id=219715 Unfortunately though, kernel updates do produce the error above (unable to open /boot/boot.b) generated by grubby. Is there any way around getting grubby to re-run lilo to execute an update when new kernels are installed? With LILO, no. LILO must be rewritten with every change in lilo.conf. GRUB, on the contrary, must not be rewritten after modifying grub.conf, because it can read the ext2/ext3 fs directly to load its config file. If you're interested in where grubby is executed, take a look at /sbin/new-kernel-pkg which is called by the kernel package scriptlets. been there...never could figure out what to change as noted here... https://bugzilla.redhat.com/show_bug.cgi?id=219715#c18 Craig -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: F9/KDE4: Can't access screen resolution changes after software install
Don Levey wrote: Based upon a mention in Linux Journal, I installed the Penumbra: Black Plague demo yesterday on my laptop: ... What is particularly odd is that when logging in via KDE it *starts up* in the correct resolution, but eventually changes. What happened to my machine, and how do I get it back? It's probably just a configuration change in one file, but I don't know which one. Where did you get Penumbra from? I'd suggest asking them what the installer did you your machine. -- Rex -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: I am having some problem in the installation of FC9
Parshwa Murdia wrote: hi all, i am downloaded the from the following link the image for the fedora core 9, link is: http://ftp.iitm.ac.in/fedora/releases/9/Fedora/i386/iso/ and after saving it in my pc, i copy pasted it to the pen-drive which i attached and mounted, now how to make it run or install the same so that the system would be upgraded from fc5 to fc9. please let me know as soon as possible. regards, parshwa murdia I think you have to create a file system on the pen drive. See this link for how to do that. http://fedoraproject.org/wiki/Docs/Beats/Live Then it seems you reboot with the pen drive as the boot device and the installer takes it from there. I haven't actually done this, perhaps someone else will be able to give you better advice. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: What is the matter with fedora 9?
Craig White wrote: First of all, Tom didn't qualify his comments on NetworkManager which is very useful in some instances and apparently is installed as the default networking daemon if you install from Live CD. His suggestion to turn it off: - lacked any suggestion that you need to turn on the regular 'network' daemon in its place instead Did you read the post you copied? He suggested that you turn NetworkMangler off, and the traditional (functional) network daemon in the very next line! It's the line between the disabling of NM and the line that says reboot if you are having problems finding it. - lacked any consideration of wireless or dhcpcd client needs Which work as they did in FC8 (and all the way back to FC4). With respect your your efforts making Fedora 9 work to your expectations, you've sort of proven your own problems to yourself but contributed nothing to fixing any issues that may exist. He provided a three line fix for the NM problem, while I knew that already I'm sure some people didn't. One of the great things about this list is that if you can figure out how to ask the questions, you can get your problems solved. Craig On Wed, 2008-06-25 at 07:02 +0800, Robert M. Bernabe wrote: newbie here... trying to make linux work as a gui interface with postgresql... found fc9 unworkable too as compared to fc8our own opinion is that fc9 has implemented some features we don't understand. e.eg. off the bat, after installation...the samba services status appear unknown in the services window...I think so do other services (somebody posted a reason for it I think... but it involves several 'classic' prompt windows edits...) so for now we are sticking to fc8...thankful for all the efforts plugged into the fedora project in general... but just wishing we understood the thinking behind the changes in fc9... - Original Message - From: Tom Horsley [EMAIL PROTECTED] To: fedora-list@redhat.com Sent: Wednesday, June 25, 2008 5:37 AM Subject: Re: What is the matter with fedora 9? On Tue, 24 Jun 2008 17:53:37 +0200 fedora [EMAIL PROTECTED] wrote: it introduced a NetworkManager which prohibits networking. Don't know about the other problems, but for me this makes networking function just like always: chkconfig --level 2345 NetworkManager off chkconfig --level 2345 network on reboot That turns off NetworkManager and goes back to the old nasty stick-in-the-mud networking that actually works :-). NetworkManager may be good for folks with laptops who flit about from one hotspot to another, but it is hopeless for us more ordinary network users who have static IPs or even DHCP networks initialized at boot time and unchanging after that. It should never have arbitrarily been made the default. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list -- Bill Davidsen [EMAIL PROTECTED] We have more to fear from the bungling of the incompetent than from the machinations of the wicked. - from Slashdot -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: grubby: unable to open /boot/boot.b: No such file or directory
On Thu, 26 Jun 2008 09:27:46 -0700, Craig White wrote: On Thu, 2008-06-26 at 18:08 +0200, Michael Schwendt wrote: On Thu, 26 Jun 2008 08:16:58 -0700, Craig White wrote: watching this thread with interest. I have several Dell Optiplex 320's that will not boot with grub but will boot with lilo and so I have lilo installed on them. Is this problem known upstream? very much so https://bugzilla.redhat.com/show_bug.cgi?id=379201 https://bugzilla.redhat.com/show_bug.cgi?id=219715 Those are about grub and the kernel. If you think grubby suffers from a bug when updating LILO installations, grubby is part of the mkinitrd package. Unfortunately though, kernel updates do produce the error above (unable to open /boot/boot.b) generated by grubby. Is there any way around getting grubby to re-run lilo to execute an update when new kernels are installed? With LILO, no. LILO must be rewritten with every change in lilo.conf. GRUB, on the contrary, must not be rewritten after modifying grub.conf, because it can read the ext2/ext3 fs directly to load its config file. If you're interested in where grubby is executed, take a look at /sbin/new-kernel-pkg which is called by the kernel package scriptlets. been there...never could figure out what to change as noted here... https://bugzilla.redhat.com/show_bug.cgi?id=219715#c18 Well, if you have reason to believe that grubby does something wrong, find out what it does wrong. Run it manually, it has a man page, too. And /boot/boot.b must exist when it is specified in lilo.conf. Do you say that grubby deletes that file by accident? And if you're really fed up with grubby, you could modify new-kernel-pkg to execute your own lilo-update script/program instead of grubby. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: What is the matter with fedora 9?
fedora wrote: Hi every What is the matter with fedora 9? it introduced a NetworkManager which prohibits networking. NetworkMangler has been around since FC6 (at least), by making it the default it became impossible to ignore. It does the right thing in cases where you have one hardwire or wireless connection which can see only one AP. For all other cases wait for the human readable documentation which will be here... or maybe not, since it was coming with FC7, 8, and 9. programs are acessible only as root user: xsane just does nothing as non-root user. More likely to be a device permission problem, in my experience. Blame hal or SElinux, it's not that hard to fix. openoffice blocks its drop-downs in the main menu for 20 seconds, if you are not root. if you are root, everything is as good/as bad as with fedora 8, thanks very much. Other people have said that's because when they upgraded they left stuff in various dot directories. Doesn't happen in clean installs, at least that I've noticed. openldap breaks down every now and then, and stays with a corrupt sleepycat database, which is not revoverable. I didn't see your bugzilla on that. could the relevant persons please provide an update to fedora 9 as soon as possible? thanks very much. -- Bill Davidsen [EMAIL PROTECTED] We have more to fear from the bungling of the incompetent than from the machinations of the wicked. - from Slashdot -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
F9/KDE4: Can't access screen resolution changes after software install
Based upon a mention in Linux Journal, I installed the Penumbra: Black Plague demo yesterday on my laptop: Acer TravelMate 4202WLMi Inten Centrino Duo 1.66GHz 1 GB RAM Intel GMA950, 1280x800 Fedora 9 x86 (hpl.log attached) KDE4 At the end of the installation, there were no errors, though it seemed to restart X on my machine. After logging in again, I tried starting the demo just to see that it was working. When I exited it, I found that my desktop had been changed to 800x600. I had hoped that restarting X would reset my settings, but that didn't help. Nor did changing the settings in the game itself. I am unable to reconfigure my desktop at all. While the correct (1280x800) resolution is visible as a selection in System Settings, the Apply/Save button is not enabled. This appears to be a specific problem in KDE; I can restart X and use another environment (Gnome) at the correct resolution. Likewise ICEwm; in ICEwm I can even start and run the game without issue and return to my proper desktop size. What is particularly odd is that when logging in via KDE it *starts up* in the correct resolution, but eventually changes. What happened to my machine, and how do I get it back? It's probably just a configuration change in one file, but I don't know which one. Thanks in advance, -Don -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Adding an ATA to a F9 installed on a SATA drive
-- Original message -- From: dexter [EMAIL PROTECTED] On Thu June 26 2008 06:20:23 [EMAIL PROTECTED] wrote: Hi, I have a two 500 Gb ATA drives that I'd like to add to F9. This computer has the onboard socket for ATA, but F9 is installed on a SATA drive. How do I go about formatting and adding these drives? I'd appreciate a good howto tutorial on the web or step by step instructions here. I've been using Fedora for years, but never had to do this. I'd suggest using gparted its a simple point and click operation and can do resizing of ext3 ntfs and much much more ... ...dex -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list How do I locate the drive? My SATA drive is sda. I was expecting the ATA to be hda, but I can't find that. Thanks, EJ -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Where are the Fedora 9 SHA1SUMs?
Kam Leo wrote: On Tue, Jun 24, 2008 at 7:12 AM, Dave Cook [EMAIL PROTECTED] wrote: Hello Fedora Gurus, I've just downloaded Fedora 9 (DVD, i386) and found its sha1sum BUT I can't locate the target SHA1SUM file on the fedoraproject.org site. It is referred to there so it must be there but I can't find it Any comments? Dave Too many ways to obtain the ISO so they winged it: http://fedoraproject.org/en/verify Short version -- Obtain ISO via torrent (also Jigdo) no need to check. Trust, but verify. -R. Reagan HTTP and FTP get SHA1SUM from same directory as .iso. -- Bill Davidsen [EMAIL PROTECTED] We have more to fear from the bungling of the incompetent than from the machinations of the wicked. - from Slashdot -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: I am having some problem in the installation of FC9
On Thu, 2008-06-26 at 10:56 +0530, Parshwa Murdia wrote: hi all, i am downloaded the from the following link the image for the fedora core 9, link is: http://ftp.iitm.ac.in/fedora/releases/9/Fedora/i386/iso/ and after saving it in my pc, i copy pasted it to the pen-drive which i attached and mounted, now how to make it run or install the same so that the system would be upgraded from fc5 to fc9. Copy-and-paste isn't enough. See: http://docs.fedoraproject.org/install-guide/f9/en_US/sn-making-media.html#id543953 Note that the section headings on this page are wrong (the heading Creating Bootable USB Media with Windows actually describes the Linux procedure. poc -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: What is the matter with fedora 9?
Bill Davidsen wrote: fedora wrote: Hi every What is the matter with fedora 9? it introduced a NetworkManager which prohibits networking. NetworkMangler has been around since FC6 (at least), by making it the default it became impossible to ignore. It does the right thing in cases where you have one hardwire or wireless connection which can see only one AP. For all other cases wait for the human readable documentation which will be here... or maybe not, since it was coming with FC7, 8, and 9. After about a dozen installs of Fedora 9 I cannot agree with you on that. On every system save one there is only one network connection, in each of those cases it's been /dev/eth0 and NM would not enable the connection by default. Maybe there's documentation on the way that will make NM a breeze to configure but until that time it's out the window. I disable the NetworkManager service and enable the network service during kickstart installs. All my systems have a statically leased DHCP address and it works just fine. Bottom line for me: NM breaks far more than it fixes. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
different mounts leads to different permissions/acl?
Hoi every we use a cvs environment, where the repository is mounted from the main cvs-server into each participants work-space. before fedora 9, we used cifs mounts exclusively. with fedora 9, we started using sshfs. this afternoon, i had the repository mounted using sshfs. i had a failure when committing a cvs module. cvs said: ... Checking in module/779930879.htm; /home/cvs/r/repository/module/779930879.htm,v -- 779930879.htm new revision: 1.2; previous revision: 1.1 cvs [commit aborted]: cannot rename file /home/cvs/r/repository/module/,779930879.htm, to /home/cvs/r/repository/module/779930879.htm,v: Operation not permitted [EMAIL PROTECTED] ~/work]$ i unmounted the repository and remounted it using cifs, whereupon the commit worked fine. i then wanted to see, what the difference is in file permissions between the two mount versions, and to my surprise, found none: user:group were the same with both mounts, also the file permissions were the same. then i tried to do manually the move cvs had complained about and got the following: repository cifs mounted: [EMAIL PROTECTED] ~/work]$ mv /home/cvs/r/repository/module/,779930879.htm /home/cvs/r/repository/module/779930879.htm,v mv: try to overwrite `/home/cvs/r/repository/module/779930879.htm,v', overriding mode 0544 (r-xr--r--)? y [EMAIL PROTECTED] ~/work]$ repository sshfs mounted: [EMAIL PROTECTED] ~]$ mv /home/cvs/r/repository/module/,779930879.htm /home/cvs/r/repository/module/779930879.htm,v mv: cannot move `/home/cvs/r/repository/module/,779930879.htm' to `/home/cvs/r/repository/module/779930879.htm,v': Operation not permitted [EMAIL PROTECTED] ~]$ i made sure, that the file i wanted to move had exactly the same permissions as when the repository was cifs mounted: it had the same permissions (r-xr--r--). for the cifs mount we use the standard fedora 9 samba installation for [home] shares: [homes] comment = Home Directories browseable = no writable = yes ; valid users = %S ; valid users = MYDOMAIN\%S as far as i can see, the difference is minimal, but it makes cvs commit fail, when the repository is sshfs mounted. can somebody explain, what the difference is, and how i could correct/work-around it? thanks in advance. suomi -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
intel3945 WLAN and Siemens ADSL Modem
Hello Friends I have one 'Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)' card (quoted from `lspci`) in my Lenovo laptop. And my Siemens ADSL modem has a Wireless network facility. But, though I set the network up according to the modem manual, I am not being able to get the wlan0 up. 'service network start' is giving me a message like this: Bringing up interface wlan0: Error for wireless request Set Mode (8B06) : SET failed on device wlan0 ; Invalid argument. SIOCSIFFLAGS: No such device Determining IP information for wlan0...SIOCSIFFLAGS: No such device SIOCSIFFLAGS: No such device failed. And 'dmesg' is telling: ACPI: PCI Interrupt :03:00.0[A] - GSI 17 (level, low) - IRQ 17 iwl3945: Radio disabled by HW RF Kill switch My question is, is some problem there in the wlan driver or I am making some stupid mistake in setting up the wireless? See, I am absolutely ignorant about both wireless and network, and so, please make your reply as less cryptic as possible. -- das ddts.randomink.org -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: F9/KDE4: Can't access screen resolution changes after software install
Rex Dieter wrote: Don Levey wrote: Based upon a mention in Linux Journal, I installed the Penumbra: Black Plague demo yesterday on my laptop: ... What is particularly odd is that when logging in via KDE it *starts up* in the correct resolution, but eventually changes. What happened to my machine, and how do I get it back? It's probably just a configuration change in one file, but I don't know which one. Where did you get Penumbra from? I'd suggest asking them what the installer did you your machine. -- Rex I got it from the publisher (http://www.penumbrablackplague.com/site/index.php). I've also posted on their forum, but thought that this might also be a more general question on how to (mis)configure KDE4. -Don -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: What is the matter with fedora 9?
Stephen Berg (Contractor) wrote: Bill Davidsen wrote: fedora wrote: Hi every What is the matter with fedora 9? it introduced a NetworkManager which prohibits networking. NetworkMangler has been around since FC6 (at least), by making it the default it became impossible to ignore. It does the right thing in cases where you have one hardwire or wireless connection which can see only one AP. For all other cases wait for the human readable documentation which will be here... or maybe not, since it was coming with FC7, 8, and 9. After about a dozen installs of Fedora 9 I cannot agree with you on that. On every system save one there is only one network connection, in each of those cases it's been /dev/eth0 and NM would not enable the connection by default. Maybe there's documentation on the way that will make NM a breeze to configure but until that time it's out the window. I disable the NetworkManager service and enable the network service during kickstart installs. All my systems have a statically leased DHCP address and it works just fine. Bottom line for me: NM breaks far more than it fixes. People who keep home directories across installs are the ones facing the most issues with NM on F9. Its almost always a good idea to get a copy of gconf-cleaner and use it before testing out the abilities of the the new release. On F9, be sure to remove any NM references to eth0, or any other hard wired interface. gconf-editor is good for that. The new version of NM and system-config-network now work together. You MUST enable NM control, and start interface at boot, in system-config-network. If you just want to tweak the file, edit /etc/sysconfig/network-scripts/ifcfg-eth0 and make sure that the following two lines appear in there. ONBOOT=yes NM_CONTROLLED=yes Now NM will happily manage the interface. Good Luck! -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: What is the matter with fedora 9? ... Network Manager rocks !
Stephen Berg (Contractor) wrote: it introduced a NetworkManager which prohibits networking. NetworkMangler has been around since FC6 (at least), by making it the default it became impossible to ignore. It does the right thing in cases where you have one hardwire or wireless connection which can see only one AP. For all other cases wait for the human readable documentation which will be here... or maybe not, since it was coming with FC7, 8, and 9. After about a dozen installs of Fedora 9 I cannot agree with you on that. On every system save one there is only one network connection, in each of those cases it's been /dev/eth0 and NM would not enable the connection by default. Maybe there's documentation on the way that will make NM a breeze to configure but until that time it's out the window. I disable the NetworkManager service and enable the network service during kickstart installs. All my systems have a statically leased DHCP address and it works just fine. Bottom line for me: NM breaks far more than it fixes. My NM esperience is instead absolutely positive. I have tryed it since F7, but at that time I was very disappointed and turned it off, as in F8. In F9 I just wanted to give last chance and NM won. I have a very standard hardware: Realtek RTL-8139 (wired) and Intel 2200BG (wireless), perhaps this is a key ingredient. It connects virtually to everything: I tested it over wireless connections (free, wep, wpa, wpa2), and wired ones, sometimes PPP over a modem. Some connections require manual IP settings, that I have configured in NM by editing the connections: all of them work flawlessly. I have noticed only a bug (due to wpa_supplicant, namely): while connecting to a wireless network with a hidden essid, sometimes the connection attempts fail and I have to restart NM service in order to get a successful connection. After the wpa_supplicant today update, that problem is fixed and NM is a charm. The only criticism is about the documentation: is very lacking at this stage. My 2 cents. Andrea -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Adding an ATA to a F9 installed on a SATA drive
[EMAIL PROTECTED] wrote: How do I locate the drive? My SATA drive is sda. I was expecting the ATA to be hda, but I can't find that. Thanks, EJ Just about all drives are handled as SCSI drives now. I would expect the new drive to be sdb. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: What is the matter with fedora 9?
Stephen Berg (Contractor) wrote: Bill Davidsen wrote: After about a dozen installs of Fedora 9 I cannot agree with you on that. On every system save one there is only one network connection, in each of those cases it's been /dev/eth0 and NM would not enable the connection by default. Maybe there's documentation on the way that will make NM a breeze to configure but until that time it's out the window. I disable the NetworkManager service and enable the network service during kickstart installs. All my systems have a statically leased DHCP address and it works just fine. Bottom line for me: NM breaks far more than it fixes. One problem for a lot of people is that NM does not open the network connection until the user logs in. This is a problem for anything that needs a network connection before you log in. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Fedora 9 + wifi + ssh stale connections
LBS, Since F9 I have occasional ssh connections that are no longer responding. For now it only occurs whem I'm using my wireless connection (intel 3945ABG). When I use my UTP connection I have no problems. There is no problem with the wireless connection, because non ssh connections keep working. Connections that use underlying ssl (like vmware-server-console), are also experiencing the same problem. Any ideas? Kind regards. Christof -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: intel3945 WLAN and Siemens ADSL Modem
d das wrote: Hello Friends I have one 'Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)' card (quoted from `lspci`) in my Lenovo laptop. And my Siemens ADSL modem has a Wireless network facility. But, though I set the network up according to the modem manual, I am not being able to get the wlan0 up. 'service network start' is giving me a message like this: Bringing up interface wlan0: Error for wireless request Set Mode (8B06) : SET failed on device wlan0 ; Invalid argument. SIOCSIFFLAGS: No such device Determining IP information for wlan0...SIOCSIFFLAGS: No such device SIOCSIFFLAGS: No such device failed. And 'dmesg' is telling: ACPI: PCI Interrupt :03:00.0[A] - GSI 17 (level, low) - IRQ 17 iwl3945: Radio disabled by HW RF Kill switch My question is, is some problem there in the wlan driver or I am making some stupid mistake in setting up the wireless? See, I am absolutely ignorant about both wireless and network, and so, please make your reply as less cryptic as possible. From the message, it looks like the hardware switch that kills the wireless NIC is turned off. If this is a laptop, check the manual or look for a little LED with a switch next to it. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
DC7700 + intel = no gigabit speeds
Hi all, I have a multiple HP DC7700s with integrated Intel ethernet adapters. They work when the network cable is plugged into a 10/100 port on a switch. They do not work when plugged into a 10/100/1000 port. I also have DC7700s with integrated Broadcom chips (tg3 driver) and they work fine. They all worked fine before the upgrade to F9. From dmesg: e1000e: Intel(R) PRO/1000 Network Driver - 0.2.0 e1000e: Copyright (c) 1999-2007 Intel Corporation. ... eth0: (PCI Express:2.5GB/s:Width x1) 00:0f:fe:4a:68:37 eth0: Intel(R) PRO/1000 Network Connection eth0: MAC: 4, PHY: 6, PBA No: 1002ff-0ff Forcing 100 Mb operation with: ethtool -s eth0 autoneg off speed 100 duplex full makes everything work OK. Forcing 1 Gb operation results in flaky or dead connections. The auto-negotiated 1 Gb state is flaky/dead. Now... I can force 100 Mb operation as a workaround, but does anyone know what's causing this bug? http://bugzilla.redhat.com/show_bug.cgi?id=453023 http://bugzilla.kernel.org/show_bug.cgi?id=10990 - Mike -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
F9 Firefox 3 crashing hard
Anyone else seeing FF3GA crashing abruptly? I'm going to disable the few plugins I have enabled and continue working. But I haven't added any recently, and this just started today... -Chris -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Fedora 9 + wifi + ssh stale connections
I've been seeing this a fair bit as well, when running VNC tunneled over the ssh connection. It's not a stale connection issue, because it happens while lots of data is being transferred. Both VNC and the underlying ssh shell hang. I thought it might be an MTU problem, and tried dialing it down on my end, but can't control it on the other end. So far, no luck. I eventually switched to the wired connection and the problem seems to go away. This is with the iwl3945 driver. I've seen a couple of kernel oops messages as well. :-( Wayne. On Thu, 2008-06-26 at 21:26 +0200, Christof Haerens wrote: LBS, Since F9 I have occasional ssh connections that are no longer responding. For now it only occurs whem I'm using my wireless connection (intel 3945ABG). When I use my UTP connection I have no problems. There is no problem with the wireless connection, because non ssh connections keep working. Connections that use underlying ssl (like vmware-server-console), are also experiencing the same problem. Any ideas? Kind regards. Christof -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: problem with FC9 login screen
On Thu, 2008-06-26 at 07:33 -0700, Gerhard Magnus wrote: My login screen for Fedora 9 has only suspend, restart and shutdown buttons, plus the list of users. There's what looks like a panel bar at the bottom of the screen with nothing in it. I can login normally to the gnome desktop. How do I change the session to KDE from the login screen? (I specified including KDE during the installation.) Is there a widget or file where I can specify a default user (the one highlighted on the login screen menu)? Thanks for the help! --Jerry Install switchdesk , if it is not installed. It will allow you to change from Gnome to KDE. -- === Grabel's Law: 2 is not equal to 3 -- not even for large values of 2. === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Any hope of KDE 3.5 in F10? I want it too !
On Thursday 26 June 2008 16:58:56 Bill Davidsen wrote: and it will NEVER be improved because they want it to work differently. So in your opinion 'different' can't ever be better? Anne -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: What is the matter with fedora 9?
On Thu, 2008-06-26 at 14:46 -0400, Bill Davidsen wrote: fedora wrote: Hi every What is the matter with fedora 9? it introduced a NetworkManager which prohibits networking. NetworkMangler has been around since FC6 (at least), by making it the default it became impossible to ignore. It does the right thing in cases where you have one hardwire or wireless connection which can see only one AP. For all other cases wait for the human readable documentation which will be here... or maybe not, since it was coming with FC7, 8, and 9. The above is clearly not true, I use NM in environments where there are 3 or 4 APs to choose from. programs are acessible only as root user: xsane just does nothing as non-root user. More likely to be a device permission problem, in my experience. Blame hal or SElinux, it's not that hard to fix. openoffice blocks its drop-downs in the main menu for 20 seconds, if you are not root. if you are root, everything is as good/as bad as with fedora 8, thanks very much. Other people have said that's because when they upgraded they left stuff in various dot directories. Doesn't happen in clean installs, at least that I've noticed. openldap breaks down every now and then, and stays with a corrupt sleepycat database, which is not revoverable. I didn't see your bugzilla on that. could the relevant persons please provide an update to fedora 9 as soon as possible? thanks very much. -- Bill Davidsen [EMAIL PROTECTED] We have more to fear from the bungling of the incompetent than from the machinations of the wicked. - from Slashdot -- === Your own qualities will help prevent your advancement in the world. === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: intel3945 WLAN and Siemens ADSL Modem
On Fri, 27 Jun 2008, d das wrote: I have one 'Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)' card (quoted from `lspci`) in my Lenovo laptop. And my Siemens ADSL modem has a Wireless network facility. But, though I set the network up according to the modem manual, I am not being able to get the wlan0 up. 'service network start' is giving me a message like this: Bringing up interface wlan0: Error for wireless request Set Mode (8B06) : SET failed on device wlan0 ; Invalid argument. SIOCSIFFLAGS: No such device Do you have the iwl3945-firmware package installed? Michael Young -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Any hope of KDE 3.5 in F10? I want it too !
On Thu, 2008-06-26 at 21:29 +0100, AnneWilson wrote: On Thursday 26 June 2008 17:08:28 Gene Heskett wrote: As do I, David. And PA wrecked it all until I had gotten out the knife and removed as much of it as I could. This is not to say that something like PA isn't potentially useful, but to ship a completely broken PA, and then the only help offered was the advice to remove it, seems to be highly counter-productive to getting it, or something like it, working. However, here on this system PA was a solution (if it worked, I'm dubious) in search of a problem I didn't have. The funny thing is that on this system I can't get anything from the onboard sound, and I frequently get a 'falling back to pulse-audio'. So far, PA has played everything. Gene struggled with pulseaudio and skype and multiple sound cards...his situation was largely untypical (what a shock). Along with running GUI as root, building packages from source as root, Gene sometimes is the poster boy for 'What not to do in Linux' - I'd hardly give his opinions on pulseaudio a second thought. Craig -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: problem with FC9 login screen
On Thu, 2008-06-26 at 07:33 -0700, Gerhard Magnus wrote: My login screen for Fedora 9 has only suspend, restart and shutdown buttons, plus the list of users. There's what looks like a panel bar at the bottom of the screen with nothing in it. I can login normally to the gnome desktop. How do I change the session to KDE from the login screen? (I specified including KDE during the installation.) In case someone else comes across this nonsense, definitely in the not a bug but a feature! category... To access KDE from the login menu I had to click on Other in the users menu. Then the blank panel bar at the bottom of the screen fills up with such familiar options as language and sessions. Why should these be hidden in this way? I'm still trying to find the file where the login screen parameters are stored: Is there a widget or file where I can specify a default user (the one highlighted on the login screen menu)? Jerry -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: What is the matter with fedora 9?
On Thu, 2008-06-26 at 14:34 -0400, Bill Davidsen wrote: Craig White wrote: First of all, Tom didn't qualify his comments on NetworkManager which is very useful in some instances and apparently is installed as the default networking daemon if you install from Live CD. His suggestion to turn it off: - lacked any suggestion that you need to turn on the regular 'network' daemon in its place instead Did you read the post you copied? He suggested that you turn NetworkMangler off, and the traditional (functional) network daemon in the very next line! It's the line between the disabling of NM and the line that says reboot if you are having problems finding it. I missed that - thanks - appreciate the sarcasm too. - lacked any consideration of wireless or dhcpcd client needs Which work as they did in FC8 (and all the way back to FC4). actually, NM is pretty much the same in F8/F9. Clearly someone with a laptop would rather use NM. I think the issue you see is users who install from Live CD because the installer will active Network Manager by default based on assumptions made by the installer. With respect your your efforts making Fedora 9 work to your expectations, you've sort of proven your own problems to yourself but contributed nothing to fixing any issues that may exist. He provided a three line fix for the NM problem, while I knew that already I'm sure some people didn't. The thing I love about flat earth folks who disparage things like NetworkManager and PulseAudio is that they are consistently blind to the fact that there are circumstances where these are valuable tools. Craig -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: grubby: unable to open /boot/boot.b: No such file or directory
Ok, my host install FC4 with lilo, so I update to F8. I suppose the update script from Fedora keep lilo and don't use grub at all. Now how can I reinstall lilo to make boot.b appears. I have only one chance :) (remote location) I am not sure that my system will reboot properly without this file, am i right ? Thanks Thomas On Thu, Jun 26, 2008 at 8:42 PM, Michael Schwendt [EMAIL PROTECTED] wrote: On Thu, 26 Jun 2008 09:27:46 -0700, Craig White wrote: On Thu, 2008-06-26 at 18:08 +0200, Michael Schwendt wrote: On Thu, 26 Jun 2008 08:16:58 -0700, Craig White wrote: watching this thread with interest. I have several Dell Optiplex 320's that will not boot with grub but will boot with lilo and so I have lilo installed on them. Is this problem known upstream? very much so https://bugzilla.redhat.com/show_bug.cgi?id=379201 https://bugzilla.redhat.com/show_bug.cgi?id=219715 Those are about grub and the kernel. If you think grubby suffers from a bug when updating LILO installations, grubby is part of the mkinitrd package. Unfortunately though, kernel updates do produce the error above (unable to open /boot/boot.b) generated by grubby. Is there any way around getting grubby to re-run lilo to execute an update when new kernels are installed? With LILO, no. LILO must be rewritten with every change in lilo.conf. GRUB, on the contrary, must not be rewritten after modifying grub.conf, because it can read the ext2/ext3 fs directly to load its config file. If you're interested in where grubby is executed, take a look at /sbin/new-kernel-pkg which is called by the kernel package scriptlets. been there...never could figure out what to change as noted here... https://bugzilla.redhat.com/show_bug.cgi?id=219715#c18 Well, if you have reason to believe that grubby does something wrong, find out what it does wrong. Run it manually, it has a man page, too. And /boot/boot.b must exist when it is specified in lilo.conf. Do you say that grubby deletes that file by accident? And if you're really fed up with grubby, you could modify new-kernel-pkg to execute your own lilo-update script/program instead of grubby. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: F9/KDE4: Can't access screen resolution changes after software install
Don Levey wrote: Rex Dieter wrote: Don Levey wrote: Based upon a mention in Linux Journal, I installed the Penumbra: Black Plague demo yesterday on my laptop: ... What is particularly odd is that when logging in via KDE it *starts up* in the correct resolution, but eventually changes. What happened to my machine, and how do I get it back? It's probably just a configuration change in one file, but I don't know which one. Where did you get Penumbra from? I'd suggest asking them what the installer did you your machine. -- Rex I got it from the publisher (http://www.penumbrablackplague.com/site/index.php). I've also posted on their forum, but thought that this might also be a more general question on how to (mis)configure KDE4. -Don As a followup: If anyone knows how to simply revert to the default KDE configuration (deleting a config file or directory, for example) that would be useful too. -Don -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: grubby: unable to open /boot/boot.b: No such file or directory
Ok, I will do what you advice. Just to make there is no misunderstanding, I do not have any more the FC4 on the systeme but only F8 (after multiple upgrade) So grub-install will install grub into the bootloader, I need first to convert the lilo.conf settings into a grub.conf settings. I have paste and copy what it look good for me. Can you tell me if it look right (sda1 = hd0,1) ? next, how do we know reboot will work, do we have a way of testing the setup ? Thanks, Thomas # cat lilo.conf prompt timeout=50 default=2.6.25.6-27.fc8 boot=/dev/sda map=/boot/map install=/boot/boot.b lba32 append= #serial=0,9600n8 image=/boot/vmlinuz-2.6.25.6-27.fc8 label=2.6.25.6-27.fc8 read-only root=/dev/sda1 initrd=/boot/initrd-2.6.25.6-27.fc8.img image=/boot/vmlinuz-2.6.24.7-92.fc8 label=2.6.24.7-92.fc8 read-only root=/dev/sda1 initrd=/boot/initrd-2.6.24.7-92.fc8.img image=/boot/bzImage-2.6.24.5--grs-ipv4-32 label=linux read-only root=/dev/sda1 # cat grub.conf default=0 timeout=50 title 2.6.25.6-27.fc8 root (hd0,1) kernel /vmlinuz-2.6.25.6-27.fc8 ro root=/dev/sda1 initrd /initrd-2.6.25.6-27.fc8.img title=2.6.24.7-92.fc8 root (hd0,1) kernel /vmlinuz-=2.6.24.7-92.fc8 ro root=/dev/sda1 initrd /initrd-2.6.24.7-92.fc8.img title 2.6.25.6-27.fc8 root (hd0,1) kernel /bzImage-2.6.24.5--grs-ipv4-32 ro root=/dev/sda1 On Thu, Jun 26, 2008 at 11:19 PM, Craig White [EMAIL PROTECTED] wrote: Now that I see you are remote...I would suggest that you run grub-install and use that instead of lilo because lilo support was dropped. grub-install /dev/sda though if you're still booted on FC4, it might only work if you run grub-install /dev/hda (depending on whether you are using ATA or SCSI drives) Craig On Thu, 2008-06-26 at 23:02 +0200, Thomas Rabaix wrote: Ok, my host install FC4 with lilo, so I update to F8. I suppose the update script from Fedora keep lilo and don't use grub at all. Now how can I reinstall lilo to make boot.b appears. I have only one chance :) (remote location) I am not sure that my system will reboot properly without this file, am i right ? Thanks Thomas On Thu, Jun 26, 2008 at 8:42 PM, Michael Schwendt [EMAIL PROTECTED] wrote: On Thu, 26 Jun 2008 09:27:46 -0700, Craig White wrote: On Thu, 2008-06-26 at 18:08 +0200, Michael Schwendt wrote: On Thu, 26 Jun 2008 08:16:58 -0700, Craig White wrote: watching this thread with interest. I have several Dell Optiplex 320's that will not boot with grub but will boot with lilo and so I have lilo installed on them. Is this problem known upstream? very much so https://bugzilla.redhat.com/show_bug.cgi?id=379201 https://bugzilla.redhat.com/show_bug.cgi?id=219715 Those are about grub and the kernel. If you think grubby suffers from a bug when updating LILO installations, grubby is part of the mkinitrd package. Unfortunately though, kernel updates do produce the error above (unable to open /boot/boot.b) generated by grubby. Is there any way around getting grubby to re-run lilo to execute an update when new kernels are installed? With LILO, no. LILO must be rewritten with every change in lilo.conf. GRUB, on the contrary, must not be rewritten after modifying grub.conf, because it can read the ext2/ext3 fs directly to load its config file. If you're interested in where grubby is executed, take a look at /sbin/new-kernel-pkg which is called by the kernel package scriptlets. been there...never could figure out what to change as noted here... https://bugzilla.redhat.com/show_bug.cgi?id=219715#c18 Well, if you have reason to believe that grubby does something wrong, find out what it does wrong. Run it manually, it has a man page, too. And /boot/boot.b must exist when it is specified in lilo.conf. Do you say that grubby deletes that file by accident? And if you're really fed up with grubby, you could modify new-kernel-pkg to execute your own lilo-update script/program instead of grubby. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list -- Thomas Rabaix Internet Consultant -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: grubby: unable to open /boot/boot.b: No such file or directory
Now that I see you are remote...I would suggest that you run grub-install and use that instead of lilo because lilo support was dropped. grub-install /dev/sda though if you're still booted on FC4, it might only work if you run grub-install /dev/hda (depending on whether you are using ATA or SCSI drives) Craig On Thu, 2008-06-26 at 23:02 +0200, Thomas Rabaix wrote: Ok, my host install FC4 with lilo, so I update to F8. I suppose the update script from Fedora keep lilo and don't use grub at all. Now how can I reinstall lilo to make boot.b appears. I have only one chance :) (remote location) I am not sure that my system will reboot properly without this file, am i right ? Thanks Thomas On Thu, Jun 26, 2008 at 8:42 PM, Michael Schwendt [EMAIL PROTECTED] wrote: On Thu, 26 Jun 2008 09:27:46 -0700, Craig White wrote: On Thu, 2008-06-26 at 18:08 +0200, Michael Schwendt wrote: On Thu, 26 Jun 2008 08:16:58 -0700, Craig White wrote: watching this thread with interest. I have several Dell Optiplex 320's that will not boot with grub but will boot with lilo and so I have lilo installed on them. Is this problem known upstream? very much so https://bugzilla.redhat.com/show_bug.cgi?id=379201 https://bugzilla.redhat.com/show_bug.cgi?id=219715 Those are about grub and the kernel. If you think grubby suffers from a bug when updating LILO installations, grubby is part of the mkinitrd package. Unfortunately though, kernel updates do produce the error above (unable to open /boot/boot.b) generated by grubby. Is there any way around getting grubby to re-run lilo to execute an update when new kernels are installed? With LILO, no. LILO must be rewritten with every change in lilo.conf. GRUB, on the contrary, must not be rewritten after modifying grub.conf, because it can read the ext2/ext3 fs directly to load its config file. If you're interested in where grubby is executed, take a look at /sbin/new-kernel-pkg which is called by the kernel package scriptlets. been there...never could figure out what to change as noted here... https://bugzilla.redhat.com/show_bug.cgi?id=219715#c18 Well, if you have reason to believe that grubby does something wrong, find out what it does wrong. Run it manually, it has a man page, too. And /boot/boot.b must exist when it is specified in lilo.conf. Do you say that grubby deletes that file by accident? And if you're really fed up with grubby, you could modify new-kernel-pkg to execute your own lilo-update script/program instead of grubby. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: grubby: unable to open /boot/boot.b: No such file or directory
I hope that's /boot/grub/grub.conf that you're showing us...but it doesn't look right. if /boot is /dev/sda1, then is /boot in the same partition as / because your 'kernel' line is using the same partition. Typically, grub will use the partition label and not the dev handle... # man e2label # e2label /dev/sda1 /boot # e2label /dev/sda2 /1 This is what grub.conf looks like on my F8 system... # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/hda2 # initrd /initrd-version.img #boot=/dev/hda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title Fedora (2.6.25.6-27.fc8) root (hd0,0) kernel /vmlinuz-2.6.25.6-27.fc8 ro root=LABEL=/1 quiet rhgb quiet initrd /initrd-2.6.25.6-27.fc8.img title Fedora (2.6.24.5-85.fc8) root (hd0,0) kernel /vmlinuz-2.6.24.5-85.fc8 ro root=LABEL=/1 quiet rhgb quiet initrd /initrd-2.6.24.5-85.fc8.img Craig On Thu, 2008-06-26 at 23:53 +0200, Thomas Rabaix wrote: Ok, I will do what you advice. Just to make there is no misunderstanding, I do not have any more the FC4 on the systeme but only F8 (after multiple upgrade) So grub-install will install grub into the bootloader, I need first to convert the lilo.conf settings into a grub.conf settings. I have paste and copy what it look good for me. Can you tell me if it look right (sda1 = hd0,1) ? next, how do we know reboot will work, do we have a way of testing the setup ? Thanks, Thomas # cat lilo.conf prompt timeout=50 default=2.6.25.6-27.fc8 boot=/dev/sda map=/boot/map install=/boot/boot.b lba32 append= #serial=0,9600n8 image=/boot/vmlinuz-2.6.25.6-27.fc8 label=2.6.25.6-27.fc8 read-only root=/dev/sda1 initrd=/boot/initrd-2.6.25.6-27.fc8.img image=/boot/vmlinuz-2.6.24.7-92.fc8 label=2.6.24.7-92.fc8 read-only root=/dev/sda1 initrd=/boot/initrd-2.6.24.7-92.fc8.img image=/boot/bzImage-2.6.24.5--grs-ipv4-32 label=linux read-only root=/dev/sda1 # cat grub.conf default=0 timeout=50 title 2.6.25.6-27.fc8 root (hd0,1) kernel /vmlinuz-2.6.25.6-27.fc8 ro root=/dev/sda1 initrd /initrd-2.6.25.6-27.fc8.img title=2.6.24.7-92.fc8 root (hd0,1) kernel /vmlinuz-=2.6.24.7-92.fc8 ro root=/dev/sda1 initrd /initrd-2.6.24.7-92.fc8.img title 2.6.25.6-27.fc8 root (hd0,1) kernel /bzImage-2.6.24.5--grs-ipv4-32 ro root=/dev/sda1 On Thu, Jun 26, 2008 at 11:19 PM, Craig White [EMAIL PROTECTED] wrote: Now that I see you are remote...I would suggest that you run grub-install and use that instead of lilo because lilo support was dropped. grub-install /dev/sda though if you're still booted on FC4, it might only work if you run grub-install /dev/hda (depending on whether you are using ATA or SCSI drives) Craig On Thu, 2008-06-26 at 23:02 +0200, Thomas Rabaix wrote: Ok, my host install FC4 with lilo, so I update to F8. I suppose the update script from Fedora keep lilo and don't use grub at all. Now how can I reinstall lilo to make boot.b appears. I have only one chance :) (remote location) I am not sure that my system will reboot properly without this file, am i right ? Thanks Thomas On Thu, Jun 26, 2008 at 8:42 PM, Michael Schwendt [EMAIL PROTECTED] wrote: On Thu, 26 Jun 2008 09:27:46 -0700, Craig White wrote: On Thu, 2008-06-26 at 18:08 +0200, Michael Schwendt wrote: On Thu, 26 Jun 2008 08:16:58 -0700, Craig White wrote: watching this thread with interest. I have several Dell Optiplex 320's that will not boot with grub but will boot with lilo and so I have lilo installed on them. Is this problem known upstream? very much so https://bugzilla.redhat.com/show_bug.cgi?id=379201 https://bugzilla.redhat.com/show_bug.cgi?id=219715 Those are about grub and the kernel. If you think grubby suffers from a bug when updating LILO installations, grubby is part of the mkinitrd package. Unfortunately though, kernel updates do produce the error above (unable to open /boot/boot.b) generated by grubby. Is there any way around getting grubby to re-run lilo to execute an update when new kernels are installed? With LILO, no. LILO must be rewritten with every change in lilo.conf. GRUB, on the contrary, must not be rewritten after modifying grub.conf, because it can read the ext2/ext3 fs directly to load its config file. If you're interested in where grubby is executed, take a look at /sbin/new-kernel-pkg which is called by the kernel package
Re: problem with FC9 login screen
On Thu, 2008-06-26 at 07:33 -0700, Gerhard Magnus wrote: My login screen for Fedora 9 has only suspend, restart and shutdown buttons, plus the list of users. There's what looks like a panel bar at the bottom of the screen with nothing in it. I can login normally to the gnome desktop. How do I change the session to KDE from the login screen? (I specified including KDE during the installation.) After you select a username, gadgets appear to make those choices. Pick a user, pick your options, type your password, in that order of events. -- [EMAIL PROTECTED] ~]$ uname -r 2.6.25.6-55.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: F9/KDE4: Can't access screen resolution changes after software install
Don Levey fedora-list at the-leveys.us writes: I am unable to reconfigure my desktop at all. While the correct (1280x800) resolution is visible as a selection in System Settings, the Apply/Save button is not enabled. Sounds like: https://bugzilla.redhat.com/show_bug.cgi?id=445089 Kevin Kofler -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: grubby: unable to open /boot/boot.b: No such file or directory
Thomas Rabaix wrote: Ok, my host install FC4 with lilo, so I update to F8. I suppose the update script from Fedora keep lilo and don't use grub at all. not sure about this one. i could never get lilo to boot an fc4 install. i skipped fc4 - 7 and fresh installed f8 with grub for boot loader. i had continuous problems trying to get lilo to boot f8 and at time, grub was a practical and easy way out. i you *have to have* lilo, best to log their site and check forums, faqs for info. i understand it can be done and will check in future as to just how to do it. Now how can I reinstall lilo to make boot.b appears. I have only one chance :) (remote location) I am not sure that my system will reboot properly without this file, am i right ? run 'lilo -v -t enter' for 'verbose test' to see what will happen. being you are remote, if you have both fc4 and f8 installed, set your 'lilo.conf' to boot f8 via _selection_ and old kernel by default. this way, you fall back to a good install. hth. -- tc,hago. g . in a free world without fences, who needs gates. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: problem with FC9 login screen
Gerhard Magnus wrote: I'm still trying to find the file where the login screen parameters are stored: 'gdm' is in '/etc/gdm', 'kdm' is in '/etc/kde/kdm'. '/etc' is directory for configurations and a few other things, etcetera, etcetera, etcetera, etcetera. -- tc,hago. g . in a free world without fences, who needs gates. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: problem with FC9 login screen
On Thu, 2008-06-26 at 22:38 +, g wrote: Gerhard Magnus wrote: I'm still trying to find the file where the login screen parameters are stored: 'gdm' is in '/etc/gdm', 'kdm' is in '/etc/kde/kdm'. '/etc' is directory for configurations and a few other things, etcetera, etcetera, etcetera, etcetera. # cat /etc/sysconfig/desktop DESKTOP=KDE # makes default desktop KDE unless specified otherwise DISPLAYMANAGER=KDE # makes default DM kdm instead of gdm - require restart Craig -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Need help with Toshiba Tecra SD reader
fred smith wrote: On Thu, Jun 26, 2008 at 10:52:50AM -0500, Luis Orlindo Tedeschi wrote: I cannot access the SD reader of a Toshiba Tecra. I already tested several SD cards. The SD cards work fine under Windows XP and Mac X, but Fedora 9 does not recognize the reader/drive? Does anyone know how to install the driver for the SD reader? Thanks a lot. Luis I dunno the answer, but I wouldn't mind knowing--I've got one of those machines (belongs to the employer, but it's old enough that no one else wants it, so I guess it's mine to use as long as I want.) Depending on what chipset it uses, you may find this page helpful (TI chipset): http://openfacts.berlios.de/index-en.phtml?title=TI_FlashMedia_xx12/xx21_driver I don't remember where to find the Ricoh driver information is. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: Need help with Toshiba Tecra SD reader
On Thu, Jun 26, 2008 at 06:01:17PM -0500, Mikkel L. Ellertson wrote: fred smith wrote: On Thu, Jun 26, 2008 at 10:52:50AM -0500, Luis Orlindo Tedeschi wrote: I cannot access the SD reader of a Toshiba Tecra. I already tested several SD cards. The SD cards work fine under Windows XP and Mac X, but Fedora 9 does not recognize the reader/drive? Does anyone know how to install the driver for the SD reader? Thanks a lot. Luis I dunno the answer, but I wouldn't mind knowing--I've got one of those machines (belongs to the employer, but it's old enough that no one else wants it, so I guess it's mine to use as long as I want.) Depending on what chipset it uses, you may find this page helpful (TI chipset): http://openfacts.berlios.de/index-en.phtml?title=TI_FlashMedia_xx12/xx21_driver I don't remember where to find the Ricoh driver information is. Mikkel -- thanks, I'll check that out! -- Fred Smith -- [EMAIL PROTECTED] - I can do all things through Christ who strengthens me. -- Philippians 4:13 --- pgplSG9iRwDo3.pgp Description: PGP signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: grubby: unable to open /boot/boot.b: No such file or directory
ok, this is my partition table : sda1 and sda2 are ext3 /dev/sda1 9,9G 3,3G 6,1G 36% / /dev/sda2 449G 709M 425G 1% /var # e2label /dev/sda1 / # e2label /dev/sda2 /var Yes the file is located into /boot/grub/grub.conf. but there is not specific partition for grub, can it be an issue, does grub know how to read a etx3 partition ?. # cat /boot/grub/grub.conf default=0 timeout=50 title 2.6.25.6-27.fc8 root (hd0,0) kernel (hd0,0)/boot/vmlinuz-2.6.25.6-27.fc8 ro root=/dev/sda1 initrd (hd0,0)/boot/initrd-2.6.25.6-27.fc8.img let's try to understand the last 3 lines - root : Set the current root device to the device device, so the root here is sda1 so h0,0 in grub syntax - kernel : define the kernel to load, so we load the kernel from disk h0,0 with read only attribute (not sure about the need of this, does the system switch to rw after loading?) and we define the root to the kernel as /dev/sda1 (look redundant as it is the same as the grub one) - initrd : Load an initial ramdisk for a Linux format boot image and set the appropriate parameters in the Linux setup area in memory. not sure to get all the bytes, but I get that this file is use to load specific module from the distribution my only current doubt, is that the / and /boot are on the same partition. So grub cannot access to /vmlinuz that's it why I add (hd0,0)/boot/ to make sure grub can find the kernel. Am I wrong ? So in your opinion does the grub configuration look fine ? to g : # lilo -v -t LILO version 22.7.3 (test mode), Copyright (C) 1992-1998 Werner Almesberger Development beyond version 21 Copyright (C) 1999-2006 John Coffman Released 11-Aug-2006 and compiled at 20:26:28 on Aug 11 2006. Reading boot sector from /dev/sda Using MENU secondary loader Calling map_insert_data Boot image: /boot/vmlinuz-2.6.25.6-27.fc8 Mapping RAM disk /boot/initrd-2.6.25.6-27.fc8.img Added 2.6.25.6-27.fc8 * Boot image: /boot/vmlinuz-2.6.24.7-92.fc8 Mapping RAM disk /boot/initrd-2.6.24.7-92.fc8.img Added 2.6.24.7-92.fc8 Boot image: /boot/bzImage-2.6.24.5--grs-ipv4-32 Added linux The boot sector and the map file have *NOT* been altered. On Fri, Jun 27, 2008 at 12:05 AM, Craig White [EMAIL PROTECTED] wrote: I hope that's /boot/grub/grub.conf that you're showing us...but it doesn't look right. if /boot is /dev/sda1, then is /boot in the same partition as / because your 'kernel' line is using the same partition. Typically, grub will use the partition label and not the dev handle... # man e2label # e2label /dev/sda1 /boot # e2label /dev/sda2 /1 This is what grub.conf looks like on my F8 system... # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/hda2 # initrd /initrd-version.img #boot=/dev/hda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title Fedora (2.6.25.6-27.fc8) root (hd0,0) kernel /vmlinuz-2.6.25.6-27.fc8 ro root=LABEL=/1 quiet rhgb quiet initrd /initrd-2.6.25.6-27.fc8.img title Fedora (2.6.24.5-85.fc8) root (hd0,0) kernel /vmlinuz-2.6.24.5-85.fc8 ro root=LABEL=/1 quiet rhgb quiet initrd /initrd-2.6.24.5-85.fc8.img Craig On Thu, 2008-06-26 at 23:53 +0200, Thomas Rabaix wrote: Ok, I will do what you advice. Just to make there is no misunderstanding, I do not have any more the FC4 on the systeme but only F8 (after multiple upgrade) So grub-install will install grub into the bootloader, I need first to convert the lilo.conf settings into a grub.conf settings. I have paste and copy what it look good for me. Can you tell me if it look right (sda1 = hd0,1) ? next, how do we know reboot will work, do we have a way of testing the setup ? Thanks, Thomas # cat lilo.conf prompt timeout=50 default=2.6.25.6-27.fc8 boot=/dev/sda map=/boot/map install=/boot/boot.b lba32 append= #serial=0,9600n8 image=/boot/vmlinuz-2.6.25.6-27.fc8 label=2.6.25.6-27.fc8 read-only root=/dev/sda1 initrd=/boot/initrd-2.6.25.6-27.fc8.img image=/boot/vmlinuz-2.6.24.7-92.fc8 label=2.6.24.7-92.fc8 read-only root=/dev/sda1 initrd=/boot/initrd-2.6.24.7-92.fc8.img image=/boot/bzImage-2.6.24.5--grs-ipv4-32 label=linux read-only root=/dev/sda1 # cat grub.conf default=0 timeout=50 title 2.6.25.6-27.fc8 root (hd0,1) kernel /vmlinuz-2.6.25.6-27.fc8 ro root=/dev/sda1 initrd /initrd-2.6.25.6-27.fc8.img title=2.6.24.7-92.fc8 root (hd0,1) kernel /vmlinuz-=2.6.24.7-92.fc8 ro root=/dev/sda1 initrd /initrd-2.6.24.7-92.fc8.img title 2.6.25.6-27.fc8 root (hd0,1) kernel
Re: grubby: unable to open /boot/boot.b: No such file or directory
Just a missing note : file stage1 and stage2 are not present in /boot/grub Thomas On Fri, Jun 27, 2008 at 1:23 AM, Thomas Rabaix [EMAIL PROTECTED] wrote: ok, this is my partition table : sda1 and sda2 are ext3 /dev/sda1 9,9G 3,3G 6,1G 36% / /dev/sda2 449G 709M 425G 1% /var # e2label /dev/sda1 / # e2label /dev/sda2 /var Yes the file is located into /boot/grub/grub.conf. but there is not specific partition for grub, can it be an issue, does grub know how to read a etx3 partition ?. # cat /boot/grub/grub.conf default=0 timeout=50 title 2.6.25.6-27.fc8 root (hd0,0) kernel (hd0,0)/boot/vmlinuz-2.6.25.6-27.fc8 ro root=/dev/sda1 initrd (hd0,0)/boot/initrd-2.6.25.6-27.fc8.img let's try to understand the last 3 lines - root : Set the current root device to the device device, so the root here is sda1 so h0,0 in grub syntax - kernel : define the kernel to load, so we load the kernel from disk h0,0 with read only attribute (not sure about the need of this, does the system switch to rw after loading?) and we define the root to the kernel as /dev/sda1 (look redundant as it is the same as the grub one) - initrd : Load an initial ramdisk for a Linux format boot image and set the appropriate parameters in the Linux setup area in memory. not sure to get all the bytes, but I get that this file is use to load specific module from the distribution my only current doubt, is that the / and /boot are on the same partition. So grub cannot access to /vmlinuz that's it why I add (hd0,0)/boot/ to make sure grub can find the kernel. Am I wrong ? So in your opinion does the grub configuration look fine ? to g : # lilo -v -t LILO version 22.7.3 (test mode), Copyright (C) 1992-1998 Werner Almesberger Development beyond version 21 Copyright (C) 1999-2006 John Coffman Released 11-Aug-2006 and compiled at 20:26:28 on Aug 11 2006. Reading boot sector from /dev/sda Using MENU secondary loader Calling map_insert_data Boot image: /boot/vmlinuz-2.6.25.6-27.fc8 Mapping RAM disk /boot/initrd-2.6.25.6-27.fc8.img Added 2.6.25.6-27.fc8 * Boot image: /boot/vmlinuz-2.6.24.7-92.fc8 Mapping RAM disk /boot/initrd-2.6.24.7-92.fc8.img Added 2.6.24.7-92.fc8 Boot image: /boot/bzImage-2.6.24.5--grs-ipv4-32 Added linux The boot sector and the map file have *NOT* been altered. On Fri, Jun 27, 2008 at 12:05 AM, Craig White [EMAIL PROTECTED] wrote: I hope that's /boot/grub/grub.conf that you're showing us...but it doesn't look right. if /boot is /dev/sda1, then is /boot in the same partition as / because your 'kernel' line is using the same partition. Typically, grub will use the partition label and not the dev handle... # man e2label # e2label /dev/sda1 /boot # e2label /dev/sda2 /1 This is what grub.conf looks like on my F8 system... # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/hda2 # initrd /initrd-version.img #boot=/dev/hda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title Fedora (2.6.25.6-27.fc8) root (hd0,0) kernel /vmlinuz-2.6.25.6-27.fc8 ro root=LABEL=/1 quiet rhgb quiet initrd /initrd-2.6.25.6-27.fc8.img title Fedora (2.6.24.5-85.fc8) root (hd0,0) kernel /vmlinuz-2.6.24.5-85.fc8 ro root=LABEL=/1 quiet rhgb quiet initrd /initrd-2.6.24.5-85.fc8.img Craig On Thu, 2008-06-26 at 23:53 +0200, Thomas Rabaix wrote: Ok, I will do what you advice. Just to make there is no misunderstanding, I do not have any more the FC4 on the systeme but only F8 (after multiple upgrade) So grub-install will install grub into the bootloader, I need first to convert the lilo.conf settings into a grub.conf settings. I have paste and copy what it look good for me. Can you tell me if it look right (sda1 = hd0,1) ? next, how do we know reboot will work, do we have a way of testing the setup ? Thanks, Thomas # cat lilo.conf prompt timeout=50 default=2.6.25.6-27.fc8 boot=/dev/sda map=/boot/map install=/boot/boot.b lba32 append= #serial=0,9600n8 image=/boot/vmlinuz-2.6.25.6-27.fc8 label=2.6.25.6-27.fc8 read-only root=/dev/sda1 initrd=/boot/initrd-2.6.25.6-27.fc8.img image=/boot/vmlinuz-2.6.24.7-92.fc8 label=2.6.24.7-92.fc8 read-only root=/dev/sda1 initrd=/boot/initrd-2.6.24.7-92.fc8.img image=/boot/bzImage-2.6.24.5--grs-ipv4-32 label=linux read-only root=/dev/sda1 # cat grub.conf default=0 timeout=50 title 2.6.25.6-27.fc8 root (hd0,1) kernel /vmlinuz-2.6.25.6-27.fc8 ro root=/dev/sda1 initrd /initrd-2.6.25.6-27.fc8.img
Re: grubby: unable to open /boot/boot.b: No such file or directory
On Fri, 27 Jun 2008 01:23:21 +0200, Thomas Rabaix wrote: ok, this is my partition table : sda1 and sda2 are ext3 /dev/sda1 9,9G 3,3G 6,1G 36% / /dev/sda2 449G 709M 425G 1% /var # e2label /dev/sda1 / # e2label /dev/sda2 /var Yes the file is located into /boot/grub/grub.conf. but there is not specific partition for grub, can it be an issue, does grub know how to read a etx3 partition ?. Yes. It can read ext2/ext3 directly. It even loads its grub.conf that way. # cat /boot/grub/grub.conf default=0 timeout=50 title 2.6.25.6-27.fc8 root (hd0,0) kernel (hd0,0)/boot/vmlinuz-2.6.25.6-27.fc8 ro root=/dev/sda1 initrd (hd0,0)/boot/initrd-2.6.25.6-27.fc8.img let's try to understand the last 3 lines - root : Set the current root device to the device device, so the root here is sda1 so h0,0 in grub syntax GRUB's root is the partition on which the /boot directory is found. In your case: /dev/sda1 = (hd0,0) - kernel : define the kernel to load, so we load the kernel from disk h0,0 with read only attribute (not sure about the need of this, does the system switch to rw after loading?) and we define the root to the kernel as /dev/sda1 (look redundant as it is the same as the grub one) It *is* redundant because of the root (hd0,0) in the previous line. As an optimisation, I would boot with root=LABEL=foo instead of root=/dev/sda1 and give sda1 label foo and also update /etc/fstab. So in your opinion does the grub configuration look fine ? You can run grub as superuser root in a terminal and play in its command-line shell. Commands like grub find /boot/grub/grub.conf (hd0,7) (hd1,6) (hd1,8) should print (hd0,0) in your case. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: grubby: unable to open /boot/boot.b: No such file or directory
On Fri, 2008-06-27 at 01:23 +0200, Thomas Rabaix wrote: ok, this is my partition table : sda1 and sda2 are ext3 /dev/sda1 9,9G 3,3G 6,1G 36% / /dev/sda2 449G 709M 425G 1% /var wow - all that space in /var - this a db server? You're barely using any of the disk space allocated to /var # e2label /dev/sda1 / # e2label /dev/sda2 /var Yes the file is located into /boot/grub/grub.conf. but there is not specific partition for grub, can it be an issue, does grub know how to read a etx3 partition ?. # cat /boot/grub/grub.conf default=0 timeout=50 title 2.6.25.6-27.fc8 root (hd0,0) kernel (hd0,0)/boot/vmlinuz-2.6.25.6-27.fc8 ro root=/dev/sda1 initrd (hd0,0)/boot/initrd-2.6.25.6-27.fc8.img let's try to understand the last 3 lines - root : Set the current root device to the device device, so the root here is sda1 so h0,0 in grub syntax - kernel : define the kernel to load, so we load the kernel from disk h0,0 with read only attribute (not sure about the need of this, does the system switch to rw after loading?) and we define the root to the kernel as /dev/sda1 (look redundant as it is the same as the grub one) - initrd : Load an initial ramdisk for a Linux format boot image and set the appropriate parameters in the Linux setup area in memory. not sure to get all the bytes, but I get that this file is use to load specific module from the distribution my only current doubt, is that the / and /boot are on the same partition. So grub cannot access to /vmlinuz that's it why I add (hd0,0)/boot/ to make sure grub can find the kernel. Am I wrong ? So in your opinion does the grub configuration look fine ? Probably going to need someone else to verify because I am uncertain. Following this information http://docs.fedoraproject.org/release-notes/f8/en_US/sn-Installer.html#sn-label-disk-partitions read through this page...it's part of the installation notes for F8 you need to use labels in grub.conf - which is what I have been trying to tell you. thus I would think that this... title 2.6.25.6-27.fc8 root (hd0,0) kernel (hd0,0)/boot/vmlinuz-2.6.25.6-27.fc8 ro root=/dev/sda1 initrd (hd0,0)/boot/initrd-2.6.25.6-27.fc8.img should look like this... title 2.6.25.6-27.fc8 root (hd0,0) kernel /boot/vmlinuz-2.6.25.6-27.fc8 ro root=LABEL=/ initrd /boot/initrd-2.6.25.6-27.fc8.img that's what I was trying to tell you. What I can't tell you for certain if it will work without labels as you have it presently configured...I simply don't know. to g : # lilo -v -t LILO version 22.7.3 (test mode), Copyright (C) 1992-1998 Werner Almesberger Development beyond version 21 Copyright (C) 1999-2006 John Coffman Released 11-Aug-2006 and compiled at 20:26:28 on Aug 11 2006. Reading boot sector from /dev/sda Using MENU secondary loader Calling map_insert_data Boot image: /boot/vmlinuz-2.6.25.6-27.fc8 Mapping RAM disk /boot/initrd-2.6.25.6-27.fc8.img Added 2.6.25.6-27.fc8 * Boot image: /boot/vmlinuz-2.6.24.7-92.fc8 Mapping RAM disk /boot/initrd-2.6.24.7-92.fc8.img Added 2.6.24.7-92.fc8 Boot image: /boot/bzImage-2.6.24.5--grs-ipv4-32 Added linux The boot sector and the map file have *NOT* been altered. isn't that because you are running '-t' (test) instead of just installing? Craig -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: grubby: unable to open /boot/boot.b: No such file or directory
first, Graig, thanks for your help ! On Fri, Jun 27, 2008 at 1:40 AM, Craig White [EMAIL PROTECTED] wrote: On Fri, 2008-06-27 at 01:23 +0200, Thomas Rabaix wrote: ok, this is my partition table : sda1 and sda2 are ext3 /dev/sda1 9,9G 3,3G 6,1G 36% / /dev/sda2 449G 709M 425G 1% /var wow - all that space in /var - this a db server? You're barely using any of the disk space allocated to /var Well I know ... the service I use preformat the server, so I don't have any control on it. /var contains all files : www, mail and database. --- # e2label /dev/sda1 / # e2label /dev/sda2 /var Yes the file is located into /boot/grub/grub.conf. but there is not specific partition for grub, can it be an issue, does grub know how to read a etx3 partition ?. # cat /boot/grub/grub.conf default=0 timeout=50 title 2.6.25.6-27.fc8 root (hd0,0) kernel (hd0,0)/boot/vmlinuz-2.6.25.6-27.fc8 ro root=/dev/sda1 initrd (hd0,0)/boot/initrd-2.6.25.6-27.fc8.img let's try to understand the last 3 lines - root : Set the current root device to the device device, so the root here is sda1 so h0,0 in grub syntax - kernel : define the kernel to load, so we load the kernel from disk h0,0 with read only attribute (not sure about the need of this, does the system switch to rw after loading?) and we define the root to the kernel as /dev/sda1 (look redundant as it is the same as the grub one) - initrd : Load an initial ramdisk for a Linux format boot image and set the appropriate parameters in the Linux setup area in memory. not sure to get all the bytes, but I get that this file is use to load specific module from the distribution my only current doubt, is that the / and /boot are on the same partition. So grub cannot access to /vmlinuz that's it why I add (hd0,0)/boot/ to make sure grub can find the kernel. Am I wrong ? So in your opinion does the grub configuration look fine ? Probably going to need someone else to verify because I am uncertain. Following this information http://docs.fedoraproject.org/release-notes/f8/en_US/sn-Installer.html#sn-label-disk-partitions read through this page...it's part of the installation notes for F8 you need to use labels in grub.conf - which is what I have been trying to tell you. thus I would think that this... title 2.6.25.6-27.fc8 root (hd0,0) kernel (hd0,0)/boot/vmlinuz-2.6.25.6-27.fc8 ro root=/dev/sda1 initrd (hd0,0)/boot/initrd-2.6.25.6-27.fc8.img should look like this... title 2.6.25.6-27.fc8 root (hd0,0) kernel /boot/vmlinuz-2.6.25.6-27.fc8 ro root=LABEL=/ initrd /boot/initrd-2.6.25.6-27.fc8.img that's what I was trying to tell you. What I can't tell you for certain if it will work without labels as you have it presently configured...I simply don't know. Ok, I didn't know about all the label options. I will have a look tomorrow (French fedora user ...) with your indication and [EMAIL PROTECTED]'s one. to g : # lilo -v -t LILO version 22.7.3 (test mode), Copyright (C) 1992-1998 Werner Almesberger Development beyond version 21 Copyright (C) 1999-2006 John Coffman Released 11-Aug-2006 and compiled at 20:26:28 on Aug 11 2006. Reading boot sector from /dev/sda Using MENU secondary loader Calling map_insert_data Boot image: /boot/vmlinuz-2.6.25.6-27.fc8 Mapping RAM disk /boot/initrd-2.6.25.6-27.fc8.img Added 2.6.25.6-27.fc8 * Boot image: /boot/vmlinuz-2.6.24.7-92.fc8 Mapping RAM disk /boot/initrd-2.6.24.7-92.fc8.img Added 2.6.24.7-92.fc8 Boot image: /boot/bzImage-2.6.24.5--grs-ipv4-32 Added linux The boot sector and the map file have *NOT* been altered. isn't that because you are running '-t' (test) instead of just installing? Yes I just return the command asked by [EMAIL PROTECTED] Craig -- Thomas Rabaix Internet Consultant -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: grubby: unable to open /boot/boot.b: No such file or directory
On Fri, 2008-06-27 at 01:51 +0200, Thomas Rabaix wrote: first, Graig, thanks for your help ! On Fri, Jun 27, 2008 at 1:40 AM, Craig White [EMAIL PROTECTED] wrote: On Fri, 2008-06-27 at 01:23 +0200, Thomas Rabaix wrote: ok, this is my partition table : sda1 and sda2 are ext3 /dev/sda1 9,9G 3,3G 6,1G 36% / /dev/sda2 449G 709M 425G 1% /var wow - all that space in /var - this a db server? You're barely using any of the disk space allocated to /var Well I know ... the service I use preformat the server, so I don't have any control on it. /var contains all files : www, mail and database. --- # e2label /dev/sda1 / # e2label /dev/sda2 /var Yes the file is located into /boot/grub/grub.conf. but there is not specific partition for grub, can it be an issue, does grub know how to read a etx3 partition ?. # cat /boot/grub/grub.conf default=0 timeout=50 title 2.6.25.6-27.fc8 root (hd0,0) kernel (hd0,0)/boot/vmlinuz-2.6.25.6-27.fc8 ro root=/dev/sda1 initrd (hd0,0)/boot/initrd-2.6.25.6-27.fc8.img let's try to understand the last 3 lines - root : Set the current root device to the device device, so the root here is sda1 so h0,0 in grub syntax - kernel : define the kernel to load, so we load the kernel from disk h0,0 with read only attribute (not sure about the need of this, does the system switch to rw after loading?) and we define the root to the kernel as /dev/sda1 (look redundant as it is the same as the grub one) - initrd : Load an initial ramdisk for a Linux format boot image and set the appropriate parameters in the Linux setup area in memory. not sure to get all the bytes, but I get that this file is use to load specific module from the distribution my only current doubt, is that the / and /boot are on the same partition. So grub cannot access to /vmlinuz that's it why I add (hd0,0)/boot/ to make sure grub can find the kernel. Am I wrong ? So in your opinion does the grub configuration look fine ? Probably going to need someone else to verify because I am uncertain. Following this information http://docs.fedoraproject.org/release-notes/f8/en_US/sn-Installer.html#sn-label-disk-partitions read through this page...it's part of the installation notes for F8 you need to use labels in grub.conf - which is what I have been trying to tell you. thus I would think that this... title 2.6.25.6-27.fc8 root (hd0,0) kernel (hd0,0)/boot/vmlinuz-2.6.25.6-27.fc8 ro root=/dev/sda1 initrd (hd0,0)/boot/initrd-2.6.25.6-27.fc8.img should look like this... title 2.6.25.6-27.fc8 root (hd0,0) kernel /boot/vmlinuz-2.6.25.6-27.fc8 ro root=LABEL=/ initrd /boot/initrd-2.6.25.6-27.fc8.img that's what I was trying to tell you. What I can't tell you for certain if it will work without labels as you have it presently configured...I simply don't know. Ok, I didn't know about all the label options. I will have a look tomorrow (French fedora user ...) with your indication and [EMAIL PROTECTED]'s one. pay attention to Michael Schwendt - he's more knowledgeable than I am. He definitely suggested that you also change /etc/fstab to reflect the label mount instead of the device which was also suggested in the F8 Installation notes that I linked. Good luck Craig -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
